binom it's probably specifying a low power level or the network location provider specifically. Trilateration is still enabled, it's rather 3D trilateration that's disabled which does result in lower accuracy due to the real world not being 2D.

I have a work-in-progress new algorithm implemented in Rust that achieves far better accuracy and is faster than the current algorithm, even though it's always running in 3D. For measurements that don't have an altitude, it tries to calculate it which results in far better accuracy.

      soupslurpr that algorithm sounds awesome!
      what i don't understand is why it only stopped working after this update now, before it worked flawlessly. logcat sadly has nothing informative as far as I can tell. Here it is anyways, maybe you see something in there: https://pastebin.com/MbevYZt7

          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

          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?

          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"

              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.

                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?

                      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.

                            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 replied to this.
                            • fxnn likes this.

                                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?

                                    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 replied to this.
                                    • de0u likes this.

                                        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 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 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 thank you for taking the time to look at this at all! and good luck with your crazy new algorithm!

                                                    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.

                                                      @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 :(