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.
Related
This application allows you to control cpu speed and number of active cores.
Features
- Help extend your battery life.
- Manually control CPU speed and active cores
- Integrated with Power saver option in system settings.
Whenever your turn on Power saver, cpu and active cores will automatically adjusted.
It uses undocumented LG API, tested on stock firmware version 10C.
No root required
{
"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"
}
Remarks
1. Try it at your own risk.
2. System instability reported with 2 active cores. (Original LG QuadGearBox)
3. The 3 cores active option does not work. I don't know why. I leave that option to test by yourself.
4. This app has been tested on rooted phone. It should work on non-root phone, need some test please.
Bugs
Sometimes it just doesn't work. Reboot phone will fix it.
Note
V1.1
initial release
V1.2
Activate by Power Saver
V1.2.1
Fix incorrect popup message.
Usage
Open LG GearBox
Choose CPU Max Speed and Active Cores then click Apply button
Testing it with my unrooted phone.
Setting clock to 1100, use 2 cores.
Quadrant benchmark then drops to 28xx (before is 47xx)
So I guess this app worked.
Let's see next if this setting have effect in battery usage.
Sent from my LG-P880 using xda app-developers app
Thanks for testing.
I will edit the post for no root requirement.
app works as it should, but i don't think that it will have a big effect in Battery usage, the Management for the cores is quite good and
quad is used not much, also the core's itself are not the big drainer's.
If we have full access and custom Rom's/Kernel's - than we can expect power savings ....
Underclock does improve my battery life and also less heat.
V1.2 will be more useful by Power saver trigger.
atipon said:
Underclock does improve my battery life and also less heat.
V1.2 will be more useful by Power saver trigger.
Click to expand...
Click to collapse
yeah, i misspelled that, underclock surely will improve, but i think reducing the cores will also give us more juice, but not so much i think,
but i test the new version now
thx for this!!!!
Originally Posted by atipon<br />
Underclock does improve my battery life and also less heat.<br />
<br />
V1.2 will be more useful by Power saver trigger.
Click to expand...
Click to collapse
<br />
<br />
yeah, i misspelled that, underclock surely will improve, but i think reducing the cores will also give us more juice, but not so much i think,<br />
but i test the new version now <br />
<br />
thx for this!!!!
Click to expand...
Click to collapse
Be careful not to set clock too low.
When entering power saver mode, the phone suddenly lag heavily
Sent from my LG-P880 using xda app-developers app
change to 4/1500 from 2/860, device turn off itself.
v10c Taiwan version
continue testing
I have another request.
Please make a preset list for combination clock and cores, so we can make a quick switch setup.
better if the list can be customized.
Sent from my LG-P880 using xda app-developers app
Will there be any problem if i uses quadgearbox in conjunction with this? or does this serves the same / better as quadgearbox?
Nevermind, i uninstalled QGB and using this instead
optimuswhite said:
I have another request.
Please make a preset list for combination clock and cores, so we can make a quick switch setup.
better if the list can be customized.
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
May be next version
L2Deliver said:
Will there be any problem if i uses quadgearbox in conjunction with this? or does this serves the same / better as quadgearbox?
Nevermind, i uninstalled QGB and using this instead
Click to expand...
Click to collapse
Actually LG Hidden Quadgearbox is where I started to look in LG API. Basically, use the same API to set 2 cores active.
I think freeze/restart is the reason why LG hasn't release it in official firmware and that's why we need this app
atipon said:
May be next version
Actually LG Hidden Quadgearbox is where I started to look in LG API. Basically, use the same API to set 2 cores active.
I think freeze/restart is the reason why LG hasn't release it in official firmware and that's why we need this app
Click to expand...
Click to collapse
Im saving more battery on this than quadgearbox. No problems with it so far - Singapore V10C - except the speed resets to 1.5GHz after reboot. Number of cores didnt.
Edit: is the fix for the resets coming any time soon? My setting is 2 cores at 1.2GHz. After reboot its 2 cores at 1.5GHz
Works but it freezes my phone twice already.
Also, it fires up the other cores even though I set core number to 1.
Will be keeping it but I won't be using it till next stable update...
Can this turn all 4 cores back on as I believe lg quad gearbox has turned 2 off and they won't come back on
Sent from my LT26i using Tapatalk 2
Doesn't seem like it can! Any idea how i turn all 4 cores back on?
Sent from my LT26i using Tapatalk 2
Ben36 said:
Can this turn all 4 cores back on as I believe lg quad gearbox has turned 2 off and they won't come back on
Sent from my LT26i using Tapatalk 2
Click to expand...
Click to collapse
The originally QuadgearBox set active cores on boot so you have to turn eco mode off in QuadgearBox.
Tried that too!?
Sent from my LT26i using Tapatalk 2
Ben36 said:
Tried that too!?
Sent from my LT26i using Tapatalk 2
Click to expand...
Click to collapse
I factory reset my phone and got my 4 cores back
Sent from my LG-P880 using xda app-developers app
atipon said:
May be next version
Actually LG Hidden Quadgearbox is where I started to look in LG API. Basically, use the same API to set 2 cores active.
I think freeze/restart is the reason why LG hasn't release it in official firmware and that's why we need this app
Click to expand...
Click to collapse
hi...is this apps still being supported by you?
Can you make some profile settings?
such as when the screen is off, we can set the frequency/no. of cores.
thx
Hello!
I was investigating ondemand governor for increasing my battery life and I discovered that our Nexus can drain too much less power than we thought. I have got almost 3 hours Screen On Time and have 57% battery left... Also I have to say that I spent all night with only 5% battery drain :
{
"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"
}
Note that I also get a very little decrease of general performance. But its very little
My current set:
ROM: Pure Speed X PSX 4.1 [JSS15Q] http://forum.xda-developers.com/showthread.php?t=2392624
KERNEL: Faux Kernel JSS Mainline Build 22 http://forum.xda-developers.com/showthread.php?t=2008222
Click to expand...
Click to collapse
Tweaks for super-battery saving [use with trickster mod https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod]:
GENERAL:
Read Ahead Buffer Size: 128
Scheduler: SIO
Frequency Lock: OFF
Min: 384000
Max: 918000
Governor: Ondemand
[These are the most important changes!]
-Down differential= 1
-Ignore nice load= 0
-Io is busy= 1
-Optimal freq= 384000
-Powersave bias= 250
-Sampling down factor= 1
-Sampling rate= 40000
-Sync freq= 384000
-Up threshold= 95
-Up threshold any cpu load = 95
-Up threshold multi core= 99
Click to expand...
Click to collapse
Click to expand...
Click to collapse
SPECIFIC:
Force fast charge= Off
Eco mode= On
MPDecision= Off
Intelli-Plug= On
Vibrator strength= 70
Dynamic FSYNC= Off
Temperature Throttle= Off (Not neccesary, it never heats with this config)
GPU Governor= Ondemand
GPU Max Frquency= 400
ZRAM= Off
CPU Voltages: 700,725,725,750,750,775,775,825,825,850,850,875,etc...
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Please try this, and tell me the results, I want to know if we can make battery life even longer!!!
.
reserved...
i will use this if I discover more secrets
According to the screenshot, you just.. turn on the screen and leave it there?
linh1987 said:
According to the screenshot, you just.. turn on the screen and leave it there?
Click to expand...
Click to collapse
No, I had been browsing with AOSP browser sending email and listened to some music via bluetooth. I use my phone a lot
I think that the config I posted above causes the battery monitor not register when the device is active, maybe because the phone never turns on 4 cores simultaneously, i dont know
It's no secret. you can have this battery life with a little tweaking. there at battery thread, you'll find better battery life than this.. Now Beat that
Sent from my Nexus 4 using Tapatalk 4
Sak3ater said:
It's no secret. you can have this battery life with a little tweaking. there at battery thread, you'll find better battery life than this.. Now Beat that
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Still at 52% with 3H 13MIN 3S :victory:
18H 8min 19s on battery
You have charged the phone a bit
Hahahaha :laugh:
Just connected with Pc to copy some files..It took me not more than 20secs while the phone was connected with Pc..It does not make any difference.Just a little bump in the overall graph
Anyways..Your's battery life is great..I am gonna try these settings..
---------- Post added at 05:51 PM ---------- Previous post was at 05:49 PM ----------
bamsbamx said:
No, I had been browsing with AOSP browser sending email and listened to some music via bluetooth. I use my phone a lot
I think that the config I posted above causes the battery monitor not register when the device is active, maybe because the phone never turns on 4 cores simultaneously, i dont know
Click to expand...
Click to collapse
It's okay..It happens at my end as well..I do a lot of stuff but it never shows up in the battery graph..
bamsbamx said:
Hello!
I was investigating ondemand governor for increasing my battery life and I discovered that our Nexus can drain too much less power than we thought. I have got almost 3 hours Screen On Time and have 57% battery left... Also I have to say that I spent all night with only 5% battery drain :
Note that I also get a very little decrease of general performance. But its very little
My current set:
Tweaks for super-battery saving [use with trickster mod https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod]:
Please try this, and tell me the results, I want to know if we can make battery life even longer!!!
.
Click to expand...
Click to collapse
will these settings show alot effect on gaming
I'll game your battery life down to 3 hours no matter what settings you make.
Whta do you mean by?
CPU Voltages: 700,725,725,750,750,775,775,825,825,850,850,875,et c...
The CPU Voltages range from:
384000 = 850000
to
1512000=1150000
Do you mean just undervolt by ~150? on some phones that not safe, ~100 is better?
If you played games you won't be getting that much
Sak3ater said:
It's no secret. you can have this battery life with a little tweaking. there at battery thread, you'll find better battery life than this.. Now Beat that
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
OK
Sent from my Nexus 4 using xda app-developers app
No offense but your battery outcome is nothing special.
Getting 6h+ onscreen time is pretty normal with wifi on all the time.
I reach this with standard Kernel and m_plus Kernel on cyanogenmod 10.1 and 10.2 without tweaking anything.
But I am glad you could improve your battery
AcmE85 said:
No offense but your battery outcome is nothing special.
Getting 6h+ onscreen time is pretty normal with wifi on all the time.
Click to expand...
Click to collapse
Exactly.
Once, I had 3h screen time, browsing and facebook, and still 65% left. So, theoretically, using Wifi I could browse for at least 8 hours.
I was using JWR66V at the time, stock kernel and rom, with root.
Sully6789 said:
OK
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
3Hrs sot,23Hrs total time & still 49% charge remaining :highfive:
Stop using SOT as some sort of benchmark. SOT differs for everyone and it depends what you're doing. For some, 3 hours is great, for some that's bad. It depends what you're doing. Anandtech got 6 hours SOT on the wifi benchmark for the Nexus 4 which requires the screen to be on at 200 nits brightness the whole time. You can easily get 6 hours reading an eBook.
So what?
Furthermore, underclocking your phone down to 1ghz isn't really an acceptable compromise to most.
Running it on dual core mode plus underclocked to 900 mhz and undervolted... Of course u can hit 6 hours
Nothing too fantastic
sent from my NEXUS 4 tasting a revamped cooking recipe of Jellybeans (stock 4.3).
I call your SOT screenshots and raise battery time at 100%
Sent from my Nexus 4
bamsbamx said:
No, I had been browsing with AOSP browser sending email and listened to some music via bluetooth. I use my phone a lot
I think that the config I posted above causes the battery monitor not register when the device is active, maybe because the phone never turns on 4 cores simultaneously, i dont know
Click to expand...
Click to collapse
awake, means all 4 cores are running, usually when the touch screen is running, and no heavy app is used, 2 cores are only running.
Also, please stop making this "contest" on who's getting better batter life... just charge it every night before you go to bed, and everything will be fine.
Going camping in about 2 weeks, no internet there, i'll wipe everything, and go on a clean, stock, 4.3 ROM without installing any app, that way i can determine how well android works with the battery on its own.
Wow, for me I run @1836 interactive with 4096 sio and GPU @487 and I still get 4 hours
Sent from my Nexus 4 [NEO @1.836 GHz] on [PSX v4.1 4.3]
I am using Carbon ROM 4.3 with Chronic kernal. The settings were at a min of ~1700mhz and a max of ~2200mhz. Before i set this I let the cpu temp cool to about 23 degrees Celsius. I then set the cpu governor to performance. Then I started running AnTuTu benchmark ver4. After the cpu integer test the cpu froze up. I was cooling my phone using a freezer with the phone on a paper towel which was on a bag of ice. The CPU crashed at the CPU float point test.
After another test I found that my CPU becomes unstable after 2160mhz.
The settings for the posted benchmark were CPU Min at 1674mhz and CPU Max at 2160mhz with the governor set at performance.
The minimum freq is mute when the gov is performance. Performance just keeps the cpu at the MAX freq.
Sent from my SPH-L720 using Tapatalk 2
Cloaker said:
The minimum freq is mute when the gov is performance. Performance just keeps the cpu at the MAX freq.
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
What he said.
Also you can just put the phone in the freezer for a while and let it cool way way down and then run the test while leaving it in the freezer.
Sent from my SPH-L720 using xda app-developers app
eskomo said:
What he said.
Also you can just put the phone in the freezer for a while and let it cool way way down and then run the test while leaving it in the freezer.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
I am aware of this. I did have it in the freezer until it cooled down enough. The problem was not overheating, it was the CPU becoming unstable at full load with the processor being overclocked. The phone was still cold but it went to a reboot or just turned off.
Gotcha. I missed that part. I wasn't fully awake yet at 4:30am.
Sent from my SPH-L720 using xda app-developers app
Ok buddy here is your issue buddy its all about volts and throttle limits ive been fine tuning oc steps on antutu, cf bench, geekbench2 and geekbench3. Im stable all the way up to 2106 so far I use ktoonzs kernel cuz it has more options in his app the control alot of the throttling and volts. Ok understanding what it means what the phone just shuts off or reboots when the phone shuts off and wont cut back on you either have to do pull the battery out or plug the charger in to get the phone to boot up that means you had a power overload it drawed to much power on the battery which means you neesd to drop volts on your max step. Now if the phone is just rebooting or if the app FC back to the home screen that means that you dont have enough volts for your max step you only have to add or substract volts on that one step not on the whole board the best way to do this is just by finding your volts for that max step first yes scores will be low but once you find the volts then you start adjusting the throttle limits that way you can control the heat of the cpu but once you find the sweet spot of that oc step move to the next one and start over again for the next oc step doing the steps I listed above I will post pics of what I gotten so far. On a further note I have found that the freezer trick hurts you more then gaining anything cuz if you cool the cpu and battery to much it will make the cpu run sluggish cuz its to cold to run and if the battery is to cold it makes the phone think it dont have enough power to run on that oc step and makes the phone reboot so bare in mine the freezer isnt always the best way to do this I found that if the battery is below 28c it will reboot the phone during benching and if the cpu is below 25c it sluggish as hell the best app to use is cool tool on the app store if you use kt kernel I can give you the direct path to monitor cpu temp like his app does hope this helps you understand alil better of whats going on if you need anymore info just pm me
The #1 misfit
of my crew of misfits
As you see in the 4 pic my score close to what the GT-I9500 are getting on antutu
The #1 misfit
of my crew of misfits
I found this thread very useful on the N4 forums, so here it is for the Nexus 5.
First, what is undervolting?
No two CPUs are made equally, every one is slightly different. This means they each need a different minimum voltage to run completely stable, so manufacturers set it high enough so that every chip can run without needing a voltage tailored to that specific chip. But this means that most devices can have their voltages lowered, and still run 100% stable
What are the benefits of undervolting?
In my experience, heat reduction is the main benefit. However, this heat reduction has implications elsewhere; for instance it means the thermal throttling will kick in later, so there is less of a performance drop. Also, less power is wasted to heat, meaning marginal gains in battery life. If you cannot run higher frequencies, i.e. over 2.26GHz, undervolting/overvolting these frequencies may help.
Any disadvantages?
Not really - you may experience reboots and instability, but that means you need to raise the voltages. Also, make sure you don't check set on boot until you know the voltages are stable, but if you have any problems you can flash the stock kernel, or in worst case wipe the data from a recovery.
How do I undervolt?
Many CPU apps are available to change the voltages, but personally I use Trickster Mod (donate). Just slowly decrease your voltages, small amounts at a time, and set them on boot when you are happy they are stable.
If you want to really want to get your voltages perfect, you can set the min/max frequency to one you want to modify, and edit each frequency to perfection. To save time, I'd recommend starting with the highly used frequencies - many apps can tell you which your device uses most often.
CPU Binning
I know on the nexus 4 the cpu bin was related to the amount users could undervolt, and Im sure the case is still the same, so heres how you can find out your CPU bin: http://forum.xda-developers.com/showthread.php?t=2515593 It would be useful to include your CPU bin in your post.
Here are my initial voltages, running ElementalX v0.7, CPU bin 3 and PSX - please, feel free to share yours (and your knowledge);
{
"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"
}
Rules of the thread
Be nice to each other, use search if you have a question, and don't flame noobs for no reason.
It would be helpful to include your CPU bin and kernel in your post.
Also, if I have made any errors in the OP or you feel something should be added, quote this (so I get notified) and tell me, I'm sure theres a lot more information I could include!
Reserved
PVS3 -50 Stable
uh60james said:
What's your CPU bin?
Click to expand...
Click to collapse
Just added to the op, I have a 3, which I think is about in the middle? I haven't had a proper look at the thread yet to find out
Sent from my Nexus 5 using Tapatalk
Tom540 said:
I have a 3, which I think is about in the middle?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I have a 3 too. So far sitting stable at a global -62.5 undervolt the past few days. Tried -75 a few times and got reboots when turning the screen on.
AndrasLOHF said:
I have a 3 too. So far sitting stable at a global -62.5 undervolt the past few days. Tried -75 a few times and got reboots when turning the screen on.
Click to expand...
Click to collapse
Same has just happened to me too, so I'll bump them up to -62.5, although I think I should be able to keep the lower CPU clocks at lower voltages as I'm sure the higher ones are used when turning on the screen
Sent from my Nexus 5 using Tapatalk
I'm running franco r14 and got two almost immediate reboots on your settings. Gonna go a little easier. I have no experience doing this, so it's still a bit confusing.
can probably go a bit easier on the higher clocks, my settings are -75 mv below 1.8 ghz and -50 above. Just played some deer hunter 2014 and seems to be fine. No reboots so farr! My bin is 3 as well. Running stock rom with faux003b6 kernel
I have a bin of 3 as well. I've only been brave enough to go -37.5 on Fauxs latest beta kernel
Sent from the jaws of my Hammerhead!
Got a CPU bin of 2. I went for -50 undervolt for all frequencies on Faux kernel 002 a few days ago, no reboots so far. Haven't tried -62.5 but -75 was too much, so I'll stick with -50.
I was a little bummed when I found out I had bin 2, but I've been running -75mv no problem for the past few days on bricked kernel
Sent from my Nexus 5 using xda app-developers app
You guys are lucky. My phone has bin of 1, could only uv 50mv on high frequency and 75mv on the low end, and I have higher default voltage to begin with.
---------- Post added at 01:33 AM ---------- Previous post was at 01:29 AM ----------
So far I believe the best app to test UV stability is Antutu Benchmark, I could pass StabilityTest no problem but Antutu always FC when I UV bit too hard.
Spunky_Monkey said:
I was a little bummed when I found out I had bin 2, but I've been running -75mv no problem for the past few days on bricked kernel
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
wow.. im have bin 3 and anything past -62 I get reboots... I think I got ripped of on on my cpu
gd6noob said:
wow.. im have bin 3 and anything past -62 I get reboots... I think I got ripped of on on my cpu
Click to expand...
Click to collapse
Exactly the same with me - I think I might be able to set the lower CPU clocks with voltages lower though, I just need a bit more time to test
Sent from my Nexus 5 using Tapatalk
I have a PVS 0 and I can undervolt - 100 without any lockups or reboot. Actually the device hasn't rebooted on me once ever. The only problem is it lacks CPU performance but the GPU works fine.
Sent from my Nexus 5 using Tapatalk
Tom540 said:
Exactly the same with me - I think I might be able to set the lower CPU clocks with voltages lower though, I just need a bit more time to test
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Let me know what your findings are... im just too lazy to test all the configs..
gd6noob said:
wow.. im have bin 3 and anything past -62 I get reboots... I think I got ripped of on on my cpu
Click to expand...
Click to collapse
Bin 3 here, I've been running with - 75 since yesterday without problem... Maybe I'll go lower
Sent from my Nexus 5 using Tapatalk 2
PVS 2 running - 75 volts full speed. Deer hunter runs great so far. Might try - 100 after more testing.
Sent from my Nexus 5 using XDA Premium 4 mobile app
seems like pvs3 is NOT the best for UVing, its all accross the board, im on PVS2 and i think i can do -75 easily , i think im on -50 accross, using franco kernel r14
It might be helpful if everyone included the actual voltages as well, as some have reported starting with different voltages, and some kernels UV put of the box.
PVS 3, I'm running 712.5 @ 300MHz, and 962.5 @ 2.26GHz; check the screenshot in the OP for all voltages
Sent from my Nexus 5 using Tapatalk
Although this might seem as a question. It really isnt.
What kind of battery life do you get on the First? Screenshots would be nice, but what is like the max time and min time you got and what kind of setting do you use, voltage, clock speed, usage etc.
Also has anyone been using the MSM-DCVS (dynamic clock and voltage scaling) CPU Governer? And if yes then have you gotten better battery life? I will do a test tomorrow and see how it goes.
My best stats.
Well before i got into cpu governors, by default the phone uses on-demand and i could max out 14 hours with variable usage. screen on maybe 50% of the time the phone was on and minimal gaming. texting. I dont have data so that didnt take any battery (i hear 4g and 3g take away lots of juice, is that true?).
Okay. So just did a quick test with msm-dcvs.
Basically for 5 minutes I tested each governed doing the same stuff.
Msm-dcvs utilizes deep sleep ALOT more. Almost 8 times more than on demand. And doesn't really use anything in between. So it goes from deep sleep to minimum 300mhz to get it going and then jumps to the max of 1.4ghz and if the screen is on it uses 700mhz.
So using deep sleep it saves batter.
On demand on the other hand tends to use 300mhz instead of deep sleep. It also jumps around a lot between all the various clock speeds using just about anything it can. So i guess on demand will get worse battery life but I will report my findings in a few hours seeing bow battery life goes with dcvs.
Sent from my HTC first using XDA Premium 4 mobile app
Just a quick update. On demand is crap. Performance is really good and dcvs is performance just more intelligent
Sent from my HTC first using XDA Premium 4 mobile app
My battery life is crap. I've tried to adjust clock speed & voltage but I don't believe JMZ's latest kernel supports it and I'm never able to get any governors besides stock to stick
abrahammmmmmm_ said:
My battery life is crap. I've tried to adjust clock speed & voltage but I don't believe JMZ's latest kernel supports it and I'm never able to get any governors besides stock to stick
Click to expand...
Click to collapse
Use performance. It has a really fast "rave-to-idle" speed. This means that the phone will finish tasks faster and go to idle/deep sleep. So it should save you batter. Unless you don't mind lag and use msm-dcvs which is performance just it takes time to ramp up the speed.
Sent from my HTC first using XDA Premium 4 mobile app
russian392 said:
Use performance. It has a really fast "rave-to-idle" speed. This means that the phone will finish tasks faster and go to idle/deep sleep. So it should save you batter. Unless you don't mind lag and use msm-dcvs which is performance just it takes time to ramp up the speed.
Sent from my HTC first using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What app do you use for this? All the ones I've tried don't make any custom settings stick
abrahammmmmmm_ said:
What app do you use for this? All the ones I've tried don't make any custom settings stick
Click to expand...
Click to collapse
CPU master by antutu. I've always used it. Best one there is
Sent from my HTC first using XDA Premium 4 mobile app
russian392 said:
CPU master by antutu. I've always used it. Best one there is
Sent from my HTC first using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Alright I'll try the app. BTW I'm pretty sure 918mhz isn't the stock minimum... Must explain my horrible battery. What do you have yours on?
Edit: so far so good. I'm feeling some better battery life even tho it might just be a placebo effect I know that the CPU will have less strain & rest more now that the minimum is at 384. And few more questions, what do you have set for your I/O scheduler and also did you configure the voltage?
It's important for battery life, that the phone goes into deep sleep while screen is off. Use this app to test whether thats the case: BetterBatteryStats
Also you can see which process "wakes up" the phone while it should sleep.
My First normaly runs about 2 days without charging. So battery is pretty good!
PS: I'm using deodexed rom with stock kernel.
G00fY2 said:
It's important for battery life, that the phone goes into deep sleep while screen is off. Use this app to test whether thats the case: BetterBatteryStats
Also you can see which process "wakes up" the phone while it should sleep.
My First normaly runs about 2 days without charging. So battery is pretty good!
PS: I'm using deodexed rom with stock kernel.
Click to expand...
Click to collapse
Wow that's great battery life.
I'm yet to test dcvs in my first and see how long that lasts me. I have Wi-Fi on all day. So I can get up to 14 hours max.
Sent from my HTC first using XDA Premium 4 mobile app
abrahammmmmmm_ said:
Alright I'll try the app. BTW I'm pretty sure 918mhz isn't the stock minimum... Must explain my horrible battery. What do you have yours on?
Edit: so far so good. I'm feeling some better battery life even tho it might just be a placebo effect I know that the CPU will have less strain & rest more now that the minimum is at 384. And few more questions, what do you have set for your I/O scheduler and also did you configure the voltage?
Click to expand...
Click to collapse
No I have yet to figure out io bit tinkering with voltage isn't a good idea since the battery is specifically set to a voltage the phone needs.
Sent from my HTC first using XDA Premium 4 mobile app
Okay I have some new findings. Idk about the custom kernel...bit with stock you only get 3 I/o schedulers. Noop, deadline, and cfq. Noop is first come first serve. Deadline reorders the task sequence and does what it thinks should come first...good for like gaming. And cfq. Which evenly distributes the power amongst all tasks. If you are using cfq make sure you kill unused tasks all the time. If you use a lot of things on your phone and multitask a lot use deadline. Noop is pointless unless you don't use your phone for anything. And cfq is just an alternative to deadline. So I/o won help much.
Then in CPU master. Go to advanced. And press "disable perflock". It will explain what it does. Hit set on boot. And reset you clock settings. Now we shall see what we get.
Sent from my HTC first using XDA Premium 4 mobile app
Okay guys. I used deadline to see if that would change anything. With the same dcvs setting with deadline I got 15% batter down in 2 hours. That's pretty good. That's 7.5% an hour.
And this is with screen on and wifi on about 70% of the time.
Sent from my HTC first using XDA Premium 4 mobile app
Okay this is my final say on how to get the most out of your battery life.
There are two set ups
1. Lag free/ smooth set up
Min 384mhz, Max 1080mhz
Governer: Performance
i/o Scheduler: Deadline
-This set up will save battery why? Because 1. You don not need your max 1.4 ghz to keep the phone running lag free, and in performance mode, the phone is LOCKED into 1.4ghz until you dim the screen and it goes into deep sleep. no inbetween. So clocking down will help save EVEN MORE battery. So unlike dcvs you will not have lag when you turn your screen on. It will jump from zero to 1ghz in a few milliseconds.
2. Inteligent
Min: 432mhz, Max 1.4ghz (default max. Dont over clock)
Governer: MSM-DCVS
i/o Scheduler: CFQ
-This set up will save battery, i go down about 1% every 6-20 minutes depending on usage. (6 being max usage and 20 meaning iddle). Once you turn the screen on your device will lag slightly and then will work just fine. This set up is good for those people who dont ALWAYS need max performance. Example: Reading an email doesnt require your phone to be locked at max frequency all the time so it will down clock the device. It simply takes time for it to rev the engine.
3. On Demand
Well this is simply absoule minimum to absolute maximum with NOOP as the i/o. This is the ultimate ondemand set up as it will do what you are currently doing first then do the rest while constantly changing clock speed.
Also...btw changing clock speed takes battery that is why performance saves batter not uses it. Its either deep sleep or max and thats it.
I will add screenshots to this soon once im done with all my tests.
Battery life today on msm-dcvs
I should be at 30% right now bit pretty good battery tight now
Sent from my HTC first using XDA Premium 4 mobile app
Tried today MSM-DCVS scheduler on my stock rooted firmware. Don't like it. Lags a lot when screen on (and CPU at max 1.4Ghz). And i do not see any significant battery improvements, instead it seems that it takes longer time for phone to do background tasks like mail checking etc.
Concerning battery life - in general I receive 3-3.5 hours of screen time. And it can be 1 day to 3. It all depends on usage, but screen on time never goes above 4 hours.
In attached file - Stats for my phone while traveling from the U.S. to Russia. As you can see, delivery does not take very much time And in standby mode phone can last almost two weeks (with wi-fi and nfc on).
Hulo_ said:
Tried today MSM-DCVS scheduler on my stock rooted firmware. Don't like it. Lags a lot when screen on (and CPU at max 1.4Ghz). And i do not see any significant battery improvements, instead it seems that it takes longer time for phone to do background tasks like mail checking etc.
Concerning battery life - in general I receive 3-3.5 hours of screen time. And it can be 1 day to 3. It all depends on usage, but screen on time never goes above 4 hours.
In attached file - Stats for my phone while traveling from the U.S. to Russia. As you can see, delivery does not take very much time And in standby mode phone can last almost two weeks (with wi-fi and nfc on).
Click to expand...
Click to collapse
Personaly i dont have NFC or 4g on at any time. 1. i dont have data and 2. i dont use nfc cause the so called "modern world" is still stuc on stupid apple devices.
I noticed the following issues with managing the cpu
1. When setting cpu clock speed, after about 5 seconds after you left the app it changes the clock speed back to how it was
FIX: in cpu master (or the app of your choice) go to advanced and turn perflock off. then go to the cpu settings and set the speed you want. you must do that every time though cause of the htc kernel
2. MSM-DCVS lags.
FIX: set your minimum to 450-500 mhz
3. 4g drains batter (or so i hear)
FIX: idk yet but if someone could show me their battery life with 4g on and normal daily usage i could try to figure something out.
Hulo. Try this set up
Performance, 300mhz - 1080mhz, deadline
IDK my phone syncs things quite well and lag isnt a big issue for me, i can deal with it because my old phone overclocked is 700mhz so lag isnt anything new to me. So i just notch up the minimum to reduce it.
MSM-DCVS saves batter when screen is off and when screen is on but idle. playing games or actively using the screen will drain battery no matter what setting you use. This is made for people who are constantly on their phones.
Performance saves battery when screen is OFF period. When screen is on its at its max. this is best used for people who dont use their phones alot.
With dcvs i got an extra 7 hours of battery life. usually i get 11. But i hear with 4g on your battery dies in about 6 hours? is that true?!
russian392 said:
Personaly i dont have NFC or 4g on at any time. 1. i dont have data and 2. i dont use nfc cause the so called "modern world" is still stuc on stupid apple devices.
I noticed the following issues with managing the cpu
1. When setting cpu clock speed, after about 5 seconds after you left the app it changes the clock speed back to how it was
FIX: in cpu master (or the app of your choice) go to advanced and turn perflock off. then go to the cpu settings and set the speed you want. you must do that every time though cause of the htc kernel
2. MSM-DCVS lags.
FIX: set your minimum to 450-500 mhz
3. 4g drains batter (or so i hear)
FIX: idk yet but if someone could show me their battery life with 4g on and normal daily usage i could try to figure something out.
Hulo. Try this set up
Performance, 300mhz - 1080mhz, deadline
IDK my phone syncs things quite well and lag isnt a big issue for me, i can deal with it because my old phone overclocked is 700mhz so lag isnt anything new to me. So i just notch up the minimum to reduce it.
MSM-DCVS saves batter when screen is off and when screen is on but idle. playing games or actively using the screen will drain battery no matter what setting you use. This is made for people who are constantly on their phones.
Performance saves battery when screen is OFF period. When screen is on its at its max. this is best used for people who dont use their phones alot.
With dcvs i got an extra 7 hours of battery life. usually i get 11. But i hear with 4g on your battery dies in about 6 hours? is that true?!
Click to expand...
Click to collapse
I'd just like to add that 4g actually consumes LESS battery than 2g/3g/3.5g only LTE tho. That's because it's more optimized and advanced I've read and experienced it in many occasions
abrahammmmmmm_ said:
I'd just like to add that 4g actually consumes LESS battery than 2g/3g/3.5g only LTE tho. That's because it's more optimized and advanced I've read and experienced it in many occasions
Click to expand...
Click to collapse
Alright then. Interesting. My friend on his s3 gets 6 hours of battery with 4g.
Sent from my HTC first using XDA Premium 4 mobile app
russian392 said:
Alright then. Interesting. My friend on his s3 gets 6 hours of battery with 4g.
Sent from my HTC first using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I should add that the optimized battery life for LTE is only true tho for new snapdragon CPU's including Apple's processors as well. I'm not aware of tegra or any exynos at the moment.