Solution to important apps closing in background

Tryptamine

thrik hey! I know this is a few months old post, but I just found a possible solution! In Developer Options, go to Suspend Eecution for Cached Apps and set it to Disabled. This setting will allow apps to remain in the background executing their code for longer!

This seems to be doing something for me. I've moved on from Accubattery, using a root solution (ACCA) instead now, but this seems to keep my current apps alive longer. Might be the solution your looking for!

oxika95

Ive been scratching my head at this issue as well on my Pixel 7. My issue is specifically with background audio playback. I use audible as well as several TTS enabled readers. They all worked fine until just a little while ago and now all cut out within about a minute if switching away from the app to another. I can tell as soon as it happens because my audio cuts out. If i switch back it picks right back up.

I may have found a fix. It seems in the "app info" settings page under "Advanced" options is an "Exploit Protection Compatibility Mode" in the description it says it improves compatibility by using Androids standard memory allocator. Having ticked this option on seems to have solved my issue from what I can tell from testing so far. At least the apps last longer than a minute in the background.

oxika95

It seems not all apps have this option. Haven't figured out what decides if the option s there but current guess is that apps from the app store seem to have it and other apps so far do not. Maybe someone else can confirm.

other8026

oxika95 It seems not all apps have this option. Haven't figured out what decides if the option s there but current guess is that apps from the app store seem to have it and other apps so far do not. Maybe someone else can confirm.

According to the GrapheneOS code comment, the toggle only shows up if the app is a "non-system app that has native 64-bit code"

oxika95

other8026 Thanks for the heads up! This toggle seems to be a working solution from what I can tell. Apps without the toggle though that have the issue i'm not sure how to address, maybe the "Suspend Execution for Cached Apps" in Developer Options like @Tryptamine suggested will work. I'll do some testing and report back.

Tryptamine

oxika95 That's interesting that Exploit Protection Compatibility Mode solves the problem! I theorized that it might on a similar discussion on the GrapheneOS Reddit here:

https://www.reddit.com/r/GrapheneOS/comments/17lty85/ram_management_issues/

GrapheneOS (official account) commented that Suspend Execution for Cached Apps should be set to "off" in the background when set to default... I set it to "off" anyways rather than let it use its default behavior. Check out the thread! Its got some relevant info with some interesting comments from GrapheneOS's official account as well.

Tryptamine

thrik Hey, I did try to uninstall and reinstall Accubattery, and didn't help. I didn't try to enable Exploit Protection Compatibility Mode however... Other apps, depending on which don't have the problem or do. Can't remember which do, but Greenify, Brevent and BatteryGuru don't have the issue. I think that in AppOps if they have the setting "AllowForegroundSpecialProcess" app op and set to "granted", it will remain in foreground as a top app and not get killed.

shroom

Has anyone found any solution to this? GrapheneOS has been unusable for me as apps seem to be killed as soon as they are minimized or the screen is locked.

de0u

shroom GrapheneOS has been unusable for me as apps seem to be killed as soon as they are minimized or the screen is locked.

This problem statement does not address the suggestions in earlier posts in the thread. Have those suggestions been tried? In particular, if any developer options are enabled, please report whether the problem continues when all of them are off. Further information: https://discuss.grapheneos.org/d/19110-mac-randomization-in-developer-mode

yaomtc

I experience this every day with Transit. Pretty frustrating to have it crash every day in the middle of my bus ride and have to relaunch it. I tried the exploit protection compatibility mode but it doesn't seem to make a difference. Using a Pixel 6a.

de0u

yaomtc If the problem is just one app, that is probably not the sane issue as this thread, in which case a new thread should be created (after searching to see whether there are threads about that app). If the app is crashing, meaning that you get a crash dump, reporting at least the start of the crash dump would be useful. But an app restarting is not the same thing as crashing.

yaomtc

de0u I have issues with other apps / Vanadium tabs staying in memory so I figured that was the issue here. I've emailed their support.

freezet

Most prominent example would be Google Maps for me, even on Stock Android , if I go to Home Screen or do something else, it keeps forgetting that it is in navigation mode with a destination. E.g. going into gas station with phone , have a coffee , maybe use an app, after that maps amnesia for sure.

DeletedUser127

yaomtc if you have a problem with app staying in memory, it is because of the way how you exit the app. Close it from the recents screen rather than escaping to homescreen or switching to another app.

yaomtc

DeletedUser127 I meant that they weren't staying in memory when I wanted them to, I wasn't talking about closing them.

I've realized the real problem though. The 6 GB of RAM on my Pixel 6a is sadly not enough for multitasking these days. I'm gonna grab a used Pixel 8 Pro from Swappa instead, it has 12 GB.

« Previous Page