9 Answers, 1 is accepted
First thing that comes to my mind is to try changing the Hardware Acceleration option in Properties/Android. On some devices turning it on speeds things up, but on some slows them down. If this doesn't help, could you please send us a small sample reproducing your issue, in order to be able to help you.
kdimitrov
the Telerik team
Share feedback and vote for features on our Feedback Portal.
Want some Kendo UI online training - head over to Pluralsight.

Debugging a specific implementation can be hard and time consuming and also we need to cooperate with Kendo team in order to help you in this case.
That is why we need as simple as possible sample to reproduce that lag issue.
Kind regards,
the Telerik team
Share feedback and vote for features on our Feedback Portal.
Want some Kendo UI online training - head over to Pluralsight.

https://www.dropbox.com/s/btwz8g0n4m9grxx/Video%2022-01-2013%2020%2031%2034.mov
The first device is my HTC One X and you can clearly see how slow it is to respond vs all the other devices (sorry for the background noise... just hit mute!)
We manage to reproduce your findings on response times:
HTC One X (v4.0.4) slowest
Motorola Razr (v.4.0.4) slower
Galaxy Nexus (v4.1.1) normal
Samsung Galaxy S III (v4.1.2.) fast
This is appears to be a known issue by Kendo team and is caused by Hardware Acceleration on slower devices (especially HTC One X) it makes animations smoother but there is an noticeable delay before animation starts.
You can experiment yourself by disabling Hardware Acceleration as Kristian mentioned already folowing this steps:
1. Device Settings > Developer options > Force GPU rendering: (unchecked)
2. In Icenium > Project Properties > Android > Hardware Acceleration: Off
3. Delete application from device and redeploy
Unfortunately there is no silver bullet (settings) that will work for all Android devices. So if you ok with a bit "choppy" animation, but more responsive Android app keep Hardware Acceleration off.
BTW: Samsung Galaxy S (2.2) is fastest probably because there is no Hardware Acceleration at all.
Regards,
the Telerik team
Share feedback and vote for features on our Feedback Portal.
Want some Kendo UI online training - head over to Pluralsight.

Maybe I'm mad, but that doesn't really make any sense to me? And calling the HTC One X a slow device is mad, it's quad core 1.5ghz and surfing the net is faster than running my app?
I might try a jquery app to see what happens
no you are not mad, it is not about hardware that is pretty decent for that smart phone.
It is caused by software implementation of android 4.x webview "accelerated" rendering. More info here.
Did you followed the instructions to disable Hardware Acceleration? As our tests confirmed that this improves the responsiveness on that particular device greatly.
Jordan
the Telerik team
Share feedback and vote for features on our Feedback Portal.
Want some Kendo UI online training - head over to Pluralsight.

the setting (Force GPU rendering) is under developer options for a reason and it dose impact some native widgets and apps same way.
As for dual binary output for android apps we have it in our backlog but you may to post it as feature request to gather more votes from community as we take this into the account when considering what to do next.Have a nice and productive week,
Jordan
the Telerik team
Share feedback and vote for features on our Feedback Portal.
Want some Kendo UI online training - head over to Pluralsight.