This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I'm using a RelativeLayout for a very simple app which consists of a textView at the top and a FrameLayout at the bottom. But the FrameLayout keeps overlapping the TextView on small-screen devices (like a cellphone). Here's some of the things I've tried that *haven't* worked to resolve the problem. (I tried Weight="1", but it's a relativeLayout, so Eclipse gives an error message. And I tried android:layout_below="@id/theText" but the contents of the FrameLayout then decide to vertically align themselves at the *top* of the FrameLayout...)
The key is, you layout the frame's alignment to the bottom of the screen and you make it below the text area.
Now the Frame will always take the space from just below the text to the bottom of the screen. The problem is that your content is probably bigger than that, which is why your bottom-aligned frame overlapped the text to begin with. Using the above mechanism will essentially ignore the frame's 'wrap_content' height to make it align appropriately. So to get the content on small screens you will need to wrap the FrameLayout into a ScrollView.
This with an AnalogClock that makes the Frame not fit on small screens. See the result image below. (Note the area with the Clock should scroll but that isn't shown in the static image). Also note that I only have one thing inside my FrameLayout. If that is your case, I would replace the FrameLayout with the ScrollView instead of wrapping it in the ScrollView.