aboutsummaryrefslogtreecommitdiff
path: root/src/compass.svg
diff options
context:
space:
mode:
authordodoradio <dodoradio@outlook.com>2023-07-09 01:19:34 +0100
committerdodoradio <dodoradio@outlook.com>2023-07-10 14:14:48 +0100
commit16dcaae647c081ba60b239e425b26bf36ca327d3 (patch)
treef94373322980a8df13e8edd8d860548c0c76baff /src/compass.svg
parent6c6ef8cdb09a2c47b60f4f8de875243b559c9fe4 (diff)
Fork and start work on asteroid-toolwatch
This is meant as a multitool app that currently allows usage of compass and barometer. The app includes a means of 'calibrating' the barometer reading. This is not a system level calibration and only affects the app (or any other apps that choose to use the value I'm setting in dconf). The mechanism was initially inspired by the same feature on Casio's watches: under WearOS, all of Casio's apps use a shared calibration offset for barometer. The calibration aims to rectify the infamous inaccuracy of the android barometer sensor. While the sensors are generally very precise and can sense small changes in air pressure, the sensors often lose calibraton and hence suffer from zero error. This can be somewhat helped by allowing the user to set a zero point - it seems this allowed Casio to make the sensor into an actually useful feature. There was discussion about making this calibration into a system-level feature (for example, as a patch to sensorfw or to QtSensors) but I think it's reasonable to expect the sensor to always return the raw value (even if it is wrong) and then have the calibration as a separate, opt-in feature.
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions