A16 for Google Pixel 8 Shiba

Hy

I just got a Pixel 8 to replace a Xiaomi that’s already running /e/ OS. The problem is that the /e/ OS image for the Pixel 8 is based on Android 15, while the phones ship with Android 16. Do these smartphones still have anti-rollback protection?

When is the migration from A15 to A16 scheduled, since A16 is already officially available on most custom ROMs?

I understand that the Pixel 8 is an official build of /e/ OS?

Thanks for good job

Please read with care Factory Images for Nexus and Pixel Devices  |  Google Play services  |  Google for Developers and be careful only to roll forward as the consequences of roll back could be fatal, rather than just inconvenient.

Official build schedules always depend on the ability to OTA Upgrade so they will lag and do not appear for this device in weekly-updates at this time.

Thanks for the reply and the link to the community build for Android 16.

One last question: if I use the community build, will I be able to switch to the official version when it becomes available, or will I have to reinstall everything from scratch?

thanks

Official advice is Fresh install. You might get away with it, but you should not really be able to do this with success due to build keys, some do report success.

Personally I am happy with community and don’t plan to change to official even though available.

If I wanted official because I thought I could benefit from some added feature then I would only consider a fresh install otherwise how could I know if the added feature was 100% “faithful”?

1 Like

Does the Community Edition receive OTA updates when a new version is available?

Thanks

Absolutely yes to updates, that is the monthly /e/OS version including Android SPL updates.

Upgrade of Android version we must do manually. New Android versions are introduced to the world annually. Community build users are often offered some flexibility of when to upgrade if 2 (or even 3) versions of /e/OS are published and available for any one device.

1 Like