Hi,
I have read the issue Battery drain in deep suspend but IMHO the answer to switch to hibernate is not really convincing. I have a Framework Laptop DIY Edition (11th Gen Intel® Core™) with an up to date Debian testing installed (current Linux kernel is 6.0.0). I compared the Frame.work with some “random” laptop I have at hand. On both laptops I called date; acpi
closed the lid, left the laptops alone for a couple of hours, reopened and again called date; acpi
to know what time was left and see what the battery status might be. Here are the results:
Frame.work
frame.work:~ $ acpi
Battery 0: Discharging, 100%, 38:33:15 remaining
frame.work:~ $ date
Mo 14. Nov 09:03:17 CET 2022
frame.work:~ $ acpi
Battery 0: Discharging, 73%, 04:03:00 remaining
frame.work:~ $ date
Mo 14. Nov 15:00:55 CET 2022
### closing lid again
frame.work:~ $ acpi
Battery 0: Discharging, 55%, 05:23:12 remaining
frame.work:~ $ date
Mo 14. Nov 18:22:16 CET 2022
Huawei Matebook 13
matebook:~ $ acpi
Battery 0: Charging, 96%, 00:16:31 until charged
matebook:~ $ acpi
Battery 0: Discharging, 96%, 05:03:42 remaining
matebook:~ $ date
Mo 14. Nov 09:03:02 CET 2022
matebook:~ $ acpi
Battery 0: Discharging, 93%, 06:23:38 remaining
matebook:~ $ date
Mo 14. Nov 15:01:00 CET 2022
### closing lid again
matebook:~ $ date
Mo 14. Nov 18:16:08 CET 2022
matebook:~ $ acpi
Battery 0: Discharging, 92%, 05:28:43 remaining
So if I compare both laptops I could say that the Frame.Work is loosing about 50% battery in about 12 hour suspend while the Matebook looses only 10% (both roughly estimated.)
I know hibernate could do better here but hibernation takes more time and is unacceptable for short breaks. IMHO there should be some improvement if the Frame.Work is five times worse than some random laptop I had access to.
Kind regards, Andreas.