this post was submitted on 04 Jun 2025
46 points (97.9% liked)
Asklemmy
49358 readers
1026 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Decided to go the let app run in the background on graphene. With 3 apps in the background running all the time. Battery last 12 hours, with heavy use less. I'm unaware of how to get or self host push notifications outside of Google. It's not death to your battery but it defintely shaves off 20 percent and that's a rough number.
I've been using a pixel for 2 years with 600 plus cycles and my battery health is still 100 percent excellent, I did a hardware health check today.
Great. Now do 40 apps and try not to get them killed by the OOM mechanism. I'm not saying I like the fact that messages go through Google's servers, but I'm afraid there is no equivalent FOSS solution.
The problem isn't really 40 apps keeping connections open. That shouldn't cause much battery drain or RAM usage. Really really heavy emphasis on "shouldn't".
Too many shitty apps that keep doing shit when running in the background instead of just waiting for data to arrive. So Google takes the sledgehammer approach and just doesn't let apps do that and instead makes them rely on Google's one dedicated background app that they know behaves.
Good guy Google. Guess what? The developer of apps can deliberately hide or delay the push notifications if it detects its background optimization is enabled. Really, really emphasize on "can", not "should".