Could not understand why my new device was burning through it's battery like it was a desktop computer. I can't remember where but I stumbled across the application OS monitor and took a look to see anything untoward.
Well I have an exchange email server that I use to sync all my contacts/calendar and emails.
It would appear that the inbuilt google mail app tends to CONSTANTLY drain power whilst it is set up, I did have push mail activated and it was set to do background data et al.
Removing this has fixed my battery drain issue and I'm now using Touchdown to manage my email exchange, with push mail activated and having no such problems at all!
I'm not suggesting that everyone switches to Touchdown but it is definitely worth trying a different client if you are having problems with poor battery performance!
Hope this helps someone as it was REALLY beginning to annoy me, not even lasting a night out!
Did Google show up under your battery use?
hah2110 said:
Did Google show up under your battery use?
Click to expand...
Click to collapse
Not quite sure what you mean? OS monitor showed the system using a few resources every now and again but mail was using 30-40% almost constantly draining the battery!
Also found that leaving WIFI enabled uses VERY little battery and so I've kept that alive so that the current mail app I'm using doesn't poll and get no connection all the time (personally what I think was happening is due to me living in the middle of nowhere there was no signal and so it kept polling until it could find a signal which was using up resources).
I was searching around for solutions to help me with my massive battery drain in CM10 A4 for these 2 days and I realised little emphasis had been put on "wakelocks" in our i9003 forums; so I thought some discussion here would be nice to help all of us, especially relatively new people like me.
A detailed explanation can be found in ahalford's thread; and also in the XDA wiki. Below is just what I managed to sort out for our device, specifically CM10 A4 (not sure about applicability in other ROMs).
Wakelocks are identifiable via BetterBatteryStats and I would like to mention a few of them that I could identify (and if possible, solve). My purpose here is just to share some info that I managed to find and if possible provide some guide based on my own experience.
In CM10 A4, I uninstalled:
Google Search
Google Maps
News & weather
Google Backup Transport
CM Wallpapers
Android Live Wallpapers and its associated LWPs
Spare Parts
GTalk
Movie Studio
Certificate Installer
Wakelocks identified:
1. RILJ
Easiest way to solve: Flash the fixed kernel by loSconosciuto. Personally tested it on CM10A4, and SlimBean v3.1; both worked. Just screen off/on and the signals will return.
Alternatively, put the phone to Airplane Mode (I left my WiFi on), reboot. Then leave it to screen off for some minutes, and turn off the Airplane Mode. The signal bars may not return as of yet; so just DC and reconnect the WiFi. Signal bars return, RILJ stopped. :victory:
2. GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice UNSOLVED
Attempts: Removed GTalk (but problem persisted); Auto-Sync off; and disabled location settings.
Also worth to mention it occurred only when WiFi was on; didn't test it on mobile data (I don't have one).
Attempts of freezing apps: (Still investigating)
Search Application Provider
Network Location
com.android.backupconfirm
Google xxxx Sync (Contacts, Calendar, etc)
* Others recommended to sign out from Google account, and re-add (but I have no experience on this).
* Also somebody was talking about disabling GTalk-related services in Google Framework Services using Autorun Manager (or similar); but it didn't work for me.
3. AudioOut_2
Perhaps not a wakelock. If the time matches time of you opening any games/app that produce sound; it should be normal and should stop after exiting application.
* Saw a thread that this may happen if the app did not exit properly (e.g. here)
Any input/discussion would be greatly appreciated.
Will update more whenever I have time! Thanks!
cheeyeen said:
2. GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice[/B]
Solution: Removed GTalk (but problem persisted). Stopped it by freezing a few apps via TitaniumBackup but the exact way to do it is still unknown, currently trying to rule out the below one by one.
Click to expand...
Click to collapse
I think for 2nd wakeclocks you have to turnoff Auto-sync from setting.Double check your setting.Though there is not perticular button to turnoff Autosync in CM10 you have to use widgets to turnoff autosync.
And go to Play store settings disable all tick.That may be solve second one.
nicsptl said:
I think for 2nd wakeclocks you have to turnoff Auto-sync from setting.Double check your setting.Though there is not perticular button to turnoff Autosync in CM10 you have to use widgets to turnoff autosync.
And go to Play store settings disable all tick.That may be solve second one.
Click to expand...
Click to collapse
Thanks. Actually it was solved, but I forgot to mention that. I just didn't know how it went solving lol :laugh: And yeah, Auto Sync off via power buttons in notification drawer and verified from the account settings.
I checked the amount of data I was using today and it was using crazy amounts. I have auto-sync disabled and restricted background data on for Google Services, although I think that only affects mobile data. This has been going on for over a week unnoticed.
So I saw that and restarted my phone hoping it will fix it but it didn't, So I checked my battery to see what app is using the most battery and it was Mediaserver which was using 43% (although I didn't have a battery problem until yesterday).
Here's screenshots: imgur.com/iz9HtZw, imgur.com/fzzreZo
(Sorry the forum won't let me post outside links so imgur will have to be copied and pasted)
Anyone else ever seen this before? I'm thinking of just reformatting the phone if there are no solutions but would rather not.
bizarrejelly5 said:
I checked the amount of data I was using today and it was using crazy amounts. I have auto-sync disabled and restricted background data on for Google Services, although I think that only affects mobile data. This has been going on for over a week unnoticed.
So I saw that and restarted my phone hoping it will fix it but it didn't, So I checked my battery to see what app is using the most battery and it was Mediaserver which was using 43% (although I didn't have a battery problem until yesterday).
Here's screenshots: imgur.com/iz9HtZw, imgur.com/fzzreZo
(Sorry the forum won't let me post outside links so imgur will have to be copied and pasted)
Anyone else ever seen this before? I'm thinking of just reformatting the phone if there are no solutions but would rather not.
Click to expand...
Click to collapse
In my case, Its usually playstore that consumes the most insane data over wifi (auto updates). also location (GPS) services. you'll need to check those out.
As for your battery, consider using greenify to put a leash on rogue apps and processes.
consider reading these two articles to further help fix these two isses
* How to make an Android phone’s battery last longer
* How to solve the problem of heavy data consumption in iPhone, iPad and Android Smartphones / Tablets
Ever since the 5.1 OTA (Or Google Services 7.0.99, I'm not sure), I've been experiencing bad battery life.
I downloaded Better Battery Stats and Wakelock Detector to try to find the culprit and this is what I've found.
- Connected to my wifi at home my Nexus 5 sleeps just fine.
- At work (wifi) I'm having a lot of wlan_rx and wlan_wd wakelocks and high awaken times due to this.
- When on mobile data it all gets worse: I'm getting hundreds of instances of RILJ wakelock in a matter of minutes, and sometimes Gmail often appears first on the list with high wakelock counts and times. Google+ and Keep also make frequent appearances I'm Wakelock Detector
- BBS ALWAYS shows bam_dmux_wakelock as the main culprit and sometimes sensor_ind (on mobile data), but I don't know what to make of that, since WD shows other things (RILJ etc).
Regarding RILJ: almost everything I've found online says that it has something to do with network location and that turning off location history removes it, but I rarely have location services on (GPS or network location) and location history is off anyway. I've tried disabled NetworkLocationService and every other service regarding location using disable service to no avail. It doesn't seem to happen when the phone is in 2G only.
Gmail frequently shows up in WD with high counts and times, I've seen Keep and Google+ in there too, first on lists. I've disabled them both for now.
In the battery stats the activity bars doesn't seem to be all that different from the screen on bars, but both WD and BBS show high awake times (sometimes as high as +20%). This is when on mobile data or connected to the wifi at work (wifi at home is just fine).
I tried downgrading to 5.0.1 (there now), installing Google Services 7.3.29, disabling a bunch of services, but nothing helps.
Google Services shows up as using more energy than anything else, sometimes even more than the screen, but only when mobile data is enable, it doesn't use energy when on wifi. There's no high data traffic as some people is experiencing with 7.X versions. The wlan wakelocks are awful at work though. So there are like several, independent problems.
I'd appreciate any insight on this matter. I don't seem to be the only one experiencing this.
I'm leaving a few screen shots. I'll post BBS screenshot by the end of the day.
Did you solve this? Nobody seems to know what really is RILJ.. If I restrict it to "7200" (2 hours) at Amplify it's safe to receive calls/sms ???
Luckzzz said:
Did you solve this? Nobody seems to know what really is RILJ.. If I restrict it to "7200" (2 hours) at Amplify it's safe to receive calls/sms ???
Click to expand...
Click to collapse
Easy way to find out is to test it. Restrict and then phone/text yourself from another phone. Test periodically until you're comfortable with the results.
I've having troubles with this from some months ago now. It dissapeared at some time, but it's back again.
Anyway, in my case, the problem happen when i'm connected to a WIFI network, with mobile data activated. If I deactivate it, everything is just fine. Don't really know what is causing this, but at least I discovered my problem.
Hope this help someone else.
Cheers
Two weeks felt like two years when my phone suddenly started acting odd. High CPU usage, 2x battery drain compared to before, phone heating up while doing simple tasks drove me insane. I thought there might be something wrong with the phone but couldn't find anything so I sent it to the customer service center. All they did was factory reset, installed the latest stock OS, and sent it back which didn't solve my issue.
So I rooted the phone, installed a custom ROM and the problem was still there. I lost the tiny bit of hope I had left and concluded that it's a hardware issue and I might have to buy a new device. Two days later I installed the Better Battery Stats app and kept my phone idle overnight with wifi on.
The next day I finally found out what's been eating my battery. In BBS under Kernel wake-locks, I saw qcom_rx_wakelock was on for 8 straight hours, as long as my wifi was on. Checked the CPU states on the FK Kernel manager and found out the phone never went to deep sleep, not for a second! Also, there was that idle wifi usage.
So I downloaded the Network Log app and kept logging on the next night. 9 hours passed, none of my apps used the internet but the kernel used almost 500 mbs in 9 hours! So that's where my wakelock was coming from.
I went to my friend's house and used his wifi for a few hours to identify what's going on and I was surprised to see there was no battery drain, low CPU usage, and zero idle wifi usage. For a moment there everything seemed to went back to normal. When I came back to the school dormitory the nightmare started again.
I started scouring on the internet and I found this which led me to this terrific post!
This comment explains everything!
To summarize, the phone was going crazy because of wifi multicast, and arp flooding. I couldn't do anything about it as I was in the university's public wifi. You can disable multicast by going to the router page and turning off wifi multicast from IGMP snooping setting. But it was impossible for me cause school won't allow me to change anything and even if I complain they won't care.
So I decided to fix it by adding some of the Pixel 3's WCNSS_qcom_cfg.ini properties to my phone's WCNSS_qcom_cfg.ini which I located in the vendor/etc/wifi/ as r/skanadian recommended in the second post which took my qcom_rx wakelock to 19%, way less compared to 86% before.
This is a step-by-step guide to reducing battery drain -
• Backup your phone's WCNSS_qcom_cfg.ini in case something go wrong. I found it in system/vendor/etc/wifi/here
It might be different for you depending on what Rom or device you are using. The filename will be the same but the location might be different.
• Get a text editor. Mixplorer is recommended as it helps to search properties quickly with its find feature.
• Open your devices WCNSS_qcom_cfg.ini using Mixplorer and keep it open. Alternatively, you can copy it to a different folder on your phone. I suggest the second one cause it's better than directly editing the file from the system.
• Go to this page
• Go to your browser option and select find in page to search. Search for the word "offload" on that page.
• Copy all the lines related to offload one by one and replace them on your devices WCNSS_qcom_cfg.ini that you opened using Mixplorer.
• If there isn't anything to replace simply add those lines. Don't forget to hit the save button while doing that.
• After that, search for these properties on your WCNSS_qcom_cfg.ini and set them as I did below
RoamRssiDiff=3
g11dSupportEnabled=0
gEnablePowerSaveOffload=5
gRuntimePM=1
RTSThreshold=1048576
gMCAddrListEnable=1
gActiveMaxChannelTime=40
gActiveMinChannelTime=20
gMaxConcurrentActiveSessions=2
If you don't see one of these to replace in your WCNSS_qcom_cfg.ini you should add it.
• Now reboot your phone, give it some time and see if the battery improves. If everything remains the same then go to WCNSS_qcom_cfg.ini using Mixplorer again, find BandCapability, and set it like this -
BandCapability=1
It will disable 5ghz from your phone. I found out most companies release their phones with bad wifi drivers which don't handle the 5ghz wifi band appropriately. Lack of power-saving and not blocking multicast requests properly leads to higher CPU usage and bad battery life.
Again you can set the BandCapability=2 if you want to use 5ghz mode only. If you have a good wifi driver, the battery drain might come from switching between 2.5 and 5ghz so keeping on one of them helps.
• Why qcom_rx wakelock and what is the best fix?
It can occur for several reasons.
- Wifi multicasting. Multicasting can be disabled from IGMP snooping on router settings. You don't need multicasting in your home network at all. But when you're on office wifi or school wifi, it does improve the speed slightly by reducing data loss and interference. It also can be solved the same way but if your school management is like mine, then they might not care if your laptop or phone burns.
- DHCP timers
- A software bug from server-side
- Band switching
- Even interference, if you have a public network with a lot of phones and PCs
There are some more reasons I can not remember now. The best way to fix it is to build a custom kernel with WLAN and qcom_rx blockers/limiters e.g. Franko Kernel.
But sadly a lot of us will never have that unless we make a kernel for ourselves. So as of now, this is the solution I could come up with.
My knowledge of this sector is very little. It would be great if you all could help me get rid of this problem.
I would love it if there was a feature built-in on Android OS to block some kernel wake-locks.
OnePlus phones allow you to turn off multicasting from Developer Options but that makes little to no difference depending on what wifi you are using.
• Very Important :
Depending on you wifi, you can try setting hostArpOffload=0 and hostNsOffload=0
or you can try setting both to 1. Use whichever improves the battery backup. Don't forget to reboot after changing anything.
If you are an expert, please help us. Cause these wakelocks aren't going anywhere. They will give some of us many more sleepless nights.
Thank you for reading. Have a good day!
For those who don't want to change settings they don't understand:
RoamRssiDiff: The difference in signal strength required before phone will switch to a new Access Point. Measured in -dbs. 3 means it will switch APs if the signal strength is 3dbs better than the one in use.
g11dSupportEnabled: WIFI 802.11d
gEnablePowerSaveOffload: Level of Powersave
gRuntimePM: Runtime Powermanagement
RTSThreshold: How long to wait before asking to send wifi packets. Should be as high as possible, only lowered if you have wifi dropouts.
gMCAddrListEnable=1: Drops all Multicast frames except for ARP. You don't want to disable ARP entirely or your internet will break, so don't lower this to 0.
gActiveMaxChannelTime: Time spent scanning.
gActiveMinChannelTime: Ditto
gMaxConcurrentActiveSessions: Self-explanatory
While looking this up I also found gNeighborLookupThreshold or RoamLowRssiThreshold: The signal strength at which the phone starts looking for a new AP (the step before RoamRssiDiff becomes relevant). Typical values are 65-80. Changing this might help too if your phone is switching AP too often or not often enough.
Thanks for this, my device was also affected by this (though not as badly as yours) I've just disabled Multicast from my router.
TrenchFullOfSlime said:
For those who don't want to change settings they don't understand:
RoamRssiDiff: The difference in signal strength required before phone will switch to a new Access Point. Measured in -dbs. 3 means it will switch APs if the signal strength is 3dbs better than the one in use.
g11dSupportEnabled: WIFI 802.11d
gEnablePowerSaveOffload: Level of Powersave
gRuntimePM: Runtime Powermanagement
RTSThreshold: How long to wait before asking to send wifi packets. Should be as high as possible, only lowered if you have wifi dropouts.
gMCAddrListEnable=1: Drops all Multicast frames except for ARP. You don't want to disable ARP entirely or your internet will break, so don't lower this to 0.
gActiveMaxChannelTime: Time spent scanning.
gActiveMinChannelTime: Ditto
gMaxConcurrentActiveSessions: Self-explanatory
While looking this up I also found gNeighborLookupThreshold or RoamLowRssiThreshold: The signal strength at which the phone starts looking for a new AP (the step before RoamRssiDiff becomes relevant). Typical values are 65-80. Changing this might help too if your phone is switching AP too often or not often enough.
Click to expand...
Click to collapse
Cool!
There are some other wakelocks that's bothering me more than qcom_rx and I have no idea what they are!
Could you please tell?
Mario3DS said:
Thanks for this, my device was also affected by this (though not as badly as yours) I've just disabled Multicast from my router.
Click to expand...
Click to collapse
Sadly I'm on school wifi and can't do anything about it!
lpass is a Qualcomm audio subsystem for things like voice based wakeup, and IPCRTR (inter-process communication router) is just how different processes on your phone communicate with each other.
Others have reported these wakelocks too, almost always when they have a wifi/cell connection. Maybe it has to do with voice assistants communicating with their home servers?
TrenchFullOfSlime said:
lpass is a Qualcomm audio subsystem for things like voice based wakeup, and IPCRTR (inter-process communication router) is just how different processes on your phone communicate with each other.
Others have reported these wakelocks too, almost always when they have a wifi/cell connection. Maybe it has to do with voice assistants communicating with their home servers?
Click to expand...
Click to collapse
Well
I asked a kernel dev and he gave exactly the same explanation you gave me. He also said these are necessary and doesn't drain battery too much.
I am on a custom kernel now and wlan, qcom_rx wls are gone.
Thanks for the help
With the new kernel, I'm not seeing Lpass wakelocks much. They are there but limited.
TrenchFullOfSlime said:
lpass is a Qualcomm audio subsystem for things like voice based wakeup, and IPCRTR (inter-process communication router) is just how different processes on your phone communicate with each other.
Others have reported these wakelocks too, almost always when they have a wifi/cell connection. Maybe it has to do with voice assistants communicating with their home servers?
Click to expand...
Click to collapse
I see you've gained quite some knowledge regarding wakelocks. Your explanation was simple and easy to grasp. Could you please guide me to a thread where I can learn more about it?
Thank you so much
I just googled all the terms. Qualcomm publishes some of its stuff (source code and .ini files) with comments, others were referenced in AOSP sources.
Thanks for posting this, with my pixel 4a setting "hostArpOffload" to 0 solved it. NETLINK wakelok are much less and no battery drain.
Although on onePlus 7 pro which I've rooted few days ago none of this is working and NETLINK wakelok is draining battery at 2-3% per hr.
I'll try flashing a different ROM and If found any fix will post it here.
Device1 : Pixel 4a | LineageOS 18.1 | microG
Device2 : OnePlus 7pro | LineageOS 18.1 | microG
Edit : There are many multicast requests and NETBIOS requests too and looks like NETBIOS requests are coming from all the windows machines which are connected via Access point.
Edit:
Tried packet capture and Router is just flooding network with Multicast and ARP traffic.
I'm in the same situation as you since I live in University Campus so no router access, Have no idea how to solve this now.
A viable option is maybe buy your own router then use it as an extender and block all these garbage requests but no idea in extender mode will you be able to block stuff or not.
seated_singer said:
Thanks for posting this, with my pixel 4a setting "hostArpOffload" to 0 solved it. NETLINK wakelok are much less and no battery drain.
Although on onePlus 7 pro which I've rooted few days ago none of this is working and NETLINK wakelok is draining battery at 2-3% per hr.
I'll try flashing a different ROM and If found any fix will post it here.
Device1 : Pixel 4a | LineageOS 18.1 | microG
Device2 : OnePlus 7pro | LineageOS 18.1 | microG
Edit : There are many multicast requests and NETBIOS requests too and looks like NETBIOS requests are coming from all the windows machines which are connected via Access point.
Edit:
Tried packet capture and Router is just flooding network with Multicast and ARP traffic.
I'm in the same situation as you since I live in University Campus so no router access, Have no idea how to solve this now.
A viable option is maybe buy your own router then use it as an extender and block all these garbage requests but no idea in extender mode will you be able to block stuff or not.
Click to expand...
Click to collapse
OP 7 pro is the device you mentioned? I think it has custom kernels with bult in wakelock blockers that automatically blocks wlan, netlink and qcom rx.
Edit: Netlink can be blocked by using Custom kernel others wakelocks are due to ARP network flood. Turning it off from WCNSS_qcom_cfg or blocking introduces another problem of few seconds delay in connection ( due to ARP Resolving issue ) when switching from one access point to another ( only when automatic ) and since I do it quite often when roaming my University campus it's a hassle.
One way to mitigate this ( if you need to keep ARP offloading off ) is by using static IP, worked for me and my roommate too, but not viable since you need root. Finally I have set up my own router, checked and there were no wakelock.
Few of my friends are also facing this battery drain issue not on all Access points but some maybe after complaining authority will fix this.
Note : Netlink is only showing on Android 11/12 with other versions there are other wakelocks.
seated_singer said:
Netlink can't be blocked nor does it show since It's a part of kernel itself, here now about other two they are due to ARP network flood. Turning it off from WCNSS_qcom_cfg or blocking introduces another problem of few seconds delay in connection ( due to ARP Resolving issue ) when switching from one access point to another ( only when automatic ) and since I do it quite often when roaming my University campus it's a hassle.
One way to mitigate this ( if you need to keep ARP offloading off ) is by using static IP, worked for me and my roommate too, but not viable since you need root. Finally I have set up my own router, checked and there were no wakelock.
Few of my friends are also facing this battery drain issue not on all Access points but some maybe after complaining authority will fix this.
Note : Netlink is only showing on Android 11/12 with other versions there are other wakelocks.
Click to expand...
Click to collapse
I have NetLink blocked from kernel.
Some of this problems are impossible to fix from phone. So I contacted school management. They didn't believe me at first then I went to the head office and showed them with Network Log app that records every single packet.
A week later they fixed it. Contact your authority and see if it helps.
Thanks for the info mate, edited. Never thought I have to deal with this stupid WiFi problem.
RyanCr7 said:
Two weeks felt like two years when my phone suddenly started acting odd. High CPU usage, 2x battery drain compared to before, phone heating up while doing simple tasks drove me insane. I thought there might be something wrong with the phone but couldn't find anything so I sent it to the customer service center. All they did was factory reset, installed the latest stock OS, and sent it back which didn't solve my issue.
Thank you for reading. Have a good day!
Click to expand...
Click to collapse
Thanks for sharing, same thing happened to me..
Reading this post and turning off Multicast on both my wifi APs worked!
Just wanted to say that following this advice with all the Offload parameters, my wifi wakelocks have pretty much vanished so far on my nexus 4, i was getting something like 14000 wakelocks in battery guru. Thank you.
I can't understand why they don't specify what commands work for what Qualcomm chipset, since even though that is a newer phone, they still work on an older WiFi chipset, I've been mixing and matching for years.
KitsuneFoxy said:
Just wanted to say that following this advice with all the Offload parameters, my wifi wakelocks have pretty much vanished so far on my nexus 4, i was getting something like 14000 wakelocks in battery guru. Thank you.
I can't understand why they don't specify what commands work for what Qualcomm chipset, since even though that is a newer phone, they still work on an older WiFi chipset, I've been mixing and matching for years.
Click to expand...
Click to collapse
I'm glad it worked for you.