|
Edited by harrycallahan at 2020-1-26 07:10
OMFG!!!
Fix/Workaround:
1. Turn on Developer Options (You can unlock the Developer options on any Android smartphone or tablet by locating the Build number in your Settings menu and tapping it multiple times.)
2. Settings -> System -> Advanced -> Developer options -> Background process limit
Set this to 'No background processes'
(Don't assume this is what you think it is, see description https://forum.xda-developers.com ... 164099&postcount=10)
3. Reboot phone. (To be sure)
Now, I do have Duraspeed On as described above (Service enabled and On for app), and also Battery Optimization off for the app. I don't know exactly which combination of options is strictly necessary - I mean sheesh, there's so many toggles which can be influential - no wonder there's a conflict somewhere.
And a weird thing: if you go back to the 'Developer options' and look at the value for 'Background process limit' - it's back at 'Standard limit'! It seems that it's only the toggling of the 'Background process limit' which has rectified some kind of initial setting flaw.
Interested in feedback from other users...
Update: Can confirm this is NOT a permanent fix. I was able to use my scrabble game app for a few hours without closing. And then, when I opened Settings -> Duraspeed, and changed nothing, the app started being killed. I already knew a reboot made a difference for a short time. So not sure if the toggling of 'Background process limit' made any difference.
Also this is a major problem with many modern Android phones. Nokia in particular have had issues due to Duraspeed on their MTK offerings (Duraspeed is a Mediatek creation/affliction). I have disabled Duraspeed but makes no difference (is it really disabled?).
https://github.com/urbandroid-team/dont-kill-my-app/issues/57
https://dontkillmyapp.com/ (Smartphones are turning back into dumbphones)
I would like to view the logs and see what is doing the killing but that isn't a simple process in Android.
|
|