I don’t use a FP4, but I do, with my FP3 running the latest FPOS, observe the following.
If I boot my PC (Windows 10 [10.0.19043.1766]) and my FP3 and then connect the latter by a certified USB cable I obtain a viable USB File transfer connection (or other protocol).
If however I then disconnect the FP3 after first using the Windows “Safely Remove Hardware and Eject Media” function, when I later reconnect the phone, Windows fails to recognize it. I also notice that after “ejecting”, the “USB key” icon remains (uselessly) in the tray.
If I just unplug the cable without the proper preparatory Ejection then the icon disappears as it should, and I can later reconnect and the phone is recognized.
[Edit - but even that only happens if, on the phone, I go to Settings > Connected devices > USB. I don’t have to change anything, just open the settings. It’s as though this initiates a handshake.]
So there’s definitely a bug somewhere and to my mind it looks like it might be more on the Windows side than the phone’s. In view of the necessity of opening the Settings on the phone, maybe they are both at fault in different ways! There is of course no evidence that this is the same problem experienced with FP4 but it’s suspiciously similar.
For those who are encountering the FP4 problem, you might try going to
Settings > Connected devices > USB
and try different combinations, notably for “USB controlled by”. Mine is set to “This device”.
Two more ideas:
-Enable USB debugging mode after entering developer mode.
-Review the access, read and write permissions that Android 11 may ask you for. It is one of the biggest drawbacks I have had jumping from version 6 to version 11.
Hello,
it must work on my computer and in the car. I do not have Linux at the moment and do not know if Ford SYNC runs on Linux base. We have Samsung, Huawei, Sony in the family/friends, everything works, only my FP4 does not connect.
Was simply intended as a fundamental question to double check it.
Whether the device is recognized under Linux or whether it doesn’t work with it and is therefore a fundamental problem
Don’t want to force Linux on you.
Hello,
Linux is fine, but I do not have Linux to test … I tested the cables and … It’s a question of how I want to spend my lifetime. It took too long already (April 18, 2022 the error appeared on my first FP4).
That happens when the phone doesn’t see that it’s connected over a cable valid for data. If we list some of the possibilities:
cable: you’ve tested several
bottom module: you’ve replaced it, twice in effect
some other hw component of the phone (which …?, how?)
phone software: you’ve done a reset
PC and Car hardware or software: unlikely, since neither work.
Above all, why did it work to begin with and then stop working, in both cases (original and replacement device)? The fact that two devices experienced the same symptoms leads me to suspect that there’s something in your local environment (in a very broad sense, including devices, software (including possible malware?), habits or ways you may have of going about things). I’m not criticizing anything here, just trying to reason.
Do you think there was anything in common in the events leading to both phones ceasing to connect over USB? Difficult I know
Are you using any specific security software that might be disabling USB data?
The fact that two FP4 devices have experienced the same symptoms, all cables are tested and work with all other Android devices, makes me suspect that there is something wrong with the FP4. I have been using Android devices for many years since the first Galaxy and have not changed my behavior. All devices worked for many years until they were too old. My S7 is now 6 years old and running (slowly).
Maybe they will find the error when I send it back. Unfortunately there was no feedback or repair report the first time either.
Quite possibly, but in that case why were they working to begin with, and why did they suddenly stop? That’s what we need to find out. Not easy unfortunately!
Yes I’ve been thinking that, too. A wrong voltage that some devices might survive easier than others, such as might come from a misplaced contact in a USB socket?
Then why do all other devices still work, charged with the same cables and chargers
I think there is no point in guessing, there is a fault and it is either a weakness in the design or something else, a good repair shop should be able to figure that out.
I’m curious how it goes on and activate my old phone for now.
my question, if someone knows the problem with the USB data connection and has a solution, has now been answered sufficiently. Apparently this error is rare or not present and I just had bad luck. Since all tested devices and cables are OK - also suitable for data transfer - I will have the Fairphone checked and then report the result in here.
Thanks for your support and your ideas on this subject
So what was the final solution to your problem? I’m facing the same issue here. Cables that used to work don’t anymore. It’s not working on neither Windows nor Linux. USB-C to USB-C is working, but I don’t have that interface on the computer I want to use it on …
and have not changed my behavior. All devices worked for many years until they were too old. My S7 is now 6 years old and running (slowly).