diff options
| author | 2023-11-03 23:14:11 +0000 | |
|---|---|---|
| committer | 2023-11-09 00:48:37 +0000 | |
| commit | 34fd9425713f83328b6d0723815628b32344ccf1 (patch) | |
| tree | aa9107dc37fa72e68d6b378c4337859987ca97ae /libs/androidfw/FileStream.cpp | |
| parent | 10614f6487059a631cda474e820a6e6ff33e208d (diff) | |
Update incompatible charger checking rule
Look at COMPLIANCE_WARNING_INPUT_POWER_LIMITED instead of
COMPLIANCE_WARNING_OTHER to flag incompatible chargers. The underlying
logic that generates the warning remains the same, what's changed is
the enum that's being used.
The purpose of the change is to have a warning type that better
represents what actually happens and free up COMPLIANCE_WARNING_OTHER
that was intended to act as a fallback reason code.
The flag enable_input_power_limited_warning controls whether to switch
to the new enum, while the flag enable_usb_data_compliance_warning
controls the new enums that are added as FlaggedApi in the framework.
Both flags need to be on to enable the change.
Bug: 308700954
Test: make test RunSettingsLibRoboTests ROBOTEST_FILTER=com.android.settingslib.UtilsTest
Flag: ACONFIG enable_input_power_limited_warning DISABLED
Change-Id: I78b55b74059b93d5a64d77003909c91bd9de9290
Diffstat (limited to 'libs/androidfw/FileStream.cpp')
0 files changed, 0 insertions, 0 deletions