Home
last modified time | relevance | path

Searched refs:SDK (Results 1 – 25 of 114) sorted by relevance

12345

/packages/modules/SdkExtensions/
Dreleased-flagged-apis.txt2 # included in the next SDK extension. This allows APIs to be released in an SDK
7 # Metalava when generating API signature files and stubs for SDK snapshots for
9 # SDK extension (and eventually Android SDK) release.
12 # immediately before the next SDK extension is to be created. Adding them here
20 # Once an SDK extension has been created it will not be possible to use any of
22 # would cause those APIs to be included in SDK snapshots used by the next train
27 # by a comment indicating which SDK extension the section relates to.
29 # Released in SDK Extension #12 - M-2024-05
64 # Released in SDK Extension #11 - M-2024-02
77 # Released in SDK Extension #10 - M-2023-11
DREADME.md4 - deciding the extension SDK level of the device;
5 - providing APIs for applications to query the extension SDK level;
21 extension SDK (for instance `build.version.extensions.r`).
23 exposes APIs to applications to query the extension SDK level.
25 ### Deriving extension SDK level
32 ### Reading extension SDK level
73 4) **packages/modules/SdkExtensions:** Define the new SDK extension version.
98 #### Finalize SDK artifacts
124 together. We currently define a new extension for every Android SDK level that
/packages/modules/AdServices/sdksandbox/tests/testutils/testscenario/
DREADME.md1 # SDK Sandbox Test Scenario Test Utilities
5 This directory contains utilities that allow you to run tests inside of an SDK.
13 invocations and reporting the results from within a SDK Sandbox
15 ## Creating new SDK Runtime tests
17 A simple example of using SDK Runtime testscenario utilities can be found in
21 suite, and a new testable SDK.
23 ### Create a new Test SDK
25 You will first need to define a new Sandbox SDK with your
47 // This runner is used to execute SDK side tests.
56 <!-- This is all normal configuration for a Sandbox SDK provider -->
[all …]
/packages/apps/ManagedProvisioning/studio-dev/
DREADME.md19 …e script pulls the dex files from the device and decompiles them to create an SDK with hidden APIs.
30 ### Updating SDK
32 you need to update your SDK. Depending on how you checked out your tree, there are two ways to
33 update the SDK. In either case, you should pass the `--update-sdk` flag.
35 For a minimal studiow-dev checkout, the SDK must be pulled from the device. Flash your device with
43 For a platform checkout, you have the option to use the built SDK from your tree's out/ directory.
44 This SDK exists if you've previously built with `m`. The script will prefer to use the built SDK if
45 it exists, otherwise it will attempt to pull the SDK from the attached device. You can pass
46 `--pull-sdk` to override this behavior and _always_ pull the SDK from the attached device, whether
47 or not the built SDK exists.
[all …]
Dstudiow604 …if ! yesNo 'This will remove the local Android Studio installation, local SDK, and project gradle …
642 …printWarning 'Could not determine age of Android SDK. This means your SDK is corrupt or out of dat…
645 printWarning 'Android SDK is more than 7 days old.'
916 Pkg.Desc=Android SDK Platform $upperCaseBranchName
/packages/modules/Connectivity/staticlibs/testutils/app/connectivitychecker/
DAndroid.bp24 // Allow running the test on any device with SDK R+, even when built from a branch that uses
25 // an unstable SDK, by targeting a stable SDK regardless of the build SDK.
/packages/modules/AdServices/adservices/service-core/java/com/android/adservices/data/topics/
DTopicsTables.java183 String SDK = "sdk"; field
196 String SDK = "sdk"; field
214 + ReturnedTopicContract.SDK
237 + ReturnedEncryptedTopicContract.SDK
255 String SDK = "sdk"; field
268 + UsageHistoryContract.SDK
DTopicsDao.java365 values.put(TopicsTables.UsageHistoryContract.SDK, sdk); in recordUsageHistory()
425 TopicsTables.UsageHistoryContract.APP, TopicsTables.UsageHistoryContract.SDK, in retrieveAppSdksUsageMap()
450 TopicsTables.UsageHistoryContract.SDK)); in retrieveAppSdksUsageMap()
700 values.put(TopicsTables.ReturnedTopicContract.SDK, app.getKey().second); in persistReturnedAppTopicsMap()
748 values.put(TopicsTables.ReturnedEncryptedTopicContract.SDK, app.getKey().second); in persistReturnedAppEncryptedTopicsMap()
790 TopicsTables.ReturnedTopicContract.SDK, in retrieveReturnedTopics()
800 TopicsTables.ReturnedTopicContract.SDK, in retrieveReturnedTopics()
845 TopicsTables.ReturnedTopicContract.SDK)); in retrieveReturnedTopics()
902 TopicsTables.ReturnedEncryptedTopicContract.SDK, in retrieveReturnedEncryptedTopics()
945 TopicsTables.ReturnedEncryptedTopicContract.SDK)); in retrieveReturnedEncryptedTopics()
/packages/modules/AdServices/sdksandbox/tests/ui/
DREADME.md1 # SDK Sandbox UI Tests
5 The SDK Sandbox UI test suite facilitates the testing of the UI components of the SDK sandbox, such
15 As part of the `SdkSandboxUiTestRule`, an SDK is loaded in the test app. The loaded SDK
17 `SdkSandboxUiTestRule`. If the test needs to interact with the SDK's `SandboxedSdk` object, this
/packages/modules/Bluetooth/android/apishim/
DAndroid.bp36 // needs access to all Build.VERSION_CODES.*, which by definition are only in the newest SDK.
48 // system_X SDK. this ensures that each shim can only use SDK classes that exist in its SDK level.
/packages/modules/Connectivity/tests/common/
DAndroid.bp25 // The target SDK version of the "latest released SDK" CTS tests.
26 // This should be updated soon after a new SDK level is finalized.
27 // It is different from the target SDK version of production code (e.g., the Tethering,
29 // - The target SDK of production code influences the behaviour of the production code.
30 // - The target SDK of the CTS tests validates the behaviour seen by apps that call production APIs.
95 // Tethering started on SDK 30
/packages/modules/AdServices/sdksandbox/flags/
Dsandbox_flags.aconfig8 …description: "This flag make the sandbox activity context based on its corresponding SDK package i…
28 description: "Bug fix for the SDK sandbox selinux input selector"
66 description: "Enables the static dex verifier for the SDK sandbox to run on new SDKs"
/packages/modules/NetworkStack/
DAndroid.bp17 // The network stack can be compiled using system_current (non-finalized) SDK, or finalized system_X
18 // SDK. There is also a variant that uses system_current SDK and runs in the system process
43 // Common defaults to define SDK level
116 // needs access to all Build.VERSION_CODES.*, which by definition are only in the newest SDK.
118 // this target against the lowest-supported SDK (currently 30).
128 // system_X SDK. this ensures that each shim can only use SDK classes that exist in its SDK level.
226 // integer so if the next SDK release happens to use that integer, we don't need to rename them.
342 // The versions of the android library containing network stack code compiled for each SDK variant.
517 // NetworkStack build targeting the current API release, for testing on in-development SDK
/packages/apps/TV/tests/robotests/src/com/android/tv/audio/
DAudioManagerHelperTest.java38 @Config(sdk = ConfigConstants.SDK)
155 @Config(sdk = {ConfigConstants.SDK, Build.VERSION_CODES.O})
166 @Config(sdk = {ConfigConstants.SDK, Build.VERSION_CODES.O})
178 @Config(sdk = {ConfigConstants.SDK, Build.VERSION_CODES.O})
/packages/modules/AdServices/sdksandbox/tests/testutils/testscenario/example/
DREADME.md1 # SDK Sandbox Test Scenario Test Utilities Example
4 write tests inside a SDK Runtime.
/packages/modules/Connectivity/tests/cts/tethering/
DAndroid.bp54 // Tethering CTS tests that target the latest released SDK. These tests can be installed on release
82 // Tethering CTS tests for development and release. These tests always target the platform SDK
83 // version, and are subject to all the restrictions appropriate to that version. Before SDK
/packages/modules/Connectivity/tests/cts/net/
DAndroid.bp75 // Networking CTS tests for development and release. These tests always target the platform SDK
76 // version, and are subject to all the restrictions appropriate to that version. Before SDK
114 // Networking CTS tests that target the latest released SDK. These tests can be installed on release
/packages/services/Car/tests/carservice_unit_test/src/com/android/car/audio/
DFocusEntryTest.java50 private static final int SDK = 0; field in FocusEntryTest
139 AudioManager.AUDIOFOCUS_GAIN, LOSS_RECEIVED, flags, SDK); in getInfo()
/packages/modules/Connectivity/Tethering/tests/integration/
DAndroid.bp57 // Library including tethering integration tests targeting the latest stable SDK.
73 // Library including tethering integration tests targeting current development SDK.
/packages/services/Car/tools/watchdog/parser/
Ddeviceperformancestats.proto59 // Build.VERSION.SDK. The Android SDK supported in this build. E.g., "33"
/packages/modules/AdServices/shared/
DREADME.md5 - SDK Sandbox
/packages/apps/TV/tests/common/src/com/android/tv/testing/constants/
DConfigConstants.java25 public static final int SDK = Build.VERSION_CODES.M; field in ConfigConstants
/packages/modules/Bluetooth/android/pandora/server/
DREADME.md4 go/pandora-doc) over gRPC implemented on top of the Android Bluetooth SDK.
/packages/apps/ManagedProvisioning/studio-dev/development/sdk/
Dsdk.properties1 # SDK properties
/packages/apps/TV/common/tests/robotests/src/com/android/tv/common/util/
DContentUriUtilsTest.java31 @Config(sdk = ConfigConstants.SDK)

12345