-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GPS Position Takes Too Long to Update After Unlocking the Phone in OsmAnd #4267
Comments
The bug has not been reproduced on our end. Please try the following steps:
You should see that the location updates correctly and follows your movement, even after unlocking the phone. Additionally, please check if the "Location Access" setting is set to "Always" in iOS Settings → OsmAnd Maps → Location. I also noticed you mentioned being in a forested area. Keep in mind that GPS signals can be weaker in such environments due to obstructions like tall trees, which could cause delays in updating your location. Please try testing the latest TestFlight version and let us know if the issue persists: TestFlight Link. OsmAnd 4.9.3 (4936)
|
@yuriiurshuliak thats definitely happens not due weak signal, because most of the times osmand just cannot find my initial position, and I need to switch to Google Maps or any other gps app to locate my position, and after that osmand works fine. Osmand has full and "always" access to gps. |
@alxmamaev We will be waiting for your updated feedback |
trim.169F69CC-4B46-4C68-8310-7CC21B5C6CC4.MOV
trim.961B90AE-B34E-485A-B58E-8736D68739B8.MOV
trim.6A41F6A6-39E2-49D1-8E45-D546E9AD6BB0.MOV
I have used Osmand for years, but one thing which I notice a long time ago makes it’s really hard use for navigation. After you are unlocking your phone and open the app it take years to find your position, firstly i think that problem with my device. But it’s gone if you just open any other map app, to find your position. Seems it just and problem with osmand and GPS device initialisation, it’s does not fix for a year, or maybe more.
The text was updated successfully, but these errors were encountered: