The High CPU Usage Issue

[Guest Simon O]

Hello Paul i installed Watchdog lite and under CPU it has

watchdog lite > foreground 2.8%

Advanced task killer > service 6.7%

Android system> foreground 2.3%

eveverything else seems to be on 0%

Under stats is showing CPU % in background Android apps 6.2%

CPU Information user 9.3% Nice 0.0% System 6.8% idle 83.0% IO 0.0% IRQ 0.0% softIRQ 0.0%

And under Alerts it says no apps misbehaving

Well to me that looks perfectly fine.

[Guest feckineejit]

Well to me that looks perfectly fine.

Cheers :) but when i go into system>about phone> battery use, it says android System 99% nothing else showing as running in there, is that normal?

[Guest Simon O]

Cheers :) but when i go into system>about phone> battery use, it says android System 99% nothing else showing as running in there, is that normal?

Yes. You would expect to be using the battery 100% load whilst you are using the phone. It'll drop down when the phone is idle.

[Guest con500]

Yes. You would expect to be using the battery 100% load whilst you are using the phone. It'll drop down when the phone is idle.

Thanks flibblesan, iv also been wondering about this. :)

[Guest screwface]

3D gallery is rubbish once i finally get a spare few minutes im going to root it and swap out the gallery too.

[Guest oh!dougal]

Cheers :) but when i go into system>about phone> battery use, it says android System 99% nothing else showing as running in there, is that normal?

Regarding the standard phone battery usage report that you mention ... it should add up to 100%. ... ;) (or near enough)

[Guest whitelightning]

I'm using OS Monitor and can see the Calendar process is running at 80% at times, which I believe is caused bt trying to sync with gmail which I have blocked. Is there anything I can do to automatically kill this process?

[Guest xzyk]

Drizmod, your solution works on mine also. I've had this issue on and off and your 'workaround' at least gives me a way to control it.

thanks. :)

[Guest Sere83]

mine does exactly the same things guys. Using OSMonitor it's always the android.system that is the problem. Sometimes it settles down, sometimes it doesn't. There doesn't even seem to be any sense in how long it takes to settles down. I've had it go from high CPU to low in 5mts, other times it takes hours. Reboots, power cycles seem to fix it sometimes but there really doesn't appear to be any logic to it.

rooted and using r3. I may have to try a factory reset just to check.

Yeah exactly the same as me, no sense to how long it took to settle. Using OSMonitor it is always the android.system that is the problem. I was running Launcher Pro and fancy widget however. So I did a reflash or the R3 then did a factory reset. Same issue though still.

So then I re-installed launcher pro and removed fancy widget (didn't uninstall). Left it on over night and re-charged. I have now just restarted 4 times in a row and the issue now seems to have gone. Everything is super pacey, all flashy animations and 3D dock on. OS monitor reporting normal cpu usage. Not counting my chickens yet though....

UPDATE: System seems ok now but Now Watchdog LITE just popped up with gallery issue, saying it was at 99.9% (misbehaving etc)

Edited October 8, 2010 by Sere83

[Guest Afrodude]

Right... i've managed to replicate this issue almost at will now (atleast on my SF). It seems to be related to some files that are written to my SD card.

If i clear the SD card and reboot - no high CPU.

If i leave files the SD card - high CPU.

I'll look into this issue a little more if someone else can replicate the same.

[Guest Erik_g]

I have just got my phone, first thing I did was to root it with superboot root.

After the first reboot I got the same problem with high cpu, after a while it went down to low cpu.

Tried format sd card and open and close the camera application but didn't help

Anyone have a soultion?

Now I'm going to flash R3 to see what happends

Right... i've managed to replicate this issue almost at will now (atleast on my SF). It seems to be related to some files that are written to my SD card.

If i clear the SD card and reboot - no high CPU.

If i leave files the SD card - high CPU.

I'll look into this issue a little more if someone else can replicate the same.

[Guest Afrodude]

High CPU when loading is perfectly normal; as its loading up all your applications and other things into memory. It should settle down after a minute or two.

[Guest nrps1]

I must have started from scratch about 5 times, just beginning to give up, when I tried using VM Heap Tool (increasing mem to 32mb). That seems to have taken it from 99% constant to 22%. Worth trying out, but may be a red herring!

[Guest nrps1]

I must have started from scratch about 5 times, just beginning to give up, when I tried using VM Heap Tool (increasing mem to 32mb). That seems to have taken it from 99% constant to 22%. Worth trying out, but may be a red herring!

No such luck, rebooted and back to square one :) really getting fed up with this!! Got a week before I hand it over as a present to the gf, anyone got any ideas?

Watchdog gives:

User - 16.2%

Nice 1.3%

System 71.2%

Idle 11.2%

OS Monitor gives:

Process - CPU Usage 89-99%

PID 1205 Android System - 70-90%

Installed Loader Pro earlier and reboot fixed until most recent reboot.

Please, anyone got any more ideas on a solution?

[Guest musclemuseum]

I have just got my phone, first thing I did was to root it with superboot root.

After the first reboot I got the same problem with high cpu, after a while it went down to low cpu.

Tried format sd card and open and close the camera application but didn't help

Anyone have a soultion?

Now I'm going to flash R3 to see what happends

Let me know what happens after you flashed r3

[Guest nrps1]

Let me know what happens after you flashed r3

Just out of interest, is flashing R3 simply vol - and choosing to reinstall zip from SD card?

[Guest ed.dark]

Hi,

first post :)

I have the exact same issue where the cpu is at constant 95-99% usage. After looking at many things I found that if i go into my camera application and open the slider for the options for the camera and close it and then close the camera application at this point it stops the high cpu usage. My current cpu usage is 16%. This happens everytime i boot my phone. I have to go go in and out of camera app to lower the cpu usage

hmm - that worked for me too!

[Guest Sere83]

Hi guys I don't seem to have high cpu issue all the time now it just fluctuates loads. Like if I look at the task manager one second it will be on 16% then shoot up to like 60% then back to 32% then up to 95% etc etc. Is this normal?

Also when I check whats draining my battery (battery has been very poor so far drops 1 bar within an hr and after only a few calls won't last the full day) it always says android system like 95% is this normal?

[Guest nrps1]

Hi guys I don't seem to have high cpu issue all the time now it just fluctuates loads. Like if I look at the task manager one second it will be on 16% then shoot up to like 60% then back to 32% then up to 95% etc etc. Is this normal?

Also when I check whats draining my battery (battery has been very poor so far drops 1 bar within an hr and after only a few calls won't last the full day) it always says android system like 95% is this normal?

Earlier in this thread they said 95% etc on Android System is normal yep. Mine does go up and down % wise, with the VM software it does seem to give some consistency with low percentages however.

[Guest z0mbix]

Hi,

first post :)

I have the exact same issue where the cpu is at constant 95-99% usage. After looking at many things I found that if i go into my camera application and open the slider for the options for the camera and close it and then close the camera application at this point it stops the high cpu usage. My current cpu usage is 16%. This happens everytime i boot my phone. I have to go go in and out of camera app to lower the cpu usage

Thank you! This also worked for me too. I'm also running r3. How did you find this out? Complete accident, or hours of scientific testing?

Cheers z0mbix

[Guest Brins0]

Just thought I'd add,

If you use a terminal emulator, and use the "top" command, you'll notice that the high cpu usage is caused by a process called "system_server". This isn't exactly more precise than other OS monitoring programs, but I'd assume it's to do with hardware. This would make what people are saying about the camera to fit correctly too.

I have found that opening a heavy 3D process such as "SpeedX" (brilliant game, get it now) also seems to cool that process off too.

[Guest trouser_mouse]

Yeah, I'm finding when my phone has been in sleep and I press the power button it can take 7-10 seconds to become usable and it remains jerky when flicking through screens for a short time after that.

I checked system_server on a terminal emulator and it's freaking out a bit... sometimes that camera trick above works, sometime I've found it's better to actually turn the phone off and on again then do the camera thing as it seems to help better then.

Seems to happen more frequently the longer the phone has been running.

I've increased the VM heap to 38mb to see if that makes a difference, but not found that it really helps. Understand the system_server issue is a known bug?

[Guest mELIANTE]

Just thought I'd add,

If you use a terminal emulator, and use the "top" command, you'll notice that the high cpu usage is caused by a process called "system_server". This isn't exactly more precise than other OS monitoring programs, but I'd assume it's to do with hardware. This would make what people are saying about the camera to fit correctly too.

I have found that opening a heavy 3D process such as "SpeedX" (brilliant game, get it now) also seems to cool that process off too.

Sorry for the OT, but is speedX running ok in your phone? It has a lousy framerate on mine :P

Edited October 19, 2010 by mELIANTE

[Guest Brins0]

Yeah, I'm finding when my phone has been in sleep and I press the power button it can take 7-10 seconds to become usable and it remains jerky when flicking through screens for a short time after that.

I checked system_server on a terminal emulator and it's freaking out a bit... sometimes that camera trick above works, sometime I've found it's better to actually turn the phone off and on again then do the camera thing as it seems to help better then.

Seems to happen more frequently the longer the phone has been running.

I've increased the VM heap to 38mb to see if that makes a difference, but not found that it really helps. Understand the system_server issue is a known bug?

Last night, I was experimenting to find out what caused the high CPU usage. I found that if the device is in a light room, and the keypad lights do not come on, the CPU usage seems to stay very high. If I turn the lights off in my room, the keypad buttons would light up, and the CPU usage would drop, after minutes of being at 100%, with no other interaction at all. I reproduced this on camera for a few friends, with various different roms, including a 100% clone of a friends that was fine.

I took my Blade back today and got it replaced for another one. I can't seem to reproduce the same bug with this one so I'm going to assume (for now) that it was a hardware fault.

If you can try and reproduce this bug on your phone, I'd be very interested to know. Using 'top' over 'adb shell' during boot is plenty, and it means you can leave the phone well alone to remove other potential catalysts.

[Guest trouser_mouse]

Last night, I was experimenting to find out what caused the high CPU usage. I found that if the device is in a light room, and the keypad lights do not come on, the CPU usage seems to stay very high. If I turn the lights off in my room, the keypad buttons would light up, and the CPU usage would drop, after minutes of being at 100%, with no other interaction at all. I reproduced this on camera for a few friends, with various different roms, including a 100% clone of a friends that was fine.

I took my Blade back today and got it replaced for another one. I can't seem to reproduce the same bug with this one so I'm going to assume (for now) that it was a hardware fault.

If you can try and reproduce this bug on your phone, I'd be very interested to know. Using 'top' over 'adb shell' during boot is plenty, and it means you can leave the phone well alone to remove other potential catalysts.

If you can set out exactly what steps you followed I'll try and reproduce it and let you know :P