iPhone Performance Degrades as Battery Ages
geekbench.com
geekbench.com
- Do you degrade performance but leave screen-on time relatively unchanged?
- Do you degrade screen-on time but leave performance relatively unchanged?
Most Android devices seem to do the opposite (lose screen-on time, but keep performance relatively unchanged). Different people will have a different perspective on what the "right" strategy is for this, but I think we can all agree that better transparency and maybe even leaving it to the consumer to make the choice would be welcome.
PS - "Planned obsolescence" only applies if Apple was doing this artificially. It seems like if they didn't degrade performance you'd lose screen-on time instead, so you'd still likely replace the handset and perhaps even sooner (since core services e.g. calling, texting, etc, work even with lower performance but not on a phone out of juice).
In effect, right now, on old devices, Low Power Mode is always either fully-enabled, or half-enabled, but never fully-disabled. All they'd have to do is to change it from a binary switch (between enabled and {disabled, secretly half-enabled}) to a three-level switch.
People don’t want to lose battery life? Ok, we can adjust so it doesn’t change much over the life of the phone.
Of course that just lead to ‘Apple slows your phone down’.
You’re right, it’s a tough spot.
I’m sure that would go over GREAT.
For laptops, as part of their hardware test they had a chart for the battery. The expected cycle count was listed in quite a few places (it was 200 for removable batteries and jumped to 1000 when they started making them non-removable). X was the cycle count and Y was the battery's maximum charge (I tried to find pics, but couldn't). The chart had a diagonal red line marked "defective." They replaced your battery if it was within the defective range, but not if your cycle count was too high.
Phones aren't any different, they're just more hand-wavy about the battery (they don't show or mention cycle-counts).
Most people don't understand that the degraded battery is the cause of the performance issues (its not very intuitive), so they should explicitely say that.
I wish there were phones built like the old IBM thinkpads. Bulky, square, ugly but also indestructible and fully user servicable with replaceable batteries.
And if they do find a way, they'll just make the phone even thinner instead.
It's not about Apple not being able to do it. It's about their priorities. And in this case their priorities seem to coincide (as if by magic) with getting people to upgrade the phones faster.
It's especially silly when you consider that Apple, a design-focused company, is making phones thinner despite using very obvious camera bumps on their phones -- a clear sign that maybe their phones shouldn't be that thin.
They’ve obviously determined that it’s not worth it on the regular iPhone. I guess their surveys and stuff show that their customers would rather have the thin phone, on the whole.
Thinness is just a side-effect of lightness, because the alternative—a “hollow” unevenly-dense phone—would be awkward and unbalanced in the hand. You make a phone lighter, keep the screen size the same, repack it to an even density to keep its center of gravity the same... oops, it’s thinner now.
An interesting thought, but is it true? I cant really think of people complaining of arm fatigue from holding up a ~150-200g phone -- the effort of holding up your arm and hand alone are going to be substantially more than additional weight of the phone.
I also dont really see any evidence of phone manufacturers decreasing weight over the years, at least with a quick review of Apple's iPhones, which have definitely increased in weight over the past decade.
And increasing the length of a phone use-session is important, because it "unlocks" experiences people wouldn't otherwise bother with, that might then increase their total satisfaction with the ecosystem, and so increase brand loyalty. For example, some people just don't want to read books on their phones... but hand them a lighter phone, and they suddenly change their minds. They don't realize that that's the difference; it just is. And this might be the first device that got them to read e-books—which means they now associate the positive feelings of reading books in situations they wouldn't have otherwise been reading, with your device.
> which have definitely increased in weight over the past decade
They do increase, but only to a point; far less than if it weren't an optimization problem between increasing battery mass to power the features promised, vs. decreasing total mass.
Also of note is the fact that as phones are made more durable, people use cases less, which decreases total in-hand weight. So switching various pieces from plastic to aluminum, or one type of glass to another, may be a win even if it increases the base mass of the phone, as long as it decreases the probability that the user will feel the need to buy a case.
The iPhone X is significantly heavier than any previous (non-plus) iPhone, which is by far my biggest complaint about it.
I wonder what percentage people who buy those razorthin phones end up adding a millimeter or more to their phones by adding tempered glass screen protectors and cases over them. IMO, that defeats the purpose of the thinness.
Having e.g. 50% more battery wouldn't do anything for me. It would save me that one day per year when I'm using a ton of GPS/video and actually run out of battery before I go to bed, but that's about it. I'd still have to remember to charge it every night.
But the problem is that the iPhones seems to last a day only when they are new-ish and there is no safety buffer down the road. If it is fine on release day it will not be fine after 2 years if there additional capacity build in.
I'm all for that - I do want all the power of the hardware and a full days charge, for the whole lifetime of the phone.
Unfortunately it's very much in the sellers interest to not do this. If they make it last 100% of a dayt on release they can instead make it cheaper/lighter/more powerful, AND if they throttle or make it behave worse some other way after 2 years, they also make it obsolete at just the right point in time.
I switched from a MBP to a ThinkPad because of Apple's decisions with product design; performance sacrificed for purely aesthetic reasons.
I thought my thinkpad x201 was like a tank, but then random shutdowns became more frequent. I disassambled the laptop 4-5 times, replaced thermal paste, checked connections, replaced all software (including BIOS), couldn't find a solution. Then I stumbled upon a 45 page thread at the lenovo support forum. Many people were claiming the existence of the exact problem, but the only solution was to "replace the motherboard".
At least, apple offers world-wide decent for their products. With used thinkpads, you're basically on your own, no matter how tech-savvy you are.
If I were to purchase another laptop for on-the-go usage I will think twice before opting out for a thinkpad for it's durability.
Thinkpads are marvelous machines, but in my experience not all that glitters is gold :).
I wouldn't want to have a user replacable battery behind a hatch if it made the phone worse in any way (less water sealed, less sturdy etc).
These batteries can be replaced but Apples absolute refusal to enable customer or 3rd party repair make all of this infinitely more difficult.
(It's not just screen-on time, a naturally expected decline in operating time. As the batteries age resistance goes up and peak currents decline, so in some circumstances the device would actually hard turn off)
As others have pointed out in this thread the batteries aren’t hard to replace; this is just not something you can do directly as a user. That probably makes sense; it’d be difficult to make a super-thin smartphone while at the same time provide an easy way to replace each part.
In the best case you get one that works properly, if you're unlucky you might get one that has lower capacity, and if you're very unlucky you might just get one that puffs up and catches on fire.
Not really! iFixit and others have done the hard work for you there (I work at iFixit).
If you need a reference: https://www.cnet.com/news/its-time-to-kiss-that-removable-sm...
Those are guesses, which is why I used "probably" and "it’d be". Glueing parts together takes less space so it makes sense they use that to make phones thinner. I’ve yet to find a single smartphone with the iPhone 7’s thickness and a replaceable battery. The Fair Phone has a replaceable battery, but it’s thicker than every iPhone since the 3GS from 8 years ago.
A better option is a larger battery, but without that, I think they make more customers happy than I'd they did the alternative.
On balance, the expected behavior for an aging phone is to suffer from decreased battery life as total battery cycles increase. Apple instead has chosen to decrease system performance to hide diminished battery life, and failed to disclose this. This kind of behavior wouldn't be tolerated in other market segments. Can you imagine the public backlash against an auto manufacturer that shipped a vehicle which intentionally decreased performance as its fuel tank drained in order to boost their 'maximum range' metric, but never disclosed this 'feature' to the public?
Familiarity with electronics doesn't matter. We can't allow vendors to simply simply cover up what are normal behaviors from components given typical operating conditions.
Nobody wants a DVD player which throws up an error and stops playing if the disk is scratched, compared to retrying then skipping on a few frames.
Nobody wants a streaming video which stops playing if there's temporary bandwidth problems instead of pixelating briefly and coming back.
Nobody wants ECC memory or hard disk error correction or parity bits removed and corrupt data to become more common because it's "normal behaviour".
Nobody wants fanless video cards that overheat and break permanently instead of slowing down a bit and staying working.
People do want run-flat tyres because they'd rather keep going instead of getting normal behaviour of hitting something sharp.
People do want sat nav which recalculates the route in the case of "typical operating conditions" of making a wrong turn, covering up the normal behaviour of "giving bad directions from then on" with much more useful behaviour of "giving good directions".
Yes it would be great if everyone went to Shenzhen and made their own iPhone from scratch but I’d much rather Apple handle the details for me and my parents and grandparents...
I’m the only one that would be slightly entertained by the harsh realities of batteries being used under duress.
Apple does have an alternative. The battery issue is neither irreversible nor has any permanent ramifications to the remedy of just replacing the f-ing battery. In fact I have no problem with graceful degradation as a stopgap. Explicit Power Saving modes already do that.
But the issue at hand is completely orthogonal and has to do with why Apple refuses to, at the same time as undervolting, also signal to the user the one sane action to take, which is to obtain a battery replacement. By not signaling such and misdirecting (whether intentional or not), they are passive-aggressively telling the user to replace the entire phone. How else would a typical user interpret this situation? In what way could they know the appropriate action to take from observation? You think a company that prides itself on every meticulous detail of the UX just "missed" this?
https://www.quora.com/Why-does-my-car-feel-more-powerful-aft...
A couple of people there speculate that's what happens to them.
I doubt there would be much backlash - stranding a driver with an empty tank is about the worst thing that could happen short of a breakdown. "Yes of course we do everything we can to help you get to a fuel stop"
Your phone battery has been abused for years and you expect it to hold a charge?!
It’s a much much better decision to slow it down than let the phone die.
This would be a non educated (and possibly excessive) reaction, but - given the success of the iPhone - what happens in reality is that another (still non educated and still excessive) reaction happens:
“this phone sucks the battery dies in 10 minutes zomg I’ll go and buy the new x phone!”.
They already let you choose lower mode on charge < 20%, why not extend it for older devices.
... unless they would rather I just buy a new device.
I'm guessing this is why my previous Samsung phone used to unexpectedly restart, and semi-predictably do so when I activated the torch. I never realised it could have been due to the battery output dropping.
I don't think Screen on Time is the concern (though I admit that article isn't extremely clear). Given that devices were shutting down at 40% capacity I think it was more of a brown-out condition, where the device shut down despite having more energy left in the battery.
Given:
1. Battery voltage decreases as charge decreases.
2. Battery voltage sags as current draw increases, due to internal resistance.
3. Internal resistance increases with battery wear.
4. If battery voltage drops too low the phone will turn off.
a moment of high current draw could cause a device to suddenly shut down. Since this issue was endemic to 6S devices, perhaps some unusually large number of those batteries had unusually high internal resistance due to wear.
If this were the case the fix would be to reduce peak power draw and thus peak performance. This change would be especially evident in geekbench, but could also affect regular usage since mobile devices typically try to alternate (sleep) -> (high performance) -> (sleep).
There aren’t only two solutions to this problem.
(Technically you can still replace the iPhone battery, unfortunately it isn’t trivial like in the bad old days when phones didn’t have high def touch screens.)
So I’d argue it’s both a solution and a tradeoff.
1. Allow performance to degrade
2. Allow longevity to degrade
3. Allow the battery to be replaced
4. Some revolutionary battery technology that doesn't degrade??
What solutions are you thinking of?
Wrong company, pal. Apple historically decides for the user. Heck, they still do it with their App Store. Often that may go right, but not always.
So if you did that and instead of a battery combined it with a (relatively large) capacitor (or some sort of amazing spring) you could have the iPhone equivalent of a shake and shine flashlight. (One bonus being that there would be absolutely no holes, as it would not be possible to charge it via a wall outlet).
It would be completely impractical, but there wouldn't be a battery, so the battery wouldn't degrade. The alternative storage mechanism might degrade, and who knows what all of the shaking would do to the delicate electronics, likely nothing good.
Anyway, I think it'll catch on. I look forward to watching young people on the train shake their iPhone vigorously before making a silly face and taking a picture of themselves in 10 years time.
To try to salvage your analogy, I'll put forth an anecdote. Last year I restored my deceased father's 1988 Bronco II. One of the issues it had was low fuel pressure, which I narrowed down to the in-tank fuel pump (the Bronco was over-engineered and had two pumps, one in the tank and one on the frame). It wasn't able to push fuel fast enough for the engine to run at top performance. Sound familiar? So I had two choices, replace it myself or take it to a shop, kind of like how you can attempt to replace your phone's battery if you know what you're doing, or take it to a repair shop and let a pro do it for a fee. I'm a competent shadetree mechanic, so I did it myself and saved a few hundred dollars, and it is back to normal operation again.
Imagine that some cars allow the gas tank to be changed by the user. But this one doesn't.
Imagine the company that makes the car never mentions the shrinkage or the gradual reduction in top speed, and has no program or system that allows you to fix this - beyond buying a newer car.
I've bought dozens of Android replacement batteries and the only batteries worth the cost of shipping were actual real OEM ones. And those always cost >$60. Knockoffs would start out decent and then die within a few weeks to months.
Apple's approach gets my vote. You get the upside of built-in battery and the peace of mind when you do need a replacement.
[Just to balance that, let me be clear that Apple's choice with regard to crippling my phone pisses me off. I just replaced an iPhone 6 that felt painfully slow and now I know why (I had tested the battery and it was at 75% -- I didn't realize replacing it would speed up the phone).]
It really is DIY. There are thousands of guide that can be followed successfully.
Now, I completely agree with the design decisions of the iPhone. The completely sealed body is great for water resistance and having the battery replaced is still pretty cheap, especially if you use (I usually just let someone replace with a 3rd party battery for cheap, as this usually takes place after warranty expired).
The battery needs to have extra space (or bad things will happen) so it effectively has to be fixed on one side inside the body. Gluing it is a pretty cheap solution to that problem.
The easiness of replacing the battery has gone up with iPhone 7/8/X compared to iPhone 6. You can verify this on iFixit guides. The iPhone 6 is _relatively_ easy to replace because you don't need say a heatgun. You do need some special screwdrivers which you gotta buy. You can, on iFixit. I just bought a whole kit (on sale during Black Friday).
> I've bought dozens of Android replacement batteries and the only batteries worth the cost of shipping were actual real OEM ones. And those always cost >$60.
20 EUR for mine: https://shop.fairphone.com/en/spare-parts/fairphone-2-batter...
Replacing any parts on my phone is very easy. Only thing is that the main module with CPU board etc is ~300 EUR.
A great way to increase the odds of an explosion near your face or office desk!
My iPhone 5 also did that, after a while, it worsened so much that the screen colors became affected. I took it to an apple store, paid the fee and had them replace the battery.
IMHO a swollen battery is a huge risk, and apple should have replaced my phone without charge.
Anyways, be careful and if the battery is swollen, it's time for yet another battery change :)
With a good heat gun and toolkit, it's doable in anything from 15-30 min (more if the case is bent or damaged from falls).
In most Android phones (the ones I have used, at least), replacing the battery took less than one minute.
If iPhone X lasted 5 years with the same perf and battery life with two $100 battery replacements, I would happily shell out $1200 for it. But I know it won't last more than 2 years (like almost every other phone at this point), and then the math doesn't work out for me.
http://www.jiayu-store.com/jiayu-g5-quad-core-mtk6589-4-5-in...
https://www.gizchina.com/2013/11/07/jiayu-g5-unboxing-hands-...
The Jiayu also has dual SIM, microSD, USB, and costs a fraction of the Apple while having a more rigid and expensive housing (stainless steel, not aluminium.) Apple could, if they wanted to, make a phone with as much user-friendly features if not more, but they deliberately chose not to.
iOS could do the same, scaling down those useless effects and transparencies, boosting performance and guaranteeing a more qualitative experience.
(This is a really nice feature, compared to, e.g., sudden shutdown when voltage drops too low to run the CPU at normal speed.)
The problem is that iOS doesn’t alert you about what’s happening. If it said something like, “Your battery needs to be replaced. Until it is, your phone will run with reduced speed.” Then you would have the information you need to make an intelligent choice.
You have to suspect Apple doesn’t do this because if you don’t know what’s going on you’re likely to assume your phone is just old and needs to be replaced.
Source: I have 6s+, noticed it was slow recently, after some updates but not right after. Read about this. Got GeekBench and battery test. It tests normal when the battery is full, slower when battery is less full.
(It wouldn’t surprise me if the GPU or something else in the rendering pipeline was even more affected than the CPU. There were previously long delays in things that just seem to be screen rendering. Those delays aren’t just faster now, but are completely gone.)
Battery life is great, though!
(Myself included. I’ve been noticing for a while that my 6 Plus was running dog slow. Thanks to all this coming out last week I just replaced my battery using a kit from Amazon, and indeed, it now runs well again.)
The vast majority of those circuits are sleeping pretty much all the time. However as you get older your battery keeps up.. except those challenging times when you activate too many things. Like say nav (that runs the GPS, GPU, 3D chip, CPU, radio, compass, etc). Then the phone just turns off because there's not enough voltage.
Many people complain about "crashing" phones, claiming less reliability over time. Seems like often it's just the battery that can't manage the needed number of volts under load. You can witness this when ever less intensive things crash, but they all work if you are plugged in.
The sad thing is that these new top of the line smart phones could be useful for 5-10 years. Fit/finish with glass/aluminum, top spec CPU/RAM, expandable storage, etc. Sadly the epoxied battery reduces the practical life to 2-3 years.
In what world would a modular/expandable phone (like has been attempted several times) decide you might want to add fancy speakers, fancy camera, 3d vision, etc. But STILL expoxy in the battery? WTF?
I wish the government would stem in and just mandate that phones have user replaceable batteries to keep them from just filling the landfills after a few years.
My iPhone 6 was faultless prior to the upgrade to iOS 11, and immediately after it battery life was greatly reduced and it now shuts down automatically when the battery hits 10%.
Apparently I am now supposed to accept that the battery has degraded not gradually but all at once and on the same day as I upgraded iOS, and this is now being managed for my benefit by the OS. Hmmm...
Now I have an Android phone. (Not especially happy about it.)
well, non-replaceable battery and all...
The issue IMO, is it's not obvious that the battery needs to be replaced and when. It's not holding charge > new battery is far more obvious than it's slow > new battery. Most people probably prefer a slow phone than one without charge however Apple should have some indication of what's going on.
They wouldn't even LET ME PAY FOR THE REPAIR.
Then you would know that it is totally their fault and the liability would be on Apple to fix other people's devices.
My phone randomly shuts down or rapidly loses battery once it is below 40%. It's even worse when it's cold.
Or you know, Apple could make it easy for the user to replace the battery by themselves. But they chose not to.
This is the engineering equivalent of saying, "Why doesn't someone just go to the Middle East, sit down at a round table with with the Israelis and Palestinians and Sunnis and Shiites and rebels and Baathists and Saudis and ISIS members and refugees and all those other guys, and help them work out their differences peacefully?"
And yet, they didn't. The world didn't need yet another security screw.
If the market wanted such a thing, then guess what... the market would get it.
At the very least, the performance should improve if you plug in the phone, and it doesn't.
Edit: other thing I remember is that when I upgraded iOS10 at one point my battery _stopped_ being reliable. I was getting the unexpected shutdowns at <50%.
Another weird thing I had experienced: after every update, my battery percentage would be totally screwy. I'd burn from 100% -> 1% in no time, then sit at 1% for hours. Over charge cycles, it'd figure it out again, but that'd be reset every time I upgraded.
Edit 2: looks like I angered the fans. This is simply my experience. My geekbench scores were awful, so I was certainly impacted by this issue. I thought I'd done something wrong until this news came out.
Last night, I finally succumbed to iOS11 (the only reason I did was that I wanted to enroll in Heart Study, for which your iphone device has to be iOS11).
Indeed I had been pushing it away because I usually associate the word "upgrade" to device death when it comes to mobile devices.
But wow... it did not screw my 6S up. In fact, I think it's faster and 'zippier' with this iOS11 upgrade.
It improved after a few weeks. Not sure if it was an .x update that fixed it, or maybe it needed time to reindex (?) but it's fine now.
(Also, the repair is free if the battery's capacity has declined to <80% while under warranty. If you pay for two-year AppleCare+ [$99], you've basically pre-paid for a free battery replacement [normally also $99] at the two-year mark, as long as you've used—abused?—your phone heavily enough to wear its battery down by then. So, Bad Life ProTip: if you have AppleCare, make sure to run your battery flat a lot to get its capacity down, so as to get your money's worth.)
Unless I'm missing something, AppleCare on new iPhones is limited to two years ... which, in my experience, is just shortly before iPhone batteries degrade noticeably.
Edit: no, they do run concurrently. See child post.
GP’s edited the reference to 3 years anyway.
I bought a new iPhone about 48 hours ago and was told the same thing as shown above.
I think my confusion was that Mac AppleCare used to be advertised as an additional 2 years (you could buy it as your standard warranty expired) but it’s now advertised as 3 years from device purchase too. Wonder when that changed…
iPhone comes with 1 year warranty. AppleCare+ extends that an additional year for a total of 2 years from purchase date.
From the site you linked above: "Every iPhone comes with one year of hardware repair coverage through its limited warranty and up to 90 days of complimentary support. AppleCare+ for iPhone extends your coverage to two years from the original purchase date of your iPhone and adds up to two incidents of accidental damage coverage, each subject to a service fee of $29 for screen damage, or $99 for any other damage, plus applicable tax. In addition, you’ll get 24/7 priority access to Apple experts via chat or phone."
What he said is the case within the European Union due to some EU law regarding warranties. I believe in the EU an extended warranty like AppleCare only goes into effect after the original warranty has expired. There are also statutory warranty periods of a year (I think) for devices like the iPhone.
In the United States, on the other hand, AppleCare replaces the original warranty rather than adds onto it.
Here's a page describing AppleCare within the UK: https://www.apple.com/uk/legal/statutory-warranty/, which lasts for three years instead of the two within the United States.
> Up to 2 years from date of purchase for Apple TV, iPad, iPhone, iPod, Apple Watch or Apple Watch Sport
With the price of iDevices rising there's probably a "reasonability" court case brewing where someone argues that a £1200 iPhone X should last longer than 1/2 years.
Edit: https://europa.eu/youreurope/citizens/consumers/shopping/gua... says the default statutory warranty should be 2 years. What a mess.
https://www.ifixit.com/Store/iPhone/iPhone-6-Replacement-Bat...
Battery should be a cake walk.
They admitted that was unusual and just gave me a new battery.
Not in my experience. Bring your iphone to an apple shop and ask for the battery to be replaced. Apple will most likely refuse unless the battery is shown as severely damaged in the settings.
Something like "is intentionally reduced" may be more accurate.
My Android (1st Gen Moto G, running Lineage OS, about 3 years old) shuts down once the battery level hits 15%. You can actually see it change from 15% to 1% for one brief moment before it shuts down.
Sure, the battery is old, but this behavior is unlike the behavior of any other OS/device I've seen. I've seen some laptops with seriously messed up batteries and as far as I can remember, the OS reports a smooth discharge profile without steep drops and without and strange "surprises".
I think Android is probably not taking battery health into account when it reports remaining capacity, but that is only a guess.
It is a bit tricky, but well worth it.
https://www.makeuseof.com/wp-content/uploads/2012/02/power_s...
My Samsung Android phone shuts down at 5-7% battery life. And the battery dies much faster these days. But it's never "inaccurate." It doesn't jump from 50% to 2% over a course of five minutes.
Other than something else being wrong with your OS, my only guess there would be the battery got bad so quickly the OS hasn't adapted to the new life cycle yet by removing enough of the old datapoints.
100-60 is still decent.
I think I even commented on the bugreport that it would be best to do the frequency scaling based on interrupts from the voltage regulators on board, but that piping all the necessary drivers/events to do that with low enough latency to not cause an under-voltage reset was far more work than was feasible.
Thats also why 60fps video dropped frames at the start of the video if you were recording video with less than 60% battery.
Anyone care to dig out the relevant commit...?
I have a long history with almost every Android device. The device doesn't get slower, the battery life just gets terrible.
Other devices suffer from similar effects - not as bad, but most devices certanly lose quite a bit of I/O performance (especially writes) over time which makes OS run noticably slower.
There are literally billions of Android devices. Benchmarking file system performance is trivial. Ergo, where are the benchmarks supporting your broad claims? This should be incredibly easy to demonstrate. We do know that it happened pre TRIM because people had factory new and after use benchmarks, and could show the decline.
The biggest killer, though, is storage with the graphite electrode more than 50% lithiated - there is a gigantic step-up in capacity fade when batteries are stored with the State of Charge over around 90%, which Tesla are very smart to avoid.
BTW the car won't actually let you drive at low charge, so yes, you can be stranded because the car refuses to damage its battery. That's why it comes with a towing service.
Since that happened I've been putting off installing the iOS updates because this degradation in performance, after an iOS update, has been way too common of a theme over the years.
Stuff that I could see is the battery percentage, example:
``` default 08:44:30.015519 +0100 coreduetd CDDBatteryMonitor: received batterycallback, currentPercentage:94.555824! ```
You can install it via 'brew cask install coconutbattery'
Anyone know why? Was iOS 10 the "Snow Leopard of iOS releases", with more of a performance focus?
Whenever I announce an update my users suddenly become hyper-sensitive and start reporting bugs that have been present for weeks/months. I wouldn't be surprised if there's a similar effect here.
What's going on my phone that it grinds to a halt? Why does a factory reset sometimes help, but sometimes not?
It can't just be that the workloads are more resource intensive. If I go get an old tablet it will take 5x as long to load google.com as the day I bought it.
A resets might improve performance of the flash device if it frees up additional space or does something similar to an SSD "trim" event.
Once upon a time, google.com was like five lines of HTML. Google loved to brag about how they didn't even close their tags, because the page still rendered and it saved bytes.
Now I measure it at 300+ lines and 200KB, not counting assets.
Same generally goes for every software you know and love.
If you take your 5yo tablet and load the 5years younger OS, a 5years younger app or a 5 year younger version of google, those are designed to be "usable" on modern hardware, and "just bearable" on your older hardware. So it's not apples to apples then. You are running an app (or page) that is much much fatter. And yes it even applies to the google front page.
Calculating a kernel density estimate just seems to add an unneccesary step between raw data and the visualization. It can hide some shortcomings in the data (e.g. low number of samples), but doesn’t add anything.
No, the effect is exactly the same as you can see from the charts since they peak at the same benchmark scores. It is the distribution of those effects that is different, with the performance being negatively affected for more phones. But keep in mind that under iOS 11.2.0, most iPhone 6S's that are tested are probably about 2 years old. Under iOS 10.x, most iPhone 6S's probably about 1 year old. I'd like to know the distribution of the times that these Geekbench benchmarks were run. If scores for one phone model in one month are one average score under iOS (x) but is substantially lower the next month under iOS (x+1), then I would consider that to be a significant act of "planned obsolescence".
But really Apple should probably be more transparent about this. And the bottom line for users is that if you notice any kind of significant performance degradation, whether it is fast battery drainage or sluggish performance, you should consider taking the phone in.
I had a old Air which ran very slowly and fans spinning like crazy due to a issue with the cable from the keyboard/touchpad. Apparently if the SMC does not get proper signals it will go into a "failsafe" where things work but slowly.
Probably not the same issue, but just a little anecdote on a similar symptoms caused by different issues so that nobody gets tunnel vision on the battery, which might very well be the cause in this case.
iFixit guide for removing your heatsink: https://www.ifixit.com/Guide/MacBook+Pro+13-Inch+Retina+Disp...
My favorite thermal paste: https://noctua.at/en/nt-h1.html
when I saw the reddit post I was like GTFO
At least it wasn't because they are trying to force us to upgrade. I'm going to try an update the battery and see if it makes a difference.
Not that this will stop the conspiracy loons foaming at the mouth in their apple hate, obviously.
Also, after 3-4 years with a laptop, you typically start to see decreased performance because of clogging of fans, degradation in the thermal paste, etc. This causes the CPU to run hotter and throttle sooner to stay inside of its thermal envelope.
The clandestine nature of how apple has provided this feature would not work in their favour.
If battery scaling is a feature, then why isn't it mentioned by Apple? Why do we need a Reddit thread and a third party benchmarking tool to figure it out?
Also, why does the google search for "iphone slow" peak every time a new iPhone is released (https://trends.google.com/trends/explore?date=all&q=iphone%2...)? Is it purely psychological? I can't find there are no similar spikes for "android slow" or "samsung slow" or similar searches.