So, as some folks noticed, there was a change recently to how trackpad mode is handled in the touch clients. This was for a variety of reasons! But the short form is that what happens now is that when the mouse cursor is visible, the touch trackpad is handled in absolute mode (e.g. setting the cursor location to where you touch), while when the mouse cursor is hidden the touch trackpad is handled in relative mode (which works better for games that are expecting mouselook type input).

This works pretty well for many things, but seems to be causing issues for some folks. In the interests of tracking down the best way to fix it, we're going to try to get some information! Specifically, if the change to the trackpad functionality in build 1.3.20 of the Android client broke stuff for you, it'd be great to know very specifically what stuff it is that's broken.

• What game is affected, and is it a Steam game being streamed?
  
• If it is NOT a Steam game, did you add it to Steam as a non-Steam game? Or are you just streaming your desktop and trying to run the game that way?
  
• What *specifically* is the incorrect/unexpected behavior? Basically, "the mouse cursor is on screen but moves more like I'm moving it with a joystick" or "there is no mouse cursor but now things seem inconsistent and oversensitive" or whatever.
  
• Any other useful data you can provide about how you're using the virtual trackpad mode.

The data will be *most* appreciated, and will help sort out the best way to approach this. Splitting the two apart again into explicit modes is not ideal (for a variety of reasons) as there *were* reasons they were combined in the first place, but the goal is definitely to make the behavior be more "what you expect" again.

Thanks!