The Galaxy Watch 9 Splits Samsung’s Watch Update Path

The Galaxy Watch 9 now installs firmware in the background, then asks for one restart. Owners found it on the first patch, not on any launch slide.

The 2026 Snapdragon watches can keep telling time while a new system image writes to a spare slot. Last year’s Exynos watches still freeze for the flash, and a later software drop cannot add those slots.

The First Patch Installed While the Watch Kept Running

Samsung began the Watch 9’s first firmware drop in South Korea on August 27, twenty days after the August 7 launch. The 44mm Wi-Fi unit took build L350XXS1AZH4, a 193.09MB package logged on the Samsung Community, and the build carried the August 2026 security patch.

United States LTE units followed under L355USQS1AZH4 for the 44mm watch and L345USQS1AZH4 for the 40mm watch. The Galaxy Watch Ultra 2’s matching US build, L715USQS1AZH4 on model SM-L715U, showed up around September 1. By September 3, a Watch 9 owner posting install screens showed the new image landing while the watch stayed awake.

The patch is the August 2026 maintenance release, which closes 56 issues: 38 from Google’s Android bulletin and 18 Samsung items. Eight of the Google fixes are rated critical. Nothing in the changelog billed a new install method.

THE FIRST WATCH 9 FIRMWARE

1. July 22, 2026: Samsung unveils the Watch 9 and Watch Ultra 2 at Galaxy Unpacked in London, with Wear OS 7 and One UI 9 Watch on both.
2. August 7, 2026: Both watches go on sale worldwide.
3. August 27, 2026: The 193.09MB Korea Wi-Fi build starts the Watch 9’s first security drop.
4. September 1, 2026: The Ultra 2’s first US security build appears on Verizon units.
5. September 3, 2026: Install screens show the Watch 9 writing firmware while the face stays usable.

Check for it in the Galaxy Wearable app under Watch settings, Watch software update, Download and install. Europe had the Watch 9 package by September 3. At least one Ultra 2 owner that day was still waiting, which fits Samsung’s usual Korea-then-US-then-everyone stagger rather than a separate feature flag.

Android Had This Feature in 2016

Google shipped this install style with Android Nougat in 2016. The method keeps a working copy of the system on disk while the updater fills a second copy, then flips to it on reboot. Samsung waited years to put it on its own phones. The Galaxy A55 was the first Samsung handset to do it, and the Galaxy S25 later brought it to the flagship line.

The watch is now following that same lag, almost ten years after phones could already do it. On paper the gain is shorter downtime. Under the lid it is a different storage map, which is why a One UI 9 Watch package cannot gift it to a watch that shipped without the extra slot.

OTA updates can occur while the system is running, without interrupting the user.

Android Open Source Project, A/B system updates documentation

Google’s design keeps two system slots during an OTA. The running slot stays untouched. The unused slot receives the new blocks. If the write fails, or the new slot will not boot, the watch can fall back to the copy that was already working. A conventional flash has no such spare. The watch sits dark until the write finishes, and a bad flash is a brick until someone recovers it.

Streaming A/B writes can also skip the need to park a full package in free user storage, which matters on a 32GB watch. The Watch 9 still downloaded a 193.09MB payload in Korea, so Samsung is not hiding the file size from the user. The change is when the watch becomes unusable: at the reboot, not for the whole write.

Why Older Galaxy Watches Cannot Get Seamless Updates

Samsung did not bury a toggle in One UI 9 Watch. The unused slot has to exist in the partition map the factory flashed, the bootloader has to accept a slot flip, and the updater has to write the idle copy while the current system keeps running. None of that appears after the fact on a watch that shipped with a single system image.

WHAT THE FACTORY HAD TO FLASH

• Two system slots: The watch needs a second full copy of the OS so the live copy can keep running.
• A slot-aware bootloader: The next boot has to target the freshly written copy, then fall back if that copy fails.
• A live updater: The unused copy must accept new blocks while you still raise your wrist.
• No retrofit path: A later One UI 9 Watch build cannot redraw that map on last year’s boards.

That is the same wall that kept older Galaxy phones off A/B until Samsung redesigned storage on newer models. Watch 8, Watch 8 Classic, Watch Ultra, Watch 7, and the Watch 6 line can still receive Wear OS upgrades and monthly patches. They will take those packages the old way, with the face locked until the write ends.

A New Chip and a Quiet Hardware Wall

The Watch 9 and Watch Ultra 2 are the first Galaxy watches on Qualcomm’s 3nm Snapdragon Wear Elite, replacing the Exynos W1000 in the Watch 8 generation. Samsung’s first look at Galaxy Watch9 talked up health scores, Gemini on a raised wrist, and battery, not a spare system slot.

Both 2026 watches share the same Snapdragon Wear Elite platform, 2GB of RAM, Wear OS 7, and One UI 9 Watch. The Watch 9 stores 32GB. The Ultra 2 stores 64GB. They also share a longer software promise than the Exynos models: five major OS upgrades and five years of security patches, which runs through 2031.

HOW THE 2026 WATCHES DIVERGE

The Ultra 2 has not produced a widely circulated install screenshot the way the Watch 9 has. It did take the same August security family in the United States, and it launched on the same silicon, so it sits on the 2026 side of the wall even if a photo of its progress ring has not made the rounds.

WHAT WE KNOW

• Watch 9: Install screens from September 3 show firmware writing while the watch stays in use.
• Older models: The extra system slot is a factory layout, so Watch 8 and earlier cannot gain it from One UI 9 Watch.

WHAT IS UNCONFIRMED

• Ultra 2 screenshots: No matching owner photo has circulated, even though the US watch already took the AZH4 security build.
• Watch 8 exceptions: Samsung has not described any Exynos model that can grow a second system slot later.

Google’s Pixel Watch still carries a three-year OS upgrade promise, so Samsung’s five-year 2026 window is the longer Android-watch clock. The background install sits beside that clock, not instead of it. You can have years of patches and still lose the watch face for every flash if the slot map is missing.

Watch 8 Owners Still Sit Through Frozen Installs

Since the Galaxy Watch 4, Samsung has sold four major OS upgrades and five years of security patches on its Wear OS watches. Watch 8, Watch 8 Classic, and the first Watch Ultra stay on that older promise. They were not moved onto the five-upgrade clock when the Snapdragon pair launched, and they will not pick up the spare slot either.

Those watches still have years of code coming. Wear OS 7 is already on the 2026 models at launch, and the 2025 models are in line for the same interface over the air. The split is not “updates versus no updates.” It is a working wrist versus a frozen one while the bytes land.

Last year’s watches already showed how a firmware drop can go wrong, including a timezone update that killed power unless the watch sat on a charger. A spare system slot does not fix a bad battery curve, but it does mean a failed write can reboot back into the last good copy instead of leaving a dead face on the nightstand.

The 40mm Watch 9 uses a 390mAh cell and the 44mm uses 445mAh. The Ultra 2 uses 800mAh. Background writing still burns power, so a low battery can delay the job the same way phone A/B updates wait for charge and Wi-Fi. The win is that you can still see the time, start a workout, or dismiss a ping while that wait happens.

The Spec Sheet Never Mentioned It

Samsung did not put background installs on the Watch 9 feature list, and the first changelog did not either. Owners found it because the August package behaved unlike every Galaxy Watch flash before it. That is a strange omission for a company that spent Unpacked talking about fewer interruptions in health tracking.

THE AUGUST PATCH ON THE WRIST

• Package size: 193.09MB on the Korean 44mm Wi-Fi Watch 9.
• Security load: 56 fixes, including eight critical Google items.
• User step left: One restart after the unused slot is ready.

A Watch 9 owner who posted the install screens on September 3 put the change in one line:

we can use the watch while update is being installed in the background

Watch 9 owner, September 3, 2026

The louder objection writes itself once you own last year’s watch. You still get patches. You still get major Wear OS upgrades for the years Samsung already promised. You just keep surrendering the face for each one, on hardware that cannot grow a second slot. The 2026 watches did not invent monthly security drops. They invented a way to take those drops without going dark, then shipped that method as an unmarked extra on a new chip.

The next Watch 9 reboot after this package is a short hop into the already-written slot. On a Watch 8, the next package is still a full stop. That gap will show up every month until those older watches age out of support, which is the part Samsung never had to print on a box.