Thanks for all the info Margret! One thing I still am not sure on though: Somebody mentioned that the device itself reports a larger activity height than there really is because it is not accounting for its own soft keys.
If this is true, then I guess I don't understand how the OS will choose the correct layout or do any automatic adjusting on it if it doesn't know the actual height of the activity. Unless it will just use the one you made specifically for it because it is simply the closest match.
But still, that doesn't help us who use dynamic layouts in code based on height if in fact the Fire is telling the app that it has up to 110
more pixels than it actually does.
I received an email from Amazon saying my apps were approved but they faked me out. After reading closely it said that testing for the Fire is done separately. So who knows. It does sound like this is turning out to be a bit of a disaster for developers and Amazon as well if many/most of the apps do not even look right on their device without special treatment. I had a customer email me a couple days ago asking why my app isn't available on the Fire. I had to bite my tongue to keep from saying what I really wanted to say about Amazon, so I just told him there were some minor compatibility issues and hopefully it would be available soon.
Still not too impressed with the way Amazon handles their Android stuff.