Comment 15 for bug 1531517

Ah yes the android input transport is biting us again. We are still bound to the limitation of that encoding. That encoding means - only one down/up touch id per event. No matter what libinput reads or qtmir sanitizes.. , as long as the transport from server to nested server or from nested server to client chops of the information of every additional down or up the gesture will break. I will keep the fix close to the encoding so we can get rid of it easier...