4 Comments

Summary:

Wondering where the factory images are for your shiny new Nexus 7? Google usually posts them, but it hasn’t yet. And now, a key Google employee is “quitting” his responsibility for maintaining such images. The problem appears to be a dispute between Google and Qualcomm.

qualcomm-snapdragon-featured

The lead Googler responsible for maintaining Android factory image software is stepping away from that responsibility. Although he has shared cryptic reasons publicly, Jean-Baptiste Quéru’s comments point to an apparent legal issue with Qualcomm, one of the main chip suppliers for Android phones. In the past, factory images were pulled for Qualcomm-powered Nexus devices as well.

On Wednsday, Quéru posted this on his Google+ page:

“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.”

AOSP is Google’s Android Open Source Project code that anyone can use free of charge. To use Google’s services with that software, however, a license through Google is required. That applies to Gmail, the Google Play store, Google Maps and other Google-specific software.

When Quéru speaks about a flagship device, he’s surely talking about a Nexus product. Other than the Nexus 10, which uses a Samsung chip, the Nexus 4 phone and new Nexus 7 tablet both use a Qualcomm chip complete with Qualcomm’s Adreno GPU and supporting graphics drivers. It’s very likely then that Quéru is talking about a newer Android build for one of these devices. Based on this July 30 tweet from Quéru, it’s likely the new tablet.

That may sound like circumstantial evidence, but there’s some history to back it up. Earlier on Wednesday, Android Police pointed out that the factory images for the new Nexus 7 tablet aren’t yet available online. These images are used to restore Nexus devices to a “like new” state; very helpful to developers and enthusiasts who are dabbling with the software on these phones and tablets. Google has long housed the software publicly on this Android developers page.

Nexus 7 in handAdditionally, other Qualcomm-powered devices have been slow to see their factory image software available online in the past. Droid Live noted in December that the Nexus 4 images were pulled down for a time and later restored. The site asked Quéru about the situation and his reply was, “I can’t comment on that, sorry.” even though a Nexus 4 owner needed the files for device recovery.

Clearly, something is amiss here in Android-land. Sadly, at the end of the day, it’s not just about a legal squabble; it’s about device owners that could have a non-working phone or tablet while they sit on the sidelines waiting for such issues get resolved.

I’ll be reaching out directly to Quéru and Qualcomm for comment and will update this post with any additional information and responses.

  1. Qualcomm have amassed far too much power in the world of SOCs and it’s dangerous. This is a company that’s traditionally been hostile to open source software, unlicensed spectrum and anything else that threatens the huge monopolistic profits that are the lifeblood for its fat IP royalties.

    A damn shame that JBQ got caught in the crossfire.

    Share
  2. Nonetest Askkessk Wednesday, August 7, 2013

    Qualcomm is an innovation killer. Qualcomm has used its money and power in deliberate bids to block the progress of competing technologies rather than competing fairly. #BoycottQualcomm

    Share
    1. Too bad Qualcomm also have the fastest ARM CPUs, AND that their CPUs play better with LTE than anyone else’s. If you want a top tier device, they’re pretty much the only option besides the Exynos, which is available in Samsung devices only.

      Share
  3. John Kneeland Thursday, August 8, 2013

    I don’t know about you, but I find it refreshing that someone isn’t blaming Microsoft for something.

    Share

Comments have been disabled for this post