Unfortunately it seems to be very difficult to determine if the emulator is ready to be used. I'd would come to the same conclusion myself.)
Android device emulator for mac cordova android#
Despite it's name, it has nothing to do with it being an android core (which I think was probably what the original author of the cordova codebase thought, with no blame. It looks like it works on cold boots, but eventually the process is killed (probably when it isn't being used). I don't believe scanning for the is a reliable way to determine if the system is booted. I have a workaround that just requires me to run the emulator from the Android Studio AVD Manager and then runĮven ps -A to return all processes, including processes owned by root fails to have listed.įurther research shows that is a process responsible for android's ContactsProvider system.
I'm not 100% sure what the steps would be to fix this. So it seems it be an issue with cordova running the adb command. Running command: adb -s emulator-5584 shell getprop dev.bootcompleteĬommand finished with error code 1: adb -s,emulator-5584,shell,getprop,dev.bootcompleteĪnd then it just keeps looping. Running adb shell command "getprop dev.bootcomplete" on target emulator-5584.
0 kommentar(er)
