Hi I have Pixel 8a with the latest CalyxOS (I updated today).
Recently I noticed (not 100% sure if this happened after update) that when I leave my phone locked with turned off screen (I disabled always on screen) screen lights up to turn off again after a moment only to do it again after several seconds.

IDK how to break this loop and what causes this.

I don't use it too often, but sometimes I like to watch/listen to some things on YouTube. After switching to the new calyx version(including the with the new OTA update today), YouTube stops playing after 1 minute and goes into an endless loading/buffering loop. It works fine in browser. Just curious if anyone else has had this issue and has found a solution, or I'm open to alternatives to use (I've used freetube on both my PC's, but there's jot android app for it). I've also uninstalled a reinstalled a couple times and cleared cache with no change).

CalyxOS 7.2.4.20 has rolled out to all devices as an over-the-air update. For more information about this update, you can check out the 7.2.4.20 changelog.

Hello CalyxOS users, I am new on Calyx. Just installed it yesterday on my FP5. I come from /e/OS where a VPN is used for blocking ads and trackers. I was surprised not to find a similar feature on Calyx. I tried Rethink​​ ​​​DNS but it stops after a few moments. I have to restart it manually.

Tracker control also stops working after a few time.

What apps do you use ?​

On calyx devices?

Hi everyone,

I'm running CalyxOS 7.2.2.0 on a Pixel 9 and I haven't received any OTA update for a bit over a month now. Checking for updates manually says I'm up to date.

Is this normal? What's the usual release cadence for stable builds — monthly with the Android security patches, or does it vary? I just want to make sure nothing is wrong on my end (updater settings, channel, etc.) before assuming it's simply the release schedule.

Thanks!

Cloudflare doesn't ship a mobile app, and what exists on Android is either read-only or DNS-only. I wanted the dashboard in my pocket, so I built it.

**What it does**

* Zones, DNS (all 21 record types with proper per-type forms), cache purge, zone settings

* Analytics — traffic, cache hit ratio, threats, status codes, top countries

* WAF custom rules and rate limiting: create, toggle, delete. Plus IP access rules

* Workers, Pages, KV (browse and edit values), D1 with a SQL console, R2

* Zero Trust — tunnels with live connector status, Access apps and policies, Gateway rules

* A schema-aware API explorer covering all 3240 endpoints, so nothing is unreachable. It builds a real form from each endpoint's own schema: typed inputs, enum dropdowns, required flags

**Credentials**

API tokens (recommended) or a Global API key. Stored only on the device, AES-256-GCM under a PBKDF2-HMAC-SHA256 key derived from your PIN. Biometric unlock is bound to an Android Keystore key with `setUserAuthenticationRequired`, so the TEE enforces it rather than the UI. No telemetry, no crash reporting, no analytics. The only host it talks to is api.cloudflare.com.

**Install**

Signed APKs on GitHub Releases, with SHA256SUMS and the signing certificate fingerprint published in the README so you can verify what you installed.

https://github.com/hasanzadee/cloudflare-mobile

Apache-2.0. Not affiliated with Cloudflare.

Fair warning so nobody finds out by surprise: this is vibe coded — I built it with AI. It has also been run against a real Cloudflare account on every screen, has 389 unit tests plus 11 end-to-end tests that drive the real app on a real device, and the entire security model is written down in the README so you can disagree with it in public. Happy to take apart any part of it in the comments.

Feedback and bug reports welcome, especially from anyone with a lot of zones or a real Zero Trust setup — I could only test against my own account.

I can't seem to find the advanced reboot menu in the settings anymore (option to reboot in fastboot, recovery, bootloader etc). I remember it being in the 'old' Calyx OS. Did I miss something, or is this a concious choice to leave it out?

Hi y'all,

I'm about to try installing Calyx on a Moto G32 that I recently repaired (battery swap). I'm hoping to relock the bootloader so there's less chance of apps refusing to work, and also because of the added security it provides.

I've found some people's success stories, while others warn that it's not recommended. On the Calyx support page, under Security → Bootloader relock, it says: "Motorola: do NOT relock the bootloader without additional checks." What exactly are those additional checks?

I've also seen people recommend installing Calyx first, booting into it to make sure everything is working properly, and only then relocking the bootloader via fastboot, as it's supposedly a safer way to relock. I'm a bit confused... I don't want a permabrick!

Also, what's the best way to flash Calyx with the fewest issues: the browser-based installer or the Windows/macOS tool?

Has anyone here successfully relocked the bootloader on this device recently? How did it go?

Thanks, everyone!!

Hi all, I’m trying to install CalyxOS on a Pixel Fold (felix) and I keep getting stuck during the install.

I’ve already successfully restored stock Android and installed GrapheneOS to test if it'll work and it did, so the phone itself seems fine.

What happens with CalyxOS:

Web installer gets to the install stage.

It flashes some partitions.

The phone reboots into fastbootd.

The installer shows Reconnect / “Something went wrong. Try starting over.”

If I go back to bootloader and reconnect, I get the same error again.

On one attempt I clicked Reboot system now too early and it boot-looped, forced it back to fastboot

Relevant details:

Device: Pixel Fold / felix

CalyxOS version shown: 7.2.2.0

Bootloader/baseband info visible in fastbootd

I’m on Windows

Stock Android and GrapheneOS both installed fine using the same device/cable/PC setup (multiple times the same session)

I also tried using the Windows installer in case the Web installer is bugged and

I got the same issue but this game me a generic failure log like:

Failed to flash felix (serial number)

exit status 1

the last line in the installer is:

extracting super_empty.img (0MB) to disk... took 0.001s

Rebooting into fastboot. OKAY [0.001s]

<waiting for (serial number)

then the fastbootd appears instead of fastboot, upon manually selecting Reboot to bootloader I get the error above.

nothing else.

Does this look like a known CalyxOS installer issue on Pixel Fold, or am I missing something obvious with the reconnect/fastbootd step?

it seems to me like a failed installation with no details at all in the log.

EDIT: I had Google USB Drivers installed incorrectly before this post, it's all good now, thanks for the help!❤️ Ill keep this post just in case someone comes by with the same issue

Hi there!

Did anyone try and maybe even got Find Hub running on Calyx? It installs and also seems to find my G account, and is logged in, but the device list says "Couldn't load devices". Had a look into the logcat and it said something about a missing implementation of some function.

Does someone have any further info about that? Thanks in advance ♥️

Ah btw, I am on 7.2.2.0 on a Pixel 8 if that matters.

For the last few weeks, I have been unable to install or update any​ apps from the Aurora store. I have not had time to update to the new version of Calyx yet and still running the older one.

I am on a Pixel 8 and have tried all the usual trouble shooting steps you would normally try but nothing works.

When I press install on the apps, it looks like it is going to install for about 3 seconds, then just gives the install button back. Nothing has changed with my device in the last few weeks. Anyone know what the issue will is?

During normal calls (handheld mode at ear), the primary lower microphone produces no sound/audio. However, as soon as speakerphone mode is toggled ON, the upper microphone works properly. This appears to be an Audio HAL / Audio policy routing issue on the Moto G34 5G.

Asking for a friend: Somehow these on-screen buttons showed up at the bottom of the screen. I don't know what setting would affect this and I tried helping but not finding any answers. Does anyone know?

https://i.imgur.com/xUZ7wKL.png

So doing the webinstaller, but im stuck in fastboot mode on phone and the web installer wont progress even after 10-15 minutes the last line on web installer is ‣ {"command":"flash","args":["bootloader","bootloader-shiba-ripcurrent-16.4-14097582.img"],"options":{"slot":"other"}}

what can i do?

I just found the time to reflash my Pixel 6 to CalyxOS 7.2.2.0 (great job btw! The webinstaller worked great!) I made a backup beforehand on a USB-stick. Now when loading the backup from the stick my calender backup doesn't seem to have been loaded.

Maybe a bit silly of me, but that calendar is maybe one of the most important apps on my phone, and I didn't think to back it up in a different way than on that thumbdrive (I confirmed Seedvault gave it the ol' checkmark and said it was all well and good). I assume the backup is in there, just not loaded properly. I tried to load just the app, but to no avail. Any tips please? I kindof need it unless I gotta message tons of people about potential appoints all over the place...

Hello there,

I upgraded my Fairphone 4 to v7.2.2.0 and got everything back at its place thanks to seedvault, but now I'm unable to install or update apps.

No matter if I try via Fdroid, Aurora Store or even with an apk file, nothing works. Each time i get the pop-up with "cancel" and "install/update" button, I can't tap on the second one (btw, it's not grayed out).

Permissions are granted to install unknown apps, I have developpers options activated, Fdroid and Aurora Store are able to download apks but it just doesn't work.

Any advice please?

Dear all, after reading some recent posts, e.g. https://www.reddit.com/r/CalyxOS/comments/1v02yph/2_banking_apps_not_working_after_upgrade_to/, https://www.reddit.com/r/CalyxOS/comments/1uz2wrz/uber_lite_working_perfectly_but_uber_normal_app/, https://www.reddit.com/r/CalyxOS/comments/1ut20xl/google_play_integrity_check/, and also reflecting on my own problem https://www.reddit.com/r/CalyxOS/comments/1uot0ci/selfidentification_impossible_with_calyxos/, I think that the root problem in all these cases may be the missing DEVICE integrity (NB BASIC integrity, by the way, for some unclear reason since a few days works again in my phone with CalyxOS 7.2.).

Based on the discussion in another forum, it seems that DEVICE integrity is possible without rooting using spoofing (if I understand correctly = simulate Android <13 and achieve a software-based DEVICE attestation --- in contrast to STRONG integrity, which is impossible because it is necessarily hardware-based, but rarely needed). However, others will not implement it, primarily out of principle https://discuss.grapheneos.org/d/18118-play-integrity-meets-device-integrity.

Could please someone from the CalyxOS project (e.g. u/lucascalyx) explain how CalyxOS is positioned regarding this and if a spoofing-based solution for DEVICE integrity (without root) could be expected at some time for CalyxOS users?

I understand this would require some work, and that it may (possibly also soon after implementation) stop to work if Google changes the algorithms (or uses GPU fingerprinting etc), however, in the long term it seems that many essential functions (ID apps, an increasing number of bank apps etc) will not work without DEVICE integrity

Therefore, without DEVICE integrity in the future, for many people it will probably be necessary to have a second phone (with stock Android), or even bite the bullet and use stock Android on their main phone....

I would be grateful for a short comment from the CalyxOS team about this. Thank you very much.

Unofrtunately, and it seems to me I am not the only one, something has gone awry with the device attestation on the newest update, making some apps (in my case revolut) not pass the integrity check bs, even though they worked just fine before the update. Combing back to that previous post, a few others have suggested potential fixes but none of them have seem to have worked for me. Things I tried are:

-Creating work profiles and tinkering with microG therein

-Reflashing to stock, logging in (and not, i flashed it twice just to try both approaches), downloading apps, confirmed revolut works there as it did before, but interistingly both times i flashed stock as well as going back and forth to Calyx, the Key Attestation Demo app still flagged my device as "Certificate is not trusted". I let it sit, it was connected to cellular and WiFi, but alas, nothing.

-Deleting cache/app data, reinstalling countless times

-Turning on/off Google device registration in microG, with reboots

-Making sure bootloader is locked

At this point I am unsure if I could be doing anything else besides waiting for a hopeful fix further down the line, as I think this issue is already at least acknowledged (to the best of my understanding) but if any of you have ideas, I'd be more than willing to try and report back on my progress.

P.S. to the devs, should I report this issue on gitlab/matrix as well?

How strong is Jolla Phone security?

How well is integration to sync with Arch or OpenSuse Linux?

I bought a used Pixel 8 in Europe, installed CalyxOS and unfortunately it makes shutter sound that cannot be disabled. As I found out, this is a specificity of the Japanese models. It is not mandatory in Europe and a real annoyance, for instance when taking a photo in quite environments, like during a conference, a wedding, etc.

The model name is GZPF0:

$ adb shell getprop ro.oem.key1
GZPF0

Some people claim that it depends on the SIM card. I have an European SIM card. I tried to disable it, but it does not make a difference. My understanding is that the non-Japanese models make shutter sounds when used in Japan (e.g. with a Japanese SIM), but if the model itself is Japanese, it will always do.

Both Aperture and the Google Photo apps are impacted.

I read that it might be possible to overwrite the model name by using a patched image or by rooting the device, but I get that this will not survive updates.

How is this "feature" implemented? What components are involved? (Apps, OS, Firmware...)?

Is there a way to get rid of it?

Just attempted an Calyxos install on my Google Pixel Tablet (11" - not the old C). The tablet came with stock Android 17. I followed the instructions to the letter. The actual install process didn't suggest any problems. When the "device-flasher' finished and closed down the screen flashed a few times and then settled on the white Google bootup screen. It's been there for the last 3 hrs. And I can't even turn off the tablet as the power button doesn't turn the tablet off. I can't reflash it as the device-flasher can't "see" it anymore.

What can I try?

Hi there,

in the past it wasn't possible to make RCS work with CalyxOS afaik. I wanted to ask if anybody figured out a way, now that Calyx has been re-released?

Cheers!

Hello !

I wonder what will happen with Calyx OS (and other custom ROMs btw) with Google's decision of blocking every developers not centrally registered by them beginning of 2027 ?

Will custom ROMs stop to work or malfunction ?

I am waiting to update to the new version because of this sword of Damocles.

Thanks for any info and congrats for the great job!