Core with slot C enabled
Follow the four steps above. Maintenance and confirmation are automatic. Later R1 signed updates use this same process.
RC15 installer-fix ISO is a separate test download. It is for a fresh, disposable installation and erases the OS disk you select. Do not upload an ISO to Core’s application updater or reinstall a working Core to apply it. Native installed GUI is not included. Candidate ISO and test status.
BRIMSTONE CORE R1 · 1.0.0-rc.16 · 7 NOVEMBER 2026
Update Core.
Keep your collection.
RC16 combines catalogue and bootleg/video corrections, bounded artwork delivery, native MS200 volume, Meridian control visibility and the high-resolution PCM planning hotfix. Install the complete signed candidate through the trusted update route only while Core is idle. Original media, saved queues and quality profiles are retained.
Release candidate · planned 1.0.0 launch: 14 November 2026. Final release remains subject to the remaining checks.
Already have Core? Use the update archive, not the fresh installer. A fresh installation erases the system disk you select; an application update preserves persistent DATA, media, accounts and metadata.
RC16 test status: 1,700 tests passed on the exact signed runtime, with zero failures and 167 skips. The normal update through Recovery C, slot-B boot and automatic confirmation are verified on the Home VM10000 test system, with all 473 installed application files and preservation of saved queues, metadata, preferences and quality settings checked. Physical hardware volume-change listening and full-library 4 GiB qualification remain outstanding; native installed GUI is not included. Full evidence and limitations. If validation refuses the signature, baseline or readiness, stop rather than bypassing it.
FOR CORE WITH THE SLOT-C UPDATER INSTALLED
One update.
Core handles the rest.
The new R1 installer includes the trusted slot-C updater. Existing installations may have it from a separate support setup. The updater decides the route; you do not need to choose a boot slot yourself.
Finish what is running
Finish playback, ripping, recording, imports and downloads. Leave Core connected to power.
Upload and activate
Open Settings → Updates & Recovery. Upload the complete signed
.tar.gzarchive without extracting it. Check the verified version is 1.0.0-rc.16, then choose Activate.Choose Restart Core
Core makes its database backup, boots maintenance slot C, updates the inactive system slot and boots back into the new Core. Allow both restarts to finish.
Check your music
Refresh the Core page. Check the installed version, open an album and try your usual speaker. A healthy exact-version boot is confirmed automatically. Your previous system slot remains available for rollback.
Let Core select C. Do not manually boot Recovery C to upload or run a patch. The signed package and backup must be queued by the running Core first.
WHICH CORE ARE YOU UPDATING?
The right route for your installation.
A version number alone does not tell you which privileged updater has been installed. An ordinary application archive cannot silently replace that trusted component.
Earlier Core with the A/B web updater
Upload the same signed update in Settings and follow the route your installed helper offers. It stages the inactive A/B application. After restarting and checking playback, use Confirm update if shown.
The application patch preserves that earlier helper; it does not add C automatically. Contact support for the separate one-time C setup.
Rev29 / Rev48 without the web helper
Use the administrator-console instructions below for the first update. A modified or unknown installation must be reviewed rather than forced through.
First-update instructions ↗Core running inside LXC
A container has no independent A/B/C boot slots. Use its managed application update or administrator-supported native-service update. Do not run the disk installer or A/B patch command inside LXC.
WHAT R1 1.0.0-rc.16 INCLUDES
The current Core, brought together.
Playback and podcasts
Earlier playback and podcast fixes are retained. Native Meridian high-resolution planning now converts material above the supported ceiling rather than rejecting it; receiver capabilities and any lower saved output limit still apply. Physical listening acceptance of the complete RC16 candidate remains separate.
Your metadata stays
Enhanced album and artist information, artwork, credits, booklets and manual corrections remain part of the current baseline. Updating does not rebuild your collection from scratch.
A clear release identity
Core and this signed application update use 1.0.0-rc.16. Existing installer images keep their separately labelled versions. 1.0.0 is reserved for the planned R1 launch.
Administrator console: first update for supported Rev29 / Rev48 systems
Download the update and its matching checksum into a folder on persistent DATA. Verify the checksum before extracting or running it. These commands are for a normally booted full Core A/B system, not LXC or manually selected recovery C.
sha256sum -c Brimstone-Core-R1-1.0.0-rc.16-Update-20261107.tar.gz.sha256
mkdir r1-1.0.0-rc.16-update
tar -xzf Brimstone-Core-R1-1.0.0-rc.16-Update-20261107.tar.gz -C r1-1.0.0-rc.16-update
cd r1-1.0.0-rc.16-update
sudo python3 apply_patch.py --check
sudo python3 apply_patch.py --apply --activate
sudo rebootAfter a healthy boot, return to the same directory on DATA and run sudo python3 apply_patch.py --confirm. This route adds the earlier trusted A/B web helper. Separate C setup is still required.
If validation refuses the signature, baseline, layout or database, stop and send the error to support. Do not change the checks or select another disk.
If an update does not start
Refresh the update status and read the saved result. Do not repeatedly upload or restart while an operation is in progress. The new C updater confirms the exact healthy release or selects the previous system slot if the new Core fails its startup check.
Use Roll back application in the update screen if needed. Application rollback retains current DATA; it does not rewind your library or media.
Fresh installation
This is an application update, not a new installation ISO. The separately labelled RC15 installer candidate contains the mount/restart corrections, but native GUI and full fresh-install/reboot qualification remain open. Existing installations should use their supported update route rather than reinstalling.
Fresh-install guidance ↗Verify your download.
R1 1.0.0-rc.16 update · 7,154,174 bytes · signed application archive
b06894cdf1cbf4bec6fa509aded59e911e38ac03b970f1b1557eb80e7b9bf95c