Map freezes on Android 4.1.1 Samsung Galaxy Note2

[florianf]

When pinch-to-zoom the map freezes with the enlarged tiles shown, no new tiles are loaded and the map can't be moved after. Zooming via the buttons with activated animations also freezes the map. This is reproducable for versions 0.4.4 and 0.5.

I think the problem is somehow related to the css3 animations. Disabling all animations and disabling pinch-to-zoom by manually setting the L.Browser.android23=true, fixes the freeze.

First thought was, that the transitionEnd standard event isn't fired correctly, but the problem persists when using the webkit specific events (browser seems to support unprefixed events, but in our code transitionEnd wasn't fired, but webkitTransitionEnd was).

Interestingly everything works fine in stock Android 4.0.3 / CyanogenMod on a Samsung Galaxy S phone.

[mourner]

Please try setting L_DISABLE_3D = true before including Leaflet. http://leafletjs.com/reference.html#global

[Mathbl]

Yes! If you want to make sure leaflet works well with most of the Android versions, your best bet is to set L_DISABLE_3D = true.

Sadly, it's gonna make the map less smooth and you lose some cool animations, but if you don't disable 3D, you'll encounter many strange random problems on different Android versions.

[danzel]

If this fixes it in this case... Maybe we just disable 3d on android native browser (AFAIK it is fine in chrome browser on android devices, right?)

[Mathbl]

I'm not sure @danzel, I was talking about my case. I'm developing an Android app with Leaflet inside webviews, and if I don't disable 3D, it's really inconsistent and many strange issues happen depending of the Android version (well from start, webview is so broken in Android).

In the browser, it may be different though (like for chrome). So i'm not sure if disabling it for all android native browser is overkill since there may be some that works :/

[mourner]

I really didn't want to disable it for all Android browser versions by default because it's so much smoother with it, and seeing Leaflet being slow on a modern Android 4 smartphone or tablet is quite frustrating... If only we could isolate the bad behaving versions somehow...

[Mathbl]

Yes you're right.

The problem is not related mainly to older devices. I've had a GalaxyTab 10.1 running 4.0.4 crashing (if 3D not disabled).

On Nexus 7 4.1 it seems correct for the 3D, but there's this frustrating problem of click being fired twice (issue #1041), causing the zoom button tap to zoom 2 steps at once and also popup closing on marker click etc.

**EDIT finally, it also crash with Nexus 7 4.1 when using the zoom button and 3D enabled

[florianf]

I tried with L_DISABLE_3D = true, but pinch-to-zoom still freezes the browser.

I made a mistake in the initial report, the exact Android version is: 4.1.1 and the phone runs Samsung's firmware.

[mourner]

Are you sure you set it before including Leaflet JS?

[florianf]

I'm sure. I included leaflet-src.js and put it there on the first line.

[mourner]

Oh, I see that it's not a crash but a freeze, so must be something different... Do you know if it reproduces on SDK emulator?

[davidd8]

I'm seeing the same problem, the map freezes with any zoom interaction whether or not 3D is enabled. This is using the default Android browser with the Samsung firmware for Android 4.1.1

[damianofontana]

I'm seeing the same problem with Samsung Galaxy Note 2 with Android 4.1.1 and leaflet 4.5. After the pinch-to-zoom or the zoom with the control button the map freezes and it doesn't respond to other zoom actions.
The zoom starts to work again when the user moves the map and leaflet redraws the vector layers.

[florianf]

As a temporary workaround for this issue, you can fallback to the Android 2.3 behaviour of Leaflet.
In Browser.js Line 15, quick proposal:

android23 = ua.search("android [23]") !== -1 || ua.search("android 4.1") !== -1,

[davidd8]

@damianofontana and @florianf Thanks, your quick proposal is a great workaround for this!