Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

reMarkable executable doesn't work on reMarkable 2 version 3.16.2.3 #113

Open
ershov opened this issue Feb 1, 2025 · 4 comments
Open

reMarkable executable doesn't work on reMarkable 2 version 3.16.2.3 #113

ershov opened this issue Feb 1, 2025 · 4 comments

Comments

@ershov
Copy link

ershov commented Feb 1, 2025

root@reMarkable:~# PATH="$PATH:/opt/bin/:." restream -h 1404 -w 1872 -b 2 -f :mem: > /dev/null
Error: Error while compressing framebuffer stream

Caused by:
    error reading from the input you gave me
@devobern
Copy link

devobern commented Feb 3, 2025

Hi,

I had the same Issue, here is what I did:

I'm not sure if this "feature" was introduced in version 3.16.2.3, but I now have an option on the RM2 to set the system time under Settings → General → Help: About → System time.

For me, it is set to UTC, but I'm actually in UTC+1. Here's what I did:

  1. Set the time on the RM to my actual time (which is also the same as on my PC).
  2. Restarted the RM.

Now, reStream works again!

Oddly enough, the time in the RM settings is reset to UTC after the restart.
-> See for this: #113 (comment)

Hope this helps, cheers

@Eeems
Copy link

Eeems commented Feb 3, 2025

Setting the time there is just to allow you to fix issues where the system is unable to automatically set it's time back to UTC, which breaks things like sync and update. The device expects UTC for this time, and will automatically set it back to the UTC time as part of normal time sync operations.

@ershov
Copy link
Author

ershov commented Feb 4, 2025

Hmm I'm in Australia, so for me it'd be a 10 hours difference.

I've logged into the device and used the date -s command to adjust the date. The result is still the same.

@nkey0
Copy link

nkey0 commented Feb 13, 2025

date adjust and restart helped me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants