The problem seems to be that the emulator can't find the DNS my computer is currently using, and the temporary workaround is to start the emulator from the command line and specify the DNS server. Note that this thread talks about Android SDK 2.3, not Android Studio 2.3. I found a temporary solution on an old Stack Overflow thread at Upgraded to SDK 2.3 - now no emulators have connectivity. If it still doesn't work, then wipe, but save that as a last resort. This allows the network emulation to start with clean memory and connect properly. Memory is not wiped, it is saved.ĭoing a cold boot is the same as rebooting your phone or rebooting your PC. When you shut off the emulator and restart it, it is like putting your PC in hibernate or sleep mode. It is unnecessary unless the data is totally corrupt. Ok, for those saying why not just wipe data and restart.ĭo you reformat your PC every time you restart it? Wiping data on the emulator is just like doing a factory reset to a phone or reformatting your hard drive on your PC and reinstalling your OS. Note that you may need to change -avd Pixel_2_API_28 part (with your own Virtual-Device name).Īlso, most tools use ANDROID_HOME environment-variable name, hence define that (if not already), but nowadays ANDROID_ROOT is yet another naming-option.
Or for MacOSX: $ANDROID_HOME/emulator/emulator -netdelay none -netspeed full -no-snapshot-load -avd Pixel_2_API_28 In case you start Emulator through command, pass -no-snapshot-load option, like: %ANDROID_HOME%/emulator/emulator.exe -netdelay none -netspeed full -no-snapshot-load -avd Pixel_2_API_28 Lo and behold my emulator has internet connectivity again! Command-line approach After trying many of these solutions, I was going to just delete my current AVD and make it again, but when I clicked the down arrow on the AVD, I noticed "Cold Boot Now".
0 kommentar(er)
