[hafqa] [hafqa] [Bug 2878] Very poor satellite acquisition with internal GPS

From: bugzilla-daemon at maemo.org bugzilla-daemon at maemo.org
Date: Fri Jul 11 04:23:08 EEST 2008
https://bugs.maemo.org/show_bug.cgi?id=2878





------- Comment #28 from advax at triumf.ca  2008-07-11 04:23 GMT+3 -------
If you strace supld you can see some info, e.g.:
SUPL daemon version is Mon May  5 12:12:24 UTC 2008
SLP address: supl.nokia.com
SLP port: 7275
A-GPS srv address: supl.nokia.com
Position timestamp: 1215295872.000000
Position latitude: 49.161850
Position longitude: -123.119431
Position uncertainty: 300
Previous A-GPS req time: 0
Previous A-GPS req status: 1
A-GPS support: 1
NW INIT enabled: 0
Cached assistance data support: 1
Packet data for assistance data allowed: 1
Preferred connection id: Rogers Internet
SetId NAI: JohnDoe at nokia.com
PSK EMSK:
Wimax BSID:
GSM Cell ID by BT support: 0
Debug SLP IP source: provisioned
Debug mode: 0
Debug log folder: /media/mmc2/supllog/

The changelog in the package file (stripped off on the tablet, but can be
downloaded) has some notes; apparently cell ID was turned off in 0.27)

I don't know how to turn on debug mode.

Re. TTF, as per my previous post when I have just had a fix then stopped the
GPS, I can get another in about 20 seconds - from using the library function to
start the GPS to getting a fix from gpsd. This includes some time to start up
gpsd and is probably as good as it gets with this hardware. Starting a mapper
application like maemo-mapper or navicore/wayfinder takes longer.

I have not tested extensively with supld running. Subjectively, it seems to
show satellite data faster than without. I did have it lock up once
as others have reported. Rebooting cleared it; I did not try restarting supld
manually.


-- 
Configure bugmail: https://bugs.maemo.org/userprefs.cgi?tab=email
Replies to this email are NOT read, instead please add comments at
https://bugs.maemo.org/show_bug.cgi?id=2878
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

More information about the hafqa mailing list