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!
Hi
Benchmarks apps like AnTuTu are Quadrant are very polular.
This thread should give you some insights why the results
of such benchmarks should not be taken too seriously
"Real world" example:
KISS kernel with max 1.5GHz OC
Using scheduler "odemand" -> AnTuTu will score at about 4000
Using scheduler "smartassV2" -> AnTuTu will score at about 2800
(Quadrant results are similiar in ratio)
So how to "read" this:
The ondemand scheduler scales very fast to highest frequencies.
This means you will get higher numbers at the "cost"
of beeing not so good on battery life.
smartassV2 is "smarter" by doing this frequency upscale differently which leads
to lower numbers since a benchmark can not take that into account.
BUT actually you will not notice a difference in speed in "daily" usage of your device
whereass you will notice a difference in battery usage especially if you tune
the govener to a battery "friendly" profile
regards
max
Thanks for the explanation... I guess the real feel of the ROM is more important that the benchmark score.
Anyway, here is my benchmark score running your kernel at 1.5 smartassV2. single run.
Database IO is :good:
ckpv5 said:
Thanks for the explanation... I guess the real feel of the ROM is more important that the benchmark score.
Anyway, here is my benchmark score running your kernel at 1.5 smartassV2. single run.
Database IO is :good:
Click to expand...
Click to collapse
Thanks for the results
For smartassV2 it also dependend on the "tweaks" you apply
So if you "force" values to be more performant "friendly". The values
are of course higher (CPU clock switching is faster then)
Have you changed any smartssV2 tweaks on your device for this
benchmark runs? The defaults are more performant friendly IIRC
BTW: you can run "my" getcpuinfo.sh script which will print out
all the govener settings
Regards
max
maxwen said:
Have you changed any smartssV2 tweaks on your device for this
benchmark runs? The defaults are more performant friendly IIRC
BTW: you can run "my" getcpuinfo.sh script which will print out
all the govener settings
Click to expand...
Click to collapse
No change to smartassV2 tweaks, use it as it is.
As requested:
Code:
Starting getcpuinfo 08-06-2012 04:42:08
--------------------------------------------------
Available goveners:smartassV2 conservative Lionheart ondemand performance
Available frequencies:245760 368640 768000 806400 1024000 1200000 1401600 1497600
Active govener:smartassV2
min CPU frequency:245760
max CPU frequency:1497600
Scaling min CPU frequency:245760
Scaling max CPU frequency:1497600
--------------------------------------------------
Settings for govener smartassV2:
awake_ideal_freq :800000
debug_mask :0
down_rate_us :99000
max_cpu_load :55
min_cpu_load :25
ramp_down_step :300000
ramp_up_step :200000
sample_rate_jiffies :2
sleep_ideal_freq :200000
sleep_wakeup_freq :99999999
up_rate_us :48000
--------------------------------------------------
VDD values:
24576: 900
61440: 900
122880: 900
184320: 900
192000: 900
245760: 900
368640: 950
768000: 1000
806400: 1000
1024000: 1100
1200000: 1150
1401600: 1175
1497600: 1175
--------------------------------------------------
End getcpuinfo 08-06-2012 04:42:09
Hey everyone I'm a bit new here, I mostly lurk lol. But I just had 2 questions on stock volts/undervolting
I'm running Agat 0.4.2 (http://forum.xda-developers.com/showthread.php?t=1767421) and
I couldn't find the stock voltages for the phone listed anywhere. Can anyone confirm these are the same as stock kernel within the 200-1200mhz range?
Also would -50mV drops be safe across the board on Agat Kernel?
1600Mhz __1400mV
1500Mhz __1375mV
1400Mhz __1325mV
1300Mhz __1300mV
1200Mhz __1274mV
1100Mhz __1225mV
1000Mhz __1175mV
900Mhz ___1125mV
800Mhz ___1075mV
700Mhz ___1025mV
600Mhz ___1000mV
500Mhz ___975mV
400Mhz ___975mV
300Mhz ___975mV
200Mhz ___950mV
100Mhz ___925mV
50Mhz ____900mV
25Mhz ____875mV
Yes that is what I was running for a while....
Sent from my SPH-D710 using xda app-developers app
I usually run 200Mhz @ 800mV, 500Mhz @ 900, 800Mhz @ 950mV and so on. I had a stable UV of about 25-50mV lower but i swapped ROMs and a little reboot gremlin appeared. These things UV quite well until you start overclocking. I haven't been able to get a stable OC yet but I'm sure it's my device that's being a party pooper ;-p
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?
So I installed the Perseus kernel and with Stweaks I overclocked the CPU at 1800Mhz.
Antatu = over 19000 points
Then I oced the GPU only to 800Mhz = 18400 Points
But when I decide to overclock both at maximum (1800/800Mhz) I get low score.
Even overclocking the CPU @ 800Mhz and CPU @ 1700Mhz = lower score than just CPU @ 1800Mhz
Is it because the CPU is throttling? What's wrong?
Dear cyber.bg,
Yes probably your cpu is throttling to 800 mhz from 1800 mhz because it reaches the temp of 80c...
To avoid throttling, you have to undervolt cpu when overclocking...
According to me , overclocking gpu over 533 is useless and also makes a lot of heat which push cpu to throttle ... Even gpu @640 mhz with higher voltages you will face freezes and lags...
So just overclock your cpu to 1800 mhz but with lower voltages... Most note 2 cpus can do 1800 mhz @ 1250mV... You can try to give -25 to other values from 1250 mV... 200 mhz @ 775 mv is also fine and no deep sleeps for me.
Dont overclock your gpu but you can undervolt it a little bit... gpu @533 is fine with 1050 mV...
With the right frequency and voltages for both cpu and gpu there will be no throttling so u can get real antutu scores... cpu @1800 and [email protected] with lower voltages, u can expect an antutu score between 19300 and 19800 depending on your rom, kernel and tweaks...
You can use stweaks app to overclock and undervolt...
You can use system tuner pro app to observe cpu temp and other data...
Hope all these helps...
Kind regards.
Sent from my Amiga Note
Thank you for your reply, it was very informative
Currently I am with Note2Core AS (the 1.92Ghz kernel) and I still have the throttling problem, even though my CPU temp doesn't go beyond 50C in Quadrant. But it is till throttling.
I've tried to edit voltage with SetCPU, Voltage Control Extreme and System Tuner Pro, but they don't stick - they just revert back to their original values (1425mV for 1.92Ghz) Stweaks says Sorry, no kernel support.
The interesting part is that in the beginning I managed to run 1-2 benchmarks without Throttling, but anything after that is throttled. Best scores so far:
Antutu: 19868
Quadrant - 7941
Do you know why I can't edit voltages and why it throttles even when CPU temperature is low?
Maybe it has to be plugged in and charging from the Wall?
Dear cyber.bg,
I am using perseus v29.1 kernel and it supports stweaks app... Also i can use voltage control or setcpu with this kernel but i prefer stweak since it has native support in the kernel.
First, 1.9 mhz @1425 mV is really high and thats why your cpu throttles...
I do max 1.8 mhz @ 1250 mV to avoid throttling... I did many test and voltages above 1250-1300 will bring throttling back. My cpu is stable @1250mV...
With quadrant cpu may not throttle because it is an outdated benchmark and i am sure it doesnt use all the cpu cores @100 percent...
Antutu is the solution to observe for throttling...
To observe temps and throttling, run both antutu and sytem tuner pro in split view...
Also i use a 4k video to push all the cpus to max and view video in floating windows so u can see all the data in system tuner pro while video is playing in floating window.
Lastly, my advice is dont go over 1.8 mhz @1250 mV for cpu and 533 mhz @1050mV for gpu... i am sure with these settings, u will have a stable note2 with no throttling and at its max performance...
Hope all these helps...
Kind regards.
Sent from my Amiga Note
Thank you again for this very knowledgeable post
I've used Perseus too. I even switch them daily while experimenting.
I put the Note2Core because I want to push the phone to its limits and get a really high benchmark scores. I've seen people reaching almost 9000 in Quadrant. And for Antutu I already got a really high score (19548), but if I manage to stabilize it at 1920Mhz I can get higher. But it throttles
And I still can't understand why it throttles? Some people say it's because of the high temperature, but how high is high? When I finish with a benchmark and go to look for the temp the highest I've seen is 50C. Is that high?
Also how do I run Antutu and System Tuner Pro in dual view? Their icons are not in the side menu that I open when holding the back button. How do I put them there?
Have you tested with more than 1800Mhz for the CPU? or more than 533Mhz for the GPU only? Can you post some Quadrant and Antutu screenshots so I can compare.
Thank you again
Dear cyber.bg,
Here is my antutu and quadrant results...
Wanamlite v2.1
Perseus v29.1
Cpu 1.8 mhz @1250mV
Gpu 533 mhz @ 1050 mV
Antutu ~19300
Quadrant ~7300
I have run both antutu and quadrant only one time...
By the way, cpu begins throttling when its temp reaches 80c so i am sure you hit this limit...
I have also tried 1920 and 2000 mhz with angelom kernel but because of throttling and so much heat, i had to return back to 1800 mhz with perseus kernel...
Kind regards.
Sent from my Amiga Note
2 questions:
1 - How can I see the maximum temp the CPU reaches?
2 - Did you have any successful test at 1920 and 2000 mhz without throttling?
cyper.bg said:
2 questions:
1 - How can I see the maximum temp the CPU reaches?
2 - Did you have any successful test at 1920 and 2000 mhz without throttling?
Click to expand...
Click to collapse
Dear cyber.bg,
1- The only way AFAIK is to use system tuner pro app... Be aware that apps like setcpu reports the BATTERY TEMP not the CPU TEMP...
2- Unfortunately NO since these speeds need min 1400 mV to be stable but throttling occurs immediately so no meaning to overclock...
Steps to observe throttling...
1- Download and install system tuner pro...
2- Download and install super video app and set it for software decoding not hardware decoding.
3- Grap a 4k video (life in the garden) from you tube with the tube mate app... i use this 4k video because it pushes all the cores to max with nearly full load in software decoding mode...
3a- Alternatively you can use antutu and system tuner pro app in split view to observe data... You have to flash this mod in able to add these app to multi windows list... http://forum.xda-developers.com/showthread.php?t=1953705
4- Play 4k video with super video app in a floating window...
5- While video is playing run system tuner pro app and touch to cpu button...
6- Now u should be able to see cpu data like temp,core speeds,load and also video in floating window all together
7- Observe the cpu temp and core speed... if the temp reaches 80c then core speeds down to 800 mhz which mean cpu is throttling... Try to undervolt some more to keep cpu under 80c but with stability of course...
As i said before, the max i can go without throttling is cpu 1800 [email protected] mV and gpu 533 mhz @1050mV... With these settings i can maintain stability, and full benefit from overclocking without throttling...
Hope all these helps...
Kind regards.
Sent from my Amiga Note...
I tried 1800Mhz @ 1200mV and it seemded stable. GPU was 533Mhz @ 1050mV
You also write that it starts to throttle at 80C - have you found out that yourself or it is in the specifications of the chip?
Here are 2 shots (these were before I tried lower voltages):
Samsung Galaxy Note 2 - Jelly Bean 4.1.1
Quadrant (Run Full Benchmark):
Note2Core Kernel
CPU: 1920Mhz, 1425mV
GPU: 533Mhz, 1050mV
AnTuTu (Пълен тест):
Perseus Kernel
CPU: 1800Mhz, 1250mV
GPU: 533Mhz, 1050mV
Geekbench 2:
Note2Core Kernel
CPU: 1920Mhz, 1425mV
GPU: 533Mhz, 1050mV
Dear cyber.bg,
Nice scores... Well done... Which rom ?
During my observations with system tuner pro, i have realized the throttling temp is 80c..
I think the throttling level can be configured via kernel so this is up to the kernel developers... i remember from note1 that there was thor kernel and with this kernel cpu was throttling @85c and to 1.4 ghz not 800 mhz if i am not wrong...
Kind regards.
Sent from my Amiga Note
Scores were with stock 4.1.1. I haven't installed any modified ROMs so far, cause I like the stock
Btw I'm afraid to use System Tuner Pro now, because last time I tried to uninstall it my phone froze, but I pressed the power button for 5 seconds and restarted. On the 2nd attempt to uninstall it the same thing happened, but after restarting the OS didn't want to load. I didn't have a backup or anything and had to reinstall everything. At least I put 4.1.2, so I'm making a Nandroid backup through CWM recovery now. That was a good lesson.
Have you tried 1.8Ghz @ 1200mV for daily use?
Dear cyber.bg,
Yes, i tried 1.8 @ 1200mV but i got frezees while playing some 2k and 4k videos so i decided to be safe and push it to 1250 mV even 1225 mV seemes stable for my cpu...
Kind regards...
Sent from my Amiga Note
My Note 2 is currently running 1956gHz @ 1412 volts.. I only ran into a problem when I locked the gpu @ 533mHz and used a stress test.
Tegrak Overclock Ultimate is amazing !
I also noticed tegrak's overclocking doesn't take effect until I open Setcpu..
Edit: Overclocked to 2gHz @ 1437 volts.. what is the repercussions to the volts being "too high?"
Sent from my GT-N7100 using xda premium
PROTOCHIP said:
Dear cyber.bg,
Yes probably your cpu is throttling to 800 mhz from 1800 mhz because it reaches the temp of 80c...
To avoid throttling, you have to undervolt cpu when overclocking...
According to me , overclocking gpu over 533 is useless and also makes a lot of heat which push cpu to throttle ... Even gpu @640 mhz with higher voltages you will face freezes and lags...
So just overclock your cpu to 1800 mhz but with lower voltages... Most note 2 cpus can do 1800 mhz @ 1250mV... You can try to give -25 to other values from 1250 mV... 200 mhz @ 775 mv is also fine and no deep sleeps for me.
Dont overclock your gpu but you can undervolt it a little bit... gpu @533 is fine with 1050 mV...
With the right frequency and voltages for both cpu and gpu there will be no throttling so u can get real antutu scores... cpu @1800 and [email protected] with lower voltages, u can expect an antutu score between 19300 and 19800 depending on your rom, kernel and tweaks...
You can use stweaks app to overclock and undervolt...
You can use system tuner pro app to observe cpu temp and other data...
Hope all these helps...
Kind regards.
Sent from my Amiga Note
Click to expand...
Click to collapse
Hi PROTOCHIP,
Can you send image files of your's STweaks settings? (for oc and for battery life)
Your experience is so reliable.
Thanks a lot.
Why can't I see any difference between the 533Mhz GPU and 800Mhz GPU on the GLBenchmark? I don't OC the CPU, I even tried to lock it to 1200Mhz to avoid thermal problems however I couldn't reach above 18 FPS in Egypt test. Normally it is 17, with 600 or 700Mhz it goes to 18 and then stays there.
When I compare the GPUs of the SGS3 and Note 2 there is %10 overclock on the Note 2 side and the results exactly indicates this. SGS3 scores 15 FPS, Note 2 scores 17 apprx %10 higher. From this comparison i take it as the results are linear with the clock speeds. I was also proving this theory by OCing the Note 1 to 400 Mhz and reacing a few FPS below SGS3 on GLBenchmark. So, without any problem Note 2 should score 30-31 FPS on 800 Mhz but that is not the case in real life. So I guess it is either never goes to 800 Mhz or thermal throttling happens during the test. Orrrr, maybe 1080p offscreen is not a good option to push-test our Mali-400s? But there is no other GPU benchmarks to push our devices like offscreen because of the 60 FPS lock.
What do you think about this? Is it possible to reach the 30 FPS level?
Can you guys tell if this is ok? Or can I still go lower.. I just eant fair speed with battery saving..
Thanks in advance
Sent from my GT-N7100 using xda app-developers app
Omega rom v9.1 + perseus alpha 29.1
Dear yerebakan,
Here are my settings for cpu and gpu... Hope all these helps... These are my lowest settings and stable values for my cpu right now... You can add +25 for both cpu and gpu to be safe then u can play with the values...
Phoniex Rom V2.1 and Perseus Kernel v29.1
CPU: 200 Mhz - 1800 Mhz ( Voltages over 1300 [email protected] Mhz makes a lot of heat and cpu throttles... )
1800 Mhz - 1250 mV
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
GPU: 160 Mhz - 533 Mhz ( Speeds over 533 are useless since making a lot of heat and also gpu throttles... )
160 Mhz - 825 mV
266 Mhz - 875 mV
350 Mhz - 950 mV
440 Mhz - 1000 mV
533 Mhz - 1025 mV
Kind Regards...
---------- Post added at 02:38 PM ---------- Previous post was at 02:29 PM ----------
_delice_doluca_ said:
Why can't I see any difference between the 533Mhz GPU and 800Mhz GPU on the GLBenchmark? I don't OC the CPU, I even tried to lock it to 1200Mhz to avoid thermal problems however I couldn't reach above 18 FPS in Egypt test. Normally it is 17, with 600 or 700Mhz it goes to 18 and then stays there.
When I compare the GPUs of the SGS3 and Note 2 there is %10 overclock on the Note 2 side and the results exactly indicates this. SGS3 scores 15 FPS, Note 2 scores 17 apprx %10 higher. From this comparison i take it as the results are linear with the clock speeds. I was also proving this theory by OCing the Note 1 to 400 Mhz and reacing a few FPS below SGS3 on GLBenchmark. So, without any problem Note 2 should score 30-31 FPS on 800 Mhz but that is not the case in real life. So I guess it is either never goes to 800 Mhz or thermal throttling happens during the test. Orrrr, maybe 1080p offscreen is not a good option to push-test our Mali-400s? But there is no other GPU benchmarks to push our devices like offscreen because of the 60 FPS lock.
What do you think about this? Is it possible to reach the 30 FPS level?
Click to expand...
Click to collapse
Dear _delice_doluca_,
Same here and never had the chance to go over 18 fps with my note2 too... Overclocking over 533 doesnt help because of gpu throttling... In theory as you stated , we should go over 30 fps easily but in reality, this seems so far...
Kind Regards...
On behalf of the people who found this thread to discover your great insight and findings Protochip, thank you.
my cpu is running at 1.3ghz 1025mv however my phone reaches 67c true temp and throttles very easily any idea if this normal i cant play any 3d games unless im sitting near a fan or ac. Everyone says they throttle at 80c, i came to this thread from another post i had made. Im mostly playing
Nova 3 and mc4 .
nielo360 said:
my cpu is running at 1.3ghz 1025mv however my phone reaches 67c true temp and throttles very easily any idea if this normal i cant play any 3d games unless im sitting near a fan or ac. Everyone says they throttle at 80c, i came to this thread from another post i had made. Im mostly playing
Nova 3 and mc4 .
Click to expand...
Click to collapse
i found that the real throttling problem is a security protocol that Samsung roms have. When the battery reach 41C the cpu throttles (no matter if its only at 60C cpu temp)
i dont know how to deactivate that protocol...but if you want, try CM10.1 or any other AOKP or AOSP roms and you´ll se that there is no cpu throttling unless the cpu reach 80C.
you´ll need "stability test" app (cpu stress testing, and you can watch battery temp), and "system tuner" app (to watch live cpu temp during the stress test)