3.2 WiFi problem...My findings. May help you.

---

Great discussion from the following thread:
http://forum.xda-developers.com/show....php?t=1191792

Thanks to know Static IP can temporary solve the connection problem.

BUT I found somethings:
1. A lot of 3.1 users upgraded to 3.2, BUT NOT ALL Users report such WiFi (grey icon / disconnect irregularly) problem.

2. A lot of people use DHCP, lot of lot users have no such problem. Some of us posted here are annoying with such WiFi problem, however, static IP can help.

3. Therefore the problem relates DHCP and Static IP.

My guess:
1. Maybe most of us (with WiFi problem) used DHCP BUT with IP reservation (I use reservation).
2. Most users (without WiFi problem (my friend's TF doesn't have grey problem)) use only the DHCP without IP reservation.

My testing and result:
1. Firstly, I disable the IP reservation (192.168.1.11) for the TF
2. Then set the DHCP range to 192.168.1.2 to 192.168.1.8 (1-7 for other devices)
3. Then I set the TF to DHCP
4. Finally, TF gets the 192.168.1.8
5. Then I use File Manager HD to get a 619MB file from my desktop to TF (Two times testing)
6. Wow, it's SMOOTH!!! Before DHCP with IP reservation...only can download around 100MB then disconnected. Now, no more disconnection

My conclusion (or you may try too):
With 3.2, don't set your router to have IP reservation with your TF, just set DHCP, MAC mapping (it's fine, no problem, WPA2-PSK (it's fine too).

Bros and Sis, if your TF faces WiFi problem after upgrading to 3.2, you may try my solution.

If your TF and router work well again with DHCP without IP reservation, my prediction is correct.

If my prediction is correct, please spread this message, to let TF fans, Xoom, Asus, Google to know it!

Please help to try and use back your DHCP.

Good Luck!

Just removed my IP reservation. Wifi icon now blue. Will let you know if this helps my disconnects

EEE Pad Transformer sent this

I have rooted 3.2 and no Wi-Fi problems. However, when I look at the syslog files from my router I see:

Aug  7 10:36:19 tomato dnsmasq-dhcp[100]: DHCPREQUEST(br0) 192.168.10.128 14:da:XX:XX:XX:XX 
Aug  7 10:36:19 tomato dnsmasq-dhcp[100]: DHCPACK(br0) 192.168.10.128 14:da:XX:XX:XX:XX  Transformer-R
Aug  7 10:38:43 tomato dnsmasq-dhcp[100]: DHCPREQUEST(br0) 192.168.10.128 14:da:XX:XX:XX:XX  
Aug  7 10:38:43 tomato dnsmasq-dhcp[100]: DHCPACK(br0) 192.168.10.128 14:da:XX:XX:XX:XX  Transformer-R
Aug  7 10:41:08 tomato dnsmasq-dhcp[100]: DHCPREQUEST(br0) 192.168.10.128 14:da:XX:XX:XX:XX 
Aug  7 10:41:08 tomato dnsmasq-dhcp[100]: DHCPACK(br0) 192.168.10.128 14:da:XX:XX:XX:XX  Transformer-R

The Transformer is doing a DHCP request every 3 minutes or so. This is exceptionally frequent, and could cause the connection to drop if a) there are existing network problems that prevent the request from going through successfully or b) the DHCP server gets pissed off and stops responding.

PS: I obscured the MAC address in the log sample on purpose.

Originally Posted by rtadams89

I have rooted 3.2 and no Wi-Fi problems. However, when I look at the syslog files from my router I see:

Aug  7 10:36:19 tomato dnsmasq-dhcp[100]: DHCPREQUEST(br0) 192.168.10.128 14:da:XX:XX:XX:XX 
Aug  7 10:36:19 tomato dnsmasq-dhcp[100]: DHCPACK(br0) 192.168.10.128 14:da:XX:XX:XX:XX  Transformer-R
Aug  7 10:38:43 tomato dnsmasq-dhcp[100]: DHCPREQUEST(br0) 192.168.10.128 14:da:XX:XX:XX:XX  
Aug  7 10:38:43 tomato dnsmasq-dhcp[100]: DHCPACK(br0) 192.168.10.128 14:da:XX:XX:XX:XX  Transformer-R
Aug  7 10:41:08 tomato dnsmasq-dhcp[100]: DHCPREQUEST(br0) 192.168.10.128 14:da:XX:XX:XX:XX 
Aug  7 10:41:08 tomato dnsmasq-dhcp[100]: DHCPACK(br0) 192.168.10.128 14:da:XX:XX:XX:XX  Transformer-R

The Transformer is doing a DHCP request every 3 minutes or so. This is exceptionally frequent, and could cause the connection to drop if a) there are existing network problems that prevent the request from going through successfully or b) the DHCP server gets pissed off and stops responding.

PS: I obscured the MAC address in the log sample on purpose.

The transformer isn't doing any DHCP requests based on it's own logic. It is all based on the length of the lease at the router handing out the DHCP requests (which runs dhcpd). If you have control of the router, you can set the lease length. All the transformer does is find out that it's lease has expired and fetch the same one again (usually, based on arp tables, etc).

My router has the DHCP lease time fro non-static (static DHCP configured from the router, not static IP configured on the client) addresses set to 24 hours. For static DHCP address the lease time is infinite. In both cases, the Transformer does a DHCP request every 3 minutes or so.

Originally Posted by rtadams89

My router has the DHCP lease time fro non-static (static DHCP configured from the router, not static IP configured on the client) addresses set to 24 hours. For static DHCP address the lease time is infinite. In both cases, the Transformer does a DHCP request every 3 minutes or so.

In that case, it's just weird. Based on reading that, I looked at the router log at home and mine isn't doing that but of course I could see the original DHCP request. I'm running 3.2 US rooted (whatever latest build is of that), no custom ROM, and as far as DHCP, it is behaving.

Yeah, I could see how an endless series of requests could cause trouble for our cheap home routers. Is there any chance that something else on your network is spitting out dhcpd services? If I were going to try to troubleshoot it, I'd setup another wifi router(some older cheap one would do) on it's own network, disconnect from your primary router, and point it at the new / old one, and see what it did over there. With only the two players, it might be easier to tell. For that matter if you've got a phone with wifi tether, I guess that would be a good test.

Does the logcat on the TF also note these DHCP requests?

Originally Posted by hachamacha

Is there any chance that something else on your network is spitting out dhcpd services?

No other DHCP servers on the network.

Originally Posted by hachamacha

If I were going to try to troubleshoot it, I'd setup another wifi router(some older cheap one would do) on it's own network, disconnect from your primary router, and point it at the new / old one, and see what it did over there. With only the two players, it might be easier to tell. For that matter if you've got a phone with wifi tether, I guess that would be a good test.

I tether to my phoen via bluetooth, so I can't really check that and I don't have any other routers that would show me enough log detail to see that info. What I did do is disable the router's DHCP/DNS services and instead used one of my Linux VMs to handle those services on the network. Same problem.

Originally Posted by hachamacha

Does the logcat on the TF also note these DHCP requests?

Yes.

What I have done though is remove the static DHCP lease for the transformer, and it let it be assigned completely randomly. I'm reviewing the logs now, but it seems to not be requesting a lease as often. I'm not sure if that is an issue with how the router is handing out "infinite" leases (I'm not sure if it just sets a lease expiration as some large value, or if it sets it as zero, or if it doesn't even send that parameter at all).

If I do this command:

#getprop | grep lease

I get back something like this:

response: *wlan0*lease* : 84600

----

I was wondering what your's shows? I got interested in this when I noticed init.ventana.rc kicking off dhcpcd (client daemon) that uses for config /system/etc/dhcpcd/dhcpcd.conf so poked around some more.

Looking at this man page:

http://roy.marples.name/cgi-bin/man-cgi?dhcpcd.conf

(sorry, but no clue if all those work on android)

It does make me wonder if the leasetime parameter works? It says this:


leasetime seconds
Request a leasetime of seconds.

The problem is usually that the busybox/hacked down versions of these utilities like dhcpcd involves drastically reduced functionality.

Apparently on mine, it is working as intended since 84600 seconds is the lease length ala my router and is what it shows as the 'given lease time' on my TF, so I wonder if at that level it is showing up the same.

I use a linux box to do my DHCPD duties. So far I've tried both mac address based allocation of address and just allowing my TF to get one from the pool - there didn't appear to be any difference between the two.

With the default lease time set to 600 seconds and the max set to 7200 I was getting a request for dhcp renewal every couple of mins :

08-06 09:53:37.660 D/DhcpStateMachine(  130): DHCP request on wlan0
08-06 09:53:38.060 D/DhcpStateMachine(  130): DHCP succeeded on wlan0
08-06 09:53:38.070 D/WifiStateMachine(  130): netId=0 Link configured: InterfaceName: wlan0 LinkAddresses: [192.168.1.17/24] Gateways: [192.168.1.254,] DnsAddresses: [192.168.1.101,192.168.1.254,] HttpProxy:  
08-06 09:53:38.090 D/ConnectivityService(  130): addDefaultRoute for WIFI (wlan0), GatewayAddr=192.168.1.254
08-06 09:56:02.450 D/DhcpStateMachine(  130): DHCP renewal on wlan0
08-06 09:56:02.850 D/DhcpStateMachine(  130): DHCP succeeded on wlan0
08-06 09:56:02.850 D/WifiStateMachine(  130): Link configuration changed for netId: 0 old: InterfaceName: wlan0 LinkAddresses: [192.168.1.17/24] Gateways: [192.168.1.254,] DnsAddresses: [192.168.1.101,192.168.1.254,] HttpProxy:  new: InterfaceName: wlan0 LinkAddresses: [192.168.1.17/24] Gateways: [192.168.1.254,] DnsAddresses: [192.168.1.101,192.168.1.254,] HttpProxy:  
08-06 09:56:02.880 D/ConnectivityService(  130): addDefaultRoute for WIFI (wlan0), GatewayAddr=192.168.1.254
08-06 09:58:27.130 D/DhcpStateMachine(  130): DHCP renewal on wlan0
08-06 09:58:27.330 D/DhcpStateMachine(  130): DHCP succeeded on wlan0
08-06 09:58:27.340 D/WifiStateMachine(  130): Link configuration changed for netId: 0 old: InterfaceName: wlan0 LinkAddresses: [192.168.1.17/24] Gateways: [192.168.1.254,] DnsAddresses: [192.168.1.101,192.168.1.254,] HttpProxy:  new: InterfaceName: wlan0 LinkAddresses: [192.168.1.17/24] Gateways: [192.168.1.254,] DnsAddresses: [192.168.1.101,192.168.1.254,] HttpProxy:  
08-06 09:58:27.370 D/ConnectivityService(  130): addDefaultRoute for WIFI (wlan0), GatewayAddr=192.168.1.254

I then changed the default lease time and the max lease time to 84600 (24 hours) and am getting practically none of these ... only when I turn on my TF since I have the wifi set to disable on screen off. - And obviously I don't see my wifi indicator go grey or loose network connectivity.

My first question is why when the lease time is set to 600 seconds is it making the request after 2 mins ?

It looks to me like it is dropping at least part of its layer 3 config when it goes through this process.

I have used IP reservations since the very first connection to my router, which included MAC filtering. I have never had my connection drop, at least none that I'm aware of.

Mind you, I buy a new router every year, to improve performance, for better implementations of standards, better compatibility, etc.

Those having issues may want to test another router.


Sent from my Transformer TF101 using XDA Premium App