You need a different version of ADB to access this phone at the moment. A future release of the SDK will provide an ADB binary that should be able to do that, but this is not available yet as far as I know.
You're quite on the bleeding edge, aren't you ;-) On Tue, Jul 14, 2009 at 6:05 PM, legerb <drim...@gmail.com> wrote: > > Hey, > I just got this device too. Trying to figure out how to debug on > device too. > According this > http://groups.google.com/group/android-beginners/browse_thread/thread/167b279683bddc8a > Samsung have their own adb. > Please update the thread if you've got any progress :) > > thanks ahead! > > On Jul 11, 10:54 pm, da yang <daboil...@googlemail.com> wrote: > > Hi > > i got this new mobilephone this week in Germany, wanted to debug my > > program on the device. but it doesn't work, "c:\>adbdevices" lists > > no device attached, though i have tried to change the > > "android_usb.inf" in order to install the usb driver from SDK. > > i added some entries as follows: > > under > > [Google.NTx86] > > > > ; HTC DREAM > > ... > > > > ; SAMSUNGGALAXY > > %USB\VID_04E8&PID_6640. > > DeviceDescRelease%=androidusb.Dev, USB > > \VID_04E8&PID_6640 > > %USB\VID_04E8&PID_6640&MI_01.DeviceDescRelease%=androidusb.Dev, USB > > \VID_04E8&PID_6640&MI_01 > > %USB\VID_04E8&PID_6640.DeviceDescRelease%=androidusb.Dev, USB > > \VID_04E8&PID_6640 > > > > and [Strings]: > > > > USB\VID_04E8&PID_6640.DeviceDescRelease="SAMSUNGGALAXY" > > USB\VID_04E8&PID_6640&MI_01.DeviceDescRelease="SAMSUNGGALAXY > > CompositeADBInterface" > > USB\VID_04E8&PID_6640.DeviceDescRelease="SAMSUNGGALAXYBootloader" > > > > i got only one VID and one PID through > > USBVIEW, though for HTC DREAM there are different PIDs used. > > Theadbinterface got installed, butadbjust didn't work. > > > > later i also tried to use the device under linux, set up the device as > > in Dev guide: > > > > If you're developing on Ubuntu Linux, you need to add a rules file: > > > > 1. Login as root and create this file: /etc/udev/rules.d/51- > > android.rules. > > > > For Gusty/Hardy, edit the file to read: > > SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666" > > > > For Dapper, edit the file to read: > > SUBSYSTEM=="usb_device", SYSFS{idVendor}=="0bb4", MODE="0666" > > 2. Now execute: > > chmod a+rx /etc/udev/rules.d/51-android.rules > > > > "adbdevices" listed nothing as well. : ( > > > > open a terminal on the device, with "ps", i guess theadbdaemon > > "adbd" is running. > > but theadbtool just doesn't work. > > > > Can someone help me? > > > > thanks da > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
