Skip to content

v1.1.1-beta

Pre-release
Pre-release
Compare
Choose a tag to compare
@Eeems Eeems released this 02 Sep 02:33
· 341 commits to master since this release
5ff260d

Issues Fixed

  • #17 The clock will now display the correct time in the afternoon.
  • #18 Battery will no longer report levels as higher than they are.
  • #12 Sleep mode will now draw correct, and has been changed to only change the top bar.
  • #9 The configuration file has been renamed to oxide.conf and move out of the /etc/draft folder.
  • Clock will now only attempt to update every minute instead of checking every second.

Warnings

Currently, battery/wifi status will be checked every 3 seconds, but the UI should only change if they have changed. I'm not sure how much this will affect performance. Please let me know on the community Discord if you notice that your battery is draining quicker on this version.

By default the clock will use UTC, if you need to change your timezone you'll need to ssh into the device and use timedatectl set-timezone to change your timezone (e.g. timedatectl set-timezone America/Denver). You can see possible timezones by looking in /usr/share/zoneinfo/ (Don't trust the output of timedatectl get-timezones)).

Upgrade Instructions

  1. Replace the oxide binary on your device.
  2. Rename your conf file to oxide.conf and move it up one directory.

Installation

  1. Copy oxide.tar.xz to your remarkable
  2. Decompress files into one of the following locations
    a. Root filesystem: /
    b. Entware: /opt
  3. If you haven't installed to the root filesystem, copy the oxide.service file to /etc/systemd/system
  4. Edit oxide.service to point it at the correct location of oxide
  5. Reload systemd unit files: systemctl daemon-reload
  6. Disable xochitl: systemctl disable --now xochitl
  7. Enable and start oxide systemctl enable --now oxide

Configuration

Configuration files can be in one of the following locations:

  1. /etc
  2. /opt/etc
  3. /home/root/.config

The configuration folder contains the following:

  • draft/icons/ Folder containing .png files that are used by applications.
  • oxide.conf Application configuration file. The launcher will automatically maintain this file.
  • draft/ Folder containing configuration files for every application entry to show in the launcher.

Oxide will search through all three locations when building a list of applications. So be careful not to duplicate files between all the locations as they will show up multiple times in the applications list in oxide.

Configuration files for an application use the following format:

name=xochitl
desc=The standard environment for reMarkable.
imgFile=xochitl
call=/usr/bin/xochitl
term=killall xochitl

Options:

  • name: Name of the application
  • desc: Description of the application, will show on long press.
  • imgFile: Name of the icon to use.
  • call: Command to run when launching the application
  • term: Command to run when button-capture is used to kill the application

Since this format is based off of the configuration format used by the draft launcher, you can leave entries blank by either omitting them from the file, or setting them to :, or leaving them blank.

Usage

oxide

After you have configured and launched oxide you can access the power menu from the image button on the top right of the screen. This will allow you to put the device to sleep, or to power off the device.
The image button on the top left side of the screen will open up the tools menu. This allows you to either refresh the grid, or to open up the options dialog.

The options dialog will allow you to configure various settings in the application. You have the option to reload the settings from the conf file on disk, or to close the options dialog and save the current settings to disk.

button-capture

Press and hold the left button for 1 second or longer to execute the contents of /tmp/.terminate. Oxide will automatically populate this file when launching an application with the term setting.

Press and hold the right button for 1 second or longer to create a screenshot at /tmp/fb.png. It will then execute /tmp/.screenshot if it exists. Due to how the reMarkable preserves colour information in the framebuffer used to generate the screenshot, there may be colour in the screenshots that are not visible on the reMarkable itself.