I installed the update, started mapper, It started, began searching for the gps and showed my last location. I hit the menu key and the box displayed the nokia screen one gets when booting - it did not reboot though and none of the buttons would respond. After about 5 minutes I popped the battery.
I is working fine post reboot. Wonder if memory fragmentation is to blame - I use my n800 heavily.
I installed the update, started mapper, It started, began searching for the gps and showed my last location. I hit the menu key and the box displayed the nokia screen one gets when booting - it did not reboot though and none of the buttons would respond. After about 5 minutes I popped the battery.
Check the last-modified time of lifeguard_resets - was it around the time that the crash occurred? If so, then it sounds like the btcond program (which interacts with the bluetooth radio) crashed, likely as a result of Maemo Mapper searching for your GPS receiver.
I is working fine post reboot. Wonder if memory fragmentation is to blame - I use my n800 heavily.
Hopefully, it was just a one-time thing. If not, it could be a hardware problem like a memory RAM chip. Keep an eye out, though, especially if your unit is still under warranty.
I asked about the fuzzy levels a while back and IIRC it had to do with not downloading all the levels for a particular map. Soooo, I checked every level from 3 up and it do take days to get the updates for all of those :-(.
What levels does one *really* need? I think they are set for every map source rather than each map source, but I'm not sure about it. After I do a set and go look at the zooms again, it seems to be precious few checked.
I'll get an understanding of this wonderful piece of software eventually (or end up with a pocketfull of 16G SDHC cards (NOT) ;-).
I asked about the fuzzy levels a while back and IIRC it had to do with not downloading all the levels for a particular map. Soooo, I checked every level from 3 up and it do take days to get the updates for all of those :-(.
What levels does one *really* need? I think they are set for every map source rather than each map source, but I'm not sure about it. After I do a set and go look at the zooms again, it seems to be precious few checked.
A couple comments....
First, if you are using "Auto-Download", where Maemo Mapper automatically downloads any of the maps that you need, then the "fuzziness" is controlled by the "Download Zoom Steps" setting, which can be set on a per-repository basis via the "Manage Repositories" dialog. This setting controls which levels Maemo Mapper "skips" downloading.
Example: If "Download Zoom Steps" is set to the minimum level, then every zoom level is downloaded as necessary, but if set to the second-to-lowest value (two bars), then only the even zoom levels are downloaded, so if you are at zoom level 5, then Maemo Mapper will (automatically) download zoom level 6 instead. This saves space because (in my opinion) you don't need the accuracy of every single zoom level - having every other zoom level is sufficient. You can, of course, set it to 1 bar in order to force Maemo Mapper to download every zoom level as needed. Again, all of this only affects Auto-Download. Manually downloading via the "Manage Maps" dialog is not affected by the "Download Zoom Steps" setting.
Second, when you say "precious few checked," I think you're referring to the "Zoom Levels" tab of the "Manage Maps" repository? That tab doesn't list which zoom levels are downloaded or "enabled," but rather which zoom levels you want to download (or delete) manually at that moment. It doesn't affect Auto-Download.
ebug, some people have had success linking to a Bluetooth anything, phone, whatever.
Maemo Mapper may then find the internal GPS.
Some people have had success just firing up the Control Panel GPS widget.
Me, I seem to need the included Map program running in the background.
The developer hasn't got an N810.
I'm also have caching maps as well. I didn't have this problem in version 1.x
The SD card usually locks up and access to the card is denied by all apps even MM 2.x
I'm still having problems when trying to add WMS repository. After adding repository MM crashes immediately and MM does not start anymore. This is what I get when trying to start MM:
~ $ maemo-mapper maemo-mapper[1420]: GLIB WARNING ** Gtk - gtk_widget_size_allocate(): attempt to allocate widget with width -24 and height 0 maemo-mapper[1420]: GLIB DEBUG ConIc - con_ic_connection_send_event(0xf6c18, Tyo, WLAN_INFRA, 0) maemo-mapper[1420]: GLIB WARNING ** Gtk - gtk_widget_size_allocate(): attempt to allocate widget with width -24 and height 0 Segmentation fault ~ $
First, if you are using "Auto-Download", where Maemo Mapper automatically downloads any of the maps that you need, then the "fuzziness" is controlled by the "Download Zoom Steps" setting, which can be set on a per-repository basis via the "Manage Repositories" dialog. This setting controls which levels Maemo Mapper "skips" downloading.
Example: If "Download Zoom Steps" is set to the minimum level, then every zoom level is downloaded as necessary, but if set to the second-to-lowest value (two bars), then only the even zoom levels are downloaded, so if you are at zoom level 5, then Maemo Mapper will (automatically) download zoom level 6 instead. This saves space because (in my opinion) you don't need the accuracy of every single zoom level - having every other zoom level is sufficient. You can, of course, set it to 1 bar in order to force Maemo Mapper to download every zoom level as needed. Again, all of this only affects Auto-Download. Manually downloading via the "Manage Maps" dialog is not affected by the "Download Zoom Steps" setting.
Second, when you say "precious few checked," I think you're referring to the "Zoom Levels" tab of the "Manage Maps" repository? That tab doesn't list which zoom levels are downloaded or "enabled," but rather which zoom levels you want to download (or delete) manually at that moment. It doesn't affect Auto-Download.
Hope this helps.
I'll read it a few more times, for some reason I seem to be having a "dense moment" with all this.
Considering that I have been constantly downloading to the n800 since before I posted that message, methinketh that I might need to live with the fuzzies, if the progress bar "Processing Maps" is any indication, I have pretty much that much time again before it is done. Then if I move it to another area...
Nokia-N800-50-2:~# du -sh /media/mmc2/Maps/
1.3G /media/mmc2/Maps
Still beat out by the sdict dictionaries though :
Nokia-N800-50-2:~# du -sh /media/mmc2/Dictionaries/
2.1G /media/mmc2/Dictionaries
And I haven't even started the topo stuff (assuming I can find it again .
IF I am going to do this, perhaps it might be wiser to find my ethernet USB dongle and a module for it...
: