When connecting the phone to the pc, Dolphin sees the phone (Galaxy 4), I can open the memory card in the phone, Dolphin sees the folders that are on the SD card. But clicking on a folder on the card, Dolphin cannot see or open the files in that folder. The process hangs.
Under MGA6 I could open the sd card in the phone fine.
====================================
In the journal I found this line:
====================================The file or folder udi=/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:02.1/usb1/1-2 does not exist.
To resume:
MGA7 sees the phone via usb.
I can open the phone
I can open the CD card.
I can see all the folders on that card.
I cannot open files in the folders on the card.
=============================================================
The command mtp-detect gives info about the following error:
- Code: Select all
$ mtp-detect
libmtp version: 1.1.16
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
Found 1 device(s):
Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 6
Attempting to connect device(s)
error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to initialize device
Unable to open raw device 0
OK.
==================================================================================
When I take the SD card out of the phone, and put it in a usb card reader, Dolphin can open the card normally. I can see the files in the folders on the card, and can copy and move files fine.
When I reboot MGA7 with the Android phone already connected via usb, the system sees the phone correct:
================================================================
- Code: Select all
$ mtp-detect
libmtp version: 1.1.16
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
Found 1 device(s):
Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 3
Attempting to connect device(s)
USB low-level info:
bcdUSB: 512
bDeviceClass: 0
bDeviceSubClass: 0
bDeviceProtocol: 0
idVendor: 04e8
idProduct: 6860
IN endpoint maxpacket: 512 bytes
OUT endpoint maxpacket: 512 bytes
Raw device info:
Bus location: 1
Device number: 3
Device entry info:
Vendor: Samsung
Vendor id: 0x04e8
Product: Galaxy models (MTP)
Vendor id: 0x6860
Device flags: 0xc9000202
Configuration 0, interface 0, altsetting 0:
Interface description contains the string "MTP"
Device recognized as MTP, no further probing.
===================================================================
When I disconnect the usb cable of the phone, and reconnect the phone via usb, the connection is lost again, resulting in the same 6LIBMTP panic again (which I really don't know what that is. Goes beyond my knowledge, I'm just a Joe Average consumer...).
=================================================================================================
In the journald log I also see an error about bind, directly after reconnecting the phone via usb:
27-12-2019 16:34 kernel usb 1-2: new high-speed USB device number 6 using ehci-pci
27-12-2019 16:34 kernel usb 1-2: New USB device found, idVendor=04e8, idProduct=6860, bcdDevice= 4.00
27-12-2019 16:34 kernel usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
27-12-2019 16:34 kernel usb 1-2: Product: SAMSUNG_Android
27-12-2019 16:34 kernel usb 1-2: Manufacturer: SAMSUNG
27-12-2019 16:34 kernel usb 1-2: SerialNumber: (removed by me)
27-12-2019 16:34 org_kde_powerdevil UdevQt: unhandled device action "bind"
27-12-2019 16:34 plasmashell file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:99: TypeError: Type error
27-12-2019 16:34 kate UdevQt: unhandled device action "bind"
27-12-2019 16:34 plasmashell UdevQt: unhandled device action "bind"
27-12-2019 16:34 plasmashell file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:99: TypeError: Type error
=================================================================================================================
BTW: I installed exfat-utils, fuse-exfat and mtpfs. They didn't cure the connection problem.
(sorry that i can't format the code lines above)