sci.electronics.repair@googlegroups.com

Google Groups

bruce2bowser@gmail.com: Jan 09 02:33AM -0800 IMO

bitrex <bitrex@de.lete.earthlink.net>: Jan 08 11:26PM -0500 On 11/17/2017 01:30 AM, Phil Allison wrote:   > Google the idea.   > .... Phil   It's one of those ideas that sounds both plausible and really clever except for the small detail that it doesn't work. Like extracting audio from ancient times off the decorative grooves cut into clay pots while spun on a wheel

Adrian Caspersz <email@here.invalid>: Jan 01 07:03PM > It's official. They are in a different time zone....   > Happy New Year martians !!!   https://www.ted.com/talks/nagin_cox_what_time_is_it_on_mars   -- Adrian C

Chris <ithinkiam@gmail.com>: Jan 08 06:30PM >> have been more transparent about it.   > It's not just an issue of transparency, if the user experience is being > impacted   My point is that the user experience wasn't impacted until *after* the discovery. Only then did people go, "Oh yeah. My phone /is/ slowing down." Post hoc discovery is hard to trust.   > to mitigate the problems of a battery that is degrading prematurely > in order to avoid warranty replacements, that's a problem in itself.   I don't think there's any evidence that batteries were degrading prematurely on a large scale.

Chris <ithinkiam@gmail.com>: Jan 08 06:35PM >> - not just swear and tear.   > I think a battery that prevents the device from running at full speed > because the unit shuts down would be considered to be "truly defective".   Eventually all batteries do that. How the batteries are (mis)used controls how soon that happens.   I can't imagine you're suggesting that all worn out batteries be replaced for free, so where would *you* draw the line?

"pfjw@aol.com" <pfjw@aol.com>: Jan 08 10:51AM -0800 Please stop feeding the Troll. There is no discussion (or conversation) to be had here. This horse is dead, skinned, quartered, flayed, flensed, rendered and jerked - and was so since the very first post on the subject.   Peter Wieck Melrose Park, PA   p.s.: I expect Jimmy Neutron will re-constitute itself as a new alias any moment now, as it has pretty much used this one up. So, please be aware and do not respond to the next iteration.

Brian Gregory <void-invalid-dead-dontuse@gmail.com>: Jan 09 01:07AM On 02/01/2018 06:14, JF Mezei wrote:   > The product development of the X was done with knowl;edge of the > batterty problems for the 6s. So it is possible that it was fixed or > significantly reduced.   I understood that this was a problem with the particular batteries originally used in the iPhone 6 (or whichever one(s) it was) and that newer batteries were expected have a longer life before their internal resistance increases enough to cause problems.   --   Brian Gregory (in England).

Brian Gregory <void-invalid-dead-dontuse@gmail.com>: Jan 09 01:11AM On 02/01/2018 16:43, Jolly Roger wrote:   > False. Android phones absolutely do throttle the CPU secretly with no > warning:   > <https://stackoverflow.com/q/11883404/6540130>   Well yes of course the CPU gets throttled to prevent overheating.   Apple is throttling because the batteries seem to age in a way that makes them incapable of powering the device properly at full speed and the device then crashes and unexpectedly reboots or locks up.   --   Brian Gregory (in England).

nospam <nospam@nospam.invalid>: Jan 08 08:18PM -0500 In article <yJidnQxOXLdQi8nHnZ2dnUU78S_NnZ2d@giganews.com>, Brian > > warning:   > > <https://stackoverflow.com/q/11883404/6540130>   > Well yes of course the CPU gets throttled to prevent overheating.   all types of throttling count.   > Apple is throttling because the batteries seem to age in a way that > makes them incapable of powering the device properly at full speed and > the device then crashes and unexpectedly reboots or locks up.   all batteries age that way.   unless the device actively manages power to avoid it, there is a risk of shutdown.   <http://www.androidpolice.com/2016/12/20/some-nexus-6ps-have-developed-a- battery-early-shutoff-problem-and-its-becoming-a-safety-issue/> A number of Nexus 6P owners have reported an alarming battery problem with their phones as of Android 7.0 being released for the handset, which causes the phone to power down when the battery gauge still shows anywhere from 10 to 60% battery remaining. ... Interestingly, it seems the problem is most common in very cold climates. These are where we see reports of phones dying at upwards of 60% battery remaining indicated, which is obviously completely ridiculous.

Harry Newton <harryne_wton@AlliOSusersJustGiveUp.com>: Jan 09 02:20AM On Tue, 9 Jan 2018 01:11:40 +0000, Brian Gregory wrote:     > Apple is throttling because the batteries seem to age in a way that > makes them incapable of powering the device properly at full speed and > the device then crashes and unexpectedly reboots or locks up.   You have to realize that you're dealing with nospam, who delights in presenting what is an illogical argument, as his only defense of the facts.   He's expert at this (like a defense lawyer is expert at it).   You have to remember that the Apple Apologists always try to deflect blame whenever facts they don't like show up here (nospam, Jolly Roger, BKonRamp, Lewis, Savageduck, Snit, etc.).   Very few of these Apple Apologists appear to have a formal education so they're not aware that others don't buy their illogical crap - to wit - nospam says Android phones do the same thing - but it's not at all the same thing.   Only Apple *secretly*, *permanently*, and *drastically* cut CPU speeds (to about half the original speeds based on the reports I posted prior) as a "solution" to extend the life of their products.   The major Android manufacturers are on record emphatically stating they would never do what Apple did to their customers.   That's a fact the Apple Apologists will try to dance around. But it's still a fact.

Harry Newton <harryne_wton@AlliOSusersJustGiveUp.com>: Jan 09 02:20AM On Mon, 8 Jan 2018 18:35:10 -0000 (UTC), Chris wrote:   > how soon that happens.   > I can't imagine you're suggesting that all worn out batteries be replaced > for free, so where would *you* draw the line?   Bearing in mind that it's a fact Apple doesn't test its products in the real world (they say the real world is "not supported"), it's a fact that Apple was blindsided by the iPhone shutdowns (they admitted this).   That means they didn't test them since it's a *lot* of phones that shut down.   Now when they finally figured out the reason (on the second pass, by their own admission), they had a choice to make as to how to "respond".   1. They could *secretly*, *drastically*, and *permanently* throttle CPU perofrmance (to about half the original speeds) hoping to not get caught... or ... 2. They could openly come clean, and recall the defective phones, and provide a trade in of a suitable phone that wasn't defective.   It was their choice. It was worth the risk if they didn't get caught (just like VW did). But they got caught.   These are facts.

Harry Newton <harryne_wton@AlliOSusersJustGiveUp.com>: Jan 09 02:20AM On Mon, 8 Jan 2018 18:30:09 -0000 (UTC), Chris wrote:     > My point is that the user experience wasn't impacted until *after* the > discovery. Only then did people go, "Oh yeah. My phone /is/ slowing down." > Post hoc discovery is hard to trust.   That's not true. Did you read the Harvard Study which, admittedly, was a second or even third-order effect - but still - plenty of people noticed the slowdown - and plenty noticed the phones just shutting off also.   Likewise, the entire point is that the benchmark results were CLEAR and OBVIOUS that the CPUs were throttled.   What it took people time was to *realize* that they weren't the only ones secretly, permanently, and drastically throttled.   So the very fact it was noticed is proof it was noticed.   >> in order to avoid warranty replacements, that's a problem in itself.   > I don't think there's any evidence that batteries were degrading > prematurely on a large scale.   Then Apple apologized for nothing.   Silly Apple. They have so many lawyers and marketing people (the best in the world) ... it's funny they made a mistake for apologizing for nothing.   And all those silly lawsuits alleging harm. Silly people.   When Apple *secretly*, *permanently*, and *drastically* cuts CPU performance after only a year of use, why should Apple apologize for that.   The good news is now, moving forward, we all know to basically halve any benchmark you see for any Apple iPhone because Apple says that they will continue to halve the performance of their phones after about a year.   Hence, an iPhone X is really, after a year, an iPhone V (1/2 X) in terms of CPU performance.

Harry Newton <harryne_wton@AlliOSusersJustGiveUp.com>: Jan 09 02:20AM On Tue, 9 Jan 2018 01:07:54 +0000, Brian Gregory wrote:   > originally used in the iPhone 6 (or whichever one(s) it was) and that > newer batteries were expected have a longer life before their internal > resistance increases enough to cause problems.   All we can tell you is that Apple stated they will *continue* to throttle phones (literally, to half speed, permanently, although no longer secretly since the cat is out of the bag).   We can give you the references where journalists have been led to believe the iPhone X will be throttled to something like an iPhone V (1/2 X) in just about a year also (see prior referenced quote).   So, basically, from this point forward, you logically can take any benchmark or phone comparison spec, and halve the benchmark results for the iPhones, so as to arrive at a realistic "one year later" comparison.   There is no other logical way to compare phone benchmarks at this time if Apple is true to their word of drastically throttling CPUs after about a year of use in the future also.   Logical rule of thumb moving forward: Halve every iPhone benchmark result.

You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page. To unsubscribe from this group and stop receiving emails from it send an email to sci.electronics.repair+unsubscribe@googlegroups.com.