This web page comprises info associated to Wear OS by Google.

2020-April-21 Wearable Help Library v2.6.0

Model 2.6.Zero of the Wearable Help Library consists of the next enchancment.

Migration to Android Jetpack

The Wearable Help Library has been migrated to Android Jetpack. Present libraries at the moment are mapped and accessible in AndroidX utilizing the androidx namespace, and all dependencies on the deprecated Help Library (android.help.* packages) have been eliminated.

This transformation additionally allows using the Wearable Help libraries in Android Studio 4.Zero and better, which resolves points like Problem #147972079.

2019-August-28 Wearable Help Library v2.5.0

Model 2.5.Zero of the Wearable Help Library consists of the next enchancment.

Repair for ComplicationDrawable when startActivity() is known as with TYPE_NO_PERMISSION complication kind

ComplicationDrawable now features a NEW_TASK flag that ensures that startActivity() calls that originate from a WatchFaceService embody FLAG_ACTIVITY_NEW_TASK to keep away from an android.util.AndroidRuntimeException.

This transformation permits the TYPE_NO_PERMISSION complication kind to correctly launch the permission request exercise relatively than crashing the watch face.

2018-September-25 Wearable SDK 16.0.0

Wearable SDK model 16.0.Zero lowers the required model of Google Play companies from model 12.Four to model 8.6. This transformation permits present apps to replace to the newest model of the Wearable SDK with out requiring an replace to the Google Play companies APK.

2018-June-11 Replace to Wear OS Developer Preview 2

A current over-the-air replace to the Wear OS Developer Preview 2 has re-enabled alarms and jobs for background apps.

Whereas this coverage change permits elevated flexibility in app improvement, background alarms and jobs proceed to be topic to different Android P restrictions, together with those that pertain to App Standby Buckets. Builders are suggested to observe the finest practices to make sure their apps behave effectively, whichever bucket the apps are in.

This replace additionally strengthens person enter and information privateness by limiting a background app’s entry to person enter and sensor information. Relying on an app’s necessities, builders may have to make use of a foreground service to allow continuous entry to sensor information.

2018-Could-8 Wear OS Developer Preview 2

Wear OS Developer Preview 2 has options comparable to an improved Google Assistant expertise.

Please submit any bugs or suggestions by way of the Wear OS by Google problem tracker. The sooner you submit them, the upper the chance that we are able to embody the fixes within the remaining launch.

Identified points

This part comprises recognized points for the Preview 2 launch.

Points for the Wear OS picture

  • If you end up in any app and also you press the ability button on the facet of the watch, chances are you’ll be returned to the earlier display relatively than to the watch face.

Points for the Wear OS for China picture

  • If you end up in any app and also you press the ability button on the facet of the watch, chances are you’ll be returned to the earlier display relatively than to the watch face.
  • Quantity-related sound settings should not continued. For instance, an incoming name leads to audible rings on the watch, even when the sound on the watch is ready to off. And in the event you alter the Alarm Quantity, the change has no impact.
  • A number of, on-going notifications could not show accurately. For instance, if each a timer and a stopwatch are set, notifications should not displayed. We suggest that you simply check your app with one on-going notification relatively than with multiple.
  • The Wear app retailer within the China model doesn’t work. Builders might be unable to replace or set up new apps by way of that channel. We suggest that builders use adb to side-load their software for testing, as a workaround.

Points for the Wear emulator

  • An incoming cellphone name to a companion cellphone isn’t proven (mirrored) as an incoming name within the paired emulator.
  • If you use the SDK supervisor to put in, or affirm that you’ve got, the newest set up of Android P or the China model, the checkboxes subsequent to these alternatives could develop into unselected after you choose (verify) them. In the event that they develop into unselected, please choose them a second time.
  • When the emulator performs a chilly boot, the next error could also be displayed: “There’s an inside drawback together with your machine. Contact the producer for particulars.” This doesn’t have an effect on performance. Scroll down and click on “OK” to start testing your app.
  • Voice reply could not work on the emulator. For instance, in the event you obtain a notification for a Google Hangouts message on the Wear emulator, and also you attempt to reply to the message by voice, a “Google retains stopping” error message happens and you might be prevented from replying by voice.
  • On the spot Run could also be incompatible with the Wear emulator.
  • Taking a screenshot programmatically comparable to by way of adb or by taking a bug report could not work. As a workaround, click on the digital camera button on the emulator toolbar to seize a screenshot.

Points for the China model of the Wear emulator

  • An incoming cellphone name to a companion cellphone will not be proven (mirrored) as an incoming name within the paired emulator. Accordingly, notifications of missed calls will not be proven within the emulator. Moreover, chances are you’ll be unable to reply a name from the emulator, and ringing of the decision will proceed.
  • If you use the SDK supervisor to put in, or affirm that you’ve got, the newest set up of Android P or the China model, the checkboxes subsequent to these alternatives could develop into unselected after you choose (verify) them. In the event that they develop into unselected, please choose them a second time.
  • When the emulator performs a chilly boot, the next error could also be displayed: “There’s an inside drawback together with your machine. Contact the producer for particulars.” This doesn’t have an effect on performance. Scroll down and click on “OK” to start testing your app.
  • On the spot Run could also be incompatible with the Wear emulator.
  • Taking a screenshot programmatically, comparable to by way of adb or by taking a bug report, could not work. As a workaround, click on the digital camera button on the emulator toolbar to seize a screenshot.

Google Assistant on Wear

Enhanced help for the Assistant on Wear OS lets you construct a wearable-ready expertise with out writing Android code. Particularly, you possibly can construct for the Actions on Google platform, serving to your customers get issues finished together with your services and products.

Moreover, Wear OS now permits quicker interactions by voice and contact. Additionally supported are suggestion chips, which do the next:

  • Assist customers full interactions shortly
  • Give customers hints about your Motion’s functionality

Furthermore, Wear OS now helps extra visible playing cards, in addition to lists and carousels.

Thus, you need to use DialogFlowTemplates or the Actions SDK to create Actions on Google for Wear OS. And you may reap the benefits of new response templates which can be particular to a watch. Greatest practices for Actions on Google embody:

  • Brief, concise dialog
  • Enabling each visible and vocal suggestions

These enhancements for the Assistant on Wear OS don’t depend upon Android P and are rolling out to all Wear 2.Zero customers. For an introduction to constructing Actions on Google, see Extending the Google Assistant.

Battery Financial savings in Developer Preview 2

As described beneath, power-related options can be found to extend battery life. The knowledge on this Developer Preview 2 part supersedes the power-related info for Developer Preview 1.

New mode: Enhanced battery saver

Whereas a watch is within the enhanced battery saver mode, a default power-optimised watch face is displayed. All the following are turned off:

  • Radios
  • The contact display
  • The lean to wake function

Customers can see the time by short-pressing the facet button. A protracted press permits the person to modify again to a fully-operational mode and carry out duties comparable to paying with NFC or replying to a message. Builders ought to assume that their apps, watch faces, and complication information suppliers are unavailable within the enhanced battery saver mode.

Restricted background exercise

To enhance energy, apps within the background are now not allowed to begin alarms and jobs except the watch is on the charger. Exceptions embody watch faces and energetic issues.

Be aware: In case your app should at all times run, e.g., for background monitoring, we suggest that you simply use a foreground service by utilizing the startForegroundService() methodology. See Background service limitations for extra particulars. Utilizing a foreground service presently is acceptable for distinctive use circumstances comparable to well being monitoring.

Improved app compatibility

As a way to enhance app compatibility, Android P has begun implementing sure restrictions on using non-SDK interfaces. It is best to make plans emigrate away from non-SDK strategies and fields. If no public equal is out there on your use case, please tell us.

Darkish UI system theme

For the reason that starting of 2018, Wear OS has switched to a default UI theme that has a darker background for the notifications stream and system launcher. This transformation is meant to enhance glanceability on your apps, and it’s best to verify your app’s accessibility with this new UI theme.

Up to date codelabs can be found

That can assist you discover essential methods to develop with Wear OS, up to date codelabs can be found. For instance, please strive the brand new Kotlin-based watch face codelab, through which we experiment with Kotlin DSL (Kotlin domain-specific language). When you’ve got any suggestions, please tell us.

2018-March-27 Wear OS Developer Preview 1

This part comprises details about Developer Preview 1 of Wear OS by Google. We count on to offer a number of updates to this preview earlier than the ultimate manufacturing launch. Please submit any bugs you discover by way of the Wear OS by Google problem tracker. The sooner you submit them, the upper the chance that we are able to embody the fixes within the remaining launch.

Identified points

  • Within the Wear OS companion app, tapping “Report wearable bug” will seem to work, however no bug report is definitely generated. We suggest utilizing adb bugreport as a workaround.
  • Accepting a cellphone name utilizing the watch doesn’t at all times succeed. If it doesn’t succeed, the person wants to simply accept the decision from the cellphone instantly.
  • A “Detected issues with API compatibility” error generally seems after pairing or launching a pre-loaded app. That error message disappears after a short while and doesn’t impression usability.
  • Within the Settings menu on the watch and within the emulator, the “Take bug report” possibility is displayed twice. To take a bug report, strive utilizing every of the 2 choices, as a result of just one is practical. If you faucet the practical possibility, a toast is displayed, exhibiting {that a} bug report is being generated.
  • Within the China model, voice enter causes an app to crash. This happens, for instance, with voice search or utilizing voice so as to add a reminder, as a result of this performance makes use of voice enter APIs. For testing, use keyboard or handwriting enter as a substitute of voice enter.
  • The Wear app retailer within the China model doesn’t work. Builders might be unable to replace or set up new apps by way of that channel. We suggest that builders use adb to side-load their software for testing, as a workaround.

Highlights on this developer preview

Developer Preview 1 consists of the next options for app testing:

  • Restricted background exercise: To enhance energy, apps within the background are now not allowed to make use of alarms and jobs. Exceptions embody watch faces and issues that the person has chosen. This function might be rolled out regularly within the developer previews, so chances are you’ll not see it instantly in your watch.

    Be aware: In case your app should at all times run, we suggest you modify it to make it a foreground service utilizing the startForegroundService() methodology. See Background service limitations for additional particulars.

  • Restrictions on apps’ use of non-SDK interfaces. To enhance app compatibility, Android P has begun implementing sure restrictions on using non-SDK interfaces. It is best to make plans emigrate away from non-SDK strategies and fields. If no public equal is out there on your use case, please tell us.
  • Darkish UI system theme. For the reason that starting of 2018, Wear OS has switched to a default UI theme that has a darker background for the notifications stream and system launcher. This transformation is meant to enhance glanceability on your apps, and it’s best to verify your app’s accessibility with this new UI theme.
  • Radios are off when the watch is off the physique: To enhance energy, the bluetooth radio, Wi-Fi radio, and mobile radio are off when the watch is detected as off the physique for an prolonged interval. This function might be rolled out regularly within the developer previews, so chances are you’ll not initially see it in your watch. If this function causes challenges in your improvement course of, you possibly can disable the function by way of adb utilizing the next command:
    adb shell settings put international off_body_radios_off_for_small_battery_enabled 0
  • Wi-Fi is off when BT is disconnected: To enhance energy, the watch will now not mechanically hook up with Wi-Fi when the watch is disconnected from bluetooth. Exceptions embody the case of an app requesting a excessive bandwidth community, and the case of the watch hooked up to a charger. This function might be rolled out regularly within the developer previews, so chances are you’ll not initially see it in your watch.

Updates to the Wearable Help Library, v2.3.0

The v2.3.Zero documentation replace for the Wearable Help Library consists of rebranding updates.

Moreover, v2.3.Zero of the library consists of updates associated to ComplicationDrawable and TextRenderer, for textual content that has markup objects hooked up to textual content ranges. These lessons have improved dealing with of Spanned texts. Solely a sure subset of spans are allowed to be rendered (see the setText methodology for the span varieties that may be drawn), so the spans don’t look out-of-place when rendered in a watch face.

2018-March-15 Rebrand of Wear

Date: 2018-March-15

This part comprises details about Wear OS options.

New identify for Android Wear

Android Wear has been renamed to Wear OS by Google.

2018-Feb-27 Ambient mode replace

Date: 2018-Feb-27

This part comprises details about new Android Wear options.

New class for supporting ambient mode

The 27.1.Zero model of the Android Help Library comprises a brand new class, AmbientModeSupport, which replaces the now-deprecated AmbientMode class. Updates to samples are deliberate in upcoming weeks.

2018-Jan-25 Closing emulator and extra

Date: 2018-Jan-25

This part comprises details about new Android Wear options.

Android Emulator: Replace for Wear

The ultimate Wear-related replace to the Android emulator is out there for testing apps primarily based on API model 26.

Enhancements within the Wearable Help Library, v2.2.0

The 2.2.Zero model of the Wearable Help Library consists of the updates described beneath.

A brand new unread notification indicator

As a result of customers need to concentrate on unread notifications, a brand new indicator is supplied: an encircled dot on the backside of the watch face. Mechanisms can be found in the event you favor to handle notifications by yourself. You need to use setHideNotificationIndicator to cover the default indicator while displaying your personal or setShowUnreadCountIndicator to show a notification rely within the standing bar.

Customise the colour of the outer ring of the unread notification indicator with the setAccentColor methodology.

For extra info, see Managing the unread notification indicator.

Enhancements to the ComplicationDrawable class

The ComplicationDrawable class begins a permission request for a watch face that’s tapped when the system signifies a price of TYPE_NO_PERMISSION (indicating that the watch face lacks permission to get the complication information).

Moreover, the ComplicationDrawable class invalidates itself when it finishes loading photographs or when a faucet spotlight expires. To reply to this invalidation (e.g., to redraw your watch face), add a Drawable.Callback.

Identified points

  • If you happen to activate Theater mode within the emulator (see Change display and brightness settings), the emulator can stay caught on Theater mode. Fixing the difficulty requires clearing the emulator information; see Run and cease an emulator, and clear information.
  • Inside the window of an emulator for API stage 25 or 26, the ability button doesn’t work. Subsequently, please use completely different buttons relatively than the ability button. Particularly, to modify to ambient mode (as if a person lined the display with their palm, for instance), use the ability button on the emulator device bar (to the suitable of the show). To begin the appliance launcher (in interactive mode), use the Dwelling (plain circle) button on the emulator device bar.
  • On the China model of the emulator, in the event you use the handwriting enter methodology, the display can start flashing. Then, once you click on the button for the on-screen keyboard, the keyboard blocks half the display.

2017-Dec-18 New entry to Google Play companies

This part comprises details about new Android Wear options.

Migrate away from the GoogleApiClient class

Beginning with model 11.8.0 of Google Play companies, Wear apps ought to migrate away from the GoogleApiClient class and as a substitute use API shopper objects which can be primarily based on the GoogleApi class, in addition to the Duties API.

For extra info, see:

New elements for connecting with Google Play companies

If you use lessons that stretch the GoogleApi class, comparable to DataClient and MessageClient, the Google Play companies SDK manages connections to Google Play companies for you; see the associated weblog posting. Apps that use these lessons now not have to create and handle GoogleApiClient objects.

For the replacements of Wear-related elements for connecting to Google Play companies, see Replacements for Deprecated Elements. For releases and recognized points associated to Google Play companies, see the Launch Notes for Google Play companies.

2017-Oct-25 Ambient mode and extra

This part comprises details about new Android Wear options.

Android Help Library, v27.0.0: Options and bugfixes

The 27.0.Zero model of the Android Help Library comprises new options for Wear, described beneath.

New, most popular option to help ambient mode

Ambient mode allows a Wear app to stay seen to a person when the machine goes idle. The Android Help Library has a brand new, most popular means on your apps to make use of ambient mode. The Wear staff seeks developer suggestions about this vital change.

Particularly, utilizing the AmbientMode class lets you profit from:

See Ambient Mode Utilizing the AmbientMode Class.

Manifest metadata constants within the Android Help Library

Constants for Android Wear apps, for the meta-data tag within the Android Manifest file, at the moment are out there within the Android Help Library. To make use of the constants (for standalone apps, notification bridging mode, and watch face preview photographs), add a reference to the next within the dependencies part of the app module’s construct.gradle file (requires the newest model of the Google Repository):

Motion drawer updates

Updates can be found to the WearableActionDrawerView class, which is used for making a wearable motion drawer. Within the newest model:

  • When menu gadgets are modified, the motion drawer is correctly up to date
  • If set for an motion drawer, the title is displayed accurately

Inflation of the RoundedDrawable class

Assuming an API stage of no less than 24, the RoundedDrawable class can now be inflated from a drawable XML file; see Customized drawables.

Wearable Help Library, v2.1.0: Enhancements and extra

The 2.1.Zero model of the Wearable Help Library consists of the updates described beneath and requires Android Help Library model 26.0.2 or increased.

Provide burn-in-safe photographs for ambient mode

The ComplicationDrawable class lets you provide burn-in-safe photographs for ambient mode. Particularly, a ComplicationData object’s burn-in safety small picture area allows a watch face to show a small picture (within the SMALL_IMAGE complication kind) in ambient mode, when burn-in safety is enabled.

Faucet occasion updates for issues

The ComplicationDrawable class has a brand new onTap methodology that permits your watch face to cross faucet occasions to issues. The brand new methodology builds on the prevailing performance through which a faucet on the watch face triggers the WatchFaceService.Engine.onTapCommand methodology.

You possibly can cross the coordinates to a ComplicationDrawable with an onTap name, to launch the motion related to the ComplicationDrawable that comprises the faucet coordinates. When the brand new onTap methodology is known as, you need to use a return worth of true to see if a ComplicationDrawable launched the motion related to it.

Moreover, the setHighlightDuration methodology units the period for a complication to stay highlighted after the onTap methodology is known as.

Progress bar for ranged worth issues

If you happen to favor to attract your personal progress bar for ranged worth issues in your watch face, chances are you’ll use the setRangedValueProgressHidden methodology of the ComplicationDrawable class to cover the ranged worth progress that’s drawn by the ComplicationDrawable.

2017-Oct-02 Android Wear beta

Date: 2017-Oct-02
Construct: OWP4.170828.008
Supported machine: LG Watch Sport

This part comprises recognized points for an Android Wear beta launch. For details about the beta program and/or to enroll, see the Android beta web page.

Identified points

  • Google Pay and its playing cards don’t operate with this Android Wear beta launch.
  • Even when mobile connectivity is on, it’s turned off after the beta is put in. As a workaround, activate mobile connectivity after the beta is put in by navigating to Settings > Connectivity > Mobile.
  • If notifications are erratic or lacking after a beta replace, or contacts weren’t synced, please factory-reset your watch.
  • Within the Wear tutorial (which begins after a watch is ready up), some playing cards behave erratically, however they are often dismissed usually (with a swipe).
  • On Android 6.0 (Marshmallow) telephones, cellphone name notifications should not acquired on the watch.
  • Coronary heart fee monitoring generally fails after an replace. As a workaround, reboot the watch.
  • The OTA card within the stream generally fails to allow an set up. As a workaround, navigate to Settings > System > About > System Updates.
>