Prerequisites
rockboxdinstalled and on your$PATH- A Bluesky account (used as the Rocksky identity)
Step 1 — Log in
6996 captures the token and writes it to ~/.config/rockbox.org/token. You only need to do this once per machine.
Verify the login succeeded:
Step 2 — Push your settings
Configure your audio settings (settings.toml, or via the web/desktop UI), then upload them:
~/.config/rockbox.org/settings.toml are uploaded:
| Section | Fields synced |
|---|---|
| Equalizer | eq_enabled, eq_precut, eq_band_settings (cutoff / gain / Q per band) |
| Crossfade | crossfade, fade_in_delay, fade_in_duration, fade_out_delay, fade_out_duration, fade_out_mixmode |
| ReplayGain | replaygain_settings.type, replaygain_settings.preamp, replaygain_settings.noclip |
| Tone | bass, treble, balance, channel_config |
music_dir, audio_output, etc.) are never uploaded.
Step 3 — Pull your settings on another device
Log in on the second device, then pull:settings.toml without touching any other fields. Restart rockboxd to apply them.
Sharing settings publicly
Any user’s settings can be pulled without logging in by passing their DID or Bluesky handle:Token management
| File | Contents |
|---|---|
~/.config/rockbox.org/token | Bearer token (plain text) |
Troubleshooting
“Session expired or invalid” — the stored token has been revoked or expired. Runrockboxd login <handle> again.
“No settings file” on settings push — pull first to create the file, or configure settings.toml manually and run push again.
Port 6996 already in use — the login callback server cannot bind. Stop whatever is listening on that port and retry.