05-12-2012 03:28 AM
It is the weekend and this does not need any urgent attention.
I am merely using some spare weekend time to report something about NMU that I find odd. In case it is of any interest to the team or anyone else.....
When I select "Device" from the main NMU screen I can get to a view of CPU activity; doing a long press on that brings up a list of running apps; on the right is a "-" sign which enables me to stop the app (unless it is "excluded"). I have a slight issue with the pop up "Note - Are you sure to stop?", as is does not mention the name of the app, and if you have big fingers you may stop the wrong app. However my main issue is the result achieved by the stop. I had assumed that it would be the same as a forced stop reached from the main Android screen by pressing :Menu:Settings:Applications:Manage applications. However this does not seem to be the case and this puzzles me.
I have a troublesome app "The Economist". For some reason after downloading the latest edition of The Economist magazine even though I have apparently closed the app it continues to hog the CPU (thanks to NMU for identifying the culprit). If I use NMU to stop it, then a few seconds later it is up and running again still chewing up around 75% of processor power! I can close it three times with NMU but it keeps coming back. However one "Force stop" from "Manage applications" and the app is put well and truly to bed. At first I thought it was a chance happening but I have now checked this out on at least four occasions. Same thing each time. Also if I go first to Manage Applications there is no repeat problem.
The staff at the Economist are aware of the issue over hogging the CPU but a fix to the Google Play version seems to be a long time coming. I have not raised the odd issue related to NMU with them.
If anyone has any questions please feel free to come back.
05-15-2012 02:52 PM
Since I'm sure you have CatLog on your Blade, let the app run and then look in the log. It should define the process information there.
05-16-2012 02:25 PM
I can't tell if it's a service. It may just be an overly agressive process that takes a little bit more to kill. The method you used to stop it would stop a service as wel. I'm leaning towards a service though. I look forward to hearing what happens after they update the app what kind of experience you have.