Assigned
Status Update
No update yet.
Comments
ra...@google.com
Can you attach / share a project that reproduces the issue?
th...@gmail.com
Now i sure this is viewpager2's bug.
because just occur recyclerview inside viewpager2 with constraintlayout, if paging3 use Independently with viewpage2 it's not problem.
because just occur recyclerview inside viewpager2 with constraintlayout, if paging3 use Independently with viewpage2 it's not problem.
th...@gmail.com
deleted
ra...@google.com
al...@google.com
th...@gmail.com
Hi,
Apparently Samsung Watch 4 is now targeted with the same update.
This is rapidly increasing the number of users complaining about this issue.
Did you make any progress on this problem ? Or is it pure Samsung problem with Wear OS intergration?
Thank you for any feedback / update.
Apparently Samsung Watch 4 is now targeted with the same update.
This is rapidly increasing the number of users complaining about this issue.
Did you make any progress on this problem ? Or is it pure Samsung problem with Wear OS intergration?
Thank you for any feedback / update.
an...@google.com
It seems like a Samsung issue, we have reached out to the Samsung folks about the same.
an...@google.com
Samsung replied back that they are aware about the issue and mentioned that the fix is included in their Oct MR.
an...@google.com
Let us know if you still face the issues after Samsung's Oct MR.
th...@gmail.com
Hi team,
I want to give you feedback about the latest samsung update.
Samsung Watch 6 was targeted with a new build (Version R930XXU1AWH4), which improved many things.
But unfortunately, the complication initialization issue after a reboot is not fixed, and is still a problem.
This issue is highly impacting the ratings of play store applications for watch faces developers
Do you have any informations about their fix and when it would be released?
Thank you
I want to give you feedback about the latest samsung update.
Samsung Watch 6 was targeted with a new build (Version R930XXU1AWH4), which improved many things.
But unfortunately, the complication initialization issue after a reboot is not fixed, and is still a problem.
This issue is highly impacting the ratings of play store applications for watch faces developers
Do you have any informations about their fix and when it would be released?
Thank you
th...@gmail.com
th...@gmail.com
Problem seems to be fixed on firmware WK4 (rolling out on SGW6 for now).
Let's hope that it will be available on SGW4 and SGW5 soon.
Let's hope that it will be available on SGW4 and SGW5 soon.
Description
This issue affects all the Samsung Galaxy Watch 6, and recently the Samsung Galaxy Watch 5 as they were targeted with the same os update:
OneUI 5.0
Google Play Services 23.33.16
Wear OS 4.0
Wear Service 1.8.1.536969553
This issue affects all the "developed" watch faces (to be opposed to watch faces created with WFS), and can be reproduced on watch faces developed with java wear api, or kotlin wear api.
When setting up a watch face with complication (like steps, agenda etc..), and then reboot the watch : When boot is completed, onComplicationDataUpdate is not sent anymore.
As a result, complications are not updated.
The only work around is to switch to another watch face, and then to switch back to the first one.
This has been reproduced on various watch faces:
And on the Watch Face sample.
It looks like the first watch face is not correctly initialized after a reboot.