Hello. I'm try to using scrollAway for moving timetext with scalingLazyColumn. I used wear-compose 1.1.2, so I still used scrollAway modifier extension. I think there are cases where scrollAway doesn't work as intended. In logic, the

yPx

value is obtained with

-it.Offset

, Using this yPx value, progress is measured by

(scrollParams.yPx / maxScrollOut.toPx()).coerceIn(0f, 1f)

. Since coerceIn is used here, if the offset of the initial value is a positive number, yPx becomes a negative number, and progress returns 0f by coerceIn, so timetext is displayed normally while the screen has just been drawn. However, the problem is when the index 1 item's offset is a negative number. If the initial offset is negative, yPx will be positive, and

positive yPx / maxScrollOut.toPx()

is performed, it will return something greater than 0. In other words, timeText is already moved to the top while the screen has just been drawn, so I cannot see the timetext. From experience, it seems that the above issue occurs when

index 1 item

is very short height and located at the top. In this case, To make

scrollAway

work normally, and to make timeText move when the item with index1 moves, what is the best way? I thinks select index 2 or 3 item, which is returns the positive offset, and apply the offset between the index 2 or 3 item and item 1 to scrollAway? Or is there something I'm missing?

Hi, can anyone please help me know, how to fulfil this Wear App Quality guideline. I am able to show the scroll bars while scrolling, but on entering the page it is not visible. My main parent composable is the MediaPlayerScaffold from the Horologist sample app.

Hi, I got that warning on my androidmanifest for all wear os activities 'set taskAffinity for wear activities to make them appear correctly in recents' is there for information about this?

Hi, I want to be able to display fullscreen notification to display to the user when he reaches a km while running. I noticed that Samsung does it with their app. I haven't found how they do it maybe you have more information about it. On mobile, you can by adding a fullscreenIntent to a notification but that doesn't seems to work on wear. Apparently it was possible to add an extend to a notification with a WearableExtender() but that has been removed on wear os 2.0 and doesn't do anything anymore. Was it replaced by something?

in Samsung, can we start an activity like healthKit’s? https://developer.apple.com/documentation/healthkit/hkworkoutactivitytype. I’m trying to demo a similar feature, which is to start a workout and automatically turn on the app watch, then track heart rate. In Iphone, there is a watch application from watch it records data. Is there a similar app in Samsung?

Your mobile app can send a message on the Wearable Data Layer, or with the RemoteIntentHelper to start the app on Wear. That can launch to the foreground and start a foreground service. It's similar to how Auth flows across paired devices works.

Hi, is there an equivalent of onRotaryScrollEvent for a pager? Like if you move the rotary input you jump to the next item

Compose for Wear OS 1.3.0-alpha02 was released last week. As announced in the previous release, we have updated Chip and ToggleChip to adjust their height to accommodate content that has grown due to large fonts for accessibility. The release also included new features in expandables (a new way to generate ExpandableStates) and also a new parameter on SwipeDismissableNavHost that allows turning off swipe gesture handling. Further, we have migrated SwipeToDismissBox from Material to Foundation. See release notes for more details. Also, we have released 1.0.0-alpha08 of the wear.compose.compose-material3 library - this adds selection controls (switch, checkbox, radio button), ListHeader and round toggle buttons to our Material3 components - see release notes. The release candidate for Compose for Wear OS 1.2 was also released.

Hi, is it possible to remove that restriction? I have a common module between my wear os app and my mobile application. This imply that I can't release the wearos app anymore. Or does that mean that I have to keep my app at 33 and wait for wear os to support 34 before updating my mobile app?

This message contains interactive elements.

The team are happy to announce that the Compose for Wear OS 1.2.0 stable version was released yesterday. In addition, 1.3.0-alpha03 was released, with an update to Placeholder to allow resetting so that the placeholder is shown again if the content is no longer in the ready state; and introducing experimental SwipeToRevealCard and SwipeToRevealChip components in Material to make it easier to implement swipe-to-reveal. We also continue to add to our Material3 library of components, with the addition of ToggleButton in the release of 1.0.0-alpha09.

I am testing my wear app on Wear OS 4 Preview ARM 33 Image Rev 2. From the AppOps system process, i receive constantly error

attributionTag  not declared in manifest of <http://my.package.com|my.package.com>

, anyone also see this? and what is this about?

Hello, I'm having issues with Dialog and Alert composable. No matter what I try, Dialog is not in 100% size, there is like 1% of pixels visible from composable which was used to initiate Dialog. Also, in Alert, I'm not able to turn off shadow around screen. It also works somehow wrongly. Is this because I use some wrong library? Anyone faced similar issue?

Hello, shouldn't the new

androidx.wear:wear-tooling-preview

library be in the

androidx.wear.compose

group instead?

id 'kotlin-parcelize'

Plugin [id: 'kotlin-parcelize'] was not found in any of the following sources:

Can’t use kotlin-parcelize for WearOS?

Hello, how can i vibrate watch? Tried to use VibrateManager, but it’s ignored.

I just found out that I can connect Android 34 emulator with Wear OS 33 emulator on M1 Mac, and the virtual Heart Rate sensor works. I can test my Companion App for upcoming Android and Wear OS release with virtual sensor end-to-end. It is like a dream came true. JOB well done !!!!! My best thanks to all the hard working people to make this happen. I would like to shake your hands all day long.

Hello, Is there any way to prevent this behavior when large font size is set in system settings? I'm using default Chip / ToggleChip composables.

They fixed the annoying visibility bug in the Wearable SDK version 18.1.0 https://developer.android.com/wear/releases/

FINALLY!!!!

Weird it's not mentioned in the release notes though.

I can see some preparation to allow switching the phone without resetting the watch also, that's nice, I've wanted that since Android Wear 1.x 🙏🏼

Compose for Wear OS 1.3.0-alpha05 was released last week, fixing a bug in the Swipe to Reveal components so that only one item at a time can be swiped - please see release notes for more details. Also, we have released 1.0.0-alpha11 of the wear.compose.compose-material3 library with updates to typography for cards and list header - see release notes.

Regarding Swipe-to-Reveal, I am using it as a way of saving an item. I would then like the item to bounce back into its original position. How could I do that? I'll put my code in the thread.

Hello, may I ask where is the right place to discuss Watch Face Format issues? https://developer.android.com/training/wearables/wff I just created first watch face using new WFF declarative xml and while it works great on real watches, it does not work on API 33 emulator. Throws some syntactic value error. Because of this, I'm not able to publish app as Google app review team is most probably using API 33 emulator for testing so I'm always getting irrelevant rejections.

@yschimke hi, which is the last horologist version that uses all stable compose libs version? 0.4.13 ?

@yschimke i have a pagerscreen with 4 pages, 3 of those have a scaling lazy column. I manually implemented 3 differents column state to maintain the scroll state, but i have a focus problem. In particular, when i switch page with an horizontal swipe, the elements in the page are tappable only after a vertical scroll. Do you know a way to request the focus after the page selection? I will provide you a repro, if needed, thanks :)

BackHandler

does not catch backs via swiping (in

SwipeDismissableNavHost

), as it does in mobile side. Now I need to do some arrengements onBackHandler, how could I do this in wear OS?

Now that the new Wear OS guidelines are in effect, I'm getting a reject because the scroll bar does not appear on entering a screen with a list (it only appears on scroll). That is a good requirement, however how do I make sure that this is the case when using ScalingLazyColumn (inside a Scaffold)? I don't see an option in PositionIndicator either.

Compose for Wear OS 1.3.0-alpha06 was released last week, including support for Modifier.edgeSwipeToDismiss with Swipe-to-Reveal - please see release notes for more details. Also, we have released 1.0.0-alpha12 of the wear.compose.compose-material3 library with updates to color classes for selection controls - see release notes.