Bug 1044744

Summary: adb from android-tools doesn't work on Android 4.4
Product: [Fedora] Fedora Reporter: Andy Lutomirski <luto>
Component: android-toolsAssignee: Ivan Afonichev <ivan.afonichev>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: ivan.afonichev
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-18 17:12:25 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:

Description Andy Lutomirski 2013-12-18 21:58:13 UTC
I think that something changed about the authentication scheme.  It always says "device offline".

Comment 1 Andy Lutomirski 2013-12-20 22:58:52 UTC
FWIW, if you fix this, would you be willing to consider packaging the systemd unit and the rules file separately?  I've had much better luck with a more standard rules file setting mode 0660 and a sensible group.

Comment 2 Ivan Afonichev 2013-12-21 19:51:00 UTC
I'am able to use adb with my Nexus 5(Android 4.4.2). 
For systemd usage there is a bug https://bugzilla.redhat.com/show_bug.cgi?id=967216 
I'll fix it

[van@vanzen ~]$ lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 18d1:4ee2 Google Inc. Nexus 4 (debug)
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 064e:f300 Suyin Corp. UVC 0.3M Webcam
Bus 001 Device 005: ID 13d3:3375 IMC Networks Atheros AR3012 Bluetooth 4.0 Adapter
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[van@vanzen ~]$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached 
03af1d62d0243fc5	device

[van@vanzen ~]$ adb shell
shell@hammerhead:/ $