FLY is FUN

Hi
Just noticed that, on my unit, the GPS acc has the unit in feet (ft) but the number is in meters.
I saw that I got a acc of 3ft in FiF while the best I ever got before with other apps is 3m.
So I compared with 'GPS Status' and 'Oruxmaps' and indeed got an acc of 3m, changed units and got 10ft.
I could even see the acc of 'GPS Status' in the Android status bar while I had FiF running, same numbers (3) but different units.

BR
/H

FIF displays what it gets from Android.

Here is code

public static final float FEET_TO_M = 0.3048f;

if (location.hasAccuracy()) {
mACC_m = location.getAccuracy();
mACC_ft = mACC_m / FEET_TO_M;
}
else {
mACC_m = NONE_FVALUE;
mACC_ft = NONE_FVALUE;
}

Thank you for your answer.
Yes, according to the code you are showing fif really grabs the accuracy both as meters and (calculated) feets.
But how are the variables used later?
You can see in my first attached picture, with fif and GPS Status side by side, that both has an acc/error of 9 (I'm indoors). But fif gives 9ft while GPS Status gives 9m.


But if you have a look at my second image where I have changed the distance unit in fif to km (acc in m), you can see they still have same numbers, but also same unit


For comparison, fif in NM (acc ft) and GPS Status in ft


All pics are screen shots with split screen and the apps running simultaneously.
Same happens with Oruxmaps as the comparison app.
Something doesn't seem to work as intended


EDIT
I noticed you need to right click and "view image" to actually see the entire image, at least that's how I need to do it in Firefox.

Thanks a lot. I have found the bug. Next upgrade will solve it.

Display unit:
switch (NavigationEngine.getDistDetailUnit()) {
case NavigationEngine.FEET: acc = NavigationEngine.mACC_ft; break;
case NavigationEngine.M: acc = NavigationEngine.mACC_m; break;
}
There was missing breaks, so it was always in meters.

Good to hear you found it.
Thanks!

I got a new update today, 20.24.
Was this bugfix suposed to be in this update?
It still only shows the meter accuracy even if unit is feet.

The next one

Excellent!

20.25 should be OK...

It is
Thanks!