13
Feb
image

Here's The Android 4.2.2 JDQ39 Update For The Yakju GSM Galaxy Nexus [Manual Installation Instructions]

Posted by in Galaxy Nexus, Google, Jelly Bean 4.2, News

A few days ago, Google pushed out the Android 4.2.2 (build JDQ39) update to the takju variants of the Galaxy Nexus. Takju Nexuses are the devices sold in the Google Play Store, whereas yakju ones can be found in other retail channels. Good news for those waiting on the latter - though a day after its sibling, we finally have the yakju OTA file that can be applied manually on any stock device, including unrooted ones with stock recovery.

If you're not sure whether you have a takju or yakju variant, download Nexus Update Checker from the Play Store and see what it says.

12
Feb
image

Here's The Android 4.2.2 JDQ39 Update For The Takju GSM Galaxy Nexus [Manual Installation Instructions]

Posted by in Galaxy Nexus, Google, Jelly Bean 4.2, News
Last Updated: February 13th, 2013

A couple of hours ago, Google started rolling out the Android 4.2.2 update to a very limited subset of Nexus devices (build JDQ39). At this point, almost nobody can get the OTA pulled by going through the Settings screen, but don't worry - one of our loyal readers extracted the OTA url for the Galaxy Nexus and sent it over to us (great work, Daniel Koch!).

For now, we only have the link for the takju Galaxy Nexus variant, i.e. GNex handsets bought from the Play Store. Once we get the yakju build, we'll update this post.

If you're not sure whether you have a takju or yakju variant, download Nexus Update Checker from the Play Store and see what it says.

07
Nov
nexusae0_nexus_thumb

Google Publishes Sprint Galaxy Nexus Factory Image For The First Time (Android 4.1.1)

Posted by in Android OS, Development, Galaxy Nexus, Google, Jelly Bean 4.1, News, Sprint

After Google's release of "experimental" binaries for Sprint's Galaxy Nexus variant, Jean-Baptiste Queru (Chief Android Release Engineer) confirmed that the binaries represented not full AOSP support, but the "taking down [of] many hurdles that were preventing [AOSP support]," citing bugs in the network stack as one of the issues yet to be addressed.

Less than one month later, it would appear that those issues have been sorted, as Google today published the toroplus' factory image for the first time. The image, for those who are wondering, carries Android 4.1.1 (build FH05).

image

So what does this mean? For one thing, it means that four months after Verizon's Galaxy Nexus started getting with the program, Sprint's Galaxy Nexus has caught up.

09
Jul
vzw-galaxy-nexus

Verizon Galaxy Nexus Is Closer Than Ever To Full AOSP Support - But It's Not There Yet

Posted by in Development, Galaxy Nexus, Jelly Bean 4.1, News, Samsung, Verizon Wireless

Earlier today, the Jelly Bean source code rolled into AOSP (Android Open Source Project). This is a big deal - one we've been waiting for since the great Google I/O unveiling. What does it mean exactly?

It means that ROMs that are built from AOSP, like CyanogenMod, can now start integrating the Jelly Bean code and release the first true JB nightlies. Not broken ports from the Galaxy Nexus builds - real ROMs. They can also work out bugs because they can see the source code.

Manufacturers can now start working on updating their devices to the actual Jelly Bean release - remember, Google was still working on the final touches to JB when they released the preview, so even OEMs didn't have what rolled out today.

03
Jul
samsung-galaxy-nexus

Samsung And Google To Release OTA Update To Galaxy Nexus To Avoid Injunction Sales Ban In US

Posted by in Galaxy Nexus, Legal, News, Samsung

According to AllThingsD, Google is working quickly to release a software patch to its Galaxy Nexus handset in order to avoid a preliminary injunction sales ban in the US. Google says the patch will be coming very soon (eg, tonight). The news came hot on the heels of Judge Koh's denial of Samsung motion to stay the ban while it appealed the injunction to the circuit court.

Google will also be assisting Samsung in its appeal of the ban, and to challenge the legitimacy of one of Apple's patents on universal search. Google is seeking to have the patent invalidated at the USPTO, as well.