Jump to content

Welcome to CyanogenMod

Welcome to our forum. Like most online communities you must register to post, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of the CyanogenMod Forum by signing in or creating an account. You can even sign in with your Facebook or Twitter account.
  • Start new topics and reply to others
  • Subscribe to topics and forums to get automatic updates
  • Get your own profile and make new friends
  • Download files attached to the forum.
  • Customize your experience here
  • Share your CyanogenMod experience!
Guest Message by DevFuse
 

High CPU Usage ?

Started by Gonzague, Aug 07 2010 07:10 AM

This topic has been archived. This means that you cannot reply to this topic.
12 replies to this topic

#1 Gonzague

Gonzague
  • Members
  • 15 posts

Posted 07 August 2010 - 07:10 AM

Hi,

I faced this problem with RC1, RC2 and nighty 08032010.

Seems that there is a high CPU usage, then the launcher (launcher pro or ADW) keep on force close, and i can't do anything else, or if i succeed on going into an app or settings, it takes ages to launches.  Had a look into the Logcat and it keep on spamming this:

07-29 12:29:23.755: ERROR/ActivityManager(121): ANR in android.process.acore (com.android.launcher/.Launcher)
07-29 12:29:23.755: ERROR/ActivityManager(121): Reason: keyDispatchingTimedOut
07-29 12:29:23.755: ERROR/ActivityManager(121): Load: 14.49 / 6.44 / 2.56
07-29 12:29:23.755: ERROR/ActivityManager(121): CPU usage from 45530ms to 54ms ago:
07-29 12:29:23.755: ERROR/ActivityManager(121):   mediaserver: 89% = 89% user + 0% kernel
07-29 12:29:23.755: ERROR/ActivityManager(121):   system_server: 3% = 3% user + 0% kernel / faults: 433 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):   adbd: 0% = 0% user + 0% kernel / faults: 38 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):   akmd: 0% = 0% user + 0% kernel
07-29 12:29:23.755: ERROR/ActivityManager(121):   d.process.acore: 0% = 0% user + 0% kernel / faults: 44 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):   d.process.acore: 0% = 0% user + 0% kernel / faults: 56 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):   events/0: 0% = 0% user + 0% kernel
07-29 12:29:23.755: ERROR/ActivityManager(121):   kondemand/0: 0% = 0% user + 0% kernel
07-29 12:29:23.755: ERROR/ActivityManager(121):   synaptics_wq: 0% = 0% user + 0% kernel
07-29 12:29:23.755: ERROR/ActivityManager(121):   zygote: 0% = 0% user + 0% kernel / faults: 46 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):   tiwlan_wifi_wq: 0% = 0% user + 0% kernel
07-29 12:29:23.755: ERROR/ActivityManager(121):   m.android.phone: 0% = 0% user + 0% kernel / faults: 18 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):   wpa_supplicant: 0% = 0% user + 0% kernel
07-29 12:29:23.755: ERROR/ActivityManager(121):   putmethod.latin: 0% = 0% user + 0% kernel / faults: 10 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):   d.process.media: 0% = 0% user + 0% kernel / faults: 9 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):   d.apps.uploader: 0% = 0% user + 0% kernel / faults: 16 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):   com.amazon.mp3: 0% = 0% user + 0% kernel / faults: 7 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):   m.android.email: 0% = 0% user + 0% kernel / faults: 8 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):   com.android.mms: 0% = 0% user + 0% kernel / faults: 8 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):   oid.voicedialer: 0% = 0% user + 0% kernel / faults: 7 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):   pps.googlevoice: 0% = 0% user + 0% kernel / faults: 13 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):   id.partnersetup: 0% = 0% user + 0% kernel / faults: 7 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):   m.android.music: 0% = 0% user + 0% kernel / faults: 14 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):   android.protips: 0% = 0% user + 0% kernel / faults: 2 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):   nie.geniewidget: 0% = 0% user + 0% kernel
07-29 12:29:23.755: ERROR/ActivityManager(121):   .cooliris.media: 0% = 0% user + 0% kernel / faults: 16 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):  +e.process.gapps: 0% = 0% user + 0% kernel
07-29 12:29:23.755: ERROR/ActivityManager(121):  +sh: 0% = 0% user + 0% kernel
07-29 12:29:23.755: ERROR/ActivityManager(121):  +logcat: 0% = 0% user + 0% kernel
07-29 12:29:23.755: ERROR/ActivityManager(121):  -ndroid.settings: 0% = 0% user + 0% kernel
07-29 12:29:23.755: ERROR/ActivityManager(121):  -e.process.gapps: 0% = 0% user + 0% kernel
07-29 12:29:23.755: ERROR/ActivityManager(121):  -oid.voicesearch: 0% = 0% user + 0% kernel
07-29 12:29:23.755: ERROR/ActivityManager(121): TOTAL: 100% = 97% user + 2% kernel

I'm using a 32a (with the ebi1 kernel). This appears regardless of the performance settings I use and rebooting doesn't change anything. Unfortunately it really makes CM6 unusable at all. 5.0.8 runs perfectly.

Any idea on how I can avoid this ??

#2 wjsturgis3

wjsturgis3
  • Donators
  • 123 posts

Posted 07 August 2010 - 01:13 PM

View PostGonzague, on 07 August 2010 - 07:10 AM, said:

Hi,

I faced this problem with RC1, RC2 and nighty 08032010.

Seems that there is a high CPU usage, then the launcher (launcher pro or ADW) keep on force close, and i can't do anything else, or if i succeed on going into an app or settings, it takes ages to launches.  Had a look into the Logcat and it keep on spamming this:

07-29 12:29:23.755: ERROR/ActivityManager(121): ANR in android.process.acore (com.android.launcher/.Launcher)
07-29 12:29:23.755: ERROR/ActivityManager(121): Reason: keyDispatchingTimedOut
07-29 12:29:23.755: ERROR/ActivityManager(121): Load: 14.49 / 6.44 / 2.56
07-29 12:29:23.755: ERROR/ActivityManager(121): CPU usage from 45530ms to 54ms ago:
07-29 12:29:23.755: ERROR/ActivityManager(121):   mediaserver: 89% = 89% user + 0% kernel
07-29 12:29:23.755: ERROR/ActivityManager(121):   system_server: 3% = 3% user + 0% kernel / faults: 433 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):   adbd: 0% = 0% user + 0% kernel / faults: 38 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):   akmd: 0% = 0% user + 0% kernel
07-29 12:29:23.755: ERROR/ActivityManager(121):   d.process.acore: 0% = 0% user + 0% kernel / faults: 44 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):   d.process.acore: 0% = 0% user + 0% kernel / faults: 56 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):   events/0: 0% = 0% user + 0% kernel
07-29 12:29:23.755: ERROR/ActivityManager(121):   kondemand/0: 0% = 0% user + 0% kernel
07-29 12:29:23.755: ERROR/ActivityManager(121):   synaptics_wq: 0% = 0% user + 0% kernel
07-29 12:29:23.755: ERROR/ActivityManager(121):   zygote: 0% = 0% user + 0% kernel / faults: 46 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):   tiwlan_wifi_wq: 0% = 0% user + 0% kernel
07-29 12:29:23.755: ERROR/ActivityManager(121):   m.android.phone: 0% = 0% user + 0% kernel / faults: 18 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):   wpa_supplicant: 0% = 0% user + 0% kernel
07-29 12:29:23.755: ERROR/ActivityManager(121):   putmethod.latin: 0% = 0% user + 0% kernel / faults: 10 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):   d.process.media: 0% = 0% user + 0% kernel / faults: 9 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):   d.apps.uploader: 0% = 0% user + 0% kernel / faults: 16 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):   com.amazon.mp3: 0% = 0% user + 0% kernel / faults: 7 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):   m.android.email: 0% = 0% user + 0% kernel / faults: 8 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):   com.android.mms: 0% = 0% user + 0% kernel / faults: 8 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):   oid.voicedialer: 0% = 0% user + 0% kernel / faults: 7 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):   pps.googlevoice: 0% = 0% user + 0% kernel / faults: 13 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):   id.partnersetup: 0% = 0% user + 0% kernel / faults: 7 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):   m.android.music: 0% = 0% user + 0% kernel / faults: 14 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):   android.protips: 0% = 0% user + 0% kernel / faults: 2 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):   nie.geniewidget: 0% = 0% user + 0% kernel
07-29 12:29:23.755: ERROR/ActivityManager(121):   .cooliris.media: 0% = 0% user + 0% kernel / faults: 16 minor
07-29 12:29:23.755: ERROR/ActivityManager(121):  +e.process.gapps: 0% = 0% user + 0% kernel
07-29 12:29:23.755: ERROR/ActivityManager(121):  +sh: 0% = 0% user + 0% kernel
07-29 12:29:23.755: ERROR/ActivityManager(121):  +logcat: 0% = 0% user + 0% kernel
07-29 12:29:23.755: ERROR/ActivityManager(121):  -ndroid.settings: 0% = 0% user + 0% kernel
07-29 12:29:23.755: ERROR/ActivityManager(121):  -e.process.gapps: 0% = 0% user + 0% kernel
07-29 12:29:23.755: ERROR/ActivityManager(121):  -oid.voicesearch: 0% = 0% user + 0% kernel
07-29 12:29:23.755: ERROR/ActivityManager(121): TOTAL: 100% = 97% user + 2% kernel

I'm using a 32a (with the ebi1 kernel). This appears regardless of the performance settings I use and rebooting doesn't change anything. Unfortunately it really makes CM6 unusable at all. 5.0.8 runs perfectly.

Any idea on how I can avoid this ??

Did you do: fastboot erase system -w before flashing CM6?  I did and have had no such problems.

#3 woozyking

woozyking
  • Members
  • 49 posts

Posted 07 August 2010 - 02:33 PM

I'm having the similar issue on my HTC Dream (T-Mobile ver.), gonna try it as soon as I get back home.

BTW: Clockwork Recovery has the erase system/boot/recovery image command built-in, guess that will ease the job a bit ;)

ps: hope RC3 or even the stable version's out when I head back :P

#4 Gonzague

Gonzague
  • Members
  • 15 posts

Posted 08 August 2010 - 02:52 AM

I'll try that but what's the difference with the wipe data from Amon ra recovery ?

#5 woozyking

woozyking
  • Members
  • 49 posts

Posted 08 August 2010 - 03:30 AM

View PostGonzague, on 08 August 2010 - 02:52 AM, said:

I'll try that but what's the difference with the wipe data from Amon ra recovery ?
Wipe data just does a factory reset like thing, deletes the data but keeps the system

Erase, on the other hand, is like formatting the whole system partition (or any other partition of your choice)

View PostGonzague, on 08 August 2010 - 02:52 AM, said:

I'll try that but what's the difference with the wipe data from Amon ra recovery ?
http://forum.cyanoge...ng-app-to-home/

You might want to read this though, after doing an erase-flash, I think erasing the system partition wouldn't complete the puzzle

#6 Gonzague

Gonzague
  • Members
  • 15 posts

Posted 08 August 2010 - 05:09 AM

Thanks for the details. The thing is the topic you point to is talking about Memory problems / swap. My issue is CPU overwhelmed and it never stops.

#7 Derkek

Derkek
  • Members
  • 13 posts

Posted 08 August 2010 - 05:53 AM

I had an fc loop once, I simply cleared the caches in recovery and it worked beautifully, if I *ever* encounter a problem, first thing I do I delete the cache. It fixes most hicups for me.

#8 woozyking

woozyking
  • Members
  • 49 posts

Posted 08 August 2010 - 02:35 PM

View PostGonzague, on 08 August 2010 - 05:09 AM, said:

Thanks for the details. The thing is the topic you point to is talking about Memory problems / swap. My issue is CPU overwhelmed and it never stops.
yeah, just try if it solves the high cpu usage issue, as well as smoothen up the "back-to-home-from-apps" process. The second part is probably about memory/swap settings etc.

#9 Gonzague

Gonzague
  • Members
  • 15 posts

Posted 08 August 2010 - 03:34 PM

Actually i don't have problems to go back to the hoem. the home jsut fc all the time :/ The few seconds it works well, the way back home is smooth

#10 Gonzague

Gonzague
  • Members
  • 15 posts

Posted 08 August 2010 - 04:20 PM

Ok, i tried your tips with the last nighty build but problem is still the same. the first 10 minutes are ok, after that it's loop force close. If i reboot. same.

#11 Gonzague

Gonzague
  • Members
  • 15 posts

Posted 17 August 2010 - 03:51 AM

Hi again,

I still have the same issue with RC3 after a fastboot erase a bit less often but the phone is still not usable properly.

With or without compcache, with or without JIT, and without dithering.
I hope you guys will be able to fix it for final release.

Thank you for your great work.

Edited by Gonzague, 17 August 2010 - 03:53 AM.

#12 at_random

at_random
  • Members
  • 18 posts

Posted 19 August 2010 - 09:26 PM

View PostGonzague, on 17 August 2010 - 03:51 AM, said:

Hi again,

I still have the same issue with RC3 after a fastboot erase a bit less often but the phone is still not usable properly.

With or without compcache, with or without JIT, and without dithering.
I hope you guys will be able to fix it for final release.

Thank you for your great work.


I have the same issue on CDMA Hero CM6 nightly.  Mediaserver just murders my battery.
  82  94% S     9  33364K   2020K  fg media    /system/bin/mediaserver
3596   4% R     1    944K    392K  fg root     top
  86   0% S     3   3132K    312K  fg compass  /system/bin/akmd

When it happens, rebooting doesnt help - it comes right back and pegs the CPU.
I pulled out my SD Card for a while and didnt have a problem.
I wonder if this is related to the amount of music? I have about 15GB on my SD card.

I really want to us CM6 cuz it's so responsive. HELP!!! :)

#13 Gonzague

Gonzague
  • Members
  • 15 posts

Posted 14 September 2010 - 07:11 AM

I up this topic again... same problem with the CM6 stable version ...

If i'm not mistaken, cm 6 as a small default overclocking no (or maybe i was dreaming)? Can it be the source of this problem ?

I'm really sad that i can't use cm6... because cm 5.0.8 really works very nicely, very fast without any issue.
Back to HTC Dream / HTC Magic Stable Mod


  1. CyanogenMod Forum
  2. → HTC
  3. → HTC Dream / HTC Magic
  4. → HTC Dream / HTC Magic Stable Mod
  5. Terms & Conditions