Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #176985
| From | Gary Dale <garydale@torfree.net> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Android phone access in Dolphin does not work |
| Date | 2017-01-24 20:50 +0100 |
| Message-ID | <t3fgl-8pN-7@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
I'm running stretch/AMD64 and I'm having extreme problems accessing my Samsung S5 phone from my Plasma5 desktop. When I plug the phone in, I get the notification with 2 suggested actions. They both read "Open with File Manager" but the first one opens Dolphin with "camera:..." while the second opens Dolphin with "mtp:..." in the location bar. When I actually try to navigate to the folder with my photos, I get a notification on the phone telling me a device is attempting mtp access... When I click "Allow", I get another notification pop-up on my desktop with the same two options... When I actually try to access the photos, I frequently get "process died" or "I/O error" messages, although sometimes I can actually see a photo (not just the file names) - persistence pays off. Moreover the phone will lock when connected, even if a file transfer is underway. This kills the transfer. To make matters worse, I have photos and videos that I have taken which show up in the Gallery on the phone and which I can view on the phone and see when I remove the SD card and read it directly but which don't show up in Dolphin. Clearly this is not the way the process is supposed to work. I can understand the phone requesting a verification for the connection, but everything on the desktop side seems wrong: - the two actions should be distinguishable by their description, - the process shouldn't die and if it does, it should relaunch, - the connection should block the phone from locking if locking will stop file transfers, - there should be a record of the error in a log somewhere. As it is, all I can find is a lot of systemd journal entries like "Jan 24 14:01:33 transponder kernel: usb 4-5: usbfs: process 20598 (mtp.so) did not claim interface 0 before use" which seem to occur before the device is actually recognized. - all the photos should show up.
Back to linux.debian.user | Previous | Next — Next in thread | Find similar | Unroll thread
Android phone access in Dolphin does not work Gary Dale <garydale@torfree.net> - 2017-01-24 20:50 +0100
Re: Android phone access in Dolphin does not work ken <gebser@mousecar.com> - 2017-01-25 19:00 +0100
Re: Android phone access in Dolphin does not work Tony Baldwin <tonybaldwin@gmx.com> - 2017-01-25 19:30 +0100
Re: Android phone access in Dolphin does not work Gary Dale <garydale@torfree.net> - 2017-01-27 05:50 +0100
Re: Android phone access in Dolphin does not work deloptes <deloptes@gmail.com> - 2017-01-27 08:50 +0100
Re: Android phone access in Dolphin does not work ken <gebser@mousecar.com> - 2017-02-02 21:40 +0100
Re: Android phone access in Dolphin does not work Darac Marjal <mailinglist@darac.org.uk> - 2017-02-02 22:10 +0100
Re: Android phone access in Dolphin does not work RLewis <lewis.r0516@rogers.com> - 2017-01-28 17:40 +0100
Re: Android phone access in Dolphin does not work Gary Dale <garydale@torfree.net> - 2017-02-02 03:00 +0100
Re: Android phone access in Dolphin does not work RLewis <lewis.r0516@rogers.com> - 2017-02-02 14:10 +0100
Re: Android phone access in Dolphin does not work Gary Dale <garydale@torfree.net> - 2017-02-03 05:50 +0100
Re: Android phone access in Dolphin does not work RLewis <lewis.r0516@rogers.com> - 2017-02-03 23:00 +0100
Re: Android phone access in Dolphin does not work Gary Dale <garydale@torfree.net> - 2017-02-07 06:30 +0100
Re: Android phone access in Dolphin does not work RLewis <lewis.r0516@rogers.com> - 2017-02-08 04:20 +0100
csiph-web