Open HemanthJabalpuri opened 1 year ago
A more recent motorola device with official TWRP is at here which can be used as a reference to fix touch issue.
This commit probably seems to fix the issue https://gerrit.twrp.me/c/android_bootable_recovery/+/6690
So, it seems like module loading has to happen in time.
More testing is required.
Touch is working fine with stock ROM (either temporary boot or permanent install) but it is behaving differently when using with custom ROM
Sometimes it will work and sometimes dont. Most of the time, it will work with temporary boot.
Multiple tries booting again to TWRP may fix but not guaranteed.
If you strictly want to use TWRP(I highly doubt because LOS recovery is there), then you can flash stock ROM vendor_boot and dtbo partitions which are used by TWRP in stock rom. (See this)
I am not familiar with kernel and it's module loading to read dmesg logs. Also I am not a custom ROM user. I don't want to leave my stock ROM setup just to test and fix this issue.
so can't fix at the moment.
Thanks