GrapheneOS version 2024091900 released

tastical

I got it and it did fix the data issue on Google Fi & Pixel 4a 5G, thank you.

ErnestThornhill

Everything runs perfectly fine. 👍

GrapheneOS

Sirut We're not aware of any issues as long as it's set up via the eSIM management app in the OS. If it's set up in another OS and not wiped, some manual setup is required to have it working properly.

Sirut

GrapheneOS seems like someone had issues when had 2 SIM (1 phisical + eSim) to receive calling.
Here a discussion

H4M

While this did fix my KDE Connect error, I am now getting a lot of 'System UI is not responding' prompts.

I am unable to reproduce, it just happens after a while when opening various apps.

When tapping 'Show details' nothing is happening (that's how I got the KDE Connect logs last time around), when tapping 'close app' the entire system is crashing to a black screen and I have to force a shutdown.

I also believe my battery is draining rapidly, Settings seem to indicate KDE Connect is the culprit, but I am not sure if this is just paranoia. Will keep an eye on it.

GrapheneOS

H4M That's not caused by this update but rather something else.

Sifer

GrapheneOS

OK. I have been running the beta for a couple of hours now (Pixel 5a). Calls have been working as expected. I can call voicemail too but visual mail no longer works. As of now I am just happy that I am able to make call and get them.

Perhaps the issue deals with VoLTE or something!?

Thank you for the rapid response/update/fix.

H4M

I get constant 'System UI is not responding' prompts on this version, to the point my login screen keeps crashing to a black screen and makes the entire phone unusable. Thankfully, the power menu still comes up so I can force a reboot.

I have uninstalled KDE Connect, and have not experienced this issue since.

Something is still not behaving like it should. 2024090400 did not have this issue.

matchboxbananasynergy

H4M Can you confirm which version of GrapheneOS you are on? 2024091900 or 2024091700?

H4M

matchboxbananasynergy 2024091900

de0u

H4M 2024091900

Which device?

H4M

de0u Pixel 6

Eirikr70

Impressive reactivity from the GrapheneOS dev team ! I suppose you have a team in America, one in Asia and one in Europe so you can work 24h a day. Smart from you ! ;)
Thanks a lot !

de0u

Eirikr70 I suppose you have a team in America, one in Asia and one in Europe so you can work 24h a day.

It is common knowledge that Ars Technica publishes from their "Orbiting HQ" and their coverage is thus not constrained by landlubber time zones. I wouldn't put that past the GrapheneOS team.

maukazius

why do you have the revert multicast leak blocking if it only affects the pixel 5? All other Pixel users now have multicast leaks again. Great.
I would like to understand the decision why the pixel 5 users are still so important?

other8026

maukazius It's my understanding that there were other issues with app compatibility that need to be addressed, so the feature was rolled back for all devices.

GrapheneOS

maukazius It caused app compatibility issues on other devices and IPv6 network compatibility issues. It only broke mobile data on 5th gen Pixels, sure. It's going to be hard to ship it because public testing isn't working well.

deadlenin

With the 19 Release, I don't have internet access any more on the cellular side. In order to have Internet access I have to enable WIFI and select a WIFI network. Mobile Data is already enabled.

GrapheneOS

deadlenin You're probably not on this release yet but rather the last one.

deadlenin

GrapheneOS
It shows 2024091900 under the Build number. I switched to Beta and ran the update yesterday because of the inbound/outbound call issue. Didn't notice the mobile data issue until this morning. I'm on a 5a if that makes any difference.

deadlenin

GrapheneOS Just following up on this, turns out AT&T put a data block on my number when I switched my sim to one of my 3G phones after the 17 update. Everything's good now.

H4M

GrapheneOS Given nothing was changed except for the update, I doubt that. Thanks for getting back to me though. Zero issues after I uninstalled KDE Connect, so seems like GOS is incompatible with that application for the time being with 'Always-on VPN' and 'Block connections without VPN' enabled (communication between mobile/desktop devices happens via VPN connection).

Murcielago

I use several profiles. If I turn on VPN in the owner profile settings> Network and Internet>VPN> enable Always-on VPN network connection works fine in owner profile.

But if I switch to a user profile (the problem occurs in all my user profiles), I have no network access in user profiles. In the setup I described, VPN is only installed in the owner profile.

The problem occurs with and without kill switch (VPN> Block connections without VPN) enabled.

If I deactivate Always-on VPN in the owner profile, network connection works fine in all profiles.

May this have something to do with this change? (To be honest - I don't understand exactly what this does - it's just the only thing that from a layman's perspective might have something to do with it - please correct me if I'm wrong):

add netfilter-based multicast firewall only permitting sending multicast packets to permitted interfaces for the process to prevent apps sending multicast packets through a disallowed interface such as a VPN tunnel for another profile

source: https://grapheneos.org/releases#2024091700

I don't use VPN regularly- always thought that I can use VPN independently in every profile...

setup:
Pixel 9 Pro
build number: 2024091900
Proton VPN version 5.5.68.0
Not using KDE Connect as described by H4M

« Previous Page Next Page »