We are disussing this issues in several threads already. let's please
focus and switch to the thread at the android developers froup:
http://groups.google.com/group/android-developers/browse_thread/thread/726ea864e89985ec
On 17 Jul., 22:41, "ludovic.perrier" <barbapa...@gmail.com> wrote:
> Hello
>
> I try to do this also from france on mac
>
> regards
>
> On 14 juil, 13:11, da yang <daboil...@googlemail.com> wrote:
>
> > it doesn't work. i have tried it. the devcie can be identified by
> > system as usb mass storage though.
>
> > 1500 mAh on the galaxy VS 1150 mAh, and AMOLED saves more energy, you
> > can judge. it's OK for using but not for development, when the adb
> > can be
> > used.
>
> > On 7月13日, 下午11时45分, Gabriel Branch <mugaf...@gmail.com> wrote:
>
> > > Try uninstalling all of your usb devices then let the OS reinstall them
> > > all
> > > and keep the phone plugged in and debugging on while you do it.
>
> > > How is the battery life on that galaxy? Better than the dream?
>
> > > On Sun, Jul 12, 2009 at 5:24 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?
>
> > > > thanks da
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Beginners" group.
To post to this group, send email to android-beginners@googlegroups.com
To unsubscribe from this group, send email to
android-beginners-unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-beginners?hl=en
-~----------~----~----~----~------~----~------~--~---
