Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #177308

Re: Android phone access in Dolphin does not work

Show all headers | View raw

On 01/26/2017 11:42 PM, Gary Dale wrote:
> On 25/01/17 01:27 PM, Tony Baldwin wrote:
>>
>>
>> On 01/25/2017 12:58 PM, ken wrote:
>>> On 01/24/2017 02:38 PM, Gary Dale wrote:
>>>> 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
>>>
>>> It sounds like you want to offload files from your android. For a few
>>> years now I've been using Software Data Cable to do this, free app, no
>>> cable needed.  Launch the app and it sets up an ftp server on the
>>> phone.  Then from my laptop I log in, navigate, up- and download files.
>>> When done, I shut down the ftp server on the phone. Easy-squeezy.
>>>
>>
>>
>> Just in case the above doesn't work out for you (and I'm going to 
>> look into that one, myself), because,  in my experience, this 
>> disaster called MTP is simply a headache...
>> I'm going to suggest what I do to access storage on my Motorola Droid 
>> II.
>> Install Dropbox.
>> Alternatively, if you have access to any remote server running an 
>> ftpd, AndFTP is an option. I've done both, and currently find the 
>> dropbox most convenient.
>>
>> Tony
>
> I'm going to hazard a guess that this problem is Linux specific since 
> the hordes of Android users would rebel if this was happening on 
> Windows. However I can't understand why it should be such an issue 
> since the MTP is an open specification that has been around since 2008 
> and Google is heavily involved with it.
>
> The Dropbox idea sounds reasonable if I don't mind putting massive 
> amounts of data onto the Internet. I think I'll try the software data 
> cable instead.
>
> Thanks.
>
Just a quick tip for using Software Data Cable:  When you fire it up on 
your android, you'll get a screen helpfully telling you the ftp command 
to run on the other end... but the command they give isn't right... 
well, maybe it is for Windows, I don't know. What's worked on Linux for 
me dozens of times is this:

$ ftp [phone's IP address] [port number]

Software Data Cable uses a non-standard port for its ftp service... a 
good thing, since ftp isn't the most secure protocol in town.  Note that 
there's a space between the ip and port#... also the first arg is just 
numbers.

I wish there was an ssh-based app for android... I've looked for such, 
haven't found it.  Is that a Windows thing?

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

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