[undervolting][ics][only siyah]how to check the stability of your undervolts! - Galaxy S II General

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!

Related

Weird problem with lag on hero with MCK 2.2, setcpu, (compcache not enabled)

so im currently running MCK 2.2 rom with the updated kernel but without compcache enabled because i havent been able to get it working yet.
here's the problem though, about once a day my phone will slow down to an unberable speed... just like it used to with the OEM Rom.
when I open up SetCpu (which i know isnt supposed to do anything on the hero) it tells me that my CPU is running at 245mhz, but the control bars in SetCPU are set for 528/480mhz... when i hit refresh the phone comes back up to 528/480 and its fast(er) again...
anybody have any ideas on this one?
dmc971989 said:
so im currently running MCK 2.2 rom with the updated kernel but without compcache enabled because i havent been able to get it working yet.
here's the problem though, about once a day my phone will slow down to an unberable speed... just like it used to with the OEM Rom.
when I open up SetCpu (which i know isnt supposed to do anything on the hero) it tells me that my CPU is running at 245mhz, but the control bars in SetCPU are set for 528/480mhz... when i hit refresh the phone comes back up to 528/480 and its fast(er) again...
anybody have any ideas on this one?
Click to expand...
Click to collapse
What gov. are you using on setcpu?
theoottesen said:
What gov. are you using on setcpu?
Click to expand...
Click to collapse
performance, and profiles are not enabled... again, it only happens after 12-15 hours or so... about once a day
Similar problem...
dmc971989 said:
performance, and profiles are not enabled... again, it only happens after 12-15 hours or so... about once a day
Click to expand...
Click to collapse
I have a similar problem. I experience serious slowdowns (compcache enabled or disabled) about once per day. I have not verified the CPU speed as I'm not using SetCPU. I am using the "performance" governor in MCK.
My typical solution is a reboot.
im just curious if this is the original problem or a new one cause by this rom setup... because I dont ever recall reading anything about the CPU getting stuck at 245mhz from sleep mode being the source the slow downs....
Have you tried disabling the location services to verify it's not that particular bug you're seeing/experiencing?
x99percent said:
Have you tried disabling the location services to verify it's not that particular bug you're seeing/experiencing?
Click to expand...
Click to collapse
yes, i keep them disabled...
jamesthomas128 said:
I have a similar problem. I experience serious slowdowns (compcache enabled or disabled) about once per day. I have not verified the CPU speed as I'm not using SetCPU. I am using the "performance" governor in MCK.
My typical solution is a reboot.
Click to expand...
Click to collapse
I look in the kernel and there are two sets of settings: The profiles and a set of setting for the kernel speed (this is split into min/max for screen on and min/max for screen off)
For screen on, it is set for 480000 min/528000 max
For screen off, it is set for 245760 min/245760 max
If the screen is off, it's possible that the kernel went into the lower settings and didn't come back.
I've heard different reports on whether the profiles work in the Hero. I'm curious myself. I do know the stock rom has everything locked, but since the kernel source has been released and Modaco released his kernel, I'm not so sure if the lock statement is true anymore.
I'm compiling a kernel as we speak with the cpu frequency scaling on. Had some issues with the cpufreq.h file not seeing two variables necessary for the userspace profile, but hopefully I was able to fix that (won't know until I run it).
tkirton said:
I look in the kernel and there are two sets of settings: The profiles and a set of setting for the kernel speed (this is split into min/max for screen on and min/max for screen off)
For screen on, it is set for 480000 min/528000 max
For screen off, it is set for 245760 min/245760 max
If the screen is off, it's possible that the kernel went into the lower settings and didn't come back.
I've heard different reports on whether the profiles work in the Hero. I'm curious myself. I do know the stock rom has everything locked, but since the kernel source has been released and Modaco released his kernel, I'm not so sure if the lock statement is true anymore.
I'm compiling a kernel as we speak with the cpu frequency scaling on. Had some issues with the cpufreq.h file not seeing two variables necessary for the userspace profile, but hopefully I was able to fix that (won't know until I run it).
Click to expand...
Click to collapse
im fairly positive that the CPU is getting stuck in the sleep mode while the rest of the phone is not, causing me these issues... the problem is i dont know how to fix them
dmc971989 said:
performance, and profiles are not enabled... again, it only happens after 12-15 hours or so... about once a day
Click to expand...
Click to collapse
Ok, modaco rom sets the governor to "performance" on boot. This essentially "sticks" your CPU to max throttle.
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Will tell you where you are, governor wise..
I'm not entirely sure what setCPU does, I've never used it, but I assume it just tweaks your top and bottom Mhz and maybe changes governor to performance when the screen is on? If it's configured properly? Maybe not, who knows?
If you want the best battery life, put the governor back to msm7k, it's a custom governor modified by HTC to make your battery last longer.
I changed the following line in modaco.sh:
echo "performance" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
to:
echo "msm7k" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_govern
and haven't noticed any slowdown from it.. my battery is lasting longer than it did on Stock or Fresh 1.1...

[Q] IS IT POSSIBLE?? pls help

I didnt want to root my phone HTC WILDFIRE because I am a little noob at these things a I thought I would totally destroy my phone.
But I found out that it is not so hard to root it as I thought, so today I succesfully rooted my phone. Than I wanted to overclock my procesor from 528 Mhz to I think 768 by downloading new kernel etc... Everything went good. I succesfully installed(or what, I said I am a little noob) that new kernel and was happy that my Wildfire will be faster.
But now I can see that my phone is lagging more, sometimes it freezes what i couldnt see before when It had original kernel.
HOW IS IT POSSIBLE?
Pls help
Do you have SetCPU installed? Then turn it a bit down, till 690~710 Mhz
Maxing it totally out can make your phone unstable. Think about it like a car, when it has 100 hp's and you tune it to 150 hp's things might break.
From stock 528 to 768 isn't a walk in the park, it's +45%
Yes I have setCPU and when I set my procesor to about 710 Mhz it lags and freezes. When I set it to about 580 it is doing the same. The only one solution of this I think is to reinstal the kernel.
Now I have 2.6.32.21-HCDRJacob-ga91 e 73b- [email protected] 1.
That is the full name of it. And in setcpu info it shows me before the version ( 2.6.32.21-HCDRJacob-ga91 e 73b- [email protected] 1) Linux versio... Maybe thats the problem???
And I have to find some solution as fast as possible because sometimes when somebody calls me I cant answer because of a biiiig lag. And then I cant do anything.
Thx for help
What id the minimum speed set to? I wouldn't go below 160. And my max is 672mhz.
Are you running different profiles or just the main profile in setCPU? Mine used to lag when i had a few profiles running but i have removed them all and only using the main profile and the lag has now gone.
when i went to wildpuzzle i found whatever speed i set my processor through set cpu it froze about 4-5 times a day. after flashing the kernel to remove overclocking it has not frozen in a week. everything really responsive, checking auto detect speeds with set cpu shows max 528mhz min450mhz
I tried many options and at last its OK. firstly I had a big difference between max and min of my procesor at setCPU, so I tried to set it to min about 630 and max about 700.
Now it is OK I dont know how, but I am happy the ****y problem is somehow solved and everytjing now goes very smoothly, thx u all
ephbee said:
when i went to wildpuzzle i found whatever speed i set my processor through set cpu it froze about 4-5 times a day. after flashing the kernel to remove overclocking it has not frozen in a week. everything really responsive, checking auto detect speeds with set cpu shows max 528mhz min450mhz
Click to expand...
Click to collapse
So what kernel did you flash it to?

[q] cm 7 rc1

Hi guys,
i tried CM7 but it was really laggy at my device, a lot of you guys said it is a very fast release !? so how can i get it working smooth ? when i wanted to get into the cpu settings i had a force close every time, jit was enabled..
do i have to get setcpu ? when yes where? which frequencies run smooth and stable ?
thanks in advance
eichl0r said:
Hi guys,
i tried CM7 but it was really laggy at my device, a lot of you guys said it is a very fast release !? so how can i get it working smooth ? when i wanted to get into the cpu settings i had a force close every time, jit was enabled..
do i have to get setcpu ? when yes where? which frequencies run smooth and stable ?
thanks in advance
Click to expand...
Click to collapse
Wipe EVERYTING, install CM7 then install HCDR.Kernal 4.1 (4.2 doesn't work as well) then use another overclock program, not setcpu, it doesn't work well with CM7. Hope that helps you!
* First, try flashing Kernel v4.1. CM7 comes with Kernel 4.2 by default, and, because it is clocked at 768 max, it leads to a lot of stability problems for everyone. Look for the HCDR.Kernel Topic in Wildfire Android Development Zone
* After that, you can install SetCPU. The SetCPU Dev has a thread here on XDA where he has posted the APK of SetCPU for download. Just enter SetCPU in the search bar and you should be able to find the thread with no issues. Here, you can set the max (Upto 710 recommended) and min (upto 245 recommended)
This should solve your lag and stability issues. If it still doesn;t, two more apps which can cause lag are (Note: This affects only a small %age of members with CM7)
* SetCPU (Alternative: OverclockWidget)
* ADW.Launcher (Alternative: Any other Launcher)
Oh, and CPU Settings FC's for everyone, from the time it was implemented. Looks like it is not ready yet.
Good Luck
hey 3xeno, thanks for your tipps!
with kernel 4.1 + setcpu + adw.launcher ex it finally works good!
the only thing thats a little strange is that i couldnt use my overclock setup from the openfire rom i had before, i have your suggested settings + screen of profile (352 max 245 min)+ tmep > 46° profile (352 max 245min), with openfire it was possible to have it at 691 mhz max and 245mhz min for normal mode, now i had to put it on 614 max 245min to not get the battery too warm, but anything else works great
eichl0r said:
hey 3xeno, thanks for your tipps!
with kernel 4.1 + setcpu + adw.launcher ex it finally works good!
the only thing thats a little strange is that i couldnt use my overclock setup from the openfire rom i had before, i have your suggested settings + screen of profile (352 max 245 min)+ tmep > 46° profile (352 max 245min), with openfire it was possible to have it at 691 mhz max and 245mhz min for normal mode, now i had to put it on 614 max 245min to not get the battery too warm, but anything else works great
Click to expand...
Click to collapse
That is rather weird, because, many are keeping it at 710 MHz Max and having no issues. What is your battery temperature when you keep it at 691? (And at idle. It is normal for the phone to get warm when you continuously run a heavy app like a game on it, also, I am sure you know this, but dont measure during charging, it does get pretty warm then )
hmm i played around with the phone a little and then put it in my pants pocket, after wa while when i put it back out it has restarted i guess and i was very warm at the back...hmm ill test it a little perhaps it was a one time thing

[Q] (Q) overclocking on cm10

hi i have successfully flashed cm10 and it has been running without problems but i tried overclocking using the bootloader but then i got stuck in a bootloop. this are the values 1200/58 900/44 600/31 300/21
If any one can help me it would be greatly appreciated, i am using the kernel is the installation guide on tezets cm10 post btw.THANKS
edit: i have solve the bootloop but my main question is how to overclock. thanks
I use the following values for over clock on CM10 (well on almost all ROMs that I use on MS2)
300 - 30, 600 - 45, 900 - 57, 1200 - 65
I do know that the vsel values are high and there are lower vsel overclock values out there but with these values I noticed that the CPU uses the 900 frequency more often than it does in lower vsel values settings.
I use these values from the bootmenu -> CPU settings
Load all modules -> Enabled
Status -> Enabled
Exit with save once you make changes to cpu values in the bootmenu.
haha ok thanks but i noticed that my phone heats up very quickly whenever i am using 3g any solutions or reasons behind this??
worldwork said:
haha ok thanks but i noticed that my phone heats up very quickly whenever i am using 3g any solutions or reasons behind this??
Click to expand...
Click to collapse
My phone has ALWAYS done this. Once i left 3g on all night and i could barely touch it in the morning
I think i just got a bad device
worldwork said:
haha ok thanks but i noticed that my phone heats up very quickly whenever i am using 3g any solutions or reasons behind this??
Click to expand...
Click to collapse
scottyn said:
My phone has ALWAYS done this. Once i left 3g on all night and i could barely touch it in the morning
I think i just got a bad device
Click to expand...
Click to collapse
It's a trait of the Milestone 2 to overheat a lot. In the stock battery cover for the Milestone 2, there is a 2-inch square amount of thermal paste under a plastic film. I believe this is to dissipate heat away from the battery, because of the overheating nature of the Milestone 2s. Furthmore from my own experience, when I use 3G or HSDPA my device overheats a lot as well. But, as turning cellular data boosts my battery by over 200% (I don't exaggerate - I have measured this) I keep it off unless I am out of range of a wifi network, where I have a small on/off widget to toggle it..
sahilarora911 said:
I use the following values for over clock on CM10 (well on almost all ROMs that I use on MS2)
300 - 30, 600 - 45, 900 - 57, 1200 - 65
I do know that the vsel values are high and there are lower vsel overclock values out there but with these values I noticed that the CPU uses the 900 frequency more often than it does in lower vsel values settings.
I use these values from the bootmenu -> CPU settings
Load all modules -> Enabled
Status -> Enabled
Exit with save once you make changes to cpu values in the bootmenu.
Click to expand...
Click to collapse
just asking how is ur battery life with this settings?
worldwork said:
just asking how is ur battery life with this settings?
Click to expand...
Click to collapse
Well I would say it is not too different from the other lower vsel values I have tried. The thing that I noticed is that with these settings, the phone tends to stay a lot even in 900 MHz zone which it does not do if vsel are low.
If vsel are too low, then the phone mostly stays in 1200 (when in use) n 300 (when idle). U can try n see for urself. This is just what I personally feel.

[GUIDE] Fastest way to properly undervolt your CPU

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?

Categories

Resources