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
I think this was forgotten because it's a new repository not represent for the raviole kernel (raven + oriole, i.e. the Pixel 6 and Pixel 6 Pro). It's missing in the manifest too:
android.googlesource.com/kernel/manifes
It's part of the bluejay (Pixel 6a) build config:
android.googlesource.com/kernel/devices
1
1
11
Pixel 6a has also not been added to the repair/warranty and OEM unlocking services. This is quite possibly a single oversight since it's the same data. For one thing, this means users trying to use store.google.com/us/repair get an error. It also means OEM unlocking isn't possible.
2
5
14
We've done as much as we can developing GrapheneOS support for the Pixel 6a without OEM unlocking working.
People received devices before official launch day today (July 28th) and many things were missing, but these 2 things are still missing even after theoretical launch day.
1
4
12
I emailed 2 engineers who worked on bluejay and had commits related to AOSP merges about this and one of them sent an email along to the right person for the missing AOSP repository.
I'm unsure who I need to contact to get issue with repair/warranty and OEM unlocking db fixed.
1
2
13
It seems someone forgot to push the serial numbers for the Pixel 6a into those databases, so they don't know about the Pixel 6a. It's not terrible that the warranty/repair check service is broken but OEM unlocking being broken on an AOSP reference device is a huge pain for devs.
Replying to
Is that why people aren't able to use their unlocked 6A phones on Cricket (AT&T) and Visible (Verizon) wireless?
1
1
Replying to
It doesn't seem directly related but the root cause could be the same issue: they didn't deploy Pixel 6a support to the usual services. It may impact eSIM activation and other services.
2
1
Show replies