Access Point for WiFi is “AP”.
I see the wired eth0 never has an IP address, so I am assuming wired is not plugged into any router or AP.
I see when it works wlan0 has the suggested 192.168.100.170 address. Typical for having WiFi active. When not working wlan0 has no address. Typical for WiFi going down. Do note that the micro-USB virtual ethernet of 192.168.55.1 is a different subnet, and so it is possible that route setup (a combination of both the host and the Jetson) might be of interest.
Is it possible to see the “route” on your Android? Also, what does the “route” command show on both working and failing circumstances from the Jetson? I am basically interested in a more verbose list of information from what @WayneWWW is suggesting with the “traceroute” command (hoping your Android can run traceroute, it might be able to). Knowing simultaneously these three things for both failing and working circumstances would be useful, especially if this can be run on both Android and Jetson:
ifconfigto show addresses;routeto show which gateways or direct routes would be used;tracerouteto see what devices are being traversed.
Also, a Jetson has the ability to do some testing via ssh from itself to itself. In theory, if the micro-B USB is connected (even if the other end doesn’t work, this is just to set up address 192.168.55.1), then you could log in to the Jetson locally and test:
ssh localhostssh 192.168.55.1ssh 192.168.100.170
Further, one could do some similar ping tests, but to the connected Android from the Jetson:
ping 192.168.55.100# Note that this is the IP address from virtual micro-USB at the Android end.ping 192.168.100.170# This is essentially self-ping, but through another interface.ping 192.168.100.4# Note that direction of ping from Jetson to Android might differ compared to ping from Android to Jetson due to any kind of firewall rule or due to route setup.