MiCode / MiCode/Xiaomi_Kernel_OpenSource
Request for Kernel Fix: DT2W not working on Xiaomi 11i (pissarro)
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 9.9k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
Hello Xiaomi Kernel Team,
I am reporting an issue on the Xiaomi 11i (codename: pissarro, MTK Dimensity 920) kernel source while running HyperOS 1 (Android 13 base).
Issue:
DT2W (Double Tap to Wake
) does not work reliably.
When the screen is turned off, DT2W does not trigger at all.
On other devices such as OnePlus, DT2W functions correctly even in screen-off state, but on pissarro it fails.
Kernel logs show touch events (ABS_MT_TRACKING_ID), but the wake action is not executed.
Possible Cause:
Incomplete event handling in the touchscreen driver (Goodix/Focaltech).
Gesture handling not properly configured during screen-off state.
Suggested Fix:
Keep the touchscreen driver partially active during screen-off mode to capture wake gestures.
Verify that input_event_wakeup flag or gesture nodes are enabled in the driver/DTS.
Compare with other MTK devices or OnePlus implementation where DT2W works correctly.
This issue impacts daily usability, so I kindly request your guidance or a patch to resolve it.
Thank you for your support.
Best regards,
Saurabh Pattebahadur
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 attached DT2W_logs.txt and locate the touchscreen driver and DTS entries for the Xiaomi 11i (pissarro), focusing on the Goodix/Focaltech handling and input_event_wakeup or gesture nodes mentioned. Compare the relevant screen-off gesture handling with other MTK devices or the cited OnePlus implementation. Done means DT2W reliably wakes the device from screen-off state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, linux
- Domain
- mobile-dev, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100