You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I guess the app is just slow in loading the conversation list. How many conversations do you have? Long-press one of them and see the number at the top-left of the screen.
No, it's definitely not slow, it's drawing a nice animation where the list gradually expands from top to bottom. It looks a bit like a flip/unfolding of a book page, but vertically.
😁 yes it doesn't look bad at all, I just like it when its faster.
However, its only the list of messages where this animation is, all other screens / elements work without animation (like going to specific chat, going to settings, etc), it must be something about drawing this list .
I have disabled animations in Accessibility settings as having Developer options on conflicts with some banking apps.
I couldn't come up with anything better and gave this to Gemini and here is what it said:
That animation is an app-level RecyclerView layout animation (typically managed via a LayoutAnimationController or a custom XML animation resource) applied specifically to the conversation list when it populates.
Why it ignores your disabled system animations
Android’s system-wide animation toggles (found in Developer Options or Accessibility settings) control global animation scales, window transitions, and standard ValueAnimator-based animations.However, layout animations applied directly to a RecyclerView or view group via an app's local code run independently. Because the Fossify Messages app explicitly triggers this layout animation when loading the conversation list—and doesn't check if global animations are disabled (such as checking ValueAnimator.areAnimatorsEnabled() or the system animator duration scale)—the animation plays regardless of your accessibility settings.
What to tell the Fossify team on GitHub
To help antodc and the other contributors track down the exact cause for your bug report, you can reply to the issue with this technical summary:
"The animation is a hardcoded RecyclerView layout animation (using a LayoutAnimationController) triggered when the conversation list adapter populates. Because it's handled locally by the app's view logic rather than standard system transitions, it completely bypasses the system's accessibility/animation-off settings. The app should ideally check if system animations are disabled (e.g., via ValueAnimator.areAnimatorsEnabled() or checking global animator scales) and skip applying the layout animation controller when disabled."
Activity
antodc commentedon Aug 31, 2026
I guess the app is just slow in loading the conversation list. How many conversations do you have? Long-press one of them and see the number at the top-left of the screen.
summer-son commentedon Aug 31, 2026
No, it's definitely not slow, it's drawing a nice animation where the list gradually expands from top to bottom. It looks a bit like a flip/unfolding of a book page, but vertically.
antodc commentedon Aug 31, 2026
Wow! It should be nice (sorry!).
Have you disabled the animations from the developer options?
summer-son commentedon Aug 31, 2026
😁 yes it doesn't look bad at all, I just like it when its faster.
However, its only the list of messages where this animation is, all other screens / elements work without animation (like going to specific chat, going to settings, etc), it must be something about drawing this list .
I have disabled animations in Accessibility settings as having Developer options on conflicts with some banking apps.
antodc commentedon Aug 31, 2026
Last thing that comes to my mind is to close the app, clear the cache, and open the app again. If you did not try that yet. Good luck!
summer-son commentedon Aug 31, 2026
I couldn't come up with anything better and gave this to Gemini and here is what it said:
That animation is an app-level RecyclerView layout animation (typically managed via a LayoutAnimationController or a custom XML animation resource) applied specifically to the conversation list when it populates.
Why it ignores your disabled system animations
Android’s system-wide animation toggles (found in Developer Options or Accessibility settings) control global animation scales, window transitions, and standard ValueAnimator-based animations.However, layout animations applied directly to a RecyclerView or view group via an app's local code run independently. Because the Fossify Messages app explicitly triggers this layout animation when loading the conversation list—and doesn't check if global animations are disabled (such as checking ValueAnimator.areAnimatorsEnabled() or the system animator duration scale)—the animation plays regardless of your accessibility settings.
What to tell the Fossify team on GitHub
To help antodc and the other contributors track down the exact cause for your bug report, you can reply to the issue with this technical summary:
"The animation is a hardcoded RecyclerView layout animation (using a LayoutAnimationController) triggered when the conversation list adapter populates. Because it's handled locally by the app's view logic rather than standard system transitions, it completely bypasses the system's accessibility/animation-off settings. The app should ideally check if system animations are disabled (e.g., via ValueAnimator.areAnimatorsEnabled() or checking global animator scales) and skip applying the layout animation controller when disabled."