Hi @fpdream Welcome to the forum.
RE Your comment. The developer who worked on the procedure may well be the most enlightened on the issue but many other people with a decent software ability and time on their hands may be able to understand.
But it may not be that simple even for the developer of the procedure to work it out.
Hopefully it is just a learning issue and will all be fine in a few days.
Thanks for your input.
I look forward to an official answer. For me it’s a software bug.
I’m checking the Ambient light sensor
a) it is reading zero when I can still read without a light
b) the lowest setting I have is ignored and the screen is darker than the piece of paper next to it.
Will try and set the value via the slider, again. Ok I have set it at 41% will see what happens. 
@aboloo I have the same issue with the brightness.
Yeah, I also want to +1 this. I have the same issue since the last update.
When ambient light is low, screen brightness used to reduce, now it immediately goes to lowest setting.
This happens already in a lit room. It makes the screen barely readable.
Just to add It seems to occur each morning and each evening. When the ambient light goes beyond a certain level (and inappropriately reads zero) the screen light drops to zero.
Although this has occurred since the latest update it is a clear single issue and am starting a new topic.
Got the update Sunday in the US on T-Mobile. Things seem to be working out pretty good!
Hi @formerFP.Com.Manager Just to ensure you have read the reports of the problems with the ambient light sensor not working well with the auto brightness feature I have made anew topic to collect user experiences of that as a single issue.
No update available with Sosh in France yet…
Hi everyone,
Thanks for flagging and for sharing your experiences here. Our team is currently looking into this and will provide an update as soon as possible. In the meantime though, you are able to turn this feature off by following these steps: Settings > Display > Adaptive brightness > Off
Thanks also to @anon9989719 for creating a new topic. I will share this internally too. 
Since this update, all incoming calls are displayed as “unknown”. I know there has been the same issue about one year ago, I did not have problems with that until now. When I disable 4G the caller’s names are displayed. Anybody experiencing the same issue? (Edit: using Vodafone in Germany)
It might be related to VoLTE. Which provider do you use? (Edit: Ah, got it, thanks!)
Yes, I think so. Unfortunately I don’t have (or don’t know of) an option to disable VoLTE, I just have the option to disable 4G, which is not an option for me as 3G is no longer available in Germany.
Read form other users with Vodafone the same, so would advise to contact support about this.
Contacting Vodafone support is the way to go. A workaround is to disable “Enhanced 4G LTE Services”, but please try Vodafone support first…
I will, thanks. I just don’t really understand why it should be their “problem”, as everything worked fine before the update.
It seems that you did not use VoLTE before and it might have been enabled on your phone while the latest update was applied to it.
I’m on Vodafone Germany as well and I’m 100% sure I had VoLTE enabled before the update too. But the “unknown number” problem (re-)appeared only after the update.
Then please call Vodafone support first, maybe their central FP3(+) profile needs to be reconfigured/-initialized…
In my experience talking to Vodafone about Fairphone issues has a 0% success rate. You basically never even find somebody who understands what you’re talking about. FP has to sort this out with them.
@formerFP.Com.Manager, would you be so kind and also notify the developers that at least for Vodafone Germany, this update re-introduces an old bug that causes all callers to be displayed as “unknown number”? Thanks.