Closed xen0n closed 9 years ago
OK this is finally solved... sort of reverse-engineered the whole thing thanks to this source. Tried to backport whole of m75
kernel's working vibration code by means of kernel modules, but that wasn't working even after replacing all power-management-related code. Anyway we can close this issue for good...
MTK vibrator in
/sys/class/timed_output
seems useless;immvibed
is deliberately coded to prevent debugging and seems to have some "registration" mechanism built in. Don't know if we can get it working without making the device namemx4
(because the two models, despite virtually the same hardware, are partitioned differently).