And here we are, as anticipated there is a new beta. Changes are big enough to justify a jump in version numbering, especially since some will let out of the door some apps… sorry.
First and foremost this release is based on Mapsforge 0.4 rather than 0.3 (more on this below).
Then there is some fine tuning on the colours, the bigger ones on primary roads (now red rather than yellow), motorways and trunks; other colours and line widths have been refined to help distinguish the different ways, especially in outdoor conditions.
I also pushed further the idea of progressive rendering. Lower zoom levels have been hugely simplified to speed up rendering and improve legibility.
We are in a quagmire. Orux switched to Mapsforge 0.4 but with a custom implementation that makes things particular.
In Mapsforge 0.3 the tile size is fixed to 256x256px regardless of pixel density, while in Mapsforge 0.4 tile size is increased proportionally as display density increases. This is a big and very welcome change, since it means that any given zoom level will have (roughly) the same magnification on any device. In theory this permits to make a single theme that renders fine on every device. In practice, that’s not Oruxmaps’ case.
In fact the new implementation still uses a fixed tile size, it just changed from 256 to 512. This fits my device better, but didn’t really solve the problem of having different themes for different devices. The behaviour is now very odd, since text will be scaled, and so are line widths, but at the same time tile size (in millimeters) will vary, so the results on any device different from the one the theme is developed on are rather unpredictable. I really hope this will eventually get solved in some way.
At the moment this theme only really works well with Oruxmaps 5.5.23 (from beta 11) on 320 dpi devices. There are however some additional settings that help minimize the issue.
I also tested in Cruiser that is probably the only Mapsforge 0.4 compliant app out there. At ~300dpi everything is fine, except circles that are bigger than in Oruxmaps, and don’t ask me why. In Cruiser Beta (that uses the latest “dev” version of Mapsforge) I also see that dy is bigger than expected. Again, don’t ask me why.
For other display densities icons will get too big or too small. Since Cruiser doesn’t offer an option to scale symbols you have to live with it, or change the symbols with the ones of the regular HR or LR versions. With the final release I’ll probably make three versions as usual. Or maybe Emux will add an icon scaling option ;-)
What about old apps based on Mapsforge 0.3, including the current Play Store version of Oruxmaps? The new theme is technically compatible, however unless you are using a 160dpi device everything will be too small, and even in that case a lot of captions will not show at all, obscured by their symbol that in turn will be too big. Try it if you want, but you are probably wasting time.
Download and install
Download from here and install as usual.
This version is deprecated. You should get the newer one instead.
Then go into “Settings>Maps>Mapsforge settings” and tweak the parameters to your liking. As a starting point I suggest:
- for 300-320 dpi set everything to 1
- for 450-480 dpi set the text multiplier to 1 and the others to 1.5. The map will be smaller than intended, but things should be kept in proportion
- for 200-233 dpi set the text multiplier to 1 and the others to 0.75. The map will be bigger than intended, but things should be kept in proportion