Hi Folks,
Interesting behaviour...
Has anyone else seen this?
The behaviour appears to be that everything works fine for a brief moment while Chrome loads up, but after an undetermined amount of time (of the order of a few seconds), the mouse interrupts (I'm guessing) no longer get handled. The mouse stops responding to input, and, eventually, the mouse pointer disappears, never to reappear again (the pointer disappearing isn't directly a symptom - it's simply disappearing as expected in the absense of any mouse input).
Toggling the enable/disable touchpad key has no effect. However, undocking the keyboard, then re-docking brings the mouse back again for a brief period before the interrupts get ignored/blocked after a few moments.
Disabling Chrome seems to prevent this issue from arising (writing this using the stock Browser instead) and the mouse pointer is still happy...
I've not tried the dev or beta versions of Chrome yet.
Interesting behaviour...
It appears that running the above version of Chrome will cause my keyboard dock touchpad mouse, and any USB attached mouse, to get disabled. Indeed, writing this makes me think that the dock has nowt to do with it, but the mouse interrupt handling area of Android is being messed with by Chrome.
Docked TF701T - Kitkat 4.4.2 (stock, not rooted)
Chrome - 46.0.2490.76
Has anyone else seen this?
The behaviour appears to be that everything works fine for a brief moment while Chrome loads up, but after an undetermined amount of time (of the order of a few seconds), the mouse interrupts (I'm guessing) no longer get handled. The mouse stops responding to input, and, eventually, the mouse pointer disappears, never to reappear again (the pointer disappearing isn't directly a symptom - it's simply disappearing as expected in the absense of any mouse input).
Toggling the enable/disable touchpad key has no effect. However, undocking the keyboard, then re-docking brings the mouse back again for a brief period before the interrupts get ignored/blocked after a few moments.
Disabling Chrome seems to prevent this issue from arising (writing this using the stock Browser instead) and the mouse pointer is still happy...
I've not tried the dev or beta versions of Chrome yet.
No comments:
Post a Comment