Regarding A-GPS data, I found this interesting comment from one of the Organic Maps contributors: Since you linked to GPSTest on F-Droid I assume that doesn’t apply to you. Not sure if something similar is planned (exists) for Organic Maps.
OsmAnd has added an option to switch to the google-less android.location API (see issue #14001 and this commit), but that’s only available in the nightly release for now. The Play Store versions use .location included in the Play Services, so if you disabled you’ll likely run into problems there. We probably have a different definition of “pristine”Īre you using OsmAnd / Organic Maps from Google Play or the F-Droid versions? I’ll mark it as solved in the wiki because it seems to work as it is designed to.ĭidn’t make any changes to the ROM, so yes, a pristine Fairphone ROM. So I think we can then confirm that it’s most likely an app specific issue, since location works fine otherwise on my Pixel 3 and Fairphone 4. Because then it’s not a bug, those other apps should use the location APIs in Android to acquire a location faster.Įdit: Just did a test with my Pixel 3 and GPSTest, it takes more than a minute to get a location fix. Just trying to pinpoint if this is actually a bug, or just using the location services differently, and thus it’s slower to get a location. Depending on the line of sight, if there are no large buildings or even trees nearby it is faster. I know that the TomTom in my parents car also takes about a minute to get a fix on location. Could it be that GPS always takes a minute to form a constellation to get a location fix? Android improves this by using known Bluetooth and WiFi signals for location as well. I don’t have this with Google Maps or when I shoot pictures and geo tags are added. Even after having cleared data using GPSTest and rebooted, waiting a day, it still takes minutes to acquire a first fix.
0 kommentar(er)
