Related
If you have undervolted your Nexus 7 or any other tegra 3 based device please post the results here so I can throw them into a Excel sheet for development.
Using advanced mathematics and complex formulas I will make a undervolted kernel that's stable for everyone. For that, I need ideally 30 results or more. Less is ok but more or equal is better.
FORMAT 1:
CPU
- [FREQ1] [VOLTAGE1]
- [FREQ2] [VOLTAGE2]
- [FREQ3] [VOLTAGE3]
- ,,,
Click to expand...
Click to collapse
FORMAT 2:
CPU GLOBAL: [OFFSET]
Click to expand...
Click to collapse
I also accept 1 frequency result. You don't have to undervolt everything. I favor the last known voltage that crashes as well if you can send this I am even more happy.
Undervolted mine by 50mv
Sent from my Nexus 7 using Tapatalk 2
djjonastybe said:
If you have undervolted your Nexus 7 or any other tegra 3 based device please post the results here so I can throw them into a Excel sheet for development.
Using advanced mathematics and complex formulas I will make a undervolted kernel that's stable for everyone. For that, I need ideally 30 results or more. Less is ok but more or equal is better.
Click to expand...
Click to collapse
In order to use "advanced mathematics" and "complex formulas".. You might want to provide a format for "the results" you want people to provide.. Without a stream of formatted data to input your "complex formulas" and "advanced mathematics" is impossible..
"Advanced mathematics" and "complex formulas" sounds like you are doing an infomercial.
Pure waffle.
Sent from my GT-I9300 using xda premium
djjonastybe said:
..I will make a undervolted kernel that's stable for everyone
Click to expand...
Click to collapse
ha! good luck. considering some devices arent stable at all when undervolted just a tiny bit, and otbers are stable with a lot of undervolting, you have a tough road ahead of you.
simms22 said:
ha! good luck. considering some devices arent stable at all when undervolted just a tiny bit, and otbers are stable with a lot of undervolting, you have a tough road ahead of you.
Click to expand...
Click to collapse
I actually came back to post exactly this but Simms22 was too quick, as usual!
Sent from my GT-I9300 using xda premium
nodstuff said:
"Advanced mathematics" and "complex formulas" sounds like you are doing an infomercial.
Pure waffle.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I see you went with the more direct and honest approach. I tried being more subtle with my response.. :laugh: But yeah.. Marketing hype for a kernel.
styckx said:
I see you went with the more direct and honest approach. I tried being more subtle with my response.. :laugh: But yeah.. Marketing hype for a kernel.
Click to expand...
Click to collapse
Might as well be honest, set him on the right track early in his dev career rather than him rely on buzzwords and fud like some people do.
These are forums for android devices, not Apple devices, the reality distortion field doesn't work here, fancy marketing terms should be left at the door.
Sent from my GT-I9300 using xda premium
My Galaxy Nexus is proof of undervolting being unstable using software while being stable with manually programming the voltages. So I am going to give this a good shot anyway.
My Galaxy Nexus uses SmartReflex to undervolt.
Look at this table I made:
https://docs.google.com/spreadsheet/ccc?key=0AuqacKmGLKJ6dEdJZG5QTmNtQnoyYk0zbm5IanluMHc#gid=1
You see the core or gpu was already crashing at 974mV, which was the reason why I stopped undervolting using the thread. But don't give up, I tried again using SmartReflex because I felt I should be able to get lower. And now I am at 911mV but I did not try to get lower yet.
I plan on undervolting by actually programming it. I don't know how you guys undervolt for the Nexus 7, since I am fairly new with this device.
READ FIRST POST for formatting
nodstuff said:
"Advanced mathematics" and "complex formulas" sounds like you are doing an infomercial.
Pure waffle.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/Student's_t-distribution
Using that I can calculate which voltage to take that will work for 90% of us or 99% of us or maybe 100% ?
For that I need some results. The more the better.
The only voltage settings that will work for 100% of people are stock voltages.
you will run into endless problems if you release an undervolted kernel because what works for 75% of people won't work for the rest.
If you adjust voltages to include more people the people that can handle the lower voltages aren't getting the full savings their device can handle. Which defeats the point of releasing an undervolted kernel to save battery.
Undervolting should be up to the individual, just release with stock voltages and make a guide showing people how to undervolt.
Sent from my Nexus 7 using xda premium
nodstuff said:
The only voltage settings that will work for 100% of people are stock voltages.
you will run into endless problems if you release an undervolted kernel because what works for 75% of people won't work for the rest.
If you adjust voltages to include more people the people that can handle the lower voltages aren't getting the full savings their device can handle. Which defeats the point of releasing an undervolted kernel to save battery.
Undervolting should be up to the individual, just release with stock voltages and make a guide showing people how to undervolt.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
^^ Truth
I've done a bit of pc overclocking over the years and we'd always seek out the best steppings to find cpu batches that would give a better clock speed for less volts. What would work on one person's cpu wouldn't work on another sometimes even within the same stepping. (My current machine is getting long in the tooth but it's running a 33% OC below stock volts and stable as a rock.)
When the N7 cpu's are tested the stock voltage is the point where 100% of them will run without issue. Certainly there are many, maybe even most N7's that will run undervolted but until you try it you just won't know. Undervolting needs to be done on a case by case basis.
I uv by 100mv on every step on Franco kernel and I've never had a sod or reboot. Maybe you could release different versions like light, medium and heavy to cater to different users that have sets than can uv more or less. To address all these people naysaying I say just go for it, don't let these people dishearten you from what you want to do. I'm sure there will always be users who are willing to try
sorry to break the fun lol
Opened a thread with undervolting settings in different situation. For now i think its the lowest possible
bervin said:
I uv by 100mv on every step on Franco kernel and I've never had a sod or reboot. Maybe you could release different versions like light, medium and heavy to cater to different users that have sets than can uv more or less. To address all these people naysaying I say just go for it, don't let these people dishearten you from what you want to do. I'm sure there will always be users who are willing to try
Click to expand...
Click to collapse
That's exactly the same as what I have done. 100mV right across the board, and I have also never had a reboot or any other negative effect from doing it. Just a bit more battery life.
I too UV 100mv across the board. Never had an issue. And I OC up to 1.6ghz.
phonic said:
I too UV 100mv across the board. Never had an issue. And I OC up to 1.6ghz.
Click to expand...
Click to collapse
Same here, no issues with 100mv UV on stock speeds. What would happen if we went too low, would it fail to boot at all or is there some safety mechanism that would allow us to boot into boot loader?
davidoff59 said:
Same here, no issues with 100mv UV on stock speeds. What would happen if we went too low, would it fail to boot at all or is there some safety mechanism that would allow us to boot into boot loader?
Click to expand...
Click to collapse
When either OCing or UVing, you should ALWAYS test out the changes prior to saving them as a persistent boot state. This way, if you set something too high/low and it proves to be unstable, if you restart the device it will revert back to normal.
In the event that you OC/UV too much, yes, you would see signs of instability. In some cases it could show up as soon as you applied to change, in other cases it could take a while to notice. For example, some games or other high processing powered activities could FC/crash. Or your tablet might freeze or reboot. But again, as long as you didn't save your changes as a boot setting, it will be fine once it reboots.
In the event that you did save it, and the settings were unstable for your device, you could boot up into recovery and then manually erase them from taking effect. Recovery doesn't use those settings, as it's technically a different OS. But that can be complicated a process for some. So test test test save. Or don't save and just apply them manually.
Two other points:
Yes, most (all?) devices do have safeguards to protect itself against permanent hardware damage from OC/UVing. If it gets too hot, they will often shut down to protect themselves.
And just because one device can handle being OC'd or UV'd to a certain level doesn't mean they all can. Very minor differences in each component can impact one devices ability from another. The manufacturers only test to see if they can handle the published speeds/etc., but in many cases they can go higher if set to. In others, not so much.
Thanks for that phonic. Given the range of ROMs and kernel's available and the improvements already built in, under volting may not help a lot but every bit helps. Eg this screen on time is pretty good.Close to six hours screen on time with iirc 35% battery remaining.
Paranoid android with motley kernel. I don't over clock the nexus 7 as its fast enough. In fact I under clocked it to 1000 MHz max before and it was still fast but the screenshots are at stock volts and speeds.
it's actually plain simple. If everyone posts results. I can make a kernel with voltages that work for 75% of all people or maybe for 95% of all Nexus 7 owners.
It's called mathematics. But to do that I need as much results as possible.
Easy to do if you know what you are doing, right ?
http://en.wikipedia.org/wiki/Confidence_interval
Hi I have recently purchased a 32gb nexus 7 and I have been having some issues with the battery since the 4.2.1 update, before this update I would get around a day on the battery no problem now I can't seem to get more than 16 hours at the most. My usage includes facebook at night for roughly 2 hours, moderate gaming during the day, and some web browsing in my spare time. All this was never a problem on 4.1 but in 4.2, the battery just seems redundant. I would like to hear your thoughts on your battery life on your nexus 7's thank you.
Sent from my Nexus 7 using xda app-developers app
How much gaming is moderate?
I noticed my governor was on interactive tonight, which was maxing the CPU even just by touching the screen, I thought my battery life seemed quite good though.
Anyway, I changed my governor to ondemand, and noticed that simply touching the screen only moves the CPU freq to 3-500mhz.. Which is fine for browsing etc... I have also played games, and I haven't noticed any lags... yet... But if there is a really hungry game that I do start to notice a lag in, I'll just put it back to interactive for that game, and meantime I should have better battery life.
Like I said, I only just changed this, so I'm yet to see how much better my battery does, but just from looking at CPU freqs I'd say there's gotta be a decent difference.
There's an idea for an app for some dev... Per app governer setting...
Sent from my Nexus 7 using Tapatalk HD
I always had excellent battery life, no matter which android version.....
Do you use Google Currents? If not, stop the service and disable it completely.
Furthermore, please post a screenshot of your battery usage.
Sent from my HTC Desire using xda premium
dalanik said:
I always had excellent battery life, no matter which android version.....
Click to expand...
Click to collapse
That's pretty damn impressive. How much screen on time is that?
On my second charge I got ~2.5d with about 4-5 hours of screen on (stock). More than satisfactory!
jasopan said:
That's pretty damn impressive. How much screen on time is that?
On my second charge I got ~2.5d with about 4-5 hours of screen on (stock). More than satisfactory!
Click to expand...
Click to collapse
Looks like 0 screen on to me, device is sitting idle. Mine would last weeks from what I've seen in standby, but yeah, I use my Nexus 7...
knuckles1978 said:
How much gaming is moderate?
I noticed my governor was on interactive tonight, which was maxing the CPU even just by touching the screen, I thought my battery life seemed quite good though.
Click to expand...
Click to collapse
Default governor is intended to max the CPU when you touch the screen, in fact it's an advertised feature for the Nexus 7. There could perhaps be a step up to a higher CPU then higher yet if needed, but the problem with that is you get jumpiness if you switch CPU speeds around when things are going on, like launcher swipes, games, etc.
Per-app governor is already easily done today in Tasker.
Aw man
MatDrOiD said:
Do you use Google Currents? If not, stop the service and disable it completely.
Furthermore, please post a screenshot of your battery usage.
Sent from my HTC Desire using xda premium
Click to expand...
Click to collapse
Hell naw, just set it to only sink on charge
That means I update my articles in the morning and evening only, and whenever else I plug it in.
khaytsus said:
Per-app governor is already easily done today in Tasker.
Click to expand...
Click to collapse
Thanks for that, I'll check it out. There is no performance loss when web browsing or similar tasks with the on demand, so I'll just use interactive for intensive games, and extend my battery a bit in that case.
Sent from my Nexus 7 using Tapatalk HD
Sent from my Nexus 7 using xda app-developers app
No I do not use Google currents at all, I can't understand how people get so much battery from it whereas I get hardly anything
Sent from my Nexus 7 using xda app-developers app
khaytsus said:
Looks like 0 screen on to me, device is sitting idle. Mine would last weeks from what I've seen in standby, but yeah, I use my Nexus 7...
Click to expand...
Click to collapse
I was like 2 hours usage total. I used it only to check my mail and write some replies, check news and such...
khaytsus said:
Per-app governor is already easily done today in Tasker.
Click to expand...
Click to collapse
Well, I'm now a happy guy.
Downloaded tasker. I now have my pad set on ondemand for browsing and light duties only with a 1ghz cap which I cannot tell any difference from stock clock,, and then when I launch any intensive games I have tasker automatically overclocking to 1.5Ghz, changing governor to interactive and closing some stuff letting my pad concentrate on the job in hand without me having to do a single thing. Then when I exit my game, tasker automatically clocks back down again and puts the governor back to ondemand.
I also have it automatically only use Sync if the battery is above 40%. I'm liking tasker, and these are only very simple uses for it, some of the example ones are really cool. @khaytsus Thanks again for telling me about it, wouldn't have known otherwise. Now I want to get more into it and seeing what it can really do using the variables etc, and the appmaker.
Another thing about battery. I got my n7 as a US import to the UK, and just noticed today that the charger they supplied me was 700mA instead of 2A,, so I went and bought a UK to US adaptor so I could use the ASUS OEM one, and its charging loads faster, should be nearly 3 times and so far it does seem it. If I was playing a game while charging, say Vice City, before I was able to actually make my N7 lose charge. Not now. So anyone with the slow charge problem please just double check your charger, just in case,, there's probably someone else out there like me that just didn't bother looking and is using a 700mA one.
Sent from my Nexus 7 using Tapatalk HD
Timed from 0% with the 2A charger. 2 hours from empty tank. That's more like it
Sent from my Nexus 7 using Tapatalk 2
Wow! That was fast! Mine is 3 hours on the stock 4.2 rom and kernel..
Sent from my Nexus 7
This is my battery life running latest CM 10.1 nightly and latest Franco kernel.
Sent from my Nexus 7 using Tapatalk 2
Nice. I'm assuming there wasn't much gaming in your 8hrs of screen time. Still great battery life though. As long as I can do anything I like in the space of a day and be sure that I'm not going to run out then I'm happy.
I am still thinking of investing in one of those 10 or 12,000mAh battery packs though, just for times where I have to leave the house and haven't had the time to give it a full charge.
http://www.amazon.co.uk/EasyAcc-12000mAh-Portable-External-Battery/dp/B008YRG5JQ/ref=pd_sim_sbs_ce_2
http://www.amazon.co.uk/RAVPower®-D...Smartphones/dp/B00974FC2G/ref=pd_sim_sbs_ce_5
Sent from my Nexus 7 using Tapatalk 2
I do not do a lot of gaming. Mostly browsing the web and reading forums. I am very satisfied with life like that for my uses.
Sent from my Nexus 7 using Tapatalk 2
Stock 4.2.1, m-kernel' cpu1.3; gpu526; LP666. 6 hours of screen on time minimum. Just daily use, with light gaming ( safari ski, etc).
Sent from my Nexus 7 using xda app-developers app
ajrich80 said:
I do not do a lot of gaming. Mostly browsing the web and reading forums. I am very satisfied with life like that for my uses.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
what's your Franco kernel setup?
Sent from my Nexus 7
My n7 with franco kernel r38 I get around 10-11 hours screen on time if I can keep off gta3
I've always been a big fan of undervolting. These are the lowest voltages I can get stable at these common speeds. I found I can underclock the Matr1x kernel further than some others I have tried for some unknown reason. How low have you been able to go? Also, what programs do you use to test stability? So far, I have been running Antutu test completion as a measure of stability. Any suggestions otherwise?
288MHz - 650mv
1.02Ghz - 800mv
1.51Ghz - 1000mv
ROM: Bionic AOSP V3
Kernel: Matr1x 6.5
Noob question~ Why do people undervolt?
WarToilet said:
Noob question~ Why do people undervolt?
Click to expand...
Click to collapse
To increase battery life,
The Long answer is that the CPU has a number of parameters where Clockspeed (MHz) and voltage (mV) are two. Clockspeed, well that is speed. Voltage is related to the amount of energy provided to the cpu, undervolting means that you feed the CPU less juice but demand that it runs at the same clocks. You are essentially starving the CPU,it uses less energy, but can become unstable if the voltage is insufficient to maintain operations. Manufactures always have extra voltage as a safety margin so power users can check their CPU bin (slow, normal, fast or faster) and lower voltages step by step until they crash the phone during a stress test, increase the voltage slightly and boom, your phone uses less battery power while being just as fast.
I undervolt to reduce heat. It makes a significant difference. The battery saving is minimal, but the temperature difference is VERY noticeable.
estallings15 said:
I undervolt to reduce heat. It makes a significant difference. The battery saving is minimal, but the temperature difference is VERY noticeable.
Click to expand...
Click to collapse
Took words from my mouth. This this and this. It reduces heat, which in turn reduces battery use. UV by itself doesn't save a lot of battery, it's the consequences of it. I'm normally not a fan of UV, but with current N4 sw/fw it NEEDS it. It's way too high.
Interesting observation. As of recently my phone jumps up by 3-5c from 37-38 hover. Never used to do it before, not until i got it up to 50c for about half an hour last week. Previously it would stay steadily at 37-38, now it spikes up now and again during use. What's interesting about is that once it goes over 40c battery use increases drastically. So i wonder if people that have really good battery life don't have phones that go over that temp often and vice versa.
I haven't played around with the values too much yet, just a -100mV across the board. This seems to work just fine, so I might experiment some more..
Using Franco test-r69 at the moment.
Sent from my Nexus 4 using xda premium
I undervolt to prevent heating like others say. My Antutu scores drop like a rock when I'm at stock clockspeeds mostly likely due to thermal throttling. Now I can run it repeatedly without having scores drop. It saves battery and runs faster while running games even for very short periods of time, so I am a big fan of undervolting. :good:
Undervolt to reduce power usage, think of the stock voltage as normally being more than is required, think of running for a bus yet you have 2 minutes why waste energy when you can walk and still make it .
Undervolt for less power usage and less heat produced meaning battery performance is better (cooler battery is a more efficient one) and performance is up as you avoid any thermal limits in place .
Great stuff undervolting, I have managed to get -150mV across the board ( 1.5ghz @ 1000mV) and 288mhz is 162.5mV .
I came from a nexus s ... And one member of xda went to amazing lengths to show that undervolting really made very little differences in battery life ... And it def wasn't worth the instability .
He did loads of tests and I mean loads and basically showed that in helped so little that if you had a reboot you would use more power in rebooting then saving via undervolt
However . it is worth it for the heat decrease for sure
Sent from my Nexus 4 using Tapatalk 2
italia0101 said:
I came from a nexus s ... And one member of xda went to amazing lengths to show that undervolting really made very little differences in battery life ... And it def wasn't worth the instability .
He did loads of tests and I mean loads and basically showed that in helped so little that if you had a reboot you would use more power in rebooting then saving via undervolt
However . it is worth it for the heat decrease for sure
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
The more the heat, the faster the battery drains. Since undervolting decreases heat, im sure it should increase battery life. Maybe not for browsing or calling, but playing a heavy 3D game.
is it normal that the higher the frequency the lower the voltage in setcpu?
screenshot: http://db.tt/k6r8c5oI
I'm quite new to nexus 4 undervolting, what's the average amount i can lower the voltages with? (i have a nominal CPU)
sent from my Nexus 4...
zakoo2 said:
how can you guys undervolt? is there an app for that? i bought Franco's kernel updater app, but there's no option to undervolt in there.
edit: just found an app called setcpu, is that it?
sent from my Nexus 4...
Click to expand...
Click to collapse
You can do it from franco kernel updater, from frequencies and voltages - voltages - cpu voltages
But i dont recommend you to undervolt if you dont know what you do.
Sent from my Nexus 4 using Tapatalk 2
aimcr7 said:
You can do it from franco kernel updater, from frequencies and voltages - voltages - cpu voltages
But i dont recommend you to undervolt if you dont know what you do.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I'm familiar with undervolting both on PC and on phone, but i had a Motorola defy before my nexus and undervolting there was a bit different.
sent from my Nexus 4...
zakoo2 said:
is it normal that the higher the frequency the lower the voltage in setcpu?
screenshot: http://db.tt/k6r8c5oI
I'm quite new to nexus 4 undervolting, what's the average amount i can lower the voltages with? (i have a nominal CPU)
sent from my Nexus 4...
Click to expand...
Click to collapse
How are you able to undervolt with SetCPU? I'm not seeing that option using CM10, and Harsh's kernel.
italia0101 said:
I came from a nexus s ... And one member of xda went to amazing lengths to show that undervolting really made very little differences in battery life ... And it def wasn't worth the instability .
He did loads of tests and I mean loads and basically showed that in helped so little that if you had a reboot you would use more power in rebooting then saving via undervolt
However . it is worth it for the heat decrease for sure
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Former nexus s user here, the reason nexus s didn't benefit in battery life much was that it only had 1 core, and used a higher nm manufacturing process, 65nm -> 28nm. Lower voltages in the 28nm means that it multiplies the heat/power savings more than a 65nm, and the 4 cores multiply the savings by up to 4.
FatalityBoyZahy said:
How are you able to undervolt with SetCPU? I'm not seeing that option using CM10, and Harsh's kernel.
Click to expand...
Click to collapse
don't know, it was just there. did you try to reboot after installing the app?
I'm on Franco's kernel btw.
sent from my Nexus 4...
Pls what are the right values for under volting Samsung captivate
Sent from my SGH-I897 using xda premium
I am new to this and my battery goes +40°C when I play simple games... I am running Franco's kernel r71 should I do UV? If so how much? Thanks in advance
Sent from my Nexus 4 using xda app-developers app
xtremer92 said:
Pls what are the right values for under volting Samsung captivate
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
this is the lg nexus 4 forum.
sent from my Nexus 4...
Hi guys!!!!!!!!
I want to know, if i want to overclock my nexus 7 what is the max safe temp i can go?
If my fuzzy memory serves me right stock thermal throttling starts at 85c and thermal shutdown at 100c..
Thanks
Thanks but is not what i asked for i asked for the max SAFE temp for the nexus 7 because i want to overclock the device!!!!
But thanks anyway
If someone wants to put their opinion go head that will help me ALOT!!!!!!!!!!!!!
GumarGamer said:
Thanks but is not what i asked for i asked for the max SAFE temp for the nexus 7 because i want to overclock the device!!!!
But thanks anyway
If someone wants to put their opinion go head that will help me ALOT!!!!!!!!!!!!!
Click to expand...
Click to collapse
Oh boy.. ..... ... What I gave you is EXACTLY what you asked for. I'm going to suggest you don't overclock because it's apparent you have no idea what you're doing or talking about.
I know what i am doing
I overclocked many devices and computers so i know what i am doing but 85 is not a safe temp so if know the max safe temp tell me if you don't stop insulting me and get a life.
GumarGamer said:
I overclocked many devices and computers so i know what i am doing but 85 is not a safe temp so if know the max safe temp tell me if you don't stop insulting me and get a life.
Click to expand...
Click to collapse
Negative bro. Just because you've overclocked "many devices" doesn't mean you know what your talking about. He answered you and your response is get pissed and tell him he's wrong? If you know he's wrong you must know what's right, so why'd you ask!? If the manufacturer sets the the "safe temp" at 85 then yes 85 is safe enough. If you think that's too warm, fine pick a lower temp and go with it.
Sent from my Nexus 7 using xda premium
Sorry
Sorry I overreacted
The question as posed has no answer.
The stock kernel throttles at 95C and shuts down at 100C
Some dev kernels use lower values than this.
The effect of heat is cumulative, and likewise for the number of temperature cycles.
(The point there is that 5 hrs @ 80C could be worse than 1 hr @ 85C)
In general devices that are heavily used experience reliability failures earlier than lightly used devices, whether they are overclocked or not.
Good luck and enjoy your device - while it lasts.
bftb0 said:
The question as posed has no answer.
The stock kernel throttles at 95C and shuts down at 100C
Some dev kernels use lower values than this.
The effect of heat is cumulative, and likewise for the number of temperature cycles.
(The point there is that 5 hrs @ 80C could be worse than 1 hr @ 85C)
In general devices that are heavily used experience reliability failures earlier than lightly used devices, whether they are overclocked or not.
Good luck and enjoy your device - while it lasts.
Click to expand...
Click to collapse
I actually had a post written out going into this perspective also but decided to not even bother. :laugh: Good on ya though for going through with it. Another spin on it is the affect those high temps have on the hardware and chipsets around, or hovering on top of it. This is why I typically don't overclock my devices for anything other than a run through benchmarks. Also, besides using more battery and generating more heat for a longer duration, typical overclocks rarely produce any significant difference the end user can actually notice on these high end devices anyway. Hell, I don't even notice a difference on my single core Nexus S when OCing from 1ghz to 1.4ghz.
This guide is for people who don't know much about changing kernel settings, etc. Experienced members should leave now.
All flaming will be ignored.
Please, for anyone who will complain that there's no point in disabling everything that makes your smartphone smart, please leave now.
NOTE: Just because I hit 6 hours screen time on average, doesn't guarantee you will. Everyone's phones are different. And how we use them is different too. This is just a thread containing guidelines to help you get the most battery.
Please note that performance may be affected.
Your ROM shouldn't matter too much. But I personally use AXI0M.
Kernel: This matters a lot. I personally use Air Kernel #10, the O2 version. This yields the best battery for me. If you use a different kernel, please don't complain that this guide doesn't have the desired results.
--------------- --------------- --------------- ---------------
All of these settings are optional but will help a lot.
Sync - off.
Screen brightness - 50% or less.
Wifi - on. 3g uses more battery.
NFC - off.
Use 2g networks only - on.
Auto rotate - off.
--------------- --------------- --------------- ---------------
--------------- --------------- --------------- ---------------
These settings, again are optional, but highly recommended. Please don't complain about this guide if you don't use these settings.
Governor: Wheatley
Minimum frequency: 286Mhz
Maximum Frequency: 1.118Ghz
GPU Maximum frequency: 400
Hotplug control/Maximum online CPUs - 2, minimum online CPUs - 1.
Undervolt: This is up to you. Find what is stable for your device. I don't undervolt at all.
All other settings should be left as default.
--------------- --------------- --------------- ---------------
That's it. Give it 2-3 charging cycles or a few days for the settings to settle. And then you should get optimum battery results with minimum effects on your performance.
Sent from my Nexus 4 using xda app-developers app
okmijnlp said:
This guide is for people who don't know much about changing kernel settings, etc. Experienced members should leave now.
All flaming will be ignored.
Please, for anyone who will complain that there's no point in disabling everything that makes your smartphone smart, please leave now.
NOTE: Just because I hit 6 hours screen time on average, doesn't guarantee you will. Everyone's phones are different. And how we use them is different too. This is just a thread containing guidelines to help you get the most battery.
Please note that performance may be affected.
Your ROM shouldn't matter too much. But I personally use AXI0M.
Kernel: This matters a lot. I personally use Air Kernel #10, the O2 version. This yields the best battery for me. If you use a different kernel, please don't complain that this guide doesn't have the desired results.
--------------- --------------- --------------- ---------------
All of these settings are optional but will help a lot.
Sync - off.
Screen brightness - 50% or less.
Wifi - on. 3g uses more battery.
NFC - off.
Use 2g networks only - on.
Auto rotate - off.
--------------- --------------- --------------- ---------------
--------------- --------------- --------------- ---------------
These settings, again are optional, but highly recommended. Please don't complain about this guide if you don't use these settings.
Governor: Wheatley
Minimum frequency: 286Mhz
Maximum Frequency: 1.118Ghz
GPU Maximum frequency: 400
Hotplug control/Maximum online CPUs - 2, minimum online CPUs - 1.
Undervolt: This is up to you. Find what is stable for your device. I don't undervolt at all.
All other settings should be left as default.
--------------- --------------- --------------- ---------------
That's it. Give it 2-3 charging cycles or a few days for the settings to settle. And then you should get optimum battery results with minimum effects on your performance.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
What app do you use to achieve these settings?
Sent from my Nexus 4 using xda premium
adamski123 said:
What app do you use to achieve these settings?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Trickster mod, the free version .
Sent from my Nexus 4 using xda app-developers app
okmijnlp said:
Trickster mod, the free version .
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Basically you are downgrading the performance of the Phone by under-clocking the CPU.
What would be more beneficial is to find a way where we don't have to sacrifice the performance of the phone for Battery life.
Stock rom and faux stock enhanced kernel gives me the best performance and Battery life.
It also helps to hibernate the rouge apps that are constantly waking the phone during deep sleep by using Greeninfy app.
Thanks
okmijnlp said:
(GUIDE) Get 6 hours screen on time.
Click to expand...
Click to collapse
okmijnlp said:
NOTE: Just because I hit 6 hours screen time on average, doesn't guarantee you will.
Click to expand...
Click to collapse
In any case, here's some general guidelines:
- Undervolting, Underclocking, and disabling cores make the device use less power
- Lowering brightness makes the device use less power
- Turning off wireless signals makes the device use less power
- Using lesser signals (2G Cellular, 2.4GHz WiFi) makes the device use less power
- Having higher signal strength makes the device use less processing power, and thus, use less power
Most of that is just common knowledge though, maybe aside from the lesser signals thing. I don't really see anything in this guide as anything significant. It's basically saying "restrict your device's processing power for more battery", which is pretty much true for... anything.
Edit: As for the kernel, I can't think of any significant difference this would make either. Still uses the same drivers and same Linux kernel base, and most kernels have the same optimizations. Only things I can think of that would make a difference is if it came pre-UV'd or implemented a longer WiFi scan interval.
Edit: Somehow I failed to read the very first sentence (or skimmed over it completely, idk)... I should've just left
I never understood the cripple and downgrade your phone for battery thing but whatever floats your boat I guess.
Sent from my Nexus 10
**** yeah, disable two cores and get better battery life. Using airplane mode helps even more
Wow this is awesome! Will try it out
Sent from my GT-N7000 using Tapatalk 2
I can get 4.5 to 5.5 hours of screen on time (browsing, whatsapp, hangouts, some gaming) using auto-brightness, WiFi throughout, and a good signal zone without crippling the phone so such an extent. Getting 6 hours of screen on time is great....but if it isn't doing anything when you're not using it....not sure why you need a smartphone.
Actually, I found the that the phone is still pretty snappy when you turn off two of the cores...I don't think you have to lower all the way to 1.118, maybe 1.3 or 1.25 should be sufficient enough plus some undervolting. Screen brightness more than anything is the biggest factor though IMHO. Hope you guys get some good results.
Brightness alone makes up for almost everyone's battery issues.
-Sent from Marino's Nexus 7-
Honestly do not see the point in disabling everything that makes a smart phone.. well smart.. but I guess it's a good guide for people that just want their phone to last.
can anyone tell me what they are using to test out how stable the phone is when undervolting? What guide lines are there, what is a good indicator that the amount you under volt still leaves stability?
Meh, I've gotten almost 9 hours of screentime. Wifi on all day(no data), GPU: 487, matr1x kernel.
http://forum.xda-developers.com/attachment.php?attachmentid=1906921&d=1366769307
Can't seem to post the image url, so click that link for the screenshot.
Thats the wrong image... I'll post the one with 9 hours when I have time.
desertflame said:
Meh, I've gotten almost 9 hours of screentime. Wifi on all day(no data), GPU: 487, matr1x kernel.
http://forum.xda-developers.com/attachment.php?attachmentid=1906921&d=1366769307
Can't seem to post the image url, so click that link for the screenshot.
Thats the wrong image... I'll post the one with 9 hours when I have time.
Click to expand...
Click to collapse
What were you doing with the phone? Leaving it on a static screen with 10 minutes screen timeout time? Lol.
Just get the Caffeine app and leave your screen on all night while you sleep. Getting high screen on times is easy!
Sent from my Nexus 4 using Tapatalk 2
I personally leave network off, WiFi off, auto brightness
384MHz min, 1.512GHz max, intellidemand, disable mpdecision, 400MHz GPU ondemand, -100mV to all frequencies, and greenify EVERY single app so I don't get a wake lock. I can last over 2 days without charging and getting at least 4 hours of screen. But I mainly just text on my phone and listen to music. No games or much else
Sent from my Nexus 4 using xda app-developers app
Well using airkernelv8.......284mhz-1512mhz....everything one WiFi,2g,facebook,twitter,g+ etc..
Enviado desde mi Nexus 4 usando Tapatalk 2
Airplane mode+low brightness +no wifi+underclocked proc...8hrs plua sot guaranteed :thumbup:
Sent from my Nexus 4 using xda premium