10-20-2011 01:44 AM
I have Eclipse plugin installed and when I try to run the application from Eclipse, it says: Connecting 192.168.3.102 to ADB failed!
Yes, I'm trying to deploy over wifi, the device is added, dev mode is on, debug token is there, signing keys are fine, it does connect and launch the android player on the device but immediately after that I get above error.
Any help is highly appreciated.
10-20-2011 03:16 AM
Okay, things got fixed. There were apparently two things that I was doing wrong.
1. I was being imnpatient. I just saw the android player and the app did not load... ABORT ABORT
2. I'm not sure. There could be something wrong on wifi, things worked on usb, debug token, run configuration, im trying to figure out what went wrong.
10-20-2011 03:27 AM
Ok, it's confirmed, deploy over wifi not working for me ![]()
10-25-2011 02:54 PM
This is a known issue
"Unable to launch a run/debug configuration on a Wi-Fi connected device. (2059211, 2143889)
Workaround: Connect the target device through USB."
See here: https://bdsc.webapps.blackberry.com/android/docume
12-21-2011 11:29 PM
It does not work over WiFi and USB here.
It always successfully 'installs' signed apps. When trying to 'run' an unsigned app, it always successfully launches the Android Player on the device, but then immediately pops up the 'failed to connect to ADB' dialog.
The same thru WiFi or USB. Software version is 2.0.0.6149.
12-22-2011 11:11 PM
12-23-2011 12:41 AM - edited 12-23-2011 01:01 AM
Yes. I also have the 16.0.1.20111215 version of Android Dev Tools here.
Edit: looks like Google simply does not have v15 available for download anymore, all they link to is v16.0.1 now...
12-23-2011 07:26 AM
I've got this issue resolved for Playbook device (2.0.0.6149) by updating to version 1.0.2.201112120946 of BlackBerry Plug-in for Android Development Tools (net.rim.ajde.feature.feature.group) and BlackBerry Tools SDK for Android Development Tools (blackberry.tools.sdk.feature.feature.group). I was not able to deploy my app on VM simulator (2.0.0.4867). But it behaves differently now - stays in "Connecting to ADB..." state instead of "ADB connection failed".
Still it is a good holiday present from RIM.
12-23-2011 11:54 AM
Yes, indeed it works now. RIM is playing catch-up with Google.
12-23-2011 04:49 PM