New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Android on emulator loads infinitely #58
Comments
I've had one other report of this internally. Can you paste both the output of the terminal command and the logcat output (if any)? |
Seems Android compiles some classes but does it very slowly. I'll try to wait for 12 hours or so. Maybe it'll finish. |
Looks like it's due to HAXM not loading:
This will cause the emulator to run much slower. Do you have HAXM installed? |
Yes, I have it installed and emulators from Android SDK work just fine. I waited for a little longer and it seems Android entered some kind of a boot-loop. |
Ok, I'll try to take a look at this more but it may not be for a couple weeks since I'm on vacation. My guess is that this is due to HAXM not loading, so if you can solve that then it may fix the issue. Found this after a brief search - hopefully helpful. |
Seems I managed to load the emulator with HAXM support by manually loading HAXM kext with
Add the emulator even managed to load Android but it took quite a long time comparing to default emulators from Android SDK. |
I encounter the same problem, also installed HAXM from Android Studio and manually, but neither work. |
Finally solve this problem, I tried those steps one by one, but I don't know which one really works.
The booting of emulator takes several minutes (5-10 mins for me). |
@CheerS17 That seems like a long time for a HAXM emulator. Are you sure HAXM successfully loads? Mind pasting the logs from the |
I think so, I can see this log: emulator:
here are all outputs after typing Launching emulator... emulator: Found target API sdkVersion: 25 emulator: Invalid int property: 'ro.build.version.incremental:eng.leland.20180507.124526' emulator: System image is read only emulator: trying to find: ~/Library/Android/sdk/emulator/lib/pc-bios/bios.bin emulator: trying to find: ~/Library/Android/sdk/emulator/vgabios-cirrus.bin emulator: trying to find: ~/Library/Android/sdk/emulator/lib/pc-bios/vgabios-cirrus.bin emulator: control console listening on port 5554, ADB on port 5555 emulator: onGuestSendCommand: [0x7f8394610fa0] Adb connected, start proxing data |
I am also facing the same issue . Is this issue fixed? Zip already downloaded: /Users/pavanbilagi/.nanoscope/roms/c1sEHfsSLhstgkhc6EcnQQ==... emulator: Found target API sdkVersion: 25 emulator: Invalid int property: 'ro.build.version.incremental:eng.leland.20180507.124526' emulator: System image is read only HAXM is not working and emulator runs in emulation mode emulator: Kernel parameters: qemu=1 no_timer_check androidboot.hardware=goldfish clocksource=pit no-kvmclock android.qemud=1 console=0 android.checkjni=1 qemu.gles=1 qemu.opengles.version=131072 ndns=4 loop.max_part=7 qemu.dalvik.vm.heapsize=256m emulator: trying to find: /Users/pavanbilagi/Library/Android/sdk/emulator/lib/pc-bios/bios.bin emulator: trying to find: /Users/pavanbilagi/Library/Android/sdk/emulator/vgabios-cirrus.bin emulator: trying to find: /Users/pavanbilagi/Library/Android/sdk/emulator/lib/pc-bios/vgabios-cirrus.bin emulator: control console listening on port 5554, ADB on port 5555 emulator: OpenGL Vendor=[Google (Intel Inc.)] |
The same for me and when i use haxm i am getting |
@warabei14 Trying to reinstall the HXAM, the first time it may take a long time to load the emulator, but it will be faster for the following loadings. |
Looking at |
In addition to @ashishb reply. Try to remove
From |
This issue in the Google bug tracker might be helpful. |
The latest version of Nanoscope creates a proper AVD with the nanoscope emulator command. Please update to the latest version brew upgrade nanoscope and re-open if this doesn't fix your issue. |
I wanted to try nanoscope on emulator, installed it from Homebrew, launched the emulator with
nanoscope emulator
but the emulator never finished launching. Unfortunately, I don't know what information I need to provide so you can reproduce this issue. But I'm ready to try it again and send you some logs.The text was updated successfully, but these errors were encountered: