zlacker

I dont recall Pixel device being sold saying "Buy our device and install GrapheneOS on it". I'd like to be wrong, so I'm happy to read articles if you have any.

>>bitpus+(OP)
Nothing I bought in the produce aisle today had instructions for use. Should I leave it to rot?

AOSP recipes themselves list reference devices and they could have updated this with their announcement in March if they didn't want external developers procuring these things as bricks for their gardens. GrapheneOS is just a community of a AOSP derivative there are any number of AOSP derived things people may have been doing with these devices.

>>lipowi+2g
I have a Macbook, and if I try to install Windows of it and fails, should I be angry with Apple? Should Apple be on the hook to make it work?

Or, how about Hackintosh (from yesteryear). Apple gave 0 support for it all those years when folks made it work, and one day it went away - and I dont remember saying Apple, please support Hackintosh.

>>bitpus+Tn
Huh? Google gives everyone in the world instructions to make derivatives of AOSP and they could install them[1] on the reference devices which were all nexus/pixel. Google said nothing until they suddenly didn't deliver for those devices.

They made related announcements in March and certainly saw interpretations of their announcement by interested AOSP derivative maintainers.

That's not remotely the same as I figured how to boot X against so and so's wishes and now it stopped working.

[1] https://source.android.com/docs/setup/test/running