Given that the display is widely regarded as one of the two biggest drawers of power/battery life on the N1 (the other being the radio/cell standby), and given that my battery usage breakdown *always* has Display at the top (by a large margin), I thought it might be interesting to see what other people's Display usage hovers around so we can build up a "operating range"...
(apologies if anyone has done this before, I did a few searches but nothing significant came up - please point me to previous posts if it has already been covered)
not exactly seeing an option for a Poll...would recommend setting one up before we get 100s of posts to comb through
bloke226 said:
not exactly seeing an option for a Poll...would recommend setting one up before we get 100s of posts to comb through
Click to expand...
Click to collapse
you got there darn quick - cheers for voting though!
it depends on what rom u have. my battery usage for the display was significantly different from cyanogen to desire rom.
nellyspageli said:
it depends on what rom u have. my battery usage for the display was significantly different from cyanogen to desire rom.
Click to expand...
Click to collapse
that was one of the things that prompted me to do the poll, as I'm familiar with a Desire with Sense that reports around 20%
unfortunately I don't think i can also capture the ROM here (kernel would have been nice too), but I wanted to - and think you may have a point...
Moved as not Android Dev.
Yeah, unfortunately if you are getting a low display usage if you use it a lot means that the rest of your system is really hogging the power. Cyanogenmod with a high display usage is great because it means the rest of the system is running very efficiently.
Clarkster said:
Yeah, unfortunately if you are getting a low display usage if you use it a lot means that the rest of your system is really hogging the power. Cyanogenmod with a high display usage is great because it means the rest of the system is running very efficiently.
Click to expand...
Click to collapse
It could mean a few different things, not just that. This is not a very scientific poll, sorry.
Thanks for this Poll. I was beginning to think that maybe my Nexus One was defective because the screen used so much of the battery. Unlike my HTC Magic, where the Cell Standby/Phone Idle was king.
The screen is supposed to be the highest drain. That means that the OS and all your apps are very efficient and not out of control.
just FYI, it seems on the bleeding edge kernels that a couple of kernel authors are producing at the moment, that Display usage is down. I am typically seeing no more than 40% in the stats now (down from around 60%) - will update once the kernel dust settles!
this poll isnt really effective, i have seen my screen usage from 10% all the way up to 89%, from what ive seen the percentage is based off of how long since the phone has been unplugged from a charger to the amount of time you were actually using it(had the screen on)
i can run my battery life into the ground in 6 hours or i can make it last 34 hours(max from full charge to shut down with all the fancy stuff turned off)
Related
Dear Nexus One users!
I'm trying to gather some data for the following thread: http://forum.xda-developers.com/showthread.php?t=753382
I have a feeling that HTC has tampered with the Desire's power usage statistics in order to make the AMOLED screen seem more efficient.
As far as I've heard (only asked two Nexus One owners so far), the Nexus's display usage is about on par with the Desire's vanilla ROMs, which leaves me to believe that the vanilla ROMs are accurate, and the HTC Sense ROMs are the ones with the problem.
I hope you can help me gather some stats
Thanks in advance!
-edit- Forgot to say: The statistics I'm talking about can be found in Settings=>About Phone=>Battery Use, and I'm interested in the statistics after a day of reasonable to heavy use (web browsing, messaging, phone calls etc.).
It's usually in the 61-80% range even with heavy use. I have to admit that I run the screen on full brightness all the time though, so that can skew the results a little.
Thanks for all the votes so far guys!
Looks like I was right
Getting some good data here... keep it up, thanks!
just thought i would add... (hopefully not too off topic) the HTC Desire (the new SLCD models), the Display only uses like <10%, seems they weren't lying about the battery saving part (this is based on what I've seen on my friend's Desire)
anyways my AMOLED Nexus one is in the 60-70% range and I'm usually in Automatic brightness mode
kwazi said:
just thought i would add... (hopefully not too off topic) the HTC Desire (the new SLCD models), the Display only uses like <10%, seems they weren't lying about the battery saving part (this is based on what I've seen on my friend's Desire)
anyways my AMOLED Nexus one is in the 60-70% range and I'm usually in Automatic brightness mode
Click to expand...
Click to collapse
Don't allow yourself to be fooled - AMOLED Desires also often use less than 10% of the battery according to HTC ROMs... which is precisely why I think it's bull****.
Hell, the day before yesterday I kept my display on nearly the whole day, just to test the new power consumption stats (using OpenDesire, and as of 3.1.0 the power consumption statistics have been changed to give pretty much the same results as Sense ROMs) - result: about 10 hours of total battery life (from a full charge!), 6 of which had the display running. Now guess what the new Sense-style battery consumption measurements told me? Supposedly, even though my display had been on all day, it only used 13% of the total battery.
So don't worry - I don't think it's true that your phone uses so much more power - but rather, that HTC has somehow screwed up the power consumption statistics in their Sense ROMs, and the screen is using much more power than they're showing.
And you're not off topic at all. You're a perfect example for someone confused by the discrepancies in power usage statistics. They're not logical, and they're leading you to believe that your AMOLED diplay is using a lot more power than the new sLCD displays in Desires, as well as the AMOLED displays in the older Desires.
My display is always up around 80% of my total use. Everyday its like that. And that's the way it should be unless your device sleeps all day with no use.
When doing your comparison, you also need to post your display-on time, and your total time since unplugged. These are in the same place as your percentages. This way we know the ratio that The display was used and how long the device was unplugged. Otherwise I could post a number but without a reference point its meaningless. What if my screen never turned on once? That certainly skews the result.
RogerPodacter said:
My display is always up around 80% of my total use. Everyday its like that. And that's the way it should be unless your device sleeps all day with no use.
When doing your comparison, you also need to post your display-on time, and your total time since unplugged. These are in the same place as your percentages. This way we know the ratio that The display was used and how long the device was unplugged. Otherwise I could post a number but without a reference point its meaningless. What if my screen never turned on once? That certainly skews the result.
Click to expand...
Click to collapse
Theoretically you're right of course. However, so far the discrepancies are so immense that I don't think that's even necessary. Leaving the display on 100% of the time on a Sense ROM doesn't even allow you to crack 20% battery used by the display... Using the display for an hour on the Nexus or an AOSP Desire ROM, gives you at least 40% battery used by the display at the end of the day. Unless someone really keeps their phone off the ENTIRE time, I don't think the clarification is even necessary...
Hello everyone!
Thanks for the useful data. After continued testing by myself and a few other interested people (namely th3, who provided the idea for disproval of HTC's Sense battery use statistics once and for all, and Andycted, who has been providing many useful statistics which helped us get a better idea of general power consumption on the Desire), I've entered the issue on the Android Issues tracker.
You can view the issue here, and feel free to comment and/or star the issue to show your support, as it concerns all Android users. The problem may only be present on HTC Sense, but how will you know if future devices are reporting battery usage correctly if the statistics are so easily tampered with?
Thank you again for your help, support, and very helpful and constructive criticism.
Mine is always between 45 and 55 %, nearly stock FRF91 and minimum brightness
Haha, a friend of mine that just got the SLCD Desire was claiming his screen wasn't burning through the power like my n1 seems to. I guess it's unfortunate that it isn't the case.
I'd wager the SLCD really does use a lot less power when displaying bright colors, especially like white web page backgrounds... but even if your buddy spends his whole day looking at bright web pages (nothing with dark backgrounds), the battery usage of his display should be at the most 10% lower than yours
bemymonkey said:
I'd wager the SLCD really does use a lot less power when displaying bright colors, especially like white web page backgrounds... but even if your buddy spends his whole day looking at bright web pages (nothing with dark backgrounds), the battery usage of his display should be at the most 10% lower than yours
Click to expand...
Click to collapse
I totally read your post wrong, sorry.
We have figures for the approximate power drain of the AMOLED screen (155mA black, 485mA white) so where are the figures for the SLCD?
ChronoReverse said:
I totally read your post wrong, sorry.
We have figures for the approximate power drain of the AMOLED screen (155mA black, 485mA white) so where are the figures for the SLCD?
Click to expand...
Click to collapse
Back a few years ago (th3 posted a PDF from a company that manufactures AMOLED screens), the figures were around 200-250mW for the LCD (on all screen colors), while an AMOLED of the same size drew 700-something mW on a white screen. Obviously older screens, and smaller in size, but should be comparable...
I'll see if I can dig it up again...
Here it is:
http://data.4dsystems.com.au/downloads/micro-OLED/Docs/4D_AMOLED_Presentation.pdf
we need to get some desire users with the SLCD screen to install the current power draw widget to their homescreen and give us some numbers. or just pull them from the dmesg log. at this point i have pretty good numbers for the nexus amoled screen, and like said above black typically around 140 mA and white 350 mA, but those both a lot of the time go much lower and higher, respectively.
RogerPodacter said:
we need to get some desire users with the SLCD screen to install the current power draw widget to their homescreen and give us some numbers. or just pull them from the dmesg log. at this point i have pretty good numbers for the nexus amoled screen, and like said above black typically around 140 mA and white 350 mA, but those both a lot of the time go much lower and higher, respectively.
Click to expand...
Click to collapse
I'll see if I can get said friend to do that then lol.
ChronoReverse said:
I'll see if I can get said friend to do that then lol.
Click to expand...
Click to collapse
Please! I'd love to see some exact figures too, if possible with all radios off and in idle. Measurements both on minimum and max brightness preferred
bemymonkey said:
Dear Nexus One users!
I'm trying to gather some data for the following thread: http://forum.xda-developers.com/showthread.php?t=753382
I have a feeling that HTC has tampered with the Desire's power usage statistics in order to make the AMOLED screen seem more efficient.
As far as I've heard (only asked two Nexus One owners so far), the Nexus's display usage is about on par with the Desire's vanilla ROMs, which leaves me to believe that the vanilla ROMs are accurate, and the HTC Sense ROMs are the ones with the problem.
I hope you can help me gather some stats
Thanks in advance!
-edit- Forgot to say: The statistics I'm talking about can be found in Settings=>About Phone=>Battery Use, and I'm interested in the statistics after a day of reasonable to heavy use (web browsing, messaging, phone calls etc.).
Click to expand...
Click to collapse
Nah, it's just that Sense uses more battery, therefore the screen doesn't use as much in comparison
Hello,
I'd have posted this to the dev section but the posting rules here require non-talkative people to fabricate 10 useless posts before they can post there.
I've noticed that "Cell Standby" is far and away my greatest battery user on my Nookie Custom 0.6.8 eMMC flashed device. Now, I'm sure this is just a mislabeled "Display" usage meter, but I wanted to make sure. I'd post a screenshot, but apparently I might be a terrorist since I haven't made ten posts yet so I'm not allowed to link images yet.
Thanks In Advance
As far as I know, the cell phone battery usage problem has been debunked. I could be completely wrong, but since the Nook lacks the necessary components, there's no actual way for the power to be lost in the process.
I'm about as new as it gets, though, so take that with a grain of salt.
junkrobot said:
As far as I know, the cell phone battery usage problem has been debunked. I could be completely wrong, but since the Nook lacks the necessary components, there's no actual way for the power to be lost in the process.
I'm about as new as it gets, though, so take that with a grain of salt.
Click to expand...
Click to collapse
Yep, it is debunked, ignore it if battery life is the concern. If you want different info in Spare Parts for partial wake, this changes it to Android System..
junkrobot said:
As far as I know, the cell phone battery usage problem has been debunked. I could be completely wrong, but since the Nook lacks the necessary components, there's no actual way for the power to be lost in the process.
Click to expand...
Click to collapse
I believe this, however -- how hard would it be to find an app that claimed to track what was using the battery with any accuracy. Pretty sad that the built in battery monitor gives "credit" to "cell standby" for 50%+ of battery usage on a device that does not even have a cell. Anybody could build an app that hard coded battery usage stats in pre-defined chunks
I don't know why this bugs me so much...it just does.
I now have one week to the Nexus One bought secondhand. It suits me perfectly stand alone I have a little trouble with the battery life of the phone. Morning when the phone is 100% and I come out of school (14:30 hours) the battery is still around 20%. I find this a bit short. Ok, I'll use him at school (bit Internet, twitter refreshes every 9 minutes)
There is an automatic task killer, and that helps a bit but I think there are about 80% after 8 hours battery life is a bit much. Me internet is also constantly and I really like to keep.
The battery is probably not because I've got 2 batteries and they both give the same result.
Anyone have any idea what I can do?
I've been a bit inet searched but not really found anything. I did see somewhere a separate battery behind the phone, but I'm not waiting because that makes him a bit heavier and uglier.
10% per hour is pretty poor battery life. Are you running stock Android? 3rd party firmwares can give you much better battery life (the latest versions of CyanogenMod are using less than 1% per hour when fully idle).
But there are things you can check. Have you looked in Settings -> About phone -> Battery usage? If you are using Gingerbread and you look at the graph, if there is a solid line (or mostly solid) next to the "awake" portion, it means that your phone isn't properly entering its low powered state. Download spare parts from the market and check out partial wake usage under the battery history section of that app.
Please post your screen on time value from the battery menu so we can see how long your screen is on.
I would say to go and disable background data. Disabling this will definitely improve your battery life. Of course, you aren't going to get you twitter updates but aside from that, the battery life should improve.
Sent from my Nexus One using XDA Premium App
FLAC Vest said:
I would say to go and disable background data. Disabling this will definitely improve your battery life. Of course, you aren't going to get you twitter updates but aside from that, the battery life should improve.
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
While it is true that battery life would improve if Background Data was disabled (or limited via a program like Juice Defender), it doesn't take into account his actual problem. Unless it is a ton of apps constantly downloading that is keeping his battery usage in the toilet, this will only yield a slight improvement. I believe the cause is is an app (or apps) that prevent his phone from entering the low powered sleep state.
I don't know what stock Android gets from completely idle use (haven't run it since July last year), but a basic CyanogenMod install would sip between 1-2% per hour with the latest stable and the latest nightlies, some are reporting 1% every 2-3 hours when the phone is left alone (due to a fix that lets the microphones go into a deep sleep state).
Twitter refreshing every 9 minutes can not be helping, that said I doubt that's your entire issue but reducing the refresh rate should help quite a bit.
If you bought it used, it could be a bum battery. Not sure i know what apps work best to find out that info. Anybody?
Estimated Prophet Hawk said:
If you bought it used, it could be a bum battery. Not sure i know what apps work best to find out that info. Anybody?
Click to expand...
Click to collapse
The battery app in my sig is the only one that reads the chip inside your battery to tell if it's legit or not, what the battery age is, etc. Needs root to work though.
Estimated Prophet Hawk said:
If you bought it used, it could be a bum battery. Not sure i know what apps work best to find out that info. Anybody?
Click to expand...
Click to collapse
You can also get Battery Left from the Marketplace and when it gets calibrated it gives you a time until death number and some other features.
Sent from my Nexus One using XDA Premium App
Start by getting rid of the task killer.
Sent from my Nexus One using XDA App
Older types of rechargable batteries exhibited a 'memory effect' which made it neccessary to completely charge/discharge the battery when using to prevent degradation of the capacity. Modern Lithium-Ion batteries like in the Nexus S do not show this problem and thus it is not necessary to use the battery in complete (dis)charge cycles. In fact on the contrary, it is commonly accepted that both very low and very high charge states accelerate the degradation of the battery capacity (that is why you should store Li-Ion batteries at around 40% charge).
While a low charge state can be simply avoided by charging the device more often, the battery in the Nexus S by default is charged to around 95% capacity and I could not find any app or tweak to stop the charging at a lower capacity. Thus the only way was to use the manual override and pull the cable which is annoying since one had to monitor the charge state.
So I implemented a simple tweak I called Battery Life eXtender (BLX) which can be used to set a limit for the capacity to which the battery will be charged by passing a value between 0 and 101 to 'charging_limit' in '/sys/class/misc/batterylifeextender' (101 by default).
Changes to the source code: http://www.pastie.org/2516542
BUGFIX:
The battery status is set to 'full' once the user defined charging limit is reached.
Bug fix: http://www.pastie.org/2534319
BUGFIX #2:
The charging limit is set to 96 by default which will mimic the behaviour of the stock kernel. Also, the maximum value accepted by 'charging_limit' is set to 96.
Bug fix: http://www.pastie.org/2560599
BUGFIX #3:
1. Made BLX compatible with the 100% charging 'fix'.
2. If the charging limit is set to the maximum charging limit, charging will not be stopped until the interrupt signal is received from the MAX8998 chip.
Bugfix: http://www.pastie.org/2751140
No further patches will be published here. I have set up a git repo for all my tweaks. Each mod has its own branch to keep the tweaks cleanly separated and one can simply pull the latest patches from the corresponding branch.
https://github.com/Ezekeel/GLaDOS-nexus-s/tree/blx
I do not accept donations and since I reached my 50GB limit of free space on SpiderOak, thanks to all of you kind people who got an account using my referral link, I could not ask for more.
Instead if you really want to donate your hard earned money to someone who deserves and needs it, consider donating to the Free Software Foundation at fsf.org: These guys are at the frontline when it comes to keeping Linux free and fighting these greedy bastards who think they are entitled to collect royalties and other fees from Linux users due to some silly patents - and if Linux falls, Android will be next.
Can't wait for Trinity to include this!
Sent from my Nexus S using XDA App
i charge my ns to 100% all the time, i wish that i could charge it even more. lol!
Wow! I am waiting for this for long time!
Sent from my Google Nexus S using XDA Premium App
simms22 said:
i charge my ns to 100% all the time, i wish that i could charge it even more. lol!
Click to expand...
Click to collapse
Yeah, the drawback of course is the shorter battery runtime. If even a fully charged battery still is not enough for you to get over the day, this tweak is not for you. However, I mostly use the Nexus for internet, email and music and for me a fully charged battery last for about 3 days. So in my case when setting the charging limit to let's say 80% that is still plenty of reserves.
Before I wrote this tweak I thought about if it actually makes sense to try and prolong the lifetime of these batteries because they can be easily replaced and are also pretty cheap. However it seemed like a good idea purely from an environmental point of view (even if there is no climate change like Rick PArry totally has convinced me).
Ezekeel said:
Yeah, the drawback of course is the shorter battery runtime. If even a fully charged battery still is not enough for you to get over the day, this tweak is not for you. However, I mostly use the Nexus for internet, email and music and for me a fully charged battery last for about 3 days. So in my case when setting the charging limit to let's say 80% that is still plenty of reserves.
Before I wrote this tweak I thought about if it actually makes sense to try and prolong the lifetime of these batteries because they can be easily replaced and are also pretty cheap. However it seemed like a good idea purely from an environmental point of view (even if there is no climate change like Rick PArry totally has convinced me).
Click to expand...
Click to collapse
i thought about the need to prolong the batterys life too. i thought about how long id be using my phone as a primary device before i get a new one vs the actual life of the battery. i figured id replace the phone before the battery actually died. of course, there is that odd random chance that the battery will die much quicker than expected. my original g1 battery from 2008 is still good, and i abused that phone for a long time. but, there is something else that i didnt think about. there are lots of people in the world that are less fortunate than i am. and they need their devices to last them as long as the devices can because they cant afford getting new ones. and that includes the battery too. they would appreciate something like this. of course, there is that envirenmental thing that you touched upon. less crap destroying our wonderful planet
Ezekeel said:
Yeah, the drawback of course is the shorter battery runtime. If even a fully charged battery still is not enough for you to get over the day, this tweak is not for you. However, I mostly use the Nexus for internet, email and music and for me a fully charged battery last for about 3 days. So in my case when setting the charging limit to let's say 80% that is still plenty of reserves.
Before I wrote this tweak I thought about if it actually makes sense to try and prolong the lifetime of these batteries because they can be easily replaced and are also pretty cheap. However it seemed like a good idea purely from an environmental point of view (even if there is no climate change like Rick PArry totally has convinced me).
Click to expand...
Click to collapse
so it is not for hardcore user? I have to recharge the phone every evening *argh* !
Sent from my Google Nexus S using xda premium
Sounds like Simms is waiting for the Nexus Prime?
simms22 said:
i charge my ns to 100% all the time, i wish that i could charge it even more. lol!
Click to expand...
Click to collapse
Sry for the noob question, but how do u charge it to 100%?
I appreciate your work Ezekeel.
I have one suggestion: Can you make one thread with all your MODs included so that it is not fragmented all over the Android Development forum?
That would be very kind of you.
Fantastic...waiting for this!!
Inviato dal mio Nexus S usando Tapatalk
dinuvali said:
Sry for the noob question, but how do u charge it to 100%?
Click to expand...
Click to collapse
You have to charge the phone with the screen on.
I'd rather wait for this mod to be implemented in kernels, or roms.
W00T ! This is THE mod I was waiting for since I got my Nexus S ! Thanks a lot Ezekeel for all your work !
WOW! Very nice. I'm waiting)
We want it fast!!!!
Accidentally sent from my Nexus S using XDA Premium App
Ezekeel said:
Yeah, the drawback of course is the shorter battery runtime. If even a fully charged battery still is not enough for you to get over the day, this tweak is not for you. However, I mostly use the Nexus for internet, email and music and for me a fully charged battery last for about 3 days. So in my case when setting the charging limit to let's say 80% that is still plenty of reserves.
Before I wrote this tweak I thought about if it actually makes sense to try and prolong the lifetime of these batteries because they can be easily replaced and are also pretty cheap. However it seemed like a good idea purely from an environmental point of view (even if there is no climate change like Rick PArry totally has convinced me).
Click to expand...
Click to collapse
What kind of battery you are using, why my battery can only last 1 day with few calls, message and a couple of hours internet.
brainmaster said:
I appreciate your work Ezekeel.
I have one suggestion: Can you make one thread with all your MODs included so that it is not fragmented all over the Android Development forum?
That would be very kind of you.
Click to expand...
Click to collapse
Totally agreeing to that.
I concur.
nice - but not something I see myself using so one little question in advance: If I use a kernel that has this and I just delete this config file - will my ns behave as if it had never been there?
brainmaster said:
I appreciate your work Ezekeel.
I have one suggestion: Can you make one thread with all your MODs included so that it is not fragmented all over the Android Development forum?
That would be very kind of you.
Click to expand...
Click to collapse
You mean joining all the thread in a single one or creating an additional thread as an index which links to the individual threads?
jaoyina said:
What kind of battery you are using, why my battery can only last 1 day with few calls, message and a couple of hours internet.
Click to expand...
Click to collapse
The stock battery with 3G disabled and CPU freq limited to 800GHz.
gotjazz said:
nice - but not something I see myself using so one little question in advance: If I use a kernel that has this and I just delete this config file - will my ns behave as if it had never been there?
Click to expand...
Click to collapse
The charging limit is set to 101 by default, so as long as you do not set a different limit this tweak will do nothing at all.
Anyone using SetCPU to throttle the device and get tolerable battery life?
I wish. Not on Verizon!
Bump!!
I just started using trickster mod and set max frequency to about 2.0GHz. The battery life has increased with no lag. On Lollipop.
obtained said:
I just started using trickster mod and set max frequency to about 2.0GHz. The battery life has increased with no lag. On Lollipop.
Click to expand...
Click to collapse
What did you have to do to get trickster working? Just download it? It works straight from the market? H3lp!
zgroten said:
What did you have to do to get trickster working? Just download it? It works straight from the market? H3lp!
Click to expand...
Click to collapse
Yeah just download it. You will have to download a busybox installer if you don't have busybox installed as well.
Awesome thanks. What mods and settings have you found useful?
Anyone has had success tweaking new Moto X with SetCPU?
martinezma99 said:
Anyone has had success tweaking new Moto X with SetCPU?
Click to expand...
Click to collapse
SetCPU caused major lag for me personally.. I switched to trickstermod and all seems fine so far
I'm using No Frills, working great across 422MHz - 1GHz ( hardcore testing )
I have never noticed any battery improvement from underclocking, and correct me if I'm wrong but I thought the general consensus (among those actually informed) was that it doesn't actually help because it causes the processor to take longer to complete tasks, canceling out any actual gains.
_MetalHead_ said:
I have never noticed any battery improvement from underclocking, and correct me if I'm wrong but I thought the general consensus (among those actually informed) was that it doesn't actually help because it causes the processor to take longer to complete tasks, canceling out any actual gains.
Click to expand...
Click to collapse
After testing for a day almost, I'll say that's crap.. I'm running this guy comfortably at 0.8GHz with ultra small lags, see the battery for yourself. I used to get 4-4.5 hours of max screen on running it untampered and now this damn battery won't die!
ManiacShri said:
After testing for a day almost, I'll say that's crap.. I'm running this guy comfortably at 0.8GHz with ultra small lags, see the battery for yourself. I used to get 4-4.5 hours of max screen on running it untampered and now this damn battery won't die!
Click to expand...
Click to collapse
Yeah I dunno man, I'm not underclocked and I can probably get 8+hrs SOT as well if all I'm doing is web browsing and reading. I mean, I average around 6-7hrs SOT on mine (still on 4.4.4) depending on what I'm doing. Everybody's usage patterns are different, which is why I don't trust SOT screen shots. Plus, there is nothing in your second screenshot that shows any actual usage. You have screen, cell standby, wifi, android system... I'm not seeing any apps in there which leads me to believe that isn't a heavy usage scenario for you.
And again, I have underclocked before with many, many devices and haven't seen any actual gains. Also, I have yet to see any actual empirical evidence that shows underclocking helps. Couple that with the fact that many people who are well versed in this stuff (including the CyanogenMod team) have come forward and said that any gains from underclocking are placebo due to the reason I stated before, and I am HIGHLY skeptical.
_MetalHead_ said:
Yeah I dunno man, I'm not underclocked and I can probably get 8+hrs SOT as well if all I'm doing is web browsing and reading. I mean, I average around 6-7hrs SOT on mine (still on 4.4.4) depending on what I'm doing. Everybody's usage patterns are different, which is why I don't trust SOT screen shots. Plus, there is nothing in your second screenshot that shows any actual usage. You have screen, cell standby, wifi, android system... I'm not seeing any apps in there which leads me to believe that isn't a heavy usage scenario for you.
And again, I have underclocked before with many, many devices and haven't seen any actual gains. Also, I have yet to see any actual empirical evidence that shows underclocking helps. Couple that with the fact that many people who are well versed in this stuff (including the CyanogenMod team) have come forward and said that any gains from underclocking are placebo due to the reason I stated before, and I am HIGHLY skeptical.
Click to expand...
Click to collapse
The reason there's no specific apps you see is because I did what you do in a typical battery test, gaming a bit, reading ,browsing and all the others... So the individual. consumption is well b below 5%.. But yeah even without underclocking i have gotten even 5.5hours which is not bad at all
_MetalHead_ said:
Yeah I dunno man, I'm not underclocked and I can probably get 8+hrs SOT as well if all I'm doing is web browsing and reading. I mean, I average around 6-7hrs SOT on mine (still on 4.4.4) depending on what I'm doing. Everybody's usage patterns are different, which is why I don't trust SOT screen shots. Plus, there is nothing in your second screenshot that shows any actual usage. You have screen, cell standby, wifi, android system... I'm not seeing any apps in there which leads me to believe that isn't a heavy usage scenario for you.
And again, I have underclocked before with many, many devices and haven't seen any actual gains. Also, I have yet to see any actual empirical evidence that shows underclocking helps. Couple that with the fact that many people who are well versed in this stuff (including the CyanogenMod team) have come forward and said that any gains from underclocking are placebo due to the reason I stated before, and I am HIGHLY skeptical.
Click to expand...
Click to collapse
You can be sceptical because you should be, the cpu throttles already and only uses max speed when needed. With light usage like me (WhatsApp, telegram, 20m phone calls and some mails a day) I get 4 days on 4g and wifi. (I turn my phone on flight mode during the night) I've also disabled moto application (voice is useless in Dutch/not working) The biggest energy consumer is the screen so change your wallpaper to a dark one and close unused background apps (moto voice, google now, virus scanner and all other useless apps. If you use all the social media out there on your phone, no battery capacity is sufficient. I could limit my max cpu speed because the cpu governor probably throttles to max even when launching undemanding apps, but I would probably won't notice any savings.