Related
This thread should be a talk about the lowest possible voltage-levels which are well-known to be stable.
Background:
I'm using a Custom-ROM on my 'classic' Desire.
Nearly every Custom-ROM has a specialized Linux-kernel with "OCUV"-Feature.
(For those, who don't know what this means: OverClock/UnderVoltage )
With OC you can speed-up you Device.
Normally, the Desire has a maximum CPU-Clock of 998 MHz.
Most custom kernels offer an OC up to 1'113 MHz (+11%), some even go up to 1'190 Mhz (+19%).
The UV-Feature enables you to reduce the voltage of the CPU.
So you can save battery (longer stand-by)
or 'protect' your CPU from getting too hot while using CPU-intensive Apps or using Overclocking.
The HTC-Desire-CPU can work with these discrete CPU-clocks (MHz):
Official: 128,245,384,422,460,499,537,576,614,652,691,729,768,806,844,883,921,960,998
Overclocked: 1036,1075,1113 (or even more...)
The concrete CPU-Clock is chosen by a so called CPU-governor, according to the current requirements:
Normally, when the screen is turned of, then the CPU-clock is limited to 245 MHz. Even if your screen is on but you do nothing that looking on a steady-home-screen, your CPU-clock will be low. But when you do somthing (starting an App, playing a game...), then your CPU-clock wile rise (more or less quickly) up to the maximum-clock and will fall down again when your devices idles again.
Additionally there is a table which defines the conrete CPU-voltage-level for every single CPU-clock-speed. There are factory-default-values for this table (see table below). With the UV-Feature (Undervoltage) you can change this table, normally to lower voltage-levels (there is no need to increase the voltage).
But there are limits for UV: If the voltage for a specific CPU-clock drops under a CPU-model-specific value, then the CPU makes sudden calculation-errors and the software (your App or the whole Android-OS) get's unstable and crashes and you have to reboot yout phone.
Perhaps you even have to remove the battery because the device doesn't react on your Power-Button-Presses any more.
But: A (permanent) defect to your hardware is unlikely.
To start-over i present the result of some intensive tests i made with my device:
Code:
MHz Default(mV) Still-ok(mV) CRASH(mV)
128 975 825 800 (thx to rootSU)
245 1000 850 825
384 1025 850 825
422 1050 850 825
460 1050 875 (not yet tested)
499 1075 900 875
537 1075 925 (not yet tested)
576 1100 950 925
614 1100 950 (not yet tested)
652 1125 975 950
691 1150 1000 (not yet tested)
729 1175 1025 1000
768 1200 1025 (not yet tested)
806 1225 1050 1025
844 1250 1075 (not yet tested)
883 1275 1100 (not yet tested)
921 1275 1125 1100
960 1275 1150 (not yet tested)
998 1275 1175 1150
1036 1275 1200 (not yet tested)
1075 1275 1225 (not yet tested)
1113 1275 1225 1200
The voltages between my test-steps can easily be interpolated (for now).
To these 'min-but-still-ok-values' i added a 'stability-supplement' of 50mV and set up my device accordingly. I use the App "OC/UC Beater2" for this.
Now it's running for some days with no crashes. So far i can say: it's stable.
I would like to see other users to test these values and give a response here in this thread (dont's forget to add 50mV!!!!!).
Later (in a few days or weeks) i will suggest to reduce the table-values by 25mV and the cimmunity tests again.
Hope to get some responses. Thx.
oli.henning said:
Code:
MHz Default(mV) Still-ok(mV)
128 975 800
Click to expand...
Click to collapse
This is ultra-extreme IMHO. I've not heard of anyone getting below 825 until now. I managed 850 for a while, but is happiest at 875
rootSU said:
This is ultra-extreme IMHO. I've not heard of anyone getting below 825 until now. I managed 850 for a while, but is happiest at 875
Click to expand...
Click to collapse
I haven't got any problems with 800, yet (I use it since june - so it should be stable )
Why don't you use a havs kernel - you could also lower the min mV to 800 for more frequencies and it's still stable because of the max mV (you can also decrease them)
PS: I'm using the vipermod
rootSU said:
This is ultra-extreme IMHO. I've not heard of anyone getting below 825 until now. I managed 850 for a while, but is happiest at 875
Click to expand...
Click to collapse
Motivated by your post i tested again with [email protected] - and you are right.
A little more intensive tests and my Desire crashed with this VDD-Level.
Perhaps it also has something to do with the CPU-Temerature.
Anyway - i will adjust the table in the first post accordingly and set the 'stable' VDD-Level to 825mv
Go on, community, such posts are what i hope to see
_Balu said:
I haven't got any problems with 800, yet (I use it since june - so it should be stable )
Why don't you use a havs kernel - you could also lower the min mV to 800 for more frequencies and it's still stable because of the max mV (you can also decrease them)
Click to expand...
Click to collapse
Hmm, i never tried a HAVS-Kernel.
But for now i want to stay at SVS for the next few weeks, simply to stabilize the table in Post#1.
_Balu said:
I haven't got any problems with 800, yet (I use it since june - so it should be stable )
Why don't you use a havs kernel - you could also lower the min mV to 800 for more frequencies and it's still stable because of the max mV (you can also decrease them)
PS: I'm using the vipermod
Click to expand...
Click to collapse
I am using HAVS with AXI. 875-950 for 128, I dont need vipermod. init.d script works fine for me.
Mine PVT-3 was able to run with 875 mV on all official frequencies. Dunno if my "new" PVT-1 can do that as well.
Terepin said:
Mine PVT-3 was able to run with 875 mV on all official frequencies. Dunno if my "new" PVT-1 can do that as well.
Click to expand...
Click to collapse
Wow, that's far, far away from what i observed.
There is absolutly no chance to run on 875mV @998MHz.
Are you really sure about your setting?
_Balu said:
Why don't you use a havs kernel - you could also lower the min mV to 800 for more frequencies and it's still stable because of the max mV
Click to expand...
Click to collapse
Another poster claimed that a HAVS kernel will adaptively adjust the voltage based on both speed and temp. What I'm not clear on is how these voltages are set. Is the kernel using a table like the OP has, does it predict the stable voltage based on actual performance of the phone in use, or do I completely not understand?
I've seen a few 'I think...' explanations but nothing definitive.
oli.henning said:
Wow, that's far, far away from what i observed.
There is absolutly no chance to run on 875mV @998MHz.
Are you really sure about your setting?
Click to expand...
Click to collapse
Yep, I was using this kernel: http://neophyte.vipme.com/ftp/_Extras/NeoPhyTe-2.6.32.28-Halcyon_HAVS.875Esp_CFS_SLQB_VR_v38.zip
oli.henning said:
This thread should be a talk about the lowest possible voltage-levels which are well-known to be stable.
I would like to see other users to test these values and give a response here in this thread (dont's forget to add 50mV!!!!!).
Later (in a few days or weeks) i will suggest to reduce the table-values by 25mV and the cimmunity tests again.
Hope to get some responses. Thx.
Click to expand...
Click to collapse
Hi oli.henning,
Thanks for sharing those values, I'm noob in setting voltages and cpu frequencies and found your post very useful.
I've tried the still ok settings adding 25 mv for several days and everything was ok, now I reduce all settings -25mv, so ussing the still ok just as it is and working, no fc yet.
Thanks a lot man!
I have a stock Tmobile ROM, I rooted the phone.
Can I use the bullet kernel with it?
Yes you can use any though I don't see why you would want to use the Bullet kernel. Not to say that its not good but it hasn't been updated in a long time and all the current ones are better performance-wise.
the bullet was good when I had the vibrant. I woild like to try it again with the S2
Sent from my SGH-T989 using XDA
But you upgraded your phone right? Maybe it's time to upgrade your kernel too
(darkside kernel's the best of the best)
yoft1 said:
But you upgraded your phone right? Maybe it's time to upgrade your kernel too
(darkside kernel's the best of the best)
Click to expand...
Click to collapse
I think Eugene's kernel is one of the best but I just say that because I haven't really given dark sides to much of an opportunity. I'm guessing that's the same with you and Eugene's kernel
Sent from my SGH-T989 using Tapatalk
darkside is def beast!
kiingJ said:
darkside is def beast!
Click to expand...
Click to collapse
I'm actually gonna give it a go for a couple of days and see how that works out for me. What are your settings?
iLeopard said:
I think Eugene's kernel is one of the best but I just say that because I haven't really given dark sides to much of an opportunity. I'm guessing that's the same with you and Eugene's kernel
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Guilty as charged! I gave macnut a twirl but LG is not really to my liking and so I never got to use streamline again. But with darkside I'm running it underclocked @1.35Ghz and undervolted by -112.5mV. Your mileage will vary with how much you can undervolt it and get away with it.
yoft1 said:
Guilty as charged! I gave macnut a twirl but LG is not really to my liking and so I never got to use streamline again. But with darkside I'm running it underclocked @1.35Ghz and undervolted by -112.5mV. Your mileage will vary with how much you can undervolt it and get away with it.
Click to expand...
Click to collapse
K so I know how to under clock but I'm a noob with undervolting. Do I have to under volt the amount you said to all the frequencies?
iLeopard said:
K so I know how to under clock but I'm a noob with undervolting. Do I have to under volt the amount you said to all the frequencies?
Click to expand...
Click to collapse
Start with -50mV across the board and work your way down from there to see how your phone reacts. I have Darksides ROM at Min 384/Max 1.51GHz and undervolted at -50mV across the board and it works quite well. I might give -100mV a shot to see how it goes.
Jdom58 said:
Start with -50mV across the board and work your way down from there to see how your phone reacts. I have Darksides ROM at Min 384/Max 1.51GHz and undervolted at -50mV across the board and it works quite well. I might give -100mV a shot to see how it goes.
Click to expand...
Click to collapse
Yesssir I'll give that a go. I'll update later, the minimum for each frequency is 800mV correct? At -50 I have the first bottom five at 800mV
iLeopard said:
Yesssir I'll give that a go. I'll update later, the minimum for each frequency is 800mV correct? At -50 I have the first bottom five at 800mV
Click to expand...
Click to collapse
You can technically go lower than 800 but it was posted at one point that any lower than that causes more battery drain than it saves (I'm not sure why though). Things to look for when you're undervolting: if you're off the mark by more than 2-3 steps (12.5mV per step), your phone will reboot on the spot. If you're off by just one step, your phone well generally work fine but will randomly reboot on occasion. For me, if I go to -125 and I leave my phone alone for around 20 min it will reboot. But I get no reboots at 112.5.
Something to keep in mind though: undervolting isn't linear which means that while my 112.5 works for my underclocked processor at 1.3GHz, it doesn't work at 1.7 GHz. The higher you run your processor the less you can globally undervolt.
yoft1 said:
You can technically go lower than 800 but it was posted at one point that any lower than that causes more battery drain than it saves (I'm not sure why though). Things to look for when you're undervolting: if you're off the mark by more than 2-3 steps (12.5mV per step), your phone will reboot on the spot. If you're off by just one step, your phone well generally work fine but will randomly reboot on occasion. For me, if I go to -125 and I leave my phone alone for around 20 min it will reboot. But I get no reboots at 112.5.
Something to keep in mind though: undervolting isn't linear which means that while my 112.5 works for my underclocked processor at 1.3GHz, it doesn't work at 1.7 GHz. The higher you run your processor the less you can globally undervolt.
Click to expand...
Click to collapse
Okay cool I'll keep that in mind. I'm on stock frequency at 1.51GHz and at -50mV. So far so good, I'll give it like 2-3 marks less later and see how that works. Thanks again for your help
iLeopard said:
Okay cool I'll keep that in mind. I'm on stock frequency at 1.51GHz and at -50mV. So far so good, I'll give it like 2-3 marks less later and see how that works. Thanks again for your help
Click to expand...
Click to collapse
Here's the full list of what the default voltages are, work your way down from there.
(Mhz/Ghz) - (mV)
192 - 800
310 - 825
384 - 825
432 - 850
486 - 850
540 - 875
594 - 875
648 - 900
702 - 900
756 - 925
810 - 975
864 - 975
918 - 1000
972 - 1025
1.02 - 1025
1.08 - 1050
1.13 - 1075
1.18 - 1100
1.24 - 1125
1.29 - 1150
1.35 - 1150
1.4 - 1175
1.45 - 1200
1.51 - 1225
1.62 - 1250
1.67 - 1275
1.72 - 1300
1.78 - 1312.5
Jdom58 said:
Here's the full list of what the default voltages are, work your way down from there.
(Mhz/Ghz) - (mV)
192 - 800
310 - 825
384 - 825
432 - 850
486 - 850
540 - 875
594 - 875
648 - 900
702 - 900
756 - 925
810 - 975
864 - 975
918 - 1000
972 - 1025
1.02 - 1025
1.08 - 1050
1.13 - 1075
1.18 - 1100
1.24 - 1125
1.29 - 1150
1.35 - 1150
1.4 - 1175
1.45 - 1200
1.51 - 1225
1.62 - 1250
1.67 - 1275
1.72 - 1300
1.78 - 1312.5
Click to expand...
Click to collapse
Thanks much for this, I undervolted too much and now my battery is draining like crazy. I was at -100mV and was fixing to flash the kernel all over again, saved me a good 5 minutes thanks
I made a function to calculate voltages for the Google Nexus
As a minimum voltage I found for stock 840mv always.
Best stable undervolt for everyone start from 800mv
840-1000-1090-1200mv
--> VOLTAGE = 733.9031364956^(0.0004200816*FREQUENCY)
REQ= MIN FREQUENCY = 800
Results in table:
MARGIN OFFSET APPLIED: -40mv
350MHz - 800mv
700 - 945
920 - 1040
1200 - 1175
1350 - 1254
1400 - 1281
1500 - 1338
1600 - 1388
Please test the settings and post back here. I believe these are stable for everyone.
I am experimenting to try pushing these into the CM10 repositories.
Not every phone under volts the same
Sent from my Galaxy Nexus using xda premium
The standard setting for 1190 MHz with Trinity kernel is 1150 mV, and it's solid as a rock for many users. That would fit right into your chart easily, so that's at least some confirmation of its accuracy.
I'll test 800 mV @ 307 MHz, and 945 mV @ 691 MHz. Those are lower than Trinity's defaults of 850 mV and 1000 mV for those frequencies.
No immediate problems but I'll leave it this way and see what happens.
Smallsmx3 said:
Not every phone under volts the same
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
that's why we could use the function:
VOLTAGE = 733.9031364956^(0.0004200816*FREQUENCY) + MARGIN
I am currently thinking about rewriting something for the Google Nexus
Let's disable Smart Reflex.
Replace it with stock voltages generated by this curve found by the frequencies the MPU runs at.
No need to program voltages!
Next is the availability of a voltage_margin value which users can modify with the android terminal emulator or a script.
How would you guys like this? This will make undervolting easier. Maybe little more limited but undervolting shouldn't take so much time in my opinion. You can't undervolt a Sandy Bridge CPU for each frequency separately. So why should phones.
Please let me know if you guys would like this feature. Then I will start developing.
GOALS:
- Making undervolting easy for everyone!
- Consumes less time!
I'd really appreciate and use this feature! I hate looking for Voltages again and again. Calculating them would be much more comfortable!
I use Franco.Kernel with Voltages from 230 to 1804 MHz and I tried to calculate the Voltages with your funktion within an excel-sheet. But my results are so damn far away from a realistic Voltage...
For example for 700MHz I get the Voltage "6,96"
I took this:
VOLTAGE = 733,9031364956^(0,0004200816*FREQUENCY)
put in the frequency:
VOLTAGE = 733,9031364956^(0,0004200816*700) = 733,9031364956 ^ 0,29405712 = 6,9608371895070636295467507606432
VOLTAGE = 6,9608371895070636295467507606432
Where's my mistake?
This sounds like a great idea, I hate trying to undervolt my phone cause I feel like I end up doing too much and start ruining the experience with ROMs so I stopped altogether.
I Like The Idea Of Making It Simple But every Single CPU Is Different And OC Differently And Will UV Differently. Even with Different Kernels And Roms You Will Have Different Results.
I Do Applaud Your Efforts but The Only Way To see How Low You Can Go Is To set It And Test It.
It Will Either Run Or It Won't, You Can't Really Harm Your CPU With UV'ing Like With OC'ing.
Sorry About The Capitals, Only Way My Phone Does It On Here I Guess
t-rip said:
I'd really appreciate and use this feature! I hate looking for Voltages again and again. Calculating them would be much more comfortable!
I use Franco.Kernel with Voltages from 230 to 1804 MHz and I tried to calculate the Voltages with your funktion within an excel-sheet. But my results are so damn far away from a realistic Voltage...
For example for 700MHz I get the Voltage "6,96"
I took this:
VOLTAGE = 733,9031364956^(0,0004200816*FREQUENCY)
put in the frequency:
VOLTAGE = 733,9031364956^(0,0004200816*700) = 733,9031364956 ^ 0,29405712 = 6,9608371895070636295467507606432
VOLTAGE = 6,9608371895070636295467507606432
Where's my mistake?
Click to expand...
Click to collapse
+1 ...But look awesone this idea!!
Cheers!
Great idea. Why you don't put directly a Google/Excel sheet?
Hi there! It's been 3 days I own a beautiful GT-N7100
I immediately rooted it, installed Perseus Kernel and started playing around with some undervolt - overclock.
From what I understood from my continuos benchmarking efforts, going over 533 MHZ for the gpu is useless, as it throttles immediately, and sometimes it even kills the performance.
So, regarding the GPU, this is the setting:
160 Mhz - 825 mV ---> MIN
266 Mhz - 875 mV
350 Mhz - 950 mV
440 Mhz - 1000 mV
533 Mhz - 1025 mV ---> MAX
It looks to be stable. Now, this is the CPU:
1800 Mhz - 1250 mV ---> MAX
1704 Mhz - 1225 mV
1600 Mhz - 1150 mV
1500 Mhz - 1125 mV
1400 Mhz - 1075 mV
1300 Mhz - 1025 mV
1200 Mhz - 1000 mV
1100 Mhz - 1000 mV
1000 Mhz - 975 mV
900 Mhz- 950 mV
800 Mhz - 925 mV
700 Mhz - 900 mV
600 Mhz - 875 mV
500 Mhz - 850 mV
400 Mhz - 825 mV
300 Mhz - 800 mV
200 Mhz - 775 mV ---> MIN
You may be wondering "Ok, so what's the problem?" As the title says, the CPU has the bad (or good, as it prevents itself from frying) habit of throttling all the way down to 800 mhz whenever its temp hits 80°C
This happens extremely fast @1,8 ghz, so fast that I wasn't even able to determine for sure the temp it hit before throttling.
@ 1,7 ghz it takes a bit more, but the end result is the same when it hits exactly 80° (it doesn't go over)
@ 1,6 ghz is stable, it never goes over 75°.
It looks that every 100 mhz I have a 5 ° increase in temp. It's not good for sure, and as far as I'm concerned is too much of an increase.
Should I further undervolt the top two frequency scales?
EDIT
Tried 1,8 ghz @ 1175 and 1,7 ghz @ 1175 and still the same s... you know what.
Or better said, it's a bit different:
1,8ghz @ 1175 takes more time to go to 80° C, but it still does.
1,7 ghz @1175 stays at 75° C, but the stupid pig throttles to 1 GHZ this time...
Any ideas?
4l3xXx said:
Hi there! It's been 3 days I own a beautiful GT-N7100
I immediately rooted it, installed Perseus Kernel and started playing around with some undervolt - overclock.
From what I understood from my continuos benchmarking efforts, going over 533 MHZ for the gpu is useless, as it throttles immediately, and sometimes it even kills the performance.
So, regarding the GPU, this is the setting:
160 Mhz - 825 mV ---> MIN
266 Mhz - 875 mV
350 Mhz - 950 mV
440 Mhz - 1000 mV
533 Mhz - 1025 mV ---> MAX
It looks to be stable. Now, this is the CPU:
1800 Mhz - 1250 mV ---> MAX
1704 Mhz - 1225 mV
1600 Mhz - 1150 mV
1500 Mhz - 1125 mV
1400 Mhz - 1075 mV
1300 Mhz - 1025 mV
1200 Mhz - 1000 mV
1100 Mhz - 1000 mV
1000 Mhz - 975 mV
900 Mhz- 950 mV
800 Mhz - 925 mV
700 Mhz - 900 mV
600 Mhz - 875 mV
500 Mhz - 850 mV
400 Mhz - 825 mV
300 Mhz - 800 mV
200 Mhz - 775 mV ---> MIN
You may be wondering "Ok, so what's the problem?" As the title says, the CPU has the bad (or good, as it prevents itself from frying) habit of throttling all the way down to 800 mhz whenever its temp hits 80°C
This happens extremely fast @1,8 ghz, so fast that I wasn't even able to determine for sure the temp it hit before throttling.
@ 1,7 ghz it takes a bit more, but the end result is the same when it hits exactly 80° (it doesn't go over)
@ 1,6 ghz is stable, it never goes over 75°.
It looks that every 100 mhz I have a 5 ° increase in temp. It's not good for sure, and as far as I'm concerned is too much of an increase.
Should I further undervolt the top two frequency scales?
EDIT
Tried 1,8 ghz @ 1175 and 1,7 ghz @ 1175 and still the same s... you know what.
Or better said, it's a bit different:
1,8ghz @ 1175 takes more time to go to 80° C, but it still does.
1,7 ghz @1175 stays at 75° C, but the stupid pig throttles to 1 GHZ this time...
Any ideas?
Click to expand...
Click to collapse
80°C?
At that temperature your hands would be frying. You must have confused with computer.
this is XXXDDDAAA
UtkarshGupta said:
80°C?
At that temperature your hands would be frying. You must have confused with computer.
this is XXXDDDAAA
Click to expand...
Click to collapse
No man its common when u started benchmark at 1800mhz -1900mhz wid max mv cpu throttle to 80° and cpu sets automatically to 800mhz :lol:
Sent from my GT-N7100 using xda premium
---------- Post added at 01:11 PM ---------- Previous post was at 01:02 PM ----------
4l3xXx said:
Hi there! It's been 3 days I own a beautiful GT-N7100
I immediately rooted it, installed Perseus Kernel and started playing around with some undervolt - overclock.
From what I understood from my continuos benchmarking efforts, going over 533 MHZ for the gpu is useless, as it throttles immediately, and sometimes it even kills the performance.
So, regarding the GPU, this is the setting:
160 Mhz - 825 mV ---> MIN
266 Mhz - 875 mV
350 Mhz - 950 mV
440 Mhz - 1000 mV
533 Mhz - 1025 mV ---> MAX
It looks to be stable. Now, this is the CPU:
1800 Mhz - 1250 mV ---> MAX
1704 Mhz - 1225 mV
1600 Mhz - 1150 mV
1500 Mhz - 1125 mV
1400 Mhz - 1075 mV
1300 Mhz - 1025 mV
1200 Mhz - 1000 mV
1100 Mhz - 1000 mV
1000 Mhz - 975 mV
900 Mhz- 950 mV
800 Mhz - 925 mV
700 Mhz - 900 mV
600 Mhz - 875 mV
500 Mhz - 850 mV
400 Mhz - 825 mV
300 Mhz - 800 mV
200 Mhz - 775 mV ---> MIN
You may be wondering "Ok, so what's the problem?" As the title says, the CPU has the bad (or good, as it prevents itself from frying) habit of throttling all the way down to 800 mhz whenever its temp hits 80°C
This happens extremely fast @1,8 ghz, so fast that I wasn't even able to determine for sure the temp it hit before throttling.
@ 1,7 ghz it takes a bit more, but the end result is the same when it hits exactly 80° (it doesn't go over)
@ 1,6 ghz is stable, it never goes over 75°.
It looks that every 100 mhz I have a 5 ° increase in temp. It's not good for sure, and as far as I'm concerned is too much of an increase.
Should I further undervolt the top two frequency scales?
EDIT
Tried 1,8 ghz @ 1175 and 1,7 ghz @ 1175 and still the same s... you know what.
Or better said, it's a bit different:
1,8ghz @ 1175 takes more time to go to 80° C, but it still does.
1,7 ghz @1175 stays at 75° C, but the stupid pig throttles to 1 GHZ this time...
Any ideas?
Click to expand...
Click to collapse
Hey Mate
mine is exactly same mv for cpus and gpu....
Mine cpu didn't throttle ....
When I start benchmark at 1800mhz mine cpu goes max 75°c
And I got 19400+ Score in Anutu bench.
Sent from my GT-N7100 using xda premium
hellDr0id said:
No man its common when u started benchmark at 1800mhz -1900mhz wid max mv cpu throttle to 80° and cpu sets automatically to 800mhz :lol:
Sent from my GT-N7100 using xda premium
---------- Post added at 01:11 PM ---------- Previous post was at 01:02 PM ----------
Hey Mate
mine is exactly same mv for cpus and gpu....
Mine cpu didn't throttle ....
When I start benchmark at 1800mhz mine cpu goes max 75°c
And I got 19400+ Score in Anutu bench.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Not all cpus are created equal.
this is XXXDDDAAA
4l3xXx said:
Hi there! It's been 3 days I own a beautiful GT-N7100
I immediately rooted it, installed Perseus Kernel and started playing around with some undervolt - overclock.
From what I understood from my continuos benchmarking efforts, going over 533 MHZ for the gpu is useless, as it throttles immediately, and sometimes it even kills the performance.
So, regarding the GPU, this is the setting:
160 Mhz - 825 mV ---> MIN
266 Mhz - 875 mV
350 Mhz - 950 mV
440 Mhz - 1000 mV
533 Mhz - 1025 mV ---> MAX
It looks to be stable. Now, this is the CPU:
1800 Mhz - 1250 mV ---> MAX
1704 Mhz - 1225 mV
1600 Mhz - 1150 mV
1500 Mhz - 1125 mV
1400 Mhz - 1075 mV
1300 Mhz - 1025 mV
1200 Mhz - 1000 mV
1100 Mhz - 1000 mV
1000 Mhz - 975 mV
900 Mhz- 950 mV
800 Mhz - 925 mV
700 Mhz - 900 mV
600 Mhz - 875 mV
500 Mhz - 850 mV
400 Mhz - 825 mV
300 Mhz - 800 mV
200 Mhz - 775 mV ---> MIN
You may be wondering "Ok, so what's the problem?" As the title says, the CPU has the bad (or good, as it prevents itself from frying) habit of throttling all the way down to 800 mhz whenever its temp hits 80°C
This happens extremely fast @1,8 ghz, so fast that I wasn't even able to determine for sure the temp it hit before throttling.
@ 1,7 ghz it takes a bit more, but the end result is the same when it hits exactly 80° (it doesn't go over)
@ 1,6 ghz is stable, it never goes over 75°.
It looks that every 100 mhz I have a 5 ° increase in temp. It's not good for sure, and as far as I'm concerned is too much of an increase.
Should I further undervolt the top two frequency scales?
EDIT
Tried 1,8 ghz @ 1175 and 1,7 ghz @ 1175 and still the same s... you know what.
Or better said, it's a bit different:
1,8ghz @ 1175 takes more time to go to 80° C, but it still does.
1,7 ghz @1175 stays at 75° C, but the stupid pig throttles to 1 GHZ this time...
Any ideas?
Click to expand...
Click to collapse
Your experience is exactly the same as mine. Even with undervolting I still hit the throttle range at 1.7 and 1.8.
I concluded that overclocking only really gave me an advantage in the benchmarks and braging rights department. If I was playing a game it was pointless as after a while I hit the throttle limit. In end I went back to 1.6 ghz, and I'm more than happy with the performance. :good:
Hi there, thank you for being interested in my situation. After playing around with the values, recovering from bootloops, freezes and instabilities, I came to a strange conclusion, which I would like to share with all of you, in case someone is living in my very same situation.
It looks like the voltage was not too high (causing the heat), it was rather too low. It looked, after some studies, that the cpu throttled not because its temp was too high (it sometimes throttled at 55°, and other times was not throttling at 80 ° ). So this is what I understood:
- Voltage was so low that it not only caused random lag spikes, both in games and in the UI as well (as I was also wondering why in the hell NFS was running worse than before), it caused the cpu to throttle itself to the highest step with enough voltage to support the demand (800 mhz, or 1 GHZ, at first). So I tried putting very low voltages on all steps, except on 1.8 ghz (I was on performance) and default voltage on the 1,2 ghz step, and it soon throttled to 1,2.
- GPU voltage is OK.
- Yesterday the CPU was going all the way up to 75 and also 80 degrees not only because it was charging, also because it was near my laptop's vent, stupid me :angel:
I know this makes no sense, but it is known that very low voltages prove to be unstable, but I couldn't think they could prove SO MUCH unstable.
The results now are these:
- 19k in Antutu
- 8k in Quadrant
- 60 fps on Basemark Taijii.
- 20 minutes of stability test, with over 170 gpu passes and 45 cpu passes, and no throttling at all (always 1.8 ghz).
I'm trying to play some NFS:MW later this afternoon, just giving the phone some time to charge, it's been a hard day for it
Any comments will clearly be appreciated. I'll come soon with my current voltages to share with you
And, by the way, I love this phone, I'm having sex with it this night
Good work, 4l3xXx :good: Will wait for your conclusions and voltages
Btw how do you know your phone was throttled?
this is XXXDDDAAA
I guess by watching frequency in stability test app - for me sometimes it drops from 1800 to some lower freq for a second. How much do you guys overclock GPU?
Here's my more performance oriented settings. Averages 19500 on Antutu, and 7400 on Quadrant Standard (Advanced version adds 1000 to score) This doesn't lag at all between screens, animations, etc. The only lag I've seen is when my apps rarely crash.
CPU Max - 1800mHz
CPU Min - 200mHz
Voltages from OP
Pegasusq governor
Sampling Rate - 15000uS
Sampling Down Factor - 1
Up Threshold - 90%
Down Differential - 10%
Frequency for Responsiveness - 600mHz
Up Threshold @ Min Freq - 60%
Frequency at Fast Down - 1400mHz
Up Threshold at Fast Down - 94%
Frequency Step - 25%
Up Threshold Differential - 5%
Frequency Step Decrease - 10%
Flexrate Enabled - 700mHz, 10000uS
CPU Up Rate - 8 samples
CPU Down Rate - 10 samples
Core Upbring Count - 1
*Default Configuration Overrides*
1 Core to Online - 300mHz
2 Cores to Offline - 200mHz
2 Cores to Online - 400mHz
3 Cores to Offline - 300mHz
3 Cores to Online - 500mHz
4 Cores to Offline - 400mHz
*Runqueue Depths*
1 Core to Online - 155
2 Cores to Offline - 155
2 Cores to Online - 250
3 Cores to Offline - 250
3 Cores to Online - 340
4 Cores to Offline - 340
CPU Online Load Bias - 2 cores
CPU Online Bias Up Threshold - 50%
CPU Online Bias Down Threshold - 30%
GPU Max - 733mHz
GPU Min - 160mHz
Up Threshold - 85%
Down Differential - 5%
Utilization Timeout - 25ms
Voltages from OP
Internal/SD Card Schedulers - SIO
Internal/SD Card Read Ahead - 2048kB
Dynamic FSync - Enabled
And battery?
this is XXXDDDAAA
UtkarshGupta said:
And battery?
this is XXXDDDAAA
Click to expand...
Click to collapse
Battery works like charm =D Do give it a try and you can always set it back to default if it doesn't work the way you want it.
ahkiongkc said:
Battery works like charm =D Do give it a try and you can always set it back to default if it doesn't work the way you want it.
Click to expand...
Click to collapse
Works like a charm... Lol what a troll.
Anyways how much Screen on time do you get?
this is XXXDDDAAA
UtkarshGupta said:
And battery?
this is XXXDDDAAA
Click to expand...
Click to collapse
UtkarshGupta said:
Works like a charm... Lol what a troll.
Anyways how much Screen on time do you get?
this is XXXDDDAAA
Click to expand...
Click to collapse
I was a heavy user and before the mod, i got only 16 hours before it goes totally flat. Now after the changes, i manage to squeeze up till 23 hours until it hit 1%. Ill try to screenshot tonight and post it up here.
ahkiongkc said:
Here's my more performance oriented settings. Averages 19500 on Antutu, and 7400 on Quadrant Standard (Advanced version adds 1000 to score) This doesn't lag at all between screens, animations, etc. The only lag I've seen is when my apps rarely crash.
CPU Max - 1800mHz
CPU Min - 200mHz
Voltages from OP
Pegasusq governor
Sampling Rate - 15000uS
Sampling Down Factor - 1
Up Threshold - 90%
Down Differential - 10%
Frequency for Responsiveness - 600mHz
Up Threshold @ Min Freq - 60%
Frequency at Fast Down - 1400mHz
Up Threshold at Fast Down - 94%
Frequency Step - 25%
Up Threshold Differential - 5%
Frequency Step Decrease - 10%
Flexrate Enabled - 700mHz, 10000uS
CPU Up Rate - 8 samples
CPU Down Rate - 10 samples
Core Upbring Count - 1
*Default Configuration Overrides*
1 Core to Online - 300mHz
2 Cores to Offline - 200mHz
2 Cores to Online - 400mHz
3 Cores to Offline - 300mHz
3 Cores to Online - 500mHz
4 Cores to Offline - 400mHz
*Runqueue Depths*
1 Core to Online - 155
2 Cores to Offline - 155
2 Cores to Online - 250
3 Cores to Offline - 250
3 Cores to Online - 340
4 Cores to Offline - 340
CPU Online Load Bias - 2 cores
CPU Online Bias Up Threshold - 50%
CPU Online Bias Down Threshold - 30%
GPU Max - 733mHz
GPU Min - 160mHz
Up Threshold - 85%
Down Differential - 5%
Utilization Timeout - 25ms
Voltages from OP
Internal/SD Card Schedulers - SIO
Internal/SD Card Read Ahead - 2048kB
Dynamic FSync - Enabled
Click to expand...
Click to collapse
Copy Cat :lol: Trolled
. . . This post was written by someone else in Verizon Note 2 section
I forgot his name
Sent from my GT-N7100 using xda premium
ahkiongkc said:
I was a heavy user and before the mod, i got only 16 hours before it goes totally flat. Now after the changes, i manage to squeeze up till 23 hours until it hit 1%. Ill try to screenshot tonight and post it up here.
Click to expand...
Click to collapse
I mean screen on.
this is XXXDDDAAA
Alright, I can tell you it was being throttled because I was running the System Tuner app. By the way, I thought I won too early. For some reason my phone still throttled, with voltage having been decreased only by 50 mV on all cpu steps and by 100 mV on all GPU steps. It also throttled on 1.6 ghz max. Stock voltages just made the process be slower. Stability test was perfect as I told you, but Nfs MW seems to be heavier than the test itself. I came to the conclusion it was time to switch from Perseus to Neak. So far so good, running at stock voltages and everything runs way smoother, the damn game as well. Battery isn't that good with stock voltages, also considering that kernel's voltages are way higher than sammy's defaults. I am trying undervolt again on this kernel, without touching the clocks, and will report back, starting with -150 mV on the gpu (the 160 mhz step is @ 950 LOL)
EDIT;
This phone is becoming extremely stupid and is starting to seriously piss me off. I can't do sh... because it throttles. Undervolted and throttlrs, downclocked and throttles, overvolted and throttles, someone please tell me what the HELL is going on before I throw it out of the window.
hmm, I saw somewhere someone mentioned that battery temperature at 36 degrees is throttling down, but I don't know. I think its worth to try and monitor battery temp also.
4l3xXx said:
Alright, I can tell you it was being throttled because I was running the System Tuner app. By the way, I thought I won too early. For some reason my phone still throttled, with voltage having been decreased only by 50 mV on all cpu steps and by 100 mV on all GPU steps. It also throttled on 1.6 ghz max. Stock voltages just made the process be slower. Stability test was perfect as I told you, but Nfs MW seems to be heavier than the test itself. I came to the conclusion it was time to switch from Perseus to Neak. So far so good, running at stock voltages and everything runs way smoother, the damn game as well. Battery isn't that good with stock voltages, also considering that kernel's voltages are way higher than sammy's defaults. I am trying undervolt again on this kernel, without touching the clocks, and will report back, starting with -150 mV on the gpu (the 160 mhz step is @ 950 LOL)
EDIT;
This phone is becoming extremely stupid and is starting to seriously piss me off. I can't do sh... because it throttles. Undervolted and throttlrs, downclocked and throttles, overvolted and throttles, someone please tell me what the HELL is going on before I throw it out of the window.
Click to expand...
Click to collapse
That could be reason, I mean, undervolted throttles because of too low voltage, stock voltage throttles because of what? CPU temp? Hell no! 60 ° the max I reached with stock voltages and stock clocks, and still throttles? There HAS to be something else going on.
I also read something about the battery here on xda, from the thread I actually took my previous voltages from. It was saying 41° was the battery temp that once reached would throttle everything. The guy also said it is a "security" protocol that's present only on Sammy ROMS.
I actually think the temp is way lower than 41°, because I can tell for sure the battery doesn't reach 41° at ALL, so your 36° info may be totally right.
Changing ROM might be an idea I guess, if the "security protocol" stuff is right. I'm eventually switching to Omega ROM, I've seen a lot of people with it.
I'm actually monitoring the battery temp right now while I play that stupid NFS game. I'll report back as soon as something happens.
Keep in mind my actual voltages are as follows (NEAK defaults)
1600 @ 1313 mV
1500 @ 1263 mV
1400 @ 1225 mV
1300 @ 1175 mV
1200 @ 1138 mV
1100 @ 1100 mV
1000 @ 1075 mV
900 @ 1050 mV
800 @ 1013 mV
700 @ 988 mV
600 @ 963 mV
500 @ 950 mV
400 @ 938 mV
300 @ 925 mV
200 @ 913 mV
And GPU
160 @ 937 mV
266 @ 962 mV
350 @ 1012 mV
440 @ 1075 mV
533 @ 1137 mV
By the way, thanks everyone for your interest and for trying to help a poor noob :highfive:
EDIT
K99's point is absolutely CORRECT. Whenever the battery reaches 35-36°C the CPU is unable to go over 800 mhz, no matter how low the CPU temp is. The CPU temp can even be 30°C no matter. Now, any idea of a good ROM NOT based on Samsung's stock with 4.2 and s pen support? Will report back and tell you if that security protocol stuff is true.
And another question. How can I backup an ENTIRE app such as that stupid NFS game to just put it back on the new ROM without having to download it again? (I have monthly limits on my connection...)
For backing up app with data, use titanium backup.
Sent from my GT-N7100 using xda premium
I just want to share my most stable maximum undervolting of my Wonder,
I did not say that I am the first one to post this, I know there are already successfully undervolted their phones.
I've learned this from Pepoluan post, I've forgot that thread already.
We all know that undervolting our device gives advantages, such as extending battery life, increases power supply, extends the life of the device and less heat.
Here's what i've used.
1. Latest CM9 Rom (cm9-20130603-UNOFFICIAL-ancora) by our master Arco68
2. Kernel capable for unvervolting- I'm using HurtSky's kernel ( 3.0.82ICSHurtSky V 3.5)
3. IncrediControl app from playstore
So here are the tabulation below:
HTML:
Frequency Default V UV(My Setting) Difference % Savings
122880 900 750 150 16.7%
245760 900 750 150 16.7%
368640 900 750 150 16.7%
768000 1050 825 225 21.4%
806400 1100 925 175 15.9%
1024000 1200 925 275 22.9%
1113600 1200 975 225 18.8%
1209600 1200 1025 175 14.6%
1305600 1225 1050 175 14.3%
1401600 1250 1100 150 12.0%
1516800 1250 1150 100 8.0%
1612800 1275 1200 75 5.9%
1708800 1300 1275 25 1.9%
1804800 1325 1325 0 0.0%
I have conducted a stress test for every frequency to determine its most stable voltage.
TIPS:
- Use minimum frequency of 368 MHz since they have the same voltage with 122 and 245.
Advantage
- Improves scrolling ( based on my experience)
- Music clarity (also based on my experence)
- Launching Apps is much faster ( again based on my experience)
Disadvantage
- please let me know
Please, if you want to use this set up on your phone, please dont blame me if your phone crashes.
Please conduct a stress test first for every step down on undervolting for every frequency and here is the a Quick Guide below:
Quick Guide - Undervolting
What you need:
1. KERNEL - Capable for UnderVolting.
2. IncerdiControl App
3. Apps for Stress Test or Heavy Games or Benchmarking Apps.
4. Patience.
STEPS
1. Set the minimum frequency and maximum frequency of the CPU - the minimum should be the lowest existing frequency of the cpu and the maximum should be 1 step higher than the minimum (sample: min= 122MHz and max = 245 MHz)
2. Open IncrediControl app and set each frequency by 1 step down ( less 25 each),
3. Then apply, do not apply at boot first, ( so when it crashes it will revert back to the default settings)
4. Conduct a stress test or play heavy games or run a benchmarking apps to test the stability.
5. When it passed, repeat steps 2, 3, 4 until your phone crashes.
6. The previous lowered voltage before your phone crashes will now be the most stable undervoltage.
7. Record now the stable lowered voltage.
8. Next, increase the maximum frequency by 1 step higher (not the voltage).
9. The minimum frequency should be set to the recorded safe lowered voltage.
10. Open IncrediControl and set the voltage of the maximum frequency only by 1 step down (less 25).
11. Then Apply, do not apply at boot first,
12.Conduct a stress test or play heavy games or run a benchmarking apps to test the stability.
13. When it passed, repeat steps 10, 11, 12 until your phone crashes.
14. The previous lowered voltage before your phone crashes will now be the most stable undervoltage.
15. Repeat steps 8, 9, 10, 11, 12, 13 and 14 for the remaining frequencies, until you have determined the stable lowered voltages for each frequencies.
16. Now, after you have determined the undervoltage, apply it to your phone, no not apply first at booth,
17. Observe and stress test your phone for at least 1 hour.
18. if it will not crash anymore, you have now the Stable Undevoltage.
19. To be more safe, for daily use, increase the voltages by 1 step for each frequencies, except those which did not changed the value.
20. You can now apply the settings at boot.
21. Enjoy.
Note:
If your phone became unresponsive or vibrates continuously, that's the time that your phone is crashing, just turn off the phone, press the power for at least 10 seconds and it will turn off, or simply pull the battery.
TO THOSE WHO HAD SUCCESSFULLY UNDERVOLTED THEIR GALAXY W, MAY POST HERE AND MAY SHARE THEIR SETTINGS, SO SOME OF THE MEMBERS MAY GET AN IDEA.
Thanks to
Arco68
HurtSky
Pepoluan
honeyx
& Galaxy W Community
stock rom compatible?
Hi, thanks for sharing this:good:
Will i be able to use it with a rooted stock rom?
is stock rom capable of undervolting?
jakelq said:
I just want to share my most stable maximum undervolting of my Wonder,
I did not say that I am the first one to post this, I know there are already successfully undervolted their phones.
I've learned this from Pepoluan post, I've forgot that thread already.
We all know that undervolting our device gives advantages, such as extending battery life, increases power supply, extends the life of the device and less heat.
Here's what i've used.
1. Latest CM9 Rom (cm9-20130603-UNOFFICIAL-ancora) by our master Arco68
2. Kernel capable for unvervolting- I'm using HurtSky's kernel ( 3.0.80ICSHurtSky V 3.4)
3. IncrediControl app from playstore
So here are the tabulation below:
HTML:
Frequency Default V UV(My Setting) Difference % Savings
122880 900 750 150 16.7%
245760 900 750 150 16.7%
368640 900 750 150 16.7%
768000 1050 825 225 21.4%
806400 1100 925 175 15.9%
1024000 1200 925 275 22.9%
1113600 1200 975 225 18.8%
1209600 1200 1025 175 14.6%
1305600 1225 1050 175 14.3%
1401600 1250 1100 150 12.0%
1516800 1250 1150 100 8.0%
1612800 1275 1200 75 5.9%
1708800 1300 1275 25 1.9%
1804800 1325 1325 0 0.0%
I have conducted a stress test for every frequency to determine its most stable voltage.
TIPS:
- Use minimum frequency of 368 MHz since they have the same voltage with 122 and 245.
Advantage
- Improves scrolling ( based on my experience)
- Music clarity (also based on my experence)
- Launching Apps is much faster ( again based on my experience)
Disadvantage
- please let me know
Please, if you want to use this set up on your phone, please dont blame me if your phone crashes.
Please conduct a stress test first for every step down on undervolting for every frequency and here is the a Quick Guide below:
Quick Guide - Undervolting
What you need:
1. KERNEL - Capable for UnderVolting.
2. IncerdiControl App
3. Apps for Stress Test or Heavy Games or Benchmarking Apps.
4. Patience.
STEPS
1. Set the minimum frequency and maximum frequency of the CPU - the minimum should be the lowest existing frequency of the cpu and the maximum should be 1 step higher than the minimum (sample: min= 122MHz and max = 245 MHz)
2. Open IncrediControl app and set each frequency by 1 step down ( less 25 each),
3. Then apply, do not apply at boot first, ( so when it crashes it will revert back to the default settings)
4. Conduct a stress test or play heavy games or run a benchmarking apps to test the stability.
5. When it passed, repeat steps 2, 3, 4 until your phone crashes.
6. The previous lowered voltage before your phone crashes will now be the most stable undervoltage.
7. Record now the stable lowered voltage.
8. Next, increase the maximum frequency by 1 step higher (not the voltage).
9. The minimum frequency should be set to the recorded safe lowered voltage.
10. Open IncrediControl and set the voltage of the maximum frequency only by 1 step down (less 25).
11. Then Apply, do not apply at boot first,
12.Conduct a stress test or play heavy games or run a benchmarking apps to test the stability.
13. When it passed, repeat steps 10, 11, 12 until your phone crashes.
14. The previous lowered voltage before your phone crashes will now be the most stable undervoltage.
15. Repeat steps 8, 9, 10, 11, 12, 13 and 14 for the remaining frequencies, until you have determined the stable lowered voltages for each frequencies.
16. Now, after you have determined the undervoltage, apply it to your phone, no not apply first at booth,
17. Observe and stress test your phone for at least 1 hour.
18. if it will not crash anymore, you have now the Most Stable Undevoltage.
19. You can now apply the settings at boot.
20. Enjoy.
Note:
If your phone became unresponsive or vibrates continuously, that's the time that your phone is crashing, just turn off the phone, press the power for at least 10 seconds and it will turn off, or simply pull the battery.
Thanks to
Arco68
HurtSky
Pepoluan
& Galaxy W Community
Click to expand...
Click to collapse
Dude, these voltages are extreme!!! For gaming, these kind of voltages will surely crash the W. Well i tried putting 1.4/1.5GHz to 1175V and it crashed while playing Subway Surfers. Set at 1200V is stable enuff !
Sent from my GT-S6500 using xda app-developers app
lincoln_bw said:
Hi, thanks for sharing this:good:
Will i be able to use it with a rooted stock rom?
is stock rom capable of undervolting?
Click to expand...
Click to collapse
As far as i know, the stock rom is not capable for undervolting.
IncrediControl apps will work only for rooted phone and kernel capable for undervolting.
Thank you...
TiTAN-O-One said:
Dude, these voltages are extreme!!! For gaming, these kind of voltages will surely crash the W. Well i tried putting 1.4/1.5GHz to 1175V and it crashed while playing Subway Surfers. Set at 1200V is stable enuff !
Sent from my GT-S6500 using xda app-developers app
Click to expand...
Click to collapse
Yup, but this was the result after the tests and its really stable enough.
If you really want to check the stable undervoltage for 1.4GHz and 1.5GHz, you may set your minimum frequency to 1.4GHz and 1.5GHZ for the maximum frequency, undervolt it and check if it really crashes your phone.
Sometimes, crashes may caused by the low frequencies, not the maximum frequencies.
Thank you,
To be 100% sure you should check each frequency separately, not just lower all voltages at the same time by 25mV till it causes your phone to crash. For me I could lover the voltages for the lower frequencies more than for the upper frequencies. By saying this even not thinking about the oc frequencies, just the standard clock frequencies.
Also some games and benchmarks will be not enough to test stability. For me many games and benachmarks passed the voltages i set while testing but for example the facebook app freezed the phone after launching it. At some voltages the phone even could last for 3 days stable but crashed then, so the whole procedure took me a while till I found my stable undervolting settings.
honeyx said:
To be 100% sure you should check each frequency separately, not just lower all voltages at the same time by 25mV till it causes your phone to crash. For me I could lover the voltages for the lower frequencies more than for the upper frequencies. By saying this even not thinking about the oc frequencies, just the standard clock frequencies.
Also some games and benchmarks will be not enough to test stability. For me many games and benachmarks passed the voltages i set while testing but for example the facebook app freezed the phone after launching it. At some voltages the phone even could last for 3 days stable but crashed then, so the whole procedure took me a while till I found my stable undervolting settings.
Click to expand...
Click to collapse
+1
Maybe after determining the stable low voltage during stress tests, it would be safe to increase the voltage by 1 step higher for each frequency.
Thanks for sharing,
jakelq said:
+1
Maybe after determining the stable low voltage during stress tests, it would be safe to increase the voltage by 1 step higher for each frequency.
Thanks for sharing,
Click to expand...
Click to collapse
That´s what I also recommend. It doesn´t hurt to incrase all voltages by 25mV after finding the lowest stable values and will incrase stability a lot, as there always might be some small fluctuations while the frequencies are changing.
honeyx said:
That´s what I also recommend. It doesn´t hurt to incrase all voltages by 25mV after finding the lowest stable values and will incrase stability a lot, as there always might be some small fluctuations while the frequencies are changing.
Click to expand...
Click to collapse
Yup, I've already included your recommendation, that would be a great help.
Thanks for the recommendation.
Noob question, what is Undervolting?
Dhada said:
Noob question, what is Undervolting?
Click to expand...
Click to collapse
Are you seroius about this? It´s quite obvious when looking at the first post. It´s lowering the voltage of the CPU to reduce consumption and so also the battery drain.
honeyx said:
Are you seroius about this? It´s quite obvious when looking at the first post. It´s lowering the voltage of the CPU to reduce consumption and so also the battery drain.
Click to expand...
Click to collapse
Sounds to conflict
Dhada said:
Sounds to conflict
Click to expand...
Click to collapse
Baby steps!
I assume you play games and probably set ur phone clock speed stock at 1.4 GHz rite? Sometimes, you notice a huge battery drain after playing games like NFSMW or Modern Combat... Well, undervolt is for you to lower the voltages for EACH clock speed of your device to make battery last abit longer... Setting it too low may result in CRASHING or FREEZING and so u have this guide to show you the most stable undervolting thing... hope it helps CMIIW
Sent from my GT-I8150 using xda app-developers app
TiTAN-O-One said:
Baby steps!
I assume you play games and probably set ur phone clock speed stock at 1.4 GHz rite? Sometimes, you notice a huge battery drain after playing games like NFSMW or Modern Combat... Well, undervolt is for you to lower the voltages for EACH clock speed of your device to make battery last abit longer... Setting it too low may result in CRASHING or FREEZING and so u have this guide to show you the most stable undervolting thing... hope it helps CMIIW
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
Nice i already did it
TiTAN-O-One said:
Dude, these voltages are extreme!!! For gaming, these kind of voltages will surely crash the W. Well i tried putting 1.4/1.5GHz to 1175V and it crashed while playing Subway Surfers. Set at 1200V is stable enuff !
Sent from my GT-S6500 using xda app-developers app
Click to expand...
Click to collapse
Unfortunately, not all W's are equal; some are more equal than the others
What I meant was: the components are varying, quite so in fact that a W might survive at those very low voltages, while others give up the ghost and/or go crazy.
One have to test; therefore, great job for @jakelq for posting the complete procedure :thumbup:
-- sent from Samsung GT-I8150 running CM10 by Arco68
pepoluan said:
Unfortunately, not all W's are equal; some are more equal than the others
What I meant was: the components are varying, quite so in fact that a W might survive at those very low voltages, while others give up the ghost and/or go crazy.
One have to test; therefore, great job for @jakelq for posting the complete procedure :thumbup:
-- sent from Samsung GT-I8150 running CM10 by Arco68
Click to expand...
Click to collapse
Hey, where have you been?
Thank you, but you know the credit should go for you.
jakelq said:
Hey, where have you been?
Thank you, but you know the credit should go for you.
Click to expand...
Click to collapse
Had been extremely busy at work... I have to supervise so many things, I lost track of this Wonder-ful forum...
-- sent from Samsung GT-I8150 running CM10 by Arco68
pepoluan said:
Had been extremely busy at work... I have to supervise so many things, I lost track of this Wonder-ful forum...
-- sent from Samsung GT-I8150 running CM10 by Arco68
Click to expand...
Click to collapse
Glad you still find time for our community.
Thank you,
jakelq said:
I just want to share my most stable maximum undervolting of my Wonder,
I did not say that I am the first one to post this, I know there are already successfully undervolted their phones.
I've learned this from Pepoluan post, I've forgot that thread already.
We all know that undervolting our device gives advantages, such as extending battery life, increases power supply, extends the life of the device and less heat.
Here's what i've used.
1. Latest CM9 Rom (cm9-20130603-UNOFFICIAL-ancora) by our master Arco68
2. Kernel capable for unvervolting- I'm using HurtSky's kernel ( 3.0.82ICSHurtSky V 3.5)
3. IncrediControl app from playstore
So here are the tabulation below:
HTML:
Frequency Default V UV(My Setting) Difference % Savings
122880 900 750 150 16.7%
245760 900 750 150 16.7%
368640 900 750 150 16.7%
768000 1050 825 225 21.4%
806400 1100 925 175 15.9%
1024000 1200 925 275 22.9%
1113600 1200 975 225 18.8%
1209600 1200 1025 175 14.6%
1305600 1225 1050 175 14.3%
1401600 1250 1100 150 12.0%
1516800 1250 1150 100 8.0%
1612800 1275 1200 75 5.9%
1708800 1300 1275 25 1.9%
1804800 1325 1325 0 0.0%
I have conducted a stress test for every frequency to determine its most stable voltage.
TIPS:
- Use minimum frequency of 368 MHz since they have the same voltage with 122 and 245.
Advantage
- Improves scrolling ( based on my experience)
- Music clarity (also based on my experence)
- Launching Apps is much faster ( again based on my experience)
Disadvantage
- please let me know
Please, if you want to use this set up on your phone, please dont blame me if your phone crashes.
Please conduct a stress test first for every step down on undervolting for every frequency and here is the a Quick Guide below:
Quick Guide - Undervolting
What you need:
1. KERNEL - Capable for UnderVolting.
2. IncerdiControl App
3. Apps for Stress Test or Heavy Games or Benchmarking Apps.
4. Patience.
STEPS
1. Set the minimum frequency and maximum frequency of the CPU - the minimum should be the lowest existing frequency of the cpu and the maximum should be 1 step higher than the minimum (sample: min= 122MHz and max = 245 MHz)
2. Open IncrediControl app and set each frequency by 1 step down ( less 25 each),
3. Then apply, do not apply at boot first, ( so when it crashes it will revert back to the default settings)
4. Conduct a stress test or play heavy games or run a benchmarking apps to test the stability.
5. When it passed, repeat steps 2, 3, 4 until your phone crashes.
6. The previous lowered voltage before your phone crashes will now be the most stable undervoltage.
7. Record now the stable lowered voltage.
8. Next, increase the maximum frequency by 1 step higher (not the voltage).
9. The minimum frequency should be set to the recorded safe lowered voltage.
10. Open IncrediControl and set the voltage of the maximum frequency only by 1 step down (less 25).
11. Then Apply, do not apply at boot first,
12.Conduct a stress test or play heavy games or run a benchmarking apps to test the stability.
13. When it passed, repeat steps 10, 11, 12 until your phone crashes.
14. The previous lowered voltage before your phone crashes will now be the most stable undervoltage.
15. Repeat steps 8, 9, 10, 11, 12, 13 and 14 for the remaining frequencies, until you have determined the stable lowered voltages for each frequencies.
16. Now, after you have determined the undervoltage, apply it to your phone, no not apply first at booth,
17. Observe and stress test your phone for at least 1 hour.
18. if it will not crash anymore, you have now the Stable Undevoltage.
19. To be more safe, for daily use, increase the voltages by 1 step for each frequencies, except those which did not changed the value.
20. You can now apply the settings at boot.
21. Enjoy.
Note:
If your phone became unresponsive or vibrates continuously, that's the time that your phone is crashing, just turn off the phone, press the power for at least 10 seconds and it will turn off, or simply pull the battery.
TO THOSE WHO HAD SUCCESSFULLY UNDERVOLTED THEIR GALAXY W, MAY POST HERE AND MAY SHARE THEIR SETTINGS, SO SOME OF THE MEMBERS MAY GET AN IDEA.
Thanks to
Arco68
HurtSky
Pepoluan
honeyx
& Galaxy W Community
Click to expand...
Click to collapse
nice and gonna try it soon, just wanna ask, if i change to another kernel, then i have to reset it again?? .. anyway thankss
jakelq said:
Glad you still find time for our community.
Thank you,
Click to expand...
Click to collapse
Going back here feels like coming back to a family... a slightly dysfunctional family, but still a family nonetheless
Just like some other senior members ; they maybe without a W for some time, but they keep peeking in every now and then, just to enjoy the camaraderie and help people when they can...
hanafi200 said:
nice and gonna try it soon, just wanna ask, if i change to another kernel, then i have to reset it again?? .. anyway thankss
Click to expand...
Click to collapse
Most probably so; a different kernel might stress the system in different ways compared to the previous kernel. What works with one kernel might not be stable with another kernel.
However, if you're using IncrediControl, the app saves the voltage settings so you can start from those numbers instead of starting from scratch. Unless you go Pristine™ of course... in which case I suggest you manually saving the numbers somewhere safe.
-- sent from Samsung GT-I8150 running CM10 by Arco68