Unable to connect to Linux PC via cable (MTP)

Using /e/OS User Queries
1

Hello everyone!

I’m using /e/OS on FP6, and I’m having issues connecting it to my Linux PC via the USB Type-C cable. I’ve made sure I selected the “File Transfer” option, but it doesn’t show up in my File Manager. I tried to check with lsusb, and I was able to get an entry for it: Bus 001 Device 092: ID 18d1:4ee1 Google Inc. Nexus/Pixel Device (MTP)

I then went ahead to make sure that it’s detected as an MTP device, but it’s not detected:

$ mtp-detect
libmtp version: 1.1.23

Listing raw device(s)
No raw devices found.

Any idea what could be the issue, or what could I look into?

I have another Android phone, and it connects fine with that, using the same cable.

1 Like
2

did you also tried using a classic USB-A <—> USB-C cable ?

2 Likes
3

Thanks for the answer. I think I failed to mention that what I used was an USB type A to USB type C cable.

4

Don’t expect that you can mount an ordinary partition containing a file system via USB - Android doesn’t allow this. With my two Blackberries I could mount without any problem, with an Android phone I never could. Also on Windows you don’t get an ordinary drive with a letter, the Explorer shows your device outside the ordinary list of drives and there will also be no option to remove the hardware safely. An Android device is special.

What you can do is: use a Linux software like android-file-transfer (try to find a package with this name). This allows copying and moving files and directories in both directions controlled by a simple small GUI on the Linux side.

Another option is to use (S)FTP or HTTP instead typically with the device as server and the PC as client. I prefer this because you don’t need a cable and it works also with a Windows PC.

Bluetooth on the other hand does actually not work anymore for file transfer with my FP3, but it did, I remember well.

2 Likes
5

Off-topic but interesting …
Initially, Android could do USB mass storage mode, but this was dropped relatively early (Android 4.something?) in favour of MTP and PTP. The best reasoning for this change I could find quickly is this … https://www.reddit.com/r/Android/comments/1aqjd0/comment/c8ztxs1/

1 Like
6

Using adb shell is an option for exploring the file system, and it can also be done via the installed recovery application (depending on the recovery: e.g. TWRP).

It’s weird that OP’s external and internal storage won’t mount on his Linux machine via USB, though. It works for me without any problem.

I really like that, too. I use Simple SSHD app, available from F-Droid.

1 Like
7

Ah, thanks for the suggestion. I use primitive FTPd for years, it always did the job. On the Linux side filezilla or gftp, also good: Double Commander with a plugin.

1 Like
8

Does anyone here have any suggestions on what I could do to work this out on the Linux side?

9

you might be missing some gvfs dependencies (gvfs-backends).
udev and plugdev user group assignment can play a role too.

If you want to go cable less, the linked threads also have recommendations.

10

I told you what you could easily do:

  • install a Linux package called android-file-transfer, this is not a big thing
  • use then a Linux executable called android-file-transfer to copy or move files and directories in both directions

I told you also what you could do not so easily (FTP, HTTP).

11

This topic was automatically closed after 30 days. New replies are no longer allowed.