Not able to connect Android Wear Emulator with Device

Question

I am not able to connect Android Wear Emulator with my device.I have HTC One device which has 4.4 (KitKat OS).

I follow below link :

Setting up Android Wear<

Answer 1

1. Enable adb debugging in the developer options on your watch.
2. Enable bluetooth debugging in the developer options on your watch.
3. Enable bluetooth debugging in the wear app on your phone. run in terminal:
4. adb forward tcp:4444 localabstract:/adb-hub; adb connect localhost:4444

See this training.

I think I also had luck with using the cradle plugged directly into the computer, but unable to confirm that now.

Answer 2

@Lance Nanek basically helped me solved this problem. In case you had the similar problem, these steps might be helpful.

1. run 'adb devices' , you should see two devices, one is your emulator, the other is your device with Android Wear Preview app installed.

2. you might see your emulator offline, if so, kill the emulator. From avd, start it, carefully uncheck 'launch from snapshot' - this is contrast to Android Wear Get started instruction: "Start the AVD again, but select Launch from snapshot and deselect Save to snapshot."

3. run 'adb devices' again, make sure you do see two devices online
4. run command 'adb -d forward tcp:5601 tcp:5601'
5. from the android wear preview app, tape connect, you should be ready to go.

Answer 3

Run the adb -d forward tcp:5601 tcp:5601 command in super user mode

Answer 4

After some hours trying to find the solution... I've found it!

In my case, the problem was that I have two different SDKs (one from Eclipse and the other from Android Studio), so I was trying to execute the ADB commands in the wrong one.

So it is important that you check the path you are using in your IDE and execute the commands on the same.

Answer 5

On the newly updated Android Wear app (Aug 2014) there is a settings button top right when asked to choose a device connected via bluetooth. Pressing this button will connect to an emulator instead.

Answer 6

The trouble I was having, was that the pre-selected API level was set incorrectly. It should be set to the following values:

Using Host GPU is optional.