Bug 962179

Summary:	Fedora 17 update breaks ADB for Android 4.x device
Product:	[Fedora] Fedora	Reporter:	Tim Jowers <timjowers>
Component:	udev	Assignee:	udev-maint
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	jonathan, udev-maint, zaitcev
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-05-12 11:06:03 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Tim Jowers 2013-05-12 10:50:01 UTC

Description of problem:
latest update broke USB debugging with Android

Version-Release number of selected component (if applicable):
uname -a
Linux fedorabook 3.8.11-100.fc17.x86_64 #1 SMP Wed May 1 19:31:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

How reproducible:
Every time

Steps to Reproduce:
1. Start Eclipse
2. Go to DDMS (perspective from Android plugin)
3. Click on device listed as ??????????
  
Actual results:
Cannot see log. Cannot push to device.

Expected results:
Prior to system update could see device and could debug with it.

Additional info:

Prior to the update a pup up dialog would come up at the bottom of the screen when the USB device was inserted. now it does not. The older samsung phone with Andorid 2.2 still shows in the DDMS but the newer with 4.1 I think it is no longer does. This is a nightmare as most of our apps are now using 4.x plus features and this will make debugging almost impossible.
Devices do show in lsusb. The computer does make a "plugging in" sound feedback for both devices.

Comment 1 Tim Jowers 2013-05-12 11:06:03 UTC

Parsing of udev rules must have changed. Fix is to use different format.
Bus 003 Device 011: ID 1004:61a6 LG Electronics, Inc. 

prior in 51-android.rules:
SUBSYSTEM=="usb",SYSFS{idVendor}=="1004",MODE="0666"
above was on line 1 in 51-android-rules. It fails and shows as 
???????????   no permissions

Fix
SUBSYSTEM=="usb", ATTRS{idVendor}=="1004", MODE="0666"


restart udev (as root):
service udev restart

./adb devices
(starts adb)

plugin device
(still no longer has pop up windows as fedora used to have)

./adb devices
List of devices attached 
443C000600000001015D9CE60102200C	device

exit root.
started Eclipse as user.
See in DDMS and can see log.

Note. adb was started as root but maybe not a reason this is working. Will find out next time I reboot I guess.

Reference: 
http://stackoverflow.com/questions/9210152/set-up-device-for-development-no-permissions

I think this bug can be closed as there is a work-around.