Hacker News Reader

HNHacker News

Top New Best Ask Show Jobs

Comment by Pfhortune | Hacker News Reader

Parent Full thread

Pfhortune·

> and new Pixels will not be able to run non-Google-certified operating systems :)

I haven't heard about this. Source?

I think there has been much _speculation_ around this, but no proof that I am aware of.

View on HN

They have already shown themselves to be both able and willing. Hopefully the backlash from this current decision will delay their plans long enough for GrapheneOS, Lineage and others to figure out how to work around it somehow, which is why I'm eagerly watching where this is going.

I can't confirm this yet but with Google refusing to provide device trees for new Pixels things definitely look headed that way; they're at least starting to make installing an alternate OS difficult. The Graphene devs are trying to set things up with a handset manufacturer to ship a GrapheneOS phone, but good luck connecting that thing to a US carrier (who allowlist handsets and often limit the allowlist to models they sell directly).

> Google refusing to provide device trees for new Pixels things definitely look headed that way

So you're just speculating.

With all the things google is doing for custom os last few years ( play protect, no major updates to asop and bundling updates to closed source google libraries etc). It is not speculation it is predicting with high certainty. Google wants custom os market to die and they are doing it brick by brick. We should Open our eyes and look at the timeline and realise it is not speculation and actual reality before it will be too late. Source: i am an owner of device with custom os and i know things i have to do to fix broken apps.

> Source: i am an owner of device with custom os and i know things i have to do to fix broken apps.

Doesn't mean you can predict the future with high certainty.

Source: I have been a happy user of custom AOSPs for years.

Reply on news.ycombinator.com