alt Hacker NewsYes, but that person still needs to file a request and wait several days
Replies
aleph_minus_one • yesterday at 11:32 PM
But after one person does this, the source code access is a solved problem.
➕ show 2 replies
Yes, but that person still needs to file a request and wait several days
But after one person does this, the source code access is a solved problem.
It was initially taking under a business day for them to respond, but our recent requests have often taken weeks for them to get back to us. We want the code for all the Beta releases and are entitled to it.
This is the relevant code for Android 17:
https://gitlab.com/grapheneos/kernel_pixel/-/tree/17-base
https://gitlab.com/grapheneos/kernel_pixel_muzel/-/tree/17-b...
There are other branches there with it for Android 17 QPR1 Beta and Android 17 QPR2 Beta.
Google could save everyone including themselves a lot of hassle by simply publishing it to GitHub. If they don't want to push it to AOSP for weird organizational reasons as part of saying AOSP doesn't support Pixels, fine. Taking weeks or more to get back to us isn't reasonable for one the largest tech companies in the world.
It's also questionable whether what they're providing is truly the preferred form for modification considering the build system is quite unhappy about the lack of Git repositories. They had to provide a repo manifest metadata file to work around part of it.