Can someone who works on Android or at least works on Google help me get in contact with the right people?
There are a few issues with the Pixel 6a release which need to be resolved.
There are a few mistakes with the push to AOSP and also services that aren't set up properly.
Conversation
Pixel 6a sources were mostly pushed correctly but a new repository needed to be added to AOSP and is missing:
kernel/google-modules/sensors/hall_sensor should be present here and the Pixel 6a kernel build system expects it to be available and breaks:
android.googlesource.com/kernel/google-
2
1
10
Replying to
It looks like it's actively being worked on. The empty repo showed up only a few hours ago. android.googlesource.com/kernel/google-
1
Replying to
I emailed 2 of the people with related commits and this part of the problem is fixed now. It just has an empty master branch like most of those repositories and the stable release is available now:
android.googlesource.com/kernel/google-
1
1
The only blocker we have now is that the OEM unlocking service is broken since it seems no one pushed the Pixel 6a SKUs, serials, IMEIs, etc. to the services for unlocking/repair/warranty. I hope that gets done quickly. The reason we're in a rush is because of Android 13 coming.
1
2
Replying to
Did you file a bug? I can help escalate, but it's easier if a bug with all the relevant details already exists.
1
Replying to
I just filed issuetracker.google.com/issues/2406116. I wasn't sure the Android issue tracker was the right place for it but it's most relevant place I can file it.
I think the service side issue was fixed but working around it requires updating to the June OTA only being shipped to Verizon users and then the device has to be factory reset because it gets persistently locked into the response it got from the server or something.
1