Hardly true, if they permitted Lineage and so on.
> Just like any enterprise software, it targets a set of common devices so they can provide support and QA on it.
Not really, there are a myriad of devices and they're not testing on all of them. A "pound sand if you're on an unsupported device and it isn't working" policy would be perfectly acceptable, as long as the issue isn't directly caused by the developer purposefully breaking the application for a subset of users that fail Play Protect check or whatever.
[–] dns_snek 1 day ago
[–] bilkow 1 day ago
What I think happened is that GrapheneOS assumed the blog post meant that those updates happened at the time of the post, while the post is actually announcing things that were done in the last few months.
[0] https://review.lineageos.org/q/subject:%22release:+Bump+Secu...
[–] dns_snek 21 hours ago
> Most non-Google-certified operating systems are setting an inaccurate Android security patch level by ignoring the non-AOSP portion of the patches. GrapheneOS doesn't do that but most of the other AOSP-based projects not being certified by Google are doing it. OEMs were caught doing it too but it's not clear if it was intentional in most cases as it is with the alternate operating systems.
[–] yjftsjthsd-h 1 day ago
[–] teekert 1 day ago
I agree, but that is also totally unrealistic for normal people.
Btw, My son has a 200 eur Samsung Galaxy A26, very fine device for the price I have to say, and supported until feb 2031.
[–] hedora 1 day ago
Installing Lineage isn't that hard. If they're going to badly inconvenience some customers / force hardware purchases, why not start with the ones who are most likely to get their accounts drained?
GrapheneOS have written about (in)security of LineageOS:
https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...