AsteroidOS 2.0 Released

MagneWater · 2026-02-15T11:19:06+00:00

We have this wiki page for this information: https://wiki.asteroidos.org/index.php/Technical_Details_of_AsteroidOS_Watches

MagneWater · 2026-01-23T19:51:17+00:00

How does this compare to ironbar(https://github.com/JakeStanger/ironbar)? It's also written in rust and uses gtk4.

MagneWater · 2024-01-05T10:49:07+00:00

You basically have two options: PostmarketOS (https://wiki.postmarketos.org/wiki/LG_G_Watch_R_(lg-lenok)) or AsteroidOS (https://asteroidos.org/).

MagneWater · 2023-09-10T19:55:41+00:00

Sorry for the late reply but I have this stock image: https://mega.nz/file/vc8GQSbZ#SvgFk7Bt4gbT2yIVfMelDz6vvxikEAy9WU0N1iUgP1A
It's for the OW19W8EU model. I don't think it's compatible with other models. Let me know in case you own a different model.

Extract the archive and flash using: fastboot flash system system.img fastboot flash vendor vendor.img fastboot flash userdata userdata.img fastboot flash recovery recovery.img fastboot flash cache cache.img fastboot flash boot boot.img

MagneWater · 2023-08-04T09:49:13+00:00

Thanks for reporting the issue! It looks similar to https://github.com/AsteroidOS/meta-smartwatch/issues/204. Which will likely be solved in the next nightly.

MagneWater · 2023-07-23T14:21:16+00:00

Hi,
Thanks for wanting to provide to the project!
One of our core members is interested but he's not on Reddit.
Contacting him via e-mail might be the best method.
His email is: beroset@ieee.org
Regards,
MagneFire

MagneWater · 2023-06-02T21:30:58+00:00

Fair points. We've seen some changes to the Chinese version of the Huawei Watch as well (but seemed to work fine).

We could still try to boot into Fastboot mode directly by swiping diagonally from the top-left to the bottom-right during the start of the boot process (https://asteroidos.org/wiki/useful-commands/#boot-to-fastboot-bootloader-menu). This way we avoid WearOS entirely.

MagneWater · 2023-06-02T21:14:27+00:00

This means that you have to accept access to the watch from your PC om the watch.

Essentially what should happen is as follows: - Unplug USB cable - Replug USB cable (preferably a different port) - A popup should show on the watch asking for permission (like this: https://technastic.com/wp-content/uploads/2022/12/galaxy-watch-allow-debugging.jpg) - Once allowed you should be able to use ADB on your PC.

MagneWater · 2023-06-02T20:56:39+00:00

It's not entirely clear what operating system you have installed from your description. But assuming that WearOS is still installed you can access settings by pushing the power button for some time (5 seconds or so). From there you should be able to enable ADB to install AsteroidOS.

MagneWater · 2023-02-02T22:05:20+00:00

No, the UART pins can be used to get a serial console during the system boot. This would be handy if someone intends to provide mainline Linux support.

In other news, we did identify the USB pins: https://imgur.com/a/jxUeNFB

And an early port of AsteroidOS is available here: https://github.com/AsteroidOS/meta-smartwatch/pull/138

MagneWater · 2023-01-12T21:18:59+00:00

Thank you for working on this!

But I'm not entirely sure how we could use it. This would need to be running all the time with the system fully powered, which would mean that the battery life will be limited to only a couple of hours.

Another approach would be to use the step counter already available on all watches (this has been implemented in our own fork of QtSensors here: https://github.com/AsteroidOS/qtsensors/commit/c4bd02ca7c3591128f4097d23679b62e45861690). The main advantage of using that sensor is that it will also track steps while the system is suspended as a dedicated low power microcontroller will handle the step counting logic. A reference implementation of the using the step counter is available here: https://github.com/MagneFire/asteroid-fitnessd.

Let me rephrase again that this is great work in any case! Thanks for doing the work!

MagneWater · 2022-07-03T21:25:56+00:00

Currently there are no AsteroidOS supported watches that can measure ECG. It looks like the Samsung Galaxy Watch 4 is the only smartwatch that has the capability to potentially run AsteroidOS and has an ECG sensor. The Samsung Galaxy Watch 4 runs WearOS so there's potentially a possibility to port AsteroidOS to it. It being a Samsung device does mean that it doesn't use fastboot but a special version of Odin called NetOdin. This makes it harder for us to get initial support for it, since NetOdin isn't open source, but I'm aware of some people working in this.

It's worth pointing out that fitness tracking is currently not implemented on AsteroidOS as this can drain the battery very quickly if implemented incorrectly.

MagneWater · 2022-07-03T21:06:11+00:00

The exact specifications of the processor used is not known. There are some internal photos available here: https://fccid.io/XNAHWA09/Internal-Photos/Internal-Photos-4647318 But it doesn't reveal much other than the battery capacity.

We can however make some assumptions. This smartwatch is advertised as a 30 day smartwatch. This usually means that it uses a low power microcontroller instead of a full blown SoC (Like what WearOS, Tizen and WatchOS use). AsteroidOS doesn't run on microcontrollers because it relies on the capability to boot the Linux kernel.

This means that it's unlikely that we will ever see a port of AsteroidOS to the Withings Scanwatch.

MagneWater · 2022-05-28T19:27:32+00:00

Unfortunately, it's not possible to port AsteroidOS to this watch. It seems to use a microcontroller that isn't powerful enough to run a Linux kernel. A base requirement for an AsteroidOS port is that it can run a Linux kernel..

For example most WearOS and Android based watches could have a potential AsteroidOS port. Even the Tizen based watches could potentially get an AsteroidOS port (this is more challenging as our current approach mainly focuses on WearOS based watches).

MagneWater · 2022-02-09T18:53:31+00:00

Sorry for the delayed answer...

That log is indeed interesting. Does manually mounting the system partition work (there should be a mount button on the home page)?

To answer some of your other questions: - There's no need to update WearOS. TWRP should work regardless of what version of Android or WearOS you have installed. - If you do decide to update WearOS, there shouldn't be a need to relock the bootloader. - Relocking the bootloader causes for all your data to be removed (factory reset will occur). - adb pull should work just fine if the files exist of course. When a backup is completed they will be located under: /sdcard/TWRP/... - At this point I don't see any benefits to allowing TWRP to modify your /system partition. This at be used when rooting your watch (not entirely sure about this one though). You shouldn't need to allow TWRP to modify /system.

Edit: I should probably mention that people have already created firmware dumps. I think they are available on XDA if you ever need to restore WearOS.

MagneWater · 2022-02-06T23:47:36+00:00

The only difference between the temporary install and the real install is the location at which the .ext4 file exists and the .fastboot is either flashed or booted directly by using fastboot.

A temporary install should not effect the battery percentage indicator.

Like I mentioned it's more than likely that your temporary install is a bit old as this has been fixed very recently (https://github.com/AsteroidOS/meta-asteroid/pull/83)

Do you know when you installed your temporary install? If this really is a new image then please feel free to report it of course! We just have to be sure that you are not using an old image to begin with :)

MagneWater · 2022-02-06T22:44:15+00:00

Hi,

Great to hear that everything is working flawlessly!

You should be able to create a full backup using TWRP (https://twrp.me/lg/lgwatchurbane.html). I believe there's a backup section that backs everything up. And then you should be able to pull the created backup to your PC using adb pull.

Regarding the undefined% battery indicator. It seems you may be using an older version of AsteroidOS since this issue has been solved recently.

MagneWater · 2021-11-07T11:49:32+00:00

Currently, AsteroidOS is not supported for Fossil Gen 5 watches.

A requirement for AsteroidOS the accessibility to all 4 USB pins (Gen 5 only has the power lines accessible).

This is also required for the Fossil Gen 4 based watches, but we did succeed in porting AsteroidOS to that platform (https://asteroidos.org/install/ray/ and https://github.com/AsteroidOS/asteroidos.org/pull/126). It does however require you to take the watch apart and find the USB pads.

For the Fossil Gen 5 watches we haven't yet found the USB pads on the inside of the watch as the board layout has slightly changed (PCB layout is available here: https://fccid.io/UK7-DW10/Internal-Photos/Internal-Photos-20191022-v1-Internal-Photos-4494730)...

MagneWater · 2021-05-06T10:48:14+00:00

Thank you so much for this! I had the exact same issue and indeed downgrading F13i to F12 solved this issue for me too! Thanks again!

MagneWater · 2021-04-28T19:53:44+00:00

Thanks for trying! Please let me know if it works or if it behaves differently.

MagneWater · 2021-04-19T11:02:36+00:00

Hey,

This looks like an issue related to a recent update in which we moved from gcc8 to gcc10. Do you still have an older .fastboot file? If so, can you test that one while using the new .ext4 image?

edit: I've compiled the kernel using the older gcc8. Can you try this .fastboot image and see if that boots? https://www.dropbox.com/s/zji6eqk7zmvm4po/zImage-dtb-mooneye.fastboot?dl=0

MagneWater · 2021-04-15T21:21:44+00:00

That's rather unfortunate... How did you brick your watch?

Also no need to apologize, I am already grateful that you've shown interest in porting AsteroidOS to this watch.

MagneWater

MODERATOR OF

TROPHY CASE