Warning: This <FrameLayout> can be replaced with a <merge> tag

Are you using this as the main layout of your activity? If so, you can replace it with a merge tag like this:

<merge xmlns:android="http://schemas.android.com/apk/res/android"
    android:layout_width="match_parent"
    android:layout_height="match_parent" >

    ... a textview and 2 linearlayouts


</merge>

At setContentView, Android will take the children of the merge tag and directly insert them to the FrameLayout with @android:id/content. Examine both approaches (FrameLayout vs merge) with HierarachyViewer to see the difference.

Refer this post by the Romain Guy for more information. It tells you why the merge option is suggested.

To understand this, you need to understand how layouts are inflated and placed.

Let's say for example, you have an activity and this is the layout xml you use. Here is what the layout of the activity looks before you put your layout file.

<FrameLayout> // This is the window
    <FrameLayout> // This is activity
    </FrameLayout>
</FrameLayout>

There might be few other layers depending on the device/OS.

Now when you inflate your layout file and put it in, this is how it will look.

<FrameLayout> // This is the window
    <FrameLayout> // This is activity
            //A textview and 2 linearlayouts
    </FrameLayout>
</FrameLayout>

Do you see the FrameLayout inside the other FrameLayout? It is redundant to have that since it does not add much value. To optimize, you can replace your outer FrameLayout with the <merge> tag. This is what it will look like.

<merge> // This is the window
    <FrameLayout> // This is activity
            //A textview and 2 linearlayouts
    </FrameLayout>
</merge>

Notice how there is no extra FrameLayout. Instead, it is just merged with the FrameLayout of the activity. Whenever you can, you should use <merge>. This doesn't only apply to FrameLayouts. You can read more about it here. http://developer.android.com/training/improving-layouts/reusing-layouts.html#Merge

Hope this helps.