@GrapheneOS

I still can not understand how new GrapheneOS feature works. I have enabled "Network Location - GrapheneOS Proxy" and allow Wi-Fi Scanning. But when i try Osmand it can not find my location (With Wi-Fi Off).

Can you explain, please?

    Serg I still can not understand how new GrapheneOS feature works. I have enabled "Network Location - GrapheneOS Proxy" and allow Wi-Fi Scanning. But when i try Osmand it can not find my location (With Wi-Fi Off).

    You still need an active network connection for the Network location feature to be able to pull the data (WiFi access points) it needs to determine your location. If WiFi is off, then you need an active mobile data connection.

    In the future, when an offline database feature is shipped, it sounds like you won't need an active network connection to get a location fix without GNSS, but WiFi scanning will still be needed in that case. I think.

        Hi GOS team, when I restart my Pixel 7a I get an error message with G Play service

        type: crash
osVersion: google/lynx/lynx:15/BP1A.250305.019/2025032500:user/release-keys
package: com.google.android.gms:250934035, targetSdk 35
process: com.google.android.gms.persistent
processUptime: 1002 + 661 ms
installer: app.grapheneos.apps
GmsCompatConfig version: 154

java.lang.NullPointerException: Attempt to invoke virtual method 'void android.app.StatsManager.setBroadcastSubscriber(android.app.PendingIntent, long, long)' on a null object reference
	at com.google.android.gms.common.subscriber.AnomalyConfigIntentOperation.onHandleIntent(:com.google.android.gms@250934035@25.09.34 (260400-738842635):110)
	at com.google.android.chimera.IntentOperation.onHandleIntent(:com.google.android.gms@250934035@25.09.34 (260400-738842635):2)
	at aott.onHandleIntent(:com.google.android.gms@250934035@25.09.34 (260400-738842635):8)
	at sgs.run(:com.google.android.gms@250934035@25.09.34 (260400-738842635):70)
	at sgr.run(:com.google.android.gms@250934035@25.09.34 (260400-738842635):152)
	at fhby.run(:com.google.android.gms@250934035@25.09.34 (260400-738842635):21)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:651)
	at java.lang.Thread.run(Thread.java:1119)

        interesting thing happened: after update finished but BEFORE reboot - suddenly most of the system interface switched to my second system language, which has never happened before.
        after reboot into the new version system interface reverted back to first system language (english)
        how? why? what??

          After updating to latest release my location is no longer working on both my pixel 8a and 9. I've not changed any settings since it was working. Is anyone else having this issue?

            legendaryD on my pixel 8 its working (tested with google maps)

            What settings do you have?

            I have SUPL und PSDS grapheneOs proxy
            and for location scanning all off (wifi scanning, bluetooth scanning, network scanning)

                SIGSEGV suddenly most of the system interface switched to my second system language, which has never happened before.

                Same, but it's not a regression for me, as it's happened several times in the past, and I'm not sure when exactly it happens. It might correlate with a system update but I'm not sure. Would likely take a lot of time to try to find a reliable way of reproducing it. It doesn't have anything to do with guest profiles as someone else stated in a different thread.

                    suddenly most of the system interface switched to my second system language, which has never happened before.

                    I noticed that this occurs when I disable Developer options. It's a reliable way to reproduce the bug for me. But not sure we're talking about the same bugs.

                    Sometimes difficult to ascertain whether or not something was caused by having Developer options enabled. Here's an example of a bug that triggers when the user disables Developer options. LOL.

                    I'm guessing that disabling Developer options somehow triggers a resort of the preferred system languages list, and that languages that do not have AOSP translations – but that are still selectable from the Settings UI as "non-system" languages – get downprioritized due to… some logic. It's probably refreshing that UI anyway because it needs to get rid of the pseudo-languages that are only displayed when Developer options are enabled. Anyway, seems pretty niche.

                    Edit: This is unlikely to be a regression, so kinda offtopic here.

                    Everything works fine here on my Pixel 6 without any Google stuff.

                    fid02 ah, good to know i was not hallucinating)
                    it took me a while to realize that something is different, then I was guessing if it was always like that)

                    i dont know what caused it for me - i've not touched developer settings