Android 16 Released

[Bill Yi]

Android 16 source code is now available. The following builds and tags are supported:

 - BP2A.250605.031.A2, android-16.0.0_r1, Pixel 9, Pixel 9a, Pixel Tablet, Pixel 8, Pixel 6 Pro, Pixel 7, Pixel 6, Pixel 7a, Pixel 9 Pro XL, Pixel 8 Pro, Pixel Fold, Pixel 7 Pro, Pixel 9 Pro, Pixel 6a, Pixel 8a
 - BP2A.250605.031.A3, android-16.0.0_r2, Pixel 9 Pro Fold

We pushed the kernel source for the following devices as part of the Android 16 release:

Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro, Pixel 7a, Pixel 8, Pixel 8 Pro, Pixel 8a, Pixel Fold, Pixel Tablet, Pixel 9, Pixel 9 Pro XL, Pixel 9 Pro, Pixel 9 Pro Fold, Pixel 9a

Tag                  | Project                             | Branch
---------------------+-------------------------------------+------------------------------------------
android-16.0.0_r0.0  | device/google/raviole-kernels/6.1   | android-gs-raviole-6.1-android16
android-16.0.0_r0.1  | device/google/bluejay-kernels/6.1   | android-gs-bluejay-6.1-android16
android-16.0.0_r0.2  | device/google/pantah-kernels/6.1    | android-gs-pantah-6.1-android16
android-16.0.0_r0.3  | device/google/lynx-kernels/6.1      | android-gs-lynx-6.1-android16
android-16.0.0_r0.4  | device/google/tangorpro-kernels/6.1 | android-gs-tangorpro-6.1-android16
android-16.0.0_r0.5  | device/google/felix-kernels/6.1     | android-gs-felix-6.1-android16
android-16.0.0_r0.6  | device/google/shusky-kernels/6.1    | android-gs-shusky-6.1-android16
android-16.0.0_r0.7  | device/google/akita-kernels/6.1     | android-gs-akita-6.1-android16
android-16.0.0_r0.8  | device/google/caimito-kernels/6.1   | android-gs-caimito-6.1-android16
android-16.0.0_r0.9  | device/google/comet-kernels/6.1     | android-gs-comet-6.1-android16
android-16.0.0_r0.10 | device/google/tegu-kernels/6.1      | android-gs-tegu-6.1-android16

thanks


bill

[Dean Wheatley]

The https://android.googlesource.com/platform/manifest/+/refs/tags/android-16.0.0_r1/default.xml includes https://android.googlesource.com/platform/external/v4l-utils but there's no android-16.0.0_r1 tag for that project yet so the repo sync is failing. All of the other projects have the tag. 

[Al Sutton]

You can use android16-release for v4l-utils as a workaround until it's fixed.

--

--

You received this message because you are subscribed to the "Android Building" mailing list.

To post to this group, send email to android-...@googlegroups.com

To unsubscribe from this group, send email to

android-buildi...@googlegroups.com

For more options, visit this group at

http://groups.google.com/group/android-building?hl=en

---

You received this message because you are subscribed to the Google Groups "Android Building" group.

To unsubscribe from this group and stop receiving emails from it, send an email to android-buildi...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/android-building/d63ceccc-cf7f-4d17-b82d-c08b39f5250fn%40googlegroups.com.

[Bill Yi]

Updated.

[sossw]

Getting this error when trying to build for Pixel 6 Pro.  (Source synced with tag android-16.0.0_r1 in a new directory).

$ lunch aosp_raven bp2a userdebug

03:19:55 Build sandboxing disabled due to nsjail error.
In file included from build/make/core/config.mk:419:
In file included from build/make/core/envsetup.mk:351:
build/make/core/product_config.mk:226: error: Cannot locate config makefile for product "aosp_raven".
03:19:55 dumpvars failed with: exit status 1

Any ideas?

[danie...@gmail.com]

Pixel device and hardware repositories have been removed in Android 16. The kernel prebuilt repositories referenced in this post have been removed from the manifest and don't have Android 16 tags. Is there going to be a post from Google about the end of AOSP support for Pixels? Existing official documentation no longer works and many public promises have been broken.

GrapheneOS was provided with early warning of this happening in April 2025 by someone with inside information. Further information beyond what's now public was provided about upcoming changes further reducing what's published beyond dropping Pixel support. We didn't know if the information we received was reliable, but now several parts of it including the removal of Pixel support from AOSP have been confirmed.

Is the lack of GPL sources for platform repositories with Android 16 QPR1 Beta 1 and Android 15 QPR1 Beta 2 intentional?

[CLF BBN]

Thanks for releasing the code!

However, I cannot find the release of pixel device repositories. Will they be released in a near future?

Thanks.

[Dean Wheatley]

Thank you for fixing the sync.

Next issue I'm seeing is after sourcing envsetup.sh, list_products is failing

$ list_products

panic: Missing config trunk_staging.  Trace=[trunk_staging]

goroutine 1 [running]:

main.main()

        build/soong/cmd/release_config/release_config/main.go:71 +0x14c5

In file included from build/make/core/config.mk:419:

In file included from build/make/core/envsetup.mk:51:

build/make/core/release_config.mk:142: error: release-config failed to run.

07:00:48 dumpvars failed with: exit status 1

Usually this is needed first to then find out which releases are supported for each target, and then to work out which build variants are supported, and then chain them all together to invoke with lunch.

[cdesai]

Thanks for publishing the release.

I'm not able to make an AOSP build for the above mentioned Pixel devices because they're missing from the platform manifest, and their git repositories also don't have the android-16.0.0_r1 tags.

Is there any further information available on this?

[Łukasz Patron]

Hello,

Are Pixel device trees omitted on purpose?

I saw that https://android.googlesource.com/platform/manifest/+/2e764235335a27ee8cc8efc16baef4c0f6a5b3fe%5E%21/ removed them from manifest, which very unfortunate for the AOSP community.

- Łukasz

[Bill Yi]

We remain committed to AOSP updates. You continue to have the option to build Cuttlefish and GSI targets from the sources for experimentation.

bill

[Nolen Johnson]

This reply is somewhat unclear.

If you could clarify:

Will Pixel device trees and hardware repos be coming at some point, or are they no longer being released period?

Will kernel source releases continue to be single commit, history-less releases?

[Oliver Scott]

Should we expect the current release to constitute the open portion of Android going forward?

Or can we expect there to be other removals? If so, would it be limited to non-essential components or could it include boot-critical components as well for example?

Thank you,

Oliver

[Dean Wheatley]

Even if you know the product, list_releases also doesn't work:

$ list_releases aosp_cf_x86_64_phone

panic: Missing config trunk_staging.  Trace=[trunk_staging]

goroutine 1 [running]:

main.main()

        build/soong/cmd/release_config/release_config/main.go:71 +0x14c5

In file included from build/make/core/config.mk:419:

In file included from build/make/core/envsetup.mk:51:

build/make/core/release_config.mk:142: error: release-config failed to run.

15:31:00 dumpvars failed with: exit status 1

So, I used first part of the build ID in https://source.android.com/docs/setup/reference/build-numbers to ascertain bp2a is the release to use.

So, this target works for Cuttlefish:

$ lunch aosp_cf_x86_64_phone-bp2a-eng

(After looking at device/google/cuttlefish/AndroidProducts.mk)

By the way, https://source.android.com/docs/setup/reference/build-numbers says Pixel devices are supported in the android-16.0.0_r1 build tag. Is that table incorrect?

[Dean Wheatley]

Cuttlefish doesn't build. I've logged bug in issue tracker: https://issuetracker.google.com/issues/424450094 .

On Wednesday, June 11, 2025 at 5:28:03 PM UTC-7 Nolen Johnson wrote: