I believe you checked most of all about adb without SDK.
* check your SDK supports SAMSUNG VID(0x04e8).
original sources for SDK doesn't support that VID.
If not supported, modify codes and build sdk.
then exchange new adb.exe and AdbWinApi.dll under tools
On Jul 14, 8:45 pm, Xinyu Chen <muddo...@gmail.com> wrote:
> Here some suggestions:
> * check init.rc, adbd service will be started or not
> * check /dev/android_adb*, this is android adb enable misc driver.
> * check adb gadget drivers are loaded in /sys/devices/
>
> On Jul 12, 4:04 am, 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:\> adb devices" 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
> > ...
>
> > ; SAMSUNG GALAXY
> > %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="SAMSUNG GALAXY"
> > USB\VID_04E8&PID_6640&MI_01.DeviceDescRelease="SAMSUNG GALAXY
> > Composite ADB Interface"
> > USB\VID_04E8&PID_6640.DeviceDescRelease="SAMSUNG GALAXY Bootloader"
>
> > i got only one VID and one PID through
> > USBVIEW, though for HTC DREAM there are different PIDs used.
> > The adb interface got installed, but adb just 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
>
> > "adb devices" listed nothing as well. : (
>
> > open a terminal on the device, with "ps", i guess the adb daemon
> > "adbd" is running.
> > but the adb tool just doesn't work.
>
> > Can someone help me?
>
> > thanks da
>
>
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---
