You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Either I forget or I have to leave before syncing1 finishes. I have to instruct users to find hte app, go to STATUS and switch it to `FOLLOW RUN CONDITIONS'.
Proposal
Allow setting force conditions for n hours. Either by a button under STATUS (better UX) or an app setting to always revert after a period.
Footnotes
The app needs the inital setup to be clicked through (next-next-next), and then continues where it left off. Or some certain devices, battery optimizations killed the radio star. ↩
The text was updated successfully, but these errors were encountered:
100% synced may never happen: a device offline, a conflict, filesystem incompatibility, other issues. On the contrary, the status may start out as 100% synced, but as the local files are scanned and peers exchange metadata, it might go down-and-100% etc.
This is meant to kickstart a was-offline-for-a-while device. Getting to 80% or 90% is success. The rest can happen as part of regular syncing.
Description of the issue
Either I forget or I have to leave before syncing1 finishes. I have to instruct users to find hte app, go to
STATUS
and switch it to `FOLLOW RUN CONDITIONS'.Proposal
Allow setting force conditions for n hours. Either by a button under
STATUS
(better UX) or an app setting to always revert after a period.Footnotes
The app needs the inital setup to be clicked through (next-next-next), and then continues where it left off. Or some certain devices, battery optimizations killed the radio star. ↩
The text was updated successfully, but these errors were encountered: