On API 28 and up the ACTION_BATTERY_CHANGED intent contains an extra BatteryManager.EXTRA_BATTERY_LOW.

Using that would allow simplifying the code and making it more robust. We can than only subscribe to the ACTION_BATTERY_CHANGED Intent and still know if the battery is low even when we did not receive the ACTION_BATTERY_LOW intent because kdeconnect started in a BATTERY_LOW condition (e.g. ACTION_BATTERY_LOW was missed)