It seems to me that people are reading with expectations rather than reading what you are writing.
This is what I read...You are getting a solid GPS lock in other applications but when you switch to osmand that connection is reset. Occasionally if osmand goes to the background and back to the foreground it is reset again. You can confirm this by getting a strong lock in gpstest in airplane mode, switching to osmand, and then switching back to gpstest to see if it is busy acquiring a lock again. Gpstest does not reset the GPS when it goes to the foreground. If you see gpstest looking for a lock, then the GPS has been initialized by the APP you opened...osmand. All of those other settings power/battery/etc only affect the device if it goes into power mode(the best way to keep your device out of power mode is to attach a charged battery pack and leave it connected.) Devices attached to power sources don't experience power related performance drops, and you may find that you get cell service farther away as well since the cellular radio will use a higher transmission powered if it is getting power. If you still experience lock loss with a battery after an immediate application switch then it is not a power issue, but an application one. That is a developer issue and needs to be handled as a bug or by contacting support. They will need device information, android version etc. All of these things no one has thought to ask you, and since we are not developers cannot for the most part answer. Since osmand is resetting the GPS every time the application goes to the foreground its killing your established lock. Since you are in airplane mode, the GPS isn't doing a warm reset, since towers are not available, but instead a cold one. I have seen this problem before. Altitude has little to do with this or speed really. I have successfully maintained airplane mode GPS locks at commercial air transportation speeds(550kmh) and altitudes(11455m) for 5 hour flights. Speed was a bit wonky over 500kmh mainly because consumer units don't expect you to be going that fast so it messes with the averaging profile that smooths position information. All applications see the averaged cleaned data. If were to look at the raw dirty data, even with a sub 3m lock the position reported could be anywhere within that circle. If two points are reported on opposite sides of that circle you are doing 10kmh between them. At a 30m error circle its 108 kmh between the edges. The averaged data has you going much slower, but also lagged slightly when you first start moving. -- You received this message because you are subscribed to the Google Groups "Osmand" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/9453953a-325c-4818-8564-4ad827dedbdc%40googlegroups.com.
