In general, I want to run the Android Wear emulator, I created a virtual device, in the Run Configuration I select the module (wear) and I launch it - but nothing happens, the logs are empty, 0 reactions. I tried to start the module first (phone), and then (wear) - also nothing, the phone starts up, and wear . There are suspicions that there is not enough disk space (2 GB left on the SSD), can this be?

When I start the mobile device emulator, I see this:

HAXM is not working and emulator runs in emulation mode

I understand rather this problem!?

UPD enter image description here

When trying to change the amount of memory, let's say up to 512 - it seems to save, but after that it writes 1 gb to 'Size on disk'

  • How many emulsions are allocated for the RAM? - Android Android
  • @AndroidAndroid now seems to see the cause of the problem! What should I do to reduce the amount of allocated memory? and why the clock can write 'Failed to load'? - Kirill Stoianov
  • It seems that gig for nexus is minimal salary. And about the error - have you installed Android tools in the SDK manager-e? - Android Android
  • @AndroidAndroid yes, I install Intel HAXM and increased the amount of memory from 512 to 1024, like all the rules. Now it’s not clear only, the wear module can’t be simply run on the emulator, you must first run the application on the phone emulator and install the application on the clock emulator through it? - Kirill Stoianov
  • one
    stackoverflow.com/questions/3152681/… right here, take a look. The problem can be - Android Android

1 answer 1

The problem on which it was impossible to start the clock emulator, or it was launched but with a black screen and offline was as follows:

  1. SDK Tools: Intel x86 Emulator Accelerator (HAXM installer) - you had to install it and increase the amount of allocated memory so that it is not less than what is allocated for your device in the emulator.

  2. SDK Manager: Android Wear Intel x86Atom System Image - it must be installed for a specific version 4.4, 5.0.1, etc. In my case, I installed the firmware version 5.0.1 for the watch, and Android Wear Intel x86Atom System Image was installed only for 4.4, thus lowering the firmware version for the watch to 4.4 - the problem was solved. I think if I left 5.0.1 on the clock and installed Intel Wear Intel x86Atom System Image for the same firmware, the result was the same.