![]() |
great update. btw "apt-get install libsqlite0" worked for me (too bad it's not the new sqlite3)
i'll definately donate when i'm on a safe connection. edit: bug: when you add poi icons it looks funny (they're displayed in the wrong position) |
i took some photos of maemo mapper in action. check out http://nurey.blogspot.com/2006/10/i-...s-present.html
|
Hmm.. I also installed it and it worked fine when I loaded it. I enabled flite and when I attempted to subsequently load it nothing happened. When I load it from the console, I get a Seg fault.
I was going to remove the maemo-mapper config file and try again, but I couldn't find where the config details are stored ? I've restarted the device after removing the battery, and tried removing and reinstalling, no luck. Cheers |
To everyone that is having problems: if you know how to capture sample output from your GPS receiver, can you please PM that to me? I have been unable to reproduce the segfault problem, and it may be related to the NMEA output of your particular GPS receivers. If you don't know how to capture the NMEA output, at least let me know what GPS receiver you are using. (Is anyone using an iBlue GPS receiver and also experiencing segfaults?)
And if you don't mind sending me your gconf configuration data (from an xterm: gconftool-2 -a "/apps/maemo/maemo-mapper"), that may also be helpful. Thanks. |
And to those of you that are now unable to start maemo mapper at all, resetting your gconf settings may help you. From an xterm:
gconftool-2 --recursive-unset "/apps/maemo/maemo-mapper" NOTE: You will, of course, lose all your previously saved settings, although your maps will still remain where you had previously downloaded them (in order to see them, you may have to set your repository's cache dir after resetting your gconf settings). If you do end up resetting your settings, let me know if you experience further segfaults or other errors. It is possible that some of these issues are cropping up due to maemo-mapper 1.2's attempt to "upgrade" from the 1.1 settings layout. |
hi
maemo-mapper 1.2 not starter. From xterminal error /home/user # maemo-mapper osso_initialize failed. ~ $ maemo-mapper *** glibc detected *** free(): invalid pointer: 0x0005061e *** Aborted advice? thanks from Italy |
This is my fix for the:
*** glibc detected *** free(): invalid pointer: 0x0005061e *** problem. Patch (against svn): http://people.freedesktop.org/~skabo...er-fix-1.patch new binary (ARMEL): http://people.freedesktop.org/~skabo...o-mapper-fix-1 Luca |
Maemo-Mapper 1.2 is great! (Just one minor feature...)
Hi John,
this is a great "feature release". Thanks for integrating the features I requested (and demonstrated with my patches/modified 1.1 version). There is only one minor feature I proposed for 1.1 missing in 1.2, the "option to operate with closed cover": if gconf-setting /system/osso/connectivity/IAP/disconnect_on_cover is not true, then in osso_cb_hw_state() Code:
set_conn_state(RCVR_OFF); It would be great if you could integrate this feature, too. See also garage.maemo.org, feature request #106: https://garage.maemo.org/tracker/ind...id=29&atid=188 regards, Armin. |
No segfault after cleaning the configuration settings !
Thanks very much, the tool is excellent. Gav |
thanks for the new version of meamo-mapper
i am using the uri Code:
http://mt.google.com/mt?n=404&v=w2.25&x=%d&y=%d&zoom=%d and Code:
http://kh0.google.co.uk/kh?n=404&v=11&t=%s |
All times are GMT. The time now is 19:41. |
vBulletin® Version 3.8.8