[Q] questions about sense bloat
I've read a number of general complaints about sense being bloated and unremovable but would like to understand what device resources are unavoidably consumed by it.
If it's just storage space I'm not too concered about that. But taking up RAM with programs/features I don't want is another matter, as is any wasted CPU-cycles it might spend automatically running programs in the background, or intercepting UI events.
I ask this without knowing specifically what in sense is believed to be bloated. Is there a way to see a list of things it runs or could run, and to disable each feature I don't want? Again, I don't mind if the unwanted programs remain in storage, as long as they are never run and thus don't consume RAM/CPU.
When I watch videos of the G2X, it's mind-boggling how fast every aspect of the UI is. What is sense doing that keeps the evo 3d / sensation from achieving the same level of snappiness? I have a hard time believing excessive RAM-usage or CPU even is playing any role in simply scrolling through the tray of apps. So what is it that affects things like simple scrolling speed there?
I'm guessing android has some kind of event handling, where every event is delivered to a list of programs that each decide if they want to do anything with the event or not, and maybe sense has programs registered all over the place to receive all kinds of events. This is wild speculation on my part as I'm not that familiar with how things really work, but when scrolling through apps in the app tray is slow, something besides simple resource consumption must be going on.
Anyway my general questions are: what makes it slow, and can 'it' be removed, whatever 'it' is.