distribution Android phone content

Hello

It used to be working fine, about a year ago. Just connecting the phone via USB - C cable and file managers showed the contents of the phone. Then suddenly it stopped working. I went through all the standard “dead roads”: changed the cable, port, phone - nothing. It seems to be detected good by tools like mtp-detect or lsusb, just can't mount it (?). In addition, the control on the phone can not be switched to a remote device(for the computer). It throws an error and reverts to local control , while in the console Journalctl -f gives the line : kernel: probe of 1-1 returned 0 after 2918 usecs I don't know if it matters, but a similar thing happened with VirtualBOX - I can't pass any USB devices to virtual machines(non is visible in VBox ). Again, it used to be working fine before.

Notice: Storage drives connected via USB or same hardware but computer booted from LiveUSB (Ubuntu or whatever) : everything works fine.(phone content is visible)

ClearLinux 43000

journalctl -f kernel: usb 1-1: USB disconnect, device number 9 Feb 15 00:22:57 u939x kernel: usb 1-1: new high-speed USB device number 10 using xhci_hcd Feb 15 00:22:58 u939x kernel: usb 1-1: New USB device found, idVendor=04e8, idProduct=6860, bcdDevice= c.00 Feb 15 00:22:58 u939x kernel: usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Feb 15 00:22:58 u939x kernel: usb 1-1: Product: SAMSUNG_Android Feb 15 00:22:58 u939x kernel: usb 1-1: Manufacturer: SAMSUNG Feb 15 00:22:58 u939x kernel: usb 1-1: SerialNumber: (snip) Feb 15 00:22:58 u939x kernel: probe of 1-1 returned 0 after 2918 usecs

mtp-detect libmtp version: 1.1.22

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 9 Attempting to connect device(s) USB low-level info: bcdUSB: 528 (...)

lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 04c5:125a Fujitsu, Ltd PalmSecure Sensor Device - MP Bus 001 Device 003: ID 04f2:b683 Chicony Electronics Co., Ltd FJ Camera Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 005: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader Bus 001 Device 006: ID 056a:51dd Wacom Co., Ltd Pen and multitouch sensor Bus 001 Device 007: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 008: ID 0bda:5629 Realtek Semiconductor Corp. FJ 5M Camera Bus 001 Device 009: ID 04e8:6860 Samsung Electronics Co., Ltd Galaxy series, misc. (MTP mode) Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 002: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub Bus 005 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 005 Device 004: ID 026d:0005
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 006 Device 002: ID 0bda:0411 Realtek Semiconductor Corp. Hub

Any ideas are welcome.

Feb 14 '25 23:02 MaciejMalusi

Any chance you can point to a specific kernel version that it last worked on?

Feb 28 '25 01:02 bryteise

not precisely, no. But I ran an older version of ClearLinux 42100 from LiveUSB and it works. btw. it seems that this "control switching" on the phone itself - (I mentioned this in the first post) is irrelevant in this context.

uname -a Linux clr-live 6.10.1-1453.native #1 SMP Wed Jul 24 10:02:10 PDT 2024 x86_64 GNU/Linux

journalctl -f

Feb 28 13:59:18 clr-live kernel: usb 1-2: USB disconnect, device number 9 Feb 28 13:59:18 clr-live gvfsd[2019]: PTP: reading event an error 0x05 occurred Feb 28 13:59:18 clr-live kernel: usb 1-2: new high-speed USB device number 10 using xhci_hcd Feb 28 13:59:18 clr-live kernel: usb 1-2: New USB device found, idVendor=04e8, idProduct=6860, bcdDevice= c.00 Feb 28 13:59:18 clr-live kernel: usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Feb 28 13:59:18 clr-live kernel: usb 1-2: Product: SAMSUNG_Android Feb 28 13:59:18 clr-live kernel: usb 1-2: Manufacturer: SAMSUNG Feb 28 13:59:18 clr-live kernel: usb 1-2: SerialNumber: Feb 28 13:59:18 clr-live kernel: probe of 1-2 returned 0 after 2386 usecs Feb 28 13:59:18 clr-live mtp-probe[2036]: checking bus 1, device 10: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-2" Feb 28 13:59:18 clr-live mtp-probe[2036]: bus: 1, device: 10 was an MTP device Feb 28 13:59:18 clr-live mtp-probe[2038]: checking bus 1, device 10: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-2" Feb 28 13:59:18 clr-live mtp-probe[2038]: bus: 1, device: 10 was an MTP device Feb 28 13:59:19 clr-live gvfsd[2019]: Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). Feb 28 13:59:31 clr-live systemd[1]: systemd-hostnamed.service: Deactivated successfully.

Feb 28 '25 14:02 MaciejMalusi

i've poke a "bit" with Live ISOs and narrowed down to following conclusions:

https://cdn.download.clearlinux.org/releases/ XXXXX/

XXXXX 42690 (and after) - doesn't work (not sure what release number came after boot) 42680 - works! but release info after boot says 42670 42670 - not tested, no ISO to download 42660 - not tested, kernel panic at boot 42650 - works

Feb 28 '25 22:02 MaciejMalusi

Thanks! I'll go digging and see if I can find something that looks suspicious.

Feb 28 '25 22:02 bryteise

Unfortunately our config diff between those two releases doesn't show anything that I'd suspect is causing this. I also note there wasn't a gvfs update. The Feb 28 13:59:18 clr-live gvfsd[2019]: PTP: reading event an error 0x05 occurred is the error manifestation of whatever is preventing it from working is my guess though so you might have some luck looking around for that.

Mar 28 '25 16:03 bryteise

I did another test on 42680. Also on the last 43150 where the error gvfsd[2140]: PTP: reading event an error 0x05 occurred did NOT appear, which is a shame because at least it would work. I added small notes to both logs"

CL42680_but_says_CL42670_journalctl_.txt

cl43150_journalctl_txt.txt

I don't know how I can be of help in solving the problem.

Mar 28 '25 17:03 MaciejMalusi

Okay so looking at those logs my best guess would be the libmtp upgrade is what is the problem at this point. It is a bit painful but if you can try replacing the current version's files with those from the libmtp rpms in https://download.clearlinux.org/releases/42680/clear/x86_64/os/Packages/ that'd be the most direct way of testing (at least swupd repair will return to previous state one way or another). You could also look through the libmtp issues to see if you find your device there.

Mar 28 '25 17:03 bryteise

I'm not sure, I did it right. In the first step I copied the files from the package libmtp-1.1.21-13.x86_64.rpm to /usr/lib/udev/ . There were no files before. Then I found mtp-probe and hwdb.d in: /usr/lib64/udev/ and replaced them there.

After restart and check the problem remains.

Under the link with issues I didn't find my device

Mar 28 '25 18:03 MaciejMalusi

Aaah I see what changed, note that the old version put the files correctly in /usr/lib/udev but the new version put them in /usr/lib64/udev which is the bug. Thanks. Should be in the next release or so.

Mar 28 '25 19:03 bryteise

Hi. Just checked and on CL43250 and i can see content of the phone. Hurra! Thank You for help.

Apr 11 '25 08:04 MaciejMalusi

Android phone content - no visibility.