Hey guys,
have you noticed that your device uses up a lot more battery on certain wifi networks (e.g. at work or university)? It is probably caused by the wlan_rx_wake wakelock.
From the wakelocks database:
Rationale: Wifi chip received a packet from somewhere - On a Galaxy S II, lots of these combined with the fact that the device takes 650 msec to resume from suspend and 150 to go back to sleep means that occasional wifi packets coming in will skyrocket Android OS usage. As an extreme example, run the following from a Linux box when wifi sleep policy is "never" and watch your deep sleep percentages plummet, your battery drain, and Android OS skyrocket: ping -i 5 <wifi IP address of phone>
Know actions: Use a sniffer to determine the cause of the traffic.
Click to expand...
Click to collapse
So apparently some other device in the network keeps waking up the Nexus. If the problem occurs in your home network you can easily find out which device is causing the problem by using Shark and Wireshark. You'll get a log that shows every network activity.
Here are some tips from a similiar thread at the SGSII-forums (thanks!):
use a static IP instead of DHCP (you may have to set a static IP every time you sign up in that particular network)
disable IPv6 protocol on your phone - see below
update your router firmware
buy a gaming adapter for your Wifi network that gets the DHCP IP adress, but gives your phone a static IP
optimise router settings: click
Windows network is causing the problem - solution here: click
Change wireless network encryption method, change wifi channel, instead of using auto baseband use only 2.4 or 5GHz baseband (Wi - Fi - advanced - Wi - Fi frequency band)
turn off uPNP in router/AP
t urn off netbios in windows network ("Go to Network and Sharing Center then change adapter settings. Right click on your wireless and select Properties.
Click on the ipv4 and then the properties button. Select Advanced, go to the Wins tab and disable tcp over netbios.")
Thoravukk FAQ tells you: Q. My device not entering deep sleep if i use Wifi?
A: That's not a Kernel issue! It's a Router and (Windows 7) Network problem. Disable IPv6, IP Helper service, shell hardware detection service and the Windows Media Player Network Sharing Service. Source: here
Other apps and devices that can cause the wakelock:
TP Link routers: disable the print server in USB settings
Asus routers: disable AiCloud
disable Dropbox Lan Sync
disable wireless on (HP) printers
disable Canon network scan utility.
Using another kernel might also help to solve this problem: but I haven't tried that yet.
Try out the Franco kernel: http://forum.xda-developers.com/showthread.php?t=2508284
He has merged some wifi driver patches which should adress this problem. It reduced the wakelocks for me to 1 min in over 8 hours on my home network and to 3 min in one hour ony my university network!
So it should be possible to get rid of this problem in your home network.
But what about work or university networks? There are even more devices connected so the problem gets even worse. In Europe we have the Eduroam wifi network at many universities. If I'm connected to this network I get about 20 min wakeup time in one hour. There are a lot of ARP, DHCP and IPv6 request from different sources. Unfortunately you can't change anything about the configuration on your university/school/work network, so we need to find a solution to block these requests on our phone.
A solution for the IPv6 requests might be to disable IPv6 on your phone if you don't use it. In terminal:
Code:
echo 1 > /proc/sys/net/ipv6/conf/wlan0/disable_ipv6
Change the 1 to a 0 if you want to reactivate IPv6. Android resets this setting every time you connect to a network, so you might try Tasker to do this.
I still haven't found a solution for the ARP and DHCP requests though. Any help or input would be appreciated.
Thanks
edit (05/14/14): updated OP with other tips you mentioned
Thanks, this was a useful post. When I am at work on their wifi my phone doesn't go to sleep and definitely drains the battery quickly. Hopefully a better solution can be found.
laxor said:
Hey guys,
have you noticed that your device uses up a lot more battery on certain wifi networks (e.g. at work or university)? It is probably caused by the wlan_rx_wake wakelock.
From the wakelocks database:
So apparently some other device in the network keeps waking up the Nexus. If the problem occurs in your home network you can easily find out which device is causing the problem by using Shark and Wireshark. You'll get a log that shows every network activity.
Here are some tips from a similiar thread at the URL="http://forum.xda-developers.com/showthread.php?t=2133176"] SGSII-forums[/URL] (thanks!):
use a static IP instead of DHCP (you may have to set a static IP every time you sign up in that particular network)
disable IPv6 protocol on your phone (Dorimanx kernels have an option for this in ST tweaks or you can use "Android Firewall" for this
update your router firmware
buy a gaming adapter for your Wifi network that gets the DHCP IP adress, but gives your phone a static IP
optimise router settings: click
Windows network is causing the problem - solution here: click
Change wireless network encryption method, change wifi channel, instead of using auto baseband use only 2.4 or 5GHz baseband (Wi - Fi - advanced - Wi - Fi frequency band)
turn off uPNP in router/AP
t urn off netbios in windows network
Thoravukk FAQ tells you: Q. My device not entering deep sleep if i use Wifi?
A: That's not a Kernel issue! It's a Router and (Windows 7) Network problem. Disable IPv6, IP Helper service, shell hardware detection service and the Windows Media Player Network Sharing Service. Source: here
Other apps and devices that can cause the wakelock:
Dropbox Lan Sync, (HP) Wireless printer, Canon network scan utility.
Using another kernel might also help to solve this problem, but I haven't tried that yet.
So it should be possible to get rid of this problem in your home network.
But what about work or university networks? There are even more devices connected so the problem gets even worse. In Europe we have the Eduroam wifi network at many universities. If I'm connected to this network I get about 20 min wakeup time in one hour. There are a lot of ARP, DHCP and IPv6 request from different sources. Unfortunately you can't change anything about the configuration on your university/school/work network, so we need to find a solution to block these requests on our phone.
A solution for the IPv6 requests might be to disable IPv6 on your phone if you don't use it. In terminal:
Code:
echo 1 > /proc/sys/net/ipv6/conf/wlan0/disable_ipv6
Change the 1 to a 0 if you want to reactivate IPv6. Android resets this setting every time you connect to a network, so you might try Tasker to do this.
I still haven't found a solution for the ARP and DHCP requests though. Any help or input would be appreciated.
Thanks
___
Use the new BBS beta to check your wakelocks.
Click to expand...
Click to collapse
Been having this wakelock as well. Almost all of the packets being picked up by my phone are being sent by my router to random ports. No idea what is really causing it, but it is pretty annoying. Doesnt seem to drain much battery from the device though.
695886915
Apparently this is a known problem. Franco has already merged two fixes from Google in his kernel which reduce the wakelock, but still don't eliminate it completely. But I'm sure that this issue will soon be resolved with custom kernels or even an update from Google.
I'm hoping for this to be fixed too. My N4 didn't exhibit this wakelock, and my N5 is not deep sleeping at all when I'm at work as a result. I'm just using LTE at work, which is okay, but still not the best solution.
Franco Kernel didn´t help at all, since he seem to include all the google wifi patches as well, the official Google update is unlikely to solve the problem... so pissed off by this, eating up my battery so quickly I have to switch off wifi completely (and I hardly have cell data reception here at my workplace) ... sucks!
Thanks finally contained this problem.
Thanks for a great summary of causes and the info I needed to finally contain it. This problem had been dogging me since I got the N5 on my home network.
I tried static IP, no good.
I tried wifi-off on sleep, no good (never got to sleep i guess!!).
I tried forcing 5 GHz, no good.
Finally I followed the advice to Disable IPv6, IP Helper service, shell hardware detection service and the Windows Media Player Network Sharing Service on each Windows PC, and my stay awake time from Android OS plummeted from hours to minutes which I can deal with.
May not work for everyone, but seems to have done it for me. Thanks again.
Thank you for the post. It makes me nervous that I'm getting this wake lock. I previously got it on my GNex and Nexus7 (2012). I tried every method above to fix but got nowhere. For whatever reason my Nexus 4 didn't suffer from this. Hopefully I can figure something out for my new nexus 5
The update to 4.4.1 does not fix this issue. Still getting this wakelock.
Yes. I found the android OS is still killing the battery after updating to 4.4.1
muyoso said:
The update to 4.4.1 does not fix this issue. Still getting this wakelock.
Click to expand...
Click to collapse
Sunkins said:
Yes. I found the android OS is still killing the battery after updating to 4.4.1
Click to expand...
Click to collapse
Wish this would get fixed, as it's my last remaining wakelock issue and the only thing holding me back from getting fantastic battery life.
Sent from my Nexus 5 using xda app-developers app
laxor said:
Hey guys,
have you noticed that your device uses up a lot more battery on certain wifi networks (e.g. at work or university)? It is probably caused by the wlan_rx_wake wakelock.
From the wakelocks database:
So apparently some other device in the network keeps waking up the Nexus. If the problem occurs in your home network you can easily find out which device is causing the problem by using Shark and Wireshark. You'll get a log that shows every network activity.
Here are some tips from a similiar thread at the SGSII-forums (thanks!):
use a static IP instead of DHCP (you may have to set a static IP every time you sign up in that particular network)
disable IPv6 protocol on your phone - see below
update your router firmware
buy a gaming adapter for your Wifi network that gets the DHCP IP adress, but gives your phone a static IP
optimise router settings: click
Windows network is causing the problem - solution here: click
Change wireless network encryption method, change wifi channel, instead of using auto baseband use only 2.4 or 5GHz baseband (Wi - Fi - advanced - Wi - Fi frequency band)
turn off uPNP in router/AP
t urn off netbios in windows network
Thoravukk FAQ tells you: Q. My device not entering deep sleep if i use Wifi?
A: That's not a Kernel issue! It's a Router and (Windows 7) Network problem. Disable IPv6, IP Helper service, shell hardware detection service and the Windows Media Player Network Sharing Service. Source: here
Other apps and devices that can cause the wakelock:
Dropbox Lan Sync, (HP) Wireless printer, Canon network scan utility.
Using another kernel might also help to solve this problem: but I haven't tried that yet.
Try out the Franco kernel: http://forum.xda-developers.com/showthread.php?t=2508284
He has merged some wifi driver patches which should adress this problem. It reduced the wakelocks for me to 1 min in over 8 hours on my home network and to 3 min in one hour ony my university network!
So it should be possible to get rid of this problem in your home network.
But what about work or university networks? There are even more devices connected so the problem gets even worse. In Europe we have the Eduroam wifi network at many universities. If I'm connected to this network I get about 20 min wakeup time in one hour. There are a lot of ARP, DHCP and IPv6 request from different sources. Unfortunately you can't change anything about the configuration on your university/school/work network, so we need to find a solution to block these requests on our phone.
A solution for the IPv6 requests might be to disable IPv6 on your phone if you don't use it. In terminal:
Code:
echo 1 > /proc/sys/net/ipv6/conf/wlan0/disable_ipv6
Change the 1 to a 0 if you want to reactivate IPv6. Android resets this setting every time you connect to a network, so you might try Tasker to do this.
I still haven't found a solution for the ARP and DHCP requests though. Any help or input would be appreciated.
Thanks
___
Use the new BBS beta to check your wakelocks.
Click to expand...
Click to collapse
Thanks for this thread. Not sure if it will help or not but I have done all the things in the op and will report back. Have to start somewhere I guess. Although this isn't totally killing my battery in home .8% per hour will sleeping at night It by far is the biggest thing waking my phone. In 9 hrs I have 45 minutes of wake and 35 come from this. If I can get this under control I an sure I can get a little better battery performance. :good:
HP wireless printer
Hi, I have done everything you have listed, though I am still experiencing the wakelock. I have an HP wireless printer so I think this is the problem. Though, what could I do to stop it from creating the wakelock on my phone? This doesn't list what you need to do for the HP printer. Thanks in advance.
Any recommendations for a good modem/router that will not cause these wakelocks?
Sent from my Nexus 5 using xda app-developers app
For those who have tp link routers and get this wake lock, disable the print server in USB settings. It stopped almost all the RX_wake..
Before stopping I used to get some regularly spaced packets from 192.168.1.1 (router) to 255.255.255.255 UDP 7437 .. Bite completely stopped..
Hit thanks if I've helped you.
gpkumaran said:
For those who have tp link routers and get this wake lock, disable the print server in USB settings. It stopped almost all the RX_wake..
Before stopping I used to get some regularly spaced packets from 192.168.1.1 (router) to 255.255.255.255 UDP 7437 .. Bite completely stopped..
Hit thanks if I've helped you.
Click to expand...
Click to collapse
I might sound like a noob, but where do you find the USB settings to disable the print server?
grumpyfuzz said:
I might sound like a noob, but where do you find the USB settings to disable the print server?
Click to expand...
Click to collapse
in ur router setup page 192.168.1.1(probably)
Kyle C said:
Thank you for the post. It makes me nervous that I'm getting this wake lock. I previously got it on my GNex and Nexus7 (2012). I tried every method above to fix but got nowhere. For whatever reason my Nexus 4 didn't suffer from this. Hopefully I can figure something out for my new nexus 5
Click to expand...
Click to collapse
Have you figured anything out yet? I have also tried everything and still getting this wakelock also.
grumpyfuzz said:
Have you figured anything out yet? I have also tried everything and still getting this wakelock also.
Click to expand...
Click to collapse
Franco kernel working to fix this?
Momotani-Hitoshi said:
Franco kernel working to fix this?
Click to expand...
Click to collapse
It didn't work for me, but it might work for other people.
Related
Just received my Nexus 5 today and I'm noticing some strange connectivity issues while on WiFi. Some apps would complain network is unavailable, Facebook would load with no pictures, etc. This happens randomly, sometimes after few minutes others - an hour(s). Rebooting the phone or even cycling WiFi off/on usually recovers it, until it happens again. Cellular data works fine all the time. It can't be the WiFi network I'm connecting to as I have a myriad of devices that have worked and continue working without any problems.
I tried 3 other WiFi networks (different routers) with different configurations of encryption as well no encryption, switching between 5GHz, 2.4GHz, no matter what, problem occurs sooner or later.
Noticed on Google support forums few users describing exactly the same issue, surprised I didn't find reports here on XDA. Maybe not many people got their phones yet.
Anyone else getting the same "treatment" from their new Nexus 5?
Sent from my Nexus 5 using Tapatalk
I am seeing exactly the same thing. Wifi will work great, then all of a sudden, nothing. Stays that way for a couple of minutes, then all of a sudden it works again.
How many bars does the sifi icon show ?
Number of bars doesn't matter. I can have full bars sitting a meter from the router and issue would happen anyways.
I tried playing with WiFi optimizations in advanced settings to no avail unfortunately. Hopefully this is a bug that Google can quickly fix with a software update
Sent from my Nexus 5 using Tapatalk
Same here. Got my N5 yesterday and experienced the same at home. Same for my brother.
Hope that gets clarified soon. Not the nicest feeling having a new phone with that (or any) kind of issue...
Yes, my N5 started doing the same on my home wifi connections (using Apple's Airport Extreme 2.4/5GHz router).
The Playstore or Youtube apps would not display images or take forever. When I switched wifi off those apps worked fine.
I got it working again when I "forgot" my wifi setting for the 2.4 and 5Ghz channels then reconnected to the 2.4. I'll let that run for a day or so then try activating the 5Ghz.
Hmmm... This may have been what was going on here...
http://forum.xda-developers.com/showthread.php?t=2516307
Is it similar to the issue I described?
http://forum.xda-developers.com/showthread.php?t=2515635
I usually don't have connection issues outright, but do have issues reconnecting. However I did notice I list connection overnight after I went to bed.
Sent from my Nexus 5 using xda app-developers app
Nah. Its no connection issue. We can connect easily and have full signal bars, but still no connection randomly for a couple of minutes.
Boonyard said:
Hmmm... This may have been what was going on here...
http://forum.xda-developers.com/showthread.php?t=2516307
Click to expand...
Click to collapse
Sound like it - yes.
pinksoviet said:
Is it similar to the issue I described?
http://forum.xda-developers.com/showthread.php?t=2515635
I usually don't have connection issues outright, but do have issues reconnecting. However I did notice I list connection overnight after I went to bed.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Hmm - no I don't think that's the one. Phone connects fine, just over time randomly does this thing with the connectivity issues.
--EDIT
OOPs my mistake...
I looked in Setting/Wifi/Advanced ...
I turned OFF "Avoid Poor Connections"
and everything seems to work the way i want ( when i tell it to go to Wifi, it does that )
--EDIT end
i added star to this issue because of same problem . If enough stars get added Google may get on it.
(Didn't know if I should create a new thread for this as it is a wifi issue but seems to be soemthing different than what the OP decribed, my issues are related only to playstore app downloading)
I too am having terrible wifi issues on my new Nexus 5. But mine are different from those described here I think. Whenever I cycle through the wifi, turn it off and on again it doesn't fix the problem (not temporarily and ofc not permanently)
When browsing the web, the play store and mostly everything it works great and is very fast, BUT when downloading or updating an app the wifi speed is practically non-existant.
Sometimes showing that it will take 25 hours to download a 25mb app :S
This while my Galaxy Nexus on the same wifi network is as speedy as ever.
I have tried factory resetting my Nexus 5, I have cleared the cache and data of the play services app and of the play store app, I have tried changing the wifi bands (from auto, to 5 to 2.4 and back to auto), I have turned off the wifi optimization, but none of those things helped. I even tried some DNS HSPC wifi settings thingy I read here
That didn;t help either.
I have unplugged my router and replugged it in but that didn't help either.
I literally had to leave my brand new Nexus 5 downloading all night just so that it could install the apps I wanted on it. So far for playing around with the phone on day 1
What makes it even weirder is that occasionaly the wifi issues resolve itself and I can get good download speeds for several seconds or sometimes up to a few minutes, but then right after it is straight back to crap speeds. Some other reported that only while making a portion of the map available offline in Google Maps their app download speeds were great, but that didn't work for me either.
I don't know what to do and if it is a hardware issue or a software issue. Please help me.
Below some info that might be useful to helping me solve this.
White Nexus 5 32GB
Bought from US play store
Shipped to and using it in the Netherlands
Currently does not have a SIM card inside (that is still in my Galaxy Nexus till the wifi issues are resolved)
Unrooted, only installed the mandatory update during the setup
All apps downloaded are apps that are also on my Galaxy Nexus which works without a hitch
Any and all suggestions/ideas/help are welcome
I think the problem somehow related to DNS. I found that if I configure static IP settings and point DNS to Google's instead router's, things work normally. I reconfigured my router to advertise 8.8.8.8 and 8.8.4.4 as DNS servers for the DHCP and now for over 24 hours I haven't experienced the disconnection issue.
If your router cannot be reconfigured, try assigning static IP settings and Google's DNS to see if it helps.
I still believe that's a software bug on the phone, we can't blame a device (the router) that has worked for years and works fine with everything else but the Nexus 5, being at fault.
Sent from my Nexus 5 using Tapatalk
I currently can't reconnect to my Wi-Fi at home as it's stuck showing the last scan I did some 40 miles away at a shopping centre earlier today.
Of course none of these networks are now present, yet all mine are shown as not found!
Guessing a reboot will fix it as toggling Wi-Fi didn't. Mobile data is working fine.
leobg said:
I think the problem somehow related to DNS. I found that if I configure static IP settings and point DNS to Google's instead router's, things work normally. I reconfigured my router to advertise 8.8.8.8 and 8.8.4.4 as DNS servers for the DHCP and now for over 24 hours I haven't experienced the disconnection issue.
If your router cannot be reconfigured, try assigning static IP settings and Google's DNS to see if it helps.
I still believe that's a software bug on the phone, we can't blame a device (the router) that has worked for years and works fine with everything else but the Nexus 5, being at fault.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Not as tech as I want to be, so could you explain to me what the difference is in setting the DNS to Google's instead of routers? I have no idea what DNS is/does so what happens when you point it soemwhere else?
WORPspeed said:
Not as tech as I want to be, so could you explain to me what the difference is in setting the DNS to Google's instead of routers? I have no idea what DNS is/does so what happens when you point it soemwhere else?
Click to expand...
Click to collapse
DNS stands for Domain Name Service. What it basically does is to translate those easy to remember names such as www.Google.com to the actual numeric address (also called IP address) of the server that serves that site on the Internet. Home routers almost always sport built-in DNS service to speed up name translation requests from internal devices. What I figured is going on on the nexus 5 is it "doesn't seem to like" some DNS servers. Works fine with some, doesn't with others. What happens is at one point, for whatever reason, it stops being able to translate names to addresses and as result "decides" there is no working connection as it fails to connect to the corresponding servers. Google hosts publicly available DNS servers with the easy to remember IP addresses of 8.8.8.8 and 8.8.4.4 which apparently Nexus 5 doesn't have problem working with. Once it gets "instructed" to use them instead router's, everything works fine.
At least that's what I figured is going on so far.
Sent from my Nexus 5 using Tapatalk
BTW, just found one small and very useful app that can display information about WiFi connection as well as DNS servers associated to it.
Sent from my Nexus 5 using Tapatalk
leobg said:
DNS stands for Domain Name Service. What it basically does is to translate those easy to remember names such as www.Google.com to the actual numeric address (also called IP address) of the server that serves that site on the Internet. Home routers almost always sport built-in DNS service to speed up name translation requests from internal devices. What I figured is going on on the nexus 5 is it "doesn't seem to like" some DNS servers. Works fine with some, doesn't with others. What happens is at one point, for whatever reason, it stops being able to translate names to addresses and as result "decides" there is no working connection as it fails to connect to the corresponding servers. Google hosts publicly available DNS servers with the easy to remember IP addresses of 8.8.8.8 and 8.8.4.4 which apparently Nexus 5 doesn't have problem working with. Once it gets "instructed" to use them instead router's, everything works fine.
At least that's what I figured is going on so far.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks, but that wouldn't fix my issue right, because it doesn't explain why only play store downloads are terribly slow while the rest works fine.
Gave it a shot and at first it seemed to work, but after a short while the problem re-arose
DNS has nothing to do with weak or lost WIFI connections...
You can be perfectly connected, at full n speed to a WIFI AP without getting proper acces to Internet : THIS can DNS isue.
But in no way a DNS isue can leads to lost or very weak WIFI signal.
2 solutions are possible with Nexus 5 :
- WIFI module has the same badly coded shape as camera one...
- its hardware related wich, no need to say, could be the worst case...
I am having the same issue since day one. In fact it just occurred as I was replying to this thread. Mostly occurs when the phone comes out of sleep mode. However it will occur often and at random.
Sent from my Nexus 5 using xda app-developers app
Hi,
Why am I getting this notification for the 1st time in approx 2 months that have got a OPO, despite that am connected to WiFi?
Hoping to hear from you experts.
Thanks.
This sort of thing normally pops up when the WiFi network wants you to go to some sort of page, this is usually for a login to free WiFi hotspots, I assume this Dlink is your WiFi? Perhaps it wants you to open this page to change a configuration or login. This doesn't seem to be Android related at all but more to do with your router, could you try tapping on the notification and screenshot the page it opens, if any.
He's right. This looks like a router setting that you might have turned on like guest mode.
oscarandjo said:
This sort of thing normally pops up when the WiFi network wants you to go to some sort of page, this is usually for a login to free WiFi hotspots, I assume this Dlink is your WiFi? Perhaps it wants you to open this page to change a configuration or login. This doesn't seem to be Android related at all but more to do with your router, could you try tapping on the notification and screenshot the page it opens, if any.
Click to expand...
Click to collapse
Thanks for replying, appreciate your expert views.
DLink is my WiFi and not a hotspot WiFi, never occurred earlier.
When I tap on it, G chrome takes me to 173.194.35.96/generate _204
Google results of this IP......173.194.35.96 which is Spy-IP.com
and Google has different results for this 173.194.35.96/generate _204
It never happened earlier in the past 2 months.
Been using the same OPO and same WiFi.
Any solutions to resolve it?
Thanks again and Best regards!
kokocabana said:
He's right. This looks like a router setting that you might have turned on like guest mode.
Click to expand...
Click to collapse
Like WPS or WiFi ON/OFF on the router?
Micheal1122 said:
Thanks for replying, appreciate your expert views.
DLink is my WiFi and not a hotspot WiFi, never occurred earlier.
When I tap on it, G chrome takes me to 173.194.35.96/generate _204
Google results of this IP......173.194.35.96 which is Spy-IP.com
and Google has different results for this 173.194.35.96/generate _204
It never happened earlier in the past 2 months.
Been using the same OPO and same WiFi.
Any solutions to resolve it?
Thanks again and Best regards!
Click to expand...
Click to collapse
This is a router setting then, that page is some sort of login. Perhaps guest mode has been enabled on your router? Try this:
Settings>Wi-Fi>Modify Network>Show advanced options> Change DHCP to Static. Here, find the box that says Gateway and note the IP here. Now change Static back to DHCP and close this menu.
Go into the browser on your OPO and put in this Gateway IP, this will take you to the router config. The login for this is usually on the bottom of the router, otherwise the default can be found by searching the router model number, try finding a guest mode setting and turning it off - I really don't know... You can also change your WiFi name and password here if you like
I can't really help you any more than that.
oscarandjo said:
This is a router setting then, that page is some sort of login. Perhaps guest mode has been enabled on your router? Try this:
Settings>Wi-Fi>Modify Network>Show advanced options> Change DHCP to Static. Here, find the box that says Gateway and note the IP here. Now change Static back to DHCP and close this menu.
Go into the browser on your OPO and put in this Gateway IP, this will take you to the router config. The login for this is usually on the bottom of the router, otherwise the default can be found by searching the router model number, try finding a guest mode setting and turning it off - I really don't know... You can also change your WiFi name and password here if you like
I can't really help you any more than that.
Click to expand...
Click to collapse
Thanks for all your expert assistance, now you have given me options shall resolve it.
and keep you updated.
Best regards!
Btw factory reset reflash could help too?
Another strange thing all internet/WiFi related apps work fine including G Chrome and Mail in it but no GMail..........
Micheal1122 said:
Thanks for all your expert assistance, now you have given me options shall resolve it.
and keep you updated.
Best regards!
Btw factory reset reflash could help too?
Click to expand...
Click to collapse
Glad to hear, I am strongly advising against the factory restore. This is a feature of Android, although it is strange for it to be happening in this circumstance there is nothing it will achieve.
oscarandjo said:
Glad to hear, I am strongly advising against the factory restore. This is a feature of Android, although it is strange for it to be happening in this circumstance there is nothing it will achieve.
Click to expand...
Click to collapse
1. Changed router's password.
2. Guests mode is Off.
3. All apps working with WiFi except GMail and GPS.
4. Still see the notification.
5. Should WPS be Enabled, it is disabled at the moment?
6. You don't recommend a factory reset what about a re flash of 30 OR?
Thanks.
Your phone is working fine, it seems you have triggered some sort of bug in Android's WIFI login detection.
The system works by accessing DNS and check if the resulting IP is owned by google.com or some network-internal redirection/replacement by a login page.
Now, the IP 173.194.35.96 is owned by Google, so the DNS lookup obviously worked perfectly but for some reason the phone gets an unexpected answer from that server. Which makes me guess to one of the 2 following options:
a) one of the computers in your network is infected and Google keeps showing the "Prove you're human" captcha window on requests.
b) your provider is replacing failed DNS lookups with it's own "helper" page which for some reason is making Android trip. If possible, change the DNS servers in your router to either OpenDNS or Google DNS.
Micheal1122 said:
5. Should WPS be Enabled, it is disabled at the moment?
Click to expand...
Click to collapse
That's entirely your choice. However I would only recommend enabling it if it's the "Push to WPS" method and not constantly on - WPS is broken and depending on your router it takes between 1 to 10'000 attempts (1 second to ~ 2 hours) to break into your WIFI. Not good!
d4fseeker said:
Your phone is working fine, it seems you have triggered some sort of bug in Android's WIFI login detection.
The system works by accessing DNS and check if the resulting IP is owned by google.com or some network-internal redirection/replacement by a login page.
Now, the IP 173.194.35.96 is owned by Google, so the DNS lookup obviously worked perfectly but for some reason the phone gets an unexpected answer from that server. Which makes me guess to one of the 2 following options:
a) one of the computers in your network is infected and Google keeps showing the "Prove you're human" captcha window on requests.
b) your provider is replacing failed DNS lookups with it's own "helper" page which for some reason is making Android trip. If possible, change the DNS servers in your router to either OpenDNS or Google DNS.
That's entirely your choice. However I would only recommend enabling it if it's the "Push to WPS" method and not constantly on - WPS is broken and depending on your router it takes between 1 to 10'000 attempts (1 second to ~ 2 hours) to break into your WIFI. Not good!
Click to expand...
Click to collapse
Thanks issue resolved.
Thanks issues resolved.
Thanks issue resolved.
oscarandjo said:
Go into the browser on your OPO and put in this Gateway IP, this will take you to the router config.
Click to expand...
Click to collapse
This resolved the issue.
Thanks again.
Everytime I get a new phone I install BBS and enable root features but I'd like to wait with the s8 before rooting. That's why I installed BBS and used adb comments to have root features without root. The reason for this is mainly checking for kernel and partial wakelocks and see what I can and can't control. A lot of people will have high battery drain on Wi-Fi without knowing it as it will be under Android system stats. After you install BBS CHECK if you have rx_wlan_wakelock. This one is caused by the router sending beacons to your phone constantly and preventing it from sleeping. There are 3 settings to change to avoid this.:
DTIM interval: set it as high as possible
BEACON interval: set it as high as possible
Fixed IP: assign your phone a fixed IP so the router doesn't send new IP to the phone frequently.
Or... create a virtual wifi ID and have your phone just connect to that with your settings.
Being that we are on XDA. Ill assume you know DD-wrt, Openwrt, etc.. which case changing the settings there on the router could help.
Rather have those tweaked for best speed for my pc anyways vs my phone thus the virtual wifi ssid config.
I am having issues regarding Wifi hotspot on Pie.
1. My laptop find it very difficult to find the hotspot. Sometimes I have to restart the hotspot 2-3 times before the network shows up on my laptop. On Oreo, this was always instant and worked immediatly.
2. In the last few days using a hotspot from the phone and my laptop I have had issues regarding DNS/internet. Even though my laptop is connected to the hotspot network, it doesn't have any internet access. When browsing the web on my laptop, all DNS requests always fails. It happens whenever I try to navigate to a site and tries to ping a url from CMD. But if I try to ping a ip address, let say 1.1.1.1, that works fine! I can also use my browser on my phone without any issues at all. The laptop works fine on any other network and the phone works well on its own but the hotspot causes great problems. It sounds to me that for some reason when using a hotspot, DNS requests doesn't come through properly. Also, if I connect to a VPN on my laptop, eveything works, even DNS requests but my VPN is somewhat unreliable so it constantly disconnects so that is not a viable solution for me.
Anyone experiencing similar problems? It's really annoying because now I can't get any work done on my daily commute.
Edit: It sounds similar to these problems: http://piunikaweb.com/2018/08/22/go...hotspot-tethering-issues-after-android-9-pie/
baxtex said:
I am having issues regarding Wifi hotspot on Pie.
1. My laptop find it very difficult to find the hotspot. Sometimes I have to restart the hotspot 2-3 times before the network shows up on my laptop. On Oreo, this was always instant and worked immediatly.
2. In the last few days using a hotspot from the phone and my laptop I have had issues regarding DNS/internet. Even though my laptop is connected to the hotspot network, it doesn't have any internet access. When browsing the web on my laptop, all DNS requests always fails. It happens whenever I try to navigate to a site and tries to ping a url from CMD. But if I try to ping a ip address, let say 1.1.1.1, that works fine! I can also use my browser on my phone without any issues at all. The laptop works fine on any other network and the phone works well on its own but the hotspot causes great problems. It sounds to me that for some reason when using a hotspot, DNS requests doesn't come through properly. Also, if I connect to a VPN on my laptop, eveything works, even DNS requests but my VPN is somewhat unreliable so it constantly disconnects so that is not a viable solution for me.
Anyone experiencing similar problems? It's really annoying because now I can't get any work done on my daily commute.
Edit: It sounds similar to these problems: http://piunikaweb.com/2018/08/22/go...hotspot-tethering-issues-after-android-9-pie/
Click to expand...
Click to collapse
@thugslug @jbm76 I know you guys had an issue with hotspot. Is this the same problem?
yldlj said:
@[email protected] I know you guys had an issue with hotspot. Is this the same problem?
Click to expand...
Click to collapse
Point 2 sounds like it..
jbm76 said:
Point 2 sounds like it..
Click to expand...
Click to collapse
I can't remember what thread you wrote the adb commands that might fix it? Was going to direct him to that post.
yldlj said:
I can't remember what thread you wrote the adb commands that might fix it? Was going to direct him to that post.
Click to expand...
Click to collapse
Yep that fixed for me ??
adb shell settings get global tether_dun_required
If the result is "null" or "1"
adb shell settings put global tether_dun_required 0
Reboot phone
yldlj said:
@[email protected] I know you guys had an issue with hotspot. Is this the same problem?
Click to expand...
Click to collapse
His first problem I don't have, but it's the second that's the same issue as mine.
Obviously he's never searched or he'd have found my lengthy post not very far back.
The solution is there too.
I've never tried turning the VPN on to see if I get through access to the internet that way. I can't now as I've applied the fix @jbm76 found, and I don't really want to back out the fix to try it.
Definitely an area where pie has gone backwards. For those of us affected anyway.
Edit.... Sorry, I didn't note that this was a new thread.
My post is in the OB4 thread (which I at first thought this was). I'm tired and didn't look well enough.
jbm76 said:
Yep that fixed for me ?
adb shell settings get global tether_dun_required
If the result is "null" or "1"
adb shell settings put global tether_dun_required 0
Reboot phone
Click to expand...
Click to collapse
I will try these and report back.
baxtex said:
I will try these and report back.
Click to expand...
Click to collapse
If you get errors at the cmd prompt make sure usb debugging is set 'on' on the phone.
Followed the commands and it seemed to do the trick! Many many thanks!
baxtex said:
Followed the commands and it seemed to do the trick! Many many thanks!
Click to expand...
Click to collapse
[emoji3][emoji3]
Most people it works straight away. What region are you in?
Sent from my SM-P605 using Tapatalk
jbm76 said:
[emoji3][emoji3]
Most people it works straight away. What region are you in?
Sent from my SM-P605 using Tapatalk
Click to expand...
Click to collapse
Sweden.
I want to remember that it did work before, then I have to reflash Pie again and that's when the issues started.
I still wanted to say that I still suffering from the first problem, having difficulties actually finding the hotspot at all.
Its very odd. This problem has started to arise again. I tried running adb shell settings get global tether_dun_required again but I get the answer that it is 0 so that looks fine. I haven't updated anything since I had this problem the last time.
Folks,
To provide some more info and more things to try if you are rooted (I am in the US on T-Mobile). These instructions should also help you avoid tethering detection using the standard Android tethering options if you wish to.
1) Go into settings --> system --> developer options and turn off Tethering hardware acceleration. This will make sure all tethering routing is done by Android at the software level and not by Qualcomm's chipsets (so following steps will apply).
2) As suggested, put global tether_dun_required 0. Note you can also do this from a command prompt by typing su (get root access) and typing setting put global tether_dun_required 0. What this does is route tething traffic over the same APN as phone traffic, and not the hidden tethering APN that some carriers put on the sim cards.
3) Install Change TTL and in settings set it to run a boot and set TTL to 64. This ensures that all traffic leaving your phone will have a TTL of 64 and look like it is coming from the phone. (I am pretty sure this also set's ipv6 hop limit, as TMobile in the US is all IPv6 and this hides traffic.)
Reboot. If you still have trouble -- try Android's USB option to see if it is WiFi related vs Tethering system related.
- Verify that global tether_dun_required is still 0 after reboot (it should be if you are rooted).
- Delete the WiFi entry on your computer and re-join the phone's network -- sometimes it is on your computer's side.
Another thing to try is Easy Tether -- this is a good USB tethering option that won't use Android tethering system and it is guaranteed to route traffic over the phone's network APN.
If the issue is DNS, you can isolate that by manually putting a DNS (8.8.8.8) into the tethered computer to see if that is the issue.
Also, google search xda VPN Hotspot. This app has a ton of options to change Android's tethering routing even if you are not using a VPN. This may also help you figure something out. You can activate tethering, then go in here and turn on the wlan interface and it should route traffic directly to that (which should be happening anyways because of tether_dun_required = 0).
Good luck!
MW
MetroWestMA said:
Folks,
To provide some more info and more things to try if you are rooted (I am in the US on T-Mobile). These instructions should also help you avoid tethering detection using the standard Android tethering options if you wish to.
1) Go into settings --> system --> developer options and turn off Tethering hardware acceleration. This will make sure all tethering routing is done by Android at the software level and not by Qualcomm's chipsets (so following steps will apply).
2) As suggested, put global tether_dun_required 0. Note you can also do this from a command prompt by typing su (get root access) and typing setting put global tether_dun_required 0. What this does is route tething traffic over the same APN as phone traffic, and not the hidden tethering APN that some carriers put on the sim cards.
3) Install Change TTL and in settings set it to run a boot and set TTL to 64. This ensures that all traffic leaving your phone will have a TTL of 64 and look like it is coming from the phone. (I am pretty sure this also set's ipv6 hop limit, as TMobile in the US is all IPv6 and this hides traffic.)
Reboot. If you still have trouble -- try Android's USB option to see if it is WiFi related vs Tethering system related.
- Verify that global tether_dun_required is still 0 after reboot (it should be if you are rooted).
- Delete the WiFi entry on your computer and re-join the phone's network -- sometimes it is on your computer's side.
Another thing to try is Easy Tether -- this is a good USB tethering option that won't use Android tethering system and it is guaranteed to route traffic over the phone's network APN.
If the issue is DNS, you can isolate that by manually putting a DNS (8.8.8.8) into the tethered computer to see if that is the issue.
Also, google search xda VPN Hotspot. This app has a ton of options to change Android's tethering routing even if you are not using a VPN. This may also help you figure something out. You can activate tethering, then go in here and turn on the wlan interface and it should route traffic directly to that (which should be happening anyways because of tether_dun_required = 0).
Good luck!
MW
Click to expand...
Click to collapse
Hi and thank you for your post. It seems that windows had changed dns settings by its own to something invalid, so that is why it didn't work. However I am still having connection issues. Mainly I find it very difficult to connect my laptop (and other devices) to the hotspot of the Oneplus 6.
1) Done.
2) Done.
3) It was already set at 64 but I tried setting in to 64 again.
DUN is still 0 after reboot. I have also removed the wifi from my PC and changed name on the hotspot. Also tried both 2.4 and 5 Ghz. When the pc is connected the hotspot, I can ping google succesfully, so internet works but not DNS, all requests in my browser times out. I have also tried setting DNS to external providers in the phone (not sure if if affects the hotspot though). I looked at easy tether but root version was pretty expensive. I also googled XDA VPN Hotspot but I'm not sure which app you mean. Do you have the link?
Right now I'm just thinking of factory resetting the phone and installing the latest oxygen version (I'm still on 9.0.0.0).
Here is even more testing:
What I am experiencing is that there are grave problems trying to connect when in an area with a lot of wifi networks.
I live on the countryside and I thought I would try using hotspot for a couple of times. Thing is, at home, sharing hotspot from the phone to my laptop always works instantly, both on 5Ghz and 2.4Ghz. I might add that there are basically no wifi networks interfering where I live, except for my own. When I start my bus ride in the morning from my house to a city were I work, the hotspot usually works pretty good. But it's when I'm going home that I am start having problems. In the city, there is probably around 50-100 wifi networks when I start the ride home. And that's when it usually is impossible to connect the hotspot to the laptop. However, when leaving the city and entering the highway, it is usually easier. I have these connection problems on both 5Ghz and 2.4Ghz and if it does connect, 2.4 is hideous, it disconnects all the time.
So the conclusion for me is that it is having a very hard time connecting when there are a lot of wifi networks around. However, It never seemed to be a major problem on Oreo, only on Pie.
baxtex said:
Hi and thank you for your post. It seems that windows had changed dns settings by its own to something invalid, so that is why it didn't work. However I am still having connection issues. Mainly I find it very difficult to connect my laptop (and other devices) to the hotspot of the Oneplus 6.
1) Done.
2) Done.
3) It was already set at 64 but I tried setting in to 64 again.
DUN is still 0 after reboot. I have also removed the wifi from my PC and changed name on the hotspot. Also tried both 2.4 and 5 Ghz. When the pc is connected the hotspot, I can ping google succesfully, so internet works but not DNS, all requests in my browser times out. I have also tried setting DNS to external providers in the phone (not sure if if affects the hotspot though). I looked at easy tether but root version was pretty expensive. I also googled XDA VPN Hotspot but I'm not sure which app you mean. Do you have the link?
Right now I'm just thinking of factory resetting the phone and installing the latest oxygen version (I'm still on 9.0.0.0).
Here is even more testing:
What I am experiencing is that there are grave problems trying to connect when in an area with a lot of wifi networks.
I live on the countryside and I thought I would try using hotspot for a couple of times. Thing is, at home, sharing hotspot from the phone to my laptop always works instantly, both on 5Ghz and 2.4Ghz. I might add that there are basically no wifi networks interfering where I live, except for my own. When I start my bus ride in the morning from my house to a city were I work, the hotspot usually works pretty good. But it's when I'm going home that I am start having problems. In the city, there is probably around 50-100 wifi networks when I start the ride home. And that's when it usually is impossible to connect the hotspot to the laptop. However, when leaving the city and entering the highway, it is usually easier. I have these connection problems on both 5Ghz and 2.4Ghz and if it does connect, 2.4 is hideous, it disconnects all the time.
So the conclusion for me is that it is having a very hard time connecting when there are a lot of wifi networks around. However, It never seemed to be a major problem on Oreo, only on Pie.
Click to expand...
Click to collapse
Seems more like WiFi / Computer related than phone. Did you try USB tethering? Is DNS get manually set in your computer by something else you installed?
MetroWestMA said:
Seems more like WiFi / Computer related than phone. Did you try USB tethering? Is DNS get manually set in your computer by something else you installed?
Click to expand...
Click to collapse
USB tethering works fine, dns as well. Its just the connection, it is very difficult to connect anything to the Oneplus 6 in wifi crowded areas.
Will this effect Bluetooth tethering too? Or is there another command for that? Dang built in hot spot get horrible speed after this setting is set, at least be on T-Mobile.
Hi guys,
I also face a strange issue, the connected devices to the hotspot it keeps disconnected after some time.. 1min, 5min, 15min...is random and annoying. Dose anyone face this issue to? Tried diferent fixes but nothing works, it remained to do a factory reset to see if the problem persist..
khrisstyan said:
Hi guys,
I also face a strange issue, the connected devices to the hotspot it keeps disconnected after some time.. 1min, 5min, 15min...is random and annoying. Dose anyone face this issue to? Tried diferent fixes but nothing works, it remained to do a factory reset to see if the problem persist..
Click to expand...
Click to collapse
Read this thread. Workaround in here.
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.