On Sunday 30 August 2020 17:36:37 J Leslie Turriff wrote: > On 2020-08-30 19:27:34 William Morder via trinity-users wrote: > > On Sunday 30 August 2020 17:19:08 J Leslie Turriff wrote: > > > On 2020-08-30 19:07:51 Sl�vek Banko wrote: > > > > On Monday 31 of August 2020 01:40:16 Felix Miata via tde-users wrote: > > > > > deloptes composed on 2020-08-31 01:01 (UTC+0200): > > > > > > Felix Miata wrote: > > > > > >> Does TDE have an app made for this purpose? If yes, what's it > > > > > >> called. If not, suggest something please. > > > > > > > > > > > > Isn't konqueror working for you? > > > > > > > > > > > > AFAIK Android also uses MTP. > > > > > > I just found out recently (for a second time) that I need > > > > > > udisks2. Konqueror does the rest assuming you have the tdeio > > > > > > plugins and the permissions. > > > > > > My phone is not exactly android, but MTP is MTP. > > > > > > > > > > Konq's media doesn't show it. Konq says protocol not supported if I > > > > > type in mtp:/ or mtp:///. If mtp://, it lists / content. No kind of > > > > > popup announces phone's been connected, even though kernel > > > > > certainly noticed: > > > > > > > > > > # rpm -qa | egrep -i 'udisk|tdeb|eio' | sort > > > > > libudisks2-0-2.6.5-lp151.3.3.x86_64 > > > > > trinity-tdebase-14.0.8-1.oss151.x86_64 > > > > > trinity-tdebase-bin-14.0.8-1.oss151.x86_64 > > > > > trinity-tdebase-data-14.0.8-1.oss151.x86_64 > > > > > trinity-tdebase-libtqt3-integration-14.0.8-1.oss151.x86_64 > > > > > trinity-tdebase-runtime-data-common-14.0.8-1.oss151.x86_64 > > > > > trinity-tdebase-tdeio-pim-plugins-14.0.8-1.oss151.x86_64 > > > > > trinity-tdebase-tdeio-plugins-14.0.8-1.oss151.x86_64 > > > > > trinity-tdebase-tdeio-smb-plugin-14.0.8-1.oss151.x86_64 > > > > > trinity-tdebindings-14.0.8-1.oss151.x86_64 > > > > > trinity-tdebindings-java-14.0.8-1.oss151.x86_64 > > > > > trinity-tdemultimedia-tdeio-plugins-14.0.8-1.oss151.x86_64 > > > > > trinity-tdepim-tdeio-plugins-14.0.8-1.oss151.x86_64 > > > > > udisks2-2.6.5-lp151.3.3.x86_64 > > > > > # dmesg tail > > > > > [ 16.257759] sky2 0000:05:00.0 eth0: enabling interface > > > > > [ 220.180082] usb 3-2: new full-speed USB device number 2 using > > > > > uhci_hcd [ 220.320054] usb 3-2: device descriptor read/64, error > > > > > -71 [ 220.564091] usb 3-2: device descriptor read/64, error -71 [ > > > > > 221.008081] usb 3-2: new full-speed USB device number 3 using > > > > > uhci_hcd [ 221.144082] usb 3-2: device descriptor read/64, error > > > > > -71 [ 221.388055] usb 3-2: device descriptor read/64, error -71 [ > > > > > 221.496101] usb usb3-port2: attempt power cycle > > > > > [ 221.940075] usb 3-2: new full-speed USB device number 4 using > > > > > uhci_hcd [ 222.356061] usb 3-2: device not accepting address 4, > > > > > error -71 [ 222.484064] usb 3-2: new full-speed USB device number > > > > > 5 using uhci_hcd [ 222.900051] usb 3-2: device not accepting > > > > > address 5, error -71 [ 222.900086] usb usb3-port2: unable to > > > > > enumerate USB device [ 294.379489] FS-Cache: Loaded > > > > > [ 294.408171] RPC: Registered named UNIX socket transport module. > > > > > [ 294.408174] RPC: Registered udp transport module. > > > > > [ 294.408175] RPC: Registered tcp transport module. > > > > > [ 294.408175] RPC: Registered tcp NFSv4.1 backchannel transport > > > > > module. [ 294.441320] FS-Cache: Netfs 'nfs' registered for caching > > > > > [ 294.452516] Key type dns_resolver registered > > > > > [ 294.484410] NFS: Registering the id_resolver key type > > > > > [ 294.484422] Key type id_resolver registered > > > > > [ 294.484423] Key type id_legacy registered > > > > > [ 322.793093] sky2 0000:05:00.0 eth0: Link is up at 1000 Mbps, > > > > > full duplex, flow control both > > > > > [ 323.000756] NET: Registered protocol family 17 > > > > > # > > > > > > > > Hi, > > > > > > > > some time ago I looked that for newer phones that probably prefer MPT > > > > transfers instead of traditional usb-storage, we will probably need > > > > to port something like this to TDE - tdeio-slave: > > > > > > > > https://github.com/KDE/kio-mtp > > > > > > > > Cheers > > > > > > Hmmm... My relatively elderly Samsung SM-920A worked automagically > > > after I plugged it in via USB; the phone asked me if I wanted to allow > > > data sharing via MTP, and when I poked Allow the media manager appeared > > > on my desktop, showing 'Unknown device 1-12:1.0, Medium type: Camera, > > > with choices of Open in new window, digiKam Detect and Download, or Do > > > Nothing. > > > > > > Leslie > > > > Yup, older phones worked just by plugging in to USB; it was as easy as > > using a flash drive. The newer phones have gone to this MTP protocol. > > > > Bill > > But as I said, my old phone Does use the MTP protocol, and it shows up in > the Removable Media manager. > > Leslie > Yes, I was saying this more for the benefit of others. Don't waste your time trying to get the newer phones to work like that, because things have changed. Now we need to use other methods or protocols to get there. I had an old Samsung Android that I used for work, a few years ago. (I forget the exact model now, as it wasn't mine to keep, and I used it only for work.) But I just plugged it in, and presto! So when I got a slightly newer phone (Samsung Galaxy On5 S550TL), I imagined, wrongly, that I would be able to do the same, but it is not so. Only by accident did I discover that MATE's Caja file manager seems to recognize the MTP protocol. As for your phone, I don't know: is it rooted? Bill