QRotationSensor values

[smitis]

Hi,

When I use QRotationSensor and values from reading->x() , there are values only like 0, 15, 30 , 45 simply with step 15° ... Is there any solution (like some setProperty or anything) like get value with step 1° (so 0,1,2,3,4 etc...) and not only 15°???

Thanks.

[rahulvala]

You can change that Rotation reading : http://doc.qt.nokia.com/qtmobility-1...nreading-units

Check this above article, If you face any problem write here.

[smitis]

I have looked over QRotationSensor very well, but I can`t see there some solution to resolve my problem. I want to only get values from roration sensor with step 1° (or smaller) and not with step 15°. Do you understand what I want?

[Devnull]

It may be more accurate create this 15° degree resolution from the raw QAccelerometerReading data. Unfortunately the pitch and roll calculation in not depending on any property.

/0

[Tiger54]

I think it is a Qt bug.

I always used this function and it always worked (with a step of 0.0001°). Since Qt4.7.4, I also get a step of only 15°!

Some times, if I restart my phone it works good the first time and after I restart the app, I get only this 15° step!

The angry thing, is that if I start an app compiled with the old Qt, the sensor works on that app!

[Devnull]

Please kindly create a bug report in that case.

[Devnull]

Other option to check the sensor's supported outputRanges(). However if the sensor backend accuracy is set to 15° not much can be done without communicating with the sensor with native APIs. The application may not even need to know which backend it connects to.

[Tiger54]

It is hard to follow you... It was so easy with mobility 1.1.2. After the sensor was created, I was able to read it and set a filter to filter the data. Now every thing I made, has no effect for this accuracy

I am not able to implement the native C code in my project. On my N8, if I check my outputranges, I get a list of 1 range:
min: -180, max: 180, accuracy: 0.0416667.

I was hoping that with the last update (yesterday) it worked again, but I get always an accuracy of 15°

EDIT: setting the outputrange to -1 (or also to 0) has no effect: mySensor.setOutputRange(-1);

[Devnull]

From 1.2.0 the system backends replace the generic backends, so exactly that is when the change had happened.

[Tiger54]

Do you think that it will be ever fixed for symbian phones? Or should I try to create the app with Qt mobility 1.1.2?

[vesao]

Hi,

Symbian Belle upgrade is causing this problem to my app as well. It's using QRotationSensor to control the app (game). It was working fine on Symbian^3/Anna and N9 using Qt 4.7.3 and QtMobility 1.1.3. Now rotation sensor returns only 0,15,30,.. degrees. The same problem occurs on app compiled against Qt 4.7.3 / Mobility 1.1.3 target and Qt 4.7.4 / Mobility 1.2.1 target.

Application output is showing following messages:
[Qt Message] loaded the Generic plugin
[Qt Message] Loaded the symbian sensor plugins
[Qt Message] loaded the Generic plugin
[Qt Message] Loaded the symbian sensor plugins
[Qt Message] A backend with type "QProximitySensor" and identifier "sym.proximity" has already been registered!
[Qt Message] A backend with type "QAmbientLightSensor" and identifier "sym.ambientlight" has already been registered!
[Qt Message] A backend with type "QMagnetometer" and identifier "sym.magnetometer" has already been registered!
[Qt Message] A backend with type "QCompass" and identifier "sym.compass" has already been registered!
[Qt Message] A backend with type "QOrientationSensor" and identifier "sym.orientation" has already been registered!
[Qt Message] A backend with type "QAccelerometer" and identifier "sym.accelerometer" has already been registered!
[Qt Message] A backend with type "QRotationSensor" and identifier "sym.rotation" has already been registered!
[Qt Message] A backend with type "QTapSensor" and identifier "sym.tap" has already been registered!

[Devnull]

Linking the solution from the relevant discussion here too.

[Tiger54]

Great

It worked, thank you!

Solution was to add following lines before starting rotation sensor:
rotationSensor->setIdentifier("generic.rotation");
rotationSensor->connectToBackend();

It works also by me

But I noticed that the accuracy is not anymore good like in version 1.0.2. Now I have an accuracy of 0.7°-0.8°.

It is surely better than 15°, but also 0.7° is not really the best what a N8 can offer.