Hi all! I'm a new GrapheneOS user (switched because I want a daily driver which is secure as possible while still functional) on a Google Pixel 7a.

So far so good, but I can't get Citymapper to work, nor anything which runs off Google Maps. Unfortunately, this is a pretty important one for me because I struggle with directions, live in London and I can't find an OSM alternative which understands London's travel infrastructure (buses+tube network).

When I open Citymapper, I can search routes etc, but the map section is blank. Even weirder though, Google Maps (downloaded from Aurora Store) works just fine.

I have Sandboxed Google Play enabled, does anyone have any advice? I'm new and really hoping to learn a lot and maybe start a skillshare locally on switching to private OS' for people who it might be beneficial to :))

    jimmii and I can't find an OSM alternative which understands London's travel infrastructure (buses+tube network).

    Which ones did you try? Transportr works for me (albeit not in London)

        jimmii Citimapper on a Pixel 5a works for me. Perhaps you missed something simple like enabling Settings -> Apps -> Citymapper -> Permissions -> Location ?

            avaluedcustomer Unfortunately Transportr only works with the underground network in London (and not buses which are way cheaper/often better)

            Then OSM maps takes about 10 minutes to load, offers really weird routing and kinda avoids ever walking? E.g. one route, makes sense to walk to the bus 15 mins away and take 2 buses because total route time is shorter, but it pushes me to take 3 different buses so I never walk. It all shows valid routes, just never... the smartest one? And doesn't factor in cost at all. Seems hopeful for future though.

              Plobberfroth Good shout, slightly annoying for the walking aspects of the route (opens a large tab and doesn't follow as you go, slightly buggy interface to zoom in and see the map) but may be a good option!

                wizoatk this is all allowed and i'm finding I also get the same issue with Uber - it's recognised where I am via location permissions (for both uber and citymapper location, network and sensors allowed atm) then the actual map view is all a plain sand colour with google in the bottom corner. Super odd that Google Maps itself is fine, but also both apps get a play integrity pop up saying it checked for that so maybe it's to do with that.

                While I was typing and checking (fiddling away mindlessly with) settings, it now wants to work, but ideally would like to trim out unnecessary permissions, although I will be turning location entirely off in the device when I'm not using it for travel routing so maybe it's not the end of the world?

                Current settings are:
                Citymapper & Uber: location, network and sensors allowed
                Google Play Services: Location (while using the app), nearby devices, network and notifications allowed
                Play Store: Network and sensors allowed, location (ask every time)

                    jimmii Sounds like progress to me. Differences between your configuration and mine:

                    • For Citimapper (and other transit apps) permission I tend to also allow notifications as well as location, network and sensors. On the theory that notifications might surface more clues if/when the app misbehaves and I don't see any real issues with sensors. I may disallow them in the future.
                    • For Google Play services permission,, I allow Contacts (for some syncronization testing between multiple email apps), Network and Sensors. I haven't yet found a compelling reason to allow Google Play services access to Location. Instead I tell Sandboxed Google Play to Reroute location requests to the OS.
                    • For Google Play Store permissions, I allow Network, Notifications, and Sensors. I don't currently allow Location.

                    Summary: you might want to consider disallowing Location permission for Google Play services and Google Play Store. Then see if anything breaks. I think that's consistent with your implied goals.

                    Disclaimer: just another relatively new GrapheneOS user.