Taps not always recognized on device, often have to double tap

Hi all!

I've got a pretty simple setup in my menus where if:

User clicks with left button object -> Jump to Frame

I also have tried multi-touch:

If new touch has started on object -> Jump to Frame

Both of them seem to act the same way. My problem is, ALMOST ALWAYS I have to double tap to get it to register my tap and perform the action. I set up a counter because I thought maybe I was dealing with a lag issue with the jump, but the counter is saying it's not registering my tap so it can't be that. It's like I never tapped it.

I've noticed this for a long time now and have always just assumed it was my device, or my cold fingers.. but started hearing from others they are experiencing the same thing. On this new game I'm creating I'm noticing it being especially bad. It's affecting some of the game play because you have to be quick with some taps and if it doesn't register the first time you tap it can be frustrating.

Am I doing this all wrong? Even the simple menus I have issues with and have to double tap or keep tap multiple times to get it to register. Multi-touch doesn't seem to change it unless I'm doing that all wrong too. Anybody have any advice?

Thank you so much!

Well after I posted this, I think it was my test device! I found another device laying around and uploaded the APK to that and it works perfectly fine on there. So who knows, it's something with that one I think!

Hey, it could be worthwhile to try 'while mouse key is being pressed' + 'only once when event loop' instead of 'user clicks' to see if that fixes it for the faulty device.

Thanks Popcorn, I'll give it a shot :)

I'm also experiencing the problems with taps not registering correctly. I'm however only having issues with one of my test-devices: a Samsung Galaxy S3.

The problem seem to have appeared in the update of Fusion 288?

My version on Google Play Store is built with the Beta release of Fusion 287.5. It works correctly.
In my latest build from version 288.3. The bug is present.

Bump- I'm having the exact same problem here. Half of the taps are not recognized my samsung Galaxy Tab 3.11 (Android 4.2.2) but they do work properly on my phone (Android 4.4).

Changing from "User clicks with left button" to "Repeat while left mouse-key is pressed + Only one action when event loops" does not make a difference. I'm hoping this gets fixed soon.

Is it a good idea to reinstall an older version until the bug gets fixed or will the MFA files not be compatible?

you need to post a small mfa for test here.

I am testing from 4.4.2 to 6 with n problem, so an example is very good to see .

I made this small test application with some different methods just to see exactly where it fails

Attachment 22671
Attachment 22672

Using single touches each time.
On frame 1 (User clicks) if the taps are done too quickly in succession, some of the taps are not recognized.
On frame 2 (User clicks, framerate to 10FPS) the effect is the same, unaltered by the frame rate change.
On frame 3 (Repeat while left mouse key+only one action) it seems to work fine (except of course when more than one touch is used at the same time)

Frame 4 uses the multi touch extension (A new touch has occurred->Set position to X(last touch) and Y(last touch)) seems to work perfectly.
Finally frame 5 uses touch 0 (Touch 0 is active+only one action) and it works pretty much the same as frame 3.

Frame 1 is the issue here (Not all "User clicks with left button" trigger events are recognized. They did work before, but now after I updated to the last version and rebuilt some of my applications, without modifying a thing, suddenly half of the taps are not recognized.)

My problem is my entire game is coded using "User clicks" trigger events and kind of a rough job right now to think of a workaround because of this bug; so I'm hoping it's something that can be solved in a less exhaustive way than manually editing a lot of events throughout all the application just because some taps are not recognized on some devices. I mean i'd do it without any further notice if it happened the same in all devices, but knowing it happens in only some devices, whereas it works perfectly on others, I felt the need to add to this).

---

Alright, sorry- As I was typing this I noticed the "User clicks with left button" thing where half of the taps are not recognized also happens on my phone so that's not the problem we're talking about.

I'm just gonna post my game's menu frame (stripped down, removed extensions and some events). The problem occurs throughout all the application; and the app uses pretty much all kinds of click events (repeat+only one, user clicks, touch occurred) even though this menu frame uses only "Repeat while mouse key pressed".

I have just now noticed (on my samsung tablet, where the bug occurs) that if I do a "soft" touch (?) and then move the finger around, the program does not even recognize that touch at all; not even while moving it.
But if I touch with another finger, without releasing the first one (which was not detected), it also doesn't recognize the second one, so it's like the first touch is registered but it's being ignored or something.

Attachment 22673
Attachment 22674

Try tapping the buttons or dragging around, the buttons should be lit when the touch is over them (The darkening effect is not the frame resetting, it's just a full-screen active.)

I cannot compile this MFA with an earlier version of fusion so I cannot properly verify it's an issue with the newest update; but I'd appreciate if someone could build it with an APK with an older version to test if taps work properly.

Again for emphasis, it works perfectly on half of my devices (All single touches are recognized properly), but on some devices some taps are ignored.

Ah also, sorry for extending ^^;

could it be this is happening when you start or when the screen does not have the focus and the first touch is used by OS to gain the touch control? (in the device 4.2.x)

Don't think it's related to focus, unless the application somehow loses focus every two seconds even while I'm quick-firing taps?
In-between that quickfire, 1 out of 7 taps is ignored (I'm tapping at a rate of 4 clicks per second approximately). It does happen, though, no matter how slowly I tap, or wherever I tap.

It does happen consistently on the first touch though.

Also... apparently If I tap every 3 seconds, no taps are recognized at all. I'm gonna try on my other device where the bug is present too, to see if this happens consistently too.

EDIT:
Yep, same behaviour on this other phone. Android 4.3.
My 11' samsung tablet has Android 4.2.2

And again, no issues on my own phone; (all taps registered) which has android 4.4.

Dunno if the android version has anything to do with it but it's easier to differentiate devices this way.

I have tried your test app (sometimes_clicks.apk) on my test phone and it's working properly. The phone is a ZTE v4.4.4 model N9130.
I can softly touch on a button and it's working, I can drag my finger around, works too by registering the click/overlap.

Alright, I've enabled developer options in android and enabled Pointer location (Draws a trail where the touches are going and draws axes) and Touch locations (white circle at touch locations). Don't know what the options are called in english so I apologize if I got the names wrong.

And it's weird because while the application is running, the white circles appear at all times, but whenever the touch is not being registered, the trail does not show up (Even tho the white circles are there).
I wish I could record a video of it but Jelly bean does not seem to support native video capture.

It's very weird because this doesn't happen in any other application or anywhere else on my tablet-
I hope I can find someone else with the bug so I can verify it's not just that half of my stuff decided to have the same problem. :s

EDIT:
Ok, apparently, locking and unlocking the tablet fixes it for me until I close the application and open it again.
Oh well at least that's a workaround I can work with for now haha

mm but that seem that you may need to reset your device something can be corrupted

(Thanks a lot for the support btw, much appreciated ^^)

Reset as in restart the device? Or reset as in doing a factory reset?
Because I have restarted it multiple times and there was no change... Also I'm not doing a factory restore on it. I wouldn't want to force anyone who runs into the same problem to factory reset their phones just because some taps are not recognized haha. Keep in mind that two completely different devices have the same issue, and it'd be very rare to think both tablet and phone have suffered the same kind of corruption; they don't even have the same apps installed or share brands or anything.

Anyway, locking and unlocking seems to consistently work for now.


EDIT:
For the sake of completeness, I've compiled the same thing in an older version of CF25+Android Exporter (I have R280 on my notebook, didn't have the chance to update) and I can confirm the bug is not present there.

Here's the APK, version r280.28; where the bug is not present
Attachment 22683

Here's the same thing, compiled with the newest updates, r288.3, where the bug is present
Attachment 22681
Attachment 22682

No changes to the MFA

try to collect a logcat from application to see is I can see any warning inside it.

Quote:

---

Originally Posted by elPatrixF

Also... apparently If I tap every 3 seconds, no taps are recognized at all. I'm gonna try on my other device where the bug is present too, to see if this happens consistently too.

EDIT:
Yep, same behaviour on this other phone. Android 4.3.
My 11' samsung tablet has Android 4.2.2

---

I have got the same behavior here on my Samsung Tablet, 7' (SM-T110), Android 4.2.2.
The first tap in 2 seconds is not detected. Locking and unlock the device does not work for me.

The app works fine on my phone, Android 6.0.1

I built with Google API 16 and API 24, with the same result.

Attachment 22722
Attachment 22723

Is it possible to downgrade my Clickteam Fusion to make the app work properly on my tablet?

Looking forward for a fix.

OK, here's something possibly related. I'm using basic mouse events instead of multi-touch. Whenever a second finger finds it's way onto the screen, the next tap isn't detected. This is on a fire phone. I'm going to use multi-touch anyway, but maybe it's something somewhat related to this issue.

I tried "mouse click on object" event and the multi-tocuch object. I got the exact same behavior on both...

please can all post the android specification for theses devices.

Samsung SM-T110, 7''
Android ver. 4.2.2
Kernel version 3.4.5-2751957
Compilation number JDQ39.T110XXUAN17