Dianne Hackborn 15 Feb 2012 +54
Okay, let me please please beg you not to do this. I can guarantee you this introduces all kinds of application compatibility issues. We work really hard to give our developers a consistent environment where their apps will operate correctly across all the devices Market runs on, not being impacted by negative reviews from bad devices that they should not have to deal specially with.
If you start making your own distributions of Android behaving in such fundamentally different ways, I suspect we are going to need to start doing things to prevent you from impacting our app ecosystem. I'm not sure what, but I could imagine things such as restricting how users can interact with Market apps on these devices (not allowing reviews or such).
We have let a lot of things in this area slide -- for example to be allowed to include Market on your device you are supposed to fully pass CTS. However, if you start really diverging from the core Android platform (I would argue this takes you well into the realm of a fork rather than a customization) then some deep issues are going to come up about how we handle these custom builds.
We have been putting a lot of thought and work for a number of years into how to let Android applications run on increasingly diverse and dynamic screens. Doing this correctly, without impacting our app developers in a negative way, is a really challenging problem. I also think it is something that needs to be done at the mainline platform level, not as a customization, because doing it right is going to require new well defined interfaces with applications for them to interact with it, possibly starting with just a facility they need to use to opt in to it.