I am having issues with android-file-transfer on Arch Linux with my Pixel 7. Some weeks ago it was still working fine without problems but now I cannot seem to make the connection between my laptop and my phone via USB to transfer files. I have the USB-C port setting set to "Charging-only when locked" and take the following steps to connect,

  1. Make sure screen is unlocked
  2. Connect phone to laptop via USB
  3. In USB pop-up settings change to "File Transfer" mode.
  4. Run aft-mtp-mount ~/mnt

This approach used to work fine until now. I've also tried using mtpfs which is based on libmtp but that hangs for a long time and after it exits I cannot access the mount folder with error message ls: cannot access 'mnt': Transport endpoint is not connected. For aft-mtp-mount I am getting the same errors as the person in this recent GitHub issue https://github.com/whoozle/android-file-transfer-linux/issues/347 .

Some version info:
Build number: 2025030900
android-file-transfer: 4.3
android-udev: 20250314
android-tools: 35.0.2
libmtp: 1.1.22

Has anyone experienced similar issues connecting to (Arch) Linux via USB on a recent GrapheneOS release? Or does anyone have any ideas how to debug this?

I am also on Arch Linux with a recent GrapheneOS install on a Pixel 9 Pro XL. I have also tried both aft-mtp-mount and mtpfs and get the same results as you describe, as well as those in the linked github issue. I am just trying this since yesterday, so have not ever seen it working. Unfortunately I don't have any further info regarding what's wrong or how to resolve it.

GrapheneOS build number: 2025031400
android-file-transfer: 4.3
android-udev: 20250314
android-tools: 35.0.2
libmtp: 1.1.22

Just for reference, gvfs-backends (libmtp9 version 1.1.20) works fine for MTP between up-to-date GrapheneOS phone and QubesOS with Debian based template. Either version 1.1.22 broke something, or it is specifically GVFS that is still working, or it is Arch specific issue for some reason.

16 days later