What steps will reproduce the problem? 1.Create a QPushButton, connect clicked() to a slot 2.Press button. 3.Release button. Button state remains pressed. No signal is sent. 4.Tap the screen outside the button. State is changed to released again, and the signal is sent.

I'm using the android_sw plugin.

Here is the log:

Pressed button: V/WindowManager( 2492): Delivering toWindow{483b6d00 org.myapp.qt/org.myapp.qt.QtMain paused=false} D/Qt (12642): mouseDown Released button: V/WindowManager( 2492): Delivering toWindow{483b6d00 org.myapp.qt/org.myapp.qt.QtMain paused=false} D/Qt (12642): mouseUp

Button remains "pressed", and no signal is sent.

Tap the screen, not on any button: D/dalvikvm( 2592): GC_EXPLICIT freed 2362 objects / 177080 bytes in 146ms V/WindowManager( 2492): Delivering toWindow{483b6d00 org.myapp.qt/org.myapp.qt.QtMain paused=false} D/Qt (12642): mouseDown

The button state is no longer pressed, and the signal is sent.

This does not happen every time, though, I guess about 1 in 5 clicks. But it very often happens on the first tap after I start the app.

I have same problem. Every touch on touchscreen - produces:

D/Qt ( 9177): mouseDown D/Qt ( 9177): mouseDown D/Qt ( 9177): mouseUp D/Qt ( 9177): mouseUp

Also, if I connect signals "pressed" and "released", I see button remains pressed. Sometimes, I have one mouseDown and two mouseUp. This tested on real device. On emulator I have same problem.

How to solve this and how I can help to improve this port? Version - latest from git.

Little addition: double mouseDown/mouseUp happens only when debugging on real device with Android 2.1 (HTC). Each touch reported twice, sometimes reported once...

http://qt.gitorious.org/qt/android-lighthouse/commit/9ce722249d29c57524b02fabc27f6d00e4854759