It's a diiferent app and the problem is probably different - but trying to solve it @soupslurpr , who seems to be involved in developing the location network feature, walks two guys through some steps of which one might solve your problem:
https://discuss.grapheneos.org/d/20480-grapheneos-version-2025030300-released/10
pyro I just installed the app, gave it all the permissions it requested, enabled "current location", and I don't get the error message. The system says that it's using location services.
This is my setup:
Pixel 6a
GrapheneOS 2025030700
Play services 25.08.32 (not sure if that's relevant)
Before installing the app:
I didn't adjust these settings after installing the app.
Try disable memory tapping and allow dynamic code loading. I need to do it with OsmAnd on P9P to get location to work.
@fid02 I see the exact same on a spare phone. Fresh install of GrapheneOS, Reroute location requests to the OS active and NINA works.
On my primary phone (that I switched from Google to the internal provider) I get "Ortungsdienste deaktiviert", even after a reinstall of the app. Fun fakt: NINA does not even ask for location permission before displaying the error.
The only explanation I have is that some Google specific remnant stayed behind after the switch and somehow NINA is the only app that gets triggered by that.
Berlino You appear to have location rerouting disabled which is why you need the Google network location service. You can enable our network location service instead (turn on Network location and also Wi-Fi scanning to make it work with Wi-Fi off), re-enable location rerouting (it's enabled by default) and revoke Location from Play services. This app probably requires network location but we have our own implementation now so you don't need to use the Google Play services one.
GrapheneOS
Thank you for you answer, location rerouting already is enabled and I totally switched to graphene location service. All location-related apps work like a charm with graphene's service, but NINA additionally needs Google Location Accuracy activated for working service. I think some google fragments are left after switching from google location to graphene location service. Location permission for Play services are denied as well.
Berlino Did you try reinstalling the NINA app?
GrapheneOS
No, but I deleted data and cache for NINA on P8 and set it up again with same result. Maybe it has to do with formerly registration for gcm and these fragments are still active/required for NINA to work!? I experience the same as @pyro
I'm going to try a reinstall for NINA and test it.
A reinstall of NINA ends with 'please wait, NINA is being setup' followed by a message stating an error while registering (Google Location Accuracy switched-off this time).
GrapheneOS I did. Same issue again. It claims "location disabled" before even asking for location permission.
From the 20250313 changelog:
Sandboxed Google Play compatibility layer: overhaul our default enabled reimplementation of the Google Play location service (location request rerouting) to provide much better compatibility for apps depending on network-based location by always telling apps that the Google Improve Location Accuracy toggle is enabled and providing fallback to GNSS for low power location requests when the OS network location service is disabled as it is by default (unlike Google Play services, which has no fallback, but apps assume users enable the feature)
This reads very much like it could solve the issue.
Should be resolved.
