Kindle Fire gets AOSP Jelly Bean ROM

Google may have introduced the Nexus 7 at a low $199 price point, but Amazon brought the Kindle Fire to the masses last year at the same price point. Although it was running a forked version of Android, it could be rooted and hacked to run custom ROMs. Now some enterprising hackers on xda-developers have ported the latest version of Android, Jelly Bean, across to Amazon’s cheap tablet.

Not much is known about the ROM right now, although it looks like basic functionality is working. Users will need to root their Kindle Fire first, then flash the provided ROM and Google Apps package. A quick fix is then needed in order to restore WiFi functionality, but after that you should be good to go. The only major feature that’s missing is hardware acceleration for video playback. Texas Instruments hasn’t added in code to support Jelly Bean just yet, so users may be waiting before they can get perfectly smooth playback in apps like YouTube and Netflix.

Other than that, you’re getting the full AOSP experience, with the ROM compiled from the latest source (4.1.1). Google were keen to point out the new features at I/O which included Project Butter, introducing frame buffering and VSync for dramatically improved performance and fluidity throughout Android. Google Now, meanwhile, acts as a personal assistant that will monitor your habits and surroundings while serving up relevant information such as the weather or local transit points. Notifications have also been improved, and some mild UI changes have been made.


Kindle Fire gets AOSP Jelly Bean ROM is written by Ben Kersey & originally posted on SlashGear.
© 2005 – 2012, SlashGear. All right reserved.


Jelly Bean source code added to AOSP

Aside from the introduction of the Nexus 7, the big reveal out of Google I/O was the announcement of Jelly Bean. The update promised to bring speed to the Android OS with Project Butter, resulting in smooth 60fps animations and transitions, as well as some smaller tweaks. Now Google has officially released the Jelly Bean source code, merging it into the current AOSP codebase.

Jean-Baptiste Queru took to Google Groups last night to make the announcement, detailing how proprietary binaries will also be available for the Nexus 7 and Galaxy Nexus. Don’t worry too much about older devices, as Nexus S and Xoom binaries will be coming in the future. Now that Jelly Bean is being merged into the AOSP, custom ROM makers will be able to take advantage of the latest code and put out some new ROMs for a wide variety of devices.

The CyanogenMod team has already expressed their interest in getting a far-reaching Jelly Bean ROM up to speed as soon as work on CM9 (which is based off Ice Cream Sandwich) has been finalized and released. In the meantime, you can expect smaller groups and individuals to pump out some ROMs for popular devices. Keep a close eye on xda-developers.

[via PocketNow]


Jelly Bean source code added to AOSP is written by Ben Kersey & originally posted on SlashGear.
© 2005 – 2012, SlashGear. All right reserved.


Verizon Galaxy S III has locked bootloader (but it’s been rooted anyway)

DNP Verizon 'forced' Samsung to lock Galaxy S III boot loader

Based on Samsung’s hacker-friendly track record, you’d generally expect one of it smartphones to come with an unlocked bootloader, making it easy to update or tweak with unofficial ROMs. That’s not the case with Verizon’s imminent version of the Galaxy S III, however. As the folk at XDA know only too well, this particular iteration of Sammy’s flagship comes with a sealed bootloader, which makes it resistant (though not impervious) to hackery.

Of course, Sammy has nothing to gain from snubbing the modding community in this way, so it stands to reason that VZW pushed the Korean manufacturer to supply them with a locked bootloader — despite the fact that all other variants have been left open. We’ve reached out to Big Red for comment, but in the meantime a clever soul over at Rootzwiki claims they’ve already found a workaround for root access. (At this point, though, we’d better provide our usual disclaimer: be very careful before you poke around in there, because going up against a locked bootloader can be risky. The apparent safety of modern life is just a shallow skin atop an ocean of blood, guts and bricked devices.)

Verizon Galaxy S III has locked bootloader (but it’s been rooted anyway) originally appeared on Engadget on Sat, 07 Jul 2012 08:04:00 EDT. Please see our terms for use of feeds.

Permalink   |  sourceXDA Developers Forum, Rootzwiki  | Email this | Comments

Jelly Bean port passes the butter to the Galaxy S III, ROM-flashing required

Image

It took only one day for devs to unleash Jelly Bean 4.1 from its server confines and out into the eager underbelly of Android’s community. And those enterprising hackers haven’t wasted any time getting that buttered up OS running on Galaxy Nexus handsets (yes, even for Verizon subs). Now, good news is also on the way for any consumers who forsook the pure Google path in favor of Samsung’s TouchWizzed way. That’s right, a (mostly) working port has been made available to Galaxy S III (I9300) users that should see some of that point upgrade’s features successfully implemented. Feel free to take it for a test run if you’re skilled in the ways of flashing, but bear in mind you’ll lose access to the camera, WiFi, Bluetooth, NFC, storage and audio. It goes without saying that this build is far from the perfect ROM for a daily driver, but if you’re curious to check it out first-hand, there’s no harm in trying. Hit up the source below for the step-by-step how-to.

Jelly Bean port passes the butter to the Galaxy S III, ROM-flashing required originally appeared on Engadget on Fri, 29 Jun 2012 14:47:00 EDT. Please see our terms for use of feeds.

Permalink   |  sourceXDA Developers  | Email this | Comments