Google's position on this has always been that they're open to the carriers/manufacturers doing whatever they want with the software, and when they do something

Google's position on this has always been that they're open to the carriers/manufacturers doing whatever they want with the software, and when they do something bad, well, people do bad things sometimes. I find it amusing that when Google is open to carriers/manufacturers doing whatever they want, people (usually non-android users, though you're an exception here) complain about how they're not open, and when Google tries to take more control of the development process to protect the user experience, people (again, usually same non-android users) complain about the same thing. That said, I think Google could definitely do things better. I, for one, wish Google would exercise their "Google Experience" branding to enforce unlocked boot loaders and root access. On the issue of open sourcing Honeycomb, I could really care less. On the spectrum of closed to open, they're way farther on the open side than anyone else in the industry so I don't find it hypocritical at all for them to claim to be open. (NB: I also own a Motorola device with a locked boot loader. I was very surprised and delighted by how much the devs were still able to do, but I definitely wish I could get some custom kernels installed.)