diff options
| author | 2024-10-24 17:23:08 +0000 | |
|---|---|---|
| committer | 2024-11-12 09:01:23 +0000 | |
| commit | bf0dd5d7ea8fcdfb2daacab8527f585da3acaae3 (patch) | |
| tree | 75b59881e47322467bc93a182a31acaeb1c82bf9 /libs/androidfw/AssetsProvider.cpp | |
| parent | 616d04cc3a7a03af07fba26683806252004aa60e (diff) | |
Dynamically disable View-based rotary haptics
Before this change, View-based rotary haptics was configured for the
entire device, controlled by an XML config. As long as this config is
enabled, the ScrollFeedbackProvider's (SFP) rotary feedback was also
disabled (to avoid duplicate rotary haptics).
With this change, the decision to enable/disable the View-based rotary
haptics will be View-specific. If we detect that a View implementation
is directly using the SFP API, we will favor the SFP API and disable the
View-based rotary haptics. This allows us to continue providing rotary
haptics for View implementations without SFP integration, while cleanly
disabling rotary View-based rotary haptics in cases where SFP has been
integrated to the specific View.
Bug: 377998870
Test: manually on a widget extending View, with SFP integration
Test: manually on a widget extending View, with no SFP integration
Test: manually on a widget NOT extending View, with SFP integration
Test: atest RotaryScrollHapticsTest HapticScrollFeedbackProviderTest
Flag: android.view.flags.dynamic_view_rotary_haptics_configuration
Change-Id: Iac63b5f7046f216f8ec958245021da5fa0a40fa7
Diffstat (limited to 'libs/androidfw/AssetsProvider.cpp')
0 files changed, 0 insertions, 0 deletions