Create VibratorFrequencyProfile in Vibrator API.
Create public class to represent the vibrator response for the supported frequency range to the Vibrator public API, with basic implementation that extracts these values from FrequencyMapping. Integrate this data with the result of Vibrator.hasFrequencyControl method, which also checks the HAL capabilities. Also make public the methods to provide resonant frequency and Q-factor of the device. Update the SystemVibrator to handle multi-vibrator scenario and return values when all vibrators have the same configurations. This includes returning the intersection of all vibrator max amplitude measurements in the new profile object. Add validation to HAL values and CTS to cover expected ranges based on the device support for frequency control. Bug: 203785430 Test: android.os.cts.VibratorTest & VibratorInfoTest Change-Id: I0b7cf599ae6039355a0a198f4bdaafb85fb7422c
Loading
Please register or sign in to comment