Showing posts with label Android 2.3 Gingerbread. Show all posts
Showing posts with label Android 2.3 Gingerbread. Show all posts

Wednesday, January 26, 2011

Android 2.3 Gingerbread ported toAndroid 2.3 Gingerbread


Out of abox, Android 2.3 is designed to run using ARM-based processors. But open source os's, anyone who’s ready to have fun with the code long enough can recompile the application to run on chips with various architectures.For the lastfew years we have seen enthusiasts porting Google Android running with thex86 processors used by mostlaptop or pc, and already there’s a version of thelatest version of Google Aandroid that can run on x86 chips.


You can get steps for gettingthe newestbuild on the Google Groups discussion. This build requires Java 1.6 and a64-bit built environment. Wi-fi and sound aren’t currently working, thus , making this clearly more for checks purposes than anything. But if you’ve always dreamed ofrunning Android2.3 Gingerbread on your laptop, it is easy to stop daydreaming.

Wednesday, January 19, 2011

0.4 % Of Android Users Use 2.3 Gingerbread

Google's Android  2.3 Gingerbread the latest version is it being run by 0.4 % devices while Android 2.2 Froyo is considered the most used version on the software, research has shown.

Based on data released on Google's Android Developer blog, the newest version with the platform is only installed on a few minutes percentage of all devices, while 2.2 Froyo was installed on 51.8 % devices.

The real reason for the lower use of Android Gingerbread is usually that the Operating system is only entirely on the Samsung Nexus S device, which is just available from select stores. The main USP of the new version from the OS is that it has support for Near Fields Communication technology.

The issue of fragmentation is constantly on the plague the platform with 35.2 % of users continuing to run on Android 2.1 Eclair, although higher versions can be found. Android versions 1.6 and 1.5 were available on 7.9 % and 4.7 % devices respectively.

One of the many reasons behind the fragmentation concern is that despite Google being prompt to release updates to the os, wireless carriers, who're ultimately accountable for delivering the update to users, have a considerable time to release them.