Fairphone and Vodafone Germany (the only provider affected as far as we know) are working on a fix.
A factory reset will not help you. An Android “factory reset” will only delete your user data and the Apps you installed and their data. It will not roll back the OS to a prior version, in fact it will not touch the OS at all.
Thanks once again for flagging these issues. Our technical team has been investigating both the adaptive brightness, and the unknown caller ID issue in Germany, and have found the root causes for both. We’re currently working hard to implement these fixes as soon as possible.
Fixes for both of these will come in the next software update. In the software update after that one, we aim to re-introduce the improvement for display lighting so that it works as we envisioned.
Our sincere apologies to all those who have been affected, and thank you very much for your patience and feedback so far.
Adaptive brightness seems to be malfunctioning after this update. In the evening, it goes to zero, making it unreadable (too dark). Sometimes in the daytime, it drops brightness to zero but quickly goes back.
So does this mean the automatic brightness changes from the most recent update will be fully reversed (i.e. lowest brightness will be back to quite bright?) in a first step before a second attempt at fixing lowest brightness will be made in the later one?
@urs_lesse Regarding the adaptive brightness issue, in the upcoming software update we’ll reverse the recent changes made. We’ll then re-introduce this feature again in the update after that one.
Are there plans to prevent or limit these things for the future? For example by having a beta tester community? Or use a slower deployment of updates so that only a subset will get a buggy update. Then things like this brightness bug could be reverted before released to everyone. You can then find a solution without too many upset customers and then release a patched version when it’s ready. I think this would definitely be worth looking into. The least bugs you have, the happier people will be with their phones and the longer they’ll use them.
These updates are staged rollouts (not all of the users will receive it immediatly at the same time); it takes some days until all the devices got the update.
So there is plenty of time to stop the rollout as soon as the first users contact the support with problems. So the software can be fixed and the rollout can be restarted again with the fix.
Some weeks ago I was asking about if the rollout was stopped and if, when it was stopped and how many people received the buggy update. There was no answer, so I assume that it was not stopped at all (just a guess).
Sounds like disabling adaptive brightness and just swiping the brightness up and down a little here and there manually like in good old times would be the better plan then until the coming update. No need to fight .
Thanks! Unfortunately I don’t understand how the automatic brightness setting works with the brightness slider . Today I accidentally moved it back all way in bright sunlight. I had to remove and replace the battery ( luckily one can do that with a FP:wink:) to get a workable situation. Is this by design?
Not sure if I understand correctly what you don’t understand – but automatic brightness can be disabled in Settings (on FP2 the relevant category is called Display).
To force a restart, holding down the power button for 10 seconds or so should also do the trick.
I have the same problems with my FFP3 and hope they will be solved soon. As mentioned earlier in this chat, it is not possible to use the phone on business when the calling number is not shown.
In such a situation it may be worthwhile buying a monthly Pay As You Go SIM on a network that doesn’t have this problem, and the phone does have two SIM slots
This has been going on for a while now and is not the first time.
Hopefully an update will be available within a few days