10-19-2011 04:02 PM
Background: I upgraded my playbook to 2.0, downloaded the eclipse plug-in, turned on debug mode, set up a debug token, right clicked my project and clicked "Add Blackberry Nature" in eclipse, and finally right clicked and clicked Run as "Blackberry Application" in eclipse. (that was to get you up to speed on how I got to the problem)
The Problem: The problem is after it compiles for a minute, Eclipse pops up a window that says
"'Launching <app name>' has encountered a problem - Connecting 169.254.0.1 to ADB failed!"
and in the Console output I see
[<date> - BlackBerry] unable to connect to 188.8.131.52:5555.
I also tried connecting from the command line adb with the same result. I have restarted the playbook, eclipse, and the computer multiple times with no changes. I am at a loss for how to proceed with testing my android app on the playbook. Any help or advice is greatly appreciated.
10-19-2011 04:10 PM
10-19-2011 04:17 PM
Thanks for the suggestion. I was really hoping to be able to test it without signing, but I guess I might have to fall back to using the online tool.
I hope to eventually find a solution with the plugin though because if something doesn't work right, fixing and then using the online tool in an endless loop seems like it would get old fast.
12-07-2011 04:13 AM
Im new here. Im having trouble connecting adb to my playbook. Ive tried to ping the device in terminal and has reply,but when i try to connect with adb it says unable to connect. and i tried to view the device using adb device but nothing recognize.
Please help. and im using mac is there any issue regarding to it?
Thank you all
12-21-2011 01:30 PM
Same issue here. 'Instaling' signed apps on the Playbook works every time, but 'Running' or 'Debugging' an unsigned app always errors out with 'unable to connect to ADB'....
12-23-2011 06:24 PM
Take a look at the following thread. It describes how to solve this problem.