Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 412a7fe2 authored by Steven Moreland's avatar Steven Moreland
Browse files

vibrator: example for how to get ID 

Since someone asked, and I was still confused, after discussion, this
is the way things work.

Bug: 173817747
Test: N/A
Change-Id: I2c4e062672a2f2d998479d4f9ae11b7749c2aca6
parent 375f7d74

vibrator/aidl/android/hardware/vibrator/IVibrator.aidl

+4 −1
Original line number Diff line number Diff line
@@ -206,7 +206,10 @@ interface IVibrator { 
     * device/board configuration files ensuring that no ID is assigned to

     * multiple clients. No client should use this API unless explicitly

     * assigned an always-on source ID. Clients must develop their own way to

     * get IDs from vendor in a stable way.

     * get IDs from vendor in a stable way. For instance, a client may expose

     * a stable API (via HAL, sysprops, or xml overlays) to allow vendor to

     * associate a hardware ID with a specific usecase. When that usecase is

     * triggered, a client would use that hardware ID here.

     *

     * @param id The device-specific always-on source ID to enable.

     * @param effect The type of haptic event to trigger.