Closed ShadowEO closed 8 years ago
I found an issue in the Bricked-flo repository referencing this exact behavior, attempting to test DT2W with it automatically enabled on startup as it seems dynamically changing it can cause the screen to not register inputs.
DoubleTap2Wake has been fixed in the current release and has been fixed in the current HEAD of the repository. For now DoubleTap2Wake requires being activated after boot with the screen on. If DT2W is activated without the screen on (meaning that the /sys file is turned on while the screen is off), the screen will become unresponsive.
A workaround for this would be to make a ramdisk change that would echo a 1 to /sys/android_touch/doubletap2wake while the screen is still effectively showing the bootlogo, thus ensuring that DT2W turns on properly.
Currently the DT2W driver and it's subsequent changes under the touchscreen driver do not work at all. I am not sure of the cause of this. The driver itself compiles and loads into memory (it's visible in /sys/android_touch) but enabling it does nothing and in my own testing caused the touchscreen to not take any input.
I will be looking into replacing the implementation I currently have with a working one from Android commits.