FS#55576 - [android-tools] Android-Tools 8.0_r4-2 Breaks ADB/MTP

Attached to Project: Community Packages
Opened by Christopher Napoli (Annoyingduck) - Sunday, 10 September 2017, 14:52 GMT
Last edited by Anatol Pomozov (anatolik) - Tuesday, 19 September 2017, 23:46 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Anatol Pomozov (anatolik)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 5
Private No

Details

Running Arch XFCE LTS kernel, also tested on Arch Cinnamon LTS, and Manjaro Cinnamon LTS (same results).

Just updated android-tools from the 7.1.2_r27-1 to 8.0_r4-2. Phone connects to pc as usual, but as soon as you try to enable MTP, the phone disconnects immediately and continues to bounce between being connected/unconnected until you reboot the pc (nothing wrong phone side other than the usb connection status/usb debugging going on and off in the status bar). Result differs device to device. On my Moto X Pure I could not connect to ADB at all. Even in charge only mode, as soon as an ADB command is given the device disconnects, along with no MTP access at all. On my LG-G3, ADB works while the phone's USB setting is in charge only mode, but not in MTP mode - device disconnects. The LG can maintain an MTP connection, but no storage locations are shown (blank in the file manager).

Downgrading back to 7.1.2_r27-1 fixes the issue - ADB/MTP work as they should. Android-udev is unaffected, the latest update works on both versions of android-tools. So for now I'm operational, just wanted the issue noted here.
This task depends upon

Closed by  Anatol Pomozov (anatolik)
Tuesday, 19 September 2017, 23:46 GMT
Reason for closing:  Upstream
Comment by oneup40 (oneup40) - Monday, 18 September 2017, 03:39 GMT
Can confirm with Arch stock linux kernel and android-tools-8.0.0_r4-2. Can't connect to an Asus Zenfone (2? or 3?) via adb. "adb devices" doesn't show the phone, KDE (systray) notifier continually fires showing new Android device, journalctl shows kernel messages repeatedly indicating USB disconnect and reconnect.

Downgrading to android-tools-7.1.2_r27-1 made the problem go away.
Comment by Anatol Pomozov (anatolik) - Monday, 18 September 2017, 18:56 GMT
I do not think it is an Arch packaging issue. Most likely it is problem in USB request handling in adb. I would suggest to send this information upstream developers for investigation.

Also there are two things you can try:
- I just pushed 8.0.0_r11 update to [community-testing]. It does not seems to contain a lot of adb issue. But anyway it worth trying.
- I adopted the build script for Android master branch and pushed it as a package to AUR [1]. I see that Android master has a lot of USB related fixed. Your problem might be fixed as well. Try to install android-tools-git and please share your experience with this package.

[1] https://aur.archlinux.org/packages/android-tools-git
Comment by Christopher Napoli (Annoyingduck) - Tuesday, 19 September 2017, 01:56 GMT
Just tested the AUR package android-tools-git r34543.424ed42fb-1 as Anatol suggested and everything is working properly, so there's definitely something broken in the current android-tools-8.0.0_r4-2 community repo package. ADB & MTP all work as they should, with ADB access via charging and MTP. I would advice pushing this package to the repo sooner than later.
Comment by Anatol Pomozov (anatolik) - Tuesday, 19 September 2017, 23:46 GMT
Thanks for confirming that it is a software bug in upstream version 8.0. AUR package android-tools-git is based on VCS sources and not going to move to stable repository. The best way to resolve the issue it to report the problem to upstream developers and ask them to cherry-pick bugfixes to stable branch (8.0.0).

Until then you have two options:
- downgrade to 7.0 version
- use AUR version

Loading...