feat: Add Dashboard screen

[barbeau]

TODO:

• Add navigation drawer item and fragment
• Fill out data in viewmodel
• Check dark and light themes contrast with https://webaim.org/resources/contrastchecker/
• Hide Filter button in Action Bar when Dashboard is visible
• Handle manual on / off switch (start tracking) - this message still shows up when it shouldn't
• Check TODO/FIXME
• Handle manual on / off switch (start tracking) - this message still shows up when it shouldn't
• Update observers to stop/start from preference
• When background app and background running pref is off, Service doesn't stop right after switching to prefsRepo observing
• On Android U and higher, use new GnssCapabilities.getGnssSignalTypes() and related methods to read signal and other support
• Add Compose screen with elements - See Add "Dashboard" tab for showing GNSS feature support #313 (comment) for checklist
  • Summary of sats and signals
    • Add Lock icon
    • Last updated
    • CF summary
    • Spacing tweaks
    • in view / in use
    • Make CF graphs all fit on one line
    • Add subtitle above CFs
  • GNSS/SBAS
    • GNSS list
    • SBAS list
    • Adjust placeholder spacing while waiting for signals to avoid snap in
  • Feature support
    • Dual-frequency
    • Raw measurements
    • Carrier phase
    • Carrier phase - Showing the human readable constant values like ADR_STATE_HALF_CYCLE_RESOLVED instead of the raw integer values would also be helpful.
    • Navigation messages
    • GNSS antenna info
    • List GNSS antenna CFs
    • Inject time
    • Inject XTRA data
    • NMEA
    • Vertical accuracy - see Accuracy Enhancements #442
    • Automatic gain control
    • Delete assist
    • Update NMEA icon to match font
    • Refactor to pass Composable to main row
    • Bearing accuracy? No, this would mostly just take up space when stationary and change to supported when moving
    • Make sure properties update after app or OS update
  • Errors in data
    • CF errors (Indicate errors in CF output in UI #295)
    • GPS week number rollover issue (Flag wrong times from GPS week rollover issue #369)
    • Duplicate carrier frequencies
    • Disagreements between dual frequency signals on azimuth and elevation from same satellite
    • Disagreements between dual frequency signals on almanac and ephemeris from same satellite
    • Satellites that are shown in list without alamanc or ephemeris data but with elevation and azimuth (Show "# Sats" in X/Y/Z format #365 (comment))
    • geoid offset and altitude MSL (ortho height) errors - see Alt MSL - Reported value is wrong on some devices #503
    • NMEA DTM datum - see Parse DTM and display some info if it is non-standard #527
    • Valid GnssAntennaInfo values (i.e., not including L2 or matching to default numbers)
    • Satellites without C/N0 or almanac or ephemeris (see above)
    • Update icons
    • Combine missing almanac with missing data (general)
• Device info:
  • GNSS hardware year, which is currently buried in the Help section. See https://developer.android.com/reference/android/location/LocationManager#getGnssYearOfHardware()
  • GNSS hardware model name - https://developer.android.com/reference/android/location/LocationManager#getGnssHardwareModelName()
  • System version info (Android API, build names, etc. - see database)
  • App version code and name
  • Main SoC - See https://stackoverflow.com/questions/10496872/android-get-hardware-information-programmatically. Skipping this for now, doesn't seem generally supported - see https://stackoverflow.com/questions/34005648/how-to-get-programmatically-system-on-chip-data-from-device.
  • Requested vs. avg actual location update rate (e.g., if you request minTime=.5s, but it updates every second.
  • User location country code

Closes #313

[botanegg]

https://en.wikipedia.org/wiki/Homunculus_loxodontus

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Please comment here if it is still valid so that we can reprioritize. Thank you!

[barbeau]

Not stale

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Please comment here if it is still valid so that we can reprioritize. Thank you!

[barbeau]

Not stale