Question about file transfer to Android device
Bret Busby
bret at busby.net
Mon Sep 22 18:19:42 UTC 2025
On 23/9/25 01:54, Bret Busby wrote:
> On 23/9/25 01:33, Bret Busby wrote:
>> On 22/9/25 23:11, Colin Law wrote:
>>> On Mon, 22 Sept 2025 at 15:57, Colin Law <clanlaw at gmail.com>
>>> wrote:
>>>>
>>>> On Mon, 22 Sept 2025 at 15:29, Bret Busby <bret at busby.net>
>>>> wrote:
>>>>> ... So, I am wondering whether Ubuntu 22.04.x is simply not
>>>>> compatible with Android versions after v12.
>>>>
>>>> I am using Ubuntu 22.04 with Nautilus and it has no problem
>>>> accessing files on my Android 14 phone.
>>>
>>> Oh, no, I am running Ubuntu 24.04
>>>
>>>>
>>>> What do you see in syslog when you plug in the phone and
>>>> enable file transfer mode on the phone?
>>>
>>> This is still a valid question.
>>>
>>> Colin L.
>>>
>>
>> The device is a tablet PC, not a cellphone.
>>
>> The device was connected at 0125:07.
>>
>> The switch to file transfer mode was instituted at 0125:57.
>>
>> " Sep 23 01:25:08 bret-Precision-Tower-5810 kernel:
>> [2018138.592180] usb 3-1: new high-speed USB device number 30
>> using xhci_hcd Sep 23 01:25:08 bret-Precision-Tower-5810 kernel:
>> [2018138.748703] usb 3-1: New USB device found, idVendor=1f3a,
>> idProduct=4ee1, bcdDevice= 4.40 Sep 23 01:25:08 bret-Precision-
>> Tower-5810 kernel: [2018138.748709] usb 3-1: New USB device
>> strings: Mfr=1, Product=2, SerialNumber=3 Sep 23 01:25:08 bret-
>> Precision-Tower-5810 kernel: [2018138.748712] usb 3-1: Product:
>> KATB10128WPA Sep 23 01:25:08 bret-Precision-Tower-5810 kernel:
>> [2018138.748713] usb 3-1: Manufacturer: Kogan Sep 23 01:25:08
>> bret- Precision-Tower-5810 kernel: [2018138.748715] usb 3-1:
>> SerialNumber: KATB10128WPAA0896 Sep 23 01:25:08 bret-Precision-
>> Tower-5810 mtp-probe: checking bus 3, device 30: "/sys/devices/
>> pci0000:00/0000:00:14.0/usb3/3-1" Sep 23 01:25:08 bret-Precision-
>> Tower-5810 mtp-probe: bus: 3, device: 30 was an MTP device Sep 23
>> 01:25:08 bret-Precision-Tower-5810 org.kde.kmtpd5[2263212]: Device
>> 0 (VID=1f3a and PID=4ee1) is UNKNOWN in libmtp v1.1.19. Sep 23
>> 01:25:08 bret-Precision-Tower-5810 org.kde.kmtpd5[2263212]: Please
>> report this VID/PID and the device model to the libmtp development
>> team Sep 23 01:25:08 bret-Precision-Tower-5810 mtp-probe: checking
>> bus 3, device 30: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-1"
>> Sep 23 01:25:08 bret-Precision-Tower-5810 mtp-probe: bus: 3,
>> device: 30 was an MTP device Sep 23 01:25:08 bret-Precision-
>> Tower-5810 gvfsd[2320056]: Device 0 (VID=1f3a and PID=4ee1) is
>> UNKNOWN in libmtp v1.1.19. Sep 23 01:25:08 bret-Precision-
>> Tower-5810 gvfsd[2320056]: Please report this VID/PID and the
>> device model to the libmtp development team Sep 23 01:25:08 bret-
>> Precision-Tower-5810 gvfsd[2320056]: libusb_claim_interface()
>> reports device is busy, likely in use by GVFS or KDE MTP device
>> handling alreadyLIBMTP PANIC: Unable to initialize device Sep 23
>> 01:25:08 bret-Precision-Tower-5810 gvfsd[2320068]: Device 0
>> (VID=1f3a and PID=4ee1) is UNKNOWN in libmtp v1.1.19. Sep 23
>> 01:25:08 bret-Precision-Tower-5810 gvfsd[2320068]: Please report
>> this VID/PID and the device model to the libmtp development team
>> Sep 23 01:25:08 bret-Precision-Tower-5810 gvfsd[2320068]:
>> libusb_claim_interface() reports device is busy, likely in use by
>> GVFS or KDE MTP device handling alreadyLIBMTP PANIC: Unable to
>> initialize device Sep 23 01:25:09 bret-Precision-Tower-5810
>> kernel: [2018139.304938] [UFW BLOCK] IN=wlx90de8039844b OUT=
>> MAC=90:de:80:39:84:4b:38:01:46:23:3c:e5:08:00 SRC=192.168.1.100
>> DST=192.168.1.105 LEN=1317 TOS=0x00 PREC=0x00 TTL=254 ID=23285 DF
>> PROTO=UDP SPT=3702 DPT=58223 LEN=1297 Sep 23 01:25:09 bret-
>> Precision-Tower-5810 kernel: [2018139.308258] [UFW BLOCK]
>> IN=wlx90de8039844b OUT=
>> MAC=90:de:80:39:84:4b:38:01:46:23:3c:e5:86:dd
>> SRC=fe80:0000:0000:0000:3a01:46ff:fe23:3ce5
>> DST=fe80:0000:0000:0000:d6bc:fcde:337f:f770 LEN=1337 TC=0
>> HOPLIMIT=64 FLOWLBL=244339 PROTO=UDP SPT=3702 DPT=51081 LEN=1297
>> Sep 23 01:25:09 bret-Precision-Tower-5810 kernel: [2018139.331157]
>> [UFW BLOCK] IN=enp0s25 OUT=
>> MAC=64:00:6a:72:4f:f3:7c:a7:b0:1b:b8:12:08:00 SRC=192.168.1.104
>> DST=192.168.1.103 LEN=1319 TOS=0x00 PREC=0x00 TTL=254 ID=59430 DF
>> PROTO=UDP SPT=3702 DPT=46953 LEN=1299 Sep 23 01:25:09 bret-
>> Precision-Tower-5810 kernel: [2018139.333873] [UFW BLOCK]
>> IN=enp0s25 OUT= MAC=64:00:6a:72:4f:f3:7c:a7:b0:1b:b8:12:86:dd
>> SRC=fd00:0000:0000:0000:7ea7:b0ff:fe1b:b812
>> DST=fd00:0000:0000:0000:cc78:9a27:25ed:cd6c LEN=1339 TC=0
>> HOPLIMIT=64 FLOWLBL=366514 PROTO=UDP SPT=3702 DPT=42814 LEN=1299
>> Sep 23 01:25:09 bret-Precision-Tower-5810 kernel: [2018139.349312]
>> [UFW BLOCK] IN=enp0s25 OUT=
>> MAC=64:00:6a:72:4f:f3:7c:a7:b0:1b:b8:12:86:dd
>> SRC=fd00:0000:0000:0000:7ea7:b0ff:fe1b:b812
>> DST=fd00:0000:0000:0000:e1e7:de5d:c0f7:7097 LEN=1339 TC=0
>> HOPLIMIT=64 FLOWLBL=487649 PROTO=UDP SPT=3702 DPT=36737 LEN=1299
>> Sep 23 01:25:09 bret-Precision-Tower-5810 kernel: [2018139.349685]
>> [UFW BLOCK] IN=enp0s25 OUT=
>> MAC=64:00:6a:72:4f:f3:7c:a7:b0:1b:b8:12:86:dd
>> SRC=fd00:0000:0000:0000:7ea7:b0ff:fe1b:b812
>> DST=fd00:0000:0000:0000:e96a:0d84:b151:cbf5 LEN=1339 TC=0
>> HOPLIMIT=64 FLOWLBL=196830 PROTO=UDP SPT=3702 DPT=35483 LEN=1299
>> Sep 23 01:25:09 bret-Precision-Tower-5810 kernel: [2018139.349700]
>> [UFW BLOCK] IN=enp0s25 OUT=
>> MAC=64:00:6a:72:4f:f3:7c:a7:b0:1b:b8:12:86:dd
>> SRC=fd00:0000:0000:0000:7ea7:b0ff:fe1b:b812
>> DST=fd00:0000:0000:0000:fa57:9b57:308b:0a00 LEN=1339 TC=0
>> HOPLIMIT=64 FLOWLBL=446014 PROTO=UDP SPT=3702 DPT=39644 LEN=1299
>> Sep 23 01:25:55 bret-Precision-Tower-5810 kernel: [2018185.911730]
>> usb 3-1: USB disconnect, device number 30 Sep 23 01:25:55 bret-
>> Precision-Tower-5810 org.kde.kmtpd5[2263212]: ERROR: Could not
>> close session! Sep 23 01:25:55 bret-Precision-Tower-5810
>> org.kde.kmtpd5[2263212]: inep: usb_get_endpoint_status(): No such
>> device Sep 23 01:25:55 bret-Precision-Tower-5810
>> org.kde.kmtpd5[2263212]: outep: usb_get_endpoint_status(): No such
>> device Sep 23 01:25:56 bret-Precision-Tower-5810 kernel:
>> [2018186.856181] usb 3-1: new high-speed USB device number 31
>> using xhci_hcd Sep 23 01:25:56 bret-Precision-Tower-5810 kernel:
>> [2018187.004564] usb 3-1: New USB device found, idVendor=1f3a,
>> idProduct=4ee1, bcdDevice= 4.40 Sep 23 01:25:56 bret-Precision-
>> Tower-5810 kernel: [2018187.004572] usb 3-1: New USB device
>> strings: Mfr=1, Product=2, SerialNumber=3 Sep 23 01:25:56 bret-
>> Precision-Tower-5810 kernel: [2018187.004576] usb 3-1: Product:
>> KATB10128WPA Sep 23 01:25:56 bret-Precision-Tower-5810 kernel:
>> [2018187.004578] usb 3-1: Manufacturer: Kogan Sep 23 01:25:56
>> bret- Precision-Tower-5810 kernel: [2018187.004580] usb 3-1:
>> SerialNumber: KATB10128WPAA0896 Sep 23 01:25:56 bret-Precision-
>> Tower-5810 mtp-probe: checking bus 3, device 31: "/sys/devices/
>> pci0000:00/0000:00:14.0/usb3/3-1" Sep 23 01:25:56 bret-Precision-
>> Tower-5810 mtp-probe: bus: 3, device: 31 was an MTP device Sep 23
>> 01:25:56 bret-Precision-Tower-5810 org.kde.kmtpd5[2263212]: Device
>> 0 (VID=1f3a and PID=4ee1) is UNKNOWN in libmtp v1.1.19. Sep 23
>> 01:25:56 bret-Precision-Tower-5810 org.kde.kmtpd5[2263212]: Please
>> report this VID/PID and the device model to the libmtp development
>> team Sep 23 01:25:56 bret-Precision-Tower-5810 mtp-probe: checking
>> bus 3, device 31: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-1"
>> Sep 23 01:25:56 bret-Precision-Tower-5810 mtp-probe: bus: 3,
>> device: 31 was an MTP device Sep 23 01:25:56 bret-Precision-
>> Tower-5810 kernel: [2018187.066953] [UFW BLOCK] IN=wlx90de8039844b
>> OUT= MAC=90:de:80:39:84:4b:38:01:46:23:3c:e5:86:dd
>> SRC=fe80:0000:0000:0000:3a01:46ff:fe23:3ce5
>> DST=fe80:0000:0000:0000:d6bc:fcde:337f:f770 LEN=1337 TC=0
>> HOPLIMIT=64 FLOWLBL=226396 PROTO=UDP SPT=3702 DPT=57903 LEN=1297
>> Sep 23 01:25:56 bret-Precision-Tower-5810 kernel: [2018187.069984]
>> [UFW BLOCK] IN=wlx90de8039844b OUT=
>> MAC=90:de:80:39:84:4b:38:01:46:23:3c:e5:08:00 SRC=192.168.1.100
>> DST=192.168.1.105 LEN=1317 TOS=0x00 PREC=0x00 TTL=254 ID=27276 DF
>> PROTO=UDP SPT=3702 DPT=41565 LEN=1297 Sep 23 01:25:56 bret-
>> Precision-Tower-5810 gvfsd[2320252]: Device 0 (VID=1f3a and
>> PID=4ee1) is UNKNOWN in libmtp v1.1.19. Sep 23 01:25:56 bret-
>> Precision-Tower-5810 gvfsd[2320252]: Please report this VID/PID
>> and the device model to the libmtp development team Sep 23
>> 01:25:56 bret-Precision-Tower-5810 gvfsd[2320252]:
>> libusb_claim_interface() reports device is busy, likely in use by
>> GVFS or KDE MTP device handling alreadyLIBMTP PANIC: Unable to
>> initialize device Sep 23 01:25:57 bret-Precision-Tower-5810
>> kernel: [2018187.121459] [UFW BLOCK] IN=enp0s25 OUT=
>> MAC=64:00:6a:72:4f:f3:7c:a7:b0:1b:b8:12:08:00 SRC=192.168.1.104
>> DST=192.168.1.103 LEN=1319 TOS=0x00 PREC=0x00 TTL=254 ID=63298 DF
>> PROTO=UDP SPT=3702 DPT=60050 LEN=1299 Sep 23 01:25:57 bret-
>> Precision-Tower-5810 kernel: [2018187.123581] [UFW BLOCK]
>> IN=enp0s25 OUT= MAC=64:00:6a:72:4f:f3:7c:a7:b0:1b:b8:12:86:dd
>> SRC=fd00:0000:0000:0000:7ea7:b0ff:fe1b:b812
>> DST=fd00:0000:0000:0000:e1e7:de5d:c0f7:7097 LEN=1339 TC=0
>> HOPLIMIT=64 FLOWLBL=40237 PROTO=UDP SPT=3702 DPT=46132 LEN=1299
>> Sep 23 01:25:57 bret-Precision-Tower-5810 kernel: [2018187.125832]
>> [UFW BLOCK] IN=enp0s25 OUT=
>> MAC=64:00:6a:72:4f:f3:7c:a7:b0:1b:b8:12:86:dd
>> SRC=fd00:0000:0000:0000:7ea7:b0ff:fe1b:b812
>> DST=fd00:0000:0000:0000:cc78:9a27:25ed:cd6c LEN=1339 TC=0
>> HOPLIMIT=64 FLOWLBL=181753 PROTO=UDP SPT=3702 DPT=35998 LEN=1299
>> Sep 23 01:25:57 bret-Precision-Tower-5810 gvfsd[2320265]: Device 0
>> (VID=1f3a and PID=4ee1) is UNKNOWN in libmtp v1.1.19. Sep 23
>> 01:25:57 bret-Precision-Tower-5810 gvfsd[2320265]: Please report
>> this VID/PID and the device model to the libmtp development team
>> Sep 23 01:25:57 bret-Precision-Tower-5810 gvfsd[2320265]:
>> libusb_claim_interface() reports device is busy, likely in use by
>> GVFS or KDE MTP device handling alreadyLIBMTP PANIC: Unable to
>> initialize device Sep 23 01:25:57 bret-Precision-Tower-5810
>> kernel: [2018187.584069] [UFW BLOCK] IN=wlx90de8039844b OUT=
>> MAC=90:de:80:39:84:4b:38:01:46:23:3c:e5:08:00 SRC=192.168.1.100
>> DST=192.168.1.105 LEN=1317 TOS=0x00 PREC=0x00 TTL=254 ID=27293 DF
>> PROTO=UDP SPT=3702 DPT=40281 LEN=1297 Sep 23 01:25:57 bret-
>> Precision-Tower-5810 kernel: [2018187.629524] [UFW BLOCK]
>> IN=enp0s25 OUT= MAC=64:00:6a:72:4f:f3:7c:a7:b0:1b:b8:12:08:00
>> SRC=192.168.1.104 DST=192.168.1.103 LEN=1319 TOS=0x00 PREC=0x00
>> TTL=254 ID=63346 DF PROTO=UDP SPT=3702 DPT=52114 LEN=1299 Sep 23
>> 01:26:38 bret-Precision-Tower-5810 kernel: [2018228.895086] [UFW
>> BLOCK] IN=wlx90de8039844b OUT=
>> MAC=01:00:5e:00:00:01:50:d4:f7:70:10:95:08:00 SRC=192.168.1.1
>> DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 Sep
>> 23 01:26:55 bret-Precision-Tower-5810 kernel: [2018245.264152]
>> [UFW BLOCK] IN=enp0s25 OUT=
>> MAC=01:00:5e:00:00:01:3c:6a:d2:9d:cc:46:08:00 SRC=192.168.1.1
>> DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=52587 DF PROTO=2
>>
>> "
>>
>
> I believe that it is Device 031 in the output from lsusb .
>
> " ~ > lsusb Bus 002 Device 002: ID 8087:8002 Intel Corp. 8 channel
> internal hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0
> root hub Bus 001 Device 002: ID 8087:800a Intel Corp. Hub Bus 001
> Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004
> Device 003: ID 0480:a200 Toshiba America Inc External USB 3.0 Bus
> 004 Device 002: ID 04e8:61f5 Samsung Electronics Co., Ltd Portable
> SSD T5 Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root
> hub Bus 003 Device 005: ID 2a7a:939f CASUE USB KB Bus 003 Device
> 004: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 003 Device
> 003: ID 04e8:4001 Samsung Electronics Co., Ltd PSSD T7 Bus 003
> Device 002: ID 04e8:4001 Samsung Electronics Co., Ltd PSSD T7 Bus
> 003 Device 007: ID 0bda:c811 Realtek Semiconductor Corp. 802.11ac
> NIC Bus 003 Device 006: ID 1bcf:2cb4 Sunplus Innovation Technology
> Inc. AAPDQT-0622-W Bus 003 Device 031: ID 1f3a:4ee1 Allwinner
> Technology KATB10128WPA Bus 003 Device 001: ID 1d6b:0002 Linux
> Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0003 Linux
> Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux
> Foundation 2.0 root hub 2025-09-23 01:48:08 bret at bret-Precision-
> Tower-5810:~ > mtp-detect Command 'mtp-detect' not found, but can be
> installed with: sudo apt install mtp-tools 2025-09-23 01:49:00
> bret at bret-Precision-Tower-5810:~ > sudo apt install mtp-tools [sudo]
> password for bret: Reading package lists... Done Building dependency
> tree... Done Reading state information... Done The following NEW
> packages will be installed mtp-tools 0 to upgrade, 1 to newly
> install, 0 to remove and 2 not to upgrade. Need to get 36.2 kB of
> archives. After this operation, 339 kB of additional disk space will
> be used. Get:1 http://archive.ubuntu.com/ubuntu jammy/universe amd64
> mtp-tools amd64 1.1.19-1build1 [36.2 kB] Fetched 36.2 kB in 1s (29.8
> kB/s) Selecting previously unselected package mtp-tools. (Reading
> database ... 577060 files and directories currently installed.)
> Preparing to unpack .../mtp-tools_1.1.19-1build1_amd64.deb ...
> Unpacking mtp-tools (1.1.19-1build1) ... Setting up mtp-tools
> (1.1.19-1build1) ... Processing triggers for man-db (2.10.2-1) ...
> 2025-09-23 01:49:38 bret at bret-Precision-Tower-5810:~ > mtp-detect
> libmtp version: 1.1.19
>
> Listing raw device(s) Device 0 (VID=1f3a and PID=4ee1) is UNKNOWN in
> libmtp v1.1.19. Please report this VID/PID and the device model to
> the libmtp development team Found 1 device(s): 1f3a:4ee1 @ bus 3,
> dev 31 Attempting to connect device(s) libusb_claim_interface()
> reports device is busy, likely in use by GVFS or KDE MTP device
> handling alreadyLIBMTP PANIC: Unable to initialize device Unable to
> open raw device 0 OK. "
>
>
> .. Bret Busby Armadale West Australia (UTC+0800) ..............
>
From all of the above, I deduce that the problem is that the hardware of
the tablet PC is not included in the lbmtp stuff, which, to me, defeats
the objective of the ancestor of Linux.
My understanding is that UNIX was created to provide an operating system
and software, that was/were hardware independent, so that UNIX systems
could communicate with each other, independent of the underlying
hardware, and, that actions like file transfers, including between
different operating systems, have been independent of underlying
hardware, so, for example, file transfers between Linux and MS Windows,
occurred using Samba, and, it did not matter whether the MS Windows
computer involved in a file transfer process, would be running on an
Intel 80486 CPU or an AMD Ryzen CPU, or, whether the RAM would be DDR3
or DDR5 or whether the HDD would be a mechanical rotating HDD or an SSD.
It would be like my PC-XT not working with DOS, because my PC used an
NEC V-22 CPU and not an Intel 8086 CPU, and, my PC-XT used an MFM HDD
and not an RLL HDD.
It seems to me, that the objective of UNIX has been lost, when file
transfer activity relies completely on provision being made for specific
hardware, rather than being dependent on communications between
operating systems.
The portability of operating systems and utilities, appears to have been
lost, over the decades.
When this goes to the hardware level, it takes it all back about 40-50
years, when I was learning the DEC RSTS/e operating system and UNIX
system V and learning programming of FORTRAN and 'C', and, one of the
students showed me a computer that he had - a DEC PDP/11, that he had on
his flat balcony, that he kept for fun, for programming in octal.
It seems that it has all gone back from hardware independent operating
systems, to machine code programming for common computer usage; back to
the days of Alan Turing and his computer that he built to defeat the
Enigma machine.
..
Bret Busby
Armadale
West Australia
(UTC+0800)
..............
More information about the ubuntu-users
mailing list