Fairphone OS & Fairphone Open 21.12.0-rel.1 are now available. You can get them through the Updater.
Changelog
Issues fixed since the previous Android 9 release (21.10.0-rel.2).
Update to security patch level 2022-01-05
from the Android Security Bulletin—December 2021:
CVE-2021-0952, CVE-2021-0953, CVE-2021-0961, CVE-2021-0963,
CVE-2021-0964, CVE-2021-0965, CVE-2021-0967, CVE-2021-0968,
CVE-2021-0970, CVE-2021-0971, CVE-2021-30262
from the Android Security Bulletin—January 2022:
CVE-2020-0338, CVE-2021-0934, CVE-2021-39621, CVE-2021-39623,
CVE-2021-39626, CVE-2021-39627, CVE-2021-39629, CVE-2021-39634
Additional security fixes:
CVE-2021-39659
Please report any (new) issues through the public bugtracker and upvote existing issues if you are affected. As usual, please specify the steps to reproduce, and provide as many details as possible.
Not being shown to me in the Updater (in beta mode: “Your operating system is up-to-date”) so far, but this might be related to very odd battery behaviour – the charging level kept (actually still keeps) jumping between 10% – 2% – 50% – 1% – 50% within seconds (not sure if that’s about hardware or software). Will the update only show with battery level above 80% or so? Fairphone Open 21.12.0-rel.0.
We did not do a beta release for this update, instead it directly went public today. Beta mode in the Updater is currently in use for testing the Android 10 upgrade, so you will receive the update only if you are on e.g. 21.10.0-rel.2 with beta mode deactivated. You are already on Android 10 by the looks of it, so you will not receive this Android 9 update.
One of the security fixes is an interesting one where the Microsoft Teams app prevented some users from calling an emergency number. There’s an explanation in this Ars Technica article
Rahman says Google’s bug for this is CVE-2021-39659, which the monthly security bulletin categorizes as a high-severity “denial of service” vulnerability with patches for devices running Android 10, 11, and 12. In the Android codebase, Google is actually backporting this fix all the way to Android 8.0, which technically isn’t supported anymore. This is mostly purely theoretical since zero manufacturers are actually pushing security updates to devices this old. But the code is there if anyone wants it.
Can’t reproduce it (I e. vibration motor is working on my FP2 running this version). So I don’t think it’s a general issue of this OS. Are you sure do-not-disturb is deactivated - as I can only reproduce it when I turn this on (then also CheckUp test does not generate a vibration).
. (No, of course not)