Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Nope. DRAM burns battery because it always has to be powered, even when the CPU is sleeping. Every 32 ms, the entire contents of RAM are read out from the array and rewritten. That means an iPhone sitting idle is reading and writing about 100 GB/s, even when the CPU has gone to sleep.
I think you are over exaggerating the battery power usage because the competition is able to handle it.
 
The A13 is Apple's first with sophisticated Clock Mgmt, & is the #1 reason Battery Life has improved in the 2019 iPhones.

By extension, I believe Apple's Software Team decided to try something similar with DRAM Mgmt, starting with iOS 13.2.

They clearly got it wrong with their first attempt, but at least now it's a priority.

IMO, the Timer addition in 13.3 may end up being a great compromise !

E.g., backgrounded apps get purged from DRAM after 5 minutes or so.

It's a BIG benefit when running High Perf apps, as well ! ... potential Game Changer to Extreme Perf Camera Apps !
 
The A13 is Apple's first with sophisticated Clock Mgmt, & is the #1 reason Battery Life has improved in the 2019 iPhones.

By extension, I believe Apple's Software Team decided to try something similar with DRAM Mgmt, starting with iOS 13.2.

They clearly got it wrong with their first attempt, but at least now it's a priority.

IMO, the Timer addition in 13.3 may end up being a great compromise !

E.g., backgrounded apps get purged from DRAM after 5 minutes or so.

It's a BIG benefit when running High Perf apps, as well ! ... potential Game Changer to Extreme Perf Camera Apps !
Whats this timer addition you speak of?
And yes my battery life is better under 13.2 compared to 12.4.1. I’m on an iPhone 7 too.
 
On second thought, I think they may have addressed the severe app closing bug.

It’s 10 PM and I just went on my phone and on Amazon and Safari and they did not relaunch, and I last opened them in the afternoon.

When the bug was present, the relaunch was rather instantaneous the moment I would leave the app.

hopefully this addresses my main issue with YouTube closing in the background the moment I pause the video in Control Center
 
Okay, this definitely fixed it for me. YouTube is not instantly restarting.
 
Its no use, I am tired of this cat and mouse game where every release fixes something and breaks something else. I am told this is just the nature of software today because its so complicated.

I wish Apple would at least let us run the OS+Software we find stable enough until we decided to upgrade when there are features we really would like to have instead of sending nagging notifications daily to upgrade to the latest buggy release. Pulling support on older OS's from Apple and 3rd party party do not allow us to do this.
 
Not even a mention of the more obvious one where it can brick iPhones during the update from iOS13.x
 
I'm guessing this is why Spotify would stop playing randomly; around the 5-10min timeframe. I downgraded to 13.1.3 and haven't had any issues.
 
It’s only one of many bugs in iOS 13 (such as the web page preview when long pressing a link that now shows about 1 inch of the top of the page only).

I am pretty convinced that iOS 13 is going to be one of those bad memory releases where it never gets it right. Time to write this one off, hunker down and wait for iOS 14
 
  • Like
Reactions: femike
The A13 is Apple's first with sophisticated Clock Mgmt, & is the #1 reason Battery Life has improved in the 2019 iPhones.

By extension, I believe Apple's Software Team decided to try something similar with DRAM Mgmt, starting with iOS 13.2.

They clearly got it wrong with their first attempt, but at least now it's a priority.

IMO, the Timer addition in 13.3 may end up being a great compromise !

E.g., backgrounded apps get purged from DRAM after 5 minutes or so.

It's a BIG benefit when running High Perf apps, as well ! ... potential Game Changer to Extreme Perf Camera Apps !
Battery life improved roughly in line with the battery size increase. I believe Anandtech did not find much in terms of efficiency improvements in A13 compared to the predecessor.
 
  • Like
Reactions: femike
Aaron is the best reviewer and he’s always on top of what’s new. He’s straight and to the point.
 
The issue caused apps like YouTube and Safari to reload more frequently than normal, with the software "aggressively" shutting down background apps and tasks.

This whole issue shows the dangers of relying on the internet for TECHNICAL explanations and understanding.

There was a real problem, yes, but as far as I can tell (my experience and reading what others say) it was NOT an "iOS 13.2 multitasking" problem, it was a problem with web-type stuff. "Non-web" multitasking (ie apps that weren't presenting web pages or web page wrappers) worked, IMHO, better in 13.2 than before (in the sense that apps stayed alive without being killed or losing state) for longer, and in the face of more other apps being launched, than in 13.1 or earlier.

Does this difference matter? Well it doesn't matter if your only interest is complaining to Apple to fix it. But it does matter if you want to understand what is going on (or at least want to present yourself as such...)
 
This whole issue shows the dangers of relying on the internet for TECHNICAL explanations and understanding.

There was a real problem, yes, but as far as I can tell (my experience and reading what others say) it was NOT an "iOS 13.2 multitasking" problem, it was a problem with web-type stuff. "Non-web" multitasking (ie apps that weren't presenting web pages or web page wrappers) worked, IMHO, better in 13.2 than before (in the sense that apps stayed alive without being killed or losing state) for longer, and in the face of more other apps being launched, than in 13.1 or earlier.

Does this difference matter? Well it doesn't matter if your only interest is complaining to Apple to fix it. But it does matter if you want to understand what is going on (or at least want to present yourself as such...)
Not sure about that. Playing a downloaded episode in Prime Video and pausing it for a bit to the point where the screen turns off and then unlocking the phone again would end up needing to fully relaunch the Prime Video app and selecting the episode to resume where you were before.
 
Not sure about that. Playing a downloaded episode in Prime Video and pausing it for a bit to the point where the screen turns off and then unlocking the phone again would end up needing to fully relaunch the Prime Video app and selecting the episode to resume where you were before.

Isn’t that what I said? Prime video is probably a thin wrapper around a web page...

Point is, this may well have nothing to do with multi-tasking per se. It may, for example, be a security measure (perhaps rushed out...) that deliberately prevents a web page from persisting after losing focus because (somehow?) that allowed for JS to escape the sandbox. Now that Apple have been able to figure out a decent solution, such an aggressive quick fix is no longer necessary.
 
Prime video is probably a thin wrapper around a web page...
Is it?
[automerge]1573085291[/automerge]
Point is, this may well have nothing to do with multi-tasking per se. It may, for example, be a security measure (perhaps rushed out...) that deliberately prevents a web page from persisting after losing focus because (somehow?) that allowed for JS to escape the sandbox. Now that Apple have been able to figure out a decent solution, such an aggressive quick fix is no longer necessary.
It may, or may not. It may have something web related to it, or it may not. As far as able being able to figure out a decent solution vs. an aggressive quick fix -- what particular details are known about it all?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.