The haptic feedback during plugging in/out is too weak

[piecesuger]

Issue type

Feature not working as intended

Device

OnePlus Ace 3V (audi)

crDroid version

crDroid 12

Exact version / Build date

12.8/2026-03-13

Bug description

With the USB cable plugged in/out, there should be haptic feedback since the vibrate option in charging sounds settings is already toggled. It actually exists and there are related records in the log. But the feedback is too weak that it is nearly imperceptible.

Steps to reproduce

Step 1. Enable vibrate option in charging sounds settings.
Step 2. Plug in or out.

Relevant log (logcat/build log)

03-15 00:26:00.902 I/[haptic_hv]aw_file_unlocked_ioctl(2299): cmd=0x5205, arg=0x11
03-15 00:26:00.942 I/[haptic_hv]aw_file_unlocked_ioctl(2299): cmd=0x5205, arg=0x8
03-15 00:26:00.983 I/[haptic_hv]aw_file_unlocked_ioctl(2299): cmd=0x5205, arg=0x3
03-15 00:26:01.022 I/[haptic_hv]aw_file_unlocked_ioctl(2299): cmd=0x5205, arg=0x1
03-15 00:26:09.587 I/[haptic_hv]aw_file_unlocked_ioctl(2299): cmd=0x5205, arg=0x0
03-15 00:26:09.589 I/[haptic_hv]aw_file_unlocked_ioctl(2365): cmd=0x520a, arg=0x0
03-15 00:26:09.590 I/[haptic_hv]aw8692x_wait_enter_standby(2365): entered standby!
03-15 00:26:09.591 I/[haptic_hv]aw8692x_upload_lra(2365): write osc_cali_data to trim_lra = 0x00
03-15 00:26:09.592 I/        (7523): [haptic_hv]rtp_work_proc enter
03-15 00:26:09.601 I/[haptic_hv]aw8692x_play_mode(7523): enter rtp mode
03-15 00:26:09.602 I/[haptic_hv]aw8692x_bst_mode_config(7523): haptic bst mode = bst
03-15 00:26:09.602 I/[haptic_hv]exit irq_handle(974): aw_haptic->haptic_rtp_mode = 1
03-15 00:26:09.602 I/[haptic_hv]aw8692x_irq_clear(7523): enter
03-15 00:26:09.603 I/[haptic_hv]aw8692x_play_go(7523): enter, flag = 1
03-15 00:26:09.605 I/[haptic_hv]rtp_work_proc(7523): RTP_GO! glb_state=0x08
03-15 00:26:09.626 I/[haptic_hv]aw_file_unlocked_ioctl(2299): cmd=0x5205, arg=0x2
03-15 00:26:09.637 I/[haptic_hv]exit irq_handle(974): aw_haptic->haptic_rtp_mode = 1
03-15 00:26:09.666 I/[haptic_hv]aw_file_unlocked_ioctl(2299): cmd=0x5205, arg=0x5
03-15 00:26:09.708 I/[haptic_hv]aw_file_unlocked_ioctl(2299): cmd=0x5205, arg=0xc
03-15 00:26:09.746 I/[haptic_hv]aw_file_unlocked_ioctl(2299): cmd=0x5205, arg=0x16
03-15 00:26:09.786 I/        (7523): [haptic_hv]reg_val = 0x10, aw_haptic->done_flag = 0, opbuf->status = 0xff done_state = 0x0
03-15 00:26:09.786 I/[haptic_hv]aw_file_unlocked_ioctl(2299): cmd=0x5205, arg=0x21
03-15 00:26:09.826 I/[haptic_hv]aw_file_unlocked_ioctl(2299): cmd=0x5205, arg=0x2d
03-15 00:26:09.866 I/[haptic_hv]aw_file_unlocked_ioctl(2299): cmd=0x5205, arg=0x39
03-15 00:26:09.908 I/[haptic_hv]aw_file_unlocked_ioctl(2299): cmd=0x5205, arg=0x3d
03-15 00:26:09.946 I/[haptic_hv]aw_file_unlocked_ioctl(2299): cmd=0x5205, arg=0x33
03-15 00:26:09.987 I/[haptic_hv]aw_file_unlocked_ioctl(2299): cmd=0x5205, arg=0x27
03-15 00:26:10.026 I/[haptic_hv]aw_file_unlocked_ioctl(2299): cmd=0x5205, arg=0x1b

Screenshots or videos

No response

Solution

No response

Additional context

No response

Acknowledgements

• I've checked device is officially supported and that no support is provided for unofficial devices (for device specific reports and not source related).
• I'm running latest version available on crdroid.net for this device and that the device is still maintainer supported (not flagged unsupported on download page)
• I have searched the existing issues and this is a new and no duplicate or related to another open issue.
• I have written a short but informative title.
• I filled out all of the requested information in this issue properly and understand that not doing so will automatically result in closing of ticket.