Hi,
I have an tap gesture issue with some controls on my samsung device (Galaxy A17 5G), especially CollectionView, Toolbar and probably others controls as well.
For example, when I select one or multiple items in the CollectionView, the tap gesture is not recognized properly and "works" randomly or not at all.
I tried with the Telerik.NET MAUI Controls app on Google Play Store and reproduce the issue on it (collectionview and toolbar).
When I use the sample app (or my app) with Vysor (screen mirroring), it works fine when I click on the items (using mouse) but it doesn't work when I tap on the item directly on the device.
It works fine on android emulator and on my other devices (Google Pixel 6a, 9a)
Environment (my app):
- Telerik UI for .NET Maui: 12.0.0
- NET Maui: 9.0.110
Device :
- Product name: Samsung Galaxy A15 5G (SM-A176B/DS)
- Android version: 16
- One UI version: 8
- Knox version: 3.12 (api lvl 39)
Has anyone else encountered this issue?
Thanks,
Franck

on some samsung devices running android 16, users have to tap items in the collectionview multiple times and it'll only work sometimes. scrolling etc all works fine. tapping on those items does not reliably work, and the success ratio is very small. the linked feedback issue from Didi doesn't seem like it is exactly the same thing. I have not got multiple gestures attached to collectionview items. The only thing we're doing is reacting to the item selection, which doesn't seem to be happening.
Hi Luis,
The behavior seems the same as the one we have logged here: https://feedback.telerik.com/maui/1675393-collectionview-android-swipe-and-tap-gestures-sensitivity-on-some-samsung-devices
It seems the issue is an issue in the Samsung phones and related to the sensitivity of the display. There are reports of similar behavior at the following link: https://www.reddit.com/r/GalaxyS22/comments/tdo1m8/swipe_when_i_tap/ which explains the issue outside of the usage of Telerik controls.
Based on the research from our side so far, the issue happens on occasion, sometimes depending on the tap (when placing bigger part of the finger on the screen) the device sends data as if there is a motion which is normally interpreted as a swipe. I am afraid, at this time, there isn't a workaround for the behavior.