Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Where you quoting someone or are you arguing with yourself?
I was facetiously demonstrating the uselessness of "battery capacity" as a statistic when comparing mobile phones.


JulianL:
> It's always intrigued me why top-of-the-range iPhone batteries do tend to be smaller than their equivalents in Samsung high-end Galaxies etc.

It’s because iPhones are much more power efficient, and there is no point for them to spend more money on larger batteries.
While hardware may play some factor, I'd say it mainly comes down to software: iOS vs. Android. Blame Java? :^)
 
I was facetiously demonstrating the uselessness of "battery capacity" as a statistic when comparing mobile phones.



While hardware may play some factor, I'd say it mainly comes down to software: iOS vs. Android. Blame Java? :^)

So I have an iPhone 14 Pro Max but also a Galaxy Fold 4. I don't think Androids battery issue is Java, it probably doesn't help but I think also has minimal hit as they pre-compile on install so after that it should be fine.

I think the biggest issue is actually how Android does notifications. Not the user facing side of it but backend. Each app has its own background service running to pick up notifications. The more apps, the more you have in the background for this to work. Hence Androids requirement for more RAM on their phones and also why on some models RAM scales up with storage because more storage = more apps = more RAM used to background processes.

This is also why Android can have delayed or no notifications. Google has a process called Doze, a bit like Apples Background App Refresh where they schedule background running to help with battery life. The catch is you don't get your notifications until those background processes run. To add to this fire, Samsung will look for apps you've not used for a while and put them into deep sleep. It does warn you of this and also that you won't get notifications from those apps until you open them. But take a parcel app, I pretty much never open them but want to know when a parcel is coming. You can manually override this but it's a pain if you've tons of apps.

No such problem on iOS as there's one OS background process handling notifications for all apps. They don't have to be awake on iOS to listen for notifications, the OS handles it and wakes the app if needed when a notification comes in. It's just far better thought out.
 
  • Like
Reactions: Fred Zed
No such problem on iOS as there's one OS background process handling notifications for all apps. They don't have to be awake on iOS to listen for notifications, the OS handles it and wakes the app if needed when a notification comes in. It's just far better thought out.
I'm pretty sure Google's equivalent is GMS's FCM (that's "Google Mobile Services' Firebase Cloud Messaging"), which works very similarly and is used by nearly every app on the Play Store.

You can also "restrict battery usage [of an app running] in the background", which (as I understand it) prevents the app from running in the background entirely(?), only waking it periodically to check for notifications and whatnot.

There's also an option to prevent an app from "[using] mobile data in the background", which I guess prevents the app from using cellular data when not currently open, but it's not clear whether it can still use Wi-Fi or what have you... It might be a setting completely unrelated to this discussion, for all I know.

(This is all information from my Google Pixel 6 Pro, so results may vary on different devices. (who am I kidding, it's likely that most devices are *far* worse...)
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.