My Galaxy A5 (2017) is not mounting automatically although it appears to be recognized properly (see dmesg) and it is set for MTP transfer:
[ 1799.793224] usb 3-1: USB disconnect, device number 3 [ 1813.883366] usb 3-1: new high-speed USB device number 4 using xhci_hcd [ 1814.011999] usb 3-1: New USB device found, idVendor=04e8, idProduct=6860 [ 1814.012004] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1814.012007] usb 3-1: Product: SAMSUNG_Android [ 1814.012009] usb 3-1: Manufacturer: SAMSUNG [ 1814.012011] usb 3-1: SerialNumber: 5210e432c0641479 [ 1814.013521] cdc_acm 3-1:1.1: ttyACM0: USB ACM device
lsusb clearly lists my phone:
Bus 003 Device 005: ID 04e8:6860 Samsung Electronics Co., Ltd Galaxy (MTP)
In addition, my phone keeps flashing an error message:
Attention The connected device is unable to access data on this device. Reconnect the USB cable and try again.
I am using a Type-C cable on Ubuntu 16.04.3 LTS running on an ASUS laptop.
I saw the question and answer at (re) mount usb device, yet it doesn't work for me since
mount | grep ^/dev shows nothing related to my phone. That being said, I do see
mount failed with the error message:
mount: /dev/ttyACM0 is not a block device
I didn't get any better results in PTP mode - i.e. the phone was not automatically mounted:
[ 3517.875378] usb 3-1: USB disconnect, device number 11 [ 3517.876961] cdc_acm 3-1:1.1: failed to set dtr/rts [ 3518.183436] usb 3-1: new high-speed USB device number 12 using xhci_hcd [ 3518.312069] usb 3-1: New USB device found, idVendor=04e8, idProduct=6866 [ 3518.312077] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 3518.312082] usb 3-1: Product: SAMSUNG_Android [ 3518.312085] usb 3-1: Manufacturer: SAMSUNG [ 3518.312088] usb 3-1: SerialNumber: 5210e432c0641479
gmtp shows the following:
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). LIBMTP ERROR: couldnt parse extension samsung.com/devicestatus:1 Error 1: Get Storage information failed. Detect: No available Storage found on device?
The same cable, connected to the same USB port, on the same (dual boot) computer, mounts the device just fine in Win10