debb1046,
If you are up for it, this issue seems to be a perfect example to start our user test database.
1. Compile evemu (bzr branch lp:utouch-evemu)
2. Find the event node of your device (grep -i galax /proc/bus/input/devices -A4 | grep H:)
3. Extract the device definition (sudo ./tools/evemu-describe /dev/input/eventX > wetab.prop)
4. Start a recording (sudo ./tools/evemu-record /dev/input/eventX > wetab.event)
5. Perform the test that fails - the recording will stop after ten seconds of inactivity.
6. Attach the wetab.prop plus wetab.event files here with a description of the failure.
With this data, it is possible to reproduce the problem exactly, and the test can be used during development.
Thanks!
debb1046,
If you are up for it, this issue seems to be a perfect example to start our user test database.
1. Compile evemu (bzr branch lp:utouch-evemu)
2. Find the event node of your device (grep -i galax /proc/bus/ input/devices -A4 | grep H:)
3. Extract the device definition (sudo ./tools/ evemu-describe /dev/input/eventX > wetab.prop)
4. Start a recording (sudo ./tools/ evemu-record /dev/input/eventX > wetab.event)
5. Perform the test that fails - the recording will stop after ten seconds of inactivity.
6. Attach the wetab.prop plus wetab.event files here with a description of the failure.
With this data, it is possible to reproduce the problem exactly, and the test can be used during development.
Thanks!