Hi Fedi. I have a question about @GrapheneOS
Some acquaintance of mine tried to install GrapheneOS on Pixel 8a and encountered a weird problem.
Apps doesn't have internet on WiFi if you do not enable "nearby devices" access for them.
Some apps like GrapheneOS store doesn't have this setting so no internet on WiFi at all.
What can ever be a reason and how can it get fixed? 
0 Boosts
0 Likes
@yura Android apps with no reason to access local network addresses should not add it as a requested permission.
It works the same way on the stock Pixel OS and other up-to-date Android devices. Most Android devices lack current standard privacy and security patches/protections. Comparing GrapheneOS to out-of-date Android forks by OEMs is the wrong way to compare the behavior. Comparison should be against an up-to-date Android 17 OS. 17 QPR1 and 17 QPR2 are Pixel OS exclusive for now though.
@GrapheneOS from the words of the person, everything seems to work fine on both stock android and LineageOS (which is, I understand, outdated).
But the issue with GrapheneOS still exists.
It also existed at the beginning of September during the previous (failed) attempt of using GrapheneOS.
But the issue with GrapheneOS still exists.
It also existed at the beginning of September during the previous (failed) attempt of using GrapheneOS.
@yura There's no stock Android. There's the stock OS on specific devices which is usually far behind the current Android version. If they haven't tested on the Pixel OS or a build of current AOSP then they're not comparing to a standard up-to-date Android OS.
It's extraordinarily unlikely that it's an issue caused by GrapheneOS. It could be an upstream AOSP issue also impacting the Pixel OS but it's equally likely that there's something very wrong with the network uncovered by Android 17.
@GrapheneOS hmm. It seems like the reason is this bug
1. The issue is with a specific WiFi in the home they rent
2. Everything works on mobile data
3. Everything works on VPN
https://www.androidauthority.com/android-17-wi-fi-3678670/
https://www.reddit.com/r/GooglePixel/comments/1u9l7fq/anyone_having_wifi_issues_after_updating_to_17
1. The issue is with a specific WiFi in the home they rent
2. Everything works on mobile data
3. Everything works on VPN
https://www.androidauthority.com/android-17-wi-fi-3678670/
https://www.reddit.com/r/GooglePixel/comments/1u9l7fq/anyone_having_wifi_issues_after_updating_to_17
@yura It looks more like an issue with the Wi-Fi networks redirecting traffic to local network addresses which can no longer be accessed by apps targeting Android 17+ without the Nearby Devices permission group. A permission for accessing local network addresses was added to Android 17 and legacy apps are granted that access by default for backwards compatibility. Most apps still don't target Android 17 but will be forced to do so before the end of 2027 by the Play Store as usual.
@yura There's no difference between GrapheneOS and standard Android 17 when it comes to this. Nearby Devices is not required for internet access. Apps targeting Android 17 or later require Nearby Devices for local network access. They don't require it to use the internet via Wi-Fi. It sounds like the network may be tampering with DNS results and trying to redirect traffic in a way that's visible through using local addresses. It wouldn't impact internet access on a normal network at all.