summaryrefslogtreecommitdiff
path: root/sensorPlugins
diff options
context:
space:
mode:
authorArseniy-Movshev <dodoradio@outlook.com>2023-07-12 17:51:32 +0100
committerArseniy-Movshev <dodoradio@outlook.com>2023-08-07 20:45:29 +0100
commite53270854b7fd6e4ca9d22fa447ca54ae803baac (patch)
tree77328abdc5193bbc9b1399c119495218d31f42d5 /sensorPlugins
parenteabcface011478b24192736fa8e2ea7b0861c5db (diff)
Add some compensation to the barometer
Here's the justification from the asteroid-toolwatch commit logs: > 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. The daemon uses the same dconf value as in toolwatch.
Diffstat (limited to 'sensorPlugins')
0 files changed, 0 insertions, 0 deletions