CalyxOS

CalyxOS 8.0.0.0 - Android 17 rollout begins, with more devices to follow

Devices have been tested internally, although there may be minor bugs. If you run into any problems, please report an issue.

This release has been rolled out to both the Beta and Security express channels because it includes significant security patches for multiple devices and apps, most notably microG. Rollout dates are listed below. Please note: the Pixel 10a build will be available when this update rolls out to Stable. We are working on bringing Android 17 to the Pixel 5a (5G) and our supported Fairphone, SHIFTphone and Motorola devices. These devices require additional device-specific work and will be released separately.

Users of CalyxOS devices that are not yet receiving the 8.0.0.0 update can install the latest microG update manually using our signed microG APKs and the instructions below. These instructions use CalyxOS Chromium as the example browser.

  1. Open CalyxOS Chromium and download both of the latest signed microG APKs:
  2. Check that both downloaded files end in .apk. If either file ends in .apk.jar, rename it so that it ends in .apk only. For example, rename GmsCore.apk.jar to GmsCore.apk.
  3. When the downloads finish, tap “Open” in the download notification for one of the APKs. You can also find the files by opening Chromium’s three-dot menu and selecting “Downloads”.
  4. Tap the downloaded APK. The first time you do this, Chromium will show a “Permission required” prompt. Tap “Settings”.
  5. On the “Install unknown apps” settings page for Chromium, enable “Allow from this source”.
  6. Return to the APK installer. When the “Update this app?” prompt appears, tap “Update”.
  7. After the first APK has finished installing, return to Chromium’s “Downloads” list and tap the second APK.
  8. When the “Update this app?” prompt appears, tap “Update” and wait for the installation to complete.
  9. Restart the device after both APKs have been installed.

In addition, we are also releasing an big update to our device-flasher install tool. Major changes include: 1) ability to install from macOS is back, and 2) a new guardrail to prevent accidental device bricking triggered by Anti-Rollback Protection issues.

Rollout

Release channel Date
Beta 1 October, Thursday
Security express 1 October, Thursday
Stable 5 October, Monday

Changelog

Features and bug fixes

Pixel 6+

Pixel 8+

Pixel 10a

Pixel Tablet

Note

  • Over-the-air (OTA) Updates: Starting from CalyxOS 7.2.2.0, CalyxOS updates resume automatically over the air. No manual install of updates needed. However, if you would like to manually update your CalyxOS device, see our OTA installation instructions.
  • Security Updates for Pixel devices: The Pixel 9a, 9 Pro Fold, 9 Pro XL, 9 Pro, 9, 8a, 8 Pro, 8, Fold, Tablet, 7a, 7 Pro, 7, 6a, 6 Pro, and 6 stock OSes follow a monthly release schedule in direct alignment with the AOSP security bulletin. However, Google has stopped publishing the source code for AOSP QPR1 and QPR3 releases. As a result, CalyxOS is not able to timely include updates of the proprietary components, such as the bootloader, modem, and vendor firmware, for versions based on those specific QPR branches. The CalyxOS releases for the above models only contain the latest fixes to the open-source components, such as the operating system and the Linux kernel. Proprietary components get updates as soon as the corresponding AOSP source code becomes available.
  • Security Updates for non-Pixel devices: The Fairphone (Gen. 6), 5, 4, Motorola moto g 5G 2024, moto g84 5G, moto g34 / g45 5G, and SHIFTphone 8 stock OSes follow a different security update release schedule, which is usually behind AOSP updates by a month or two. The CalyxOS releases for these devices only contain the latest fixes to the open-source components. Proprietary components get updates as soon as the stock OS update becomes available.
  • End-of-life: The Motorola moto g52, moto g42, moto g32, Pixel 5a (5G), 4a (5G), and 5 are no longer being updated by the manufacturer, the CalyxOS updates for these devices only contain the fixes to the open-source components. Proprietary components no longer get updated.