question

The issue doesn't affect the HDX 8.9" or original 7" Kindle Fire either. To be clear, what I meant above is that when holding one finger down on the screen and tapping with a second finger, the touch down and touch up events are occasionally missed. Also there isn't a clear relationship between how rapidly I tap, sometimes tapping slowly does not generate the events.

Hi Andre, Can you please provide a sample code to demonstrate that how you are measuring the touch down events in the native code? Also, it would be helpful if you could write up for building apk around your native code. Before going to respective team with the issue I need to present it in a sample app. Thanks for reporting this.

We were able to reproduce the problem while using this multitouch test app from the Amazon store: http://www.amazon.com/Developer-Multitouch-Test/dp/B004TSGBQ6/ref=sr_1_1?s=mobile-apps&ie=UTF8&qid=1390216310&sr=1-1&keywords=multitouch+test In our racing game we log all the received touch events and the action type. What we are seeing is that touch down events are sometimes not received while holding one finger down on the screen and tapping with a second finger. I cannot share our source code but the issue would be easily reproducible using a multitouch test app. If not then our device may be faulty, we have only tested this on one 8.9" Kindle Fire HD. Thank you for your help.

Hi, we got hold of a second Kindle Fire HD 8.9" and was able to reproduce this. So it wasn't that the particular device we were testing on was faulty. I noticed a message spammed in logcat after all touch events during debugging, unsure if it is relevant though: channel ' (client)' ~ Failed to receive dispatch signal. status=-11. Thank you for your help.

Hi Andre, I tested the "Multitouch Test" in our end in Kindle HD 8.9 and unable to reproduce any issue with multi touch as you said. The OS version of my device is 8.4.6_user_4620220. Can you please confirm the OS version of your device? I can see your app is in progress state in developer portal. Can you please upload the binary so that I can test it?

OS version 8.4.6. This is my personal account, not my client's, and so I cannot upload an .apk now. However I will request this. I have seen this issue on two devices running this version straight after rebooting each device. Here is how I reproduce the issue in the racing app and the "multitouch test app": 1) Place the Kindle Fire HD 8.9" flat on a desk 2) Place and hold your left index finger on the lower left side of the screen (creates a blue touch circle id0=0) and hold it still 3) Repeatedly tap your right index on the lower right side of the screen. This will usually create a red touch circle id1=1, but sometimes no touch will be detected. Moving either finger on the screen at all will cause the second touch circle to appear. Like my client's app, the multitouch test app does not exhibit the issue on the Kindle Fire HDX 7" OS 13.3.1.0.

Clarification: when both fingers are pressed to the screen but the second "red touch circle" is not shown (i.e. the touch was not detected), moving either finger at all (triggering more motion events), causes both circles to display as expected. Also, thank you once again for your help.

I am seeing exactly the same behavior as Andre in both my custom app and in the Multitouch Test app. I am testing on a Kindle Fire HD 8.9" (2nd gen) with OS 8.4.6_user_4620220. I don't have another Kindle to test on but I have tried it on a couple other Android tablets and have not been able to reproduce the issue.

Here is some sample code that I can use to reproduce the issue. It's printing to a TextView on the main activity but you could just as well write to System.out. If I hold down with one finger and then tap with a second finger, I see that event.getPointerCount() is sometimes 1 and sometimes 2. @Override public View onCreateView(LayoutInflater inflater, ViewGroup container, Bundle savedInstanceState) { View rootView = inflater.inflate(R.layout.fragment_main, container, false); final TextView textView = (TextView)rootView.findViewById(R.id.MyTextView); View.OnTouchListener touchListener = new View.OnTouchListener() { @Override public boolean onTouch(View v, MotionEvent event) { String result = "PointerCount=" + event.getPointerCount() + ", Action=" + eventActionToString(event.getAction()); textView.setText(result + "\n" + textView.getText()); return true; } public String eventActionToString(int eventAction) { switch (eventAction) { case MotionEvent.ACTION_CANCEL: return "Cancel"; case MotionEvent.ACTION_DOWN: return "Down"; case MotionEvent.ACTION_MOVE: return "Move"; case MotionEvent.ACTION_OUTSIDE: return "Outside"; case MotionEvent.ACTION_UP: return "Up"; case MotionEvent.ACTION_POINTER_DOWN: return "Pointer Down"; case MotionEvent.ACTION_POINTER_UP: return "Pointer Up"; case MotionEvent.ACTION_POINTER_2_DOWN: return "Pointer 2 Down"; case MotionEvent.ACTION_POINTER_2_UP: return "Pointer 2 Up"; } return ""; } }; rootView.setOnTouchListener(touchListener); return rootView; }

Hopefully someone at Amazon will be able to reproduce and look into the issue, as I'm sure it's just not us that are affected.