I have htc wildfire s ...i hav rooted ...i want to overclock it 806 mhz.....pls tell me the procedure to overclock..
I am using htc wildfire rom ..pls help
First you need a kernel that supports overclocking.
If you using a stock Rom then look for the kernel that matches your Android version eg. 2.3.3 or 2.3.5 you will find them in the development section posted by Jikantaru
If you install a custom Rom then it will most likely have an overclockable kernel baked in.
To change clock settings I recommend 'no frills CPU' search it in the market or you could use set CPU.
Once you install one of the above apps then change the min and max sliders to the desired frequency.
if we over clock it much does it effect the speed or hardware of the phone?
Your phone may hang.
There is SetCPU for XDA members:
http://forum.xda-developers.com/showthread.php?t=505419
RRRb50 said:
if we over clock it much does it effect the speed or hardware of the phone?
Click to expand...
Click to collapse
You will definitely get better performance and it shouldn't cause you any problems.
Use no frills CPU I find its better than set CPU, when restarting your phone set CPU doesn't keep your overclock settings even though its set on boot.
As for the govonor settings I would choose smartass2 and noop for the scheduler.
I would keep the minimum frequency on 245MHz it can go lower but it could cause some issues (lag and slow unlocking and waking)
Note: not all cpu's are capable of running at the same speed, I'm lucky mine can run at 806MHz but some people have issues.
If you notice any problems like freezing etc, then drop the speed to a lower frequency until you find the sweet spot for your CPU.
I had mine at 806 MHz with no problems
Sent from my NookColor using xda premium
so it wont cause hardware problems only lagging and other stuff
RRRb50 said:
so it wont cause hardware problems only lagging and other stuff
Click to expand...
Click to collapse
Should be fine mate.
But remember if in the very unlikely event something does go wrong I wont be held responsible.
youll have to need an overclock kernel for that. (and a rom which supports one)
go for dust kernel or cake kernel! These two are well known for high end kernels!
Related
Hello there,
I've been flashing kernels since I was in LeeDroid Froyo and got no problems. However since I switched to GB based roms such as RCMix3D and TB Fusion, my phone always freezes when I try setting Kernel-Lee-V3.1.1-2.6.35.13-CALLREC or MDJs v19 to maximum overclock so I have no choice to but to stay on stock kernel. I have no ext3/ext4 partition on my SD card in case you ask.
Current ROM: TB Fusion 1.1.2
Radio: 12.54.60.25U_26.09.04.11_M2
Any idea what should I do to solve this issue?
golokipok said:
Hello there,
I've been flashing kernels since I was in LeeDroid Froyo and got no problems. However since I switched to GB based roms such as RCMix3D and TB Fusion, my phone always freezes when I try setting Kernel-Lee-V3.1.1-2.6.35.13-CALLREC or MDJs v19 to maximum overclock
Click to expand...
Click to collapse
uoooo this is sooo dangerous for your handset... u can "smoke" it...
Any idea what should I do to solve this issue?
Click to expand...
Click to collapse
yes, your handset freezes because the overclock that u do its too high... underclock it at 1200-1400mhz & try...
and configure SET CPU features... like the standby status, etc....but do it with common sense....
think about that DHD proccessor goes by default at 1gz, really when we overclock the processor we are putting in danger the security of our device
SERGI.3210 said:
uoooo this is sooo dangerous for your handset... u can "smoke" it...
yes, your handset freezes because the overclock that u do its too high... underclock it at 1200-1400mhz & try...
and configure SET CPU features... like the standby status, etc....but do it with common sense....
think about that DHD proccessor goes by default at 1gz, really when we overclock the processor we are putting in danger the security of our device
Click to expand...
Click to collapse
Haha! I know that overclocking is quite dangerous. Back on the froyo days, my phone is quite stable around 1.8ghz so I'm just wondering why is this happening (maybe my phone's processor is starting to fry up? ). Is there any effect if I'm using smartass profile on those kernels I've mentioned?
golokipok said:
Haha! I know that overclocking is quite dangerous. Back on the froyo days, my phone is quite stable around 1.8ghz so I'm just wondering why is this happening (maybe my phone's processor is starting to fry up? ).
i hope that the processor works or not works (don´t crashes a little bit...)
but the reason of your freezes maybe (almost sure) because froyo & gingerbread don´t works at the same form, and gingerbread need more resources & stability for to work correct... don´t forget that the kernel manages the hardware...
if u force it......... u know what can happen...
golokipok said:
there any effect if I'm using smartass profile on those kernels I've mentioned?
Click to expand...
Click to collapse
it´s possible, take this explanation, read and judge by yourself what´s the better cpu governor...
smartass (Best explanation i've found paraphrases to: based on interactive, but better.)
----
ondemand
Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see "up threshold" in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed. - SetCPU website
conservative
Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery. - SetCPU website
performance
Available in most kernels. It will keep the CPU running at the "max" set value at all times. This is a bit more efficient than simply setting "max" and "min" to the same value and using ondemand because the system will not waste resources scanning for the CPU load. This governor is recommended for stable benchmarking. - SetCPU website
powersave
Available in some kernels. It will keep the CPU running at the "min" set value at all times. - SetCPU website
userspace
A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor. - SetCPU website
Interactive
The 'interactive' governor has a different approach. Instead of sampling the cpu
at a specified rate, the governor will scale the cpu frequency up when coming
out of idle. When the cpu comes out of idle, a timer is configured to fire
within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer
fires then we assume the cpu is underpowered and ramp to MAX speed.
If the cpu was not 100% busy, then the governor evaluates the cpu load over the
last 'min_sample_rate' (default 50000 uS) to determine the cpu speed to ramp down
Click to expand...
Click to collapse
Thanks for the info
SERGI.3210 said:
because froyo & gingerbread don´t works at the same form, and gingerbread need more resources & stability for to work correct... don´t forget that the kernel manages the hardware...
if u force it......... u know what can happen...
Click to expand...
Click to collapse
You have mentioned about those "resources", is there any special measure that I need to do or what? I'm using the smartass profile on those kernels but still *sigh*
Anyway, I've observed on your sig that yours is overclocked @ 1.8ghz even though you're running GB, me envy
golokipok said:
have mentioned about those "resources", is there any special measure that I need to do or what? I'm using the smartass profile on those kernels but still *sigh*
Click to expand...
Click to collapse
you only should do a good over/underclock & set the correct cpu governor for your daily use....
well, you know ho is @MDeeJaay? the developer of MDJ kernels and roms...
he explained smartass with this words:
SMARTASS GOVERNOR - is based on the concept of the interactive governor.
I have always agreed that in theory the way interactive works - by taking over the idle loop - is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the "old" minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Smartass will also cap the max frequency when sleeping to 245Mhz (or if your min frequency is higher than 245 - why?! - it will cap it to your min frequency). Lets take for example the 998/245 kernel, it will sleep at 245.
golokipok said:
, I've observed on your sig that yours is overclocked @ 1.8ghz even though you're running GB, me envy
Click to expand...
Click to collapse
no, no buddy... i only show the max speed nothing more... i set my cpu concretly like this;
CPU GOVERNOR:interactive
MAX SPEED:1113 MHZ
MIN SPEED:245 MHZ
PROFILE: screen off; 245 MHZ max.
245 MHZ min.
in adition i´m going to modify my syg LOL
haha..thanks again. I'm gonna try playing with the frequencies to see which will suit me
i hope someone can make a stable 1.8ghz kernel without the freeze
IT´S POSSIBLE but i don´t want to try it LOL
i love a lot my DHD
What are the safe/stable clockspeeds for underclocking and overclocking my Desire Z? Also, what app do I use? Like, I don't mind paying for the app (as long as it's not too expensive)
Sent from my HTC Vision using XDA App
SetCPU can be used to overclock if you're rooted. Depending on the ROM and Kernel combination, overclocking to about 1.3ghz is usually safe. Some go up to 1.5ghz or even 1.8ghz, but are often quite unstable depending on other configurations you have in your ROM.
As far as underclocking goes, some custom kernels clock all the way down to 122mhz, I've been using a streamline5 kernel on CM7 (which offers 122mhz min) and haven't had any ill effects with this.
I have the Virtuous Sense ROM (with it's default kernel, although it does have other kernels which can give other cpu speeds), right now but might try out another ROM soon (maybe) do you know what's the min and safe max for this ROM?
Also, can I just set a particular clock speed (e.g. 500MHz) and it should be ok or is there any stability difference between say 500MHz and 505MHz? Just curious. I looked at SetCPU and it looks like a good one. Also, if the clock speed I set makes things go wrong, can I revert it or can I get stuck with it and need to do a wipe?
Sent from my HTC Vision using XDA App
zaghy2zy said:
I have the Virtuous Sense ROM (with it's default kernel, although it does have other kernels which can give other cpu speeds), right now but might try out another ROM soon (maybe) do you know what's the min and safe max for this ROM?
Also, can I just set a particular clock speed (e.g. 500MHz) and it should be ok or is there any stability difference between say 500MHz and 505MHz? Just curious. I looked at SetCPU and it looks like a good one. Also, if the clock speed I set makes things go wrong, can I revert it or can I get stuck with it and need to do a wipe?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
No, there's no need to set a particular clock speed. Just whatever works for you. I wouldn't recommend going under 800mhz, as the phone will really really bog down even with normal use.
I haven't used that particular ROM, but I'm assuming anywhere around 1.3ghz should be safe on the upper limit. Like I said before, anything above that might start to cause issues. You might also want to consider the battery life implications of severe overclocking.
You can change the clock speed any time you want. If you're having wakeup or heat or any other issues just go back to SetCPU and change the max clock speed again. You can also use profiles in SetCPU to change the clock speed when the phone is overheating, or when the screen is off, or when the battery gets to a certain %. There are tons of posts detailing how others have setup their SetCPU profiles.
One last note, don't forget to check the box for "Set on Boot" in SetCPU, this way your changes aren't undone on reboot.
Thank, I think I got everything I need to know in your last reply
I'm on CM7, with the CM7 kernel, and clocked in at 1.5GHz, and have no problems, and the rom is super fast. And I use SetCPU.
Hi folks!
I´ve installed the latest LeeDroid with full wipe and got the problem, that the display often don´t wake up from standby. The touchscreen works, but it won´t wake up.
Then i tried to install the latest radio version and flashed/wiped again. Still the same problem.
So i tried to flash CyanogenMod7 with GAPPS, but the same error is still available. Never had that problem with original rom.
What should i try next?
What radio do you have/flashed.
Maybe try a different kernel.
Now i´ve installed radio: 5.17.05.23
Before i had installed 5.17.05.08. I got the problems with both radio versions.
Version of kernel is 2.6.37.6-cyanogenmod-g37556d9 [email protected] #1
Where can i download suitable kernel versions?
AOSP Kernels - in the developement section.
http://forum.xda-developers.com/showpost.php?p=12350779&postcount=3
Are you using any program to control CPU? You can try SetCPU and use a screen-off profile.
I didn´t use this tools before, but now i´ve installed Set CPU for root users.
I´m now in the menu and see the the profile screen-off, but i don´t know what i should configure there?! What does that tool with screen-off do?
Update:
Made a profile with screen off with 245 max/min. Enabled it!
Anything else to do?
Which kernel you would prefer for my desire gsm?
Okay, first of all - set the main frequencies.
Depends on ROM, I have 384-998 Ondemand.
Then go to profiles, click enable.
Click add profile, then select:
Profile: Screen OFF
Max: 245
Min: 128
Scaling: Ondemand (but you can play around with that)
Priority: 100
Maybe, you must adjust higher frequencies, but play around with it a little.
Profile: Screen OFF
Max: 245
Min: 245 (minimum is 245, i can´t configure it to 128)
The display bug is still available!
Set max to 368. Seems as if your desire can't handle 245/245.
Swyped from Oxygen with Transparent XDA App
Update!
Now i wiped and installed CyanogenMod7 RC1 again with Gapps. I didn´t install any other Apps, so i can be shure, that no app cause this display problem.
I can´t reproduce the problem again. I need more time for testing, but at this time it seems that there is a problem with any installed app.
Set CPU is disabled!
Update:
Problem is here again!
Now i´m testing the suggestion of Mr. MatDrOiD!
Which governor do you use?
Swyped from Oxygen with Transparent XDA App
i use "Set CPU".
It feels like, the chance my Display wake up from standby is now bit higher and better, but the problem still exists.
Heavymaxx said:
i use "Set CPU".
It feels like, the chance my Display wake up from standby is now bit higher and better, but the problem still exists.
Click to expand...
Click to collapse
No, i mean the governor, not the software. The governors are the controllers for the regulation of the cpu frequencies (how fast it increases and decreases). Most available governors are "ondemand", "performance", "powersave", "interactive" and "smartass". So what governor do you use?
According to your experiences, setcpu is probably the crux of matter.
I can't be 100% I had the same issue as you, but when I used to use CM7 or Redux I did have problems with black screens and unresponsive touchscreen (in that order respectively). Didn't happen on Sense at all.
But now I've been on Oxygen for close to two weeks and I haven't had any of those symptoms since. I think all the hacks they include in CM7 and other custom ROMS is to blame. Perhaps give Oxygen a try to rule it out, as it's an almost pure AOSP ROM. Don't run Setcpu either on it.
MatDrOiD said:
No, i mean the governor, not the software. The governors are the controllers for the regulation of the cpu frequencies (how fast it increases and decreases). Most available governors are "ondemand", "performance", "powersave", "interactive" and "smartass". So what governor do you use?
According to your experiences, setcpu is probably the crux of matter.
Click to expand...
Click to collapse
Ah ok! I use "ondemand".
I would not use SetCPU if i would have no problems. I´m testing around, BECAUSE i have problems.
@Salty: Thanks for the fish! I got the same problem on LeeDroid too. IDC what Rom i use. It should be up to date and should support App2SD+, i need more internal memory, that´s all.
Amoled Display got changed - everything works fine!
Just wanted to finish this thread with a solution!
Thanx!
**CLOSED**
My phone freezes just as or very soon after i choose to overclock in cm7 settings.
My last WFS was really loving the O/C.
Has anyone any solution. Many thanks
Edit: I can use userspace govenor and go to 806mhz but dont notice any difference in speed of hone. Tried cpu spy
Perhaps it's your kernel. Which kernel do you use? (go to Settings, About Phone, Software, More, Kernel version)
Also, what apps do you use to do the overclock?
It's likely your phone. Not all chips are made the same. Set your governor to performance and slowly ramp her up till it freezes. Then take a step down and leave it.
Sent from my HTC_A510c
BigChillin said:
It's likely your phone. Not all chips are made the same. Set your governor to performance and slowly ramp her up till it freezes. Then take a step down and leave it.
Click to expand...
Click to collapse
BigChillin's right try what he said.
My setting are 120/806 without any problems. This must be you phone...
Hello, i wanna share my experience undervolting.
For people who dont know what undervolting is, its the power or energy that the battery send to the CPU with determinate clock speed.
For example:
384 Mhz is the lowest frequency of our CPU, it has a 800mv volt in the stock ROM with stock kernel.
So in theory, the battery send 800mv to the CPU when it runs at 384 Mhz.
The effect of undervolt the CPU is bassically get more battery life and at the same time reduce the temperature of the phone.Less energy send less battery used and less hot phone in our hands.
How to Undervolt
Im running Stock ROM with Ruby Kernel stable.
For undervolt you need a kernel that support it, you can do it in all rom if the kernel support that.
If you want to Undervolt, i recommend you to use Trickster MOD.
You can Undervolt maybe -50mv all frequencies and see how it goes. Some people can even in best cases undervolt -200 mv. But you need patience to test slowly.
DONT TICK SET AT BOOT IF NOT TESTED.
That why you cant:
For example if you undervolt -100mv and if not stable, and you have set at boot ticked, it will freeze the screen and after reboot it will happen again.
After you set the mv for undervolt, download from play store CPU stability test and run it.
It will test all CPU frequencies to see if it is stable.
If you dont get any SoD, congratulations its stable.
My undervolt settings are -100 or in some cases -75 mv and very stable. My battery temp is 30 C°.
Thank you very much
Sent from my LG-E975 using XDA Premium 4 mobile app
What is needed to undervolt?
Thanks for the info. What are your battery stats after undervolting? How does it suffer other operations of our mobile like browsing or gaming etc ?
Sent from my LG-E975 using xda app-developers app
You need to first make a backup, install a custom kernel, install trickster mod, and from there apply what this discussion is talking about. Good luck!
Sent from my Nexus 5 using xda app-developers app
lfuentes said:
What is needed to undervolt?
Click to expand...
Click to collapse
Bootloader unlocked with freegee and some kernel for your rom that supports undervolt.
nch26 said:
Bootloader unlocked with freegee and some kernel for your rom that supports undervolt.
Click to expand...
Click to collapse
And after that? Some specific app?
lfuentes said:
Some specific app?
Click to expand...
Click to collapse
Depends on the kernel. I am using Trickster Mod with Viper ZVC kernel. There are other control apps available -- some of them are kernel-specific, some are more universal (Kernel Tuner, Android Tuner, System Tuner, etc.). Look in your kernel's thread -- the developer usually tells which control app(s) to use with it.
nch26 said:
Hello, i wanna share my experience undervolting.
For people who dont know what undervolting is, its the power or energy that the battery send to the CPU with determinate clock speed.
For example:
384 Mhz is the lowest frequency of our CPU, it has a 800mv volt in the stock ROM with stock kernel.
So in theory, the battery send 800mv to the CPU when it runs at 384 Mhz.
The effect of undervolt the CPU is bassically get more battery life and at the same time reduce the temperature of the phone.Less energy send less battery used and less hot phone in our hands.
How to Undervolt
Im running Stock ROM with Ruby Kernel stable.
For undervolt you need a kernel that support it, you can do it in all rom if the kernel support that.
If you want to Undervolt, i recommend you to use Trickster MOD.
You can Undervolt maybe -50mv all frequencies and see how it goes. Some people can even in best cases undervolt -200 mv. But you need patience to test slowly.
DONT TICK SET AT BOOT IF NOT TESTED.
That why you cant:
For example if you undervolt -100mv and if not stable, and you have set at boot ticked, it will freeze the screen and after reboot it will happen again.
After you set the mv for undervolt, download from play store CPU stability test and run it.
It will test all CPU frequencies to see if it is stable.
If you dont get any SoD, congratulations its stable.
My undervolt settings are -100 or in some cases -75 mv and very stable. My battery temp is 30 C°.
Click to expand...
Click to collapse
Thank you, I'm using AK kernel with UKM and Synapse app from google playstore. Using E-975 (intl.). Can you suggest if I should change the global setting or the individual settings for frequencies ? I had recently (soft) bricked my phone by running benchmark at ~1900mhz CPU and 487mhz GPU (like a villain, I know. Re-connected battery to save it... phew..). I'm really cautious now and I just want it to be less hot and save some battery, that's all. Any guidance would be really appreciated... thanks
Claureid said:
Thank you, I'm using AK kernel with UKM and Synapse app from google playstore. Using E-975 (intl.). Can you suggest if I should change the global setting or the individual settings for frequencies ? I had recently (soft) bricked my phone by running benchmark at ~1900mhz CPU and 487mhz GPU (like a villain, I know. Re-connected battery to save it... phew..). I'm really cautious now and I just want it to be less hot and save some battery, that's all. Any guidance would be really appreciated... thanks
Click to expand...
Click to collapse
I dont have anymore this phone because some people stole my phone like 1 year ago. Sorry.
Oh okay, sad loss....