I got this working in windows XP (french), but not following any of
the suggestions I have seen so far exactly:
1) Set the device in debug mode, under applications (mentioned
everywhere, clearly required)
2) Install Samsung New PC Studio (not sure this actually did anything
useful...)
3) Install the USB Driver from the Samsung New PC Studio disk (not
sure this actually did anything useful...)
4) Modify the "android_usb.inf" file in the android SDK folder (C:
\Program Files\android-sdk-windows-1.5_r3\usb_driver
\x86\android_usb.inf, for 32-bit windows), ALMOST exactly as "da yang"
specified in the first post of this thread:
add under
[Google.NTx86
; SAMSUNG GALAXY
%USB\VID_04E8&PID_6640.DeviceDescRelease%=androidu sb.Dev, USB
\VID_04E8&PID_6640
%USB\VID_04E8&PID_6640&MI_04.DeviceDescRelease%=an droidusb.Dev, USB
\VID_04E8&PID_6640&MI_01
%USB\VID_04E8&PID_6640.DeviceDescRelease%=androidu sb.Dev, USB
\VID_04E8&PID_6640
and add under [Strings
USB\VID_04E8&PID_6640.DeviceDescRelease="SAMSUNG GALAXY"
USB\VID_04E8&PID_6640&MI_04.DeviceDescRelease="SAM SUNG GALAXY
Composite ADB Interface"
USB\VID_04E8&PID_6640.DeviceDescRelease="SAMSUNG GALAXY Bootloader"
NOTE: the only change with respect to "da yang"'s original entries
were replacing "MI_01" with "MI_04" in all entries. When originally
trying da yang's suggestions the INF file was not working for me, and
looking into the unknown device's properties I noticed this
discrepancy.
5) plug in the phone, allow all the USB mass storage and standard
samsung drivers to install, and finally when you are asked for drivers
for an unknown device, point windows to your "C:\Program Files\android-
sdk-windows-1.5_r3\usb_driver\x86\" folder with your modified INF file
(assuming 32-bit windows).
If windows recognizes the device, great! If it complains that the INF
file does not contain information for the device, or something like
that, try looking at the properties of the unknown device in device
manager - you might have a different device signature.
After windows successfully recognized the device, I was able to debug
in Eclipse connected directly to my phone - very cool. I guess adb
started recognizing it, but I honestly haven't messed with the command-
line tools yet - I can just confirm that the fully integrated
Eclipse / Android SDK / Android Plugin debug environment works
perfectly.
One other note that might be relevant: I used the "Samsung New PC
Studio" software to update my Galaxy to the latest image BEFORE I did
any of this; I suspect that may be what caused the discrepancy in
terms of device signature with respect to "da yang"'s original notes,
but I can't be sure.
Hopefully this helps someone out there!
Best regards,
Tao
Click to expand...