[Q] Phone extremly laggy, 100% constant CPU load - EVO 4G Q&A, Help & Troubleshooting

I'm on CM 7.0.3.1, SavagedZen 2.2.1 CFS HAVS kernel. Haven't made any sort of changes in awhile. My phone is laggy to the point of almost being unusable. CPU load is staying at 100%. Not an expert on finding out what's causing it...but battery use has cell standby at the top at 23%. Supposed to be a question here..so, what's causing this? How do I fix it? Let me know of any other info needed to diagnose. Thanks.

effluent said:
I'm on CM 7.0.3.1, SavagedZen 2.2.1 CFS HAVS kernel. Haven't made any sort of changes in awhile. My phone is laggy to the point of almost being unusable. CPU load is staying at 100%. Not an expert on finding out what's causing it...but battery use has cell standby at the top at 23%. Supposed to be a question here..so, what's causing this? How do I fix it? Let me know of any other info needed to diagnose. Thanks.
Click to expand...
Click to collapse
install terminal emulator, open it and do "top -n 5 -m 5" (press enter)
It will spam some things across the screen a few times, with %ages that indicate where the CPU usage is going.
take a screenshot of that if you can or post what you see towards the top of the list.
There's probably some better GUI apps that can display it a little more friendly, but that's the "dirty" way to see where the biggest CPU hog is.

It was the Pure News widget. Had it awhile without problems but I uninstalled it.

Related

defrost problems

Hello,
I find things very funny on my phone let me describe. This happens on both opendesire 4.0.25 and defrost 4.9 . I am downloading defrost 4.7 now to see if the problem solves. This is it, my phone clock speed is always at 998MHZ and the CPU usage is always at 100% . I realised that is why my phone always got hot and the battery drains fast. I hope someone could give me a solution, or is it the new kernal that is giving the problems?
Thank you.
On Defrost you can try a different kernel directly from the Defrost setup.
I am now using HAVS 1113and the phone works great and the battery life has increased significally
Thank you for your reply
but that is not the problem. This is, my CPU usage is always at 100% (checked with many apps) also the CPU setting is ondemand which means my usage being at 100%, makes the clockspeed always at 998. The process that took up 76% of the CPU was named android.process.media or something like that. Anyone knows what it means and what I am supposed to do now? How am I to disable the process and what process is that? How can I disable it?
Thank you and I'm hoping for more replys its quite upsetting to have your processor running high all the time
Sounds like a background app is stopping the Desire going into a sleep state...you might have to reset the phone and add 1 app at a time to see what it is...
install Android System Info on your Desire and take a look at the tasks list.
There press the menu button to sort the list by CPU load.
The total CPU load should be around 10%, which gets consumed by the Android System Info process itself, and a small amount by Android System Info.

CPU usage through the roof, may be causing the reboots, any ideas?

So I hve been going nuts trying to figure out why my phone keeps rebooting. I'm in another country so getting a replacement isn't an option for me and it seems it hasn't helped some people anyways (After a while it comes back).
THe only constant I see is that the CPU usage after maybe 30 seconds after the phone comes on stays at 95-100% all the time. Only thing that makes sense is that the phone is shutting itself down before it melts down.
This kinda makes sense since it seems the more I try to do the more random the reboots become.....and battery life is beyond horrible. I did the steps to increase battery life and battery life is making this phone virtually unusable off AC power (EXample: Leaving from my Brother in laws apartment and travelling 10 floors down to my car results in 89% battery left. Phone is dead within the hour if i use it and 3 or 4 if leave it idling.
I tried killing all the tasks that te phone starts up with but nothing change the CPU usage. I thought maybe it was the kernel but I flashed the latest one from this thread: http://forum.xda-developers.com/show...RI+version+PRL [the undervolted version]. Not sure if that would help (THe info in this forums is so scattered and disorganized it makes my head spin.....and I'm a techie).
Also try flashing the combo package of the latest radio, PRI, NV etc and that doesn't work also....CPU usage is still through the roof.
I just got this a few days ago. I'm currently on:
HBoot 2.10 [s-off]
H/W 0004
Basband 2.15.00.11.19 [I was on this before I was rooted]
Kernel version 2.6.32.27-SBC-net-4.2.2-less-havs [email protected] #19 [Just flashed] ROM myn's Warm TwoPointTwo 9RLS 4)
Software: 3.3-.651.3
PRI Version: 1.90_0003
PRL Version: 60662
Can I get some help from people smarter then me. I'm at the end of my rope and I'm not convinced a handset swap is going to fix my issue esp. since this was BNIB straight from Sprint and other people who've had this issue and had a new phone seem to somehow have it later.
If i leave it alone it will reboot on its own eventually. If i switch from airport to turning on the cell data, reboot, turning on wifi......reboot, toggling 4g.......reboot, After a few web page searches......reboot, open up an application.....reboot.
This isn't temperature related as far as I can tell.....The app I have monitoring temp has seen this happen at 25 degrees and sometimes less.
PLEASE HELP
Ok.. firs tthings first..
when your phone is unstable and rebooting, dont use an undervolt kernel. Undervolt kernels provide less power to the CPU at set frequencies.
In my case, I discovered undervolting CAUSED reboots, because my phone couldnt handle anything under 950mv... there is such a range in the quality of the components that theres no way to always say yes, undervolting this much will work with every phone.
so 1: Use stock kernel ( for whatever rom your using.. also use a well established rom, not one of the 'hey, last night i got bored and made this' ones.. it may work, but it may be so buggy its what is causing your crash )
2: do a fresh install. run the phone with 0 apps added, see if it has the same issue. If it does, may be the phone itself. If it doesnt, its one of your apps.. install one at a time, and see if it improves.
and you made two posts why?
Didn't know they would move it. Posted in the wrong forum and they moved it as well. lOL. My bad.
I've been on a stock kernel up until I started trying different kernels. I will try the other one then.
My CPU usage is the problem I think. I have both memoryusage and system monitor and both report the same thing.....95-100% usage constantly. If I could resolve that then maybe my phone would work properly.
Didn't know they would move it. Posted in the wrong forum and they moved it as well. lOL. My bad.
I've been on a stock kernel up until I started trying different kernels. I will try the other one then.
My CPU usage is the problem I think. I have both memoryusage and system monitor and both report the same thing.....95-100% usage constantly. If I could resolve that then maybe my phone would work properly.

SetCPU Gingerbread

Is anyone using SetCPU with gingerbread?
I'm using GingerVillain 1.5 but I can't seem to find the right profiles with SetCPU.
Oc'd @ 1,2 Ghz without profiles.
Because when I use the screen off profile, my screen sometimes won't turn on.
Screen off - min 245 max 1200
Can someone help me finding the right profiles?
Share your user experience.
In my experience and many others too, the profiles are not needed. The only profile you should ever need is a temperature profile and that's only if you really have it cranked up.
Having a screen off profile is always bad since switching to another profile doesn't happen instantly - there are polling intervals involved and until the next cycle runs your phone will still be using the screen off profile. That makes the phone slow which causes SetCPU to take longer in switching profiles, bogs down the cpu and it becomes a vicious cycle for a few seconds (sometimes a couple minutes). All the while it's draing your battery because the cpu has to work harder. Even regular profiles eat the battery due to the constant querying of the systems status and processing power used for that - which is the main reason you'll hear people whining about their battery life (some aren't effected as much).
Profiles are just not a good idea except for a temp profile for those that oc to the higher GHz (probably 1.4+).
You could try using cpu tuner instead. Gives you way more options.
CM 7
You have a lot of options with cpu tuner.
What triggers and/or profiles do you use?
My screen on/off has been working fine with CM7 nightlies before and after the RC1. I've been using SetCPU with a normal profile of 1017max/245min and a screen off profile of 365max/245min.
I think your issue is with overclocking. Idk about Gingervillain but as far as CM7 goes lots of people are having issues with the on/off animations and wakelock issues when overclocked over 1ghz. Try using your profiles and clocking at or under 1ghz and see how things change.
Not sure why anyone would really need a higher clock than 1ghz but what do I know. I dont see any slowdowns at 1017mhz and I feel that anything faster than that would lead to heat or battery issues?
Yes, screen off profiles work. But they drain your battery faster than if you have no profiles.
Sent from my T-Mobile G2 running Cyanogenmod.
thanks bro, i OC'd to 1017 and there are no issues
ibemad1 said:
Yes, screen off profiles work. But they drain your battery faster than if you have no profiles.
Sent from my T-Mobile G2 running Cyanogenmod.
Click to expand...
Click to collapse
I'm not so sure about this. Have you tested this at all? Starting using screen off profiles of 365max/245min have really increased my battery life, especially when my phone sits idle for a decent amount of time. I don't think you could see more battery life by leaving the clock at 1ghz while the screen is off.
martonikaj said:
I'm not so sure about this. Have you tested this at all? Starting using screen off profiles of 365max/245min have really increased my battery life, especially when my phone sits idle for a decent amount of time. I don't think you could see more battery life by leaving the clock at 1ghz while the screen is off.
Click to expand...
Click to collapse
Every kernel that I know of out there drops down the clock cycle when the screen times out. The reason not having the screen off profile saves the battery is because SetCPU isn't constantly sending requests about the phones state and then checking that against your profiles to see if it meets the parameters set in them.
Now it could be a bit different for you. You might have a different set up or different apps that make having a screen off profile useful (ones that constantly update or run in some way). You just have to watch your phone for a few days and get an app that keeps track of that stuff so you know which route to take.
KCRic said:
Now it could be a bit different for you. You might have a different set up or different apps that make having a screen off profile useful (ones that constantly update or run in some way). You just have to watch your phone for a few days and get an app that keeps track of that stuff so you know which route to take.
Click to expand...
Click to collapse
This is very true. It is definitely hard to make a blanket statement because no two people have the exact same setup. All I was saying is what I've been doin with the screen off animation and I've been having pretty solid battery numbers.

[Q] SetCPU and battery life - am I doing this right?

I'm looking to optimize my battery life without sacrificing performance when I need it. I know it sounds easier said than done, but I figure that if anyone might know how, they'd be here. My goal here is to have the performance when I need it, and to keep the battery preserved when I don't.
I'm rooted and running ViperROM 4.0.4 Trinity v2.0. I have the "Genocide 1.2GhzOC EB13 Kernel v0.3a" kernel also flashed to my phone. SetCPU is installed and I've set up my profiles, but I think I may be doing something wrong with them.
I am using autodetect settings as is recommended for adjusting clockspeed. Everything is set to on boot. All profiles are set to conservative as I'm not sure which ones actually apply. Below are screens for everything I have currently set up.
|
|
Am I doing anything wrong here? And if not, is there anything I need to do to improve battery life without sacrificing performance?
I would bump your charging max to 1200Mhz and keep the min at 1000Mhz, although I keep max and min while charging through AC power at 1200Mhz.
Your screen off profile is fine. If you get hiccups or missed calls for any reason, bump the max up to 400Mhz.
If you can run it smoothly, set your minimums for your battery profiles to 100Mhz. It what I'm at now and it runs fine. You may want to keep your minimum for your "screen off" profile at 200Mhz if you get hiccups or missed calls like I mentioned before.
As for your battery <50% profile, I'd set the min at 200Mhz if you're wanting to save battery. Don't want the phone running at a higher clock when it doesn't need it. That's the point of running the min lower.
I personally uncheck the "set on boot" to allow SetCPU to always come back to the appropriate profile rather than going back to the default setting.
Also, set a Battery < 101% profile which will be your new default. I have mine at max 1000Mhz and min 100Mhz and it works well.
Also, conservative simply means the battery will remain at the lowest possible clock until it needs more juice. Assuming it starts at 200Mhz, it'll bump up to 400Mhz, 800Mhz, etc. depending on what the demand is. It will jump frequencies from 200Mhz to 1000Mhz if necessary.
On Demand means the CPU will either be at your minimum set clock frequency or your maximum.
On Demand is usually the most compatible/stable, but the conservative setting is best for battery/performance if your kernel allows it.
Hope this helps =). Let us know if you have more questions.
EDIT: The "set on boot" button simply sets the min and max that's shown on the main screen in SetCPU. If this button is unchecked but the "enable" button on the profiles menu is checked, your profiles will still adjust accordingly.
I can't really see the profiles but do you have the Max set at 400 when the battery is under 50%? If you do your phone will crawl. The 1000 is undervolted. That way you get speed and save battery. And on demand does not.mean that your CPU is either at min. Or Max. It means that it Scales faster then Conservative does. My profiles are when battery is less than 50% I go to 1000/100 and when screen is off I'm at 200/100 all set on demand. My regular setting.is 1200/100.
Sent From My Evo Killer!
I'd like to hijack this since I have a similar question.
I'm using ACS Frozen 1.0 and have the latest SetCPU and am still getting pretty crummy battery life.
The weird thing is that in SetCPU the maximum CPU frequency is always 1.2ghz even if I drag the slider down to 1.0. I don't currently have any profiles enabled that would cause this, so why won't SetCPU let me top off a 1ghz undervolted instead of 1.2ghz?
My battery life definitely hasn't improved at that's a big bummer for me :\
I also have a question. I kept getting a message about superusers rights not being given. I searched to see how to grant SU rights, but could not fond any. I turned the phone off and on, and that message did not pop up anymore.
Now the main screen I cannot adjust any of the numbers, is this normal? I can however enable and make profiles. I made the first one if temp is greater then 0 (I obviously do not want it like this, but its just a test) then it should be OC to 1200. When I saved this in the top right hand corner it says I am at 1200, however when I bring up a program, and go to setcpu and look at the main screen it says 1000.
So what am I doing wrong.
badbeats said:
I also have a question. I kept getting a message about superusers rights not being given. I searched to see how to grant SU rights, but could not fond any. I turned the phone off and on, and that message did not pop up anymore.
Now the main screen I cannot adjust any of the numbers, is this normal? I can however enable and make profiles. I made the first one if temp is greater then 0 (I obviously do not want it like this, but its just a test) then it should be OC to 1200. When I saved this in the top right hand corner it says I am at 1200, however when I bring up a program, and go to setcpu and look at the main screen it says 1000.
So what am I doing wrong.
Click to expand...
Click to collapse
This might be a dumb question, but is your phone fully rooted?
I think so I used Clockwork mod 3.0.6 and I am running Bonsai 3, with 2.2.1
ZeppelinJ0 said:
I'd like to hijack this since I have a similar question.
I'm using ACS Frozen 1.0 and have the latest SetCPU and am still getting pretty crummy battery life.
The weird thing is that in SetCPU the maximum CPU frequency is always 1.2ghz even if I drag the slider down to 1.0. I don't currently have any profiles enabled that would cause this, so why won't SetCPU let me top off a 1ghz undervolted instead of 1.2ghz?
My battery life definitely hasn't improved at that's a big bummer for me :\
Click to expand...
Click to collapse
Yeah I hear you, I get the same crummy battery life with SyndicateROM, I was dying for the 30 hours ! Starting to think it's the battery itself.
musclehead84 said:
I can't really see the profiles but do you have the Max set at 400 when the battery is under 50%? If you do your phone will crawl. The 1000 is undervolted. That way you get speed and save battery. And on demand does not.mean that your CPU is either at min. Or Max. It means that it Scales faster then Conservative does. My profiles are when battery is less than 50% I go to 1000/100 and when screen is off I'm at 200/100 all set on demand. My regular setting.is 1200/100.
Sent From My Evo Killer!
Click to expand...
Click to collapse
Do you keep your 1200/100 on conservative? And what's the battery life you're getting on average? Dummy question but you know...
I'm going to try out this setting today actually with BakedSnack.
Referring to those of you getting "crummy" battery life. The screen takes so much battery many other things don't come into play. Therefore, if you're getting 4-6 hours of screen-on time, you're getting about what everyone else is getting. Those who report 30 hours+ probably have there phone idle more often than not.
Blankrubber said:
Referring to those of you getting "crummy" battery life. The screen takes so much battery many other things don't come into play. Therefore, if you're getting 4-6 hours of screen-on time, you're getting about what everyone else is getting. Those who report 30 hours+ probably have there phone idle more often than not.
Click to expand...
Click to collapse
Ahh this is a good point then. I'm still confused though why when I set my SetCPU to 1ghz it still keeps it at 1.2 :\
ZeppelinJ0 said:
Ahh this is a good point then. I'm still confused though why when I set my SetCPU to 1ghz it still keeps it at 1.2 :\
Click to expand...
Click to collapse
Did you update to the latest Twilight kernel? It's 1.0.1 I believe. Try that as I believed it fixed some CPU scaling issues. Just install the zip in CW, but I'd still wipe cache at last, just in case.
Sent from my SPH-D700 using XDA App
Blankrubber said:
Did you update to the latest Twilight kernel? It's 1.0.1 I believe. Try that as I believed it fixed some CPU scaling issues. Just install the zip in CW, but I'd still wipe cache at last, just in case.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
+1 I think this was a bug with the original release of Twilight Zone that was fixed in 1.0.1.
Blankrubber said:
Did you update to the latest Twilight kernel? It's 1.0.1 I believe. Try that as I believed it fixed some CPU scaling issues. Just install the zip in CW, but I'd still wipe cache at last, just in case.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I'm trying this out right away, thanks!
This whiny message brought to you by the letter E for Epic 4g

Battery life is horrible, yet not much is running?

I have my cpu settings on 245 245 powersave when the screen is off, yet I'm still getting horrible battery. I use my phone extremely lightly, maybe once in a while to listen to music. Check my emails, chat every so often. I use to get 48 hours with light usage. Seems I cant figure what is causing my battery to drain. I have a craigslist app, I had one search enabled so I deleted that to see how much it will effect. Does google talk drain that much? In the past it was fine. My usage shows the 2 main ones are cell standby and phone idle. Any tips on finding out what exactly is draining my battery? Im running CM 7.0.2??, latest stable, forgot. Koni's was the same. I thought maybe sense drained the battery, but it doesnt seem to be the problem.
Click the link in my sig and run that battery conditioning routine for one. What kernel are you using?
And dump SetCPU. Useless app, seriously...
1. Update to the latest stable version...7.0.3.1 released this morning.
2. Google talk could be draining, but I've never used it
3. Perhaps install it under a clean install and see if that helps.
Get tge system panel app. It'll show you what apps and everything that's eating your battery. Does the kernal your on perflock unlocked for over /under clocking cause if it isn't setcpu doesn't work.
Sent from my PC36100 using XDA Premium App
HipKat said:
Click the link in my sig and run that battery conditioning routine for one. What kernel are you using?
And dump SetCPU. Useless app, seriously...
Click to expand...
Click to collapse
+1 SetCPU is great for Sense ROMs, but not necessary for CM based ROMs.
looks to me like you were in pretty crappy coverage. that makes the phone work hard. it's justifiable that you'll have a lot of battery drain then, even while sleeping.
you can greatly reduce this by:
1: upgrade to newest cm7
2: flash a custom kernel. may i reccomend tiamat 4.0.1?
3: put your governer on smartass, and uninstall setcpu. smartass does it better.
4: use a bsm from viperboy. they decrease voltages. work almost too well.
5: USE JUICEDEFENDER! this will save a ton of battery in low coverage, because it turns off 3g when screen is off. this still lets you get calls and texts, but with mobile data off, your battery will last much longer while sleeping.
what prl are you on?

Categories

Resources