I tried with a recent andnav2 version and it doesn't have this issue. There must be a difference with our way of using the OpenStreetMapTileFilesystemProvider instance, and especially its database connection.
I tried with a recent andnav2 version and it doesn't have this issue. There must be a difference with our way of using the OpenStreetMapTi leFilesystemPro vider instance, and especially its database connection.