Android 3.0, 3.0.1, and 3.2 running…somewhere?

I’m not sure how easy or difficult it is for a ROM cooker to make his software false report about the version of Android it’s based on, and I can’t think of any legitimate reason a hacker would go to the trouble without ensuring a big hoopla ensued. So it’s definitely interesting that GreenComputing found evidence of Android 3.0, 3.0.1, and 3.2 running their popular benchmark software, Linpack for Android:

“Android 2.2 (FroYo) took the Linpack lead for the most runs this last week. According to my analytics, Android 2.2 was used 43.1% of the time. Android 2.1-update1, the previous leader was used 39.8% of the time. So what was used for the rest of the 17% of the time? How about 158 other ROMs! That is a lot of variety to choose.

Mixed in with the lot is some curious ROMs; Android 3.0, Android 3.0.1 and Android 3.2.” (Emphasis added)

Are some Google engineers testing the performance of versions as far out (or close?) as 3.2? I don’t know, but there’s something comforting about seeing those numbers. Thanks to Jonathan for sending this in.

Via GreeneComputing

Tags:

Post comment as twitter logo facebook logo
Sort: Newest | Oldest

If they named it to 2.3 would you guys be this crazy? Version numbers mean nothing

If they named it to 2.3 would you guys be this crazy? Version numbers mean nothing

3.0 is supposed to come out before the end of the year. Google said that updates were slowing to one a year, so I find it kind of weird that 3.1 and 3.2 are out there also. They most have meant big updates, like 3.0 to 4.0, are happening once a year.

I would take this story with a HUGE grain of salt. Linpack scores can be easily hacked. I'm familiar with the dev community and have made a custom ROM myself. One of our droid eris dev's said it would be easy to bump up our phone to say 1.5ghz even though there's no way it could hit that. But then again they could actually be testing it and just teasing us with it.

It is very easy to change the build.prop to display whatever. That is how developers tag their custom ROMs. The Linpack apk is not OS dependent so it shouldn't force crash if you changed those values. I could run a test showing 4.1b

Not a surprise. Google did the same thing with Froyo before launch.

Well, we are supposed to see Android 3.0.x (Gingerbread) by the end of the year, therefore there is no doubt that Google is in the development stage as we speak and they're gonna be testing out the OS as they go of course so it's no surprise to see some 3.0 ROMs in the mix.