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
Hi @GliderGeek et al. I would have liked to discuss by mail or chat, but there are no contact data (:
I was wondering why there were two services, and a duplicate of the utils file, so I read some code.
The reload service seems to react to home.mount, and the normal service reacts to home.mount and the UI to come up xochitl.service.
Now I was wondering when and how often these events rise on a reMarkable. I don't know when reMarkable actually shuts down, as it probably mostly goes into standby?
Is the Pocket sync triggered often enough is my question.
Or might network-up.target actually be a better event, since it probably gets called after each wake-up, and seems to be used by the reMarkable itself to sync.
The text was updated successfully, but these errors were encountered:
Hi @GliderGeek et al. I would have liked to discuss by mail or chat, but there are no contact data (:
I was wondering why there were two services, and a duplicate of the utils file, so I read some code.
The reload service seems to react to
home.mount
, and the normal service reacts tohome.mount
and the UI to come upxochitl.service
.Now I was wondering when and how often these events rise on a reMarkable. I don't know when reMarkable actually shuts down, as it probably mostly goes into standby?
Is the Pocket sync triggered often enough is my question.
Or might
network-up.target
actually be a better event, since it probably gets called after each wake-up, and seems to be used by the reMarkable itself to sync.The text was updated successfully, but these errors were encountered: