AsteroidOS - User contributions [en]

Seluna/solios

2025-10-26T20:07:45Z

Jrt:

[[Category:Watches]]
seluna (Pixel Watch 3 LTE) and solios (Pixel Watch 3 Wi-Fi/Bluetooth) are Android 16 smartwatches featuring the Qualcomm Snapdragon W5 Gen 1 chipset (monaco).{{Watches
|Name=seluna,solios
|Model=Google Pixel Watch 3
|Chipset=sw5100
|AndroidVersion=16}}

= Description =
This watch is sold in 4 variations. LTE and Wi-Fi versions in both 41 mm and 45 mm:
{| class="wikitable"
|-
! Codename !! Model Name
!Note
|-
| seluna || Pixel Watch 3 LTE
|selene+luna=seluna=common LTE platform
|-
|selene
|Pixel Watch 3 LTE (41 mm)
|Resolution: 408x408
|-
|luna
|Pixel Watch 3 LTE (45 mm)
|Resolution: 456x456
|-
| solios || Pixel Watch 3 Wi-Fi
|sol+helios=solios=common Wi-Fi platform
|-
|helios
|Pixel Watch 3 Wi-Fi (41 mm)
|Resolution: 408x408
|-
|sol
|Pixel Watch 3 Wi-Fi (41 mm)
|Resolution: 456x456
|}

=== Bootloader Unlock ===
The bootloader of the Pixel Watch 3 can be unlocked by enabling “OEM unlock” within the Android developer options, rebooting into bootloader mode via ADB and unlocking afterward via fastboot.<syntaxhighlight lang="bash">
# reboot to bootloader
adb reboot bootloader

# check if the watch is unlockable. If yes it returns "1"
fastboot flashing get_unlock_ability

# ask the device to prompt for bootloader unlock
fastboot flashing unlock
</syntaxhighlight>After issuing the unlock command, the action must be confirmed on the watch.

=== Repair ===
The Pixel Watch 3 has replaceable straps, but the device is glued shut, making repair attempts harder.

=== Firmware ===
OTA firmware images are available on [https://developers.google.com/android/ota-watch?hl=de#seluna developers.google.com]. The zip files contain a file called payload.bin that can be extracted with [https://github.com/ssut/payload-dumper-go payload-dumper-go].

Once extracted, the partitions are contained in named image files. e.g. <code>boot.img</code>.

Seluna/solios

2025-10-26T20:00:29Z

Jrt: sol+helios

[[Category:Watches]]
seluna (Pixel Watch 3 LTE) and solios (Pixel Watch 3 Wi-Fi/Bluetooth) are Android 16 smartwatches featuring the Qualcomm Snapdragon W5 Gen 1 chipset.{{Watches
|Name=seluna,solios
|Model=Google Pixel Watch 3
|Chipset=sw5100
|AndroidVersion=16}}

= Description =
This watch is sold in 4 variations. LTE and Wi-Fi versions in both 41 mm and 45 mm:
{| class="wikitable"
|-
! Codename !! Model Name
!Note
|-
| seluna || Pixel Watch 3 LTE
|selene+luna=seluna=common LTE platform
|-
|selene
|Pixel Watch 3 LTE (41 mm)
|Resolution: 408x408
|-
|luna
|Pixel Watch 3 LTE (45 mm)
|Resolution: 456x456
|-
| solios || Pixel Watch 3 Wi-Fi
|sol+helios=solios=common Wi-Fi platform
|-
|helios
|Pixel Watch 3 Wi-Fi (41 mm)
|Resolution: 408x408
|-
|sol
|Pixel Watch 3 Wi-Fi (41 mm)
|Resolution: 456x456
|}

=== Bootloader Unlock ===
The bootloader of the Pixel Watch 3 can be unlocked by enabling “OEM unlock” within the Android developer options, rebooting into bootloader mode via ADB and unlocking afterward via fastboot.<syntaxhighlight lang="bash">
# reboot to bootloader
adb reboot bootloader

# check if the watch is unlockable. If yes it returns "1"
fastboot flashing get_unlock_ability

# ask the device to prompt for bootloader unlock
fastboot flashing unlock
</syntaxhighlight>After issuing the unlock command, the action must be confirmed on the watch.

=== Repair ===
The Pixel Watch 3 has replaceable straps, but the device is glued shut, making repair attempts harder.

=== Firmware ===
OTA firmware images are available on [https://developers.google.com/android/ota-watch?hl=de#seluna developers.google.com]. The zip files contain a file called payload.bin that can be extracted with [https://github.com/ssut/payload-dumper-go payload-dumper-go].

Once extracted, the partitions are contained in named image files. e.g. <code>boot.img</code>.

Seluna/solios

2025-10-26T19:59:30Z

Jrt: sol+helios

[[Category:Watches]]
seluna (Pixel Watch 3 LTE) and solios (Pixel Watch 3 Wi-Fi/Bluetooth) are Android 16 smartwatches featuring the Qualcomm Snapdragon W5 Gen 1 chipset.{{Watches
|Name=seluna,solios
|Model=Google Pixel Watch 3
|Chipset=sw5100
|AndroidVersion=16}}

= Description =
This watch is sold in 2 variations:
{| class="wikitable"
|-
! Codename !! Model Name
!Note
|-
| seluna || Pixel Watch 3 LTE
|selene+luna=seluna=common LTE platform
|-
|selene
|Pixel Watch 3 LTE (41 mm)
|Resolution: 408x408
|-
|luna
|Pixel Watch 3 LTE (45 mm)
|Resolution: 456x456
|-
| solios || Pixel Watch 3 Wi-Fi
|sol+helios=solios=common Wi-Fi platform
|-
|helios
|Pixel Watch 3 Wi-Fi (41 mm)
|Resolution: 408x408
|-
|sol
|Pixel Watch 3 Wi-Fi (41 mm)
|Resolution: 456x456
|}

=== Bootloader Unlock ===
The bootloader of the Pixel Watch 3 can be unlocked by enabling “OEM unlock” within the Android developer options, rebooting into bootloader mode via ADB and unlocking afterward via fastboot.<syntaxhighlight lang="bash">
# reboot to bootloader
adb reboot bootloader

# check if the watch is unlockable. If yes it returns "1"
fastboot flashing get_unlock_ability

# ask the device to prompt for bootloader unlock
fastboot flashing unlock
</syntaxhighlight>After issuing the unlock command, the action must be confirmed on the watch.

=== Repair ===
The Pixel Watch 3 has replaceable straps, but the device is glued shut, making repair attempts harder.

=== Firmware ===
OTA firmware images are available on [https://developers.google.com/android/ota-watch?hl=de#seluna developers.google.com]. The zip files contain a file called payload.bin that can be extracted with [https://github.com/ssut/payload-dumper-go payload-dumper-go].

Once extracted, the partitions are contained in named image files. e.g. <code>boot.img</code>.

Seluna/solios

2025-10-26T19:37:36Z

Jrt:

[[Category:Watches]]
seluna (Pixel Watch 3 LTE) and solios (Pixel Watch 3 Wi-Fi/Bluetooth) are Android 16 smartwatches featuring the Qualcomm Snapdragon W5 Gen 1 chipset.{{Watches
|Name=seluna,solios
|Model=Google Pixel Watch 3
|Chipset=sw5100
|AndroidVersion=16}}

= Description =
This watch is sold in 2 variations:
{| class="wikitable"
|-
! Codename !! Model Name
!Note
|-
| seluna || Pixel Watch 3 LTE
|selene+luna=seluna=common LTE platform
|-
|selene
|Pixel Watch 3 LTE (41 mm)
|Resolution: 408x408
|-
|luna
|Pixel Watch 3 LTE (45 mm)
|Resolution: 456x456
|-
| solios || Pixel Watch 3 Wi-Fi/Bluetooth
|
|}

=== Bootloader Unlock ===
The bootloader of the Pixel Watch 3 can be unlocked by enabling “OEM unlock” within the Android developer options, rebooting into bootloader mode via ADB and unlocking afterward via fastboot.<syntaxhighlight lang="bash">
# reboot to bootloader
adb reboot bootloader

# check if the watch is unlockable. If yes it returns "1"
fastboot flashing get_unlock_ability

# ask the device to prompt for bootloader unlock
fastboot flashing unlock
</syntaxhighlight>After issuing the unlock command, the action must be confirmed on the watch.

=== Repair ===
The Pixel Watch 3 has replaceable straps, but the device is glued shut, making repair attempts harder.

=== Firmware ===
OTA firmware images are available on [https://developers.google.com/android/ota-watch?hl=de#seluna developers.google.com]. The zip files contain a file called payload.bin that can be extracted with [https://github.com/ssut/payload-dumper-go payload-dumper-go].

Once extracted, the partitions are contained in named image files. e.g. <code>boot.img</code>.

Seluna/solios

2025-10-26T19:14:25Z

Jrt:

[[Category:Watches]]
seluna (Pixel Watch 3 LTE) and solios (Pixel Watch 3 Wi-Fi/Bluetooth) are Android 16 smartwatches featuring the Qualcomm Snapdragon W5 Gen 1 chipset.{{Watches
|Name=seluna,solios
|Model=Google Pixel Watch 3
|Chipset=sw5100
|AndroidVersion=16}}

= Description =
This watch is sold in 2 variations:
{| class="wikitable"
|-
! Codename !! Model Name
|-
| seluna || Pixel Watch 3 LTE
|-
| solios || Pixel Watch 3 Wi-Fi/Bluetooth
|}

=== Bootloader Unlock ===
The bootloader of the Pixel Watch 3 can be unlocked by enabling “OEM unlock” within the Android developer options, rebooting into bootloader mode via ADB and unlocking afterward via fastboot.<syntaxhighlight lang="bash">
# reboot to bootloader
adb reboot bootloader

# check if the watch is unlockable. If yes it returns "1"
fastboot flashing get_unlock_ability

# ask the device to prompt for bootloader unlock
fastboot flashing unlock
</syntaxhighlight>After issuing the unlock command, the action must be confirmed on the watch.

=== Repair ===
The Pixel Watch 3 has replaceable straps, but the device is glued shut, making repair attempts harder.

=== Firmware ===
OTA firmware images are available on [https://developers.google.com/android/ota-watch?hl=de#seluna developers.google.com]. The zip files contain a file called payload.bin that can be extracted with [https://github.com/ssut/payload-dumper-go payload-dumper-go].

Once extracted, the partitions are contained in named image files. e.g. <code>boot.img</code>.

Seluna/solios

2025-10-26T16:34:02Z

Jrt:

Seluna/solios

2025-10-26T16:25:25Z

Jrt:

{{Watches
|Name=seluna
|Model=Google Pixel Watch 3 (LTE)
|Chipset=sw5100
}}
[[Category:Watches]]
seluna (Pixel Watch 3 LTE) and solios (Pixel Watch 3 Wi-Fi/Bluetooth) are Android 16 smartwatches featuring the Qualcomm Snapdragon W5 Gen 1 chipset.

= Description =
This watch is sold in 2 variations:
{| class="wikitable"
|-
! Codename !! Model Name
|-
| seluna || Pixel Watch 3 LTE
|-
| solios || Pixel Watch 3 Wi-Fi/Bluetooth
|}

=== Bootloader Unlock ===
The bootloader of the Pixel Watch 3 can be unlocked by enabling “OEM unlock” within the Android developer options, rebooting into bootloader mode via ADB and unlocking afterward via fastboot.<syntaxhighlight lang="bash">
# reboot to bootloader
adb reboot bootloader

# check if the watch is unlockable. If yes it returns "1"
fastboot flashing get_unlock_ability

# ask the device to prompt for bootloader unlock
fastboot flashing unlock
</syntaxhighlight>After issuing the unlock command, the action must be confirmed on the watch.

=== Repair ===
The Pixel Watch 3 has replaceable straps, but the device is glued shut, making repair attempts harder.

Seluna/solios

2025-10-26T16:20:15Z

Jrt: bootloader unlock procedure

Seluna/solios

2025-10-26T15:50:44Z

Jrt: Created page with "{{Watches |Name=seluna |Model=Google Pixel Watch 3 (LTE) |Chipset=sw5100 }} Category:Watches seluna (Pixel Watch 3 LTE) and solios (Pixel Watch 3 Wi-Fi/Bluetooth) are Android 16 smartwatches featuring the Qualcomm Snapdragon W5 Gen 1 chipset. = Description = This watch is sold in 2 variations: {| class="wikitable" |- ! Codename !! Model Name |- | seluna || Pixel Watch 3 LTE |- | solios || Pixel Watch 3 Wi-Fi/Bluetooth |}"

Useful Commands

2025-10-25T09:51:16Z

Jrt: systemctl --force reboot bootloader doesn't work anymore. systemd has a reboot argument that gets passed to the reboot syscall. Passing "bootloader" works as before and doesn't require the --force anymore

AsteroidOS comes with several command line tools that are very handy to control a watch from [[SSH]] or a script. This page tries to document the basic features of those commands, don't hesitate to use their <code>--help</code> options if you want to learn more.

Commands and gestures to enter the fastboot (bootloader) mode are listed at the bottom of this page.

== Notifications ==

AsteroidOS complies to the [freedesktop.org notifications specification](https://specifications.freedesktop.org/notification-spec/notification-spec-latest.html), which means you can use standard Linux desktop tools such as libnotify to show notifications in asteroid-launcher.
On AsteroidOS a useful command named <code>notificationtool</code> is provided that allows you to create/update/close/list notifications from the CLI.

Following example creates a new notification with various parameters
<pre>
notificationtool -o add \
--icon=ios-happy \
--application="Super App" \
--urgency=3 \
--hint="x-nemo-preview-summary Incredible preview title" \
--hint="x-nemo-preview-body Exceptional preview content" \
--hint="x-nemo-feedback notif_strong" \
"Great Title" \
"Amazing content"
</pre>

== Launch applications ==

AsteroidOS uses an <code>invoker</code> to launch apps. The invoker is used to allow for quicker app startup by caching many of the Qt components into memory.

This example launches the alarm clock app using the invoker and hides the title bar.
Ensure that this command is executed under the <code>ceres</code> user.
<pre>
EGL_PLATFORM=wayland \
QT_QPA_PLATFORM=wayland \
QT_WAYLAND_DISABLE_WINDOWDECORATION=1 \
invoker --single-instance --type=qt5 \
/usr/lib/asteroid-alarmclock
</pre>

== Screenshots ==

The AsteroidOS Wayland compositor is named asteroid-launcher, it is based on lipstick which offers a DBus API to take screenshots. This DBus interface can be used from the command line with dbus-send but a tool named screenshottool makes the usage of this command easier.

Save a screenshot in <code>$HOME</code> after 3 seconds
<pre>
screenshottool /home/ceres/screenshot.jpg 3
</pre>

== Alarms ==

Managing the time is very important on a smartwatch. Systemd provides basic timer capabilities but the timed daemon goes further and is much more capable. This daemon also comes with a tool named <code>timedclient-qt5</code> that can help you run commands on special events.

Execute the /home/ceres/test.sh script every day at 12:15
<pre>
timedclient-qt5 -a'whenDue;runCommand=/home/ceres/test.sh@ceres' \
-r'hour=12;minute=15;everyDayOfWeek;everyDayOfMonth;everyMonth' \
-e'APPLICATION=Test;TITLE=Test'
</pre>

== USB ==

In AsteroidOS, the USB mode is handled by a daemon named usb_moded. This daemon offers a DBus interface that is exposed to the GUI by asteroid-launcher and asteroid-settings. However, usb_moded also comes with a command named <code>usb_moded_util</code> to control this DBus interface from the command line.

Return a list of supported modes:
<pre>usb_moded_util -m</pre>
Show the currently used USB mode:
<pre>usb_moded_util -q</pre>
Set USB to the ADB Mode:
<pre>usb_moded_util -s adb_mode</pre>

== Screen ==

A daemon named MCE is in charge of handling various screen related behaviors. For example, MCE handles the device locking, the tap to unlock, the current brightness, fading and dimming and others.... It can be controlled thanks to a CLI tool named <code>mcetool</code>.

Display the current state of various variables:
<pre>mcetool</pre>
Enable "demo mode": screen stays on:
<pre>mcetool -D on</pre>
Disable the tap to unlock functionality:
<pre>mcetool -M disabled</pre>

== Restart ==

Systemd is the init system used by AsteroidOS. It is controlled by a command named <code>systemctl</code>. This command can be used to restart the user session or the entire system into a different mode.

Restart the ceres session (including the entire UI):
<pre>systemctl restart user@1000</pre>
Simply reboot your watch:
<pre>reboot</pre>
Restart the watch in bootloader mode:
<pre>systemctl reboot --reboot-argument=bootloader</pre>
Restart the watch in recovery mode:
<pre>systemctl reboot --reboot-argument=recovery</pre>

== Time zone, date & time ==

Although we offer [[Synchronization Clients | synchronisation clients]] for different platforms, it might still be useful to set the time zone or synchronise the date and time using standard Linux tools. The Linux folder <code>/usr/share/zoneinfo/</code> contains the naming scheme for your local time zone in <code><continent>/<zone></code> format.

<pre>ssh root@192.168.2.15 "timedatectl set-timezone <continent>/<zone>"</pre>
<pre>ssh root@192.168.2.15 "date -s @`(date -u +"%s" )`"</pre>

= Boot to fastboot (bootloader) menu =

In case you can not boot to the fastboot menu using
<pre>adb reboot bootloader</pre>
Try the manual method for your watch specified below. These methods come in very handy in case your watch does neither boot AsteroidOS, nor WearOS successfully in its current state.

==== Anthias, Bass, Dory, Lenok, Mooneye, Sparrow, Swift, Wren====
During the first seconds of the boot process, swipe diagonally across the screen. Starting from the top/left outer edge of the screen to the bottom/right.

==== Catfish, hoki, Skipjack====
Power down the watch. Keep holding both buttons during the boot process until the fastboot menu appears.

==== Firefish, Ray====
After the watch stops vibrating on startup, immediately touch the top/left & bottom/right of the screen and press the middle button while the manufacturer logo displays.

==== Nemo, triggerfish====
Power down the watch. Keep holding the lower button while powering on the device.

==== Pike====
Power down the watch. Keep holding both buttons during the boot process, then select fastboot from the menu.

==== Sawfish, Sawshark, Sturgeon====
Press and hold the power button when the manufacturer bootlogo appears, until the vibration finishes. Release the button and press it again quickly. The time frame for this method is short and might need several attempts. Some users report that spamming power button presses already during the vibration helps.

==== Smelt====
Keep holding the power button during the boot process and release it quickly after the second (double) vibration.

Mercury

2024-02-13T21:39:04Z

Jrt:

<code>mercury</code> is known under the name "Ticwatch 2 international", "Ticwatch 2i" or "Ticwatch 2 i18n" and uses the [https://www.mediatek.com/products/wearables/mt2601 MediaTek MT2601] SoC.
[[File:Ticwatch 2 internals.jpg|alt=Ticwatch 2 internals|thumb|Ticwatch 2 internals]]

==== Partitions ====
<syntaxhighlight lang="bash" line="1">
GUID Partition Table (EFI)
Offset Sector: 0
Units are in 512-byte sectors

Slot Start End Length Description
000: Meta 0000000000 0000000000 0000000001 Safety Table
001: ------- 0000000000 0000001023 0000001024 Unallocated
002: Meta 0000000001 0000000001 0000000001 GPT Header
003: Meta 0000000002 0000000006 0000000005 Partition Table
004: 000 0000001024 0000007167 0000006144 proinfo
005: 001 0000007168 0000017407 0000010240 nvram
006: 002 0000017408 0000037887 0000020480 protect1
007: 003 0000037888 0000058367 0000020480 protect2
008: 004 0000058368 0000058623 0000000256 seccfg
009: 005 0000058624 0000059391 0000000768 lk
010: 006 0000059392 0000073727 0000014336 boot
011: 007 0000073728 0000088063 0000014336 recovery
012: 008 0000088064 0000088575 0000000512 secro
013: 009 0000088576 0000089599 0000001024 para
014: 010 0000089600 0000095743 0000006144 logo
015: 011 0000095744 0000161279 0000065536 nvdata
016: 012 0000161280 0000196607 0000035328 expdb
017: 013 0000196608 0001835007 0001638400 system
018: 014 0001835008 0002457599 0000622592 cache
019: 015 0002457600 0005029887 0002572288 userdata
020: 016 0005029888 0007590911 0002561024 intsd
021: 017 0007590912 0007633919 0000043008 flashinfo
</syntaxhighlight>

==== boot.img configuration ====
<syntaxhighlight line="1">
bootsize = 0x700000
pagesize = 0x800
kerneladdr = 0x10008000
ramdiskaddr = 0x11000000
secondaddr = 0x10f00000
tagsaddr = 0x10000100
name = 1516354717
cmdline =
</syntaxhighlight>

==== Stock Firmware Linux Version ====
<syntaxhighlight lang="bash" line="1">
cat /proc/version
Linux version 3.10.72+ (jenkins@mobvoi-indiana) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Fri Jan 19 17:19:11 CST 2018
</syntaxhighlight>

==== Relevant build.prop fields ====
<syntaxhighlight line="1">
[ro.btstack]: [blueangel]
[ro.build.characteristics]: [watch]
[ro.build.date.utc]: [1516353162]
[ro.build.date]: [Fri Jan 19 17:12:42 CST 2018]
[ro.build.description]: [mercury_i18n-user 5.1 LMY47I 1516353091 release-keys]
[ro.build.display.id]: [LMY47I]
[ro.build.fingerprint]: [TIC/mercury_i18n/mercury:5.1/LMY47I/1516353091:user/release-keys]
[ro.build.flavor]: [mercury_i18n-user]
[ro.build.host]: [mobvoi-indiana]
[ro.build.id]: [LMY47I]
[ro.build.product]: [mercury]
[ro.build.tags]: [release-keys]
[ro.build.type]: [user]
[ro.build.user]: [jenkins]
[ro.mediatek.platform]: [MT2601]
[ro.mediatek.project.path]: [device/mobvoi/mercury_i18n]
[ro.mediatek.version.branch]: [L1.MP9]
[ro.mediatek.version.release]: [ALPS.L1.MP9.V3.8_MOBVOI2601.WP.L]
[ro.product.brand]: [TIC]
[ro.product.cpu.abi2]: [armeabi]
[ro.product.cpu.abi]: [armeabi-v7a]
[ro.product.cpu.abilist32]: [armeabi-v7a,armeabi]
[ro.product.cpu.abilist64]: []
[ro.product.cpu.abilist]: [armeabi-v7a,armeabi]
[ro.product.device]: [mercury]
[ro.product.locale.language]: [en]
[ro.product.locale.region]: [US]
[ro.product.manufacturer]: [Mobvoi Inc.]
[ro.product.model]: [Ticwatch2-i18n]
[ro.product.name]: [mercury_i18n]
[mediatek.wlan.chip]: [MT6630]

</syntaxhighlight>

==== Misc Hardware Info ====
The metal part of the watch where “Model: WE12016” is engraved is a sticker with a metal look and can be removed. Once the sticker is removed, the watch exposes 6 pads, with 5 of them connected internally. The current working theory is that the pads are USB.
[[File:Ticwatch2 pads.jpg|alt=Ticwatch 2 with model number sticker removed, exposing pads|thumb|Ticwatch 2 with model number sticker removed, exposing pads]]

Mercury

2024-02-13T21:38:56Z

Jrt:

Mercury

2024-02-13T21:38:37Z

Jrt:

Mercury

2024-02-13T21:15:40Z

Jrt:

File:Ticwatch 2 internals.jpg

2024-02-13T21:14:36Z

Jrt:

Ticwatch 2 internals

Mercury

2024-02-13T21:11:02Z

Jrt: info about possible usb pads

<code>mercury</code> is known under the name "Ticwatch 2 international", "Ticwatch 2i" or "Ticwatch 2 i18n" and uses the [https://www.mediatek.com/products/wearables/mt2601 MediaTek MT2601] SoC.

==== Misc Hardware Info ====
The metal part of the watch where “Model: WE12016” is engraved is a sticker with a metal look and can be removed. Once the sticker is removed, the watch exposes 6 pads, with 5 of them connected internally. The current working theory is that the pads are USB.
[[File:Ticwatch2 pads.jpg|alt=Ticwatch 2 with model number sticker removed, exposing pads|thumb|Ticwatch 2 with model number sticker removed, exposing pads]]

File:Ticwatch2 pads.jpg

2024-02-13T21:09:48Z

Jrt:

Ticwatch 2 (mercury) with model number sticker removed

Mercury

2024-02-13T16:23:27Z

Jrt:

<code>mercury</code> is known under the name "Ticwatch 2 international", "Ticwatch 2i" or "Ticwatch 2 i18n" and uses the [https://www.mediatek.com/products/wearables/mt2601 MediaTek MT2601] SoC.

Mercury

2024-02-13T16:23:10Z

Jrt: Created page with "mercury is known under the name "Ticwatch 2 international", "Ticwatch 2i" or "Ticwatch 2 i18n" and uses the [https://www.mediatek.com/products/wearables/mt2601 MediaTek MT2601] SoC."

mercury is known under the name "Ticwatch 2 international", "Ticwatch 2i" or "Ticwatch 2 i18n" and uses the [https://www.mediatek.com/products/wearables/mt2601 MediaTek MT2601] SoC.

GW4

2023-12-21T12:14:12Z

Jrt:

{{DISPLAYTITLE:Samsung Galaxy Watch 4}}

The Samsung Galaxy Watch 4 (LTE) is a round smartwatch that is one of the first ones to contain a bioelectrical impedance analysis (BIA) sensor.

{| class="wikitable"
|+ Samsung Galaxy Watch 4
|-
| Model number || SM-R860, SM-R870, SM-R880, SM-R890 (Wi-Fi only), SM-R865U, SM-R875U, SM-R885U, SM-R895U (USA, LTE model), SM-R895F (Int., LTE model)
|-
| Memory || 1.5 GB
|-
| Storage || 16 GB
|-
| SoC || Exynos W920 dual core 1.18 GHz; GPU: Mali-G68
|-
| Sensors ||
* Heart rate monitor
* Bioelectrical Impedance Analysis
* Accelerometer
* Gyroscope
* Barometer
|-
| Battery || Non-removable 247mAh / 361mAh
|}

=== Miscellaneous hardware docs ===

==== Manually getting into Download or Recovery Mode ====
Press and hold both buttons until the "Rebooting..." screen appears. Release both buttons and press the power button (red outline) 3 times.

The reboot menu should be displayed. Press the power button to cycle between the options and confirm the selection with a long press (3 seconds).

==== Skipping initial setup ====
The pairing and setup of the watch can be skipped by pressing and holding down the Wear OS logo on the pairing screen.

==== Debugging and Jigs ====
The device probably exposes a UART via the USB pads if ID is connected to GND with a 619k resistor, similar to the [[WC1]]. This is currently untested.

GW4

2023-12-21T12:13:31Z

Jrt:

{{DISPLAYTITLE:Samsung Galaxy Watch 4}}

The Samsung Galaxy Watch 4 (LTE) is a round smartwatch that is one of the first ones to contain a bioelectrical impedance analysis (BIA) sensor.

{| class="wikitable"
|+ Samsung Galaxy Watch 4
|-
| Model number || SM-R860, SM-R870, SM-R880, SM-R890 (Wi-Fi only), SM-R865U, SM-R875U, SM-R885U, SM-R895U (USA, LTE model), SM-R895F (Int., LTE model)
|-
| Memory || 1.5 GB
|-
| Storage || 16 GB
|-
| SoC || Exynos W920 dual core 1.18 GHz; GPU: Mali-G68
|-
| Sensors ||
* Heart rate monitor
* Bioelectrical Impedance Analysis
* Accelerometer
* Gyroscope
* Barometer
|-
| Battery || Non-removable 247mAh / 361mAh
|}

=== Miscellaneous hardware docs ===

==== Manually getting into Download or Recovery Mode ====
Press and hold both buttons until the "Rebooting..." screen appears. Release both buttons and press the power button (red outline) 3 times.

The reboot menu should be displayed. Press the power button to cycle between the options and confirm the selection with a long press (3 seconds).

==== Skipping initial setup ====
The pairing and setup of the watch can be skipped by pressing and holding down the Wear OS logo on the pairing screen.

==== Debugging and Jigs ====
The device probably exposes a UART via the USB pads if ID is connected to GND with a 619k resistor. This is currently untested.

WC1

2023-12-21T12:09:01Z

Jrt:

== 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>

WC1

2023-12-21T11:23:26Z

Jrt: /* Debugging and Jigs */

== 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. 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>

WC1

2023-12-16T12:37:29Z

Jrt: Created page with "== Galaxy Gear S2 Classic =="

== Galaxy Gear S2 Classic ==

Building AsteroidOS

2023-10-21T14:44:35Z

Jrt: Replaced user selected AUR helper and pacman wrapper with standard pacman, since all packages are available in the default repositories.

[[Category:Developers]]
If you decide to compile AsteroidOS from source be aware that it’s a simple process but requires a lot of disk space (potentially more than 100GB) and the first build might take you a lot of time (hours). Report any problem to the [https://github.com/AsteroidOS/asteroid/issues issue tracker]:

[https://asteroidos.org/asteroid.mp4 Video showing the build process]

= General information =

You might want to build AsteroidOS in a ''container engine'' such as [https://www.docker.com/ Docker] or [https://podman.io/ podman] because you'll get a clean build environment that works no matter what kinds of package repositories or package versions you have installed or how outdated your Linux distribution is or which Linux distribution you're using in the first place.

Another advantage of Docker specifically is that it ''should'' also work on Windows and OS X. (However, this has not been tested yet!)

Using containers also allows you to easily roll back. Without a container, if you decided to delete the AsteroidOS repository and uninstall the prerequisite software packages from your computer, you will potentially remove packages that you had installed before and might actually still need. With a container, simply deleting the container image has no other effect on the host computer.

= Clone the repository =

Clone the main repository using the following command:

<pre>
git clone https://github.com/AsteroidOS/asteroid.git
</pre>

If you haven't set a global git name and email yet, adapt the following ''git config'' commands to your information. (This is only required to clone some git repositories when building.)

<pre>
git config --global user.email "you@example.com"
git config --global user.name "Your Name"
</pre>

Before you continue to ''Build without containers'' or ''Build with containers'', make sure you're in the asteroid directory:

<pre>
cd asteroid/
</pre>

= Build without containers =

== Downloading ==

Install the prerequisites:

{| class="wikitable"
|+ Distribution prerequisite installation
|-
! Distro !! Command
|-
| Ubuntu || <code>apt-get install git build-essential chrpath cpio diffstat gawk liblz4-tool python3 shared-mime-info texinfo wget zstd </code>
|-
| Fedora || <code>dnf install chrpath diffstat g++ lz4 perl perl-bignum python3-pip rpcgen socat texinfo</code>
|-
| Arch || <code>pacman -Sy base-devel chrpath cpio diffstat gawk lz4 python3 rpcsvc-proto shared-mime-info texinfo wget zstd</code>
|-
| Alpine || <code>apk add binutils chrpath gcc g++ gawk gcc lz4 make patch perl rpcgen</code> <br>Note: Alpine Linux does not contain diffstat in its repositories, thus you have to [https://github.com/asottile-archive/diffstat build it yourself from source].
|}

This repository basically only contains a shell script that populates <code>src/</code> with OpenEmbedded and the appropriate Asteroid layers. Then, it setups the environment for a bitbake build. The following command will setup a build for <code>dory</code> (the LG G Watch) but you can also build an image for other watches by using the corresponding codename. (Codenames can be found on the [https://asteroidos.org/watches/ Watches page].)

<pre>
source ./prepare-build.sh dory # Be careful that this script must be sourced and not only ran
</pre>

If the environment has been correctly setup, you should now be in the <code>build</code> subdirectory.

== Building ==

Once the environment is prepared, you can simply trigger a build with the following command:

<pre>
bitbake asteroid-image
</pre>
''Notes:''
1) The build process requires roughly 2GB memory per thread. It might be necessary to limit the number of threads. This can be done by prepending <code>BB_NUMBER_THREADS=n</code> to the build command. Or by adding <code>BB_NUMBER_THREADS = "n"</code> to <code>build/conf/local.conf</code>. Where <code>n</code> is the amount of threads.
2) Bitbake is a powerful tool that can also build single packages (e.g: <code>bitbake strace</code>) or [Creating an Asteroid app#Building the Cross Compilation Toolchain|building the SDK] for example. Refer to its documentation for more details.

If this step was successful, you can proceed to the [[#Installing|Installing]] section below.

== Updating the Sources ==

You can update the AsteroidOS sources with the following command:

<pre>
source ./prepare-build.sh update
</pre>

= Build with containers =

These instructions have been tested on Ubuntu 19.04 (with Docker) and Fedora 34 (with podman), but should also be applicable to Debian Sid (at least at the time of writing). For other distributions the dependencies may have different names and you may have to install additional ones.

From a user's point of view, Docker and podman are quite similar and accept almost all of the exact same commands, but there are some difference. The most significant differences for building Asteroid are that podman does not use a daemon and can be run "rootless" (that is, as a non-root user). This makes some things a bit easier, but either can be used.

== Setup ==

Remove the Docker container called <code>asteroidos-toolchain</code> if it already exists:

<pre>
sudo docker rm -f asteroidos-toolchain
</pre>
or
<pre>
podman rm -f asteroidos-toolchain
</pre>

Build a container image called <code>asteroidos-toolchain</code> from the given Dockerfile:

<pre>
sudo docker build --tag asteroidos-toolchain .
</pre>
or
<pre>
podman build --tag asteroidos-toolchain .
</pre>

== Building the software ==

Now that the container with the toolchain software has been created, we can use this to build AsteroidOS. All of the tools are contained and run within the container, but we use a ''shared volume'', essentially some drive space that both the host computer and the container can read and write, for actually creating the AsteroidOS image files.

In this example, we will build AsteroidOS for <code>dory</code>(the LG G Watch). To build for a different watch than the LG G Watch, use its corresponding codename instead of <code>dory</code> when executing the <code>docker run ...</code> command. You can find the codenames for the supported watches on the [https://asteroidos.org/watches/ Watches page].

Assuming that you have carefully followed the instructions so far and are in the <code>asteroid</code> directory, you can now build the software.

'''Run this as a non root user''':

<pre>
sudo docker run \
--rm \
-it \
-v /etc/passwd:/etc/passwd:ro \
-u "$(id -u):$(id -g)" \
-v "$HOME/.gitconfig:/$HOME/.gitconfig:ro" \
-v "$(pwd):/asteroid" asteroidos-toolchain \
bash -c "source ./prepare-build.sh dory && bitbake asteroid-image"
</pre>
or
<pre>
podman run \
--rm \
-it \
-v "$(pwd)":/asteroid:z \
--userns keep-id asteroidos-toolchain \
bash -c "source ./prepare-build.sh dory && bitbake asteroid-image"
</pre>

The files created during the build are placed in the current directory; more specifically, the source files are placed in a <code>src</code> subdirectory and build artefacts, including the final binary images are placed in the <code>build</code> subdirectory.

Here is a detailed explanation of the Docker command above:

*<code>sudo docker run</code> Runs a container image
*<code>--rm</code> Cleans up after the command is run by removing temporary container storage
*<code>-it</code> Attaches the terminal to the container so that we can see the output. Otherwise it would run blindly in the background.
*<code>-u "$(id -u):$(id -g)"</code> Ensures that the current user id and group id from the host is used on files inside the container to avoid permission issues.
*<code>-v /etc/passwd:/etc/passwd</code> Ensures that the user ids and groups from the host are also available in the Docker container. (Otherwise the <code>-u</code> and <code>-g</code> would be useless.)
*<code>/etc/passwd</code> Contains the user names and their ids.
*<code>"$HOME/.gitconfig:/$HOME/.gitconfig"</code> Share your user's git config with the container.
*<code>-v "$(pwd):/asteroid"</code> Mount the current directory (which is your asteroid git repo clone) into the container.
*<code>bash -c "source ./prepare-build.sh dory && bitbake asteroid-image"</code> This is the command to be executed inside of the container with "dory" being the codename of your watch.

Here is a detailed explanation of the podman version of the command above:

*<code>podman run</code> Runs a container image
*<code>--rm</code> Cleans up after the command is run by removing temporary container storage
*<code>-it</code> Attaches the terminal to the container so that we can see the output. Otherwise it would run blindly in the background.
*<code>-v "$(pwd)":/asteroid:z</code> Mount the current directory (which is your asteroid git repo clone) into the container. The <code>:z</code> tells SELinux, if it's running, to allow multiple containers to share this mount.
*<code>--userns keep-id</code> Run as the current user inside the container
*<code>bash -c "source ./prepare-build.sh dory && bitbake asteroid-image"</code> This is the command to be executed inside of the container with <code>dory</code> being the codename of your watch.

If this step was successful, you can proceed to [[#Installing|Installing]] below.

= Installing =

After a while, whether you build with or without containers, the generated image should be available in <code>build/tmp-glibc/deploy/images/dory/</code> (for <code>dory</code> -- for other watches, the image files are in the corresponding code word directory.)

Install AsteroidOS using your usual device's instructions, which you can find linked from the [https://asteroidos.org/watches/ Watches page].

GW4

2023-10-09T18:52:35Z

Jrt:

{{DISPLAYTITLE:Samsung Galaxy Watch 4}}

The Samsung Galaxy Watch 4 (LTE) is a round smartwatch that is one of the first ones to contain a bioelectrical impedance analysis (BIA) sensor.

{| class="wikitable"
|+ Samsung Galaxy Watch 4
|-
| Model number || SM-R860, SM-R870, SM-R880, SM-R890 (Wi-Fi only), SM-R865U, SM-R875U, SM-R885U, SM-R895U (USA, LTE model), SM-R895F (Int., LTE model)
|-
| Memory || 1.5 GB
|-
| Storage || 16 GB
|-
| SoC || Exynos W920 dual core 1.18 GHz; GPU: Mali-G68
|-
| Sensors ||
* Heart rate monitor
* Bioelectrical Impedance Analysis
* Accelerometer
* Gyroscope
* Barometer
|-
| Battery || Non-removable 247mAh / 361mAh
|}

=== Miscellaneous hardware docs ===

==== Manually getting into Download or Recovery Mode ====
Press and hold both buttons until the "Rebooting..." screen appears. Release both buttons and press the power button (red outline) 3 times.

The reboot menu should be displayed. Press the power button to cycle between the options and confirm the selection with a long press (3 seconds).

==== Skipping initial setup ====
The pairing and setup of the watch can be skipped by pressing and holding down the Wear OS logo on the pairing screen.

GW4

2023-10-09T18:00:00Z

Jrt: Recovery and Download (Odin) Mode

{{DISPLAYTITLE:Samsung Galaxy Watch 4}}

The Samsung Galaxy Watch 4 (LTE) is a round smartwatch that is one of the first ones to contain a bioelectrical impedance analysis (BIA) sensor.

{| class="wikitable"
|+ Samsung Galaxy Watch 4
|-
| Model number || SM-R860, SM-R870, SM-R880, SM-R890 (Wi-Fi only), SM-R865U, SM-R875U, SM-R885U, SM-R895U (USA, LTE model), SM-R895F (Int., LTE model)
|-
| Memory || 1.5 GB
|-
| Storage || 16 GB
|-
| SoC || Exynos W920 dual core 1.18 GHz; GPU: Mali-G68
|-
| Sensors ||
* Heart rate monitor
* Bioelectrical Impedance Analysis
* Accelerometer
* Gyroscope
* Barometer
|-
| Battery || Non-removable 247mAh / 361mAh
|}

=== Manually getting into Download or Recovery Mode ===
Press and hold both buttons until the "Rebooting..." screen appears. Release both buttons and press the power button (red outline) 3 times.

The reboot menu should be displayed. Press the power button to cycle between the options and confirm the selection with a long press (3 seconds).

GW4

2023-10-08T13:26:06Z

Jrt:

{{DISPLAYTITLE:Samsung Galaxy Watch 4}}

The Samsung Galaxy Watch 4 (LTE) is a round smartwatch that is one of the first ones to contain a bioelectrical impedance analysis (BIA) sensor.

{| class="wikitable"
|+ Samsung Galaxy Watch 4
|-
| Model number || SM-R860, SM-R870, SM-R880, SM-R890 (Wi-Fi only), SM-R865U, SM-R875U, SM-R885U, SM-R895U (USA, LTE model), SM-R895F (Int., LTE model)
|-
| Memory || 1.5 GB
|-
| Storage || 16 GB
|-
| SoC || Exynos W920 dual core 1.18 GHz; GPU: Mali-G68
|-
| Sensors ||
* Heart rate monitor
* Bioelectrical Impedance Analysis
* Accelerometer
* Gyroscope
* Barometer
|-
| Battery || Non-removable 247mAh / 361mAh
|}

GW4

2023-10-08T13:11:17Z

Jrt:

{{DISPLAYTITLE:Samsung Galaxy Watch 4}}

The Samsung Galaxy Watch 4 (LTE) is a round smartwatch that is one of the first ones to contain a bioelectrical impedance analysis (BIA) sensor.

{| class="wikitable"
|+ Samsung Galaxy Watch 4
|-
| Model number || SM-R860, SM-R870, SM-R880, SM-R890 (Wi-Fi only), SM-R865U, SM-R875U, SM-R885U, SM-R895U (USA, LTE model), SM-R895F (Int., LTE model)
|-
| Memory || 1.5 GB
|-
| Storage || 16 GB
|-
| SoC || Exynos W920 dual core 1.18 GHz; GPU: Mali-G68
|-
| Sensors || * Heart rate monitor
* Bioelectrical Impedance Analysis
* Accelerometer
* Gyroscope
* Barometer
|}

GW4

2023-10-08T13:10:55Z

Jrt:

{{DISPLAYTITLE:Samsung Galaxy Watch 4}}

The Samsung Galaxy Watch 4 (LTE) is a round smartwatch that is one of the first ones to contain a bioelectrical impedance analysis (BIA) sensor.

{| class="wikitable"
|+ Caption text
|-
| Model number || SM-R860, SM-R870, SM-R880, SM-R890 (Wi-Fi only), SM-R865U, SM-R875U, SM-R885U, SM-R895U (USA, LTE model), SM-R895F (Int., LTE model)
|-
| Memory || 1.5 GB
|-
| Storage || 16 GB
|-
| SoC || Exynos W920 dual core 1.18 GHz; GPU: Mali-G68
|-
| Sensors || * Heart rate monitor
* Bioelectrical Impedance Analysis
* Accelerometer
* Gyroscope
* Barometer
|}

GW4

2023-10-08T10:59:23Z

Jrt: Created page with "{{DISPLAYTITLE:Samsung Galaxy Watch 4}} The Samsung Galaxy Watch 4 (LTE) is a round smartwatch that is one of the first ones to contain a bioelectrical impedance analysis (BIA) sensor. {{Short description|Smartwatch developed by Samsung Electronics}} {{Infobox smartwatch | references = <ref name=":1"/><ref name=":2"/> | name = Samsung Galaxy Watch 4 | codename = | logo = | logosize = | image = | imagesize = | alt = | caption = | brand = Samsung Galaxy | manu..."

{{DISPLAYTITLE:Samsung Galaxy Watch 4}}

The Samsung Galaxy Watch 4 (LTE) is a round smartwatch that is one of the first ones to contain a bioelectrical impedance analysis (BIA) sensor.

{{Short description|Smartwatch developed by Samsung Electronics}}
{{Infobox smartwatch
| references = <ref name=":1"/><ref name=":2"/>
| name = Samsung Galaxy Watch 4
| codename =
| logo =
| logosize =
| image =
| imagesize =
| alt =
| caption =
| brand = [[Samsung Galaxy]]
| manufacturer = [[Samsung Electronics]]
| series = [[Samsung Galaxy Watch series]]
| modelnumber = SM-R860, SM-R870, SM-R880, SM-R890 (Wi-Fi only), SM-R865U, SM-R875U, SM-R885U, SM-R895U (USA, LTE model), SM-R895F (Int., LTE model)
| released = {{Start date and age|2021|8|27|df=no}}
| available =
| unitssold =
| predecessor = [[Samsung Galaxy Watch 3]]<br>[[Samsung Galaxy Watch Active 2]]
| successor = [[Samsung Galaxy Watch 5]]
| related =
| type = [[Smartwatch]]
| form =
| weight =
| memory = 1.5 GB [[Random Access Memory|RAM]]
| storage = 16 GB
| battery = *Non-removable 247mAh (1.2"), 361mAh (1.4")<br/>
*[[Qi (standard)|Qi wireless charging]]
| cpu = [[Exynos]] W920 [[Multi-core processor|dual core]] 1.18 G[[hertz|Hz]]; GPU: Mali-G68
| size =
| soc =
| os = [[Wear OS|Wear OS 4]] with [[One UI|One UI Watch 5]]
| rear_camera =
| front_camera =
| ext_display = [[Always On Display]]
| memory_card =
| display = *{{convert|1.2|in|mm|0|abbr=on}} [[AMOLED display|Super AMOLED]] [[capacitive display]], 396×396 pixels, 16 M colours, ~330 [[pixel density|ppi density]], 1:1 [[aspect ratio]]
*{{convert|1.4|in|mm|0|abbr=on}} [[AMOLED display|Super AMOLED]] [[capacitive display]], 450×450 pixels, 16 M colours, ~330 [[pixel density|ppi density]], 1:1 [[aspect ratio]]
*digital touch bezel or physical rotating bezel (classic)
* glass front ([[Gorilla Glass|Gorilla Glass DX+]]) (Galaxy Watch 4) ([[Gorilla Glass|Gorilla Glass DX+]]) (Galaxy Watch 4 Classic)
| connectivity =
| sound =
| input = *[[Heart rate monitor]]<br/>
*[[Bioelectrical Impedance Analysis]]
* [[Accelerometer]]
*[[Gyroscope]]
*[[Barometer]]
*Natural language commands & dictation
| networks = [[2G]], [[3G]], [[4G]]
| website = [https://www.samsung.com/us/watches/galaxy-watch4/ Official Website]
}}