Fairphone 3 use with Ford SYNC 3

My wife has just recently bought an FP3.
Having seen it I am rather keen to buy one too however I tried to connect via Bluetooth to our car’s audio/nav system (Ford SYNC 3). It pairs with the phone but then immediately asks to pair again. The car’s system gives the message that the Fairphone 3 has no SYNC operability.
This is a great pity because I want to be able to connect to the car’s system so that I can call handsfree, use Android Auto (incl Waze) and stream music.
Is there a workaround for this?


There is already a topic in German about the issue: 🇩🇪 FP3 bluetooth problem with Ford SYNC3

Up till now there doesn’t seem to be a solution. But somebody mentioned that also newer Samsung models are affected (https://us.community.samsung.com/t5/Galaxy-S10/Connection-problems-with-ford-sync-3/td-p/777248).

So maybe it’s best to contact Ford and ask them to provide an update/solution.


I have the same problem.
The exact error message I get is: “Fairphone 3 does not offer any SYNC-compatible features.”

I have contacted Ford Netherlands by e-mail and did not get a response. A week later I have called them. The person was nice but did not provide a solution. She promised to report the problem to higher up. So I suggest that everyone who has this problem reports it to Ford, to make sure it will be noticed and hopefully fixed.

Also, I was wondering whether it’s possible to change the Bluetooth address (MAC) of the phone so I can test whether Fairphones are blacklisted (or not whitelisted) in Ford SYNC3.

1 Like

I have contacted Fairphone and they are aware of this problem. According to them it’s on Fairphone’s side and they are working on a solution.



Does anyone tried to pair their device plugged on a lighter or on a powerbank?

I’m believing the issue comes from the battery saver which is really efficient and could create this inconvenience.

1 Like

I hope this solution will also fix the pairing issue between Fairphone 3 and Toyota Corolla 2019 (Toyota Touch) - wondering if the fix would include adding more bluetooth profiles?

In my case, as far as I can tell, the “battery saver” functionality was not active when I tried - multiple times - to connect to the Toyota Touch 2 Bluetooth system.

It might as well be another Android 9 issue: https://www.bestusefultips.com/fix-bluetooth-issues-after-android-9-pie-update/
The post is not the most helpful, but it does point out that there are more devices out there having this issue than only FairPhone.
Another thread which describes my same problem: https://forum.xda-developers.com/showthread.php?t=2516763 - from six years ago…

Johan, would you kindly take on your time and try to pair with device plugged on power source?

Thanks to provide us with the results :wink:


I reconnected the Fairphone 3 with the “Toyota Touch 2 Go” (2019) car system while keeping the phone connected to the USB port and I’m happy to be able to share that it all worked. Connected as audio and also connected as phone! However syncing my 400 contacts over Bluetooth didn’t seem to succeed. But that’s a different problem. There is an USB sync option, but I didn’t have an USB cable which also transfers data. So for me this issue is resolved. Thank you @GamTrad for urging me to try with the phone in “charging” state.


Your welcome,

I insisted also on the matter via Twitter ^^’ so I’m happy to see that you can use your device.


If the problem is to do with battery saver mode, shouldn’t you be able to overrule that as a user? I haven’t had any problems with the Garmin system in my VW Up! but since I mostly use it for music I have a habit of connecting my phone to a power source whenever I use it in my car, so maybe I got lucky :stuck_out_tongue:

Same here. Ford Tourneo. It dosnt work even if i Plug it in.

However btw, Android Auto Works. I have to click away about 3 “Bluethooth Warning” messages (YES, i’m aware Bluethooth dosn’t work! Would i plug it in otherwise?), because Android auto automatically activates Bluethooth and tries to connect. How ever, if you have enough nervers to click it away (every thime) it works, inclusive Audio over plugged cable.
(Requires a Built in USB Plug obviously)

by the way, by tipping i consider… the Adapter i tried is most probably not QuickCharge enabled - its older. Is quick charge required to disable battery saver?
Fairfphone (or Ford) - please fix that.

1 Like

Unfortunatly even with my FP 3 charing at Toyotas USB or external Power Source, it won’t connect for audio or phone usage. Toyota Touch answers that the phone is not supported. Any more advises?

Unfortunately, I just joined the group of people with a new FP3 unable to connect with Ford Sync3. No news on the topic since last month, I presume?
Thanks for sharing…
I tried to connect bluethooth, while connected to usb power outlet (cigarette lighter). Same error as the other persons in this feed.

Hi and welcome to the forum.

Sorry, no news so far - but I guess you can contact Fairphone support to bring the topice back to their attention.

I had the same issue with a Focus and a Kuga, fortunately these have been only rented cars for a business trip. With a Volkswagen SUV I had no problem with the connectivity. With my own car with Ford Sync 1 also no problem. I hope they solve the problem, but I don’t know how much they depend on Ford here.

1 Like

Probably not a “workaround” for everyone but I think still worth mentioning it:
In a German topic about the same problem it came up that if /e/ os is installed on the FP3 then Bluetooth and Ford Sync3 seems to work.


Here’s the english-spoken thread reagarding the connectivity problem.
As it seems, this problem is one of the FP-OS, it might be solved by Fairphone in a future update.
The tricky part might be to find out, what it is, that makes /e/ work.

1 Like

I noticed the security patch lvl was different. FP-OS April20 and /e/ Mai20. All other settings I could see as user seemed to be the same. We even tried to switch the bluetooth AVRCP-Version (FP-OS = 1.6 /e/ = 1.4), but it did not help.

As you can see in the German thread for this problem, FP is now at least aware and @formerFP.Com.Manager is looking into it.
Possibly they are able to find out more.