Opened 4 years ago

Last modified 4 years ago

#1126 new defect/bug

Navin on Android download map error

Reported by: skupko sk Owned by: cp15
Priority: major Milestone: version 0.5.1
Component: port/android Version:
Severity: Keywords:
Cc:

Description

I am constantly getting the error during the download of Europe map on Android 4.0.4 running on Prestigio PMP5770D. The download finishes with error "Error downloading map!" on 72% (4194368 bytes).

Change History (2)

comment:1 Changed 4 years ago by mvglasow (2)

That is a limitation of the file system. Android downloads to /sdcard/navit, which is FAT formatted and has a 4 GB file size limit. That is exactly where your download stops, as the file gets too big for the filesystem to handle. The whole Europe map is currently (planet 130621) around 6 GB in size.

As a workaround: if you don't need all of Europe, try downloading a smaller region, like just a single country. You can download multiple countries, but that may produce some strange routing for neighboring countries, as the border region will be covered by two maps and Navit will see each object twice.

Or download manually from http://maps.test.navit-project.org. Select your region, choose "split at 4000 MB". You will be offered multiple files to download, get each of them and place them in /sdcard/navit on your phone. (You can delete all *.bin for maps you no longer need.)

Note: the split download seems broken at the moment, reporting "Selected planet does not exist". You can try playing with the link, lowering the number after "&timestamp=", e.g. "&timestamp=130621" instead of "&timestamp=130622" until the download starts (this did the trick for me today).

To the devs: I have used split binfile maps from http://maps.test.navit-project.org since it went live in January and, as long as the download worked, they worked like a charm. Please, please, please go live with that feature. Also it would make sense to automatically request split binfiles in the automatic map download on Android. A quick and dirty, hardcoded 4 GB threshold would already do the trick for most devices. Querying maximum file size for the target file system and splitting at that size would be perfect, of course...

comment:2 Changed 4 years ago by usul

  • Milestone set to version 0.5.1
Note: See TracTickets for help on using tickets.