After panning the map several times, the recticle of adding a new feature doesn't move to the right position of the stylus

[tobiasgrau0]

Describe the issue

After panning the map several times and add some new points with the stylus, the reticle for adding a new feature don't move to the position of the stylus - the new point feature will be added in a wrong position.

https://github.com/opengisch/QField/assets/171577940/606600b1-9703-46f0-86fc-d8634e80fbfb

Reproduction steps

Steps to reproduce the behavior:

1. Add some new points with the stylus
2. Panning the map several times
3. Add further points with the stylus

Expected behavior

The reticle move to the position of the stylus.

Observed behavior

Sometimes the reticle doesn't move, sometimes it only moves after zooming in and zoom out

Screenshots and GIFs

See video (only a short abstract)

[Please also attach additional files if a specific project/dataset is useful to investigate the problem.]

• QField Version [e.g.3.1.9] and it also appears at the actual DEV-version

Additional information

• Problem started happening recently, didn't happen in an older version of QField: [Yes] - in version 2.8.4 all works fine
• Problem can be reliably reproduced, doesn't happen randomly: [Yes] - but sometimes many new points have to be added
• Problem happens with all files and projects, not only some files or projects: [Yes]

[If the problem happened with QFieldCloud, please add your username and project name.]

[nirvn]

@tobiasgrau0 , can you test with APKs here: https://github.com/opengisch/QField/pull/5359 -- are you still able to replicate?

[tobiasgrau0]

@nirvn : i have tested it with the APK 5359 unfortunately the problem is not solved

[Paul-Losse]

I have the same problem. The stylus works fine until you pan the map and then stops functioning

[lp-dj]

I can also confirm the problem in the latest QField version (3.4.3 - Ebo 412c8d).

I even updated/ upgraded to the latest hardware (Samsung Galaxy Tab Active 5 5G) and operating system (Android 14, One UI 6.1) to make sure that my ongoing problems with stylus use (unfortunately not just the issue described here) are not due to the outdated base.

Regarding the issue discussed here: I found out that you can get the stylus to work again quite reliably by tapping the burger menu (three dashes at the top left) once. If you then tap back on the map canvas, the stylus works again as intended. The procedure also works during a digitizing process.

Maybe this can be a hint for bugfixing, @nirvn?

[Paul-Losse]

@nirvn I confirm that the stylus starts working again when the menu icon is tapped. Otherwise the problem persists

[m-kuhn]

@Paul-Losse are you able to check with the latest QField release (3.5)? There have been changes that could have solved this issue.

[Paul-Losse]

@nirvn Only version 3.4.7 seems to be available on Android Play Store

[m-kuhn]

@Paul-Losse it will be rolled out incrementally over the next weeks, you can download it already here https://github.com/opengisch/QField/releases/tag/v3.5.0

[Paul-Losse]

@nirvn OK, downloaded. I'm afraid that problem persists

[nirvn]

@Paul-Losse , we've nailed one more stylus problem here https://github.com/opengisch/QField/pull/6012 -- if you have a minute to try that APK out and report whether it helped your situation or not, it'd be great.

[Paul-Losse]

@nirvn, sorry for the delay. I've now had a chance to try out that APK. Sorry but the problem is still there. Best regards, Paul

[nirvn]

@Paul-Losse , thanks for trying. Would you be able to attach a screencast of your experience here?

[mohsenD98]

Hey @Paul-Losse , are you using a stylus exclusively, or do you sometimes use finger touches?

[Paul-Losse]

@mohsenD98, I mainly use a stylus but occasionally use finger touches when the stylus is not functioning as expected.

[Paul-Losse]

https://github.com/user-attachments/assets/fdb55d1d-7411-49fe-81d6-1acbfde49cf6

[Paul-Losse]

@nirvn See screencast above. As you can see the stylus works with panning the screen for a while but then stops functioning. I have to revert to finger movements to add the next vertex. It's only a problem when the screen needs to be panned. I notice that if only the stylus is used to pan the map, there is no problem. If a finger is used to pan whilst using the stylus to add a polygon, then the problem appears. So the work around is to use only the stylus and not touch the screen with a finger whilst digitising

[mohsenD98]

Thanks @Paul-Losse , As noted in #6012, if the transition from using a stylus to using a finger occurs within 500 milliseconds or less, the binding may be disrupted. Could you please try to allow a bit more time between switching? Thank you!

[Paul-Losse]

@mohsenD98 Thanks, I'll try that