Frequently Asked Questions#

What kind of telemetry do you have?#

As of 2.4, Oxide has opt-in basic telemetry. The first time you run Oxide you’ll be asked what level of telemetry you’d like to enable. This feature can be disabled at runtime, or completely removed when compiling the application manually. The telemetry is used for the following:

  • Automated crash reporting.

  • Determining how quickly new versions are used by users.

  • Determining what older versions are still in use.

What kind of information is collected by telemetry?#

  • The device machine-id, but anonymised through

    sd_id128_get_boot_app_specific. This is used to uniquely identify the devices connecting so that I can properly determine what percentage of devices are on specific versions. It can also allow me to determine what crash reports are sent by a user if they are willing to share the anonymised value from their devices.

  • OS version via the contents of /etc/version on the device.

    This helps ensure that the OS version is properly taken into account when investigating a crash.

  • Name of application and version. i.e. rot@2.4

    This ensures that the correct application is investigated for a crash.

  • Minidump of the crash.

    This hopefully provides enough information that a crash can be replicated and the specific piece of code that is causing issues can be identified.

How can I disable the telemetry?#

As of 2.6 you can disable telemetry with the following commands:

xdg-settings set telemetry false
xdg-settings set crashReport false
xdg-settings set applicationUsage false

On 2.5 or earlier you can use the following commands to disable telemetry:

rot settings set telemetry 'bool:false'
rot settings set crashReport 'bool:false'
rot settings set applicationUsage 'bool:false'

Alternatively, you can compile the applications manually without the sentry feature enabled.

I’m installing without Toltec and nothing displays?#

Oxide (and most other applications) on the reMarkable 2 requires rm2fb do display to the screen.

How do I change my pin after I’ve set it?#

As of 2.6 you can change your pin to any 4 numbers with the following command:

xdg-settings set pin <new-pin>

For example:

xdg-settings set pin '0123'

As of 2.6 you can clear your pin to skip the lock screen with the following command:

xdg-settings set pin ''

On 2.5 or earlier you can use the following commands to manually clear your pin:

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

You will then be prompted to enter a new pin

Not all of my applications are listed?#

Oxide doesn’t import draft applications automatically, you can import them by using the menu on the top left of the launcher. If your application is still not listed, you may need to review the device logs to determine why it’s failing to load. If an application is configured in draft to pass arguments in the call= line, it will fail to import as this is not supported by Oxide.

You can check for errors with your application registration files with the following command:

desktop-file-validate /opt/usr/share/applications/*.oxide

How do I review my device logs?#

Most logs on the device are accessable from the command line through journalctl. To get at the logs for Oxide’s programs, and any application you run through Oxide, you can run the following:

journalctl -eau tarnish

As of Oxide 2.5, you can now get logs for specific applications with the following, where codes.eeems.oxide is the name of the application as it’s been registered.

journalctl -eat codes.eeems.oxide

To get logs for just the Background Service (tarnish), you can use the following command:

journalctl -eat tarnish

Where are the configuration files?#

The primary configuration file can be found in one of the following locations:

  1. /etc/oxide.conf

  2. /opt/etc/oxide.conf

  3. /home/root/.config/oxide.conf

Other configuration files can be found in /home/root/.config/Eeems/.

Can I disable a specific gesture?#

Yes, you can disable specific gestures with the following commands:

# Disable swipe from left edge of the screen
rot system call setSwipeEnabled 'int:1' 'bool:false'
# Disable swipe from right edge of the screen
rot system call setSwipeEnabled 'int:2' 'bool:false'
# Disable swipe from bottom of the screen
rot system call setSwipeEnabled 'int:3' 'bool:false'
# Disable swipe from top of the screen
rot system call setSwipeEnabled 'int:4' 'bool:false'