GrapheneOS version 2024120900 released

GrapheneOS

GrapheneOS version 2024120900 released:

https://grapheneos.org/releases#2024120900

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

FlipSid

GrapheneOS does this include "everything" from 2024120700 for the Pixel 7 Pro?

decadentist

CarrierConfig2 (app created by GrapheneOS to replace Google CarrierSettings): add support for new ICCID MVNO type in Android 15 QPR1

Does this mean, that non Google approved mobile network providers work with VoLTE or 5G? I can't test it yet, cuz I'm still on 4a.

If yes - this is worth a donation.

locked

decadentist The project is worth a donation anyhow, I say.

spring-onion

FlipSid Elaborate? Updates all build upon another, the improvements and changes are typically here to stay unless they introduce or cause (substantial) bugs.

GrapheneOS

FlipSid Every installation of the same OS version on a device model is identical. The update ships the whole set of firmware and OS images. It ships only the differences from the version you were on to the new version if you didn't fall very far behind, but the end result is an identical set of firmware and OS images. There's no such thing as applying some of the updates but not others.

FlipSid

spring-onion I mean I was waiting for the 2024120700 to come through the channel, but when the update came it was 2024120900.
I figure they would build on each other, just felt I would ask for peace of mind :)

Grafeen

This update unfortunately removed all my PWAs and shortcuts again. I won't be adding them back until this issue is fixed, because it's annoying having to add them again after each update.

The issue seems to be known / acknowledged by the developers, for anyone who's interested: https://github.com/GrapheneOS/os-issue-tracker/issues/3677

GrapheneOS

Grafeen It's not a GrapheneOS issue but rather an Android issue.

BuckWylde

Did anyone's Android Auto stop working properly after this update? Everything was working fine yesterday, then today after the update my phone connected to my car no problem but it was as if the audio was muted even though it wasn't. I was able to play from regular bluetooth connection but not through AA.

yore

BuckWylde This is a known temporary issue.

Android 15 QPR1 introduced a bug requiring the Microphone (record audio) permission for routing local audio too. It impacts Android Auto on both GrapheneOS and stock OS, but only users on GrapheneOS will notice it because the permissions aren't granted by default.

https://grapheneos.social/@GrapheneOS/113629803646184979

Our next release will have a fix for this issue to avoid the audio recording permission (Microphone) being needed.

If you need this feature and don't use the voice features for Android Auto, you can choose if you want to work around it by temporarily granting it this access.

https://grapheneos.social/@GrapheneOS/113629804204322533

BuckWylde

yore

Thanks for the info. I'll give it a shot tomorrow morning.

raccoondad

Pixel 6a user here, a lot of things look different in this update, very confused, was there a UI overhall? My settings looks completely off

My Material You colors are weird as well, icons look...smaller?

My material you speifically is slightly off colored, was completely wrong for a few minutes as well. Still optimizing however

Probably9857

raccoondad

Android 15 QPR1 introduces a Material You Settings redesign.

Themed icons are appreciably lighter than before, especially the circular background, when dark mode is enabled.

https://9to5google.com/2024/12/05/android-15-qpr1-december-pixel-update/

decadentist

locked

I already donated multiple times when stuff got implemented on my wishlist. Just wanted to say this would be donarion-worthy :-)

raccoondad

Probably9857

Ah, I see....

Haiku for GOS per update, #5:

My phone restarted
New design, pants shitted, help
checking changelog

grapheneos-enthusiast

Probably9857 I really thought that the new themed icons were a bug

h-2

My WiFi stopped working in a weird way on my newly installed Pixel 9 Pro:
It connects to the WiFi, but DNS is broken for some domains, works for others (I couldn't figure out a pattern yet). Furthermore, I cannot reach local IPv4 addresses via the browser. Certain network related apps (e.g. port authority) claim that I am not on a WiFi.

I am suspecting something to do with IPv6. The WiFi settings show that I have an IPv6 address and the DNS server has one, as well.

Other devices in the LAN, including an older GOS phone (not rebooted into this update) exhibit no problems.

lululu

h-2 google photos editor mode still not working

Blueman32

The new settings page is awful and ugly please make it look better like it was before.

Looks awful

redfoxjumper

Blueman32

Hard disagree. I find it easier to locate stuff.

Aquathing

Blueman32 I honestly like them more, it's way easier to find stuff without relying on the search function

Exhort14

Blueman32 Upstream change, not a GOS change.

Berlino

With this update on my P9P the IMS registration is gone for Deutsche Telekom (T-Mobile), so no VoWiFi/VoLTE works atm. In settings menue for SIM and APN everything is set as it should, but ##4636## IMS status shows not registered for IMS, VoLTE/VoWiFi not available.

Berlino

Berlino
Everything works as expected...it was my own fault, having activated/checked 'ims' in APN settings de-registered me for IMS service. Reverted it and VoWiFi/VoLTE are working as expected again. The best of all: no more fiddling with Shizuku/PixelIMS for activating WLAN-call after every update.

n2gwtl

With this update, fingerprint login when switching from secondary profile to primary user profile is not working. It works fine from primary to secondary. Pixel 8 pro

SerenityNow

n2gwtl Isn't that how it is supposed to work? To protect the primary user who is like the admin?

JollyRancher

n2gwtl

On the Pixel 9 Pro you can switch from a secondary profile to the owner profile via biometrics without issue.

Eagle_Owl

n2gwtl
Not for me.
I can switch in both directions on both Pixel phones, where I use two profiles: Pixel 7 Pro and Pixel 8 Pro.
Maybe it's an issue with the recognition of your fingerprint?
If a reboot doesn't help, I recommend to repeat to store your fingerprints and use both thumbs for that.