Regression. Battery optimization was activated by update ? or trip recording bug about osmand

[sonora]

I recently noticed I occasionally have the problem of tracks not recorded if I start a recording and then immediately turn off the screen. Almost like if the foreground service does not have enough time to get initialized. Counting to 5 after starting the recording and before turning off the screen reliably avoids the issue, it seems. No dependency or change of the battery optimization setting in play, though, it seems.

[pebogufi]

After making some more tests
Reinstalling older OsmAnd~ 4.8.0#2758m, veröffentlicht: 2024-07-17
Some recording
Reinstalling OsmAnd~ 4.8.0#2781m, veröffentlicht: 2024-07-18
Some recording
...
No more problems, battery optimization "not optimized" is unchanged.
But i don't understand the problems as described...

Is there anybody with similar problems ??

[pebogufi]

I recently noticed I occasionally have the problem of tracks not recorded if I start a recording and then immediately turn off the screen. Almost like if the foreground service does not have enough time to get initialized. Counting to 5 after starting the recording and before turning off the screen reliably avoids the issue, it seems. No dependency or change of the battery optimization setting in play, though, it seems.

I also have this problem since months. Maybe not good described, but i am shure it is the same as in
#19845

Sometimes it is not easy to understand what problem is really behind the observed behavior.
And again, i do not really understand what was my problem described above. ...
May be also just trip recording foreground service ?

[sonora]

Thanks for pointing out #19845. I have added my observation there perhaps worth re-opening it.

I think what you are describing here seems different. If you are reallly certain you had exermpted the OsmAnd app from battery optimization and that had changed without you explicitly causing it, it seems worth exploring possible root causes, both within OsmAnd's code and outside (like perhaps the OS 'Adaptive' battery saving or so.

So far I could not reproduce, so perhaps this is not associated with a certain recent OsmAnd build, but timing was accidental and depended on something else.

[pebogufi]

I try to clarify about battery optimization:
First, i am very aware that wrong setting may lead to multiple gaps in recording.
I am absolutely shure that battery optimization was set "optimized" when i detected the problem with so many gaps.
Then i switched it to "nicht eingeschränkt" = not restricted = not optimized.
I do NOT really know when the false setting was introduced, i just see that the day before i had used a older app version 2758 with hiking of 20km without any gap (but with very frequent gps on/off messages).
So it is just my conclusion that the change of battery optimization setting happend with app update to 2781 in the morning before the very bad recording.

[yuriiurshuliak]

The bug was not reproduced on the release version. To reproduce it, I verified that the app's battery optimization was set to unrestricted. Then attempted to update the app. Post-update, the battery optimization status remained unchanged and still unrestricted.

So could you confirm if you reinstalled the app, which might have caused the status to change?

OsmAnd 4.8.2, released: 2024-07-10

video_2024-07-19_13-45-08.mp4

video_2024-07-19_13-44-54.mp4

[pebogufi]

I also cannot reproduce the bug. Please see my last posting, there was something strange going on...
I already changed the title of this topic and added "or trip recording bug"