Renaming Frequency Profile APIs
To prepare for the implementation of PWLE v2, which requires a new FrequencyProfile, we're renaming the existing profile to avoid naming conflicts: - VibratorFrequencyProfile -> VibratorFrequencyProfileLegacy - VibratorInfo.FrequencyProfile -> VibratorInfo.FrequencyProfileLegacy The legacy APIs were never made part of the public API, so this renaming should not affect external developers. Bug: 347034419 Flag: android.os.vibrator.normalized_pwle_effects Test: atest FrameworksVibratorCoreTests Change-Id: I57bd2768d1253537a4a7cfeef00f111fa3989457
Loading
Please register or sign in to comment