AsteroidOS - User contributions [en]

Emulator

2026-02-01T19:55:54Z

Casept: Reflect qemux86 -> emulator rename

[[Category:Developers]]
If you don't have a supported smartwatch or if you want to develop an app without having to touch your device you can try AsteroidOS in an emulator.

'''Note:''' The emulator has some known issues under x11 sessions. Make sure that you run it in a wayland session. You can check your session type with <code>echo $XDG_SESSION_TYPE</code>.
== Get a qemux86 build of AsteroidOS ==

Nightly builds of AsteroidOS for QEMU can be found [https://release.asteroidos.org/nightlies/emulator/ here]. You will need to download a [https://release.asteroidos.org/nightlies/emulator/asteroid-image-emulator.rootfs.ext4 prebuilt rootfs] and [https://release.asteroidos.org/nightlies/emulator/bzImage-emulator.bin kernel].

If you want more control over your asteroid image, you can also [[Building AsteroidOS|build AsteroidOS]] yourself using the "emulator" machine codename (the resulting rootfs and kernel will then be located in your <code>build/tmp/deploy/images/emulator/</code> directory).

== Get an appropriate version of QEMU ==
The AsteroidOS emulator image requires a paravirtualized GPU only offered by QEMU when built with support for Virgil3D. Recent distributions (such as Fedora 27 and later) offer QEMU packages built with Virgil and can be used directly to run AsteroidOS.

Unfortunately, most Linux distributions (such as Debian) still do not provide QEMU packages with support for this setup. Moreover, OpenEmbedded currently offers no clean way to build a host QEMU binary with Virgil due to various constraints. You then need to compile QEMU yourself.

== Run AsteroidOS ==
Once you have a correct version of QEMU, a rootfs and a kernel, you can start AsteroidOS in an emulator using:
<pre>
qemu-system-x86_64 -enable-kvm -kernel bzImage-emulator.bin \
-device virtio-vga-gl \
-net nic -net user,hostfwd=tcp::2222-:22 \
-drive format=raw,file="asteroid-image-emulator.rootfs.ext4" \
-m 512 \
-display sdl,gl=on \
-cpu qemu64,+ssse3,+sse4.1,+sse4.2 \
-usb -device usb-tablet \
--append "verbose root=/dev/sda rw mem=512M video=800x800"
</pre>

The previous command sets up a port forwarding so that you can connect to the emulator using SSH with the following command:

<code>ssh -p 2222 ceres@localhost</code>

Note that versions of the image prior to 11 August 2024 did not have "rootfs" as part of the file name, so the effect is that that portion of the line would be <code>file="asteroid-image-qemux86.ext4"</code>instead.

= Troubleshooting =

Here are some common problems and their solutions.

* Unable to accurately select buttons or items
*: Versions of the emulator image prior to 11 August 2024 did not include the <code>ceres</code> user in the <code>input</code> group, causing the emulator to ignore mouse input. To fix that, log in to the watch remotely as root (or use the serial console) and issue the command <code>usermod -a -G input ceres</code> and then <code>systemctl restart user@1000</code>. This should make it possible for the mouse input to be received.
*: Even with the fix applied, sometimes a click does not seem to select the right thing. Most typically, a click registers as an item above where the user actually clicked. The way around this is to resize the qemu window to be taller. When this is done, even though the display is not square, clicks on screen are closer to where the user actually clicks. It may also be helpful to show the mouse cursor. This can be done by altering the display line to <code>-display gtk,gl=on,show-cursor=on</code>.

* Errors with -virtio-vga
*: Newer versions of QEMU use <code>-device virtio-vga-gl</code> instead of <code>-device virtio-vga,virgl=on</code>, so if you get an error message complaining about <code>virtio-vga-gl</code>, you have an earlier version of QEMU. You can either use <code>-device virtio-vga,virgl=on</code> instead or upgrade to a newer version of QEMU.

* Video corruption using NVIDIA drivers
*: There have been reported problems on machines using proprietary NVIDIA drivers. One symptom is a black screen instead of the AsteroidOS screen which may or may not also show messages like these:
<pre>
gl_version 46 - core profile enabled
GLSL feature level 460
failed to complete framebuffer 0x8cd7 asteroid-launch
</pre>
*: Other symptoms include video artifacts (smearing, double screens) and crashing, usually with a message <code>Segmentation fault (core dumped)</code>. If you're experiencing these and are using a proprietary NVIDIA driver, either updating the driver or using <code>gtk</code> instead of <code>sdl</code> may work better. An example command line:
<pre>
qemu-system-i386 -enable-kvm -kernel bzImage-emulator.bin \
-device virtio-vga-gl \
-net nic -net user,hostfwd=tcp::2222-:22 \
-drive file=asteroid-image-emulator.ext4,format=raw \
-m 512 \
-display gtk,gl=on \
-cpu qemu64,+ssse3,+sse4.1,+sse4.2 \
-usb -device usb-tablet -device usb-mouse \
--append "verbose root=/dev/sda rw mem=512M video=800x800"
</pre>

* Watch seems to lock up after a few seconds
*: It's possible that the display is no longer updating but that the watch is actually still running. To make sure that the emulator continues to update the screen you can enter [[Useful Commands#Screen|demo mode]] to keep the screen on. If you have followed this guide and the watch is listening on port 2222, this command will turn on demo mode.
: <code> ssh -t -p2222 root@localhost mcetool -D on </code>

Porting Status

2024-06-27T10:57:05Z

Casept: Gear 2 port

This page aims at gathering info about the currently supported platforms and porting efforts.

== WearOS Smartwatches ==

The WearOS smartwatches are the most widespread and easy to support. The source code of their kernels is usually easily available and the drivers can be supported with [https://github.com/libhybris/libhybris libhybris]. Those watches are the current priority of AsteroidOS.

=== Supported watches ===
{{#cargo_query:
tables=Watches
|fields=CONCAT("[[",_pageName,"|",Model,"]]")=Model,Name,Stars
|order by=Watches.Stars DESC
|format=table
|limit=9999
|where=Watches.Status = "supported"
|more results text=
}}

=== Experimental watches ===
{{#cargo_query:
tables=Watches
|fields=CONCAT("[[",_pageName,"|",Model,"]]")=Model,Name,Stars
|order by=Watches.Stars DESC
|format=table
|limit=9999
|where=Watches.Status = "experimental"
|more results text=
}}

=== Failed WearOS ports ===
These ports have been attempted, but have not been successful.
* Moto 360 3rd gen (<code>mola</code>)
*: This port has failed because the kernel does not ship DTS, so it is not possible to build a full boot image. A port may be possible if a WearOS update package is found.
* Fossil Sport family (<code>darter</code>)
*: this port has failed because attempts at unlocking the bootloader have failed. Fastboot behaves as if the bootloader unlock has succeeded, but the bootloader does not end up being unlocked.
* Misfit Vapor/Fossil Q Control (<code>mullet</code>)
*: this port has failed because the watch does not seem to boot an asteroid boot image, even if the bootloader is unlocked. It is not clear why this happens.

=== Impossible ports due to unmet hardware dependencies ===

* Fitbit watches & smartbands
* Honor Magic Watch 2
* Huawei Watch GT Series
* OPPO Watch Free
* PineTime
* Umidigi Uwatch GT

== Tizen Smartwatches ==

The Samsung Gear S2, S2 Classic and S3 might be supported by AsteroidOS in the future but they will require more work than the other watches. Someone already got interested in the S2 port but gave up because he couldn’t find the kernel’s defconfig.

A port for the Gear 2 based on a mainline kernel is currently in progress.

== Other watches ==

There are many Android (non-Wear) smartwatches available for a lower price. (e.g: the Omate *, Sony SW, Intex iRist, zWatch etc…) It might be more difficult to get access to the kernels or android tree of those devices but libhybris could also make running AsteroidOS on top of them possible. This is typically the case of the MTK6580 watches.

Other low-end smartwatches using cheap Mediatek SoCs aren’t able to run a Linux kernel and can’t be supported by AsteroidOS.

Rinato

2024-06-13T17:07:05Z

Casept: Update port state

== Galaxy Gear 2 ==
[[File:Rinato.webp|alt=Picture of the watch with a blank screen|left|thumb]]
The Gear 2 is a Tizen-based smartwatch released in 2014. See [https://www.gsmarena.com/samsung_gear_2-7717.php gsmarena] for detailed specs. There are two variants of this watch - Gear 2 (SM-R380) and Gear 2 Neo (SM-R381), which are identical save for a camera that's only present on the Gear 2. The codename for this watch is "rinato".

As the vendor kernel is very old (3.4) and there's no existing abstraction for the Tizen HAL, a mainline Linux port for this watch is being attempted instead.

Downstream sources available at https://github.com/casept/linux-exynos3250-common/tree/rinato, as Samsung no longer hosts them.

===Hardware docs and kernel support===

These are maintained on the [https://wiki.postmarketos.org/wiki/Samsung_Gear_2_(samsung-rinato) postmarketOS wiki page for this device].

===Current port state===

This watch is being worked on [https://github.com/casept/meta-smartwatch/tree/rinato here].

Currently (June 2024) the watch boots and the launcher starts, but rendering is extremely sluggish. This is suspected to be caused by lacking support for non-Android hardware acceleration in Asteroid's version of lipstick, and is currently being investigated.

Rinato

2024-06-08T22:59:33Z

Casept: Created page with "== Galaxy Gear 2 == The Gear 2 is a Tizen-based smartwatch released in 2014. See [https://www.gsmarena.com/samsung_gear_2-7717.php gsmarena] for detailed specs. There are two variants of this watch - Gear 2 (SM-R380) and Gear 2 Neo (SM-R381), which are identical save for a camera that's only present on the Gear 2. The codename for this watch is "rinato". As the vendor kernel is very old (3.4) and there's no existing abstraction for the Tizen HAL, a mainline Linux port..."

== Galaxy Gear 2 ==

The Gear 2 is a Tizen-based smartwatch released in 2014. See [https://www.gsmarena.com/samsung_gear_2-7717.php gsmarena] for detailed specs. There are two variants of this watch - Gear 2 (SM-R380) and Gear 2 Neo (SM-R381), which are identical save for a camera that's only present on the Gear 2. The codename for this watch is "rinato".

As the vendor kernel is very old (3.4) and there's no existing abstraction for the Tizen HAL, a mainline Linux port for this watch is being attempted instead.

Downstream sources available at https://github.com/casept/linux-exynos3250-common/tree/rinato, as Samsung no longer hosts them.

=== Hardware docs and kernel support ===

These are maintained on the [https://wiki.postmarketos.org/wiki/Samsung_Gear_2_(samsung-rinato) postmarketOS wiki page for this device].

=== Current port state ===

This watch is being worked on [https://github.com/casept/meta-smartwatch/tree/rinato here].

Currently (June 2024) the watch boots and the launcher starts, but due to a possible bug in the kernel side of the graphics stack trying to launch any app results in a lockup and the kernel emitting a warning.

File:Rinato.webp

2024-06-08T22:55:46Z

Casept: An image of the watch (silver non-neo variant)

== Summary ==
An image of the watch (silver non-neo variant)

WC1

2023-12-21T16:18:15Z

Casept: Note port state

== Galaxy Gear S2 Classic ==

The Gear S2 classic is a Tizen-based smartwatch released in 2015. See [https://www.gsmarena.com/samsung_gear_s2_classic-7677.php gsmarena] for detailed specs. The codename used in Tizen and Recovery seems to be "WC1".

As the vendor kernel is very old (3.4) and there's no existing abstraction for the Tizen HAL, a mainline Linux port for this watch is being attempted instead.

Downstream sources available at https://github.com/casept/samsung-wc1-sources, as Samsung no longer hosts them.

=== Hardware docs ===

==== Recovery mode and flashing ====

Like other Samsung watches, the Gear S2 classic can either be flashed wirelessly via the NetOdin protocol, or using the regular Odin protocol by opening it up and soldering a USB cable to some internal pads. See e.g. [https://xdaforums.com/t/gear-s2-wireless-download-mode-error.3745724/ this XDA thread] for the pinout.

Note that flashing the BOOT partition with a bad kernel will result in a broken recovery and inability to use wireless download mode, so make sure you have USB connected before working on the watch.

==== List of peripherals and their kernel driver state ====

Most of the hardware in this watch seems to have drivers in the mainline kernel, especially the SoC and most of the regulators.

{| class="wikitable"
|+ Samsung Gear S2 Classic
|-
! Chip !! Function !! Driver state in mainline Linux !! Notes
|-
| Exynos 3250 || SoC || Supported || DTS for dev boards based on it exist
|-
| WM1831 || Microphone DAC || Supported
|-
| BCM4343W || WLAN and BT || Unsupported || Infineon still maintains this chip. There's a patch for recent kernels (5.15) available on [https://community.infineon.com/t5/Wi-Fi-Bluetooth-for-Linux/Cypress-Linux-WiFi-Driver-Release-FMAC-2023-09-01/td-p/492862 Infineon's support site]. A quite complete datasheet exists [https://www.infineon.com/dgdl/Infineon-CYW4334WKUBGT-DataSheet-v11_00-EN.pdf?fileId=8ac78c8c7d0d8da4017d0ee1f02f680f here].
|-
| SENN5DDPS2 || NFC || Possibly supported || There exists a kernel driver for 5th generation Samsung NFC chips, whether this chip is part of it is unknown.
|-
| BCM53950 || Wireless charge controller || Unsupported || No public datasheet, Samsung code seems readable enough and quite short (~1500LoC)
|-
| ISA1000A || vibrator motor controller || Unsupported || No datasheet, but probably only requires SoC PWM+GPIO, Samsung driver ca. 500LoC (''drivers/motor/isa1000a_vibrator.c'')
|-
| Unknown IC || hall effect sensor, crown || Unsupported || Connected via I2C, Samsung driver at ''drivers/input/misc/sec_rotary.c'', ~1300LoC
|-
| CYTMA525 || touchscreen controller || Supported
|-
| MAX77836 || MUIC || Supported || downstream kernel judges jig modes based on resistor connected to this via USB
|-
| ATSAMG55G19A || sensor hub || unknown || possibly supported via "Samsung sensor hub" driver. Sensor chips are connected to this and not the SoC directly.
|-
| Unknown (marked "OCTA") || LCD controller || unknown || unknown
|}

==== Debugging and Jigs ====

The device exposes a UART via the USB pads if ID is connected to GND with a 619k resistor. D+ goes to TX on the TTL adapter and D- goes to RX. VCC does not need to be connected. [https://web.archive.org/web/20231221120727/https://xdaforums.com/t/guide-usb-uart-on-galaxy-s-devices-2012-09-25.1901376/ This works identically to other Samsung smartphones].

Connecting to the device via UART yields the following output on startup:<syntaxhighlight line="1">
= 0x00
PMIC_STATUS1 = 0x27
PMIC_STATUS2 = 0x11
PMIC_OFFSRC = 0x00
PMIC_PWRON = 0x08
PMIC_IRQ1 = 0xc3
PMIC_IRQ2 = 0x11
PMIC_IRQ3 = 0x00
PMIC_RTC_OFFSRC = 0x00
PMIC_RTC_SMPL = 0x23
pwm-0: stop, tcon = 0x510000
pwm-0: prescaler = 1, divider = 3
pwm-0: src clk = 50000000, prescaler = 1, div = 8
pwm-0: freq = 3125000, request freq = 25344
pwm-0: tcnt = 0x7b, tcmp = 0x79
s5p_check_reboot_mode: INFORM3 = 0 ... skip
board_ps_hold_control: state (1)
s5p_reboot_menu_is_7sec_reset
debug_level: 0x00004f4c (20300)
pwron-ap: 0x00010000 (hard reset)
pwron-pmic: 0x00000008 (mrst)
s5p_reboot_menu_is_7sec_reset: 7sec reset at low debug level
cmu_div:65535, div:1, src_clk:0, pixel_clk:15552000
reset_lcd by s6e36w1x01
s5p_dsim_display_config: COMMAND MODE
display id: 40, 20, 15
s5p_reboot_menu_is_7sec_reset: timeout
target reboot with swreset as workaround
s5p_restart_handler ('N':normal)

OMUIC rev = MAX14577(117)
MON: 0x65(4)
MON[0] = (4)[0x37, 0xe8]
MON[1] = (5)[0x39, 0xe8]
MON[2] = (6)[0x3a, 0xc0]
MON[3] = (7)[0x0c, 0x14]
MON[4] = (0)[0x36, 0xe8]
MON[5] = (1)[0x32, 0xfc]
MON[6] = (2)[0x18, 0x20]
MON[7] = (3)[0x0a, 0x00]
cardtype: 0x00000007
buswidth: 0x00
hstiming: 0x00
SB_MMC_HS_52MHZ_1_8V_3V_IO
mmc->card_caps: 0x00000f11
mmc->host_caps: 0x00000f11
!!!Enter 8 Bit DDR mode.!!!
[mmc] capacity = 7634944

MODEL_NAME:{{SM-R732}}
eMMC_SERIAL_NUMBER:{{150100464A32354441008825557FC261}}
</syntaxhighlight>

=== Current port state ===

Porting currently on hold due to lifting pins from the board, resulting in a bricked watch which can no longer be recovered via USB.

WC1

2023-12-19T12:33:07Z

Casept: Add a bunch of hardware and flashing info