- Edited
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?
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?
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.
deadlenin You're probably not on this release yet but rather the last one.
H4M That's not caused by this update but rather something else.
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.
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.
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).
Update: a combination of rebooting/uninstalling/installing has done the trick, and everything is working again.
H4M Do you notice battery consumption when using KDE Connect
Every new release the square button to show background apps is broken and doesn't work after a few hours, I cannot reproduce it with an specific thing but it happens all the time, any idea how to fix this? it's really annoying.
gonzalo would be helpful if you say which device you're using
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
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.
So multicast fix coming to Pixel 5a (5G) at some point later or not? I've been waiting for that for that fix for a while...
YCjHK18 later, after investigation
YCjHK18 See the note before the tags and changes listed for the 2024091900 release: https://grapheneos.org/releases#2024091900
The important part:
We've moved 5th generation Pixels to legacy extended support around a month early since we're not getting the feedback we would need to have confidence in shipping the next round of multicast leak blocking for them. They're insecure legacy devices regardless.
Based on this note, and what was said by developers in the alpha/beta testing room, I believe 5th generation Pixels are most likely not going to get a fix for the multicast leak when the next attempt is made.
AlphaElwedritsch Usually no, after the update it was draining my battery quickly. Since the reboot/uninstall/reboot/install/reboot song & dance, it's back to normal.