QAccelerometer gives x, y and z values as 0's

Bug #1541162 reported by Lorn Potter
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
qtubuntu-sensors
Invalid
Undecided
Unassigned

Bug Description

When using the sensors examples show_acceleration (console app), it outputs:

Acceleration: 0.0 x 0.0 y 0.0 z m/s^21454370684631437160 (5035 ms since last, 0.2 Hz)
Acceleration: 0.0 x 0.0 y 0.0 z m/s^21454370684636472560 (5035 ms since last, 0.2 Hz)
Acceleration: 0.0 x 0.0 y 0.0 z m/s^21454370684641507960 (5035 ms since last, 0.2 Hz)

I added some debugging output:

2016-02-03T11:33:03 (unknown:0) - void core::SharedAccelerometer::onAccelerometerReading(UASAccelerometerEvent*) 8.08527
2016-02-03T11:33:03 (unknown:0) - void core::Accelerometer::onAccelerometerReadingChanged(QSharedPointer<QAccelerometerReading>) 8.08527
Acceleration: 0.0 x 0.0 y 0.0 z m/s^21454463183653186648 (948448 ms since last, 0.0 Hz)
2016-02-03T11:33:03 (unknown:0) - void core::SharedAccelerometer::onAccelerometerReading(UASAccelerometerEvent*) 8.09122
2016-02-03T11:33:03 (unknown:0) - void core::SharedAccelerometer::onAccelerometerReading(UASAccelerometerEvent*) 8.03052
2016-02-03T11:33:03 (unknown:0) - void core::Accelerometer::onAccelerometerReadingChanged(QSharedPointer<QAccelerometerReading>) 8.09122
Acceleration: 0.0 x 0.0 y 0.0 z m/s^21454463183921863406 (268676 ms since last, 0.0 Hz)

You can see the values are getting lost somewhere.

qml app seems to work fine.

Revision history for this message
Lorn Potter (lorn-potter) wrote :

changing this to invalid.
A recompile of example app and is working fine.

Changed in qtubuntu-sensors:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.