Open barbeau opened 2 years ago
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!
Closing this. Please reopen if you believe it should be addressed. Thank you for your contribution.
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!
Not 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!
Not stale
Is your feature request related to a problem? Please describe. A known issue with the GPSTest Database is the variability due to the uptime of GNSS before submitting a record to the database. For example, the longer GNSS is active (either in a single app session or multiple app sessions, or triggered by other apps) the more CFs and GNSSs will be visible (see https://github.com/barbeau/gpstest/issues/545 for example). For more explanation of this see https://barbeau.medium.com/crowdsourcing-gnss-capabilities-of-android-devices-d4228645cf25.
PDOP may also be a good indicator of how good the fix is and how likely that the full view of the sky is possible (also satellite counts, etc.).
Describe the solution you'd like To help understand these differences, it would be good to report GNSS uptime (time since GNSS last started in app) and time to first fix to get a general idea of how long GNSS has been active before the user submits the data. This isn't a perfect measure (user could have primed the GNSS with another app first) but it's something.