KOReader on rM Paper Pro Move – installation & configuration

[timj91]

TL;DR: I find KOReader on the Move to be an effective solution for reading and annotating ebooks, but am looking for a few solutions for optimizing the experience.

Is anyone else using KOReader on the rM Paper Pro Move? I installed it using the automated installer at http://readmarkable.org/ (which worked, but I'm not sure what to make of the mandatory device registration...). I've started this post in the interest of seeing if anyone can help me configure and optimize KOReader for the Move, as well as document fixes for others who might want to do the same.

The only bug that I have found so far in KOReader on the Move is that if I close the Move's folio (or switch it off with the power button), the KOReader screen shutoff conflicts with the rM software and it shows the "Sleeping" modal, but does not wake up. I have to triple-press the power button to restart the Move. (Workaround: don't close the folio or turn off the power in KOReader—exit out to the rM UI and all is well.) If anyone knows how to fix this, please comment below. It looks like it can be done, but I have not yet deciphered this post (https://github.com/koreader/koreader/issues/8891) to understand how to do it.

Current KOReader configuration research:

• How to change the highlight colors to make the "green" color lighter and easier to read.
• How to format the "Export highlights to Markdown" to include metadata in a format that is immediately usable by Obsidian.

If anyone has any ideas, please share!

[dkyates79]

Hi all, first post here so bear with me.
I just got a reMarkable Paper Pro Move and tried installing KOReader using the READMarkable installer on my Mac. The installer ran through everything and reported success, but AppLoad never appears in the sidebar and I can't access KOReader.

My setup:

reMarkable Paper Pro Move, firmware 3.27.0.87
Macbook Pro M3 Pro(Apple Silicon) Tahoe 26.3

I did some digging via SSH and KOReader is actually on the device at /home/root/xovi/exthome/appload/koreader — the problem is XOVI isn't injecting into xochitl. The installer tries to create a service drop-in at /etc/systemd/system/xochitl.service.d/xovi.conf to set LD_PRELOAD, but it never sticks. Turns out /etc on the Paper Pro Move uses an overlay filesystem that writes to /var/volatile/etc (which is tmpfs and wipes on reboot), and /usr is fully read-only. Even writing directly to /var/volatile/etc/systemd/system/xochitl.service.d/ doesn't surface through the overlay — systemctl cat xochitl never shows the drop-in.

One other thing I noticed — during the tripletap enable.sh step the installer started getting "Authentication failed" SSH errors mid-session even though the password hadn't changed. Not sure if that's related.

Is this a known issue with 3.27? Anyone found a workaround for getting persistent systemd drop-ins working on the Paper Pro Move?

Thanks in advance