Gilad Ben-Yossef wrote:
Shachar Shemesh wrote:
The Samsung Galaxy, at least as sold by Cellcom, does not run ADB
by default. Even when I set "USB debugging", I cannot see the phone
when I do "adb devices", and cannot connect to it (let alone
install anything on it).
Not sure, but I'm guessing it might be a problem with your setup,
rather then a Smasung imposed limit.
Are you sure you have set up the ADB udev rules correctly?
I'm connecting to other Android devices without a problem.
That's because the USB vendor/product properties for the Samsung are
different then your HTC made ones (different vendor), which means the
udev rule needs to be different.
That would be true had I needed to do anything to get udev to support
the HTC. As things stand, I am mounting the relevant usbfs file system
with write permissions for my user, so I can mount USB devices inside my
VirtualBox machines.
You also need to patch the adb client soruces with the different
vendor ID.
My adb sources already had the Samsung Vendor ID.
RTFG, for example:
http://groups.google.com/group/android-developers/msg/ae589dcd4ce8810d?pli=1
Just to be sure, I made the udev change and used their binary of adb,
and deviec still wouldn't show up. It shows up in lsusb:
Bus 004 Device 008: ID 04e8:6640 Samsung Electronics Co., Ltd Usb Modem
Enumerator
but not in adb:
/tmp$ ./adb devices
List of devices attached
Either I am missing something else (which is possible), or Cellcom did
remove adb from the device.
Shachar
--
Shachar Shemesh
Lingnu Open Source Consulting Ltd.
http://www.lingnu.com
_______________________________________________
Linux-il mailing list
Linux-il@cs.huji.ac.il
http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
