290496e94e35d1bc804aad4ef7f7d04ee5c86eea
When this code got refactored the check for severe warnings accidentally had the time remaining being compared against the percentage value of the severe warning threshold. Unfortunately this meant that it was impossible to mark the severe level warning as shown and could result in multiple triggerings. This change makes it so everything is compared with the appropriate type of value again. Test: PowerUI Tests pass Bug: 129730217 Change-Id: Ic8bdabf1c70e49d117210bb80f1ca0a0d7684617
…
Merge "Relaxed nullability requirements for setTintMode APIs for both PorterDuff.Mode and BlendMode"
Merge "Switch android.test and junit classes to use UnsupportedAppUsage" am:
7bb0bcd305 am: b5ccf0e21c
…
Description
No description provided
Languages
Java
73.7%
Kotlin
14%
PowerBuilder
5.8%
C++
5.2%
AIDL
1%