-
Notifications
You must be signed in to change notification settings - Fork 325
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
Request: Add support for ADB over Bluetooth #5
Comments
This would be great. Also planning on adb over wifi (mostly for Android TV). Do you think wifi could replace Bluetooth or do we need both? |
Not all Wear devices will get WiFi support so supporting bluetooth too would be better. Not sure there would even be a difference though since they're both just going over TCP/IP from adb's perspective |
I was wondering why the app wasn't working at all. I was using adb via tcp. I think it's pretty common and should be supported. |
This should be fairly easy to implement:
Tested over WiFi (and USB), works well. I noted some more problems related to using the device's serial instead of the ADB identifier. For example:
Which consequently logs:
Perhaps If you want I can prepare a PR but I don't feel too comfortable changing so many parts (basically every place where |
Here's a diff that makes it work over WiFi: master...jlhonora:master Tested APK install, screenshot, video recording and bug report script.
|
@jlhonora Thanks for your patch, it works fine with Moto 360 via bluetooth debug, including screenshot, recording(need tiny changes in the processing script) and bug report. |
@Dibel Great! Could you elaborate on the changes for the processing script? |
@jlhonora Yeah, but the change is for Moto 360's resolution (320x320). I don't know why the original command can't work.
|
If anyone wants to contribute with a pull request that can solve this for all Android Wear screen sizes, I'd be happy to merge it in. Thanks! |
Great. @Dibel, I have some changes that I'd like you to try in a real device, if that's possible. Let's talk via email (joseluishonorato at gmail) and I'll walk you through. Thanks in advance. |
@mortenjust @jlhonora Tested OK on El Capitan with Moto 360. And I also migrated the app to Swift 2 to compile it on Xcode 7. I've created a pull request #67, but please double-check it due to the huge changes. |
Thanks! Went into 1.3. |
Android Wear bluetooth debugging uses TCP port forwarding from the phone to the watch on port 4444, the correct syntax to communicate with a device connected this way is:
adb -s localhost:4444 …
instead of using the actual device's serial number. You should use the device names reported by "adb devices", as that correctly shows localhost:4444 for my Moto 360.
The text was updated successfully, but these errors were encountered: