30 Aug
2020
30 Aug
'20
8:42 p.m.
Does TDE have an app made for this purpose? If yes, what's it called. If not,
suggest something please.
--
Evolution as taught in public schools, like religion,
is based on faith, not on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
30 Aug
30 Aug
10:17 p.m.
On Sun August 30 2020 13:42:43 Felix Miata wrote:
Does TDE have an app made for this purpose? If yes,
what's it called. If
not, suggest something please.
I have in the dim and distant past used kdebluetooth and relatives
but it was never easy and these days I simply email the photos from
the android and open them in kmail.
If anyone has a better solution I'd love to hear it.
--Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
10:26 p.m.
On Sun, 30 Aug 2020, Mike Bird wrote:
On Sun August 30 2020 13:42:43 Felix Miata wrote:
Can't it be mounted as a Mass Storage Device?
I plug my Android phone (and/or Android tablet) into a USB port
and Trinity asks to open it in konqueror. Then Bob's your uncle.
Jonesy
--
Marvin L Jones | Marvin | W3DHJ | linux
Pueblo, Colorado | @ | Jonesy | FreeBSD __
38.238N 104.547W | jonz.net | DM78rf | SK
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Does TDE have an app made for this purpose? If
yes, what's it called.
If not, suggest something please.
I have in the dim and distant past used kdebluetooth and relatives
but it was never easy and these days I simply email the photos from
the android and open them in kmail.
If anyone has a better solution I'd love to hear it. 
10:45 p.m.
On 2020-08-30 17:26:16 Marvin Jones via trinity-users wrote:
On Sun, 30 Aug 2020, Mike Bird wrote:
That's the way I do it.
Leslie
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Sun August 30 2020 13:42:43 Felix Miata wrote:
Can't it be mounted as a Mass Storage Device?
I plug my Android phone (and/or Android tablet) into a USB port
and Trinity asks to open it in konqueror. Then Bob's your uncle.
Jonesy Does TDE have an app made for this purpose? If
yes, what's it called.
If not, suggest something please.
I have in the dim and distant past used kdebluetooth and relatives
but it was never easy and these days I simply email the photos from
the android and open them in kmail.
If anyone has a better solution I'd love to hear it.
11:13 p.m.
On Sun August 30 2020 15:26:16 Marvin Jones via trinity-users wrote:
Can't it be mounted as a Mass Storage Device?
I plug my Android phone (and/or Android tablet) into a USB port
and Trinity asks to open it in konqueror. Then Bob's your uncle.
When I try that my laptop just charges my phone.
Non-systemd Debian buster.
Anyone got the clue I'm missing?
--Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
11:43 p.m.
On Sunday 30 August 2020 16:13:38 Mike Bird wrote:
On Sun August 30 2020 15:26:16 Marvin Jones via
trinity-users wrote:
You can change you connection from charging to file transfer (which is MTP,
right?). I was messing round with this -- no luck, either -- but I did
discover something interesting.
When I was installing a Jessie system, I would use the MATE desktop to
complete the process (for downloading TDE packages, etc.); and in MATE, there
is a file manager called Caja, which allows access to an Android phone which
is connected via USB cable.
In Caja, the connections showed up like so:
mtp://[usb:002,007]/
mtp://[usb:002,010]/
mtp://[usb:002,010]/Phone
mtp://[usb:002,010]/Card
I could access files on the phone and SD card, but could not add or delete,
and using root did not seem to help. If the phone itself has been rooted,
that would probably help. But I am not quite there yet, so I set it aside for
the near future.
From what I can tell, Konqueror and other file managers do not recognize these
connections; only Caja, and then you need the MATE desktop. But I have not
explored this any further, due to lack of time, and other pressing issues.
Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Can't it be mounted as a Mass Storage
Device?
I plug my Android phone (and/or Android tablet) into a USB port
and Trinity asks to open it in konqueror. Then Bob's your uncle.
When I try that my laptop just charges my phone.
Non-systemd Debian buster.
Anyone got the clue I'm missing?
--Mike
11:44 p.m.
On Sunday 30 August 2020 06:13:38 pm Mike Bird wrote:
On Sun August 30 2020 15:26:16 Marvin Jones via
trinity-users wrote:
We're the wrong list for this :(
Dig up how to switch the phone to ???? mode. (Maybe MTP?) Then when you plug
it into the computer USB it's a harddrive.
The only thing I remember is you have to go open up the developer functions
(which is specific per phone hardware, so you'll need to search on that too)
Should read something like, go to xyz menu, tap 7 times on abc.
Can't it be mounted as a Mass Storage
Device?
I plug my Android phone (and/or Android tablet) into a USB port
and Trinity asks to open it in konqueror. Then Bob's your uncle.
When I try that my laptop just charges my phone. Non-systemd Debian buster.
Anyone got the clue I'm missing?
Maybe try going the other route? Doubt this will work, but it'll give you the
idea of what to look for:
https://f-droid.org/en/packages/org.kde.kdeconnect_tp/
https://community.kde.org/KDEConnect
Maybe this instead?
https://f-droid.org/en/packages/com.google.android.sambadocumentsprovider/
Dig through these, there should be something...
https://search.f-droid.org/?q=computer&lang=en
Best,
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
11:50 p.m.
On Sunday 30 August 2020 06:13:38 pm Mike Bird wrote:
On Sun August 30 2020 15:26:16 Marvin Jones via
trinity-users wrote:
Maybe you're using a "charge-only" cable? I believe the USB data and
charge wirings are unique/separate. I've seen "charge-only" cables in
the past.
Jonesy
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Can't it be mounted as a Mass Storage
Device?
I plug my Android phone (and/or Android tablet) into a USB port
and Trinity asks to open it in konqueror. Then Bob's your uncle.
When I try that my laptop just charges my phone. 
31 Aug
31 Aug
4:46 a.m.
New subject: fetching photos from android phone
On Monday 31 August 2020 00.17:59 Mike Bird wrote:
I have in the dim and distant past used kdebluetooth
and relatives
but it was never easy and these days I simply email the photos from
the android and open them in kmail.
If anyone has a better solution I'd love to hear it.
--Mike
As most (Android) phones now no more work as USB drives and require MTP - and
maybe because I don't use my phone for much more that phone and agenda) I use
a tool called Airmore. Works quite well overt the local wifi.
Thierry
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
5:49 a.m.
New subject: fetching photos from android phone
On Sunday 30 August 2020 21:46:18 Thierry de Coulon wrote:
On Monday 31 August 2020 00.17:59 Mike Bird wrote:
Bill's simple solution, but it will cost some money.
SD card - 256 gb $85 US
SD card reader - Vivitar 50-in-1 $10 US
Save or move stuff to the SD card. The reader plugs into a USB port. My old
reader transfers are slow (200 kbps tops), but my older one was even slower.
I just got the new reader, and have the new SD card set to pick up maybe next
weekend. (It was to be yesterday, but I am getting too old to be schlepping
all over the place like I used to do.)
Music is more my thing, but here I put the real money into good
professional-grade studio headphones; comes with different size plug-in
jacks, so I can listen on practically any device. I listen more on my phone
now than on computer or anything else. 256 gb holds a whole lotta music.
Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
I have in the dim and distant past used
kdebluetooth and relatives
but it was never easy and these days I simply email the photos from
the android and open them in kmail.
If anyone has a better solution I'd love to hear it.
--Mike
As most (Android) phones now no more work as USB drives and require MTP -
and maybe because I don't use my phone for much more that phone and agenda)
I use a tool called Airmore. Works quite well overt the local wifi.
Thierry
30 Aug
30 Aug
11:01 p.m.
New subject: [trinity-users] Re: fetching photos from android phone
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.
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
11:40 p.m.
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
#
--
Evolution as taught in public schools, like religion,
is based on faith, not on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
31 Aug
31 Aug
12:07 a.m.
New subject: [trinity-users] Re: fetching photos from android phone
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):
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
--
Slávek
Felix Miata wrote:
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
# 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.
12:19 a.m.
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:
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
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
deloptes composed on 2020-08-31 01:01
(UTC+0200):
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 Felix Miata wrote:
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
# 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.
12:27 a.m.
On Sunday 30 August 2020 17:19:08 J Leslie Turriff wrote:
On 2020-08-30 19:07:51 Slávek Banko wrote:
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
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Monday 31 of August 2020 01:40:16 Felix Miata
via tde-users wrote:
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
deloptes composed on 2020-08-31 01:01
(UTC+0200):
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 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
#
12:36 a.m.
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:
But as I said, my old phone Does use the MTP protocol, and it shows up in the
Removable Media manager.
Leslie
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On 2020-08-30 19:07:51 Slávek Banko wrote:
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 On Monday 31 of August 2020 01:40:16 Felix Miata
via tde-users wrote:
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 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
1:26 a.m.
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:
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
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Sunday 30 August 2020 17:19:08 J Leslie
Turriff wrote:
But as I said, my old phone Does use the MTP protocol, and it shows up in
the Removable Media manager.
Leslie
On 2020-08-30 19:07:51 Slávek Banko wrote:
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 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
1:49 a.m.
On Monday 31 of August 2020 03:26:35 William Morder via trinity-users
wrote:
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
I noticed a change when on an older phone where I had CyanogenMod installed
I updated to LineageOS. Previously it was possible to use classic
usb-storage, now there is only MPT for file transfers.
Cheers
--
Slávek
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
7:54 a.m.
New subject: [users] fetching photos from android phone
On 2020-08-30 20:26:35 William Morder via trinity-users wrote:
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
It is not.
If I understand you correctly, MTP works for older phones but not newer ones?
I had the impression from reading this thread that MTP was something new; now
I'm confused. :-)
Leslie
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
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
7:59 a.m.
New subject: [users] fetching photos from android phone
On Monday 31 August 2020 09.54:16 J Leslie Turriff wrote:
If I understand you correctly, MTP works for older
phones but not newer
ones? I had the impression from reading this thread that MTP was something
new; now I'm confused. :-)
Leslie
Mass storage and MTP can coexist, older phones had this option. MTP was
introduced by Microsoft and, as usual, we lost the alternative on the way.
As I have hardly used MTP at all, I don't know the difference. I had a feeling
that mass storage let you see your phone as an external drive, while MTP
(Media Transfer Protocol) onyl gave you acces to "media" (music, photos,
videos) but not to the rest of the drive - maybe I'm wrong.
Thierry
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
8:04 a.m.
New subject: [users] fetching photos from android phone
On Monday 31 August 2020 00:54:16 J Leslie Turriff wrote:
On 2020-08-30 20:26:35 William Morder via
trinity-users wrote:
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
It is not.
If I understand you correctly, MTP works for older phones but not newer
ones? I had the impression from reading this thread that MTP was something
new; now I'm confused. :-)
Leslie
I cannot say authoritatively whether MTP is "new" or "old"; what I do
know is
that I never saw that protocol with my old phone. I could just connect my
phone to computer using a USB plug, and it worked just like a flash drive.
When I got a newer phone, it didn't work, and that's when I heard about MTP,
so I assume that it is newer. Maybe it was always around, for as long as
smartphones, but I didn't notice because it just worked. Regardless, whether
MTP is a recent development or not, something has been fundamentally changed,
so we must find different ways to get there.
Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
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
8:12 a.m.
New subject: [users] fetching photos from android phone
Anno domini 2020 Mon, 31 Aug 01:04:19 -0700
William Morder via trinity-users scripsit:
On Monday 31 August 2020 00:54:16 J Leslie Turriff wrote:
I use "adb" to get things from testdevices or put things onto
devices("Testdevices" 'cause don't use a smartphone). MTP has been
around for more than 15 years, but I never got it to work.
On 2020-08-30 20:26:35 William Morder via
trinity-users wrote:
It is not.
If I understand you correctly, MTP works for older phones but not newer
ones? I had the impression from reading this thread that MTP was something
new; now I'm confused. :-)
Leslie
I cannot say authoritatively whether MTP is "new" or "old"; what I do
know is
that I never saw that protocol with my old phone. I could just connect my
phone to computer using a USB plug, and it worked just like a flash drive.
When I got a newer phone, it didn't work, and that's when I heard about MTP,
so I assume that it is newer. Maybe it was always around, for as long as
smartphones, but I didn't notice because it just worked. Regardless, whether
MTP is a recent development or not, something has been fundamentally changed,
so we must find different ways to get there. 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
Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
8:30 a.m.
New subject: [users] [users] fetching photos from android phone
On 2020-08-31 03:12:14 Dr. Nikolaus Klepp wrote:
Anno domini 2020 Mon, 31 Aug 01:04:19 -0700
William Morder via trinity-users scripsit:
How strange; for me it's working out-of-the-box. (I think I've connected my
phone to my desktop only about four times in the last four years.)
Leslie
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Monday 31 August 2020 00:54:16 J Leslie
Turriff wrote:
I use "adb" to get things from testdevices or put things onto
devices("Testdevices" 'cause don't use a smartphone). MTP has been
around
for more than 15 years, but I never got it to work.
> Bill On 2020-08-30 20:26:35 William Morder via
trinity-users wrote:
I cannot say authoritatively whether MTP is "new" or "old"; what I
do
know is that I never saw that protocol with my old phone. I could just
connect my phone to computer using a USB plug, and it worked just like a
flash drive.
When I got a newer phone, it didn't work, and that's when I heard about
MTP, so I assume that it is newer. Maybe it was always around, for as
long as smartphones, but I didn't notice because it just worked.
Regardless, whether MTP is a recent development or not, something has
been fundamentally changed, so we must find different ways to get there. 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
It is not.
If I understand you correctly, MTP works for older phones but not
newer ones? I had the impression from reading this thread that MTP was
something new; now I'm confused. :-)
Leslie
8:42 a.m.
New subject: [users] fetching photos from android phone
On Monday 31 August 2020 01:12:14 Dr. Nikolaus Klepp wrote:
Anno domini 2020 Mon, 31 Aug 01:04:19 -0700
William Morder via trinity-users scripsit:
Don't use a smartphone, that's smart.
Anyway ... if the phone is rooted, then I believe that this problem is
supposed to disappear. This is on my list, but there are other things that
rank higher or are more immediate concerns.
Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Monday 31 August 2020 00:54:16 J Leslie
Turriff wrote:
I use "adb" to get things from testdevices or put things onto
devices("Testdevices" 'cause don't use a smartphone). MTP has been
around
for more than 15 years, but I never got it to work.
> Bill
>
> On 2020-08-30 20:26:35 William Morder via
trinity-users wrote:
I cannot say authoritatively whether MTP is "new" or "old"; what I
do
know is that I never saw that protocol with my old phone. I could just
connect my phone to computer using a USB plug, and it worked just like a
flash drive.
When I got a newer phone, it didn't work, and that's when I heard about
MTP, so I assume that it is newer. Maybe it was always around, for as
long as smartphones, but I didn't notice because it just worked.
Regardless, whether MTP is a recent development or not, something has
been fundamentally changed, so we must find different ways to get there. 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
It is not.
If I understand you correctly, MTP works for older phones but not
newer ones? I had the impression from reading this thread that MTP was
something new; now I'm confused. :-)
Leslie
9:12 a.m.
New subject: [users] fetching photos from android phone
Anno domini 2020 Mon, 31 Aug 01:42:37 -0700
William Morder via trinity-users scripsit:
On Monday 31 August 2020 01:12:14 Dr. Nikolaus Klepp wrote:
Won't spill the fun, but the problem might not disappear. I have here a Samsng Galaxy
note something with linageos. It can't do usb-masstorage-device.
Anno domini 2020 Mon, 31 Aug 01:04:19 -0700
William Morder via trinity-users scripsit:
Don't use a smartphone, that's smart.
Anyway ... if the phone is rooted, then I believe that this problem is
supposed to disappear. This is on my list, but there are other things that
rank higher or are more immediate concerns. On Monday 31 August 2020 00:54:16 J Leslie
Turriff wrote:
I use "adb" to get things from testdevices or put things onto
devices("Testdevices" 'cause don't use a smartphone). MTP has been
around
for more than 15 years, but I never got it to work.
> Bill
>
> On 2020-08-30 20:26:35 William Morder via
trinity-users wrote:
> 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
It is not.
If I understand you correctly, MTP works for older phones but not
newer ones? I had the impression from reading this thread that MTP was
something new; now I'm confused. :-)
Leslie
I cannot say authoritatively whether MTP is "new" or "old"; what I
do
know is that I never saw that protocol with my old phone. I could just
connect my phone to computer using a USB plug, and it worked just like a
flash drive.
When I got a newer phone, it didn't work, and that's when I heard about
MTP, so I assume that it is newer. Maybe it was always around, for as
long as smartphones, but I didn't notice because it just worked.
Regardless, whether MTP is a recent development or not, something has
been fundamentally changed, so we must find different ways to get there.
Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
10:05 a.m.
New subject: [users] fetching photos from android phone
On Monday 31 August 2020 02:12:03 Dr. Nikolaus Klepp wrote:
Anno domini 2020 Mon, 31 Aug 01:42:37 -0700
William Morder via trinity-users scripsit:
I wonder if something like a PinePhone would be more cooperative -- or a phone
with Replicant installed, or other free/libre OS? I've been considering one
of those options, because otherwise I believe that I will move back to a
landline.
Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Monday 31 August 2020 01:12:14 Dr. Nikolaus
Klepp wrote:
Won't spill the fun, but the problem might not disappear. I have here a
Samsng Galaxy note something with linageos. It can't do
usb-masstorage-device.
Anno domini 2020 Mon, 31 Aug 01:04:19 -0700
William Morder via trinity-users scripsit:
Don't use a smartphone, that's smart.
Anyway ... if the phone is rooted, then I believe that this problem is
supposed to disappear. This is on my list, but there are other things
that rank higher or are more immediate concerns. On Monday 31 August 2020 00:54:16 J Leslie
Turriff wrote:
> On 2020-08-30 20:26:35 William Morder via trinity-users wrote:
> > 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_6
> > > > > > >4 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
>
> It is not.
> If I understand you correctly, MTP works for older phones but not
> newer ones? I had the impression from reading this thread that MTP
> was something new; now I'm confused. :-)
>
> Leslie
I cannot say authoritatively whether MTP is "new" or "old"; what I
do
know is that I never saw that protocol with my old phone. I could
just connect my phone to computer using a USB plug, and it worked
just like a flash drive.
When I got a newer phone, it didn't work, and that's when I heard
about MTP, so I assume that it is newer. Maybe it was always around,
for as long as smartphones, but I didn't notice because it just
worked. Regardless, whether MTP is a recent development or not,
something has been fundamentally changed, so we must find different
ways to get there.
I use "adb" to get things from testdevices or put things onto
devices("Testdevices" 'cause don't use a smartphone). MTP has been
around for more than 15 years, but I never got it to work.
> Bill
10:18 a.m.
New subject: [users] fetching photos from android phone
Anno domini 2020 Mon, 31 Aug 03:05:45 -0700
William Morder via trinity-users scripsit:
[cutting out a lot of stuff ..]
I wonder if something like a PinePhone would be more cooperative -- or a phone
with Replicant installed, or other free/libre OS? I've been considering one
of those options, because otherwise I believe that I will move back to a
landline.
I was thinking about building my own phone from scrap parts. Something like the Siemens
C55, just with an arduino + Sim800 module + 18650 :)
Don't
use a smartphone, that's smart.
Anyway ... if the phone is rooted, then I believe that this problem is
supposed to disappear. This is on my list, but there are other things
that rank higher or are more immediate concerns.
Won't spill the fun, but the problem might not disappear. I have here a
Samsng Galaxy note something with linageos. It can't do
usb-masstorage-device.
Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
10:29 a.m.
New subject: [users] fetching photos from android phone
On Monday 31 August 2020 03:18:04 Dr. Nikolaus Klepp wrote:
Anno domini 2020 Mon, 31 Aug 03:05:45 -0700
William Morder via trinity-users scripsit:
I like your style. That is partly why I like building my own computers from
parts; because then at least I know what goes into it. Well, that, and also
it's a lot cheaper.
The same goes for food; better to learn some cookery skills, rather than
depending on others. On the down side, I am now very hard to please.
Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
[cutting out a lot of stuff ..]
I wonder if something like a PinePhone would be more cooperative -- or a
phone with Replicant installed, or other free/libre OS? I've been
considering one of those options, because otherwise I believe that I will
move back to a landline.
I was thinking about building my own phone from scrap parts. Something like
the Siemens C55, just with an arduino + Sim800 module + 18650 :)
Don't
use a smartphone, that's smart.
Anyway ... if the phone is rooted, then I believe that this problem
is supposed to disappear. This is on my list, but there are other
things that rank higher or are more immediate concerns.
Won't spill the fun, but the problem might not disappear. I have here a
Samsng Galaxy note something with linageos. It can't do
usb-masstorage-device.
12:34 p.m.
New subject: [users] fetching photos from android phone
On Mon, 31 Aug 2020, Dr. Nikolaus Klepp wrote:
Anno domini 2020 Mon, 31 Aug 03:05:45 -0700
William Morder via trinity-users scripsit:
OK! Warm up your soldering iron:
http://skysedge.us/unsmartphones/rotarycellphone_3g/
available from the Brookhaven National Lab engineer Justine Haupt
that built the first one. Backstory here:
http://justine-haupt.com/rotarycellphone/
But it seems not to be a _complete_ kit. There's a list of stuff
you need to supply on your own. But, there does not seem to be
any unobtainium in the list.
It sure would be a WOW! factor at the next cocktail party I go to.
But, WAIT!!! I don't go to cocktail parties....
Jonesy
--
Marvin L Jones | Marvin | W3DHJ | linux
Pueblo, Colorado | @ | Jonesy | FreeBSD __
38.238N 104.547W | jonz.net | DM78rf | SK
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
[cutting out a lot of stuff ..]
I wonder if something like a PinePhone would be more cooperative --
or a phone with Replicant installed, or other free/libre OS? I've
been considering one of those options, because otherwise I believe
that I will move back to a landline.
I was thinking about building my own phone from scrap parts. Something
like the Siemens C55, just with an arduino + Sim800 module + 18650 :) Don't
use a smartphone, that's smart.
Anyway ... if the phone is rooted, then I believe that this
problem is supposed to disappear. This is on my list, but there
are other things that rank higher or are more immediate concerns.
Won't spill the fun, but the problem might not disappear. I have
here a Samsng Galaxy note something with linageos. It can't do
usb-masstorage-device.
1:14 p.m.
New subject: [users] fetching photos from android phone
On Monday 31 August 2020 05:34:08 Marvin Jones via trinity-users wrote:
On Mon, 31 Aug 2020, Dr. Nikolaus Klepp wrote:
Maybe you will have to start, once you have built it. Or if you build it,
maybe the cocktail parties will come to you.
As a matter of fact, I do have a pretty nice soldering iron, but now it is in
my storage unit, which is far, far away from here.
It would be a total badass feat, though, to be able to build a phone oneself.
You have put the thought in my head.
Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Anno domini 2020 Mon, 31 Aug 03:05:45 -0700
William Morder via trinity-users scripsit:
OK! Warm up your soldering iron:
http://skysedge.us/unsmartphones/rotarycellphone_3g/
available from the Brookhaven National Lab engineer Justine Haupt
that built the first one. Backstory here:
http://justine-haupt.com/rotarycellphone/
But it seems not to be a _complete_ kit. There's a list of stuff
you need to supply on your own. But, there does not seem to be
any unobtainium in the list.
It sure would be a WOW! factor at the next cocktail party I go to.
But, WAIT!!! I don't go to cocktail parties....
Jonesy [cutting out a lot of stuff ..]
I was thinking about building my own phone from scrap parts. Something
like the Siemens C55, just with an arduino + Sim800 module + 18650 :) > Don't use a smartphone, that's
smart.
>
> Anyway ... if the phone is rooted, then I believe that this
> problem is supposed to disappear. This is on my list, but there
> are other things that rank higher or are more immediate concerns.
Won't spill the fun, but the problem might not disappear. I have
here a Samsng Galaxy note something with linageos. It can't do
usb-masstorage-device.
I wonder if something like a PinePhone would be more cooperative --
or a phone with Replicant installed, or other free/libre OS? I've
been considering one of those options, because otherwise I believe
that I will move back to a landline.
8:11 p.m.
New subject: [users] fetching photos from android phone
I have had success over usb cable with my phone but it didn't seem
possible with my partner's which is about three yrs younger than mine.
I have a Samsung J3.
however in the past I have also used a kind of sftp client which
worked well. I did a brief look in the 'PlayStore' and see some
options though not the one I used.
someone mentioned 'airmore' which I don't know but likely similar.
I've also had success with gmtp which was mentioned, but that does
assume mtp is on the phone.
I'd try the sshfs/sftp route if nothing else avails.
there is sending stuff by email, also suggested. one can also upload
to Google-drive.
(assuming Android throughout.)
f.
--
Felmon Davis
Verbum sat sapienti.
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
1:41 p.m.
New subject: [users] fetching photos from android phone
On Monday 31 August 2020 William Morder wrote:
On Monday 31 August 2020 02:12:03 Dr. Nikolaus Klepp
wrote:
Interesting question. I've been trying to find some information for
PinePhone and it seems that there is currently only a USB-network
available for USB host mode.
Cheers
--
Slávek
.
.
.
Won't spill the fun, but the problem might not disappear. I have here
a Samsng Galaxy note something with linageos. It can't do
usb-masstorage-device.
I wonder if something like a PinePhone would be more cooperative -- or a
phone with Replicant installed, or other free/libre OS? I've been
considering one of those options, because otherwise I believe that I
will move back to a landline.
Bill
7:39 p.m.
New subject: fetching photos from android phone
Felix Miata wrote:
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:
I don't think there is MTP protocol implemented in konqueror, but I have
installed go-mtpfs and as J Lesslie Turriff reports, it works out of the
box in konqueror.
You have to put the phone in MTP mode though.
Then if you go to System > Storage Media and double click the device, it
should work, but I am not sure if it is typical MTP - I believe so because
I do not have to umount it as I do for USB devices.
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
8:49 p.m.
New subject: fetching photos from android phone
On Monday 31 of August 2020 21:39:56 deloptes via tde-users wrote:
Felix Miata wrote:
Yes, go-mtpfs is a tool that I use from time to time - it mounts the phone
to a folder in the tree, making it possible to use Konqueror just like any
other folder. But I usually did the mount / umount it manually from the
command line. Anyway, there would be nice if we could port kio-mtp to
tdeio-mtp and then use it without the need for additional tools.
Cheers
--
Slávek
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:
I don't think there is MTP protocol implemented in konqueror, but I have
installed go-mtpfs and as J Lesslie Turriff reports, it works out of the
box in konqueror.
You have to put the phone in MTP mode though.
Then if you go to System > Storage Media and double click the device, it
should work, but I am not sure if it is typical MTP - I believe so
because I do not have to umount it as I do for USB devices.
8:56 p.m.
New subject: fetching photos from android phone
On Monday 31 August 2020 13:49:15 Slávek Banko via tde-users wrote:
On Monday 31 of August 2020 21:39:56 deloptes via
tde-users wrote:
Now that's what I am looking for, as well. I would prefer that it is either
TDE software, or vanilla Devuan/Debian. Konqueror would be perfect, as it's
what I normally use as a file manager. (I have almost never used it as a web
browser, though I hear good things.)
Between that, and being able to build my own smartphone (or at least buy
something like a PinePhone), I would be all set, and might even decide not to
abandon smartphones altogether.
Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Felix Miata wrote:
Yes, go-mtpfs is a tool that I use from time to time - it mounts the phone
to a folder in the tree, making it possible to use Konqueror just like any
other folder. But I usually did the mount / umount it manually from the
command line. Anyway, there would be nice if we could port kio-mtp to
tdeio-mtp and then use it without the need for additional tools.
Cheers 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:
I don't think there is MTP protocol implemented in konqueror, but I have
installed go-mtpfs and as J Lesslie Turriff reports, it works out of the
box in konqueror.
You have to put the phone in MTP mode though.
Then if you go to System > Storage Media and double click the device, it
should work, but I am not sure if it is typical MTP - I believe so
because I do not have to umount it as I do for USB devices.
1 Sep
1 Sep
6:18 a.m.
New subject: fetching photos from android phone
Felix Miata wrote:
| egrep -i 'udisk|tdeb|eio' | sort
$ dpkg -l | egrep -i 'mtp|udisk|tdeb|eio' | sort | awk '{print $2}'
go-mtpfs
libnet-smtp-ssl-perl
libudisks2-0:amd64
tdebase-data-trinity
tdebase-runtime-data-common-trinity
tdebase-tdeio-plugins-trinity
tdebase-tdeio-smb-trinity
tdebase-trinity
tdebase-trinity-bin
tdebase-trinity-dbg
tdeio-umountwrapper-trinity
tdemultimedia-tdeio-plugins-trinity
tdepim-tdeio-plugins-trinity
udisks2
udisks2-lvm2
I don't see the tdeio-umountwrapper, but honestly I don't know which one is
exactly responsible for handling the MTP here.
I am on Sailfish OS phone that apparently supports MTP (this is why I
installed go-mtpfs before I found out I was missing udisks2 the first
time).
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
6:28 a.m.
New subject: fetching photos from android phone
On Tuesday 01 September 2020 08.18:28 deloptes wrote:
I am on Sailfish OS phone that apparently supports MTP
From a search I get that mass storage was dropped when
Android/Google
increased "data scurity" on the phones. Why we are not
allowed to take
responsibility for the security of our data I don't know.
I guess that any newer Android version will be MTP only. I did try various
Linux OSes on a PinePhone and I nust say the results are - for the time
being - quite devastating. The device is slow, and the OS are far from ready,
to the point that many can't even... phone. Apps don't adapt to the screen,
most don't rotate (and usually only manualy if they do). There's no camera
suppport or very bad if any.
I don't use my phone much, and I I still use a "real" camera for pictures,
but
even so I'm not abandonning my compact Sony for a while.
Thierry
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
9:42 p.m.
New subject: fetching photos from android phone
Thierry de Coulon wrote:
From a search I get that mass storage was dropped when
Android/Google
increased "data scurity" on the phones. Why we are not allowed to take
responsibility for the security of our data I don't know.
I guess that any newer Android version will be MTP only. I did try various
Linux OSes on a PinePhone and I nust say the results are - for the time
being - quite devastating. The device is slow, and the OS are far from
ready, to the point that many can't even... phone. Apps don't adapt to the
screen, most don't rotate (and usually only manualy if they do). There's
no camera suppport or very bad if any.
I don't use my phone much, and I I still use a "real" camera for pictures,
but even so I'm not abandonning my compact Sony for a while.
I started using Nokia N9 when the whole madness around "smart" kicked in. It
was a kind of debian OS (MeeGo) and it is still a great phone.
Few years later when Nokia gave up the guys that were working on N9 founded
Jolla and 2016 I bought the Intex AquaFish, that unfortunately finally
ended in the hands of my wife. 2017 it was not possible to purchase the
Intex anymore, because production was too expensive and Jolla was in bad
shape (They failed on the hardware manufacturing costs). I went for Sony
Xperia X where you could flash the Saialfish OS and I am still using it
today as primary phone. Licensed (29,-€) version has Dalvik and you can run
Android apps as well. I tried last year XA2 (which has a newer Dalvik), but
I failed flashing it and returned as I did not have the time to
investigate. At the moment I can not find hardware (latest is Xperia 10 or
so but is also out of stock).
Long story short there are only few meaningful alternatives to Android and
iOS and there is nothing for my pocket - Librem 5
(https://shop.puri.sm/shop/librem-5/) $750,- or PinePhone that you
described very well.
I would like to try librem-5 but 750 is simply too much and I am not sure it
will cover my daily use cases.
In 2016 I was already familiar with Qt, so Sailfish seemed to be a good
choice and things that worked on the N9 still work on the Sailfish (well
some had to be recompiled and pimped of course). But at the moment I have
peace.
It is indeed very very hard to swim against the mainstream on the phone
market. Incredible (IMO)!
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
10:08 p.m.
New subject: [users] Re: fetching photos from android phone
On 2020-09-01 16:42:50 deloptes wrote:
Thierry de Coulon wrote:
Yep; way too many unchecked monopolies in the "technology" world today.
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
From a search I get that mass storage was dropped
when Android/Google
increased "data scurity" on the phones. Why we are not allowed to take
responsibility for the security of our data I don't know.
I guess that any newer Android version will be MTP only. I did try
various Linux OSes on a PinePhone and I nust say the results are - for
the time being - quite devastating. The device is slow, and the OS are
far from ready, to the point that many can't even... phone. Apps don't
adapt to the screen, most don't rotate (and usually only manualy if they
do). There's no camera suppport or very bad if any.
I don't use my phone much, and I I still use a "real" camera for
pictures, but even so I'm not abandonning my compact Sony for a while.
I started using Nokia N9 when the whole madness around "smart" kicked in.
It was a kind of debian OS (MeeGo) and it is still a great phone.
Few years later when Nokia gave up the guys that were working on N9 founded
Jolla and 2016 I bought the Intex AquaFish, that unfortunately finally
ended in the hands of my wife. 2017 it was not possible to purchase the
Intex anymore, because production was too expensive and Jolla was in bad
shape (They failed on the hardware manufacturing costs). I went for Sony
Xperia X where you could flash the Saialfish OS and I am still using it
today as primary phone. Licensed (29,-€) version has Dalvik and you can run
Android apps as well. I tried last year XA2 (which has a newer Dalvik), but
I failed flashing it and returned as I did not have the time to
investigate. At the moment I can not find hardware (latest is Xperia 10 or
so but is also out of stock).
Long story short there are only few meaningful alternatives to Android and
iOS and there is nothing for my pocket - Librem 5
(https://shop.puri.sm/shop/librem-5/) $750,- or PinePhone that you
described very well.
I would like to try librem-5 but 750 is simply too much and I am not sure
it will cover my daily use cases.
In 2016 I was already familiar with Qt, so Sailfish seemed to be a good
choice and things that worked on the N9 still work on the Sailfish (well
some had to be recompiled and pimped of course). But at the moment I have
peace.
It is indeed very very hard to swim against the mainstream on the phone
market. Incredible (IMO)!
2 Sep
2 Sep
2:38 a.m.
New subject: [users] Re: fetching photos from android phone
‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday, September 1, 2020 3:08 PM, J Leslie Turriff <jlturriff(a)mail.com> wrote:
On 2020-09-01 16:42:50 deloptes wrote:
> Thierry de Coulon wrote:
>
> > From a search I get that mass storage was
dropped when Android/Google
> > increased "data scurity" on the phones. Why we are not allowed to
take
> > responsibility for the security of our data I don't know.
> > I guess that any newer Android version will be MTP only. I did try
> > various Linux OSes on a PinePhone and I nust say the results are - for
> > the time being - quite devastating. The device is slow, and the OS are
> > far from ready, to the point that many can't even... phone. Apps don't
> > adapt to the screen, most don't rotate (and usually only manualy if they
> > do). There's no camera suppport or very bad if any.
> > I don't use my phone much, and I I still use a "real" camera for
> > pictures, but even so I'm not abandonning my compact Sony for a while.
>
I started
using Nokia N9 when the whole madness around "smart" kicked in.
It was a kind of debian OS (MeeGo) and it is still a great phone.
Few years later when Nokia gave up the guys that were working on N9 founded
Jolla and 2016 I bought the Intex AquaFish, that unfortunately finally
ended in the hands of my wife. 2017 it was not possible to purchase the
Intex anymore, because production was too expensive and Jolla was in bad
shape (They failed on the hardware manufacturing costs). I went for Sony
Xperia X where you could flash the Saialfish OS and I am still using it
today as primary phone. Licensed (29,-€) version has Dalvik and you can run
Android apps as well. I tried last year XA2 (which has a newer Dalvik), but
I failed flashing it and returned as I did not have the time to
investigate. At the moment I can not find hardware (latest is Xperia 10 or
so but is also out of stock).
Long story short there are only few meaningful alternatives to Android and
iOS and there is nothing for my pocket - Librem 5
(https://shop.puri.sm/shop/librem-5/) $750,- or PinePhone that you
described very well.
I would like to try librem-5 but 750 is simply too much and I am not sure
it will cover my daily use cases.
In 2016 I was already familiar with Qt, so Sailfish seemed to be a good
choice and things that worked on the N9 still work on the Sailfish (well
some had to be recompiled and pimped of course). But at the moment I have
peace.
It is indeed very very hard to swim against the mainstream on the phone
market. Incredible (IMO)!
Yep; way too many unchecked monopolies in the
"technology" world today.
well said, my experience also.
My solution is pay for webmail, protonmail, mykolab. encrypted (end to end).
I have been following /e/. /e/ provides a "de-googleized" android, supports
quite a few phones if you are into flashing stuff.
/e/ also sells phones pre-installed.
https://e.foundation/ , Europe..I wonder if the phones would work in the USA.
greg
4:43 p.m.
New subject: [users] Re: fetching photos from android phone
On Tuesday 01 September 2020 09:38:31 pm greg wrote:
https://doc.e.foundation/devices/
Number of Smartphones officially supported by /e/OS : 93
Select Region: North America
-No results found-
Bummer, although I wasn't that happy with their you must have an /e/ account?
(I could have read that wrong though)
Thanks for the link!,
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday, September 1, 2020 3:08 PM, J Leslie Turriff <jlturriff(a)mail.com>
wrote:
On 2020-09-01
16:42:50 deloptes wrote:
well said, my experience also.
My solution is pay for webmail, protonmail, mykolab. encrypted (end to
end).
I have been following /e/. /e/ provides a "de-googleized" android, supports
quite a few phones if you are into flashing stuff. /e/ also sells phones
pre-installed.
https://e.foundation/ , Europe..I wonder if the phones would work in the
USA. Thierry de Coulon wrote:
Yep; way too many unchecked monopolies in the "technology" world today. From a search I get that mass storage was dropped
when Android/Google
increased "data scurity" on the phones. Why we are not allowed to
take responsibility for the security of our data I don't know.
I guess that any newer Android version will be MTP only. I did try
various Linux OSes on a PinePhone and I nust say the results are -
for the time being - quite devastating. The device is slow, and the
OS are far from ready, to the point that many can't even... phone.
Apps don't adapt to the screen, most don't rotate (and usually only
manualy if they do). There's no camera suppport or very bad if any.
I don't use my phone much, and I I still use a "real" camera for
pictures, but even so I'm not abandonning my compact Sony for a
while.
I started using Nokia N9 when the whole madness around "smart" kicked
in. It was a kind of debian OS (MeeGo) and it is still a great phone.
Few years later when Nokia gave up the guys that were working on N9
founded Jolla and 2016 I bought the Intex AquaFish, that unfortunately
finally ended in the hands of my wife. 2017 it was not possible to
purchase the Intex anymore, because production was too expensive and
Jolla was in bad shape (They failed on the hardware manufacturing
costs). I went for Sony Xperia X where you could flash the Saialfish OS
and I am still using it today as primary phone. Licensed (29,-€)
version has Dalvik and you can run Android apps as well. I tried last
year XA2 (which has a newer Dalvik), but I failed flashing it and
returned as I did not have the time to investigate. At the moment I can
not find hardware (latest is Xperia 10 or so but is also out of stock).
Long story short there are only few meaningful alternatives to Android
and iOS and there is nothing for my pocket - Librem 5
(https://shop.puri.sm/shop/librem-5/) $750,- or PinePhone that you
described very well.
I would like to try librem-5 but 750 is simply too much and I am not
sure it will cover my daily use cases.
In 2016 I was already familiar with Qt, so Sailfish seemed to be a good
choice and things that worked on the N9 still work on the Sailfish
(well some had to be recompiled and pimped of course). But at the
moment I have peace.
It is indeed very very hard to swim against the mainstream on the phone
market. Incredible (IMO)!
9:35 p.m.
New subject: [users] Re: fetching photos from android phone
Michael wrote:
https://doc.e.foundation/devices/
Number of Smartphones officially supported by /e/OS : 93
Select Region: North America
-No results found-
Bummer, although I wasn't that happy with their you must have an /e/
account? (I could have read that wrong though)
The problem is always the eco system - what else do you buy a smart phone
for.
This was another argument for the licensed Sailfish OS - via Dalvik I can
still run some Android apps.
Of course if you don't need such, this argument is not important, but why
would you need a smart phone then.
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
31 Aug
31 Aug
8:57 a.m.
New subject: fetching photos from android phone
On Sunday 30 August 2020, Felix Miata wrote:
Does TDE have an app made for this purpose? If yes,
what's it called. If
not, suggest something please.
There's gmtp
Works well for me.
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
1571
days inactive
1574
days old
42 comments
18 participants
participants (18)
-
BorgLabs - Kate Draven -
deloptes -
deloptes
-
Dr. Nikolaus Klepp
-
Felix Miata -
Felmon Davis
-
greg
-
J Leslie Turriff -
J Leslie Turriff
-
Marvin Jones via trinity-users
-
Marvin Jones via trinity-users -
Michael -
Michael
-
Mike Bird -
Slávek Banko -
Thierry de Coulon
-
William Morder via trinity-users
-
William Morder via trinity-users