May 4, 2016 at 11:38 #9280
Hello Tobias, I’m testing the new beta versions style 4.0 with OruxMaps donate 6.5.5.
I have an annoying problem, I think due to the style that slows the map display of OpenAndromaps, giving this “graph inconvenience” which I am attaching below.
It is not due to memory. I have a Moto G 2015 with 16 GB.
Attachments:May 4, 2016 at 21:21 #9296
thanks for testing. Could you tell me a bit more, is the display just slow or do the missing tiles never render?
I’m using an original Moto G LTE and map rendering is fine, no difference to previous versions. Same area and zoom level, hiking mapstyle with all overlays, less than 2 seconds with cleared cache. Also OruxMaps Donate 6.5.5
See attached screenshot.
Have you used OruxMaps quick install or manual install? Check if ele_res directory is the included one in the zip file.
Maybe it helps to clear the map cache and/or restart the app.
Attachments:May 4, 2016 at 23:06 #9299
I always use your OAM maps with OruxMaps.
I don’t know if it’s a problem due to the Moto G 2015, that I’ve since a month. I solved the crash problem zoom, due to Motorola with Oruxbeta.
Instead this problem persists. The tiles are very slowly texturing in areas of new map.
I always install OAM map in manual install. There is no zip, and I deleted the cache mapforge.
I restarted the program.
Best regardsMay 5, 2016 at 08:45 #9302
Is the rendering only slow with Elevate 4 and normal with Elevate 3? Maybe it’s the update to OruxMaps 6.5.5 that slows your device.
I meant if you installed Elevate 4 beta via quick install or manual, not the maps. Maybe it’s best to delete all files in the mapstyles folder and use quick install for Elevate 4 beta and see if this works.
Maybe it’s worth a try to test with and without the crash zoom problem option.
TobiasMay 5, 2016 at 09:43 #9304
The problem appears solved… I replaced the Elevate 3
I even install your styles in manual mode.
Uhm….with the Orux 6.5.5 if you remove or put the crash zoom option, will not change anything…
VancoriJune 19, 2016 at 14:17 #10345
One size fits all is the new approach as I understood. Looks fine in Locus on a Note 4. BUT… and now comes the big BUT: Because of today’s obnoxiously high res devices, we have to use something like a 200% magnification for all other raster maps.
200% on the new svg style is way too much though.
What this means is that we have to manually switch magnification on and off when switching between vector and raster maps. Very inconvenient. Also makes use of overlay maps mixing those two hard to impossible.
Secondly, I really enjoyed the 4times speed boost that using vector maps at 200% gave over 100%.
Long story short: Is there any way I can make the new svg only theme believe it renders on a lower resolution device? I would really need to render vector maps at 200% pixel magnification… both for speed reasons and for compatibility with pixel maps.
PS, to clarify: currently I use elevate L with a 200% magnification. How can I do something like that in the future with the new theme? I really want to keep the pixel quadrupling…June 19, 2016 at 22:30 #10354
Elevate was always made for best display at 100%, other usages are more by chance.
I think that is more a problem of the app. It would make sense for this usage to offer different scale factors for raster and bitmap maps, you should request this.
Without that you could use Elevate 2, this was never meant to be scaled, and will be maintained on a smaller level, too.
Elevate 3 was always made with automatic scaling in mind, and all standard mapsforge apps do this e.g. for text size. Only Locus works like you wrote, as it needs a workaround.
Another solution would be to reduce text size for vector maps, but Locus doesn’t allow anything wise to be changed.
Or remove all “dp” units from the values you don’t want to be scaled in the xml file.
You must be logged in to reply to this topic.