With Android 6 (Marshmallow), Google has introduced Doze mode to the base Android, in an attempt to unify battery saving across the various Android phones.
Unfortunately, vendors (e.g. Xiaomi, Huawei, OnePlus or even Samsung..) did not seem to catch that ball and they all have their own battery savers, usually very poorly written, saving battery only superficially with side effects.
Naturally users blame developers for their apps failing to deliver. But the truth is developers do the maximum they can. Always investigating new device specific hacks to keep their (your!) apps working. But in many cases they simply fall short as vendors have full control over processes on your phone.
This is a legitimate problem on my OnePlus 6T. I enjoy using this phone, but the aggressive non-standard application cycle management definitely leads to issues with not receiving notifications or login procedures being restarted as you leave an application. It doesn’t happen often enough to truly bother me, but I can definitely see how people who make more extensive use of their phone than I do run into this issue every day.
The link seems broken…
Great find! I have been complaining about this since my first Android device in 2013 (I have used all Android versions from 4.1 to 8).
Coming from a Symbian phone (the one with the largest RAM) I was perfectly accustomed to managing open apps the way I wanted rather than the way the OS wanted.
When I started using Android devices I was very disappointed by the fact that many apps would reload without any warning. Most times it was – and is – the browser getting killed and then reopening
– losing all the text you had been writing (it happened too many times, until I learned to select all and copy before switching from the browser to any other app);
– failing to reload pages if the connection was not available anymore, despite their supposedly being in the cache.
Many other apps suffer from this problem. The music player sometimes exits. Many other times it gets killed when I pause it, despite the notification that should help keep it open. The picture album almost always reloads after switching back – of course, if you were looking at an old picture, you’ll have to find it again. Same goes for everything else – maps, messaging apps (Whatsapp sometimes recovers the drafts, some other times it discards them – no clear pattern, so I also learned to copy the message text before leaving if I am not going to send it immediately).
Being a frequent task switcher, the way Android happily kills background apps makes it very cumbersome for me to use my phone without losing part of my work.
Things have not greatly changed so far. BTW I am mainly using Sony devices, which are not the worst offenders in this.
Just for history. Symbian phones would sometimes complain about memory being full and I would close the apps I was not using. The task switcher would display the apps that were actually running rather than the “most recently used”. In this respect the workings were similar (and prior) to MeeGo/Harmattan and BB10.
There was an app menu with folders, home launcher with widgets and app icons and one of the widgets was for most recently used apps.
I can’t wait for Android to stop freaking close my apps.
To be honest, Android app lifecycle is designed so the app shall be prepared to be killed at any moment when it’s not in the front.
Therefore apps are expected be able to serialize their complete state on disk when switched away. It’s hard to do and few do that correctly. Especially the ones with codebases originating in Linux/Windows apps.
That’s one of the reasons putting more and more ram in android handsets is justifiable. It allows to avoid the background killing problem to some extent. But now custom battery saver hacks make even Gigs of RAM that less effective.
On the other hand, if an app decides to run arbitrary commands while in the background and open arbitrary network connections, why it should be allowed to do it uninterrupted on a power-constrained device? How does the OS know it’s a messaging app and not game fetching new “promotions” from an http server?
If app vendors had standardized on a chat protocol that the OS could support natively, they wouldn’t have this problem right now. Facebook is particularly guilty of this, using a power hungry message-fetching service because they can. I have no sympathy for them, and with SMS messages being basically free now, I cannot wait until we get back to SMS for important messages. I have already made it clear to my relatives that if it’s not an SMS message it isn’t time-sensitive.