Database Develop

[HACK] Overclocking/Undervolting kernels with Voltage Control support

Hello,
I'm the author of Voltage Control, an application for Galaxy S series to control OC/UV kernels. I don't personally own a Nexus S (and I cant say I will, unless someone want to Nexus S donate one for me ;p).
Voltage Control Lite 4.00 on Android Market!
{
"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"
}
I know there are many apps to control OC, but I dont know any doing UV work.
If anybody is interested in making UV kernel for Nexus S there are some working kernels for SGS (given the hardware similarities some knowledge may be taken from current solutions).
Authors of most OC/UV code are raspdeep and Unhelpful, heres the topic: http://forum.xda-developers.com/showthread.php?t=822027 and second: http://forum.xda-developers.com/showthread.php?t=762171
If you are interested in creating UV kernel working with Voltage Control, I'll give brief explanation how VC works, and how are things done on SGS.
My application communicates with kernel via sysfs interfaces via cat and echo:
mandatory:
Code:
/sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state // to read all states
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq // may be obsolete, didnt make a decision yet
Code:
/sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
key in UV procedure, it represents undervolt for each frequency from highest to lowest; "25 25 50 50 100" means UV highest freq by 25, and lowest by 100
providing additional functionality:
Code:
/sys/devices/system/cpu/cpu0/cpufreq/frequency_voltage_table
Containing all frequencies and corresponding voltages, format:
FREQ STOCK CURRENT
Code:
1120000 1300 1300
1000000 1300 1300
This is useful for determining stock voltages used by the device, because they are needed in voltage calculation. Stock values are hardcoded, but If you want to change them I suggest to implement this table, to let user know at exactly what voltage his device is running.
Third column is obsolete, since VC calculates current (stock-uv) voltage itself might be removed in the future.
Code:
/sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table
This is table where we store enabled ("1") and disabled ("0") state for each frequency;
"0 1 1 0 1" means we disabled highest frequency and second to lowest.
This is useful when kernel developer wants to produce ONE kernel for all OC lovers.
This means there could be one kernel supporting OC frequencies up to 1600Mhz (lets say 1600,1500,1400,1300,1200,1120), and user could choose which ones he wants to use (eg 1400 and 1120, disabling the rest).
I'm aware that Nexus S will receive tremendous attention from developers so I believe that someone might actually come with better implementation (single table consisting of all information needed by VC?)of this mess.
Best idea would be to make one table for all information, so it can be easily parsed.
Current version of app is 4.0 beta, which is a complete rewrite.
I'm open for ideas, suggestions regarding additional features.
Happy OCing.

Thanks xan for this invitation
Unhelpful also played a big part with the initial code to load dynamically frequencies and voltages using a sysfs interface.
BTW, your app source is welcome on project-voodoo github !
I know several people motivated to contribute, it would be a place to start.

Right, Unhelpful, adding topic to OP.
Yes, this needs to be open-sourced.
No date yet, because there are monsters inside.
The thing that struck me now, is why is all of that so complicated?
I think I like single-table idea more and more.

ill volunteer to help.

Very exciting to see some of the best dev names from the SGS community showing interest in the Nexus S. Many goog things to come for us if they remain interested...

So when are we gonna see a 1.2GHz Voodoo OC/UV kernel

My phone recieves a noticeable speed increase with the voodoo kernel for Nexus S with max and min set to 1000 with performance governor Can't wait for a super optimized kernel OC/UV!

looking forward to a UV kernel to extend battery life.

jroid said:
My phone recieves a noticeable speed increase with the voodoo kernel for Nexus S with max and min set to 1000 with performance governor Can't wait for a super optimized kernel OC/UV!
Click to expand...
Click to collapse
Anything on battery?
defysword said:
looking forward to a UV kernel to extend battery life.
Click to expand...
Click to collapse
+1

why is no one compiling a kernel supporting xans app? i really loved it on my galaxy s and when i saw this threat i was hoping for a supported kernel for my nexus s. it really can make oc more stable if u r patient enough to test the best setzings for ur phone
Sent from my Nexus S using Tapatalk

Can't wait for this too. Xan's app is really good on SGS.

shrooms90 said:
why is no one compiling a kernel supporting xans app? i really loved it on my galaxy s and when i saw this threat i was hoping for a supported kernel for my nexus s. it really can make oc more stable if u r patient enough to test the best setzings for ur phone
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
This died the 22nd of December, I got my Nexus S around that time, kept it stock while on vacation over the holidays, missed out there.
I *may* check this out, don't want to turn into Patches....
But I could continue to build Honity stable for Will, but others run lower than he does.
Instead of stock + UV build it would be only 1.
And Honity14 could be the UVOC some want.
Problem in that is that I take a risk of people not understanding the "use at your own risk" part involved.
Thanks for bumping this thread, didn't know xan had this.
Sent from my Nexus S

morfic said:
This died the 22nd of December, I got my Nexus S around that time, kept it stock while on vacation over the holidays, missed out there.
I *may* check this out, don't want to turn into Patches....
But I could continue to build Honity stable for Will, but others run lower than he does.
Instead of stock + UV build it would be only 1.
And Honity14 could be the UVOC some want.
Problem in that is that I take a risk of people not understanding the "use at your own risk" part involved.
Thanks for bumping this thread, didn't know xan had this.
Sent from my Nexus S
Click to expand...
Click to collapse
sounds good. i like honity kernel but for my phone it needs a little fine tuning.
i think people would understand "use at ur own risk" imo most people understood it on the sgs forum.
so i really would love to see honity14 with uv options
Sent from my Nexus S using Tapatalk

Is there any progress?

xan said:
I'm open for ideas, suggestions regarding additional features.
Happy OCing.
Click to expand...
Click to collapse
Hi. great stuff here. would this app work (or made to work) using snq-'s undervolting via sysfs here.
I use a kernel with the above patch enabled and my ROM users would love to be able to do this using an app like this.
Thanks!

pongster said:
Hi. great stuff here. would this app work (or made to work) using snq-'s undervolting via sysfs here.
I use a kernel with the above patch enabled and my ROM users would love to be able to do this using an app like this.
Thanks!
Click to expand...
Click to collapse
Im a noob when it comes to kernel developping, but i hope this will help u:
From what i understood this app undervolts using following command:
echo "0,0,50,100,0...." /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
Where the numbers stand for the amount of undervolting in mV for each freq. (I think it is from lowest to highest but im not sure. If u set the values at boot it just writes a startup script in /system/etc/init.d/
Sent from my Nexus S using Tapatalk

Fantastic,
The nexus s dev community is definitely growing now
JD
Sent from my Google Nexus Magic Wand S

JupiterDroid said:
Fantastic,
The nexus s dev community is definitely growing now
JD
Sent from my Google Nexus Magic Wand S
Click to expand...
Click to collapse
wtf? fancy seeing you here

Stea1thmode said:
wtf? fancy seeing you here
Click to expand...
Click to collapse
WTH young man, did you get lost

Just thought that I'd mention this.
I develop a kernel for the Captivate for CM7. Our cm kernel is based off Nexus S code, so anything that works under it will work under your kernels as well (probably). I've implemented this successfully under my kernel with no real problems.
Just add a sysfs interface to the cpufreq driver to store the uv amount, then subtract that amount * 1000 from arm_volt before feeding it into the regulator.
Sources are here --> https://github.com/TheEscapistxda/CM7-OCUV
PS I apologize for my terrible commenting.

Kernel and ROM Benchmarks

Users can feel free to post their benchmarks here
Here's some of my benchmarks:
- Tests were ran from [ROM][STOCK IMAGE]Android 4.1.1 (JRO03D) ROOT, Deodexed, Busybox
- Testing done with latest Quardrant Standard
- Battery, Dalvik, and Cache were all wiped after installing kernel from zip in CWM
- Kernels tested were all the latest and highest-OC'd versions available as of 8/7
- No governers, schedulers, or clock speeds were altered from default values (I plan to reupload screenshots of performance later)
[KERNEL][GPL][Linaro][OC 1.624GHz][UV][GPU+][ZRAM][SIO+V(R)] 2012-08-03 motley 1.0.12 (GPU 520, build 175)
{
"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"
}
Kernel[006]AP33(1.55Ghz Quad)UV,CIFS+UTF-8,PowerHAL,Linux-3.x Hybrid [Aug-04] (Ultimate Edition)
[DER KERNEL] Trinity Seven (TS-1640-ALPHA41)
Stock

Note to self get an HTC One X, man thats a fast phone

Quadrant is very inconsistent with benchmarks. I would suggest Antutu/CFBench/Nenamark/GLBenchmark/RL Benchmark as being more accurate.
Sent from my Nexus 7

If you use TKT with trinity it blows the One C X away
you can do it via the terminal but idk the code and I already had TKT
Sent from my Nexus 7 using xda app-developers app

I've never seen a trinity kernel score that low. Most people score more than double overall of what you posted. Plus your I/O scores are warped. People scoring in the 7000-11,000 range. You not benching your device properly or something or using the wrong settings. Those are the worst scores I've seen posted on a nexus 7..lol.
Main tip for benching: put device in performance mode or at least ondemand. Even on stock governor, I've seen majority score higher than you. Just take a look at majority of posted benchmarks and you will see you don't have something right set up on your device.
You making those kernels look bad. Check mines out and it wasn't even on the highest setting. This is with trinity kernel OC to 1.5ghz. Stock rom and stock gpu speed.
I've never seen Motley, Infinity kernel, faux, or even stock score as low as what you have..lol.
the last quadrant I posted was on motley kernel.
huge difference in my scores and yours. plus mines on the lower end because I only benched at 1.5ghz. if I would've went top speed, scores would be even higher. we have people now benching close to and over 7000-7100 overall on quadrant. it blows any other android device out now. so much so there's been several tech news stories on how nexus 7 is blowing away other higher end android devices in benchmarks.
p.s. my nenamark2 score is 64.7fps
also I know quadrant can be inconsistent but those scores you posted still suspiciously low for those kernels they supposedly are from.

Just did 3 more ones. Stock rom. Trinity kernel CPU speed 1.5ghz. Performance governor and deadline scheduler
I find chainfire bench to be one of the best. doesn't rely on fancy graphics testing and such. this tests more raw power. as you can see, I beat out the new Samsung galaxy S3 with its 32nm high speed chip. remember also, we still in infancy stage of nexus7 development and we blowing away all benches & devices(Android) already. pretty good for a $199-249 tablet huh? lol. this performance level also translates to real world use. not just for show.

how are you getting such high scores? mine are always around 4600.. running at 1600 with trinity. doesnt make sense that yours are so high? highest ive seen by a good ways.

You’re very professional.

demandarin said:
I've never seen a trinity kernel score that low. Most people score more than double overall of what you posted. Plus your I/O scores are warped. People scoring in the 7000-11,000 range. You not benching your device properly or something or using the wrong settings. Those are the worst scores I've seen posted on a nexus 7..lol.
Main tip for benching: put device in performance mode or at least ondemand. Even on stock governor, I've seen majority score higher than you. Just take a look at majority of posted benchmarks and you will see you don't have something right set up on your device.
Click to expand...
Click to collapse
When I benched, I just had everything set at default settings (didn't change governers, clocks, or anything).

espionage724 said:
When I benched, I just had everything set at default settings (didn't change governers, clocks, or anything).
Click to expand...
Click to collapse
when you benchmark, use highest cpu/highest cpu. if you dont set it there, you let your device decide what cpu speed it actually wants to use, therefore you have no idea what cpu speed you are benching. for all you know is that on one bench it might be benching 1100mhz, on another it might be benching less or more. btw, those benchmarks are horrible, my galaxy nexus benchmarks higher

simms22 said:
when you benchmark, use highest cpu/highest cpu. if you dont set it there, you let your device decide what cpu speed it actually wants to use, therefore you have no idea what cpu speed you are benching. for all you know is that on one bench it might be benching 1100mhz, on another it might be benching less or more. btw, those benchmarks are horrible, my galaxy necus benmarks higher
Click to expand...
Click to collapse
Would setting ROM Toolbox to use the highest CPU frequency + performance be acceptable? Or should I use another program to ensure the CPU is at highest?
Edit: After doing that:
Total, CPU, Mem, I/O, 2D, 3D
Trinity: 4142, 12791, 3737, 1387, 332, 2464
Faux: 4457, 14257, 3890, 1339, 333, 2465
Motley: 5846, 15184, 3618, 7191, 300, 2935
Tests done from Glazed JellyBean 1.12
Those scores still seem worse then what some others have said though. Is there anything else I should be doing?

Sadly I have to flash back to stock kernel to make the wifi functionally. But sure the motley kernel is pretty attractive on its performance and addons.

espionage724 said:
Would setting ROM Toolbox to use the highest CPU frequency + performance be acceptable? Or should I use another program to ensure the CPU is at highest?
Edit: After doing that:
Total, CPU, Mem, I/O, 2D, 3D
Trinity: 4142, 12791, 3737, 1387, 332, 2464
Faux: 4457, 14257, 3890, 1339, 333, 2465
Motley: 5846, 15184, 3618, 7191, 300, 2935
Tests done from Glazed JellyBean 1.12
Those scores still seem worse then what some others have said though. Is there anything else I should be doing?
Click to expand...
Click to collapse
I find system tuner to be the best for those type of settings. If you run trinity kernel though, you will get more out of it by using the trinity kernel app in playstore that lets you tweak things in their kernel that even apps like system tuner can't do. But overall system tuner is the best, IMO. Its more in depth than most apps of THST nature.
Also best to use performance governor. Or on demand. Then use deadline or sio as the scheduler.
x-magic said:
Sadly I have to flash back stock kernel to make the wifi functionally. But sure the motley kernel is pretty attractive on its performance and addons.
Click to expand...
Click to collapse
Nothing wrong with wifi on motley kernels. Which build were you running? His latest runs great and no issues. Trinity kernel wifi works perfect also.

This is my score using latest trinity build 41 and pure aosp ROM.
Sent from my Nexus 7 using xda premium

saadi703 said:
This is my score using latest trinity build 41 and pure aosp ROM.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
as with others i max out at 46XX on quad if i am lucky and thats using system tuner and putting min/max sliders to 1.6 and performance gov. are you guys doing any other kernel tweaks to get these numbers

xspeed9190 said:
as with others i max out at 46XX on quad if i am lucky and thats using system tuner and putting min/max sliders to 1.6 and performance gov. are you guys doing any other kernel tweaks to get these numbers
Click to expand...
Click to collapse
I used trinity kernal build 41 with pure aosp rom. I used trinity kernel toolbox app from play store to tweak it. It is a paid app and if you don't want to buy the app then you have to use scripts but to keep things simple I used the app.
I clocked the processor to 1640 MHz, put the governor to performance which means processor would run at 1640 always. I/O scheduler to deadline and in tunable I select Fsync to faster. Good luck
Oh I forget to mention that good thing about Trinity kernel toolbox app is that you can use it with any kernel not only with trinity. The CPU temp widget is also good
Sent from my Nexus 7 using xda premium

Quadrant scores are meaningless. There are so many ways that they can be artificially inflated. I suspect that the scores in the 4000 range are the ones that truly reflect the overall performance of the device. 6000+ scores are obviously not realistic scores. Look at the IO scores, 10000 is a bogus 10x improvement over stock. No setting change anywhere is going to improve your IO performance 10x.

hecksagon said:
Quadrant scores are meaningless. There are so many ways that they can be artificially inflated. I suspect that the scores in the 4000 range are the ones that truly reflect the overall performance of the device. 6000+ scores are obviously not realistic scores. Look at the IO scores, 10000 is a bogus 10x improvement over stock. No setting change anywhere is going to improve your IO performance 10x.
Click to expand...
Click to collapse
someones feeling small..

TS-ALPHA50 + Glazed Jellybean v1.12

espionage724 said:
TS-ALPHA50 + Glazed Jellybean v1.12
Click to expand...
Click to collapse
better :victory:

[UV] Nexus 4 UV Thread - POST YOUR UNDERVOLTING RESULTS - GET A (BATTERY)LIFE :)

Hey Guys,
I read alot about OCing your Phone and Overvolting, but how about Undervolting? I thought I’ll open a new thread for discussing the UV potential of our Nexus and to show other users that they can achieve better batterylife by UVing. If you want to, please provide which chip you've got (slow, nominal, fast, faster) which ROM/kernel you are on and which voltage you’ve set on each state (use Trickster or similar apps. I recommend System Tuner Pro. You can save your stable UV settings and easily apply them again after a ROM/Kernel update).
Use this code to figure out which chip you've got (the result will either be slow - faster or numbers from 1 - 4):
1.) Install Terminal Emulator
2.) Type in su and press enter
2.) Reboot your phone
3.) Open Terminal Emulator and type:
su (press enter)
dmesg | grep PVS (press enter again)
Click to expand...
Click to collapse
I have a "FAST" chip and I’m on PA 3+ with latest _m+ kernel (motley kernel continued).
My voltages so far (StabilityTest stable):
192 MHz - 625,0 mV
304 MHz - 650,0 mV
486 MHz - 675,0 mV
594 MHz - 700,0 mV
702 MHz - 737,5 mV
810 MHz - 775,0 mV
918 MHz - 800,0 mV
1,02 GHz - 825,0 mV
1,13 GHz - 850,5 mV
1,24 GHz - 875,0 mV
1,29 GHz - 900,0 mV
1,35 GHz - 910,0 mV
1,40 GHz - 925,0 mV
1,45 GHz - 940,0 mV
1,51 GHz - 950,0 mV
Attention! Some users reported glitches/artifacts when going under a certain Voltage-level. So don't just test your settings with StabilityTest, take some pictures and or videos as well
Here is a post I consider to be very useful. Please read it:
kelah said:
I think google/LG messed up with voltages in more ways it looks on the first glance.
Put their values on the graph and You'll notice that the line is linear. But it should be somewhat parabolic.
It's easy to demonstrate on the graph.
Blue line - stock google voltages.
Red line - this I get when I set UV -150 (I can't go lower it).
Violet line - my stable setup.
As you can see my stable setup is parabolic. And in the center difference is big - 225mV at 1188mHz and 200mV at 1026mHz. For other values it ranges from 25 to 35.
Green line consist of values crashes device immediatly - I set them and right after I tap on "apply" my lovely N4 rebooting. The point is what between them and stable values 50mV. If difference abot 5-25 device works but it reboot for sure in half of hour or something like that. This is the easy way to determine how much UV you can - just find values of instant crash and rise them about 40-50mV. These values are easy to find - no need to run long tests. Would be better to do nandroid before - many repeatedly sporadic reboots can corrupt some of your data.
My surrent setup:
384 - 700 (-150)
486 - 700 (-175)
594 - 720 (-180)
702 - 740 (-185)
1026 - 825 (-200)
1188 - 875 (-225)
1350 - 940 (-185)
1512 - 1000 (-150)
{
"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"
}
Click to expand...
Click to collapse
Greetz

Re: Nexus 4 UV Thread
I am on the new pa ROM
Faux latest kernel
Min 384
Max 1300
UV at -150
WiFi and data use.
Screen brightness just below half .
Now on 56% battery left and been off charge for
1 day 2 hours. ..... Gimme a hell yehh....
Sent from my pie'd nexus 4

Re: [UV] Nexus 4 UV Thread - POST YOUR UNDERVOLTING RESULTS
CM10.1
Sent from my Nexus 4 using Tapatalk 2

Re: [UV] Nexus 4 UV Thread - POST YOUR UNDERVOLTING RESULTS
Bigxie AOKP PUB build 2/15 (4.2.2)
Frankien intelli-plug kernel
Fast bin
Sent from my Nexus 4 using xda premium

Re: [UV] Nexus 4 UV Thread - POST YOUR UNDERVOLTING RESULTS
revamper said:
CM10.1
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
+1
Sent from my Nexus 4 using xda premium

How do you test for different frequency stages? Stability test always runs at maximum CPU speed.

Re: [UV] Nexus 4 UV Thread - POST YOUR UNDERVOLTING RESULTS
CM 10.1 with franco
Sent from my Nexus 4 using xda app-developers app

384Mhz min
1024Mhz max
-150mV
Faster binned CPU
Completely stable, could probably go to at least -175mV stable... But it's okay as it is, phone is still snappy(can't even tell the difference tbh) and the battery will last me 1,5 - 2 days, which was something unseen on the iPhone 4 I had before..

How do you test for different frequency stages? Stability test always runs at maximum CPU speed.
Click to expand...
Click to collapse
You just have to choose "Scaling Stability Test (Root)" in the main menu. There you can choose which frequencies will be tested.

I'm really interested in undervolting but want to find out which chip I have. I tried doing the terminal emulator technique above but the sheer amount of info it pulls seems incomprehensible to me! Could someone point me in the right direction of how I find out what kind of chip I have got in here so I can start playing around with UVing? Just for reference I'm on the latest PA 3.0 ROM with Faux Kernel
Cheers

NightflyUK said:
I'm really interested in undervolting but want to find out which chip I have. I tried doing the terminal emulator technique above but the sheer amount of info it pulls seems incomprehensible to me! Could someone point me in the right direction of how I find out what kind of chip I have got in here so I can start playing around with UVing? Just for reference I'm on the latest PA 3.0 ROM with Faux Kernel
Cheers
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2052496
You should be able to UV to at least -100mV, no matter what chip you have..

I might be being daft but when I run that command nothing comes up (can't post PIC) I'm definitely rooted as I'm running custom ROM and kernel and using terminal editor. It just comes up
1|[email protected]:/#

Okay i did those steps:
1. Installed Terminal Emulator
2. SU and enter
3. Reboot
4. SU command and command from the OP
5. The last word describes your chip (could be also numbers from 1 - 4 I think)

Herminator19640927 said:
Okay i did those steps:
1. Installed Terminal Emulator
2. SU and enter
3. Reboot
4. SU command and command from the OP
5. The last word describes your chip (could be also numbers from 1 - 4 I think)
Click to expand...
Click to collapse
Cheers man that sorted it its giving me a result as 1 so at which end of the scale is that? Also when I run the acpuclk its telling me it can support 15 frequencies

NightflyUK said:
Cheers man that sorted it its giving me a result as 1 so at which end of the scale is that? Also when I run the acpuclk its telling me it can support 15 frequencies
Click to expand...
Click to collapse
I think 1 means slow or nominal, not quite sure. Read it somewhere... just look around in the dev section (I think it was a post by Harsh).
Greetz

NightflyUK said:
I might be being daft but when I run that command nothing comes up (can't post PIC) I'm definitely rooted as I'm running custom ROM and kernel and using terminal editor. It just comes up
1|[email protected]:/#
Click to expand...
Click to collapse
I had to reboot after installing terminal emulator in order to get the command to work.

Herminator19640927 said:
I think 1 means slow or nominal, not quite sure. Read it somewhere... just look around in the dev section (I think it was a post by Harsh).
Greetz
Click to expand...
Click to collapse
Thanks. I just tried it but it always stay at 1016Mhz. I'm using Franco's latest Kernel. Governor is set to ondemand, but I wont change frequencies.

Re: [UV] Nexus 4 UV Thread - POST YOUR UNDERVOLTING RESULTS
Faster, cm10.1 original, francos kernel r72
Sent from my Nexus 4 using xda app-developers app

digitalfrost said:
Thanks. I just tried it but it always stay at 1016Mhz. I'm using Franco's latest Kernel. Governor is set to ondemand, but I wont change frequencies.
Click to expand...
Click to collapse
Strange... for me everything's working fine. StabilityTest sets my governor to userspace and changes through all frequencies in the specified delay.

Stock 4.2.2, franco r92.
Stability test, long term usage, etc... is stable.

Get better multi core usage

As I had a slight reduction in performance from v10d to v20b, I searched the one X forums and found a way to get a SMALL boost in core use and performance that was sufficient to stop the little stutters I have got in games.
Instructions:
1. Download setcpu, latest version.
2. Open it and continue with recommended setup
3. Change max speed to 1400mhz and min to 51mhz (We are lowering top value because 1500mhz only uses one core) and governer to ondemand
4. Go to governer values, change up threshold to 50 (you can play with this to suit yourself, lower is faster, higher may save battery.
5. (Optional) Apply set on boot to all values so they stick
This method is tested on v20b, but it may help on ICS roms too!
Sent from my rooted P880

Best results were with ondemand governer and up threshold @50, clock max 1400mhz. Saw average of 2-3 cores used in need for speed and noticable lag reduction. Still not perfect but that game has issues with the one x too. What I don't get is how lg home can fire up all cores at max speed straight away, lg definitely did some strange things with tegra. Will continue trying things from the one x forums, see if I can't find any other useful tweaks
Sent from my rooted P880

can you please specify the name of the files that you have downloaded?
and what files you have open with SManager?
because I have a lot of files...
how to install the supercharger_diehardlauncher_service.rar?
...and thank you for your work!!
Sent from my LG-P880 using xda app-developers app

UncleRipper said:
can you please specify the name of the files that you have downloaded?
and what files you have open with SManager?
because I have a lot of files...
how to install the supercharger_diehardlauncher_service.rar?
...and thank you for your work!!
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
The script is not the best, use setcpu or similar to set ondemand governer and up threshold @50
Sent from my rooted P880

You are forgetting key thing here, CUSTOM KERNEL!!!
Since this can maybe do so slight boost you would not even notice...

nedooo said:
You are forgetting key thing here, CUSTOM KERNEL!!!
Since this can maybe do so slight boost you would not even notice...
Click to expand...
Click to collapse
You are wrong, Its no miracle I agree, but games with small frame dips like shadowgun, dead trigger and NFS all were significantly smoother. I would love a custom kernel, but this just fixes some minor annoyances in my favourite games
Sent from my rooted P880

UPDATED OP WITH PROPER INSTRUCTIONS
Sent from my rooted P880

@non4 said:
As I had a slight reduction in performance from v10d to v20b, I searched the one X forums and found a way to get a SMALL boost in core use and performance that was sufficient to stop the little stutters I have got in games.
Instructions:
1. Download setcpu, latest version.
2. Open it and continue with recommended setup
3. Change max speed to 1400mhz and min to 204mhz (We are lowering top value because 1500mhz only uses one core) and governer to ondemand
4. Go to governer values, change up threshold to 50 (you can play with this to suit yourself, lower is faster, higher may save battery.
5. (Optional) Apply set on boot to all values so they stick
This method is tested on v20b, but it may help on ICS roms too!
Sent from my rooted P880
Click to expand...
Click to collapse
Erm, wont increasing the min MHz to 204 prevent the phone from going to deep sleep @ 51MHz?
Sent from my (V20A, Unlocked, Rooted, CWM, Optimised) LG-P880 using xda app.

Xenogenics said:
Erm, wont increasing the min MHz to 204 prevent the phone from going to deep sleep @ 51MHz?
Sent from my (V20A, Unlocked, Rooted, CWM, Optimised) LG-P880 using xda app.
Click to expand...
Click to collapse
204 seems to be default in my rom, although it goes that low. I'll update the post in case that is the case
Sent from my rooted P880

Xenogenics said:
Erm, wont increasing the min MHz to 204 prevent the phone from going to deep sleep @ 51MHz?
Sent from my (V20A, Unlocked, Rooted, CWM, Optimised) LG-P880 using xda app.
Click to expand...
Click to collapse
??? Isn't deep sleep a special low power state where the cores are effectively at 0MHz? IIRC 51MHz is not deep sleep, just the phone using the low power core.
Also, so long as you are using the phone, the minimum it should clock is 102MHz (as seen from Hidden Settings CPU Usage bar). Touching the screen changes the minimum frequency to 750MHz (effectively 760MHz in our phone's CPU frequency table) for a moment; this is one of the 3 Project Butter implementations (boosting CPU frequency when screen is touched).
Sent from my LG-P880 using Tapatalk 2

exFAT said:
??? Isn't deep sleep a special low power state where the cores are effectively at 0MHz? IIRC 51MHz is not deep sleep, just the phone using the low power core.
Also, so long as you are using the phone, the minimum it should clock is 102MHz (as seen from Hidden Settings CPU Usage bar). Touching the screen changes the minimum frequency to 750MHz (effectively 760MHz in our phone's CPU frequency table) for a moment; this is one of the 3 Project Butter implementations (boosting CPU frequency when screen is touched).
Sent from my LG-P880 using Tapatalk 2
Click to expand...
Click to collapse
Well, I forgot the name of one app I used. It showed me the time spent in core states in a pie chart, where I saw 51MHz, a major section of the chart along with 1500MHz. I assume that thats the state for deep sleep.
In addition, I would like to inquire, how would a phone even be at 0MHz? If thats the case, the phone wouldn't even respond after it entered deep sleep, right? Because technically assuming, 0MHz = 0 current = phone off.
Sent from my (V20A, Unlocked, Rooted, CWM, Optimised) LG-P880 using xda app.

exFAT said:
??? Isn't deep sleep a special low power state where the cores are effectively at 0MHz? IIRC 51MHz is not deep sleep, just the phone using the low power core.
Also, so long as you are using the phone, the minimum it should clock is 102MHz (as seen from Hidden Settings CPU Usage bar). Touching the screen changes the minimum frequency to 750MHz (effectively 760MHz in our phone's CPU frequency table) for a moment; this is one of the 3 Project Butter implementations (boosting CPU frequency when screen is touched).
Sent from my LG-P880 using Tapatalk 2
Click to expand...
Click to collapse
That's what I thought, I've updated the OP anyway, no drops in performance fron doing this
Sent from my rooted P880

I think 51MHz is not deep sleep
Like someone said before, 0 MHz = deep sleep (maybe)
{
"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"
}

in our case, 0mhz is possible, we have a fith core for the deep sleep, so in theory, the other 4 cores can be shut down and go back to work when they need to
Sent from my LG-P880 using xda app-developers app

Xenogenics said:
Well, I forgot the name of one app I used. It showed me the time spent in core states in a pie chart, where I saw 51MHz, a major section of the chart along with 1500MHz. I assume that thats the state for deep sleep.
In addition, I would like to inquire, how would a phone even be at 0MHz? If thats the case, the phone wouldn't even respond after it entered deep sleep, right? Because technically assuming, 0MHz = 0 current = phone off.
Sent from my (V20A, Unlocked, Rooted, CWM, Optimised) LG-P880 using xda app.
Click to expand...
Click to collapse
You answered yourself . The power button wakes the CPUs up. Just like how the phone powers up when the power button is long held. It's like the ignition for a car.
In addition, having your phone at 51MHz much of the time means your phone's battery will drain quickly, much quicker than if the cpus had been in deep sleep.
The CPU also doesn't shut down completely. It runs at maybe a few KHz (still effectively 0KHz), just enough to keep the system alive. When power button is pressed, it ramps up quickly.
Sent from my LG-P880 using Tapatalk 2

to answer the questions, first answer this. you also have to consider the presence of ram
How does our computers keep the clock ticking even after we've pulled the plug?
In deep sleep mode the processor is technically in low power state, kinda like hibernating.
It is still, however, keeping note of the time, and the alarms (processes) requiring him to wake up and do some short tasks (sync or whatever)
A sleeping warrior but his senses are still alert.
During so those alarms in deep sleep are also listening to incoming messages (someone calls you on skype) in low power.
It is these listeners, thereby bits of wakes that are draining battery when our phone is in deep sleep (therefore more 'listening' apps increases battery drain.)
51MHz or maybe even 1MHz isn't deep sleep. The warrior is wake and he is walking. The processor is actively processing real-time traffic and load.
1.5GHz x 4 is when the warrior is fighting a full scale battle.
I'm bad at explaining stuff. but this is the overall of how deep sleep and 51MHz works.

Nexus 5 high/crazy/abnormal clock speeds

I'm curious to see what kind of speeds you guys are running you snapdragon 800 with voltage myself i managed to get to 2880 ghz running stock voltages and my cpu bin is PVS 0 has anyone managed to get to 3.0 GHZ or maybe even further post your speeds and voltage below

voltages are default trinity kernel, pvs 3, speed is obvious..
{
"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"
}

simms22 said:
voltages are default trinity kernel, pvs 3, speed is obvious..
Click to expand...
Click to collapse
How's battery? 1 hr screen time?

aooga said:
How's battery? 1 hr screen time?
Click to expand...
Click to collapse
lol, at that cpu speed, you are not allowed consider battery life! but i do use 2880/300 occasionally for a daily. ill see 4-4.5h sot normally with 2880/300. you have to remember, it doesnt stay at 2880mhz, itll only go there if it needs to.

simms22 said:
lol, at that cpu speed, you are not allowed consider battery life! but i do use 2880/300 occasionally for a daily. ill see 4-4.5h sot normally with 2880/300. you have to remember, it doesnt stay at 2880mhz, itll only go there if it needs to.
Click to expand...
Click to collapse
really? i dont see that much sot on stock speed i only get about 3.5hr sot max and thats with light usage

driftshadows said:
really? i dont see that much sot on stock speed i only get about 3.5hr sot max and thats with light usage
Click to expand...
Click to collapse
I regularly see 5-6 hours SoT on everything stock. Check the battery results thread as many are getting 7-8 with under clocking.
Sent from my Nexus 5 using Tapatalk

driftshadows said:
really? i dont see that much sot on stock speed i only get about 3.5hr sot max and thats with light usage
Click to expand...
Click to collapse
at stock speeds i usually see between 5 and 6 hours sot with heavy usage, on lte 100% of the time(no wifi). ill normally kill my battery in 7-12 hours, but that because im always using the phone. i dont let it lay around sleeping for hours.

simms22 said:
you have to remember, it doesnt stay at 2880mhz, itll only go there if it needs to.
Click to expand...
Click to collapse
Yeah, I was talking about your screenshot where it said both the min/max were 3000. You get pretty good battery out of this phone with 2880. I get about 3 hours on 1700, but thats for a different thread.

aooga said:
Yeah, I was talking about your screenshot where it said both the min/max were 3000. You get pretty good battery out of this phone with 2880. I get about 3 hours on 1700, but thats for a different thread.
Click to expand...
Click to collapse
i put it to 3014/3014 to makes sure and to show that it was actually running at 3014mhz. id be affraid to guess the battery life

simms22 said:
i put it to 3014/3014 to makes sure and to show that it was actually running at 3014mhz. id be affraid to guess the battery life
Click to expand...
Click to collapse
What voltages do you run 3014 MHz at? You said stock voltages, but could you look those up for me? I've been able to run Franco at 2880, but at 3014 I get reboots
Sent from my Nexus 5 using Tapatalk

Gormsen said:
What voltages do you run 3014 MHz at? You said stock voltages, but could you look those up for me? I've been able to run Franco at 2880, but at 3014 I get reboots
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
reboots would be the normal behavior, i would think most phones wont be able to run at 3014mhz

driftshadows said:
really? i dont see that much sot on stock speed i only get about 3.5hr sot max and thats with light usage
Click to expand...
Click to collapse
from this evening/morning http://forum.xda-developers.com/showpost.php?p=50450077&postcount=4001

Swadin1 said:
Its helpful for me. Thanks
Click to expand...
Click to collapse
You know there's a thanks button for that, right?
Okay, so I couldn't get Franco r33 to run more than 2880 MHz, so I switched to the newest Trinity (The one from the new build environment) and now I can easily hit 3014 MHz. I don't know if it will ever be of any use, but it's nice to know that it's possible
Sent from my Nexus 5 using Tapatalk

Gormsen said:
You know there's a thanks button for that, right?
Okay, so I couldn't get Franco r33 to run more than 2880 MHz, so I switched to the newest Trinity (The one from the new build environment) and now I can easily hit 3014 MHz. I don't know if it will ever be of any use, but it's nice to know that it's possible
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
sweet, so im not the only one that can

simms22 said:
sweet, so im not the only one that can
Click to expand...
Click to collapse
Nope, don't you think everybody is able to? Your device being a PSV 0 and mine being a 4, I don't think it makes much difference.
It could be fun to see how far we can push it. I don't experience any problems on 3014, so I'm thinking that we can go higher
Sent from my Nexus 5 using Tapatalk

Gormsen said:
Nope, don't you think everybody is able to? Your device being a PSV 0 and mine being a 4, I don't think it makes much difference.
It could be fun to see how far we can push it. I don't experience any problems on 3014, so I'm thinking that we can go higher
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
im a pvs 3. for 3 and 4 it should be easier to run. anyways, all cpus arent equal, some are better than others.

simms22 said:
im a pvs 3. for 3 and 4 it should be easier to run. anyways, all cpus arent equal, some are better than others.
Click to expand...
Click to collapse
Sorry there, misread a previous post if yours. But think about it, wouldn't it be awesome figuring out how much we can push it. As a bonus I would love tauting my little brother, joking about how my phone runs at the double amount of clocks of his One (if 3.4 GHz is even possible)
Sent from my Nexus 5 using Tapatalk

bblzd said:
I regularly see 5-6 hours SoT on everything stock. Check the battery results thread as many are getting 7-8 with under clocking.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
This is what I get I might switch kernels to that could be the problem because I under clocked today and didn't do much on my phone as I was at school
Sent from my Nexus 5 using XDA Premium 4 mobile app

I tryed 3ghz and got a reboot. PVS 2 Trinity.
Sent from my Nexus 5 using xda app-developers app

Tunderpimp said:
I tryed 3ghz and got a reboot. PVS 2 Trinity.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
did you try adjust the voltage at 3014mhz?