在 SDK Platforms 标签页中,点击 Show Package Details,然后展开包含 API 级别 35-ext15 工件的 Android 15.0(“VanillaIceCream”)部分。然后,选择 Wear OS 5.1 ARM 64 v8a System Image 或 Wear OS 5.1 Intel x86_64 Atom System Image:
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["没有我需要的信息","missingTheInformationINeed","thumb-down"],["太复杂/步骤太多","tooComplicatedTooManySteps","thumb-down"],["内容需要更新","outOfDate","thumb-down"],["翻译问题","translationIssue","thumb-down"],["示例/代码问题","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-07-27。"],[],[],null,["# Wear OS 5.1\n\nExplore the latest version of Wear OS, available on select devices and in the\nofficial emulator in Android Studio. Check that your app runs as expected after\nyou [update your target SDK version](#update-target-sdk-version).\n\nWear OS 5.1 is based on Android 15 (API level 35), which requires you to test\nyour apps that already target API level 34 for Wear OS 5.\n\nPrepare a supported device for testing\n--------------------------------------\n\nWear OS 5.1 can run on the following devices:\n\n- Google Pixel Watch 3\n- Google Pixel Watch 2\n- Google Pixel Watch\n\nYour device should receive an over-the-air (OTA) software update. You can also\nmanually update your device by doing one of the following:\n\n- From the **Settings** app, navigate to **System \\\u003e System updates**.\n- After you [enable developer options](/training/wearables/get-started/debugging#enable-dev-options), flash a specific software image onto devices that support a USB (wired) data connection. For example, you can flash a [factory image](https://developers.google.com/android/images-watch) or a [full OTA image](https://developers.google.com/android/ota-watch).\n\nPrepare the emulator for testing\n--------------------------------\n\nTo run Wear OS 5.1 in the official emulator, you must first download and install\nthe system image that runs on the emulator. You must then create a virtual\ndevice that runs this system image.\n\n### Download and install the system image\n\nTo download and install the correct system image, complete the following steps:\n\n1. Download and install the latest release of [Android Studio Ladybug Feature Drop](/studio) or later if you haven't done so already.\n2. In Android Studio, click **Tools \\\u003e SDK Manager**.\n3. In the **SDK Platforms tab** , click **Show Package Details** and expand the\n **Android 15.0 (\"VanillaIceCream\")** section that contains artifacts for\n API level 35-ext15. Then, select either\n **Wear OS 5.1 ARM 64 v8a System Image** or\n **Wear OS 5.1 Intel x86_64 Atom System Image**:\n\n4. Click **OK** . When the **Confirm Change** window appears, click **OK**\n again.\n\n5. Wait for Android Studio to download and install the system image, and then\n click **Finish**.\n\n### Create a virtual device\n\nTo create a virtual device that runs this system image in the official emulator,\ncomplete these steps:\n\n1. In Android Studio, open the Device Manager by selecting **Tools \\\u003e Device\n Manager** . The **Device Manager** pane appears.\n2. In the toolbar within the **Device Manager** pane, click **Add a new\n device** **\\\u003e Create Virtual Device**.\n3. In the **Form Factor** pane, select **Wear OS** and choose a hardware profile. Click **Next**.\n4. Select a Wear OS 5.1 system image to use. The system image should have an **API Level** of **35**.\n5. Click **Next** , and then click **Finish**.\n\nTest your app on the emulator\n-----------------------------\n\nTo test your app on this virtual device that you've created, complete the\nfollowing steps:\n\n1. Go to the Android Studio toolbar and select the virtual device.\n2. Click **Run** .\n3. Install your app on the virtual device and navigate through the different user-facing workflows that your app uses.\n\n### Changes that affect all apps\n\nAs you test your app on Wear OS 5.1, check to see how your app handles the\nsystem [behavior changes that affect all apps in Android 15](/about/versions/15/behavior-changes-all), which uses the\nsame API level as Wear OS 5.1.\n\nSeveral behavior changes don't take effect in Wear OS 5.1:\n\n- [Private spaces](/about/versions/15/behavior-changes-all#private-space-changes) aren't supported in Wear OS 5.1.\n- [Predictive back animations](/about/versions/15/behavior-changes-all#predictive-back) might not appear.\n\nUpdate your app's target SDK version\n------------------------------------\n\nYou can improve your app's compatibility with Wear OS 5.1 by updating your app's\ntarget SDK version to API level 35. (This is the same API level that\n[Android 15](#update-target-sdk-version) uses.)\n\nTo do so, open your module-level `build.gradle` or\n`build.gradle.kts` file, and update them with values for Wear OS 5.1.\n\nHow you format the values in your build file depends on the version of the\nAndroid Gradle plugin (AGP) that you are using.\n\n### AGP 7.0.0 or higher\n\nIf you are using AGP 7.0.0 or higher, update your app's `build.gradle` or\n`build.gradle.kts` file with the following values for Wear OS 5.1: \n\n### Groovy\n\n```groovy\nandroid {\n compileSdk 35\n ...\n defaultConfig {\n targetSdk 35\n }\n}\n```\n\n### Kotlin\n\n```kotlin\nandroid {\n compileSdk = 35\n ...\n defaultConfig {\n targetSdk = 35\n }\n}\n```\n\n### AGP 4.2.0 or lower\n\nIf you are using AGP 4.2.0 or lower, update your app's `build.gradle` or\n`build.gradle.kts` file with the following values for Wear OS 5.1: \n\n### Groovy\n\n```groovy\nandroid {\n compileSdkVersion \"35\"\n ...\n defaultConfig {\n targetSdkVersion \"35\"\n }\n}\n```\n\n### Kotlin\n\n```kotlin\nandroid {\n compileSdkVersion = \"35\"\n ...\n defaultConfig {\n targetSdkVersion = \"35\"\n }\n}\n```\n\n### Changes that only affect apps targeting API level 35\n\nAfter you update your target SDK version to API level 35, handle the [changes\nfor apps that target Android 15](/about/versions/15/behavior-changes-15), which uses the same API level as\nWear OS 5.1.\n\nExplore new features\n--------------------\n\nWear OS 5.1 introduces several features to help enhance your Wear OS app\nexperience.\n| **Note:** Before you add these features to your app, prepare your app for handling the behavior changes that Wear OS 5.1 introduces.\n\nNotable features to explore include the following:\n\n- **Credential manager support:** The Credential Manager API provides a unified authentication solution, supporting sign-in flows using passwords, [passkeys](/design/ui/mobile/guides/patterns/passkeys), and federated identity (such as [Sign In with Google](https://developers.google.com/identity/gsi/web/guides/overview)). A user's credentials are stored in a credential provider, which syncs account information across devices.\n- **Watch speaker playback:** On devices that support media playback through the watch speaker, users can select this speaker as their preferred media output option if your app integrates with the [Wear Output Switcher](/training/wearables/apps/audio#let-user-choose).\n\nRelease notes\n-------------\n\nThe latest system image for Wear OS 5.1, which is available on supported devices\nand on the emulator, has the following characteristics:\n\n|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| **Release date** | March 18, 2025 for Google Pixel Watch 3 LTE, Google Pixel Watch 2 LTE, and Google Pixel Watch (both Bluetooth/Wi-Fi and LTE) March 4, 2025 for Google Pixel Watch 3 Bluetooth/Wi-Fi and Google Pixel Watch 2 Bluetooth/Wi-Fi |\n| **Build** | BP1A.250305.019.W3 on Google Pixel Watch 3 and Google Pixel Watch 2 BP1A.250305.019.W2 on Google Pixel Watch AP4A.241205.004.F4 on emulator |\n| **Emulator support** | x86 (64-bit), ARM (v8-A) |\n\n### Known issues\n\nThe system image that contains Wear OS 5.1 has the following known issues:\n\n- The emulator doesn't always allow the user to add an account during the setup flow following a device reset.\n- When tapping on a notification, the app that sent the notification doesn't open until the user scrolls the screen.\n- Wear Health Services sometimes fails to start an exercise.\n- If you access the [`androidx.wear.tiles`](/jetpack/androidx/releases/wear-tiles) or [`androidx.wear:wear-phone-interactions`](/jetpack/androidx/releases/wear#wear-phone-interactions-1.1.0-alpha05) libraries within an app that targets API level 35, a [`SecurityException`](/reference/java/lang/SecurityException) might occur. To resolve this issue, upgrade to [`androidx.wear.tiles` 1.5.0-alpha05](/jetpack/androidx/releases/wear-tiles#1.5.0-alpha05) or later, or [`androidx.wear:wear-phone-interactions` 1.1.0](/jetpack/androidx/releases/wear#wear-phone-interactions-1.1.0) or later."]]