Did you change from a different (previous) source?
I can comment that using the source in Post #9 consistently the update to beta-6 actually worked just fine. (Previously I think I had treated it as a reinstall.)
Incidentally the Post #9 source is the url in your error. I first read your post as an update.
Edit. Your error seemed to suggest same, but perhaps yours was a fresh install?
Yes, it was a fresh installation.
I have removed the app from Obtainium, deleted the cache and tried the link from the wiki again. Again the above error occurred.
Now I have installed the murena maps app manually, by downloading it from gitlab.
It works but without the automatic updates by Obtainium.
Since Beta6 public Transport routing feels kinda ready & perfect for official release. Way better than in most of other APPs. From my opinion it can also be competitive to Google maps.
There still has to be some improvements in searching, downloading offline maps, and routing, but i think they are on a good way 
Is it possible, that this error occurred installing on my tablet, because I had installed Murena Maps on my phone already?
Both devices are registered in my Murena account.
Is there a how to use this map ? Because for now I really donāt understand this app. Where are the options ? You canāt choose if you want to take highway or no ? Choose if you want the shortest way in kilometres or in timeā¦etcā¦ ? Just questions because I donāt understand, not free criticism.
But for the moment Magic Earth is more easy for me to use and understand.
These are called āRouting profilesā and need setting up manually, all are empty at install.
The Settings icon 
is top left combined with Murena icon.
Significant also within the Routing profile is Routing mode.
Thanks for you answer. I will explore more but at a first look I donāt find it practical not being able to change the options once driving, for example able or disable the sound.
There is a speaker icon in the top-right corner. Click on it to mute the sound.
Thanks, I dont know why I didnāt see it. Too obvious maybe !
Well at this point you need to question yourself rather than ask a documentation for the appā¦.
Thanks for your kindness !
With beta6 on my FP6, I am still experiencing a lag between the position on the map and my actual position: the position on the map is about 2 seconds behind my actual position, which is uncomfortable when I have to turn in presence of multiple side roads. This delay has been present in Murena Maps since the start but I do not experience such delay in CoMaps or MagicEarth. It seems that the lag depends on the zoom level (itās slightly better if I zoom in) but I cannot set the zoom permanently. Why would the position lag in Murena Maps but not in other navigation apps also using OSM? It seems that Murena Maps is smooth otherwise and the FP6 more than powerful enough to handle itā¦ Is there any way to improve this?
FYI, I was using Murenamaps in the car, and after about 10 minutes, the navigation stopped. The arrow remained stationary.
Yes indeed, it seems to do that when the internet connection is lost even though the route tiles and map tiles are likely pre-downloaded and the location is still updated.
Actually it might be because the whole route is not pre-downloaded. Letās try to have a look in the code and raise a gitlab issue.
In the future I wish that there will be a seamless integration of the routing cache with the offline data that the user consciously downloaded for a whole region.
Tester yesterday the app for the first time. Navigation in urban settings was smooth, maybe at time a slight lag, but nothing major.
The problems started when I entered the highway, where I had multiple issues: navigation frozen after few minutes, sometimes the app got confused when I was passing on a bridge, as it continued navigation on the street below the bridge, or sometimes the app thought that I was located on highway going in the opposite direction.
Indeed it looks like there is today no pre-dowload of map tiles when the routing servers sends the route itinerary and turn-by-turn instructions to the client-app.
So if the area has is not in the offline data, then I guess the navigation cannot continue.
/**
* Find tile data for given coordinates from available sources
*/
private suspend fun findTileData(z: Int, x: Long, y: Long): Pair<ByteArray?, Boolean> {
val tmsY = (2.0.pow(z.toDouble()) - 1 - y).toLong()
// First try to get tile from built-in database
val tileData = basemapDatabase?.let { getTileData(it, z, x, tmsY) }
if (tileData != null) {
Log.d(TAG, "Tile found in basemap database")
return Pair(tileData, true) // gzipped
}
// If not found, try offline databases
Log.d(TAG, "Tile not found in basemap database, checking offline databases")
val offlineTileData = getTileDataFromOfflineDatabases(z, x, y)
if (offlineTileData != null) {
return Pair(offlineTileData, false) // not gzipped
}
// Check if we should fetch from the internet (not in offline mode)
if (!isOfflineMode()) {
Log.d(TAG, "Tile not found in local caches, attempting to fetch from internet")
val internetTileData = CoroutineScope(Dispatchers.IO).async {
fetchTileFromInternet(z, x, y)
}.await()
if (internetTileData != null) {
Log.d(
TAG,
"Successfully fetched tile from internet: size: ${internetTileData.size} bytes"
)
return Pair(internetTileData, false) // not gzipped
}
}
return Pair(null, false) // not found
}
Hi,
I tested Murena Maps to go to my holiday destination and to come back. I used it because it was the only one proposing the road I wanted to take for the trip. It was a 10-hour trip covering 800 km, and here is my feedback:
The trip to the holiday destination was done with Murena Maps beta 5:
Tunnels are not handled correctly. GPS is lost, and on the map our position does not move automatically at the latest known speed.
Once, when exiting a tunnel on the motorway, Murena Maps put my position on the opposite way. Despite it being a one-way road and me going in the opposite direction, it locked me onto the incorrect way, which ended up in incorrect directions. I had to restart the application to fix it.
If you start navigation and donāt quit it properly (meaning you donāt press the back button several times to exit the application), you still get the navigation directions from the former navigation. So in my case, I killed the app because of the wrong-way problem, relaunched a navigation, and I ended up with directions told twice each time. I even had them told three times, since I killed it another time because of a GPS issue.
Sometimes the position stops being updated for an unknown reason, and you have to restart the app. It happened to me twice.
During the first day of my holidays, I used it, but I encountered the incorrect-way-detected issue several times. It was not a motorway, but a regular road with a separation in the middle. Navigation is OK at first, but when stopped at a red light or in a traffic jam, the GPS position changes slightly and sometimes ends up detecting me on the opposite way, never going back to the correct one.
Because of this, I stopped using it during the holidays and used CoMaps without any issues. Then, just before coming back home, beta 6 was released. I updated it and did the trip back with it. I shouldnāt have, since it was way worse than beta 5 for me:
There were a lot of traffic jams, and the application wanted me to take small roads. I preferred continuing on the standard road. Almost every time, it never computed a new route based on my new position. I even sometimes saw my GPS position jumping between my actual position and the position where I had left the navigation. I had to quit and restart the application several times.
Navigation quit several times during the trip. The position stays stuck, the speed is OK, but the navigation panels are gone. I think itās the same issue as the stuck GPS position I had on beta 5, except it happened a lot more (I stopped counting at 10).
I also had the issue of the incorrect way being detected on the motorway after a tunnel.
Sometimes the position on the map lags 2 seconds behind. I also had to restart the application to fix it.
I also had the issue of navigation directions being told several times when not exiting the app properly.
Maybe you could post issues on the gitlab of Murena maps or add comments to issues already posted. Developpers donāt look at this forum.
(edit, look at the answers of tcecyk and gabirelIT under it seems some dev look at this thread, and another one.)