August 10, 2013 By: Will Verduzco
Just a few days back, we covered the unfortunate news that official restore images for the new 2013 Nexus 7 were not yet available. Much speculation pointed towards Qualcomm as the underlying cause for the delay, given that such a trend was observed on previous Qualcomm-based Nexus devices. Thankfully, either due to a change of heart by Qualcomm or Google, the factory images are now available. Furthermore, the component drivers are now also available, so those looking to compile from source can do so with ease.
The 359 MB factory restore image comes in the form of build JSS15J. For those keeping track, this is the same build that is found after the second OTA for the device. The drivers come from Asus (Audio and Sensors), Broadcom (NFC), and Qualcomm (Graphics, Camera, GPS, WiFi, Bluetooth, Sensors Media, DRM, DSP, and USB). They should provide custom ROM developers with all they need to get the ball rolling with the aftermarket development we all know and crave.
August 7, 2013 By: Will Verduzco
Now that’s a doozy, isn’t it? Before proceeding, let’s take a moment for that to better sink in. In addition to support from the AOSP, one of the hallmarks of the Nexus program has traditionally been the availability of factory restore images. This is more than a simple convenience for Nexus device owners. Rather, it allows for users to safely and reliably restore their devices to their factory state.
As a result of the availability of factory restore images, Nexus device owners always had a safety net available for when (not “if” here at XDA) they decide to leave the confines of stock software and venture into the realm of aftermarket development. And the loading of unsupported firmware was always a relatively supported task, as evidenced by the availability of the simple command fastboot oem unlock.
There have been minor inconveniences along the way, however, as exemplified by the Nexus One and Nexus 4 factory images. Ultimately, these issues were all resolved in some way or another. For the Nexus One, HTC was able to release factory images. And for the Nexus 4, Google released the images after some time had passed. However one thing links these devices, along with the new Nexus 7 (2013): Qualcomm.
As a quick refresher, the Nexus One used the original Snapdragon system-on-a-chip with a single core Scorpion CPU mated to an Adreno 200 GPU. The Nexus 4 uses the Snapdragon S4 Pro, which features four Krait CPUs and an Adreno 320 GPU. Finally, the Nexus 7 uses a potentially lower-binned Snapdragon 600, which has been relabeled as an S4 Pro. And coincidentally, all of these devices have faced significant setbacks in their factory image availability.
Well, I see that people have figured out why I’m quitting AOSP.
There’s no point being the maintainer of an Operating System that can’t boot to the home screen on its flagship device for lack of GPU support, especially when I’m getting the blame for something that I don’t have authority to fix myself and that I had anticipated and escalated more than 6 months ahead.
While this was the most clearly the issue has thus far been stated, his followers knew something was amiss ever since JBQ tweeted on the matter back on July 30th:
That feeling when lawyers sabotage the launch you spent 6 months working on? I haz it. Sad sad sad sad sad sad.
The bottom line of the factory image drama is simple: We currently have no officially supported way to factory restore our Nexus devices. We don’t know if this will be solved by Google and Qualcomm like it was for the Nexus 4, or if this will remain a longer-standing issue requiring the intervention of an OEM partner, as was the case with the Nexus One. And finally, this forced the man ultimately in charge of the technical side of the Android Open Source Project to resign.
Luckily, there are options available for users looking to restore their factory firmware, thanks to XDA Senior Member ATGAdmin who released a factory restore package for users in need. In fact, a certain editor-in-chief of a certain mobile development forum’s news site already had to make use of such accommodations after some late-night flashing without adequate precautions left him with an unusable slab. However, these images are unsupported, and it would ultimately be better if they were to come from Google themselves.
Because of this issue, and past issues like it, the future direction of the Android Open Source Project is unfortunately all too nebulous. It’s times like these that we’re grateful that other open source options are beginning to emerge.
[Via Android Police]