Using Qfield with bluetooth mouse does not seem to work properly in the newest version (worked on the previous version)

[ollirantanen1]

Describe the issue

Using Qfield with bluetooth mouse does not seem to work properly in the newest version (worked on the previous version)

Reproduction steps

Steps to reproduce the behavior:

1. Connect bluetooth mouse to device
2. On Qfield try to open menus, digitize, drag or any other action (except zooming) with mouse and it does not work.
   a. Also, you can notice during digitizing that that coordinate cursor is not connected to the mouse cursor
3. Additionally tested to alter the setting: "Consider mouse as a touchscreen device" which did not affect the behavior

Expected behavior

Using the mouse worked on the previous versions

QField (please complete the following information)

• Device: Samsung Galaxy Tab Active Pro 5G
• OS: Android 14
• QField version: 3.4.4-Ebo (5cc32f v3.4.4)

Additional information

• Problem started happening recently, didn't happen in an older version of QField: Yes
• Problem can be reliably reproduced, doesn't happen randomly: Yes
• Problem happens with all files and projects, not only some files or projects: Not tested but multiple users have reported the same issue with different projects

[nirvn]

@ollirantanen1 , can you manually install QField 3.4.3 from here (https://github.com/opengisch/QField/releases/tag/v3.4.3) and confirm that the version works with your bluetooth mouse?

[ollirantanen1]

Unfortunaly I don't have access to needed devices but our testers reported the problem today after they started using the new version. One of them had used the previous version this morning which worked with the mouse but when they updated the new version it did not work. The actual version is unknown but they updated it on the 22.10.2024 so it most likely was 3.4.3.

Edit: One of our testers has 3.4.1. and another one 3.4.3. and the mouse works well without any issues

[nirvn]

One significant change between 3.4.3 and 3.4.4: we upgraded from Qt 6.6.3 to 6.7.3. I suspect it's an upstream change that led to this situation.