# Sudo > What's new in Sudo's firmware, version by version, newest first. Firmware updates for [Sudo](/devices/sudo), newest first. Each new version is published as a **test build** first. With **Test builds** turned on, it shows up in your Ring's **Firmware update** screen in the Italic app, once the app supports it. Italic asks you to sync first, because an update can erase recordings that are still on the Ring. ## Sudo 1.0.138 [#sudo-10138] November 4, 2026. Test build. - **Removing another phone's pairing needs Sudo on its charger.** Put Sudo on its charger, wait about 30 seconds for Italic to reconnect, then remove the other phone in Italic. No touch is needed, and it works the same whichever phone paired first. Off its charger, once you've touched it, Sudo keeps its pairings, so a phone that's only nearby can't take Sudo over. - **No more 15-second hold to pair.** Putting Sudo on its charger opens pairing, as it has since Sudo 1.0.133. - **A double tap right after you lift a full Sudo off its charger shows the battery light again.** On Sudo 1.0.136 and 1.0.137 it stayed dark until you touched Sudo. - **A failed cleanup no longer stops deleting synced recordings.** Sudo reconnects its storage and carries on. - **A brand-new Sudo starts with clean recording storage,** even if a factory test left data on it. - This needs an Italic app that supports Sudo 1.0.138. ## Sudo 1.0.137 [#sudo-10137] November 3, 2026. Test build. It includes Sudo 1.0.136, which wasn't released on its own. - **Your first hold after changing a setting records.** Before, the first press and hold after a settings change, an update or a restart could do nothing. - **When Sudo buzzes to start, it records.** Before, a hold you let go of during the buzz buzzed but saved nothing. Every hold now records for at least a second after the buzz, and if you press again before that second is up, it keeps recording until you let go. - **Letting go ends a memo normally.** Before, some releases ended a memo with the error buzz. - **A memo keeps going past a storage error.** Sudo checks its storage and carries on in the same recording, instead of stopping it. A failed cleanup after a sync no longer stops Sudo recording until it restarts, and Italic retries Sudo's storage for you when it finds that problem. - **A full Sudo on its charger stays at 100%,** even when its charger stops and starts on its own. - **Removing another phone's pairing from your newer phone needs a touch on Sudo.** When Italic asks, touch Sudo, then try again. A phone that's only nearby can't take Sudo over. - **Sudo updates off its charger only above 20%.** On its charger, it updates at any level, and Italic tells you to charge Sudo when its battery is too low. - Sudo recovers more reliably when its radio goes quiet, and records more detail about problems so we can fix them. - We've tested these on a computer and are now checking them on real Rings. This needs an Italic app that supports Sudo 1.0.137. ## Sudo 1.0.135 [#sudo-10135] November 1, 2026. Test build. - **A full Sudo stays connected on its charger.** When Sudo is full, its charger stops and starts on its own. On Sudo 1.0.133 and 1.0.134, each stop could look like you had taken it off and put it back, which dropped your iPhone and opened pairing again. We've tested the fix on a computer and are now checking it on real Rings. - **To pair a new phone with Sudo already on its charger, lift it for about 10 seconds** and put it back. A quick lift no longer counts. - **The battery reaches 100% when Sudo is really full.** It can get there a little later than before. - **Less can stop a recording.** One failed read of Sudo's storage no longer blocks new recordings until a restart. A long memo also has more room before storage counts as full. - Other devices can no longer rename a Sudo they aren't paired with, which could hide it from pairing. - This needs an Italic app that supports Sudo 1.0.135. ## Sudo 1.0.134 [#sudo-10134] October 30, 2026. Test build. - **Long memos should no longer get cut off.** On Sudo 1.0.129 to 1.0.133, a bug could make Sudo restart itself while recording, which ended the memo you were making. What it had already saved was kept, but nothing more was recorded until you started again. We've tested the fix on a computer and are now checking it on real Rings. - This needs an Italic app that supports Sudo 1.0.134. ## Sudo 1.0.133 [#sudo-10133] October 30, 2026. Test build. - **Put Sudo on its charger to pair a new phone.** For 2 minutes after Sudo goes on its charger, a new phone can pair with it, with no touch and without using the old phone. If Sudo is already on its charger, lift it for a few seconds and put it back. It can take about 30 seconds to notice. - **Your old phone can't block it.** For the first 30 seconds on the charger, Sudo disconnects from phones it already knows, so one nearby can't keep the new phone out. Syncing to your old phone waits for that time, then carries on. This needs an Italic app that supports Sudo 1.0.133. ## Sudo 1.0.132 [#sudo-10132] October 29, 2026. Test build. - **Nothing you'll notice.** An old copy of the Opus audio library is taken out of the build settings, so the build can only read the one it uses. Sudo behaves as 1.0.131 does. ## Sudo 1.0.131 [#sudo-10131] October 28, 2026. Test build. - **A quieter standby.** Sudo's clock wakes its processor once a second instead of eight times, and a battery reading now sleeps while it waits instead of spinning. At rest, Sudo should wake about 9 times a second instead of 16. - **Fewer reads from storage.** Recordings are read from flash in larger steps, which should cut flash reads by roughly a third. - **A leaner encoder.** An audio mode Sudo never used is out of the firmware. Recordings sound the same. ## Sudo 1.0.130 [#sudo-10130] October 28, 2026. Test build. - **A cheaper recording.** The audio encoder uses the processor's built-in math instructions and its hardware divider, and produces exactly the same audio. That is about a quarter fewer instructions, which should add roughly 10 to 30 minutes of recording to a charge. We haven't metered it on a Ring yet. - **Gentler flash writing.** The writer keeps a larger buffer and sleeps while the flash erases a sector, instead of waiting at full power. - **Sudo times its own recordings.** It records where each recording's time went, so we can check the saving on real Rings. ## Sudo 1.0.129 [#sudo-10129] October 28, 2026. Test build. - **Sudo keeps its own battery level.** Before, the Ring and the app each worked out a percentage, and they could disagree by a lot. Now the Ring works out one steady level, and its light, its replies and the app all use it. It reads 100% at the Ring's own full mark, uses only readings taken at rest, never rises off the charger, falls at most a point every 30 seconds, and rises as the Ring charges. - **Long recordings no longer split.** The audio encoder now runs ahead of the storage writer, so a long recording doesn't break apart when the audio buffer's deadline passes. ## Sudo 1.0.128 [#sudo-10128] October 27, 2026. Test build. - **Flash storage.** A pin that no part on the current board uses is no longer driven. - **Settings repair.** Repairing damaged settings reports success only once one fresh settings record is left, the one it wrote. - **Updates.** The charger isn't set up while a firmware update is starting. ## Sudo 1.0.127 [#sudo-10127] October 26, 2026. Test build. - **Touch and pairing.** The 15-second pairing hold on the charger counts a wide thumb's two contacts. A finger that lingers ends a recording normally. Sudo checks that the touch chip accepted its setup, and waits for no contact before restarting it. - **Bluetooth.** Sudo re-reads its saved pairings when it starts. - **Power.** The Ring no longer has a deep power-off step. At the low-battery cut it tries twice, then stops until the charger or a restart. - **Settings.** A damaged settings record runs on the defaults and is repaired by the next save. - **Storage.** A failed mount at startup is tried again. Sudo formats only when two reads agree the storage isn't this build's, and a failed read ends just that operation instead of marking all storage as failed. - **Smaller.** Unused vendor commands are refused, and unused libraries and the NFC driver are out of the firmware. ## Sudo 1.0.126 [#sudo-10126] October 26, 2026. Test build. - **Touch.** A calibration error in the wake sensor no longer throws touch reports away. A stuck calibration error restarts the touch chip after 2 seconds, at most every 30 seconds. - **Pairing a new phone.** The 15-second hold on the charger no longer restarts on a wide thumb or a passing flag. - **Bluetooth storage.** If it can't start, Sudo repairs the pages that don't belong to it once, restarts, and opens its recovery window. - **Charging.** The charge voltage and current settings are checked every few minutes on the charger and restored if they drift. Over-voltage is detected and remembered. The low-battery cut has a fallback. - **Storage.** A failed mount at startup no longer erases a Ring that has a filesystem. ## Sudo 1.0.125 [#sudo-10125] October 25, 2026. Test build. - **A bigger Small touch area.** Small is now the top three touch columns instead of two, so a thumb resting a little past the ring's lip still lands on it. Medium and Large are unchanged. The Touch area card in the app draws Small as a three-column strip. ## Sudo 1.0.124 [#sudo-10124] October 25, 2026. Test build. - **One press per contact.** A wide thumb that the touch chip sees as two patches, or as too many fingers, is still one press. A hold lasts until every contact has lifted. - **Taps end before the hold time.** With the 0.25 second quick hold, a tap has to lift within 0.2 seconds, whatever the tap setting. With the 0.5 second standard hold, the tap settings are unchanged. - **Wake sensor.** It recalibrates after every start, touch chip reset and touch area change. - **Press history.** Sudo keeps its last eight presses and counts every touch report's flags, and the app writes them to its log. ## Sudo 1.0.123 [#sudo-10123] October 25, 2026. Test build. - **Storage readiness.** Sudo reports its recording storage as ready only once its startup marker has been written and read back. If that fails, storage stays unavailable and Sudo doesn't tell the app it worked. - **Repairs.** A damaged marker that Sudo can positively identify is repaired only after the app's usual confirmation. A one-off read error never erases recordings. - **Flash writes.** Sudo waits correctly for the flash to finish writing. - It keeps the connected thumb contact from 1.0.122 and the Soft, Medium and Bright recording lights from 1.0.121.