Scrambled stream on 3.7

[cgbaker]

I just installed goMarkableStream for the first time. My remarkable firmware is up-to-date, running 3.7.0.1930. I installed v0.13 of goMarkableStream. After running the server and connecting, I get the following in my browser:

I've verified this on Safari, Brave, and Firefox on macOS; and Brave on Android. The only output from goMarkableStream are TLH handshake errors (remote error: tls: unknown certificate); there are no error in the browser JS console.

[owulveryck]

I did not update yet as I needed to stream and couldn't risk a break yet (as I have little time to fix it)

Does any user can confirm that they have the same issue with 3.7?

[cgbaker]

Let me know what I can do to help. If there's debugging instructions somewhere, I can take a shot at investing this.

On Thu, Nov 9, 2023, 12:50 Olivier Wulveryck @.***> wrote:

I did not update yet as I needed to stream and couldn't risk a break yet (as I have little time to fix it)

Does any user can confirm that they have the same issue with 3.7?

— Reply to this email directly, view it on GitHub https://github.com/owulveryck/goMarkableStream/issues/84#issuecomment-1804391934, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAMY6T347FPO3KJLPHYUW5LYDUQXXAVCNFSM6AAAAAA7FA5XR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBUGM4TCOJTGQ . You are receiving this because you authored the thread.Message ID: @.***>

[owulveryck]

What I will do is extract the memory region and search for the image in this region.

• First, I am extracting an image of the memory using a set of dd commands on the reMarkable.

  • Find the memory space of the virtual framebuffer with cat /proc/$(pidof xochitl)/maps (the memory space is located right after the /dev/fb0 definition).
  • Extract a picture, for example: dd if=/proc/$(pidof xochitl)/mem of=full_memory_region.raw count=10513152 bs=1 skip=$((0x763a2004)) if 0x763a2004 is the address you've found. Note: Since version 3.6, the image is set on every other pixel, so we need to grab more data (hence the higher count).

• Then, I am using the exploration code to assist me in the quest for the picture.

You can try to do this, and if you eventually have a picture, send me the "exploration" code. Or you can send me the full_memory_region.raw containing an image so I can play with it without updating my reMarkable :D

References:

• Streaming the reMarkable 2, which explains the basic principle of grabbing the image from the memory.
• Evolving the Game: A clientless streaming tool for reMarkable 2, a more recent article about the current architecture (but does not change the way to grab the picture).

[cgbaker]

Thanks, I should have some time this weekend. 👍

[owulveryck]

I just updated my reMarkable this morning, and I don't have the problem:

I tried to download a fresh 0.13 version from github, and so far it is working.

[RedTartan04]

Also no problems here with rM 3.7.0.1930 and goMS 0.13, Firefox on macOS 12.7

[code-hunger]

A few days ago I updated to the newest version of reMarkable, 3.8., and I can still successfully present my screen with goMarkableStream.

I came to this thread because initially it didn't work, but then it turned out I cannot connect to RM and use ethernet at the same time. I have to be on Wifi for some reason.

[owulveryck]

Ok, I close this issue, @cgbaker feel free to reopen it if you are still facing this issue

[cgbaker]

Still seeing it after a reboot, after updating to reMarkable 3.8.2.1965 and goMarkableStream 0.17. I'll try to find some time to debug, haven't had a chance. (I did try connecting over the same wireless networking, it didn't change anything.)