Hi, so basically, i've got a weird issue. and i've gone through many other threads regarding this, but still have not been able to find a proper solution.
firstly, when i'm connected to wifi, i don't receive my notifications when the screen is locked. until i wake the phone up the notifications come up. and yes, on advanced wifi - keep wifi on during sleep is on always.
when i disable wifi optimisation, it's slightly better but not completely solved. it's jumpy, as in sometimes i get a notification and sometimes i don't till i wake the phone. however the phone's idle battery consumption jumps from 9-20 mAh to about 40-100mAh which i hate.
this leads to - when im not on wifi my idle battery consumption is between 6-10mAh, whilst on wifi with wifi optimisation enabled its 9-20mAh.
Through reading numerous threads, i installed push notifications fixer - root. it has kind of fixed my push notifications issue, but now idle battery consumption is between 100-145mAh.
I do believe it's an issue with my router, but when i installed another router, the same issue popped up. could it be both routers are at fault. or something else?
guys please help as i'm sure others have the same issue.
There is a jira open here:
https://jira.cyanogenmod.org/browse/BACON-1649
Now i've taken screenshots to display how the it was and how it is now with push notifications fixer.
no one?
I can only say I noticed this when I wake up my phone all notifications comes at batch. Also, while in deep sleep I do get combined notifications at batches.
it looks like scheduled data connection, goes on and off. In term of the delay its max 3 minutes when I compare it with message notification time sent and time arrival.
In my case I don't suffer from battery drain.
Related
I have trouble downloading large files using this ROM since when my screen turns off, WIFI is also disabled. How can I change it. I've been looking in the settings but to no avail.
Edit: Found it...you have to click menu when in the WIFI Settings, then choose advanced.
Edit2: Wifi is disabled when screen is turn off even if the Wifi sleep policy is changed to Never.
Any ideas?
then that is some kind of bug. because setting wifi sleep policy to never should behave as such.
related note, setting wifi sleep to never greatly increases batteyr life, as said thru the forums, because back on 3g the data kills your battery much faster. so allowing wifi to stay on makes a huge improvement on battery.
for example if you leave wifi on overnight, you might lose 5% total. but if it switches back to 3g overnight, you might lose 20%.
is this bug confirmed?
me too have same problem with SuperAosp (i will test with other rom....)
Okay, I've been trying to diagnose a somewhat annoying issue. I've been using a fairly simple set of conditions in the Llama utility to automatically disable Wifi when the screen turns off in CM7 to prevent a wakelock condition and reduce battery drain.
So I activate wifi, I reset the log in CPU Spy, and I lock the phone disabling the screen. When I reactivate the phone and check CPU Spy, wifi was definately off but the phone was never in Deep Sleep, so something was holding the wakelock I guess. I repeat the experiment with no changes and Llama still running, but this time I manually disable wifi before locking the screen. This time the phone immediately goes into Deep Sleep according to CPU Spy-- it works perfectly.
So what is the difference between Llama autodisabling and manually disabling wifi that leaves a wakelock active? I've repeated this experiment like ten times last night, and it isn't making much sense to me.
Thanks,
Gnat
I would love an answer to this as well. I can add that with juice defender ultimate the same thing happens. It will disable the wifi but the wakelock stays active. I have tried several settings and reboots and tests and the only thing that would get my phone to deep sleep was disabling JD.
mikel81 said:
I would love an answer to this as well. I can add that with juice defender ultimate the same thing happens. It will disable the wifi but the wakelock stays active. I have tried several settings and reboots and tests and the only thing that would get my phone to deep sleep was disabling JD.
Click to expand...
Click to collapse
I can't tell whether this is the exact same, because you make it sound like JD has the wakelock. In my case, Llama is running in both tests, the only difference is whether Llama turns off Wifi or I manually toggle it-- manual toggling puts it into deep sleep even with Llama running.
On the general battery issues on Triumph, one of the more helpful discussions I've seen is this one here-- http://androidforums.com/triumph-all-things-root/456795-cm7-triumph-battery-life-improvement.html. In it a quote from Tickerguy blesses the JuiceDefender approach to throttling data use for battery savings, but I don't think he had done any analysis regarding wakelocks. BTW, I reverted to stock today, and I am finding the exact same problems as CM7-- wifi imposes a wakelock, and Llama can't shut down wifi automatically without the wakelock persisting. I have to manually toggle wifi off before screen off before the wakelock is gone.
Regards,
Gnat
gnatd said:
I can't tell whether this is the exact same, because you make it sound like JD has the wakelock. In my case, Llama is running in both tests, the only difference is whether Llama turns off Wifi or I manually toggle it-- manual toggling puts it into deep sleep even with Llama running.
Click to expand...
Click to collapse
Sorry; the wakelock is WLAN. It is almost always active if JD is toggling wifi. I hadn't tried disabling wifi manually but leaving JD active yet. I just tested that and got deep sleep immediately. So it must have something to do with how it disables wifi isn't releasing the wakelock.
You know, after switching back to stock from CM7 I'm really not sure I'm not happier. With CM7 I was getting worse battery performance, which led me to start obsessing about wakelocks and deep sleep. Now that I am back on stock, I do the same analysis and see that I have the same problems with wakelocks and deep sleep-- but the battery performance is better so it's not that big a deal. I'm sure that there are things I could do to make CM7 have better battery performance-- but I wasn't enjoying the process and wasn't finding answers, so why bother?
It's like power management programs. I ran Green Power for a long time, and had some glitchy problems with being unable to get wifi to turn on even though it wasn't supposed to be managed while the screen was on. Then I disabled it, and you know what... my battery life was good enough to get me through the day. Froyo is good enough to get me through the day.
The wakelock was put in there on purpose to prevent the phone from hanging when WiFi was on and the phone went to sleep. I use my power widget to turn off WiFi before I turned off the screen unless I'm actually using it.
You could try and build it to see if removing the wakelock is still necessary. If you need help on that side, just post and I'll help. It's not hard, really.
This topic has been up a couple of times before, perhaps most interestingly discussed in this thread.
It appears the problem still exists (asusdec_wake kernel wake), and I'm experiencing extreme battery drain during sleep with the dock attached. Currently running Cromi-X 5.4, and I have tried hunds 3.4.4, and _that 8 and 9 kernels.
It appears to behave as following: The tablet enters deep sleep with low battery drain (0.3% per hr with wifi off), and after a while (have seen it happen after a range of 1 - 5 hours) it starts draining quickly as asusdec_wake wakes the tablet up. It only occurs when the tablet is docked, it can occur at both high charge levels and when the dock is empty (mine always drains to 0%). It does not seem to matter whether wifi is on or off. I monitor the battery with better battery stats.
It's a real pity, since I have to turn the tablet off whenever I want to keep the dock attached.
Is anyone else experiencing this drain? Any suggestions for fixes?
Also: obligatory first post thanks-for-making-my-tablet-great to @sbdags, @_that and all the other contributors to Cromi :good:
rkha said:
It appears to behave as following: The tablet enters deep sleep with low battery drain (0.3% per hr with wifi off), and after a while (have seen it happen after a range of 1 - 5 hours) it starts draining quickly as asusdec_wake wakes the tablet up.
Click to expand...
Click to collapse
How do you know that it first enters deep sleep and that it's woken up later?
asusdec_wake is a wake lock which only keeps the tablet awake, so the question is what causes the wake up and keeps the wake lock?
_that said:
How do you know that it first enters deep sleep and that it's woken up later?
Click to expand...
Click to collapse
It might be a strong assumption, but it's based on the battery drain patterns I've seen. I've tried to monitor this a bit the last few days. Usually the battery drain is as expected during sleep for a while (whenever I check during this period, the asusdec_wake has not been active and the entire period the tablet has been in deep sleep), before it increases and stays high. I attach some screen shots where this can be seen. The change in slope in the battery graph is after about 7 hours. In those screen shots the deep sleep time reported by bbs was 6h24m. I'm not sure the reason for suspend_backoff, but I assume something is forcing the tablet to stay out of deep sleep. If I disconnected the tablet, there are no issues with suspend_backoff (and naturally not with asusdec_wake either).
_that said:
asusdec_wake is a wake lock which only keeps the tablet awake, so the question is what causes the wake up and keeps the wake lock?
Click to expand...
Click to collapse
Good point. Any tips on how this can be diagnosed?
rkha said:
It might be a strong assumption, but it's based on the battery drain patterns I've seen. I've tried to monitor this a bit the last few days. Usually the battery drain is as expected during sleep for a while (whenever I check during this period, the asusdec_wake has not been active and the entire period the tablet has been in deep sleep), before it increases and stays high. I attach some screen shots where this can be seen. The change in slope in the battery graph is after about 7 hours. In those screen shots the deep sleep time reported by bbs was 6h24m. I'm not sure the reason for suspend_backoff, but I assume something is forcing the tablet to stay out of deep sleep. If I disconnected the tablet, there are no issues with suspend_backoff (and naturally not with asusdec_wake either).
Good point. Any tips on how this can be diagnosed?
Click to expand...
Click to collapse
Try turning location services off completely for me in settings.
Does that help? Give it a reboot as well.
sbdags said:
Try turning location services off completely for me in settings.
Does that help? Give it a reboot as well.
Click to expand...
Click to collapse
Yes it did, thank you! 21 hours, only 3% down and asusdec_wake inactive. I will report back if things change.
Will add always turning this off when tablet screen is off to Tasker. Interesting that it caused this huge battery drain, given that gps and wifi was off anyways. Wakeups from com.google.android.gms decreased from many to nearly none when turning off location access, perhaps it is sufficient to turn of google apps location access in settings.
Thanks again!
rkha said:
Yes it did, thank you! 21 hours, only 3% down and asusdec_wake inactive. I will report back if things change.
Will add always turning this off when tablet screen is off to Tasker. Interesting that it caused this huge battery drain, given that gps and wifi was off anyways. Wakeups from com.google.android.gms decreased from many to nearly none when turning off location access, perhaps it is sufficient to turn of google apps location access in settings.
Thanks again!
Click to expand...
Click to collapse
It's Google now constantly polling for your location as far as I can tell.
Hello,
my battery only lasts half a day max, before needing a recharge. I've already tried different custom roms, and currently I'm on Blisspop for android 5.1. The area I live in has good coverage, so that shouldn't be the culprit. I never play games on my device, but even basic web browsing drains my battery very rapidly. I do use android wear, but I don't think that is the reason I only get around 1 hour of screen on time.
Here are the things I've tried already:
- Turning off location reporting
- Disabling Google Now
- Removing Google Fit
- 'recalibrating' the battery by letting it discharge and then charge it fully without unplugging
- Using 3g instead of 4g
- Turning off location access
This is driving me nuts, and I don't know if it's my battery's fault or my phone's fault.
Thanks in advance.
Go to wifi, special, and disable scanning when the wifi is off. It helps A LOT. Also keep location reporting off, as setting it to network only creates tons of wakelocks even when mobile data and wifi are turned off.
I know some custom ROMS have had issues with Bluetooth battery drain in the past. Try turning it off and see what happens.
Turn down the brightness as well. There is significant difference in power usage between %50 and %100 brightness .
Hold power button and select power off. Helps
I've had this phone for a few days now and I notice some mean battery drain that happens from time to time. I dumped a Bug Report via developer options, and used Google's Battery Historian after leaving my phone unplugged and idle overnight after a full charge and reboot. The tool seems to show that the following kernel wakeup reason seems to be the problem and holding the phone awake for over 1.5 hours:
Code:
Ranking Name Duration/Hr Count/Hr Total Duration Total Count
0 Abort:Wakeup IRQ -1111803216 (null) pending 10m8s737ms 779.87 1h34m13.62s 7243
The only thing that looks remotely relevant is that on the tool WiFi signal strength became weaker when the above wakeup events started.
Has anyone else had similar issues with random battery drains like this and/or happen to know any workarounds?
Mine seems like it is always awake. Android OS has been keeping it awake for 8-9 while I'm at work.
I tried setting wifi to stay on when sleeping when plugged in, after a full idle overnight, I used my phone in the morning and the same issue came up. The ID above was different, but generally the same problem (IRQ with no description pending). Again, it looks to be wifi related based on the battery stats in Historian. I've rebooted, charged up and turned off wifi to see if the problem goes away.
ru_ready said:
Mine seems like it is always awake. Android OS has been keeping it awake for 8-9 while I'm at work.
Click to expand...
Click to collapse
You might want to try enabling developer options and getting a bugreport generated (which has battery stats), and then visualizing it in Google's Battery Historian to see if it is the same problem. Kind of convoluted, I know, but without root, I don't know of any better way to analyze kernel wakelocks (it isn't a partial wakelock issue on my device).
Last night I left my phone idle with wifi off and WLAN Scanning and Bluetooth Scanning off under Location Settings. The battery ran down only 2% over 9 hours and the Wakeup IRQ pending problem did not keep the phone awake!
I am going to try turning wifi back on today but keep the scanning off and see if that keeps this problem at bay. If not, I may use Tasker to force wifi off when the screen is not on and not plugged in.
The wakelocks seem to happen randomly no matter what my wifi settings are. Though I do think it is related to location settings trying to use wifi scanning.
I give up, there is no reason why a phone I just bought should be like this.
Maybe there are some apk wake up the system
@kumodog Maybe there are some apk wake up the system, you can reboot the system and kill all of application programs when you test it in night with wifi on.
After test, you can also use : "adb dumpsys alarm" in command line to find Top Alarms. it will tell you which alarm make system wakeup.