Does the Graphene team strongly recommend always updating to the latest version right away for security purposes? I updated mine last month...not sure if that puts me at risk...
Is there a setting to allow the phone to automatically download only those GOS updates containing critical patches the Graphene team highly recommends?
K8y Basically every update either contains security updates or important bugfixes. It is highly recommended to always be on the latest release.
matchboxbananasynergy if I downloaded it in "beta mode" would I need to redownload again once it is in final ready status? (I only desire the final version).
Also is there an auto OS update feature in Graphene?
Thank you.
K8y *I wasn't sure since here it seemed to say updates are auto checked every 6 hours, but also says you need to go to settings then system update: https://grapheneos.org/usage#updates-security
K8y Updates are automatic. It downloads and installs it and then notifies you to reboot so that it can apply it. You don't need to anything other than that.
K8y if I downloaded it in "beta mode" would I need to redownload again once it is in final ready status? (I only desire the final version).
No, all releases are production releases, they just go through different release channels.
I'm experiencing two issues with the new stable release.
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.
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.
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)?
"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.
