Success! Looks like we've fixed this one. According to our records the fix was applied for TOUCH-5408 in 2.3.3.
  1. #1
    Sencha User
    Join Date
    Jun 2012
    Posts
    11
    Vote Rating
    0
    freelancer187 is on a distinguished road

      0  

    Default Touch events not firing

    Touch events not firing


    Hello,


    I'm experiencing something really strange with one of the devices I'm working with.


    We've been trying to deploy one of our existing Sencha Touch 2 app on a HP Slate 8 Pro Android tablet. The app itself seems to work fine (at least, it starts properly), however, none of the touch events (touch start, touch move or touch end....nor tap, etc.) are being registered by this device. We basically can't press a button, scroll a list, etc.


    The screen is properly responsive since we can tap on a textbox and get the soft keyboard to pop up. So I assumed something was wrong with the bindings...But I can't figure out what exactly.


    This app is built with Sencha Touch 2 and Cordova 3.1. In order to eliminate potential sources of issues:
    • I got rid of Cordova and built the application with the Sencha Native Packager. Behavior persisted.
    • I got rid of the Sencha Native Packager and built a very simple 1 activity application which loads index.html from the asset folder to the webview. Behavior persisted.
    So I started to wonder what exactly could cause this. I tested this last version (lite Android app) in 3 different devices:
    • A Samsung Galaxy S3 running the latest Cyanogen Mod (Android 4.4.2)
    • A Galaxy Nexus running Android 4.2.1 (retail)
    • The HP Slate 8 pro running Android 4.2.2 (probably some HP homebrew fork which so far I blame for the issue...)
    First difference is, the user agents:
    • SGS3 Webview uses:
    Mozilla/5.0 (Linux; Android 4.4.2; SAMSUNG-SGH-I747 Build/KOT49H) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/30.0.0.0 Mobile Safari/537.36
    • The Galaxy Webview uses:
    Mozilla/5.0 (Linux; U; Android 4.2.1; en-us; Galaxy Nexus Build/JOP40D) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Mobile Safari/534.30
    • The Slate Webview uses:
    Mozilla/5.0 (Linux; U; Android 4.2.2; en-us; HP Slate 8 Pro Build/JDQ39) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Safari/534.30


    The only difference (excluding the SGS3 using Chrome as a webview which is a new feature of Android KitKat) is that the Slate isn't using a Mobile version of safari. This might be expected since this is a tablet and not a phone. I'm not quite sure if there's a real impact.


    Other test I ran was to trace all the events bound on the app startup:

    Galaxy S3 Cyanogen 4.4.2
    Code:
    binding Ext.AnimationQueue#run
    binding Ext.AnimationQueue#whenIdle
    binding Ext.AnimationQueue#processIdleQueueItem
    binding Ext.AnimationQueue#processTaskQueueItem
    binding Ext.TaskQueue#run
    binding Ext.TaskQueue#watch
    binding Ext.event.publisher.Dom#onEvent
    binding Ext.event.publisher.TouchGesture#onEvent
    binding Ext.viewport.Default#doPreventPanning
    binding Ext.viewport.Default#doPreventZooming
    binding Ext.viewport.Default#doBlurInput
    firing event initialize
    binding Ext.viewport.Default#onOrientationChange
    binding Ext.viewport.Default#onElementFocus
    binding Ext.viewport.Default#onElementBlur
    firing event ready
    binding Ext.util.paintmonitor.OverflowChange#onElementPainted
    binding Ext.util.sizemonitor.OverflowChange#onExpand
    binding Ext.util.sizemonitor.OverflowChange#onShrink
    binding Ext.util.sizemonitor.Abstract#refresh
    firing event initialize
    firing event initialize
    binding Ext.app.History#detectStateChange
    firing event exception
    firing event beforeload


    Galaxy Nexus (4.2.1)


    Code:
    binding Ext.AnimationQueue#run
    binding Ext.AnimationQueue#whenIdle
    binding Ext.AnimationQueue#processIdleQueueItem 
    binding Ext.AnimationQueue#processTaskQueueItem 
    binding Ext.TaskQueue#run 
    binding Ext.TaskQueue#watch
    binding Ext.event.publisher.Dom#onEvent 
    binding Ext.event.publisher.TouchGesture#onEvent 
    binding Ext.viewport.Default#doPreventPanning 
    binding Ext.viewport.Android#doPreventZooming 
    binding undefined 
    firing event initialize
    
    
    binding Ext.viewport.Default#onElementFocus 
    binding Ext.viewport.Default#onElementBlur 
    firing event ready 
    binding Ext.util.paintmonitor.CssAnimation#onElementPainted 
    binding Ext.util.sizemonitor.Scroll#onScroll 
    
    
    binding Ext.util.sizemonitor.Abstract#refresh
    firing event initialize 
    firing event initialize 
    binding Ext.app.History#detectStateChange 
    firing event exception 
    firing event beforeload


    Slate 8 Pro (4.2.2)


    Code:
    binding Ext.AnimationQueue#run
    binding Ext.AnimationQueue#whenIdle
    binding Ext.AnimationQueue#processIdleQueueItem
    binding Ext.AnimationQueue#processTaskQueueItem
    binding Ext.TaskQueue#run
    binding Ext.TaskQueue#watch
    binding Ext.event.publisher.Dom#onEvent
    binding Ext.event.publisher.TouchGesture#onEvent
    binding Ext.viewport.Default#doPreventPanning
    binding Ext.viewport.Android#doPreventZooming
    binding undefined
    firing event initialize
    
    
    binding Ext.viewport.Default#onElementFocus
    binding Ext.viewport.Default#onElementBlur
    firing event ready
    binding Ext.util.paintmonitor.CssAnimation#onElementPainted
    binding Ext.util.sizemonitor.Scroll#onScroll
    
    
    binding Ext.util.sizemonitor.Abstract#refresh
    firing event initialize
    firing event initialize
    binding Ext.app.History#detectStateChange
    firing event exception
    firing event beforeload

    Funny thing is the binding of both the Galaxy and the Slate are the same...But the Slate still won't react to touch (binding Ext.event.publisher.TouchGesture#onEvent)


    I'm running out of ideas right now. Is there anything you'd recommend looking at?


    I already tried the solution presented in this post with no luck.

    EDIT:
    I'm not sure if this is appropriate to post this as a bug as I couldn't yet identify if this is related to Sencha Touch or specifically this device.

    Thanks

  2. #2
    Sencha - Support Team
    Join Date
    Oct 2011
    Posts
    3,936
    Vote Rating
    130
    fmoseley is a name known to all fmoseley is a name known to all fmoseley is a name known to all fmoseley is a name known to all fmoseley is a name known to all fmoseley is a name known to all

      0  

    Default


    Thanks for the report. Can you please specify the exact version of Sencha Touch that you are using?
    Have you tried running your mini test app as a web app in a browser on HP Slate? Does it work?
    Get more personalized support via a support subscription.

    Want to learn Sencha Touch 2? Check out
    Sencha training
    Sencha Touch in Action

    Need more help with your app? Hire Sencha Services services@sencha.com

    When posting code, please use BBCode's CODE tags.

    Need to include a test case use:
    The official Sencha Fiddle

  3. #3
    Sencha User
    Join Date
    Jun 2012
    Posts
    11
    Vote Rating
    0
    freelancer187 is on a distinguished road

      0  

    Default


    Thanks for the quick reply!

    I'm using Sencha Touch 2.3.1a.

    The app (in web app mode) works just fine (in Chrome). It's only once packaged that I encounter such issue.

  4. #4
    Sencha - Support Team
    Join Date
    Oct 2011
    Posts
    3,936
    Vote Rating
    130
    fmoseley is a name known to all fmoseley is a name known to all fmoseley is a name known to all fmoseley is a name known to all fmoseley is a name known to all fmoseley is a name known to all

      0  

    Default


    It is possible as we have had a similar issue reported with the HTC One (TOUCH-5193). Unfortunately I do not have access to that particular device to confirm, but I will file a bug and bring this issue to Engineering's attention. Can you send me the code for your simple app.
    Quote Originally Posted by freelancer187 View Post
    Thanks for the quick reply!

    I'm using Sencha Touch 2.3.1a.

    The app (in web app mode) works just fine (in Chrome). It's only once packaged that I encounter such issue.
    Get more personalized support via a support subscription.

    Want to learn Sencha Touch 2? Check out
    Sencha training
    Sencha Touch in Action

    Need more help with your app? Hire Sencha Services services@sencha.com

    When posting code, please use BBCode's CODE tags.

    Need to include a test case use:
    The official Sencha Fiddle

  5. #5
    Sencha User
    Join Date
    Jun 2012
    Posts
    11
    Vote Rating
    0
    freelancer187 is on a distinguished road

      0  

    Default


    Thank you sir!

    Unfortunately, I am not allowed to provide you with my source code. But I can confirm that this issue is also occurring when packaging the Kitchen Sink application.

    If you want an even simpler app to test with, please name another one of the sencha examples you consider fit and I'll gladly package/test it on the device to confirm that the bug is reproducible.

    Please, let me know.
    Thanks

  6. #6
    Sencha Premium Member
    Join Date
    Sep 2013
    Posts
    2
    Vote Rating
    0
    tdeng is on a distinguished road

      0  

    Default Same issue in HP Slate 21

    Same issue in HP Slate 21


    I have the same issue in a HP Slate 21 (non pro). We're making an app using the android webview, and it works fine in a Nexus device, as well as several other android 4.1 devices, but this HP Slate 21 (android 4.2.2) does not work. It appears all of the buttons do not accept any input. We've tested on several devices with android 4.1, 4.2, 4.3 and 4.4 and they all work but not this HP Slate 21.

    I've tried our own app, and all buttons do not work, but text fields do. Event the little (X) in the text field do not work.

    I tried loading the sencha examples through our app's webview as well, and the same behavior with buttons do not work.

    We're using sencha touch 2.3.1a, loading the code inside a android Webview, not through the browser or chrome.

  7. #7
    Sencha Premium Member
    Join Date
    Sep 2013
    Posts
    2
    Vote Rating
    0
    tdeng is on a distinguished road

      0  

    Default


    After a bit more digging, and debugging with the chrome debugger, in the tablets that work, the button elements have Event Listeners, and the HP Slate 21 does not have event listeners for the same elements.

  8. #8
    Sencha Premium Member
    Join Date
    Jun 2013
    Posts
    6
    Vote Rating
    0
    kjsteinke is on a distinguished road

      0  

    Default


    Any fix / patch information on this yet?

  9. #9
    Sencha - Support Team
    Join Date
    Oct 2011
    Posts
    3,936
    Vote Rating
    130
    fmoseley is a name known to all fmoseley is a name known to all fmoseley is a name known to all fmoseley is a name known to all fmoseley is a name known to all fmoseley is a name known to all

      0  

    Default


    No unfortunately there is not a patch available at this time.
    Get more personalized support via a support subscription.

    Want to learn Sencha Touch 2? Check out
    Sencha training
    Sencha Touch in Action

    Need more help with your app? Hire Sencha Services services@sencha.com

    When posting code, please use BBCode's CODE tags.

    Need to include a test case use:
    The official Sencha Fiddle

  10. #10
    Sencha User
    Join Date
    Jul 2012
    Posts
    2
    Vote Rating
    0
    michalHalamish is on a distinguished road

      0  

    Default We Having the same problem - HPAnywhere mobile app

    We Having the same problem - HPAnywhere mobile app


    Hi,
    We are facing the same problem, our mobile app get freeze on Slate 8 pro.
    When do you plan to fix it?

    Thanks