A good example of this is Amazon. They are doing this successfully.
Imagine you want to sell a Linux laptop with your own Linux distribution. You're just a small shop in California, and you're shopping around to find a manufacturer for your laptops. And you find that anyone connected to Microsoft (Foxconn, Asus, Acer, Gigabyte, etc) can't do any job with you. Would you say "that's fair, Microsoft isn't evil by forcing hardware manufacturers to work exclusively with them" in such situation?
A good analogy would be Microsoft preventing you from selling your fork of Windows on those manufacturers, which happens to be exactly what every big OS maker does, by simply not distributing it under a Free license.
See: https://plus.google.com/112218872649456413744/posts/9HHRURor...
Your argument itself is also somewhat of a mischaracterization, because at least Google could have wrestled redistribution rights for the binary drivers, thus making AOSP actually usable on the nexus, and they didn't even bother with that.
Vendors are a convenient whipping boy when don't care about openness but wanna look like you do.
Subject to the terms of this Agreement, Licensor hereby grants to
You, free of charge, a non-exclusive, non-sublicensable,
non-transferable, limited copyright license, during the term of
this Agreement, to download, install and use the Software
internally in machine-readable (i.e., object code) form and the
Documentation for non-commercial use on an Authorized Android
Enabled Device and non-commercial redistribution for academic
purposes only of a reasonable number of copies of the Authorized
Android Enabled Device Software (the "Limited Purpose"). You may
grant your end users the right to use the Software for
non-commercial purposes on an Authorized Android Enabled Device.
The license to the Software granted to You hereunder is solely for
the Limited Purpose set forth in this section, and the Software
This makes it entirely impossible for AOSP to distribute the driversGithub don't constantly go on about how 'open' Github is, though.
Not really. You will have your mainline Abdroid implementation shutdown if you do this. Google is clearly doing this to make forking a very risky proposition for device manufacturers. It's the antithesis to open.
That is why they are being criticized. It's not about who is more open. It's that Google misled everyone about their intentions.
Unfortunately, this highlights some weaknesses in the GPLv2, which is supposed to guarantee freedom.
It's all according to the previously openly aired plan. Google keeps all of the existing code open source. Anyone who wants to build a fork can do so. Now if they want a hardware platform to run on, go find one outside the Open Handset Alliance ecosystem. It's fair game -- if a hardware partner thinks that one of Google's competitors can provide a better Android fork, they are free to leave the Alliance and go partner with that competitor. They will still get an enormous amount of code for free in AOSP. They just won't get all of the services that Google is building specifically for its own version of Android. How is any of this maintaining an "iron grip" in any way? Just contrast this with Apple where it is the sole owner of everything to do with the OS and app marketplace.