Software Update: 3.A.0129.20210805 (unknown caller and zero brightness bugs)

True the update only effects Fairphone as it’s a Fairphone update.

The issue is that the caller ID issue, especially can be found elsewhere

It just seems to happen more frequently with Vodafone. i.e.

  • the info Fairphone have for interpreting carrier IDs comes from Vodafone in this case and the info is incorrect.
  • The update is rolled out to Vodaphoen for checks before it is released and presumably Vodafone was happy with it.
  • The update is not rolled out to each carrier that uses Vodafone, so there is only a problem with certain carriers, in individual countries.

Again, got it. And there I thought that at my workplace we actually extensively tested software before release. This must mean that our software is Very Simple. Clearly, there is no way somebody at Fairphone could have actually tried automatic brightness under different lighting conditions after changing the minimum brightness. That would have been far too complex.

I’m done with this. Bye.

1 Like

No doubt that could have been a possibility and maybe they did a poor job if they did. No one is saying that they don’t hold Fairphone responsible, but rather it’s not that simple to fix given it accompanied a security update.

Sure, the car’s engine exploded. But that isn’t the manufacturer’s fault because there is this other car by a different company whose engine also exploded.

I’m really done now, don’t bother responding. This is a colossal waste of time. I’ve turned off notifications and don’t plan on coming back here.


Then why not change exactly that piece of code back to befor the Update. Build, package it and ship it as a hotfix? That buyes you time to do a propper fix and angry customers do not rant in the forum…

It is possible that vodafone does not know shit. They do not exactly manufacture phones themselfes or build operarating systems. (VF-bloatware does not count as software)


I imagine Fairphone were not aware of it. I don’t expect Fairphone to try a SIM card from every possible carrier. I would hope Vodafone would do that.

If it’s too much to ask Vodaphone to test their carriers then it seems beyond reason to expect Fariphone to do so. I don’t imagine that Fairphone even know of all the carriers and one may be created as we chat.

The carrier info is down to Vodafone.

I proposed exactly the same a long time ago.

The processing of the carrier info is down to Fairphone. And it worked fine before the latest update…


I just don’t understand the agressive wording and tone in this thread.

To be clear: Fairphone messed up with the last update. In the last answer to my private support request (September 27th), Fairphone stated:

Fairphone is aware of the problem and has promised a fix with the next update. I see no reason in discussion any other possible faults, e.g. Vodafone Germany.

The only question remaining is the date, when the next update will be rolled out.


@LordNerevar I agree with your view but then I don’t have the problem with the caller ID so I am not much put out by the brighteness.

Others are very upset and find this a place to vent.

@DeepSea >The processing of the carrier info is down to Fairphone.

Yes but if the info is incomplete Fairphone can’t do much.

When I first got my FP3 the carrier/network name was T-Mobile.
T-Mobile run the network that EE were running on in the UK. It was a little disturbing when I saw it as I was expecting to see EE

It wasn’t a caller ID issue just a carrier name one. The info being sent by the carrier was incorrect. Luckily it was not impacting the use of the phone and was resolved quicker than this caller ID issue.

However I note it has happened with Vodafone more than once on Fairphone and on other carriers of theirs.

I imagine if there was a quick and easy fix it would have been pushed out within a week. Clearly it’s not as simple for Fairphone to do, as those with the problem would wish.

Again: It worked before the latest update.

So you have deep insights in their software development, or is that a vague speculation?

I note from the preceding response there is still this idea that the poster is very upset with what they perceive as a failure on the part of Fairphone to live up to the author’s expectation…

Such repetitive complaints about how Fairphone have managed, or failed to have managed the author’s expectations, especially if they have the caller ID issue.

That however does not relate to the actual issues that were acquired by some after the update.

Responding to such complainants can be demanding and they can appear like trolls, I think the expression is, but they are ‘human’ and want acknowledgement of their pain and suffering.

To those people I am sure Fairphone have some idea, maybe not much but I don’t see how the criticism of Fairphone is going to help resolve the problem.

There could be a post dedicated to Upset about Fairphone’s handling of Update issues.

OK I’ll make one :slight_smile:

1 Like

Well then… Senpai of the forum… tell us your wisdom? What exactly changed in vodafones carrier info?? I put my sim in my wifes new FP3. Fresh out of the box, vanilla from the factory. No updates are made. I put it in 4G and let my wife call me. Suprise… the number showd up. As expected! Put my sim back in my up-to-date 4G FP3… Unknown caller…

You know what changed on vodafones side? Absolutly nothing.

1 Like

Nothing has to change, it may just not be compatible with the update.

I’m sure I read somewhere that Fairphone and Vodafone have looked into this and the issue resolved.

Anyway when posts are more about abilities of Fairphone or their lack of there is this.

Probably you mean this post:


I can’t find the post/topic I am thinking of, but here’s an example of an earlier problem with Vodafone.

I tried to help but when people just refuse every solution then there is no way to help them. That’s why I don’t understand what they keep writing the same post again and again asking people who don’t work at Fairphone to hurry up to fix the problem.

1 Like

You will never get a Fairphone since it will never be as powerful as you want. Just go for a pixel, it is a good phone for you.


(post deleted by author)

1 Like

what’s the point?

3G was disabled this year in Germany by all 3 providers (T-Mobile, Telefonica, Vodafone). This means concerning the combination FP3/Germany/Vodafone the following. You can either disable 4G/LTE and know who is calling, but at the same time crippling your mobile date transfer to 2G/EDGE… or you can use 4G/LTE but you can’t see who is calling. If you miss a call, you can’t answer.

And this situation hasn’t changed for nearly 2 months. This is not a question of a fast mobile phone for mobile multimedia / gaming / whatever. This bug simply broke the most basic function of a mobile PHONE for users of Vodafone in Germany. At least, Fairphone could show up in this thread and announce a planned release date for the f***ing patch to fix the mess they made.

Of course, we could buy a second SIM for mobile data and leave the Vodafone SIM in 2G-mode… if FP would pay for it :wink:

If FP doesn’t fix this sh** soon, this will be the first and last Fairphone I ever owned.


I 100% agree. I do really love the whole concept of fairphone and I was always proud to own one. But I never expected the fairphone team to fail in such a massive way as they do with the unknown-caller-id. If I would use my fairphone for business they would have already lost me as a customer forever. But even with private-use only I am extremely annoyed by now. I have to apologize to friends and relatives on a daily basis for not getting back to them. this simply can´t go on. Either you fix this really soon or I will never buy another fairphone ever.