The 'nobody asked, we shipped anyway' energy is the right spirit for OSS. The wearable OS space is a duopoly with zero interoperability, and having a Linux base means you can actually write what you want without fighting proprietary SDKs.
The QML choice makes sense for the constraints. It gets a bad reputation in desktop contexts, but for small screens with limited input it is genuinely practical. The bigger win here is what happens when a manufacturer abandons your watch: instead of a dead device, you keep getting updates.
Congrats on 2.0. Sustained long-term open source projects are rare, and this one solves a real problem.
Wild to see such fragmentation in such a niche space. It's an aftermarket Linux flash for smartwatches, and there are companion apps for SailfishOS and Ubuntu Touch, which are extremely niche flavors of the already very niche mobile Linux.
Not being much of a watch person let alone a smartwatch aficionado, I had no idea there were even that many smart watches. The long list looks impressive. I wonder if there are a lot of the same guts so it's not as bad of a nightmare to maintain as it looks. Either way, the list of supported devices is impressive.
> niche space
Think of the space as less "I want Linux on my wrist", and more "I want a [cheap || not 1st world expensive] smartwatch as a gift."
These folks do gods work of making them supported and a real shared platform (c.f. their self-post "The only real signal we get is occasional [chat visitor] going "hey, it booted on my watch from 2014 and now it's usable again"")
This is seriously impressive! Never knew after market os's were even a thing for watches with their proprietary drivers.
I like that peeking watch face switcher, companies like samsung even after all these years still takes way too long to apply a watch face.
Thanks so much! The peek gesture is inherited from lipstick and we kind of built our UI around those possibilities.
Hey, thanks for the new release. I should definitely fix my wristband and start wearing my AsteroisOS watch again (LG Lenok).
You have probably addressed that somewhere, but would it be possible to run your UI stack somewhere else? (PostmarketOS).
My other wish for AsteroidOS would be for it to leverage Wi-Fi better. Not sure how much more energy it would use, but having a longer range for my notifications would be nice (at least on LAN). Being able to perform a few other actions independently of my phone would be great: weather % time updates, e-mail notifications, home assistant control, etc. I get that it may affect battery life as well.
While I'm at it: tiny bug report, but I adjusted the time while the stopwatch was running, and this affected the stopwatch result.
Nice, thanks for the bug report! I have made in issue in the stopwatch repo:
https://github.com/AsteroidOS/asteroid-stopwatch/issues/13
We have implemented a wifi toggle in the quickpanel with 2.0. But the wifi credentials still need to be entered into connmanctl on the cli. As soon as you got wifi set up and connected, you can already now sync weather data usin asteroid-weatherfetch. But right, wifi usually uses up to 30% more power and should be enabled selectively.
For the postmarket question, yes, it is our longterm goal to mainline watches, which we are sort of doing in coorperation with the postmarket guys. But thats a humongous task and part of the idea of this 2.0 release is to interest capable contributors to push things further ;)
These are all Linux kernel-based WearOS watches (not just smartbands running a barebones microcontroller), so could they be running a mainlined kernel and Linux OS such as pmOS? Of course the UI layer might be specific to the form factor, but everything else could just be standard.
In theory yes. Asteroidos has experimental support for a mainline watch.
Most vendors don't upstream their drivers and kernel mods. Also Android drivers use an abstraction layer and a different format to some extentent. So you have to reverse and write your own driver.
So they could run mainline if the vendor or a user bothers to upstream drivers and hardware quirks.
A lot of the vendors don't meet quality expectations of the kernel team and sources are usually for older kernel versions and the code would need changes or refactoring.
The mainlining work is usually done by the community, not necessarily vendors. The relevant pmOS wiki page is https://wiki.postmarketos.org/wiki/Category:Watch but it may be less comprehensive or up-to-date than the AsteroidOS hardware support list. Everyone can help by adding technical info about hardware to the wiki!
This is an awesome project. Props to y'all for just making something you want to exist!
I have a Tizen-based Samsung watch (Gear Sport, 2017). It's served me faithfully but I'm starting to notice the battery degrading. I'd be interested in trying AsteroidOS with it, if Tizen support ever lands.
> wrist-sized Linux
What a charming turn of phrase!
we're finally upon the year of the linux wristwatch
Can anyone suggest where to find a watch that is supported if you live in the US? I've been scanning eBay but it feels difficult to get ahold of a supported device. Are there sites that ship to the US where a new or used device can be found?
Usually the Ticwatch Pro 2018/2020 (catfish) is widely available since it was a popular model. The more recent version Ticwatch Pro 3 (rubyfish/rover) is freshly ported and not as well supported as the first Ticwatch Pro yet. I bought one new in box just this week from german ebay for 70€.
We got a Team member in the US/ML who is hoarding watches and seems to have no problem acquiring them :D I wish you luck.
This sounds like an interesting investigatory problem you've put in front of me...
Thanks so much!
I can see some Fossil Gen 6's on eBay in the US. (I only learned about AsteroidOS today and I'm not in the US)
Thats awesome! Recently I was looking into making apps for my smartwatch that don't exist (like watch display with multiple timezones), and infrastructure to make your own apps is very poor.
One thing I wish for is Rust support, since its running Linux it should be possible, isn't it?
It would be possible to use Rust. Nobody got around working on it tbh. But simple things like your mentioned watchface idea are really quick to do in QML.
Damn, not even LLM copy. Frodo lives.
Perfect! Our Ring is libhybris, Sauron is the binary blob drivers the manufacturers cursed us with, and we're still hobbling toward mainline Mordor one old kernel backport at a time. One does not simply upstream a smartwatch driver.
Great work to everyone involved with the project!
I have a galaxy watch 4 which I'd hoped was old-enough to be supported but I can see that it is not. I get it, hardware is hard.
I'm curious, is the challenge with newer hardware lack of chipset drivers for modern watches, or is there a fundamental difference between the new devices and the old ones that make them completely incompatible with asteroidOS?
With the latest devices its usually a problem that manufacturers choose to omit the usb pin outs in favor of water resistance and wireless charging. Making them a challenge to flash and still wear afterwards.
Another issue is that we currently need to rely on libhybris for quick porting process that employs the android drivers. And the new devices run android versions that libhybris can not handle yet. Its just a slow process on all fronts but we are actually releasing this 2.0 publicly to possibly interest more developers.
Thanks for sharing this, it looks promising!
I would love if it would support some of the no-brand Chinese watches you get usually for cheap, the hardware is great but the software usually is bad or outdated. I use one now, I don’t even know anything about it other than the Bluetooth name and app name, but it’s good in measuring distance, blood pressure, heart rate, sleep, among others that’s surprisingly it’s very accurate, it also has a builtin strong flashlight, I like it but with a fully fledged linux would definitely be better.
fyi the announcement is very obviously ai-written. It’s off-putting.
Fair suspicion in 2026 — but we actually started drafting that announcement in early 2023 before first committing it here: https://github.com/jrtberlin/aos2.0-post. As a non native speaker i sure ran my commits through grammar polishing multiple times over the years. And i am genuinely curious now what to avoid to not sound like an LLM if you could dig out one or two examples.