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?
Hey, I'm using camcory's CM10 on my Galaxy Exhibit (the old kernel version). I just received a text message from Bell that I'm at 90% of my monthly usage (resets on the 7th on each month). I have the data usage set to warn me @ 80% and disable data @ 100%.
Strange thing, when I look at my data usage, the last time it recorded info is April 19th. I can select older months to see what my data usage was for those cycles, but it isnt showing the current usage cycle at all - May7th-June7th isn't even an option.
Is there a way to reset the data usage app, or any tips on how I can dig in to see why it is stuck in April?
Thanks!
Joel
Posted in the General section, thought it might get a response here..
Hey, I'm using camcory's CM10 on my Galaxy Exhibit (the old kernel version). I just received a text message from Bell that I'm at 90% of my monthly usage (resets on the 7th on each month). I have the data usage set to warn me @ 80% and disable data @ 100%.
Strange thing, when I look at my data usage, the last time it recorded info is April 19th. I can select older months to see what my data usage was for those cycles, but it isnt showing the current usage cycle at all - May7th-June7th isn't even an option.
Is there a way to reset the data usage app, or any tips on how I can dig in to see why it is stuck in April?
Thanks!
Joel
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?
Hello,
is there a possibility to set the usage cycle of mobile data from 1 month to 4 weeks (28 days)?
A lot of prepaid providers reset the usage of mobile data after 4 weeks and I'd like to check the consumption within android to know how much is left until the end of the cycle.
I'm using the latest Android 11 on my Pixel 5.
I know that I can change the due date of the cycle every monthly cycle 2-3 days backward but that will change the beginning date, too, so that usage calculation isn't correct. An in addition it's very annoying to do that every month.
If there isn't a solution, how can I gave up a feature request for the developers which will seriously be considered for next android updates? (Feedback in settings->about doesn't seem to have any priority for the developers)
I'm glad if you've got some ideas how accomplish this issue.
Regards,
Daniel