Because two days ago, I upgraded Android studio from version 2 . three . Upgrade 3 to 3 . 3. At the same time, we also upgraded the SDK, including the emulator to 27 . x。 Then the nightmare began. After the simulator starts successfully, the Android studio card cannot be connected, and waiting for target device to come online is displayed. I read the related posts of stack overflow again, but it didn’t work out. In the end, there was no way to do it. They almost wanted to reload the operating system (fortunately, it’s still the same problem after the reload). Before reloading, I took an old SDK from another machine. As a result, I was able to run and finally found the problem with the emulator. Lesson: if you have no problem with IDE, don’t always upgrade. The hairline is rising again. p>
My system: win7 p>
div>
Similar Posts:
- [Solved] PANIC: Missing emulator engine program for ‘x86’ CPUS.
- Android Studio Emulator: PANIC: Cannot find AVD system path. Please define ANDROID_SDK_ROOT (Solved)
- AS Install Error: Cannot find AVD system path. Please define ANDROID_SDK_ROOT
- Emulator: Process finished with exit code 1
- [Solved] Emulator: dsound: Could not initialize DirectSoundCapture
- Android studio change project name exception solution: can’t rename root module
- Install and run Android in Androidx86 emulator – This adb server’s $ADB_VENDOR_KEYS is not set
- [Solved] No accelerator found – failed to create HAX VM
- SVN You need to upgrade the working copy first.
- [Solved] Ionic Error: Could not find gradle wrapper within Android SDK.