@michaelbechtold
you mean around the rendering of maps?
I believe we all will agree that best from long-term will be adapt to latest MapsForge version. This on one side will be a lot of work mainly for @voldapet who work years on themes for LoMaps, on the second side, it simplifies life to all of you, who suffer from divided themes for Locus Map and other apps.
Currently, latest version 0.10.0 of MapsForge library is already in app so V4 maps (and in next version V5 also) are supported. Auto-loading most probably does not work, MapsForge POI's are another, currently not so important, story.
Anyway, support for external V4 maps is not problem for LoMaps (they may still use old renderer).
Issue reported by John is probably little more complicated.
MapsForge is based on the same system as Google Maps or other map frameworks. They have own "map view" component which has logic how to draw map tiles. Anyway here is a problem. Locus Map has also own component. For using maps from MapsForge V4+, I use own hack how to prepare map tiles, which most probably cause a new issue with labels. But seems, there is one active use who may save us for now:
https://github.com/mapsforge/mapsforge/issues/1085 . So let's wait on 0.11 version of MapsForge, I'll then use this method and we will see

.