GrapheneOS version 2025031400 released

GrapheneOS

GrapheneOS version 2025031400 released:

https://grapheneos.org/releases#2025031400

See the linked release notes for a summary of the improvements over the previous release.

DeletedUser216

GrapheneOS updated from 2025030900 to 2025031400 and fingerprint is broken again. whats wrong with latest grapheneos updates? so much bugs...
Pixel 9

JoeAverage64

GrapheneOS

NO problems here with an P8 !
Thanks for support

Berlino

"Sandboxed Google Play compatibility layer: add back default values to the API definitions for our reimplementation of the Google Play location service since dropping them broke compatibility with a subset of apps..."

A big thank you for this update and I can confirm, NINA warn app now locates my position without the need of Google Location Accuracy, fully switched to Graphene Location services.👍

fid02

DeletedUser216 updated from 2025030900 to 2025031400 and fingerprint is broken again. whats wrong with latest grapheneos updates? so much bugs...

https://discuss.grapheneos.org/d/20636-workaround-for-android-15-qpr2-fingerprint-firmware-glitch-on-pixel-9-non-pro

GrapheneOS

DeletedUser216

and fingerprint is broken again

GrapheneOS has not done anything which either broke or fixed anything about the fingerprint reader. You're very likely on a Pixel 9. You can do a Google search "pixel 9" "march update" fingerprint and find news coverage of the regression impacting some Pixel 9 users. GrapheneOS did not cause this and the fact that it comes and goes with reboots has nothing to do with updates. You're wrongly blaming us and wrongly blaming our updates. Example:

https://www.androidpolice.com/google-march-update-fingerprint-problems-pixel-users/

whats wrong with latest grapheneos updates?

Nothing is wrong with the recent updates. Android 15 QPR2 fixed many issues and introduced a few new ones, but overall things are much better with it.

so much bugs...

Hardly, and nearly all of them are upstream bugs. Aside from that, why are you updating to releases in the Alpha channel if you can't tolerate regressions? The last release didn't move beyond Alpha because of a regression fixed in this one. That's how our update system works. We avoided any serious recent regressions reaching Stable.

User712890

On this update, I have gotten a random black screen on my P6a twice in the last 3 hours. The device is not reacting to anything until a force reboot. It happens without user action. Can I send logs?

DeletedUser216

User712890 Same problem with Pixel 9.

rlw63ig0

Looks like the fingerprint issue is resolved on this release. My only problem now: not able to connect to my data immediately. Took multiple reboots, multiple turning on/off mobile data but finally connected after several hours. Worked just fine before. To test to make sure i'm not crazy, i rebooted and it again wasn't able to connect my data provider until about an hour later. So it's connected now but I'm afraid to reboot or turn off/on data. Anybody else experiencing this?

GrapheneOS

rlw63ig0 The fingerprint issue is an upstream issue likely in the fingerprint scanner firmware which comes and goes with reboots. It's not gone but rather reboots make it go away and come back since it causes the fingerprint scanner to be a bit flaky and not always show up on boot. It primarily only seems to impact the non-Pro variant of the Pixel 9. There are some reports of similar issues on other devices but they seem very rare and may not be the same issue at all.

ErnestThornhill

All is running well on my 9 Pro XL, 9 Pro Fold and Tablet.

Eirikr70

Everything fine for me on a P6a. Thanks for the great job!

grapheneosuser294783

@GrapheneOS I see you can map a port now, I tried doing what I did before, setting '2222' to sshd, however I am still unable to SSH into the terminal directly.

Do the ports get exposed outside the VM? I.E lanip:2222? Or are the ports listening to the VM only?

If somebody has managed to get SSH working into the terminal I'm interested how you made it work.

Carpool7341

Would it be possible to, at some point, add an option to do the second, background, app recompilation at full throttle? I prefer to wait until all the apps are done and restarted before using the phone and if I leave it running with the phone locked, it does it so much slower than if I keep the screen awake...

fid02

Carpool7341 I prefer to wait until all the apps are done and restarted before using the phone

Could I ask why? I've read that some users always do this, but I don't understand why. Is your device performing very poorly during "optimizing apps"?

Carpool7341

fid02 I wouldn't say it's performing poorly, but it's obvious it's working hard... The battery is being used up faster and it stays warm. Also, I guess, the security benefits of a full compilation aren't there.

guser39

This update changed the system language for quick setting tiles and dates to a secondary language.

Steps to resolve:

Switched system language to secondary language then back to my primary language. This fixed the quick tiles but not the system date, which still displayed using the secondary language.
System reboot. This restored the dates, too.

Watermelon

guser39 You don't need to change any settings. Please see: https://discuss.grapheneos.org/d/19518-grapheneos-randomly-changes-the-device-language

guser39

Watermelon what specifically should I be taking away from that 34 post long thread?

Watermelon

guser39 Most importantly that the thread has existed way earlier than this update