Having recently switched over from the Symbian/Belle platform to Android, a constant comparison between the two is to be expected. Generally, Android has proved a more interesting and engaging platform
for me. The abundance of apps for almost anything you can dream of, is so very welcome.
With meticulous use of Android, it has become clear that the data guzzling reputation on Android is grossly exaggerated.
However, one comparative flaw I have found on Android, is the way it handles its multi-tasking. It is not one of its stellar traits. At best, you could regard it as immature when compared to Symbian/Belle. At worst, the implementation is radically different. And this may not necessarily be a good thing.
I am referring to what I have personally observed, and may not actually be from a technical point of view.
In Symbian/Belle, when you switch from one task to another, you expect to come back and find the former task running the exact way you left it, and not just open in a frozen state!
So can begin a download, for instance, switch to something else, and expect to come back later, to see that download completed. I have not been able to see this kind of MULTI-tasking on Android gingerBread 2.3.4 that powers my Sony xPeria Pro(SxP).
Here is a scenario. I open a blog (let’s say www.oviealbert.com), post a comment. I then switch over to another application. Often, by the time I switch back to the browser, the Browser reloads, and I have to launch www.oviealbert.com all over, with the comment lost.
Another one; I am typing a document on a Text Editor, switch to another app. But by the time I come back to the app handling the doc I was typing, the text has disappeared. It means the text editor was re-launched!
Now, this happens more often than not. Not always, but often enough to Make it annoying.
It would seem that Android appears to prefer populating your device memory with apps it feels you use often. That way, it is presumed that Android can launch your apps faste. This is evident when you kill all apps, and come back to check a few minutes later to find tens of apps still running. What this actually means is that those apps started up all by themselves!
It is also the basis of the argument that Android perhaps, does not need all those Task Killers. You kill tasks now, and they come back into memory (by themselves), so what is the point of killing?
At other times, it looks apparent, in so doing, minimised apps that should not be closed, are sometimes closed. A memory management issue, perhaps?
While an out of memory situation could cause apps to be force closed on any OS, I would imagine that a System Message informing the user, and allowing him decide which app to close – would be a more orderly way of doing things?
I would not know if this happens in Android 4.0 (a.k.a – Ice Cream Sandwich), but I sure would hope that things are done differently in Android 4.1 (Jelly Beans).
What about you? Have you experienced apps closing when you otherwise expect them NOT to?
What strategies do you adopt to circumvent this?
Ibukun Olaoya popularly called Eye.Bee.Kay is a Geek and Mobile Tech Enthusiast, with a passion for Symbian, now with the mission to conquer the world of Android. He is vastly read and hopes to come out with the next big thing in Tech. You can follow him on Twitter at @Eye_Bee_Kay
Do you want to talk about this? You can do this in the comment section below. Your comments are welcomed.