Okay, I had time to check right now and with the patched ADB as well
as with the unpatched (sdk r3 only!) version work fine under OpenSuSE
11.1 with the rule that I emailed earlier. Make sure to restart the
computer so that the new Udev rules are taken into consideration.

On Jul 24, 1:22 am, "Chris R." <christopher.rabo...@gmail.com> wrote:
> I will let the group know if I manage to develop on my samsung phone.
> However I just checked and am using the android sdk 1.5 r3. Juat to
> check the update patch. I need is not in the current 1.5 r3 android
> sdk release.
>
> P.s.: just realized there is no android specific layout on Google
> groups.
>
> On Jul 23, 10:45 pm, dan raaka <danra...@gmail.com> wrote:
>
> > "android update adb" is highly misleading ..
> > at the source level .. essentially android script it being triggered to
> > parse the addon directory for SDK-addon created by OEM, in that it is
> > looking for ini file which specifies the vendor id. However, as a special
> > case the SDK r3 version already has harcoded support for samsung Galaxy and
> > a motorola (not sure what is the name) device ..
>
> > -Dan
>
> > On Thu, Jul 23, 2009 at 11:55 AM, Olaf Geibig 
> > <olaf.gei...@googlemail.com>wrote:
>
> > > My mini howto works with ubuntu. Maybe the udev rule is not needed or
> > > must be different for open suse. Please read the docs at
> > >http://developer.android.com/intl/de/guide/developing/device.htmland
> > > search the web for developing android under open suse. You just have
> > > to change two things to make it work with the galaxy: change the
> > > vendor id in the udev rule (if there is any) to 04e8 and use the
> > > patched adb binary from my previous post. If you make it work please
> > > post it here.
>
> > > good luck
>
> > > On 23 Jul., 16:17, Xionbox <christopher.rabo...@gmail.com> wrote:
> > > > Hi,
>
> > > > I'm trying to use the Samsung Galaxy on OpenSuSE 11.1 (Linux). I add
> > > > the following line to /lib/udev/rules.d/50-udev-default.rules
> > > > SUBSYSTEM=="usb" SYSFS{idVendor}=="04e8", MODE="0666"
> > > > I also created /etc/udev/rules.d/51-android.rules which has the exact
> > > > same line.
> > > > I also updated adb via "android update adb" and then I restarted the
> > > > adb server. Even after upluging and repluging several times adb still
> > > > doesn't list the device.
>
> > > > Any idea on how the rule should be?
> > > > Thanks in advance.
>
> > > > On Jul 21, 1:21 am, Olaf Geibig <olaf.gei...@googlemail.com> wrote:
>
> > > > > Quick Howto for ubuntu:
>
> > > > > - download SDK 1.5 r3
> > > > > - enable debug mode on the device: Settings -> Applications ->
> > > > > Development -> USB debugging
> > > > > - add udev rule:http://developer.android.com/intl/de/guide/developing/
> > > > > device.html but use Samsung's vendor id instead: SYSFS{idVendor}
> > > > > =="04e8"
> > > > > - replace the adb binary by this one:
> > >http://floe.butterbrot.org/external/adb.gz
> > > > > - to use ddms on a 64 bit system:
> > >http://coffeecokeandcode.blogspot.com/2009/07/ddms-on-ubuntu-64bit.html
>
> > > > > Patched adb thanks to Flori7500 as mentioned in my previous post.
>
> > > > > Cheers, Olaf
>
> > > > > On 18 Jul., 21:13, fexpop <caspar...@googlemail.com> wrote:
>
> > > > > > Hi,
>
> > > > > > on my device the build number is 76XXCSDCBALUM6375. It won't be 
> > > > > > found
> > > > > > by adb, neither on Windows nor on Linux.
>
> > > > > > Regards,
>
> > > > > > Felix
>
> > > > > > On Jul 18, 8:50 pm, dan raaka <danra...@gmail.com> wrote:
>
> > > > > > > can you post what you see in the settings->about .. about the 
> > > > > > > build
> > > info you
> > > > > > > have ..
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers-unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to