Jaye,
Those are good suggestions but neither solved the problem and I even
tried them again when I read your post just to be sure! Also keep in
mind that it works on my Windows machine so I know that Tab is running
the service correctly.
On Sep 6, 7:01 am, Jaye <jfranklin...@gmail.com> wrote:
> This happened on my galaxy tab 7. For me to fix my issue, I either
> restarted thedeviceor toggled the ability to debug application on
> thedevice.
>
> On Sep 5, 10:15 am, RodneyJLambert <rodney.j.lamb...@gmail.com> wrote:
>
>
>
>
>
>
>
> > I have a Ubuntu development system that I have been using to do
> > Android development and until this week theADBwould detect my Galaxy
> > Tab 10.1, now theADBwill not list the tab as an availabledevice.
>
> > lsusb shows :
>
> > $ lsusb
> > Bus 002Device046: ID 04e8:685e Samsung Electronics Co., Ltd
> > Bus 002Device005: ID 059b:0370 Iomega Corp.
> > Bus 002Device004: ID 0518:0001 EzKEY Corp. USB to PS2 Adaptor v1.09
> > Bus 002Device003: ID 058f:6254 Alcor Micro Corp. USB Hub
> > Bus 002Device002: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop
> > Laser
> > Bus 002Device001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> > Bus 001Device001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
> >adbdevices returns :
> > $./adbdevices
> > List of devices attached
>
> > 51-android.rules :
> > SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
> > SUBSYSTEM=="usb", SYSFS{idVendor}=="22b8", MODE="0666"
> > SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666"
> > SUBSYSTEM=="usb", SYSFS{idVendor}=="1004", MODE="0666"
>
> > The result of running uname -r is :
> > 2.6.35-30-generic
>
> > Ubuntu 10.10
>
> > Android SDK Tools, revision 12
> > Android SDK Platform-tools, revision 6
>
> > TheADBcanseemy other devices (G2 and G2X) like normal. It seems
> > like something has changed in Ubuntu that is causing the Galaxy Tab
> > 10.1 to be treated differently that it was two weeks ago! It is also
> > worth mentioning thatADBon my Windows Vista system canseethe tab.
>
> > Does anyone have any ideas about what might have changed to cause a
> > valid targetdeviceto suddenly no longer be detected byADB?
--
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
