FWIW, I got my positioning working. Manifest/plist issues. It'd be nice to get these documented in the location or platform documentation. Especially since Qt is in the sub-obptimal role of opening devs up to new and unfamilar platforms.
 
Sent: Wednesday, August 26, 2015 at 5:09 AM
From: "Blasche Alexander" <alexander.blas...@theqtcompany.com>
To: "Federico Buti" <bacaro...@gmail.com>
Cc: "interest@qt-project.org" <interest@qt-project.org>
Subject: Re: [Interest] Qt positioning

Are you certain that the two non-working devices have a valid position fix? It is quite possible for a fix to take up to 2 mins and if GPS only is permitted and you are inside a building... Another test might be to check whether other apps (e.g. the maps app) can retrieve the position .

 

 

If you are certain that the above points are not the issue then I think it is time to put this into a bug report on https://bugreports.qt.io. The report should contain all the info already provided. In addition there should be information like any output you see on the command line. I am fairly certain it should mention something about provider.

 

When you press "Locate & Update", what does the display say? What is mentioned in the UI as source?

 

LBNL I'd like you to apply https://codereview.qt-project.org/#/c/124254/ before you run the example. This adds a bit more details on the output and improves error handling.

 

--

Alex

 

From: interest-bounces+alexander.blasche=theqtcompany....@qt-project.org <interest-bounces+alexander.blasche=theqtcompany....@qt-project.org> on behalf of Federico Buti <bacaro...@gmail.com>
Sent: Wednesday, August 26, 2015 09:37
To: Jason H
Cc: interest@qt-project.org
Subject: Re: [Interest] Qt positioning
 
Hi all.
 
Sorry for the delay in answering my own thread. Being busy doing other stuff I had no time to further test my issue. 
As suggested by Alex I've started studying the problem with the built-in examples. I've deployed the "Geoglickr" to my three devices. In accordance to the results I've obtained with my initial toy example the application correctly fetched coordinates on just one device out of three. More in details:
 
- Lenovo A806 [rooted with AOSP 4.4.2] 
nan values, hitting "Locate & update" does not change a thing
 
- Archos 50 Titanium [stock Android 4.2.2] 
Correct value dispayed at startup
 
- Galaxy Tab2 (GT-P7500) [stock Android 4.0.4] 
nan values, hitting "Locate & update" does not change a thing
 
Is there some trace/output I can attach or some other specific test I can execute? Should I add other relevant info (e.g. kernel version, build number)?
Thanks in advance,
F.
 
 
On 19 August 2015 at 22:24, Jason H <jh...@gmx.com> wrote:
Nope, did not know. Not really an iOS guy, but that key was it!

Thanks!

> Sent: Wednesday, August 19, 2015 at 2:43 PM
> From: maitai <mai...@virtual-winds.org>
> To: Interest@qt-project.org
> Subject: Re: [Interest] Qt positioning
>
> Very probably you know it already, you need to put that in your
> info.plist file:
>
>       <key>NSLocationAlwaysUsageDescription</key>
>       <string>Location information needed for whatever reason..</string>
>
> Le 19-08-2015 19:54, Jason H a écrit :
> >> Sent: Wednesday, August 19, 2015 at 5:33 AM
> >> From: "Blasche Alexander" <alexander.blas...@theqtcompany.com>>What is
> >> the status of this? I'm at a point now where the feature using
> >> positioning is on the radar.
> >>
> >> An invalid PositionSource is an indication that you don't even load
> >> the Position plugin/engine. In such scenarios you will never get any
> >> updates. I suggest you start testing the issue by using one of the
> >> provided > position examples (e.g. geoflickr or weatherinfo).
> >>
> >> The provided QML is just not enough to figure out why it might no load
> >> and indeed it may never be enough as it may depend on how you build
> >> and your application. Please don't post your entire application
> >> (unless it > is a very very small test case app or you are referring
> >> to an existing example) either though.
> >>
> >> Check that you are adding Qt+= positioning or otherwise the required
> >> plugins may not even be deployed.
> >  
> > Well it works for Android. On IOS, I just get NaN, NaN
> >
> > Everytime I relaunch the app in Creator, it clears the Location
> > permission. Location Services are on. I set this to "Always" for my
> > app. No result.
> >
> > Are there any special notes for iOS?
> >
> >
> > _______________________________________________
> > Interest mailing list
> > Interest@qt-project.org
> > http://lists.qt-project.org/mailman/listinfo/interest
> _______________________________________________
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Reply via email to