Related
I'm on zeus 6.22o, my battery consuption is high, tried 6.22n but is the same and o version works better for me. I have always 3g on; in stock froyo and cm7 nightlies with 3g on and same apps and config I had better batttery life and the phone normaly went to deep sleep when I turn screen off and had considerably less wakelocks, battery graph was quite horizontal.
I have installed betterbatterystats and the problem is:
-Partial wakelocks: Datatracker-FD
-Kernel wakelock: PowerManagerService
-Alarms: com.google.android.gsf (gtalk_reconnect; gtalk_heartbeat)
They produce the most wakelocks.
I have freeze gtalk app with titanium because don't use it but it isn't the problem and waakelocks are the same.
Does anyone know how to fix it?
Thanks and sorry if my english is not good enough.
-Kernel wakelock: PowerManagerService
-Alarms: com.google.android.gsf (gtalk_reconnect; gtalk_heartbeat)
gsf = google services framework
are not causing preoccupations, these are system relevant things. A wakeup isn´t at all a bad thing. Bad is when a process begins to work an to force the cpu for a prolonged time.
-Partial wakelocks: Datatracker-FD
Try to turn fastdormancy off maybe your provider don´t support this.
All this things don’t explain a higher battery consumption.
Regards!
Thanks. I tried disable fast dormancy but it doesn't help and causes problems with data network. Awake time is about twice the screen on time and these are the only with high values in betterbatterystats. Other apps are the same I was using in stock froyo and cm7 (in both I had better battery life): go launcher, whatsapp, hotmail (never had battery problems with it), tapatalk, sygic,a few games, mjoy.
Enviado desde mi LG-P970 usando Tapatalk 2
Now I'm experimenting a huge battery drain due change WiFi policy to "never" turn off. It leads to a consumption of 4-5% per hour. Normally, with turning Wi-Fi off, there is a consumption with 3G on, of 3-5% in 8 hours.
BetterBatteryStats since unplugged:
Kernel Wakelocks: "wlan_rx_wake" 30%
Cpu-Spy reports for the same time CPU-activity from 300MHz.
Tried change Wi-Fi voltage via Zeustweaker, but doesn't seem to work. Changing 20 - 14 -10 -8 - 2, no matter in range of Wi-Fi nor in indication of the Wi-Fi symbol in the notification bar (of course switched Wi-Fi off/on after each change).
Someone an idea?
It's like some app maintains your wifi connection active long time.
In 3g my conumption is about 12% in 8 hours without use.
Enviado desde mi LG-P970 usando Tapatalk 2
Pacos1 said:
Now I'm experimenting a huge battery drain due change WiFi policy to "never" turn off. It leads to a consumption of 4-5% per hour. Normally, with turning Wi-Fi off, there is a consumption with 3G on, of 3-5% in 8 hours.
BetterBatteryStats since unplugged:
Kernel Wakelocks: "wlan_rx_wake" 30%
Cpu-Spy reports for the same time CPU-activity from 300MHz.
Tried change Wi-Fi voltage via Zeustweaker, but doesn't seem to work. Changing 20 - 14 -10 -8 - 2, no matter in range of Wi-Fi nor in indication of the Wi-Fi symbol in the notification bar (of course switched Wi-Fi off/on after each change).
Someone an idea?
Click to expand...
Click to collapse
I think that if you select "never" at the Wifi sleep policy then it actually never disconnects from Wifi, which in turn means that the phone can't enter deep sleep. At least for me it always worked that way, even on another android phone.
Thank you verszipo for your hint. The rest of the time (70%) the cpu is in deep sleep. I will try this in v10, because I think this old one is a lot better programmed than the v20.
Although wifi was always connected it doesn't mean that is always active, like with 3g when is connected but arrows aren't blue. I think it can be an app that keep wifi active or an error in wifi on v20.
Enviado desde mi LG-P970 usando Tapatalk 2
I agree with you, jes0411.
Now I can confirm, that the v10 based Nova8 have the same behaviour like the v20 based Zeus 6.22. So this not seem to be a Zeus specific issue. Maybe cause by LG´s provided code or an generally android issue?
I installed a fresh Zeus 6.23 without any app beside cpustats, betterbatterystats and of course the apps inside de Rom. Here the results with Wifi policy “never”:
CPU SPY:
Total State time (approx. values): 13h
From This: 7h 15 min deep sleep, 3h 20 min by 300MHz, 2h 8min by 600MHz, 10 min 800MHz
BETTER BATTERY STATS since unplugged (approx. values):
Kernel Wakelock:
wlan_rx_wake 4h 20min, wlan_wake 1h, PowerManagerService 8min
Other:
Wifi On, Wifi Running, No Data Connection, No or Unknown Signal: all this 13h 9min 21s
Deep Sleep 7h 15min, Awake 5h,54min, Srceen On 15min
Partial Wakelocks (all insignificant):
WifiStateTracker 3min 55s, *Wifi* 2min 51s, GTALK_ASYNC_CONN 41s, AlarmManager 37s
Alarm (also all insignificant):
com.google.android.gsf 46Wakeups, android 10wakeups, com. android.vending 1wakeup.
BATTERY CONSUMTION: 47% in 13h of inactivity: approx. 3,6% per h
RESUMING:
Wi-Fi policy “never” causes an inexplicable CPU-activity of around of 40% of the time where the phone is unused. No application seem to cause this behaviour. The CPU not only is waked up, it has to work, so that around 40% of the wakeup time the CPU operates with 600MHz.
WiFi is NOT used for Data-transfer!
CONCLUSION AND FURTHER STEPS:
This is an not acceptable behaviour!
I will freeze vending, gtalk and gmail with titanium and observe it again. I also will change the Governor to OndemandX and use a Firewall.
Stay tuned!
I have a feeling for some reason that Froyo was better from Gingerbread in terms of battery consumption,
Is it true? What are the improvements on Gingerbread?
To be honest, in battery consumption I don't see any difference between the v10 (Froyo) and v20 (GB). The only what I see as advantage in v20 is the more fluid reacting user interface.
Negative points in v20:
- Removed the led attenuation of the keys
- Removed the possibility of use key leds for call, charging, sms... notification
- No stable reconnect to WiFi with hidden SSID
- Buggy music player
Also again thank you LG (this is sarcasm).
Since publication, from now around 4 months, they haven't fix this. I fear that ICS will be the same trash.
RESULTS of testing:
Results of freezing apps vending (google play), gtalk and gmail:
none, wlan_rx_wake still in huge consumption
Result of Use Firewall: no change, wlan_rx_wake still in huge consumption
Result changing governor from Smartass to OndemandX: no change, wlan_rx....
Result of switching of my WiFi-router: Success, wlan_rx_wake doesn’t appear, battery drain in normal way (around 0,3% per h).
CONCLUSION:
This huge battery drain caused by Wi-Fi is a result of the combination of an P970 and a specific Wi-Fi routers. A Google search results that not only our device is affected, also found Samsung Galaxy S2 and Note.
SOLUTION:
Buy another router or an other not Android-based phone.
Pacos1 said:
RESULTS of testing:
Results of freezing apps vending (google play), gtalk and gmail:
none, wlan_rx_wake still in huge consumption
Result of Use Firewall: no change, wlan_rx_wake still in huge consumption
Result changing governor from Smartass to OndemandX: no change, wlan_rx....
Result of switching of my WiFi-router: Success, wlan_rx_wake doesn’t appear, battery drain in normal way (around 0,3% per h).
CONCLUSION:
This huge battery drain caused by Wi-Fi is a result of the combination of an P970 and a specific Wi-Fi routers. A Google search results that not only our device is affected, also found Samsung Galaxy S2 and Note.
SOLUTION:
Buy another router or an other not Android-based phone.
Click to expand...
Click to collapse
Hey Pacos1 (fellow Spanish here)
I dont own an Lg but I do own a Galaxy s2 and now Im having the same problem as you guys but in a veeeeeery reduced manner, those wakelogs due to the wlan are call for around 3-4 % of my battery, still good battery life altogether. The reason Im posting here is to let yo guys know that i didnt have this problem before, I didnt even see the wlan wakelogs in the list of betterbatterystats since they were so little, and this is due to a change in the kernel, which is exactly what rules the wifi behaviour, I suggest you change it and try a different one if you have the chance and youll probably experience a change.
Cheers ( y saludos)
Thanks paieneso for the hint and this is truly the solution. I tried the CM7 build78 from temasek, which comes with another kernel than the stock one (and stock derivates like Zeus) and the wlan_rx_wake issue disappeared.
(ironic mode on) So, thank you LG, once again! (ironic mode off)
But now is a new stock rom out, the Spanish v20Q, will test it if this one makes a better job.
Saludos!
PS: Sorry, I forgot this thread and also to post the “solution” of wlan_rx... .
The new stock v20Q have still the wlan_rx_wake bug!
Hi!
I just noticed that my phone does not go to deep sleep if I have wlan on. Though I do not have any long wakelocks according to BetterBatteryStats, just some minutes total while the device have been awake for much more.
Stock .534 unrooted, newly repaired with _only_ BetterBatteryStats and CPU Spy installed. No accounts added etc.
Wlan/Advanced: "Always on"
Location-based wlan: "on"
Low battery mode: "on"
STAMIN mode: "off"
Location based services "on" / "off" tested.
When I have wlan on CPU Spy reports as Deep sleep unused, and instead most of the time is spent in 300 MHz.
Any of you that can reproduce?
Have the same problem. Is that normal that it doesnt goes to deep sleep ?
muslim187 said:
Have the same problem. Is that normal that it doesnt goes to deep sleep ?
Click to expand...
Click to collapse
No, it's absolutely not normal. Something is keeping the device awake, probably a bug.
I left the device over night,
wlan kernel wakelock for 7h, but no long-standing partial wakelocks. I don't get it, how can something keep wifi awake without actually issuing a wakelock?
Bah I have suddenly been afflicted with this issue since yesterday. Noticed battery drain from 100% to 33% with minimal use between this morning and lunchtime while at work. Currently it is charging off my laptop but only holding its own, not increasing. Only had it a week, very little installed on it.
Battery life was fine for the first week of ownership, today it lost 75% with little or no use in 5 hours, then it did not charge when connected by USB to laptop it merely held the same charge, before quickly discharging again when disconnected.
No deep sleep all day
https://www.dropbox.com/s/b19ixx16dgnqrcb/2013-10-07 17.46.20.png
Inquitus said:
Battery life was fine for the first week of ownership, today it lost 75% with little or no use in 5 hours, then it did not charge when connected by USB to laptop it merely held the same charge, before quickly discharging again when disconnected.
No deep sleep all day
https://www.dropbox.com/s/b19ixx16dgnqrcb/2013-10-07 17.46.20.png
Click to expand...
Click to collapse
Hi, can you please verify that you indeed do not have any wakelocks caused by any other third-party programs you have installed? Just to knwo that we are in fact experiencing the same issue. You could also try to disable wlan (and mobile data (I haven't tested to turn that on, as I do not yet have a data plan).
The application needed to test that is Better Battery Stats, available here on XDA (or on Play): http://forum.xda-developers.com/showthread.php?t=1179809
Exry said:
Hi, can you please verify that you indeed do not have any wakelocks caused by any other third-party programs you have installed? Just to knwo that we are in fact experiencing the same issue. You could also try to disable wlan (and mobile data (I haven't tested to turn that on, as I do not yet have a data plan).
The application needed to test that is Better Battery Stats, available here on XDA (or on Play): http://forum.xda-developers.com/showthread.php?t=1179809
Click to expand...
Click to collapse
Today's issue on my phone was driven by several hours of a "bam_dmux wakelock."
edit: and no partial wakelocks so no idea of the driver.
Inquitus said:
Today's issue on my phone was driven by several hours of a "bam_dmux wakelock."
edit: and no partial wakelocks so no idea of the driver.
Click to expand...
Click to collapse
Ok. So it might be the same issue then, though I don't really know what the "bam_dmux" wakelock is.
FYI Mine is back to normal today. Lost 3% in 3 hours of light use. Only thing I have changed is I deleted a Wifi network from my preferred list that the phone was having trouble connecting to, may or may not be related.
I have a question about wake lock and msm_hsic_host
I'm noticing that it definitely in my wakelock bbs. But it only goes up when I have the screen on and using it for the most part.* So my question is, is this ok?* Or should I have no wake lock or msm_hsic_host should not be on for that long?
I'm also curious because this wakelock is crazy high for me
noob4598 said:
I'm also curious because this wakelock is crazy high for me
Click to expand...
Click to collapse
Have you tried to go on plane mode and see if that wakelock goes off? Because when I do that it does go off. I believe is data related. But even when I use WiFi and turn mobile data off that still runs... Lmk
MadTechnique said:
I have a question about wake lock and msm_hsic_host
Click to expand...
Click to collapse
A quick Google search found this, posted at XDA: http://forum.xda-developers.com/nexus-4/help/msmhsichost-wakelock-battery-life-t2155461
"The msm_hsic_host wakelock is because the 3G modem is connected to the phone as an external USB device controlled by the hsic host controller. When the modem wakes up for any reason (apps sync, location, tower ping, etc...) the wakelock is requested. The problem is that the hsic host controller doesn't go back into suspend mode properly, this is a problem with the kernel. The result is that because the hsic host controller isn't asleep the phone wont enter deep sleep while it waits for the hsic host to suspend.
There is the additional issue that if your signal is poor the operations that caused the wakelock in the first place take longer to complete thus lengthening the time the wakelock is held.
The issue is significantly reduced on WiFi for obvious reasons, all the data is transmitted via WiFi so the 3G modem doesn't need to wake up nearly as often, it still wakes up to deal with tower checks and that sort of thing to ensure that it has voice connectivity, but those events are much rarer.
There are kernels available that attempt to solve this problem, Harsh kernel as suggested by another user has fixes in it along with a lot of other changes, the fixed kernel I'm working on is stock with these changes as well, either should help, it's not possible to eliminate this wakelock completely without shutting down the 3G modem which would of course prevent data and voice use of the phone, but they will reduce the wakelock and may help with your battery life."
Some kernels address the problem. Some don't. Just Google the wakelock. Lots of info on it.
Pinan said:
A quick Google search found this, posted at XDA: http://forum.xda-developers.com/nexus-4/help/msmhsichost-wakelock-battery-life-t2155461
"The msm_hsic_host wakelock is because the 3G modem is connected to the phone as an external USB device controlled by the hsic host controller. When the modem wakes up for any reason (apps sync, location, tower ping, etc...) the wakelock is requested. The problem is that the hsic host controller doesn't go back into suspend mode properly, this is a problem with the kernel. The result is that because the hsic host controller isn't asleep the phone wont enter deep sleep while it waits for the hsic host to suspend.
There is the additional issue that if your signal is poor the operations that caused the wakelock in the first place take longer to complete thus lengthening the time the wakelock is held.
The issue is significantly reduced on WiFi for obvious reasons, all the data is transmitted via WiFi so the 3G modem doesn't need to wake up nearly as often, it still wakes up to deal with tower checks and that sort of thing to ensure that it has voice connectivity, but those events are much rarer.
There are kernels available that attempt to solve this problem, Harsh kernel as suggested by another user has fixes in it along with a lot of other changes, the fixed kernel I'm working on is stock with these changes as well, either should help, it's not possible to eliminate this wakelock completely without shutting down the 3G modem which would of course prevent data and voice use of the phone, but they will reduce the wakelock and may help with your battery life."
Some kernels address the problem. Some don't. Just Google the wakelock. Lots of info on it.
Click to expand...
Click to collapse
I read that before posting and Google it. My question is that I see the wakelock running when the screen is on and used. But when I lock the Oh one it stops running. What I wanna know is. Is this how. It suppose to be? Because it goes on for hoursfor obvious reasons. Also I get the same. Result when I use WiFi. I also have 4g lte if that helps.
I'm suffering from excessive battery drains on Note 8, Nougat 7.1.1. The battery drain is excessive when on idle mode/when the phone is asleep. I have installed BetterBatteryStats (gave it all permissions) and tested with different settings for a couple days.
My findings:
I strongly believe the issue is with my wifi.
Day 1: I kept wifi on, turned off "adaptive wifi" and "wifi power saving mode" and set "keep wifi on during sleep" to always. Battery drain was very excessive at home. In BBS, wlan_rx_wake and powermanagerservice.wakelocks were very high and phone didn't doze much. When I left home and went to the library and was connected to my school's wifi, the phone dozed, and the two wakelocks mentioned didn't occur any more. In fact, from the screenshot you can see the two flat regions are those when I was at the library, and the downhill regions are when I was home.
Day 2: I kept wifi on, turned on "adaptive wifi" and "wifi power saving mode" and set "keep wifi on during sleep" to never. No change. The results were just like day 1. Excessive wakelocks and battery drain. In fact, funny enough, the wakelocks occurred more often as if "wifi power saving mode" was doing the opposite of what it was supposed to.
Day 3: I turned off wifi completely, and was on cellular the whole time. Battery performance was amazing. Lost 5% over 10 hours, and I actually used the phone during this time. I made calls, surfed the web and texted. Additionally, the are no excessive wakelocks, and the battery plot is nearly flat the whole time.
In conclusion, I am really confused. At home, wifi kills my battery. At school, wifi doesn't do anything weird. It makes me feel like this is more than just some setting on the phone or some bug with Nougat. Maybe some networking issues with my wifi at home? I was hoping I could better understand my situation by getting help here. Any feedback is welcome. I have screenshots from each day so tell me if you think they'll be helpful. Thanks.
Make a factory reset... try that, it makes my stars better.
Could very well be caused by Wifi calling. Try switch off Wi-Fi Calling at home.
I remember having this issue in past with my Note 5 icw bad Cell reception at certain locations.
But wifi calling is always on, regardless of what wifi I'm connected to. It must be something specific to my wifi at home.
I have a suspicion that broadcasts from my Google Home/Chromecast devices are causing my Pixel 2 to come out of deep sleep frequently to briefly process the broadcasts. This is experienced as approaching 3x normal battery discharge rate on the phone over night or when it's not being used. Normally it's around 0.6%/hr, with Google Home devices/Chromecast on it can be over 2%/hr
Some basic testing and a little rhetoric I found Googling seems to suggest this. I have no battery problems with phone on my router's guest network or with all the Google Home devices unpowered with the phone on the main network. All Google Home related apps on the phone are force closed.
Anyone else seen/noticed this?