Closed Bug 604774 Opened 14 years ago Closed 9 years ago

Gut the i9000 blacklisting

Categories

(Core :: JavaScript Engine, defect)

ARM
Android
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: cjones, Unassigned)

Details

This involves backing out bug 601222 and bug 604432.

We should drop i9000+2.1 like a hot potato once the 2.2 upgrades have been rolling out "for a bit".  (Ideally, at the point where people aren't on 2.2 because they've chosen not to upgrade.)  After that, i9000+2.1 will be an unsupported configuration and we'll pretend this code never existed.

I don't care if relnote or refuse to start up like we do for armv6 devices or whatever else.
Are we ready for this? I'm refactoring a bunch of regexp junk to make them lazy, so it would be nice to do while I'm in there.
No, some Galaxy S vendors never released an over-the-air update for 2.1->2.2, so we have to assume all the folks who bought Galaxy S's before the update are still on 2.1.  http://developer.android.com/resources/dashboard/platform-versions.html shows ~12% of users still on 2.1, of which the majority are probably Galaxy S's.

I think we're stuck with this junk a while longer :/.
Assignee: general → nobody
Firefox now requires Android 2.3.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.