| I have been playing with my (spare) Android phone and its GPS to record my location and speed when driving. My guess is when using an app on Android, there are too many variables (from the actual GPS hardware, device ROM settings, app settings, etc.) which are not very easily accessible and likely optimized for different goals. In my use case (as in the article) only care about GPS readouts when the car is in motion so I don't really care about energy efficiency (within reason, the cigarette lighter thing should be able to safely power the device). The GPS module manual says it takes about forty seconds for the GPS module to position. https://images-na.ssl-images-amazon.com/images/I/81+jY5X2YrL... > Once the GPS module is powered on, there is data output
> It usually takes about 40 seconds to be successfully positioned.
> After the positioning is successful, the correct time, latitude and longitude position data will be available. But the article says: > GPS is usually acquired within 15-30 seconds of starting (much faster than the cheap electronic speedometers I tested first). Maybe this does not include the time it takes for the raspberry pi to boot? Maybe the raspberry pi takes an additional thirty seconds to boot and the GPS unit powers on almost simultaneously with the raspberry pi but we don't blame the GPS module for any delay until the raspberry pi boots, logs in, and the Navit application starts? Or maybe the GPS positions way before forty seconds and the manual is written that way to not be overly optimistic (could never get decent GPS signal when walking in areas with tall skyscrapers on my Android phone a few years back). This is also exciting because it is modular. When GPS III[1] (hopefully) becomes operational by the end of the decade (The tenth and final GPS Block III launch is projected in Q2 2023 so it should be fully operational/adopted by 2030), you could simply use a new module (in theory at least). [1] https://en.wikipedia.org/wiki/GPS_Block_III |