This bug was fixed in the package udev - 165-0ubuntu1
---
udev (165-0ubuntu1) natty; urgency=low
* New upstream release. Switch to Ubuntu-ish version number to avoid
confusing them with Debian's.
- Allow local users ACL access to raw USB devices of mobile phones.
(LP:
** Branch linked: lp:~ubuntu-core-dev/ubuntu/natty/udev/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/316215
Title:
rule to enable use of android's adb
--
ubuntu-bugs mailing list
ubuntu-bu
I fixed that in upstream git:
http://git.kernel.org/?p=linux/hotplug/udev.git;a=commitdiff;h=0e6546c11
** Changed in: udev (Ubuntu)
Status: In Progress => Fix Committed
--
rule to enable use of android's adb
https://bugs.launchpad.net/bugs/316215
You received this bug notification because
Incidentally the current m-p-i rules already also tag the raw USB
device, for UMS devices.
** Changed in: media-player-info (Ubuntu)
Status: In Progress => Fix Released
--
rule to enable use of android's adb
https://bugs.launchpad.net/bugs/316215
You received this bug notification because
Guilherme Salgado [2010-11-04 14:08 -]:
> Martin, while you're at it, can you add the HTC Desire (idVendor 0x0bb4
> and idProduct 0x0c87) as well?
It's already present in upstream trunk, I'll do a release and upload
soon.
Martin
--
Martin Pitt| http://www.piware.de
U
Martin, while you're at it, can you add the HTC Desire (idVendor 0x0bb4
and idProduct 0x0c87) as well? It's not present on natty's
media-player-info.
Thanks!
--
rule to enable use of android's adb
https://bugs.launchpad.net/bugs/316215
You received this bug notification because you are a member
Martin, I agree with you about not to do it by vendors, but It'd be nice
if (as long the bug is for android phones, not just for the N1) we put
the rule also for more phones. At least for the Google's ones, like the
Nexus One (which is pretty extended I think):
# Nexus One
SUBSYSTEM=="usb", ATTR{i
Actually, I think we can do better. Incidentally, the G1 (and other
phones) are already marked as music players, and I see little reason to
not give users raw access to this class of devices. This requires us to
reshuffle the media-player-info rules a bit, but this should be
feasible.
** Changed i
For the same reason that it was removed upstream it would also be quite
a nuisance to maintain this list in the Ubuntu package, but I'm not
opposed to doing that as long as it's precise vendor/product lists.
Juanje's approach of allowing access to all devices from a large set of
vendors would also
That's because upstream decide to remove that:
http://git.kernel.org/?p=linux/hotplug/udev.git;a=commitdiff;h=232f180
I was trying to add suport for more Android devices but they said there was no
good way to manage all the new devices and they were going to remove the
support for specific devic
Confirmed, this isn't working for me either in 10.10:
perseus:[~/src/android/tools] lsusb |grep G1
Bus 001 Device 043: ID 0bb4:0c02 High Tech Computer Corp. Dream / ADP1 / G1
Phone (Debug)
perseus:[~/src/android/tools] sudo getfacl /dev/bus/usb/001/043
getfacl: Removing leading '/' from absolute
Except that I don't seem to have the rights to reopen the bug, so I'll
have to chase someone who does.
BTW, I've tried using adb with a G1 on a fresh Maverick install and I
got the no permissions error. I got that even after adding a rule [1]
identical to the one in http://bazaar.launchpad.net/~v
http://bazaar.launchpad.net/~vcs-imports/udev/trunk/revision/3353 seems
to be the revision that made it possible to use adb with G1 phones, but
the rule added there is no longer present in Maverick's udev or udev
trunk. There's also the fact that this bug is not about making it
possible to use adb
I've been trying to manually configure udev for a while now to be
compatible with adb, I've had to buy a suite of applications for my
phone as an alternative due to the fact it just isn't working. this
would be an awesome feature for android developers on ubuntu.
--
rule to enable use of android'
Well, as I told you above, I sent the patch to upstream but they haven't
pay much attention to it...[1]
Anyway I marked back to Confirmed before because the package released
din't fix this bug. At least not the one is described at the
Description. It was fixed just for a single phone's model and t
Marking back as Fix Released since the original rule is present - once
you've got the new rules in the udev package upstream and there's been a
release, feel free to open a new tracking bug requesting the update (in
case of required freeze exceptions, etc.)
--
rule to enable use of android's adb
Please don't patch the Ubuntu udev package, instead submit the patch to
udev upstream and it will be included when we update
** Changed in: udev (Ubuntu)
Status: Confirmed => Fix Released
--
rule to enable use of android's adb
https://bugs.launchpad.net/bugs/316215
You received this bug n
Actually the bug has been fixed just for the smartphone G1, but not for the
rest. There are a lot of new smartphones that are affected by this issue.
Following the upstream rules about to use ACL instead of give permissions to
everyone I've created a patch for upstream and I've sent to the mailli
@Tero Karvinen: first of all, thank you so much for your answer.
-with wm:
I can see the device with lsusb ONLY with windows mobile:
"Bus 002 Device 002: ID 0bb4:0c13 High Tech Computer Corp. "
so I known the vendor ID and add it in udev rule.
Additionally, I can see HTC in "computer" as "HTC Stor
Perla, the problem is probably not in your udev rule. The device should
show in 'lsusb' listing before you create the rule.
I use 'lsusb' to check for vendor ID before creating the rule.
Check that you have set HOME: MENU: Settings: Applications: Development:
USB debugging: On.
--
rule to enabl
Hello
I've Ubuntu 10.04 and I try to connect my HTC diamond by USB with the original
cable.
I've tried to add rule (SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
and also SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666") and restart
udev, but nothing.
the output of my lsusb:
Bus
This bug was fixed in the package udev - 151-1
---
udev (151-1) lucid; urgency=low
* New upstream release:
- Support for systems with SYSFS_DEPRECATED=y officially dropped.
- Bug fixes.
- Rules updates. LP: #492657, #316215, #259244, #250732.
* Merge additional fixes
9.10 was released in October, while the fix for this bug was committed
in December. It's not available in Ubuntu yet; the bug will be marked
Fix Released when it's available it Lucid (10.04).
--
rule to enable use of android's adb
https://bugs.launchpad.net/bugs/316215
You received this bug noti
When was this fixed? I ask because Im still seeing this problem in 9.10.
Moreover, if the fix is only for the vendors above then I predict there
will be a lot of updates to the vendor IDs since there are going to be a
LOT of new Android devices (not just phones but also media players,
tablets, netb
Pushed as git 4fe41ac
** Changed in: udev (Ubuntu)
Status: Triaged => Fix Committed
--
rule to enable use of android's adb
https://bugs.launchpad.net/bugs/316215
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
Assigned to Scott per comment #24
** Changed in: udev (Ubuntu)
Assignee: (unassigned) => Scott James Remnant (scott)
--
rule to enable use of android's adb
https://bugs.launchpad.net/bugs/316215
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I have been working on getting the Android Debug Bridge (adb, the
Android tool referenced in the original bug report) working with the
Motorola Droid on Ubuntu 9.10. The hardware vendor id is different -
this is a Motorola handset. If this is going to be addressed, should all
the major Android hand
On Sat, Nov 14, 2009 at 05:29:17PM -, Scott James Remnant wrote:
> I think it's just a matter of adding this directly to 70-acl.rules,
> there's unlikely to be many devices in this case, so we can just put
> them in like we do for fingerprint readhers, etc. already.
>
> Maybe something like
>
I think it's just a matter of adding this directly to 70-acl.rules,
there's unlikely to be many devices in this case, so we can just put
them in like we do for fingerprint readhers, etc. already.
Maybe something like
# smart phones
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0c02"
An android-developers thread at http://groups.google.com/group/android-
developers/browse_thread/thread/af53210a9c41ec37/a0abc58971a44ac0?pli=1
suggests:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
which is the same as the one in comment #10 but seems too broad, both in
the devices mat
** Package changed: hal (Ubuntu) => udev (Ubuntu)
--
rule to enable use of android's adb
https://bugs.launchpad.net/bugs/316215
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
htt
#17
First time I attach the ADP1 the ACL is set. But the next time I attach the ACL
is never set and I have to run adb as super-user to get in contact with the
ADP1.
I read the first couple of chapters of the HAL description and it struck
me that the other PDA's (like Palm, PocketPC) are defined
#17
First time I attach the ADP1 the ACL is set. But the next time I attach the ACL
is never set and I have to run adb as super-user to get in contact with the
ADP1.
I read the first couple of chapters of the HAL description and it struck
me that the other PDA's (like Palm, PocketPC) are defined
Matt Zimmerman's post #12 made me think that I may have been sold an HTC
Hero with adb disabled.
Luckily that it not the case - http://www.finalcog.com/htc-hero-android-
adb-0bb4-0c01-ubuntu-jaunty-0bb4-0c02-problem
--
rule to enable use of android's adb
https://bugs.launchpad.net/bugs/316215
Yo
Jason's livejournal post says not to do it that way
Update 2009-07-06: All of this is broken on the latest versions of
various parts as hal is in the process of being aggressively purged from
the newest distros. The new, officially blessed method is to use udev-
acl support which grants access to
Jason D. Clinton said he got this working, in
http://jasondclinton.livejournal.com/73152.html
I haven't looked to see if his configuration was substantially different
from the one I experimented with yet.
--
rule to enable use of android's adb
https://bugs.launchpad.net/bugs/316215
You received
** Attachment added: "patch to set access_control.file based on
pda.platform=android"
http://launchpadlibrarian.net/26668784/20-acl-management.diff
--
rule to enable use of android's adb
https://bugs.launchpad.net/bugs/316215
You received this bug notification because you are a member of Ubu
** Attachment added: "patch to set pda.platform=android property"
http://launchpadlibrarian.net/26668775/10-usb-pda.diff
--
rule to enable use of android's adb
https://bugs.launchpad.net/bugs/316215
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Based on my (new and very basic) understanding of access control in HAL,
the two patches above should cause the active session to have access to
the device node for a connected G1 phone.
It didn't work when I tested it, though. access_control.file was set to
the correct device node path, but its
** Package changed: hal-info (Ubuntu) => hal (Ubuntu)
--
rule to enable use of android's adb
https://bugs.launchpad.net/bugs/316215
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I see the same product id and lshal output for my ADP1.
The 0bb4:0c01 is the id you will see when booting a Dream into HBOOT,
the bootloader. Stock G1s won't be able to do this.
Apparently it's also the id for phones that have adb disabled, and/or an
older version of the firmware, but I can't co
In order to work, adb requires access to /dev/bus/usb// for the
device. Mine (T-Mobile G1) is:
Bus 001 Device 013: ID 0bb4:0c02 High Tech Computer Corp.
A quick Google search indicates that 0bb4:0c01 is used for some other G1
phones. I don't know the difference between the two.
Please
udi = '/org/freedesktop/Hal/devices/usb_device_bb4_c02_HT839GZ23983'
info.linux.driver = 'usb' (string)
info.parent = '/org/freedesktop/Hal/devices/usb_device_1d6b_2__00_1a_7'
(string)
info.product = 'Android Phone' (string)
info.subsystem = 'usb_device' (string)
info.udi = '/org
** Changed in: hal (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: hal (Ubuntu)
Status: Incomplete => Triaged
** Package changed: hal (Ubuntu) => hal-info (Ubuntu)
--
rule to enable use of android's adb
https://bugs.launchpad.net/bugs/316215
You received this bug notificatio
Per Scott's recommendation, this is a HAL rule we need, not udev.
** Changed in: hal (Ubuntu)
Sourcepackagename: udev => hal
--
rule to enable use of android's adb
https://bugs.launchpad.net/bugs/316215
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Changing SYSFS to ATTRS did not fix the issue for me too. However, if I
start the ADB server as root, it works. So it seems to be a permission
issue.
I attach the output of "udevadm info" for the device. Maybe someone with
a better understanding of the udev rules could propose a fix.
** Attachmen
Ok. I just fixed the issue. 50-udev-default.rules was overwriting my
rule stored in 50-android.rules.
[8728] udev_rules_apply_to_event: MODE 0666 /etc/udev/rules.d/50-android.rules:1
[8728] udev_rules_apply_to_event: LINK 'char/189:132'
/lib/udev/rules.d/50-udev-default.rules:4
[8728] udev_rules_
*didn't fix the rule for me. I wish there was a way to edit comments.
--
rule to enable use of android's adb
https://bugs.launchpad.net/bugs/316215
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
Nevermind, changing SYSFS to ATTRS in the rule fix the problem for me.
--
rule to enable use of android's adb
https://bugs.launchpad.net/bugs/316215
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
Could this have something to do with it?:
https://lists.ubuntu.com/archives/jaunty-changes/2009-January/002637.html
It seems SYSFS is now called ATTRS.
--
rule to enable use of android's adb
https://bugs.launchpad.net/bugs/316215
You received this bug notification because you are a member of Ubu
Attached is an attempt at a hal fdi for the G1/Android Dev Phone 1.
Also attached is the output of hald --verbose=yes when plugging in the
device. I attach the log as the device is not getting sufficient
permissions from hal/policykit with access_control.type set to pda.
** Attachment added: "ha
** Attachment added: "20-adb.fdi"
http://launchpadlibrarian.net/21469831/20-adb.fdi
--
rule to enable use of android's adb
https://bugs.launchpad.net/bugs/316215
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
On Thu, 2009-01-15 at 22:18 +, Joel Stanley wrote:
> Generally speaking, adb doesn't allow you to brick your phone. It can
> give you a non-root shell (root on a dev phone, but if you have a dev
> phone there's plenty of ways to brick), install and remove applications,
> pull and push files f
Generally speaking, adb doesn't allow you to brick your phone. It can
give you a non-root shell (root on a dev phone, but if you have a dev
phone there's plenty of ways to brick), install and remove applications,
pull and push files from/to the device.
I saw your new udev-extras package. Not muc
** Changed in: udev (Ubuntu)
Status: New => Incomplete
--
rule to enable use of android's adb
https://bugs.launchpad.net/bugs/316215
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
Would this not give all system users the ability to brick your phone?
--
rule to enable use of android's adb
https://bugs.launchpad.net/bugs/316215
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
56 matches
Mail list logo
