Skip to content

Instantly share code, notes, and snippets.

@picaq
Last active February 17, 2024 01:58
Show Gist options
  • Save picaq/7c3d5ead431e8f1caa63bc04718fb874 to your computer and use it in GitHub Desktop.
Save picaq/7c3d5ead431e8f1caa63bc04718fb874 to your computer and use it in GitHub Desktop.
re-style remarkable2 sleep screens after update

Re-style Remarkable2 sleep screens after update

I got sick of reapplying the sleep screens on my remarkable after every single software update, so here are some aliases to facilliate the process. This also allows quickly swapping out different sleeping screens until you find one that you like.

Skip to: Usage:aliases.sh

  • I store my unix aliases in a separate aliases.sh file, but you can put them in your .bashrc or .zshrc instead.

  • All constants are in ALL CAPS. Update them with your own values before running anything.

  • The IP address to your remarkable may update after a software update. It can be stored in the following format:

    export RM_IP="123.123.123.123"

    This value, along with your password, can be found in:

    Menu → Settings → General → Help → About → Copyrights and Licenses → General Information → GPLv3 Compliance
    
  • In my experience, the password to your remarkable does not change after an update, so it can be hardcoded in rmssh().

  • Ensure the images in your source file path are named suspended.png and poweroff.png

  • If file transfer fails, check your connection: your remarkable might be idle long enough to sleep, or the source image files may be too large. In the latter case, you may reduce the image sizes by reducing image quality, increase the vacuum size in your remarkable, and/or delete some software update images.

  • Your remarkable must be connected to the same wifi network as your computer on the terminal.

  • You can include subfolders and other file types in the source directory to store different screen versions and they will be ignored during the file transfer due to the wildcard *.png.

  • clip.exe in Windows and WSL systems works the same way as pbcopy in Unix. Do not include the alias in line 2 in Unix systems!

Usage:

  1. rmssh copies your password into your clipboard so you can paste it in and press enter/return afterwards to ssh into your remarkable.
  2. cmd + v return or ctrl + v enter to paste when prompted for the password.
    You will see the following after a successful connection and login:
    reMarkable
    ╺━┓┏━╸┏━┓┏━┓   ┏━┓╻ ╻┏━╸┏━┓┏━┓
    ┏━┛┣╸ ┣┳┛┃ ┃   ┗━┓┃ ┃┃╺┓┣━┫┣┳┛
    ┗━╸┗━╸╹┗╸┗━┛   ┗━┛┗━┛┗━┛╹ ╹╹┗╸
    reMarkable: ~/
    
  3. Open a new terminal window while keeping the previous session open.
  4. stylerm copies all of the files stored in the first path specified into the /usr/share/remarkable/ folder in your remarkable.
    Paste the password already in your clipboard when prompted to initiate.
    A successful file transfer will look like this:
    poweroff.png                    100%  160KB   1.7MB/s   00:00
    suspended.png                   100%  419KB   1.4MB/s   00:00
    
# this is only necessary if you are using WSL or anything Windows-based like I am. Do NOT include this if you are using a Unix system!
# alias pbcopy='clip.exe'
# in my experience, the IP address for the remarkable updates after every software update, so I set it as a constant here
export RM_IP="IP.A.D.RESS"
function rmssh() { echo 'PASSWORD' | pbcopy ; ssh root@$RM_IP; yes }
function stylerm() { scp /mnt/c/Users/USER/FOLDER/"ANOTHER FOLDER"/remarkable/*.png root@$RM_IP:/usr/share/remarkable/ }
alias sshrm='rmssh'
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment