this post was submitted on 22 Sep 2023

34 points (85.4% liked)

Apple

17127 readers

7 users here now

Welcome

to the largest Apple community on Lemmy. This is the place where we talk about everything Apple, from iOS to the exciting upcoming Apple Vision Pro. Feel free to join the discussion!

Rules:

No NSFW Content
No Hate Speech or Personal Attacks
No Ads / Spamming
Self promotion is only allowed in the pinned monthly thread

Lemmy Code of Conduct

Communities of Interest:

Apple Hardware
Apple TV
Apple Watch
iPad
iPhone
Mac
Vintage Apple

Apple Software
iOS
iPadOS
macOS
tvOS
watchOS
Shortcuts
Xcode

Community banner courtesy of u/Antsomnia.

founded 1 year ago

MODERATORS

MichelleG@lemmy.world

RoyalEngineering@lemmy.world

thisisdee@lemmy.world

iOS17 - Battery Drain Worse Than Recent Beta (lemmy.world)

submitted 11 months ago by 353247532631@lemmy.world to c/apple_enthusiast@lemmy.world

29 comments fedilink hide all child comments

Has anyone else seen a dramatic drop in battery life after updating to the final release of iOS 17?

My 12 Pro was doing fine on the last few beta releases and the battery life has tanked in the last week or so. I’m not doing anything different, so I wanted to see if other beta users saw the same change after updating.

top 29 comments

sorted by: hot top controversial new old

[–] skbo@lu.skbo.net 29 points 11 months ago (2 children)

Isn’t this the same with every major iOS release? The OS needs to rebuild its caches, and that tends to impact on battery life, for a time, and then everything goes back to normal…

[–] HollandJim@lemmy.world 8 points 11 months ago

Yes, every single major release, we have to repeat ourselves on this. Tiresome!

[–] 353247532631@lemmy.world 1 points 11 months ago (2 children)

Genuine question: Would the caching/reindexing have been different between the later beta releases and the final release? Would those incremental beta releases not have triggered the process each time? If not, then this explanation makes sense, though the one thing that doesn’t make sense is that I’m still seeing lower life after a full week.

Regardless, it seems like a nuke and pave is probably in order to see if that corrects the issue.

[–] skbo@lu.skbo.net 3 points 11 months ago

I don’t think there’s any difference between the beta and the final release in this regard (generally, the official release has the same build number than the latest release candidate).

From what I understand, the process can take a lot of time, as it happens in the background, when the phone is not actively used. And for power users that install .0 versions day one (which is really not a thing to do, but that’s not the point here), I imagine they will dig everything they can from these new versions, leaving less time for background processes to be run.

[–] Earthwormjim91@lemmy.world 2 points 11 months ago

The final public beta and the release version are exactly the same build.

[–] ScoobyDoo27@lemm.ee 12 points 11 months ago (4 children)

My phone feels about the same but watchOS 10 wrecked my Apple Watch. I used to end the day at 30-40% and now it’s barely hanging on by 7pm

[–] possum@lemmy.world 5 points 11 months ago (1 children)

I noticed the same on my Series 4, which, as old as it is, used to last me through the day with about 30% left by 8pm. I had to turn on the low power mode yesterday at noon with around 60% and then it died by 7pm

[–] Nikls94@lemmy.world 3 points 11 months ago (1 children)

It’s about the same here for me. It’s just not made to handle that much color all the time.

I get the feeling that it’s not going to get WatchOS 11.

[–] possum@lemmy.world 1 points 11 months ago

I wouldn’t be surprised if it didn’t get WatchOS 11. In fact, I think the Series 4 and 5 will be considered obsolete next year since they are using basically the same SiP.

[–] 353247532631@lemmy.world 2 points 11 months ago

I’ve seen the same with my series 6. I would usually end the day around 35% and now it is under 10%

[–] garretble@lemmy.world 2 points 11 months ago

My series 5 had had a big drop in battery life, too. I hope they figure it out because I do like the update.

[–] jonno@discuss.tchncs.de 1 points 11 months ago

Same here. Not sure I’ll update to a new Apple Watch though. Coros is looking really nice and affordable.

[–] chiisana@lemmy.chiisana.net 6 points 11 months ago

14 Pro Max; resisted beta until mid/late August; upgraded to 21A329 a little bit back; no noticeable battery drains on both beta and current version here.

Perhaps some settings got botched during one of the earlier betas and problem just started to surface in final? Try a backup and restore to see if that’d resolve it?

[–] James_Ryan@feddit.de 4 points 11 months ago

My battery life has been bad since 16.x Barely 2 hours sot I already reseted the phone Until now it is even worse on 17.0

Hope .1 does help

[–] krousenick@lemmy.world 4 points 11 months ago

Back it up, and dfu restore the phone, then restore from back up. Probably something corrupted. I havent had any real issue on the same model.

[–] ultratiem@lemmy.ca 3 points 11 months ago

Reset all settings.

[–] Ocelot@lemmies.world 2 points 11 months ago

Ive had horrible battery life in my 14 pro since 16.6.1. Just installed 17 yesterday and it still seems at least as bad.

[–] malloc@lemmy.world 1 points 11 months ago

Haven’t noticed any difference. I’m on a XS max

[+] circuitfarmer@lemmy.sdf.org -10 points 11 months ago (3 children)

Maybe I'm entirely wrong: isn't this the forced obsolescence that Apple is famous for? If it isn't, could someone explain to me why?

Not at all trying to be obtuse, but this is exactly what is meant by "forced obsolescence".

[–] DavidGA@lemmy.world 12 points 11 months ago (1 children)

Maybe I'm entirely wrong: isn't this the forced obsolescence that Apple is famous for?

Apple does not and never has practiced forced obsolescence. In fact, quite the opposite, as iOS is supported in iPhones for much longer than any version of Android ever is.

The "famous" story is about Apple keeping your phone alive by (necessarily) throttling the CPU when your battery was worn out, so that it wouldn't shut down due to lack of power.

If they did anything wrong, it was not explaining this well enough.

[–] kayazere@feddit.nl 1 points 11 months ago (1 children)

It’s a different story for their computers. Macs from 2017 are not supported by Sonoma. It’s pretty terrible to have a desktop/laptop obsoleted at 6 years.

[–] DavidGA@lemmy.world 3 points 11 months ago (1 children)

Sonoma not supporting your Mac does not mean that it is obsolete. Apple still supports macOS Big Sur with updates, and that came out in 2020.

Macs that can’t run Sonoma will continue to be supported for many more years.

[–] kayazere@feddit.nl 1 points 11 months ago

Once Sonoma is out, Big Sur won’t see any more security updates. Apple only updates the lastest three versions of macOS.

The bigger problem is software applications increasing there minimum macOS version very quickly once Apple stops supporting the OS version.

Apple is the worst with this with Xcode increasing the minimum macOS version each year. You can’t stay on old Xcode versions, at least for iOS development, as Apple requires a certain version to submit to the AppStore. This in effect causes devs to have to buy new hardware quickly after Apple drops support.

[–] Earthwormjim91@lemmy.world 6 points 11 months ago (1 children)

It’s not really forced obsolescence unless they intentionally made it perform worse on older phones, or stopped supporting older devices entirely.

The most reasonable explanation is that iOS 17 was designed first and foremost to take advantage of the advances in the 3nm a17 chip, while supporting older chips as a secondary benefit.

It’s not optimized for older devices at launch because it’s designed for the new devices, and will be updated and patched as time goes on. Staying in iOS 16 on an older device until a few minor versions into iOS 17 will likely see better battery life on older devices.

I’ve been on a base 12 for 3 years, battery health at 88%, and iOS 17 is perfectly usable for me. I’ve been on the beta since the first public release. Battery life is a little worse, sure but still perfectly usable with no noticeable performance hits. I’m giving it to my dad when my 15 pro max gets here and it will likely last him another 3 or more years, probably needing a battery replacement in a year or so though.

[–] circuitfarmer@lemmy.sdf.org -5 points 11 months ago (2 children)

unless they intentionally made it perform worse on older phones

What I'm suggesting is that this is exactly why performance got worse after the beta. It's a pattern seen from Apple for a long time.

There is nothing intrinsic about a smaller manufacturing process that transfers into software, unless they've secretly added new instructions to the set. What it does mean is that the new chips should be more power efficient, which means in turn that the same software on new hardware should already translate into battery life gains. What we see instead is software "tuned" for the new version to minimize gains on one side and suggest to existing customers that they need an upgrade.

[–] Earthwormjim91@lemmy.world 2 points 11 months ago

Every developer develops for the newest devices first and foremost. Across the board.

There is nothing intrinsic about a smaller manufacturing process that transfers into software, unless they’ve secretly added new instructions to the set. What it does mean is that the new chips should be more power efficient, which means in turn that the same software on new hardware should already translate into battery life gains.

Orrrrr what it means is that the software can take advantage of the more efficient hardware and push harder while maintaining similar battery life. Which is what most manufacturers typically do.

What we see instead is software “tuned” for the new version to minimize gains on one side and suggest to existing customers that they need an upgrade.

Welcome to every piece of technology ever made. If you want the latest and greatest software performance, you need to buy the latest and greatest hardware.

Being less optimized doesn't mean you need to upgrade. You may need to charge a little more often but that's the trade off for running new software on older hardware. You can still run the latest software and don't need to upgrade.

Apple supports iPhones for a minimum of 6-7 years. The iPhone XR from 2018 is supported for iOS 17, 6 years and 6 major OS updates. It will keep getting iOS patches until they stop doing OS updates on iOS 17 sometime late next year. They support security updates for even longer. They just released a security update for the iPhone 5s, released in 2013, in January this year. Almost 10 years later.

Forced obsolescence is MUCH more common with Android phones. An $1800 Pixel Fold released in June this year, 2023, is only going to get Android updates until June 2026. 3 years for a nearly $2000 device. You will HAVE to buy a new phone if you want new software after that. Which is absolutely ridiculous for Google, who develop Android ffs. An iPhone 12 Pro Max from 2020 will be supported longer than that.

A Galaxy fold, another nearly $2000 device, will only be supported for 4 years before you will HAVE to buy a new phone to get a new version of Android.

Most other Android phone makers, especially the budget ones, only give 1-2 years of support, if that.

And again, OP's case is anecdotal. I have a base iPhone 12 from the same year, and have been running the iOS 17 betas since the first public one and have seen no drops in battery life. The first beta had a little worse battery life but the following ones fixed it a bit. The last public beta from a little while back is the exact same as the release version. You don't even get a separate update for the release version if you are still on the beta profile, and if you want to leave the beta once you are on the RC, you just turn off beta updates and you will only get the release versions from then on. If OP is suddenly seeing a huge battery life difference, it isn't the version they are on because they have been on it longer than they have been seeing the issue. There are things they could look at, which others in the thread have given, and they could look at their battery health. That's a 3 year old battery and it may just need a replacement depending on how hard they have driven it over the last 3 years. Batteries are consumable parts and need replaced.

[–] conciselyverbose@kbin.social 1 points 11 months ago

No, it isn't. It has never once happened.

Doing more demanding things to take advantage of better hardware is not "forced obsolescence". It's just progress.

[–] 353247532631@lemmy.world 4 points 11 months ago* (last edited 11 months ago) (1 children)

I’m certainly suspicious of them intentionally not fixing some performance bugs until later to encourage people to upgrade now that the new phones are launching.

The fact that the battery drain has gotten worse with the final iOS 17.0 version is what really made me suspicious and why I wanted to see what others have experienced.

The joke is on them (or, really, me) because I have a 15 pro arriving tomorrow anyways.

[–] circuitfarmer@lemmy.sdf.org 0 points 11 months ago

The fact that the battery drain has gotten worse with the final iOS 17.0 version is what really made me suspicious and why I wanted to see what others have experienced.

Yeah, exactly my point. I'm not saying they break things or make them unusable. But it does seem clear that they detune software to get a mix of slightly better performance on the next gen (below what the hardware improvements suggest) and significantly worse-than-possible performance on older devices to try and force upgrades.