If you are using Horologist's

fadeAway

modifier. It's being replaced by scrollAway temporarily, and this will be coming in Wear Compose 1.1. The design has changed also for Column and LazyList, so it also fades away. Previously it was just scrolling (like

Modifier.offset

) https://github.com/google/horologist/pull/669/files

Paparazzi 1.1 now has support for 3 Wear devices. It will render automatically with round time text (isScreenRound = true) for 2 of them, and crop screenshots in a circle. https://twitter.com/yschimke/status/1580429572067463168

I tried to rewrite the

WatchFaceConfig

class from the

WatchFaceKotlin

example using compose-wear, (https://github.com/yingding/wear-os-examples/blob/main/Wear3KtxWatchFaceConfigExam[…]xample/watchfaceconfigexample/editor/WatchFaceConfigActivity.kt), So far everything works fine, except adding the onClick events to setComplication on top of the WatchFace Bitmap generated from EditorSession. In the original example, two Button views are vaguely put to the whole viewports. How can i do this in compose wear in a more accurate way? It would be nice to have a

EditorSession.renderWatchFaceToComposable(...) ->  (@Composable()()->Unit)

function to allow me specify the onClick events. Any thoughts on this matter?

It's here!!!!

ScalingLazyColumn

is incredibly, mind blowingly, fascinatingly… extremely laggy, even in release builds… 😕 You don't even get 10fps! How is that possible? I tested on the Pixel Watch and the Samsung Galaxy Watch 4. Is Google using these in their apps with some tricks, or is Google using only View APIs? Here's my code:

import androidx.wear.compose.foundation.CurvedLayout
import androidx.wear.compose.material.AutoCenteringParams
import androidx.wear.compose.material.Icon
import androidx.wear.compose.material.ScalingLazyColumn
import androidx.wear.compose.material.Text
import androidx.wear.compose.material.ToggleChip
import androidx.wear.compose.material.ToggleChipDefaults
import androidx.wear.compose.material.curvedText
import androidx.wear.compose.material.rememberScalingLazyListState


@Composable
fun SomeScreenContent() {
    ScalingLazyColumn(
        Modifier.fillMaxSize(),
        state = listSate,
        autoCentering = AutoCenteringParams(itemIndex = 0),
    ) {
        items(20) {
            ToggleChip(
                checked = false,
                onCheckedChange = { isChecked -> },
                label = {
                    Text("Some setting")
                },
                toggleControl = {
                    Icon(
                        imageVector = ToggleChipDefaults.switchIcon(checked = false),
                        contentDescription = "setting disabled"
                    )
                }
            )
        }
    }
}

Is anyone make base profile with wear os? My app is currently developed with only compose. Scrolling is slow right after running the app, and the speed improves after a certain period of time. If I run the app again after killing the process on the watch, it is slow for a while, and the scroll speed improves after a certain period of time. Can this case also be considered a JIT issue like the thread below? https://kotlinlang.slack.com/archives/C02GBABJUAF/p1655128462622249 I also read about under thread. but my app is already speed-profile. [status=speed-profile] [reason=install] https://kotlinlang.slack.com/archives/C02GBABJUAF/p1665931379289959 I'm trying to proactively add a base profiler into my app. I finished all the settings with base profile code-lab, but I found that "gradle managed device" is not available on the watch. It seems that I have no choice but to root my test device or use an emulator, is there any problem with the improvement effect of the base profiler even if I make base profiler with watch emulator? Also make baseProfile on watch emulator is extreamly slow. I waiting 7 hours but it still PROGRESSING. Currently I give up about processing and retry make baseprofile on next morning. @yschimke How did you create baseline-prof.txt on under commit? Please advise me. https://github.com/android/wear-os-samples/pull/572/files

The team are pleased to announce that Compose for Wear OS 1.1.0-beta01 has been released. Release notes can be found here. More details in the thread.

Hi, is the wear os swimming sample from Monday keynote available somewhere? Thanks!

Starting to mock up the wear version of our app rewrite for real 🙂

It’s kinda exciting 🙂

It’s also a fun challenge trying to translate over a mobile consumer oriented design language to the wrist, but so far I’m liking what I see 😄

The onClick of CompactChip has stopped working after I upgraded to

Wear Compose 1.1.0-beta01

and

compose 1.3.0

. Is there an example how to define CompactChip and make it clickable?

CompactChip(
    modifier = modifier.padding(top = 8.dp),
    onClick = onClick,
    label = {
        Text(
            text = stringResource(R.string.click_me),
            maxLines = 1,
            overflow = TextOverflow.Ellipsis
        )
    }
)

Hi does wear os support app bundle? I doesn't look like it right? Like you put your app and your wear os app in the same app bundle and the Google play manage the distribution of it to the correct channels

Hi it is me again 😁! About the ambient, is it managed by compose automatically? It is probably the case right otherwise you would mention it on the doc and there will be a local provider for it, right?

I couldn't find just a 'wear' channel so trying here, is there a way to catch exceptions like this from within the wear communication layer? This is the top crash in our watch app that seems to have started/spiked about a month ago:

Exception e4.b: 20: The connection to Google Play services was lost due to service disconnection.
  at com.google.android.gms.common.internal.ApiExceptionUtil.fromStatus (ApiExceptionUtil.java)
  at com.google.android.gms.common.internal.zap.zaa (zap.java)
  at com.google.android.gms.common.internal.zar.onComplete (zar.java)
  at com.google.android.gms.common.api.internal.BasePendingResult.zab (BasePendingResult.java)
  at com.google.android.gms.common.api.internal.BasePendingResult.setResult (BasePendingResult.java)
  at com.google.android.gms.common.api.internal.BasePendingResult.forceFailureUnlessReady (BasePendingResult.java)
  at com.google.android.gms.common.api.internal.zav.zaa (zav.java)
  at com.google.android.gms.common.api.internal.zav.zaa (zav.java)
  at com.google.android.gms.common.api.internal.GoogleApiManager$zaa.zaa (GoogleApiManager.java)
  at com.google.android.gms.common.api.internal.GoogleApiManager$zaa.onConnectionSuspended (GoogleApiManager.java)
  at com.google.android.gms.common.internal.zag.onConnectionSuspended (zag.java)
  at com.google.android.gms.common.internal.BaseGmsClient$zzb.handleMessage (BaseGmsClient.java)
  at android.os.Handler.dispatchMessage (Handler.java:106)
  at android.os.Looper.loop (Looper.java:246)
  at android.os.HandlerThread.run (HandlerThread.java:67)

Hello everyone i have been reading about compose but i cant understand how to implemente user input, anyone can provide som info please

Hi all, i’ve run into a strange bug in ScalingLazyColumn on Wear OS When I use a long Text inside of ScalingLazyColumn and launch the app the bottom of the Text gets the focus, instead of the beginning. Here’s detailed description of a problem with a code snippet https://stackoverflow.com/questions/74384254/bug-in-default-behavior-of-scalinglazycolumn-jetpack-compose-wear-os Any idea how to fix it? Feel free to respond in this thread or on Stack Overflow. In my opinion, it should be the default behavior to focus on the beginning of the first element, focusing on the bottom of the first element makes no sense, hence I feel like it’s a bug

ScalingLazyListState defaults to the center of the second item (index 1). You can tell it to instead start in the first item and even jn the ScalingLazyColumn parameters use the start of items.

Compose for Wear OS 1.1.0-rc01 was released on Wed 9th. It includes updated baseline profiles and a number of bug fixes in preparation for the upcoming 1.1.0 final release. See the release notes for details

Hi all 👋 Does anyone know if there is a plan to make a BOM (Bill of Materials) for wear compose artefacts like they introduced for Compose in October (https://android-developers.googleblog.com/2022/10/whats-new-in-jetpack-compose.html)? 🙂 If yes, will that then include the artefacts that compose has or would you need to use the compose BOM as well? Just curious 🙂

Hello, i have two projects in compose one for Wear and one for Mobile, i want to sync and share data between them, how can i perform it? Thanks in advance

Google published a playlist of the new Dev Summit, it has a quite a few videos that show how to architect and design apps on Wear OS with Jetpack Compose, I recommend to check it out https://www.youtube.com/playlist?list=PLWz5rJ2EKKc9jBnpl83LH6oZc7nFIVSRq

Hey @Odin, nice PR for the SquareSegmentedProgressIndicator. Paparazzi screenshot tests, Android Studio previews with animation. https://github.com/google/horologist/pull/695

This isn't a compose question (I know I know) BUT I wanted to ask if using the data client on the watch could potentially be a big battery drain ? I have an app sending data every second

Hi, is there an up-to-date tutorial for a simple connection between a mobile phone and a watch? I only want to send a

String

. I have tried to follow the DataLayer code in the wear-os-samples, but it is a bit complicated for my level... 🤔

Hello, if anyone wants/needs to use

RecyclerView

or

WearableRecyclerView

in a

@Composable

function, you need to hack around to get rotary input to work. If any of you need that, let me know, I will share my code in a gist or in an open source library. BTW, does anyone know how to have something like

ScalingLazyColumn

but with

RecyclerView

? Basically, I'm looking for the same effect as in the Settings app and in the App Drawer from the Pixel Watch.

Hey everyone 👋 . In the latest Horologist release (0.2.3) we added support for rotary with haptics 🎉. We added 3 modifiers :

rotaryWithScroll

,

rotaryWithFling

and

rotaryWithSnap

.

rotaryWithScroll

- a modifier when only scroll is required

rotaryWithFling

- scrolling with flinging. Supports any scrollableState

rotaryWithSnap

- scrolling with snapping. For now supports only ScalingLazyColumn ( Picker and Pager will be supported as well later ) All modifiers support haptics out of the box, which can be switched off if necessary.

What is the wear os app lifecycle? Like when does an app go into start/resume/pause/stop ? If it's only OS driven, is there a way to trigger this manually ?

A silly question, I want to use bluetooth debugging with pixel watch. But can’t find the debugging over bluetooth in android pixel watch app. Is this possible?