do you think it´s a rendering problem because of more considered rules in the themes?
At least with the older Galaxy Tab (PT1000) and the Galaxy S2 I didn´t see this problem. Even the 865 MB Alps map (without cycle routes) from jurajs works fine.
(@jurajs, thank you for your effort)
Hi Jusc,
This is very complex issue it depends on many details and im far from beeing able calculate a behaviour of a map in advance.
The Alps are no Problem, it seems that it depends on the amount of vectors per area (eg Vectors/mile²),
this is a serious Problem at low zoom-levels, the worst is level 7, here a major area of a country is visible
_and_ all ncn+icn + major roads appear so the {vectors/area*visible_area} needs lots of calculation time and sometimes crash a phone/app.
This leads to several different "zoom-interval-conf"s for map creation (=amount and ajustment of internal base zoom levels)
+ tagmappings adjusted to these levels (3 base levels per default, 4 for GB+NL otherwise these maps crash).
Another problem are Monster relations (Multipolygons) like the lake district west of Stockholm, while the Sweden is no problem at all,
this single area sometimes causes misbehaviour.
And, of couse you are right, it depends on the phone.
I theory maps that are critical even on the small screen of my Xperia Active should crash every high-resolution screen - however, in the contrary they run fine on SGII, S_Note aso. 8-)
So well... I check the behaviour of every map after major upgrades in the prozessing-sheme.
This lead to 5 mapping runs for GB after adding wateriles till the map rendered reliable on the phone :roll:
