Most or all devices we support have been updated to Android 2.2. (We should look at our Market statistics to confirm this.) Dropping support for Android 2.1 and earlier would let us simplify our code by removing 2.1-specific code paths. For example: bug 661843, bug 622684, and bug 602978. This would also give us access to new platform APIs, like Camera.setPreviewCallbackWithBuffer (faster frame rate for camera preview) and new MotionEvent fields (simplifies multi-touch implementation).

Stuart said in the meeting we are still at about 10% pre-2.2.

stuart, is that just installs or pings?

2.1 still takes up 10% according to marketplace. WONTFIX for now.

2.1 is at 7.1% now

If the usage share is at 7% now, and is currently falling at about 3% per month, then it could be pretty tiny three months from now when Firefox 8 ships, or five months from now when Firefox 9 ships. I think it's reasonable to make this change in next release cycle or so.

See also Bug 717869, which touches code that already relies on API v8.

Any closer to a final decision on this, chaps? Would like to know whether I ought to hack Base64 in (see Bug 730637).

We should land this on the Maple branch because of bug 727142.

Comment on attachment 600932 [details] [diff] [review] patch Review of attachment 600932 [details] [diff] [review]: ----------------------------------------------------------------- agreed. we can back this out when we do run on 2.1 without the startup crash

Landed on Maple: https://hg.mozilla.org/projects/maple/rev/1613b71bad2e If this is not backed out before release, we'll need to make some sort of announcement that Firefox for Android 2.0 and 2.1 is EOL.

Filed Bug 731315 to track reverting to API level 5.