Bump module version to 5.4.0

Change-Id: Icd7c227040671925afa112d353603c16c8e241f4
Reviewed-by: Sergio Ahumada <sahumada@blackberry.com>
Reviewed-by: Lars Knoll <lars.knoll@digia.com>
Fix autotests expecting a trailing whitespace for qDebug stream

The behavior of QDebug was fixed in qtbase. Update autotests
accordingly.

Change-Id: Iec8d28f18ca6f5ff1ae960e74d0d978b212ca60b
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@digia.com>
Reviewed-by: Lorn Potter <lorn.potter@jollamobile.com>
Merge remote-tracking branch 'origin/stable' into dev

Change-Id: I3305a1b8bf20b36ad614d1d0492d6a81eb99278a
Merge remote-tracking branch 'origin/stable' into dev

Change-Id: Icf78a6052ee367ea11638443dd4cf7ecfaf606e3
Create a new sensor type for distance.

Create a new sensor type for distance. This sensor type supports new hardware sensors
that can measure physical distance from the device, in centimeters. The API is designed
to mimic the Android API for proximity (TYPE_PROXIMITY), so that if a given proximity
sensor only supports a binary measurement (near vs far), then instead of reporting distance
in cm, the QDistanceSensor will return the max range value to represent far, and a lesser
value to represent close. Using this definition should simplify implementation.

The main reason for not implementing this as a new property of QProximitySensor is that
clients of QProximitySensor have made the assumption that they will receive the readingReady
signal if and only if the reading has changed from near to far or vice versa. Adding a
distance property will break that assumption, as distance has a higher degree of precision.

Change-Id: Ia804948c78ff7391fc8b78df975cddcf861326dc
Reviewed-by: Fabian Bumberger <fbumberger@rim.com>
Reviewed-by: Bernd Weimer <bweimer@blackberry.com>
Reviewed-by: Lorn Potter <lorn.potter@jollamobile.com>
Merge remote-tracking branch 'origin/stable' into dev

Change-Id: I6b203a32b2f52255ae4e63cfb279e762458c0128
Merge remote-tracking branch 'origin/stable' into dev

Change-Id: I07a6842afc72f56c82e82906429fa422f9a82de2
fix obs build

Change-Id: Ia70486a0c6b813829ffd633f5334945f73d3b628
Reviewed-by: Lorn Potter <lorn.potter@jollamobile.com>
send first proximity signal even when it's "closed".

This fixes a bug where the proximity sensor would send the initial
signal only when it was not closed. This will send it regardless.

Change-Id: I5f388e671091ae2a7719f700a049cea41bfaa0db
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
Doc: Fix qmlclass selector used in documentation config

A recent change (46959875) in qdoc raised QML types from
subnodes to top-level nodes. This change modifies the
documentation configuration file(s) accordingly.

Change-Id: Iac59992a7ed9bf389502834d0bc694f3e64621b6
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>
Reviewed-by: Martin Smith <martin.smith@digia.com>
Merge remote-tracking branch 'origin/5.3' into dev

Conflicts:
	.qmake.conf

Change-Id: Ia804a9a975baea0f971c7bea004c5ce403d1adee
Bump version

Change-Id: I0ac4e13a17aaff50027c94e06ee1f4f71aa3cdb4
Merge remote-tracking branch 'origin/5.3.1' into 5.3

Change-Id: I04906f381fefa4a60e4a31021d282253a632f833
Merge remote-tracking branch 'origin/5.3' into dev

Conflicts:
	.qmake.conf

Change-Id: I01306a5c0d34f85efdbc5f947add4dee0cccbf8e
Doc: Removing url variable from qdocconf file.

-url inherited from the url variable set in qtbase/doc/global

Change-Id: I0bab30bfd8e6f386aa94c2e28d13184fde9af63c
Reviewed-by: Martin Smith <martin.smith@digia.com>
Register all QtSensor QML types for version 5.4

Change-Id: I6afcbcf691e203491ee563168c19d084c051a449
Reviewed-by: Frederik Gladhorn <frederik.gladhorn@digia.com>
[sensorfw] need to run init after sensord has been restarted

This ensures things are setup and work properly.

Change-Id: I23c8b53e760d49695c5ae207eed77a2e7d2be3a4
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
Series of crash fixes from Mer, squashed

        1)tracing plugin loading

        2)m_remoteSensorManager can be nullptr

        But it seems it does not solve incorrect initialization in the case
        manager interface is nullptr: init() for different sensors does not
        check initDone

        3)split initSensor() to template function and function

        most of initSensor() does not depend on template param, so it is
        better to split it -> less code should be generated

        4)do not use sensor manager if it is invalid

        5)correct class members initialization order

        6)assert sensor interface is not null

        From what I saw according to logic it should not happen so using
        Q_ASSERT for better maintainability

        7)check local interface pointer in SensorfwTapSensor::start()

        Signed-off-by: Denis Zalevskiy <denis.zalevskiy@jolla.com>

Change-Id: I5c1bf3999ad2268c0dba9b3fe511d999c2e63fd9
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
Restore setting of sensors interface.

Change I5c1bf3999ad2268c0dba9b3fe511d999c2e63fd9's forward porting from Qt 5.1
removed this, thus the interface was never set, thus sensors all broke.

Change-Id: If3b14b5ebd20e6cb64bc2000b23a2c1e37d36b05
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
Add missing word to QCompass documentation.

Change-Id: I46b9a3c20b5169843292057439c80c859ccc7e82
Reviewed-by: Lorn Potter <lorn.potter@jollamobile.com>