In metric mode, elevation is still in Feet

[bqv]

Describe the bug
Metric mode selected in settings. My current location's altitude is still identified in ft - possibly because of my locale (UK), but I would like elevation to be in meters.

To Reproduce
Steps to reproduce the behavior:

1. Go to Home screen
2. Ensure "Current location"
3. Observe elevation
4. See feet

Expected behavior
Altitude unit should match the settings unit

Screenshots
I can add one on request, I assume this is clear enough as is

Version Info:

• App Version: [e.g. 0.14.3] 0.16.8
• Android Version: [e.g. 10] 14
• Device Model: [e.g. Pixel 6] OnePlus Nord 2

Additional context

[bqv]

Yes, changing locale back to EU fixes it. Maybe this is a choice?

[forrestguice]

Thanks for reporting. 👍
Unfortunately I can't seem to reproduce this bug, and inspecting the code involved hasn't revealed anything obvious yet. I'm confused why the locale setting is affecting this - displayed units should only be based on the General -> Units of length setting.

I think a screenshot (or two) might provide some missing context, and will hopefully help me understand this better.

[bqv]

No problem!

Here is with my Android UI language set to English (UK) (but location still set to Finland):

Here is with my Android UI set to Finnish (but app language pinned to English still, of course):

This is the app language config:

And my unit settings are just all metric, á la EU. You can see how it went from feet to meters based on language - took me a while to notice it too

[forrestguice]

Thanks. My theory is that the unit setting is actually unset and returning a locale specific default, which is why swapping system locales seems to flip the setting. It should default to metric for all locales except English (US). I suspect the value shown by Settings -> General also flips with the locale, and that touching that setting (swapping between imperial and metric) will cause the bug to disappear (at least until storage is cleared).

Language pinning might play into this too. If I recall its a relatively new feature (newer than api28, which is what the app currently targets), so it wouldn't surprise me if the app was also failing to respect that somehow.

Anyhow, I think if the "welcome activity" explicitly set the units (overriding the default), it would prevent the unexpected flipping of the value later on when changing locales.

[bqv]

Indeed! Touching the setting does fix it at least, thanks!