Do it while your Android and development machine screens are unlocked.
If your device is showing up as Offline, accept the Allow USB Debugging permission prompt on your Android device. The Remote Target has successfully detected an offline device that is pending authorization If you see the model name of your Android device, then DevTools has successfully established the connection to your device. The first time you do this, you usually see that DevTools has detected an offline device. The Discover USB Devices checkbox is enabledĬonnect your Android device directly to your development machine using a USB cable. Make sure that the Discover USB devices checkbox is enabled.įigure 2. On your development machine, open Chrome. See Configure On-Device Developer Options. Open the Developer Options screen on your Android. See Troubleshooting: DevTools is not detecting the Android device for more help. Remote Debugging lets you inspect a page running on an Android device from your development machine.
Then retrieve the name of your AVDs : emulator -list-avds
In your Terminal go to the folder tools of your Android sdk to find the 'emulator' program: cd ~/Library/Android/sdk/tools What did the trick for me was to launch in command line my AVD and giving manually the Google public DNS 8.8.8.8.
If while trying the below solution you get the following message "PANIC: Missing emulator engine program for 'x86' CPU.”, then please refer to to update your bash environment.įor some reasons, I wasn't able to access internet through my AVD at work (probably proxy or network configuration issues).
So, how to fix? Simple: Disable your LAN card. Not a problem when you're connected via that LAN, but utterly useless if you're on a wireless connection. I think some of the answers may have addressed this, however obliquely, but here's what worked for me.Īssuming your problem is occurring when you're on a wireless network and you have a LAN card installed, the issue is that the emulator tries to obtain its DNS settings from that LAN card.