Red Hat Bugzilla – Bug 1478580
why is usb reset on close forced on android devices ?
Last modified: 2017-08-04 16:54:25 EDT
I noticed that the behavior of libmtp via gvfs is to reset an android device when it is closed, based on the macro DEVICE_FLAGS_ANDROID_BUGS containing the value DEVICE_FLAG_FORCE_RESET_ON_CLOSE in device-flags.h.
On my samsung I9300, it has the side effect that it's not possible to make gvfs unmount the device /and/ let the device stay unmounted. After issuing the command "gio mount -u mtp://xxxx", the device immediately reappears with an incremented device number, and will be automatically mounted again by gvfs (the default gsettings parameter /org/gnome/desktop/media-handling/automount is true).
Aug 03 13:53:30 kernel: usb 3-1: reset high-speed USB device number 44 using xhci_hcd
Aug 03 13:53:30 kernel: usb 3-1: USB disconnect, device number 44
Aug 03 13:53:31 kernel: usb 3-1: new high-speed USB device number 45 using xhci_hcd
Aug 03 13:53:31 gvfsd: Android device detected, assigning default bug flags
Aug 03 13:53:31 kernel: usb 3-1: New USB device found, idVendor=04e8, idProduct=6860
Aug 03 13:53:31 kernel: usb 3-1: New USB device strings: Mfr=2, Product=3, SerialNumber=4
Aug 03 13:53:31 kernel: usb 3-1: Product: GT-I9300
Aug 03 13:53:31 kernel: usb 3-1: Manufacturer: samsung
I'm wondering if this bug flag is (still) required for android devices in the context of the gnome desktop usage ?