Plexamp Android: Touch Ripple causes dropped frames on some views

  • Plexamp 3.4.5
  • Pixel 4a

The new update visually looks very nice! The native font and touch ripple on Android really makes plexamp feel like a native app.
However, on certain views I noticed that if you scroll a list with your finger the touch ripple will cause the scroll to drop frames.

This is most apparent on the Library > Artists view however it can be seen in other screens as well.
If you look on an Album’s detail page you do NOT see the lag, so one can reason this lag may not be directly attributed to the touch ripple.

If you carefully scroll the Artist’s view such that your finger immediately triggers a scroll when it hits the screen this will not trigger the lag (nor will it trigger the touch ripple) and the list will not lag.

Regardless of the lag or not, it would be nice to slightly increase the delay for which the touch ripple gets triggered. If you use some Google apps you might notice the touch ripple is delayed just enough that it doesn’t get triggered when a user is leisurely scrolling.

However, if the lag around the touch ripple can be removed from the few views that induce the lag I think the ripple would be much less jarring when scrolling though plexamp.

Interesting feedback, thanks! By any chance do you have Blurred Action Bar enabled, and if you disable it, does it make a difference?

Unfortunately, there is no way I can see to delay the ripple…

Hello Elan,

I did some more testing.
The Blurred Action bar I dont believe has a bearing on this behavior. I can see the lag in the same areas in the UI even with it disabled. I can also see the lag in areas the Action bar is not present such as the Album Details page.

I have since updated to Android 12 Beta 1, and this gives me interesting findings.
The touch ripple does not appear in some parts of plexamp, and as such the lag is not there.

On android 12 there is one example, the Album Detail view, the ‘popular tracks’ section does have the touch ripple on it’s list items specifically.
I can trigger the lag on Android 12 from the ‘popular tracks’ section.

I had a facepalm moment as I have been trying to screen record this lag but it seems the framebuffer for the recording does not demonstrate the lag at all. You can only see it with the naked eye.

You’re on an Android beta, but … still.

I think it’s probably best to just disable the ripple effect for now. It’s not a huge net positive and it seems like there’s at least some downside.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.