osmandapp / OsmAnd

OsmAnd
https://osmand.net
Other
4.69k stars 1.02k forks source link

track recording not possible #20377

Closed t-h-oma-s closed 3 months ago

t-h-oma-s commented 3 months ago

Description

The recording of a track often, approximately every third record stops several times. GPS is available and the mobile is on the same Position as always. You can See this on the Screenshots I shared. Have the same error in the same paths, therefore buildings,... can not have an impact on GPS. The root cause is the app.

Steps to reproduce

Started recording, no energy saving active, Often, also at the hiking trip visible in the screenshot, the recording was stoppen. But there was no problem with GPS, this was available.

Actual result

Have the same issue approximately once per week without any change in settings...

Expected result

Track recording without gaps

Your Environment (required)

WARNING Crash-Logs MAY contain information you deem sensitive. Review this CAREFULLY before posting your issue!

OsmAnd Version:
Android/iOS version:
Device model:
Crash-Logs: ?
sonora commented 3 months ago

Any track recording filters active? Like a speed filter, or a displacement filter, and you had a break? Then perhaps this was caused by setting "Auto-split recording after gap" being set to "true".

(You could manually combine sub-tracks again by manually editing your gpx file and removing the interim inserted

</trkseg>
/trkseg>

lines.)

scaidermern commented 3 months ago

no energy saving active

It is not quite clear from your comment whether battery optimization for OsmAnd really is disabled in your Android settings.

yuriiurshuliak commented 3 months ago

The term "no energy saving active" can be understood in various ways. Simply disabling the phone's energy-saving mode won't suffice; you need to disable optimization for the specific application.

The issue is likely specific to your device. Please check if your device has any power optimization settings that might be impacting the app's performance. You can find more details on power optimization at https://dontkillmyapp.com/.

Additionally, we recommend joining our beta testing program to see if the issue persists. Information on how to sign up for beta testing can be found here: https://osmand.net/docs/versions/nightly_versions.

sonora commented 3 months ago

As I saidd, it may well be a filter issue the way it looks on your screenshots. But regarding Power Saving, most OsmAnd users have good experience with these settings: https://osmand.net/docs/user/troubleshooting/track-recording-issues#tested-power-settings-for-android-9-10-and-11-hardy-2020-08-25

t-h-oma-s commented 3 months ago

Thank's a lot. had to adjust one setting. Going to check within the next days if this had solved the problem.Am 24.07.24, 18:10 schrieb Hardy @.***>:

As I saidd, it may well be a filter issue the way it looks on your screenshots. But regarding Power Saving, most OsmAnd users have good experience with these settings: https://osmand.net/docs/user/troubleshooting/track-recording-issues#tested-power-settings-for-android-9-10-and-11-hardy-2020-08-25 —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

t-h-oma-s commented 3 months ago

Tested the track recording 5 times with these settings and Till now everthing was ok. Thank's a lot for your help.

‐------ Thank's a lot. had to adjust one setting. Going to check within the next days if this had solved the problem. Am 24.07.24, 18:10 schrieb Hardy @.>: As I saidd, it may well be a filter issue the way it looks on your screenshots. But regarding Power Saving, most OsmAnd users have good experience with these settings: https://osmand.net/docs/user/troubleshooting/track-recording-issues#tested-power-settings-for-android-9-10-and-11-hardy-2020-08-25 — Reply to this email directly, view it on GitHub[https://github.com/osmandapp/OsmAnd/issues/20377#issuecomment-2248405377], or unsubscribe[https://github.com/notifications/unsubscribe-auth/BKBFURIAP54HKEWJK2HULHTZN7GYDAVCNFSM6AAAAABLIPSP6KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBYGQYDKMZXG4]. You are receiving this because you authored the thread.Message ID: @.>