Hi.
I am recently going through the process of finding out how low I can push the voltage on the snapdragon 600 of your beloved Nexus 7.
But I someow get the impression that the voltage is not sticking after setting it.
Why you may ask?
Because I am running on 486 MHZ and 700mv. thats like, -275mv of stock., although it may be possible because I have a ACPU BIN 6 CPU (yay!) so it should in theory undervolt better.
Added a screenshot of TricksterMod.
Now to my question: Is it possible for the CPU to operate at this low undervolt? Or are my voltages not sticking?
PS: I am running on the lates Glitch Kernel
Related
is it possible to overclock above 768mhz? my phone never gets warm and battery lasts 2+ days, completely stable at this speed, i want to learn how i can edit a kernel and increase the cpu voltage ever so slightly and increase max cpu clock and see whats stable, could you help me?
i think you will just start to get kernel panics if you try to go much higher .
i have another phone (lg 500) also with the same arm6 cpu that comes clocked at 600 from factory. i have the option to oc to 825 with custom kernel but it always panics at 806 and is stable at 787.
So i think if you want a faster phone go buy one
massigann said:
i have another phone (lg 500) also with the same arm6 cpu that comes clocked
Click to expand...
Click to collapse
Nope.
P500 has an ARM11 MS7227 processor
Wildfire has an ARM11 MS7225 processor.
http://xi0.info/qualcomm-chips-kernel-arm-phones_7000.html
lol the chipset for the wildfire is MSM7225 but the cpu is arm6/11? on half of the sites is arm6 the other arm11..
Hi I have mine set to 710 and any higher starts getting random reboots.
But overclocking any higher than 768, your risking a chip melt or definitely shorting its life.
Ok so i have cm7.2 rc1 instaled with the new kernel. I've changed many different roms in the past to find out i cant overclock over 768 w/o the phone crashing. Anyway yesterday i searched the forum and found out i can overclock to more if i change the governor to userspace. It did work however i ran antutu benchmark and i saw the folowing.
At 864 governor userspace i get 1328 points.
At 844 governor userspace i get 1479 points.
At 825 governor userspace i get 1486 points
At 806 governor userspace i get 1675 points.
At 768 governor performance i get 1644 points.
So my question is could it be that antutu is wrong or is it some something buggy with the kernel or my device.
Edit. And also something that i noticed at 864 the cpu is what lowers the score drasticly and on 844 and 825 its the 2d graphics. I could post SS later cuz i dont have time now if neceserry.
baluuu said:
Ok so i have cm7.2 rc1 instaled with the new kernel. I've changed many different roms in the past to find out i cant overclock over 768 w/o the phone crashing. Anyway yesterday i searched the forum and found out i can overclock to more if i change the governor to userspace. It did work however i ran antutu benchmark and i saw the folowing.
At 864 governor userspace i get 1328 points.
At 844 governor userspace i get 1479 points.
At 825 governor userspace i get 1486 points
At 806 governor userspace i get 1675 points.
At 768 governor performance i get 1644 points.
So my question is could it be that antutu is wrong or is it some something buggy with the kernel or my device.
Edit. And also something that i noticed at 864 the cpu is what lowers the score drasticly and on 844 and 825 its the 2d graphics. I could post SS later cuz i dont have time now if neceserry.
Click to expand...
Click to collapse
reason is because of governor
Keep it at 806 and use whatever governor you'd like to (smartass2 if you want better battery life and high performance only when running apps). Don't set it any higher, as it could melt your phone and it'll definitely drain your battery a lot faster than it should.
Mine runs at 120 - 787 MHz and "ondemand" governor. If I set the upper limit to 806, the phone would crash when under load (e. g. benchmarking). The settings appear to save a bit of power compared to the "default" values, which is probable due to the so-called "race to idle"-effect. Basically "race to idle" means that higher clock frequencies will save power, since the processor gets the work done faster and can enter low-power states earlier than when running on lower clock frequencies, so if you can clock it even higher you should get even better battery life in the long run, even though this might seem counter-intuitive. Only disadvantage with these settings is that the phone lags a bit directly after booting and screen unlocking, but otherwise is really smooth.
My freequency is 245-864 and i have very stable work. But i have extended battarey (2200mah)
This is really strange and probably even stranger to complain about but I want to understand.
I UV on my Note and so far managed to drop to levels I find hard to believe.
200MHz - 600mV
300MHz - 600mV
400MHz - 600mV
500MHz - 600mV
600MHz - 600mV
700MHz - 600mV
800MHz - 600mV
900MHz - 600mV
1000MHz - 600mV
1100MHz - 600mV
1200MHz - 975mV
1300MHz - 975mV
1400MHz - 1000mV
1500MHz - 1050mV
1600MHz - 1100mV
Why is my note able to run at 600mV on all frequencies up to 1100MHz??? At first I thought it was a reporting error and It wasn't really running on those voltages but found breaking points on higher frequencies so eliminated that theory. :silly: Would be to be able to test these frequencies at even lower levels. Anybody know a tool that can do it?
This is the process I followed:
Set the voltage value in STweaks,
Set the max MHz in STweaks to the frequency for which I just dropped the voltage ,
Close STweaks,
Open Voltage Control to confirm that the voltage and max frequency has really been set,
Close Voltage control,
Reboot,
Open Voltage Control again to confirm that the voltage and max frequency is really set,
Close Voltage control,
Reset timings in Android Tuner Free,
Start Stability - Classic Test and verify that the Note is running at the max frequency,
Open some other apps and play around for a while,
Get Stability Test back to foreground and go to sleep (if it is time to sleep)
For all of the above frequency values i ran the Stability Test overnight for at least 4 hours plus for a couple hours while using the phone. Didnt get a single freeze or reboot. The only issue was that while I had it on max 200 MHz the Note was not usable while the 300 and 400 MHz frequencies were annoyingly slow. 500 MHz and up is bearable even with Stability Test running.
Attached are the last status and test screenshots. The Stability Test has been running while I been also using it for calling, messaging, adjusting other app setting and taking screenshots.
I check the frequency timings in Android Tuner Free and it is usually 1-4% on offline, 95-98% on the tested frequency and sometime 1% on the frequency just above the tested one. All other frequency times usually 0%
Any ideas if something funny is going on or is this Note just unbelievably under-voltable???
MutantWizard said:
This is really strange and probably even stranger to complain about but I simply need to understand.
I UV on my Note and so far managed to drop to levels I simply cant believe.
200MHz - 600 mV
300MHz - 600 mV
400MHz - 600 mV
500MHz - 600 mV
600MHz - 600 mV
700MHz - 600 mV
800MHz - 600 mV
Rest of the frequencies are still at stock values
First I copy pasted some UV setting from another post and the Note ran without Issues. Then I started dropping a little bit here and there and at some point got some freezes and reboots but couldnt figure out which frequency was the issue so I returned all to stock and started one by one from 200 MHz. The above is where I got to so far and simply need to understand why or what is happening.
This is the process I followed:
Set the voltage value in STweaks,
Set the max MHz in STweaks to the frequency for which I just dropped the voltage ,
Close STweaks,
Open Voltage Control to confirm that the voltage and max frequency has really been set,
Close Voltage control,
Reboot,
Open Voltage Control again to confirm that the voltage and max frequency is really set,
Close Voltage control,
Reset timings in Android Tuner Free,
Start Stability - Classic Test and verify that the Note is running at the max frequency,
Open some other apps and play around for a while,
Get Stability Test back to foreground and go to sleep (if it is time to sleep)
For all of the above frequency values i ran the Stability Test overnight for at least 4 hours plus for a couple hours while using the phone. Didnt get a single freeze or reboot. The only issue was that while I had it on max 200 MHz the Note was not usable while the 300 and 400 MHz frequencies were annoyingly slow. 500 MHz and up is bearable even with Stability Test running.
Attached are the screenshots of the process at 800 MHz and the Stability Test has been running for almost six hous while I been also using it for messaging, adjusting other app setting and taking screenshots. After about 5 hours of 100% CPU load at 800 MHz the Note is down to 80% battery. Not really sure but it seems quite low power consumption.
I just checked the timings again in Android Tuner Free and 12% on offline, 86% on 800 MHz. All other frequency times 0%
Any ideas if something funny is going on or is this Note just unbelievably undervoltable???
Click to expand...
Click to collapse
1st thing, my STweaks is ver 1.1 but looks a bit different than your screenshots, pls confirm that.
2nd, I too like to underclock but had no idea you could push it as far as you . It's kind of like driving a car low on gas to see how far you can go.
3rd What ROM & kernel you on? I'm on X-Note 3.3 with Adam kernel.
Last, here's a screenshot of my undervolting...I'm kinda embarrassed compared to yours Note the differences in layout of STweak menu.
I'm inspired to go even lower now, my battery life is pretty awesome but I think I can squeeze it more.
tweeny80 said:
1st thing, my STweaks is ver 1.1 but looks a bit different than your screenshots, pls confirm that.
2nd, I too like to underclock but had no idea you could push it as far as you . It's kind of like driving a car low on gas to see how far you can go.
3rd What ROM & kernel you on? I'm on X-Note 3.3 with Adam kernel.
Last, here's a screenshot of my undervolting...I'm kinda embarrassed compared to yours Note the differences in layout of STweak menu.
I'm inspired to go even lower now, my battery life is pretty awesome but I think I can squeeze it more.
Click to expand...
Click to collapse
My STweaks is also 1.1 and guessing the menu difference might be due to different kernel. I am on RedPill, stock ROM and probably irrelevant but TWERP as well.
I have mixed feelings about the achieved UV. Very happy if it is true but suspicious that there is some kind of a reporting error and that I am actually not under-volting it at all.
I will soon update the OP since I have now been now testing the 900 MHz for the last 3 turns. Started at 900 mV then droped to 800 mV and now already running it for a couple hours at 700 mV. I just cant believe that its actually at at this voltage and running without issues.
MutantWizard said:
My STweaks is also 1.1 and guessing the menu difference might be due to different kernel. I am on RedPill, stock ROM and probably irrelevant but TWERP as well.
I have mixed feelings about the achieved UV. Very happy if it is true but suspicious that there is some kind of a reporting error and that I am actually not under-volting it at all.
I will soon update the OP since I have now been now testing the 900 MHz for the last 3 turns. Started at 900 mV then droped to 800 mV and now already running it for a couple hours at 700 mV. I just cant believe that its actually at at this voltage and running without issues.
Click to expand...
Click to collapse
Hmm yes, because you're going so low, it begs the question is the app reading accurate? I mean, you're reeeaaaal low. Would be good for a more knowledgeable person to chip in and give us feedback.
One thing - in your screenshot it shows your max frequency capped at 800MHz. To me that reads you are running only at 50% power. If so, that explains your insane battery life. From steps 900 and above you've left voltage at stock because they're unused. right?
tweeny80 said:
Hmm yes, because you're going so low, it begs the question is the app reading accurate? I mean, you're reeeaaaal low. Would be good for a more knowledgeable person to chip in and give us feedback.
One thing - in your screenshot it shows your max frequency capped at 800MHz. To me that reads you are running only at 50% power. If so, that explains your insane battery life. From steps 900 and above you've left voltage at stock because they're unused. right?
Click to expand...
Click to collapse
Yes higher frequencies still at stock and not used but will be getting to them at their own time. Fact though is that even with cap at current 900 MHz and with Stability test running I can still use the Note normally for any regular tasks. If I don't play games I would never need more speed.
Now updating the OP with the 900 MHz setting and screenshots.
BTW I just realized I added to battery life when transferring screenshots by connecting the Note to the laptop by cable. Battery life still remains to be seen.
Updated the OP with the full range of voltages 200-1600. I don't OC so those will not be doing. But I still have the original question.
Is it possible???
Gets more and more strange. GPU under-clocking and under-volting of following frequencies working for days without any usage issue. I changed the minimum and maximum MHz to include the below frequencies and didn't notice any difference in the Note behavior / performance. When running the stability test with GPU testing included I don't get any errors if running under 2 hours but if I leave it overnight the test does crash at some point in time without any other ill effect. I only know that it crashed coz it disapears and it tells me it crashed when the next day I re-start the test.
54MHz - 600mV
108MHz - 600mV
160MHz - 600mV
266MHz - 600mV
350MHz - 600mV
The fact though is I don't understand what to expect as an issue when under-clocking or under-volting the GPU.
Mate, you're still at it!?
Rereading your data, I strongly suggest you post these stats in whatever thread belongs to the kernel and/or tuner app you're using.
My overseas Singaporean work colleagues would say 'cannot be, cannot be.....'
tweeny80 said:
Mate, you're still at it!?
Rereading your data, I strongly suggest you post these stats in whatever thread belongs to the kernel and/or tuner app you're using.
My overseas Singaporean work colleagues would say 'cannot be, cannot be.....'
Click to expand...
Click to collapse
Yea slowly trying one by one new settings and letting it run for a while so that when I go to the next setting and experience an issue I am sure its the newest setting that's causing it.
Thanks will do as suggested.
I am using ElementalX kernel on stock 4.4.4 android. I have to OC set to 1.944GHz currently. AnTuTu bench at 1.944GHz and 450MHz GPU gives me between 24-25k result. Now if I lower the CPU to 1.89GHz it drops to 21k. And if I go back to stock freq I get 19k. Something does not seem right in the test results as related to the frequencies. Question is this: Are there sweet spots in the frequency range for the CPU?
P.S. I know many people dislike benchmarks...I'm using it for comparative purposes...
mrcoffee1985 said:
I am using ElementalX kernel on stock 4.4.4 android. I have to OC set to 1.944GHz currently. AnTuTu bench at 1.944GHz and 450MHz GPU gives me between 24-25k result. Now if I lower the CPU to 1.89GHz it drops to 21k. And if I go back to stock freq I get 19k. Something does not seem right in the test results as related to the frequencies. Question is this: Are there sweet spots in the frequency range for the CPU?
P.S. I know many people dislike benchmarks...I'm using it for comparative purposes...
Click to expand...
Click to collapse
It states it in the thread, having cpu at 1.9ghz is not economical with battery consumption and performance, it Is best at 1.7ghz
mrcoffee1985 said:
I am using ElementalX kernel on stock 4.4.4 android. I have to OC set to 1.944GHz currently. AnTuTu bench at 1.944GHz and 450MHz GPU gives me between 24-25k result. Now if I lower the CPU to 1.89GHz it drops to 21k. And if I go back to stock freq I get 19k. Something does not seem right in the test results as related to the frequencies. Question is this: Are there sweet spots in the frequency range for the CPU?
P.S. I know many people dislike benchmarks...I'm using it for comparative purposes...
Click to expand...
Click to collapse
You should monitor your CPU temp and frequency while benching.
You would see that your CPU's temp probably goes above 70°C if not higher and so the kernel thermal throttling policies would downclock your CPU's max freq. in order to keep your CPU "cool".
If you first bench @ 1944MHz then bench @ a litle lower frequency and have very lower score then its not because of the lower freq. but because you did first heat up your CPU @ 1944 and when you re-run @ lower freq. your CPU is already very hot and so does a severe thermal throttling.
Last point : running your CPU @ 1944MHz is not good since thermal throttling while happen every now and then.
Not convinced?
Then simply launch the camera app and try to take a video of 5 mins...your CPU will become so hot that it will downclock to something ridiculously low and your recording will become jerky.
I noticed that I can only overclock the CPU from 1.9 GHZ to 2.1 GHZ with skyhigh kernel. Is there anyway to get it higher?
CentroXer said:
I noticed that I can only overclock the CPU from 1.9 GHZ to 2.1 GHZ with skyhigh kernel. Is there anyway to get it higher?
Click to expand...
Click to collapse
Not with my kernels.
99% of devices won't be stable above that and in any case will not provide any great benefit.
I did have GPU higher but is really a waste and with CPU, due to higher temps invoking thermal throttle, leading to decrease in overall benchmark/performance.
Through my extensive testing, having anything higher than my current max CPU and GPU frequency = PLACEBO
Edit: Maybe things might change compiling with Lollipop source (once released), but unlikely. Obviously I will test though
UpInTheAir said:
Not with my kernels.
99% of devices won't be stable above that and in any case will not provide any great benefit.
I did have GPU higher but is really a waste and with CPU, due to higher temps invoking thermal throttle, leading to decrease in overall benchmark/performance.
Through my extensive testing, having anything higher than my current max CPU and GPU frequency = PLACEBO
Click to expand...
Click to collapse
ok thank you. What about the GPU, any benefits for overclocking it?
Maybe when opening the case and adding some cooling mod to CPU/GPU, the overclocking will do better.