first, a huge heap of thank you for authoring .
Wanted to get some advice: should I get a Pixel 3a and use GrapheneOS on it or get Pixel4a (when released) and contribute code for its device support.
Ive read a reddit post that pxl4 didnt have contributors
Conversation
I’d be happy to work on Pixel4a device support, is there a preliminary doc to do some background reading or any topics you can suggest to get started with? Thanks!
1
Replying to
grapheneos.org/build is a good starting point. Look at device/google/crosshatch, kernel/google/crosshatch and vendor/google/crosshatch for the device support code for the Pixel 3 along with looking into android-prepare-vendor which is how we currently handle the vendor image.
The device support components outside of vendor aren't actually required and could just be omitted. Stuff in product is already omitted by GrapheneOS and stuff in system could be omitted too. It would mean not having certain carrier features/support but we mostly lack it anyway.
1
1
Technically only need the kernel (which is fully open source) and components in vendor. Unfortunately, we don't currently build the components in vendor from source even though for most of them we could either build them from source, omit them or use available alternatives.
1
Replying to
Thank you for the links. Is r/GrapheneOS a good place to ask n00b questions or is there a xda/dedicated forum where those discussions take place?
1
Replying to
Use the #grapheneos channel on Freenode or the bridged #grapheneos:matrix.org channel via Matrix. The subreddit is pretty terrible and people who can actually answer questions especially those about development are active on IRC/Matrix rather than the subreddit.
1
1
Show replies