https://twitter.com/Arubin/status/27808662429
This ("access to source code") is clearly less than GPL, and that's OK, as other commenters point out.
But what they're offering now with Honeycomb is less than Rubin's definition above.
From a support point of view, I cannot see any reason why any hardware manufacturer would go along with GPLv3 software. It adds a level of complexity that just doesn't make much sense to deal with, because it's not the manufacturer's best interest to support ANY code, just the code that they have put on the device.
And as far as supporting any code, most manufacturers of processors do in fact support running any code you like on them. Especially the dominant Intel-compatible personal computer, where Apple themselves support running any operating system you like.
Maybe, but then it would have failed in the market place.
Something like most of Motorola's recent phones with locked down bootloader, those aren't in any meaningful sense running an open source OS. At least not any meaningful sense for the average consumer. For a business with the money to roll their own hardware, they can take advantage of the source, but for me, I can't get that kind of touchscreen hooked up to that kind of battery, CPU, and GPU unless I'm willing to accept a closed OS.
Of course the point is moot, since Motorola would never use a GPLv3-licensed Android. I don't really see why, since, as I said, it's not the software but the hardware that I want to pay them for. (Though there's a good chance I would leave the software unmodified.)