| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
.qmake.conf
Change-Id: Ic691e11af371acfb7706ee218665fb5a9f96a9c3
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
According to documentation, changing the mode shall have no effect when
the device does not support a particular mode.
Task-number: QTBUG-76862
Change-Id: I805daa3a3f659e8aed25e4b7b6531f804dd654b2
Reviewed-by: BogDan Vatra <bogdan@kdab.com>
|
|\|
| |
| |
| |
| |
| |
| | |
Conflicts:
.qmake.conf
Change-Id: Ib6ec0928ab14e075b35648ce0da4efc293be9c94
|
| |
| |
| |
| |
| |
| |
| | |
Fixes: QTBUG-76384
Change-Id: Ib1977ea1371e3a82ca14d1c7c450984fa40cd71d
Reviewed-by: Vyacheslav Koscheev <vok1980@gmail.com>
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
|\|
| |
| |
| | |
Change-Id: I71deece5315cb9b29bd9bc72c3198c80c9d14442
|
| |
| |
| |
| |
| |
| | |
Fixes: QTBUG-74905
Change-Id: I78ca045d2723fa47dc2d0f9cc559320be84e5f32
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
|\|
| |
| |
| | |
Change-Id: Iff501d1162491fafeb9aaf0a68927ade79b3b6e7
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Until Qt 5.9, we had to use JNI way because the NDK sensors API was
introduced in API-16. Starting with Qt 5.9 we can safely use the NDK API
as API_16 is the minimum API supported by Qt.
Using the NDK API instead of JNI boost the performance a lot! The CPU
usage dropped 2 to 4 times, from over 60% using the JNI to less than
20%.
[ChangeLog][Android] Rewrite Qt Android Sensors using NDK
API.
Change-Id: If3e3f1e56973e2a189662912b2a6ebfbd71dee14
Reviewed-by: Lorn Potter <lorn.potter@gmail.com>
|
|/
|
|
|
|
|
|
|
| |
Move the variable to the implementation section to silence:
"warning: declaration of instance variables in the interface
is deprecated"
Change-Id: I2381995d4fdaea83e0af6687faa140b249da3e3d
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>
|
|
|
|
|
|
|
|
|
| |
[ChangeLog][Platform Specific Changes][Android] QCompassReading::calibrationLevel
now returns a valid value when possible.
Change-Id: Ia7b6af9fc14d4edc4ce04af251eb29c84f08b957
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
Reviewed-by: Lorn Potter <lorn.potter@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The sensorfw plugin assumes that both proximity state query and change
notifications use the same withinProximity boolean type values. Because
the state query actually returns integer distance, the initial value
visible in for example QML ProximitySensor is logically reversed from
what it should be and it requires one or two sensor state transitions
before changes get notified in the expected manner.
Evaluate initial proximity state as "distance" value where zero means
that the sensor is covered.
Also use the initial value to setup the cached previously seen value
instead of blindly assuming that sensor is not covered.
As suggested in sensorfwd documentation: Switch from deprecated
dataAvailable() signal to reflectanceDataAvailable() signal.
Signed-off-by: Simo Piiroinen <simo.piiroinen@jollamobile.com>
Change-Id: I49e5607134848dc3c72e79733321df6251b7df52
Reviewed-by: Lorn Potter <lorn.potter@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The device orientation angles provided by QTiltSensor were being
incorrectly calculated from the accelerator sensor measurements,
in all supported devices. This resulted in a restricted range of
values reported for the roll angle, thus making non-equivalent
device orientations, like a tablet lying horizontally with the
screen up, and the flipped configuration with the screen down,
report equivalent orientation angles, making it impossible to
distinguish between them.
Task-number: QTBUG-57898
Change-Id: I82c1d4d2c1eab435f389b89dbb537fa7b349cbf1
Reviewed-by: Lorn Potter <lorn.potter@gmail.com>
|
|\
| |
| |
| | |
Change-Id: I11b81861a0dcd8380374060161550690812ff96d
|
| |
| |
| |
| |
| | |
Change-Id: I69f37f9304f24709a823fffd14e676c097712329
Reviewed-by: Edward Welbourne <edward.welbourne@qt.io>
|
| |
| |
| |
| |
| | |
Change-Id: I51c0fc424f44ae68c3c1c4cf6377e7701ee5a0dd
Reviewed-by: Lorn Potter <lorn.potter@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
[ChangeLog][QSensorBackend] Support for TI Sensortag sensor board.
Introduce env var QT_SENSORTAG_ID for specifying a specific
sensor tag. On mac, this is the sensortag uuid, on linux
it is the sensor tag's bluetooth address.
Change-Id: I7c5db8dac15ddbfdb0709bd6462759b4a70d32b7
Reviewed-by: Lorn Potter <lorn.potter@gmail.com>
|
| |
| |
| |
| |
| | |
Change-Id: Ib258bbc787f43e563fff8af8151ceae87471c672
Reviewed-by: Lorn Potter <lorn.potter@gmail.com>
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
| |
This removes the pre-dexed JAR files activated by the absence of the
bundled_jar_file CONFIG option, as versions of Android >= 5 no longer
support this deployment mechanism.
Now, the "bundled" JARs simply become normal JARs containing class
files, and are neither activated by a bundled_jar_file CONFIG entry nor
do they have a -bundled suffix in the file's base name.
Task-number: QTBUG-62995
Change-Id: I23fe81254efee5517453f73b1938026257ddb7a6
Reviewed-by: BogDan Vatra <bogdan@kdab.com>
|
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
.qmake.conf
Change-Id: Ib23a0c24c0ec5758dd0799a443c5e43ce7c5f35b
|
| |
| |
| |
| |
| | |
Change-Id: Ibda65cd63dcf277730044da04ee30b68513f95ee
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
|
| |
| |
| |
| |
| | |
Change-Id: Icd0e0d4b27cb4e5eb892fffd14b5285d43f4afbf
Reviewed-by: Lorn Potter <lorn.potter@gmail.com>
|
|\|
| |
| |
| |
| |
| |
| | |
Conflicts:
.qmake.conf
Change-Id: Iac052b07a815ed6bcaea42109895e323342c5d71
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Remove unused old license files
- Update BSD and FDL license headers
- Unify licensing
* Examples are nowdays licensed under BSD, update correct license
header to there
* Tools and tests are nowdays licensed under GPL-EXCEPT, update
correct license header to those
* Src is nowdays licensed under LGPL, update correct license
header to there
Task-number: QTBUG-57147
Change-Id: I5d9d7a3bc5e360f01ec73fb6a2a873f3173b5918
Reviewed-by: Lars Knoll <lars.knoll@qt.io>
Reviewed-by: Lorn Potter <lorn.potter@gmail.com>
|
|/
|
|
|
|
|
|
|
| |
They document intent more clearly than arithmetic with pi does.
Also eliminate some hand-rolled RADIANS_TO_DEGREES constants in
favor of calling qRadiansToDegrees().
Change-Id: I7ca5e876b3591433bf681b56ad51c4cb409ac59f
Reviewed-by: Lorn Potter <lorn.potter@gmail.com>
|
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
src/plugins/sensors/ios/ios.pro
Change-Id: I8d9ca692713c8ba5d8c243371474b0e61630b05e
|
| |
| |
| |
| |
| |
| |
| | |
'override' keyword can be used directly since Qt 5.7.
Change-Id: Ibf0fc590f7e247a310a833a22ece700ec75199bb
Reviewed-by: Lorn Potter <lorn.potter@canonical.com>
|
| |\
| | |
| | |
| | | |
Change-Id: I912756c6bbecf7c55acd60d136ea6ce490118ebb
|
| | |\
| | | |
| | | |
| | | | |
Change-Id: I77e9c7f825716af5ab4a1c04551f89e22099696e
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Android reports accuracy in four different levels (0, 1, 2 and 3),
these values were used directly in Qt, so the reported values would be
outside Qt documented range, which is a floating point number between
0 and 1.
Task-number: QTBUG-57184
Change-Id: I912a76bffd3e205689103b0352ea4c480d660d63
Reviewed-by: Lorn Potter <lorn.potter@canonical.com>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Make light sensor value consistent with timestamp
Change-Id: If6d5f15e2c645e86852a5b66cf0894a1e2ca3f1c
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Don't invoke pkg-config at build time, automatically check
for sensorfw and compile the correct plugin if found.
Change-Id: I30dcd41cdebd7cf082cec66f3122c24fbab5c893
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@qt.io>
Reviewed-by: Robin Burchell <robin.burchell@viroteck.net>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
watchOS supports accelerometer, gyroscope, and magnetometer.
tvOS supports only the proximity sensor.
No sensors are available on macOS yet, but the plugin is still built
there because many of the underlying APIs are available cross platform
and so some macOS sensors can appear here in the future.
Change-Id: I1668d81f09c745e60c1906be621a74f969841566
Reviewed-by: Mike Krus <mike.krus@kdab.com>
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@theqtcompany.com>
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Change-Id: I57123eed34ee4618f1cba643c2ce49c8c621a6cd
Reviewed-by: Lorn Potter <lorn.potter@canonical.com>
|
|\| | |
| | | |
| | | |
| | | | |
Change-Id: Iaeb7c9f62b50d68e0cedb95c523aebcceb9128c0
|
| |\| |
| | | |
| | | |
| | | | |
Change-Id: I35021aba57d8acc6b6e27e9800c6a244cb0e99da
|
| | |\|
| | | |
| | | |
| | | | |
Change-Id: I14345192d06a8a0ac9000feab6daea0f11b41f72
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When a Qt sensor is told to stop, it automatically stops the underlying
OS sensor as well. This caused a problem when several Qt sensors were
running, since stopping one would stop them all.
This patch will add a ref count for each affected sensor, so that we
keep track of when it's safe to start and stop the underlying OS sensor.
Task-number: QTBUG-54977
Change-Id: If06c4daac22916feef2f4c7bd521363d74f342a6
Reviewed-by: Edward Welbourne <edward.welbourne@qt.io>
Reviewed-by: Lorn Potter <lorn.potter@canonical.com>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
A compass has 360 degrees, not 365.
Change-Id: I2f0628fa0151434b1b529fbefd1a4bab9de99a8a
Reviewed-by: Edward Welbourne <edward.welbourne@qt.io>
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | | |
Static linking was hiding the Foundation.framework dependency.
Change-Id: I7c038488196d31d18c5174020c69dd03f15fa6f3
Reviewed-by: Lorn Potter <lorn.potter@canonical.com>
|
|\| |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
.qmake.conf
Change-Id: I4be6cbe9e4ac981f46b3c45d271cac5c7fc677cb
|
| |\|
| | |
| | |
| | | |
Change-Id: I53d801a88bda3a8b8519b6002e1d37053c03e103
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since Android 5.0 Google introduce a nasty bug[1] which calls
JNI_OnLoad more than once.
Basically every time when a library is loaded JNI_OnLoad is
called if found, but it calls *again* JNI_OnLoad of its .so
dependencies!
[1] Workaround https://code.google.com/p/android/issues/detail?id=215069
Change-Id: I34728572bc279581b8c95c42c206ed104bfc09a5
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
OpenBSD does not provide librt.so for the sensors module, which leads to
linker errors in this case. Disable linking to librt.so by adding
!openbsd to the list of OSes not having it.
Change-Id: If7b33eb33b4027be79bce4bb3272bef3a5b7d832
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Coverity noticed uninitialized members (CID 22309). Eliminate members
handler (never accessed or set; the code always uses
QtSensorGestureSensorHandler::instance() instead) and lastTs (set but
never accessed). Initialized timer (to 0; it'll be set more sensibly
as long as create() gets called). Reformatted constructor.
Change-Id: I41738ec51db94fb35e068af509e9a34bf9221770
Reviewed-by: Lorn Potter <lorn.potter@canonical.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Task-number: QTBUG-54506
Change-Id: I83576e79f12556479a43aac95123edcacd50c63c
Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
More efficient if all you want is the number of seconds.
Change-Id: Ib57b52598e2f452985e9fffd145a371003ede342
Reviewed-by: Lorn Potter <lorn.potter@canonical.com>
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
When sensorfw is restarting/recovering DBus service is
momentarily not available. Give it another change once
the service becomes registered.
Change-Id: I6fd3e5985ac60cfffbc84ff86aabe9cebe110ab6
Reviewed-by: Lorn Potter <lorn.potter@canonical.com>
|
|\|
| |
| |
| |
| |
| |
| | |
Conflicts:
src/sensors/doc/src/compatmap.qdoc
Change-Id: I7bd464cbd506f630798091fef3896050ade7b3f8
|
| |
| |
| |
| |
| |
| |
| |
| | |
this fixes static builds by ensuring that all dependencies are exported.
Task-number: QTBUG-51071
Change-Id: Ia3c3f69505650fd35982fc76e385e744b877e4df
Reviewed-by: Joerg Bornemann <joerg.bornemann@theqtcompany.com>
|
|\|
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
.qmake.conf
src/sensors/doc/src/compatmap.qdoc
Change-Id: I4049bc3c335a8a9db5c935032207d0bcfba78480
|