Hi, this is very interesting. I wanted to start a thread about not getting position data, when I saw this thread....
On Thu, 2011-03-31 at 19:38 +0300, Juha Turunen wrote: > On Thu, Mar 31, 2011 at 6:32 PM, Harri Pasanen <[email protected]> wrote: > > Also it would seem to me that mobility has sometimes trouble waking up the > > GPS, in that I get no position updates at all, unless I "prime" it by > > running > > Nokia Maps first. Would that be possible, or does it sound hogwash? > > I've noticed the same, so it's probably not hogwash. My app might > simply not get any coordinate updates for minutes and instantly after > starting Nokia Maps they start pouring in. I've also noticed that on > some devices (S^3, unlocked, nothing special) the QtMobility's > positioning doesn't work at all unless you manually disable the > network/wi-fi (not network based) positioning module from the device's > settings. My (not always reproducible) experience so far on Nokia C7 with Qt 4.7.2 and QtM 1.1.1: Indoor WLAN and GSM: - Running my app alone, I don't get any position updates at all. - Ovi Maps gets a position just fine. - Running Ovi Maps and my app in parallel I can get at least some data when calling lastKnownPosition(). - After disabling the "Wi-Fi/Network" positioning method I get position updates. Outdoor GSM: - It looks like if I have a GPS fix, I also get position updates. But I'm not completely sure about that yet. Also it looks like the Symbian implementation differs from the Maemo5 implementation. On Maemo5, if I do setUpdateInterval(1000), I'll get a signal every second whether or not the position has actually changed. On Symbian it looks to me that I only get a signal if the position really has changed. Cheers, Conny _______________________________________________ Qt-mobility-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt-mobility-feedback
