Please notice: This article is more than 3 years old
Content, Source code or links may no longer be correct in the meantime.
Please notice: This article is more than 3 years old
Content, Source code or links may no longer be correct in the meantime.
Today I will report a brief description of the battery and power management of Mobian on a Pinephone.
Reading the battery parameters from the console was already quite special. The usual way with upower was not successful and provided only zero values. Without ACPI the readout only worked with:
# cat /sys/class/power_supply/axp20x-battery/uevent
My first measurements: At idle with active mobile network, BT and WLAN and 50% display brightness the power consumption is about 2.5 to 3W. At 100% display brightness it jumps up to 3.5 to 4W each time without any apps in the background. From the desktop perspective this may not sound bad, but in fact it is.
To get a hands-on impression of the power management I made up the following challenge between my old Apple iPhone7 (current iOS 14.2) and the Pinephone with Mobian. At…
…I have taken the time it takes for a device to reach 40%. After exactly 16 minutes the Pinephone broke this limit, while the iPhone still lingered around 47%. The result was expected, but clearly shows how optimisation and a certain product maturity can affect a system.
The WLAN/BT module with its RTL8723CS chip always needs the internal battery - even with external power supply. This is not explained in the very good Wiki1. But a quick look at the construction plans2 revealed the explanation: The module gets its energy directly from the battery, bypassing the X-Power AXP803.3
As I’m replacing the battery of my 6 year old Macbook Pro tomorrow (the blog post on this will follow soon), it reminds me very much of a similar Apple design decision. A Macbook slows down so much when the battery is disconnected that working is hardly possible.
What definitely saves battery power and is a feature for me is the possibility to operate a Pinephone with relatively few connections. Except the connections to my Nextcloud (in the screenshot the host with 130.180…) no further connections to foreign hosts are made. A prerequisite for this is the removal of geoclue if you can dispense with its geolocation services.
That’ s all for today.
Stay healthy!
Tomas Jakobs