Database Users

[INFO] CPU [MSM8974AC] Binning Concept, Overclocking, Undervolting - ONE General

MSM8974AC Snapdragon 801 CPU Binning
​
!! INTRO !!
Click to expand...
Click to collapse
Hello XDA Friends,
I just collected some information related to CPU Binning and undervolting. Different sections of this POST is collected from different internet sources.
All Source Links are given below in each section. I am just the info collector and all credits goes to them (Original Author in different sources...)
Please share your views and updated information here
*** I don’t know, this thread should be in "General" or in "Android Development". Request to Moderators: please move this to proper thread-category***
APPS & Kernel You May Need For OnePlus One
Click to expand...
Click to collapse
Apps
[ROOT] Kernel Tweaker -- Google Play - https://play.google.com/store/apps/details?id=com.dsht.kerneltweaker
Trickster MOD Kernel Settings --- Google Play - https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod
Custom Kernel with UV Support (undervolting)
Franco Kernel -- http://forum.xda-developers.com/oneplus-one/orig-development/kernel-franco-kernel-r1-t2800871
!! SECTION 1 !!
Click to expand...
Click to collapse
Code:
[SIZE=4][B]Source[/B]: [URL]https://forums.oneplus.net/threads/check-your-opo-cpu-binning.33330/[/URL][/SIZE]
CPU binning quality defines the quality of a semiconductor processor.. like if it needs more voltage
to run stable than others of the same version.
it normally means, the lesser demanding stable vcore on stock clock, the higher binning
the cpu got and more capable it could be in terms of overclocking.
it's like intel processors. the i5 4570 has lessened stock clock than a i5 4670 for example and this is due to the
chip quality of the i5 4570 didn't turn out as good as the i5 4670 to operate at targeted stock clock
think of it like cutting out a perfect circle out of paper with a normal pair of scissors.
would every circle look the same by your hand by their tiniest nanometers?
no they probably wouldn't unless you're chuck norris but this is the same which applies to creating semi conductors..
they don't turn out perfect all the time and get sorted out but still are usable.
this is also why some i5 4670k hit a 4.3ghz overclock on air whilst other 4670k might reach even higher 4.7ghz
because their binning rate/grade of quality is actually higher
other than that there was once a great news about the nexus 4 because some people felt betrayed since the variety of
fast and slow snapdragon processors differed very much and geeks wanted to exchange it
because of that since it really made a slight difference in processor power
Phone must be rooted!!
1. Install Busybox
2. Install a Terminal Emulator
3. Reboot
4. Open Terminal and type:
Code:
su
dmesg | grep PVS
5. A line should be outputted that tells you what type you have.
1= slow
2= nominal
3= fast
4= faster
dmesg is a limited buffer of kernel messages so if the phone has been on for a while the command suggested may not show anything.
An alternative command is:
Code:
grep PVS /proc/kmsg
This is where all the kernel messages are stored (similar to /var/log/messages on linux).
!! SECTION 2 !!
Click to expand...
Click to collapse
PVS Bins for MSM8974AC are --> 0 to 15
Snapdragon 801 2.5ghz MSM8974AC v3
=======================================
Code:
MSM8974AC 2.5ghz PVS 0 - 422mhz
MSM8974AC 2.5ghz PVS 1 - 499mhz
MSM8974AC 2.5ghz PVS 2 - 576mhz
MSM8974AC 2.5ghz PVS 3 - 652mhz
MSM8974AC 2.5ghz PVS 4 - 729mhz
MSM8974AC 2.5ghz PVS 5 - 806mhz
MSM8974AC 2.5ghz PVS 6 - 652mhz
MSM8974AC 2.5ghz PVS 7 - 729mhz
MSM8974AC 2.5ghz PVS 8 - 806mhz
MSM8974AC 2.5ghz PVS 9 - 883mhz
MSM8974AC 2.5ghz PVS 10 - 960mhz
MSM8974AC 2.5ghz PVS 11 - 1036mhz
MSM8974AC 2.5ghz PVS 12 - 1113mhz
MSM8974AC 2.5ghz PVS 13 - 1190mhz
MSM8974AC 2.5ghz PVS 14 - 1113mhz
MSM8974AC 2.5ghz PVS 15 - 1190mhz
========= By XDA Recognized Developer @HD2Owner (Thank You Sir) =================
Best max frequency (sweet performance/power spot):
MSM8974AC 2.5ghz - 1.57ghz
How to get the maximum battery life:
if you have a MSM8974AB pvs 6 for example, try the following steps:
try the next higher pvs levels (pvs7). don't try AC pvs values on AB chips.
AB chips are binned for lower frequencies while AC are binned for higher frequencies (duh).
so if you have a AB chip, work your way up the AB pvs values until you have freezes or similar and move back.
if you have a AC chip, work your way up the AC pvs values etc...
if you found highest setting that does not cause any problems after intensive testing and usage:
congratulations, you did it.
How to get the maximum frequency:
first try higher than stock maximum clock and see how it behaves.
if you don't reach your desired clockspeed, try the next lower pvs setting of your chip. yes, i said LOWER.
this gives the processor more voltage to reach higher overclocks.
i don't recommend it tho since we all want our phones to last as long as possible usually.
==========================================================
Source -- XDA
http://forum.xda-developers.com/htc-one-m8/general/guide-snapdragon-801-clocking-voltage-t2807173
I have one question ...Higher Bin indicates higher quality chip ?
Similar question asked here.... see details...
https://developer.qualcomm.com/forum/qdn-forums/general-discussion/27244
Another nice command to get binning info is
Code:
su
cat /sys/module/clock_krait_8974/parameters/table_name
Note 1:
Click to expand...
Click to collapse
It's said that the higher the PVS bin value the better - in terms of it gives of less heat and requires less voltage:
0 requires the MOST/HIGHEST voltage range to boot, and 7 required the LEAST/LOWEST voltage range to boot.
Because lower binning SOCs use higher voltage values, they tend to run hotter than higher binning versions.
===================
Source: XDA
http://forum.xda-developers.com/showthread.php?t=2786841
Note 2:
Click to expand...
Click to collapse
users with CPU
Binning 0 running @ 2.3 GHz is using 1.100 volts
Binning 1 running @ 2.3 GHz is using 1.075 volts
...
Binning 6 running @ 2.3 GHz is using 0.95 volts
so if you take binning 6 compare to binning 0, you are "effectively" pre-undervolted from the factory by 150mv ALREADY! Wow...
So users with binning 0's MASSIVE -150mv undervolt compare to binning 6's STOCK voltage is effectively the SAME!
Wait a second... Isn't Binning 0 designed to run @ higher voltage? SO the massive undervoltage should crash correct?
Answer: Yes and No...
Lower Binning SOCs may need higher voltage to BOOT, but when running, it may use the same nominal voltage as the higher binning SOCs.
So once successfully booted, you can run the lower binning SOCs at lower voltage values than during boot.
===========================
Source: Google+
https://plus.google.com/+PaulReioux/posts/YXxQnnZxC7j
Note 3:
Click to expand...
Click to collapse
Snapdragon 801 2.5ghz MSM8974AC v3 --- Also Known As ---- MSM8974Pro AC Rev 1
(Two Revisions are available 0, 1)
============================
Code:
/* 8974Pro AC 2.5GHz */ (REV 0)
[0][3][0] = { pro_rev0_2p5g_pvs0, sizeof(pro_rev0_2p5g_pvs0) },
[0][3][1] = { pro_rev0_2p5g_pvs1, sizeof(pro_rev0_2p5g_pvs1) },
[0][3][2] = { pro_rev0_2p5g_pvs2, sizeof(pro_rev0_2p5g_pvs2) },
[0][3][3] = { pro_rev0_2p5g_pvs3, sizeof(pro_rev0_2p5g_pvs3) },
[0][3][4] = { pro_rev0_2p5g_pvs4, sizeof(pro_rev0_2p5g_pvs4) },
[0][3][5] = { pro_rev0_2p5g_pvs5, sizeof(pro_rev0_2p5g_pvs5) },
[0][3][6] = { pro_rev0_2p5g_pvs6, sizeof(pro_rev0_2p5g_pvs6) },
[0][3][7] = { pro_rev0_2p5g_pvs6, sizeof(pro_rev0_2p5g_pvs6) },
/* 8974Pro AC 2.5GHz */ (REV 1)
[1][3][0] = { pro_rev1_2p5g_pvs0, sizeof(pro_rev1_2p5g_pvs0) },
[1][3][1] = { pro_rev1_2p5g_pvs1, sizeof(pro_rev1_2p5g_pvs1) },
[1][3][2] = { pro_rev1_2p5g_pvs2, sizeof(pro_rev1_2p5g_pvs2) },
[1][3][3] = { pro_rev1_2p5g_pvs3, sizeof(pro_rev1_2p5g_pvs3) },
[1][3][4] = { pro_rev1_2p5g_pvs4, sizeof(pro_rev1_2p5g_pvs4) },
[1][3][5] = { pro_rev1_2p5g_pvs5, sizeof(pro_rev1_2p5g_pvs5) },
[1][3][6] = { pro_rev1_2p5g_pvs6, sizeof(pro_rev1_2p5g_pvs6) },
[1][3][7] = { pro_rev1_2p5g_pvs7, sizeof(pro_rev1_2p5g_pvs7) },
[1][3][8] = { pro_rev1_2p5g_pvs8, sizeof(pro_rev1_2p5g_pvs8) },
[1][3][9] = { pro_rev1_2p5g_pvs9, sizeof(pro_rev1_2p5g_pvs9) },
[1][3][10] = { pro_rev1_2p5g_pvs10, sizeof(pro_rev1_2p5g_pvs10) },
[1][3][11] = { pro_rev1_2p5g_pvs11, sizeof(pro_rev1_2p5g_pvs11) },
[1][3][12] = { pro_rev1_2p5g_pvs12, sizeof(pro_rev1_2p5g_pvs12) },
[1][3][13] = { pro_rev1_2p5g_pvs13, sizeof(pro_rev1_2p5g_pvs13) },
[1][3][14] = { pro_rev1_2p5g_pvs14, sizeof(pro_rev1_2p5g_pvs14) },
[1][3][15] = { pro_rev1_2p5g_pvs15, sizeof(pro_rev1_2p5g_pvs15) },
Voltage Table of REV 0 and REV 1 are following....
Code:
For Rev 0
------------------------------
Ordinary 8974AC PVS 0
static struct acpu_level pro_rev0_2p5g_pvs0 [] __ initdata = {
{1, {300000, PLL_0, 0, 0}, L2 (0), 800000, 76},
{1, {422400, HFPLL, 2, 44}, L2 (2), 800000, 106},
{1, {652800, HFPLL, 1, 34}, L2 (3), 810000, 165},
{1, {729600, HFPLL, 1, 38}, L2 (4), 820000, 186},
{1, {883200, HFPLL, 1, 46}, L2 (4), 840000, 229},
{1, {960000, HFPLL, 1, 50}, L2 (9), 850000, 251},
{1, {1036800, HFPLL, 1, 54}, L2 (10), 860000, 273},
{1, {1190400, HFPLL, 1, 62}, L2 (10), 880000, 319},
{1, {1267200, HFPLL, 1, 66}, L2 (13), 890000, 342},
{1, {1497600, HFPLL, 1, 78}, L2 (16), 920000, 415},
{1, {1574400, HFPLL, 1, 82}, L2 (17), 930000, 439},
{1, {1728000, HFPLL, 1, 90}, L2 (18), 960000, 493},
{1, {1958400, HFPLL, 1, 102}, L2 (19), 1005000, 579},
{1, {2265600, HFPLL, 1, 118}, L2 (19), 1065000, 700},
{1, {2457600, HFPLL, 1, 128}, L2 (19), 1100000, 785},
{0, 0}} {
};
Common 8974AC PVS 6/7
static struct acpu_level pro_rev0_2p5g_pvs6 [] __ initdata = {
{1, {300000, PLL_0, 0, 0}, L2 (0), 750000, 76},
{1, {422400, HFPLL, 2, 44}, L2 (2), 750000, 106},
{1, {652800, HFPLL, 1, 34}, L2 (3), 750000, 165},
{1, {729600, HFPLL, 1, 38}, L2 (4), 750000, 186},
{1, {883200, HFPLL, 1, 46}, L2 (4), 750000, 229},
{1, {960000, HFPLL, 1, 50}, L2 (9), 750000, 251},
{1, {1036800, HFPLL, 1, 54}, L2 (10), 750000, 273},
{1, {1190400, HFPLL, 1, 62}, L2 (10), 750000, 319},
{1, {1267200, HFPLL, 1, 66}, L2 (13), 755000, 342},
{1, {1497600, HFPLL, 1, 78}, L2 (16), 785000, 415},
{1, {1574400, HFPLL, 1, 82}, L2 (17), 795000, 439},
{1, {1728000, HFPLL, 1, 90}, L2 (18), 815000, 493},
{1, {1958400, HFPLL, 1, 102}, L2 (19), 855000, 579},
{1, {2265600, HFPLL, 1, 118}, L2 (19), 915000, 700},
{1, {2457600, HFPLL, 1, 128}, L2 (19), 950000, 785},
{0, 0}} {
};
For Rev 1
----------------------------------------------------
Revision 8974AC PVS 0
static struct acpu_level pro_rev1_2p5g_pvs0 [] __ initdata = {
{1, {300000, PLL_0, 0, 0}, L2 (0), 800000, 76},
{1, {422400, HFPLL, 2, 44}, L2 (2), 800000, 106},
{1, {652800, HFPLL, 1, 34}, L2 (3), 830000, 168},
{1, {729600, HFPLL, 1, 38}, L2 (4), 840000, 189},
{1, {883200, HFPLL, 1, 46}, L2 (4), 860000, 233},
{1, {960000, HFPLL, 1, 50}, L2 (9), 870000, 256},
{1, {1036800, HFPLL, 1, 54}, L2 (10), 880000, 278},
{1, {1190400, HFPLL, 1, 62}, L2 (10), 900000, 324},
{1, {1267200, HFPLL, 1, 66}, L2 (13), 910000, 348},
{1, {1497600, HFPLL, 1, 78}, L2 (16), 940000, 421},
{1, {1574400, HFPLL, 1, 82}, L2 (17), 950000, 446},
{1, {1728000, HFPLL, 1, 90}, L2 (18), 980000, 501},
{1, {1958400, HFPLL, 1, 102}, L2 (19), 1025000, 588},
{1, {2265600, HFPLL, 1, 118}, L2 (19), 1085000, 716},
{1, {2457600, HFPLL, 1, 128}, L2 (19), 1120000, 802},
{0, 0}} {
};
Revision 8974AC PVS 7
static struct acpu_level pro_rev1_2p5g_pvs7 [] __ initdata = {
{1, {300000, PLL_0, 0, 0}, L2 (0), 775000, 76},
{1, {422400, HFPLL, 2, 44}, L2 (2), 775000, 106},
{1, {652800, HFPLL, 1, 34}, L2 (3), 775000, 168},
{1, {729600, HFPLL, 1, 38}, L2 (4), 775000, 189},
{1, {883200, HFPLL, 1, 46}, L2 (4), 790000, 233},
{1, {960000, HFPLL, 1, 50}, L2 (9), 800000, 256},
{1, {1036800, HFPLL, 1, 54}, L2 (10), 810000, 278},
{1, {1190400, HFPLL, 1, 62}, L2 (10), 830000, 324},
{1, {1267200, HFPLL, 1, 66}, L2 (13), 840000, 348},
{1, {1497600, HFPLL, 1, 78}, L2 (16), 870000, 421},
{1, {1574400, HFPLL, 1, 82}, L2 (17), 880000, 446},
{1, {1728000, HFPLL, 1, 90}, L2 (18), 910000, 501},
{1, {1958400, HFPLL, 1, 102}, L2 (19), 955000, 588},
{1, {2265600, HFPLL, 1, 118}, L2 (19), 1015000, 716},
{1, {2457600, HFPLL, 1, 128}, L2 (19), 1050000, 802},
{0, 0}} {
};
Revision 8974AC PVS 15
static struct acpu_level pro_rev1_2p5g_pvs15 [] __ initdata = {
{1, {300000, PLL_0, 0, 0}, L2 (0), 750000, 76},
{1, {422400, HFPLL, 2, 44}, L2 (2), 750000, 106},
{1, {652800, HFPLL, 1, 34}, L2 (3), 750000, 168},
{1, {729600, HFPLL, 1, 38}, L2 (4), 750000, 189},
{1, {883200, HFPLL, 1, 46}, L2 (4), 750000, 233},
{1, {960000, HFPLL, 1, 50}, L2 (9), 750000, 256},
{1, {1036800, HFPLL, 1, 54}, L2 (10), 750000, 278},
{1, {1190400, HFPLL, 1, 62}, L2 (10), 750000, 324},
{1, {1267200, HFPLL, 1, 66}, L2 (13), 760000, 348},
{1, {1497600, HFPLL, 1, 78}, L2 (16), 790000, 421},
{1, {1574400, HFPLL, 1, 82}, L2 (17), 800000, 446},
{1, {1728000, HFPLL, 1, 90}, L2 (18), 830000, 501},
{1, {1958400, HFPLL, 1, 102}, L2 (19), 875000, 588},
{1, {2265600, HFPLL, 1, 118}, L2 (19), 935000, 716},
{1, {2457600, HFPLL, 1, 128}, L2 (19), 970000, 802},
{0, 0}} {
};
Sources:
1) http://www.anandtech.com/show/7846/...-snapdragon-800-and-801-clearing-up-confusion
2) http://tieba.baidu.com/p/2870895640 (Use Google Translate)
!! SECTION 3 !!
Click to expand...
Click to collapse
Fully Copied from Source: http://forum.xda-developers.com/galaxy-s3/general/guide-fastest-to-properly-undervolt-cpu-t2072087
Click to expand...
Click to collapse
===========================================
Hello.
Undervolting your CPU has always been a daunting task - there's so many CPU steps, if you pick say -100mV to all frequency steps and you get a reboot, how do you work out which step (or steps!) is causing the problem? If you undervolt -25mV on one frequency, then wait a couple of days to make sure it's stable, then reduce the same frequency by another 25mV.. you'll still be undervolting a year later.
This thread is my tutorial on how to do a best effort at quickly and safely undervolting your phone CPU.
First of all - is undervolting your CPU worth it?
Initially it was thought not to make much difference, but after some serious testing (thanks AndreiLux), "we" decided that it was a good idea. I also did my own basic testing, and it looks like it's worth it.
What are the advantages of undervolting?
Better battery life
Cooler phone, especially useful if you overclock your CPU
What are the disadvantages of undervolting?
That's the great thing! Really the worst that can happen is your phone freezes or reboots. The steps below should eliminate all of that. Once you have undervolted your CPU to just above its freeze/crash levels, there are no disadvantages!
Note: I have had some minor data loss (eg an app forgets a setting) after an undervolting related crash, but it was rare and I believe has to do with the Perseus kernel "Enable dynamic FSync" setting. I note below how to mitigate against this.
What do you need?
A rooted phone, and a kernel that supports undervolting. Perseus and Siyah will work, but any kernel should be fine that supports SetCPU's undervolting schema
SetCPU or you can use a combination of STweaks and Stability Test (use STweaks for setting the frequency and voltage, and use Stability Test's Classic Test for the stress test)
A paper and a pen - I used Sticky Notes as I was at a computer for most of the process
Some patience
Let’s begin.
Open SetCPU. You’ll be greeted by the Main screen which has the min/max CPU frequencies, the governor options, and the IO scheduler options. Reduce the max CPU frequency to the lowest step. On the SGS3 this will be reducing 1400MHz down to 200MHz, so you now have both the min and the max set at 200MHz. The phone will get pretty slow at this point. Ensure the Set on Boot option is unticked
Set the governor to Performance (note: you have to make sure all cores of your CPU are being used. In a complex kernel such as Perseus, you'll have to go into STweaks and set the CPU hotplug lock to 4 so all 4 cores are used. Also note there appears to be a bug in Perseus at the time of writing: you have to set the hotplug lock BEFORE you change the governor to performance)
Move to the Voltages screen
Ensure the Set on Boot option is unticked, and scroll down to the lowest setting, and change it to something low, like 700mV, and then apply it (click the third icon from the right at the top of the screen, a rectangle with a tick on it) . This first setting is always a bit of guess and check, and to be honest you’re hoping for the phone to freeze or crash on this first one. Has it frozen? If so move on to the next step. If not, reduce it by a further 25mV and apply again, repeat until your phone freezes or reboots.
So, you have undervolted too far. Reboot the phone, and perform steps 1-3 again. At step 4, use the voltage that crashed your phone +25mV (eg if it crashed at 675mV, this time set it to 700mV). Now, you have a very slow phone running a low voltage that doesn’t immediately crash it. Move on to the next step
An easy crash test I found was simply allowing the phone to go into deep sleep, and waking it up again. To do this, unplug your phone if it’s charging, and turn the screen off. At this point I usually wrote the time down on my piece of paper, as well as what frequency and voltage I was testing as I’m prone to forget these things. Wait 5 minutes with the screen off (and make sure no notifications have come in while the screen is off – this wakes the phone up and you’ll have to wait another 5 mins), then turn the phone on. You’ll know it’s gone into deep sleep as there’ll be a slight delay before the screen turns on as compared to no delay when turning it off and immediately back on again. If the phone doesn’t turn on, go to step 5. If your phone comes out of deep sleep OK, move on to the next step.
Now, we stress test. In SetCPU scroll over to the Info screen, and scroll down to the Stress Test option. Start it, and note down the time on your paper/Sticky Notes. Your CPU will now run as hard as it can at the current frequency. Let it run for 15-20 minutes. At the lowest frequency it will be pretty laggy and slow, if you think it has frozen always give it 30 seconds to see if it picks up again. If it gets stuck for over a minute, you probably have a crash. Go to step 5. If after 15-20 minutes it’s still running, you have found your first stable(ish) voltage for that frequency! At this point I saved the voltages in SetCPU by pressing the diskette icon. To ensure the changes are written to disk turn the phone screen off for 5 seconds then turn it back on again.
We are now ready for the next frequency. There’s pretty much no way a frequency will run stably on a lower voltage than a frequency below it, so our first voltage for the next frequency up should be the same stable voltage we found for the previous frequency. For example if we found a stable voltage of 725mV on the 200MHz frequency, our first test voltage for 300MHz should be 725mV. Write this down with the frequency on your paper. In the Main screen of SetCPU, change the max frequency to the next step up. Then, in the Voltages screen, adjust the voltage to be the same as the lower frequency, as discussed above. If your phone immediately freezes or reboots, move to the next step. If not, go to step 10.
So, you have undervolted too far, again! Reboot your phone, open up SetCPU, and in the main screen ensure the max frequency is set to the frequency we’re testing. Give the sliding bar things a jiggle to apply it. Ensure the governor is set to Performance by pressing it on the lower left part of the screen. Move to the Voltages screen, and you’ll either see your previous “saved” voltage values ready to be applied in dark grey under the “current” voltage settings, or you’ll have lost your “saved” voltage settings. If you have lost them, never fear; just restore the latest settings by clicking the first from the right icon at the top (a square with an arrow pointing outwards). Adjust the frequency we’re testing’s value to 25mV more than the value you last used when it crashed, and apply it. If it crashes immediately, repeat this step. If not, move on
We now start the two tests in steps 6 and 7 again, but this time if your phone crashes or freezes, go to step 9. If it completes the deep sleep and stress test tests, go to step 8 for the next frequency test.
Sorry for the complexity here, but it was the easiest way I could write it without repeating myself too much. The TL;DR version goes like this:
Pick the lowest untested frequency, set the max frequency to this and the governor to Performance, and find the lowest voltage that doesn’t immediately crash the phone
Put the phone into deep sleep, and see if it crashes. If it does, increase the voltage for the current frequency we’re testing by 25mV and test again. If not, move on
Run a stress test on the phone for 15-20 minutes. If it crashes, raise the voltage by 25mV and go to step B. If it doesn’t crash the current frequency is now tested. Go to step A
You now have a set of frequencies that shouldn’t immediately crash the phone. Set the min and the max frequencies back to normal, and set the governor back to your usual governor. At this point for me I was able to use the phone for about 2 hours before I had my first crash. How running a stress test on each frequency for 20 minutes didn’t pick up this crash situation I’m not sure, but it didn't.
After screwing around for a while I found the easiest solution was to just raise each frequency step by 25mV and then continue every day usage. That was enough to stabilise my phone. If it still crashes for you, keep raising all the values by 25mV until it settles down. After a day or two of no crashes you can start slowly one by one reducing each step by 25mV again to find out which step caused the crash.
After that, you should be done!
===========================================
Please hit "thanks button", if the above information is somehow helpful to you
Thank you all

Reserved 1

Reserved 2

Great info! PVS8 here...

shojus said:
Great info! PVS8 here...
Click to expand...
Click to collapse
Thank you friend..

PVS 6
Manufactured JUNE 21.2014

ADJack said:
PVS 6
Manufactured JUNE 21.2014
Click to expand...
Click to collapse
Have you tried undervolting ?

Mnt-XDA said:
Have you tried undervolting ?
Click to expand...
Click to collapse
Besides rooting and installing PhilZ, I haven't tried anything else.

shojus said:
Great info! PVS8 here...
Click to expand...
Click to collapse
Thank you

1 here...rather disappointing

B3L13V3 said:
1 here...rather disappointing
Click to expand...
Click to collapse
Nothing to disappoint... because it does not indicate speed.
Its about the voltage required to reach a certain speed..
Mine is 2... but I configured it by undervolting
and its now working same as PVS 7 voltage table...
You can try that... and let me know in case of any issue..:good:

PVS7 here. Currently running tests at PVS15.
Will be interesting if it works.
Sent from my GT-N8010 using XDA Premium 4 mobile app

AJ RIMMER! said:
PVS7 here. Currently running tests at PVS15.
Will be interesting if it works.
Sent from my GT-N8010 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
PVS 15 table not worked for me...
7 worked..
I need voltage table form PVS 8 to PVS 14, Can somebody find those for us ?
Then I will try 8,9,10... 14...

PVS 4 here. Undervolted slightly lower than PVS 15. Here's my table:
300Mhz - 700mV
422Mhz - 700mV
652Mhz - 700mV
729Mhz - 700mV
883Mhz - 725mV
960Mhz - 725mV
1036Mhz - 750mV
1190Mhz - 750mV
1267Mhz - 775mV
1497Mhz - 800mV
1574Mhz - 825mV
1728Mhz - 850mV
1958Mhz - 875mV
2265Mhz - 950mV
2457Mhz - 1000mV

And that runs smoothly for you? No problems?
I ran the stress test for about 2 hours and it didn't even blink.
CM11s. Franco r7 Kernel. TWRP 2.7.1.0
Sent from my One, using the XDA app.

No problems for 3 days, ran scaling stability test for 30m and classic for 20m on each freq. I could probably go lower on some, but I bumped everything up by 25mV after they passed the stress test just to be safe.

Well, I just opened FKU and undervolted globally -50mV, used it for some days, and now running on -75mV since yesterday. No probs until now.
I touched global -100mV today, it crashed after screen off/on. Too lazy for finetuning though, the phone's running good enough.
My OPO is PVS8.
Table:
300Mhz - 700mV
422Mhz - 700mV
652Mhz - 700mV
729Mhz - 700mV
883Mhz - 710mV
960Mhz - 720mV
1036Mhz - 730mV
1190Mhz - 750mV
1267Mhz - 760mV
1497Mhz - 790mV
1574Mhz - 800mV
1728Mhz - 825mV
1958Mhz - 870mV
2265Mhz - 930mV
2457Mhz - 965mV

D4rkSoRRoW said:
Well, I just opened FKU and undervolted globally -50mV, used it for some days, and now running on -75mV since yesterday. No probs until now.
I touched global -100mV today, it crashed after screen off/on. Too lazy for finetuning though, the phone's running good enough.
My OPO is PVS8.
Table:
300Mhz - 700mV
422Mhz - 700mV
652Mhz - 700mV
729Mhz - 700mV
883Mhz - 710mV
960Mhz - 720mV
1036Mhz - 730mV
1190Mhz - 750mV
1267Mhz - 760mV
1497Mhz - 790mV
1574Mhz - 800mV
1728Mhz - 825mV
1958Mhz - 870mV
2265Mhz - 930mV
2457Mhz - 965mV
Click to expand...
Click to collapse
Is it the default table for PVS 8 or your modified table ?

Mnt-XDA said:
Is it the default table for PVS 8 or your modified table ?
Click to expand...
Click to collapse
Modified after 75mV UV.

Okay, I'm confused.
I used this command
Code:
su
dmesg | grep PVS
and got this
Code:
<6>[ 1.020314] clock-krait-8974 f9016000.qcom,clock-krait: PVS config version: 1
<6>[ 1.020587] clock-krait-8974 f9016000.qcom,clock-krait: PVS bin: 8
<6>[ 1.020741] clock-krait-8974 f9016000.qcom,clock-krait: PVS version: 1
What does that mean exactly?
I think it's the slowest version because it's obviously version 1.
The second line just tells us what voltage settings are used right?

Related

Hey all, really simple here, just curious as to what settings people have when undervolting their cpu's. Thanks in advance.

1200 - 1.2875
1100 - 1.25
800 - 1.1875
600 - 1.0
300 - .8125
I think this is about the norm.

cm7 n155 / conservative / 16 bit / nenamark1 22.9 neocore 29.9 quadrant 2642
300 @ .8125v
600 @ 1.0v
800 @ 1.1625v
1100 @ 1.2375v
1200 @ 1.2875v

Hey Guys,
what about having a thread, dedicated to Benchmarks, Performance Settings, Firmware, Tweaks and other Drugs you are on
So here is what I'm using:
RAZR HD - XT925
- Stock ROM
- Unlocked BL
- Rooted
- Android Tweaker -> Autotweak
Quadrant Score:
- 5032
CPU: 9789
Memory: 8727
I/O: 3439
2D: 1000
3D: 2206
Antutu Benchmark:
-10344
CPU Integer: 1536
CPU Float: 2260
2D: 1087
3D: 2801
Database I/O: 555
SD-Card write: 149
SD-Card read: 191
AnTuTu 3dRating:
3d Score 2899
Off-Screen: 820
Feel free to post your Settings and Benchmarkresults
Greetz Esok

hi
i did some research regarding the topic and want to share my finds/work with everyone.
the comparison shows all pvs of MSM8974AB 2.3ghz (one m8 - pro_rev1_2p3g) and MSM8974AC (gs5 - pro_rev1_2p5g).
all table data manually taken from latest one m8 kernel sources.
in addition i added one m7 (APQ8064) and lumia 930 (2p2g) chips (pvs0 and pvs6) for intresting comparison.
with this guide in combination with root access, custom kernel and trickster mod you can find out your cpu's pvs bin (compare default voltages).
alternative to find your pvs: adb shell from recovery (su) "cat /proc/last_kmsg | grep bin: -i".
also it serves as a template to try out higher pvs settings on your cpu.
as you see, qualcomm did some impressive work with binning and trying to get most out of each cpu.
however there is usually still some headroom for optimizations if you do some efforts.
same research i already did for the m7 (APQ8064 compared to APQ8064T of galaxy s4) if someone is intrested (let me know).
happy clocking/volting!
i take no responsibilities for potential harm you do to your device. all on your own risk.
please share your results of which pvs level works on your personal chip (also tell stock pvs value of course).
preview:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
download link:
PVS Research.xls
best max frequency (sweet performance/power spot):
MSM8974AB 2.3ghz - 1.34ghz
MSM8974AC 2.5ghz - 1.57ghz
MSM8974v2 2.2ghz - 1.34ghz
APQ8064 1.7ghz - 1.24ghz
APQ8064T 1.9ghz - 1.35ghz
best screen-off frequency (this varies if you try higher pvs settings):
Snapdragon 801 2.3ghz MSM8974AB - One M8
MSM8974AB 2.3ghz PVS 0 - 300mhz
MSM8974AB 2.3ghz PVS 1 - 346mhz
MSM8974AB 2.3ghz PVS 2 - 422mhz
MSM8974AB 2.3ghz PVS 3 - 499mhz
MSM8974AB 2.3ghz PVS 4 - 576mhz
MSM8974AB 2.3ghz PVS 5 - 652mhz
MSM8974AB 2.3ghz PVS 6 - 499mhz
MSM8974AB 2.3ghz PVS 7 - 576mhz
MSM8974AB 2.3ghz PVS 8 - 652mhz
MSM8974AB 2.3ghz PVS 9 - 729mhz
MSM8974AB 2.3ghz PVS 10 - 806mhz
MSM8974AB 2.3ghz PVS 11 - 883mhz
MSM8974AB 2.3ghz PVS 12 - 960mhz
MSM8974AB 2.3ghz PVS 13 - 1036mhz
MSM8974AB 2.3ghz PVS 14 - 960mhz
MSM8974AB 2.3ghz PVS 15 - 1036mhz
Snapdragon 801 2.5ghz MSM8974AC - Galaxy S5
MSM8974AC 2.5ghz PVS 0 - 422mhz
MSM8974AC 2.5ghz PVS 1 - 499mhz
MSM8974AC 2.5ghz PVS 2 - 576mhz
MSM8974AC 2.5ghz PVS 3 - 652mhz
MSM8974AC 2.5ghz PVS 4 - 729mhz
MSM8974AC 2.5ghz PVS 5 - 806mhz
MSM8974AC 2.5ghz PVS 6 - 652mhz
MSM8974AC 2.5ghz PVS 7 - 729mhz
MSM8974AC 2.5ghz PVS 8 - 806mhz
MSM8974AC 2.5ghz PVS 9 - 883mhz
MSM8974AC 2.5ghz PVS 10 - 960mhz
MSM8974AC 2.5ghz PVS 11 - 1036mhz
MSM8974AC 2.5ghz PVS 12 - 1113mhz
MSM8974AC 2.5ghz PVS 13 - 1190mhz
MSM8974AC 2.5ghz PVS 14 - 1113mhz
MSM8974AC 2.5ghz PVS 15 - 1190mhz
Snapdragon 800v2 2.2ghz MSM8974v2
MSM8974v2 2.2ghz PVS 0 - 345mhz
MSM8974v2 2.2ghz PVS 1 - 499mhz
MSM8974v2 2.2ghz PVS 2 - 422mhz
MSM8974v2 2.2ghz PVS 3 - 499mhz
MSM8974v2 2.2ghz PVS 4 - 576mhz
MSM8974v2 2.2ghz PVS 5 - 499mhz
MSM8974v2 2.2ghz PVS 6 - 576mhz
Snapdragon 600 1.7ghz APQ8064 - One M7
APQ8064 1.7ghz PVS 0 - 594mhz
APQ8064 1.7ghz PVS 1 - 594mhz
APQ8064 1.7ghz PVS 2 - 702mhz
APQ8064 1.7ghz PVS 3 - 810mhz
APQ8064 1.7ghz PVS 4 - 702mhz
APQ8064 1.7ghz PVS 5 - 810mhz
APQ8064 1.7ghz PVS 6 - 702mhz
Snapdragon 600 1.9ghz APQ8064T - Galaxy S4
APQ8064T 1.9ghz PVS 0 - 702mhz
APQ8064T 1.9ghz PVS 1 - 702mhz
APQ8064T 1.9ghz PVS 2 - 702mhz
APQ8064T 1.9ghz PVS 3 - 810mhz
APQ8064T 1.9ghz PVS 4 - 702mhz
APQ8064T 1.9ghz PVS 5 - 702mhz
APQ8064T 1.9ghz PVS 6 - 702mhz
best min frequency:
lowest possible setting (300mhz in case of MSM8974)
i highly recommend to run those values (exept if you are actually playing demanding 3d games).
use trickster mod frequency lock feature to do so. you will experience amazing battery life.
how to get the maximum battery life:
if you have a MSM8974AB pvs 6 for example, try the following steps:
try the next higher pvs levels (pvs7). don't try AC pvs values on AB chips.
AB chips are binned for lower frequencies while AC are binned for higher frequencies (duh).
so if you have a AB chip, work your way up the AB pvs values until you have freezes or similar and move back.
if you have a AC chip, work your way up the AC pvs values etc...
if you found highest setting that does not cause any problems after intensive testing and usage:
congratulations, you did it. :good:
how to get the maximum frequency:
first try higher than stock maximum clock and see how it behaves.
if you don't reach your desired clockspeed, try the next lower pvs setting of your chip. yes, i said LOWER.
this gives the processor more voltage to reach higher overclocks.
i don't recommend it tho since we all want our phones to last as long as possible usually.
signs of too high overclock:
device lockups (not responding) or sudden reboots during heavy load.
signs of too low voltage:
problems with audio when screen off, long screen wakeup time, lockups and reboots even without cpu-load.
caused by not enough voltage for low frequency levels usually.
snapdragon 805 infos:
HD2Owner said:
here you go. i digged in the kernel sources and found it.
2.7GHz RC1 - speed2-bin-v1 (PVS levels 0-15)
2.7GHz RC0 - speed2-bin-v0 (PVS levels 0-15)
2.5GHz RC1 - speed1-bin-v1 (PVS levels 0-15)
2.5GHz RC0 - speed1-bin-v0 (PVS levels 0-15)
2.3GHz RC1 - speed0-bin-v1 (PVS levels 0-15)
2.3GHz RC0 - speed0-bin-v0 (PVS levels 0-15)
there seem to be two different variants of the 805 (RC0 and RC1).
RC0 seems to use less voltage at higher frequencies.
RC1 seems to use less voltage at lower frequencies.
the voltage tables you can take from the attached txt.
i also attached a txt containing how the bus clocks behave in relation to the cpu-frequency.
snapdragon 805 pvs 2.7ghz RC0.txt
snapdragon 805 pvs 2.7ghz RC1.txt
snapdragon 805 pvs 2.5ghz RC0.txt
snapdragon 805 pvs 2.5ghz RC1.txt
snapdragon 805 pvs 2.3ghz RC0.txt
snapdragon 805 pvs 2.3ghz RC1.txt
snapdragon 805 bus ratios.txt
Click to expand...
Click to collapse
enjoy and leave a thanks if you like it please.
edit v2:
fixed some flaws (22 downloads of v1)

@HD2Owner, seems like this would be better in an Original Dev section?
I realize that there's no place on XDA anymore without non-dev clutter, but this information - and a discussion of it - would seem to be better alongside kernel work than in the same section as "India chat", "British chat", "USA chat", and "I'm too lazy to read any thread so I'm going to post a question that's been answered 50294 times in the past 24 hours."
(I'd request a mod to move it, but it's your thread...)
Take care
Gary

sure.. it's not actual development but closely related research yes.

Sorry for the n00bish question, but what can I actually do with this? Im guessing some kind of undervolting / overclocking?
I am running ElementalX Kernel and have the Trickster Mod app installed.
Cheers
Stewart

StuMcBill said:
Sorry for the n00bish question, but what can I actually do with this? Im guessing some kind of undervolting / overclocking?
I am running ElementalX Kernel and have the Trickster Mod app installed.
Cheers
Stewart
Click to expand...
Click to collapse
Yea it's for understanding where you device Falls on the overclockability / how much voltage you'd need at different OC rates scale

I am in touch with trickster mod devs.
saving presets does not work yet.
when they fixed it, I will release all pvs presets.

Code:
cat /proc/last_kmsg | grep bin: -i
[ 0.321444] c1 1 clock-krait-8974 f9016000.qcom,clock-krait: Speed bin:
1
[ 0.321460] c1 1 clock-krait-8974 f9016000.qcom,clock-krait: PVS bin: 13
HTC One with PVS 13 here but happily running the following:
Code:
300MHz - 725mV
422MHz - 725mV
652MHz - 725mV
729MHz - 725mV
883MHz - 735mV
960MHz - 745mV
1036MHz - 755mV
1190MHz - 775mV
1267MHz - 785mV
1497MHz - 815mV
1574MHz - 825mV
1728MHz - 845mV
1958MHz - 880mV
2265MHz - 940mV
2457MHz - 975mV

HD2Owner said:
same research i already did for the m7 (APQ8064 compared to APQ8064T of galaxy s4) if someone is intrested (let me know).
Click to expand...
Click to collapse
I'd be very interested in that
I'm using an S4

Mr_Bartek said:
Code:
cat /proc/last_kmsg | grep bin: -i
[ 0.321444] c1 1 clock-krait-8974 f9016000.qcom,clock-krait: Speed bin:
1
[ 0.321460] c1 1 clock-krait-8974 f9016000.qcom,clock-krait: PVS bin: 13
HTC One with PVS 13 here but happily running the following:
Code:
300MHz - 725mV
422MHz - 725mV
652MHz - 725mV
729MHz - 725mV
883MHz - 735mV
960MHz - 745mV
1036MHz - 755mV
1190MHz - 775mV
1267MHz - 785mV
1497MHz - 815mV
1574MHz - 825mV
1728MHz - 845mV
1958MHz - 880mV
2265MHz - 940mV
2457MHz - 975mV
Click to expand...
Click to collapse
that's what i want to see here.. :highfive:
i will enhance the first post later with m7 vs gs4.
probably also some general guidelines.
but i need as much info as i can gather from different bins and experiences to make conclusions.
the plan is to post trickster mod voltage settings for all 32 pvs levels when export/import works.
until then you need to manually try the values. please stick to the posted values or report in detail.
@ moderators: feel free to move the thread where it fits best

I am using elementalX with undervolt -45. The values I get from trickster mod do they take into account the undervolting of the kernel or is it something more global that trickster mod does not show?

PVS info are unavailable on the galaxy S5 and the command on the terminal emulator isn't working,with that in mind checking the PVS binning is done in this directory :
/sys/devices/system/soc/soc0/soc_pvs

andreasyeah said:
I am using elementalX with undervolt -45. The values I get from trickster mod do they take into account the undervolting of the kernel or is it something more global that trickster mod does not show?
Click to expand...
Click to collapse
The issue with elementalX is that the undervolt only works for the lowest clock value and doesn't apply for the rest. Check in Trickster Mod and you'll notice that it's only applied to 300MHz.

also, even without root access, you could use adb bugreport >bugreport.txt then grep the file for infos.
On my note3 with Android 4.3 I don't get any Bin strings but ...

Hmm I can't get over 2.4ghz.
Locks up. Although elemental voltages seem a lot lower than those cited in the document attached to this thread.
I do wonder, is kernel tweaker successfully amending voltages?
I tried to ramp the voltages up whilst in power saving mode, then disabled power saving mode, but it locks up and restarts.
I would of hoped 2.5ghz is easily attainable as I thought we had the same processor but clocked to a lower frequency compared to the S5 etc.
Would appreciate some help with oc'ing.

I am PVS 12 and I've set the voltages specified in the spreadsheet with stock frequency and when I am running Antutu X, CORE 1 is stuck at 1%. I am not sure if this happens with default voltages too or if it's kernel related because I am running ElementalX 0.19. I've rebooted and I am trying to reproduce it now
EDIT: I've tested it with stock voltages, and I get the same problem. I am using Insertcoin ROM and the usage statistics of Insertcoin Control on the notifications(picture attached. Picture just shows the tool I am using. Not the moment when CORE1 locks.)
Is there a chance that it's not showing correct values for CORE1? Is there another app I can use to test the core usage while benchmarking?
EDIT2: I've found the problem. Everything works fine when I uninstall trickster and then restart. After I install trickster and run the benchmark, CORE1 locks at 1%-5% while others are 100%. I don't change any settings on trickster. Stock voltages and it does not even apply any settings on boot. If it is installed, no matter how many reboots I do, the problem persists. If I uninstall it and reboot, the problem is gone. I am really confused
EDIT3: Will it work if I change the UV_mV_table in /sys/devices/system/cpu/cpuX/cpufreq for each CPU Core? I want to change the voltage without Trickster because of the lock issue. Maybe we can make a flashable for each PVS that changes that file, so we don't have to use trickster

added some more infos and conclusions in first post.

Just an addition.
You can get the pvs number in HTC ONE M8 with:
Code:
su
cat /sys/module/clock_krait_8974/parameters/pvs_number

andreasyeah said:
Just an addition.
You can get the pvs number in HTC ONE M8 with:
Code:
su
cat /sys/module/clock_krait_8974/parameters/pvs_number
Click to expand...
Click to collapse
I am something doing wrong ?

Onem8 said:
I am something doing wrong ?
Click to expand...
Click to collapse
Are you doing this while in recovery or while it's booted up?
You can try to navigate to that path using a file explorer and see if it's actually there. Make sure you have a file explorer with root capabilities. If it's not there, I have no idea why!

andreasyeah said:
Are you doing this while in recovery or while it's booted up?
You can try to navigate to that path using a file explorer and see if it's actually there. Make sure you have a file explorer with root capabilities. If it's not there, I have no idea why!
Click to expand...
Click to collapse
This are the only files i have..

Anyone no where the CPU/ PVS binning is located on the N6P 

I'm not really sure, but I found this in the output of the dmesg command (straight after a reboot):
Code:
[ 0.385299] cpu-clock-8994 f9015000.qcom,cpu-clock-8994: using A57 speed bin 0 and pvs_ver 0

JustinTrouble said:
I'm not really sure, but I found this in the output of the dmesg command (straight after a reboot):
Code:
[ 0.385299] cpu-clock-8994 f9015000.qcom,cpu-clock-8994: using A57 speed bin 0 and pvs_ver 0
Click to expand...
Click to collapse
I got the same, I'd like to know what binning these have and which is best. Doesn't look like thats the binning unless it starts at 0
Sent from my Nexus 6P using Tapatalk

I also had a look at another 6P, which reported the same: cpu-clock-8994 f9015000.qcom,cpu-clock-8994: using A57 speed bin 0 and pvs_ver 0
I wonder if the CPU binning is no longer reported in dmesg.
I wonder if we could determine it from cpr_adjust_init_voltages, which differed on my two 6Ps.
I can't remember where in Android the voltages are defined, to compare them.
The first 6P:
Code:
[ 0.273414] cpr_adjust_init_voltages: apc0_corner: adjusted initial voltage[2]: [B]880000 -> 855000[/B] uV
[ 0.273435] cpr_adjust_init_voltages: apc0_corner: adjusted initial voltage[3]: 930000 -> 905000 uV
[ 0.273464] cpr_pvs_init: apc0_corner: pvs voltage: [[B]780000 855000[/B] 905000[B] 1145000[/B]] uV
[ 0.274333] cpr_adjust_init_voltages: apc1_corner: adjusted initial voltage[3]: 950000 -> 925000 uV
[ 0.274355] cpr_adjust_init_voltages: apc1_corner: adjusted initial voltage[4]: 1145000 -> 1110000 uV
[ 0.274375] cpr_pvs_init: apc1_corner: pvs voltage: [840000 840000 925000 1110000] uV
The second 6P:
Code:
[ 0.272297] cpr_adjust_init_voltages: apc0_corner: adjusted initial voltage[2]: [B]860000 -> 835000[/B] uV
[ 0.272318] cpr_adjust_init_voltages: apc0_corner: adjusted initial voltage[3]: 930000 -> 905000 uV
[ 0.272346] cpr_pvs_init: apc0_corner: pvs voltage: [[B]760000 835000[/B] 905000 [B]1125000[/B]] uV
[ 0.273220] cpr_adjust_init_voltages: apc1_corner: adjusted initial voltage[3]: 950000 -> 925000 uV
[ 0.273242] cpr_adjust_init_voltages: apc1_corner: adjusted initial voltage[4]: 1145000 -> 1110000 uV
[ 0.273261] cpr_pvs_init: apc1_corner: pvs voltage: [840000 840000 925000 1110000] uV

Nobody has found where this information is located?
Sent from my Nexus 6P using Tapatalk

I would like to know where the CPU binning is located since its not in the usual place like on the 32bit SD805

Any updates?

I'm curious as well. I looked thru system with root explorer but had no luck.

I am still very interested in some insight into this

App to detect CPU quality and bin
Hi guys,
I would like to let you know that we've developed an app that should help identify CPU bin differences.
The app will inform you of your CPU bin if your device is rooted, otherwise, it runs a 'benchmark' to detect how good/bad your CPU is relative to other user's devices.
On older SoCs, like the Snapdragon 800, it was straightforward to determine the quality of the CPU from the CPU bin number. This is no longer the case with SoCs containing heterogeneous cores such as the Nexus 6P. Newer SoCs use AVS (Adaptive Voltage Scaling) rather than PVS (Passive Voltage Scaling) and thus, the voltages are determined by the device at runtime. To the best of our knowledge, there is no longer a simple CPU bin number that tells you how good or bad your chip is. Even if you did get hold of a CPU bin number, is a higher bin number really better? (dl.acm.org/citation.cfm?id=3032982)
Today, we're left with trying to determine the quality of our devices by running benchmarks and comparing the scores obtained. One of the biggest problems with benchmarks is that they don't account for temperature; both CPU and ambient. A good CPU running at room temperature can never match up to a bad CPU running inside, say, a refrigerator. Thus, benchmark results are skewed in favor of those that ran at lower ambient temperatures. Often, in benchmarks like Antutu, we're left with the scores of our device and the scores of the top 50 devices overall; a list in which our device model may not even make an appearance.
Our app is designed to account for both CPU temperature and ambient temperature. Comparisons between the results of your phone and others of the same make & model are further filtered based on temperature.
In other words, if you ran an experiment in a very cold environment, your results are compared against other iterations that ran under similar conditions.
We've had good success in identifying the quality of CPUs on the Nexus 5 and Nexus 6. We're trying to get the word out and collect data from a larger set of devices. Do note that the app is experimental and may have a few bugs. However, I'm actively working on improving it to providing better and more accurate results. Our end goal is to be able to allow users to run our app and get to know the quality of their smartphone before they buy it.
The app is available for Android on the PlayStore at:
Code:
play.google.com/store/apps/details?id=edu.buffalo.cse.phonelab.smartphonesexposed

These 3 are given:
Balanced = 1 GHz CPU / 468 MHz GPU
Quick = 1.4 GHz CPU / 768 MHz GPU
Performance = 1.7 GHz CPU / 920 MHz GPU
However, it has two other, low-end settings.
Power Save:
Efficiency:
These two lower settings do save on battery, but you can't even emulate PS1 games with them properly. It makes me wonder what the clock speeds for those two are, though.

KernelTasker allows for more, if you are rooted.