Pixel 6a gos killing app in ram to violently

pesa44

Hallo, I recently switched to GOS and one thing irritates me a lot. The OS keeps killing my apps all the time and there is no way to keep them open. I did gave the apps I use unrestricted battery and it still kills them. Running out of memory is not the issue, cause I have always 1gb+ of free ram, usually around 2gb. Apps I use are Boost for Reddit, Kiwi browser, Youtube revanced and Messanger. It will keep them live for a while, but within 1 minute or so it just kills them. Any way to mitigate this issue?

It's a fresh install of gos and I had bo issues like this on official Google Android.

fid02

pesa44 Did you enable developer options? If so, try disabling it and reboot your device.

pesa44

fid02

fid02 Yes, I did, and turning it off seemed to help a bit so thanks a lot for your advice. The rest I blame on 6gb ram. I'm only testing GOS for now so later I'll buy P9 Pro. Btw, do you know why DO enabled causes this issue? I'm used to having animations speed down to 0.5.

AlphaElwedritsch

In what context is that supposed to be?

fid02

pesa44 Developer options contains a setting to destroy every activity as soon as the user leaves them.

DeletedUser127

fid02 this is by default set to standard limit. Users should only use options in developer settings they have a knowledge how they change device behaviour. If we are to follow general advice, we shouldn't be even permitted to OEM unlock device in order to flash alternative OS because such setting is hidden in there. Naturally, one must be always cautious when using features that are not available under normal circumstances. Some apps misbehave when they detect Dev options turned on. I still need regular checks on for example Running processes so I will keep that bit always active.

There can be several reasons that can explain why app in question stops in the background starting from the way it was programmed to behave, battery usage settings, RAM availability during prolonged use etc.

fid02

DeletedUser127 this is by default set to standard limit.

My thinking is that users might have changed that setting, not realizing what it actually does.

Advising someone to try disabling developer options as a whole is a quicker way to begin troubleshooting: if the issue is identical even when developer options are disabled, then it seems logical to deduce that developer options is an unlikely culprit.* That's a more efficient testing path compared to starting out by testing each configuration entry manually. The OP can now reenable developer options on their development device and start experimenting with each entry and see if the issue rearises. They can then get on with using their device for development and debugging purposes.

*Unless some options stay enabled even after developer options are off, which I'm not sure if they do.