Skip to content

v2.2
Compare
Choose a tag to compare
@Eeems Eeems released this 11 Jul 18:33
· 185 commits to master since this release
v2.2
98790e6
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

New Features

  • #191, #168, #111 Add gestures for better rM2 support.
  • #171 When running an application in a chroot, properly catch suspends from sysfs interface.
  • #176 Add onLogin and onFailedLogin script hooks.
  • #140 Add application switcher. This can be opened by swiping from the bottom of the screen.
  • #39 Add screenshot viewer application.
  • #179 Add splashscreens when launching applications.

Issues Fixed

  • #203 Fix issue where you could skip the lockscreen with the leftAction (hold left button, or swipe from left of screen).
  • #195, #198 Fix issue where icons wouldn't display properly on 2.6+
  • #173 When running without rm2fb on a rM2, start xochitl instead.
  • #155, #115 Clear touch input when switching between applications.
  • #164 Increase maximum "Sleep After" time to 6 hours.
  • #132 Remove kill button from process manager. Tapping on a row will now prompt to kill the process.

Known Issues

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

Warnings

There is currently no way to change your PIN after you've set it. You can do the following over SSH to clear your PIN and the lockscreen will prompt for a new pin the next time it's shown:

systemctl stop tarnish
rm /home/root/.config/Eeems/decay.conf
systemctl start tarnish

If you change the lockscreen application to another application, it will need to make sure to launch the launcher application via the system service after validating the user.

When importing applications from draft, it will fail to import applications that have configured the call= option to use arguments. This is due to oxide only supporting pointing at a single file for an application without arguments.

As part of implementing #38 users have lost the ability to choose what order applications will display. There is a plan to add this back in a future release as part of #11.

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. It's been quite a few releases and nobody has said anything, so you are likely fine.

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)). You can install more timezones through toltec by installing the various zoneinfo-* packages.

reMarkable 2 support requires rm2fb.

Manual Upgrade

  1. Copy packges.zip to your remarkable
  2. Decompress files onto a temporary folder
  3. Run opkg install path/to/folder/*.ipk
  4. Enable the tarnish service: systemctl enable --now tarnish

Automated Upgrade

  1. Run opkg update
  2. Run opkg upgrade
  3. Enable the tarnish service: systemctl enable --now tarnish

Manual Installation

  1. Copy packges.zip to your remarkable
  2. Decompress files onto a temporary folder
  3. Run opkg install path/to/folder/*.ipk
  4. Enable the tarnish service: systemctl enable --now tarnish

Automated Installation

  1. Add the toltec repository to your entware install
  2. Run opkg update
  3. Run opkg install oxide
  4. Enable the tarnish service: 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 wiki for usage information.

Assets 3
Loading