Originally Posted by
ubizmo Until we have headless apps, rogue native apps eating the battery shouldn't be a concern. But Android ports and sideloads--especially sideloads--are. I had to sideload the Android "Task Killer", but it reports on which Android apps are cached and/or running. Here's what I've observed.
1. Some apps appear as cached but not running, some of the time. The T-Mobile "My Accounts" apps is one of these. It's not always cached, however.
2. Closing any Android app, ported or sideloaded, removes it from the "Running" list; some stay cached. K-9 mail, for example, stays cached, but not running, after I close it. If I "kill" the process in Task Killer, it's gone from cache too.
3. I've yet to find any Android app in the "running" state that isn't in an active frame.
I cautiously conclude that BB10 has some fairly strong voodoo that prevents Android processes from running in the background (i.e., when not in an active frame).