maemo.org Bugzilla – Bug 3833
Request for information to allow hooking into A-GPS location framework
Last modified: 2012-03-24 11:45:03 UTC
You need to log in before you can comment on or make changes to this bug.
Basically, I'd like to be able to replace agps-ui with some other location providing application, and be able to hook into supld and let it know where I think we are, so that it can query the supl server and obtain AGPS information. This would allow us to provide an initial location using a GeoClue-type system, or to remove agps-ui and allow Maemo-mapper to provide this information via a higher accuracy tap (I know the accuracy doesn't need to be too high). It would also, hopefully, allow us to debug the operation of agps-ui and work out whether there are some problems obtaining the AGPS information, or if it's all down to the chipset being rubbish (either the hw, or the firmware). One way to do this, would be to release the source for agps-ui, or you could simply release the API used to talk to supld. On a related note, it would be interesting to know the format of the nvd_data file.
I should add that I've started this bug as a follow on from #2890 as the original request in that bug was met (and it was closed as I requested), but later ideas were not. This bug is to separate out those later ideas.
> One way to do this, would be to release the source for agps-ui, or you could > simply release the API used to talk to supld. CC'ing Quim here.
I've asked.
Alright, the answer is much easier to explain and understand once the Fremantle location framework is public (beta SDK, latest). Let's go back here once it is released.
agps-ui just sets 3 gconf settings, when you tap location Those are: /system/osso/supl/pos_latitude /system/osso/supl/pos_longitude /system/osso/supl/pos_timestamp If you want maemo-mapper to set those, you have to do it before you start gps.
Thanks. I assume that gpsdriver writes back into those when the gps is shut down? I'm happy we know what we need to about agps-ui, we can close this as resolved.
(In reply to comment #6) > Thanks. > > I assume that gpsdriver writes back into those when the gps is shut down? > > I'm happy we know what we need to about agps-ui, we can close this as resolved. > Yes, gpsdriver writes back to those, but not only on shutdown. Because assistance data is valid only for 30minutes and supld needs to update the cache if gps is used longer than that.
> Yes, gpsdriver writes back to those, but not only on shutdown. Because > assistance data is valid only for 30minutes and supld needs to update the cache > if gps is used longer than that. So supld will download data for the current location every 30min even if there's a working GPS connection? If the GPS is working, what can supld download that is of use at that point or indeed at any future point? Doesn't gpsdriver save the current almanac and ephemeris data as reported by the GPS chipset when it shuts down? Or are the data supplied to supld in some way more accurate (Long Term Orbit, etc.) than those saved by the GPS chipset?
If the gps is shut off or goes somewhere the signal can't reach, then goes back on again, the refreshed supld information would help. It might not matter with the gps constantly on and with a lock. But does it do the same with a bluetooth external GPS (if it gets a lock, does the supl gconf position/time get updated?). To repeat a request: a "pull now" button in the AGPS program - if the data is stale (or not - maybe it will go stale in 5 minutes - how much overlap - does fresh data last for an hour or 30 minutes?) Actually that is an important question. If there is no overlap between old and new data valid time, there is a window during the update where the data will be stale. So the data downloaded 29 minutes ago would be stale in 1 minute? Or longer? Also, the information posted here I think contradicts something in the Very Poor thread - The position and time for the gconf variables ARE updated by gpsdriver (periodically and upon shutdown) and not gpsd?
(In reply to comment #4 by Quim Gil) > Alright, the answer is much easier to explain and understand once the Fremantle > location framework is public (beta SDK, latest). Let's go back here once it is > released. Quim: ping ;-)
(In reply to comment #4) > Alright, the answer is much easier to explain and understand once the Fremantle > location framework is public (beta SDK, latest). Let's go back here once it is > released. So can somebody update the status here with regard to Maemo5/Fremantle please? Is this FIXED, is this WORKSFORME, is this still a valid issue? Simon?
We have the gconf keys, so we can replace agps-ui with our own code and tell the SUPL server where we are (and therefore where we want assistance data for), so I think the main gist of the request is probably resolved. There are of course other questions that have been brought up by tz and I'd really like to see those answered (which should be reasonably straight forward) before closing the bug. Thanks.
Those questions are related to Diablo, and nowadays I would even have a hard time getting those answers from whoever wrote the code for Fremantle. For what is worth, GeoClue is part of the MeeGo stack, and any UI is open there. I know this doesn't solve the questions for Maemo but this is the most practical answer I can give right now.
Thanks Quim, in fact I think Marko probably answered the question in comment #5, and we just continued with the bug as it was interesting. Thinking about legacy support/community images for the N8x0, it would still be nice to have some api to access the SUPL service (though I think the form of the communications can be determined from a careful study of the relevant standards) and in fact more information about the format of the assistance data that the GPS chipset requires (which we can't really do without lots of trial and error testing- it would be nice to release this if possible), but I think this bug can be closed as it has been answered.
The Maemo 5 User Interface and Maemo 5 platform components (e.g. libraries) used for the N900 are considered stable by Nokia and it seems that there are no plans for official updates currently, hence nobody plans to work on this enhancement/wishlist request. (And in case you feel like discussing this situation: Nokia Customer Care or http://talk.maemo.org would be the place to do so as you will not reach Nokia officials in this community bugtracker - though all of this is really no news.) Reflecting this status by setting RESOLVED WONTFIX for this enhancement/wishlist request (see https://bugs.maemo.org/page.cgi?id=fields.html#status for status explanations). There is a small chance for issues in those Maemo components that are open source: Contributed patches could be included and made available in the Maemo 5 Community CSSU updates. The Maemo CSSU project is run by a small team of volunteers; see http://wiki.maemo.org/CSSU for more information. So in case that you can provide a patch that fixes the reported problem, please feel encouraged to file a request under https://bugs.maemo.org/enter_bug.cgi?product=Maemo%205%20Community%20SSU . Please note: The Maemo CSSU project is not related in any way to Nokia. ( Tag for mass-deleting bugmail: [cleanup20120324] )