For the Fairphone 5, there’s now a stock OS release (FP5.VT2E.C.059.20250908) which reportedly fixes that OS’s issue that prevents Android 15 booting with a broken fingerprint sensor.
Is it expected that /e/OS v3.2-a15 for FP5 (“ETA Mid October”) would pick up any material from that Fairphone OS release, or is that now too late to get into v3.2?
(I ask in case /e/OS is affected by the same issue – which I still don’t know or have any evidence for – and if so, whether the root cause is in components shared with the Fairphone OS – which I don’t know either, despite asking – and also I don’t understand fully how/whether software components flow from fairphone.com to /e/OS. So a lot of speculation on my part behind this question. But I’m holding off upgrading my /e/OS from a14 to a15 until there’s more clarity on this, due to the severity of the potential bug, which could brick my daily driver on upgrade, or thereafter at any time if the fragile fingerprint sensor fails.)