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!
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