micku7zu / micku7zu/QuickCursor
Clicks stop working after some time on Android 15
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 83
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Issue description
The click functionality on devices running Android 15 stops working after a certain period. Restarting the device temporarily resolves the issue, but the problem reoccurs after some time.
Workaround
I've implemented 3 workarounds in Quick Cursor version 2.2.0 (233):
- Simulate multi taps when click stops working (the detection mechanism is experimental, hopefully it works)
- Simulate multi taps on tracker long tap (this means that you need to long tap when the click doesn't work anymore)
- Simulate multi taps on every tracker release (this is more intrusive and might interfere with other apps or notification bar)
You can enable any of this 3 workarounds in the "Android 15 issue ⚠" menu in the Quick Cursor app.
Simulating a multi tap on the screen fixes the issue temporarly until it happens again.
Previous "manual" workaround
- Assign a "Multi tap" action with 2 simultaneous taps as an Edge action, Tracker action, or Tracker long tap action
- When the click stops working, trigger that action once
- The click should start working again
Example: Go to Quick Cursor Settings -> Tap behaviour -> Long tap action -> More actions -> Multi tap -> Save. When the tap doesn't work, you just have to long tap the tracker, it will simulate a Multi tap and it will start working again.
Root cause
This is an OS bug confirmed by Google and they are working on a fix. This bug affects other apps as well. It is not Quick Cursor specific.
I've posted more details about the investigation here: https://www.reddit.com/r/android_beta/comments/1hev8jm/touch_simulation_via_accessibility_services_stops/
Updates:
Google fixed this issue in Android 16 but the issue will remain forever on devices with Android 15. For this situation, only the workarounds can help.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the issue description, the linked Google issue 384188031, and the referenced Android 15 investigation. No repository files or tests are named, and the reported cause is an Android 15 OS bug fixed in Android 16. Treat the existing Android 15 workarounds as the documented scope; there is no remaining repository change specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100