I have been using francos app along with kernel version 3.61. I set the minimum freq to 1.8 and then moved to set the max 1.8 and then that sent it into a boot loop and the back got real hot. I don't know what happened maybe between charging which makes it also hot contributed to it. Has this happened to anyone else. I tried it again but not plugged in and it was fine.
Why would you set Min and Max frequency the same? Over clocking increases the core(s) temperature, to much and you'll fry your device.
Sent from my Galaxy Nexus using xda premium
pr0xyw0rm said:
Why would you set Min and Max frequency the same? Over clocking increases the core(s) temperature, to much and you'll fry your device.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I think it's indeed the problem of overheating that causes the bootloop.
@TS: My Galaxy Nexus is blazingly fast at max 1,4 and min 400. It's no use to set min and max at the same frequency.
Good to know. I won't try that again.
Was that a safety thing related to temp?
F-Fect said:
I think it's indeed the problem of overheating that causes the bootloop.
@TS: My Galaxy Nexus is blazingly fast at max 1,4 and min 400. It's no use to set min and max at the same frequency.
Click to expand...
Click to collapse
Overheating won't cause a bootloop. The phone has built in safeties that force it to downclock regardless of your settings if it gets too hot. What will cause a bootloop is setting your phone to a frequency that is unstable, especially if you set it as min and max.
Related
I used to use setcpu on my first rom (LeeDroid) but it lagged my phone bad, so uninstalled it. Now have came back to it on droidzone RoM and its running fine, I only want screen off profile, but whats the best setting? am using smartass 245 max-128min is smartass best scaling?
EDIT
Topic started of has a question thread, so I thought on changing this to setCPU General CHAT
I recommend for screen off, 245-128 powersave governor.
Setcpu is a great tool ,but you need to play with it a bit with the settings...
Sent from my HTC Desire
dexter93 said:
I recommend for screen off, 245-128 powersave governor.
Setcpu is a great tool ,but you need to play with it a bit with the settings...
Sent from my HTC Desire
Click to expand...
Click to collapse
Thanks for reply, what you recommend for the main scaling? Also powersaver give's me lag, when switching screen back on.
Same here. I'm using smartass at screen-off for same reason.
shankly1985 said:
Thanks for reply, what you recommend for the main scaling? Also powersaver give's me lag, when switching screen back on.
Click to expand...
Click to collapse
Min 128 max 245 for screen off is too low to wake phone up, does not matter which governor you use. Min 128 max 245 with screen off may only work with ondemand governor, but i would not recommend it.
If you want to use min 128 mhz with screen off, you should set max to 422 mhz. As governor i recommend ondemand or interactive. On this way you can avoid issues in waking up the phone and you will still have a great battery life. For screen on you can use min 128 and max 768 with ondemand/interactive. But keep in mind, some phones have problems with 128. If your phone crashes sometimes randomly, set min cpu frequencies in both profiles up to 245.
A little different opinion:
rootSU said:
I use on demand with eviollet kernel min 128 max 245. Only thing that happens screen off is Poweramp, so can't comment for other back ground apps. But wake up is fine and power amp runs fine.
Of course with teh eviolet kernel you can set your own voltage levels so the next frequency up from 245 (384) can be set with the same voltages as 245, so having max of 384 would be no different power drain wise than 245.
Smartass is very bad for waking the phone so I steer clear of that all together.
Once thing that is important to note, using a different governor for screen off than screen on will also slow down your wake time. Changing governors can take time so will produce a lag when turning on the screen so find your governor and stick with it through out.
The most efficient governor for screen off if min and max are the same is either powersave or performance. The reason for this is they as default run at min or max (respectively) so they do not poll the CPU to check for load as they do not care. That said of course, these governors are no good fro screen on use IMHO so it would need a different one which then gives you the governor change issue.
Click to expand...
Click to collapse
That's interesting. Thanks! Didn't know the governor change issue.
MatDrOiD said:
Min 128 max 245 for screen off is too low to wake phone up, does not matter which governor you use. Min 128 max 245 with screen off may only work with ondemand governor, but i would not recommend it.
If you want to use min 128 mhz with screen off, you should set max to 422 mhz. As governor i recommend ondemand or interactive. On this way you can avoid issues in waking up the phone and you will still have a great battery life. For screen on you can use min 128 and max 768 with ondemand/interactive. But keep in mind, some phones have problems with 128. If your phone crashes sometimes randomly, set min cpu frequencies in both profiles up to 245.
A little different opinion:
Click to expand...
Click to collapse
Very good read thanks, am using ondemand for both default and screen off and its perfect screen off set to min128 max384 priority 100
works smooth not so sure about battery saving tho? but I have noticed display in battery settings is now down to 40% used to be always 55-65%
You might want to check this, as I'm pretty certain your 128MHz state almost never kicks in with that profile.
Also, check vdd levels as I think 128 and 245 share the same, so all you get is a placebo, and battery wise you get nothing.
erklat said:
You might want to check this, as I'm pretty certain your 128MHz state almost never kicks in with that profile.
Also, check vdd levels as I think 128 and 245 share the same, so all you get is a placebo, and battery wise you get nothing.
Click to expand...
Click to collapse
I am pretty sure 128 mhz cosumes less battery than 245 mhz, because clock is lower, even if the vdd level (the tension) is the same.
erklat said:
You might want to check this, as I'm pretty certain your 128MHz state almost never kicks in with that profile.
Also, check vdd levels as I think 128 and 245 share the same, so all you get is a placebo, and battery wise you get nothing.
Click to expand...
Click to collapse
Looking at the info and the time of each % 128 has 45% 245 13% 998 23%
I was shocked lad night, after 16 hours and at 12pm my phone had 51% battery
shankly1985 said:
Looking at the info and the time of each % 128 has 45% 245 13% 998 23%
I was shocked lad night, after 16 hours and at 12pm my phone had 51% battery
Click to expand...
Click to collapse
I hope shocked in a good way?
MatDrOiD said:
I hope shocked in a good way?
Click to expand...
Click to collapse
Very good way ha ha
I'd like to try SetCPU, but running across this thread has made me nervous... is there a guide somewhere please?
tobydjones said:
I'd like to try SetCPU, but running across this thread has made me nervous... is there a guide somewhere please?
Click to expand...
Click to collapse
There is no real risk mate, just don't go over clocking it all the way, right away. Start of small steps. Under clocking is very safe
Sent from my HTC Desire using XDA App
tobydjones said:
I'd like to try SetCPU, but running across this thread has made me nervous... is there a guide somewhere please?
Click to expand...
Click to collapse
http://www.setcpu.com/
You might want to check this, as I'm pretty certain your 128MHz state almost never kicks in with that profile.
Also, check vdd levels as I think 128 and 245 share the same, so all you get is a placebo, and battery wise you get nothing.
Click to expand...
Click to collapse
Looking at the info and the time of each % 128 has 45% 245 13% 998 23%
I was shocked lad night, after 16 hours and at 12pm my phone had 51% battery
Click to expand...
Click to collapse
What settings is that with mate?
tbaxter08700 said:
What settings is that with mate?
Click to expand...
Click to collapse
998max 128 min ondemand
Screen off 384 max 128 min ondemand 100% priority.
And that's it mate my battery life is superb
Sent from my HTC Desire using XDA App
Uploaded pic to show.
shankly1985 said:
998max 128 min ondemand
Screen off 384 max 128 min ondemand 100% priority.
And that's it mate my battery life is superb
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
And what other stuff do you have on/off? Mobile internet, WiFi?
tbaxter08700 said:
And what other stuff do you have on/off? Mobile internet, WiFi?
Click to expand...
Click to collapse
Mobile data always on, wifi only when download Apps, sync only when I want it to.
Screen brightness just under halfway, dont use bluetooth that much, never use GPS.
Anything else that I missed?
Im new to android, what is the best setting for setcpu for balancing performance and battery life. Thanks in advance
Sent from my SPH-D700 using XDA App
What Rom/kernel are you on? Voltage Control might be the better option.
The Root said:
What Rom/kernel are you on? Voltage Control might be the better option.
Click to expand...
Click to collapse
On leaky gingerbread eeo3, don't know what kernel but kernel version is 2.6.35.7, firmware is 2.3.3...
The lower the maximum speed you can tolerate will give you the max battery life. A lot of people keep 800 Mhz as max for that reason.
If you want a good mix between battery and performance, I recommend keeping your maximum clock at 1000Mhz (default) and lowering your minimum clock to 100Mhz (default should be 200Mhz) if your phone will allow it.
Blankrubber said:
If you want a good mix between battery and performance, I recommend keeping your maximum clock at 1000Mhz (default) and lowering your minimum clock to 100Mhz (default should be 200Mhz) if your phone will allow it.
Click to expand...
Click to collapse
Yeah, just make sure you have journaling on if you are going to try 100 Mhz. A lot of phones get the sleep of death from that. Mine is one of those. Then you will have to pull the battery and adjust your settings to 200 Mhz minimum on SetCPU.
Or....You could not use 100mhz at all!
It uses the same voltage as 200mhz. And by increasing the amount frequencies scaled makes the phone slower.
800mhz max, 200mhz min. 800mhz is volted -75 over 1ghz. Which should increase battery life.
Awsome stuff guys. Thanks for all the great info and to all that reply... Thanks again
Sent From My Epic 4G
darkierawr said:
Or....You could not use 100mhz at all!
It uses the same voltage as 200mhz. And by increasing the amount frequencies scaled makes the phone slower.
800mhz max, 200mhz min. 800mhz is volted -75 over 1ghz. Which should increase battery life.
Click to expand...
Click to collapse
I'd quote him but I'm on my phone. Rodderik has stated that all the frequencies use the same internal voltage except for 100mhz, which uses a slightly less internal voltage. What we're adjusting and seeing read in voltage control is the arm voltage, or the processor voltage at each frequencies. I'm not sure the exact difference, but there is a slight drop in voltage at 100mhz compared to the other frequencies? A battery saving difference? Who knows
Sent from my SPH-D700 using XDA App
Just insalled new syndicate frozen rom. Set cpu not compatible? Installed set cpu and every time screen goes to sleep, I can't get it to wake up unless I pull out battery. Anybody else having this problem on this rom?
Sent from my SPH-D700 using XDA Premium App
otee670 said:
Just insalled new syndicate frozen rom. Set cpu not compatible? Installed set cpu and every time screen goes to sleep, I can't get it to wake up unless I pull out battery. Anybody else having this problem on this rom?
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Everyone try conservative now, not on demand...
Edit::: The problem is with Voltage control 4b4, I'm going to test more before I report and start a thread, but feel free to...
Help support autism awareness,it only takes 2 seconds to help make a difference...
http://picketfenceblogs.com/vote/3616
Just changed setting to coservative and so far it seems to be working. settings is max-1300000 min-200 conservative (charging) max-1300000 min-1300000 conservative (screen off) max-400 min-400 consevative... on screen off, I tried max-200 min-200 phone stays in sleep. This what worked for me...
Sent from my SPH-D700 using XDA Premium App
Thanks to ecooce
Sent from my SPH-D700 using XDA Premium App
I know unrooted desire z devices always work at 800mhz. My device is set to 245mhz min and 1400mhz max (interactive or smartass governor). It sometimes causes my device to wake up a bit late. I wonder how long time my battery goes if I set my device at min 800 mhz and max 1200 or 1400 mhz... Did anyone try this clock speeds?
Deadly Sto(R)m said:
I know unrooted desire z devices always work at 800mhz. My device is set to 245mhz min and 1400mhz max (interactive or smartass governor). It sometimes causes my device to wake up a bit late. I wonder how long time my battery goes if I set my device at min 800 mhz and max 1200 or 1400 mhz... Did anyone try this clock speeds?
Click to expand...
Click to collapse
That's way too low of a min speed, just bump it up to the next (I think it's 386) and you should see noticable improvement.
I'd also suggest the ondemand gov; since it only ramps up to the top speed when needed, then drops it back down again, you should get a bit better battery life.
Sent from my HTC Vision using XDA App
OriginalGabriel said:
That's way too low of a min speed, just bump it up to the next (I think it's 386) and you should see noticable improvement.
I'd also suggest the ondemand gov; since it only ramps up to the top speed when needed, then drops it back down again, you should get a bit better battery life.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
i read ondemand and conservative governors are od, so using interactive or smartass are better then using others. I will try min 368 mhz but am not sure if it works...
What are you trying to accomplish by messing with the clock speed? Leave it alone at default. Performance difference is NEGLIGIBLE (bottleneck is elsewhere), and all you'll accomplish is eating the battery and burning it up with excessive heat caused by excessive clock.
dhkr234 said:
What are you trying to accomplish by messing with the clock speed? Leave it alone at default. Performance difference is NEGLIGIBLE (bottleneck is elsewhere), and all you'll accomplish is eating the battery and burning it up with excessive heat caused by excessive clock.
Click to expand...
Click to collapse
First of all, I would like to thank you for your comments.
People don't do anything to access root if they don't want to mess device. I am one of them and want to have a device which both has performance and visuality. You offered me to not to change clock speeds. But we know HTC Desire Z is scheduled to work at 800mhz everytime (default). My opinion is just to set minimum clock speed to 800 mhz or something like this. If my device was burn by this clock speed, it was already dead.
Today i tried this clock speed (min 614, max 1382) and during the day it didn't heat up. Moreover, 8 hours passed, i played NFS for about 1,5 hour, made some call and 30 percent of battery left. It seems this clockspeeds doesn't cause battery drain or i couldn't feel it...
EDIT: 13 hours passes, 16 percent battery left (I made minimum 30 minutes of call)
Hi I have an xperia play with doomkernel @ 1.7ghz stable.. Well that is until I leave it charging overnight then maybe twice a week wake up to find it stuck in a boot loop. Thing is I have a profile in CPU that underclocks when screen is off. I'm thinking its to do with temp coz after this happens the phone is hot and has that unmistakable electrical smell I remember from when I tried to OC to 2.0ghz (which froze phone until I removed batt). Thing is phone works 100% stable at 1.7ghz for hours on end when I'm actually using it, its only going into loop occassionally after being left on charge overnight (underclocked). Have searched forums but couldn't find an answer to my particular problem, any suggestions?
You answered your own question. At 1.7ghz your CPU will be creating maybe double the heat it would normally, the CPU is designed to reboot device when it is being stressed to prevent damage to the SOC. I suggest maybe your device is not as stable as you think at such a high clock speed. The fact your device is rebooting at all is a warning that you are pushing it too far and at risk of damaging it.
Sent from my R800i using Tapatalk
k
AndroHero said:
You answered your own question. At 1.7ghz your CPU will be creating maybe double the heat it would normally, the CPU is designed to reboot device when it is being stressed to prevent damage to the SOC. I suggest maybe your device is not as stable as you think at such a high clock speed. The fact your device is rebooting at all is a warning that you are pushing it too far and at risk of damaging it.
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
doesn't the processor only overclock when it is needed.?
like it will run the. lowest speed needed to complete current tasks
Sent from my R800i using Tapatalk
fma965 said:
k
doesn't the processor only overclock when it is needed.?
like it will run the. lowest speed needed to complete current tasks
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
That depends on the governor, for example the performance governor, is either at min or max, there is no inbetween, add a hot charging battery and well .....
Sent from my R800i using Tapatalk
AndroHero said:
You answered your own question. At 1.7ghz your CPU will be creating maybe double the heat it would normally, the CPU is designed to reboot device when it is being stressed to prevent damage to the SOC. I suggest maybe your device is not as stable as you think at such a high clock speed. The fact your device is rebooting at all is a warning that you are pushing it too far and at risk of damaging it.
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
The thing its not overclocked when it restarts. I have it set @ 245/768 min/max on smartass v2 governor when in the "screen off" profile, wouldnt that still apply even while charging?
Try ondemand governor...That works for me. Also it is set at 122/652.
Edit: I think "screen off" profile is different than "charging" profile..
Sent from my R800i using XDA App
ryballs said:
The thing its not overclocked when it restarts. I have it set @ 245/768 min/max on smartass v2 governor when in the "screen off" profile, wouldnt that still apply even while charging?
Click to expand...
Click to collapse
It could be something simple like underclocking too much, a lack of voltage would also cause a reboot.
Sent from my R800i using Tapatalk
Thanks everyone for your help it seems the screen off profile doesn't apply whilst charging ;p
ryballs said:
Thanks everyone for your help it seems the screen off profile doesn't apply whilst charging ;p
Click to expand...
Click to collapse
I have identical problems, how did you solve it
How safe is it to overclock my Galaxy S II to 1.78 max and 1.78 min?
If not, what combination of max and min would be most safe but still give a noticeably boost in speed.
In theory overclocking isn't that good as is adding additional strain to the CPU than it was designed to.this will cause wear and tear faster possibly shortening the life of your phone. I would set your min much lower and place it on demand. There's no need for your CPU to be running at max all the time, set it on demand do it only runs at a faster speed when it's needed to...
PS this has been covered in other threads a search would have given you an answer oppose to starting another thread.
Sent from my SGH-T989 using XDA App
Voltage kills components, not overclocking.
You can google this and research it if you would like.
I keep mine min 810 max 1782 ondemand with setcpu.
810 is more than enough(still faster than Iphone4) to hold its own without lag when you actually start to bog it down.
I think the max itll go is 1.83ghz. in reality nothing over 1.65ish really adds anything.
Sent from my SGH-T989 using XDA App
locked mine at 1.51ghz which is plenty of fast, no throttling and no lag
Setting the min up that high will kill your battery in hours. You can over clock it by setting the max up to whatever you like. Set the min lower. Then set your governor. Overclocking will wear down your cpu faster and make it run hotter. Overvolting will do the same. I would only overclock when I need it. Normally mine is set at 1.5 for max and .3-.5 for min.