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.
The biggest question mark to come out of Google I/O is the Nexus Q. Trying to describe it to someone is an exercise in awkwardness at the very least. Google desicribes it as a “social streaming media player,” and once you see it working, it kind of makes sense. At $299 a pop, however, you have to wonder if this is more of a solution looking for a problem.
Personally, I like the concept, and once I update my router I should be able to give this thing a full review (seems like the Q is having issues with some routers and as luck would have it, mine is one of them). In any case, the idea is that anyone with an Android device, the Q app, and Play Store music or video content can easily add that content to the Q’s queue during a party, for example, and everyone gets to play DJ. That’s the social part. In its most basic form, it serves as simply a way to stream your Google Play content through your entertainment system, using your phone or tablet as a remote.
The important thing to realize, though, is that this is a Nexus device, meaning it is made for easy hacking, and to that end, some dev folks over at XDA Forums have put together a little guide on how to unlock, root, install and run apps on the Q itself, which requires pushing commands to it through a computer connected to the USB port since the Q has no real graphical user interface.
The hope is that devs will help expand the capabilities of the Q once new apps or ROMs can be cooked up. So there just might be an audience for this thing yet.
source: xda – rooting and unlocking | xda – installing apps
Good news from Koush of ClockworkMod fame… an alpha test build of ClockworkMod version 126.96.36.199 has been released that greatly speeds up device backups, and also reduces the file size of incremental backups to around 20MB.
For those who don’t know, ClockworkMod Recovery is a replacement for the stock recovery of any Android device. The recovery is basically a partition on the device’s memory that you can boot into and perform some basic functions, like a factory reset or a restore of the stock ROM. Besides that, stock recoveries don’t usually let you do much more.
ClockworkMod Recovery, however, allows you to perform several advanced recovery, restoration, installation and maintenance operations that aren’t usually possible with the stock recovery. It can be used used to help gain root access, back up device data, install custom ROMs and kernels, install themes, mods and more. ClockworkMod, built by Koushik Dutta, has been one of the most popular recovery replacements in the modding community.
Head on past the break for download links and more info.
While Samsung generally makes developer-friendly devices, Verizon Wireless went ahead and became a party-pooper by locking the bootloader of the Galaxy S III smartphone. Of course people didn’t take too kindly of that and immediately went to work and take it to Big Red. Well a landmark achievement has been accomplished by a tireless developer who hates the needless extras and bloatware on Verizon’s Samsung Galaxy S III. Thanks to superstud invisibleK of RootzWiki, interested parties of the Verizon variant of the Galaxy S III will now be able to slap on some root action, with little to no trouble. Looks like that recently-released stock image is looking just a little more tantalizing, isn’t it?
Naturally, those of you who are interested will want to take extreme caution as rooting the device will not only void the warranty, but any mishaps or stumbles could possibly result in an unusable or bricked device. Now that we gave you Verizon Galaxy S III owners a full disclaimer, hit the break to see the full detailed instructions on how to get in on some sweet, sweet root action.
Samsung Updates has released the official stock firmware for the Verizon version of Samsung‘s flagship Galaxy S III smartphone. This is great news for ROM modders, hackers, and devs since it now offers the safety net of being able to always get back to stock should things go wrong.
This could lead to great new ROMs being cooked up for the S III, but Verizon users have another barrier to get through first. The bootloader on the Verizon S III appears to be locked, meaning no easy hacking or flashing of unsigned images, and no one has been able to unlock or root it yet. Verizon is known for keeping their phones locked down, with the exception of Google’s Galaxy Nexus, and it’s unlikely they would change their policies for the S III. Hope is not lost, however, since devs have been known to find loopholes in the past. As more S III’s hit the streets, the chances get better that someone will find a way to crack this beast. Let’s keep our fingers crossed.
Still, the stock firmware is greatly appreciated and a good first step on the road to root.
source: samsung updates
Remember when Ice Cream Sandwich was the bomb? It seems so long ago, but how things change as ever since Google announced Android 4.1 Jelly Bean last week, everyone is clamoring to get it on their device. There has been numerous ports so far, but we can now add the Nexus S and the Nexus S 4G to the list. The Nexus S port came from XDA member DeXmax and now XDA member CooLoserTech ported it to the Nexus S 4G.
Unfortunately everything isn’t working and since both ROMs are cut from the same cloth, you can expect the non-working list to be the same.
Since Jelly Bean’s recent announcement, there’s been a major scramble for developers to get their hands dirty and work on individual ports for all types of devices. While we’ve seen a port here and there, most folks have been anxiously waiting on what would be done from the CyanogenMod team. Well you should note that the famed development team has already been hard at work on its version of the new Android OS and took some time to share some thoughts on what it has done in preparation for the new CM release. First thing’s first: CM’s version of Jelly Bean will now be identified as CM10 (following CM9 for ICS). Here’s the reasoning behind the thought:
“Many have asked whether JB will be CM9.1 or CM10. Keeping with the pattern thus far, every newly named AOSP update results in a bump to the CM major version. This has the added benefit of fitting into the pattern of [insert codename position in the english alphabet] = CM version. Examples being: G is the 7th letter thus CM7, I is the 9th letter thus CM9 and J = 10″.
Next, the CM team highlights how Project Butter will impact device requirements for the CM10 port. Turns out it shouldn’t be too much of an issue for
older existing devices. Here are some additional thoughts regarding the topic:
“The ‘Project Butter’ enhancements to Android are much anticipated and should not be a huge pain to merge. We anticipate some breakage in existing libs but nothing that the reference board devices or some hackery won’t overcome. Essentially, if your device met our criteria for CM9 (512mb RAM, etc) and is already supported, then you should be in line for CM10. There may be some added headaches around hwcomposer, but we’ll cross that bridge when we get source”.
So there you have it folks. It looks we’re set for what looks to be a smooth ride with the upcoming CM10 version. Hopefully all of you will be ready when the time comes.