Latest 4.2 build is not able to find the device and aft-mtp-cli has some broken output.

[Animeshz]

Re of https://github.com/void-linux/void-packages/issues/34321#issuecomment-984730376 as an upstream bug.

Short Description:

android-file-transfer outputs probing device... is being printed more than expected times (seems like device is not found), and also aft-mtp-cli says device not found (filter = '' (some broken text).

Tried/Tested on:

• Device: Vivo V20 (V2040)
• Laptop: Acer Swift 3 SF314-42 (AMD)
• OS: Void Linux (glibc)

~~Works fine at 4.0, issue experienced in 4.2~~

[Animeshz]

Oopsie, it was not a bug but missing warning of not running as superuser/root... Running with sudo solves the problem, but the software should explicitly state that sudo permissions are required at startup, and the broken text at aft-mtp-cli should be fixed.

[hkienle]

For me it works without sudo (Debian 10.0):

$ ./Android_File_Transfer-cce42ee-x86_64.AppImage 
Gtk-Message: 14:45:46.739: Failed to load module "atk-bridge"
upload worker started 
current text color value:  0 , guessed theme:  "light" 
scan
probing device...
probing device...
probing device...
probing device...
probing device...
device found, opening session... 
device info "ZTE"   "ZTE Blade A5 2020" 
mtpz-data path:  "/home/xxx/.mtpz-data" 
switching to storage id  65537 
session opened, starting