Tile rendering broken on Android 4.0 ICS about ol2 HOT 13 OPEN

Thanks for the report. Can you try http://dev.openlayers.org/releases/OpenLayers-2.11/examples/mobile.html and see if you have the same issue there? If not, then I suspect that the reason for the distortion is the percentage based tile positioning, which we introduced after 2.11. Anyway, this issue should be reported on the Android bug tracker, since it is obviously an Android issue.

from ol2.

The 2.11 example works as expected! It was the first or second week of January when I noticed that the example on the link in my initial post started to show this misbehavior since I played with it nearly every day - it was the same time that the CSS transitions were added so I initially thought that there is a relation but removing the transitions shows the opposite.

If you're right and this really is an Android issue, I fear it'll take a very loooong time until this issue gets resolved, if at all :/ Even if it gets resolved, people with Android 4.0 - 4.0.3 handsets would still be stuck with this problem so I guess the workaround for this problem would be to stick with the 2.11 release for those OS versions.

from ol2.

Could someone please point me to the commit or file in which the change to percentage based tile positioning happened?

from ol2.

I did some investigation on this, and the culprit is not the percentage based positioning. It is just the opacity transition for the tile fade-in. To make things work in Android 4, you only have to turn off the opacity transition by adding the following to your application's css:

.olTileImage {
    -webkit-transition: none;
    -moz-transition: none;
    -o-transition: none;
    transition: none;
} 

from ol2.

Very strange, last time I tried it the tiles where still shown distorted for a small moment of time, this time it works as expected. Thank you!

from ol2.

Catching up here... @ahocevar do you still think this is an Android 4 issue? If so we may want to work around it somehow.

from ol2.

I cannot reproduce the issue with Android 4.0.2 on a Galaxy Nexus (http://openlayers.org/dev/examples/mobile.html).
@Colony, do you use cyanogenmod or an other rom ?

from ol2.

I was able to reproduce this with the 4.0.3 emulator. It really is something that should be fixed in Android, unless there are many devices out there with this bug.

from ol2.

I'm using stock Android 4.0.3 on the Nexus S. Just tested it in the 4.0 emulator and can confirm that it works correctly there. Seems like the problem was introduced with 4.0.3.

from ol2.

I'm experiencing the same issue on android 4.1.2

from ol2.

Hi,
same issue here,
the CSS modification won't solve it
Anything new ?

from ol2.

Hi,
I had this issue only with JQM and OL. I switched to Sencha Touch, which in my opinion is less buggy then jqm.

from ol2.

btw - removing the opacity transition as @ahocevar also suggested can do great job to enhance map performance and responsiveness on 2.3.

Reason: They have this weird rendering cache layer over the WebView on android 2 which you can see working whenever some animation happens on those devices (at least with a devicePixelRatio <> 1) - all images are pixel-sharp during animations/gestures and anti-aliased again after they have finished. Using border: > 0 and the default transition, the whole webview will flicker between the two states as new tiles are being displayed.

from ol2.