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 and Undervolting My Epic 4g

Hey i just got setcpu for my epic...I overclocked it to 1200 and i undervolted it. Whats the safest overclock? my undervolts are -125mV at 100MHz, -75 at 200MHz and 400, -50 for 600 and 800mhz, and -25mV for 900 1000 1100 and 1200....are these safe values? anyone have recommended values or know the lowest safest ones?
thanks

EVERY Phone is different! And any overclocking can potentially damage your phone. I would never go higher than 1200, my phone starts to lock up at 1300, but there are crazies out there pushing their phones to 1500.

kennyglass123 said:
EVERY Phone is different! And any overclocking can potentially damage your phone. I would never go higher than 1200, my phone starts to lock up at 1300, but there are crazies out there pushing their phones to 1500.
Click to expand...
Click to collapse
what about undervolting at each MHz in order to save battery?

andrewt328 said:
what about undervolting at each MHz in order to save battery?
Click to expand...
Click to collapse
People have gotten mixed results. Best thing to do is try it. Never select set on boot in case it screws up your phone. Start small, 25mV per frequency and run you phone for a bit. Keep a chart. If something don't work go back to previous settings and try changing certain frequencies until your phone is stable. When you are sure of stability, pick set on boot and run it for a day to see if it makes a difference in your battery life.

kennyglass123 said:
People have gotten mixed results. Best thing to do is try it. Never select set on boot in case it screws up your phone. Start small, 25mV per frequency and run you phone for a bit. Keep a chart. If something don't work go back to previous settings and try changing certain frequencies until your phone is stable. When you are sure of stability, pick set on boot and run it for a day to see if it makes a difference in your battery life.
Click to expand...
Click to collapse
if i put it on set on boot and the phone crashes, will my phone be dead for since it will boot to that power every time and crash? or could i just restore it through cwm and have it work again?
thanks

andrewt328 said:
if i put it on set on boot and the phone crashes, will my phone be dead for since it will boot to that power every time and crash? or could i just restore it through cwm and have it work again?
thanks
Click to expand...
Click to collapse
You can restore through CWM. Also if you are using Voltage Control a little screen pops up telling you that it will make a quick flashable file to restore your stock settings. I can't remember the name of the file but you will see it.

I know that every phone is very different but both my phones sit well at 100Mhz:-100 200Mhz:-100 400/600Mhz:-75 800/1000Mhz:-50 1100Mhz:-25
I know these may not work on yours but this might help for a base line. Hope it helps.
EDIT: and yeah both phones are over clocked to 1500 with deadline / ondemand

Stable OC for my Epic !!!!
I have used Voltage control to OC it with settings : 400 Mhz minimum(recommended somewhere in dev post), 1340 Mhz maximum(~1400 mv voltage which I think maximum my handset can handle) with ONDEMAND governor.
My Epic is running flawlessly with no random eboots of FC's since last 4 days (while it used to reboot atleast 3-4 times daily earlier).
ROM : ERA Lagendary RC2
Kernel : Samurai 2.0.1 (inbuilt with Rc2)
Theme : Ei22Ics version 2 (just for fun !!!)
Epic Timezzzzzzzzz !!!!!!

[Q] How low can we go? (Undervoltage)

Okay I have tried searching, but it is a bit hard from my phone, so I'm sorry if I missed a post answering this.
Does anyone know how low UV this phone normally goes? In miui I could go as low as it allowed (750?) at the slowest CPU setting, but I wonder how low others go. I know it differs from one phone to another, but still..
Sent from my HTC Vision using XDA App

Our phone can usually only go down to about 850 but what you'll have to do is test each voltage for each clock speed, so what you would do is set the voltage (TEMPORARILY!!! THIS IS VERY IMPORTANT!) then set your clock speed to be only this speed to see if it is stable. IE: Set ~200 to 850, set clock speed to only ~200 (whatever it is for miui kernel, they are all different by a little bit) and then go around the ROM and look for any HARD lockups (lockups that require a battery pull, lots of lag and lag spikes are to be expected) and then turn screen off for like 30 secs and back on to check it. Do this for all clock speeds (if you want to change them all) For the record, AFAIK if a clock speed has a certain voltage, all clock speeds below it will be stable at that voltage. Once you get up to ~700 MHz also test it with some video. This should work if you want to be SUPER thorough but make sure you always TEMP first (because if it cause's a hard lockup, that will cause major problems...) also do a nandroid first just in case.
For the record, undervolting can be risky, so I am not responsible if you cause damage, just giving you a means of doing it

The lowest I've gone was 750 and works perfect. I don't want to go any lower though, phone's still eating up 32maH with screen off.

Thanks for the explanation. I already know how it works though and I'm being super careful. I was more interested in finding out what settings others use. So what are you at at other CPU speeds?
I test stability with Stability Test (I think its called) and some benchmark apps. Then try different stuff like movies, flash (like in a browser, not flashing anything) and turning the screen on and off. With temp settings in oc/uv beater.
--------------------
Sent from my HTC Desire Z using XDA premium

Does anyone know what scenario causes the most voltage drain from the CPU? Playing HD video? Crunching numbers (pi?)? Shooting pigeons?
Hmm, let me rephrase that
Name the 3 best ways to test stability when tweaking undervoltage

theres an app i found yesterday to test the stability of my SG2 its call "stability test" just set your core at that fixed clock and let it go...i just let it run 3-4 times after that if its good then i move on, but sometimes i feel the phone sluggish, i just increase the voltage on that and its fine again.
too much voltage burn the thing/ kill the battery, not enough voltage it starting to freeze up.

Yes I know the app and it's great! But I'm playing around with my own little app project so I was interested in what everyone use to test stability. That would be +1 to number crunching so far

Although I am starting to feel like I'm talking to myself I'll still post my (hopefully stable) undervoltage results if anyone should be interested:
Code:
245760: 750
368640: 750
576000: 900
768000: 900
806400: 925
902400: 925
1017600: 975
1113600: 1000
1209600: 1050
1305600: 1100
1401600: 1150
1507200: 1225
1574400: 1300
I'm testing a small app I'm coding, to learn more about Android, so the numbers will probably change as I learn more and get better at coding and testing the stability of my phone.
Also please remember your phone is going to be different than mine, even if the hardware is exactly the same, so this is only a rough guide.
Sent from my HTC Desire Z using xda premium

How do you undervolt with the default CM7 kernel?

[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

[Q] Really strange UV capability on GN7100???

This is really strange and probably even stranger to complain about but I want to understand.
I UV on my Note and so far managed to drop to levels I find hard to believe.
200MHz - 600mV
300MHz - 600mV
400MHz - 600mV
500MHz - 600mV
600MHz - 600mV
700MHz - 600mV
800MHz - 600mV
900MHz - 600mV
1000MHz - 600mV
1100MHz - 600mV
1200MHz - 975mV
1300MHz - 975mV
1400MHz - 1000mV
1500MHz - 1050mV
1600MHz - 1100mV
Why is my note able to run at 600mV on all frequencies up to 1100MHz??? At first I thought it was a reporting error and It wasn't really running on those voltages but found breaking points on higher frequencies so eliminated that theory. :silly: Would be to be able to test these frequencies at even lower levels. Anybody know a tool that can do it?
This is the process I followed:
Set the voltage value in STweaks,
Set the max MHz in STweaks to the frequency for which I just dropped the voltage ,
Close STweaks,
Open Voltage Control to confirm that the voltage and max frequency has really been set,
Close Voltage control,
Reboot,
Open Voltage Control again to confirm that the voltage and max frequency is really set,
Close Voltage control,
Reset timings in Android Tuner Free,
Start Stability - Classic Test and verify that the Note is running at the max frequency,
Open some other apps and play around for a while,
Get Stability Test back to foreground and go to sleep (if it is time to sleep)
For all of the above frequency values i ran the Stability Test overnight for at least 4 hours plus for a couple hours while using the phone. Didnt get a single freeze or reboot. The only issue was that while I had it on max 200 MHz the Note was not usable while the 300 and 400 MHz frequencies were annoyingly slow. 500 MHz and up is bearable even with Stability Test running.
Attached are the last status and test screenshots. The Stability Test has been running while I been also using it for calling, messaging, adjusting other app setting and taking screenshots.
I check the frequency timings in Android Tuner Free and it is usually 1-4% on offline, 95-98% on the tested frequency and sometime 1% on the frequency just above the tested one. All other frequency times usually 0%
Any ideas if something funny is going on or is this Note just unbelievably under-voltable???

MutantWizard said:
This is really strange and probably even stranger to complain about but I simply need to understand.
I UV on my Note and so far managed to drop to levels I simply cant believe.
200MHz - 600 mV
300MHz - 600 mV
400MHz - 600 mV
500MHz - 600 mV
600MHz - 600 mV
700MHz - 600 mV
800MHz - 600 mV
Rest of the frequencies are still at stock values
First I copy pasted some UV setting from another post and the Note ran without Issues. Then I started dropping a little bit here and there and at some point got some freezes and reboots but couldnt figure out which frequency was the issue so I returned all to stock and started one by one from 200 MHz. The above is where I got to so far and simply need to understand why or what is happening.
This is the process I followed:
Set the voltage value in STweaks,
Set the max MHz in STweaks to the frequency for which I just dropped the voltage ,
Close STweaks,
Open Voltage Control to confirm that the voltage and max frequency has really been set,
Close Voltage control,
Reboot,
Open Voltage Control again to confirm that the voltage and max frequency is really set,
Close Voltage control,
Reset timings in Android Tuner Free,
Start Stability - Classic Test and verify that the Note is running at the max frequency,
Open some other apps and play around for a while,
Get Stability Test back to foreground and go to sleep (if it is time to sleep)
For all of the above frequency values i ran the Stability Test overnight for at least 4 hours plus for a couple hours while using the phone. Didnt get a single freeze or reboot. The only issue was that while I had it on max 200 MHz the Note was not usable while the 300 and 400 MHz frequencies were annoyingly slow. 500 MHz and up is bearable even with Stability Test running.
Attached are the screenshots of the process at 800 MHz and the Stability Test has been running for almost six hous while I been also using it for messaging, adjusting other app setting and taking screenshots. After about 5 hours of 100% CPU load at 800 MHz the Note is down to 80% battery. Not really sure but it seems quite low power consumption.
I just checked the timings again in Android Tuner Free and 12% on offline, 86% on 800 MHz. All other frequency times 0%
Any ideas if something funny is going on or is this Note just unbelievably undervoltable???
Click to expand...
Click to collapse
1st thing, my STweaks is ver 1.1 but looks a bit different than your screenshots, pls confirm that.
2nd, I too like to underclock but had no idea you could push it as far as you . It's kind of like driving a car low on gas to see how far you can go.
3rd What ROM & kernel you on? I'm on X-Note 3.3 with Adam kernel.
Last, here's a screenshot of my undervolting...I'm kinda embarrassed compared to yours Note the differences in layout of STweak menu.
I'm inspired to go even lower now, my battery life is pretty awesome but I think I can squeeze it more.

tweeny80 said:
1st thing, my STweaks is ver 1.1 but looks a bit different than your screenshots, pls confirm that.
2nd, I too like to underclock but had no idea you could push it as far as you . It's kind of like driving a car low on gas to see how far you can go.
3rd What ROM & kernel you on? I'm on X-Note 3.3 with Adam kernel.
Last, here's a screenshot of my undervolting...I'm kinda embarrassed compared to yours Note the differences in layout of STweak menu.
I'm inspired to go even lower now, my battery life is pretty awesome but I think I can squeeze it more.
Click to expand...
Click to collapse
My STweaks is also 1.1 and guessing the menu difference might be due to different kernel. I am on RedPill, stock ROM and probably irrelevant but TWERP as well.
I have mixed feelings about the achieved UV. Very happy if it is true but suspicious that there is some kind of a reporting error and that I am actually not under-volting it at all.
I will soon update the OP since I have now been now testing the 900 MHz for the last 3 turns. Started at 900 mV then droped to 800 mV and now already running it for a couple hours at 700 mV. I just cant believe that its actually at at this voltage and running without issues.

MutantWizard said:
My STweaks is also 1.1 and guessing the menu difference might be due to different kernel. I am on RedPill, stock ROM and probably irrelevant but TWERP as well.
I have mixed feelings about the achieved UV. Very happy if it is true but suspicious that there is some kind of a reporting error and that I am actually not under-volting it at all.
I will soon update the OP since I have now been now testing the 900 MHz for the last 3 turns. Started at 900 mV then droped to 800 mV and now already running it for a couple hours at 700 mV. I just cant believe that its actually at at this voltage and running without issues.
Click to expand...
Click to collapse
Hmm yes, because you're going so low, it begs the question is the app reading accurate? I mean, you're reeeaaaal low. Would be good for a more knowledgeable person to chip in and give us feedback.
One thing - in your screenshot it shows your max frequency capped at 800MHz. To me that reads you are running only at 50% power. If so, that explains your insane battery life. From steps 900 and above you've left voltage at stock because they're unused. right?

tweeny80 said:
Hmm yes, because you're going so low, it begs the question is the app reading accurate? I mean, you're reeeaaaal low. Would be good for a more knowledgeable person to chip in and give us feedback.
One thing - in your screenshot it shows your max frequency capped at 800MHz. To me that reads you are running only at 50% power. If so, that explains your insane battery life. From steps 900 and above you've left voltage at stock because they're unused. right?
Click to expand...
Click to collapse
Yes higher frequencies still at stock and not used but will be getting to them at their own time. Fact though is that even with cap at current 900 MHz and with Stability test running I can still use the Note normally for any regular tasks. If I don't play games I would never need more speed.
Now updating the OP with the 900 MHz setting and screenshots.
BTW I just realized I added to battery life when transferring screenshots by connecting the Note to the laptop by cable. Battery life still remains to be seen.

Updated the OP with the full range of voltages 200-1600. I don't OC so those will not be doing. But I still have the original question.
Is it possible???

Gets more and more strange. GPU under-clocking and under-volting of following frequencies working for days without any usage issue. I changed the minimum and maximum MHz to include the below frequencies and didn't notice any difference in the Note behavior / performance. When running the stability test with GPU testing included I don't get any errors if running under 2 hours but if I leave it overnight the test does crash at some point in time without any other ill effect. I only know that it crashed coz it disapears and it tells me it crashed when the next day I re-start the test.
54MHz - 600mV
108MHz - 600mV
160MHz - 600mV
266MHz - 600mV
350MHz - 600mV
The fact though is I don't understand what to expect as an issue when under-clocking or under-volting the GPU.

Mate, you're still at it!?
Rereading your data, I strongly suggest you post these stats in whatever thread belongs to the kernel and/or tuner app you're using.
My overseas Singaporean work colleagues would say 'cannot be, cannot be.....'

tweeny80 said:
Mate, you're still at it!?
Rereading your data, I strongly suggest you post these stats in whatever thread belongs to the kernel and/or tuner app you're using.
My overseas Singaporean work colleagues would say 'cannot be, cannot be.....'
Click to expand...
Click to collapse
Yea slowly trying one by one new settings and letting it run for a while so that when I go to the next setting and experience an issue I am sure its the newest setting that's causing it.
Thanks will do as suggested.