Floss: Avoid non-empty battery result
Some peripherals don't have BAS profile but have other means to convey the battery level. We have preferences to display the battery level from BAS profile if that exists though. However, sometimes (e.g. after device disconnection) the BAS profile might reports empty battery result and it stays that way even after reconnection. This causes battery conveyed via other means to be meaningless because we use the empty result from BAS instead. Update the behavior to prefer non-empty battery reports. Also, avoid entering empty battery report by providing a remove battery API to remove the entry instead of setting it empty. Bug: 295577710 Tag: #Floss Test: Disconnect/reconnect WH-1000XM3 multiple times. Observe the battery level is always displayed. Change-Id: I10dd8ae8624f001cf539f5e0ac9b29655a76440b
Showing
- system/gd/rust/linux/service/src/iface_battery_provider_manager.rs 5 additions, 0 deletions.../rust/linux/service/src/iface_battery_provider_manager.rs
- system/gd/rust/linux/stack/src/battery_manager.rs 13 additions, 1 deletionsystem/gd/rust/linux/stack/src/battery_manager.rs
- system/gd/rust/linux/stack/src/battery_provider_manager.rs 19 additions, 0 deletionssystem/gd/rust/linux/stack/src/battery_provider_manager.rs
- system/gd/rust/linux/stack/src/battery_service.rs 3 additions, 7 deletionssystem/gd/rust/linux/stack/src/battery_service.rs
Loading
Please register or sign in to comment