Lines Matching refs:SDK

19 …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.
50  - If you are using a sysui-studio checkout, it will always pull the SDK from the attached device.
51  - If you are using a platform checkout which you've never built, it will pull the SDK from the
53  - If you are using a platform checkout which you've built with `m`, it will use the SDK from the
54    out/ directory. However, in this scenario, if you wanted to use the SDK from the attached device
81 Android Studio shouldn't ask you to choose which Android SDK to use and will instead select the
82 right SDK automatically. But, [if it does ask](https://screenshot.googleplex.com/AtA62tTRyKWiSWg),
83 choose the **project** SDK (likely in the `.../<branchname>/prebuilts/fullsdk-linux` directory),
84 **not** the Android SDK (likely in the `.../<username>/Android/Sdk` directory).
203 Setting up SDK from scratch