I've read the many posts here and elsewhere that say that setting Wifi Sleep to Never will significantly improve battery life. That has not been my experience. I installed 'Battery Graph' from the Market and have been watching my battery levels.
(1) With sleep set to never, battery consumption is about 5%/h when idle. Set to screen off, consumption is around 2%/h.
(2) I stayed overnight at a friend's house on the weekend. My wifi policy was set to never sleep. Returned home at 8am and slept a few more hours. When I woke up, I looked at my phone. While I was out (and asleep) my phone was using about 2%/h. The second I got home (and the phone connected to Wifi) it jumped back up to 5%/h.
I'm thinking this may be due to the weak Wifi signal in my room. I am going to test it by leaving my phone beside the router overnight. Will post the results in the morning.
[12pm, Aug 24]
I left the phone overnight about 1.5m from my router. It had full signal strength according to the Wifi meter in the status bar. It used 6%/h overnight (from 41% at 2am to 18% at 6am).
I'm going to test for the Wifi bug. Then I'm going to try Enom and Modaco. I'm trying to recall exactly when I became concerned about battery life. It has been poor for a little while, but I'm not sure if it only started when I switched to CM.
[3pm, Aug 24]
Don't seem to have Wifi bug. Wiped and flashed CM 6.0 RC3. Battery usage with 'Never sleep' looks better. Suspect that something I was running was eating up battery power on Wifi only.
[5pm, Aug 24]
5%/h. Trying it with sleep on screen off.
[7pm, Aug 24]
I was a little impatient. But with sleep set to screen off, I went 40 minutes without losing a single percent.
Code:
Never (5%/h)
=====
sample_date battery_level
2010 Aug 24 15:31:58 25
2010 Aug 24 15:36:58 25
2010 Aug 24 15:41:55 25
2010 Aug 24 15:46:55 24
2010 Aug 24 15:51:55 23
2010 Aug 24 15:56:55 23
2010 Aug 24 16:01:55 23
2010 Aug 24 16:06:55 22
2010 Aug 24 16:11:55 21
2010 Aug 24 16:16:55 21
2010 Aug 24 16:21:55 21
2010 Aug 24 16:26:55 20
2010 Aug 24 16:31:58 20
Screen Off (~= 1%/h)
=============
2010 Aug 24 17:56:56 33
2010 Aug 24 18:01:55 33
2010 Aug 24 18:06:55 33
2010 Aug 24 18:11:55 33
2010 Aug 24 18:16:55 33
2010 Aug 24 18:21:55 33
2010 Aug 24 18:26:55 33
2010 Aug 24 18:31:55 33
2010 Aug 24 18:36:56 33
Your assumption is most probably right. And you probably also have good reception at home.
If your wifi Mac address starts with 00 then you have the bug and need the new updated driver. Also make sure you set the correct option on settings. I think cyanogen rom uses the fixed driver.
RogerPodacter said:
If your wifi Mac address starts with 00 then you have the bug and need the new updated driver. Also make sure you set the correct option on settings. I think cyanogen rom uses the fixed driver.
Click to expand...
Click to collapse
what?! most mac addresses start with 00
RogerPodacter said:
If your wifi Mac address starts with 00 then you have the bug and need the new updated driver. Also make sure you set the correct option on settings. I think cyanogen rom uses the fixed driver.
Click to expand...
Click to collapse
I am using Cyanogen 6.0 RC3. Although, it's the other way around. The non-zero people had the bug. Mine starts with 00. The official thread seems to say that the fix might cause the bug to effect zero people too. I'll look into that some more to see if it's my problem.
webarnes said:
I've read the many posts here and elsewhere that say that setting Wifi Sleep to Never will significantly improve battery life. That has not been my experience. I installed 'Battery Graph' from the Market and have been watching my battery levels.
(1) With sleep set to never, battery consumption is about 5%/h when idle. Set to screen off, consumption is around 2%/h.
(2) I stayed overnight at a friend's house on the weekend. My wifi policy was set to never sleep. Returned home at 8am and slept a few more hours. When I woke up, I looked at my phone. While I was out (and asleep) my phone was using about 2%/h. The second I got home (and the phone connected to Wifi) it jumped back up to 5%/h.
I'm thinking this may be due to the weak Wifi signal in my room. I am going to test it by leaving my phone beside the router overnight. Will post the results in the morning.
Click to expand...
Click to collapse
Odd, I had exactly the opposite experience when I set wifi sleep to "never." I'm also confused by your test. Wouldn't it be more telling to set your wifi policy to sleep at YOUR home so you can compare that to how the phone performs when sleep is set to never?
webarnes said:
I'm thinking this may be due to the weak Wifi signal in my room. I am going to test it by leaving my phone beside the router overnight. Will post the results in the morning.
Click to expand...
Click to collapse
I left the phone overnight about 1.5m from my router. It had full signal strength according to the Wifi meter in the status bar. It used 6%/h overnight (from 41% at 2am to 18% at 6am).
I'm going to test for the Wifi bug. Then I'm going to try Enom and Modaco. I'm trying to recall exactly when I became concerned about battery life. It has been poor for a little while, but I'm not sure if it only started when I switched to CM.
Just did a search but couldn't find it. Where can I get this driver and how do I apply it?
johnbibbs said:
Just did a search but couldn't find it. Where can I get this driver and how do I apply it?
Click to expand...
Click to collapse
From what I hear, it's in AOSP. So most ROMs should have it now. See here.
How do I installl this? I really dont know. should have a guide for that.
webarnes said:
I left the phone overnight about 1.5m from my router. It had full signal strength according to the Wifi meter in the status bar. It used 6%/h overnight (from 41% at 2am to 18% at 6am).
I'm going to test for the Wifi bug. Then I'm going to try Enom and Modaco. I'm trying to recall exactly when I became concerned about battery life. It has been poor for a little while, but I'm not sure if it only started when I switched to CM.
Click to expand...
Click to collapse
yeah that's a lot of battery drain on wifi. i have left my phone connected to wifi for 10 hours, and in total only lost 10% from 100% to 90%. so 4 hours and you lost 24%, that's a little high..
webarnes said:
I am using Cyanogen 6.0 RC3. Although, it's the other way around. The non-zero people had the bug. Mine starts with 00. The official thread seems to say that the fix might cause the bug to effect zero people too. I'll look into that some more to see if it's my problem.
Click to expand...
Click to collapse
Wait what? This could explain the sleep issues I've started to have with wifi which I didn't have earlier.
The wifi driver is part of the rom right? If I flash an earlier non-AOSP rom I'll automatically use the "unfixed" driver right?
I was a little impatient. But with sleep set to screen off, I went 40 minutes without losing a single percent.
Code:
Never (5%/h)
=====
sample_date battery_level
2010 Aug 24 15:31:58 25
2010 Aug 24 15:36:58 25
2010 Aug 24 15:41:55 25
2010 Aug 24 15:46:55 24
2010 Aug 24 15:51:55 23
2010 Aug 24 15:56:55 23
2010 Aug 24 16:01:55 23
2010 Aug 24 16:06:55 22
2010 Aug 24 16:11:55 21
2010 Aug 24 16:16:55 21
2010 Aug 24 16:21:55 21
2010 Aug 24 16:26:55 20
2010 Aug 24 16:31:58 20
Screen Off (~= 1%/h)
=============
2010 Aug 24 17:56:56 33
2010 Aug 24 18:01:55 33
2010 Aug 24 18:06:55 33
2010 Aug 24 18:11:55 33
2010 Aug 24 18:16:55 33
2010 Aug 24 18:21:55 33
2010 Aug 24 18:26:55 33
2010 Aug 24 18:31:55 33
2010 Aug 24 18:36:56 33
RogerPodacter said:
yeah that's a lot of battery drain on wifi. i have left my phone connected to wifi for 10 hours, and in total only lost 10% from 100% to 90%. so 4 hours and you lost 24%, that's a little high..
Click to expand...
Click to collapse
What is your Wifi sleep policy?
Related
I have a stock Droid Bionic that I have been quite pleased with, well that is up until the latest OTA update I received. Prior to the update, I was enjoying 20+ hours of battery life with moderate use (with juice to spare), and had generally no complaints with the phone. A few weeks ago, however, I received an OTA update in the middle of the night, and it didn't take long for me to discover something with the update had caused my battery life to severely suffer. Long story short, I get about 8-10 hours of life now with very little use, and there is a constant drain whether the screen is on/off, wi-fi disabled, etc. Battery stats show Android OS and the Screen as battery hogs, and I have exhausted all options to this point without finding a solution (FDR, clear cache, etc.).
So now to my question; I feel as if my only option (other than getting a new phone or waiting for the official next update) is to root my phone in order to freeze whatever android app/services are causing my battery drain. However I am a complete newbie to rooting, ROM's, etc., and really don't know where to begin. I really only want to solve this battery issue to get back to the experience I had prior to this 4.1.2 JB update.
So, what would you all suggest as far as the simplest and easiest root solution? I know this might seem like a complicated (or even incorrectly worded) question, but I appreciate everyone's responses.
Thanks!
Read the first few threads on this, if you're really bored then read them all:
http://forum.xda-developers.com/showthread.php?t=2256439
A little searching will go a long way here...
A lot of times after an ota a factory reset will take care of a lot of problems
Sent from my DROID BIONIC using Tapatalk 2
B.E.McAllister said:
A lot of times after an ota a factory reset will take care of a lot of problems
Sent from my DROID BIONIC using Tapatalk 2
Click to expand...
Click to collapse
I've tried that a few times, but the problem persists. I've posted some stats from BBS (attached in this post too) in other threads hoping someone can help me pin down the issue. Thanks for your help!
You don't need to root to freeze apps.
Go to the apps section in the settings menu, then go to the all tab and click on an app you don't need and hit disable, it won't let you do it with a few apps but you can freeze a majority of the bloatware this way.
Also it might be worth it to try a battery calibrator, this doesn't extend your battery life but it helps ensure that your battery is getting a full charge and reporting the correct percentage.
If you do decide to root your phone check out marty45714's Easy Root for Bionic Stock 4.1.2 (Jelly Bean) thread in the Bionic General subforum
jemmox21 said:
I've tried that a few times, but the problem persists. I've posted some stats from BBS (attached in this post too) in other threads hoping someone can help me pin down the issue. Thanks for your help!
Click to expand...
Click to collapse
Looks like your WiFi is running full bore while it's asleep.
Deep Sleep (): 6 h 44 m 32 s (24272 s) Ratio: 95.3%
Awake (): 19 m 50 s (1190 s) Ratio: 4.7%
Screen On (): 10 m 58 s (658 s) Ratio: 2.6%
Wifi On (): 7 h 4 m 22 s (25462 s) Ratio: 100.0%
Wifi Running (): 7 h 4 m 22 s (25462 s) Ratio: 100.0%
No Data Connection (): 7 h 4 m 22 s (25462 s) Ratio: 100.0%
No or Unknown Signal (): 7 h 4 m 22 s (25462 s) Ratio: 100.0%
Screen dark (): 10 m 58 s (658 s) Ratio: 2.6%
I would suggest setting the WiFi to off during
Sleep
Settings -> Wi-Fi -> Settings\ Advanced -> Keep Wi-Fi on during sleep -> Only when plugged in
On 14.5.A.0.270 my date range suddely went crazy in Data usage. My data plan refreshes on 5th each month. But suddenly the date range when I open the Data usage is Mar 5 - Apr 2, 2073. Apps below show the real data usage but the graph is empty.
So I scroll down to select the nearest date possible (Jun 14 - Jul 12, 2015) and what I see is the same as with the 2073 date range.
Further on when I close Data usage and reopen it, I see the 2073 date range again.
Has anyone seen this and how to fix it?
Thanks.
When I woke up this morning, my ASUS MeMO Pad 7 (ME176CX) was showing the wrong time. It was about 3 hours and 37 minutes slow. It is set to get the time automatically from the network. It is wifi only, not a phone. It is not rooted, and it says it is fully updated.
I rebooted, and when it came back up the time was correct. However, after a few minutes, it was running behind again. I rebooted again, again it showed the correct time, but after about 6 minutes it was running about 3 minutes behind, and as time progresses it falls further behind. If I set the time to manual, it also falls behind.
It has kernel version 3.10.20-x86_64_byt [email protected] #1 Tue Jun 23 13:05:51 CST 2015
Build number LRX21V.WW_K013-12.10.1.24-20150623 044030456_201502160111 0010000200001
Android version 5.0
Developer mode enabled, but developer options set to off
ronzie009 said:
When I woke up this morning, my ASUS MeMO Pad 7 (ME176CX) was showing the wrong time. It was about 3 hours and 37 minutes slow. It is set to get the time automatically from the network. It is wifi only, not a phone. It is not rooted, and it says it is fully updated.
I rebooted, and when it came back up the time was correct. However, after a few minutes, it was running behind again. I rebooted again, again it showed the correct time, but after about 6 minutes it was running about 3 minutes behind, and as time progresses it falls further behind. If I set the time to manual, it also falls behind.
It has kernel version 3.10.20-x86_64_byt [email protected] #1 Tue Jun 23 13:05:51 CST 2015
Build number LRX21V.WW_K013-12.10.1.24-20150623 044030456_201502160111 0010000200001
Android version 5.0
Developer mode enabled, but developer options set to off
Click to expand...
Click to collapse
Clearing the cache seems to have fixed the problem.
This happens to mine all the time. It will be fine for a while and then suddenly be way off. It is something in the system making time move slowly because I can tell in games that it is actually showing things happening more slowly and games that rely on time passing will be in line with the tablets perceived time.
Hi, im having the same problem since lollipop update.
If i compare Asus clock with other clock, when Asus did 45 seconds, real clocks did 60 seconds.
This is very annoying, do you know any solution?
What cache should i clear?
Hwy everyone
Quick question has anyone's watch started randomly switching off and reseting? It was going it like crazy every couple of mins and when it boots back up the time is at 12 and the date the first of January 1970 :S its seems to do it when my phone isn't connected to it.
LG watch do not keep time. Every time the watch boot (after off) it start at midnight UTC Juanuary 1, 1970 and it sync with the phone after connection.
Hi everybody, i've noticed recently that, even if i charge my phone every 2 days, in the "power consumption detail" section, into "battery" menu, it doesn't count correctly the "Used since last full charge" time. Example: charged on the afternoon of April 2nd, so now, in the afternoon of april the 4th, there should be almost 2 days of use but the counter says it has been only 1 day and 12 hours starting count on April 3rd morning when i turned it on (even if in the evening of the 2nd i used it after full charging it).
Has anyone had the same "issue"? I'm not sure if it started after the Google security patch of February or March, thank you!