Re: GPS stopped working, can't figure it out... what else?
On 10 July 2010 04:42, Yaroslav Halchenko site-openmoko@onerussian.com wrote: On Fri, 09 Jul 2010, Joachim Ott wrote: I had the same problem with the new shr-unstable image. I got me some assist data from u-blox and fed them into /dev/ttySAC1. It still took khm... would you mind sharing what 'assist data' that was? and how you got around getting it? I got me a password from u-blox.com and use the script from this page: http://wiki.openmoko.org/wiki/Neo_FreeRunner_GPS#GTA02_GPS_Hardware_Assist_Feature (the python one). I set the values for lat and lon to known values (for me lat=52.375756;lon=13.651114;) and feed the output into /dev/ttySAC1 - this speeds up finding satellites alot. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: GPS stopped working, can't figure it out... what else?
khm... would you mind sharing what 'assist data' that was? and how you got around getting it? I got me a password from u-blox.com and use the script from this page: http://wiki.openmoko.org/wiki/Neo_FreeRunner_GPS#GTA02_GPS_Hardware_Assist_Feature (the python one). I set the values for lat and lon to known values (for me lat=52.375756;lon=13.651114;) and feed the output into /dev/ttySAC1 - this speeds up finding satellites alot. This is an important action if you're using the GPS. The wiki discussion cited above could use some cleanup but the information you need is there. Anyone using a FR device and wanting to use the GPS should be using this. There's even a version for Android On OM at http://androidgps.blogspot.com/2009/02/priming-openmoko-u-blox-gps-chip.html ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: GPS stopped working, can't figure it out... what else?
some cleanup but the information you need is there. Anyone using a FR device and wanting to use the GPS should be using this. There's even a version for Android The alternative is to keep GPS constanly on but in low power state. This gives you privacy and you don't need internet connectivity either. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: GPS stopped working, can't figure it out... what else?
thanks everyone -- I will check it out although I am a bit confused since * originally GPS worked for me without AGPS at all, just TTFF was around 2 min * I thought AGPS feeding chip with previous locations was already implemented and that is why there is a button to remove AGPS data if you rellocate (used it few times, and then again acquired time/fix within few minutes) now I am experiencing now fixation (or even time acquisition) at all, which sounds somewhat different... but ok -- I guess I better check first what effect I would get with online assistance. On Sat, 10 Jul 2010, Ian Darwin wrote: I got me a password from u-blox.com and use the script from this page: http://wiki.openmoko.org/wiki/Neo_FreeRunner_GPS#GTA02_GPS_Hardware_Assist_Feature (the python one). I set the values for lat and lon to known values (for me lat=52.375756;lon=13.651114;) and feed the output into /dev/ttySAC1 - this speeds up finding satellites alot. This is an important action if you're using the GPS. The wiki discussion cited above could use some cleanup but the information you need is there. Anyone using a FR device and wanting to use the GPS should be using this. There's even a version for Android On OM at http://androidgps.blogspot.com/2009/02/priming-openmoko-u-blox-gps-chip.html -- .-. =-- /v\ = Keep in touch// \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User^^-^^[17] ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: GPS stopped working, can't figure it out... what else?
On 10 July 2010 15:48, Timo Juhani Lindfors timo.lindf...@iki.fi wrote: some cleanup but the information you need is there. Anyone using a FR device and wanting to use the GPS should be using this. There's even a version for Android The alternative is to keep GPS constanly on but in low power state. This gives you privacy and you don't need internet connectivity either. How to I set that low power mode? GPS time is the cheapest clock source on the FR. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: GPS stopped working, can't figure it out... what else?
Joachim Ott jo.o...@googlemail.com writes: The alternative is to keep GPS constanly on but in low power state. This gives you privacy and you don't need internet connectivity either. How to I set that low power mode? GPS time is the cheapest clock source on the FR. I personally do darcs get http://iki.fi/lindi/darcs/ubx cd ubx ./set-nmea.py off ./set-periodic-logging.py off ./set-fixnowmode.py on to turn the power saving mode on and then use ./set-fixnowmode.py off ./set-nmea.py on ./set-periodic-logging.py on to return to normal mode. If you want to suspend you also need to say om gps keep-on-in-suspend 1 to make sure that the GPS stays on during suspend. NOTE: This works only if you make sure that no other process is using /dev/gps (om is part of omhacks which you can get from debian or SHR (I think) or http://git.debian.org/?p=pkg-fso/omhacks.git;a=summary Note that I added 2.6.32 support just yesterday to iki.fi/lindi/git/omhacks and it hasn't been propagated yet to SHR or debian.) -Timo ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: GPS stopped working, can't figure it out... what else?
On Saturday 10 July 2010, Yaroslav Halchenko wrote: thanks everyone -- I will check it out although I am a bit confused since * originally GPS worked for me without AGPS at all, just TTFF was around 2 min It still should work. TTFF will be ~40s in ideal conditions, longer as * I thought AGPS feeding chip with previous locations was already implemented and that is why there is a button to remove AGPS data if you rellocate (used it few times, and then again acquired time/fix within few minutes) It is, but I think there are deficiencies in the implementation. It seems to save incorrect data in some situations (like shutting down gps before it has a fix), then load it next time the GPS is started. Depending on how lucky you are it can then take a long time to get a fix, or not get one at all. In this case shut down the gps, remove the stored data, then start the gps again. now I am experiencing now fixation (or even time acquisition) at all, which sounds somewhat different... but ok -- I guess I better check first what effect I would get with online assistance. On Sat, 10 Jul 2010, Ian Darwin wrote: I got me a password from u-blox.com and use the script from this page: http://wiki.openmoko.org/wiki/Neo_FreeRunner_GPS#GTA02_GPS_Hardware_Ass ist_Feature (the python one). I set the values for lat and lon to known values (for me lat=52.375756;lon=13.651114;) and feed the output into /dev/ttySAC1 - this speeds up finding satellites alot. This is an important action if you're using the GPS. The wiki discussion cited above could use some cleanup but the information you need is there. Anyone using a FR device and wanting to use the GPS should be using this. There's even a version for Android On OM at http://androidgps.blogspot.com/2009/02/priming-openmoko-u-blox-gps-chip.h tml ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
