Fix the examples so they can be deployed on Android

Change-Id: I8d3b0c84091cf7743164c083318e0a115e948d1c
Reviewed-by: Lorn Potter <lorn.potter@jollamobile.com>
Reviewed-by: Topi Reiniö <topi.reinio@digia.com>
BlackBerry: Update threshold for close detection

The current algorithm for close detection in QProximitySensor will not
work for sensors whose output is not binary (ie, close/far). The new
algorithm will use the threshold of 8cm when the output is not binary.

Change-Id: I2173e9afae0a2d29434e092e1afc09d1c6f5647c
Reviewed-by: Bernd Weimer <bweimer@blackberry.com>
Reviewed-by: Fabian Bumberger <fbumberger@rim.com>
Remove unused and unlinked qdocconf file from the project.

Change-Id: I24ba7ae438d4763ca065d88147ff0a023c0ce85c
Reviewed-by: Lorn Potter <lorn.potter@jollamobile.com>
Doc: Append handler names to \qmlsignal documentation

Change-Id: I4754a36bd6977cc2bc83a3fee58fb5ce6d2c2c84
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>
Implement QAccelerometer accelerationMode

The Qt API does not expose Linear Accel and Gravity as separate sensor types,
they are different versions of QAccelerometer, accessed by modifying the
accelerationMode property. The possible values are Combined, User, and Gravity, which
correspond to Acceleration, Linear Acceleration, and Gravity respectively. When
constructing the accelerometer backend, the accelerationMode must be queried. The
backend must also connect to the accelerationModeChanged signal from the QAccelerometer.

I think that the existing implementation of QSensors on Android assumes that there is a
one-to-one correspondence between QSensors and AndroidSensorTypes. To fix this assumption,
I promoted the m_type attribute of androidcommonsensor.h from private to protected so
that a sensor backend can update the Android sensor being used.

Task-number: QTBUG-30531
Change-Id: I842d2485109542f74731d179e2720ea55fa248cc
Reviewed-by: Fabian Bumberger <fbumberger@rim.com>
Reviewed-by: Lorn Potter <lorn.potter@jollamobile.com>