fix(display): watch direct/partial writes for idle chunks#128
Open
cryptomilk wants to merge 2 commits into
Open
fix(display): watch direct/partial writes for idle chunks#128cryptomilk wants to merge 2 commits into
cryptomilk wants to merge 2 commits into
Conversation
Both watchdogs measured elapsed time since transfer START and fired at a flat 15 minutes. On a weak BLE link (e.g. E1003 with a distant proxy), successful transfers already take 4-10 minutes, so a stalled transfer held the EPD rail powered, BLE connected, and the CPU looping for up to 15 minutes before cleanup. This is a heavy battery drain on a device that's supposed to be mostly asleep. Track time since the last chunk actually received instead, and cut the threshold to 60s of silence. A slow-but-flowing transfer never trips it (the clock resets on every chunk); a genuinely dead one is now cleaned up in ~1 minute instead of ~15.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Both watchdogs measured elapsed time since transfer START and fired at a flat 15 minutes. On a weak BLE link (e.g. E1003 with a distant proxy), successful transfers already take 4-10 minutes, so a stalled transfer held the EPD rail powered, BLE connected, and the CPU looping for up to 15 minutes before cleanup. This is a heavy battery drain on a device that's supposed to be mostly asleep.
Track time since the last chunk actually received instead, and cut the threshold to 60s of silence. A slow-but-flowing transfer never trips it (the clock resets on every chunk); a genuinely dead one is now cleaned up in ~1 minute instead of ~15.