Opened 3 years ago

Last modified 3 years ago

#1289 new defect/bug

Android map size (r6035 related)

Reported by: jandegr Owned by: cp15
Priority: major Milestone:
Component: port/android Version: git master
Severity: normal Keywords:
Cc:

Description

I have used selfbuilt maps of 3.5GB on Android for a long time and seeing r6035 I downloaded a map of Germany with the Android mapdownloader before the 1.8GB limit was imposed. Downloading and a brief test of the map went just fine. I am aware of the 4GB filesize limit of fat SDcards and there may be devices where sometimes a 2GB limit is in place but the limit imposed by r6035 is too restricting. Now nobody can downlad a map of France or Germany to name a few. In the past I have seen some message about a 2GB limit in the logs but I just ignored it and kept using 3+GB maps.

What did I overlook ?

Change History (1)

comment:1 Changed 3 years ago by jandegr

A little more info :

Tested on Android 4.2 The downloaded Germany map seems to be some 2,64GB in size.

the log says :

error:navit:file_int:Maps larger than 2GB are not supported by this binary,
sizeof(off_t)=4


 

which originates from file.c

enabling both the selfbuilt 3+GB map, covering The Netherlands + Belgium + France and the 2,64GB downloaded map covering Germany, I could even plan a route from a point on the one map onto a point on the other map

Last edited 3 years ago by jandegr (previous) (diff)
Note: See TracTickets for help on using tickets.