Just an idea that I had after a few months of noticing every time I'd turn my phone's display back on, the CPU would be pegged. I'm not sure, but I think that it might be indicative of some malware, and I want to collect some other statistics regarding what is going on when the display is inactive.
Different objects to be instantiated (ie CPUDetails) need to have fields, and constructors, set up properly, in order to take advantage of OO for maintainability. Right now it's pretty nasty; been doing it the quick & easy way in order to handle initial debugging.
Which reminds me; learning unit testing in a fashion applicable for 'droid development is probably a damn good idea. I know it would've saved some serious effort in the last several attempts at debugging.
Different objects to be instantiated (ie
CPUDetails
) need to have fields, and constructors, set up properly, in order to take advantage of OO for maintainability. Right now it's pretty nasty; been doing it the quick & easy way in order to handle initial debugging.Which reminds me; learning unit testing in a fashion applicable for 'droid development is probably a damn good idea. I know it would've saved some serious effort in the last several attempts at debugging.