Hi Mark,

Thanks for your reply. Here's the result--the "system_server" is
what's using the CPU right now:

  PID CPU% S  #THR     VSS     RSS UID      Name
   55  36% S    47 227780K  22252K system   system_server
   36   3% S     3   3352K    444K compass  /system/bin/akmd
 4241   3% R     1    904K    376K shell    top
   87   0% S    15 114704K  14868K radio    com.android.phone
    5   0% S     1      0K      0K root     events/0
    7   0% S     1      0K      0K root     suspend/0
    8   0% S     1      0K      0K root     kblockd/0
    9   0% S     1      0K      0K root     kmmcd
   10   0% S     1      0K      0K root     btaddconn
   11   0% S     1      0K      0K root     btdelconn
   12   0% S     1      0K      0K root     qmi
   13   0% D     1      0K      0K root     rpcrouter
   14   0% S     1      0K      0K root     detection/0
   15   0% S     1      0K      0K root     krpcserversd
   16   0% S     1      0K      0K root     pdflush
   17   0% S     1      0K      0K root     pdflush
   18   0% S     1      0K      0K root     kswapd0
   19   0% S     1      0K      0K root     aio/0
   20   0% S     1      0K      0K root     kadspd
   21   0% S     1      0K      0K root     panel_on/0
   22   0% S     1      0K      0K root     mtdblockd
   23   0% S     1      0K      0K root     USB mass_storag
   24   0% S     1      0K      0K root     synaptics_wq
    1   0% S     1    264K    144K root     /init
   26   0% S     1    796K    144K system   /system/bin/servicemanager
   27   0% S     2   1828K    208K root     /system/bin/mountd
   28   0% S     1    652K    132K root     /system/bin/debuggerd
   29   0% S     6   7720K    640K radio    /system/bin/rild
   30   0% S     1  66044K   9280K root     zygote
   31   0% S     7  21560K   1316K media    /system/bin/mediaserver
   33   0% S     1   1164K    176K bluetoot /system/bin/dbus-daemon
   34   0% S     1    812K    204K root     /system/bin/installd
   37   0% S     4   3328K    132K shell    /sbin/adbd
   46   0% S     1      0K      0K root     mmcqd
   89   0% S    17 139680K  19748K app_8    android.process.acore
  127   0% S    16 115236K  15240K app_11   com.google.process.gapps
  152   0% D     1      0K      0K root     audmgr_rpc
  201   0% S     7  89964K   9708K app_33   edu.mit.locale
 2251   0% S     8  91124K   9388K app_37
com.fingerpainters.fingerpaint
 2485   0% S     7 100372K  14312K system   com.android.settings
 2497   0% S     6  87020K   9972K app_57
com.streamfurious.android.free
 2652   0% S     5  85884K   9828K app_43   com.tmobile.wifi
 3496   0% S     8 103396K  17924K app_9    com.android.email
 3575   0% S     7 106996K  13308K app_14   com.android.mms
 3943   0% S     5  94296K  13916K app_89
com.google.android.netmeter
 4220   0% S     7  91816K  14632K app_6    com.android.calendar
 4240   0% S     1    724K    320K shell    /system/bin/sh
   25   0% S     1      0K      0K root     krfcommd
    2   0% S     1      0K      0K root     kthreadd
    3   0% S     1      0K      0K root     ksoftirqd/0
    4   0% S     1      0K      0K root     watchdog/0
    6   0% S     1      0K      0K root     khelper


On Dec 5, 10:17 am, Mark Murphy <[EMAIL PROTECTED]> wrote:
> Ed wrote:
> > I am guessing that bad programming on one or more of my apps is the
> > culprit, but Android does not have a built-in task manager, and it
> > does not allow the user to end specific tasks. There is a "NetMeter"
> > app on the Market, but it isn't helpful other than showing current CPU
> > load (it doesn't tell you what apps are running). I just turned on my
> > phone from sleep after getting to work today, and the CPU load is
> > 42.6%--with no app running other than NetMeter. After reboot, this
> > number drops to 4%.
>
> I'm not sure if you're a developer or not. If you are, fire up adb shell
> to your G1, run top -n 1 on the G1, and see if it tells you anything useful.
>
> Eventually, I or somebody will probably try to put a GUI in front of
> top, so you can run it just from the device without adb and get more
> pleasant output.
>
> This doesn't let you kill off any offending processes, but you may be
> able to determin who's at fault so you can uninstall the app, strangle
> the developer who wrote it, etc. My only request is that you not
> strangle the author of the book that the developer used, in case that's
> me, as my neck bruises easily... ;-)
>
> --
> Mark Murphy (a Commons Guy)http://commonsware.com
> _The Busy Coder's Guide to Android Development_ Version 1.9 Available!
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to