Eeems-Org / Eeems-Org/oxide

Shutdown the rM if on battery and battery level is dropping below a threshold.

Open
#153 5 comments 0 reactions 1 assignee Claimed by @Eeems View on GitHub
enhancement
Dominant language
C
Stars
281
Forks
25
PR merge metrics
No merged PRs in 30d

Description

I guess the title says it all.
Right now, with autosuspend off, the battery will be completely drained. The rM seems to have a safety feature during charging, which avoids turning on the rM below a certain battery level (pretty much known from Android devices too).
However, the rM does not indicate charging or activity during that stage. That means people fear they have a broken or bricked device, esp. as the device powers off and the last image (possible oxide) remains on the eink-screen. I am not sure if it powers of controlled or simply power off mid-running due to power loose.

How to fix this right now:
After about 5-10min charging, one can turn on the rM again.

What to do:
A watchdog should control the battery level and if it drops below a certain threshold being operated on battery:
a) the rM should be shutdown in an "ordered way" (saving, housekeeping, shutdown) and power off.
b) this "ordered way" should contain a power-off screen to notify the user that no reactions can be expected and that the device need to be charged first
c) The watchdog could send warnings starting from a slightly higher threshold (blinking battery icon, notification, etc.) to create awareness that the device need to be charged very soon.

EDIT: corrected the wording... auto poweroff -> autosuspend

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.