Comments on: Getting Android SDK to work with Fedora 10

By: Katharina Posto

Katharina Posto — Mon, 17 Jan 2011 20:57:48 +0000

When i visit a blog, chances are that i get disappointed. On the contrary,I could honestly say that you writting is decent and your website solid.

By: Marius Mathiesen

Marius Mathiesen — Thu, 25 Nov 2010 12:37:17 +0000

The SYSFS identifier seems to be deprecated in newer Fedora/udev builds, I wrote a recipe for how to get it running under Fedora 14 as a gist here: https://gist.github.com/715264

By: nwk

nwk — Sat, 05 Jun 2010 06:32:43 +0000

Your post was the solution to the device permissions problem I was having with Fedora 12.
http://forums.fedoraforum.org/showthread.php?t=246154

Thanks for taking the time to post this!

By: 7 String Bass

7 String Bass — Thu, 13 May 2010 06:56:03 +0000

Its always good to discover tips in the event that you discuss for weblog posting. Because simply started posting comments for blog and facing issue associated with associated with rejections. I think your own suggestion will useful for me. I will in its work for me too.

By: David Khosid

David Khosid — Wed, 29 Jul 2009 12:35:10 +0000

Hi,

’50-android.rules’ name is problematic. It should be at least 51-android.rules to be alphabetically after /lib/udev/rules.d/50-udev-default.rules

I tried your recipe for connecting Android Dev Phone 1 on Fedora 11. It worked after I with ATTR{idVendor} and udevadm command

Two questions:
1. Why you add SYMLINK+=”android_adb” to its content? It works fine without it also.

2. As I checked, the system uses original files, it’s no need to reload. Why we need to reload rules?

NB, the command is slightly different from mike’s mail.
# sudo udevadm control –-reload-rules

Also, looking on syslog output (#tail -f /usr/var/messages) helped in investigating the problem, this way I understood that it was a problem in the file name.

Thanks a lot to you both!

David