<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body dir="ltr" bgcolor="#ffffff" text="#000000">
Gilad Ben-Yossef wrote:
<blockquote cite="mid:4A9A7745.7090707@codefidence.com" type="cite">
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<p style="margin-bottom: 0cm; margin-top: 0pt;">Shachar Shemesh wrote:<br>
</p>
<blockquote cite="mid:4A9A7511.6000506@shemesh.biz" type="cite">
<meta content="text/html;charset=ISO-8859-1"
http-equiv="Content-Type">
<blockquote cite="mid:4A9A73AD.6090305@codefidence.com" type="cite">
<blockquote cite="mid:4A9A706A.70404@shemesh.biz" type="cite">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).<br>
</blockquote>
Not sure, but I'm guessing it might be a problem with your setup,
rather then a Smasung imposed limit. <br>
<br>
Are you sure you have set up the ADB udev rules correctly?<br>
</blockquote>
I'm connecting to other Android devices without a problem.<br>
</blockquote>
<br>
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.</blockquote>
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.<br>
<blockquote cite="mid:4A9A7745.7090707@codefidence.com" type="cite">
You also need to patch the adb client
soruces with the different vendor ID.<br>
</blockquote>
My adb sources already had the Samsung Vendor ID.<br>
<blockquote cite="mid:4A9A7745.7090707@codefidence.com" type="cite"><br>
RTFG, for example:
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://groups.google.com/group/android-developers/msg/ae589dcd4ce8810d?pli=1">http://groups.google.com/group/android-developers/msg/ae589dcd4ce8810d?pli=1</a><br>
<br>
</blockquote>
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:<br>
Bus 004 Device 008: ID 04e8:6640 Samsung Electronics Co., Ltd Usb Modem
Enumerator<br>
<br>
but not in adb:<br>
/tmp$ ./adb devices<br>
List of devices attached<br>
<br>
Either I am missing something else (which is possible), or Cellcom did
remove adb from the device.<br>
<br>
Shachar<br>
<pre class="moz-signature" cols="72">--
Shachar Shemesh
Lingnu Open Source Consulting Ltd.
<a class="moz-txt-link-freetext" href="http://www.lingnu.com">http://www.lingnu.com</a>
</pre>
</body>
</html>