Related
WiFi on campus here uses WPA enterprise auth - good. I was shocked when I saw that the phone seemingly didn't support it. Network didn't even appear in the list, and Add Network only supports WPA Personal / WEP. How Apple of them. But WHY? It's wpa_supplicant behind the scenes.
I've been using campus wifi successfully for a few days now. It seems to integrate well enough - the wifi settings menu doesn't seem to break at all, the enterprise-authed network and status are listed correctly including the 'lock' icon, etc.
These instructions are slightly modified from being specific to the particular university (posted locally too, you see). If you can rub some braincells together, this can be adapted. The parts regarding a certificates file may or may not be needed in your setup, for example.
* Get a root shell
* cd /data/misc/wifi/
* cat wpa_supplicant.conf
* The existing supplicant config is displayed - copy and paste it into a text editor (the beginning bits are important, as are your existing networks)
* Paste in a working wpa_supplicant.conf section for your network at the end
* Fill in username and password in the new section. Replace the path for cacerts.pem with /data/misc/wifi/cacerts.pem
* Save the new config onto the SD card
* Save the cacerts.pem (same site) onto the SD card also
* On the handset: In the settings/storage menu, disable the SD card for USB storage (otherwise, can't access it from the shell)
* rm wpa_supplicant.conf
* cp would be used here normally, but it isn't in the stock image: dd if=/sdcard/wpa_supplicant.conf of=wpa_supplicant.conf
* chmod 666 wpa_supplicant.conf (Warning! Readable/Writable by EVERYONE! Use 664 such that only root can write it if you want, but this will possibly disallow changes by the settings app - if chown was available, ownership would be reverted back to wifi:wifi)
* dd if=/sdcard/cacerts.pem of=cacerts.pem
* chmod 444 cacerts.pem (needs to be readable by wifi user)
* The network should appear in the wifi menu and connect if you enable wifi. Reboot if not maybe?
Problems:
* Permissions are a bit wonky due to lack of chown. The process would be cleaner with busybox installed (possible with root), but this process is written to work on a stock RC29 handset.
* It will almost surely fail following an update. Try not to give up root before the WiFi UI is patched
* Maybe there's a reason that enterprise auth is absent from the settings UI
* WiFi settings page may or may not break. WiFi settings page may or may not undo your changes.
A quick troubleshooting tip: if you've dealt with wpa_supplicant before, note that wpa_cli is available to root. Helpful to diagnose any issues that crop up.
Enjoy.
How Apple of them. But WHY? It's wpa_supplicant behind the scenes
Click to expand...
Click to collapse
I suspect it's because the majority of consumers only access wifi networks secured through psk or mac-address. iirc my university used mac-address too. Not sure if that's changed by now. In any case, I wouldn't hold my breath for official support on the G1. Maybe on some future Android device with enterprise in mind.
Anyway, good tips and good first post. Welcome to the forum
busybox has chown
WPA2
Can I ask a question?
The SSID for your campus wifi is not broadcasted, correct? if this is true, then it won't show up and the only way to get access is to add it manually.
Now when you go to add it manually, did you try to change the type of security before you flipped out the keyboard? Just wondering since WPA2 is clearly seen if you have the keyboard in and if you have it out it looks like WPA2 isn't an option but if you try to move the security box with a swipe up with your finger, WPA2 will be shown. I haven't had a single problem attaching to my home or work network using WPA2 PSK since RC19 and beyond.
Yep, busybox has chown - which makes the whole thing cleaner and safer. My instructions were written originally with no assumptions as to previous modding, incl how to get telnet.
The wifi network here does broadcast, but is filtered out due to "unsupported" security. Add network lists wpa2 personal but not enterprise.
I modified my wpa_supplicant.conf file using your instructions and it worked!
Thanks!
Dave
vSymm said:
How Apple of them. But WHY? It's wpa_supplicant behind the scenes.
Click to expand...
Click to collapse
Because there's a substantial amount of UI work that needs to be done for WPA2-Enterprise compared with the relatively common WPA2-PSK.
My advice? If official support is something you'd like, go write it and submit a patch to the Android devs.
Not working
I can't get this to work. It says "failed to start wifi".
My non-enterprise wifi won't even work now. It connects but apps say network error.
I am trying to connect to my university's wifi that is "Secure 802.1X authentication and EAP-TTLS with PAP inner-authentication (anonymous)"
Can anyone give me an example config for this? It doesn't use a certificate.
Confirm that the permissions were set correctly on wpa_supplicant.conf
I'm sure you can find an example for that particular setup online somewhere.
happyface_0 said:
I can't get this to work. It says "failed to start wifi".
My non-enterprise wifi won't even work now. It connects but apps say network error.
I am trying to connect to my university's wifi that is "Secure 802.1X authentication and EAP-TTLS with PAP inner-authentication (anonymous)"
Can anyone give me an example config for this? It doesn't use a certificate.
Click to expand...
Click to collapse
try this:
adb shell
cd /data/misc/wifi
chown 1010:1010 wpa_supplicant.conf
Worked for me too, but the connection was really unstable. I've added the option bssid to wpa_supplicant.conf to prevent roaming. Now it works really well on my desk, but I haven´t tried the rest of the company.
need help connecting
I'm trying to connect to a campus network, I see the SSID detected (as following), and It tries to connect and aborts by itself.
my wpa_supplicant.conf shows this:
network={
ssid="Techwifi"
scan_ssid=1
key_mgmt=NONE
priority=2
}
hey guys,
will this also work with WPA2 and EAP/TTLS with PAP?
or do you know when this feature will be integrated?
thaks a lot
linulli said:
hey guys,
will this also work with WPA2 and EAP/TTLS with PAP?
or do you know when this feature will be integrated?
thaks a lot
Click to expand...
Click to collapse
Yes, I have it working.
Code:
network={
ssid="ssidname"
scan_ssid=1
key_mgmt=WPA-EAP
eap=TTLS
identity="user"
password="pass"
phase2="auth=PAP"
}
Note: It seems to drain my G1's battery pretty nicely and it starts to get hot after being connected for a bit. Also, my G1 added disabled=1 to the end of this network after the ADP1 v1.1 update, strange.
Thanks happyface_0,
so I will have a few minutes online.
Is there a way to alter your wpa_supplicant settings on an unrooted German G1 , or how can i downgrade and then alter the settings, does anyone know?
I'd love to know that too, i really want to use wifi at work.
Can we do anything to help you help us?
Maybe someone with a US RC33 can look if the WPA 2 Enterprise support finally made it into the gui of the G1 , then our problem would be solved ,
can´t find something on the net which says that WPA 2 Enterprise was part of the Internet .
So please can somebody look up his or her connection settings for wlan and tell us if WPA 2 Enterprise is available now?
Gedomania said:
Maybe someone with a US RC33 can look if the WPA 2 Enterprise support finally made it into the gui of the G1 , then our problem would be solved ,
can´t find something on the net which says that WPA 2 Enterprise was part of the Internet .
So please can somebody look up his or her connection settings for wlan and tell us if WPA 2 Enterprise is available now?
Click to expand...
Click to collapse
Neither WPA-Enterprise nor WPA-2 Enterprise are available yet without actually editing the wpa_supplicant configuration manually, even on RC33.
Hmm thats pretty sad, is it actually possible to write a program which can edit the Wpa_supplicant file so that we can manually insert the settings we need to get WPA 2 Enterprise working , even on phones without root?
Hello,
I have noticed that a lot of sapphire roms (even the original one) have some problems on H3G and some other networks here (i.e. Vodafone Italy in my case), on my 32A magic.
Download stalls on 2G, uploads may be very slow on 3G. This is because mtu path discovery seems not working very well or maybe some servers block fragmentation request packets, etc etc.
I am wondering if it's enough to issue a "ifconfig rmnet0 mtu XXXX" as root to modify the MTU in android, and how to make this a permanent change in the system, so that it won't lose it for each bootup/interface up&down .
I have investigated this problem for weeks, thinking in the first place it was a problem with the build.prop kernel ril.parameters. Indeed setting this parameters to more conservative values fix that (ie gprs class 10 and not 12, hep disabled, etc), but it doesn't seem to be the main issue.
As I want to conduct some further testing I am wondering if someone knows how to set MTU in a permanent way on android for the remote (GPRS/3G) interfaces.
thanks a lot.
I would also like to know this, I have 3G and it does stall alot. While downloading from market it will go up to 99% then freeze
ziokendo said:
Hello,
I have noticed that a lot of sapphire roms (even the original one) have some problems on H3G and some other networks here (i.e. Vodafone Italy in my case), on my 32A magic.
Download stalls on 2G, uploads may be very slow on 3G. This is because mtu path discovery seems not working very well or maybe some servers block fragmentation request packets, etc etc.
I am wondering if it's enough to issue a "ifconfig rmnet0 mtu XXXX" as root to modify the MTU in android, and how to make this a permanent change in the system, so that it won't lose it for each bootup/interface up&down .
I have investigated this problem for weeks, thinking in the first place it was a problem with the build.prop kernel ril.parameters. Indeed setting this parameters to more conservative values fix that (ie gprs class 10 and not 12, hep disabled, etc), but it doesn't seem to be the main issue.
As I want to conduct some further testing I am wondering if someone knows how to set MTU in a permanent way on android for the remote (GPRS/3G) interfaces.
thanks a lot.
Click to expand...
Click to collapse
theres some method to use bettercut to lock the phone to only be in 3g not to connect to gprs or edge connections
lemme search for it and ill post the link
Zarboz said:
theres some method to use bettercut to lock the phone to only be in 3g not to connect to gprs or edge connections
Click to expand...
Click to collapse
In htc based roms there's the check "3G Only".
But I am just interested to know how to lower the mtu, because here in my flat I have only 2G coverage.
There's a paid app on the market that does exactly that if you're root (lowering the mtu), is called something like "3UK Fixer", so there should be a way.
(it's not like i don't want to pay 1£ btw for that app, is just that is for 3UK and installs a different APN.. i am just interested in applying the MTU fix)
I was flashing a JB 4.1.2 ROM several days ago when I noticed that my Desire S doesn't connect to my home WiFi network. As I played with the router settings before that and I didn't have the time to troubleshoot it at that time, I ignored the incident. Next day, I saw that I'm not able to connect to my work WiFi network either...then I've started to wonder what happened.
The long story short, is that I frequently flash several ROMs that are all CM10 derivates: CM10 builds from nk111, Andromadus ROM by Flinny, Paranoid by djpbx (current ROM). I usually flash every new release/build and test it to see if I encounter bugs/issues. Now I am not able to connect to any WiFi with ANY ROM...I don't remember the exact moment from which this happened but since then, I've tried with ROMs on which WiFi worked before like IceColdSandwich ported from Lord ClockaN's ROM, several CM10 builds (newer or older), even with Sense based ROMs (I've tried Fallout and Sabsa Prime). With or without full wipe, doesn't make any difference.
On all I got the same thing: WiFi "see"the surrounding networks but doesn't connect...it's not even say "Authenticating" or "Acquiring IP address". I've tried all the settings in Advanced TAB (WiFi frequency band, WiFi region), I tried with different security options (WEP, WPA, WPA2), I tried with hidden network as well as with visible (SSID is transmitted), I even tried with open network. No success at all. Network is saved but that's all. On hidden networks It says network is not in range, on visible ones is not connecting at all.
I've tried to change radio...I've used the last one (20.4801.30.0822U_3822.10.08.04), I've flashed also the one I was using before and which DID WORK (20.48.30.0822U_3822.09.08.20)...nothing.
I've tried with or without a SIM (I read on a thread that it could influence)
I was hoping to solve it but it seems I was not able to do it. Don't know if it's something hardware related either, but since I can see the visible WiFi networks, at least the scanning part is working. Just that it does not connect. And it was working before, at least with some of the ROMs I've flashed
Now I end up with a Desire S without WiFi. Everything else works: BT, sensors, mobile data and so on. I don;t understand what happened, anyone that can give me clues or what else to check, please let me know. Phone is out of warranty and I exclude the "send it to repair center"" option. I'll do that only as last resort and when I'm going to buy a new phone.
NOTE: To avoid extra questions: I am S-Off, current radio 20.48.30.0822U_3822.09.08.20. I've also posted the problem initailly in Andromadus thread and attached a logcat HERE
I have the same problem with my desire s. BT and WIFI don't have mac adres id.
I am not sure it this much related, but I had plenty of such siituations while porting the Wireless driver into my kernel.
It was a permmission issiue (when certain files were created with certain permission another ramdisk with another permissions was not able to start the WiFi.) Usually a full wipe should fix this. Do not restore any wifi data with Titanium. Use 4EXT recovery if you are still on CWM
Once I managed to fix this by starting WiFi hotspot (on Sense 4 ROM) then stop it and start WiFi. Hope this helps
I've gone through the obvious (for me at least) things. I didn't post here without trying them first. Full wipe, gone through initial setup wizard, then first thing added a WiFi network... Nothing restored with TB or anything else, nothing installed, just flashed the ROM + GAPPS + aGPS patch then setup manually everything. When I've flashed Sabsa Prime I've even setup WiFi dirrectly from the initial setup wizard when it was asking how do I connect to internet. Still nothing
Later edit: I've tried to setup a WiFi access point from mobile (WiFi tethering). The access point is created but not visible to any device. It seems like the "emitting" part is not working, only the "reception" is ok.
Code:
[COLOR="Red"]15:25:47.265 Error hostapd 4245 Configuration file: /data/misc/wifi/hostapd.conf
15:25:47.812 Debug Tethering 1670 sendTetherStateChangedBroadcast 1, 0, 0
15:25:47.920 Warning hostapd 4245 wlan0: Could not connect to kernel driver
15:25:47.920 Error hostapd 4245 Using interface wlan0 with hwaddr d4:20:6d:be:66:76 and ssid 'RapierAP'[/COLOR]
15:25:47.920 Debug CommandListener 1431 Setting iface cfg
15:25:47.920 Debug CommandListener 1431 Trying to bring up wlan0
15:25:47.920 Debug Tethering 1670 Tethering wlan0
15:25:47.920 Debug Tethering 1670 InitialState.processMessage what=2
15:25:47.920 Debug Tethering 1670 sendTetherStateChangedBroadcast 0, 0, 0
15:25:47.920 Debug Tethering 1670 Tethered wlan0
15:25:47.920 Debug Tethering 1670 sendTetherStateChangedBroadcast 0, 1, 0
15:25:47.920 Debug Tethering 1670 MasterInitialState.processMessage what=1
15:25:48.030 Debug TetherController 1431 Setting IP forward enable = 1
15:25:48.030 Debug TetherController 1431 Starting tethering services
15:25:48.030 Debug TetherController 1431 Tethering services running
15:25:48.030 Info dnsmasq 4247 started, version 2.51 cachesize 150
15:25:48.030 Info dnsmasq 4247 compile time options: no-IPv6 GNU-getopt no-DBus no-I18N DHCP no-scripts no-TFTP
15:25:48.030 Warning dnsmasq 4247 warning: no upstream servers configured
15:25:48.030 Info dnsmasq 4247 DHCP, IP range 192.168.48.2 -- 192.168.48.254, lease time 1h
15:25:48.030 Info dnsmasq 4247 DHCP, IP range 192.168.47.2 -- 192.168.47.254, lease time 1h
15:25:48.030 Info dnsmasq 4247 DHCP, IP range 192.168.46.2 -- 192.168.46.254, lease time 1h
15:25:48.030 Info dnsmasq 4247 DHCP, IP range 192.168.45.2 -- 192.168.45.254, lease time 1h
15:25:48.030 Info dnsmasq 4247 DHCP, IP range 192.168.44.2 -- 192.168.44.254, lease time 1h
15:25:48.030 Info dnsmasq 4247 DHCP, IP range 192.168.43.2 -- 192.168.43.254, lease time 1h
15:25:48.031 Info dnsmasq 4247 DHCP, IP range 192.168.42.2 -- 192.168.42.254, lease time 1h
15:25:48.031 Info dnsmasq 4247 read /etc/hosts - 1 addresses
When starting WiFi, I get the following:
Code:
[COLOR="Red"]15:32:47.517 Error WifiHW 1670 Unable to open connection to supplicant on "wlan0": No such file or directory[/COLOR]
15:32:48.171 Verbose SCREEBL 2762 --> ROTATION_0
15:32:48.171 Verbose SCREEBL 2762 --> Orientation IN BOUNDS: 5.0 < 5.00065256449902 < 90.0
15:32:49.596 Debug Tethering 1670 sendTetherStateChangedBroadcast 1, 0, 0
15:32:49.703 Debug Beautiful Widgets 4120000 WIFI_STATE_CHANGED_ACTION
15:32:49.810 Error WifiConfigStore 1670 configuration found for missing network, ignored
It seems a problem with the wlan0 which is not found...
Rapier said:
I've gone through the obvious (for me at least) things. I didn't post here without trying them first. Full wipe, gone through initial setup wizard, then first thing added a WiFi network... Nothing restored with TB or anything else, nothing installed, just flashed the ROM + GAPPS + aGPS patch then setup manually everything. When I've flashed Sabsa Prime I've even setup WiFi dirrectly from the initial setup wizard when it was asking how do I connect to internet. Still nothing
Click to expand...
Click to collapse
I know that you are here from quite some time and into this things and has no intention to offend you. Have you tried a backup and format of the SDcard? I saw this as a solution in one of the official ICS threads.
And what is the logcat saying when you enable WiFi?
Sent from my HTC Desire S
amidabuddha said:
I know that you are here from quite some time and into this things and has no intention to offend you. Have you tried a backup and format of the SDcard? I saw this as a solution in one of the official ICS threads.
And what is the logcat saying when you enable WiFi?
Sent from my HTC Desire S
Click to expand...
Click to collapse
No, no, please, no offence taken. Sorry if it sounded this way. But as you said, I'm here for some time and learned alot (thanks to this wonderful community) and I just wanted to say that I've tried through the "normal" ways. The logcat is as you see in my previous post (last code quote). There are only some rows because the rest are related to other things....
I've taken another logcat while starting up WiFi and then scan. Attached
I'll also try to format sdcard. This indeed is something I didn't try yet (I thought is not related). Wouldn't be the same thing if I just take out the card completely? For the test purpose I don't care what files are there and if some apps won''t work
Rapier said:
No, no, please, no offence taken. Sorry if it sounded this way. But as you said, I'm here for some time and learned alot (thanks to this wonderful community) and I just wanted to say that I've tried through the "normal" ways. The logcat is as you see in my previous post (last code quote). There are only some rows because the rest are related to other things....
I've taken another logcat while starting up WiFi and then scan. Attached
I'll also try to format sdcard. This indeed is something I didn't try yet (I thought is not related). Wouldn't be the same thing if I just take out the card completely? For the test purpose I don't care what files are there and if some apps won''t work
Click to expand...
Click to collapse
From your first logcat:
E/WifiHW ( 1674): Unable to open connection to supplicant on "/data/system/wpa_supplicant/wlan0": No such file or directory
and you have noticed the other one yourself:
Error WifiHW 1670 Unable to open connection to supplicant on "wlan0": No such file or directory
It seems like a permission issue to me not a hardware fault. LIke I mentioned the same happened to me several times (WiFi works, sees the networks but refuses to connect) What is strange that usually a data wipe/clean install solves this.
Actually I think yours is not seeing the networks (scanning):
"configuration found for missing network, ignored"
Not sure is this possible but your /data partition seems not wiped properly. Can you make a factory reset on your current rom?
Hi I see you are posting again "from over the air"
Have you solved it or using another device?
Sent from my HTC Desire S
amidabuddha said:
Hi I see you are posting again "from over the air"
Have you solved it or using another device?
Sent from my HTC Desire S
Click to expand...
Click to collapse
I wish...unfortunately not . I have mobile data (3G/HSDPA) with 1.5 GB traffic and 7.2 Mbps speed. It's enough for browsing the forum, even to download ROMs and updates.
Now I've noticed that not only WiFi is not workind...BT is not working as well. Cannot connect to my car kit and it was working before with almost all the ROMs.Since I first noticed the WiFi problem, I didn't try BT so I think the problem came in the same moment for both. I realy hope that is not something hardware related and it can be fixed. But I just don't know what else to check/do. I wanted to buy an One S but I didn't receive an answer from my carrier yet.
Rapier said:
I wish...unfortunately not . I have mobile data (3G/HSDPA) with 1.5 GB traffic and 7.2 Mbps speed. It's enough for browsing the forum, even to download ROMs and updates.
Now I've noticed that not only WiFi is not workind...BT is not working as well. Cannot connect to my car kit and it was working before with almost all the ROMs.Since I first noticed the WiFi problem, I didn't try BT so I think the problem came in the same moment for both. I realy hope that is not something hardware related and it can be fixed. But I just don't know what else to check/do. I wanted to buy an One S but I didn't receive an answer from my carrier yet.
Click to expand...
Click to collapse
Maybe trying the latest firmware (from the thread that keeps your recovery and hboot). This is the last resort before going for hardware check I suppose...
Sent from my HTC Desire S
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.
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.