Lines Matching full:your
71 setting an activity theme in your app's manifest file. Setting an activity theme in your app's
73 hidden in your app (though strictly speaking, you could programmatically override the
89 to render your UI before instantiating your app's main activity.</li>
95 your app:</p>
115 programmatically), the flags remain in effect unless your app clears them.</p>
119 to set your activity layout to use the same screen area that's available when you've enabled
120 {@link android.view.WindowManager.LayoutParams#FLAG_FULLSCREEN}. This prevents your
148 activity), your app needs to reset them if you want to hide the bars again.
150 discussion of how to listen for UI visibility changes so that your app can
153 <li>Where you set the UI flags makes a difference. If you hide the system bars in your activity's
157 persist as the user navigates in and out of your activity, set UI flags in
171 <p>On Android 4.1 and higher, you can set your application's content to appear behind
176 {@link android.view.View#SYSTEM_UI_FLAG_LAYOUT_STABLE} to help your app maintain a
179 <p>When you use this approach, it becomes your responsibility to ensure that critical parts
180 of your app's UI (for example, the built-in controls in a Maps application) don't end up
181 getting covered by system bars. This could make your app unusable. In most cases you can
182 handle this by adding the {@code android:fitsSystemWindows} attribute to your XML layout file, set to
187 layout for your app. To directly manipulate how your
193 insets (and hence your app's layout) however you want. </p>
