On Dec 19, 8:36 am, Ed <[email protected]> wrote: > Thanks for your message. I think that the outdated scoreboard app was > one culprit, but as this thread shows, the problem existed before > scoreboard was even released. I suspect that whatever bug had to be > fixed in scoreboard exists in some other apps as well.
For future reference (and for the benefit of anybody who lands here by searching)... "adb shell top" will tell you what's using up CPU. In most cases this will identify the (over-)active app. "adb logcat -v time" will show the debug log, with timestamps. In many cases it will identify *why* things are active, e.g. scoreboard getting swatted constantly. "adb bugreport" dumps about a megabyte of stuff, with logs from various components. If you are seeing a lot of activity in system_server but don't see anything telling in the logs, and only a little activity in "top", then something may be quietly driving system server to distraction. If you skip down to "BINDER TRANSACTION LOG" you can see the most recent chatter, identified by process ID. If something is appearing very frequently, it may be the culprit. You can map the processes to apps with "ps" or by looking in the PROCESSES section. I used the above to identify edu.mit.locale as a source of difficulty on somebody's device yesterday. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
