Display is now correctly updated with fixed fps. #1152
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes for slower display refresh rate
Description
The e-ink display is updated very frequently whenever the state of the pwnagotchi changes.
This effectively makes the config parameter
ui.fps
useless as changes of the state are more frequent than the refresh rate. I think a too high refresh rate is bad for the display, so I would like to give users the opportunity to change how often the display is refreshed.With the new code, the display is not refreshed under a fixed time that is given by the parameter
ui.fps
:However, the caveat is that not all states and information are displayed and some information will therefore be lost.
The user has still the possibility to choose
ui.fps = 0
(default) which shows all states and does not suppress information.Note that the web interface is not affected by this limit of the refresh rate. In the web-ui still all states and information are shown. So if in doubt, what the device is doing, the user can check the web-ui.
Motivation and Context
Solves the issue that
ui.fps
does not have much influence on the refresh rate.Types of changes
Checklist:
git commit -s