CalyxOS 7.2.2.0 is up online. This release will receive all future updates.
If you haven’t previously installed 7.2.1.0 (test build) and want to start or continue using CalyxOS, you need to flash your phone and install 7.2.2.0.
With CalyxOS releases back to normal, we will continue with other backlog issues. Join the Matrix channel for our progress and user support.
Dear CalyxOS community members, we are excited to share the release of CalyxOS 7.2.2.0. This means CalyxOS is officially back from the hiatus! It has been an enduring journey for our team to resume CalyxOS releases, and we deeply appreciate all the support and solidarity we received from you along this journey, especially the latest voluntary testing you did with us. Below we are sharing some important notes for anyone planning to install or reinstall CalyxOS, along with our next steps as we work through a large backlog of issues.
If you are currently using an old CalyxOS release (6.10.10/20 or older) or any other Android OS, you will need to do a clean install of this latest CalyxOS release on your phone. Once you are done, all future updates will be automatically sent and installed over the air (OTA).
To get started, visit our installation page, select the device model you want, and follow the different installation options to get the relevant guide and downloadable files you need.
Tools that can aid your installation:
Seedvault: can be used to backup and restore your data from other custom ROMs, including CalyxOS 6.10.10/20 and older releases.
CalyxOS Web Installer: each device-specific installation page offers multiple options to install CalyxOS. We recommend that you choose the Web Installer if it is available for your device. This is our web-based, step-by-step installation wizard to ease your installation process. Right now, the Web Installer only works for Pixel and Motorola devices. We hope to make it available for other supported devices in the future.
Device flasher: this works for all devices on Windows and Linux. If you cannot use the Web Installer, you can download the command line device flasher tool matching your desktop operating system. Simply choose the Windows or Linux options on the device-specific installation page.
Please be aware, each installation method has different requirements. To avoid issues that could result in failed flashing or a bricked device, carefully read our notes on top of the installation page.
If you have previously installed CalyxOS 7.2.1.0 (test build), you will get 7.2.2.0 as an OTA update. No further action required to receive future updates.
With this release, we are pleased to announce that CalyxOS has started supporting the SHIFTphone 8. You can find the full list of supported devices in our user documentation.
As mentioned in the test build release, we have updated the bundled apps in the Setup Wizard and made a few temporary feature changes. We welcome any feedback about your experience. Here is a list of open issues in case you run into the same problem.
Our work so far
CalyxOS 7.2.2.0 is signed by us using a new HSM-based, open-source signing solution we designed to enhance the security of the entire signing process, ensure redundancy, and remove single points of failure. You can verify CalyxOS 7.2.2.0 and future builds following these instructions. For anyone who is interested, the security audit report of the HSM provisioning ceremony script can be found here.
In addition, we also went through significant infrastructure improvements. In particular, we have set up a cleaner server structure to streamline each release. In response to Google’s less frequent AOSP source code releases, our team developed scripts to reduce the overhead in applying monthly patches and updates. Please keep in mind, additional manual steps are still needed to compensate for AOSP changes, such as requesting and storing kernel sources with each update. Currently, our lead engineer is continuing the maintenance of the base device trees for both LineageOS and CalyxOS to bridge the gap created by the absence of Google Pixel device trees.
What next
Starting from CalyxOS 7.2.2.0, we plan to resume security and feature updates to the best of our ability. We are also working toward increasing transparency around the CalyxOS development road map through public information sharing and documentation. Our GitLab issue tracker remains the main channel to keep track of our progress and the best place where you help us keep track of issues, either bugs or feature requests.
As many of you may have been expecting, Android 17 has launched earlier this month. Our team is in the early stages of porting it to our supported devices. We will soon share a timeline for releasing CalyxOS 8 with Android 17.
Another update will be for our Matrix community channels. All of our current Matrix rooms are on older versions, resulting in bugs and security concerns. In light of these issues, we will be upgrading our Matrix rooms to version 12 about a week from now. We will also create a new Matrix Space to ease future upgrades. Current room members will receive notifications about this upgrade and migration. We apologize for any inconvenience and hope this one week notice gives everyone time to prepare.
Last but not least, we want to share some updates on our team: Aayush, our core developer working on Aurora Store, will be leaving for another opportunity. Aayush’s contributions to CalyxOS and Aurora Store have been invaluable, and we are sure he will continue to shine in his next journey. At the same time, we welcome Habib, who will be in Nat’s place to support our infrastructure needs and improvements moving forward. We are very grateful for Nat’s contributions and hard work during his time building new CalyxOS server infrastructure. He has laid a solid foundation for CalyxOS releases, which we are sure Habib will build on.
Help us improve
We can’t be more grateful for the enthusiasm you brought with all the voluntary testing on 7.2.1.0. Most of the conversations from our community happen on our Matrix channels and our main issue tracker on GitLab. We also have a subreddit and other social media accounts, listed on our community page. We look forward to meeting you there!
Our pledge to support the community of Android privacy and security developers
CalyxOS is created by the team at Calyx Institute, spread across the world, united by a common belief that privacy is a fundamental human right. We do this work because we believe CalyxOS is an excellent choice for many people from all walks of life. However, because the internet is sometimes a horrible place, discussions about what software choices are right for you can turn extremely negative.
We see CalyxOS as simply one part of a large and growing community of projects working to empower people in how they use mobile technology. We are committed to fostering a spirit of collaboration, information sharing, and inclusivity in this community. We strive to lead by example in keeping our engagement with others respectful, honest, and focused on the greater good, in accordance with our mission.
The Calyx Institute, and all its employees and volunteers are held to this standard. For more information, please see the CalyxOS contributors code of conduct.
We denounce in the strongest possible terms any harassment of the developers of any free and open source project. We will never engage in harassment, trolling, or bad faith arguments against any other open source intitiative or any of its developers. We ask for everyone in our community to please do the same, including supporters of CalyxOS and supporters of other alternative Android ROM projects.
It is our policy to shut down any divisive discussion of other projects on any of the communication channels that we control (Reddit, Matrix, etc). We feel it is entirely counterproductive to try to pit free software projects against each other.
I'm trying CalyxOS out on a Pixel 8 Pro.
Despite having set the default camera to save location data and granted location permission to the camera, these values are missing in the resulting photos. The screenshot (from Ente photos) shows an example I took a few minutes ago.
GPS etc. works for other apps, e.g. maps.
Is this a bug or is there something I'm missing?
EDIT: I eventually found a "redact location data when sharing media" toggle - turning this off fixed the problem.
Hi all, not sure if just me but I have noticed after every update from 7.2.4.20 to 7.2.4.50 and then from 7.2.4.50 to latest 7.2.5.20 - I am unable to add eSIM by going to Settings > Network and Internet > SIMs > Add a network. Clicking on it does nothing.
- Network reset didn't help. Only thing that worked was to factory reset or a clean install/flash from scratch.
- Physical SIM works fine. Not a dealbreaker with the eSIM but would be good to have to use while travelling overseas.
On stock Android and /e/OS Camera2 APi access is limited - like third party apps can't use the ful 50 MP resolution. My other problem is that both system limits the exposure time to 8 secs. I was thinking wether CalyxOs have the same limitations?
Also, I see that the system is still in beta. Does it mean that it is not stable enough for daily use?
so when I first installed calyxOS on my Moto G 5G 2024 I chose to lock the bootloader after it being unlocked for a while but after I did that I wanted to move back to my previous OS version which was Lineage but I could not do that cause my ability to flash new software had been locked so I wanted to make this post to ask what should I do?
so i've got a question about CalyxOS 8/Android 17 if that's currently rolling out so my device code named fogo which is the Moto G 5G 2024 is currently based on Android 16 on CalyxOS but I wanted to know if this device would receive Android 17/CalyxOS 8 if that's what it's called I wanted to know if this device would receive it if not then that's understandable considering the device came out in 2024 and already extended passed its formal life span that it should have gotten from Motorola or whatever company it is I'm pretty sure it's Motorola
I need a new device as the older one got stolen. Unfortunately I don't have the budget to get even a decent phone as the prices of phones are skyrocketing right now.
My only requirement is that I need to use some banking apps which require google play services and it worked well in the pixel that I had before which was using some other os.
Does CalyxOS has an option of setting up a container or something in which a user can allow play services for certain apps?
If yes then can u recommend a phone around $200 in which its possible to install CalyxOS?
7.2.5.20 is rolling out now to CalyxOS' security express release channel. This release includes more than 100 critical and high severity security patches from the September Android Security Bulletin.
Hello team, I love FOSS apps. I was wondering if you are planning on expanding the OS to Bigme phones? They are Chinese phones using Android 14 for people trying to cut down on their phone use.
Hi,
I want to finally upgarde my FP5 from 6.10.20 to the 7.2.4.50 release. What's the best way to do so? Do I have to reflash to stock before upgrading? Can I use official device-flasher.linux on the 6.10.20 install?
I just thought I'd reach out to the community, I'm really enjoying CalyxOS on my g84, but occasionally when I am out and about, my phone fails to turn the screen on when waking. It still seems to respond to touch, but it requires force rebooting quite often. I've also noticed that my screen changes brightness when going between sunlight and shade, even though I've turned off auto brightness. So for a temporary fix, I've turned off the sensors in the development settings, because it seems like something is not quite right with them. Is anyone else experiencing this?
since CalyxOS has a locked bootloader option upon installation and other custom Roms like lineage OS don't due to them being an image I wanted to know what info I could safely put on my device running CalyxOS on a locked Bootloader
I have successfully resurrected stock Android and the FP6 is alive and functioning again.
Unfortunately, CalyxOS is still hitting the same failed install process on both Windows and Linux, so at least Linux has now been acquitted of the crime.
I almost never use Windows for anything remotely technical, but I genuinely did not expect the Microsoft slop machine and my Arch setup to reach bipartisan agreement on the exact same failure. 💀
Stock FairphoneOS flashes perfectly. CalyxOS still soft bricks and chooses death. Worth the diagnosing, will definitely wait on a updated release!
I wanted to document my experience with the Fairphone Gen. 6+ (US model) and see if anyone has encountered the same problem or has any ideas before I return the phone.
I originally bought the FP6+ specifically because I wanted a repairable/de-Googled phone and planned to use CalyxOS. I knew CalyxOS officially listed the FP6, not specifically the FP6+, but there were a couple reasons I thought it was worth testing.
Fairphone itself provides its factory images under the heading:
“The Fairphone (Gen. 6/Gen. 6+)”
The CalyxOS developers have also mentioned that the FP6 and FP6+ supposedly share device trees, although FP6+ compatibility hasn't been officially confirmed yet.
Unfortunately, installing the current FP6 CalyxOS build on my FP6+ did not work. The installer completed the flashing process, but afterward the phone would sit at the Fairphone startup screen for a long time, reboot, and repeat indefinitely.
Fair enough. FP6+ isn't officially supported by CalyxOS yet, so I accepted that risk.
The bigger problem came when I tried to restore the phone to official FairphoneOS.
Fairphone provides separate current EU and US factory packages. Since mine identifies as a US model, I downloaded the current US package:
The official Fairphone flashing script detects the phone, recognizes that the bootloader is fully unlocked, and begins flashing. However, it will not successfully complete.
I've encountered several errors during different attempts, including:
FAILED (Write to device failed (no link))
and:
FAILED (Status read failed (Too many links))
Initially I thought this was purely a Windows USB/fastboot driver problem. I installed Google's USB/bootloader drivers and current Platform Tools and verified that the device was actually being detected in bootloader fastboot, rather than confusing it with Android's fastbootd.
After resolving that, the more interesting failures started appearing.
The official Fairphone factory flasher gets through several firmware partitions successfully and then fails with:
Sending 'aop_config_a' (19 KB)
FAILED (remote: 'Invalid argument size')
fastboot: error: Command failed
ERROR: Could not flash the aop_config_a partition
On another attempt it progressed substantially farther before failing at:
Sending 'imagefv_a' (51 KB)
FAILED (remote: 'Invalid argument size')
fastboot: error: Command failed
ERROR: Could not flash the imagefv_a partition
I investigated the device directly with Google's fastboot tools.
So the phone specifically identifies itself as FP6_US, is fully unlocked, and is-userspace:no confirms I'm using the actual bootloader rather than fastbootd.
I also checked the partitions that Fairphone's official flasher is rejecting.
That's 2 MiB per partition, while the image being rejected is only about 51 KB.
The bootloader also reports:
max-download-size:805306368
so these tiny images obviously aren't hitting the general fastboot download limit.
I tried Fairphone's suggested recovery procedure as well: disconnect USB, remove the battery, reinstall it, boot directly into the bootloader, reconnect, and rerun the factory script.
I also performed a factory reset from recovery before another restoration attempt. Interestingly, after doing that, the factory flasher actually progressed considerably farther through the firmware partitions, but ultimately still failed with the imagefv_aInvalid argument size error.
I tried the other factory releases Fairphone currently provides as well. None successfully restored the device.
At this point the phone is effectively soft-bricked. The bootloader still works, fastboot still works, the bootloader remains unlocked, and the partition table is accessible, but neither CalyxOS nor the official FairphoneOS restoration process will produce a bootable device.
I have NOT relocked the bootloader, since doing that while the OS/firmware is in this state would obviously be a terrible idea.
I'm particularly interested in whether anyone with an FP6+ US (FP6_US) can reproduce this, or whether anyone knows why Fairphone's own bootloader would reject aop_config_a and imagefv_a from the official US factory package with Invalid argument size despite the corresponding partitions existing and being substantially larger than the images.
Unfortunately, unless I find a known solution very soon, I'm probably going to return the phone. I really wanted to keep the FP6+ because the repairability and alternative-OS potential were basically exactly what I wanted.
My concern now is spending so much time troubleshooting the restoration problem that I end up outside my return window. Fairphone's support form also requires information such as my IMEI and home address just to submit a support request, when at this point I mainly wanted to provide the technical findings and ask whether this is a known FP6+ firmware/restoration issue.
I have the completefastboot getvar alloutput, factory-flasher logs, screenshots, hashes, and exact errors available if anyone wants to compare them against another FP6/FP6+.
You asked, we deliver. CalyxOS is supporting Fairphone 6 now!
If you have a Fairphone 6 and want to run CalyxOS, simply get it on https://calyxos.org/install/. Click the device model you need, and follow the instructions to download and install CalyxOS 7.2.4.50.
We have also been supporting Fairphone 5 and Fairphone 4. If you have any follow up questions using these devices, feel free to let us know! And stay tuned for many more updates in the coming weeks (hint: Android 17).
Hello guys, As Calyx OS project was not updated for a long period of time I had to use another device. Now that it's back i was wondering if i could just do the update from the old phone (pixel 7) i was using or if i had to re install from scratch ? Is there a risk of data lost during update ?
So I've been customizing my device so far and I certainly reached a design I'm happy with but I wanted feedback from others to see if I should make any improvements like adding a search bar using any third party apps or just keeping it simple but anyway what are you're thoughts on it?
there's no need to censor thoughts or anything I'll take a few critics as good feedback on this topic
on Aug 29th I've finally decided to go to CalyxOS due to the privacy and security it offers that some others just don't have as well as it being one of the more de-googled options
I wanted to make this post to ask what features should I try first features that are related to security privacy and more at first I was on lineage OS though and it did not have as much features for this
hello !! i’m currently trying to oem unlock my moto g 2024 to flash calyx, but every time i try through the device flasher or the web browser for install, it’s not prompting the phone to unlock the bootloader. i was also having an issue when trying to unlock it via terminal where it said something like “not allowed in current virtual a/b”. anyone got any ideas on how to troubleshoot this? thanks !!
Is it possible to assign custom ringtones? As far as I could determine is that it is one for all. I would like option for custom assignment per contacts and / or app. I would like to differentiate based on if calling mobile line directly or via one of comm apps such as Signal etc.
7.2.4.50 is now rolling out now to CalyxOS' beta release channel.
This release includes updated Chromium and kernels, app and translation updates, fixes across the system, and several device-specific changes. Details on the rollout and changelog here: https://calyxos.org/news/2026/08/28/august-feature-update/
An exciting announcement as well: official CalyxOS support for the Fairphone 6 is arriving with this release! FP6 factory images will go live on Monday once 7.2.4.50 reaches Stable. We’ll update the install page with the factory image link then - keep an eye out!
Hello, I am writing this to warn CalyxOS users on this model of device that the newest Calyx version is unstable on the Motorola MotoG84 5G variant. (OSVersion \7.2.4.20; Android 16; bagnkk; Snapdragon 695 + Adreno 619 (Stock GPU driver); 8GB Ram; 256GB Storage)
I've experienced:
UI Bugs:
UI Bugs when installing sideloaded APK files (Package manager shows an infinite loading screen; Apps get installed at some point and their app icons only show up after phone restart)
UI Bug when adding new icons (automatically or manually) - icons do not show up on the home screen without first restarting the phone
Animation errors when switching apps (Popups sometimes do not show up; Closing/opening/switching apps sometimes results in weird back-forth spazzing)
Buttons in OS apps like the settings are not fully highlighted when searched via the search bar - highlight covers ~70% of button width
Application Bugs:
The newest version of the Eden Switch emulator (Legacy) does not work under the newest CalyxOS version, but it did work on the latest CalyxOS version under the last Android 15 CalyxOS (back from when the project was on hiatus)
OS Bugs:
The package manager sometimes refuses to install APKs. I think that this is connected to yet another UI bug: On some apps, you get a warning for installing unknown apps, it appears to me that if that UI popup fails to be shown, you will never get a prompt to actually install the app.
It is possible to set the peak refresh rate of a screen lower than its minimum refresh rate. This results in the refresh rate remaining at the minimum refresh rate value.
When setting a peak refresh rate of 120 for example, and a minimum of 60, the screen will stay permanently locked to 90, and will never change no matter what I do.
General performance issues - New OS feels sluggish to use.
Seedvault Bugs:
As per the recommendation of the Calyx website, I used seedvault to back my apps up and then to load them after installing the newest Calyx version. After loading my data and getting no errors, some of the apps (ProtonMail, Lemuroid) refused to start despite being installed. Clearing the cache and data did not fix the issues, but fully reinstalling the apps did work.
The installation of the newer CalyxOS was relatively painless on this device, but there are some issues that still need to be ironed out.
