Tolriq

@DevSrSouza bump. This will be an issue for shared transitions and predictive back.

Hum thanks will test next week. But no half the doc is without data class for the screens and the doc explains that the params needs to be serializable or...

I actually just took your code from the other thread without changes (except adding more levels to ensure it triggers all the time).

Ok so hashcode and equals to avoid future issues. Thanks for the update.

Back to voyager 1.0 RC6 and I'm facing this too. I'm logging the key in an AndroidScreen and it's properly restored after activity kill. But `rememberSaveable` by default does not...

Bump

I'm deeper in the hierarchy and using Compose 1.5 but basically I'm having AndroidScreen in different modules. Like : ``` class ProviderLocalDeviceAddScreen : AndroidScreen() { override val key: ScreenKey get()...

Ok so I did more tests and seems the issue is about FadeTransition @DevSrSouza ```FadeTransition(navigator)``` to ```navigator.lastItem.Content()``` fix this. (But I'd love to have transitions :)

@yschimke the 100 000$ question is about the battery usage of BT vs wifi, in the doc you suggest no BT for more that 1 Mb. But is there any...

Well in my case the need is to transfert large amount of data from the phone to the watch in the most efficient way possible battery wise. Speed would be...