Your data. Your choice.

If you select «Essential cookies only», we’ll use cookies and similar technologies to collect information about your device and how you use our website. We need this information to allow you to log in securely and use basic functions such as the shopping cart.

By accepting all cookies, you’re allowing us to use this data to show you personalised offers, improve our website, and display targeted adverts on our website and on other websites or apps. Some data may also be shared with third parties and advertising partners as part of this process.

Fairphone 3+ (64 GB, Black, 5.65", Dual SIM + SD, 4G)

Fairphone 3+

64 GB, Black, 5.65", Dual SIM + SD, 4G


Question about Fairphone 3+

avatar
thisisturus

4 years ago

My Fairphone has started having issues with receiving and making calls shortly after I bought it. I contacted Fairphone, who told me that they have received several similar customer complaints about this issue, and are still investigating the matter. I tried to do what they suggested, such as rebooting, switching sim cards, using different networks, ... but to no avail. Has anyone else had the same issue, and has anyone managed to resolve it?

Avatar
avatar
geosound

4 years ago

I bought a similar device in Zurich-Digitech and works perfectly since day 1. I was having a version 2 and reloading all apps took less than few hours. One thing that may be relevant is that there is a new Fairphone3+ update available that I did not install so far, for lack of time. Maybe you did install the update after basic install and this may be the root cause of the problem?

avatar
chiara.griffoni

4 years ago

Hi, I had the same problem at the beginning and by looking at the Fairphone community forum it happened to many other people as well. As for every other software-related problem, the only solution is to notify the producer about the bug and they will update the specifics in the next software update. In my case, this was solved already after a couple of weeks, so you will most likely get it solved with the next update too.