How to run google maps on GrapheneOS?

Mikaelson

Hi, I’m completely new to this forum and just a few days ago I installed GrapheneOS on my Pixel 9 Pro XL, but I haven’t switched over yet because I’m missing Google Maps. I installed Google Maps, Google Play, Google Framework, and other Google services all in a separate profile with a brand-new Google account, and I granted all apps every possible permission like network, sensors, location, and unrestricted battery usage. Nevertheless, Maps can’t find my location, and I absolutely rely on Google Maps—otherwise the smartphone is useless to me. It worked briefly once and then not the next time I started it, maybe because GrapheneOS was updated? I’ve already reinstalled the apps multiple times and even deleted the entire profile and set everything up again, but it just won’t work, and I’m getting totally desperate and frustrated. Could someone give me a foolproof step-by-step guide on how to finally get Google Maps running? Many thanks in advance.

edebbbb

Mikaelson Google Play Services is the one that needs location permissions

de0u

Mikaelson Is the GrapheneOS network location service enabled?

someone27281

Mikaelson

Everything should work as is with location enabled and the info that is already in the thread, but in case nothing works u can turn off location rerouting (in sandboxed gplay settings) to get a much faster lock (for some reason) on GMaps. Once u turn it off under the potential issues Geolocation will be shown, and just follow those instructions to properly enable Google's location

mortuary_jab

edebbbb I don't think so, I have Maps with location permission, Play Services without. Works fine. Maps also given Network, Notifications, Sensors. Play Services just has Network, Notifications, SMS.

GrapheneOS

edebbbb Google Play services doesn't need the Location permission for Google Maps to work. The only feature which would require it is location sharing since it's actually implemented in Google Play services. Leaving location request rerouting enabled as it is by default is recommended, in which case apps using the Google Play Location API work without Google Play services having it. If you want network-based location, we recommend enablng the network location service built into GrapheneOS rather than the Play services one.

jarell

@Mikaelson I recommend you read through these pages regarding geolocation on GrapheneOS:

These pages are pretty much the step-by-step guides you're looking for.

Also, if you want to see the direction you are facing in Google Maps (the blue dot), you have to give Google Play Services sensor access.

secrec

Try this;

1) Install gpstest https://f-droid.org/en/packages/com.android.gpstest.osmdroid/
2) Launch gpstest and wait for a location lock.
3) KILL gmaps.
4) LAUNCH gmaps.

Working now?

If so, it sounds like you need to mess around with the location settings. Gmaps, for some unknown reason, needs to start either with a gps FIX, or have network location enabled.

P.S. if you can get your hands on the apk for gmaps version 11.111.0202, it works withOUT gservices, however, you ALWAYS have to use the hackaround mentioned above for it to work.

I'd also recommend you look at Waze for navigation.... google owns it and it runs off the same database as gmaps, but works better -- no gservices or existing fix required.

mmobder

Depending on your use cases, GMaps WebView may be enough for you (though it requires some adaptation, and may require to access web Google maps on rare occasion).
https://github.com/woheller69/maps

In combination with Waze for navigation, as advised by @secrec , it may cover basic needs.

However: Google has announced that, starting in 2026/2027, all apps on certified Android devices
will require the developer to submit personal identity details directly to Google.
Since the developers of this app do not agree to this requirement, this app will no longer work on certified Android devices after that time.

GrapheneOS

mmobder

However: Google has announced that, starting in 2026/2027, all apps on certified Android devices
will require the developer to submit personal identity details directly to Google. Since the developers of this app do not agree to this requirement, this app will no longer work on certified Android devices after that time.

This isn't relevant to GrapheneOS. We would have to go out of our way to provide a toggle for enabling that feature if we wanted to offer it either via our own code (highly unlikely) or via sandboxed Google Play (not planned).

jdoe

Google maps app installed from google play in private space works just fine for me. It isn't as precise to pinpoint my location as on a normal android phone but it's good enough. Did you change some location settings in Settings? Leave them as default. Also give open street maps a try from Accrescent. For driving I use that. Google maps for satellite view, looking for restaurants, reviews, etc. You cand also just install maps.google.com as a progressive web app, no need for google play and if you use a VPN you have privacy

GrapheneOS

jdoe Satellite-based location on GrapheneOS works as well as it does on the stock OS. It has the same GNSS and A-GNSS (PSDS and SUPL) support. PSDS uses static database downloads of a non-region-specific database to heavily speed up GNSS. SUPL is essentially a primitive form of network location speeding up GNSS via having an initial estimate that's not directly used as a location estimate and also providing GNSS almanacs like PSDS which is essentially obsoleted by PSDS.

The difference between the stock OS and GrapheneOS is mainly that the stock OS has network location integrated into the Setup Wizard and you'll get it enabled by going through that if you don't toggle it off. You can turn on the GrapheneOS network location service in Settings > Location > Location services. You likely also want to turn on Wi-Fi scanning to enabling using Wi-Fi scans when Wi-Fi is otherwise off since it has to fall back to much worse detection based on cell towers without Wi-Fi.

jdoe

GrapheneOS Wifi and bluetooth scanning was off for me, maybe that's why it wasn't that precise

mmobder

GrapheneOS This isn't relevant to GrapheneOS

As I've proposed the app, I thought I have to mention it will be discontinued (though it's 2026/27).

Mikaelson

hello and thank you all for all your tips. I just realized that actually no app has access to my location not even gps test. I hope its not an hardware issue, I'll just reset GrapheneOS and try again.

yore

Mikaelson Although PSDS and SUPL turned off should only increase the time it takes to get a location lock, I had similar issues with get a location at all when I had them turned off.

And while it may seem obvious no one has mentioned it; is your global toggle location setting on?

GrapheneOS

yore If you have both PSDS and SUPL off, it's normal for GNSS to take a very long time to get a location lock. PSDS alone should work fine. SUPL just speeds it up a bit more with an initial estimate since PSDS almost entirely obsoletes providing GNSS almanacs via SUPL. PSDS + network location should make GNSS as fast as it is with PSDS + SUPL. SUPL is near fully obsolete due to proper network location existing now, but we still want to keep it as an option. We could change what the defaults are to PSDS + network location enabled and SUPL off with a setup wizard page for configuring it.

secrec

mmobder Who says it will be discontinued?

mmobder

secrec https://github.com/woheller69/maps

de0u

mmobder https://github.com/woheller69/maps

What I see there is:

Google has announced that, starting in 2026/2027, all apps on certified Android devices
will require the developer to submit personal identity details directly to Google.

Since the developers of this app do not agree to this requirement, this app will no longer
work on certified Android devices after that time.

That does not say that the developers plan to stop working on the app.

mmobder

de0u @secrec you're both correct, I've took my expectations re app support as granted.
Typically, unless author/community has strong personal reasons to maintain an app, once it's user base (and thus contributors) is reduced, it gets less attention and decays.
I personally use the app with combination with waze (limited by amazing rethinkdns, tnx @ignoramous) and I hope it will continue to work, but it's not granted.