Remove EnhancedEstimates isHybird flag from trigger condition
- In some rare cases, EnhancedEstimates will not provide isHybird as true(means EnhancedEstimates can not provide data to us), it will makes low battery warning logic back to the previous trigger flow, remove isHybird condition to make sure we always use the new trigger condition. - Although BatteryStateSnapshot will be created by different EnhancedEstimates data, but we already remove the usage of remaining time as our trigger condition(which provided by EnhancedEstimates) so we are safe to always use new trigger condition with or without EnhancedEstimates data. we should think about refactor the class here in the future. - Use current battery level as notifications string content instead of a fixed value. Bug: 232663250 Bug: 232686016 Bug: 232712770 Test: atest SystemUITests Change-Id: I412be50763db39d364757ae3afc2927467451118
Loading
Please register or sign in to comment