Lines Matching full:your
42 don?t have a device running Android 4.2 on which to test your app, use the Android 4.2 system
43 image to test your app on the <a href="{@docRoot}tools/devices/emulator.html">Android emulator</a>.
44 Then build your apps against the Android 4.2 platform to begin using the latest APIs.</p>
51 <h3 id="ApiLevel">Declare your app API Level</h3>
53 <p>To better optimize your app for devices running Android {@sdkPlatformVersion},
54 you should set your <a
61 conditions to your code that check for the system API level before executing
62 APIs not supported by your <a
82 changes that might affect your app?s behavior:</p>
88 able to access your content provider, you must now explicitly set <a
99 if your app requests the {@link android.Manifest.permission#ACCESS_COARSE_LOCATION} permission but
101 <p>To meet the privacy expectations of users when your app requests permission for
107 read-only. If your app attempts to write changes to settings defined in {@link
110 <p>Even if your value for <a href="{@docRoot}guide/topics/manifest/uses-sdk-element.html#target">{@code
112 android:minSdkVersion}</a> is lower than 17, your app is not able to modify the settings that have
116 <li>If your app uses {@link android.webkit.WebView}, Android 4.2 adds an additional layer of
117 security so you can more safely <b>bind JavaScript to your
118 Android code</b>. If you set your
121 want available to your JavaScript (the method must also be public). If you do not provide the
122 annotation, the method is not accessible by a web page in your {@link android.webkit.WebView}
125 to 16 or lower, the annotation is not required, but we recommend that you update your target version
142 to the full suite of input events. Your dreams run in your app?s process and have full access to
148 designed to be similar to those of {@link android.app.Activity}. To specify the UI for your
159 You cannot initiate a {@link android.service.dreams.DreamService} from your
162 <p>If your dream is interactive, you can start an activity from the dream to send the user into
163 your app?s full UI for more detail or control. You can use {@link
167 <p>To make your daydream available to the system, declare your {@link
170 in your manifest file. You must then include an intent filter with the action {@code
213 <p>Android now allows your app to display unique content on additional screens that are connected
217 {@link android.app.Presentation#onCreate onCreate()}, specify your UI for the secondary display
220 android.app.Presentation} class provides the region in which your app can display a unique UI on the
223 <p>To detect secondary displays where you can display your {@link android.app.Presentation},
230 <p>To get the default display for your presentation, call {@link
238 <p>You can then display your presentation by passing the {@link android.view.Display} object
239 to a constructor for your {@link android.app.Presentation} class. Your presentation will now
254 <p>To further optimize the UI in your {@link android.app.Presentation} for
259 applied to your application or activity.</p>
264 to request additional resources from your {@link
268 the appropriate resources from your app that are best suited for the
285 <p>Android now allows users to add app widgets to the lock screen. To make your <a
288 android:widgetCategory} attribute to your XML file that specifies the {@link
290 and {@code keyguard}. By default, the attribute is set to {@code home_screen} so users can add your
291 app widget to the Home screen. If you want your app widget to be also available on the lock
301 <p>You should also specify an initial layout for your app widget when on the lock screen with
305 a layout that can appear immediately until your app widget is initialized and able to update the
309 size your app widget when on the lock screen, see the <a
324 <p>As an app developer, there?s nothing different you need to do in order for your app to work
326 device, the data your app saves for a given user is kept separate from the data your app saves
328 your app is running and provides your app access to only that user?s data and does not allow
333 <p>Whenever your app saves user preferences, creates a database, or writes a file to the user?s
336 <p>To be certain that your app behaves properly in a multi-user environment, do not refer to your
349 accessible while running as a different user. From your app?s point of view, each user is running
354 <p>If your app wants to identify unique users such as to gather analytics or create other account
357 unique installations</a>. By creating a new {@link java.util.UUID} when your app starts for the
359 users install your app on a single device. Alternatively, you can save a local token fetched from
360 your server or use the registrations ID provided by <a
363 <p>Beware that if your app requests one of the hardware device identifiers (such as the WiFi MAC
378 android.provider.Settings.System} or {@link android.provider.Settings.Secure}. If your app is
385 the system log when running your app on Android 4.2 or higher.</p>
401 <p>To begin supporting RTL layouts in your app, set the {@link android.R.attr#supportsRtl
402 android:supportsRtl} attribute to the {@code <application>} element in your manifest file
404 display your app with RTL layouts. For instance, the action bar will show the icon and title
408 <p>If you need to further optimize the appearance of your app when displayed with an RTL layout,
424 layout-direction-right-to-left}). For example, you can save your default layout files in
425 {@code res/layout/} and your RTL optimized layouts in {@code res/layout-ldrtl/}.
439 have been converted to their Arabic equivalents if your device has been set to the Arabic locale.
542 tell the Renderscript runtime your scripts do not require strict IEEE 754-2008 floating point precision.
543 This precision allows flush-to-zero for denorms and round-towards-zero. In addition, your Filterscript
