Earlier quoted context omitted.
I think you mean "not very open", as in not community built, or some other type of extreme openness like that (open close is a scale, it's not black or white). But I'd argue that while Android should remain open source (you can use the source once it's ready), it should be even more "closed", in the sense that Google needs to have a lot more control over what the manufacturers/their partners can do with Android. Why?…
Yes, I was pointing at the community aspect of open-source. Just to get some source dumps after a while does not mean "open-source" to me. Seems people at Hacker News see this differently. Yet, I agree with your comments, in general. Why not split it like they did for Chrome (suggestion in the comment below).
There is a good reason for that. Show me one "community driven" open source project successful in the scale that Android is. Think about it, think about the other community driven SmartPhone OS projects and why they failed. What trade offs Google makes with Android are very fair and necessary - once they get the kernel bits in Korg it will only get better.