Related
Iv always considered battery life a very important factor in my purchasing of a phone and was one of the big reasons i moved from my Desire HD to the Nexus S (amongst many others). However having been on the android scene for a while im used to tinkering with kernels and roms etc and due to the new battery graph in gingerbread im now able to make direct comparisons rom by rom and kernel by kernel to see how they all differ. This is all shown + explained below.
First id like to explain my method;
I install the rom and kernel with the same apps I always use and charge the phone fully until i am about to go to sleep. I then unplug the phone and leave it in the exactly the same place on my desk with exactly the same settings (sync intervals etc) and i kill all apps before i leave it just to make sure the test is fair.
In the morning i then take a screen shot of the battery life over the period of usually 8 hours and will upload this for you to see. I then look at the over-night battery drain as a comparison on how good battery life is on specific roms and kernels.
Justification - Many of you may be thinking who cares about standby battery life? I care about the battery when im using it!?
Well although that's valid there are many reasons i have taken this approach;
1. It is completely fair i.e. no individual differences such as 'im a heavy user' but we all have different definitions of a 'heavy user'. This is eliminated by the fact the phone is not used and thus the same every time (no individual differences)
2. If a phone has severe battery drain during sleep general knowledge should dictate that battery drain should increase when the screen is on, cpu is working and your syncing your facebook wall, thus a direct correlation with sleep battery drain and usage drain should be apparent.
Therefore i have decided over the next few days/weeks etc i will upload on a regular basis a screenshot of the battery drain over night, along with the battery use details and screen on time etc etc. In addition to the rom and kernel info and i hope that over time this proves to be a very useful thread.
I have been doing this over the last few days on a less strict system and there have been some VERY interesting results which i will upload over the next few days.
(Just a final note iv never really done anything like this on xda before so if its a stupid idea then please tell me now so i dont waste my time doing it, however if people are really interested please let me know and il make sure i do my best!!)
Thanks for reading my extremely long post!
Bratfink
SCREENSHOT 1: This was using modacos custom rom r10 and the kernel that comes with it, i had quite a short sleep (about 6 hours) but the curve pretty much shows what the point im trying to make is. The battery life is great!!
SCREENSHOT 2: This is CM7 Nightly build 27# with Netarchy's latest 1.2.1 kernel and although i didnt use the screen once of charge for a few minutes as you can see once the screen was off battery life barely decreased and was over a long period of time.
If anyone wants me to test specific combos please let me know.
I'm actually looking forward to reading your results.
Sent from my Nexus S using XDA App
Yep, this would actually be pretty useful. Good luck and good work!
i'm a sucker for these types of tests, always love doing them and seeing the results. post soon!
I like others will be keeping an interested eye on your findings.
Uploading pictures of modaco r10 with it's own original kernel today. Its an interesting result!
Sent from my Nexus S using XDA App
Uploaded to OP
I'm interested too.
Can u try modaco r10 with Netarchy 1.2.1 kernel.
bratfink said:
Iv always considered battery life a very important factor in my purchasing of a phone and was one of the big reasons i moved from my Desire HD to the Nexus S (amongst many others). However having been on the android scene for a while im used to tinkering with kernels and roms etc and due to the new battery graph in gingerbread im now able to make direct comparisons rom by rom and kernel by kernel to see how they all differ. This is all shown + explained below.
First id like to explain my method;
I install the rom and kernel with the same apps I always use and charge the phone fully until i am about to go to sleep. I then unplug the phone and leave it in the exactly the same place on my desk with exactly the same settings (sync intervals etc) and i kill all apps before i leave it just to make sure the test is fair.
In the morning i then take a screen shot of the battery life over the period of usually 8 hours and will upload this for you to see. I then look at the over-night battery drain as a comparison on how good battery life is on specific roms and kernels.
Justification - Many of you may be thinking who cares about standby battery life? I care about the battery when im using it!?
Well although that's valid there are many reasons i have taken this approach;
1. It is completely fair i.e. no individual differences such as 'im a heavy user' but we all have different definitions of a 'heavy user'. This is eliminated by the fact the phone is not used and thus the same every time (no individual differences)
2. If a phone has severe battery drain during sleep general knowledge should dictate that battery drain should increase when the screen is on, cpu is working and your syncing your facebook wall, thus a direct correlation with sleep battery drain and usage drain should be apparent.
Therefore i have decided over the next few days/weeks etc i will upload on a regular basis a screenshot of the battery drain over night, along with the battery use details and screen on time etc etc. In addition to the rom and kernel info and i hope that over time this proves to be a very useful thread.
I have been doing this over the last few days on a less strict system and there have been some VERY interesting results which i will upload over the next few days.
(Just a final note iv never really done anything like this on xda before so if its a stupid idea then please tell me now so i dont waste my time doing it, however if people are really interested please let me know and il make sure i do my best!!)
Thanks for reading my extremely long post!
Bratfink
SCREENSHOT 1: This was using modacos custom rom r10 and the kernel that comes with it, i had quite a short sleep (about 6 hours) but the curve pretty much shows what the point im trying to make is. The battery life is great!!
If anyone wants me to test specific combos please let me know.
Click to expand...
Click to collapse
Sent from my Dell Streak using XDA App
I'd be interested in seeing CM7, just whatever nightly build you manage to catch.
I don't think that result will give you precise result.
I found that statistic is wrong sometimes.
It is better to measure using "play video loop".
So, find a movie, set to the same brightness and play in loop?
gogol said:
I don't think that result will give you precise result.
I found that statistic is wrong sometimes.
It is better to measure using "play video loop".
So, find a movie, set to the same brightness and play in loop?
Click to expand...
Click to collapse
Unfortunately that will not give you how well the rom does while it is idle.
I'm really looking forward to your results. My only issue with this phone is the battery life is terrible. I ordered an extended battery off Ebay 3 weeks ago and have yet to receive it. Never ordering anything from Hong Kong again!
Fuse8499 said:
I'm really looking forward to your results. My only issue with this phone is the battery life is terrible. I ordered an extended battery off Ebay 3 weeks ago and have yet to receive it. Never ordering anything from Hong Kong again!
Click to expand...
Click to collapse
What were you using before that you consider this phone to have bad battery life? By far this phone has the best battery life of any Android device I've owned. If you want bad battery life, get an Evo. That is horrific battery life.
bratfink said:
Uploading pictures of modaco r10 with it's own original kernel today. Its an interesting result!
Sent from my Nexus S using XDA App
Uploaded to OP
Click to expand...
Click to collapse
I am looking forward to the rest of these, however just a quick question. What was your battery use like in that situation with the stock ROM? Just for reference, because I'm thinking I might switch to modaco soon. Thanks!
More soon
Iv got a few more screenies but it seems i may have to end this thread prematurely. Its the SNS or 2.3 but idle battery usage for me is pretty much identical no matter what the kernel or rom (il upload a CM7 + Netarchy 1.2.1 shot top op). This was unexpected on my behalf because with my DHD kernels and roms had a big impact on idle battery consumption. I have noticed however that without a full wipe when changing some kernels such as with M r10 idle battery life can increase drastically. I will continue for the next few days and if i dont see any big changes i may move method to a video loop or something of the sort.
Interesting find
I found out something today that may interest may of you. I was messing around with the sleep profiles on SetCpu with netarchys kernel and i found that its better to leave the range from 100-800 than 100-400 or less. This i believe is because when the phone is asleep and carries out a process it will be forced to clock to the maximum of 400mhz and then stay at that speed for 10 seconds, instead of say going up to 800mhz for 1-2 seconds to complete the same process. So a tip to you would be set your profile to 100-800mhz conservative and see what you get!
bratfink said:
I found out something today that may interest may of you. I was messing around with the sleep profiles on SetCpu with netarchys kernel and i found that its better to leave the range from 100-800 than 100-400 or less. This i believe is because when the phone is asleep and carries out a process it will be forced to clock to the maximum of 400mhz and then stay at that speed for 10 seconds, instead of say going up to 800mhz for 1-2 seconds to complete the same process. So a tip to you would be set your profile to 100-800mhz conservative and see what you get!
Click to expand...
Click to collapse
This kinda enforces the point that SetCPU is useless for the NS unless you really want to overclock...
Any battery saving tactics used buy lowering screen off profiles are counteracted by the system process;( So i think in the context of battery life you are probably better to not use SetCPU
JD
bratfink said:
Iv got a few more screenies but it seems i may have to end this thread prematurely. Its the SNS or 2.3 but idle battery usage for me is pretty much identical no matter what the kernel or rom (il upload a CM7 + Netarchy 1.2.1 shot top op). This was unexpected on my behalf because with my DHD kernels and roms had a big impact on idle battery consumption. I have noticed however that without a full wipe when changing some kernels such as with M r10 idle battery life can increase drastically. I will continue for the next few days and if i dont see any big changes i may move method to a video loop or something of the sort.
Click to expand...
Click to collapse
I would definitely move to a video loop or some other 'heavy use' task because when you think about it, not too much can really be changed when almost no power is being used in the first place.
You could also just mention your general feeling for the battery life of each rom, because quite often that is what I go by as my usage varies depending on a range of things (school day or weekend etc) .
Sent from my Nexus S using XDA App
Could you please test modaco r10 with Netarchy's latest 1.2.1 kernel ?
I would love to see the difference between modaco's default kernel vs netarchy's kernel.
On CM nightly 13, I just went 11 hours and I'm at 90%. That's 1/2% an hour. Not bad. That is with stock kernel.
Sent from my Nexus S using Tapatalk
Because of this post and this article I did more digging and playing around with earlier kernels vs. 2.6.38
What I found out is that my phone's battery life almost doubles each time I flash older kernels, based on say, 2.6.37 such as Tiamat 3.3.7.
I've tried most of the most popular 2.6.38 based kernels out there, such as Tiamat, Savaged-Zen, TigerBlood, GoDmOdE - my battery lasts significantly less with all of them comparing to pre 2.6.38 kernels. I should mention I have not changed any settings, in between kernel trials, not a damn thing and I tested it without doing any overclocking.
Devs and Android users beware.
http://forum.xda-developers.com/showthread.php?t=695878
DomSim said:
http://forum.xda-developers.com/showthread.php?t=695878
Click to expand...
Click to collapse
this is not Q&A. This is important info for kernel and ROM devs to take into account, when they decide on direction of future developement endeavors
This is not development, you are not introducing a Rom or kernel, you are commenting on results from personal testing, essentially asking " why does this thing do what it do?"
NewZJ said:
This is not development, you are not introducing a Rom or kernel, you are commenting on results from personal testing, in essence asking " why does this thing do what it do?)
Click to expand...
Click to collapse
If the mods think it doesn't belong here they'll move it. Personally, I think this needs to have high visibility and needs to be sticky topic.
Moved to General, ill gladly move back when it has some factual data .(as in numerical, comparisons ect)
I'd have to agree with the OP. Im at work from 9-5 mon-fri and I do alot of kernel testing. The 3.3.7 tiamat and earlier savage zen kernels give way better battery life than the newer 2.6.38 based kernels. I also feel like my battery and performance is better using .37 kernels and its funny you brought this up!
For what it's worth, pretty much each revision of Tiamat (and possibly other kernels) are less and less undervolted, which may affect things to an extent. I'm not saying that's the sole source of decreased battery life, but it's a factor nonetheless.
that is true of sz. Blaim all the complaining people... and very picky evos.
jug6ernaut said:
Moved to General, ill gladly move back when it has some factual data .(as in numerical, comparisons ect)
Click to expand...
Click to collapse
Numeric comparisons between different kernels might upset the kernel devs, whose battery "benchmarks" in my testing are lower. I feel it wouldn't be fair thing to do
Also, it's pretty hard to provide objective numeric data, because battery drain heavily depends on the type of usage, and even though my day-to-day usage is similar, its not quite the same, so those numbers would not be accurate.
If it helps - I get ~17 hours of moderate usage with 2.6.37 or earlier kernels and I'm lucky if I can squeeze 9 hours with the same usage out of 2.6.38. And that info is more or less accurate for ALL 2.6.38 kernels across the board.
Consider this: if toastcfh, the rest of TeamWin gang, Cayniarb, Savaged-Zen crew and other devs miss this info because the thread was moved - it'll be our loss...
Aren't these kernels meant for 2.3.4?
midget tossing is habit...2010 midwest regional champion... hw 001
Apo11on said:
Numeric comparisons between different kernels might upset the kernel devs, whose battery "benchmarks" in my testing are lower. I feel it wouldn't be fair thing to do
Also, it's pretty hard to provide objective numeric data, because battery drain heavily depends on the type of usage, and even though my day-to-day usage is similar, its not quite the same, so those numbers would not be accurate.
If it helps - I get ~17 hours of moderate usage with 2.6.37 or earlier kernels and I'm lucky if I can squeeze 9 hours with the same usage out of 2.6.38. And that info is more or less accurate for ALL 2.6.38 kernels across the board.
Consider this: if toastcfh, the rest of TeamWin gang, Cayniarb, Savaged-Zen crew and other devs miss this info because the thread was moved - it'll be our loss...
Click to expand...
Click to collapse
so you know more about these kernels than these developers who rip them apart and rebuild them from scratch huh? and your gonna teach em all something right? sheesh...
Great thread, this is the type of stuff I like to know about. I am going to run a few short tests on Tiamat 4.0.2 and Tiamat 3.3.8 and see how noticeable the power consumption is between the two.
I call BS. To test properly.. you would need to wipe battery stats and calibrate between kernels. Then give it a couple days to settle. Also... there is no way to ever have the usage be the same if your actually using the phone. You would need to turn the radios off so that the service you are getting is equal. A whole bunch of other things too.. so basically you would need to not use it as a phone to test the kernel right.
Oh yeah, and also use the same under volt.
Sent from my PC36100 using XDA Premium App
I ran a 5 minute idle test with Tiamat 3.3.8 and 4.0.2 with all radios turn on and governor set to performance. The power consumption was logged by PowerTutor.
I parsed each log to pull the total-power measurements and then averaged the middle 25% of the measurements to ensure they were from the phone's true idle state.
Tiamat 4.0.2 - 52mW
Tiamat 3.3.8 - 53mW
So essentially they are almost identical. Of course the 4.0.2 does have lower voltages in HAVS and the radios were on, so there could be room for improvement on these measurements.
Bottom line....even if 2.6.38 uses more power, you shouldn't even notice a difference between the two, due to HAVS voltage differences between these two kernels.
Redid the test with all radios turned off. Essentially these are CPU only readings. The power difference still seems rather moot. It could be a different story under intense CPU utilization though if the percentage difference scaled. I'll leave that to someone else though. Also, remember that these numbers are in no way entirely accurate...there is going to be a +/- deviation in any power consumption measurements unless it is done in a truly controlled environment.
Tiamat 4.0.2 - 5mW
Tiamat 3.3.8 - 2mW
aimbdd said:
I call BS. To test properly.. you would need to wipe battery stats and calibrate between kernels. Then give it a couple days to settle. Also... there is no way to ever have the usage be the same if your actually using the phone. You would need to turn the radios off so that the service you are getting is equal. A whole bunch of other things too.. so basically you would need to not use it as a phone to test the kernel right.
Oh yeah, and also use the same under volt.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
I did recalibrate battery for each new kernel...I put a couple of weeks of hard work into this and I started well before I saw that phoronix article because I knew something is up. I'm sorry if this is not good enough "proper testing" for you. If you chose to be ignorant and pretend the issue doesn't exist - its your decision of course, but many others would want to know.
As per your advice to turn off the radios - what if the power hog regression in 2.6.38 is related to one of them?
The power regression was solved by phoronix last week.
http://phoronix.com/scan.php?page=article&item=linux_2638_aspm&num=1
Basically, active state power management isn't being used properly. There needs to be modifications based around the parameter "pcie_aspm=force". An example in a different kernel git is below:
http://android-x86.tarot.com.tw/?p=...ff;h=d6d385743463f38a0da899cd4607e526ad9a049f
With this fix on my laptop (applied to GRUB), I saw an increase in battery life of 27%.
LifeInTheGrey said:
The power regression was solved by phoronix last week.
http://phoronix.com/scan.php?page=article&item=linux_2638_aspm&num=1
Basically, active state power management isn't being used properly. There needs to be modifications based around the parameter "pcie_aspm=force". An example in a different kernel git is below:
http://android-x86.tarot.com.tw/?p=...ff;h=d6d385743463f38a0da899cd4607e526ad9a049f
With this fix on my laptop (applied to GRUB), I saw an increase in battery life of 27%.
Click to expand...
Click to collapse
So in other words, the OP was right even though people doubted him?
Not surprised.
Hopefully the devs are aware of this and can incorporate it into their kernels.
mattykinsx said:
So in other words, the OP was right even though people doubted him?
Not surprised.
Hopefully the devs are aware of this and can incorporate it into their kernels.
Click to expand...
Click to collapse
+1
Bump
10char
So since I had my nexus 4, I had to complain about its terrible battery life.
I would never get more than 3h of screen on time, despite my best efforts in conserving battery. Even with the phone in flight mode and on Wifi, I could not cross 3h give or take a few minutes. I even tried disabling location, google now, sync and everything else.
It was deep-sleeping nice, while the screen was off, standby time was awesome for me. If I turned it on though, it started to burn through battery insanely quick. So I started monitoring the frequency states with battery spy, and noticed that as if there was a little load, it spiked to 1026MHz and then stayed there for about three seconds every time before falling back to 386 MHz. So I tried setting the max cpufreq to 916Mhz with CPU tuner, and was astonished to find out, that immediately after the load was done, it went back to the lowest frequency. Like it should be, not hanging for multiple seconds on the high step.
Also, If I start CPU tuner, the min freq is always shown as 1026MHz. So I changed min to 386 and max to 916. Afterwards, this stays until I swipe cpu tuner away from the recent apps list. If I start it again, the settings revert. Strange...
With my cpu limited to 916MHz, I get about 5h and 50 min of screen on time without any other measures. Location on, Wifi on, Google now and sync all active. If I just go one step higher and set my max frequency to 1026, the old behavior starts again, and screen time drops to 3h because it seems to be stuck on that freq. Therefore I would like everybody who also has bad screen time to try that out and report back.
I don't really understand why it would take so long to drop back from the 1GHz step, and drop back immediately from the 0,9GHz step?
Of course, this is with normal surfing via chrome, or using normal apps that are not that much CPU intensive. Also, you hardly notice the performance limitation without playing games. There probably is an easy way to fix this?
Feedback would be appreciated. Maybe I see this wrong...
Thanks
tl;dr : if screen on, for me only 1026mhz is used, if max freq is set to anything lower, the phone spends most of the time at the lowest step 386mhz, greatly increasing screen time for me.
Flash Franco Kernel and buy the app and you'll be set.
Sent from my Nexus 4 using xda app-developers app
NoLunchBox_ said:
Flash Franco Kernel and buy the app and you'll be set.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Maybe, but I really first wanted to examine out of the box behavior
This is caused by qualcoms Mpdecision which ramps up the cpu to 1ghz on screen on and touches. All in the name of speed. It's basically a hot plugging technique such that smoothness is guaranteed under loaded gui transitions and scrolling. Before this you would have to wait for the cpu to be loaded for it to ramp up speed. Now the OS can demand speed.
You can see in Franco kernel he replaced Mpdecision with an open source alternative and swapped the lowest cpu speed to 368mhz. Then added a load step of 768mhz (for 60% loads). This actually added a bit of lag but should be better in the battery department. Some more tweaking to be done though.
Qualcoms thermald is what is causing thermal throttling.
Edit: this could be wrong. But I think I'm in the general area of what's going on...
Sent from my Nexus 4 using xda premium
This does sound logical, but why the hell waste nearly half of the possible screen time on "perfect smoothness" when even if limited to 0,9ghz everything runs pretty amazing... I will look into francos kernel, even though I dont like to buy an app to tune it,
ArRaY92 said:
This does sound logical, but why the hell waste nearly half of the possible screen time on "perfect smoothness" when even if limited to 0,9ghz everything runs pretty amazing... I will look into francos kernel, even though I dont like to buy an app to tune it,
Click to expand...
Click to collapse
You don't have to buy an app, everything can be set through scripts. The app just automates the process, allows you to back up kernels, download the latest nightly and milestone (when one becomes available). It's really worth the investment, plus you're helping out a great Dev who has shared his awesome work with us for a long time.
Sent from my Nexus 4 using Tapatalk 2
I like my phone to sleep. I bumped it down to 384!
No need to keep it @ the 1.026, it will pretty much kill battery! Makes no sense to me.
Sent from my Nexus 4 using Tapatalk 2
You can set the max to 384 mhz.. and still everything is smooth
Can I use SetCPU or is that app defunt now? And to change my CPU speeds can that be done on a phone that's simply rooted or do I need a custom kernel?
EDIT: I downloaded CPU tuner, but I'm not sure if it's working or not. Does it work w/ stock kernel or no?
Faux's Intellidemand fixes pretty much what you're describing. Since mpdecision is not used instead of fauxs alternative.
Sent from my Nexus 4
What is max frequency by default?
Have to say firstly, that the perfect smoothness of this phone is what has sold me on it as the camera is well below average, it has some bugs and the output quality and volume of the audio is shocking, but it is the single smoothest phone out there.
Get rid of what I came to know as Touchboost (feature brought in in jelly bean to introduce the lag free experience of project butter I imagine) from my Sgs3 days, and the phone becomes as laggy as every other android phone out there.
Secondly, I get around 3.5 hours screen on time, without messing about, wifi on constant, depending on whether i'm on the net or not, I can get more.
I find AOKP perfect as its super fast and battery is excellent.
Franko kernel works, but the phone then feels choppy. Setting the cores to 1ghz makes the phone laggy also.
All I can say is, get lots of chargers, I have two at home, two at work, one in the car, one at the other halfs, and it's trickle charging when and if I can and I never worry about battery anyway. I find it wastes far too much life.
Good luck.
biffsmash said:
Have to say firstly, that the perfect smoothness of this phone is what has sold me on it as the camera is well below average, it has some bugs and the output quality and volume of the audio is shocking, but it is the single smoothest phone out there.
Get rid of what I came to know as Touchboost (feature brought in in jelly bean to introduce the lag free experience of project butter I imagine) from my Sgs3 days, and the phone becomes as laggy as every other android phone out there.
Secondly, I get around 3.5 hours screen on time, without messing about, wifi on constant, depending on whether i'm on the net or not, I can get more.
I find AOKP perfect as its super fast and battery is excellent.
Franko kernel works, but the phone then feels choppy. Setting the cores to 1ghz makes the phone laggy also.
All I can say is, get lots of chargers, I have two at home, two at work, one in the car, one at the other halfs, and it's trickle charging when and if I can and I never worry about battery anyway. I find it wastes far too much life.
Good luck.
Click to expand...
Click to collapse
Thank you for not contributing to this thread with that useless comment. The rest of us may not want to charge the phone 1500 times a day (or are even able to), and are looking for ways to help battery discharge go slower while using the phone. If you're fine with charging your phone nonstop, then what are you doing in this thread? Everyone knows you can buy many chargers, that's not a solution.
ksc6000 said:
Thank you for not contributing to this thread with that useless comment. The rest of us may not want to charge the phone 1500 times a day (or are even able to), and are looking for ways to help battery discharge go slower while using the phone. If you're fine with charging your phone nonstop, then what are you doing in this thread? Everyone knows you can buy many chargers, that's not a solution.
Click to expand...
Click to collapse
Welcome to Project Butter. If you want to do something different than Google's goals for UI smoothness and responsiveness, which is what everyone has been complaining about in Android vs iOS, then you'll have to go the custom ROM/kernel route. Thankfully that is easily available to you on this hardware and software platform. Me? I like the N4 just fine the way it is stock.
[hfm] said:
Welcome to Project Butter. If you want to do something different than Google's goals for UI smoothness and responsiveness, which is what everyone has been complaining about in Android vs iOS, then you'll have to go the custom ROM/kernel route. Thankfully that is easily available to you on this hardware and software platform. Me? I like the N4 just fine the way it is stock.
Click to expand...
Click to collapse
Dude, this has nothing to do with googles project, but instead with Qualcomms responsivness "fix". Please read the answer to my inital post, and you will understand. Also, the phone does in no way feel choppy if you restict it to .9ghz. Except if you load it so much, that it cant cope with this max frequency. But then again, this is not the issue, but the issue is, that 1026 stays active for to long, so that it burns through your battery. There would be only a small change needed to change this behavior, and "possibly" loosing about a fraction of a second of responsivness, that most of the time you wouldnt even notice... Everybody who tells me he is happy with barely 3h of screen time or even less is just the android equivalent of an isheep, because this is in no way acceptable.
ArRaY92 said:
Dude, this has nothing to do with googles project, but instead with Qualcomms responsivness "fix". Please read the answer to my inital post, and you will understand. Also, the phone does in no way feel choppy if you restict it to .9ghz. Except if you load it so much, that it cant cope with this max frequency. But then again, this is not the issue, but the issue is, that 1026 stays active for to long, so that it burns through your battery. There would be only a small change needed to change this behavior, and "possibly" loosing about a fraction of a second of responsivness, that most of the time you wouldnt even notice... Everybody who tells me he is happy with barely 3h of screen time or even less is just the android equivalent of an isheep, because this is in no way acceptable.
Click to expand...
Click to collapse
I'm getting around 4-5. Auto brightness, 1 Gmail push, 1 touchdown push, Google now on, HD widgets weather, greader pro syncing, falcon pro syncing, all location services on (I like the monthly reports). Wi-Fi when I can.
[hfm] said:
I'm getting around 4-5. Auto brightness, 1 Gmail push, 1 touchdown push, Google now on, HD widgets weather, greader pro syncing, falcon pro syncing, all location services on (I like the monthly reports). Wi-Fi when I can.
Click to expand...
Click to collapse
What kernel are u using? Im using franco kernel + latest CM 10.1 nightly.
My min CPU speed is 1 GHz and in still getting 4 hours on screen time though. I don't think setting my min at 384 MHz even made much difference in my battery, will try it again soon.
Sent from my Nexus 4 using xda premium
droyd4life said:
What kernel are u using? Im using franco kernel + latest CM 10.1 nightly.
Click to expand...
Click to collapse
Stock never rooted bootloader still locked.
If you are getting bad battery... simply flash a custom kernel. You get to keep your stock ROM or whatever but you will get substantial benefits. I prefer Trinity Kernel. Only the second or third update on this kernel and now the phone has made huge gains in battery life. Like hfm, I good on screen time... usually 5-5.5. I have auto brightness on, mobile on 100% of the time, and all Google services synced including books, gmail, currents, google now, etc etc. I have locations on, gps on... everything. Sometimes I turn off NFC because I rarely am somewhere where I can use those cool RFID card scanners. What sucks battery is probably a problem in Android 4.2. The phone does not sleep as much as it should. Go ahead and turn all your sync stuff off and keep the screen on static and let the battery die at stock clock speeds. Probably will get at least 5 hours with auto-brightness on. My phone probably sleeps 60% of the time now according to CPU spy when it sits idle in my car for my 8-10 hour work day. I usually get to the car with a bunch of emails, a text or two waiting for me, and the phone has only been asleep the aforementioned 60% and around 90-91% battery life. On a new phone, starting from full charge, this should be at least 95%. My N10 that doesn't have mobile data, only loses about 1% overnight. Apples to oranges but still. I'm convinced that stock voltages on this device are too high, and that Qualcomm did not give Google the latest drivers... maybe because it's not releasable to AOSP as of yet. I really don't know, but it's gotta be something buggy. This SoC is capable of doing better... and it does in the Optimus G and even with sense, 1080p screen, and a 100mah smaller battery the HTC Droid DNA/Butterfly gets 3.5-4 hours stock screen time. None of the other phones using the S4 Pro are running 4.2. I'm hoping either Qualcomm pulls a Samsung and releases some updated drivers/firmware that Google can incorporate or that Google fixes whatever bugs they may have not worked out. In the next calendar year other phones will be out that use the S4 Pro and 4.2 and I doubt Qualcomm wants to lose the luster it earned with the regular S4 Kraits performance/efficiency. When 4.2 comes to other devices we will probably know whether or not Google is to blame for this or that the Nexus 4 is just a poor performer.
I am considering purchasing a moto x pure edition because it can move to any carrier. This is the main reason I was considering this phone. The second and equally important reason is battery life. My current phone is a galaxy s4 active. The battery doesn't get me through the day at work (10 hours) with moderate use (4 hours screen time). This has annoyed me greatly. Unfortunately, I cannot have it charging at work so the phone needs to make it with ease through the day. I do not have wifi available so all activity will be through 4glte with 3/5 signal. I realize one of the complaints with the phone is battery life. My question is, if I root/unlock bl (which I do with every device), are there kernels that anyone here is running that can undervolt and get me that all day battery life out of this thing? I really don't want to buy it and be back in the same boat again. Unfortunately, the gs4a i had was never boot loader unlocked so i'm stuck on crappy touchwiz with stock kernel. It performs fine but battery life stinks. If I buy this phone, will i be dissapointed? Thanks to everyone for your responses.
thejase said:
I am considering purchasing a moto x pure edition because it can move to any carrier. This is the main reason I was considering this phone. The second and equally important reason is battery life. My current phone is a galaxy s4 active. The battery doesn't get me through the day at work (10 hours) with moderate use (4 hours screen time). This has annoyed me greatly. Unfortunately, I cannot have it charging at work so the phone needs to make it with ease through the day. I do not have wifi available so all activity will be through 4glte with 3/5 signal. I realize one of the complaints with the phone is battery life. My question is, if I root/unlock bl (which I do with every device), are there kernels that anyone here is running that can undervolt and get me that all day battery life out of this thing? I really don't want to buy it and be back in the same boat again. Unfortunately, the gs4a i had was never boot loader unlocked so i'm stuck on crappy touchwiz with stock kernel. It performs fine but battery life stinks. If I buy this phone, will i be dissapointed? Thanks to everyone for your responses.
Click to expand...
Click to collapse
You shouldn't have any problem hitting 4hrs SOT in 10 hours off the charger. I never have to charge this thing at work. I leave the house at 5am and don't plug it in until about 9pm.
thejase said:
I am considering purchasing a moto x pure edition because it can move to any carrier. This is the main reason I was considering this phone. The second and equally important reason is battery life. My current phone is a galaxy s4 active. The battery doesn't get me through the day at work (10 hours) with moderate use (4 hours screen time). This has annoyed me greatly. Unfortunately, I cannot have it charging at work so the phone needs to make it with ease through the day. I do not have wifi available so all activity will be through 4glte with 3/5 signal. I realize one of the complaints with the phone is battery life. My question is, if I root/unlock bl (which I do with every device), are there kernels that anyone here is running that can undervolt and get me that all day battery life out of this thing? I really don't want to buy it and be back in the same boat again. Unfortunately, the gs4a i had was never boot loader unlocked so i'm stuck on crappy touchwiz with stock kernel. It performs fine but battery life stinks. If I buy this phone, will i be dissapointed? Thanks to everyone for your responses.
Click to expand...
Click to collapse
I just got my moto x pure two days ago. I came from using an S4 active which I still have. The turbo charing helps with the moto x. I'm still getting use to setting up my moto x the way I want it. You learn from trial and error. The main thing for me is that I want to make sure I can return to stock regardless of what happens to my phone.
brholt6 said:
You shouldn't have any problem hitting 4hrs SOT in 10 hours off the charger. I never have to charge this thing at work. I leave the house at 5am and don't plug it in until about 9pm.
Click to expand...
Click to collapse
Thanks so much for the reply! This is exactly the info I'm looking for. Some questions though, how much are you on in it and how much are you using wifi during that time? Also, are you on a custom kernel/rom?
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
dkeepitabuck said:
I just got my moto x pure two days ago. I came from using an S4 active which I still have. The turbo charing helps with the moto x. I'm still getting use to setting up my moto x the way I want it. You learn from trial and error. The main thing for me is that I want to make sure I can return to stock regardless of what happens to my phone.
Click to expand...
Click to collapse
The charger is a good point at home but I can't have it at work, unfortunately.
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
thejase said:
Thanks so much for the reply! This is exactly the info I'm looking for. Some questions though, how much are you on in it and how much are you using wifi during that time? Also, are you on a custom kernel/rom?
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
Click to expand...
Click to collapse
I range from 3-5 hours of screen on time depending on my usage. If I'm at the 3 hr end, then I usually make it off the charger from 5am-9pm range with a bit of life left. If I'm at the 5 hr end I'll have to charge a decent amount sooner (maybe 5am-6pm) but it's still a full day's use. I've run completely stock and I've tried a few different Roms and Kernels...I've never seen a huge difference in battery life though.
5 hs.of SOT, 12 hs without a charger ( not in the first week of use) you need a minimal of 5 charge/discharge cycles
Its a excellent phone !! (sorry for my english)
Enviado desde mi XT1575 mediante Tapatalk
Altomugriento said:
5 hs.of SOT, 12 hs without a charger ( not in the first week of use) you need a minimal of 5 charge/discharge cycles
Its a excellent phone !! (sorry for my english)
Enviado desde mi XT1575 mediante Tapatalk
Click to expand...
Click to collapse
This is good to know but I will be purchasing it used so the cycles will be there already.
thejase said:
This is good to know but I will be purchasing it used so the cycles will be there already.
Click to expand...
Click to collapse
Think about this advice if you change the ROM.
Enviado desde mi XT1575 mediante Tapatalk
thejase said:
I am considering purchasing a moto x pure edition because it can move to any carrier. This is the main reason I was considering this phone. The second and equally important reason is battery life. My current phone is a galaxy s4 active. The battery doesn't get me through the day at work (10 hours) with moderate use (4 hours screen time). This has annoyed me greatly. Unfortunately, I cannot have it charging at work so the phone needs to make it with ease through the day. I do not have wifi available so all activity will be through 4glte with 3/5 signal. I realize one of the complaints with the phone is battery life. My question is, if I root/unlock bl (which I do with every device), are there kernels that anyone here is running that can undervolt and get me that all day battery life out of this thing? I really don't want to buy it and be back in the same boat again. Unfortunately, the gs4a i had was never boot loader unlocked so i'm stuck on crappy touchwiz with stock kernel. It performs fine but battery life stinks. If I buy this phone, will i be dissapointed? Thanks to everyone for your responses.
Click to expand...
Click to collapse
I just got my Moto XPE too. Battery life was one of my biggest concerns. I came from a moto e (that little thing had ridiculous battery life). I was worried because of all the complaints of short battery life but I can tell you this:
When I first used the phone (no root, mods, out anything) I got around 4 hours sot pretty easily. That's a little short for me but it isn't terrible. The phone got really warm though and I felt as if it was unoptimized and the CPU was doing more work than it needed to.
I proceeded to void my warranty and unlock the bootloader. First I did a little research on these big.LITTLE cpus then i used a (well pretty much the only established one) custom kernel, Frankenclark, to do a little tweaking.
All I did was turn touchboost off and make the lowest CPU frequency one step lower, as well as turning hotplug to where the screen on minimum CPU count is 1. There was basically no loss in performance and it doesn't even get as much as warm now. I can't give you stats on the long term battery life yet but in the time that I wrote this I only lost 2% ( I type slow ).
Before both the big and LITTLE CPU clusters were showing on and pretty much going crazy all the time. Now the big cluster is hardly ever on. The phone by default has touchboost set to turn on cpu1 (which is one of 2 cores in the big cluster) every time you touch the screen, which is very wasteful. (At least that's how it was with this kernel, I'm pretty sure stock did the same thing) I'm currently running TruPureX ROM (stock debloated) but I doubt it gives any battery life improvements. Motorola made a good stock rom. I really like this phone. Good luck with your purchase! PS the Nexus 6p has generally better battery life if you can live with no sdcard and the steeper price. The 6p can also move between carriers as the XPE can. Verizon included which is what I use.
[Edit]
When you put this thing down, you can expect to pick it back up with the same battery % left. Standby is ridiculous, which is nice.
^^Does your screen on setting of 1 cpu stick? On mine with kernel editor it reverts back to 2 after a reboot.
elite001mm said:
I just got my Moto XPE too. Battery life was one of my biggest concerns. I came from a moto e (that little thing had ridiculous battery life). I was worried because of all the complaints of short battery life but I can tell you this:
When I first used the phone (no root, mods, out anything) I got around 4 hours sot pretty easily. That's a little short for me but it isn't terrible. The phone got really warm though and I felt as if it was unoptimized and the CPU was doing more work than it needed to.
I proceeded to void my warranty and unlock the bootloader. First I did a little research on these big.LITTLE cpus then i used a (well pretty much the only established one) custom kernel, Frankenclark, to do a little tweaking.
All I did was turn touchboost off and make the lowest CPU frequency one step lower, as well as turning hotplug to where the screen on minimum CPU count is 1. There was basically no loss in performance and it doesn't even get as much as warm now. I can't give you stats on the long term battery life yet but in the time that I wrote this I only lost 2% ( I type slow ).
Before both the big and LITTLE CPU clusters were showing on and pretty much going crazy all the time. Now the big cluster is hardly ever on. The phone by default has touchboost set to turn on cpu1 (which is one of 2 cores in the big cluster) every time you touch the screen, which is very wasteful. (At least that's how it was with this kernel, I'm pretty sure stock did the same thing) I'm currently running TruPureX ROM (stock debloated) but I doubt it gives any battery life improvements. Motorola made a good stock rom. I really like this phone. Good luck with your purchase! PS the Nexus 6p has generally better battery life if you can live with no sdcard and the steeper price. The 6p can also move between carriers as the XPE can. Verizon included which is what I use.
[Edit]
When you put this thing down, you can expect to pick it back up with the same battery % left. Standby is ridiculous, which is nice.
Click to expand...
Click to collapse
This is incredible information! Thank you! Unfortunately, the 6p is just out of my price range.
gpz1100 said:
^^Does your screen on setting of 1 cpu stick? On mine with kernel editor it reverts back to 2 after a reboot.
Click to expand...
Click to collapse
I think I remember it's a bug where it will stick if the screen is on while kernel adiutor is restoring the settings but it will revert to 2 cores if the screen is off while it's restoring. Don't quote me on it but I think that's what it was.
---------- Post added at 02:08 AM ---------- Previous post was at 02:06 AM ----------
thejase said:
This is incredible information! Thank you! Unfortunately, the 6p is just out of my price range.
Click to expand...
Click to collapse
It was mine too. I got the 64GB MXP for the same price as the 16GB on amazon and I couldn't resist. It's nice to have an SDcard too :good:
elite001mm said:
I think I remember it's a bug where it will stick if the screen is on while kernel adiutor is restoring the settings but it will revert to 2 cores if the screen is off while it's restoring. Don't quote me on it but I think that's what it was.
Click to expand...
Click to collapse
If I set it 1 6 1 (min screen on cores: 1, max cores : 6, max screen off cores 1), the phone will reboot if I don't allow kernel auditor to apply the settings while screen is still on (after a reboot). That is, after phone reboots, if screen goes blank, when I hit the power button, phone will reboot on its own.
Probably not a major issue considering I only reboot about once every week or two. I can make sure I watch the cycle and unlock it, wait for everything to settle, then turn off the screen.
Guess what I just got? someone on eBay was selling the 64gb for 300 bucks in mint condition! Just can't beat it. Thanks to everyone for info and suggestions along the way. Any recommendations on cases and screen protectors? I've always like seidio for cases and whatever is highly rated on @maz0n for screen protectors but any advice would be appreciated!
I have seidio case and holster, I think they only sell one for it, and I love it.
Sent from my XT1575 using Tapatalk
Ultimately I wound up getting a vena vskin that's see through. I really love it. Only problem is the back is curved life the phone so using it on a table with one hand swiping for SwiftKey makes it spin.
Sent from my XT1575 using XDA Free mobile app
Either i'm not looking hard enough, or i'm just not finding any decent guides on in-depth tweaking in kernels, what does what (with examples, because a lot of the time, only certain types of people can grasp what an explanation of a setting or value does), whether certain groups of values are synergetic (changing one value can have an effect on another value, good or bad; not using 1 setting when another setting is active), stuff like that. I took screenshots of everything in EXKM, except for the governor parameters, i didn't change what the kernel has for defaults with the Wheatley governor.
GWARslave119 said:
Either i'm not looking hard enough, or i'm just not finding any decent guides on in-depth tweaking in kernels, what does what (with examples, because a lot of the time, only certain types of people can grasp what an explanation of a setting or value does), whether certain groups of values are synergetic (changing one value can have an effect on another value, good or bad; not using 1 setting when another setting is active), stuff like that. I took screenshots of everything in EXKM, except for the governor parameters, i didn't change what the kernel has for defaults with the Wheatley governor.
Click to expand...
Click to collapse
Well, you definitely have the right program, I used to think Kernel Adiutor was the best kernel tweaker of all times, so I bought it, with no additional benefit
Not long ago or yesterday, ( Lol ) I finally decided to spend a few dollars and buy Ex Kernel Manager, its very satisfying to use with its beautiful design and extensive features. One awesome feature of EXKM is the ability to save your profile to widgets so you can quickly change to a saved profile for balance, battery or speed.
Because my original X727 suffered from chip death early last month, I am hesitant to use overclocking and probably never will again. Honestly, the phone is still extremely fast when underclocking and the battery life is amazing.
Below are a couple of screenshots. Maybe later, when I have time I will make an extensive post with all of the small details or better yet someone else does it.
tsongming said:
Well, you definitely have the right program, I used to think Kernel Adiutor was the best kernel tweaker of all times, so I bought it, with no additional benefit
Not long ago or yesterday, ( Lol ) I finally decided to spend a few dollars and buy Ex Kernel Manager, its very satisfying to use with its beautiful design and extensive features. One awesome feature of EXKM is the ability to save your profile to widgets so you can quickly change to a saved profile for balance, battery or speed.
Because my original X727 suffered from chip death early last month, I am hesitant to use overclocking and probably never will again. Honestly, the phone is still extremely fast when underclocking and the battery life is amazing.
Below are a couple of screenshots. Maybe later, when I have time I will make an extensive post with all of the small details or better yet someone else does it.
Click to expand...
Click to collapse
lol my battery life is half of yours ;p And how exactly where u overclocking it, by changing the voltages? And yeah it's a fast phone for the money, I haven't found a game yet that it doesn't run smoothly on..
A couple things I've been noticing lately, one is fast charge hasn't been working lately even when selected. Not sure if it's the cable or the rom or what. And also I've noticed the charge times change when I flip over the usb-c connector when plugging it in..again i dunno if thats cause of the cable or if usb-c is meant to be that way
GWARslave119 said:
lol my battery life is half of yours ;p And how exactly where u overclocking it, by changing the voltages? And yeah it's a fast phone for the money, I haven't found a game yet that it doesn't run smoothly on..
A couple things I've been noticing lately, one is fast charge hasn't been working lately even when selected. Not sure if it's the cable or the rom or what. And also I've noticed the charge times change when I flip over the usb-c connector when plugging it in..again i dunno if thats cause of the cable or if usb-c is meant to be that way
Click to expand...
Click to collapse
The charge speed is not static, it fluctuates otherwise it will shorten the life of the battery. The speed can be improved upon by switching the kernel. For example, Black Screen 5.4 uses the higher rate charging, it also allows you to change voltage frequencies, which I don't recommend. I fried my old X727 early last month, by simply restoring Google settings..
If you are using the stock Leeco cable, get rid of it and but an Anker cable instead. Some of the stock cables were really bad quality and quite a few people burned their ports due to faulty cables.
Concerning battery life, Right now AICP 14 has the best battery life.
It also has the new perf profiles extracted from EUI. It is my understanding (?) that this was extracted and made compatible by Max 2 developer : shivatejapeddi.
He made a comment on telegram stating that he may build a flashable zip for Zl1 that could be flashed on any rom to improve the battery life.
Lets hope, that would be awesome.
tsongming said:
The charge speed is not static, it fluctuates otherwise it will shorten the life of the battery. The speed can be improved upon by switching the kernel. For example, Black Screen 5.4 uses the higher rate charging, it also allows you to change voltage frequencies, which I don't recommend. I fried my old X727 early last month, by simply restoring Google settings..
If you are using the stock Leeco cable, get rid of it and but an Anker cable instead. Some of the stock cables were really bad quality and quite a few people burned their ports due to faulty cables.
Concerning battery life, Right now AICP 14 has the best battery life.
It also has the new perf profiles extracted from EUI. It is my understanding (?) that this was extracted and made compatible by Max 2 developer : shivatejapeddi.
He made a comment on telegram stating that he may build a flashable zip for Zl1 that could be flashed on any rom to improve the battery life.
Lets hope, that would be awesome.
Click to expand...
Click to collapse
Sorry, been too distracted to reply ha. Yeah I don't mess with the voltage frequencies, just try different governors and whatnot...I don't mess with the governor settings much since somet imes it's hard for me to notice any difference , unless it's a huge one. Basically it's jsut me trying to put aside time to focus and I haven't made time, it's all jumbled with other things i do ;p
Actually I lie, I did notice what seemed to me as odd on a few things... i'll toss screenshots. What I dont get is the first boost duration under the CPU Boost at 0... also, the boost frequency, is the mhz it boosts to, or an addon amount.. and just the boost in general, input boost vs touchboost...? next there's the online core count.., max cores online for litl and big make sense, 2 each. Min core online 1, max cores online...2? with an up and down threshold of 0...how does 0 work in this case? NExt is arch_power and wq_power_saving, i've tried looking them up and couldn't find much, so not sure what they doe xactly and what it would hurt/hinder...
Zram, does it hurt to have it on and at full, 2096mb? Just as an extra ceiling, in case I do use all my 6gb, or does having it on but not using it constantly affect anything.. the TCP algorithm i've scoured and couldn't find anything about which ones are good for what types of networks, maybe only a couple of them, so i usually don't play with that since to me it'd be hard to test because of the fluxuation.
Ok that was more than I thought I'd throw out, sorry ;p There's lots more probably, but I don't need to overload mine or yours' head right now ;p
oh.. i was wondering if i posted this or not lol... wasnt sure if the draft had gotten lost or what.. anyways, i was just now going to take screenshots when i rememebred, you can just use the ones from my origianl post ha
GWARslave119 said:
oh.. i was wondering if i posted this or not lol... wasnt sure if the draft had gotten lost or what.. anyways, i was just now going to take screenshots when i rememebred, you can just use the ones from my origianl post ha
Click to expand...
Click to collapse
Just now seeing this and no time to respond at the moment. I will answer later.