Recently updated to v1.15
Just pushed to the Play Store, wait a few hours for it to propagate or grab the APK from XDA here: http://forum.xda-developers.com/showthread.php?t=3050998
Some minor fixes, a form of multi-user support (config as admin, works the same for all) and some CM specific fixes. Barring the discovery of any major issues, this should be the last update to Recently
for some time.CM
Let it not be said (again...) that I never give any love to CM users. There was a bug in the service code which left the background process alive if using CM's su and you turned Recently
But the real reason I even looked at CM were the many requests to do something about the # symbol in the status bar when using Recently
. Apparently it's a bit of an annoyance that the user can't turn off, and as the root process exists the entire time the app is activated, this means you'd always see the # symbol, and it loses all the usefulness you may think it has.
The work-around used is not very complex (though it did require more code changes than I generally expect doing on a Sunday), and it is only one of several ways it could be done. It does make you wonder though... What's worse than a security related indicator the user can't turn off? A security related indicator the user can't turn off that also doesn't reliably indicate the conditions you expect it to indicate.Changelog
- Workaround CM's # in statusbar
- Fix never quitting with CM's SU
- Multi-user support - works for all users, but with admin's config
- Fix settings screen margins on tabletsOther apps
As an aside, several of my recent root apps (and upcoming ones too) will keep a root shell open in the background during the app's lifetime, as it is both faster and generally more efficient than repeatedly creating a root shell, running one or two commands, closing the root shell, and doing it all over again seconds (or even minutes) later.
Ironically, these are the virtually the same reasons some argue against the use of Recently
itself, though I maintain those arguments do not hold when none of the Advanced Recently
settings are used, in any but the very worst case scenarios.
Anyway - those apps will show you the # as well - I do not foresee implementing this same work-around for most of them.