Ask / Submit
6

Bug: Positioning gives bogus numbers for horizontalAccuracy and verticalAccuracy

asked 2014-01-18 20:17:31 +0200

MartinK gravatar image

updated 2014-01-18 20:18:28 +0200

Or to be more precise - they are always the same.

Minimal testcase:

import QtPositioning 5.2

PositionSource {
    active : true
    id: ps
    onPositionChanged: {console.log("h/v accuracy:", ps.position.horizontalAccuracy, ps.position.verticalAccuracy)}
}

Just run it with something qmlscene/sailfish-qml. You will get something similar to:

[D] QWaylandEglIntegration::QWaylandEglIntegration:58 - Using Wayland-EGL
h/v accuracy: -1 -1
QMetaMethod::invoke: Unable to handle unregistered datatype 'QGeoPositionInfo'
h/v accuracy: 20 20
h/v accuracy: 20 20
h/v accuracy: 20 20
h/v accuracy: 19 19
h/v accuracy: 21 21
h/v accuracy: 22 22
h/v accuracy: 23 23
h/v accuracy: 23 23
h/v accuracy: 22 22
edit retag flag offensive close delete

Comments

Great finding! I was suspecting there was a location related bug somewhere. Out of votes for today...

simo ( 2014-01-18 20:54:54 +0200 )edit

1 Answer

Sort by » oldest newest most voted
0

answered 2014-01-18 21:06:00 +0200

balta gravatar image

I've seen the same behaviour, the hardware of the Jolla is only giving one accuracy value.

See this Mailing-List entry: https://lists.sailfishos.org/pipermail/devel/2014-January/002819.html

edit flag offensive delete publish link more

Comments

Well, that's rather unfortunate if it really turns out to be a hardware limitation.

MartinK ( 2014-04-23 03:08:51 +0200 )edit
Login/Signup to Answer

Question tools

Follow
1 follower

Stats

Asked: 2014-01-18 20:17:31 +0200

Seen: 274 times

Last updated: Jan 18 '14