Thread: [Android] Apps for NITdroid
View Single Post
Vid is offline Vid
2008-12-19 , 21:03
Posts: 12 | Thanked: 23 times | Joined on Jul 2008
#6
Originally Posted by Sevanteri View Post
I'm still having trouble with the adb.
I did just what the instructions said, and it still doesn't work.

Trying to run sudo ./adb devices but it just doesn't show my NIT...

Should the NIT show something on the screen when you plug the USB?
No, there's nothing different on the tablet screen to show that adb is working. If you list the USB devices on your host will see a device named `adb driver' when the USB cable is connected. This device will show `Android' as the manufacturer, with product ID 0x0001, serial number 0123456789ABCDEF, and vendor ID 0x18d1.

What OS are you using for adb?

EDIT: I think I've found the problem, at least for MacOS. The adb source code only recognizes the following vendor and product IDs (see http://android.git.kernel.org/?p=pla...09a44e;hb=HEAD and http://android.git.kernel.org/?p=pla...1a6482;hb=HEAD)

Code:
 355 // Google's USB Vendor ID
 356 #define VENDOR_ID_GOOGLE        0x18d1
 357 // HTC's USB Vendor ID
 358 #define VENDOR_ID_HTC           0x0bb4
 359 
 360 // products for VENDOR_ID_GOOGLE
 361 #define PRODUCT_ID_SOONER       0xd00d  // Sooner bootloader
 362 #define PRODUCT_ID_SOONER_COMP  0xdeed  // Sooner composite device
 363 
 364 // products for VENDOR_ID_HTC
 365 #define PRODUCT_ID_DREAM        0x0c01  // Dream bootloader
 366 #define PRODUCT_ID_DREAM_COMP   0x0c02  // Dream composite device
Since the product ID for NITdroid isn't 0xd00d or 0xdeed, adb doesn't properly attach to the tablet. We either need to build our own adb binaries, or figure out how to get NITdroid to use a different product ID :-(

Note that this isn't a problem for Windows, as the .inf file specifies the product IDs. So for now, adb only works from a Windows host.
Last edited by Vid; 2008-12-19 at 21:48. Reason: Updated info