2020-05-26 17:55:47 +01:00
|
|
|
set(debug_file_SRCS)
|
|
|
|
|
ecm_qt_declare_logging_category(
|
|
|
|
|
debug_file_SRCS HEADER plugin_battery_debug.h
|
|
|
|
|
IDENTIFIER KDECONNECT_PLUGIN_BATTERY CATEGORY_NAME kdeconnect.plugin.battery
|
|
|
|
|
DEFAULT_SEVERITY Warning
|
|
|
|
|
EXPORT kdeconnect-kde DESCRIPTION "kdeconnect (plugin battery)")
|
|
|
|
|
|
2013-08-13 23:03:46 +01:00
|
|
|
set(kdeconnect_battery_SRCS
|
|
|
|
|
batteryplugin.cpp
|
2020-05-26 17:55:47 +01:00
|
|
|
${debug_file_SRCS}
|
2013-08-12 15:09:52 +01:00
|
|
|
)
|
|
|
|
|
|
2021-06-28 19:33:52 +01:00
|
|
|
kdeconnect_add_plugin(kdeconnect_battery SOURCES ${kdeconnect_battery_SRCS})
|
2013-08-13 23:03:46 +01:00
|
|
|
|
2014-09-22 08:16:17 +01:00
|
|
|
target_link_libraries(kdeconnect_battery
|
|
|
|
|
kdeconnectcore
|
2022-10-29 15:51:41 +01:00
|
|
|
Qt${QT_MAJOR_VERSION}::DBus
|
Finally, we have support for sending out Battery information.
## Summary
The core idea is as follows:
1. When a Link loads the BatteryPlugin, we query Solid for a list of batteries.
1. If the list is empty, we print a warning message and return quickly
2. Otherwise, we connect *two signals* to every object in that list
2. We send out a single new NetworkPacket as soon as we've processed that list
3. When either of those two signals emits, we send another new NetworkPacket
### Multi-battery Support
BUG: 357193
To handle devices with multiple batteries (requested in that bug), we average
together the battery percentages. This also includes a new field in the packet for
'number of batteries' called `batteryQuantity`. For backwards compatibility, we can
assume it has a default value of one.
This should ensure we support
- devices with no batteries at all (like many desktop machines)
- devices with hot-pluggable batteries (like those laptops with detachable screens)
### Concerns
Note that the implementation isn't perfect.
We'll need some new localizable text to make it clear that we now support sending
battery status information.
Then there's a rather significant question: maybe we should have two battery plugins
on each client, like we do for the `findmyphone`/`findthisdevice` plugins?
## Test Plan
We need to ensure that other clients (including those using the Android codebase)
will respond correctly. The main things to look at are
1. are these new packets sent when the plugin is enabled, and not sent when it's disabled?
2. is the charge percentage accurate?
3. is the charge state (charging, discharging, or full) accurate?
and
4. do we see the correct number of warnings for low-battery?
2020-04-13 06:54:11 +01:00
|
|
|
KF5::Solid
|
2014-09-22 08:16:17 +01:00
|
|
|
KF5::I18n
|
|
|
|
|
)
|