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.
Related
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.
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.
Hi guys,
My phone is constantly "awake" despite rarely even turning on the screen.
Would you know what could be causing this?
I'm currently running Caulkins rom and whatever kernel it came with.
My battery life is ~15 hours so I dont think it's affecting my battery too much.
Either way, is there an app that can tell me whats causing the drain?
First of all, to see if your CPU is sleeping properly when the screen is off, download CPU spy… it is an app that gives you total time the CPU has spent in each scaling frequency available.
Then download watchdog, this app tells you which programs are polling the CPU for usage.
Then download “better battery stats”.. this app tells you if there are wakelocks.
With those 3 apps running at the same time, you will find out any abnormalities in your system caused by applications.
Side note – disregard info that either of the apps report about each other (obviously)
I recently have bought a Defy plus.
Stock 2.3.4 ROM used so far with LauncherPro.
Doing OK with battery life so far, but now starting to look at the CPU over/underclock capabilities. Started with Antutu CPU Master and CPUTuner also.
One thing I haven't seen as yet is the ability to underclock clock below the min 300MHz.. or even whether this makes sense. I guess undervolting is the other option, but perhaps someone can guide me here.
use setvsel to oc/uv, thats the easiest and best app imo. although underclocking your phone below 300mhz may cause instability and makes the phone wake up much slower in my experience.
sent from my cm7 defy...
I agree with zakoo2: Going below 300 will not be a good idea and it will most likely not improve your battery life in any significant way:
My Defy is running between 300-600Mhz and right now the LCD screen is the biggest consumer: Changing the (auto-)brightness settings in CM7 will do *much* more to your battery life than going below 300mhz.
What really helps saving battery life: use setvsel and leave the minimum clockspeed at 300MHz, but set a vsel value of about 20 for it, then scroll down and enable "limit to vsel1 while screen is off".
Also, going below 300MHz will probably make the phone sluggish when waking up from sleep like if a call comes.
Sent from my MB525 using XDA App
im just change from 300mhz to 330mhz lowest. 300mhz will make my defy+ lag when got incoming call. im using smartass govenor.
I heard some guy out there got 80 MHz and running, but I'm not sure of it.
As people said, clocks lower then 300 MHz would make your phone run horribly while waking up (i.e., it would take a long time for the screen to turn on when receiving a call, and you would probably miss it most of the times). Setting 300 as VSel1 and limitting to it while screen is off (2nd-init enabled bootmenu has this option, and downloading SetVSel - free at Android Market - will also do the trick if you have a rooted, but stock ROM) will help you save a lot of juice. Using a lightweight launcher (I personally recommend MetroUI or Zeam) also boosts up batt saving. Last, but not least, setting brightness to auto or minimum (using frosted/mat screen protectors will help a lot while using the phone under direct sunlight) also saves loads of charge.
Obviously, using a light ROM (I think Barebones may be a good option, though I think it's not suitable for me, but it's a personal matter) and calibrating your battery in a monthly basis (via manual calibration - you can find how to do so by googling -, wiping batt stats in custom recovery and/or using the batt calibration app included in most ROMs - but also free at AM) also help.
I'm on stock, rooted, s-off
my device is getting extremely hot during normal use.(i dont play games at all, just whatsapp, facebook, news etc..)
sync is off, auto brightness.no google location reporting and history, no google now or history.
and using bbs to see what is going on ,i have no wakelocks and looking at battery screen, screen on time and awake time are almost identical.so nothing is keeping my device awake.
but for some reason, when the device is idle, the cpu goes nuts!
i installed cpu status bar xposed module so i could monitor cpu on real time, and i see the device jumping allot from 300mhz to 960 and 1000+ for no reason.(without touching it, and no apps running).when i touch the screen it scales to maximum.
it drives me crazy because i dont understand why the cpu behave like that.there is no logical reason for cpu going to max when i'm typing text.
its unbearable, cause its getting really hot while i hold it.
i have tried various kernels(elementalx, skydragon, faux, ionx, hacker kernel, but all of them shows that behavior.
on my old i9100, i never got that behavior, ondemand governor was perfect and i could reach 4 hours of screen on time.with the m8, i can barley pass it , going for 4-5 hours, because its draing too fast.
any suggestions?
*EDIT*
tried a factory reset, and i just installed xposed with cpufreq status bar module, and the device is still going nuts.WTF?
Can I ask... are you sure this is abnormal? I mean, are you seeing ill effects? Is the device laggy? Is your screen-off battery time awful?
All OS's do stuff in the background, and "idle" doesn't really mean anything at all to be honest -- even when you "don't have any apps running" there are apps running, and you'll always see the CPU cycle from idle to low speed to high speed if you're looking for it.
thebobmannh said:
Can I ask... are you sure this is abnormal? I mean, are you seeing ill effects? Is the device laggy? Is your screen-off battery time awful?
All OS's do stuff in the background, and "idle" doesn't really mean anything at all to be honest -- even when you "don't have any apps running" there are apps running, and you'll always see the CPU cycle from idle to low speed to high speed if you're looking for it.
Click to expand...
Click to collapse
i know there are background process and apps, and i don't except the device to stay at 300mhz all the time, but its quite annoying to hold on to a device and feel its temperature rising to insane levels without doing anything fancy with it.just texting.and every touch ramp the cpu to the max frequency, its weird.and unnecessary.
i don't know if its normal behavior, as i mentioned, my old i9100(galaxy s2) would not act like this. and i could get 4 hours of screen on time, and here, i get 4-5 hours max.it dose not seem logical.
I'm not using lte of nfc or BT.my reception is full(both wifi and cell).
i just want to know if this a normal behavior? anyone else having this heat buildup on light use?
I have a similar problem there on M8S. I killed half the background tasks, disabled syncing, auto backups, and then I open FBreader(or any other app) at 30% brightness and all the cpu cores go to 50 degrees C, heat up my battery to 43 degrees C. It results in loss of 40% of battery charge in just an hour. With screen off my device usually consumes 1-2% an hour. Whatever I do, I have never seen at least one core sleeping, they always work at 600-900MHz.