location services not working in LaGuardia airport

theemperor204

Long story short. Landed in LaGuardia airport and wanted to see what the prices of ubers were at my next stop, however i noticed location services arnt working. Uber doesnt know where i am, google maps doesnt know where I am. Tried restarting my phone and turning my cellular on and off with no luck. Im currently on data so my cellular works fine

Thoughts?

de0u

theemperor204 I think it might be useful to try a GPS test app. If your device is too far indoors the GPS receiver can't see enough satellites....

treenutz68

theemperor204

I think location on GrapheneOS by default needs line of sight to satellites, it doesn't use other things like nearby known wifi signals, etc... to pinpoint your location indoors. Its an issue with your use case (call an uber while indoors). There is a workaround where you use google's location services, its outlined here:

https://grapheneos.org/usage#sandboxed-google-play-configuration

Personally, it sounds like giving up too much privacy to google for my taste, but seems like its an option if you really needed it!

DeletedUser29

It's the sun's fault.

So I don't know, see if there are any cattle, weird foreigners and/or virgins around that you can sacrifice?

UndercoverBozo

DeletedUser29 interesting and scary as fuck, thanks.

Even organic maps started glitching out on me mid trip, makes sense now.

Speeduser7533

I have mine set up to route all location requests to the OS. My experience (using Waze) is that it works fine; I haven't had any issues so far. Maybe the app you are using is more finicky.

treenutz68

Speeduser7533

My understanding is that the expected behavior when using the routing location to OS (as in, not routing to google) is that it requires line of sight to satellites and is slower to get a lock on your location than otherwise. But perhaps there is variability by app... I don't know

RRZishe

I actually had the same thing at multiple airports including twice at LGA.

de0u

RRZishe I actually had the same thing at multiple airports including twice at LGA.

If Google's location service is not in use, and the device is indoors, and the airport's roof is thick enough (and/or there is sufficient ambient radio noise), this is expected behavior. The native GrapheneOS location service depends on satellite lock; if the native GrapheneOS location is in use and the device can't see satellites, then the device won't know where it is.

A GPS test app (perhaps GPSTest) might shed light on the situation -- if a GPS test app can't establish position, then the native GrapheneOS location service won't be able to either.

Standing outside for five minutes might help too.