

Read their comment and I’m left scratching my head. Their role in security with the straight android phone (not the /e/OS version) is simply pushing security patches as/when they get them from the Android team, as they’re using straight Android. Security is handled by Google for Android, not them. When it comes to /e/OS, no idea how good/bad it is, but apparently Graphene has some beef with Murena (the people who make it), at least according to their comment.
Not at all knowledgable about mobile kernels and drivers to comment on the rest of it. I do know Fairphone 5 uses an unusual CPU normally used for SoC as that was the only CPU that was both good enough to run Android reasonably while simultaneously providing very long-term driver updates (they’re aiming for a minimum of 8 years of updates).
I have a friend who does game QA. A lot of the time issues this major are caught, documented, and then management decides the extra delay to solve it isn’t worth the effort because “it’s not going to impact enough people to matter”. Then, once a firestorm erupts due to public backlash, they try and blame it on QA.
My friend has gotten very good at ass-covering, and makes sure every issue ticket is very explicit, not only in terms of what the issue is, the cause, reproducibility, but also how likely the average user is to hit it just to avoid blame.