dv said:
Spiny Norman said:
dv said:I’ll try that next time. Like I say, once we touch down it works again, so it would not be just the Faraday cage effect but maybe some combination or Faraday cage effect plus speed.
I’ll still argue against the speed being a factor. Unless your phone has some kind of speed limit in the code.
Mmm
Or in this app.
From Claude –
Me: Hey hey!
I had a quick search but couldn’t find what I was after.
A friend of mine has a gps app on his phone that won’t work on an airliner. He thinks that the speed of the plane is too high but I doubt that.
Do you know if any phone apps have an upper limit of the speed they can display?
Claude:
Hey! Your friend might actually be onto something, though not always for the reason he thinks.
Speed limits in apps: Some GPS apps do cap displayed speed, but it’s usually a deliberate design choice rather than a technical limit. Many fitness and driving apps filter out readings above a certain speed (often a few hundred km/h) as “implausible” GPS noise, so they just show zero or drop the signal. An airliner cruises at roughly 800-900 km/h, which would trip those filters.
The bigger issue is the phone’s GPS chip itself: Under US export rules (the old COCOM limits), consumer GPS receivers were meant to stop reporting position above about 1,900 km/h (~1,000 knots) and above about 18 km (60,000 ft) altitude. Most chips require both conditions to be exceeded before cutting out, so an airliner at ~900 km/h and ~11 km up wouldn’t trigger it. Some older or cheaper chipsets were implemented with an “either/or” rule, but 1,900 km/h is still well above airliner speed.
More likely culprits for an app not working on a plane:
No clear sky view. GPS signals through the window can be weak, especially in the middle of the cabin. Sitting at a window helps.
Airplane mode disables the GPS in some phones and apps, and you often have to re-enable location services separately.
The app needs data. Many map apps need an internet connection to download map tiles, so they show a blank map even though the GPS itself is working. Offline maps fix that.
App filtering as mentioned above, where the app discards fast readings as errors.
So you’re probably right that the raw speed isn’t beyond what the phone can handle, but your friend could still be right that his particular app is rejecting or ignoring the speed. If he tells me which app it is, I can look into whether it has a known cap. A good test is a basic GPS status app (like GPS Test or GPSStatus) that shows raw satellite data and speed with no maps involved.
So definitely maybe.