Hi, is there anything wrong with using a broadcast receiver to communicate between phone and watch? I see that there is a type of workaround in the DataLayer code in the Wear OS samples. Is using a BR considered bad practice?

Using the DataLayer code in the Wear OS samples, I am getting this warning:

This method should only be accessed from tests or within private scope

Should I just ignore it?

I've discussed the wear os baseline profile here a while ago, so I'd like to share the results of applying it to my product. In my case, since scrolling was slow right after the app was turned on, so I considered applying baseline profile. Since rooting is required to create a baseline profile on a real wear device, I was created baseline profile on AVD. After that, the produced baseline-profile.txt was applied to the real device and the performance test was conducted. StartupBenchmark_None timeToInitialDisplayMs. min 1259.9, median 1355.6, max 1401.2 StartupBenchmark_Partial timeToInitialDisplayMs min 928.6, median 954.6, max 982.5 ScrollBenchmark_None frameDurationCpuMs P50 12.9, P90 34.0, P95 66.9, P99 388.8 ScrollBenchmark_Partial frameDurationCpuMs P50 12.5, P90 28.7, P95 51.8, P99 156.2 It helped improve the overall speed at start-up, and helped improve the bad case of p90 or higher at scroll. Since production and application can be done separately, if you do not want rooting, it is best way to make baseline-profile with AVD.

Am I the only that gets a questionably looking button by default with Wear Compose? The padding is missing. I'm quite confused at why this would be the default and what is the correct thing to do since on Material 3 for phones, it just looks correct with the right inner padding applied.

Hi, I am using Horologist (v0.2.3) libraries for my media app, I am facing a issue that whenever I click on the media notification on my watch the MainActivity gets recreated, I also tried using the Horologist sample app and the same thing happens there as well (MediaActivity gets recreated on notification click), I want to just resume the app if is in background on clicking the media notification, and recreate the activity only if app is not already in background. Does anyone have some idea how can I achieve this behaviour, or am I missing out something ?

Hello Team, I am developing a KIOSK Mode stand alone application for Wear OS(Samsung Watch 4, Wear OS 3.5). For KIOSK mode I am using device owner permission using ADB and used device DevicePolicyManager class to handle hardware button and status bar etc. My Issue is, I am not able to open System WIFI settings which navigate to outside of KIOSK mode. Just for your information I can open system bluetooth settings without disabling KIOSK mode. 1 more information case 3 code work perfectly if your KIOSK mode is disable I tried:- Case1. context.startActivity(Intent("com.google.android.clockwork.settings.connectivity.wifi.ADD_NETWORK_SETTINGS")) Case 2. val intent = Intent(Settings.ACTION_WIFI_SETTINGS) intent.flags = Intent.FLAG_ACTIVITY_NEW_TASK intent.addCategory(Intent.CATEGORY_LAUNCHER) startActivity(intent) Case 3. startActivity(Intent(Settings.ACTION_WIFI_SETTINGS)) If any one have any idea or workaround. Much appreciate your inputs!

A quick wear os 3 health service related question: I intend to design a service for my health app to collect heart rate data 24/7 using PassiveListenerService from a TileService. Will this work? There are a lot of background service restrictions on Galaxy Watch and Pixel Watch, the only service running 24/7 on Wear 2 is the watchface service, can tile service also survive the energy optimisation? I noticed that the pixel watch is constantly measuring heart rate data, can i retrieve the heart rate data retrospectively ?

I have a problem with navigation. It is working perfectly on my Wear OS emulator but crashing on my Pixel watch. I would love it if someone could please help! 😊 Details in thread.

I just enabled USB debugging on my Google Pixel Watch and wanted to connect it to my laptop to deploy a sample wear OS app but I'm unable to get them to pair. I used the adb command (enabled Debug over Wifi) using the watch's IP and the 'Pair Devices using Wi-fi' flow from Android Studio but to no avail. Am I missing any key steps?

Has anyone tried to display a QR code using wear OS? I'm just trying to show a regular png with a QR code in a sample app and I'm just seeing a white screen (I played around with the dimensions of the resource but to no avail)

The Compose for Wear OS team are excited to announce that version 1.1.0 stable has been released. The latest release includes a number of bug fixes and minor UX tidy ups as well as some improvements to the Experimental placeholder UI. Additionally we have released the first 1.2.0 alpha release which adds new functionality for

HierarchicalFocusCoordination

as well as accessibility improvements for the

Picker

- see the release notes for more details.

Hi, I am trying to open the mobile app from the wear app, is there any documentation or tutorial for the same? Thanks!

Hi, about bedtime on wear os, is there an API to switch the watch to bedtime mode? I had a look on the internet but there doesn't seem to have any documentation about it. Thanks!

Hi, i got some design idea to implement an activity chooser with compose wear. It may be done with a ScalingLazyColumn, and i will need an overlay over it to add optional nav button. Can you give me some suggestions how to implement such overlay with compose wear? or is there any other way to achieve this design?

Rotary input. I would also include pointer input and move based on which half of the screen the user taps

I would like to use a Hilt ViewModel in my ListenerService in order to save some info that is coming from the mobile to the watch into a Room Database. I know how to use a Hilt ViewModel in a Composable, but is it possible to use one in a ListenerService, and if so, how would I need to instantiate it?

The

NavGraphBuilder.scalingLazyColumnComposable

is deprecated in

horologist==0.2.5

, i shall use the

listComposable

@Deprecated(
    "Use listComposable"
)
public fun NavGraphBuilder.scalingLazyColumnComposable(

In the nav example,

NavGraphBuilder.scrollable

has replaced

NavGraphBuilder.scalingLazyColumnComposable

, what is the difference between

listComposable

and

scrollable

? The only

listComposable

which I can found in

NavGraphBuilder

is

lazyListComposable

.

Is it possible to define different height for the items in ScalingLazyColumn? I have a head element, which shall have only the half height of the rest items. My SLC sets by default all items to the same height.

I am using a Listener Service to insert some data from the phone to the watch into a room database. Is it possible for my watch app's UI to update itself without having to reload it once new data is inserted? Or would I need to use a broadcastReceiver to notify the UI that it needs to recompose?

Hi team, I would like to suggest

IconButton

in

androidx.wear.compose.material

, just noticed that I shall not use

androidx.compose.material

with compose wear. As I wrapped Icon in a Button, it attaches a shadow. How can I get ride of this shadow from the

Button

?

I applied

horizontalScroll

modifier to the

androidx.wear.compose.material.dialog.Alert

and got an

IllegalArgumentException

It appears to me,

horizontalScroll

modifier applied on the parent composable of a

ScalingLazyColumn

will raise the IllegalArgumentException, what is the reason for that?

Hi, just wondering if this bug fix has also been propagated to compose wear: https://android-review.googlesource.com/c/platform/frameworks/support/+/2307790. I am having problems with the

PullRefreshIndicator

getting stuck halfway down the screen. Any ideas?

how to get information wears os is watch shape is square or rounded in jetpack compose ui

wear os timetext align to right default it is center align how to fixed this issue please help me

The swipe back gesture of the

horologist.WearNavScaffold

intercepts the drag gesture intended for a

AndroidView

composable. Is it possible to disable the swipe back gesture on a

NavGraphBuilder.scrollable

temporarily?

Hi everyone, I hope you had a nice Christmas break! Just to confirm my assumption, this doesn't work at all right? https://developer.android.com/training/wearables/user-input/physical-buttons. I have also tried with

BackHandler

but both the emulator back button and swipe to go back doesn't trigger anything

I added a deepLink to

NavGraphBuilder.scrollable

, called the deepLink with a PendingIntent from complication, and got

java.lang.IllegalArgumentException: The WearNavigator backstack is empty, there is no navigation destination to display.

Is this normal?

Compose for Wear OS 1.2.0-alpha02 was released on Wed 11th Jan. It includes bug fixes and accessibility improvements for Picker and a bug fix Placeholder so that state updates if the onContentReady lambda is updated. See the release notes for details.

I would like to implement an

exercise timer

feature with compose wear that user can start and stop the exercise. Is there any example for this? What are the options and recommendations on wear? App Widgets, Tiles, Music App like Always on App? Horologist or Glance? Thanks for any hints.