Martas explanation is better late than never …I suppose? Thanks to the dedicated angels, people with knowledge, and others already burned by this “upgrade” we kind of knew already though.
I’m pleased that the rollout of A13 has been paused. I’m in total agreement with Soupape50 in this now closed thread . I think the OTA update should be halted permanently, well unless a solution is offered (seems unlikely). If members of the commune want Droid13 knowing the side effects, then let them download it manually. As this removes phone functionality it certainly should not be pushed.
I will continue using A11 until the time comes when the various apps I use stop supporting it. A11 is supported by Google until the end of this year I believe? How about Fairphone supporting A11 until its end of life date?
If the problem is the sensor, I will happily pay (a fair price) to upgrade it to a new module, I’d even put a deposit down. Perhaps FP should poll to see how much interest there is in this option? Solution may not be as simple as replacing the sensor though. I hope @Roli gets a reply from Fairphone on this issue.
Beta testing : What is the point of beta testing if after a set period of time, FP roll out that release regardless of negative reports by their testers?? Does FP understand that the principle of beta testing is to iron out bugs before a major release? Companies often release several beta versions before settling on a stable one. Question for beta testers. Have you ever reported a serious flaw, and if so, did Fairphone rectify the issue before general release?
I’d rather not use a custom ROM. I’m just not that confident I wouldn’t do permanent damage, maybe kill my phone entirely. However, if FP don’t come up with any sensible solution before my favourite apps stop supporting A11, I think I may investigate Lineage. Thanks very much to @yvmuell for posting the link.