If you own a Verizon Galaxy Nexus (toro), and you’re looking for a good AOSP-based Jelly Bean ROM, then you might want to try Peter Alfonso’s Bugless Beast 4.1. It’s based on Android 4.1.1 and is as close to stock as it gets. For enhancements, he did include native tethering, Google Wallet, improved scrolling, louder audio output, and Chrome is the default browser. It’s recommended that you download the offline speech recognition package in Google Search settings once you install the ROM.
It used to be called the Galaxy Nexus Root toolkit, but with version 1.5, it’s now called the Nexus Root Toolkit because it supports all Nexus devices, including the Nexus 7. WugFresh is famous for giving us the quick and easy way to unlock and root the Galaxy Nexus as well as flash it back to stock and re-lock it. There really couldn’t be anything simpler, although we do encourage you to go about things the manual way, which isn’t all the much harder.
Nonetheless, we understand that some of you might be a little nervous and that’s where the Nexus Root Toolkit comes in. It can even flash zips, install apps, restore android backup files, and flash/boot img files with just a double click. This new version now supports all Nexus devices. Hit the break for instructions and download links.
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.
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.
In the next year, I’m expecting to see more and more Android-related media devices and set-top boxes such as the Nexus Q. Last week we told you about a new Android-based gaming console called OUYA, but we really didn’t know much about it. Well it just became a Kickstarter project so we have more details.
The concept and idea behind the project is to make it easier for developers to bring a console game to market. Every OUYA console is a developer kit and there won’t be a need to purchase a license or an expensive SDK. So basically no licensing fees, retail fees, or publishing fees so anyone can create the next big title. All games will have the freemium model so everyone will at least be able to try any of the ones they’re interested in.
Sure the Nexus Q is going to be a revolutionary media device for us Android users, but don’t forget— at the end of the day, it’s still a Nexus product and so you know what that means? It means that the Nexus Q is meant to be tinkered with and improved upon silly. After seeing the Q get unlocked and rooted for all kinds of tomfoolery, it was time to see what else could be done with the device. Well thanks to XDA Forum member fredc888, we are now one step closer to being able to see the full potential and take full advantage of the Q’s ability to run apps and games. fredc888 was able to successfully connect a Bluetooth-compliant HID mouse to the device. Yes friends a Bluetooth mouse. That is definitely big time.
While this is an exciting achievement, it is one that should be taken with extreme caution. As you might expect, the Q doesn’t have a traditional Bluetooth menu to allow it to connect to other devices outside of Android phones and tablets, so the Bluetooth stack configuration file must be directly edited to allow input devices and connect to them automatically and naturally— this step requires unlocking the bootloader, which effectively wipes the device’s data partition. Should you make an oopsies, unbricking options for the Nexus Q are limited and that means users should take extraordinary precaution when writing to the device.
Despite the significant risk to the Nexus Q– you can’t help but be excited at the idea of connecting additional gadgets to the device. So if you’re feeling a little lucky, brave or just plain curious, be sure to check out the complete thread— which you can find at the source link below.
source: XDA Forums
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