Today the CynaogenMod team announced CM9 support for three U.S. Galaxy S III devices. It doesn’t take a rocket scientist to figure out that Verizon’s version didn’t make the cut. For now they are supporting the AT&T, T-Mobile, and Sprint versions. They did mention the Verizon version and their original intent, but nothing was said about the U.S. Cellular version. Hit the break for their statement.
Sure the Amazon Kindle Fire might not be at full fledged Android tablet, but that shouldn’t stop you from having the full experience including Jelly Bean 4.1.1. XDA member Hashcode just posted an AOSP based Jelly Bean ROM. This is a beta so there are some issues like the HD codecs (YouTube and Netflix). The good news is this will be fixed shortly as Texas Instruments is updating the libion code. Other oddities is the screen over rotates and the dev is having an issue turning on UMS. These are all issues that will be fixed shortly.
Motorola confirmed tonight, in a series of tweets, that the Atrix HD will indeed have a locked and signed bootloader. This means that altering the kernel on the Atrix HD will not be possible, limiting the customization possibilities of the phone. In other words, no custom ROMs. The phone, however, should still be rootable.
It’s not the end of the world, though, since Moto also tweeted the following:
“…our goal is still to provide a way to unlock the bootloaders on our devices to those who wish to do so, more details to come.“
So it seems that although the Atrix HD will launch with a locked bootloader, an unlock method may be coming in the hopefully not-too-distant future.
When we told you that Verizon was keeping their Galaxy S III tightly locked up, many folks were upset, considering the other carriers have user-onlockable bootloaders on their S III’s. Well fret no more, young hackers, for Samsung has just announced that they will be offering a developer edition S III that works on Verizon.
This hacker-friendly version will be sold directly from Samsung’s developer portal (developer.samsung.com) for $599. It’s unfortunate Verizon won’t sell it directly themselves since it won’t be subsidized, so if you want this phone for $199, you’re out of luck. But if you’re willing to spend the bucks or don’t want to be on-contract anyway, Samsung’s offer should be music to your ears. Of course, many of you who already purchased the Verizon S III are probably a little miffed. Time for a return?
All the usual warnings apply… unlocking, modding, flashing, etc. is all done at your own risk. Screw something up and you’ve got a very pretty and expensive brick. But we know you’ll be careful.
Hit the break to read Samsung’s mini-FAQ about this edition.
Thanks to LastStandingDroid over at the XDA forums, the Samsung Galaxy S II (I9100) has received an Android 4.1 Jelly Bean SDK port. With any SDK port, the build is fairly rough and one should expect many things to either not work, or not work correctly. Although there is a short list of things that do work:
With the release of the source code for Android 4.1 Jelly Bean, we can expect to see a bunch of ROMs soon, but some of you might want create your own port from the source. To help you along, XDA member dastin1015 put together a guide to get you started compiling Jelly Bean on Ubuntu. It covers the setting up of the build environment, connecting to and downloading from the repository, adding a device, and building. Just hit the source link below to get started.
Well while the Verizon Galaxy Nexus is one step closer to truly becoming a “Nexus”, Sprint’s Galaxy Nexus is still lacking AOSP support, so what gives? Well, for one thing Verizon’s Galaxy Nexus— also known as toro— only has experimental binaries at this point and Sprint’s Galaxy Nexus— also known as toroplus— well… is not getting even an experimental build of the various binaries. And not only that— Sprint’s Galaxy Nexus is not only getting the cold shoulder from Google Developers, but there are no immediate plans to offer support for that version of the device as indicated by Jean-Baptiste Queru:
“As far as toroplus, the situation is unchanged: there are no plans to support it as a target device for custom AOSP builds.
This is certainly a bit of a messy situation unfolding. Considering the resounding success of the Nexus S 4G and the fact loyal Sprint customers have been eager to have the Galaxy Nexus, Sprint (and Google) would best figure out some type of compromise or solution and soon. The loyal Nexus customers deserve at least that much.
source: Android Police
Earlier this year, Google dropped the Verizon Galaxy Nexus from being a “supported developer device” due to its CDMA binaries that could not be signed by the same platform key as the AOSP binaries. When this news broke, everyone was in a tizzy about the Verizon Galaxy Nexus not being a real Nexus device.
Well, Google has our backs and have just released Verizon driver binaries to use for the 4.1.1 Jelly Bean AOSP build. What does this all mean? Basically, it just means the Verizon Galaxy Nexus is still being supported as a developer device as much as it can be. These drivers will help ROM developers build custom Jelly Bean ROMs for Verizon’s Nexus.
It’s not all rainbows and unicorns, however. Jean-Baptiste Queru, tech lead of the Android Open Source Project, posted in a forum that he doesn’t consider “toro to be higher than ‘experimental’ at this point,” the term toro referring to the Verizon binaries. What that means is currently not totally known, but expect devs to pull this apart and tell us how it’s all working… or not working. Stay tuned.
Devs, click the source link for the binary downloads.
source: google developers
Well the Galaxy S III might be created for humans, but not for the development community. Well, at least for the Verizon version that is as its bootloader is locked by design. Now it was rooted over the weekend, but we need a method to permanently unlock the bootloader to allow unrestricted flashing from ODIN. Well our friends over at XDA created a bounty for anyone who can do it. Right now the total is at $1,320 and is sure to climb. Hit the break for the rules:
One of the great things about Android devices is that well, you get to modify them and put them through unusual jobs, such as putting it to use as a topnotch gaming device. Okay, so many of you are looking perplexed, so let me explain: a crafty Galaxy Note owner realized the 5.3-inch screen of the device is too good to not be taken advantage of when it comes to gaming. So in having some time on his hands, the crafty developer went ahead and did the unthinkable— he literally gathered ports of popular games like Mario on his Galaxy Note, created an attachment terminal mount on his Playstation 3 controller, mounted his Galaxy Note to the controller and successfully configured the setup to allow his PS3 controller control the games. Impressive isn’t it?
Don’t take my word for it— check out the cool achievement in all its glory once you hit past the break.