Haptic engine/motor is engaged all times

[acmeplus]

Haptic engine is engaged all times. In some cases resetting works as a temporary workaround, but V6 motherboards users seem to be unable to disable it.

Note: Some users have reported success stopping the motor by ejecting the SDCard, reset, insert SDCard, and reset again.

[8trius]

Yes, I just opened up my device to confirm: I'm running a v.6.0 2022-11-19 motherboard and this issue is persistent. Three resets in a row stopped it. But once I switch to another OS like GarlicOS, or reset, the issue can reactivate.

[ghost]

In the Test Release Alpha 0.2 I was finally able to get mine to stop by using suspend in the Batocera QUIT GUI. When resuming I hear a pop from the speaker and it rebooted with the Haptic engine/motor disabled. subsequent reboots/shutdowns it seems to stay disabled too.

[ghost]

Well it came back but after lots of trial and error I think I found the problem..... I removed this from the DTS

vdd-gpu-dcdc { compatible = "actions,atc2603c-ext-pwm-dcdc1\0actions,atc2603c-ext-pwm-dcdc"; regulator-name = "vdd-gpu-dcdc"; regulator-min-microvolt = <0xdbba0>; regulator-max-microvolt = <0x1312d0>; regulator-always-on; pwms = <0x0d 0x01 0xa6a 0x00>; table_len = <0x0f>; vdd_cpu_table = <0xdbba0 0xe1d48 0xe7ef0 0xee098 0xf4240 0xfa3e8 0x100590 0x106738 0x10c8e0 0x112a88 0x118c30 0x11edd8 0x124f80 0x12b128 0x1312d0>; pwm_config_table = <0x13 0x12 0x11 0x10 0x0f 0x0e 0x0d 0x0c 0x0b 0x0a 0x09 0x08 0x07 0x06 0x05>; linux,phandle = <0x1b>; phandle = <0x1b>; }; vdd-core-dcdc { compatible = "actions,atc2603c-ext-pwm-dcdc2\0actions,atc2603c-ext-pwm-dcdc"; regulator-name = "vdd-core-dcdc"; regulator-min-microvolt = <0xdbba0>; regulator-max-microvolt = <0x1312d0>; regulator-always-on; pwms = <0x0d 0x02 0xa6a 0x00>; table_len = <0x0f>; vdd_cpu_table = <0xdbba0 0xe1d48 0xe7ef0 0xee098 0xf4240 0xfa3e8 0x100590 0x106738 0x10c8e0 0x112a88 0x118c30 0x11edd8 0x124f80 0x12b128 0x1312d1>; pwm_config_table = <0x13 0x12 0x11 0x10 0x0f 0x0e 0x0d 0x0c 0x0b 0x0a 0x09 0x08 0x07 0x06 0x05>; };

converted back to dtb and it booted without the haptic vibes.

kernel.dtb.zip

[acmeplus]

Well it came back but after lots of trial and error I think I found the problem..... I removed this from the DTS
[...]
converted back to dtb and it booted without the haptic vibes.

kernel.dtb.zip

Very interesting, supposedly the gpu needs that block, but just checked and as far as the gpu is enabled in its gpu section below it seems to work.

I've narrowing down the issue to a conflict in the pwm. In theory that block should just enable the GPU, but it's possible that there's an overlapping with the motor pwm.

I've sent a modified file to some testers to see if it works. In my rg35xx the motor stays off most of the time.

[fouadchamoun]

I flashed the v0.2 alpha and had the haptic issue. I then replaced the kernel.dtb file with the modified one and it fixed the issue for me.

[jamezh2020]

Same here. Replaced the kernel.dtb with the one provided and the motor is now silent.

[acmeplus]

This is now fixed in the upcoming release. Closing this issue.

Thanks @ghost for the hint.