[TouchPad General] mikedill24:
Mind Blown

First, I'd like to start out by saying THANK YOU to all involved with this latest round of improvements. My mind is blown. I cannot believe how simple it is to flash different versions of Android on the TP. I have been able to get each version of the ROM ssuccessfully flashed and running on my TPs. Overall, performance is very good with each.

I do, however, have one issue I am unable to figure out. My WiFi keeps dropping on version 7.1, 8 and 9 of Android. I did a logcat to try and get more visibility. Here's a snippet of what was captured. The below disconnect messages are the same on 7.1, 8 and 9. I have tested all three.

===============================================

IpReachabilityMonitor: ALERT: NeighborEvent{elapsedMs=206531134, fe80::a02:8eff:fe0a:48e2, [(null)], RTM_NEWNEIGH, NUD_FAILED}

IpReachabilityMonitor: FAILURE: LOST_PROVISIONING, NeighborEvent{elapsedMs=206531134, fe80::a02:8eff:fe0a:48e2, [(null)], RTM_NEWNEIGH, NUD_FAILED}

WifiStateMachine: ConnectedState !CMD_IP_REACHABILITY_LOST rt=206531200/206531186 FAILURE: LOST_PROVISIONING, NeighborEvent{elapsedMs=206531134,

WifiStateMachine: L2ConnectedState !CMD_IP_REACHABILITY_LOST rt=206531200/206531187 FAILURE: LOST_PROVISIONING, NeighborEvent{elapsedMs=206531134,

WifiStateMachine: FAILURE: LOST_PROVISIONING, NeighborEvent{elapsedMs=206531134, fe80::a02:8eff:fe0a:48e2, [(null)], RTM_NEWNEIGH, NUD_FAILED}

WifiNative: : [206,531,187,300 us] DISCONNECT stack:logDbg - disconnect - handleIpReachabilityLost - -wrap22 - processMessage

WifiNative-wlan0: doBoolean: DISCONNECT

wpa_supplicant: wlan0: CTRL-EVENT-DISCONNECTED bssid=08:02:8e:0a:48:e3 reason=3 locally_generated=1

===============================================

I've tried 2.4Gz and 5Gz. I've played around with changing Channels on my router. Rebooting, etc. The lower versions of Android do not seem to have this problem but I cannot use them because some of the apps I need to run do not work on version 4 or 5 of Android, which leaves me with 7.1, 8 or 9. So, a catch-22 situation.

Behaviorally, the end impact of the above is slightly different between 7.1 and 8/9. In 7.1, when the disconnect happens my Home Networks are still available in the list of available networks. I can go in and manually reconnect. As a temporary workaround I use this App called Automate. I have a Flow that checks if the network is connected and if not reconnect. The problem is that the network disconnects too much, so it's become to common of a scenario to be in the middle of something and have network cutout. Extremely frustrating.

For some reason, AutoConnect does not occur. In versions 8/9 of Android my Home Networks are somehow being "blacklisted". They no longer show up in the List of Available Networks. I can see them in the Saved Networks section but cannot connect to them and Scanning does not find them. If I reboot the device it can now see my Home Networks, connects successfully but then shortly thereafter encounters the above disconnect and if I want to reconnect I have to reboot.

In searching the almighty Google I've found some posts stating it may be possible to workaround it by disabling ipReachabilityMonitor.

So, a few questions:

1. First, anyone else encountering this? I don't believe it's hardware related because the lower versions of Android do not seem to encounter this issue.

2. Anyone aware of a known fix for this issue? I could not find anything concrete.

3. Is it possible to comment out the code related to ipReachabilityMonitor, to test if this does have an impact? If so, can someone help me to do so?

Thanks in advance.

Mike