[iioadaptor] Allow overriding iioDevices' scaling factor. Fixes MER#2053

[iioadaptor] Allow overriding iioDevices' scaling factor

See merge request !39

Signed-off-by: Eugenio Paolantonio (g7) <me@medesimo.eu>

[rpm] Fix version numbering in dependencies. JB#45163

See merge request !37

Signed-off-by: Matti Kosola <matti.kosola@jolla.com>

Add sensorfw-qt5-hybris.inc to spec source.

See merge request !36

Signed-off-by: Matti Kosola <matti.kosola@jolla.com>

[binder] Add binder backend to hybris adaptor. JB#45163

See merge request !35

[compasschain] Fix the compass value calculation. Fixes MER#2016

See merge request !34

[sensorfw] Fixed pkgconfig version, contributes to jb#38551

See merge request !33

[compasschain] Change types of the 'oldHeading' and 'heading' variables inside CompassFilter from int to qreal. Fixes MER#2016
Signed-off-by: Ivan Shchitov <ivan.shchitov@fruct.org>

Rename sensorfw-qt5-docs to sensorfw-qt5-doc. JB#38578

See merge request !32

Rename sensorfw-qt subpackage docs to doc and make packaging information
more consistent with other packages.
Signed-off-by: Tomi Leppänen <tomi.leppanen@jolla.com>

Rename Config class to SensorFrameworkConfig

See merge request !31

Sensorfwd crashes on exit in h3113 devices (Xperia XA2). This happens
because of Config class related symbol name clash between sensorfwd
and android dynamic loader / libhybris: Destructor from sensorfwd
code base ends up used for cleaning up libhybris objects - which then
leads to segfault.

As runtime loader is what it is, rename "Config" class in sensorfwd
to less generic "SensorFrameworkConfig".
Signed-off-by: Simo Piiroinen <simo.piiroinen@jollamobile.com>

Deal with android sensor type aliasing changes

See merge request !30

It seems that in later android header versions sensor type values
have been changed from #define constants into enumeration values.
And while previously SENSOR_TYPE_MAGNETIC_FIELD was alias for
SENSOR_TYPE_GEOMAGNETIC_FIELD, now it is the other way around. Which
then has the net effect of: Attempt to provide fallback value for
SENSOR_TYPE_MAGNETIC_FIELD with symbolic name results in compilation
failures.

Use hard-coded fallback values for both SENSOR_TYPE_GEOMAGNETIC_FIELD
and SENSOR_TYPE_MAGNETIC_FIELD to break dependency on what types android
header considers to be aliases vs not.
Signed-off-by: Simo Piiroinen <simo.piiroinen@jollamobile.com>

Provide fallback sensor maxDelay value

See merge request !29

Sensor maximum delay is available from sensors device API version 1.3
onwards. If development headers are too ancient, trying to access
maxDelay member in sensor_t structure causes compilation failures.

Use fallback value for maxDelay unless both development headers and
sensors device exposed via hal indicate that sensors device API version
1.3 features are available.
Signed-off-by: Simo Piiroinen <simo.piiroinen@jollamobile.com>

Provide fallback values for android sensor types

See merge request !28

The code can't be compiled for devices that use older android hal versions
that do not define all sensor types referred to in the code.

Provide values for all sensor types that are not defined in the android
header files.
Signed-off-by: Simo Piiroinen <simo.piiroinen@jollamobile.com>

Refactor sensor start/stop logic and tune als/ps default values

See merge request !27

It is possible that on-change type sensors are not reported by android
hal until a change is actually detected. Sensorfwd is left using zero
initialized default values like proximity=covered / light=darkness -
which in turn can cause various issues after each bootup.

As the initial state can't be queried, choose the lest harmful option
and define fallback values during sensor hal probing:
- proximity sensor = not covered
- light sensor = 400 lux

If no actual sensor data has been received in a situation where sensor
state needs to be communicated to clients, apply the fallback value.
Signed-off-by: Simo Piiroinen <simo.piiroinen@jollamobile.com>

Sensor specific adaptors derived from HybrisAdaptor class can be configured
to enable/disable sensors directly via sysfs. While doing that they also
bypass enable/disable policy that is implemented in HybrisAdaptor.

Fix each HybrisXxxAdaptor class so that common policy logic is executed
first, and direct sysfs manipulation is done based on policy decision.
Signed-off-by: Simo Piiroinen <simo.piiroinen@jollamobile.com>

Whether sensors should be started or stopped depends on a number
of state variables. Using case specific conditionals at places
where state variables might change makes the code fragile and
hard to maintain.

Separate sensor hal operations more clearly from logic and forms
dictated by sensorfwd conventions.

Use m_memberName naming convention for member variables, make
all member data private and usable only via accessor functions.

Use a single sensor start/stop policy evaluation function and
call it from each place where relevant state variables might
change.

Use sensorfwd specific logging functions instead of qDebug etc.
Signed-off-by: Simo Piiroinen <simo.piiroinen@jollamobile.com>