I have cyanogenmod gingerbread android on my HD2 but when I play games the phone gets very hot quickly, after about 5 mins. Is there any way I can set CPU speed lower or any other way to stop it getting so hot. Works fine when just browsing or with windows.
Thanks
cant you set profiles using setcpu?
Thanks for the reply, would that solve the issue?
Everyone's processor is different so we can't answer that, won't hurt to try though eh?
$1 gets you a reply
In cm7 builds,,,, settings, cyanogenmod settings, performance, CPU settings.
Thanks for the replies everyone, I put setcpu on and it looks to be working great, Is 37C battery temp ok when playing games on the phone?
Related
this may be posted in the wrong section but i would like everyone running froyo to test this out
HERE IS THE LINK TO GET THE LATEST SETCPU
http://forum.xda-developers.com/showthread.php?t=505419
So I have been doing some experiments on ways to save battery life....I think i have made a break through it is not fully tested i would like for some of you to try it out.
with the latest updates to your ROM itself, setcpu, superuser, and the addition of cache cleaner and the incredible AUTOKILLER (a must have) i have been able to run extremely low setcpu sleep profiles without any noticeable loss of performance.
Believe it or not i have my sleep profile down clocked to 19200mhz with out "noticeable" performance loss
i would like for some of you if possible to try these profile out for a while and see how it works out for you
DEFAULT 480min---whatever you want max (mine is 787) ondemand (for performance)
OR DEFAULT 245min---whatever max (for even more battery savings)
SLEEP 192min---480max ondemand (works great even without sleep to wake lag)
it works dont believe me then check out set cpus new feature "time in state"
open setcpu
go over to info
scroll down a little and you will see the times in state your phones cpu runs in the most
you should now see values at the lowest state of 19200
if this works in theory we can benefit from longer battery life
and faster charging
please try these out and report back to the post or PM me...this could be good
Thanks
UPDATE 8/22 EDIT: some users are having success running an even lower default 19min--whatever max (thats even more savings) will be looking into it
try these even lower profiles
DEFAULT 122min--whatever max (screen ON cpu does not drop below 122mhz)
Screen OFF 19min--245max (no lag just ran pandora and cardio trainer at the same time here no lag from sleep to wake either)
or Screen Off 19min--480 max for more performance
REMEMBER not to have conflicting profiles and to have SCREEN OFF at your highest priority
please post here your own findings and results
Thanks again
UPDATE 08/24/2010
after experimenting with other speeds i have finally settled on these speeds for my personal taste on performance and battery savings
MY FINAL SETTINGS...
DEFAULT 19MIN---786 or whatever MAX on demand
SCREEN OFF 19MIN---480 MAX on demand (highest priority) think deeply about why this is the highest
TEMP <40 19MIN---528MAX (screen off overrides this which cools anyway)
BATT <40 19MIN---604MAX
next more into advanced settings....coming soon
UPDATE 08/26/2010
im almost at the holy grail here
try this set up
SCREEN OFF 19--480 (95 priority)
TEMP <40 19--580 (90 priority)
ADVANCED SETTINGS
SAMPLING RATE---100000
UP THRESHOLD---98
ignore nice ---0
power save bias---0
hit apply (if you like it check set at boot)
ALL CPUS ARE NOT CREATED EQUALLY WE ALL KNOW THIS SO DONT EXPECT MY EXACT SETTING TO WORK FOR EVERY SINGLE PHONE
I CAN ONLY OFFER A STARTING POINT BUT ITS UP TO YOU TO TWEAK IT BUT ITS WORK
I HOPE THIS HELPS
things to notice....
in the main screen in setcpu watch the main frequency values bounce up and down...after a few seconds the values seem to stabilize at the lowest frequency of 19
in time of state screen even when screen on most of the time the 19 freq get the most values
i need a few guys to run, test and monitor the values that i just posted ^^^HERE^^^
this may further the battery life once we stabilize the frequency to 19 most of the time while keep the SAME performance which i think i may have did
run some linpacks and quadrants with those setting
i got
5.4 linpack running 787max
431 quad running 787max
then it drops back to 19 and stabilizes
hope this works and please post all your feed back and setting so we can learn this and get it perfect
thanks
I even use 122 and 480 for my screen off profile.. And I don't have any lag at all.
thisisreallygay said:
I even use 122 and 480 for my screen off profile.. And I don't have any lag at all.
Click to expand...
Click to collapse
19 is even lower try it
Oh 19200? Wow I wasn't paying attention well enough. I'll try it.
Almost from the beginning of my rooting in May and using SetCPU, I've been using 19.2- 748.8 (on demand) with the screen on (sometimes higher but recently reduced the max to see if it helped with some FC's I was having - still haven't determined if it was the profile or the ROM that fixed my FC's).
I use 19.2-245 for screen off. I'd venture that there's about a one second delay for the caller ID to work once a call rings in, but it's more than bearable and worth it.
I have it go to 19.2-528 when the battery is less than 25%,and 19.2-480 if the temperature is above 49 degrees celcius.
I wonder what it's like when receiving a call. I just set it and I'm not having any lag with just turning it on or anything. I'll test it out with other things. I hope this greatly improves my battery.
roirraW "edor" ehT said:
Almost from the beginning of my rooting in May and using SetCPU, I've been using 19.2- 748.8 (on demand) with the screen on (sometimes higher but recently reduced the max to see if it helped with some FC's I was having - still haven't determined if it was the profile or the ROM that fixed my FC's).
I use 19.2-245 for screen off. I'd venture that there's about a one second delay for the caller ID to work once a call rings in, but it's more than bearable and worth it.
I have it go to 19.2-528 when the battery is less than 25%,and 19.2-480 if the temperature is above 49 degrees celcius.
Click to expand...
Click to collapse
shame on you for keeping that secret all to yourself
SHAME
By the way why did you say froyo roms specifically? I'm trying this on tainted tenzo and it's working. I'm usually on a frooy ROM though.
Hi Guys,
Can you please tell me how to get setcpu? I can't find it in the market.
Sent from my Nexus One using XDA App
Search for it on his website, idk what his website is you'll have to search for it. Or download a ROM with it already in it.
im on froyo 30 and was unable to get the 19.2 to show on time in state with screen off profile set to 100 priority at 245/19.2
i was however able to have it start using that frequency by using 710/19.2 as my default setting, then enabling the 245/19.2 profile as screen off.
ive read its not too good to have the cpu jump more than 300mhz per profile though so im not sure how this will work out.
thisisreallygay said:
By the way why did you say froyo roms specifically? I'm trying this on tainted tenzo and it's working. I'm usually on a frooy ROM though.
Click to expand...
Click to collapse
hmm last time i was on sense rom sense fell apart if you clocked lower than 245
epically receiving a phone call
but i only test this method on froyo
I've heard that too. Although I don't know what is bad about it.
sh_mohanna said:
Hi Guys,
Can you please tell me how to get setcpu? I can't find it in the market.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
HERE
http://forum.xda-developers.com/showthread.php?t=505419
eklipze said:
im on froyo 30 and was unable to get the 19.2 to show on time in state with screen off profile set to 100 priority at 245/19.2
i was however able to have it start using that frequency by using 710/19.2 as my default setting, then enabling the 245/19.2 profile as screen off.
ive read its not too good to have the cpu jump more than 300mhz per profile though so im not sure how this will work out.
Click to expand...
Click to collapse
i heard that too but all froyo dev have a 245 to 710 stock on their roms
thats why i kinda spilt the two profiles and why 245min--- is experimental
leave your screen off for a while and see if the ime of state shows up
also make sure not to have conflicting profiles running in setcpu
Hmm. Well tainted is vanilla but has some sense elements (like sense dialer) So idk. It seems to work. I'll test out calls.
thisisreallygay said:
Hmm. Well tainted is vanilla but has some sense elements (like sense dialer) So idk. It seems to work. I'll test out calls.
Click to expand...
Click to collapse
oh ok tainted is not vanilla
tainted IS sense with sense removed with vanilla remaning hence the word tainted
some sense is still there
i think
Yeah it's got sense contacts and stuff but vanilla messaging. But it has the sense dialer so I think it would also have lag with calls if the sense ones were having lag. And I just tested it and it took a lil while for it to recognize whose number it was but it still gave me plenty of time to answer the call. I'll be testing to see how it improves battery. Thanks for the find
Im also testing setcpu Advanced settings batery life (without performance loss)
What settings are those?
Hey guys,
A few weeks back I rom'd my HTC hero with VillainRom 12 and it was working great for awhile. Now however it crashes all the time, or just freezes up and I have to remove the battery.
I have the phone over clocked to about 650mHz. The battery temps seem fine.
Has anyone else experienced this problem before? Any way I can do a debug on my phone to find out what's crashing?
It's really starting to annoy me considering that I use my phone for my business and it's not good when a customer calls and my phone dies and reboots when I go to answer a call.
try overclocking to a lower extent
it might be because your phone cannot handle ur clock speed
(my MAX clock speed is 672... it simply crashes with 691 or higher)
You were absolutely right. It was clocked too high.
I turned it down and now it works great.
Thanks for the tip.
652 seems to be my max.
710 is my max, I can't go below 192 either or the phone starts to have a fit, I wanted to use a lower clock speed in "screen off" mode, but I'll have to stick with 192
So no matter what kernel I use, when ever i use SetCpu (or overclock widget) to underclock my phone when the screen is off it causes the phone to freeze and I have to pull the battery out. I set it so that it goes down to 200mhz, tried 400mhz and experienced the same problem. Any ideas? Solutions?
rockethot said:
So no matter what kernel I use, when ever i use SetCpu (or overclock widget) to underclock my phone when the screen is off it causes the phone to freeze and I have to pull the battery out. I set it so that it goes down to 200mhz, tried 400mhz and experienced the same problem. Any ideas? Solutions?
Click to expand...
Click to collapse
More info.. What rom are you running? Are you sure your rooted? What settings are you applying?
I have not had any issues yet with setcpu and my screen being off
rjmjr69 said:
More info.. What rom are you running? Are you sure your rooted? What settings are you applying?
I have not had any issues yet with setcpu and my screen being off
Click to expand...
Click to collapse
I'm running Baked Snack 1.1, doesn't matter what rom or kernel I use though, it still happens.
It doesn't matter if I use overclock widget or SetCpu, if I were to set it so that my phone underclocks to 200mhz or 400mhz while the screen is off it freezes and I have to pull the battery.
Same here im running stock and i've tried setcpu and no matter what i hav to pull the battery out everytime. So i uninstalled it.
Sent from my Epic 4G
I had the same problem set the cpu with min of 400 and max off 800 should fix your problem
Sent from my SPH-D700 using XDA App
It means that there is not enough voltage run that frequency on your phone. Some times these kernel developers undervolt the phone which all phone don't support at all. Try some other kernel like the xtreme kernel. That kernel actually work for me and I can underclock my phone without freezing.
rockethot said:
So no matter what kernel I use, when ever i use SetCpu (or overclock widget) to underclock my phone when the screen is off it causes the phone to freeze and I have to pull the battery out. I set it so that it goes down to 200mhz, tried 400mhz and experienced the same problem. Any ideas? Solutions?
Click to expand...
Click to collapse
wow.. i just posted something like this i had set cpu installed since i rooted my phone last week. today i was playing with the settings because my music was stuttering.. i thought it might be a underclockign problem so i changed the profile to "ondemand" it made the stuttering better and everything seemed fine. about 12 hours later i got home and was playing with the phone. i updated 3 programs in market and all of a sudden my phone would go to sleep and not wake up. had to do a battery pull. i uninstalled the 3 programs i updated but the problem kept going. just uninstalled setcpu. hopefully it resolves everything
using epic experience
murso74 said:
wow.. i just posted something like this i had set cpu installed since i rooted my phone last week. today i was playing with the settings because my music was stuttering.. i thought it might be a underclockign problem so i changed the profile to "ondemand" it made the stuttering better and everything seemed fine. about 12 hours later i got home and was playing with the phone. i updated 3 programs in market and all of a sudden my phone would go to sleep and not wake up. had to do a battery pull. i uninstalled the 3 programs i updated but the problem kept going. just uninstalled setcpu. hopefully it resolves everything
using epic experience
Click to expand...
Click to collapse
The use of profiles is not recommended on Galaxy S phones. The developer of SetCPU actually does not recommend using any other governor than conservative, even though we've been able to make Interactive work on some kernels.
I'm running Baked Snack 1.3 and found it to be stable at 1.2ghz using OC Widget. With screen on I have it set to min 400 and max 1200. With screen off it's set to min 400 max 600.
I too am having this problem. No mater what rom or kernal I use. It seems as if Setcpu and Overclock widget sometimes cant read the frequencies and let the phone underclock to 19.2Mhz which is probably like trying to wake the dead!
I wonder if it has anything to do with the new Superuser.apk? it always seems like setcpu is trying to get permissions. Maybe, I dont really know. Can one of you really smart people look into this?
In the meantime the only profile that I have set is screen off Max 800 Min 400, maybe that will work?
same issues here. i'm running with my screen off at min 100 and a max of 800. If i change my max to anything lower, my phone won't wake up. I'm running the latest VIPERrom. I'm hearing some mixed feedback about this app so i would like hear your feedback.
What i've gathered over the last several months, is that SetCPU profiles are buggy with our phone. Its recommended not to use profiles.
I'm fairly certain that SetCPU should not be used without a custom kernel that allows for over/under clocking. If you're on the latest ViperROM then you are using a kernel that we have no source code for, therefore it doesn't support over/under clocking; rendering SetCPU useless and prone to cause problems.
mattallica76 said:
The use of profiles is not recommended on Galaxy S phones. The developer of SetCPU actually does not recommend using any other governor than conservative, even though we've been able to make Interactive work on some kernels.
Click to expand...
Click to collapse
My SetCPU is using conservative and I haven't had any problems so far. I am running BonsaiROM 1.14.
jemarent said:
same issues here. i'm running with my screen off at min 100 and a max of 800. If i change my max to anything lower, my phone won't wake up. I'm running the latest VIPERrom. I'm hearing some mixed feedback about this app so i would like hear your feedback.
Click to expand...
Click to collapse
If you have it set to under 200 with the screen off it won't wake up after a while.
I've had the same problem on all builds and ROMs that I've used. The only constant through all the different setups I've used were Advanced Task Killer and SetCPU. I stopped using ATK (with auto-kill on screen off, I use EStaskmanager for manual killing when phone is on) and the problem seems to be mostly fixed. It does still happen once in a blue moon though, say once every day or two.
Phoenix Kernel/Syndicate ROM 2.1
SetCPU: 100min/1200max
Screen off: 100min/200max
Batter < 30%: 100min/600max
Here's an issue I just noticed late last night. My CPU seems to be stuck at max. I've tried different governors, wiped cache/dalvik and reflashed kernel and rom. I also killed all running apps to see if an app was causing it, to no avail.
Here's what really stumps me, my battery life seems fantastic. Not what I'd expect if my CPU is running at 100%. Could there be an issue with detecting CPU speed? As I mentioned before, trying different governors doesn't help with scaling but I notice when I select "powersave" my CPU jumps from max to the minimum value and stays there, still not scaling.
Before someone mentions I did search before posting. Went through the threads, tried the suggestions within and still have the problem. Hence why I'm posting here now.
Am I overlooking something? Any help will be appreciated, thanks!
Edit: My current rom and kernel are in my sig.
so are you monitoring this via setcpu on Decks?
alaman68 said:
so are you monitoring this via setcpu on Decks?
Click to expand...
Click to collapse
Yes I am, is there a known issue?
My understanding is that having both setcpu and the native CPU performance running will result in some conflict. that is probably the problem, but I don't know how to monitor the scaling with the native performance. so i see what you are trying to do.
I never run setcpu on CM7 or Decks because it is built in, but if the battery life is alright, it would appear the built in takes precedence.
Is there a good way to monitor the CPU without setCPU? Thanks
cesjr02 said:
Is there a good way to monitor the CPU without setCPU? Thanks
Click to expand...
Click to collapse
check out "system panel"
edit: or android system info app > system tab > cpu. gives you a break down of time (%) spent at each frequency.
Thanks, I like that app a lot.
Unfortunately even after deleting setCPU I'm still seeing 100% CPU usage. According to system panel the System is using 80%.
Edit: I am underclocked to 499MHz, and that's where she's pegged. Still oddly enough I'm getting the best battery life I've seen in weeks.
My CPU doesn't scale correctly either. Its either running at MAX, Deep Sleep, or 245mhz. Never does it use the in between frequencies no matter what govenor I use(I have tried them all). I use CPU Spy to check scaling and No Frills CPU to change the governor both are from the market.
cesjr02 said:
Thanks, I like that app a lot.
Unfortunately even after deleting setCPU I'm still seeing 100% CPU usage. According to system panel the System is using 80%.
Edit: I am underclocked to 499MHz, and that's where she's pegged. Still oddly enough I'm getting the best battery life I've seen in weeks.
Click to expand...
Click to collapse
so if you do this:
or android system info app > system tab > cpu. gives you a break down of time (%) spent at each frequency
what is the frequency while it is sleeping?
1. you may need to overclock just a bit
2. you may want to reflash rom without wiping the data and see if that helps
3. every phone is slightly different, so yours may need more time to process the commands at 499, especially if you are undervolted as well. which is why you getting pegged.
alaman68 said:
so if you do this:
or android system info app > system tab > cpu. gives you a break down of time (%) spent at each frequency
what is the frequency while it is sleeping?
1. you may need to overclock just a bit
2. you may want to reflash rom without wiping the data and see if that helps
3. every phone is slightly different, so yours may need more time to process the commands at 499, especially if you are undervolted as well. which is why you getting pegged.
Click to expand...
Click to collapse
Thanks, says the time spent at 499 MHz is 92.51%. I don't think underclocking is the issue. If I overclock to 1113MHz it will peg there as well. Seems to only go 100% when screen is on however according to the system panel app. I'll try your suggestion in (#2) and report back.
Tried reflashing the rom without wiping. Still have the same issue. So odd. I'll try a different kernel just to see if that helps, but I'd hate to part with my 3.3.7 LEE kernel.
Last thing I can think of is doing a full wipe, but I'd like to avoid that if I can.
Definitely experiencing the problem with other kernels. I'm out of ideas.
Did you try tiamat 4.1.0? I'm using it now and the battery life is right there with 3.3.7.
Sent from my PC36100 using XDA App
Did you restore any apps with titanium backup by chance?
Sent from my PC36100 using XDA App
By the way, I appreciate all your help alaman68.
Tiamat 4.1.0 was the other kernel I tried. No luck. Also I've never used titanium backup to restore apps. I'm stumped as to why my CPU won't scale anymore. The Android System seems to be using as much as I allow it.
Trying, you could try a sense rom for a day and check the scaling for a benchmark.
Is there anything else you are running? Undervolting, v6... Anything else?
Not undervolting as my phone never liked it. Nor running V6 or any other scripts either. I'll try flashing a sense rom, see if I have the same problem there. Or else, think doing a full wipe and reflash everything would help?
if all else fails, a clean flash won't hurt. Even get a new download. Gotta ask, did everything properly? you using amon_ra recovery? did you download any new apps when that started happening?
I may just have to. I suppose there's always a chance I made a mistake somewhere, but I've been at this rooting/flashing thing for a long while. Thing is, everything was fine up until I noticed it last night.
I'll do a clean install. I can always nand restore if it doesn't work. (Save me the time to set up everything.)
I'll report back
Did a clean install and guess what, my CPU is scaling again! There must have been a conflict somewhere. Thanks again alaman68 for all your help and suggestions. Sometimes these phones get gremlins I tell ya.
I've searched for hours for this topic on google and I've tried a lot of the presets people are using for their N4 but man, it just doesn't work with mine unless mine is different? Whenever I use the presets of other people who claim it to be good, my N4 just stutters or just crashes and restarts. It also says many apps and even franco kernel updater has stopped working every like 30 seconds. Its annoying and not normal. I want good presets for the best battery life without performance loss and I would like good screen settings too. Much appreciated guys, thanks.
Cheers.
valeriee said:
I've searched for hours for this topic on google and I've tried a lot of the presets people are using for their N4 but man, it just doesn't work with mine unless mine is different? Whenever I use the presets of other people who claim it to be good, my N4 just stutters or just crashes and restarts. It also says many apps and even franco kernel updater has stopped working every like 30 seconds. Its annoying and not normal. I want good presets for the best battery life without performance loss and I would like good screen settings too. Much appreciated guys, thanks.
Cheers.
Click to expand...
Click to collapse
Don't put so much importance on voltage. I'm only undervolted by -50mv and I have awesome battery life. I can try to get my screen settings up a bit later, I've calibrated it to match my n7 as closely possible. I'm fast binned and anything at or over -100mv causes mass instability for me, it sounds like you might be in the same situation.
Thanks. May you please show me your voltage settings please?