I'm also an Android developer and I don't share those concerns. There have been some frustrations, yes, but there are usually decent workarounds for a lot of things. As an example: Bluetooth support wasn't really solid until 2.0, yet there are excellent backport open-source libraries that make it easy to provide that support to 1.5 and 1.6 devices.
I completely disagree about reflection as well. Using reflection you can degrade gracefully for platforms that dont support what you're doing. Reflection is not ugly at all, it actually quite an elegant deign pattern imho.
If you're ending up with 6 layouts for each screen you're doing something wrong and perhaps overreaching in your support for older devices or your layout is overly complicated. It's unreasonable to think the latest Mass Effect game would run on a tiny 320x240 screen. And while that's hyperbole, yes, the point is made.
Just to be clear though, I don't find you concerns invalid, However I don't think this is unique to Android.
Granted there is still much work Google and the manufacturers could do to streamline all of this. But any software development platform, any OS, has some level of variation for what is supported. OSX, Linux, iOS, WebOS, Windows, Windows Mobile, Windows Phone 7, Symbian, HTML5/JS/CSS, Blackberry OS. Really the only platforms that don't, are the video game consoles. But now even that's starting to happen there too with external storage and peripherals.