I want to overclock my droid to 1200mhz but everytime I try my phone locks up almost immediatly after setting the clock speed. Is there a certain process I should go through or just a specific kernel or rom any help or advice would be greatly appreciated.
Sent from my Droid using XDA
Why do you want to do this?
I did it once in my Milestone but I think it's unecessary.
The system usually get very unstable, increase battery consumption, and reduce your phone's life.
I really don't recommend that.
1000mhz is already great, you can even try 1100.
What's your rom?
You could try /etc/init.d/10overclock . In my Milestone CM7, there is the clocks defined and vsel. Try setting 1200mhz and 70 to vsel.
Add a water cooling set up, go for 1.6Ghz. Go big or go home buddy!!!
Related
I just rooted my HTC Hero (Sprint) Stock 2.1 and now I notice my Cpu is running slow. If I install SetCpu it speeds it up right away...Upon opening SetCpu I notice my Cpu speed says 245 mhz max/min. When I the refresh it it says 480/528 but after my screen turns off and back on it slows down again and returns back to 245 mhz. I never had this problem until after I rooted the phone. Why does my phone keep reverting back to 245 mhz and slowing down after I turn my screen off? Also it seems like my Battery life has gone down drastically...
edit: I intalled overclock widget and when I open it it also says 245 mhz. When I then set it up to 528 it makes my phone run fast again. As soon as I turn my screen off and back on it automatically reverts back to 245...
fifedogg said:
I just rooted my HTC Hero (Sprint) Stock 2.1 and now I notice my Cpu is running slow. If I install SetCpu it speeds it up right away...Upon opening SetCpu I notice my Cpu speed says 245 mhz max/min. When I the refresh it it says 480/528 but after my screen turns off and back on it slows down again and returns back to 245 mhz. I never had this problem until after I rooted the phone. Why does my phone keep reverting back to 245 mhz and slowing down after I turn my screen off? Also it seems like my Battery life has gone down drastically...
edit: I intalled overclock widget and when I open it it also says 245 mhz. When I then set it up to 528 it makes my phone run fast again. As soon as I turn my screen off and back on it automatically reverts back to 245...
Click to expand...
Click to collapse
Your phone going to 245 is completely normal. It only gives your phone power when it needs it, and sitting on Setcpu screen isnt going to make it throttle up. You dont want your phone running at 528mhz at all times. It will KILL your battery. Our phones have a setting of "Ondemand", like gives the power on demand, if its not demanding a lot of power it will go back down saving battery life, CPU life and keeping temperatures down.
If you have problems with the phone running slow, i recommend checking out an overclocked kernel. You can run it at stock speeds, if you dont feel comfortable running OC. But if you want the extra power, the choice is always there.
Sounds like something to do with conserving battery by dropping the cpu speed.
-------------------------------------
Sent via the XDA Tapatalk App
Had thr same problem in the beginning way back idk how i guxed it i guess its the stock rom idk
-------------------------------------
Sent via the XDA Tapatalk App
Well on a stock rom setcpu cant do anything other then read the cpu and it will only update when it is force refresh. If you want setcpu to be able to control or change your cpu speeds this will require installing a rom that is overclock enabled. There are several located on this forum.
For some reason SetCpu was doing this. I just set it back to 480/528 and rebooted it and then uninstalled SetCpu and now everything is fine. For some reason SetCpu was the cause of this. I reinstalled to make sure and sure enough it was happenening again. I'm glad I figured it all out
Yeah, apparently you decided to create a new thread instead of utilizing the response I gave to your thread last night:
If it is not a ROM running an overclockable kernel apps like setCpu and OC widget will actually slow your phone down. If you would like to see your clock speed without this side-effect, I suggest SystemPanel.
Click to expand...
Click to collapse
For future reference, anyone not using a ROM based on Toast's kernel DO NOT install an OC program. This is the typical behavior and it is not fun to deal with because you will have to be patient waiting for the phone to start up and open the OC program to set it back and uninstall. I believe that just uninstalling and rebooting is sufficient, but am not 100%.
lineman78 said:
Yeah, apparently you decided to create a new thread instead of utilizing the response I gave to your thread last night:
Click to expand...
Click to collapse
I actually made that thread at the same time last night. I didnt know where to put it exactly...
fifedogg said:
I actually made that thread at the same time last night. I didnt know where to put it exactly...
Click to expand...
Click to collapse
Aw, this must be the one from the Dev section and got moved over here. I noticed it over there, but had already posted on the one in Q&A... So now there are 2 in Q&A.
Setcpu determines that 1704mhz can be achieved, would it be safe running the GNote at that constantly does anyone know?
Hmm...
I would say, this is depending on more than only the frequency,
if you set the voltages for 1704mhz on e.g. 1650mV u'll get a very hot phone and a hot accu... this will not be good for ur phone, if you're doing this constantly.
But if u find a good compromise between voltage and frequncy, u can do this constantly.
Also you could make profiles in SetCPU so that for example if you're gaming it will set voltage and frequency to 1704mhz and if your screen is off, it setz frequency to 800mhz.
So you have to decide if u'll want to take the risk...
I hope i could help u and sorry for my bad english,
Schnizel.
Aside from benchmarks theres no real benefit from running at 1.7ghz. Most of the time thebphone stays at 200 to 1200mhz
safe?
thought overclocking is always a risk. think nobody here will tell go do it its safe is there ?
and why would you overclock a 1,4ghz dual core in a mobile ?
Thanks, i've seen in a different thread that the voltage would need to be lowered so overheating isnt too bad.
SetCPU gives information on what frequencies are used by percentage and mine is either minimum or max so it suggested its topping out while doing stuff....
1.7ghz is too much for a constant setting.
I had my phone at 1.7 and while watching Netflix on 3G, it would get TOO HOT. and i mean TOO HOT.
I have just updated to Cyanogenmod 7.2 stable on my P990 Optimus 2x (Fido Canadian version).
When I go to the CPU settings I cannot change the min/max frequencies or select a CPU governor.
I have done some research and found kernels like Vork and FauxDS, but they are for 7.1 nightlies so I am not sure if it is a good idea to flash them.
What I am most afraid about is the possibility of getting the black screen of death while my phone sleeps (it happened once already but it stopped after I changed to a different charger and reflashed CM7.2).
The reason why I want to change the settings is that there tends to be scrolling lag (my old HTC Desire Z was faster!) and there is also a bit of lag waking up the phone (lockscreen does not appear instantly when pressing power button).
Does anyone know what is the best kernel I can flash to enable frequency/governor changes in CM7.2 stable? I would prefer not to change the ROM if possible as I am kinda nooby in comparison to the XDA community in general. Thanks for any help.
I suggest you try Etana kernel. It has the things you need. Also use CPU master to set profiles and minimum CPU frequencies. I used something like min freq 352 MHz when asleep (don't worry doesn't drain battery) and I had no lag whatsoever.
heavencanwait said:
I suggest you try Etana kernel. It has the things you need. Also use CPU master to set profiles and minimum CPU frequencies. I used something like min freq 352 MHz when asleep (don't worry doesn't drain battery) and I had no lag whatsoever.
Click to expand...
Click to collapse
Are you referring to http://forum.xda-developers.com/showthread.php?t=1427646 ?
If so, do I just flash the zip off the sd card using ClockworkMod? And what are the differences between lite and DS?
Thanks.
All right, after reading, I determined I don't need LOC/HOC/DS as I don't intend to raise the max frequency, I just want to raise min frequency.
Installed the Etana kernel via CWM and it works. I can raise minimum frequency, though I still cannot see a governor option! Any idea how to get my governor setting back?
You can use CPU master and set some profiles. It's not exactly the same as governors but it's as close as it gets and it gets the job done pretty well. As far as I remember there were two governors for O2X - powersave and performance. I've always used performance and I can't tell if there's a HUGE difference in battery usage. I guess performance utilizes higher CPU frequencies when the device is asleep and somehow scales faster to even higher frequencies when needed to. But this might be complete crap as I am not too much into how CPUs work...
And please use the THANKS button (right below the user name), it kind of forum etiquette and it keeps people motivated to help others. Thank the Etana developer too.
heavencanwait said:
You can use CPU master and set some profiles. It's not exactly the same as governors but it's as close as it gets and it gets the job done pretty well. As far as I remember there were two governors for O2X - powersave and performance. I've always used performance and I can't tell if there's a HUGE difference in battery usage. I guess performance utilizes higher CPU frequencies when the device is asleep and somehow scales faster to even higher frequencies when needed to. But this might be complete crap as I am not too much into how CPUs work...
And please use the THANKS button (right below the user name), it kind of forum etiquette and it keeps people motivated to help others. Thank the Etana developer too.
Click to expand...
Click to collapse
Thanks for letting me know, I didn't realize there was a thanks button at first haha.
Fixed!
As for now CPU Master in his profiles let's you choose governor. We have only 2. Power save nd Performance.
Sent from LG 2X using Tapatalk 2 Elite
hey i needed some help on overclocking and changing some voltages on my device!!
1.i have read threads and guides on other forums before which explain how to OC and what are governers and schedulers etc.
2. most threads on this topic are from different devices' forums
so i thought their frequencies voltages must vary as they have different CPUs and hence started a new thread!!
3. What i want to know is, what voltages should i choose at different frequencies??
or it is completely not important to set voltages??
4. Earlier i used setCPU but it doesnt stick to frequencies i set and resets default 1024 after reboot.
how do i avoid this??
Currently i am using AnTuTu CPU master PRO for doing all this
please guide me if possible provide specific values on which htc incS performs good!!!
my system details are in my signature
any help is appreciated!!
prunzzz said:
hey i needed some help on overclocking and changing some voltages on my device!!
1.i have read threads and guides on other forums before which explain how to OC and what are governers and schedulers etc.
2. most threads on this topic are from different devices' forums
so i thought their frequencies voltages must vary as they have different CPUs and hence started a new thread!!
3. What i want to know is, what voltages should i choose at different frequencies??
or it is completely not important to set voltages??
4. Earlier i used setCPU but it doesnt stick to frequencies i set and resets default 1024 after reboot.
how do i avoid this??
Currently i am using AnTuTu CPU master PRO for doing all this
please guide me if possible provide specific values on which htc incS performs good!!!
my system details are in my signature
any help is appreciated!!
Click to expand...
Click to collapse
+1
Sent from my HTC Incredible S using Tapatalk 4 Beta
I've commented on this 100 times before but I can't search on mobile. So there are a few threads out there explaining this in this forum. If you can search and find them they'll go into a little more detail than I'm about to.
OK so the OC controller you're using I'm unfamiliar with however they all do the same thing. What you should do is find out which governers your kernel supports and than use Google to figure out what their perimeters are. Generally speaking you're going to want to have different profiles set up for "screen on"and "screen off" for your basic set up. Later once you understand why you're doing you can set the governers for gaming, charging etc.
Set your screen off for around 200 min and 400 max. This will keep your phone from running high frequencies that will drain your battery while you are not using your phone. Set the governer to smart ass or on demand, read about them and see what's best for you.
Screen on set to max 1200 - 1400 if you want high performance and the low to whatever you like just not above 400 as it will not allow your CPU to idle. Set governer to smartass. You don't really need to be running above 1100 for most I stances however you will notice it is a bit peppier. While running at higher freqs you will notice your phone heating up... I have never heard of an incs over heating and frying in every case your phone will shut itself off or freeze. If you're afraid of overheating there's a profile for that too to change your freqs at certain temps.
Do NOT choose "set at boot" until you are certain that your set freqs will not hang your phone, doing this will cause your phone to freeze as soon as your ROM boots up causing a boot loop and you will have to revert to a backup to fix the situation.
As for uv'ing the premise of this is to save battery life, running at lower freqs than intended. I recommend not bothering but if you do want to try and save battery I generally suggest -10 for all values. Be aware it is very common for this to hang your phone. You have to tinker with it to get it right for your ROM.
Hope this helps any other questions just ask.
Sent from my Incredible S using xda premium
itsbeertimenow said:
I've commented on this 100 times before but I can't search on mobile. So there are a few threads out there explaining this in this forum. If you can search and find them they'll go into a little more detail than I'm about to.
OK so the OC controller you're using I'm unfamiliar with however they all do the same thing. What you should do is find out which governers your kernel supports and than use Google to figure out what their perimeters are. Generally speaking you're going to want to have different profiles set up for "screen on"and "screen off" for your basic set up. Later once you understand why you're doing you can set the governers for gaming, charging etc.
Set your screen off for around 200 min and 400 max. This will keep your phone from running high frequencies that will drain your battery while you are not using your phone. Set the governer to smart ass or on demand, read about them and see what's best for you.
Screen on set to max 1200 - 1400 if you want high performance and the low to whatever you like just not above 400 as it will not allow your CPU to idle. Set governer to smartass. You don't really need to be running above 1100 for most I stances however you will notice it is a bit peppier. While running at higher freqs you will notice your phone heating up... I have never heard of an incs over heating and frying in every case your phone will shut itself off or freeze. If you're afraid of overheating there's a profile for that too to change your freqs at certain temps.
Do NOT choose "set at boot" until you are certain that your set freqs will not hang your phone, doing this will cause your phone to freeze as soon as your ROM boots up causing a boot loop and you will have to revert to a backup to fix the situation.
As for uv'ing the premise of this is to save battery life, running at lower freqs than intended. I recommend not bothering but if you do want to try and save battery I generally suggest -10 for all values. Be aware it is very common for this to hang your phone. You have to tinker with it to get it right for your ROM.
Hope this helps any other questions just ask.
Sent from my Incredible S using xda premium
Click to expand...
Click to collapse
thanks a lot
Hi,
first, I want to apologize for my bad english.
I have a problem with the clockingspeed of my HTC One.
I was impressed by how bad the battery life of the One is.
I found out, that the CPU is always clocking at 1,7Ghz, both values (Min AND Max) are set to 1.7 Ghz.
If I turn on the battery-safe option, it clocks at 1Ghz, but again on both values.
So, I have downloaded some CPU apps, which should let me change the clocking speed of the CPU.
Well, it works, but if I turn on "Set on boot", and reboot, the values are gone.
I thought, this would be caused by the stock ROM, so I have flashed the "InsertCoin" ROM, but no changes.
Has someone the same problem, or does someone has a solution for me?
regards.
The clock speed is dynamically controlled. When the phone is not in use, it should reduce the clock speed.
It sounds like you have an app that is preventing it from sleeping.
Install betterbatterystats and look for partial wakelocks. Feel free to leave a screenshot here.
Hi,
even if there is an app which would prevent my phone from clocking down, the MIN-value should be at 300/400mhz, and not be the same as the max-value ..
regards.
No idea..?
what hes saying is theres a rogue app mostly likely in the background thats pushing your phone that it thinks it should ramp up the speed of your phone. so even if you have it set to 384/1.7 the phone is detecting "oh **** *so and so* app is beastly bump the speed to max 1.7. bad analogy but you get the idea. i would start by wiping the phone install a brand new rom and DONT install anything just the mhz reader. then check. if your on a fully clean flash and still holding at max value all the time. then next is to check the CPU governor. it may have been set to performance at some point "accidentally" the performance governor forces the phone to hold at max speed. mostly only used for synthetic benchmarks.
Nope nope nope.
Nope.
I just had to S-Off my phone ..