Develop Bugs

[Q] Safe Overclock

What is the highest MHz that i can go up to without risking my phone too much? My ROM and Kernal lets me go up to 1920 but thats probably not the best idea.

Scottymeuk said:
What is the highest MHz that i can go up to without risking my phone too much? My ROM and Kernal lets me go up to 1920 but thats probably not the best idea.
Click to expand...
Click to collapse
you have reason.... NO GOOD IDEA lol
in a kernel thread (a lot of time ago...) i was read... that was not recomended overclock avobe of 1600 Mhz... And atention important!!! don´t underclock down 170Mhz more or less (because can be the devece cannot exit from standby mode when you unlock the screen....) i cannot remember what was be the thread but i really believe that there is not a concret limit for overclock....
sure that it´s not good any tipe of overclock for improve the performance...
but i have a hero overclocked at 714 mhz (factory stock at 525 mhz) since 2009 and NO PROBLEM never,,,,
and my DHD overclocked at 1200 mhz (with a quality kernel in mode smartass)
and underclocked at 245 mhz more or less and no problem....
judge by your self but use the common sense... cheeeers

At the moment i have it on smartass to 1459 max and 230 min and it seems fine. Do i just judge it on the CPU temp, and if it stays quite low (Around 30c) then im fine?

Scottymeuk said:
At the moment i have it on smartass to 1459 max and 230 min and it seems fine. Do i just judge it on the CPU temp, and if it stays quite low (Around 30c) then im fine?
Click to expand...
Click to collapse
it depends buddy...
maybe its well.... the normal temp. of my batt. in use is 33-35º (but here in spain we are now at 30º !)
but my question is... are you really sure about its neccesary overclock our DHD?
I think that still DHD supports well all kinds of software with 1 GHZ of power...
maybe for a future thinks....or for gamming but always u can overclock for use a game and then return to 1ghz...
it´s only a suggestion... maybe another OP uses the processor of different mode...

The overclocking limit differs from device to device, so there is no general answer.
As a rule of thumb, when you start getting random revolts or crashes, you have gone too far.
If you want a more professional way, just slowly turn the clock of your CPU up and run a stress test after each time. It takes a bit more time but should get you pretty good results.

How long should i leave the stress test running for?
The reason i want to overclock it a little is that it just runs a bit more smoothly with it over clocked a bit. Just everything in general seems a bit better to use, its not really for gaming etc.

overclocking dhd

I have recently rooted my dhd and currently running CM7. Using the cpu setting within the performance menu I am wondering what peoples thoughts are on a noticeable but safe increase of cpu speed. its set as 1017MHz which i believe is default. I am told I can run anything up to 1500 safely. can anyone confirm this and also tell me what kind of result (performance and battery life) i should expect.
thanks

Well, I use Android Revolution HD (a sense rom, meaning heavy UI!) and i overclock to about 1.3GHz. In terms of battery life when it's awake, it seems a drain a teeny bit more readily, but I've never had a freeze on sense (quite rare)
On stock it underclocks to let the processor max at around 400MHz when the screens off, so that helps to really save a lot of battery on standby. On CM, I'd expect it'd feel more or less the same in terms of performance after you hit 1.2/1.3GHz

hmohammed43 said:
Well, I use Android Revolution HD (a sense rom, meaning heavy UI!) and i overclock to about 1.3GHz. In terms of battery life when it's awake, it seems a drain a teeny bit more readily, but I've never had a freeze on sense (quite rare)
On stock it underclocks to let the processor max at around 400MHz when the screens off, so that helps to really save a lot of battery on standby. On CM, I'd expect it'd feel more or less the same in terms of performance after you hit 1.2/1.3GHz
Click to expand...
Click to collapse
thanks for the reply mate. going to try out revolution HD soon i think. have you overclocked using a third party app or is there one built into that rom?
also im a little confused by the governors. 'on demand' is the default governor. Does that mean it will only use the max selected cpu speed when necessary? would you recommend using a difference setting?
cheers

rhodri11 said:
thanks for the reply mate. going to try out revolution HD soon i think. have you overclocked using a third party app or is there one built into that rom?
also im a little confused by the governors. 'on demand' is the default governor. Does that mean it will only use the max selected cpu speed when necessary? would you recommend using a difference setting?
cheers
Click to expand...
Click to collapse
The CPU is managed by the ROM itself. You can tweak it yourself by using setCPU (or similar), but I can advise you not to. Can't help you with the governors buddy, since I dunno what it is
Cheers

darude0306 said:
The CPU is managed by the ROM itself. You can tweak it yourself by using setCPU (or similar), but I can advise you not to. Can't help you with the governors buddy, since I dunno what it is
Cheers
Click to expand...
Click to collapse
nice one dude

I'm running cm7 and I'm overclocked to 1.5 ghz. It's been totally fine for months.
Sent from my Motorola Startac running Atari 2600 software!

rhodri11 said:
thanks for the reply mate. going to try out revolution HD soon i think. have you overclocked using a third party app or is there one built into that rom?
also im a little confused by the governors. 'on demand' is the default governor. Does that mean it will only use the max selected cpu speed when necessary? would you recommend using a difference setting?
cheers
Click to expand...
Click to collapse
Lucky you picked a linuxhead!
The system itself has a daemon (background process built into the system) that handles overclocking. It's all explained on the page and also on this thread:
http://forum.xda-developers.com/showpost.php?p=14638641&postcount=34279
You can use another app (like SetCPU) but the daemon usually handles screen off's quicker. The governors basically determine how the processor frequency is changed. I'll explain the common ones:
Performance - Runs at highest speed, so if you have a range of 200 to 1.3G, it'll stay at 1.3G all the time, not usually the best
Ondemand - The universal default for phone overclocking, it only changes the speed up after a certain percentage of the CPU is used, and it switches on the fly, so if the CPU is used too much at 400MHz, it'll ramp it up to maybe 600 or 800, and if it's still overused, it'll put it up to maybe 1 or 1.2G
Conservative - This is like ondemand, except it makes the changes more gradual. It can give noticable lags in the foreground at times, so this is mainly used when the phone is asleep (screen off)
Smartass - This governor is like ondemand, except it'll less readily switch frequencies to higher values when it detects the screen off. This isn't really used because the overclocking daemons take into account the phone being awake or not
Basically, there isn't really a need to change governors, only really frequencies if anything. The thread, however, does tell you how to change governors.

Im using latest LeeDroid GB 3.2.1 and to be honest with the work he's done with the Kernal (3.1.8BFS) I have found that the ROM is a lot MORE responsive without me overclocking the CPU.
Im not really sure how it all works, but I guess doing this on different ROMS has its own different out comes.

overclocking has me confused too, is there really that much of a benefit in it? how much will i gain from it?

toby_lerone said:
overclocking has me confused too, is there really that much of a benefit in it? how much will i gain from it?
Click to expand...
Click to collapse
There is a benefit when you use certain apps, or even sense itself. For example, I've never had sense ui freeze, or go slow. The under clocking helps to improve the rubbish battery life when your phone is asleep.
In terms of measuring the gain, I have no idea. Really, I'd think you could use a process heavy app, or benchmarking app and see.
There's also loads of guides on overclocking to help out! (that's how I got the hang of it! )
Sent from my Desire HD using XDA Premium App

For the need on OC, it depends on the kind of apps u're using. If u're happy w a non OC DHD, its totally up to u.
But for the UC, it works as a terrific battery saver, mich better/effective than other battery saver soln on market

The safe range depends on the DHD as the manufacturing changed even though same part, i'm OC 1.5GHz "On Demand" profile and under clock 245MHz on screen off "Power Save" profile.
Getting approx a day usage on Lee 2.1.

[Q] Original ROM's CPU freq scaling range

Hi, just wanted to know what is original HTC's ROM CPU scaling range and what is its CPU governor. My guess is 245-528, ondemand - is that correct?

Sorry, I don't know myself, but I'd like to know this too! I've just installed JokerDroid on mine, and I want to set it to stock frequencies so I can improve the battery life.

I'm using 352-691 ondemand, but I think 748 is ok too.

I think the min is 352MHz. But again, I am not so sure. (I arrived at this value when I was on the Stock ROM and used Android System Info which shows the various CPU frequencies and the time periods they operate on that frequency)

zigee said:
I'm using 352-691 ondemand, but I think 748 is ok too.
Click to expand...
Click to collapse
Isn't the max. for this device "528"

xXxeXtreme said:
Isn't the max. for this device "528"
Click to expand...
Click to collapse
Custom ROM's (Or, more appropriately - Custom Kernels) allow you to set a CPU Speed upto 768MHz.
BUT - The performance increase is not as great as the speed increase shows. So, if you do overclock, don't keep huge expectations.

zigee said:
I'm using 352-691 ondemand, but I think 748 is ok too.
Click to expand...
Click to collapse
I am running on 710 max, some people run on 768 max. But apparantly it is phone related because some people can perfectly run on 768 whilst I read a few days ago from a person here whose wildfire started force closing things around 710 or one higher or so.
Try a bit yourself which works for you. There are benchmarks that you can let run to see how often an error will occur approximately I have no link myself but I know a bud of mine did that to try how high he could go

At 691, some apps force closed, so I'm back to 595. It was stable for me.

gues that the 352MHz is the stock minimum then. There should be a noticable battery life increase when 122MHz is my current IDLE clock huh?
Now Iam running 122-710MHz on stock HTC ROM, very stable. If I set the frequency above 710MHz the scaling become unstable uner LOAD sometimes and dropping to 480MHz.
Using jacob kernel v4.

overclocking - my questions for understanding

So I thought about overclocking. I never overclocked any CPU by now. No PC cpus, no mobile cpus
I just always read: Do not overclock! More heat production, more energy costing and of course: probably decrease device life-time and may damage the phone.
On the opposite there is: more cpu-power. WFS seems to be able to get OC'd to 800 MHz (which is 200 above standard and only 200 below Desire)
So, what can you tell me about the above conclusions?
Next question: Do I need overclocking, or is it just to win a p.... length comparing ?
I'm on stock European rom 2.3.5. I know I need custom kernel. which one I could use, how to flash? Which apps do I need furthermore?

theq86 said:
So I thought about overclocking. I never overclocked any CPU by now. No PC cpus, no mobile cpus
I just always read: Do not overclock! More heat production, more energy costing and of course: probably decrease device life-time and may damage the phone.
On the opposite there is: more cpu-power. WFS seems to be able to get OC'd to 800 MHz (which is 200 above standard and only 200 below Desire)
So, what can you tell me about the above conclusions?
Next question: Do I need overclocking, or is it just to win a p.... length comparing ?
I'm on stock European rom 2.3.5. I know I need custom kernel. which one I could use, how to flash? Which apps do I need furthermore?
Click to expand...
Click to collapse
No it's not just for a pissing contest.
Jikantaru's new kernel will allow you to set your clock to vary between 120 Mhz and 806 Mhz although 787 Mhz tends to work for those unlucky enough to have phones that freeze up at 806 Mhz.
The CPU doesn't run balls out all the time. It speedsteps as needed to save battery power.
You flash the kernel that you download to your SD card through CWM Recovery's Install zip from SD card feature.
Reboot and you now have Ext4 support for Link2SD, etc, and overclocking capabilities as well as a host of other kernel tweaks to handle memory management, etc.
As far as programs to set the clock with? SetCPU, Rom Toolbox, Nofrills CPU, Antutu CPU, etc.
I would choose "Smartass" as your governor and 120 and 806 as your min and max CPU settings and choose to set it at boot.
That's just my preference.
I personally bought Rom Toolbox Pro and manage the CPU settings through it.
It's got a host of other cool features all in one place and jrummy updates it very often with new fixes, features, etc.

thanks for that.
so what about damaging the cpu or the device? is there nothing to worry about?
and what is a govener? do I need it in addition to setcpu ?

theq86 said:
thanks for that.
so what about damaging the cpu or the device? is there nothing to worry about?
and what is a govener? do I need it in addition to setcpu ?
Click to expand...
Click to collapse
The governor is the method by which the phone plans it's stepping up and down of frequencies. Smartass is a tried and true good combination of power savings and stepping to the plate with high clock frequencies when needed.
No you won't need anything extra. It's one of the settings in any of those programs.

Sorry for asking again:
It won't damage my device or burn the cpu as overclocking a normal PC CPU would do?
edit: using nofrills now. Seems to work.

theq86 said:
Sorry for asking again:
It won't damage my device or burn the cpu as overclocking a normal PC CPU would do?
edit: using nofrills now. Seems to work.
Click to expand...
Click to collapse
Overclocking comes with no promises man. Mine's been overclocked since August so that's all I have to go on.

There is always a danger or risk when overclocking. The manufacturers determine the safe frequencies, temperatures, voltage, etc. based on scientific experiments in different environments. However, with that said, obviously, they are not infallable either. The best way to determine your risk is to think about what conditions you'll be using it in the most and what kind of stress it'll put on your phone's internals. Do some research and see what other people have problems with and under what kind of stress was the phone. Use common sense. Things like raising voltage and frequencies raise the temperature of the phone's internals, also. So, in turn, do you also have a case on the device that retains heat? Do you live in an humid/dry or warm/cold area? Do you do a lot of multitasking? Are you constantly on it? Hope this helps.
Sent from my myTouch_4G_Slide using XDA App

[Q] franco.Kernel v141 Stock Voltages

So, I know we all have different phones, and after looking at a review of some voltages to try, I changed all the stock voltages to the ones I saw and saved them as default (don't ask me why, I do not know myself). Since this, I set my phone to hotplug and the phone has had multiple Sleep of Death cases. I think it has to do with the voltage but it could just be my phone not liking hotplug because it stops if I turn off hotplug. Or hell it could be that both together are causing it. So I was wondering could someone provide me with stock voltages at 384, 729, 1036, 1228 and 1344 mhz. Or better yet if you could provide me with the best voltages that help save a little battery life. Thank You! (Also I have been looking but have not found the stock voltage for the numbers I listed above)

stock voltages are 1025, 1203, 1317, 1380. 1350mhz is not a stock clock speed so theres no stock voltages. you can try these undervolt values, they are pretty conservative 850, 950, 1050, 1175 and 1250. remember to do nandroid backup first.
undervolt will not really gain you any noticeable difference in battery life, the cpu uses relatively little power to begin with so reducing it by a few hundred mv is not going to make a different with normal use. If you want to try it out just start from stock and go down 25-50mv at a time and test it with some games or stress test.

neotekz said:
stock voltages are 1025, 1203, 1317, 1380. 1350mhz is not a stock clock speed so theres no stock voltages. you can try these undervolt values, they are pretty conservative 850, 950, 1050, 1175 and 1250. remember to do nandroid backup first.
undervolt will not really gain you any noticeable difference in battery life, the cpu uses relatively little power to begin with so reducing it by a few hundred mv is not going to make a different with normal use. If you want to try it out just start from stock and go down 25-50mv at a time and test it with some games or stress test.
Click to expand...
Click to collapse
Thank you. If they really don't make a difference I will leave them be at stock. Any good value for 1350? Or should I just stick with 1250mV? Just really trying to get 2 days out of the phone, but I assume I cannot complain since I am already getting 4h of screen time with normal use on the 2000mah battery. I will look around here some more and see if I can find any more useful tips on better battery life. Thanks again!

neotekz said:
stock voltages are 1025, 1203, 1317, 1380. 1350mhz is not a stock clock speed so theres no stock voltages. you can try these undervolt values, they are pretty conservative 850, 950, 1050, 1175 and 1250. remember to do nandroid backup first.
undervolt will not really gain you any noticeable difference in battery life, the cpu uses relatively little power to begin with so reducing it by a few hundred mv is not going to make a different with normal use. If you want to try it out just start from stock and go down 25-50mv at a time and test it with some games or stress test.
Click to expand...
Click to collapse
I wish I would have read this post a few days ago prior to changing my voltage settings also. Only to learn that I wasn't doing my GNex a significant favor.

falconfan said:
I wish I would have read this post a few days ago prior to changing my voltage settings also. Only to learn that I wasn't doing my GNex a significant favor.
Click to expand...
Click to collapse
Ya thankfully read it, tried these voltages with hotplug on and screen off settings and the phone did not sleep of death this time, but it froze right after wakeup, so no hotplug for me, just conservative.

Also, be very careful with CORE and IVA undervolting. In my case, undervolting theese too much caused the exactly same issue you are dealing with. Same goes with profiles for SetCPU profiles which also causes the phone to behave like that in some cases

keem85 said:
Also, be very careful with CORE and IVA undervolting. In my case, undervolting theese too much caused the exactly same issue you are dealing with. Same goes with profiles for SetCPU profiles which also causes the phone to behave like that in some cases
Click to expand...
Click to collapse
So for what I can make out from your post, some reason its setcpu profiles not working, not the phones cpu itself not allowing it be put into hotplug mode? also, sorry for the noob question but what is the difference between CORE and IVA undervolting? Or should I say could you explain them to me.

If you are going to use profiles, your phone should be very stable. In other words undervolting makes it instable if you tweak it too much. Core and iva are very sensitive. Core is your graphic gpu. Let them stay at the normal settings. Use milestone franco stable build undervolting only the cpu. Rather 700 mhz at the lowest. Try it out
EDIT: "If you are going to use profiles, your phone should be very stable BEFORE setting profiles"
Sent from my Galaxy Nexus using xda premium