Connect to Droid (file-manager is PCManFM)

When I plug a USB adapter from my Droid to a Windows machine I am easily allowed to access it’s stored memory.
Why not in Fedora?
What do I need be able to do this?

  Hi.  Try to scan through bookmarks on the left side of File Manager app.

  Else post the following:

  Fedora
  What is the edition (Workstation, Server, ...)?
  What is the release (29, 30, 31, ...)?
  What DE is used (an WM, Gnome, KDE, ...)?

  Device
  What Android release it is (5, 6, 7, 8, 9, ...)?

Thanks, it’s Fedora 29 running LXDE
uname -a
Linux localhost.localdomain 5.3.11-100.fc29.x86_64 #1 SMP Tue Nov 12 20:41:25 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Android 8.1.0
Phone: TCL- A501DL from Tracfone

There was nothing on the left of the PCmanFM like a flash drive would show.
Saw nothing in /run/media// either.
I remember getting this to work a few versions ago but it was not exactly simple. I had expected to see a thread on it here but nothing showed up.

  Is gvfs installed?  Is the connection on Droid side set to "Media Transfer" or such (i'm not sure, maybe it was negotiated automatically before)?
  PS:  Also you may wish to install an another file manager:  
nautilus, or dolphin; both should work.  Amusement:  Also device's storage can be accessed through terminal (Arch Wiki, MTP).

  BTW, aren't LXDE is abandoned (more or less) in favor to LXQt?  The Fedora LXQt Desktop page.

Well some success. Yes gvfs was always there and showed up in mount (see below). Reading through the Archlinux page above prompted me to do:

dnf -C search mtp

which turned up:

gvfs-mtp.x86_64 : MTP support for gvfs
kio_mtp.x86_64 : An MTP KIO slave for KDE
simple-mtpfs.x86_64 : Fuse-based MTP driver
libmtp-devel.i686 : Development files for libmtp
libmtp-devel.x86_64 : Development files for libmtp
libmtp.x86_64 : A software library for MTP media players
libmtp.i686 : A software library for MTP media players
libmtp.x86_64 : A software library for MTP media players
jmtpfs.x86_64 : FUSE and libmtp based filesystem for accessing MTP devices
android-file-transfer.x86_64 : Reliable Android MTP client with minimalist UI

I figured installing android-file-transfer would include any needed libs:

sudo dnf install android-file-transfer.x86_64
================================================================================
 Package                 Arch     Version                       Repo       Size
================================================================================
Installing:
 android-file-transfer   x86_64   3.4-1.fc29                    fedora    423 k
Installing dependencies:
 qt                      x86_64   1:4.8.7-45.fc29               updates   4.6 M
 qt-common               noarch   1:4.8.7-45.fc29               updates   7.2 k
 qt-x11                  x86_64   1:4.8.7-45.fc29               updates    12 M
 dbusmenu-qt             x86_64   0.9.3-0.18.20150604.fc29      fedora     90 k
Installing weak dependencies:
 sni-qt                  x86_64   0.2.6-12.fc29                 fedora     60 k

Transaction Summary
================================================================================
Install  6 Packages

Total download size: 18 M
Installed size: 58 M

Well NOW I see
LXDE Menu > Accessories > “Android File Transfer (MTP)”

If I press it with no driod plugged I get nothing.
If I plug the droid a neat little file transfer gui appears and is usable.
If I do have not signed into the droid screen I get a “locked” msg with a retry button waiting for me to unlock droid and retry! cool.

So with that install I saw no libraries being added just qt stuff.
I still see nothing in PCmanFM.
I see no change in the “mount” output at phone plug in.
But chasing down this line

gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)

I see nothing show up at /run/user/1000/gvfs as phone is plugged in. This is (I think) where I used to be able to access the phone a couple of years ago and at times be able to navigate there via the file manager. I don’t see where this is happening now.

Oh well, it’s usable now and that’s what counts!

1 Like