My FP4 arrived 2 days ago. Everything works smoothly, but the USB connection to my Win 10 PC operates extremely slowly. I can see the Phone in Win Explorer, can open folders withput problems. Right after I plug it in, I can also move files, but not for very long.
After that initial period, i can’t even move very small (e.g. 30 kb) files or view pictures.
Thing I have tried but didnt work:
use another USB cable
use different USB port (including USB-C)
uninstalling and reinstalling the FP from the Windows device manager
it gets unbearably slow, but the phone never disconnects. The Win explorer does seem to be affected by it too, I had it nearly crash a couple of times
i tried to use the SD card as internal storage, so the PC didnt distinguish between the memory of the phone and the SD card (no separate folders). But i just physically remoced the card and there was no change
the SD card worked just fine in my last phone too, up until a few das ago. so I think we can rule it out as the source of the problem
Ok, so at least the SD card doesn’t get unmounted suddenly. I can’t help you with the explorer behaviour, somebody who’s running Windows will have to answer that.
I would strongly advise against formatting the SD card as internal storage, the risks far outweigh the benefits. Have a look at the SD card guide for FP3/FP4.
I wouldn’t rule it out as a potential problem, the FP4 is a bit picky regarding microSD cards, especially if they are made by SanDisk. There’s a long thread about it here and a ✏ List of compatible micro SD / SDXC cards for FP4
Maybe try formatting the card as external storage and see if the transfer problems persist when writing directly to it. If you have other microSDs lying around, it would be also very interesting to know if they exhibit the same problem
I completely agree with you, there is something seriously wrong with the FP4s MTP stack (there are some other, smaller problems as well).
A folder with ~17,000 pictures / 23.5 GB reaches 1% / 25 files copied after a few minutes, then the process just hangs there for a while before throwing an error and continuing. That’s with the official USB-C 3.2 Long Life Cable plugged in the USB 3 port of a Linux PC.
Meanwhile I can adb push that same folder with the same cable in just under 10 minutes, no issue whatsoever…
Same thing with a bunch of .flac files, videos, anything really.
I have long given up on using the MTP connection to transfer files to the FP4, just too unreliable.
Those only throw an error for me (on Linux / KDE Plasma), but don’t crash the transfer.
I’ve got ID 18d1:4ee2 Google Inc. Nexus/Pixel Device (MTP + debug), so at least they apparently used different IDs for the different models (or maybe that’s just with adb enabled)
I have no idea how this works, but they somehow released the FP1 under a HTC vendor ID (0bb4:0c03), the FP2 under their own (2ae5) and Qualcomm’s (05c6:90dc).
Didn’t find any specific mention for the FP3 or FP4 in any of the USB ID databases, the Google one does contain a few random non Google devices (18d1)
You might have to ask support if they can explain that. But I wouldn’t count on an answer anytime soon, that probably has to be relayed to the dev team and that takes forever…
