Skip to content

v2.4
Compare
Choose a tag to compare
@Eeems Eeems released this 22 May 03:18
· 132 commits to master since this release
v2.4
bf12a75
This commit was signed with the committer’s verified signature.
Eeems Nathaniel van Diepen
GPG key ID: 87F4F19E784573DA
Learn about vigilant mode.

New Features

  • #238 Opt-in crash reporting and analytics
  • #260 Created new shared library to make codebase smaller, and provide an easier API for applications to use

Issues Fixed

  • #239 Launcher will crash if a notification is removed with the API instead of through the UI
  • #246 Task switcher background disappears if you close an application
  • #244 Don't allow importing applications if they are not executable

Known Issues

  • There have been some odd issues reported on the rM2 that haven't been fully validated yet. #135
  • #147 Multiple button press actions do not work in remarkable-hacks

Manual Installation/Upgrade

  1. Copy packges.zip to your remarkable
  2. Decompress files onto a temporary folder
  3. Run opkg install path/to/folder/*.ipk
  4. If you are on a rM2, make sure you have rm2fb installed/enabled/running
  5. Enable the tarnish service: systemctl enable --now tarnish

Automated Installation

  1. Install toltec repository if you haven't already
  2. Run opkg update
  3. Run opkg install oxide
  4. If xochitl or another launcher is enabled, disabled them: systemctl disable --now xochitl
  5. Enable the tarnish service: systemctl enable --now tarnish

Automated Upgrade

  1. Run opkg update
  2. Run opkg upgrade
  3. If xochitl or another launcher is enabled, disabled them: systemctl disable --now xochitl
  4. Enable the tarnish service if it isn't already: systemctl enable --now tarnish

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:

  • oxide.conf Application configuration file. The launcher will automatically maintain this file.

There are two other application specific configuration files that are not intended for user modification. You must stop the tarnish service before modifying either of them.

  1. /home/root/.config/Eeems/tarnish.conf
  2. /home/root/.config/Eeems/decay.conf

Usage

See the website for more information.

Assets 3
Loading