[Galaxy S III Themes and Apps] Nazo:
So, I have a question about this. You're saying over and over that it "stays in memory." So I'm curious, are you oversimplifying and this just means the app stays running in the background at all times, or does this quite literally mean that it just marks its data in memory to not be cleared? In other words, can you kill said app and then restart it and it still keep the data in memory for less resource intensive loading while keeping it from wasting CPU resources, utilizing WiFi, and etc when not actually being used? The distinction might not seem important at first, but there are some apps that could benefit from a faster start that probably don't really use a ton of memory, but which will drain battery if actually running in the background as they do a lot of stuff that just isn't very nice, thus I "Greenify" them (another app which has the ability to benefit from the Xposed Framework btw.) Based on the fact that the term "resident" is used and the fact that you said earlier battery draining apps might be bad if locked, I'm guessing that it was the oversimplification and it does indeed mean that they are still running in the background as usual, but I just want to verify to be sure. There are several apps that it would be neat if I could keep their data in memory for faster reloading but which must stay closed when not in use or they tend to abuse resources a bit more than they rightly should. (I'm trying to absolutely maximize my battery life as much as I can short of making more serious underclocks and such that could affect performance negatively.)

BTW, you should probably tell the author of the Xposed Framework about this adjustment. This sounds like something that should be fixed at the source once and for all to me and this is a good idea definitely -- if used correctly and carefully that is, lol. (But then everything involving such low level access requires a bit of thought and care anyway.)

PS. Well, I'm a bit late responding to these, but no one else did, so what the hey!

Do not confuse Android (the software) with hardware made for Google (note the for -- Google doesn't even really make those themselves, but has other companies make them to their specs and the real hardware expertise comes from those companies, not Google) such as the Nexus series of phones/tablets. Android is an operating system like Windows/Linux/Mac OSX/etc (most like Linux obviously) and is not hardware any more than your computer was made by Microsoft (unless your computer is an Xbox "console.") A Nexus 4 or similar phone might seem to run better than some others, but generally speaking, if you look in more detail at what's actually in each, you may find that the only thing you need to do is freeze built-in apps or run a cleaner version of Android (like Cyanogenmod) versus how a phone comes stock. It's almost frightening how much junk is running 24/7 on a typical phone out of the box. I can't even say how much snappier my SGS3 runs with CM 10.1 (10.2 still has no dock audio support, so for now I'm staying away until I'm either sure that it's gone permanently and find a low enough power cheap USB DAC to use as a dock or until it comes back) versus the stock with all of the stuff Samsung had running. TitaniumBackup helped when I first rooted it, but frankly it didn't take me long to go Cyanogenmod, lol.

This is going about it all wrong. The next time a service-level app like SetCPU or etc where you need it to be able to do its thing at all times without interruption asks for superuser access, set it to remember to allow for said app. Anything that is occurring so frequently that it pops up even while you're in a game is something that you need to permanently allow or deny so it won't ask anymore. You'll only want to not set it to remember on things such as file managers where you wouldn't necessarily want to let it just automatically have instant root access at all times (aka someone messing with your phone who doesn't know what they are doing could even accidentally render it unbootable quite easily for instance. To this end, I even personally set a simple pin number on su so careless accidents are impossible.)