iScroll gets Android 1.5 compatibility

You asked for it and now you have it. v3.3 (beta 1) is my first attempt to port iScroll to Android 1.5. It seems to work, but no hardware acceleration. Is it really worth the effort?

Basically all you have to do to get Android 1.5 and 1.6 compatibility is to use translate(x,y) instead of translate3d(x,y,z). In fact iScroll v3.3 checks if your phone supports 3d functionality and use the best option it finds.

The problem here is that translate(x,y) seems not to activate the hardware acceleration, so do not expect blazing fast scrolling. To reduce lagginess to the minimum, iScroll disables all the eye candies and wisely preserves resources. Momentum, bouncing, and scrollbar fade in/out are all disabled but at least you can scroll.

We are now back in beta. I need the help of all the (un)lucky owners of an Android 1.5/1.6 and receive some feedback. My question is: should we really target version < 1.6? If scrolling performs so badly shouldn't we just pass over? If you don't care about Android, fear not: version 3.3 adds some new features and improves overall stability for you too. So go get the new version.

6 thoughts on “iScroll gets Android 1.5 compatibility”

  1. Hi Matteo,

    Thanks for this project, great work.

    Android >= 1.5 is well worth it. There are still a lot out there and on my phone it works a treat. In my office we have 2 Android 2.1s, 1 Android 1.6 and 3 Android 1.5s.

  2. Hi,
    I am using iscroll for the content div and it works fine for android and blackberry
    But however now i face a issue in the page, where there is textinput and textared. The fields are disabled and not able to edit the input textfields

    Any work arounds for this.


Comments are closed.