You are reading a single comment by @Gordon and its replies.
Click here to read the full conversation.
-
Going from memory, but the phone will show ft starting at 500ft and decrement down 50ft until it reaches 0ft.
On the bangle with the code snippet I posted above in my locale file, it will switch back to 0.3mi starting after 0.1 mi instead of switching to ft like on the the phone, then when it gets to 0.1mi on the watch again it switches to ft but at this point the phone will be at 150ft maybe . It is exactly 3.28084 times more than what it should be due to the meter->ft conversion.
It's also worth mentioning there were some weird instances where it would read one less mile on the watch than the phone and at other times it would match perfectly, albeit with a slight delay in both cases.
stweedo
@Gordon
That's great, thanks!
@stweedo maybe you could take a screenshot of your phone's notification screen when it's showing the distance in feet? Does it just say something like
234 ft?Gadgetbridge parses the notification in https://codeberg.org/Freeyourgadget/Gadgetbridge/pulls/3136/files#diff-3dacbc2d2b6a5f9fe4a6ea7f82994629bf3fb71a and right now it doesn't handle feet - tweaking it should be easy