I have a flip phone that is recognized immediately (lsusb) but does not appear anywhere in TDE that I can see.
I receive popups or desktop icons in KDE and Xfce.
I have enabled KControl->Desktop->Behavior->Device Icons->Show Device Icons. There are few devices in that list not enabled, but I do not see anything in Konqueror Storage Devices.
My first presumption is something not configured correctly here or packages not compiled correctly. What is fully required to get TDE to recognize the phone?
Thanks.
On 4/22/25 2:05 PM, deloptes via tde-users wrote:
I have a flip phone that is recognized immediately (lsusb) but does not appear anywhere in TDE that I can see.
and what is the output of the lsusb command?
The phone is an Alcatel A405DL running KaiOS 2.5.
lsusb:
Bus 001 Device 015: ID 1bbb:a00e T & A Mobile Phones Vodafone Smart Tab 4G Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x1bbb T & A Mobile Phones idProduct 0xa00e Vodafone Smart Tab 4G bcdDevice 3.10 iManufacturer 1 Android iProduct 2 Android iSerial 3 EQLC36CFMPB00XO bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0027 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 0 iInterface 4 MTP Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x001c 1x 28 bytes bInterval 6 Device Qualifier (for other device speed): bLength 10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 bNumConfigurations 1 Device Status: 0x0000 (Bus Powered)
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.
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.
-- Philippe
On Tuesday 22 April 2025 22:40:11 Darrell Anderson via tde-users wrote:
On 4/22/25 2:05 PM, deloptes via tde-users wrote:
I have a flip phone that is recognized immediately (lsusb) but does not appear anywhere in TDE that I can see.
and what is the output of the lsusb command?
The phone is an Alcatel A405DL running KaiOS 2.5.
lsusb:
Bus 001 Device 015: ID 1bbb:a00e T & A Mobile Phones Vodafone Smart Tab 4G Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x1bbb T & A Mobile Phones idProduct 0xa00e Vodafone Smart Tab 4G bcdDevice 3.10 iManufacturer 1 Android iProduct 2 Android iSerial 3 EQLC36CFMPB00XO bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0027 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 0 iInterface 4 MTP Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x001c 1x 28 bytes bInterval 6 Device Qualifier (for other device speed): bLength 10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 bNumConfigurations 1 Device Status: 0x0000 (Bus Powered)
tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskt op.org
On 4/23/25 6:43 AM, Mavridis Philippe via tde-users wrote:
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.
I think you hit on the root cause -- TDE doesn't support the phone. Probably because MTP.
I live in a cell phone dead zone and I use the phone only when traveling. The phone has a camera and that is what prompted me to test the phone in TDE. To hopefully transfer photos to my computers. I never used the phone to take photos, but I thought I'd check the support in TDE. So I guess until TDE has MTP support I launch a different DE if that need arises. A paper cut but not a show stopper.
On Wed April 23 2025 12:11:02 Darrell Anderson via tde-users wrote:
I think you hit on the root cause -- TDE doesn't support the phone. Probably because MTP.
Long long ago I used to use kdebluetooth and OBEX to get pictures from phones, but it was a pain and I no longer remember the details.
These days we use Syncthing to backup phones continuously to users' own Linux laptops. Users can easily access their phone pictures in the DCIM folder in their Syncthing backups on their laptops.
Some apps store pics and videos on remote servers. In such cases media can usually be transferred by sharing via email, WhatsApp, etc.
On Wed, Apr 23, 2025 at 14:11 (-0500), Darrell Anderson via tde-users wrote:
On 4/23/25 6:43 AM, Mavridis Philippe via tde-users wrote:
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.
I think you hit on the root cause -- TDE doesn't support the phone. Probably because MTP.
I live in a cell phone dead zone and I use the phone only when traveling. The phone has a camera and that is what prompted me to test the phone in TDE. To hopefully transfer photos to my computers. I never used the phone to take photos, but I thought I'd check the support in TDE. So I guess until TDE has MTP support I launch a different DE if that need arises. A paper cut but not a show stopper.
That seems like overkill. Why not just start up the file manager of one of the other DEs, access the camera, and then kill that file manager?
Jim
On 4/23/25 3:37 PM, Jim via tde-users wrote:
That seems like overkill. Why not just start up the file manager of one of the other DEs, access the camera, and then kill that file manager?
There is an old adage that old dogs can't learn new tricks. That proverb is misleading. Old dogs can learn new tricks. They just prefer not to.
Statler and Waldorf might comment about my intelligence too.
From within TDE I launched KDE Dolphin. I have overconfigured the Dolphin "Places" panel because no "Devices" appeared.
From within TDE I launched Xfce Thunar. In the navigation panel was a "Devices->Android" option. Selecting /Internal Storage/photos/ showed no files but selecting /Internal Storage/DCIM/100KAIOS/ found a fresh photo. That latter file path and method is the same as when I connect my Canon PowerShot camera with a USB cable.
From within TDE I launched KDE Konqueror, which I seldom use and haven't done any overconfiguring like KDE Dolphin. KDE Konqueror showed a "Remote->MTP Devices" option but nothing appeared there.
I returned to KDE Dolphin and tinkered until I could display Devices. Like Thunar, an "Android" device appeared but selecting that option resulted in an error message that no such device existed. Oddly the full device file path was in the error message.
I toggled to a different console and logged in as a different user with KDE. From within KDE both Dolphin and KDE Konqueror allowed me to browse the phone with no problems. The Location bar in both showed "mtp:" but since TDE does not support MTP I guess that point is moot.
Similarly with logging in with Xfce. In addition to Thunar readily recognizing the device, an "Android" icon appeared on the desktop.
Launching KDE Dolphin and Konqueror from within TDE seems to indicate the tools see a device but fail to show anything because some kind of handshake or process notification is missing from the full KDE environment. Possibly playing with some KDE environment variables might help use those tools within TDE, but probably not worth my time since Xfce Thunar recognizes the device with no fuss.
As Oddball (Kelly's Heroes) might say, "Woof, woof." Old dogs can learn new tricks.
I guess that raises the question of whether there is a wish list item in the bug tracker to add MTP support. I did not find any such issue but I'm not clever with that gitea interface.
On Wed, Apr 23, 2025 at 16:35 (-0500), Darrell Anderson via tde-users wrote:
On 4/23/25 3:37 PM, Jim via tde-users wrote:
That seems like overkill. Why not just start up the file manager of one of the other DEs, access the camera, and then kill that file manager?
There is an old adage that old dogs can't learn new tricks. That proverb is misleading. Old dogs can learn new tricks. They just prefer not to.
Or they know their wages should have gone up over the years and expect more treats per new trick.
Statler and Waldorf might comment about my intelligence too.
Most eloquently, too.
From within TDE I launched Xfce Thunar. In the navigation panel was a "Devices->Android" option. Selecting /Internal Storage/photos/ showed no files but selecting /Internal Storage/DCIM/100KAIOS/ found a fresh photo.
That seems very promising.
Similarly with logging in with Xfce. In addition to Thunar readily recognizing the device, an "Android" icon appeared on the desktop.
I will admit I only have tried Thunar, and that would be because it works for me in situations like this.
Launching KDE Dolphin and Konqueror from within TDE seems to indicate the tools see a device but fail to show anything because some kind of handshake or process notification is missing from the full KDE environment.
Maybe that's it, but (speaking as a person who uses a window manager, as opposed to a DE) it seems bizarre to me. Maybe there is some good design reason why a program needs all of the DE daemons and such running in order for it to be able to do much. I'm really not fond of this design, but (given I am sending this to the TDE users' list) I may be the only person here who feels this way.
Possibly playing with some KDE environment variables might help use those tools within TDE, but probably not worth my time since Xfce Thunar recognizes the device with no fuss.
Probably not worth your time, unless you feel like some derring-do, tilting at windmills and the like.
Jim
On 4/23/25 5:05 PM, Jim via tde-users wrote:
I will admit I only have tried Thunar, and that would be because it works for me in situations like this.
I admit the entire way Xfce handled the phone impressed me. I hate the cliche, but Thunar "just worked" and a nice icon appeared on the desktop. So simple and quiet.
The KDE method isn't too bad although likely I do not have something configured correctly. With KDE I am annoyed by --oops- informed with a popup that a new device exists. Selecting "browse files" launches Dolphin and that is fine. I think Xfce wins the day here. Now I am a tad curious now how other DEs or file managers handle all of this.
Launching KDE Dolphin and Konqueror from within TDE seems to indicate the tools see a device but fail to show anything because some kind of handshake or process notification is missing from the full KDE environment.
Maybe that's it, but (speaking as a person who uses a window manager, as opposed to a DE) it seems bizarre to me.
Which window manager? There is the rebellious grumpy old man part of me that sometimes thinks about going back to those days, but ever since KDE 3.5 I have been content with DEs.
Maybe there is some good design reason why a program needs all of the DE daemons and such running in order for it to be able to do much. I'm really not fond of this design, but (given I am sending this to the TDE users' list) I may be the only person here who feels this way.
I am not one who feels a severe need to do the Calvin decal thing with KDE. To me KDE 4 was a fiasco, especially after 4.7 or so when the developers forced upon users their silly "pillars." KDE 5 seems much nicer than 4. I used KDE 5 for a couple of years before pushing back to TDE. I keep KDE 5 (and Xfce) installed as an alternative and backup. I don't like all of how KDE 5 is designed, such as the useless activity manager and that nonsense known as akonadi, but I tamed KDE 5 quite a bit to be useful for me.
Oh well, this is a TDE mail list. Best I move along now.
On Wed, Apr 23, 2025 at 17:29 (-0500), Darrell Anderson via tde-users wrote:
On 4/23/25 5:05 PM, Jim via tde-users wrote:
I will admit I only have tried Thunar, and that would be because it works for me in situations like this.
I admit the entire way Xfce handled the phone impressed me. I hate the cliche, but Thunar "just worked" and a nice icon appeared on the desktop. So simple and quiet.
Yup. (While I don't use xfce, I do recommend it to some people every now and then. My wife uses it on her laptop, under MX Linux.)
Launching KDE Dolphin and Konqueror from within TDE seems to indicate the tools see a device but fail to show anything because some kind of handshake or process notification is missing from the full KDE environment.
Maybe that's it, but (speaking as a person who uses a window manager, as opposed to a DE) it seems bizarre to me.
Which window manager? There is the rebellious grumpy old man part of me that sometimes thinks about going back to those days, but ever since KDE 3.5 I have been content with DEs.
fvwm3. I suppose I'm missing out on all sorts of conveniences and features and bells and whistles, but the only thing that I know that I'm missing is the notification (in whatever form it takes) telling me I just plugged something in. Well, duh, I know I just plugged it in, because I just plugged it in. Admittedly, having to type "mount /sdcard" instead of clicking on some icon is an onerous task not all people would want to do, but I'm OK with it. Not for the faint-hearted, I suppose.
Maybe there is some good design reason why a program needs all of the DE daemons and such running in order for it to be able to do much. I'm really not fond of this design, but (given I am sending this to the TDE users' list) I may be the only person here who feels this way.
I am not one who feels a severe need to do the Calvin decal thing with KDE.
It took me a few seconds to realize what you meant. :-)
To me KDE 4 was a fiasco,
I agree. The first time I started that up my machine (reasonably powerful for the time) was ground down into unresponsiveness because some KDE person thought I should have an up-to-date index of all of mankind's knowledge, or whatever it was doing. Mind you, had KDE4 worked well, I wouldn't have gone looking and found TDE.
especially after 4.7 or so when the developers forced upon users their silly "pillars." KDE 5 seems much nicer than 4.
Could it be as bad or worse?
I used KDE 5 for a couple of years before pushing back to TDE. I keep KDE 5 (and Xfce) installed as an alternative and backup. I don't like all of how KDE 5 is designed, such as the useless activity manager and that nonsense known as akonadi, but I tamed KDE 5 quite a bit to be useful for me.
I think configuring xfce is probably less work, but to each his own.
Jim
On Wed, 23 Apr 2025 14:11:02 -0500 Darrell Anderson via tde-users users@trinitydesktop.org wrote:
On 4/23/25 6:43 AM, Mavridis Philippe via tde-users wrote:
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.
I think you hit on the root cause -- TDE doesn't support the phone. Probably because MTP.
I live in a cell phone dead zone and I use the phone only when traveling. The phone has a camera and that is what prompted me to test the phone in TDE. To hopefully transfer photos to my computers. I never used the phone to take photos, but I thought I'd check the support in TDE. So I guess until TDE has MTP support I launch a different DE if that need arises. A paper cut but not a show stopper.
You might be able to mount it manually using one of the FUSE packages for MTP (ther are at least three), then operate normally on it through Konqueror. I admit I've never tried, since it's easier just to pull the SD card from the one MTP-using device I have.
E. Liddell
On 4/23/25 4:29 PM, E. Liddell via tde-users wrote:
You might be able to mount it manually using one of the FUSE packages for MTP (ther are at least three), then operate normally on it through Konqueror. I admit I've never tried, since it's easier just to pull the SD card from the one MTP-using device I have.
TDE recognizes my Canon PowerShot camera with a USB cable as well as the SD card if I insert only that. Once upon a time I used the SD card method to transfer photos.
The flip phone is a different beast. The phone's back cover doesn't slide off and requires a flat edged screwdriver to pop off. Kind of PITA. The phone has a micro SD card but I don't have anything that can read or handle a micro SD. Likely I could buy some kind of holder or adapter but shrug.
This is not critical because I never have used the phone for photos. I'm just not into selfies. Transferring photo files was one of those spur of the moment things that popped into my head. I just happened to think about the idea yesterday. I can conceive of wanting to take a photo with the phone once in a blue moon but as shared in other replies, I have alternate solutions I can live with to transfer the files. Would be nice if TDE supported MTP but I'm not fretting over that.
On Wed, 23 Apr 2025 17:08:29 -0500 Darrell Anderson via tde-users users@trinitydesktop.org wrote:
The flip phone is a different beast. The phone's back cover doesn't slide off and requires a flat edged screwdriver to pop off. Kind of PITA. The phone has a micro SD card but I don't have anything that can read or handle a micro SD. Likely I could buy some kind of holder or adapter but shrug.
Some microSD cards come with a free adapter that bumps them up to full-sized SD—it's common enough that I have several spares. I also have an SD->USB adapter that cost about $10CAD several years ago and takes both micro and full-sized cards.
I don't know whether this is worth even that much of an outlay to you, though.
E. Liddell
On 4/23/25 6:38 PM, E. Liddell via tde-users wrote:
Some microSD cards come with a free adapter that bumps them up to full-sized SD—it's common enough that I have several spares. I also have an SD->USB adapter that cost about $10CAD several years ago and takes both micro and full-sized cards.
I don't know whether this is worth even that much of an outlay to you, though.
Thanks. I'll keep my eyes open for an adapter. Some months ago I picked up a couple of USBA-USBC adapters. Always nice to have silly gadgets like that. :)
On Wednesday 23 April 2025 16:53:34 Darrell Anderson via tde-users wrote:
On 4/23/25 6:38 PM, E. Liddell via tde-users wrote:
Some microSD cards come with a free adapter that bumps them up to full-sized SD—it's common enough that I have several spares. I also have an SD->USB adapter that cost about $10CAD several years ago and takes both micro and full-sized cards.
I don't know whether this is worth even that much of an outlay to you, though.
Thanks. I'll keep my eyes open for an adapter. Some months ago I picked up a couple of USBA-USBC adapters. Always nice to have silly gadgets like that. :)
I crawl out from under my rock, run off to the farmers market and library for a few hours, and come back to find 20+ emails (all from the TDE mailing list), most of them about this same question. One more reply here will be like a drop in the ocean.
Now, I no longer use a dumbphone, flip phone, and nowadays live in a place that is saturated with far too much technology and connectivity. I yearn for simpler times and places, my Amish neighbors from 50 years ago, or a nice anarcho-primitivist neo-Luddite commune ... that kind of thing.
Likewise, I don't use my phone much, except as a phone, a few times per month, and to send text messages, mostly to one other human being. I do, however, use it as a camera sometimes, or want to transfer other types of files from the DCIM folder in my phone's internal storage, or from my SD card. I don't like taking out the SD card just to transfer files, because it means shutting down my phone, and when I restart I lose some of the developers options that I've enabled, and I am forced to reset them manually.
This may not apply to your situation, as my smartphone is a little different from a dumbphone. I do have a couple of old dumphones buried away; but the same basic trick worked with them, and I simply kept on using it with smartphones.
I connect a USB dongle to my phone; for my current smartphone (Samsung Galaxy), I have a USB dongle with USB-C connector, same as my phone charger, so no problem connecting it. Then I plug in a flash drive, transfer my photos or whatever other files to the flash drive. Then I unmount the flash drive, plug it into my laptop, transfer to my laptop. As I said, I used to do the same thing with my dumphones, except that the USB dongles had different connectors.
As an comparatively old dog myself, I do understand that you want to keep doing things your own way, because it's what you're used to, you're comfortable with that. But this way, in my opinion, is just a lot simpler and easier.
Regarding the related question, about which other DEs are "compatible" with TDE, I would return to that matter of the more "minimalist" desktops. The bigger desktops with lots of eye-candy and flashy features tend to clutter up my system with garbage and cruft. Those few desktops that are the least trouble are, in my opinion, and in this order:
1 XFCE (comes as the default DE on my Devuan installation images) 2 MATE (so-so) 3 LXDE (the lightdm stuff); I've seen a couple of variants of this, too.
Otherwise, practically all other desktops manage to leave too much garbage that needs to be cleaned up. KDE4/5 krap and the Gnomish stuff are the worst; however, some Gnome packages are necessary, I guess, to make other stuff work. I've managed to strip out everything that isn't necessary, and eventually I may figure out a way to install TDE without ever having another desktop installed, with only Devuan packages, and using only GNU/Linux free/libre packages. But I am not quite there yet, and have other things to occupy my time besides wrestling with my machines and devices.
Bill
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
On Tuesday 22 April 2025 21:40:11 Darrell Anderson via tde-users wrote:
On 4/22/25 2:05 PM, deloptes via tde-users wrote:
I have a flip phone that is recognized immediately (lsusb) but does not appear anywhere in TDE that I can see.
and what is the output of the lsusb command?
The phone is an Alcatel A405DL running KaiOS 2.5.
Hello, What can do TDE with a flip phone ? (files transmission... ?), Thanks, cheers, André
On 4/23/25 5:24 PM, deloptes via tde-users wrote:
The phone is an Alcatel A405DL running KaiOS 2.5.
The phone should be recognized and handled properly by udev (if I am not completely wrong). Try mtp-detect and mtp-connect and see what it reports
The problem is not recognizing the phone. The problem, at least how this conversation began, is TDE does nothing when connecting the phone. KDE 5 and Xfce handle the phone fine. Probably other DEs too, but I haven't looked. Philippe replied that TDE does not have MTP support so that is that.
That said, mtp-detect reports the phone as a OneTouch 5042D rather than A405DL and complains about being unable to initialize because GVFS or KDE MTP is handling the device. On odd message because I am using TDE. I'll have to try later with a fresh reboot.
Darrell Anderson via tde-users wrote:
The problem is not recognizing the phone. The problem, at least how this conversation began, is TDE does nothing when connecting the phone. KDE 5 and Xfce handle the phone fine. Probably other DEs too, but I haven't looked. Philippe replied that TDE does not have MTP support so that is that.
well, but some are detected with tdeio-kamera and handled properly.
That said, mtp-detect reports the phone as a OneTouch 5042D rather than A405DL and complains about being unable to initialize because GVFS or KDE MTP is handling the device. On odd message because I am using TDE. I'll have to try later with a fresh reboot.
now you are starting to narrow down :) if something else is using whatever ...
When I plugin any phone here (Android or not) I always get a konqueror popping up and opening the device with the tdeio-kamera, which is part of kamera-trinity
Description: digital camera io_slave for Konqueror This is a digital camera io_slave for TDE which uses gphoto2 and libgpio to allow access to your camera's pictures with the URL camera:/ . This package is part of Trinity, as a component of the TDE graphics module. See the 'tde-trinity' and 'tdegraphics-trinity' packages for more information.
On 4/23/25 6:21 PM, deloptes via tde-users wrote:
That said, mtp-detect reports the phone as a OneTouch 5042D rather than A405DL and complains about being unable to initialize because GVFS or KDE MTP is handling the device. On odd message because I am using TDE. I'll have to try later with a fresh reboot.
now you are starting to narrow down :) if something else is using whatever ...
When I plugin any phone here (Android or not) I always get a konqueror popping up and opening the device with the tdeio-kamera, which is part of kamera-trinity
Description: digital camera io_slave for Konqueror This is a digital camera io_slave for TDE which uses gphoto2 and libgpio to allow access to your camera's pictures with the URL camera:/ . This package is part of Trinity, as a component of the TDE graphics module. See the 'tde-trinity' and 'tdegraphics-trinity' packages for more information.
I noticed something similar when I sent my previous reply. The /lib/udev/hwdb.d/69-libmtp.hwdb and 20-libgphoto2.hwdb files list the A405DL with a USB ID of 1bbb:901b (1BBBp901B).
On my computer lsusb shows 1bbb:900e.
Searching /lib/udev finds no IDs of 1bbb:900e (1BBBp900E). That might explain why TDE fails to show the device. Might not. Since the device is listed in both of those files, seems TDE should see the device using the 20-libgphoto2.hwdb file even if MTP is not supported.
Possibly all I need is to create a /etc/udev override files with the correct ID and name plate. I need to dig further, but my brain is tapped out for today.
Darrell Anderson via tde-users wrote:
I noticed something similar when I sent my previous reply. The /lib/udev/hwdb.d/69-libmtp.hwdb and 20-libgphoto2.hwdb files list the A405DL with a USB ID of 1bbb:901b (1BBBp901B).
On my computer lsusb shows 1bbb:900e.
those devices have different ids for different USB modes/identities. May be you need to switch identity manually or adjust something on the phone.
Searching /lib/udev finds no IDs of 1bbb:900e (1BBBp900E). That might explain why TDE fails to show the device. Might not. Since the device is listed in both of those files, seems TDE should see the device using the 20-libgphoto2.hwdb file even if MTP is not supported.
I don't know if tde uses this file.
Possibly all I need is to create a /etc/udev override files with the correct ID and name plate. I need to dig further, but my brain is tapped out for today.
Yes, I think this is worth trying.
-
ajh-valmer -
Darrell Anderson -
deloptes -
E. Liddell -
Jim -
Mavridis Philippe -
Mike Bird -
William Morder