Samsung Galaxy S5 - Issue selecting DropDown items.

[gORGUTS]

Device - Samsung Galaxy S5
Seems that I have to multi-tap several times to end up with a successful selection or to find that the DropDown closes.

[dessant]

Only that device or android in general? What is your kivy version?

Could you share a minimal app example which shows the issue?

[gORGUTS]

Saw issue with Kivy Showcase installed today (2/25/2016). Originally saw from Electrum 2.6 Android beta version. They had me test with the showcase and I got the same results. I tried 2 galaxy s5's, Android Ver 5.1.1 - Kivy Showcase - 1.9.1.0

[CodePi]

I have the same issue with the Galaxy Note 4. Android 5.1.1. Kivy 1.9.1.

[jojomike]

I do not know if this is helpful:

• Samsung Galaxy S4, Android 5.0.1, works most of the time
• Samsung Tab A 9.7, Android 5.0.2, works most of the time, but worse than S4
• Samsung Tab S 10.5, Android 5.0.2, worse than Tab A
• Samsung Galaxy S6, Android 5.1.1, does not work most of the time

(Kivy 1.9.1 Android with Kivy Launcher, and Kivy Showcase from Play Store, too).

A race condition dependant on CPU speed or similar?

Maybe related to: #3805

[coeps]

I got the same issue (I think) on a Samsung s III.
Kivy 1.9.1. Create an Spinner on the PC, works with left mousebutton, deploy it as apk -> Spinner ends up: I need to tab it with two fingers simultaneously to get the selection . If I use two fingers with this widget, everything seems to work as expected.

[kived]

This happens on the Note 5 as well. It's likely due to the high DPI/density of these screens - maybe we're not detecting these settings appropriately, or maybe it's an issue with jitter as @akshayaurora suggested on #kivy-dev. I've notice the same in other, non-Kivy, apps as well - for example Assassin's Creed Unity companion app. Anything that scrolls in that app is almost impossible to select.

[jojomike]

(*) But - kivy 1.9.0 does not have this problem (my workaround is to use 1.9.0).

The TAB A has 1024x768 pixels, for a tablet a rather low DPI - same problem with 1.9.1, not so bad, but exists.

(*) Meanwhile after much touches on all my devices (see above) I think, 1.8.0 and 1.9.0 are having the same? problem, too - albeit very rarely, but not only DropDown. It seems to me reproducing and debugging is not so simple.

[FilipDem]

See also #3805.
Is there any workaround available? This problem blocks me deploying the app on the GooglePlay. Going back to 1.9.0 is difficult because I use the "below_target' from the softinput_mode that is added in 1.9.1.

[FilipDem]

Can somebody help on this topic? Is there any solution upcoming?

[inclement]

Have you tried with kivy master? I'm not sure if there was some activity about this.

[FilipDem]

Yes I did... Makes no change...
Seems this is already longtime slipping. I see this in various issues.
F

On 27-05-16 23:57, Alexander Taylor wrote:

Have you tried with kivy master? I'm not sure if there was some
activity about this.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#4031 (comment), or
mute the thread
https://github.com/notifications/unsubscribe/APcjC64b7nE00VkpHdw5c5jvAsGl4Degks5qF2i-gaJpZM4Hi1uW.

[jsaddiction]

I am experiencing the same issue on my galaxy S7 Edge. Originally thought my code was the root cause of the issue. This bug report describes my problem to the T. Is there any workaround or solutions other than moving to the dev branch?

[melassa]

Same problem here on Spinner on LG G3 Android, kivy 1.9.1, python 2.7.

[souliane]

Same problem for me with Galaxy s3 and s7, both on Android 6.0.1. It is very difficult to click, most of the time it feels like if there's no callback to the buttons. Is there something to do like tuning the sensitivity or could it only be solved with a proper fix? Thanks.

[lordOfThePits]

Samsung Galaxy Note 4 and Samsung Galaxy Tab 10.1, same issue, spinner selection not working (or very sluggish) once being pressed. It does respond once it's pressed several times, but then it sometimes comes with wrong respond. Works slightly better on Galaxy Tab then on Note 4. Kivy 1.9.1, Python 3.5.2

[whendonkiesfly]

Has anyone tried Kivy 1.10.0 and looked for this issue? I no longer have it on my LG G2.

[DavidAPease]

I am running Kivy 1.10.0. I have two kivy apps that work perfectly on my ZTE Axon 7 (2560x1440 screen), running Android 6.0.1. Installed both apps on my wife's Samsung Galaxy S6 (also 2560x1440 screen) running Android 7.0, and have this exact problem. I have also seen this on Galaxy Tab S2. It seems to be (mostly) Samsung devices, and it seems to have been going on to over two years, on various versions of Kivy.