Mavridis Philippe via tde-users wrote:
I recall there were some applications for non-smartphone mobile phones called KMobile and Kandy, but I don't know if they are compatible with KaiOS devices.
I spent some time dealing with mobile phone interactions. I did also some experiments with ofono and can call any number though the mobile via dbus :-D But I couldn't find time writing a TDE interface for that. I also do not use very often the phone as HSP bluetooth device
If the phone supports MTP, then you can just use GMTP (I don't think TDE has MTP protocol support yet). Otherwise, it might be that the phone can function like a standard USB mass storage device and the TDE Hardware library just doesn't recognize that. That still happens to me when I connect an MP4 player device to the PC, so I have to mount it manually.
regarding MTP I was looking last week if it were too hard to program a tdeio mtp plugin. I actually tried few years ago but couldn't find out how tdeio is supposed to work :D I must admit that I do not have that much time to investigate and study the code
But back to the topic. Those old applications do not work with new phones unless one is using the AT commands (I mean the above mentioned KMobile and Kandy) In fact for some parts they indeed use the AT commands, but the problem is that aside of standard AT commands there were many vendor specific and those vendors do not produce phones anymore.
One thing that I use on my phone is to send images via bluetooth to the PC One should just run tdebluetooth and enable the Obex server. Then on the phone you select a picture and tap share, select BT and your PC and send the image.
So back to MTP. Recently after upgrading one of the phones to Android 14 it stopped working with GMTP unless rebooted. I upgraded another phone and it works even in konqueror.
It triggers cdc_acm driver as shown below
[906591.027579] usb 1-1.6: new high-speed USB device number 4 using ehci-pci [906591.136602] usb 1-1.6: New USB device found, idVendor=04e8, idProduct=6860, bcdDevice= 2.23 [906591.136612] usb 1-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [906591.136616] usb 1-1.6: Product: SAMSUNG_Android [906591.136619] usb 1-1.6: Manufacturer: SAMSUNG [906591.136621] usb 1-1.6: SerialNumber: xxxxxxxxxxx [906591.193781] cdc_acm 1-1.6:1.1: ttyACM0: USB ACM device [906591.193825] usbcore: registered new interface driver cdc_acm [906591.193828] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters [906611.457197] usb 1-1.6: USB disconnect, device number 4 [906611.684016] usb 1-1.6: new high-speed USB device number 5 using ehci-pci [906611.800949] usb 1-1.6: New USB device found, idVendor=04e8, idProduct=6860, bcdDevice= 2.23 [906611.800960] usb 1-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [906611.800964] usb 1-1.6: Product: SAMSUNG_Android [906611.800966] usb 1-1.6: Manufacturer: SAMSUNG [906611.800968] usb 1-1.6: SerialNumber: xxxxxxxxxxx [906611.802757] cdc_acm 1-1.6:1.1: ttyACM0: USB ACM device
Another phone with custom OS (Sailfish OS) does not make it so far as shown below, but gmtp works fine
907126.327368] usb 1-1.6: new high-speed USB device number 7 using ehci-pci [907126.438034] usb 1-1.6: New USB device found, idVendor=0fce, idProduct=0a07, bcdDevice= 2.23 [907126.438039] usb 1-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [907126.438041] usb 1-1.6: Product: Xperia 10 II - Dual SIM [907126.438043] usb 1-1.6: Manufacturer: Sony [907126.438044] usb 1-1.6: SerialNumber: xxxxxxxxxxx [907132.097917] traps: tdeio_kamera[2058541] general protection fault ip:7fe94e0f58ee sp:7ffce3736c10 error:0 in libgcc_s.so. [7fe94e0e3000+17000] [907166.410432] traps: tdeio_kamera[2058636] general protection fault ip:7fe94e0f58ee sp:7ffce3736c10 error:0 in libgcc_s.so. [7fe94e0e3000+17000]
so it depends probably on how the device is handled or how it is supporting the protocol