Repository navigation
Background sync waits for the ring's history pass to finish - #75
Merged
Merged
Conversation
The owner's 2.16.3 export (2026-11-12) confirms the new jring offline logs on hardware. Temperature, SpO₂ and the sensor log all answered with data, in the vendor's order. The same export shows every background sync cut at ~15 s, because RingSyncWorker closed the link on a fixed timer, before those logs were asked for. They only arrived when the app was opened. RingSyncEngine.historyPassRunning (jring: JringHistorySync.isRunning) lets the worker hold the link while the paged pass runs, for up to 90 s more. The overall timeout rises to 150 s. Other families keep the fixed window. The confirmation is recorded in the plan doc. Claude-Session: https://claude.ai/code/session_01P1t1aUqSUPd3whKXmgVm7w
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
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.
Why
The owner's 2.16.3 diagnostics export (2026-11-12) confirms the new jring offline logs on hardware:
0x39,0x40and0x55all answered with data (127, 54 and 85 frames), none of itunknown.The same export also shows that every background sync was cut at about 15 s:
RingSyncWorkerwaits a fixed 15 s after connecting and then closes the link. So the new logs only ever arrived when the app was opened. In the foreground the full three-day chain took about 50 s.What
RingSyncEngine.historyPassRunning(defaultfalse). For jring it isJringHistorySync.isRunning.RingSyncWorkerholds the link while that is true, for up to 90 s more. Its overall timeout rises from 45 s to 150 s. It still yields at once if the app opens.docs/jring-56ff-plan.md.No UI change.
Generated by Claude Code