Messages

Hi ut - Thanks for your suggestions. When I checked I found that the settings you suggest (battery optimisation/background running/GPS always on) were already set as you suggested - I've tried most of the obvious settings in my efforts to get Orux to run properly! As suggested I also downloaded the v7 profile from my S5 to v10 on my S22. I did the usual walk around the block with both the S5 and S22 tracking the walk (both now with the same profile), and while the S5 worked fine, Orux scribbled all over the map on the S22. However, Minimum time was set to 8sec on this profile, and when I set it to 0 (always) the S22 worked beautifully. It seems that this setting is essential for me.

Thanks also for your thoughts Ivan. Agreed that first positions when GPS is started are always inaccurate. My contention is that with Minimum time set to anything other than 0 (always) Android on my S22 is shutting down GPS completely between track-points, so that every point recorded is a first point. No idea how to confirm this idea though....

I seem to have resolved this issue myself by setting Sensors>GPS>Minimum time to 0 (always).
I think that what was happening is that calculating a GPS position involves a series of itterations, with the last position usually taken as the starting point for the next. The first position calculation could take anywhere as its starting point and is usually much less accurate. (I noticed that when Orux is started it takes a few seconds for the position to settle to the correct position.) I suspect that with Minimum time set to anything other than 0, Android(?) is shutting down the GPS completely so that GPS starts every position calculation from scratch, and is therefore giving big errors. When I had another GPS app running, this may have been keeping the GPS active so avoiding the issue . The problem might also be related to the S22's rather aggressive power saving (it doesn't have a very large battery.)
I'd be interested if anyone has any comments on my theory? Also, is this a problem which the Orux developers might have a fix for (I'm now worried about the implications for battery life...)

I've run Orux v7.4.26 on my S5 for some years, and it's by far my favourite GPS app. I've recently upgraded to an S22 and installed the paid-for version (v10.5.0), and the track recording is very inaccurate - looks as though a child has scribbled all over the map! However, if I run a second GPS app at the same time (Memory Map for All) then Orux works beautifully. Very Strange, and if anyone has any ideas I'd be grateful.
I've put v7.4.26 on my wife's S22 (identical in all respects to mine) and it works as it should without requiring MMfA also running. GPS Test on my phone reports good satelite reception.
I've attached an image with 3 track plots - the first is with V10.5.0 running alongside MMfA and follows my actual route to within a few metres. The next two are with Orux running on its own.