backtop


Print 36 comment(s) - last by wushuktl.. on Jul 6 at 1:14 PM

New operating system will be for high end handsets only, will scrap third party shells (Motoblur, HTC Sense)

Android 2.2 seemed pretty cool, bringing Flash 10.1, a Davlik JIT compiler for faster apps, and the ability to run apps off a memory card.  But Google's recently unveiled Android 3.0 operating system, codenamed "Gingerbread" may make Android 2.2 "Froyo" look downright pedestrian.

First and foremost, not all Android phones will get Android 3.0 when it launches in Q4 of this year.  Only high end handsets, and potentially tablets, will get the top of the line operating system.  Laggard models (also known as "entry level" smartphones) will still run either Android 2.1/2.2, which will be kept alive by minor updates.

For those who experience Android 3.0, the taste will be sweet.  The minimum spec calls for 1 GHz processors, 512 MB RAM, and a 3.5" display.  Resolutions of 1280x760 will be offered on displays 4" and larger, surpassing the iPhone 4's fancy "Retina Display".  And some phones are rumored to have 2 GHz processors (hopefully they'll come with a hearty battery or employ significant die shrink power savings).

Another drastic change in Android 3.0 is that Google is killing off third-party user interface shells like Motorblur and HTC Sense, by offering a faster, superior alternative.  The new built-in UI is reportedly similar to that seen in the Gallery app in this clip, with fluid animations and a photobook sort of feel to it.

The wealth of information was leaked by Mobile-review.com’s Eldar Murtazin in his Russian language/locale podcast "Digestiv." This podcast has been translated by 
Unwired News.

In the podcast, Murtazin claims that the new OS will air to developers and tinkerers in mid-October 2010.  That will be followed by a November/December series of hardware launches, just in time for the Christmas season.



Comments     Threshold


This article is over a month old, voting and posting comments is disabled

RE: Boooo
By legaceez on 6/30/2010 5:14:45 PM , Rating: 4
I think the main reason is because custom UI such as Sense and MotoBlur are more tightly integrated into the OS than say OpenHome or LauncherPro. It's probably actually modifying some of the base code to enable/disable certain features and add new features not possible without such a tight integration into the OS.

In other words they aren't just replacements for the Home app like OpenHome and dxTop are. Sense and MotoBlur have a Home replacement component but there is probably a lot more to it. Plus with access to the low level OS i'm assuming the OEM UI's will run more efficiently.


"If you can find a PS3 anywhere in North America that's been on shelves for more than five minutes, I'll give you 1,200 bucks for it." -- SCEA President Jack Tretton














botimage
Copyright 2014 DailyTech LLC. - RSS Feed | Advertise | About Us | Ethics | FAQ | Terms, Conditions & Privacy Information | Kristopher Kubicki