After the backup-reset-restore dance, I also did a sign out from iCloud then login again. This improved the battery life a lot on my SE 2016. It will need to run detection on your photos again (should be mostly done while charging), but otherwise no excessive power use.I've got SE 1st gen with 11 months old battery (replaced through Apple). iOS 14 melts through battery, even thought I tried clean install. I regret upgrading a lot. If I leave my phone idle for night, I lose about 30% battery and 'battery setting page' shows that nothing was running at the time.
It most likely has alreadyI dont know... I guess I am lucky. But I think it will start to fall under 100% soon.
I don't think so.It most likely has already
Not sure about that as my router broadcasts a dual signal but if you try the reset and restore let us know if it works for you. It didnt make a difference for meHas anyone ever noticed 5GHz Wifi has worse battery life than 2.4? On my iPhone 8 that has been a problem historically.
I still feel like 14.0.1 is worse than 13 on battery life. It's better than 14.0, so I guess there is that. I'm tempted to do the iCloud backup/wipe/restore from backup dance.
If iOS 14.1 (soon) doesn't help, maybe try signing out of iCloud (waiting for a bit) then signing back in.Looking at apps doesn't help as it doesn't really list anything. I deleted all widgets, no background app refresh, etc. I don't have an Apple watch but I still tried a reset and restore which did nothing.
Thank you. I'm hoping 14.1 releases soon but will try that if it doesn't (or doesn't help!)If iOS 14.1 (soon) doesn't help, my try signing out of iCloud (waiting for a bit) then signing back in.
I now have near 12 hour battery life on my iPhone SE. Which is not stellar, but but much better than the 33% drain I saw a few weeks ago.
Sign out of iCloud on your devices - Apple Support
If you want to stop using iCloud on one of your devices, learn how to sign out and what happens when you sign out.support.apple.com
Battery life does seem better with the 14.1.Thank you. I'm hoping 14.1 releases soon but will try that if it doesn't (or doesn't help!)
Aside from the problematic update and battery drain, 5GHz may drain more battery as transfer speeds are higher, so it uses slightly more CPU.Has anyone ever noticed 5GHz Wifi has worse battery life than 2.4? On my iPhone 8 that has been a problem historically.
I still feel like 14.0.1 is worse than 13 on battery life. It's better than 14.0, so I guess there is that. I'm tempted to do the iCloud backup/wipe/restore from backup dance.
This brings hope! Did you get it OTA or downloaded the build?For me anyway I can confirm 14.1 GM fixes battery issues. About time
Downloaded and flashed in dfu modeFor me anyway I can confirm 14.1 GM fixes battery issues. About time
If iOS 14.1 (soon) doesn't help, my try signing out of iCloud (waiting for a bit) then signing back in.
I now have near 12 hour battery life on my iPhone SE. Which is not stellar, but but much better than the 33% drain I saw a few weeks ago.
Sign out of iCloud on your devices - Apple Support
If you want to stop using iCloud on one of your devices, learn how to sign out and what happens when you sign out.support.apple.com
iPhone SE 2016, taking it off the charger -> having to charge again = almost 12 hours.SE2020? But it's in general? I asume it's not screen time. The most far I've got it's almost 7h
I dont think thats the case. They have logs which show them what was using battery power. If they had seen something about a motion sensor draining battery it would probably be in the logs. they most likely did not reproduce the issue, or just havent solved it yetiPhone SE 2016, taking it off the charger -> having to charge again = almost 12 hours.
Screen on time is almost independent of that. It could be 5 hours, it could be a bit over 2.
I have the suspicion it might have something to do with the motion sensor keeping the iPhone awake. Had it laying on my bed at night, off the charger, and it had used only a little bit of battery.
I suppose with these huge iPhones, even the developers always have their phones laying on tables, not in their pockets, not moving. So the motion -> CPU wake-up -> going to sleep path never gets tested.