Items are continiously animating their positions when scrolling (Modifier.animateItemPlacement) [209947592]

Fixed

Bug

Status Update

No update yet.

Description

zo...@gmail.com

created issue #1

Dec 9, 2021 03:17PM

I adopted Modifier.animateItemPlacement in my project, and while it has worked well overall, Ive received 1 report (with video) about lags - from what I can tell, the items are just continiously animating their positions while the person is scrolling, even though their positions are unchanged, and they have stable keys.

This happens on a Pixel 5 running on Android 12.

Box(
modifier = modifier.conditional(
condition = animated && !sticky && actualKey != null,
modifier = {
Modifier.animateItemPlacement(
animationSpec = OffsetSpec
)
}
),
content = {
content()
}
)

Comments

ma...@google.com <ma...@google.com> Dec 9, 2021 03:39PM

Reassigned to an...@google.com.

an...@google.com <an...@google.com> #2Dec 9, 2021 03:45PM

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

Android build
Which Android build are you using? (e.g. PPP5.180610.010)

Device used -- Device Make, Model, Android OS Version
Which device did you use to reproduce this issue? Are you also using 2 phones: Pixel 4 with Android 10 and Sony Xperia L3?

Steps to reproduce
What steps are needed to reproduce this issue?

Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:

https://developer.android.com/studio/debug/bug-report#bugreportdevice

Screen record of the issue, if possible
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue.

Note: Please avoid uploading directly to the issue using attachments. Please upload to google drive and share the folder to android-bugreport@google.com, then share the link here.

zo...@gmail.com <zo...@gmail.com> #3Dec 9, 2021 04:40PM

It's bug in you Bluetooth stack. It's not depend on any build system. I point exact line in code where bug happen. Please stop use blueprint response. This problem happened even in system applications. Current happened on Pixel 6 device whit last march update. Also this bug present in gabeldorsche Bluetooth stack here we also hard-code only 1M phy for scanning

zo...@gmail.com <zo...@gmail.com> #4Dec 9, 2021 05:32PM

We’ve shared this with our product and engineering teams and will continue to provide updates as more information becomes available.

screen-20211130-103803.mp4

6.4 MB

Download

an...@google.com <an...@google.com> #5Dec 9, 2021 05:54PM

I can confirm that fixing this code allow scan on Coded PHY.

I rebuild system with this changes and now i see coded phy device

zo...@gmail.com <zo...@gmail.com> #6Dec 10, 2021 05:34AM

Can anyone give on update on this bug ?

an...@google.com <an...@google.com> #7Dec 10, 2021 02:07PM

Could the assignee of the ticket update us on the status. This is an useful feature to a number of users as well as developers. It being inoperable for such a long time since its release casts a shadow on the reliability of Pixel phones and demonstrates certain lack of support.

zo...@gmail.com <zo...@gmail.com> #8Dec 10, 2021 02:47PM

Hi, is there any update on this ticket?

an...@google.com <an...@google.com> #9Dec 10, 2021 02:54PM

Hello vi...@gmail.com (Assignee)- can you give an update please ?

an...@google.com <an...@google.com> #10Dec 10, 2021 02:56PM

Any update? This is terrible

zo...@gmail.com <zo...@gmail.com> #11Dec 10, 2021 03:08PM

Our engineering team is still working on this issue. We will provide more updates as they become available.

zo...@gmail.com <zo...@gmail.com> #12Dec 14, 2021 10:00AM

"Our engineering team is still working on this issue. We will provide more updates as they become available." - thank you

an...@google.com <an...@google.com> #13Dec 14, 2021 01:18PM

Hi,
Is there any update on this issue?
We see that there is fix already available ->

https://android-review.googlesource.com/c/platform/packages/modules/Bluetooth/+/2054032/2
Could you please get this patch merged.

zo...@gmail.com <zo...@gmail.com> #14Dec 14, 2021 02:22PM

Hello,

I second that "na...@qualcomm.corp-partner.google.com" #13.

Will this show up in Android 14 today ?

so...@gmail.com <so...@gmail.com> #15Dec 25, 2021 02:37PM

How can I fixed this issue on my Android 10 and 11?

WordTeacher_lazylist_animation_on_scrolling_problem.webm

6.3 MB

Download

jo...@onsalesit.com <jo...@onsalesit.com> #16Feb 3, 2022 02:23PM

Hello,
are there any updates regarding this bug/feature ?
I've been waiting for quite a while ;-)
Regards, Paul

an...@google.com <an...@google.com> #17Jun 1, 2022 03:38PM

Looks like this was finally addressed here, and will make it into the next Android release:

-

https://android-review.googlesource.com/c/platform/packages/modules/Bluetooth/+/2942289
-

https://android-review.googlesource.com/c/platform/packages/modules/Bluetooth/+/3013872

ap...@google.com <ap...@google.com> #18Sep 27, 2022 05:34PM

Marked as fixed.

Hello,
I have been testing Android 14 on a pixel 6 - this still is not working.
The fix seems to be reverted - is that correct ?
Or... will the fix get into Android 15 ?
Many thx, Paul

na...@google.com <na...@google.com> #19Oct 5, 2022 05:15PM

I find this a big problem. Phones where it worked fine. Now it doesn't. Please when will a fix be available?