Closed bengtan closed 4 years ago
mstidham
commented
4 years ago Clean install results in the app being Optimized (battery restricted). The user also has the option to put the app to sleep. Once the user adds TR to the Not Optimized list the option to put app to sleep goes away.
bengtan
commented
4 years ago We have encountered one or two cases when the app can sometimes become 're-optimised' (thereby becoming restricted) again.
https://hippware.slack.com/archives/C2V6L53TQ/p1579645799022100
I think this is good enough info. Closing.
Information at https://dontkillmyapp.com/samsung suggests that apps can be put to sleep again, or become battery restricted again, after a period of time or after some unknown event.
We'd like to clarify this via our own testing.
The main question is: Under what conditions is our app being put to sleep or battery restricted?
But this can be split into sub-questions, for example:
Is 'being put to sleep' correlated with battery restrictions or do they seem to be independent things?
If an app is not battery restricted, is it still eligible to be put to sleep?
If an app is manually removed from the sleeping apps list, when does it revert to being eligible to be put to sleep?
If an app is manually 'battery unrestricted', when (or if) does it revert to being battery restricted again?
When an app is installed, does it default to being battery restricted and sleep-eligible?
Even if we cannot solve this programmatically, it is useful information that assists us in providing support for samsung android phones.
More information and background: https://dontkillmyapp.com/samsung