I believe there is a conflict in latest versions of Ubuntu, try to rename
your 50-android-something
rule file to 51-android-something, because Ubuntu recently added another
50-something file that
appears to be resetting/overriding the definitions here.
There does not appear to be another udev rules file starting with 50
in Ubuntu Jaunty.
I did find a workaround that works: Remove (or comment-out) the udev
rule, and set permissions on adb to run as root. Rebooted, and now
"adb devices" results in...
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT91RLZ01056 device
...I just got this result moments ago, so I have not checked that
everything depending on this functions correctly, but it's progress
relative to where I was.
On Apr 15, 4:03 pm, David Turner <di...@android.com> wrote:
> I believe there is a conflict in latest versions of Ubuntu, try to rename
> your 50-android-something
> rule file to 51-android-something, because Ubuntu recently added another
> 50-something file that
> appears to be resetting/overriding the definitions here.
> Let us know if this works.
> On Wed, Apr 15, 2009 at 9:56 PM, Zigurd <zigurd.medni...@gmail.com> wrote:
> > Trying to get an Ubuntu Jaunty system to talk to a dev phone. I have
> > the 1.5 sdk and the new master branch of the sources.
My not-very-elegant "solution" indicates this is a permission issue.
The udev rule appears to set permissions, so it probably isn't being
run. It would be nice to verify the udev rule match, but I'm a udev
n00b and can't find what the ATTRS (formerly SYSFS) rule is supposed
to match.
I just reformatted and installed Ubuntu 9.04 (Jaunty) and I appear to
be experiencing this same issue. My G1 just isn't recognized, but it
worked fine in Ubuntu 8.10. What exactly is the process to get things
working again in 9.04?
On Apr 15, 3:36 pm, Zigurd <zigurd.medni...@gmail.com> wrote:
> My not-very-elegant "solution" indicates this is a permission issue.
> The udev rule appears to set permissions, so it probably isn't being
> run. It would be nice to verify the udev rule match, but I'm a udev
> n00b and can't find what the ATTRS (formerly SYSFS) rule is supposed
> to match.
DavidG wrote: > I just reformatted and installed Ubuntu 9.04 (Jaunty) and I appear to > be experiencing this same issue. My G1 just isn't recognized, but it > worked fine in Ubuntu 8.10. What exactly is the process to get things > working again in 9.04?
I just had the same problem. With some help from the #android irc channel, I managed to get it working using:
> DavidG wrote:
> > I just reformatted and installed Ubuntu 9.04 (Jaunty) and I appear to
> > be experiencing this same issue. My G1 just isn't recognized, but it
> > worked fine in Ubuntu 8.10. What exactly is the process to get things
> > working again in 9.04?
> I just had the same problem. With some help from the #android irc
> channel, I managed to get it working using:
Hi,
I had the same problem.
I was very skeptical about renaming the file to 51-android.rules,
because as you said, there are no other files with a name starting
with 50-...
but well, I tried, thinking that maybe, in some other directories, or
whatever...
And it solved my problem !
Hope it will work for you as well !
Best.
On Apr 15, 4:36 pm, Zigurd <zigurd.medni...@gmail.com> wrote:
> My not-very-elegant "solution" indicates this is a permission issue.
> The udev rule appears to set permissions, so it probably isn't being
> run. It would be nice to verify the udev rule match, but I'm a udev
> n00b and can't find what the ATTRS (formerly SYSFS) rule is supposed
> to match.
I am also having problems with Jaunty/Android 1.5.
I currently have 1.1 installed on my phone. It is the dev phone.
I am using Jaunty x86_64, and have installed the ia32-libs package.
I ran adb server as root with a "sudo adb start-server," and I'm able
to see my device using "adb devices." Following the HTC update guide
(http://www.htc.com/www/support/android/adp.html) I next try to push
the ota-radio image to the phone using "adb push ..." and nothing
happens. The command appears to hang.
I tried mounting using the phone's software, and I'm able to browse
the sdcard in Nautilus, but any attempt to modify the sdcard results
in another hang.
I tried reboot the phone and the computer. I've been unable to find
any information on the Internet similar to this problem. Is there
something else I can do to find some more diagnostic information to
get past this problem?
> Hi,
> I had the same problem.
> I was very skeptical about renaming the file to 51-android.rules,
> because as you said, there are no other files with a name starting
> with 50-...
> but well, I tried, thinking that maybe, in some other directories, or
> whatever...
> And it solved my problem !
> Hope it will work for you as well !
> Best.
> On Apr 15, 4:36 pm, Zigurd <zigurd.medni...@gmail.com> wrote:
> > My not-very-elegant "solution" indicates this is a permission issue.
> > The udev rule appears to set permissions, so it probably isn't being
> > run. It would be nice to verify the udev rule match, but I'm a udev
> > n00b and can't find what the ATTRS (formerly SYSFS) rule is supposed
> > to match.
> On Apr 23, 8:04 pm, YC <lep...@gmail.com> wrote:
> > Hi,
> > I had the same problem.
> > I was very skeptical about renaming the file to 51-android.rules,
> > because as you said, there are no other files with a name starting
> > with 50-...
> > but well, I tried, thinking that maybe, in some other directories, or
> > whatever...
> > And it solved my problem !
> > Hope it will work for you as well !
> > Best.
> > On Apr 15, 4:36 pm, Zigurd <zigurd.medni...@gmail.com> wrote:
> > > My not-very-elegant "solution" indicates this is a permission issue.
> > > The udev rule appears to set permissions, so it probably isn't being
> > > run. It would be nice to verify the udev rule match, but I'm a udev
> > > n00b and can't find what the ATTRS (formerly SYSFS) rule is supposed
> > > to match.
> On Apr 23, 8:04 pm, YC <lep...@gmail.com> wrote:
> > Hi,
> > I had the same problem.
> > I was very skeptical about renaming the file to 51-android.rules,
> > because as you said, there are no other files with a name starting
> > with 50-...
> > but well, I tried, thinking that maybe, in some other directories, or
> > whatever...
> > And it solved my problem !
> > Hope it will work for you as well !
> > Best.
> > On Apr 15, 4:36 pm, Zigurd <zigurd.medni...@gmail.com> wrote:
> > > My not-very-elegant "solution" indicates this is a permission issue.
> > > The udev rule appears to set permissions, so it probably isn't being
> > > run. It would be nice to verify the udev rule match, but I'm a udev
> > > n00b and can't find what the ATTRS (formerly SYSFS) rule is supposed
> > > to match.
After completing the above procedure and trying to browse the SD card
unsuccessfully a few times (unable to mount error)
It popped to life, i.e once I could see the SD card adb also started
working ...
Any explanation ?
On May 15, 9:36 pm, avrono <avr...@mail.com> wrote:
> > On Apr 23, 8:04 pm, YC <lep...@gmail.com> wrote:
> > > Hi,
> > > I had the same problem.
> > > I was very skeptical about renaming the file to 51-android.rules,
> > > because as you said, there are no other files with a name starting
> > > with 50-...
> > > but well, I tried, thinking that maybe, in some other directories, or
> > > whatever...
> > > And it solved my problem !
> > > > My not-very-elegant "solution" indicates this is a permission issue.
> > > > The udev rule appears to set permissions, so it probably isn't being
> > > > run. It would be nice to verify the udev rule match, but I'm a udev
> > > > n00b and can't find what the ATTRS (formerly SYSFS) rule is supposed
> > > > to match.
Try running adb as root
./adb kill-server;./adb devices
If you then see the dev phone you could ; chown root.root adb;chmod
4777 adb
This will run adb as root automagically.
Tom
On Apr 16, 5:56 am, Zigurd <zigurd.medni...@gmail.com> wrote:
What worked for me was to add “SYMLINK+=”android_adb”" to the rules
file so it would read:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", SYMLINK+="android_adb",
MODE="0666"
Here's what works for me on Ubuntu Karmic with my Htc Dream (Vendor ID
0bb4 as seen with 'lsusb') :
- device in usb debug mode (settings/applications/developpment/)
- in file /etc/udev/rules.d/51-android.rules :
SUBSYSTEM==”usb”,ATTRS(idVendor)==”0bb4“,SYMLINK
+="android_adb",MODE=”0666″
Renaming the rules file to -51- worked for me on my desktop computer,
but not on my laptop. On my laptop, I renamed to 99, then it worked.
There's a bug in Ubuntu, the software for one of the lower number
rules does something that's not finished when rule 50 gets fired. I
guess the slower your computer, the more time you need to give this
feature to finish.
On Aug 29, 12:03 pm, Rino <renaud.chail...@gmail.com> wrote:
> Here's what works for me on Ubuntu Karmic with my Htc Dream (Vendor ID
> 0bb4 as seen with 'lsusb') :
> - device in usb debug mode (settings/applications/developpment/)
> - in file /etc/udev/rules.d/51-android.rules :
> SUBSYSTEM==”usb”,ATTRS(idVendor)==”0bb4“,SYMLINK
> +="android_adb",MODE=”0666″
