Verizon Xoom Jelly Bean OTA Soak Test and Public Release

On May 10, 2013, Motorola began sending out soak test invites to members of the Motorola Feedback Network who own a Verizon Xoom. The update is the long-awaited Jelly Bean update. Specifically, based on AOSP tags, it appears that the Verizon model will be receiving Android 4.1.2, build JZO54L. As for the differences between the common JZO54K build and JZO54L, it appears they’re all minor Verizon-related changes specifically for the Xoom.

Historically, the soak test rolls out within a week of invites being sent, with a public OTA rollout within a week after the soak test goes out. I have added JZO54L information here on the site, but we still have no OTA links or radio information. That information will be updated as soon as it’s available.

Also, in case anyone is wondering, this update applies to both MZ600 (Verizon 3G/CDMA) and MZ602 (Verizon 4G/LTE) models. Unfortunately, if you have an international 3G Xoom (MZ601, MZ605) or a WiFi model (MZ604, MZ606) with non-US firmware, your Xoom will remain on Ice Cream Sandwich. This is because, while the US variants run stock Android firmware and get updates from Google, all international models have firmware that is created and updated by Motorola. The decision to update the US models was Google’s. The decision to not update international models was Motorola’s.

And the Wait for the Verizon Xoom’s Jelly Bean Update Continues

Nine months ago, Google released Android 4.1/Jelly Bean to the world. At Google I/O, Vic Gundotra promised over-the-air updates to “Nexus S, Motorola Xoom, and Galaxy Nexus devices beginning in mid July [2012]“. Well as we all know, when Google promises an OTA, they’re referring to firmware for those devices that they control. Google made good on those promises and by September 2012, Jelly Bean had been rolled out to every Nexus S device, the WiFi-only Motorola Xoom, and the Verizon and yakju/takju HSPA+ Galaxy Nexus variants.

Conspicuously absent from that list was the Verizon Motorola Xoom variant. A build of Android 4.1.1/JRO03H (the same build as the WiFi-only model) was leaked on the XDA Developers forums, but the build had problems despite the leaker claiming that Verizon had signed off on it.

Needless to say, the build never saw public release. In October 2012, Android 4.1.2 began rolling out to the WiFi-only Xoom, and it was to be the Xoom’s last OTA update. Given Verizon’s usual two month delay, most Xoom owners figured we would finally see the Verizon Xoom’s update around December or early January at the latest.

It’s now mid-April and still there has been no OTA. On Motorola’s official Android software update page, the update timeline has changed from Q4 2012 to Q1 2013, and now simply states that the Verizon Xoom “will be updated to Jelly Bean”.

Considering that Android 4.1.2 released six months ago, this is getting comical. I’m not sure if the delay lies with Motorola or Verizon at this point. It’s possible that there are radio or driver issues that Motorola would have to provide fixes for, or it could be that Verizon is just sitting on the update. Being over two years old now, the Xoom is definitely not a priority device for Verizon anymore. This is further exacerbated by the fact that sales of the Verizon variant were pretty bad by most accounts.

I have no doubt that we will see the update, but at this point I’m just laughing. Is six months honestly not enough time to get this update tested and released? Considering that this will be the Xoom’s last update, it seems that all parties would have a solid interest in getting it out there so this awesome device can finally be put to bed.

Android 4.2.2 for Verizon Galaxy Nexus Is Now Official

Today, Verizon posted an article on their official news blog announcing the Android 4.2.2 update for the Galaxy Nexus. This is the same build, JDQ39, that leaked several weeks ago. If you already flashed to that build, there’s nothing you need to do as the official update uses the exact same file.

You can see the official announcement on Verizon’s News Blog.

mysid 4.2.2/JDQ39, Verizon Galaxy Nexus OTA Update in Testing

Verizon is currently testing a mysid 4.2.2 build from Google. The build number is JDQ39 just like all other Nexus devices. The OTA file can be downloaded from Google’s servers directly at http://android.clients.google.com/packages/ota/verizon_prime/5939ff985946.signed-mysid-JDQ39-from-JRO03O.5939ff98.zip.

Even though this is a testing build, logic dictates that this will become a public OTA in due time. JDQ39 was the official public OTA for the Nexus 4, 7, 10 and GSM models of the Galaxy Nexus, so I would be shocked if Verizon doesn’t sign off on this build. Because of this, I have added it to the mysid page in anticipation of it becoming a public OTA. If, for whatever reason, a month or more goes by and it becomes obvious that JDQ39 won’t be a public OTA, I will remove it. All credit goes to XDA forum member El Madhatter for getting the link.

Nexus One Page Now Available

By popular request (though I’m still not sure why, since the phone is 3 years old), I have added a page for all official Nexus One OTA updates and images. If you’re familiar with the Nexus One’s release history, you’ll look at my page and say “Wow, there were a ton more than this.” Anything not listed on my page was a leak or test build (they were numerous on the N1) and not officially released by Google to the general public. If you’re still rocking an N1, enjoy!

Android 4.2.2/JDQ39 Rolling Out to Galaxy Nexus, Nexus 4, Nexus 7 and Nexus 10

Android 4.2.2, build JDQ39 has begun rolling out for the following firmware:

Nexus 4 – occam
Nexus 7 – nakasi, nakasig
Nexus 10 – mantaray
Galaxy Nexus – takju, yakju

As OTA links become available, I will mirror them here. No word yet on any new firmware rollouts for Verizon (mysid) or Sprint (mysidspr) Galaxy Nexus models. In my opinion, however, this is getting ridiculous on the Verizon front. Verizon’s draconian testing policies are prohibiting Google from rolling out an update to the device. With this rollout, the Verizon Galaxy Nexus is now four updates behind GSM models.

Android Gaming Consoles: A Lesson in Irrelevance

Lately, there has been a lot of buzz about Ouya, a new Android gaming console that is expected to see release in 2013. There was an article yesterday on several Android outlets talking about how Ouya, listening to customer feedback, made some changes to the controller. This got me thinking…does this really matter in the grand scheme of things?

The answer is no, it doesn’t. The Ouya and other upstart Android consoles will be completely dead on arrival and will be a distant memory three to four months from now. Between Nintendo launching the Wii U back in November and Sony and Microsoft launching the “PS4″ and “Xbox 720″ this year, there simply is no room in the console marketplace for an Android console. Why is that?

It’s simple, really. Android does not provide the gaming experiences that people expect from modern-day gaming consoles. Hardcore gamers – traditionally the people who keep consoles a viable business – have consistently shown their willingness to pay top-dollar for games that are immersive, full of content, well written, and beautiful to look at. These gaming experiences do not exist on Android. This is not to say there are not great games for Android; quite the contrary, in fact. Let’s examine this more in-depth.

First-person shooter games are very, very popular. There are some good ones for Android such as N.O.V.A. 3 and Shadowgun: Deadzone. I play both of these games regularly and enjoy them thoroughly. That said, however, these games cannot hold a candle to the “800-pound gorilla” franchises like Call of Duty or Halo. Games of that size, scope, and beauty do not exist on Android. Let’s move to other types of games. You will never find a 3D platform game on Android that would come close to matching the brilliance and sheer joy of Super Mario Galaxy 2. Android has no adventure games that can come close to rivaling established franchises like The Legend of Zelda, Darksiders, or Prince of Persia. Even when major publishers make installments in a major franchise for Android – Mass Effect: Infiltrator and Dead Space come to mind – they are incredibly neutered games that don’t have graphics, stories, or gameplay mechanics that are nearly as satisfying as their console counterparts. While not Android, another example that applies to this conversation is Resident Evil 4. Has anyone ever tried playing the iOS version of Resident Evil 4 and compared it to the original GameCube or Playstation 2 release? That makes my point for me.

Now, there is one segment of the gaming world where Android (and iOS for that matter) have it all over consoles. That would be the “Free to Play” games that have loads of in-app purchases. Consoles, as a business model, don’t go for this since gamers are more than happy to pay $60 up front for the entire game. When people sit down to play a game on a console in their living room, they expect the kind of experience that mobile platforms like Android simply do not and cannot provide right now. Nobody wants to sit down and play Where’s My Water (another fantastic game) in 1080p HD on their 42″ plasma TV. While console gamers such as myself are likely to play mobile games as well, the reverse is not necessarily true. The average casual game player who plays games on their phone is probably not likely to buy a game console.

Games are what sell systems. A console without games people want to play in their living rooms may as well not even exist. Until Android can deliver the types of experiences that people expect, and receive, from Sony, Microsoft, Nintendo and 3rd party publishers on modern gaming consoles, Ouya and other upstarts are absolutely pointless and will not generate anywhere near the excitement required to get people to separate from their wallets. We could revisit this conversation in 5 years and have a drastically different take, but for now, good luck if you buy an Ouya.

Sprint Galaxy Nexus Firmware Returns

When the Sprint Galaxy Nexus first launched, I had put up a page for firmware. A few days later, I discovered that the “mysidspr” firmware that runs on Sprint’s model was one of the Samsung-maintained variants and thus, I removed the page. Recently, however, Google has begun to recognize the Sprint model and has begun supporting it in AOSP with binaries, as well as providing factory images. Though this site has been exclusively for Google-maintained firmware, there are always exceptions to every rule.

Due to Google’s backing of this phone, I have restored the firmware page and have updated it with the very latest information available. Moving forward, you will always be able to find the latest updates and factory images for mysidspr just as you do for all the Google-maintained firmware.

As an aside for those of you wondering if one day you’ll see all the Samsung-maintained yakju(xx) firmware mirrored here, the answer is no. I did consider it while considering bringing back the Sprint page, but in the end, several factors led me to decide against it:

1. 100% of the yakju(xx) firmware runs on the same HSPA+ variant that the Google-sanctioned yakju firmware runs on. Which firmware your phone shipped with depended solely on from where or from whom it was purchased. Either way, the phones are exactly the same. Sprint, on the other hand, has its own unique model and mysidspr is the only firmware that runs on it. This makes it more unique in my eyes.

2. There just isn’t enough information about some of the more obscure yakju(xx) variants like yakjuxe or yakjujt. It’s almost impossible at this point to figure out what radio, bootloader, and Android build those originally shipped with out of the box because nobody seems to have noted it originally. Now that a year has passed, nobody can go back and look anymore. Without this information, the pages for many of the yakju(xx) firmware variants would be incomplete. I am not in the business of providing incomplete information on this site. It’s all or nothing.

So, enjoy the Sprint firmware. If you are in need of yakju(xx) information and firmware updates, you can try Efrant’s amazing Galaxy Nexus update thread on the XDA Developers forum.