You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
...and Dashboard will be after PR #570 is merged, it should be relatively straightforward to re-use these in a Wear Compose app. We'll probably need to add code to only show certain items (e.g., for Status - azimuth, elevation, LocationCard) if the screen is over a certain width. That should allow us to present a minimal set of elements on a small watch screen to provide GNSS info like the list of signals with ID, constellation, CF, and C/N0.
We can start with just showing Status first in a new WearOS module in this project.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
WearOS is getting somewhat of a reboot, and Wear Compose is in developer preview:
https://android-developers.googleblog.com/2021/10/compose-for-wear-os-now-in-developer.html
Additionally, smart watches are getting more interesting from the GNSS perspective with some supporting dual-frequency.
Describe the solution you'd like
I'd like to create a very simple "dashboard" display similar to #313, and a Status list, as a Wear app.
Given that the Status screen is already implemented as Composables:
https://github.com/barbeau/gpstest/blob/master/GPSTest/src/main/java/com/android/gpstest/ui/status/StatusScreen.kt
...and Dashboard will be after PR #570 is merged, it should be relatively straightforward to re-use these in a Wear Compose app. We'll probably need to add code to only show certain items (e.g., for Status - azimuth, elevation, LocationCard) if the screen is over a certain width. That should allow us to present a minimal set of elements on a small watch screen to provide GNSS info like the list of signals with ID, constellation, CF, and C/N0.
We can start with just showing Status first in a new WearOS module in this project.
The text was updated successfully, but these errors were encountered: