Describe the bug
When the Wear OS app is first started, the user interface populates with default (i.e., not real) GNSS information.
Here's an example picture:
For example:
Time is 19:00:00
Lat: is 0.0000000
Long: is 0.00000
Bearing: is 0.0
PDOP: is NaN
These fields should all be blank before real information is reported from the Android APIs - in other words, they should be initialized to empty values.
Here are some examples for how this is handled with Compose in the mobile app Status screen:
Describe the bug When the Wear OS app is first started, the user interface populates with default (i.e., not real) GNSS information.
Here's an example picture:
For example:
These fields should all be blank before real information is reported from the Android APIs - in other words, they should be initialized to empty values.
Here are some examples for how this is handled with Compose in the mobile app Status screen:
The one exception is "# Sats" - we can keep this as 0/0/0 until it populates with real data.
@adaext Is this something you could tackle?
To Reproduce Steps to reproduce the behavior:
Expected behavior Fields with data should be initialized to empty values
Observed behavior Fields are populated to default values
App, Device and Android version:
Main branch as of https://github.com/barbeau/gpstest/commit/7f56a0e8490a0de77c9cce5b67936461aea2b079