Searched refs:explicitly (Results 1 – 25 of 223) sorted by relevance
123456789
/frameworks/compile/slang/tests/P_warnings_deprecated/ |
D | stderr.txt.expect | 2 ../../../../../frameworks/rs/scriptc/rs_math.rsh:6482:5: note: 'rsClamp' has been explicitly marked… 4 …/rs/scriptc/rs_object_info.rsh:381:5: note: 'rsGetAllocation' has been explicitly marked deprecate…
|
/frameworks/opt/setupwizard/tools/gradle/ |
D | android.properties | 10 // unless explicitly enabled
|
/frameworks/base/docs/html/guide/practices/ |
D | screen-compat-mode.jd | 90 screen compatibility mode when the application does not <strong>explicitly declare that it supports 93 toggle screen compatibility mode on and off (figure 3). An application can also explicitly 123 android:targetSdkVersion}</a> to {@code "10"} or lower and <strong>does not explicitly 131 android:targetSdkVersion}</a> to {@code "11"} or higher and <strong>explicitly declares that it does 175 practice is to always explicitly declare your support for different screen sizes using the <a
|
D | verifying-apps-art.jd | 62 <p>Under Dalvik, apps frequently find it useful to explicitly call {@link 198 size should be approximately the same as for Dalvik. However, if you explicitly
|
/frameworks/native/cmds/dumpstate/ |
D | dumpstate.rc | 32 # Device Owner explicitly requests it, and shared with the Device Policy Controller (DPC) app only
|
D | bugreport-format.md | 66 which had to be passed do `dumpsys` explicitly (i.e., trhough a
|
/frameworks/base/docs/html/guide/topics/manifest/ |
D | uses-feature-element.jd | 13 <li><a href="#declared">Filtering based on explicitly declared features</a></li> 275 <h3 id="declared">Filtering based on explicitly declared features</h3> 277 <p>An explicitly declared feature is one that your application declares in a 285 <p>Google Play handles explicitly declared features in this way: </p> 288 <li>If a feature is explicitly declared as being required, Google Play adds 293 <li>If a feature is explicitly declared as <em>not</em> being required, Google 295 that reason, an explicitly declared non-required feature is never considered when 301 <li>If a feature is explicitly declared, but without an 311 <p class="note"><strong>Note:</strong> By declaring a feature explicitly and 326 sets up filters for those features, just as it would do for an explicitly [all …]
|
D | uses-permission-element.jd | 22 <p>To control filtering, always explicitly declare
|
D | supports-screens-element.jd | 102 you explicitly declare this attribute at all times. Beware that setting it "false" will 114 you explicitly declare this attribute at all times. Beware that setting it "false" will
|
/frameworks/base/docs/html/training/permissions/ |
D | requesting.jd | 64 user has to explicitly give approval to your app. 142 the app has to explicitly ask the user for permission. 316 same way it would if the user had explicitly granted your request through the 321 <strong>Note:</strong> Your app still needs to explicitly request every 356 same way it would if the user had explicitly rejected your request again.
|
D | index.jd | 37 information outside of its sandbox, the app has to explicitly request
|
/frameworks/base/docs/html/training/tv/playback/ |
D | options.jd | 21 Since the user did not explicitly request to pause playback, the default behavior might seem
|
/frameworks/base/docs/html/guide/topics/security/ |
D | normal-permissions.jd | 44 permission explicitly. By contrast, there's no great risk in allowing an app
|
/frameworks/base/cmds/uiautomator/cmds/uiautomator/ |
D | uiautomator | 65 # if they are not explicitly specified
|
/frameworks/base/docs/html/ndk/guides/ |
D | cpu-arm-neon.jd | 82 <p>You should explicitly check that {@code android_getCpuFamily()} returns {@code
|
/frameworks/base/docs/html/training/swipe/ |
D | add-swipe-interface.jd | 94 automatically supported. However, explicitly declaring the {@link
|
D | respond-refresh-request.jd | 153 you need to explicitly turn the progress indicator on with {@link
|
/frameworks/base/docs/html/about/versions/marshmallow/ |
D | android-6.0-changes.jd | 298 {@code RTLD_LOCAL} is the default, so calls to {@code dlopen(3)} that didn’t explicitly use 299 {@code RTLD_LOCAL} will be affected (unless your app explicitly used {@code RTLD_GLOBAL}). With 320 the device and its content over a USB connection, users must explicitly grant permission for such 322 consideration that the interaction must be explicitly enabled.
|
/frameworks/native/opengl/specs/ |
D | EGL_ANDROID_create_native_client_buffer.txt | 193 - Set color formats and usage bits explicitly using additional attributes,
|
/frameworks/base/packages/SystemUI/docs/ |
D | demo_mode.md | 27 …on-exit commands will automatically flip demo mode on, no need to call this explicitly in practice)
|
/frameworks/base/docs/html/training/articles/ |
D | assistant.jd | 243 explicitly for every window created by the activity, including Dialogs. Your 248 firing. The activity which uses <code>FLAG_SECURE</code> can still explicitly
|
/frameworks/base/docs/html/training/in-app-billing/ |
D | list-iab-products.jd | 50 …g the query, you will need to specify the product IDs for the products explicitly. You can manuall…
|
/frameworks/base/docs/html/training/efficient-downloads/ |
D | regular_updates.jd | 53 <p>A simple approach is to offer preferences to allow users to explicitly set their required update…
|
/frameworks/base/docs/html/training/wearables/apps/ |
D | creating-app-china.jd | 113 wearable app, you must selectively add those Google Play service APIs into your app and explicitly
|
/frameworks/base/docs/html/training/sync-adapters/ |
D | creating-stub-provider.jd | 171 transfers with the content provider, but transfers only occur if you do them explicitly.
|
123456789