matchboxbananasynergy My phone can't find me on the map when i'm indoors while the iPhone can. Yes, Wi-Fi is enabled and yes, Wi-Fi scanning is enabled too. Log is the same as it was with first alpha release:

type: logcat
osVersion: google/husky/husky:15/AP4A.250205.002/2025030300:user/release-keys
package: app.grapheneos.networklocation:35, targetSdk 35
buffers: main,system,crash,events,kernel
level: verbose

--------- beginning of main
03-05 10:33:38.776  2040 12289 D TrafficStats: tagSocket(77) with statsTag=0xffffffff, statsUid=-1

      matchboxbananasynergy Right now yes. The result was the same in a low building too. Unfortunately I didn't take a look at the log when I was in a low building.

        I tried the location.. Waze was reporting I am at a gas station 10 km away, I was not there for years. Organic maps reported I am at the place where I used the app the last time. Google maps was correct. The same apps on ipad, same place, same time reported correctly.

        (I was sitting at home - appartment house, wifi on, connected, many many wifis around, gps not reachable of course - 5 floors above me)

        On my side I tried the location just now, indoor, WiFi activated, Grapheneos Proxy, correct position detected almost instantly. Organic Map and Magic Earth.

        Confirming P9PF with Magic Earth picked up my location in a basement about 30s after enabling this network service. WiFi and WiFi scanning are both enabled. Assuming it took some time to download the files, I killed magic earth, cleared cache and location locks pretty much instantly.

        I believe the disabling of trilateration broke the swiss public transport ticketing app "SBB easyRide".
        It's a service that tracks your location when "checked in" and bills you for your rides at the end of the day.
        Since the update, it says "location accuracy too weak", even though precise location is allowed.
        edit: can't figure out how to add screenshot. Here is the link: https://i.ibb.co/mCksjYz6/IMG-20250306-094050.jpg

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