I'm experiencing two issues with the new stable release.

  1. The new GrapheneOS wifi location services toggle is missing on other user profiles other than the owner. Does this carry forward to other profiles if enabled in the owner? I'm just confused because each profile still has the option to route location through play services instead of re-routing to the OS.

  2. Pixel camera getagging doesn't work at all on the owner after the update. I've tried every combination of using the grapheneos proxy, using apple directly, and turning off the Network location feature completely and reverting back to routing through google play services rather than the OS. Pixel camera appears to require Play Services to have location enabled just for the location notification to pop up when I open the app. But, even if it does pop up - which most of the time it doesn't -- it still doesn't getotag the photos. The GrapheneOS camera isn't having these issues nor is Pixel camera having these issues on other user profiles with location going through Play Services. I also wasn't having geotagging issues before this update.

    K8y There are no different versions in the sense you're thinking about, all releases are production ready. Even in the alpha channel you get the "final" version so to speak, only in the event problems are found is the release cancelled and a new one pushed as a replacement. Which means a new update to download and install for you.

    • K8y likes this.

      DirtyDan The new GrapheneOS wifi location services toggle is missing on other user profiles other than the owner. Does this carry forward to other profiles if enabled in the owner? I'm just confused because each profile still has the option to route location through play services instead of re-routing to the OS.

      It's global, so you set it in owner and it applies everywhere.

          matchboxbananasynergy What happens if you select to use the new wifi grapheneos proxy/apple, but don't re-route to the OS, keeping the setting on to route through play services (both on the owner and in other profiles)?

            DirtyDan I figured out the Pixel Camera issue. No idea why, but I had to re-install Pixel camera. It's working now. Neither Google Maps nor Pixel Camera requires Play Services to have location data in order to fetch my location.

            This is beautiful. Thank you GrapheneOS team!

              "Wi-Fi scanning" + "Bluetooth scanning"

              Since both functions could be activated in the past and were not grayed out (no Google services installed), I wonder what functions these two sliders had in the past?

                asd The toggles determine whether apps with Nearby Devices (partial Bluetooth scans) and Location (full Bluetooth scans and Wi-Fi scans) can do that when Bluetooth and Wi-Fi are otherwise disabled. The toggles functioned the same way as they do now. They aren't directly tied to any specific network location implementation or app. Our network location implementation works without Wi-Fi scanning enabled but won't work if you disable Wi-Fi without enabling Wi-Fi scanning since that's the whole purpoes of the toggle. It doesn't use Bluetooth devices yet. With sandboxed Google Play, it was possible to explicitly use their network location service using cell towers, Wi-Fi APs and Bluetooth beacons so both toggles were relevant to it. None of that is specific to sandboxed Google Play. Other apps can use the Location permission to scan for cell towers, Wi-Fi APs and Nearby Devices + Location to scan for Bluetooth beacons.

                    GrapheneOS if I'm understanding this correctly, if you're rerouting to the OS without any Google location services, turning the bluetooth toggle on right now won't benefit you until bluetooth locstion scanning is implemented by GrapheneOS?

                    Would turning this on erode battery life since it's still scanning for bluetooth connections (even if it can't find any)?

                        DirtyDan GrapheneOS currently only uses Wi-Fi APs for network location.

                        Would turning this on erode battery life since it's still scanning for bluetooth connections (even if it can't find any)?

                        No, this toggle only allow apps with Nearby Devices + Location permissions to do Bluetooth scans while Bluetooth is otherwise off. Wi-Fi toggle similarly only allows applications with the Location permission to do Wi-Fi scans while Wi-Fi is otherwise wise. Both toggles only have to do with using them for scans while you have them turned off. Neither needs to be enabled for scanning if you always have them enabled. They exist to allow scanning for location detection without having them turned on. On the stock OS, they're on by default.