tag:blogger.com,1999:blog-3581505770205891021.post3194962279184370849..comments2020-11-25T20:20:31.830+09:00Comments on Nicolas Raoul's blog: Developing on an Android device using Ubuntu 9.04Nicolas Raoulhttp://www.blogger.com/profile/08422064640500287012noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-3581505770205891021.post-65712290292968973302009-11-12T21:00:29.769+09:002009-11-12T21:00:29.769+09:00Well, it is working with SUBSYSTEM and ATTR, it is...Well, it is working with SUBSYSTEM and ATTR, it is not a typo.<br /><br />My instructions also work on Ubuntu 2009.10 Karmic Kaolo, I just tried.Nicolas Raoulhttps://www.blogger.com/profile/08422064640500287012noreply@blogger.comtag:blogger.com,1999:blog-3581505770205891021.post-63536874772885884372009-11-08T14:58:00.249+09:002009-11-08T14:58:00.249+09:00Well I found another post but can't seem to pa...Well I found another post but can't seem to paste into this edit window.. and it's a very long URL. Needless to say, the udev rules you typed in was missing a letter (or at least it seems to be)<br /><br />You have SUBSYSTEM and it should be SUBSYSTEMS, as well it should be ATTRS not ATTR. But I could be wrong..I added that in and it seems to work now.<br /><br />Anyway, the one link shows the following for the moto droid:<br /><br />SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", ATTRS{idProduct}=="41db", MODE="0666", OWNER="your username here"<br /><br />For some reason ATTRS instead of SYSFS?? Not sure the diff on this rules file. As well, the OWNER at the end, and keep in mind the ATTRS has TWO = signs after each (as does the SUBSYSTEMS), the MODE and OWNER only have a single =.<br /><br />Make sure your Moto Droid is NOT plugged in (if it is, unplug it, then plug it in again) AFTER you run the adb kill-server command. Then, adb devices seems to list some long number instead of a name. At least now when I run my app from Eclipse, it runs on my Moto Droid.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3581505770205891021.post-12602204115772030182009-11-08T14:36:24.682+09:002009-11-08T14:36:24.682+09:00Incidentally, I DID select the motorolla id info, ...Incidentally, I DID select the motorolla id info, still not working.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3581505770205891021.post-94225054114497692009-11-08T14:35:55.701+09:002009-11-08T14:35:55.701+09:00Well..this may be old.. but I just got my Droid an...Well..this may be old.. but I just got my Droid and am trying what you put there. Problem is, adb devices lists as:<br /><br />??????????? no permissions<br /><br />not sure why this is? I put the droid into USB debug mode, selected to mount it, folder opens up on my Ubuntu 9.04 showing the contents. It is clearly "seeing" it, but it's not able to determine it I guess?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3581505770205891021.post-18456698020140264892009-10-16T08:25:48.193+09:002009-10-16T08:25:48.193+09:00That's because the Galaxy is produced by Samsu...That's because the Galaxy is produced by Samsung, not HTC.<br />So I guess the vendor id is 04e8 instead of 0bb4.<br /><br />More information at the top of this page:<br />http://ghantoos.org/2009/08/08/running-debian-on-a-samsung-galaxy-under-android/<br /><br />Cheers,<br />Nicolas Raoul.Nicolas Raoulhttps://www.blogger.com/profile/08422064640500287012noreply@blogger.comtag:blogger.com,1999:blog-3581505770205891021.post-20641000367099553992009-10-16T06:20:53.701+09:002009-10-16T06:20:53.701+09:00I follow your instruction... unfortunetaly list of...I follow your instruction... unfortunetaly list of devices is empty with a Galaxy USB connected and USB Debug...Anonymousnoreply@blogger.com