You need to change battery optimization for the affected apps (well, the apps you don't want hibernated instantly).
Some brands of phones have aggressive hibernation config for all apps by default (Samsung, Xiomi I think).
Lookup hibernation control for your brand of phone.
Also check out https://dontkillmyapp.com/
GrapheneOS. It keeps Termux and Molly (for MollySocket) open but nothing else.
Thanks for this thread. I just switched to GrapheneOS and noticed the same thing. It's particularly annoying having my Lemmy feed reset so often.
I'm also using grapheneos, but I've never noticed anything like this.
To check I just went back to the very last app in the app switcher, which was ironfox, which was still open on the same page I left it during lunch today. (About 6 hours ago)
Some apps store parts of the apps running state in storage some don't.
Your phone is trying to keep your battery alive. The lower the specs of the phone, then the more aggressive the OS is. I don't know how it works in Graphene but this is why many UIs now have and advertise multiapp ux like floating windows, split screen, floating icon and desktop modes. I suggest to use your phone intended keep app alive tactic.
Your phone is trying to keep your battery alive. The lower the specs of the phone, then the more aggressive the OS is.
No, apps closing between switches is not a matter of battery, it's a core feature of Android related to the management of RAM. Whenever the OS needs more available RAM, the OS will close a backgrounded app to make those resources available. This is why it happens more frequently on low-end devices - these generally ship with less RAM.
Some misguided vendors will limit background execution in incorrect ways in the name of saving battery, but the general thing with apps living in background is a story of RAM.
Interestingly enough, apps are supposed to be built to cope with being closed down due to lack of RAM and then be restored seamlessly, but this is an art that is uncommonly done correctly in the Android development space. The OS support is there, though.
You can see your current live memory usage.
Settings -> Developer Options -> Running Services
Nearly half of it is "system"
Ah, yes, a feature only developers use: task manager
When did you last reboot your phone?
I have had memory leaks in android that slowly consumes ram until I have the same issue. A reboot clears it for a while.
Every day or two. Last one was probably 2 nights ago.
What's your phone model?
Does that matter? It's a pixel running Graphene.
Do you have access to developer options?
If so make sure "don't keep activites" isn't checked. And also check background process limit.
Oh also don't keep activities is turned off.
Background process limit is max signed 32 bit integer value because I need Termux to fucking work
Do you swipe away all the unwanted running apps?
No. The phone kills them anyway and AOSP multitasking is a piece of shit that is broken more than it works properly
Ya answered your own question
The phone is killing the ones you want because you aren't swiping the ones you don't want away
Not OP, but same happens to me, and I swipe out apps as soon as I'm done with them, so that's not the problem. My phone literally can't hold open example.com on Firefox, and Voyager app at the same time, and it has 8GB of RAM
Wouldn't it kill the ones I've last opened longer ago first?
Welcome to the Android community on Lemmy. Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources: