Hello.
Undervolting your CPU has always been a daunting task - there's so many CPU steps, if you pick say -100mV to all frequency steps and you get a reboot, how do you work out which step (or steps!) is causing the problem? If you undervolt -25mV on one frequency, then wait a couple of days to make sure it's stable, then reduce the same frequency by another 25mV.. you'll still be undervolting a year later.
This thread is my tutorial on how to do a best effort at quickly and safely undervolting your phone CPU.
First of all - is undervolting your CPU worth it?
Initially it was thought not to make much difference, but after some serious testing (thanks AndreiLux), "we" decided that it was a good idea. I also did my own basic testing, and it looks like it's worth it.
What are the advantages of undervolting?
Better battery life
Cooler phone, especially useful if you overclock your CPU
What are the disadvantages of undervolting?
That's the great thing! Really the worst that can happen is your phone freezes or reboots. The steps below should eliminate all of that. Once you have undervolted your CPU to just above its freeze/crash levels, there are no disadvantages!
Note: I have had some minor data loss (eg an app forgets a setting) after an undervolting related crash, but it was rare and I believe has to do with the Perseus kernel "Enable dynamic FSync" setting. I note below how to mitigate against this.
What do you need?
A rooted phone, and a kernel that supports undervolting. Perseus and Siyah will work, but any kernel should be fine that supports SetCPU's undervolting schema
SetCPU or you can use a combination of STweaks and Stability Test (use STweaks for setting the frequency and voltage, and use Stability Test's Classic Test for the stress test)
A paper and a pen - I used Sticky Notes as I was at a computer for most of the process
Some patience
Let’s begin.
Open SetCPU. You’ll be greeted by the Main screen which has the min/max CPU frequencies, the governor options, and the IO scheduler options. Reduce the max CPU frequency to the lowest step. On the SGS3 this will be reducing 1400MHz down to 200MHz, so you now have both the min and the max set at 200MHz. The phone will get pretty slow at this point. Ensure the Set on Boot option is unticked
Set the governor to Performance (note: you have to make sure all cores of your CPU are being used. In a complex kernel such as Perseus, you'll have to go into STweaks and set the CPU hotplug lock to 4 so all 4 cores are used. Also note there appears to be a bug in Perseus at the time of writing: you have to set the hotplug lock BEFORE you change the governor to performance)
Move to the Voltages screen
Ensure the Set on Boot option is unticked, and scroll down to the lowest setting, and change it to something low, like 700mV, and then apply it (click the third icon from the right at the top of the screen, a rectangle with a tick on it) . This first setting is always a bit of guess and check, and to be honest you’re hoping for the phone to freeze or crash on this first one. Has it frozen? If so move on to the next step. If not, reduce it by a further 25mV and apply again, repeat until your phone freezes or reboots.
So, you have undervolted too far. Reboot the phone, and perform steps 1-3 again. At step 4, use the voltage that crashed your phone +25mV (eg if it crashed at 675mV, this time set it to 700mV). Now, you have a very slow phone running a low voltage that doesn’t immediately crash it. Move on to the next step
An easy crash test I found was simply allowing the phone to go into deep sleep, and waking it up again. To do this, unplug your phone if it’s charging, and turn the screen off. At this point I usually wrote the time down on my piece of paper, as well as what frequency and voltage I was testing as I’m prone to forget these things. Wait 5 minutes with the screen off (and make sure no notifications have come in while the screen is off – this wakes the phone up and you’ll have to wait another 5 mins), then turn the phone on. You’ll know it’s gone into deep sleep as there’ll be a slight delay before the screen turns on as compared to no delay when turning it off and immediately back on again. If the phone doesn’t turn on, go to step 5. If your phone comes out of deep sleep OK, move on to the next step.
Now, we stress test. In SetCPU scroll over to the Info screen, and scroll down to the Stress Test option. Start it, and note down the time on your paper/Sticky Notes. Your CPU will now run as hard as it can at the current frequency. Let it run for 15-20 minutes. At the lowest frequency it will be pretty laggy and slow, if you think it has frozen always give it 30 seconds to see if it picks up again. If it gets stuck for over a minute, you probably have a crash. Go to step 5. If after 15-20 minutes it’s still running, you have found your first stable(ish) voltage for that frequency! At this point I saved the voltages in SetCPU by pressing the diskette icon. To ensure the changes are written to disk turn the phone screen off for 5 seconds then turn it back on again.
We are now ready for the next frequency. There’s pretty much no way a frequency will run stably on a lower voltage than a frequency below it, so our first voltage for the next frequency up should be the same stable voltage we found for the previous frequency. For example if we found a stable voltage of 725mV on the 200MHz frequency, our first test voltage for 300MHz should be 725mV. Write this down with the frequency on your paper. In the Main screen of SetCPU, change the max frequency to the next step up. Then, in the Voltages screen, adjust the voltage to be the same as the lower frequency, as discussed above. If your phone immediately freezes or reboots, move to the next step. If not, go to step 10.
So, you have undervolted too far, again! Reboot your phone, open up SetCPU, and in the main screen ensure the max frequency is set to the frequency we’re testing. Give the sliding bar things a jiggle to apply it. Ensure the governor is set to Performance by pressing it on the lower left part of the screen. Move to the Voltages screen, and you’ll either see your previous “saved” voltage values ready to be applied in dark grey under the “current” voltage settings, or you’ll have lost your “saved” voltage settings. If you have lost them, never fear; just restore the latest settings by clicking the first from the right icon at the top (a square with an arrow pointing outwards). Adjust the frequency we’re testing’s value to 25mV more than the value you last used when it crashed, and apply it. If it crashes immediately, repeat this step. If not, move on
We now start the two tests in steps 6 and 7 again, but this time if your phone crashes or freezes, go to step 9. If it completes the deep sleep and stress test tests, go to step 8 for the next frequency test.
Sorry for the complexity here, but it was the easiest way I could write it without repeating myself too much. The TL;DR version goes like this:
Pick the lowest untested frequency, set the max frequency to this and the governor to Performance, and find the lowest voltage that doesn’t immediately crash the phone
Put the phone into deep sleep, and see if it crashes. If it does, increase the voltage for the current frequency we’re testing by 25mV and test again. If not, move on
Run a stress test on the phone for 15-20 minutes. If it crashes, raise the voltage by 25mV and go to step B. If it doesn’t crash the current frequency is now tested. Go to step A
You now have a set of frequencies that shouldn’t immediately crash the phone. Set the min and the max frequencies back to normal, and set the governor back to your usual governor. At this point for me I was able to use the phone for about 2 hours before I had my first crash. How running a stress test on each frequency for 20 minutes didn’t pick up this crash situation I’m not sure, but it didn't.
After screwing around for a while I found the easiest solution was to just raise each frequency step by 25mV and then continue every day usage. That was enough to stabilise my phone. If it still crashes for you, keep raising all the values by 25mV until it settles down. After a day or two of no crashes you can start slowly one by one reducing each step by 25mV again to find out which step caused the crash.
After that, you should be done!
Ps I know there is another thread around here discussing undervolting, but I found it too vague on the details and sometimes wrong, so I thought I’d share my experiences in the hope it might help.
Good work!
Would you pls post your testing results for our reference?
Thanks.
Mod edit: please do not quote the OP.
A table with the running undervolting settings would be a great orientation help. Given that, people don't need to trail and error from scratch.
Sent from my Nexus 4 using xda app-developers app
me_max said:
A table with the running undervolting settings would be a great orientation help. Given that, people don't need to trail and error from scratch.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Under/over volting doesn't work that way. Each chip is unique, and chips are tested only on default voltage and frequencies, so each one's behavior on non-default settings is unpredictable. Some are able to work on 100 mV lower voltage, some can't handle even -25mV... Trial and error is the core of overclocking.
yep, that's one of the reasons i disagreed with the other UV thread - they list absolute voltage levels which are only applicable to the specific grade of chip in their phone (and yes, I posted some corrections in the other thread but they were ignored).
Have a look HERE if you'de like to see all the different possible default voltage settings for the i9300/i9305.
As a rough rough guide of a voltage level for the 200MHz step that will (hopefully) crash your phone, I'd start at 650mV.
i have tested my cpu
for stable values and i finished with these settings:
200Mhz - 0.775V
300Mhz - 0.800V
400Mhz - 0.825V
500Mhz - 0.850V
600Mhz - 0.875V
700Mhz - 0.900V
800Mhz - 0.925V
900Mhz - 0.950V
1000Mhz - 0.975V
1100Mhz - 1.000V
1200Mhz - 1.050V
1300Mhz - 1.100V
1400Mhz - 1.150V
1500Mhz - 1.200V
My exynos is stable for 2 months now, i play a lot of new games like most wanted etc.
In UV more important is leaving phone in idle, deep sleep on and off, or non demanding tasks, if i UV too much games were stable but i had random restarts when phone was in the pocket sleeping. But, as You mentioned, every cpu is different so everyone has to test it...
Thank you OP for this very, very useful guide. I am new to undervolting and even though I have a T999V north-american model with the Qualcomm SoC, this will prove very useful in my experimentation.
Only difference with the Qualcomm is that clock speed can go as low as 96Mhz, but you can't undervolt under 700mV - SetCPU just refuses to apply anything under that.
No probs
That's a kernel limitation, not SetCPU. Check with your kernel dev to see if they can allow further undervolting.
I tried to make the instructions as generic as possible so any stepping config could use them. good luck!
I'm doing my 96Mhz test and running a stress test.
The loading circle is still moving just fine (although a bit sluggishly) but none of my buttons are responding at all so I cant leave the test until I pull the battery. Would this count as a freeze/crash, or do you think this voltage is okay to stick at (or even go lower?!)
That's just the CPU bogging down, it's not a voltage issue.
hi guys. this might sound like a dumb question but i honestly looked everywhere but i cant seem to find the UV in setcpu. i'm i missing something?
Probably the kernel you're using doesn't support UV.
Hey
I find that 200 is stable on 687500
And then when I move to edit 300 it reboots
Then increased the number on both and still reboot.
I don't restart in between. Any idea??????
Sent from my GT-I9300 using xda app-developers app
tony1234567890tony said:
Hey
I find that 200 is stable on 687500
And then when I move to edit 300 it reboots
Then increased the number on both and still reboot.
I don't restart in between. Any idea??????
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
That means that 200 is NOT stable. Try using a higher voltage. 0.6875v is ridiculously low
TP.
What do you mean low he says in the op to reduse to 700
THC for fast answear
Sent from my GT-I9300 using xda app-developers app
tony1234567890tony said:
What do you mean low he says in the op to reduse to 700
THC for fast answear
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Default voltage for 200mhz step is 0.9v (for me on asv2). So 0.7v (which is still higher than what you have set) it a whopping 200mv less than stock which is like I said before, ridiculously low. It may run at this voltage for you for now(depending on your as level), but I can pretty much guarantee you that it will never be 100% stable
I'll take your THC ; ) lol
TP.
Thanks I'll give you feed back
Sent from my GT-I9300 using xda app-developers app
omniwolf said:
Probably the kernel you're using doesn't support UV.
Click to expand...
Click to collapse
i thought the matr1x kernel supports it. UV works fine in trickster mod. i don't even have a heading for 'voltages' in the the app like it's shown in the play store.
tony1234567890tony said:
What do you mean low he says in the op to reduse to 700
THC for fast answear
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
yep, as STAticKY says, if you get a reboot on a step, then it's not stable. raise the voltage on that step and try again.
STAticKY said:
Default voltage for 200mhz step is 0.9v. So 0.7v (which is still higher than what you have set) it a whopping 200mv less than stock which is like I said before, ridiculously low. It may run at this voltage for you for now, but I can pretty much guarantee you that it will never be 100% stable
I'll take your THC ; ) lol
TP.
Click to expand...
Click to collapse
This is only correct for your ASV value. Please edit this post, it contains incorrect information. Your default voltage for 200MHz might be 0.9v, but for other people it's likely different, as they have different quality chips. Read post 3, 4, and 5 in this thread for more info.
genericuser2013 said:
i thought the matr1x kernel supports it. UV works fine in trickster mod. i don't even have a heading for 'voltages' in the the app like it's shown in the play store.
Click to expand...
Click to collapse
possibly the matirx kernel does support UV, but it might not be exposed in the way that SetCPU is expecting. Does the Matrix kernel developer recommend a specific app to adjust the voltages? If so use that, you can still follow my guide.
Can anybody tell me how to determine ASV-level of my chip?
Related
this may be posted in the wrong section but i would like everyone running froyo to test this out
HERE IS THE LINK TO GET THE LATEST SETCPU
http://forum.xda-developers.com/showthread.php?t=505419
So I have been doing some experiments on ways to save battery life....I think i have made a break through it is not fully tested i would like for some of you to try it out.
with the latest updates to your ROM itself, setcpu, superuser, and the addition of cache cleaner and the incredible AUTOKILLER (a must have) i have been able to run extremely low setcpu sleep profiles without any noticeable loss of performance.
Believe it or not i have my sleep profile down clocked to 19200mhz with out "noticeable" performance loss
i would like for some of you if possible to try these profile out for a while and see how it works out for you
DEFAULT 480min---whatever you want max (mine is 787) ondemand (for performance)
OR DEFAULT 245min---whatever max (for even more battery savings)
SLEEP 192min---480max ondemand (works great even without sleep to wake lag)
it works dont believe me then check out set cpus new feature "time in state"
open setcpu
go over to info
scroll down a little and you will see the times in state your phones cpu runs in the most
you should now see values at the lowest state of 19200
if this works in theory we can benefit from longer battery life
and faster charging
please try these out and report back to the post or PM me...this could be good
Thanks
UPDATE 8/22 EDIT: some users are having success running an even lower default 19min--whatever max (thats even more savings) will be looking into it
try these even lower profiles
DEFAULT 122min--whatever max (screen ON cpu does not drop below 122mhz)
Screen OFF 19min--245max (no lag just ran pandora and cardio trainer at the same time here no lag from sleep to wake either)
or Screen Off 19min--480 max for more performance
REMEMBER not to have conflicting profiles and to have SCREEN OFF at your highest priority
please post here your own findings and results
Thanks again
UPDATE 08/24/2010
after experimenting with other speeds i have finally settled on these speeds for my personal taste on performance and battery savings
MY FINAL SETTINGS...
DEFAULT 19MIN---786 or whatever MAX on demand
SCREEN OFF 19MIN---480 MAX on demand (highest priority) think deeply about why this is the highest
TEMP <40 19MIN---528MAX (screen off overrides this which cools anyway)
BATT <40 19MIN---604MAX
next more into advanced settings....coming soon
UPDATE 08/26/2010
im almost at the holy grail here
try this set up
SCREEN OFF 19--480 (95 priority)
TEMP <40 19--580 (90 priority)
ADVANCED SETTINGS
SAMPLING RATE---100000
UP THRESHOLD---98
ignore nice ---0
power save bias---0
hit apply (if you like it check set at boot)
ALL CPUS ARE NOT CREATED EQUALLY WE ALL KNOW THIS SO DONT EXPECT MY EXACT SETTING TO WORK FOR EVERY SINGLE PHONE
I CAN ONLY OFFER A STARTING POINT BUT ITS UP TO YOU TO TWEAK IT BUT ITS WORK
I HOPE THIS HELPS
things to notice....
in the main screen in setcpu watch the main frequency values bounce up and down...after a few seconds the values seem to stabilize at the lowest frequency of 19
in time of state screen even when screen on most of the time the 19 freq get the most values
i need a few guys to run, test and monitor the values that i just posted ^^^HERE^^^
this may further the battery life once we stabilize the frequency to 19 most of the time while keep the SAME performance which i think i may have did
run some linpacks and quadrants with those setting
i got
5.4 linpack running 787max
431 quad running 787max
then it drops back to 19 and stabilizes
hope this works and please post all your feed back and setting so we can learn this and get it perfect
thanks
I even use 122 and 480 for my screen off profile.. And I don't have any lag at all.
thisisreallygay said:
I even use 122 and 480 for my screen off profile.. And I don't have any lag at all.
Click to expand...
Click to collapse
19 is even lower try it
Oh 19200? Wow I wasn't paying attention well enough. I'll try it.
Almost from the beginning of my rooting in May and using SetCPU, I've been using 19.2- 748.8 (on demand) with the screen on (sometimes higher but recently reduced the max to see if it helped with some FC's I was having - still haven't determined if it was the profile or the ROM that fixed my FC's).
I use 19.2-245 for screen off. I'd venture that there's about a one second delay for the caller ID to work once a call rings in, but it's more than bearable and worth it.
I have it go to 19.2-528 when the battery is less than 25%,and 19.2-480 if the temperature is above 49 degrees celcius.
I wonder what it's like when receiving a call. I just set it and I'm not having any lag with just turning it on or anything. I'll test it out with other things. I hope this greatly improves my battery.
roirraW "edor" ehT said:
Almost from the beginning of my rooting in May and using SetCPU, I've been using 19.2- 748.8 (on demand) with the screen on (sometimes higher but recently reduced the max to see if it helped with some FC's I was having - still haven't determined if it was the profile or the ROM that fixed my FC's).
I use 19.2-245 for screen off. I'd venture that there's about a one second delay for the caller ID to work once a call rings in, but it's more than bearable and worth it.
I have it go to 19.2-528 when the battery is less than 25%,and 19.2-480 if the temperature is above 49 degrees celcius.
Click to expand...
Click to collapse
shame on you for keeping that secret all to yourself
SHAME
By the way why did you say froyo roms specifically? I'm trying this on tainted tenzo and it's working. I'm usually on a frooy ROM though.
Hi Guys,
Can you please tell me how to get setcpu? I can't find it in the market.
Sent from my Nexus One using XDA App
Search for it on his website, idk what his website is you'll have to search for it. Or download a ROM with it already in it.
im on froyo 30 and was unable to get the 19.2 to show on time in state with screen off profile set to 100 priority at 245/19.2
i was however able to have it start using that frequency by using 710/19.2 as my default setting, then enabling the 245/19.2 profile as screen off.
ive read its not too good to have the cpu jump more than 300mhz per profile though so im not sure how this will work out.
thisisreallygay said:
By the way why did you say froyo roms specifically? I'm trying this on tainted tenzo and it's working. I'm usually on a frooy ROM though.
Click to expand...
Click to collapse
hmm last time i was on sense rom sense fell apart if you clocked lower than 245
epically receiving a phone call
but i only test this method on froyo
I've heard that too. Although I don't know what is bad about it.
sh_mohanna said:
Hi Guys,
Can you please tell me how to get setcpu? I can't find it in the market.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
HERE
http://forum.xda-developers.com/showthread.php?t=505419
eklipze said:
im on froyo 30 and was unable to get the 19.2 to show on time in state with screen off profile set to 100 priority at 245/19.2
i was however able to have it start using that frequency by using 710/19.2 as my default setting, then enabling the 245/19.2 profile as screen off.
ive read its not too good to have the cpu jump more than 300mhz per profile though so im not sure how this will work out.
Click to expand...
Click to collapse
i heard that too but all froyo dev have a 245 to 710 stock on their roms
thats why i kinda spilt the two profiles and why 245min--- is experimental
leave your screen off for a while and see if the ime of state shows up
also make sure not to have conflicting profiles running in setcpu
Hmm. Well tainted is vanilla but has some sense elements (like sense dialer) So idk. It seems to work. I'll test out calls.
thisisreallygay said:
Hmm. Well tainted is vanilla but has some sense elements (like sense dialer) So idk. It seems to work. I'll test out calls.
Click to expand...
Click to collapse
oh ok tainted is not vanilla
tainted IS sense with sense removed with vanilla remaning hence the word tainted
some sense is still there
i think
Yeah it's got sense contacts and stuff but vanilla messaging. But it has the sense dialer so I think it would also have lag with calls if the sense ones were having lag. And I just tested it and it took a lil while for it to recognize whose number it was but it still gave me plenty of time to answer the call. I'll be testing to see how it improves battery. Thanks for the find
Im also testing setcpu Advanced settings batery life (without performance loss)
What settings are those?
Well, it worked with three other testers, some friends of mine that found the same problem. If you're facing this, try and feedback me. Just want to make sure that I've helped someone.
This guide is for those who have the 0% battery issue, found the fix by Bazoocaze (thanks a lot !!!) and are experiencing some quick battery drain. If you're not, then you can go read something else In two or three weeks of testing, I believe that this does not have something related to the ROM that we're using. The processes on background and the use of CPU is relative, but maybe a process is using too much energy, and if we keep the energy level on a low status, I think this process won't have so much energy to use. And maybe the kernel, or the kernel's governors are affecting something, not sure of this last one. I've also concluded that this don't have anything to do with the Wi-Fi modules, because I've already tried that fix, and it drains pretty quick anyway, some believe that there is a bug affecting the Wi-Fi, and it doesn't turn off, even if we turn it off on the menu.
First of all, if you haven't find the fix, read this: http://forum.xda-developers.com/showthread.php?t=1312398
You can also use the DooMKerneL ICS v4 that DooMLorD developed, and it already has the patch built-in (I recommend for this guide): http://forum.xda-developers.com/showthread.php?t=1520654
1 - Flash the kernel, the one of Bazoocaze or the DooM Kernel
2 - Turn on your phone, normally, make all your configs, and do a little test, BEFORE following this guide. See how many time your battery can hold on. If you feel that it's going out too fast, keep going on the guide.
3 - For this operation, I suggest you buy or download the free version of SETCPU, never forget that name. NoFrills didn't work very well to me..
4 - Overclock, if you want and if you're using DooMKerneL. Keep the MHz min on 364 (will explain later)
5 - Go to the profiles tab and press the ''plus'' button. Change the MHz max to 768 and keep the min at 364. In profile, select Screen Off, and change the governor to powersave or smartass and set priority to 100%
6 - Save it, and press Enable and Notifications on the bottom of the screen.
7 - Now test it for some time. Try not to keep your screen always on, as it ''cancel'' the effect of this guide.
Explanations:
a) The reason to keep the min MHz at 364 is that you won't face stuttering in the screen on/off, because the app will only change the max value, and not the min value, which makes the system still work fine (I believe, if some dev could correct me..). It behave better in AOSP alike roms.
b) NoFrills didn't give me the same results as SetCPU, that's why I'm recommending SetCPU. Make some effort to buy the Pro app.
c) The main trick is to reduce the power usage and capacity when the screen is off, because you don't use your phone 100% of the day, and because the process that may exist (mentioned above) would not use the whole capacity of the energy and the CPU as well. That's why it works. At least worked for me.
d) There is absolutely no hardware of software issue if you try this guide, you can uninstall the SetCPU app and use kernel other than DooM's. It's safe and quick, if it doesn't work, you can always revert everything.
Please, if you want to try this guide, give me the feedback. As I've said, I just want to confirm that theory and make sure that I've helped someone.
Thanks Bazoocaze and DooMLorD for being life savers!!!!!!!!
Bye
Thanks for your help
Sent from my LT18i using xda premium
ok guys first of all ill start by saying that none of this i mine...its all stuff that i understood from different threads.I am a complete noob so there are gonna be many things ill not be able to understand to you!
i am gonna thank these brilliant people first
-gokhanmoral
-pikachu
-droidphile
-andre
and others(who have started undervolt threads) ive missed!
ok now to the main point!
this works only on ics siyah kernels as currently GM is the only one who supports the following commands!
what you need!!
-terminal emulator
-volt tweaking app (set cpu, voltage control),i wont prefer extweak or xxtweak as you cant edit a perticular freq volt with them
-patience
ok now start by selecting the freq on which you wanna work..undervolt it to your desired volt
e.g ive undervolted my 200mhz to 925mv
now open terminal emulator
type:
su
LVL=`cat /proc/kallsyms|grep " level\."|awk '{print $3}'`;kmemhelper -n $LVL -t int 14
and press enter
ok what this command does is that it changes your touch screen freq to the number last in the command line..in this case 14 it is
you can alter these numbers as follow:
0-1600 6-1000 12-400
1-1500 7-900 13-300
2-1400 8-800 14-200
3-1300 9-700 15-100
4-1200 10-600
5-1100 11-500(stock)
so as you can see the above command line sets my touch freq to 200 mhz.
ok so as soon you press enter in the terminal emulator your touch freq is changed to the freq of your liking..(remember use the above states numbers and not the freq itself in the command line) and some how that perticular freq takes load in such a pattern which i could not recreate with any stress stability test or even mxvideo test( you can find about it in various threads) and hence if the undervolt is below the stability threshold your phone will crash,hang,reboot...but you will get to know which volt value on which freq is unstable.
After setting the touch screen freq try(you can use voltage control to confirm if your touch freq has changed or not) use your phone normally...scrolll between pages..browse..play games..and if the perticular freq volt is unstable your phone will indefinitely crash within 5-10 min..!
do this procedure for every freq and ull definitely will get yourself the most stable UV's your device can handle!
you can read much about this and other stuff in droidphiles thread
http://forum.xda-developers.com/showthread.php?t=1572937
thank me if it helped!!
Hmm... do we really need another one of these threads lol
Sent from my 80GB CyanogenMOD 9 + Siyah ICS powered beast. Booya!!
i jus tought of sharing this as it seems to me that this kinda crash which the touchscreen freq produces isnt reproduced by any stability test..hence another way for testing your stability...besides i myself was facing few crashes with my settings lately and this cured it...!
Your CAPS key is broken ...
haha not really...HERE YOU GO...i had words in caps up there aswell...dun knw what went wrong..btw...love your dp!!
Thanks for the info. I've been having a little trouble with some UV values that I believe should be stable. This might be the fix. I'll report back after I've tested it.
I didn't even know you could do that, learn something everyday.
Interesting because in Siyah I've always noticed the max frequency ALWAYS exceeds whats set in SetCPU etc.
If I set it to 500mhz, it will still jump to 800Mhz momentarily when touching the screen, loading apps, scrolling etc. I've noticed on the latest kernel it hits 1200mhz, no matter what my global max frequency is. On Abyss kernel etc, it behaves normally. Is this 'touch frequency' the reason for this?
I watch the CPU frequency using Cool Tools/CPU spy...
Tye:P said:
Thanks for the info. I've been having a little trouble with some UV values that I believe should be stable. This might be the fix. I'll report back after I've tested it.
I didn't even know you could do that, learn something everyday.
Click to expand...
Click to collapse
yeah i myself was having issues with uv's..found this way indirectly with the help of droidphile...would love to see if it helped you!
busky2k said:
Interesting because in Siyah I've always noticed the max frequency ALWAYS exceeds whats set in SetCPU etc.
If I set it to 500mhz, it will still jump to 800Mhz momentarily when touching the screen, loading apps, scrolling etc. I've noticed on the latest kernel it hits 1200mhz, no matter what my global max frequency is. On Abyss kernel etc, it behaves normally. Is this 'touch frequency' the reason for this?
I watch the CPU frequency using Cool Tools/CPU spy...
Click to expand...
Click to collapse
mate your issue can be solved simply by installing extweak and setting the smooth scaling level to your max freq..on default the level is 1200..but this issue was solved in the 3.2.7.X versions of siyah..which version are you using?
i'll try to UV with xxtweak
doesnt matter what uv tool you use...but i should be an app which uv's indivisual freq's and not all at once as then you wont be able to figure out which volt is giving error on which freq!
is anybody else having an issue when you underclock? i usually set it to 1.4Ghz but the phone overrides the setting i put up using Atuntu CPU master. i feel that the phone is still fluid when underclocked, so i tend to under clock to save battery life(and stop if from overheating to 105.1 degrees farenheit).i need to get full usage out of my phone as the day starts at 5 AM till 5PM with heavy usage
any luck with this issue?
Kernel on forums if you have compatible phone. Inteli and trickster with thermald disabled. Lock freq. While your at it, look up your soc bin and and start trialling undervolts.
42 8996883
Steamer86 said:
Kernel on forums if you have compatible phone. Inteli and trickster with thermald disabled. Lock freq. While your at it, look up your soc bin and and start trialling undervolts.
Click to expand...
Click to collapse
in English please? o dont get what wou mean by the SOC Bin and the part after that. i did the trickster, but it still overrides it.
You can't make it stick with default kernel. You need a modified one with inteli so thermald doesn't auto override. SOC bin is details on your "CPU" quality for base volt values, better SOC means better overclock, underclock, and undervolting. If you're serious in doing this, search and learn. This isn't simple modification, and you will not be able do this in simple way. Make sure you have set on boot checked in trickster. Well work somewhat better, but still not a permanent solution.
Setting up Custom Kernels
*this information is helpful for anyone, everything written here, I have thoroughly tested, this guide is not laid out beautifully,I will rewrite it on my desktop pc soon.
There seems to be allot of confusion about how to set up
"Custom" Kernels for the Moto G 2015 (Osprey) for testing
This is mostly due to the following reasons :
Guides/info are Outdated
info usually Vague/Confusing for Novice
Guides are often for different hardware/software
Information is wrong or unfounded or based on speculation/theory
tunables for "performance" often do the opposite
But the biggest issue that Novices have seems to be
A lack of understanding that almost every tunable has
An equal opposite reaction (side effects)
Therefore balancing each tunable with each other is essential*
Getting Ready to bench
1 ) My First step is, head over to the Android Modders Guide (look in KA to see which Gov's & Scheduler's) and get familiar with the Govs & Sched's featured in the kernel your using
2 ) now that you're familiar with that open up KA and go to
To the hotplugging section, disable any hotplugging
For the reason that you want to be able to accurately test the performance/characteristics of The CPU and Governor in use (in order to properly tune the system.)
(If you want, turn it back on when your *COMPLETELY DONE TUNING*)
3 ) make sure that while testing your phone CPU freq and Gov
That you're IO ReadAhead cache is set to 128, that way it doesn't interfere or confuse you while trying to set the CPU.
4 ) Go to the misc tab, do you see "Dynamic Fsync" ?
If so turn that off, This will switch it back to Standard Fsync
So in the rare case of a system crash your less likely to damage your data.
5 )*(optional) in the IO tab, Disable add random, and then go to entropy tab and set to 64-192 or 128-256 depending on preference.
Now onto the benching itself
1 ) alright, open the CPU tab and check the Max CPU Frequency, if there is OC available make sure you Never Start your testing/tuning using the Highest OC Frequency
(We don't have a baseline yet and most chips will not be able to perform properly or stable at these higher OC freq's eg. Above 1.593 GHz) start testing with your Max CPU set to
1.363 GHz and work your way up testing each one for performance and stability(Geekbench 3 is a good start).
2 ) Do the same thing for Selecting a Governor for benching . (Your phone might get warm while benchmarking, if you feel Like your phone is getting too hot, this could effect performance turn the phone off for a while until it cools down. Also make sure you restart occasionally in between tests to refresh everything.)
3) in GPU Tab, this is going to be just like setting up the CPU with one exception, you'll want to stick with one of
these two GPU govs (simple_ondemand) & (Msm-adreno)
the other ones are experimental.
and another thing, if your overclocking gpu to max550-650
i recommend setting the min freq to 200 for 550 and 310 for 650mhz, to avoid heat due to ramping up and down.
4 ) alright now into the IO tab, this is where you pick the scheduler that you're going to test with, I suggest fiops or tripndroid. *.
5 ) start benchmarking, I suggest you do multiple tests of whatever your using to benchmark.
6 ) Have fun!
*understand that benching will eat battery, therefore make sure when you get settings you like, you do separate battery test on a full charge.
*once you get the tunables that you're comfortable with.
You can enable hotplugging if you want.
I will post my recommended tunables for the 1GB Osprey
Below...
__________________________________________________________
*if you're going to be doing GPU heavy tasks i recommend
disabling Adreno idler.
recommended tunable for Adreno Idler
(battery savings and cool GPU)
24
17
6