v2.8.4

Other Changes

• Update sentry to 0.7.6 (#370)

Known Issues

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

v2.8.3

Issues Fixed

• Disabled logging that was providing some information to me in telemetry that could be used to identify a user based on wireless networks around their device. See the FAQs for more information on telemetry in oxide.
• Reduced overall logging for non-debug builds.

Known Issues

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

v2.8.2

Issues Fixed

• Fix tarnish segmentation fault when running from package build #354

Known Issues

• There have been some odd issues reported on the rM2 that haven't been fully validated yet. (#135)
• Multiple button press actions do not work in remarkable-hacks (#147)
• No touch input is detected for applications when an external keyboard is connected (#259)

v2.8.1

Issues Fixed

• Fix memory leak in wifi handling #353

Known Issues

• There have been some odd issues reported on the rM2 that haven't been fully validated yet. (#135)
• Multiple button press actions do not work in remarkable-hacks (#147)
• No touch input is detected for applications when an external keyboard is connected (#259)

v2.8

New Features

• Support landscape mode for all Oxide applications #337 #342
• Display suspend screens in landscape when the type folio is attached #337
• Add keyboard shortcuts #337
• Taking a screenshot will now show a notification when the screenshot is done #337
• Depend on new sysfs_preload package to make sure that applications will use systemd to suspend the device. #336

Issues Fixed

• Pen events didn't trigger on all UI elements #310

Other Changes

• Update sentry has been updated to 0.7.0 #338
• Automated testing of packages #335

Known Issues

• There have been some odd issues reported on the rM2 that haven't been fully validated yet. (#135)
• Multiple button press actions do not work in remarkable-hacks (#147)
• No touch input is detected for applications when an external keyboard is connected (#259)

v2.7

New Features

• Allow users to select the system locale and timezone from the settings menu. This does not affect the language or timezone settings in xochitl. #308
• Default auto suspend timeout changed to 5 minutes #232
• Buttons will no longer indicate which one is selected while entering your pin. #311
• Add a new setting to allow automatic locking of the device. #278
• Use rfkill on wifi disable to attempt to use less power #315
• Fix issue where wireless connection information would sometimes not be available #318

Issues Fixed

• Fix issue where draft files missing the name property, breaking app import.
• Fixed issue where notification text would cut off if it was on more than one line. #304
• A notification will now be displayed if tarnish failed to start the lockscreen or launcher #199
• Automatically remove debugging from release builds #315
• Fix issue where button and pen logic would stop handling events #315
• Fix issue where auto suspend would not temporarily disable while plugged in with usb #145

Other Changes

• erode, tarnish, decay, and corrupt have been merged into the oxide package
• fret, and anxiety have been merged into the oxide-extra package
• rot has been merged into the oxide-utils package
• Added new liboxide-dev package

Known Issues

• There have been some odd issues reported on the rM2 that haven't been fully validated yet. (#135)
• Multiple button press actions do not work in remarkable-hacks (#147)
• Keyboard folio is not currently tested/supported (#297)
• No touch input is detected for applications when an external keyboard is connected (#259)

v2.6

New Features

• Added new helper executables to make it easier for application development and scripting (#290 #299)

Issues Fixed

• Fixed multitouch handling to avoid issues with the onscreen keyboard (#298)
• Fix issue that would cause crash while reading battery information on a reMarkable 2 with the mainline kernel (#302)

Other Changes

• Some shared settings have been moved to a new location. This migration will happen automatically. (#293)

Known Issues

• There have been some odd issues reported on the rM2 that haven't been fully validated yet. (#135)
• Multiple button press actions do not work in remarkable-hacks (#147)
• Keyboard folio is not currently tested/supported (#297)
• No touch input is detected for applications when an external keyboard is connected (#259)

v2.5

New Features

• Added meta.h, json.h, power.h, slothandler.h, and debug.h to liboxide (#268 #282 #283)
• Added new optionial notify-send command line tool (#282)
• Application logs now are identified using systemd-journal identifiers to make it easier to debug (#284)
• Display a notification while a screenshot is being taken so that users know that it has triggered (#286)

Issues Fixed

• Xochitl syncing didn't work in a chroot (#270)
• Inputs were not cleared on suspend (#271)
• Runing xochitl with remarvin doesn't allow it to see the files (#275)
• Charger status isn't properly displayed on newer versions of the OS (#279)
• Launcher and task switcher don't properly report when an icon is changed on an application (#285)

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

v2.4

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.

v2.3

New Features

• #208 Feedback when shutting down. This will display a message letting you know what applications are being stopped while tarnish is stopping.
• #224 Allow configuration of swipe length (Thanks @nhnt)
• #184 Added cpu usage, and memory usage to the process manager
• #118 Enhanced notifications
  • Added notification created date to the API
  • Display information about how long ago a notification was created in the notification popup
  • Display icon for notification in the launcher's notification popup
  • Display icon when showing notification on top of other applications
  • Added default icon for notifications
• Swipe enabled/disabled status now survives reboots
• #67 Added a website! You can check it out at oxide.eeems.codes
• Moved all the wiki content to the website

Issues Fixed

• #225 Fix issue where auto sleep settings were not properly saved (Thanks @nhnt)
• #159 Fixed issue where applications are sorted based on the hidden "name" field instead of the display name.
• #216 Fixed issue where Oxide didn't play nice with rmfakecloud
• #229 Fixed issue where Oxide didn't play nice with templatectl (Thanks @bkirwi)
• #228 Fixed issue where Xochitl failed to launch when a custom rm2fb.conf was used for rm2fb (Thanks @murchu27)
• #234 No longer depend upon a bug in the kernel for detecting the touchscreen (Thanks @alistair23)
• #110 Fix issue where wifi is reconnected when tarnish is started, instead of staying connected.
• #222 Fix issue where wifi signal isn't shown on the rM2
• #161 Fixed issue where unlocking with no pin could get you to a broken state

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
• #239 Launcher will crash if a notification is removed with the API instead of through the UI

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.

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 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.