[Android Q&A, Help & Troubleshooting] dferreira:
Look at that?

ferreira@pikatchu:~/builds$ adb logcat | grep vibrator
- waiting for device -
02-12 06:33:20.520 1 1 I [1:swapper/0][haptic_hv][3492]vibrator_init: enter
02-12 06:33:20.520 1 1 I [1:swapper/0][haptic_hv][3521]vibrator_init: loaded in leds_cdev framework!
02-12 06:33:20.597 1 1 W [1:swapper/0]qcom,qpnp-vibrator-ldo 1c40000.qcom,spmi: qcom,pmi632@3:qcom,vibrator@5700: Led vibrator renamed to vibrator_1 due to name collision
02-12 06:33:20.597 1 1 I [1:swapper/0]qpnp_vibrator_ldo_probe: Vibrator LDO successfully registered: uV = 3000000, overdrive = disabled
02-12 06:33:23.673 1 1 I [1:init]: Parsing file /vendor/etc/init/vendor.qti.hardware.vibrator.service.rc...
02-12 06:33:25.137 1 1 I [1:init]: Command 'write /sys/class/leds/vibrator/trigger transient' action=init (/system/etc/init/hw/init.rc:448) took 0ms and failed: Unable to write to file '/sys/class/leds/vibrator/trigger': Unable to write file contents: Invalid argument
06-23 21:23:38.003 1 1 I [1:init]: starting service 'vendor.qti.vibrator'...
06-23 21:23:38.011 1 1 I [1:init]: ... started service 'vendor.qti.vibrator' has pid 1726

and we got VIBES!

06-23 21:27:14.998 1726 1726 D vendor.qti.vibrator: QTI Vibrator off
06-23 21:27:15.014 1726 15193 D vendor.qti.vibrator: Notifying on complete
06-23 21:27:15.785 1726 1726 D vendor.qti.vibrator: Vibrator on for timeoutMs: 356
06-23 21:27:15.803 1726 15269 D vendor.qti.vibrator: Starting on on another thread
06-23 21:27:16.017 1726 1726 D vendor.qti.vibrator: QTI Vibrator off
06-23 21:27:16.160 1726 15269 D vendor.qti.vibrator: Notifying on complete
06-23 21:27:19.633 1726 1726 D vendor.qti.vibrator: Vibrator on for timeoutMs: 10
06-23 21:27:19.645 1726 1726 D vendor.qti.vibrator: QTI Vibrator off
06-23 21:27:19.647 1726 15610 D vendor.qti.vibrator: Starting on on another thread
06-23 21:27:19.658 1726 15610 D vendor.qti.vibrator: Notifying on complete
06-23 21:27:19.665 1726 1726 D vendor.qti.vibrator: QTI Vibrator off
06-23 21:27:24.172 1726 1726 D vendor.qti.vibrator: Vibrator on for timeoutMs: 14
06-23 21:27:24.173 1726 16130 D vendor.qti.vibrator: Starting on on another thread
06-23 21:27:24.184 1726 1726 D vendor.qti.vibrator: QTI Vibrator off
06-23 21:27:24.187 1726 16130 D vendor.qti.vibrator: Notifying on complete
06-23 21:27:24.243 1726 1726 D vendor.qti.vibrator: QTI Vibrator off
06-23 21:27:40.711 1726 1726 D vendor.qti.vibrator: Vibrator on for timeoutMs: 10
06-23 21:27:40.715 1726 17888 D vendor.qti.vibrator: Starting on on another thread
06-23 21:27:40.725 1726 17888 D vendor.qti.vibrator: Notifying on complete
06-23 21:27:40.725 1726 1726 D vendor.qti.vibrator: QTI Vibrator off
06-23 21:27:52.394 1726 1726 D vendor.qti.vibrator: Vibrator on for timeoutMs: 350
06-23 21:27:52.397 1726 18966 D vendor.qti.vibrator: Starting on on another thread
06-23 21:27:52.745 1726 1726 D vendor.qti.vibrator: QTI Vibrator off
06-23 21:27:52.747 1726 18966 D vendor.qti.vibrator: Notifying on complete
06-23 21:27:52.994 1726 1726 D vendor.qti.vibrator: Vibrator on for timeoutMs: 350
06-23 21:27:53.088 1726 19028 D vendor.qti.vibrator: Starting on on another thread
06-23 21:27:53.438 1726 19028 D vendor.qti.vibrator: Notifying on complete
06-23 21:27:53.439 1726 1726 D vendor.qti.vibrator: QTI Vibrator off
06-23 21:28:02.529 1726 1726 D vendor.qti.vibrator: Vibrator on for timeoutMs: 10
06-23 21:28:02.530 1726 19401 D vendor.qti.vibrator: Starting on on another thread
06-23 21:28:02.540 1726 19401 D vendor.qti.vibrator: Notifying on complete
06-23 21:28:02.541 1726 1726 D vendor.qti.vibrator: QTI Vibrator off

However the call vibration is weak and short :-/ what are we missing?

@damianmqr @vbhai