Solved!!! Flori7500 from the German andoid community had fixed the linux adb issue. See his changeset: https://review.source.android.com/#change,10728
Looks like he didn't notice the actual changes in the current head concerning the Samsung vendor id constant, but I guess he will merge his changes to adb/usb_linux.c into the head. If you can't wait and/or build your own SDK he posted a linux binary on a german Samsung Galaxy forum: http://www.android-hilfe.de/o2-samsung-galaxy-i7500-forum/4021-adb-jetzt-auch-auf-dem-galaxy.html#post38582 Kudos to Flori as he saved my day. Cheers, Olaf On 19 Jul., 14:08, legerb <drim...@gmail.com> wrote: > Something like that ;-) > > On Jul 14, 7:11 pm, David Turner <di...@android.com> wrote: > > > 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... > > > 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 -~----------~----~----~----~------~----~------~--~---
