3 ms·
You're describing bad app implementation. It is quite common for the OS to suspend apps when they're in the background or when the device is under low memory/p
by isodev 3y ago
You're describing bad app implementation.
It is quite common for the OS to suspend apps when they're in the background or when the device is under low memory/power conditions. The fact that you as a user are experiencing it in the form of degraded functionality is a bug with the app itself and should be addressed by the developer.
As a reference, check iOS apps where the system monitors and controls each app's resource usage much more aggressively and a user is never aware of this.
- g-b-r 3y agoThese phones kill apps, not suspend them.
- isodev 3y agoFrom the app's point of view both are the same - the app can no longer execute code and upon resume it must restore state.
- g-b-r 3y agoSuspending means that its memory was preserved, so the app doesn't have to do anything !!!
- isodev 3y agoWhile suspending may be the first state, the OS can choose to fully evict the app from memory if it needs it for other tasks. So a "good app" saves state before being suspended so that upon resume, it can restore from disk even if it was "killed".
- g-b-r 3y agoYes, but in practice almost all apps don't do it always with the complete state,; and on phones that don't kill them so easily most of the times you can switch between apps without problems.