GrapheneOS version 2025030300 released

ThP

Joining @binom as I am experincing the same issue.
I was able to get it pass the "location accuracy too weak" (not sure if I enabled the WiFi scanning), but the app is still not able to get the location, and displays the message "Determining location..." forever

ThP

On "Services" I tried to disable the network location, but still the same issue.

Any way we can help you @soupslurpr in identifying the issue?

binom

soupslurpr this has actually gotten me past the "location accuracy too weak" error. Network location under Settings > Location > Location services was turned off, and changing it to "GrapheneOS Proxy" got me one step further. But now the app is stuck on "Determining location..." forever. So I guess it's the same issue that @ThP is having now.
Steps I tried so far, to no avail:

disable my VPN
disable my private DNS
turn on Wifi and Bluetooth scanning in Settings > Location > Location services
tried "Apple" and "GrapheneOS Proxy" for "Network location"
tried "Exploit protection compatibility mode" for SBB App
tried switching SUPL and PSDS to "Standard Server"

soupslurpr

binom Franco could you both try disabling network location, going into a Maps app, getting a location there, then immediately go into that ride app?

Franco

I am not using the Easyride option of the SBB application, but I just gave it a try after reading the messages above and I confirm the same symptoms as Binom, stuck on "Determining location...". But I don't know if it was working better before.

ThP

soupslurpr Following your scenario: I got the "location accuracy too weak" message on the App (see screenshot shared here: binom )
From that screenshot: the app has a "Change location permission" button, which usually lead to the OS location settings. Clicking on that button does nothing (but it used to work).

Enabling the "Network location" under Location Services, I get again the "Determining location..." spinning forever.

Note: I configured GrepheneOS to use all Location services from Graphene proxy.

Franco

soupslurpr Hi, I just tried this:

Network location disabled
opened Organic Map and waited fot GPT to capture the exact location
immediately went to SBB Map and launched EasyRide
-> Ooops, location accuracy too weak. In order to record your journey properly, Easyride needs your location services to be highly accurate. Please adjust this setting.

And like THP, "From that screenshot: the app has a "Change location permission" button, which usually lead to the OS location settings. Clicking on that button does nothing (but it used to work)."

soupslurpr

ThP it's likely it's just that one app that's having issues because it's just not written well. There are a lot of bad reviews for it. I haven't seen similar issues with any other app and it doesn't really make sense if it's still happening after doing what I said.

ThP

soupslurpr the application has been working flawlessly with GrapheneOS latest's versions (I used the app last week, before installing the newest GrapheneOS release, and it worked fine).
And the application was not updated in the between.

Is it be possible to locally rollback to a previous release of GrapheneOS, to exclude that the new location changes in GOS are affecting it? I was not able to find any documentation on how to do it 🤔. Anybody can help here?

soupslurpr

ThP rolling back to a previous release isn't possible without a specific rollback update being made. This is so attackers can't just roll the device back to a previous version that doesn't have the latest security updates.

ThP

soupslurpr yeah. makes sense in that scenario.
How can we support you in digging into that issue? any other tests or logs we should provide?

In my case the issues with that application is quite a problem, as I daily use it :(

soupslurpr

ThP hm, maybe could you try and let me know how disabling rerouting location requests to the OS (follow https://grapheneos.org/usage#sandboxed-google-play-configuration) affects it? If it still doesn't work, then I think it may really be an app issue.

Franco

soupslurpr Just tried this as well:

disabling rerouting location request to the OS
allowed precise location
and still symptoms are the same, but the Change location permission" button becomes clickable. Maybe the application is specifically looking for Google Play Services.

(now I reversed all these changes)

soupslurpr

Franco unfortunately I'm all out of ideas then.

binom

soupslurpr thank you for taking the time to look at this at all! and good luck with your crazy new algorithm!

binom

As a general update to the SBB EasyRide issue:

apparently, "Network Location" under Settings > Location > Location services is a requirement for the EasyRide feature to work. Disabling it reliably causes the "location accuracy too weak" error.

As @ThP and @Franco mentioned, the "Change location permissions" button does nothing when tapped.

There is a location based timetable in the same app, which still works without issues, even though the EasyRide part is non functional.
This reminded me that EasyRide is a service that's actually integrated to the SBB by a third party, called Fairtiq. They also have their own app, just called FAIRTIQ. I tried downloading that one and signing up for an account. After registering, it is showing exactly the same behaviour as the SBB App:
With Network location disabled, it's showing "Limited access to your location" with a link to a generic help article. With it enabled, it's stuck on "Searching for stations..."

Sadly both apps don't seem to write anything useful to the logcat logs.

Franco

binom Hi, it looks like EasyRide could be functional again.
I can't test the feature because i don't use it, but the error messages disappeared with the last update 2025030900.

ThP

@binom @Franco do you have any contact with any Fairtiq app developers? maybe we can poke them?
From the analysis it looks like the new GrepheneOS Location feature (overtaking the G location service) is sadly causing the issue :(

binom

ThP sadly not. Have done some more digging to come to this conclusion?
I can definitely also just contact them through their support form at https://support.fairtiq.com/hc/en-us/requests/new (or apparently preferrably through their app). I just fear it will be another "we don't support custom ROMs" kinda conversation...

angela

I have this build and sometimes use location when in airplane mode to navigate (without being subject to surveillance capitalism, since with the cellular modem on the data of the relative position to the cell towers be sold).

I recently used an open-sourxe map application. The location is usually slow to be detected, taking over a minute. Recently it took so long, I gave up. I was in an area without much cellular reception and it's possible this is not related to the new update, so no github issue is being created, and I have no logs or errors to share. I am guessing location stuff is being worked on while the new feature is rolled out and it will get smoothed out over time.

DeletedUser370

angela This might be of interest: https://discuss.grapheneos.org/d/15245-gps-location-doesnt-work/3

The phone has to download various datasets that help to resolve the location in the future. so having a network connection also helps speed things up. Without any network connection the phone will pick up the PSDS almanacs that are very slowly broadcasts directly from GNSS satellites, takes more than 5 minutes. If you have an internet connection it will quickly download these almanacs.

Murcielago

angela

I have this build and sometimes use location when in airplane mode to navigate (without being subject to surveillance capitalism, since with the cellular modem on the data of the relative position to the cell towers be sold).

I'm confused - if you're driving/walking in Airplane mode - you use WiFi or how are you connected to the internet?

Just to clarify: To use Network Location you need to have an internet connection:

...When using the recommended proxy mode, it sends location data (nearby Wi-Fi networks and also cell towers when we add it) through an HTTPS connection with pinned TLS keys (Let's Encrypt roots and our backup leaf keys) to a GrapheneOS server which then sends them to Apple.

source: https://discuss.grapheneos.org/d/20369-grapheneos-version-2025022700-released/76

Or rather: Will not work yet: GrapheneOS seems to build their own database which could be downloadable in the future:

We're building our own database of Wi-Fi networks and cell towers in order to provide our own service. Our service will also have offline support added to it similar to how you can download maps for Organic Maps to use offline. You'll be able to download a database of Wi-Fi networks and/or cell towers for an area from our service for offline usage.

source: https://discuss.grapheneos.org/d/20369-grapheneos-version-2025022700-released/78

an open-sourxe map application

Unfortunately, this description is quite imprecise. If you describe errors, it would be helpful to name the app and version number - it makes it a lot easier for other users to understand, verify the error by themselves and jump im to help you.

Murcielago

angela

Thanks for sharing more information about the app you used.

The discussion here was mainly about the network location feature recently implemented in GrapheneOS, which currently requires an internet connection for faster positioning. That's why i was confused about you're post.

Of course you can only navigate with GPS. However, this can lead to the problems described by DeletedUser370 and network location won't (yet) work with your setup.

« Previous Page Next Page »