https://wiki.asteroidos.org/api.php?action=feedcontributions&feedformat=atom&user=BerosetAsteroidOS - User contributions [en]2026-10-05T04:29:37ZUser contributionsMediaWiki 1.46.0https://wiki.asteroidos.org/index.php?title=Installing_the_SDK&diff=1045Installing the SDK2026-09-11T20:58:39Z<p>Beroset: changed qt5 references to qt6</p>
<hr />
<div>[[Category:Developers]]<br />
The Software Development Kit (SDK) for AsteroidOS is a set of tools and libraries for developing software to run on AsteroidOS. Since AsteroidOS is a Linux distribution, you can use just about any programming language to develop software, but most of the core applications use a combination of C++ and Qt, with CMake to build. This page describes how to install and configure the SDK.<br />
<br />
==== Which SDK? ====<br />
One thing to note is that while this describes "the SDK", there are actually two versions -- the main one is used to develop software that runs on ARM-based watches running AsteroidOS. The other one is the SDK for developing applications that run on the emulator, which uses qemux86. See the [[Emulator]] page for details on the qemux86 version. <br />
<br />
You can install both SDKs on the same machine -- they do not interfere.<br />
<br />
= Build or Download =<br />
You can either build the SDK from sources or download a prebuilt version. Using a prebuilt version is much faster and easier, and is recommended for developers who want to get started quickly. <br />
<br />
The prebuilt SDK is available [https://release.asteroidos.org/nightlies/sdk/oecore-meta-toolchain-qt6-x86_64-armv7vehf-neon-sturgeon-toolchain-nodistro.0.sh here]. If you wish to build it yourself, see [[Building the SDK]].<br />
<br />
== Installing the SDK ==<br />
If you downloaded a prebuilt SDK, run the downloaded script. If you built your own, the generated installation script should be in <code>tmp/deploy/sdk/</code> (relative to the <code>build</code> directory). In either case, navigate to the directory which contains the <code>oecore-meta-toolchain-qt6-x86_64-armv7vehf-neon-sturgeon-toolchain-nodistro.0.sh</code> script and run it:<br />
<br />
<pre><br />
./oecore-meta-toolchain-qt6-x86_64-armv7vehf-neon-sturgeon-toolchain-nodistro.0.sh<br />
</pre><br />
<br />
This script will install the cross-compiler and ARM libraries in <code>/usr/local/oecore-x86_64</code> by default, along with a script that needs to be sourced before every build. If you want to compile software for AsteroidOS on a watch, the command-line steps generally look like this:<br />
<br />
<pre><br />
source /usr/local/oecore-x86_64/environment-setup-armv7vehf-neon-oe-linux-gnueabi<br />
cmake -B build<br />
cmake --build build<br />
</pre><br />
<br />
=== Installing the emulator version of the SDK ===<br />
Installing the emulator version of the SDK is almost exactly the same. The only difference is that the file name for the installer is <code>oecore-meta-toolchain-qt6-x86_64-core2-32-qemux86-toolchain-nodistro.0.sh</code>.<br />
<br />
As noted above, you can install either or both versions on the same computer with no problem. They are completely independent.<br />
<br />
See [[Creating an Asteroid app]] for next steps.</div>Berosethttps://wiki.asteroidos.org/index.php?title=Build_from_the_command_line&diff=1044Build from the command line2026-09-11T20:57:30Z<p>Beroset: moved linguist description from Qt5 to Qt6</p>
<hr />
<div>This page describes how to build an app from the command line other than by using <code>bitbake</code>. As described in [[Creating an Asteroid app]], the preferred method for building an app is to set up and use <code>bitbake</code>. However, if you are a beginner and want to try a lower resource method for building, this page documents how to do so from the command line. The other relatively low resource method is to [[Build with QtCreator]].<br />
<br />
== Prerequisites ==<br />
To build an app from the command line using this method you should:<br />
# Have the [[Installing the SDK|SDK installed]]<br />
# Be familiar with CMake and C++<br />
<br />
It is technically possible, but not generally recommended to create new AsteroidOS applications in languages other than C++ and with build tools other than CMake.<br />
<br />
= Building from the command line =<br />
Generally, to build a CMake project from the command line, use this: <br />
<br />
<pre><br />
export CMAKE_PROGRAM_PATH=/usr/local/oecore-x86_64/sysroots/armv7vehf-neon-oe-linux-gnueabi/usr/bin/<br />
source /usr/local/oecore-x86_64/environment-setup-armv7vehf-neon-oe-linux-gnueabi<br />
cmake -B build<br />
cmake --build build<br />
</pre><br />
<br />
If you're building for the [[Emulator]], use this instead:<br />
<pre><br />
export CMAKE_PROGRAM_PATH=/usr/local/oecore-x86_64/sysroots/core2-32-oe-linux/usr/bin<br />
source /usr/local/oecore-x86_64/environment-setup-core2-32-oe-linux<br />
cmake -B build<br />
cmake --build build<br />
</pre><br />
<br />
== Example project ==<br />
A example project, asteroid-helloworld is available as both an example and a template for new software. To fetch it from <code>git</code> and build it, use the following:<br />
<br />
<pre><br />
git clone https://github.com/AsteroidOS/asteroid-helloworld.git<br />
cd asteroid-helloworld<br />
export CMAKE_PROGRAM_PATH=/usr/local/oecore-x86_64/sysroots/armv7vehf-neon-oe-linux-gnueabi/usr/bin/<br />
source /usr/local/oecore-x86_64/environment-setup-armv7vehf-neon-oe-linux-gnueabi<br />
cmake -B build -DCMAKE_INSTALL_PREFIX:PATH=/usr<br />
cmake --build build --target package<br />
</pre><br />
<br />
If everything was successful, you should now have a new library named <code>asteroid-helloworld.so</code> in the <code>build</code> directory. You should also have an <code>.ipk</code> file in the build directory. If the watch is connected via USB to the host computer, you can copy this to the watch and then install it with:<br />
<br />
<pre><br />
scp build/asteroid-helloworld*.ipk root@192.168.2.15:.<br />
ssh root@192.168.2.15 "opkg install asteroid-helloworld*.ipk"<br />
</pre><br />
<br />
Note that we specify the <code>CMAKE_INSTALL_PREFIX</code> in the commands above. This is to assure that the package is built to install the software in <code>/usr/lib/</code> rather than <code>/usr/local/lib/</code> which would otherwise be the default. The <code>--target package</code> instructs CMake to build a package the <code>.ipk</code> file in our case.<br />
<br />
Once the software is installed, it should show up as the last item on the launcher page. Pressing the icon should show an orange background with the words "Hello World!" in white. You should make sure all of this works before going further with development.<br />
<br />
You can start by modifying occurrences of "asteroid-helloworld" to your app's name. Then you can change the *.desktop file which describes the icon on the apps launcher. Then modify main.qml to describe your UI. To get started with QML development you can read the [http://doc.qt.io/qt-5/qml-tutorial.html official tutorial].<br />
<br />
==== Translations ====<br />
Within the AsteroidOS project, we use Qt Linguist and Weblate to enable [[Translating AsteroidOS]] and applications within it. If you're starting on "my-cool-project", you may want to add some language translations to it. This is done using the <code>lupdate</code> tool. Because Qt5 is nearing the end of support and Qt6 has been out for a while, the tool is named <code>lupdate-qt6</code> to differentiate between the two tools on most Linux distributions. Many will also allow <code>lupdate</code> as a synonym for the Qt6 version.<br />
<br />
'''Example''': Let's say that you want to start with English, French, Spanish, German and Italian translations. You will have to create them before they can be translated. To do this, within your top level <code>my-cool-project</code> directory, execute the following command line code:<br />
<br />
<pre><br />
for lang in en fr es de it<br />
do<br />
lupdate-qt6 -no-obsolete src/* i18n/*.h -ts i18n/my-cool-project.${lang}.ts<br />
done<br />
</pre><br />
<br />
This creates a <code>.ts</code> file for each of those language within the <code>i18n</code> directory. <br />
<br />
Once they are created, you or others who know the languages may use [https://doc.qt.io/qt-5/qtlinguist-index.html Qt Linguist] to actually translate the strings. Note that AsteroidOS uses the [https://doc.qt.io/qt-5/linguist-id-based-i18n.html id based] translation mechanism which uses <code>qsTrId</code> rather than <code>qsTr</code>.<br />
<br />
Qt and therefore AsteroidOS also supports national language variants, so if you want to create the Argentinian Spanish version or the Great Britain English version those would be named <code>es_AR</code> and <code>en_GB</code> respectively.<br />
<br />
==== Updating language translation files ====<br />
Once they are created, to update language translation files, and assuming you have all source files in <code>src</code> and translation files in <code>i18n</code> (which is short for "internationalization"), you can use this command to update the files.<br />
<br />
<pre><br />
lupdate-qt6 -no-obsolete src/* i18n/*.h -ts i18n/*.ts<br />
</pre><br />
=Tips and tricks=<br />
==Running your app==<br />
If you want to start your app from the command line, open a shell with [[SSH]], connect to ceres and use the shell script which, in turn, calls invoker:<br />
<br />
<code><br />
QT_QPA_PLATFORM=wayland asteroid-stopwatch<br />
</code><br />
<br />
Or more generally, call invoker directly:<br />
<code><br />
QT_QPA_PLATFORM=wayland invoker --single-instance --type=qtcomponents-qt6 /usr/lib/asteroid-stopwatch.so<br />
</code><br />
<br />
If you want to disable screen locking for easier development you can enable the demo mode of mce as root with:<br />
<br />
<code><br />
mcetool -D on<br />
</code><br />
<br />
Don't forget to turn it back off when you are done to avoid draining the battery.<br />
<br />
==Examining an .ipk file==<br />
On systems that have it, one can use <code>opkg-cl</code> or <code>ipkg-deb</code> to examine, extract or modify .ipk files. Without those, one can simply use <code>ar</code> and <code>tar</code>. <br />
Examples:<br />
<pre><br />
ar t path/to/package.ipk # show members<br />
ar x path/to/package.ipk control.tar.gz data.tar.gz<br />
tar --zstd -tf data.tar.zst # list files from package payload<br />
tar --zstd -xf data.tar.zst -C /tmp/pkg-extract # extract payload<br />
</pre><br />
<br />
We can also use one-liners to manipulate just the part of the .ipk file that contains data files (the package payload):<br />
<br />
<pre><br />
ar p path/to/package.ipk data.tar.zst | tar -tv --zstd # show data files<br />
ar p path/to/package.ipk data.tar.zst | tar -xv --zstd # extract data files<br />
</pre><br />
<br />
== Debugging ==<br />
Debugging is described in detail in [[Debugging Applications]]</div>Berosethttps://wiki.asteroidos.org/index.php?title=Building_the_SDK&diff=1043Building the SDK2026-09-11T20:54:32Z<p>Beroset: updated to use meta-toolchain-qt6</p>
<hr />
<div>[[Category:Developers]]<br />
<br />
==Summary==<br />
This page describes how to build the Software Development Kit (SDK) for AsteroidOS '''without''' using ''software containers''. If you want to build the SDK using containers, see [[Building the SDK in a container]] instead. <br />
<br />
If you're not sure which you want, skip to [[Building_the_SDK#With_or_without_software_containers?|With or without software containers?]] <br />
<br />
If you're not sure why you would want an SDK, continue reading. <br />
<br />
===What is an SDK?===<br />
<br />
The Software Development Kit (SDK) for AsteroidOS is a set of tools and libraries for developing software to run on AsteroidOS. Since AsteroidOS is a Linux distribution, you can use just about any programming language to develop software, but most of the core applications use a combination of C++ and Qt, with CMake to build. To get things running quickly, it's recommended to download and install the prebuilt version as described in [[Installing the SDK]]. This page describes how to build the SDK from source. Be aware that this can take several hours, even on a fast computer. <br />
<br />
==== Which SDK? ====<br />
One thing to note is that while this describes "the SDK", there are actually two versions -- the main one is used to develop software that runs on ARM-based watches running AsteroidOS. The other one is the SDK for developing applications that run on the emulator, which uses qemux86. See the [[Emulator]] page for details on the qemux86 version. This page describes only the main ARM-based SDK but building the emulator version is almost the same. The only difference is that instead of this: <br />
source ./prepare-build.sh sturgeon<br />
bitbake meta-toolchain-qt6<br />
you would do this instead:<br />
source ./prepare-build.sh qemux86<br />
bitbake meta-toolchain-qt6<br />
<br />
You can install both SDKs on the same machine -- they do not interfere.<br />
<br />
== With or without software containers? ==<br />
There are two choices to build the SDK: build natively without software containers or build within a software container (such as docker or podman).<br />
<br />
Building natively requires somewhat fewer resources (memory and disk space) than building with containers but requires software, such a compilers and other tools, to be installed on the host system. Since these software packages are different for each Linux distribution, this method requires more knowledge and patience to install required software that might not already be installed on your host computer.<br />
<br />
The alternative, building with software containers, is somewhat more simpler in that the required software is only installed within the container and not on your host computer, but it requires much more time to compile everything. Still, this may be preferable for people who wish to keep the build environment isolated from the host computer.<br />
<br />
== Building the Cross Compilation Toolchain ==<br />
<br />
If you’ve already got an OpenEmbedded build directory via the [[Building AsteroidOS]] page, <code>cd</code> to that directory. Else, create one with:<br />
<br />
<pre><br />
git clone https://github.com/AsteroidOS/asteroid<br />
cd asteroid/<br />
</pre><br />
<br />
Then, build the cross compilation toolchain with:<br />
<br />
<pre><br />
source ./prepare-build.sh dory<br />
bitbake meta-toolchain-qt6<br />
</pre><br />
<br />
<br />
==Install the SDK==<br />
Whether you have built with or without containers, if the process was successful, you should have an SDK installation script <code>tmp/deploy/sdk/oecore-meta-toolchain-qt6-x86_64-armv7vehf-neon-sturgeon-toolchain-nodistro.0.sh</code> (relative to the <code>build</code> directory) -- or a <code>oecore-meta-toolchain-qt6-x86_64-core2-32-qemux86-toolchain-nodistro.0.sh</code> script if you are building the version of the SDK for the emulator. Follow [[installing the SDK#Installing the SDK|these steps]] to install the SDK.<br />
<br />
==Related pages==<br />
<br />
[[Building the SDK in a container]] <br />
<br />
[[installing the SDK]]<br />
<br />
[[Building AsteroidOS]]<br />
<br />
[[Creating an Asteroid app]]</div>Berosethttps://wiki.asteroidos.org/index.php?title=Building_the_SDK_in_a_container&diff=1042Building the SDK in a container2026-09-11T20:53:20Z<p>Beroset: /* Which SDK? */ updated to use meta-toolchain-qt6</p>
<hr />
<div>[[Category:Developers]]<br />
<br />
==Summary==<br />
This page describes how to build the Software Development Kit (SDK) for AsteroidOS using ''software containers''. If you want to build the SDK without using containers, see [[Building the SDK]] instead. <br />
<br />
If you're not sure which you want, skip to [[Building_the_SDK#With_or_without_software_containers?|With or without software containers?]]<br />
<br />
If you're not sure why you would want an SDK, continue reading. <br />
<br />
===What is an SDK?===<br />
<br />
The Software Development Kit (SDK) for AsteroidOS is a set of tools and libraries for developing software to run on AsteroidOS. Since AsteroidOS is a Linux distribution, you can use just about any programming language to develop software, but most of the core applications use a combination of C++ and Qt, with CMake to build. To get things running quickly, it's recommended to download and install the prebuilt version as described in [[Installing the SDK]]. This page describes how to build the SDK from source. Be aware that this can take several hours, even on a fast computer. <br />
<br />
====Which SDK?====<br />
One thing to note is that while this describes "the SDK", there are actually two versions -- the main one is used to develop software that runs on ARM-based watches running AsteroidOS. The other one is the SDK for developing applications that run on the emulator, which uses qemux86. See the [[Emulator]] page for details on the qemux86 version. This page describes only the main ARM-based SDK but building the emulator version is almost the same. The only difference is that instead of this: <br />
source ./prepare-build.sh dory<br />
bitbake meta-toolchain-qt6<br />
you would do this instead:<br />
source ./prepare-build.sh qemux86<br />
bitbake meta-toolchain-qt6<br />
<br />
You can install both SDKs on the same machine -- they do not interfere.<br />
<br />
==With or without software containers?==<br />
There are two choices to build the SDK: build natively without software containers or build within a software container (such as docker or podman). <br />
<br />
Building natively requires somewhat fewer resources (memory and disk space) than building with containers but requires software, such a compilers and other tools, to be installed on the host system. Since these software packages are different for each Linux distribution, this method requires more knowledge and patience to install required software that might not already be installed on your host computer.<br />
<br />
The alternative, building with software containers, is somewhat more simpler in that the required software is only installed within the container and not on your host computer, but it requires much more time to compile everything. Still, this may be preferable for people who wish to keep the build environment isolated from the host computer.<br />
<br />
The rest of this page describes how to build '''with''' containers. If you have decided to build natively instead, go to [[Building the SDK]] <br />
<br />
===Build with containers===<br />
<br />
Assuming you already prepared a docker or podman build environment as described in [[Building AsteroidOS]], build the SDK like so:<br />
<br />
<pre><br />
sudo docker rm -f asteroidos-toolchain<br />
sudo docker run -it \<br />
--name asteroidos-toolchain \<br />
-v /etc/passwd:/etc/passwd:ro \<br />
-u "$(id -u):$(id -g)" \<br />
-v "$HOME/.gitconfig:/$HOME/.gitconfig:ro" \<br />
-v "$(pwd):/asteroid" asteroidos-toolchain \<br />
bash -c "source ./prepare-build.sh dory && bitbake meta-toolchain-qt6"<br />
</pre><br />
<br />
or<br />
<br />
<pre><br />
podman run --rm -it \<br />
-v "$(pwd)":/asteroid:z \<br />
--userns keep-id asteroidos-toolchain \<br />
bash -c "source ./prepare-build.sh dory && bitbake meta-toolchain-qt6"<br />
</pre><br />
<br />
==Install the SDK==<br />
Whether you have built with or without containers, if the process was successful, you should have an SDK installation script <code>tmp/deploy/sdk/oecore-x86_64-armv7vehf-neon-toolchain-nodistro.0.sh</code> (relative to the <code>build</code> directory) -- or a <code>oecore-x86_64-core2-32-toolchain-nodistro.0.sh</code> script if you are building the version of the SDK for the emulator. Follow [[installing the SDK#Installing the SDK|these steps]] to install the SDK.<br />
<br />
==Related pages==<br />
<br />
[[Building the SDK]]<br />
<br />
[[installing the SDK]]<br />
<br />
[[Building AsteroidOS]]<br />
<br />
[[Creating an Asteroid app]]<br />
<br />
[[OpenEmbedded]]</div>Berosethttps://wiki.asteroidos.org/index.php?title=Building_the_SDK_in_a_container&diff=1041Building the SDK in a container2026-09-11T20:52:39Z<p>Beroset: /* Which SDK? */ updated to use meta-toolchain-qt6</p>
<hr />
<div>[[Category:Developers]]<br />
<br />
==Summary==<br />
This page describes how to build the Software Development Kit (SDK) for AsteroidOS using ''software containers''. If you want to build the SDK without using containers, see [[Building the SDK]] instead. <br />
<br />
If you're not sure which you want, skip to [[Building_the_SDK#With_or_without_software_containers?|With or without software containers?]]<br />
<br />
If you're not sure why you would want an SDK, continue reading. <br />
<br />
===What is an SDK?===<br />
<br />
The Software Development Kit (SDK) for AsteroidOS is a set of tools and libraries for developing software to run on AsteroidOS. Since AsteroidOS is a Linux distribution, you can use just about any programming language to develop software, but most of the core applications use a combination of C++ and Qt, with CMake to build. To get things running quickly, it's recommended to download and install the prebuilt version as described in [[Installing the SDK]]. This page describes how to build the SDK from source. Be aware that this can take several hours, even on a fast computer. <br />
<br />
====Which SDK?====<br />
One thing to note is that while this describes "the SDK", there are actually two versions -- the main one is used to develop software that runs on ARM-based watches running AsteroidOS. The other one is the SDK for developing applications that run on the emulator, which uses qemux86. See the [[Emulator]] page for details on the qemux86 version. This page describes only the main ARM-based SDK but building the emulator version is almost the same. The only difference is that instead of this: <br />
source ./prepare-build.sh dory<br />
bitbake meta-toolchain-qt6<br />
you would do this instead:<br />
source ./prepare-build.sh qemux86<br />
bitbake meta-toolchain-qt6<br />
<br />
You can install both SDKs on the same machine -- they do not interfere.<br />
<br />
==With or without software containers?==<br />
There are two choices to build the SDK: build natively without software containers or build within a software container (such as docker or podman). <br />
<br />
Building natively requires somewhat fewer resources (memory and disk space) than building with containers but requires software, such a compilers and other tools, to be installed on the host system. Since these software packages are different for each Linux distribution, this method requires more knowledge and patience to install required software that might not already be installed on your host computer.<br />
<br />
The alternative, building with software containers, is somewhat more simpler in that the required software is only installed within the container and not on your host computer, but it requires much more time to compile everything. Still, this may be preferable for people who wish to keep the build environment isolated from the host computer.<br />
<br />
The rest of this page describes how to build '''with''' containers. If you have decided to build natively instead, go to [[Building the SDK]] <br />
<br />
===Build with containers===<br />
<br />
Assuming you already prepared a docker or podman build environment as described in [[Building AsteroidOS]], build the SDK like so:<br />
<br />
<pre><br />
sudo docker rm -f asteroidos-toolchain<br />
sudo docker run -it \<br />
--name asteroidos-toolchain \<br />
-v /etc/passwd:/etc/passwd:ro \<br />
-u "$(id -u):$(id -g)" \<br />
-v "$HOME/.gitconfig:/$HOME/.gitconfig:ro" \<br />
-v "$(pwd):/asteroid" asteroidos-toolchain \<br />
bash -c "source ./prepare-build.sh dory && bitbake meta-toolchain-qt5"<br />
</pre><br />
<br />
or<br />
<br />
<pre><br />
podman run --rm -it \<br />
-v "$(pwd)":/asteroid:z \<br />
--userns keep-id asteroidos-toolchain \<br />
bash -c "source ./prepare-build.sh dory && bitbake meta-toolchain-qt5"<br />
</pre><br />
<br />
==Install the SDK==<br />
Whether you have built with or without containers, if the process was successful, you should have an SDK installation script <code>tmp/deploy/sdk/oecore-x86_64-armv7vehf-neon-toolchain-nodistro.0.sh</code> (relative to the <code>build</code> directory) -- or a <code>oecore-x86_64-core2-32-toolchain-nodistro.0.sh</code> script if you are building the version of the SDK for the emulator. Follow [[installing the SDK#Installing the SDK|these steps]] to install the SDK.<br />
<br />
==Related pages==<br />
<br />
[[Building the SDK]]<br />
<br />
[[installing the SDK]]<br />
<br />
[[Building AsteroidOS]]<br />
<br />
[[Creating an Asteroid app]]<br />
<br />
[[OpenEmbedded]]</div>Berosethttps://wiki.asteroidos.org/index.php?title=IP_Connection&diff=1040IP Connection2026-09-07T20:56:42Z<p>Beroset: /* AsteroidOS versions 2.2 and later */ added secure root access section</p>
<hr />
<div>Configuring an IP connection on your watch has to be done manually until a GUI settings option is available. On watches that support WLAN, you can enable Wi-Fi and configure the connection using <code>connmanctl</code> like described below. Forwarding IP requests to a connected PC via USB is another option, explained in the second paragraph.<br />
<br />
<br />
== AsteroidOS versions before 2.2 ==<br />
By default, there is no <code>root</code> or <code>ceres</code> password, and no firewall rules. (However, on some watches, the kernel has the <code>CONFIG_ANDROID_PARANOID_NETWORK</code> kernel option enabled, see below.) A password can be set using the passwd command.<br />
<br />
== AsteroidOS versions 2.2 and later ==<br />
There is no <code>ceres</code> password, and no firewall rules. There is an invalid <code>root</code> password set, disallowing any password login. Root login is also disabled in <code>sshd_config</code>. However the <code>sudo</code> command is now included by default, so the <code>ceres</code> user can use that for temporary privilege escalation when needed.<br />
<br />
===Secure root access===<br />
If you need root access over ssh, the most secure way to accomplish that is to put your computer's public key on the watch. The process for doing that is described [[OpenEmbedded#A_word_about_root_access|here]].<br />
<br />
===Legacy root access===<br />
If it's needed, root empty password can be re-enabled by running:<br />
<code>sudo passwd -d root</code><br />
<br />
Also, ssh password login for <code>root</code> can be enabled with:<br />
<pre><br />
sudo sed -i 's/^[#[:space:]]PermitRootLogin./PermitRootLogin yes/' /etc/ssh/sshd_config<br />
</pre><br />
<br />
By default, password and keyboard-interactive authentication is disabled for <code>root</code>.<br />
<br />
= IP over WLAN (WiFi) =<br />
Connect to your watch using <code>ssh root@192.168.2.15</code> or <code>adb shell</code>.<br />
<br />
<pre>connmanctl</pre><br />
Starts the connmanctl interactive mode. The prompt indicator will change to <code>connmanctl></code><br />
<pre>enable wifi</pre><br />
Output: Enabled wifi<br />
<pre>scan wifi</pre><br />
Output: Scan completed for wifi<br />
<pre>agent on</pre><br />
Output: Agent registered<br />
<br />
The Agent will handle automatic reconnect to the network.<br />
<pre>services</pre><br />
Shows the discovered SSIDs and their service identifier.<br />
<br />
Output example:<br />
<br />
<code>YourNetwork wifi_1234567890_1234567890_managed_psk</code><br />
<br />
<code>OtherLAN wifi_0987654321_123456789_managed_psk</code><br />
<pre>connect <ServiceIdentifierOfYourSSID></pre> <br />
Example:<br />
<br />
<code>connect wifi_1234567890_1234567890_managed_psk</code><br />
<br />
Prompt changes to <code>Passphrase?</code> and asks for the password to the SSID.<br />
<br />
<code>TypeYourPassPhraseAndPressEnter</code><br />
<br />
Output: Connected to wifi_1234567890_1234567890_managed_psk<br />
<br />
Note: If the connection fails with an error (e.g., "Invalid key" or no connection), try connecting to the other service identifier listed for the same SSID name, as it may correspond to the 2.4 GHz band that your watch supports more reliably (while the other is likely 5 GHz).<br />
<pre>quit</pre><br />
Leaves the connmanctl interactive mode.<br />
<br />
Check whether an IP address has been assigned to the watch using <code>ip a show dev wlan0</code> or <code>ifconfig wlan0</code> or by trying to <code>ping 8.8.8.8</code>.<br />
<br />
Note that activated WLAN consumes additional power. Currently, it is recommended to disable the function after use. <code>connmanctl disable wifi</code> is used to disable Wi-Fi and power off WLAN temporarily. <code>connmanctl enable wifi</code> activates WLAN again and connects to the last used Wi-Fi network.<br />
<br />
Some more documentation on connman can be found on [https://wiki.archlinux.org/index.php/ConnMan#Connecting_to_a_protected_access_point ArchWiki].<br />
<br />
<br />
=IP over USB=<br />
It is possible to allow your watch to be able to use your Linux computer's internet connection via a USB connection. You will need: <br />
<br />
#A Linux computer with RNDIS support loaded and enabled<br />
#The ability to change network configurations on that computer<br />
#A network connection<br />
<br />
This works by using the RNDIS driver to allow the USB device to appear to be a network interface. RNDIS stands for "Remote Network Driver Interface Specification" and was a proprietary protocol from Microsoft. It is supported in Linux by the <code>rndis_host</code> driver. This driver may either be compiled into the kernel, or more typically provided as an optional module. If you're not sure, you can try this <code>lsmod</code> to see if it's loaded on your computer.<br />
<br />
<pre><br />
lsmod | grep ndis<br />
rndis_host 24576 0<br />
cdc_ether 24576 1 rndis_host<br />
usbnet 61440 2 rndis_host,cdc_ether<br />
</pre><br />
<br />
If it isn't you might be able to use <code>modprobe rndis_host</code> (with root privileges) to install the module.<br />
<br />
Once the <code>rndis_host</code> is installed and running, you can enable Network Address Translation (NAT) to allow your Linux computer to share it's internet IP address with the watch. To configure a NAT '''on your computer''' (Note: Replace eth0 with the name of the interface that connects your computer to the Internet) with:<br />
<br />
<pre>echo 1 > /proc/sys/net/ipv4/ip_forward</pre><br />
<pre>iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE</pre><br />
<br />
Here again, you might need root privileges for those commands, depending on how your computer is configured.<br />
<br />
Configure a default gateway and DNS '''on the watch''' with the following commands ran via [[SSH]] as the root user:<br />
<br />
<pre>ip route add default via 192.168.2.1</pre><br />
<pre>echo "nameserver 8.8.8.8" >> /etc/resolv.conf</pre><br />
<br />
Note that this assumes that your computer's IP address on RNDIS is 192.168.2.1, which is the default, but if you have multiple watches, or have plugged and unplugged the same watch a few times, it might be different. To make sure, on the watch, you can type <code>who</code> and it will reply with something like this:<br />
<br />
<code><br />
root pts/0 00:01 Jun 9 08:06:24 192.168.2.2<br />
</code><br />
<br />
In this particular case, the address shown is 192.168.2.2, so the first command listed above would be <code>route add default gw 192.168.2.2</code>.<br />
<br />
== Custom Address ==<br />
The watch defaults to the address 192.168.2.15, but this can be changed. If, for example, you want to change the address to 10.0.0.2, the recommended way to change it is to do this:<br />
<br />
# temporarily changing the USB mode on the watch to "ADB mode"<br />
# issue the command <pre>adb dbus-send --system --type=method_call --print-reply --dest=com.meego.usb_moded /com/meego/usb_moded com.meego.usb_moded.net_config string:'ip' string:'10.0.0.2'</pre><br />
# change USB mode to "SSH mode"<br />
<br />
Note that if you have more than one ADB device attached to your computer, you might have to give it the transport ID in step 2. This change persists across boots.<br />
<br />
An alternative approach for developers building their own image using bitbake, is to edit the file https://github.com/AsteroidOS/meta-asteroid/blob/master/recipes-nemomobile/usb-moded/usb-moded/usb-moded/usb-moded.ini. And add:<br />
<br />
<pre><br />
[network]<br />
ip=10.0.0.2<br />
</pre><br />
<br />
= Paranoid Kernels=<br />
On some watch models (e.g., <code>lenok</code>), the kernel shipped with AsteroidOS is compiled with the Android-specific <code>CONFIG_ANDROID_PARANOID_NETWORK</code> kernel option enabled. That option enforces non-standard restrictions on networking, based on hardcoded group IDs (GIDs):<br />
*GID 3003 is the <code>inet</code> group, allowing to create <code>AF_INET</code> and <code>AF_INET6</code> sockets,<br />
* GID 3004 is the <code>net_raw</code> group, allowing to create raw INET sockets.<br />
<br />
Only <code>root</code> and members of the groups with those magic GIDs are allowed to perform the described actions. In particular, by default, the <code>ceres</code> user is '''not'''.<br />
<br />
Therefore, in order to be able to access the network as <code>ceres</code> (e.g., for <code>asteroid-weatherfetch</code> to work), SSH into your watch as <code>root</code> (or use <code>adb shell</code>) and run the following 2 commands:<br />
<pre><br />
groupadd -g 3003 -U root,ceres inet<br />
groupadd -g 3004 -U root,ceres net_raw<br />
</pre><br />
These create the two magic groups with the same name and GID as on Android and add both <code>root</code> and <code>ceres</code> to them. Then reboot your watch, because only newly started sessions will pick up the new group memberships.</div>Berosethttps://wiki.asteroidos.org/index.php?title=Catfish_hardware&diff=1039Catfish hardware2026-09-05T20:01:20Z<p>Beroset: fixed chip number for NFC controller</p>
<hr />
<div>The [[Catfish|catfish]] hardware is based on the Qualcomm MSM8909w chipset. In the picture of the front of the main board with the shield removed, this part is just above the horizontal center line of the board and slightly to the left of the vertical center line. The large part under the bit of rubber or glue is a Kingston 04EPOP04-NL3DM627, which is a combo memory of 4GB MLC + 4Gb LPDDR3 in a 136-Ball BGA package.<br />
<br />
'''NOTE:''' The unit GB is giga''bytes'' while the unit Gb is giga''bits''. This terminology comes directly from the manufacturer (see: [https://web.archive.org/web/20211205022748/https://www.kingston.com/unitedkingdom/en/embedded/epop-embedded-flash an archived web page])[[File:Front of catfish main board with shield removed.jpg|thumb|alt=Front of catfish main board with shield removed|Front of catfish main board with shield removed]]<br />
[[File:Back of catfish main board with shield removed.jpg|thumb|alt=Back of catfish main board|Back of catfish main board]]<br />
[[File:F412REY6 chip.jpg|alt=Unknown chip #1 on front of catfish main board|thumb|STM32F412REY (package WLCSP) on front of catfish main board]]<br />
<br />
=== Hardware details - front ===<br />
Outside the shield at the top left of the board is a STM32F412REY (package WLCSP). Markings on that chip are:<br />
<pre><br />
F412REY6<br />
A5 008 VQ<br />
TW 8 16 C<br />
</pre><br />
A picture of this chip is shown below. Voltage detector XC6114 from Torex, providing 2.1V detection, is a much smaller chip to the right side of the board. Markings on that chip are:<br />
<pre><br />
848<br />
2605<br />
A7NZ<br />
</pre><br />
[[File:Unknown chip -2 on front of catfish main board.jpg|alt=Unknown chip #2 on front of catfish main board|thumb|Voltage detector XC6114 from Torex. 2.1V detection.]]<br />
<br />
=== Hardware details - back ===<br />
[[File:Unknown chips 3 and 4 on back of catfish.jpg|alt=Unknown chips 3 and 4 on back of catfish|thumb|Unknown chips 3 and 4 on back of catfish]]<br />
At the top of the board below the two connectors are two chips, shown in a picture below as "unknown chips 3 and 4 on back of catfish." Chip 3 is probably a Class‑K speaker amplifier (from Awinic AW87318CSR). The markings on the chip to the left say:<br />
<pre><br />
2310208<br />
VGM41_1<br />
B8214<br />
</pre><br />
The markings on the on the right say:<br />
<pre><br />
K318<br />
AFC3<br />
</pre><br />
Toward the bottom of the board are three additional chips. To the left of the battery connector is a chip labeled:<br />
<pre><br />
SF<br />
739<br />
</pre><br />
<br />
With a barcode between "SF" and "739". A closeup photo is shown below as unknown chip #5. This SF739 chip may be the secure element paired to the NFC chip (perhaps a ST33J2M0 family as they are designed to work together).<br />
[[File:SF739 chip.jpg|alt=Unknown chip #5 labeled SF739|thumb|Unknown chip #5 labeled SF739. May be the secure element paired to the NFC chip (perhaps a ST33J2M0 family as they are designed to work together).]]<br />
[[File:75CK371.jpg|alt=Unknown chip #6 labeled 75CK371|thumb|Chip labeled 75CK871, a single-cell Li-ion gauge from Texas Instruments BQ27421YZFR-G1D.]]<br />
The chip labeled 75CK871 is a single-cell Li-ion gauge from Texas Instruments BQ27421YZFR-G1D and is to the right of the battery connector and bears these markings:<br />
<pre><br />
75CK371<br />
BQ27431<br />
G1D<br />
</pre><br />
In the photo below, it's the smaller chip to the left.<br />
[[File:ST71NFCD.jpg|alt=ST21NFCD Near Field Communications (NFC) controller|thumb|ST21NFCD Near Field Communications (NFC) controller]]<br />
The chip to the right of at the bottom, the largest chip on the back of the board, is a ST21NFCD which is a Near field communication (NFC) controller which includes its own ARM Cortex-M3 microcontroller. A closeup photo of that chip is also shown below.</div>Berosethttps://wiki.asteroidos.org/index.php?title=Bluetooth&diff=1038Bluetooth2026-09-04T12:43:20Z<p>Beroset: clarified and updated</p>
<hr />
<div>[[Category:Developers]]<br />
An app named [https://github.com/AsteroidOS/AsteroidOSSync AsteroidOSSync] can be downloaded on Android to synchronize data from a phone to an AsteroidOS watch. Other platforms have [[Synchronization Clients|other synchronization clients]]. Several [[BLE profiles|profiles]] are already supported: Notifications, Weather, Music and Battery, more could come in the future.<br />
<br />
=Technical details=<br />
== AsteroidOSSync ==<br />
On the phone, AsteroidOSSync uses the [https://github.com/AsteroidOS/AsteroidOSSync/tree/master/app/src/main/lib/sweetblue SweetBlue] library to access the Bluetooth Low Energy capabilities of Bluedroid as a central device. It scans for watches and implements the client part of the aforementioned profiles.<br />
== AsteroidOS Bluetooth implementation ==<br />
On the watch, data are usually received by a BCM20715 BT chip from Broadcom, this chip needs a proprietary firmware which is uploaded by the [https://github.com/AsteroidOS/meta-dory-hybris/blob/master/recipes-android/brcm-patchram-plus/brcm-patchram-plus/patchram.service patchram] systemd service. Once the firmware is uploaded an hci0 interface is created and can be set up with hciconfig.<br />
The Linux Kernel can then receive BLE payloads. A newer Bluetooth subsystem (4.1) has been [https://github.com/AsteroidOS/meta-smartwatch/blob/865d65514ee4e852bf2ed53add71ca3d18692608/meta-dory/recipes-kernel/linux/linux-dory/0003-Backport-mainline-4.1-Bluetooth-subsystem.patch backported] to provide newer MGMT API functionalities needed by the userspace (e.g: DBus advertisement). This MGMT API is only used by the BlueZ5’s bluetoothd daemon which exposes various DBus abstraction API. Bluetoothd also had to be [https://github.com/AsteroidOS/meta-asteroid/blob/master/recipes-connectivity/bluez5/bluez5/advertise-name.patch patched] to expose more complete advertisement payloads.<br />
Simple and common interactions with the bluetoothd’s DBus API like checking for the powered/connected status are implemented in [https://github.com/AsteroidOS/qml-asteroid/blob/master/src/utils/src/bluetoothstatus.cpp org.asteroid.utils.BluetoothStatus] of qml-asteroid. This class is for example used in asteroid-launcher, asteroid-music and [https://github.com/AsteroidOS/asteroid-settings/blob/master/BluetoothPage.qml asteroid-settings].<br />
More complex interactions with bluetoothd are implemented in [https://github.com/AsteroidOS/asteroid-btsyncd asteroid-btsyncd], a user-space daemon running as a standard user (ceres) and acting as a DBus multiplexer between BlueZ and the apps. On the BlueZ side it registers BLE Services, Characteristics and Advertisement payloads. On the user side, it exposes specific API for each and every usage needed. For example, it communicates with asteroid-music with to the [https://github.com/AsteroidOS/asteroid-music/blob/master/main.qml#L98 MPRIS API], with asteroid-launcher based on the FreeDesktop’s notification API or with asteroid-weather thanks to data saved in the dconf “register”.<br />
<br />
=Bluetooth Personal Area Network=<br />
In order to use BT PAN on AsteroidOS, you first need to modify the default image. Start by adding the following packages to the <i>IMAGE_INSTALL</i> variable of <code>asteroid/src/meta-asteroid/classes/asteroid-image.bbclass</code>:<br />
<pre>bluez5-testtools bluez5-noinst-tools python-dbus connman-client</pre><br />
You also need to modify the bluez5’s main configuration in <code>asteroid/src/meta-asteroid/recipes-connectivity/bluez5/bluez5/main.conf</code> to<br />
<pre>[General]<br />
#ControllerMode = le<br />
DiscoverableTimeout = 180</pre><br />
Finally, modify <code>build/conf/bblayers.conf</code> to add the following line to <code>BBLAYERS</code>:<br />
<pre>/path/to/src/meta-openembedded/meta-networking \</pre><br />
After above changes, you can rebuild a new asteroid rootfs and install it to the watch as described in [[Building AsteroidOS]].<br />
In order to watch logs and check on progress, open up first a first terminal on the watch via [[SSH]] and run:<br />
<pre>tail -F /var/log/messages</pre><br />
In a new terminal, download and push the bt-pan helper script: ([http://blog.fraggod.net/2015/03/28/bluetooth-pan-network-setup-with-bluez-5x.html more info])<br />
<pre>wget https://raw.githubusercontent.com/mk-fg/fgtk/master/bt-pan<br />
chmod +x ./bt-pan<br />
scp bt-pan ceres@192.168.2.15:/tmp/bluetooth/bt-pan</pre><br />
Now, fix up DNS and make sure localhost is a known thing by modifying (if needed) <code>resolv.conf</code> and hosts<br />
<pre>sh-4.3# cat /etc/resolv.conf<br />
nameserver 8.8.8.8<br />
nameserver ::1<br />
sh-4.3# cat /etc/hosts<br />
127.0.0.1 localhost</pre><br />
Make sure you can see bluetooth in connman:<br />
<pre>sh-4.3# connmanctl technologies<br />
...<br />
/net/connman/technology/bluetooth<br />
Name = Bluetooth<br />
Type = bluetooth<br />
Powered = True<br />
Connected = False<br />
Tethering = False</pre><br />
You can now use bluetoothctl to establish a connection to your computer ([http://trac.gateworks.com/wiki/wireless/bluetooth#PersonalAreaNetworkDeviceProfilePAN more info])<br />
<pre>sh-4.3# bluetoothctl<br />
[NEW] Controller 20:70:02:A0:1F:AC dory [default]<br />
[NEW] Device 3C:15:C2:C7:DA:95 my-rmbp2<br />
agent on<br />
default-agent<br />
discoverable on<br />
pairable on<br />
scan on<br />
pair 3C:15:C2:C7:DA:95<br />
trust 3C:15:C2:C7:DA:95</pre><br />
Launch bt-pan client which triggers bnep0 creation from connman (you will see it in <code>/var/log/messages</code>)<br />
<pre>sh-4.3# /tmp/bluetooth/bt-pan --debug client 3C:15:C2:C7:DA:95<br />
DEBUG:root:Using local device (addr: 20:70:02:A0:1F:AC): /org/bluez/hci0<br />
DEBUG:root:Using remote device (addr: 3C:15:C2:C7:DA:95): /org/bluez/hci0/dev_3C_15_C2_C7_DA_95<br />
DEBUG:root:Connected to network (dev_remote: /org/bluez/hci0/dev_3C_15_C2_C7_DA_95, addr: 3C:15:C2:C7:DA:95) uuid 'nap' with iface: bnep0<br />
DEBUG:root:Finished</pre><br />
At this point your default route should still be rndis0 (USB OTG) instead of bnep0:<br />
<pre>sh-4.3# ip route<br />
default via 192.168.2.1 dev rndis0<br />
192.168.2.0/24 dev rndis0 proto kernel scope link src 192.168.2.15</pre><br />
If the ip/bcast/netmask fields are missing on bnep0:<br />
<pre>sh-4.3# ifconfig bnep0<br />
bnep0 Link encap:Ethernet HWaddr 20:70:02:A0:1F:AC<br />
inet6 addr: fe80::2270:2ff:fea0:1fac%1202001524/64 Scope:Link<br />
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br />
RX packets:39 errors:0 dropped:0 overruns:0 frame:0<br />
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0<br />
collisions:0 txqueuelen:1000<br />
RX bytes:10504 (10.2 KiB) TX bytes:148 (148.0 B)</pre><br />
Fix it with ifconfig and verify it worked:<br />
<pre>sh-4.3# ifconfig bnep0 192.168.2.2 netmask 255.255.255.0 broadcast 192.168.2.255<br />
sh-4.3# ifconfig bnep0<br />
bnep0 Link encap:Ethernet HWaddr 20:70:02:A0:1F:AC<br />
inet addr:192.168.2.2 Bcast:192.168.2.255 Mask:255.255.255.0<br />
inet6 addr: fe80::2270:2ff:fea0:1fac%1201331708/64 Scope:Link<br />
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br />
RX packets:134 errors:0 dropped:0 overruns:0 frame:0<br />
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0<br />
collisions:0 txqueuelen:1000<br />
RX bytes:40369 (39.4 KiB) TX bytes:252 (252.0 B)</pre><br />
Now that both routes are available, data are still going over rndis0 instead of bnep0:<br />
<pre>sh-4.3# ip route<br />
default via 192.168.2.1 dev rndis0<br />
192.168.2.0/24 dev rndis0 proto kernel scope link src 192.168.2.15<br />
192.168.2.0/24 dev bnep0 proto kernel scope link src 192.168.2.2</pre><br />
Delete default route and aad a new default one over bnep0<br />
<pre>sh-4.3# ip route delete default<br />
sh-4.3# ip route change default via 192.168.2.1 dev bnep0</pre><br />
Verify default is now over bnep0:<br />
<pre>sh-4.3# ip route<br />
default via 192.168.2.1 dev bnep0<br />
192.168.2.0/24 dev rndis0 proto kernel scope link src 192.168.2.15<br />
192.168.2.0/24 dev bnep0 proto kernel scope link src 192.168.2.2</pre><br />
You can now test your connection via ping and nslookup<br />
<pre>sh-4.3# ping -c 1 8.8.8.8<br />
PING 8.8.8.8 (8.8.8.8): 56 data bytes<br />
64 bytes from 8.8.8.8: seq=0 ttl=42 time=80.094 ms<br />
sh-4.3# nslookup www.google.com<br />
Server: 8.8.8.8<br />
Address 1: 8.8.8.8 google-public-dns-a.google.com</pre><br />
<br />
=Bluetooth Audio and HID=<br />
You will need to enable legacy mode in order to connect to legacy (BR/EDR) mode Bluetooth devices. To enable legacy mode you will need to edit the configuration file '''on the watch''' via [[SSH]] use the following command:<br />
<pre>sh-4.4# vi /etc/bluetooth/main.conf<br />
</pre><br />
Now edit the contents to the following:<br />
<pre>[General]<br />
#ControllerMode = le<br />
DiscoverableTimeout = 180</pre><br />
Next you will need to restart Bluetooth. To avoid weird behaviour its best to restart the entire system, use the following command:<br />
<pre>sh-4.4# reboot<br />
</pre><br />
Now you are ready to connect a Bluetooth device to AsteroidOS use bluetoothctl to connect to a Bluetooth device:<br />
<pre>sh-4.4# bluetoothctl<br />
Agent registered<br />
[bluetooth]# agent on<br />
Agent is already registered<br />
[bluetooth]# default-agent<br />
[bluetooth]# discoverable on<br />
[bluetooth]# pairable on<br />
[bluetooth]# scan on<br />
Default agent request successful<br />
Changing pairable on succeeded<br />
Changing discoverable on succeeded<br />
[CHG] Controller 43:43:A0:12:1F:AC Discoverable: yes<br />
Discovery started<br />
[CHG] Controller 43:43:A0:12:1F:AC Discovering: yes<br />
[NEW] Device 27:EC:10:01:00:1A Gamepad.<br />
[bluetooth]# pair 27:EC:10:01:00:1A<br />
Attempting to pair with 27:EC:10:01:00:1A<br />
[CHG] Device 27:EC:10:01:00:1A Paired: yes<br />
Pairing successful<br />
[Gamepad.]# connect 27:EC:10:01:00:1A<br />
Attempting to connect to 27:EC:10:01:00:1A<br />
Connection successful<br />
[Gamepad.]#<br />
</pre><br />
<br />
=== A2DP audio playback ===<br />
<br />
Tested on the Huawei Watch 2 (`sawfish`) with a Bose NC 700 headset.<br />
<br />
AsteroidOS configures BlueZ for BLE-only operation by default. To use ordinary<br />
Bluetooth audio headsets, enable both BLE and BR/EDR:<br />
<br />
<syntaxhighlight lang="sh"><br />
sudo cp -a /etc/bluetooth/main.conf /etc/bluetooth/main.conf.before-a2dp<br />
sudo sed -i \<br />
's/^[[:space:]]*ControllerMode[[:space:]]*=[[:space:]]*.*/ControllerMode = dual/' \<br />
/etc/bluetooth/main.conf<br />
sudo systemctl restart bluetooth.service<br />
</syntaxhighlight><br />
<br />
Pair, trust and connect the headset using `bluetoothctl`. A successful A2DP<br />
connection lists `Audio Sink` in `bluetoothctl info HEADSET_ADDRESS`, and<br />
PulseAudio creates a sink named like<br />
`bluez_sink.HEADSET_ADDRESS_WITH_UNDERSCORES.a2dp_sink`.<br />
<br />
On current images, `module-stream-restore-nemo` can restore the `x-maemo`<br />
media role at `-20000` volume (silence). Fix its fallback rule:<br />
<br />
<syntaxhighlight lang="sh"><br />
sudo cp -a /etc/pulse/x-maemo-stream-restore.table \<br />
/etc/pulse/x-maemo-stream-restore.table.before-a2dp<br />
sudo sed -i \<br />
's/^sink-input-by-media-role:x-maemo[[:space:]]\+-20000$/sink-input-by-media-role:x-maemo 0/' \<br />
/etc/pulse/x-maemo-stream-restore.table<br />
</syntaxhighlight><br />
<br />
Reload the module as user `ceres`:<br />
<br />
<syntaxhighlight lang="sh"><br />
pactl list short modules | grep stream-restore-nemo<br />
pactl unload-module MODULE_ID<br />
pactl load-module module-stream-restore-nemo \<br />
restore_device=no restore_volume=yes restore_muted=no \<br />
route_table=/etc/pulse/x-maemo-route.table \<br />
fallback_table=/etc/pulse/x-maemo-stream-restore.table use_voice=false<br />
</syntaxhighlight><br />
<br />
A previously stored stream setting can still set a new playback stream to 0%.<br />
While playback is active, inspect and fix it:<br />
<br />
<syntaxhighlight lang="sh"><br />
pactl list sink-inputs<br />
pactl set-sink-input-mute SINK_INPUT_ID 0<br />
pactl set-sink-input-volume SINK_INPUT_ID 100%<br />
</syntaxhighlight><br />
<br />
Set the headset as the default output:<br />
<br />
<syntaxhighlight lang="sh"><br />
pactl set-default-sink bluez_sink.HEADSET_ADDRESS_WITH_UNDERSCORES.a2dp_sink<br />
pactl set-sink-mute bluez_sink.HEADSET_ADDRESS_WITH_UNDERSCORES.a2dp_sink 0<br />
pactl set-sink-volume bluez_sink.HEADSET_ADDRESS_WITH_UNDERSCORES.a2dp_sink 100%<br />
</syntaxhighlight><br />
<br />
Test playback with a tone:<br />
<br />
<syntaxhighlight lang="sh"><br />
gst-launch-1.0 -q \<br />
audiotestsrc wave=sine freq=880 num-buffers=430 ! \<br />
audioconvert ! audioresample ! \<br />
pulsesink device=bluez_sink.HEADSET_ADDRESS_WITH_UNDERSCORES.a2dp_sink<br />
</syntaxhighlight></div>Berosethttps://wiki.asteroidos.org/index.php?title=SSH&diff=1035SSH2026-09-02T21:36:37Z<p>Beroset: /* Root access via SSH */</p>
<hr />
<div>By default, you can get a remote shell on you smartwatch with SSH over RNDIS. On some smartwatches, it is also possible to use SSH with Wi-Fi.<br />
<br />
== SSH over USB ==<br />
USB Moded already set up udhcpd so that your watch gets the 192.168.2.15 IP address on its rndis interface. You can then connect to your watch from your computer with the following command:<br />
<pre><br />
ssh ceres@192.168.2.15<br />
</pre><br />
If your computer does not automatically get an IP address for its rndis interface, you might need to run this first:<br />
<pre><br />
sudo dhclient -v enp0s20f0u8<br />
</pre><br />
<br />
== SSH over WiFi ==<br />
<br />
Dropbear is already running on the watch so we just need to configure an IP address to connect to.<br />
The [[IP Connection]] page describes how to set up Wi-Fi.<br />
Once the setup is done, you can look for the IP address your Router assigned via DHCP, with <br />
<pre># ip a show dev wlan0</pre>.<br />
<br />
== Root access via SSH ==<br />
If you need to access root via ssh, there are two choices on the most recent builds. First is to use <code>sudo</code> after having logged in as the <code>ceres</code> user. The other option is to copy ssh keys as described in [[OpenEmbedded#A_word_about_root_access]]<br />
<br />
== Troubleshooting SSH ==<br />
<br />
* Using SCP/SSH results in a <code>REMOTE HOST IDENTIFICATION HAS CHANGED!</code> warning<br />
** This means that there is already a different device known with the same IP adress. This happens if you reinstall AsteroidOS or you use multiple watches. The warning can be resolved by removing the record of the IP adress from the list of known hosts as follows: <br />
<pre>ssh-keygen -R 192.168.2.15</pre><br />
<br />
----<br />
= ADB =<br />
<br />
Some watches have a known issue with the SSH implementation that prevents a working SSH connection. On these devices, ADB (Android Debug Bridge) is the only available shell access method.<br />
<br />
ADB can also be used as a straightforward alternative to SSH on any supported watch, and provides equivalent root shell access.<br />
<br />
== Enabling ADB ==<br />
<br />
ADB and SSH are both enabled and disabled individually in '''Settings > USB'''. Selecting '''Charging only''' disables both. The toggle takes effect immediately without a restart.<br />
<br />
== Connecting ==<br />
<br />
With ADB enabled and the watch connected over USB, open a shell with:<br />
<br />
<pre>adb shell</pre><br />
<br />
This gives you a root shell equivalent to <code>ssh root@192.168.2.15</code>.<br />
<br />
== Multiple watches ==<br />
<br />
When more than one watch is connected, ADB assigns each device a port. List all connected devices and their ports with:<br />
<br />
<pre>adb devices</pre><br />
<br />
Connect to a specific watch by passing its port with the <code>-s</code> flag:<br />
<br />
<pre>adb -s <port> shell</pre></div>Berosethttps://wiki.asteroidos.org/index.php?title=SSH&diff=1034SSH2026-09-02T21:34:32Z<p>Beroset: Added notes about root access</p>
<hr />
<div>By default, you can get a remote shell on you smartwatch with SSH over RNDIS. On some smartwatches, it is also possible to use SSH with Wi-Fi.<br />
<br />
== SSH over USB ==<br />
USB Moded already set up udhcpd so that your watch gets the 192.168.2.15 IP address on its rndis interface. You can then connect to your watch from your computer with the following command:<br />
<pre><br />
ssh ceres@192.168.2.15<br />
</pre><br />
If your computer does not automatically get an IP address for its rndis interface, you might need to run this first:<br />
<pre><br />
sudo dhclient -v enp0s20f0u8<br />
</pre><br />
<br />
== SSH over WiFi ==<br />
<br />
Dropbear is already running on the watch so we just need to configure an IP address to connect to.<br />
The [[IP Connection]] page describes how to set up Wi-Fi.<br />
Once the setup is done, you can look for the IP address your Router assigned via DHCP, with <br />
<pre># ip a show dev wlan0</pre>.<br />
<br />
== Root access via SSH ==<br />
If you need to access root via ssh, there are two choices on the most recent builds. First is to use <code>sudo</code> after having logged in as the <code>ceres</code> user. The other option is to copy ssh keys as described here: https://wiki.asteroidos.org/index.php/OpenEmbedded#A_word_about_root_access<br />
<br />
== Troubleshooting SSH ==<br />
<br />
* Using SCP/SSH results in a <code>REMOTE HOST IDENTIFICATION HAS CHANGED!</code> warning<br />
** This means that there is already a different device known with the same IP adress. This happens if you reinstall AsteroidOS or you use multiple watches. The warning can be resolved by removing the record of the IP adress from the list of known hosts as follows: <br />
<pre>ssh-keygen -R 192.168.2.15</pre><br />
<br />
----<br />
= ADB =<br />
<br />
Some watches have a known issue with the SSH implementation that prevents a working SSH connection. On these devices, ADB (Android Debug Bridge) is the only available shell access method.<br />
<br />
ADB can also be used as a straightforward alternative to SSH on any supported watch, and provides equivalent root shell access.<br />
<br />
== Enabling ADB ==<br />
<br />
ADB and SSH are both enabled and disabled individually in '''Settings > USB'''. Selecting '''Charging only''' disables both. The toggle takes effect immediately without a restart.<br />
<br />
== Connecting ==<br />
<br />
With ADB enabled and the watch connected over USB, open a shell with:<br />
<br />
<pre>adb shell</pre><br />
<br />
This gives you a root shell equivalent to <code>ssh root@192.168.2.15</code>.<br />
<br />
== Multiple watches ==<br />
<br />
When more than one watch is connected, ADB assigns each device a port. List all connected devices and their ports with:<br />
<br />
<pre>adb devices</pre><br />
<br />
Connect to a specific watch by passing its port with the <code>-s</code> flag:<br />
<br />
<pre>adb -s <port> shell</pre></div>Berosethttps://wiki.asteroidos.org/index.php?title=User_talk:Monperrus&diff=1033User talk:Monperrus2026-09-01T12:56:32Z<p>Beroset: Created page with "Hi! I rejected the edit to add asteroid-local-music but wanted to let you know why. The app looks interesting and useful, but it's not added to meta-asteroid-community yet. Also, there should probably be a way to have both the existing music app and the local one coexisting on the same watch."</p>
<hr />
<div>Hi! I rejected the edit to add asteroid-local-music but wanted to let you know why. The app looks interesting and useful, but it's not added to meta-asteroid-community yet. Also, there should probably be a way to have both the existing music app and the local one coexisting on the same watch.</div>Berosethttps://wiki.asteroidos.org/index.php?title=Seluna/solios&diff=1031Seluna/solios2026-08-29T10:16:11Z<p>Beroset: </p>
<hr />
<div>{{Watches<br />
|Name=seluna<br />
|OtherNames=solios,helios,sol,selene,luna<br />
|Model=Google Pixel Watch 3<br />
|ReleaseDate=2024-09-10<br />
|Chipset=sw5100<br />
|KernelVersion=5.15<br />
|AndroidVersion=16<br />
|Picture=<br />
|Status=port in progress<br />
|Stars=0<br />
|StatusDisplay=good<br />
|StatusTouch=good<br />
|StatusBluetooth=bad<br />
|StatusHaptics=good<br />
|StatusTiltToWake=good<br />
|StatusLightSensor=good<br />
|StatusAlwaysOnDisplay=good<br />
|StatusDualDisplay=missing<br />
|StatusMicrophone=partial<br />
|StatusSpeaker=partial<br />
|StatusCompass=partial<br />
|StatusSteps=partial<br />
|StatusHeartRate=partial<br />
|StatusUSB=partial<br />
|StatusWLAN=bad<br />
|StatusGPS=bad<br />
|StatusNFC=bad<br />
|StatusCellular=bad<br />
|StatusCamera=missing<br />
|StatusCrown=missing<br />
|StatusHands=missing<br />
}}<br />
[[Category:Watches]]<br />
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).<br />
<br />
= Description =<br />
This watch is sold in 4 variations. LTE and Wi-Fi versions in both 41 mm and 45 mm:<br />
{| class="wikitable"<br />
|-<br />
! Codename !! Model Name<br />
!Note<br />
|-<br />
| seluna || Pixel Watch 3 LTE<br />
|selene+luna=seluna=common LTE platform<br />
|-<br />
|selene<br />
|Pixel Watch 3 LTE (41 mm)<br />
|Resolution: 408x408<br />
|-<br />
|luna<br />
|Pixel Watch 3 LTE (45 mm)<br />
|Resolution: 456x456<br />
|-<br />
| solios || Pixel Watch 3 Wi-Fi<br />
|sol+helios=solios=common Wi-Fi platform<br />
|-<br />
|helios<br />
|Pixel Watch 3 Wi-Fi (41 mm)<br />
|Resolution: 408x408<br />
|-<br />
|sol<br />
|Pixel Watch 3 Wi-Fi (41 mm)<br />
|Resolution: 456x456<br />
|}<br />
<br />
=== Bootloader Unlock ===<br />
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.<br />
<syntaxhighlight lang="bash"><br />
# reboot to bootloader<br />
adb reboot bootloader<br />
<br />
# check if the watch is unlockable. If yes it returns "1"<br />
fastboot flashing get_unlock_ability<br />
<br />
# ask the device to prompt for bootloader unlock<br />
fastboot flashing unlock<br />
</syntaxhighlight>After issuing the unlock command, the action must be confirmed on the watch.<br />
<br />
=== Fastboot ===<br />
You can reach Fastboot Mode without pairing the device by tapping the upper left and lower right of the display right after booting (the first Google Logo). See also [https://support.google.com/googlepixelwatch/answer/13575675?hl=en-GB here].<br />
<br />
=== Repair ===<br />
The Pixel Watch 3 has replaceable straps, but the device is glued shut, making repair attempts harder.<br />
<br />
=== Firmware ===<br />
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].<br />
<br />
Once extracted, the partitions are contained in named image files. e.g. <code>boot.img</code>.</div>Berosethttps://wiki.asteroidos.org/index.php?title=Seluna/solios&diff=1030Seluna/solios2026-08-29T10:13:21Z<p>Beroset: Updated features list</p>
<hr />
<div>{{Watches<br />
|Name=seluna<br />
|OtherNames=solios<br />
|Model=Google Pixel Watch 3<br />
|ReleaseDate=2024-09-10<br />
|Chipset=sw5100<br />
|KernelVersion=5.15<br />
|AndroidVersion=16<br />
|Picture=catfish.png<br />
|Status=port in progress<br />
|Stars=0<br />
|StatusDisplay=good<br />
|StatusTouch=good<br />
|StatusBluetooth=bad<br />
|StatusHaptics=good<br />
|StatusTiltToWake=good<br />
|StatusLightSensor=good<br />
|StatusAlwaysOnDisplay=good<br />
|StatusDualDisplay=missing<br />
|StatusMicrophone=partial<br />
|StatusSpeaker=partial<br />
|StatusCompass=partial<br />
|StatusSteps=partial<br />
|StatusHeartRate=partial<br />
|StatusUSB=partial<br />
|StatusWLAN=bad<br />
|StatusGPS=bad<br />
|StatusNFC=bad<br />
|StatusCellular=bad<br />
|StatusCamera=missing<br />
|StatusCrown=missing<br />
|StatusHands=missing<br />
}}<br />
[[Category:Watches]]<br />
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).<br />
<br />
= Description =<br />
This watch is sold in 4 variations. LTE and Wi-Fi versions in both 41 mm and 45 mm:<br />
{| class="wikitable"<br />
|-<br />
! Codename !! Model Name<br />
!Note<br />
|-<br />
| seluna || Pixel Watch 3 LTE<br />
|selene+luna=seluna=common LTE platform<br />
|-<br />
|selene<br />
|Pixel Watch 3 LTE (41 mm)<br />
|Resolution: 408x408<br />
|-<br />
|luna<br />
|Pixel Watch 3 LTE (45 mm)<br />
|Resolution: 456x456<br />
|-<br />
| solios || Pixel Watch 3 Wi-Fi<br />
|sol+helios=solios=common Wi-Fi platform<br />
|-<br />
|helios<br />
|Pixel Watch 3 Wi-Fi (41 mm)<br />
|Resolution: 408x408<br />
|-<br />
|sol<br />
|Pixel Watch 3 Wi-Fi (41 mm)<br />
|Resolution: 456x456<br />
|}<br />
<br />
=== Bootloader Unlock ===<br />
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.<br />
<syntaxhighlight lang="bash"><br />
# reboot to bootloader<br />
adb reboot bootloader<br />
<br />
# check if the watch is unlockable. If yes it returns "1"<br />
fastboot flashing get_unlock_ability<br />
<br />
# ask the device to prompt for bootloader unlock<br />
fastboot flashing unlock<br />
</syntaxhighlight>After issuing the unlock command, the action must be confirmed on the watch.<br />
<br />
=== Fastboot ===<br />
You can reach Fastboot Mode without pairing the device by tapping the upper left and lower right of the display right after booting (the first Google Logo). See also [https://support.google.com/googlepixelwatch/answer/13575675?hl=en-GB here].<br />
<br />
=== Repair ===<br />
The Pixel Watch 3 has replaceable straps, but the device is glued shut, making repair attempts harder.<br />
<br />
=== Firmware ===<br />
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].<br />
<br />
Once extracted, the partitions are contained in named image files. e.g. <code>boot.img</code>.</div>Berosethttps://wiki.asteroidos.org/index.php?title=OpenEmbedded&diff=1028OpenEmbedded2026-08-12T16:24:44Z<p>Beroset: /* A word about root access */ clarified language</p>
<hr />
<div>[http://www.openembedded.org/wiki/Main_Page OpenEmbedded] (OE) is the build system used by AsteroidOS. It provides a way to easily maintain embedded Linux distributions. OE is also used by projects such as WebOS-Ports, SHR or Ångström. OpenEmbedded is supported by the [https://www.yoctoproject.org/ Yocto project] from the Linux Foundation and provides a rock-solid basis for AsteroidOS.<br />
<br />
OpenEmbedded uses the [https://docs.yoctoproject.org/bitbake/ <code>bitbake</code>] tool which is developed in Python to generate images (like <code>asteroid-image</code>) from packages (like <code>asteroid-launcher-dev</code>) built from recipes (ex: <code>asteroid-launcher_git.bb</code>) provided in layers (ex: <code>meta-asteroid</code>).<br />
<br />
Layers are git repositories containing a bunch of related recipes, example of layers include board support packages (BSPs) like [https://github.com/AsteroidOS/meta-smartwatch/tree/master/meta-dory meta-dory-hybris] or <code>meta-rockchip</code> which describe a way to support a new machine, but also UI layers like <code>meta-xfce</code> or <code>meta-gnome</code> which describe the building process of graphic components.<br />
<br />
A recipe describes how to fetch, patch, configure, compile, install, package (in <code>.rpm</code>, <code>.deb</code> or <code>.ipk</code>) and test a piece of software. Bitbake handles all those operations and the dependencies between them and between recipes. In the end it can generate images or an SDK for multiple targets.<br />
<br />
Contributing to the AsteroidOS’s OE architecture mostly consists in maintaining the [https://github.com/AsteroidOS/meta-asteroid meta-asteroid] and [https://github.com/AsteroidOS/meta-smartwatch meta-smartwatch] repositories which contain the recipes related to AsteroidOS and the watches' BSPs.<br />
<br />
In depth info can be found in the [https://docs.yoctoproject.org/index.html Yocto Project's manual]<br />
<br />
[[File:Openembedded.png|frameless]]<br />
<br />
<br />
=A Quick Tutorial=<br />
<br />
The rest of this description assumes that you have already read and followed the [[Building AsteroidOS]] instructions, and that you have built AsteroidOS for at least one platform (a particular watch or the emulator), and that you are familiar with [https://www.atlassian.com/git/tutorials <code>git</code>] and the [https://www.linux.org/forums/linux-beginner-tutorials.123/ Linux] command line.<br />
<br />
This tutorial will introduce you to the following topics:<br />
<br />
*[[OpenEmbedded#Changing an Existing Application|Changing an Existing Application]] You don't like how something behaves or want to fix an issue in an existing application? This will introduce you to the tooling used to allow you to make these changes.<br />
* [[OpenEmbedded#Adding a New Application|Adding a New Application]] Use the tooling to create a new application recipe and test it on a watch.<br />
*[[OpenEmbedded#Sharing your changes|Sharing your changes]] You've made changes on your local build of AsteroidOS. How do you share these changes? This will be explained in this part of the tutorial.<br />
<br />
<br />
==Changing an Existing Application==<br />
<br />
This will guide you step-by-step from the process of wanting to make a change to actually making that change and getting it running on your watch.<br />
<br />
Let's say that you want to make a simple change to the flashlight app on the watch. Your favorite color is blue, so you want to change the flashlight screen's color to a blue color.<br />
<br />
Since you have already run <code>bitbake asteroid-image</code> you know that there are over 5000 tasks to create the image file that can be flashed to a watch. How do you figure out which of those 5000 tasks builds the flashlight application?<br />
<br />
Two fundamental concepts within Yocto and bitbake are the ''layer'' and the ''recipe'' as mentioned above. Examine the layers in the AsteroidOS project:<br />
<br />
<pre><br />
bitbake-layers show-layers<br />
NOTE: Starting bitbake server...<br />
layer path priority<br />
==========================================================================<br />
meta-qt5 /home/developer/asteroid/src/meta-qt5 7<br />
meta /home/developer/asteroid/src/oe-core/meta 5<br />
meta-asteroid /home/developer/asteroid/src/meta-asteroid 7<br />
meta-asteroid-community /home/developer/asteroid/src/meta-asteroid-community 7<br />
meta-oe /home/developer/asteroid/src/meta-openembedded/meta-oe 5<br />
meta-multimedia /home/developer/asteroid/src/meta-openembedded/meta-multimedia 5<br />
meta-gnome /home/developer/asteroid/src/meta-openembedded/meta-gnome 5<br />
meta-networking /home/developer/asteroid/src/meta-openembedded/meta-networking 5<br />
meta-android /home/developer/asteroid/src/meta-smartphone/meta-android 7<br />
meta-python /home/developer/asteroid/src/meta-openembedded/meta-python 5<br />
meta-filesystems /home/developer/asteroid/src/meta-openembedded/meta-filesystems 5<br />
meta-anthias /home/developer/asteroid/src/meta-smartwatch/meta-anthias 7<br />
meta-bass /home/developer/asteroid/src/meta-smartwatch/meta-bass 7<br />
meta-beluga /home/developer/asteroid/src/meta-smartwatch/meta-beluga 7<br />
meta-catfish /home/developer/asteroid/src/meta-smartwatch/meta-catfish 7<br />
meta-dory /home/developer/asteroid/src/meta-smartwatch/meta-dory 7<br />
meta-lenok /home/developer/asteroid/src/meta-smartwatch/meta-lenok 8<br />
meta-mooneye /home/developer/asteroid/src/meta-smartwatch/meta-mooneye 7<br />
meta-mtk6580 /home/developer/asteroid/src/meta-smartwatch/meta-mtk6580 7<br />
meta-narwhal /home/developer/asteroid/src/meta-smartwatch/meta-narwhal 7<br />
meta-ray /home/developer/asteroid/src/meta-smartwatch/meta-ray 7<br />
meta-sawfish /home/developer/asteroid/src/meta-smartwatch/meta-sawfish 7<br />
meta-skipjack /home/developer/asteroid/src/meta-smartwatch/meta-skipjack 6<br />
meta-smelt /home/developer/asteroid/src/meta-smartwatch/meta-smelt 7<br />
meta-sparrow /home/developer/asteroid/src/meta-smartwatch/meta-sparrow 7<br />
meta-sprat /home/developer/asteroid/src/meta-smartwatch/meta-sprat 7<br />
meta-sturgeon /home/developer/asteroid/src/meta-smartwatch/meta-sturgeon 7<br />
meta-swift /home/developer/asteroid/src/meta-smartwatch/meta-swift 8<br />
meta-tetra /home/developer/asteroid/src/meta-smartwatch/meta-tetra 7<br />
meta-wren /home/developer/asteroid/src/meta-smartwatch/meta-wren 7<br />
</pre><br />
<br />
By convention, Yocto layers all begin with <code>meta</code>. There are layers for individual pieces such as Qt, networking, Python, and filesystems. These are followed by the layers for each of the watch codenames. If you are looking for an AsteroidOS-specific application, you can probably guess that it's in the <code>meta-asteroid</code> layer, but you can also ask the computer to search for you.<br />
<br />
Originally, <code>bitbake</code> and its related tools were the only way to do things, but there is now a newer and much more convenient tool named [https://docs.yoctoproject.org/dev/ref-manual/devtool-reference.html <code>devtool</code>]. To search for a recipe with <code>flashlight</code> in the name:<br />
<br />
<pre><br />
devtool search flashlight<br />
</pre><br />
<br />
After a minute or so, <code>devtool</code> finds a single recipe: <code>asteroid-flashlight</code>. You can now modify this recipe:<br />
<pre><br />
devtool modify asteroid-flashlight<br />
</pre><br />
<br />
The last two lines of output will be something like these:<br />
<br />
<pre><br />
INFO: Source tree extracted to /home/developer/asteroid/build/workspace/sources/asteroid-flashlight<br />
INFO: Recipe asteroid-flashlight now set up to build from /home/developer/asteroid/build/workspace/sources/asteroid-flashlight<br />
</pre><br />
<br />
Navigate into this directory, and find the relevant line in <code>src/main.qml</code> and alter the color from white to light blue:<br />
<br />
<pre><br />
color: flashOn ? "lightblue" : "#66444444"<br />
</pre><br />
<br />
Save the altered source code and build this copy of the flashlight app:<br />
<br />
<pre><br />
devtool build asteroid-flashlight<br />
</pre><br />
<br />
After some time, the build will complete and you can test the application on a watch.<br />
<br />
<pre><br />
devtool deploy-target asteroid-flashlight root@192.168.2.15<br />
</pre><br />
<br />
Now the flashlight app will show a light blue screen. Reverting to the original version is very simple:<br />
<br />
<pre><br />
devtool undeploy-target asteroid-flashlight root@192.168.2.15<br />
</pre><br />
<br />
==Adding a New Application==<br />
<br />
Let's say you have decided to create a new application. As described in [[Creating an Asteroid app]] page, the [https://github.com/AsteroidOS/asteroid-helloworld Asteroid-helloworld] which can be used as the basis for your own new application can be cloned and then modified. So let's say you've done that and now you'd like to integrate the app into the Yocto and bitbake build system.<br />
<br />
For these instructions, it is assumed that you have already built AsteroidOS for <code>sturgeon</code> (or your preferred test platform). Let's say you have already cloned the <code>asteroid-helloworld</code> into a directory named <code>~/tools/AsteroidOS/asteroid-helloworld/</code>. You can very easily create a recipe for it with <code>devtool</code>:<br />
<br />
<pre><br />
devtool add hello ~/tools/AsteroidOS/asteroid-helloworld/<br />
</pre><br />
<br />
<pre><br />
$ devtool add hello ~/tools/AsteroidOS/asteroid-helloworld/<br />
NOTE: Starting bitbake server...<br />
NOTE: Starting bitbake server...<br />
INFO: Please add the following line for 'LICENSE' to a 'lib/recipetool/licenses.csv' and replace `Unknown` with the license:<br />
84dcc94da3adb52b53ae4fa38fe49e5d,Unknown<br />
NOTE: Starting bitbake server...<br />
INFO: Recipe /home/developer/asteroid/build/workspace/recipes/hello/hello_git.bb has been automatically created; further editing may be required to make it fully functional<br />
</pre><br />
<br />
So the tool has created a recipe based on just the name we have given and the directory containing the source. Since it seems unsure about the license and suggests that further editing might be required, let's take its advice and edit the recipe. The simplest way to do that is again to use <code>devtool</code>:<br />
<br />
<pre><br />
devtool edit-recipe hello<br />
</pre><br />
<br />
This will open the recipe in an editor. It says that the license is unknown, so we change the line from <code>LICENSE = "Unknown"</code> to <code>LICENSE = "GPL-3.0-only"</code>. Not that the <code>SRC_URI</code> is set to point to a git repository. This is because <code>devtool</code> is smart enough to figure out that even though you gave it a local directory, it discovered that the source was actually git and made the appropriate changes. We can now attempt to build.<br />
<br />
<pre><br />
devtool build hello<br />
</pre><br />
<br />
However this fails because we're still missing something. In this case, we're missing two things. First, instead of the <code>inherit cmake</code> line, it should be <code>inherit cmake_qt5</code> and second, we need to add the following line just below that:<br />
<br />
<pre><br />
DEPENDS += "qml-asteroid asteroid-generate-desktop-native qttools-native qtdeclarative-native"<br />
</pre><br />
<br />
With those two small changes, we should now get a successful build.<br />
<br />
===A word about root access===<br />
If you're building for a pre-2.2 AsteroidOS, no special setup is required, since those versions used an empty root password. <br />
<br />
However, starting with version 2.2 of AsteroidOS, root login via password is explicitly disabled by default. So for the following section to work with version 2.2 or later, we have to set up root access via ssh keys. <br />
<br />
The first thing that's needed is to generate a key-pair. If the file <code>~/.ssh/id_ed25519.pub</code> already exists, then this step is already done. If it does not, you can generate the key pair like this:<br />
<br />
<pre><br />
ssh-keygen -t ed25519<br />
</pre><br />
<br />
This creates a private key (<code>~/.ssh/id_ed25519</code>) and a public key (<code>~/.ssh/id_ed25519.pub</code>). <br />
<br />
Once these are created, we need to add the contents of the public key to the watch. One can copy the public key to the watch using `adb` and then append its contents to the <code>authorized_keys</code> file. Execute these command on the host computer<br />
<br />
<pre><br />
adb push id_ed25519.pub /home/root<br />
adb shell<br />
</pre><br />
<br />
Then in the root shell on the watch, add the key to the list of authorized ones:<br />
<br />
<pre><br />
mkdir -p ~/.ssh<br />
chmod 700 ~/.ssh<br />
cat ~/id_ed25519.pub >> ~/.ssh/authorized_keys<br />
chmod 600 ~/.ssh/authorized_keys<br />
</pre><br />
<br />
This sets up the watch to allow password-less but secure root access. You can now proceed to deploying the app on the watch.<br />
<br />
===Deploying to the watch===<br />
As before, we can easily test on the watch. <br />
<br />
<pre><br />
devtool deploy-target hello root@192.168.2.15<br />
</pre><br />
<br />
This will automatically install all of the install targets from the <code>hello</code> project onto the watch. Start the launcher on the watch and scroll to the end of your list of apps, and you should now see a "HELLO WORLD APP" at the end. Running it will show "Hello World!" on the screen.<br />
<br />
Removing it from the watch is also the same as before:<br />
<br />
<pre><br />
devtool undeploy-target hello root@192.168.2.15<br />
</pre><br />
<br />
==Sharing your changes==<br />
<br />
If you make a change to AsteroidOS software that you think might be useful to others, such as a bug fix or feature enhancement, there are several ways to share it, depending on what exactly is being changed.<br />
<br />
*creating a recipe patch file<br />
*creating a pull request for an AsteroidOS project<br />
*creating an installable package (<code>.ipk</code>)<br />
<br />
==Creating a recipe patch file==<br />
<br />
Many of the software packages that make up an AsteroidOS image are not unique to AsteroidOS. They may be general purpose tools such as <code>systemctl</code> or watch-specific software from other open source repositories such as <code>mcetool</code>. For these, there may be a need to introduce a patch just for AsteroidOS. To do so, first, within the appropriate <code>workspace</code> directory where you made changes, use <code>git commit</code> to commit the changes to the local repository. Once this is done, automatically create the patch. For our example, we could do that with this command:<br />
<br />
<pre><br />
devtool finish asteroid-flashlight meta-asteroid<br />
</pre><br />
<br />
This creates one patch for each new git commit and automatically updates the recipe file in the named layer (in this case, <code>meta-asteroid</code>). (Note that this is just an example and would not really be appropriate for <code>asteroid-flashlight</code> because this application is unique to AsteroidOS.) To see what was done, you can navigate to <code>asteroid/src/meta-asteroid</code> and type <code>git diff</code>. You will see that the patch file has been added to the recipe for <code>asteroid-flashlight</code>. Also note that to ensure you don't lose any work, <code>devtool</code> will not delete the directory tree in <code>workspace</code> unless you specifically ask it to do so.<br />
<br />
==Create a pull request==<br />
<br />
For an AsteroidOS application, it may be more appropriate to create a [https://opensource.com/article/19/7/create-pull-request-github *pull request*]. To do that, we need to create a fork of the software we want to modify, create a branch, make the changes, commit and push the changes, and then create a pull request (PR). This guide doesn't describe all of these steps in detail, but describes how to use <code>devtool</code> and <code>git</code> to create a PR.<br />
<br />
Once the changes are made, as in the <code>asteroid-flashlight</code> example above, you can simply use git to point to your own repository. Specifically, navigate to <code>asteroid/build/workspace/sources/asteroid-flashlight</code> and use the command <code>git remote -v</code> to see that the remote repository is the original source. Change it to point to your own repository with <code>git remote set-url origin MYCLONE</code>, substituting your repository's URL for <code>MYCLONE</code>. If you have already made local commits, you may wish to change the name of the branch from <code>devtool</code> (which is what <code>devtool</code> uses by default) to something meaningful to you before pushing the changes to your repository. Then create a PR from the new branch in the usual way.<br />
<br />
==Create an installable package==<br />
<br />
Chances are that your own Linux computer uses <code>.rpm</code> or <code>.deb</code> files with a package manager to allow simplified installation of software. AsteroidOS uses the [https://en.wikipedia.org/wiki/Opkg <code>opkg</code>] package manager which uses <code>.ipk</code> files. To create one from your modified software, here we need to use <code>bitbake</code> rather than <code>devtool</code>:<br />
<br />
<pre><br />
bitbake asteroid-flashlight<br />
</pre><br />
<br />
Note that this typically creates four different <code>ipk</code> files. We can take a look:<br />
<br />
<pre><br />
cd tmp/deploy/ipk/armv7vehf-neon/<br />
ls asteroid-flashlight*<br />
</pre><br />
<br />
This returns the names of the four files:<br />
<br />
<pre><br />
asteroid-flashlight-dbg_+git999-r1_armv7vehf-neon.ipk<br />
asteroid-flashlight-dev_+git999-r1_armv7vehf-neon.ipk<br />
asteroid-flashlight_+git999-r1_armv7vehf-neon.ipk<br />
asteroid-flashlight-src_+git999-r1_armv7vehf-neon.ipk<br />
</pre><br />
<br />
We can ignore the <code>-dbg</code>, <code>-dev</code> and <code>-src</code> files and simply choose the one with the shortest name, which is the release version of the package. We can copy it to the watch:<br />
<br />
<pre><br />
scp asteroid-flashlight_+git999-r1_armv7vehf-neon.ipk root@192.168.2.15:.<br />
</pre><br />
<br />
Now we can [[SSH]] as root to the watch (<code>ssh root@192.168.2.15</code>) and install the package:<br />
<br />
<pre><br />
opkg --force-reinstall install asteroid-flashlight_+git999-r1_armv7vehf-neon.ipk<br />
</pre></div>Berosethttps://wiki.asteroidos.org/index.php?title=OpenEmbedded&diff=1027OpenEmbedded2026-08-12T16:23:04Z<p>Beroset: /* Adding a New Application */ Added section on how to use devtool with AsteroidOS 2.2 and later</p>
<hr />
<div>[http://www.openembedded.org/wiki/Main_Page OpenEmbedded] (OE) is the build system used by AsteroidOS. It provides a way to easily maintain embedded Linux distributions. OE is also used by projects such as WebOS-Ports, SHR or Ångström. OpenEmbedded is supported by the [https://www.yoctoproject.org/ Yocto project] from the Linux Foundation and provides a rock-solid basis for AsteroidOS.<br />
<br />
OpenEmbedded uses the [https://docs.yoctoproject.org/bitbake/ <code>bitbake</code>] tool which is developed in Python to generate images (like <code>asteroid-image</code>) from packages (like <code>asteroid-launcher-dev</code>) built from recipes (ex: <code>asteroid-launcher_git.bb</code>) provided in layers (ex: <code>meta-asteroid</code>).<br />
<br />
Layers are git repositories containing a bunch of related recipes, example of layers include board support packages (BSPs) like [https://github.com/AsteroidOS/meta-smartwatch/tree/master/meta-dory meta-dory-hybris] or <code>meta-rockchip</code> which describe a way to support a new machine, but also UI layers like <code>meta-xfce</code> or <code>meta-gnome</code> which describe the building process of graphic components.<br />
<br />
A recipe describes how to fetch, patch, configure, compile, install, package (in <code>.rpm</code>, <code>.deb</code> or <code>.ipk</code>) and test a piece of software. Bitbake handles all those operations and the dependencies between them and between recipes. In the end it can generate images or an SDK for multiple targets.<br />
<br />
Contributing to the AsteroidOS’s OE architecture mostly consists in maintaining the [https://github.com/AsteroidOS/meta-asteroid meta-asteroid] and [https://github.com/AsteroidOS/meta-smartwatch meta-smartwatch] repositories which contain the recipes related to AsteroidOS and the watches' BSPs.<br />
<br />
In depth info can be found in the [https://docs.yoctoproject.org/index.html Yocto Project's manual]<br />
<br />
[[File:Openembedded.png|frameless]]<br />
<br />
<br />
=A Quick Tutorial=<br />
<br />
The rest of this description assumes that you have already read and followed the [[Building AsteroidOS]] instructions, and that you have built AsteroidOS for at least one platform (a particular watch or the emulator), and that you are familiar with [https://www.atlassian.com/git/tutorials <code>git</code>] and the [https://www.linux.org/forums/linux-beginner-tutorials.123/ Linux] command line.<br />
<br />
This tutorial will introduce you to the following topics:<br />
<br />
*[[OpenEmbedded#Changing an Existing Application|Changing an Existing Application]] You don't like how something behaves or want to fix an issue in an existing application? This will introduce you to the tooling used to allow you to make these changes.<br />
* [[OpenEmbedded#Adding a New Application|Adding a New Application]] Use the tooling to create a new application recipe and test it on a watch.<br />
*[[OpenEmbedded#Sharing your changes|Sharing your changes]] You've made changes on your local build of AsteroidOS. How do you share these changes? This will be explained in this part of the tutorial.<br />
<br />
<br />
==Changing an Existing Application==<br />
<br />
This will guide you step-by-step from the process of wanting to make a change to actually making that change and getting it running on your watch.<br />
<br />
Let's say that you want to make a simple change to the flashlight app on the watch. Your favorite color is blue, so you want to change the flashlight screen's color to a blue color.<br />
<br />
Since you have already run <code>bitbake asteroid-image</code> you know that there are over 5000 tasks to create the image file that can be flashed to a watch. How do you figure out which of those 5000 tasks builds the flashlight application?<br />
<br />
Two fundamental concepts within Yocto and bitbake are the ''layer'' and the ''recipe'' as mentioned above. Examine the layers in the AsteroidOS project:<br />
<br />
<pre><br />
bitbake-layers show-layers<br />
NOTE: Starting bitbake server...<br />
layer path priority<br />
==========================================================================<br />
meta-qt5 /home/developer/asteroid/src/meta-qt5 7<br />
meta /home/developer/asteroid/src/oe-core/meta 5<br />
meta-asteroid /home/developer/asteroid/src/meta-asteroid 7<br />
meta-asteroid-community /home/developer/asteroid/src/meta-asteroid-community 7<br />
meta-oe /home/developer/asteroid/src/meta-openembedded/meta-oe 5<br />
meta-multimedia /home/developer/asteroid/src/meta-openembedded/meta-multimedia 5<br />
meta-gnome /home/developer/asteroid/src/meta-openembedded/meta-gnome 5<br />
meta-networking /home/developer/asteroid/src/meta-openembedded/meta-networking 5<br />
meta-android /home/developer/asteroid/src/meta-smartphone/meta-android 7<br />
meta-python /home/developer/asteroid/src/meta-openembedded/meta-python 5<br />
meta-filesystems /home/developer/asteroid/src/meta-openembedded/meta-filesystems 5<br />
meta-anthias /home/developer/asteroid/src/meta-smartwatch/meta-anthias 7<br />
meta-bass /home/developer/asteroid/src/meta-smartwatch/meta-bass 7<br />
meta-beluga /home/developer/asteroid/src/meta-smartwatch/meta-beluga 7<br />
meta-catfish /home/developer/asteroid/src/meta-smartwatch/meta-catfish 7<br />
meta-dory /home/developer/asteroid/src/meta-smartwatch/meta-dory 7<br />
meta-lenok /home/developer/asteroid/src/meta-smartwatch/meta-lenok 8<br />
meta-mooneye /home/developer/asteroid/src/meta-smartwatch/meta-mooneye 7<br />
meta-mtk6580 /home/developer/asteroid/src/meta-smartwatch/meta-mtk6580 7<br />
meta-narwhal /home/developer/asteroid/src/meta-smartwatch/meta-narwhal 7<br />
meta-ray /home/developer/asteroid/src/meta-smartwatch/meta-ray 7<br />
meta-sawfish /home/developer/asteroid/src/meta-smartwatch/meta-sawfish 7<br />
meta-skipjack /home/developer/asteroid/src/meta-smartwatch/meta-skipjack 6<br />
meta-smelt /home/developer/asteroid/src/meta-smartwatch/meta-smelt 7<br />
meta-sparrow /home/developer/asteroid/src/meta-smartwatch/meta-sparrow 7<br />
meta-sprat /home/developer/asteroid/src/meta-smartwatch/meta-sprat 7<br />
meta-sturgeon /home/developer/asteroid/src/meta-smartwatch/meta-sturgeon 7<br />
meta-swift /home/developer/asteroid/src/meta-smartwatch/meta-swift 8<br />
meta-tetra /home/developer/asteroid/src/meta-smartwatch/meta-tetra 7<br />
meta-wren /home/developer/asteroid/src/meta-smartwatch/meta-wren 7<br />
</pre><br />
<br />
By convention, Yocto layers all begin with <code>meta</code>. There are layers for individual pieces such as Qt, networking, Python, and filesystems. These are followed by the layers for each of the watch codenames. If you are looking for an AsteroidOS-specific application, you can probably guess that it's in the <code>meta-asteroid</code> layer, but you can also ask the computer to search for you.<br />
<br />
Originally, <code>bitbake</code> and its related tools were the only way to do things, but there is now a newer and much more convenient tool named [https://docs.yoctoproject.org/dev/ref-manual/devtool-reference.html <code>devtool</code>]. To search for a recipe with <code>flashlight</code> in the name:<br />
<br />
<pre><br />
devtool search flashlight<br />
</pre><br />
<br />
After a minute or so, <code>devtool</code> finds a single recipe: <code>asteroid-flashlight</code>. You can now modify this recipe:<br />
<pre><br />
devtool modify asteroid-flashlight<br />
</pre><br />
<br />
The last two lines of output will be something like these:<br />
<br />
<pre><br />
INFO: Source tree extracted to /home/developer/asteroid/build/workspace/sources/asteroid-flashlight<br />
INFO: Recipe asteroid-flashlight now set up to build from /home/developer/asteroid/build/workspace/sources/asteroid-flashlight<br />
</pre><br />
<br />
Navigate into this directory, and find the relevant line in <code>src/main.qml</code> and alter the color from white to light blue:<br />
<br />
<pre><br />
color: flashOn ? "lightblue" : "#66444444"<br />
</pre><br />
<br />
Save the altered source code and build this copy of the flashlight app:<br />
<br />
<pre><br />
devtool build asteroid-flashlight<br />
</pre><br />
<br />
After some time, the build will complete and you can test the application on a watch.<br />
<br />
<pre><br />
devtool deploy-target asteroid-flashlight root@192.168.2.15<br />
</pre><br />
<br />
Now the flashlight app will show a light blue screen. Reverting to the original version is very simple:<br />
<br />
<pre><br />
devtool undeploy-target asteroid-flashlight root@192.168.2.15<br />
</pre><br />
<br />
==Adding a New Application==<br />
<br />
Let's say you have decided to create a new application. As described in [[Creating an Asteroid app]] page, the [https://github.com/AsteroidOS/asteroid-helloworld Asteroid-helloworld] which can be used as the basis for your own new application can be cloned and then modified. So let's say you've done that and now you'd like to integrate the app into the Yocto and bitbake build system.<br />
<br />
For these instructions, it is assumed that you have already built AsteroidOS for <code>sturgeon</code> (or your preferred test platform). Let's say you have already cloned the <code>asteroid-helloworld</code> into a directory named <code>~/tools/AsteroidOS/asteroid-helloworld/</code>. You can very easily create a recipe for it with <code>devtool</code>:<br />
<br />
<pre><br />
devtool add hello ~/tools/AsteroidOS/asteroid-helloworld/<br />
</pre><br />
<br />
<pre><br />
$ devtool add hello ~/tools/AsteroidOS/asteroid-helloworld/<br />
NOTE: Starting bitbake server...<br />
NOTE: Starting bitbake server...<br />
INFO: Please add the following line for 'LICENSE' to a 'lib/recipetool/licenses.csv' and replace `Unknown` with the license:<br />
84dcc94da3adb52b53ae4fa38fe49e5d,Unknown<br />
NOTE: Starting bitbake server...<br />
INFO: Recipe /home/developer/asteroid/build/workspace/recipes/hello/hello_git.bb has been automatically created; further editing may be required to make it fully functional<br />
</pre><br />
<br />
So the tool has created a recipe based on just the name we have given and the directory containing the source. Since it seems unsure about the license and suggests that further editing might be required, let's take its advice and edit the recipe. The simplest way to do that is again to use <code>devtool</code>:<br />
<br />
<pre><br />
devtool edit-recipe hello<br />
</pre><br />
<br />
This will open the recipe in an editor. It says that the license is unknown, so we change the line from <code>LICENSE = "Unknown"</code> to <code>LICENSE = "GPL-3.0-only"</code>. Not that the <code>SRC_URI</code> is set to point to a git repository. This is because <code>devtool</code> is smart enough to figure out that even though you gave it a local directory, it discovered that the source was actually git and made the appropriate changes. We can now attempt to build.<br />
<br />
<pre><br />
devtool build hello<br />
</pre><br />
<br />
However this fails because we're still missing something. In this case, we're missing two things. First, instead of the <code>inherit cmake</code> line, it should be <code>inherit cmake_qt5</code> and second, we need to add the following line just below that:<br />
<br />
<pre><br />
DEPENDS += "qml-asteroid asteroid-generate-desktop-native qttools-native qtdeclarative-native"<br />
</pre><br />
<br />
With those two small changes, we should now get a successful build.<br />
<br />
===A word about root access===<br />
If you're building for a pre-2.2 AsteroidOS, this will work directly, since those versions used an empty root password. However, starting with version 2.2 of AsteroidOS, root login via password is explicitly disabled by default. So for the following section to work with version 2.2 or later, we have to set up root access via ssh keys. <br />
<br />
The first thing that's needed is to generate a key-pair. If the file <code>~/.ssh/id_ed25519.pub</code> already exists, then this step is already done. If it does not, you can generate the key pair like this:<br />
<br />
<pre><br />
ssh-keygen -t ed25519<br />
</pre><br />
<br />
This creates a private key (<code>~/.ssh/id_ed25519</code>) and a public key (<code>~/.ssh/id_ed25519.pub</code>). <br />
<br />
Once these are created, we need to add the contents of the public key to the watch. One can copy the public key to the watch using `adb` and then append its contents to the <code>authorized_keys</code> file. Execute these command on the host computer<br />
<br />
<pre><br />
adb push id_ed25519.pub /home/root<br />
adb shell<br />
</pre><br />
<br />
Then in the root shell on the watch, add the key to the list of authorized ones:<br />
<br />
<pre><br />
mkdir -p ~/.ssh<br />
chmod 700 ~/.ssh<br />
cat ~/id_ed25519.pub >> ~/.ssh/authorized_keys<br />
chmod 600 ~/.ssh/authorized_keys<br />
</pre><br />
<br />
This sets up the watch to allow password-less but secure root access. You can now proceed to deploying the app on the watch.<br />
<br />
===Deploying to the watch===<br />
As before, we can easily test on the watch. <br />
<br />
<pre><br />
devtool deploy-target hello root@192.168.2.15<br />
</pre><br />
<br />
This will automatically install all of the install targets from the <code>hello</code> project onto the watch. Start the launcher on the watch and scroll to the end of your list of apps, and you should now see a "HELLO WORLD APP" at the end. Running it will show "Hello World!" on the screen.<br />
<br />
Removing it from the watch is also the same as before:<br />
<br />
<pre><br />
devtool undeploy-target hello root@192.168.2.15<br />
</pre><br />
<br />
==Sharing your changes==<br />
<br />
If you make a change to AsteroidOS software that you think might be useful to others, such as a bug fix or feature enhancement, there are several ways to share it, depending on what exactly is being changed.<br />
<br />
*creating a recipe patch file<br />
*creating a pull request for an AsteroidOS project<br />
*creating an installable package (<code>.ipk</code>)<br />
<br />
==Creating a recipe patch file==<br />
<br />
Many of the software packages that make up an AsteroidOS image are not unique to AsteroidOS. They may be general purpose tools such as <code>systemctl</code> or watch-specific software from other open source repositories such as <code>mcetool</code>. For these, there may be a need to introduce a patch just for AsteroidOS. To do so, first, within the appropriate <code>workspace</code> directory where you made changes, use <code>git commit</code> to commit the changes to the local repository. Once this is done, automatically create the patch. For our example, we could do that with this command:<br />
<br />
<pre><br />
devtool finish asteroid-flashlight meta-asteroid<br />
</pre><br />
<br />
This creates one patch for each new git commit and automatically updates the recipe file in the named layer (in this case, <code>meta-asteroid</code>). (Note that this is just an example and would not really be appropriate for <code>asteroid-flashlight</code> because this application is unique to AsteroidOS.) To see what was done, you can navigate to <code>asteroid/src/meta-asteroid</code> and type <code>git diff</code>. You will see that the patch file has been added to the recipe for <code>asteroid-flashlight</code>. Also note that to ensure you don't lose any work, <code>devtool</code> will not delete the directory tree in <code>workspace</code> unless you specifically ask it to do so.<br />
<br />
==Create a pull request==<br />
<br />
For an AsteroidOS application, it may be more appropriate to create a [https://opensource.com/article/19/7/create-pull-request-github *pull request*]. To do that, we need to create a fork of the software we want to modify, create a branch, make the changes, commit and push the changes, and then create a pull request (PR). This guide doesn't describe all of these steps in detail, but describes how to use <code>devtool</code> and <code>git</code> to create a PR.<br />
<br />
Once the changes are made, as in the <code>asteroid-flashlight</code> example above, you can simply use git to point to your own repository. Specifically, navigate to <code>asteroid/build/workspace/sources/asteroid-flashlight</code> and use the command <code>git remote -v</code> to see that the remote repository is the original source. Change it to point to your own repository with <code>git remote set-url origin MYCLONE</code>, substituting your repository's URL for <code>MYCLONE</code>. If you have already made local commits, you may wish to change the name of the branch from <code>devtool</code> (which is what <code>devtool</code> uses by default) to something meaningful to you before pushing the changes to your repository. Then create a PR from the new branch in the usual way.<br />
<br />
==Create an installable package==<br />
<br />
Chances are that your own Linux computer uses <code>.rpm</code> or <code>.deb</code> files with a package manager to allow simplified installation of software. AsteroidOS uses the [https://en.wikipedia.org/wiki/Opkg <code>opkg</code>] package manager which uses <code>.ipk</code> files. To create one from your modified software, here we need to use <code>bitbake</code> rather than <code>devtool</code>:<br />
<br />
<pre><br />
bitbake asteroid-flashlight<br />
</pre><br />
<br />
Note that this typically creates four different <code>ipk</code> files. We can take a look:<br />
<br />
<pre><br />
cd tmp/deploy/ipk/armv7vehf-neon/<br />
ls asteroid-flashlight*<br />
</pre><br />
<br />
This returns the names of the four files:<br />
<br />
<pre><br />
asteroid-flashlight-dbg_+git999-r1_armv7vehf-neon.ipk<br />
asteroid-flashlight-dev_+git999-r1_armv7vehf-neon.ipk<br />
asteroid-flashlight_+git999-r1_armv7vehf-neon.ipk<br />
asteroid-flashlight-src_+git999-r1_armv7vehf-neon.ipk<br />
</pre><br />
<br />
We can ignore the <code>-dbg</code>, <code>-dev</code> and <code>-src</code> files and simply choose the one with the shortest name, which is the release version of the package. We can copy it to the watch:<br />
<br />
<pre><br />
scp asteroid-flashlight_+git999-r1_armv7vehf-neon.ipk root@192.168.2.15:.<br />
</pre><br />
<br />
Now we can [[SSH]] as root to the watch (<code>ssh root@192.168.2.15</code>) and install the package:<br />
<br />
<pre><br />
opkg --force-reinstall install asteroid-flashlight_+git999-r1_armv7vehf-neon.ipk<br />
</pre></div>Berosethttps://wiki.asteroidos.org/index.php?title=IP_Connection&diff=1026IP Connection2026-08-05T13:27:23Z<p>Beroset: document 2.2 changes regarding root login and sudo</p>
<hr />
<div>Configuring an IP connection on your watch has to be done manually until a GUI settings option is available. On watches that support WLAN, you can enable Wi-Fi and configure the connection using <code>connmanctl</code> like described below. Forwarding IP requests to a connected PC via USB is another option, explained in the second paragraph.<br />
<br />
<br />
== AsteroidOS versions before 2.2 ==<br />
By default, there is no <code>root</code> or <code>ceres</code> password, and no firewall rules. (However, on some watches, the kernel has the <code>CONFIG_ANDROID_PARANOID_NETWORK</code> kernel option enabled, see below.) A password can be set using the passwd command.<br />
<br />
== AsteroidOS versions 2.2 and later ==<br />
There is no <code>ceres</code> password, and no firewall rules. There is an invalid <code>root</code> password set, disallowing any password login. Root login is also disabled in <code>sshd_config</code>. However the <code>sudo</code> command is now included by default, so the <code>ceres</code> user can use that for temporary privilege escalation when needed.<br />
<br />
If it's needed, root empty password can be re-enabled by running:<br />
<code>sudo passwd -d root</code><br />
<br />
Also, ssh password login for <code>root</code> can be enabled with:<br />
<pre><br />
sudo sed -i 's/^[#[:space:]]PermitRootLogin./PermitRootLogin yes/' /etc/ssh/sshd_config<br />
</pre><br />
<br />
By default, password and keyboard-interactive authentication is disabled for <code>root</code>.<br />
<br />
= IP over WLAN (WiFi) =<br />
Connect to your watch using <code>ssh root@192.168.2.15</code> or <code>adb shell</code>.<br />
<br />
<pre>connmanctl</pre><br />
Starts the connmanctl interactive mode. The prompt indicator will change to <code>connmanctl></code><br />
<pre>enable wifi</pre><br />
Output: Enabled wifi<br />
<pre>scan wifi</pre><br />
Output: Scan completed for wifi<br />
<pre>agent on</pre><br />
Output: Agent registered<br />
<br />
The Agent will handle automatic reconnect to the network.<br />
<pre>services</pre><br />
Shows the discovered SSIDs and their service identifier.<br />
<br />
Output example:<br />
<br />
<code>YourNetwork wifi_1234567890_1234567890_managed_psk</code><br />
<br />
<code>OtherLAN wifi_0987654321_123456789_managed_psk</code><br />
<pre>connect <ServiceIdentifierOfYourSSID></pre> <br />
Example:<br />
<br />
<code>connect wifi_1234567890_1234567890_managed_psk</code><br />
<br />
Prompt changes to <code>Passphrase?</code> and asks for the password to the SSID.<br />
<br />
<code>TypeYourPassPhraseAndPressEnter</code><br />
<br />
Output: Connected to wifi_1234567890_1234567890_managed_psk<br />
<br />
Note: If the connection fails with an error (e.g., "Invalid key" or no connection), try connecting to the other service identifier listed for the same SSID name, as it may correspond to the 2.4 GHz band that your watch supports more reliably (while the other is likely 5 GHz).<br />
<pre>quit</pre><br />
Leaves the connmanctl interactive mode.<br />
<br />
Check whether an IP address has been assigned to the watch using <code>ip a show dev wlan0</code> or <code>ifconfig wlan0</code> or by trying to <code>ping 8.8.8.8</code>.<br />
<br />
Note that activated WLAN consumes additional power. Currently, it is recommended to disable the function after use. <code>connmanctl disable wifi</code> is used to disable Wi-Fi and power off WLAN temporarily. <code>connmanctl enable wifi</code> activates WLAN again and connects to the last used Wi-Fi network.<br />
<br />
Some more documentation on connman can be found on [https://wiki.archlinux.org/index.php/ConnMan#Connecting_to_a_protected_access_point ArchWiki].<br />
<br />
<br />
=IP over USB=<br />
It is possible to allow your watch to be able to use your Linux computer's internet connection via a USB connection. You will need: <br />
<br />
#A Linux computer with RNDIS support loaded and enabled<br />
#The ability to change network configurations on that computer<br />
#A network connection<br />
<br />
This works by using the RNDIS driver to allow the USB device to appear to be a network interface. RNDIS stands for "Remote Network Driver Interface Specification" and was a proprietary protocol from Microsoft. It is supported in Linux by the <code>rndis_host</code> driver. This driver may either be compiled into the kernel, or more typically provided as an optional module. If you're not sure, you can try this <code>lsmod</code> to see if it's loaded on your computer.<br />
<br />
<pre><br />
lsmod | grep ndis<br />
rndis_host 24576 0<br />
cdc_ether 24576 1 rndis_host<br />
usbnet 61440 2 rndis_host,cdc_ether<br />
</pre><br />
<br />
If it isn't you might be able to use <code>modprobe rndis_host</code> (with root privileges) to install the module.<br />
<br />
Once the <code>rndis_host</code> is installed and running, you can enable Network Address Translation (NAT) to allow your Linux computer to share it's internet IP address with the watch. To configure a NAT '''on your computer''' (Note: Replace eth0 with the name of the interface that connects your computer to the Internet) with:<br />
<br />
<pre>echo 1 > /proc/sys/net/ipv4/ip_forward</pre><br />
<pre>iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE</pre><br />
<br />
Here again, you might need root privileges for those commands, depending on how your computer is configured.<br />
<br />
Configure a default gateway and DNS '''on the watch''' with the following commands ran via [[SSH]] as the root user:<br />
<br />
<pre>ip route add default via 192.168.2.1</pre><br />
<pre>echo "nameserver 8.8.8.8" >> /etc/resolv.conf</pre><br />
<br />
Note that this assumes that your computer's IP address on RNDIS is 192.168.2.1, which is the default, but if you have multiple watches, or have plugged and unplugged the same watch a few times, it might be different. To make sure, on the watch, you can type <code>who</code> and it will reply with something like this:<br />
<br />
<code><br />
root pts/0 00:01 Jun 9 08:06:24 192.168.2.2<br />
</code><br />
<br />
In this particular case, the address shown is 192.168.2.2, so the first command listed above would be <code>route add default gw 192.168.2.2</code>.<br />
<br />
== Custom Address ==<br />
The watch defaults to the address 192.168.2.15, but this can be changed. If, for example, you want to change the address to 10.0.0.2, the recommended way to change it is to do this:<br />
<br />
# temporarily changing the USB mode on the watch to "ADB mode"<br />
# issue the command <pre>adb dbus-send --system --type=method_call --print-reply --dest=com.meego.usb_moded /com/meego/usb_moded com.meego.usb_moded.net_config string:'ip' string:'10.0.0.2'</pre><br />
# change USB mode to "SSH mode"<br />
<br />
Note that if you have more than one ADB device attached to your computer, you might have to give it the transport ID in step 2. This change persists across boots.<br />
<br />
An alternative approach for developers building their own image using bitbake, is to edit the file https://github.com/AsteroidOS/meta-asteroid/blob/master/recipes-nemomobile/usb-moded/usb-moded/usb-moded/usb-moded.ini. And add:<br />
<br />
<pre><br />
[network]<br />
ip=10.0.0.2<br />
</pre><br />
<br />
= Paranoid Kernels=<br />
On some watch models (e.g., <code>lenok</code>), the kernel shipped with AsteroidOS is compiled with the Android-specific <code>CONFIG_ANDROID_PARANOID_NETWORK</code> kernel option enabled. That option enforces non-standard restrictions on networking, based on hardcoded group IDs (GIDs):<br />
*GID 3003 is the <code>inet</code> group, allowing to create <code>AF_INET</code> and <code>AF_INET6</code> sockets,<br />
* GID 3004 is the <code>net_raw</code> group, allowing to create raw INET sockets.<br />
<br />
Only <code>root</code> and members of the groups with those magic GIDs are allowed to perform the described actions. In particular, by default, the <code>ceres</code> user is '''not'''.<br />
<br />
Therefore, in order to be able to access the network as <code>ceres</code> (e.g., for <code>asteroid-weatherfetch</code> to work), SSH into your watch as <code>root</code> (or use <code>adb shell</code>) and run the following 2 commands:<br />
<pre><br />
groupadd -g 3003 -U root,ceres inet<br />
groupadd -g 3004 -U root,ceres net_raw<br />
</pre><br />
These create the two magic groups with the same name and GID as on Android and add both <code>root</code> and <code>ceres</code> to them. Then reboot your watch, because only newly started sessions will pick up the new group memberships.</div>Berosethttps://wiki.asteroidos.org/index.php?title=Building_AsteroidOS&diff=1025Building AsteroidOS2026-07-20T14:24:06Z<p>Beroset: /* Build with containers */ add instructions on customizing the toolchain container</p>
<hr />
<div>[[Category:Developers]]<br />
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]:<br />
<br />
<br />
[https://asteroidos.org/asteroid.mp4 Video showing the build process]<br />
<br />
= General information =<br />
<br />
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.<br />
<br />
Another advantage of Docker specifically is that it ''should'' also work on Windows and OS X. (However, this has not been tested yet!)<br />
<br />
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.<br />
<br />
= Clone the repository =<br />
<br />
Clone the main repository using the following command:<br />
<br />
<pre><br />
git clone https://github.com/AsteroidOS/asteroid.git<br />
</pre><br />
<br />
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.)<br />
<br />
<pre><br />
git config --global user.email "you@example.com"<br />
git config --global user.name "Your Name"<br />
</pre><br />
<br />
Before you continue to ''Build without containers'' or ''Build with containers'', make sure you're in the asteroid directory:<br />
<br />
<pre><br />
cd asteroid/<br />
</pre><br />
<br />
= Build without containers =<br />
<br />
== Downloading ==<br />
<br />
Install the prerequisites:<br />
<br />
<br />
{| class="wikitable"<br />
|+ Distribution prerequisite installation<br />
|-<br />
! Distro !! Command<br />
|-<br />
| Ubuntu || <code>apt-get install git build-essential chrpath cpio diffstat gawk liblz4-tool python3 shared-mime-info texinfo wget zstd </code><br />
|-<br />
| Fedora || <code>dnf install chrpath diffstat g++ lz4 perl perl-bignum python3-pip rpcgen socat texinfo patch</code><br />
|-<br />
| Arch || <code>pacman -Sy base-devel chrpath cpio diffstat gawk inetutils lz4 python3 rpcsvc-proto shared-mime-info texinfo wget zstd</code><br />
|-<br />
| 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].<br />
|}<br />
<br />
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].)<br />
<br />
<pre><br />
source ./prepare-build.sh dory # Be careful that this script must be sourced and not only ran<br />
</pre><br />
<br />
If the environment has been correctly setup, you should now be in the <code>build</code> subdirectory.<br />
<br />
== Building ==<br />
<br />
Once the environment is prepared, you can simply trigger a build with the following command:<br />
<br />
<pre><br />
bitbake asteroid-image<br />
</pre><br />
''Notes:''<br />
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.<br />
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.<br />
<br />
If this step was successful, you can proceed to the [[#Installing|Installing]] section below.<br />
<br />
== Updating the Sources ==<br />
<br />
You can update the AsteroidOS sources with the following command:<br />
<br />
<pre><br />
source ./prepare-build.sh update<br />
</pre><br />
<br />
<br />
= Build with containers =<br />
<br />
These instructions have been tested on Ubuntu 19.04 (with Docker) and Fedora 41 (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.<br />
<br />
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.<br />
<br />
== Setup ==<br />
<br />
Remove the Docker container called <code>asteroidos-toolchain</code> if it already exists:<br />
<br />
<pre><br />
sudo docker rm -f asteroidos-toolchain<br />
</pre><br />
or<br />
<pre><br />
podman rm -f asteroidos-toolchain<br />
</pre><br />
<br />
Build a container image called <code>asteroidos-toolchain</code> from the given Dockerfile:<br />
<br />
<pre><br />
sudo docker build --tag asteroidos-toolchain .<br />
</pre><br />
or<br />
<pre><br />
podman build --tag asteroidos-toolchain .<br />
</pre><br />
<br />
== Building the software ==<br />
<br />
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.<br />
<br />
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].<br />
<br />
Assuming that you have carefully followed the instructions so far and are in the <code>asteroid</code> directory, you can now build the software.<br />
<br />
'''Run this as a non root user''':<br />
<br />
<pre><br />
sudo docker run \<br />
--rm \<br />
-it \<br />
-v /etc/passwd:/etc/passwd:ro \<br />
-u "$(id -u):$(id -g)" \<br />
-v "$HOME/.gitconfig:/$HOME/.gitconfig:ro" \<br />
-v "$(pwd):/asteroid" asteroidos-toolchain \<br />
bash -c "source ./prepare-build.sh dory && bitbake asteroid-image"<br />
</pre><br />
or<br />
<pre><br />
podman run \<br />
--rm \<br />
-it \<br />
-v "$(pwd)":/asteroid:z \<br />
--userns keep-id asteroidos-toolchain \<br />
bash -c "source ./prepare-build.sh dory && bitbake asteroid-image"<br />
</pre><br />
<br />
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.<br />
<br />
Here is a detailed explanation of the Docker command above:<br />
<br />
*<code>sudo docker run</code> Runs a container image<br />
*<code>--rm</code> Cleans up after the command is run by removing temporary container storage<br />
*<code>-it</code> Attaches the terminal to the container so that we can see the output. Otherwise it would run blindly in the background.<br />
*<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.<br />
*<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.)<br />
*<code>/etc/passwd</code> Contains the user names and their ids.<br />
*<code>"$HOME/.gitconfig:/$HOME/.gitconfig"</code> Share your user's git config with the container.<br />
*<code>-v "$(pwd):/asteroid"</code> Mount the current directory (which is your asteroid git repo clone) into the container.<br />
*<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.<br />
<br />
Here is a detailed explanation of the podman version of the command above:<br />
<br />
*<code>podman run</code> Runs a container image<br />
*<code>--rm</code> Cleans up after the command is run by removing temporary container storage<br />
*<code>-it</code> Attaches the terminal to the container so that we can see the output. Otherwise it would run blindly in the background.<br />
*<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 that this container to allow multiple containers to share this mount. If <code>:Z</code> is used instead, it tells SELinux, if it's running, that the container has ''exclusive access'' to this mount. Either can be used, but using the exclusive access flag causes the need to re-apply security labels to all files which can take significant time when the container starts.<br />
*<code>--userns keep-id</code> Run as the current user inside the container<br />
*<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.<br />
<br />
If this step was successful, you can proceed to [[#Installing|Installing]] below.<br />
<br />
== Customizing the toolchain container ==<br />
It can be convenient to add <code>tmux</code> (to support commands like <code>bitbake -c devshell asteroid-hello</code> and <code>vim</code> (or the editor of your choice). You may have other tools that you would like to install. You can gain root access to a running and install packages to customize the environment to your liking. First, run the <code>podman run</code> ''without'' the <code>--rm</code> argument. <br />
<br />
Then access the running container as root:<br />
<br />
<pre><br />
podman exec -itu root asteroid bash<br />
</pre><br />
<br />
Then within the image, you can make any needed changes. When finished, exit the container and run:<br />
<br />
<pre><br />
podman commit asteroid custom-asteroidos:1.0<br />
</pre><br />
<br />
It also may be convenient to configure git with email and name. Obviously, use your own email and name:<br />
<br />
<pre><br />
git config --global user.email "you@example.com"<br />
git config --global user.name "Your Name"<br />
</pre><br />
<br />
= Installing =<br />
<br />
After a while, whether you build with or without containers, the generated image should be available in <code>build/tmp/deploy/images/dory/</code> (for <code>dory</code> -- for other watches, the image files are in the corresponding code word directory.)<br />
<br />
Install AsteroidOS using your usual device's instructions, which you can find linked from the [https://asteroidos.org/watches/ Watches page].</div>Berosethttps://wiki.asteroidos.org/index.php?title=Building_AsteroidOS&diff=1017Building AsteroidOS2026-07-13T12:41:08Z<p>Beroset: /* Building the software */ corrected previous edit</p>
<hr />
<div>[[Category:Developers]]<br />
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]:<br />
<br />
<br />
[https://asteroidos.org/asteroid.mp4 Video showing the build process]<br />
<br />
= General information =<br />
<br />
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.<br />
<br />
Another advantage of Docker specifically is that it ''should'' also work on Windows and OS X. (However, this has not been tested yet!)<br />
<br />
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.<br />
<br />
= Clone the repository =<br />
<br />
Clone the main repository using the following command:<br />
<br />
<pre><br />
git clone https://github.com/AsteroidOS/asteroid.git<br />
</pre><br />
<br />
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.)<br />
<br />
<pre><br />
git config --global user.email "you@example.com"<br />
git config --global user.name "Your Name"<br />
</pre><br />
<br />
Before you continue to ''Build without containers'' or ''Build with containers'', make sure you're in the asteroid directory:<br />
<br />
<pre><br />
cd asteroid/<br />
</pre><br />
<br />
= Build without containers =<br />
<br />
== Downloading ==<br />
<br />
Install the prerequisites:<br />
<br />
<br />
{| class="wikitable"<br />
|+ Distribution prerequisite installation<br />
|-<br />
! Distro !! Command<br />
|-<br />
| Ubuntu || <code>apt-get install git build-essential chrpath cpio diffstat gawk liblz4-tool python3 shared-mime-info texinfo wget zstd </code><br />
|-<br />
| Fedora || <code>dnf install chrpath diffstat g++ lz4 perl perl-bignum python3-pip rpcgen socat texinfo patch</code><br />
|-<br />
| Arch || <code>pacman -Sy base-devel chrpath cpio diffstat gawk inetutils lz4 python3 rpcsvc-proto shared-mime-info texinfo wget zstd</code><br />
|-<br />
| 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].<br />
|}<br />
<br />
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].)<br />
<br />
<pre><br />
source ./prepare-build.sh dory # Be careful that this script must be sourced and not only ran<br />
</pre><br />
<br />
If the environment has been correctly setup, you should now be in the <code>build</code> subdirectory.<br />
<br />
== Building ==<br />
<br />
Once the environment is prepared, you can simply trigger a build with the following command:<br />
<br />
<pre><br />
bitbake asteroid-image<br />
</pre><br />
''Notes:''<br />
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.<br />
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.<br />
<br />
If this step was successful, you can proceed to the [[#Installing|Installing]] section below.<br />
<br />
== Updating the Sources ==<br />
<br />
You can update the AsteroidOS sources with the following command:<br />
<br />
<pre><br />
source ./prepare-build.sh update<br />
</pre><br />
<br />
<br />
= Build with containers =<br />
<br />
These instructions have been tested on Ubuntu 19.04 (with Docker) and Fedora 41 (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.<br />
<br />
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.<br />
<br />
<br />
== Setup ==<br />
<br />
Remove the Docker container called <code>asteroidos-toolchain</code> if it already exists:<br />
<br />
<pre><br />
sudo docker rm -f asteroidos-toolchain<br />
</pre><br />
or<br />
<pre><br />
podman rm -f asteroidos-toolchain<br />
</pre><br />
<br />
Build a container image called <code>asteroidos-toolchain</code> from the given Dockerfile:<br />
<br />
<pre><br />
sudo docker build --tag asteroidos-toolchain .<br />
</pre><br />
or<br />
<pre><br />
podman build --tag asteroidos-toolchain .<br />
</pre><br />
<br />
== Building the software ==<br />
<br />
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.<br />
<br />
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].<br />
<br />
<br />
<br />
Assuming that you have carefully followed the instructions so far and are in the <code>asteroid</code> directory, you can now build the software.<br />
<br />
'''Run this as a non root user''':<br />
<br />
<pre><br />
sudo docker run \<br />
--rm \<br />
-it \<br />
-v /etc/passwd:/etc/passwd:ro \<br />
-u "$(id -u):$(id -g)" \<br />
-v "$HOME/.gitconfig:/$HOME/.gitconfig:ro" \<br />
-v "$(pwd):/asteroid" asteroidos-toolchain \<br />
bash -c "source ./prepare-build.sh dory && bitbake asteroid-image"<br />
</pre><br />
or<br />
<pre><br />
podman run \<br />
--rm \<br />
-it \<br />
-v "$(pwd)":/asteroid:z \<br />
--userns keep-id asteroidos-toolchain \<br />
bash -c "source ./prepare-build.sh dory && bitbake asteroid-image"<br />
</pre><br />
<br />
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.<br />
<br />
Here is a detailed explanation of the Docker command above:<br />
<br />
*<code>sudo docker run</code> Runs a container image<br />
*<code>--rm</code> Cleans up after the command is run by removing temporary container storage<br />
*<code>-it</code> Attaches the terminal to the container so that we can see the output. Otherwise it would run blindly in the background.<br />
*<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.<br />
*<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.)<br />
*<code>/etc/passwd</code> Contains the user names and their ids.<br />
*<code>"$HOME/.gitconfig:/$HOME/.gitconfig"</code> Share your user's git config with the container.<br />
*<code>-v "$(pwd):/asteroid"</code> Mount the current directory (which is your asteroid git repo clone) into the container.<br />
*<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.<br />
<br />
Here is a detailed explanation of the podman version of the command above:<br />
<br />
*<code>podman run</code> Runs a container image<br />
*<code>--rm</code> Cleans up after the command is run by removing temporary container storage<br />
*<code>-it</code> Attaches the terminal to the container so that we can see the output. Otherwise it would run blindly in the background.<br />
*<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 that this container to allow multiple containers to share this mount. If <code>:Z</code> is used instead, it tells SELinux, if it's running, that the container has ''exclusive access'' to this mount. Either can be used, but using the exclusive access flag causes the need to re-apply security labels to all files which can take significant time when the container starts.<br />
*<code>--userns keep-id</code> Run as the current user inside the container<br />
*<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.<br />
<br />
If this step was successful, you can proceed to [[#Installing|Installing]] below.<br />
<br />
= Installing =<br />
<br />
After a while, whether you build with or without containers, the generated image should be available in <code>build/tmp/deploy/images/dory/</code> (for <code>dory</code> -- for other watches, the image files are in the corresponding code word directory.)<br />
<br />
Install AsteroidOS using your usual device's instructions, which you can find linked from the [https://asteroidos.org/watches/ Watches page].</div>Berosethttps://wiki.asteroidos.org/index.php?title=Building_AsteroidOS&diff=1016Building AsteroidOS2026-07-13T12:27:59Z<p>Beroset: /* Building the software */ Add a note about :z versus :Z for volume mount</p>
<hr />
<div>[[Category:Developers]]<br />
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]:<br />
<br />
<br />
[https://asteroidos.org/asteroid.mp4 Video showing the build process]<br />
<br />
= General information =<br />
<br />
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.<br />
<br />
Another advantage of Docker specifically is that it ''should'' also work on Windows and OS X. (However, this has not been tested yet!)<br />
<br />
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.<br />
<br />
= Clone the repository =<br />
<br />
Clone the main repository using the following command:<br />
<br />
<pre><br />
git clone https://github.com/AsteroidOS/asteroid.git<br />
</pre><br />
<br />
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.)<br />
<br />
<pre><br />
git config --global user.email "you@example.com"<br />
git config --global user.name "Your Name"<br />
</pre><br />
<br />
Before you continue to ''Build without containers'' or ''Build with containers'', make sure you're in the asteroid directory:<br />
<br />
<pre><br />
cd asteroid/<br />
</pre><br />
<br />
= Build without containers =<br />
<br />
== Downloading ==<br />
<br />
Install the prerequisites:<br />
<br />
<br />
{| class="wikitable"<br />
|+ Distribution prerequisite installation<br />
|-<br />
! Distro !! Command<br />
|-<br />
| Ubuntu || <code>apt-get install git build-essential chrpath cpio diffstat gawk liblz4-tool python3 shared-mime-info texinfo wget zstd </code><br />
|-<br />
| Fedora || <code>dnf install chrpath diffstat g++ lz4 perl perl-bignum python3-pip rpcgen socat texinfo patch</code><br />
|-<br />
| Arch || <code>pacman -Sy base-devel chrpath cpio diffstat gawk inetutils lz4 python3 rpcsvc-proto shared-mime-info texinfo wget zstd</code><br />
|-<br />
| 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].<br />
|}<br />
<br />
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].)<br />
<br />
<pre><br />
source ./prepare-build.sh dory # Be careful that this script must be sourced and not only ran<br />
</pre><br />
<br />
If the environment has been correctly setup, you should now be in the <code>build</code> subdirectory.<br />
<br />
== Building ==<br />
<br />
Once the environment is prepared, you can simply trigger a build with the following command:<br />
<br />
<pre><br />
bitbake asteroid-image<br />
</pre><br />
''Notes:''<br />
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.<br />
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.<br />
<br />
If this step was successful, you can proceed to the [[#Installing|Installing]] section below.<br />
<br />
== Updating the Sources ==<br />
<br />
You can update the AsteroidOS sources with the following command:<br />
<br />
<pre><br />
source ./prepare-build.sh update<br />
</pre><br />
<br />
<br />
= Build with containers =<br />
<br />
These instructions have been tested on Ubuntu 19.04 (with Docker) and Fedora 41 (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.<br />
<br />
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.<br />
<br />
<br />
== Setup ==<br />
<br />
Remove the Docker container called <code>asteroidos-toolchain</code> if it already exists:<br />
<br />
<pre><br />
sudo docker rm -f asteroidos-toolchain<br />
</pre><br />
or<br />
<pre><br />
podman rm -f asteroidos-toolchain<br />
</pre><br />
<br />
Build a container image called <code>asteroidos-toolchain</code> from the given Dockerfile:<br />
<br />
<pre><br />
sudo docker build --tag asteroidos-toolchain .<br />
</pre><br />
or<br />
<pre><br />
podman build --tag asteroidos-toolchain .<br />
</pre><br />
<br />
== Building the software ==<br />
<br />
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.<br />
<br />
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].<br />
<br />
<br />
<br />
Assuming that you have carefully followed the instructions so far and are in the <code>asteroid</code> directory, you can now build the software.<br />
<br />
'''Run this as a non root user''':<br />
<br />
<pre><br />
sudo docker run \<br />
--rm \<br />
-it \<br />
-v /etc/passwd:/etc/passwd:ro \<br />
-u "$(id -u):$(id -g)" \<br />
-v "$HOME/.gitconfig:/$HOME/.gitconfig:ro" \<br />
-v "$(pwd):/asteroid" asteroidos-toolchain \<br />
bash -c "source ./prepare-build.sh dory && bitbake asteroid-image"<br />
</pre><br />
or<br />
<pre><br />
podman run \<br />
--rm \<br />
-it \<br />
-v "$(pwd)":/asteroid:Z \<br />
--userns keep-id asteroidos-toolchain \<br />
bash -c "source ./prepare-build.sh dory && bitbake asteroid-image"<br />
</pre><br />
<br />
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.<br />
<br />
Here is a detailed explanation of the Docker command above:<br />
<br />
*<code>sudo docker run</code> Runs a container image<br />
*<code>--rm</code> Cleans up after the command is run by removing temporary container storage<br />
*<code>-it</code> Attaches the terminal to the container so that we can see the output. Otherwise it would run blindly in the background.<br />
*<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.<br />
*<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.)<br />
*<code>/etc/passwd</code> Contains the user names and their ids.<br />
*<code>"$HOME/.gitconfig:/$HOME/.gitconfig"</code> Share your user's git config with the container.<br />
*<code>-v "$(pwd):/asteroid"</code> Mount the current directory (which is your asteroid git repo clone) into the container.<br />
*<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.<br />
<br />
Here is a detailed explanation of the podman version of the command above:<br />
<br />
*<code>podman run</code> Runs a container image<br />
*<code>--rm</code> Cleans up after the command is run by removing temporary container storage<br />
*<code>-it</code> Attaches the terminal to the container so that we can see the output. Otherwise it would run blindly in the background.<br />
*<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 that this container has ''exclusive access'' to this mount. If <code>:z</code> is used instead, it tells SELinux, if it's running, to allow multiple containers to share this mount. Either can be used, but the exclusive access flag avoids the need to re-apply security labels to all files which can take significant time when the container starts.<br />
*<code>--userns keep-id</code> Run as the current user inside the container<br />
*<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.<br />
<br />
If this step was successful, you can proceed to [[#Installing|Installing]] below.<br />
<br />
= Installing =<br />
<br />
After a while, whether you build with or without containers, the generated image should be available in <code>build/tmp/deploy/images/dory/</code> (for <code>dory</code> -- for other watches, the image files are in the corresponding code word directory.)<br />
<br />
Install AsteroidOS using your usual device's instructions, which you can find linked from the [https://asteroidos.org/watches/ Watches page].</div>Berosethttps://wiki.asteroidos.org/index.php?title=Beluga&diff=1015Beluga2026-07-12T11:37:08Z<p>Beroset: added additional recovery method under issues</p>
<hr />
<div>{{Watches<br />
|Name=beluga<br />
|Model=OPPO Watch<br />
|ReleaseDate=2020-07-31<br />
|Picture=beluga.png<br />
|Status=supported<br />
|Stars=4.9<br />
|Chipset=msm8909w<br />
|KernelVersion=4.9<br />
|AndroidVersion=pie<br />
|StatusDisplay=good<br />
|StatusTouch=good<br />
|StatusBluetooth=good<br />
|StatusHaptics=good<br />
|StatusTiltToWake=good<br />
|StatusLightSensor=good<br />
|StatusAlwaysOnDisplay=good<br />
|StatusDualDisplay=missing<br />
|StatusMicrophone=good<br />
|StatusSpeaker=good<br />
|StatusCompass=good<br />
|StatusSteps=bad<br />
|StatusHeartRate=good<br />
|StatusUSB=partial<br />
|StatusWLAN=good<br />
|StatusGPS=good<br />
|StatusNFC=bad<br />
|StatusCellular=bad<br />
|StatusCamera=missing<br />
|StatusCrown=missing<br />
|StatusHands=missing<br />
}}<br />
Beluga (OPPO Watch) is a large rectangular watch with a lot of features. <br />
----<br />
Warning: The OPPO Watch Free is not supported! See the list on the [[porting Status]] page to find out if your model is supported.<br />
<br />
= Description =<br />
Beluga is a large rectangular watch with a (side) curved OLED display, fairly large amount of sensors and a good vibration motor.<br />
The casing of the watch is relatively thin, making it easier to tuck under the sleeves.<br />
The watch uses a proprietary watchband mechanism for which one can buy adapters so standard 22mm straps can be attached.<br />
<br />
== Issues ==<br />
NFC support causes graphical glitches, so it has been disabled for now.<br />
<br />
It has also been reported by some that switching back to the original OS from backups via the usual method doesn't always seem to work, so an alternative recipe is to extract the parts from the backup (as with [https://github.com/beroset/asteroid-hosttools#watch-image watch-image]) and then, with the watch in fastboot mode:<br />
<br />
<pre><br />
fastboot flash system system.img <br />
fastboot flash vendor vendor.img<br />
fastboot flash userdata userdata.img<br />
fastboot flash recovery recovery.img<br />
fastboot flash cache cache.img<br />
fastboot flash boot boot.img<br />
</pre><br />
<br />
<br />
== Repair and customisation ==<br />
The back of the watch is held on by glue, which means that disassembly will impact water resistance and is somewhat frustrating.<br />
<br />
== Sensorlogd ==<br />
<br />
=== Stepcounter ===<br />
The watch needs to be powered on when 0:00 happens. Else it does not reset the previous day.<br />
<br />
= Miscellaneous hardware docs =<br />
== Keys ==<br />
There are two hardware buttons located on the right of the watch.<br />
<br />
The bottom button is used to power on or hard reset the watch.<br />
The top button can be used to wake/sleep the watch from AsteroidOS. This button is also used to navigate through the boot menu. <br />
Beluga is unconventional because the power button used in AsteroidOS is not the one used to power on the watch.<br />
<br />
== Manually getting to fastboot ==<br />
When the watch is unlocked you can easily enter fastboot by pressing the upper right hardware button during the bootup of the watch. This will make the watch enter a boot menu. Using the top button to cycle through the list. Once "Fastboot" is selected press the bottom button to boot to fastboot.</div>Berosethttps://wiki.asteroidos.org/index.php?title=Fresh/Wise/Lucky7&diff=1014Fresh/Wise/Lucky72026-07-10T20:52:59Z<p>Beroset: eliminate blank lines above description</p>
<hr />
<div>{{Watches<br />
|Name=fresh<br />
|Model=Samsung Galaxy Watch 4<br />
|ReleaseDate=2021-08-27<br />
|Picture=fresh.png<br />
|Status=port in progress<br />
|Stars=0<br />
|Chipset=exynos5515<br />
|KernelVersion=7.1<br />
|AndroidVersion=redvelvetcake<br />
|StatusDisplay=bad<br />
|StatusTouch=bad<br />
|StatusBluetooth=bad<br />
|StatusHaptics=bad<br />
|StatusTiltToWake=bad<br />
|StatusLightSensor=bad<br />
|StatusAlwaysOnDisplay=bad<br />
|StatusDualDisplay=missing<br />
|StatusMicrophone=bad<br />
|StatusSpeaker=bad<br />
|StatusCompass=bad<br />
|StatusSteps=bad<br />
|StatusHeartRate=bad<br />
|StatusUSB=bad<br />
|StatusWLAN=bad<br />
|StatusGPS=bad<br />
|StatusNFC=bad<br />
|StatusCellular=bad<br />
|StatusCamera=missing<br />
|StatusCrown=bad<br />
|StatusHands=missing<br />
}}{{Watches<br />
|Name=wise<br />
|Model=Samsung Galaxy Watch 4 Classic<br />
|ReleaseDate=2021-08-27<br />
|Picture=wise.png<br />
|Status=port in progress<br />
|Stars=0<br />
|Chipset=exynos5515<br />
|KernelVersion=7.1<br />
|AndroidVersion=redvelvetcake<br />
|StatusDisplay=bad<br />
|StatusTouch=bad<br />
|StatusBluetooth=bad<br />
|StatusHaptics=bad<br />
|StatusTiltToWake=bad<br />
|StatusLightSensor=bad<br />
|StatusAlwaysOnDisplay=bad<br />
|StatusDualDisplay=missing<br />
|StatusMicrophone=bad<br />
|StatusSpeaker=bad<br />
|StatusCompass=bad<br />
|StatusSteps=bad<br />
|StatusHeartRate=bad<br />
|StatusUSB=bad<br />
|StatusWLAN=bad<br />
|StatusGPS=bad<br />
|StatusNFC=bad<br />
|StatusCellular=bad<br />
|StatusCamera=missing<br />
|StatusCrown=bad<br />
|StatusHands=missing<br />
}}{{Watches<br />
|Name=lucky7<br />
|Model=Samsung Galaxy Watch FE<br />
|ReleaseDate=2024-06-13<br />
|Picture=lucky7.png<br />
|Status=port in progress<br />
|Stars=0<br />
|Chipset=exynos5515<br />
|KernelVersion=7.1<br />
|AndroidVersion=tiramisu<br />
|StatusDisplay=partial<br />
|StatusTouch=bad<br />
|StatusBluetooth=bad<br />
|StatusHaptics=bad<br />
|StatusTiltToWake=bad<br />
|StatusLightSensor=bad<br />
|StatusAlwaysOnDisplay=bad<br />
|StatusDualDisplay=missing<br />
|StatusMicrophone=bad<br />
|StatusSpeaker=bad<br />
|StatusCompass=bad<br />
|StatusSteps=bad<br />
|StatusHeartRate=bad<br />
|StatusUSB=bad<br />
|StatusWLAN=bad<br />
|StatusGPS=bad<br />
|StatusNFC=bad<br />
|StatusCellular=bad<br />
|StatusCamera=missing<br />
|StatusCrown=bad<br />
|StatusHands=missing<br />
}}<br />
[[Category:Watches]]<br />
==Description==<br />
Fresh (Samsung Galaxy Watch 4) and Wise (Samsung Galaxy Watch 4 Classic) are round smartwatches developed by Samsung. They released with Android 11, and use the Exynos W920 (Exynos 5515) Cortex-A55 based AArch64 SoC.<br />
<br />
Lucky7 (Samsung Galaxy Watch FE) is a derivative of Fresh, so their hardware is almost identical. It released with Android 13.<br />
<br />
Wise takes on the "classic" chassis design of the Samsung Gear S2, with a larger chassis and rotating bezel for navigation, whereas Fresh and Lucky7 have a smaller, more minimalistic design, with the bezel being touch-activated to fulfill the same purpose as the rotating bezel on Wise.<br />
<br />
Fresh, Wise, and Lucky7 all have two buttons on the side.<br />
<br />
There are ten different variants of this watch:<br />
{| class="wikitable"<br />
|+<br />
!Codename<br />
!Model Number<br />
!Model Name<br />
!Display Size<br />
|-<br />
|freshbs<br />
|SM-R860<br />
|Samsung Galaxy Watch 4 (WiFi)<br />
|40mm<br />
|-<br />
|freshus<br />
|SM-R865<br />
|Samsung Galaxy Watch 4 (LTE)<br />
|40mm<br />
|-<br />
|freshbl<br />
|SM-R870<br />
|Samsung Galaxy Watch 4 (WiFi)<br />
|44mm<br />
|-<br />
|freshul<br />
|SM-R875<br />
|Samsung Galaxy Watch 4 (LTE)<br />
|44mm<br />
|-<br />
|wisebs<br />
|SM-R880<br />
|Samsung Galaxy Watch 4 Classic (WiFi)<br />
|42mm<br />
|-<br />
|wiseus<br />
|SM-R885<br />
|Samsung Galaxy Watch 4 Classic (LTE)<br />
|42mm<br />
|-<br />
|wisebl<br />
|SM-R890<br />
|Samsung Galaxy Watch 4 Classic (WiFi)<br />
|46mm<br />
|-<br />
|wiseul<br />
|SM-R895<br />
|Samsung Galaxy Watch 4 Classic (LTE)<br />
|46mm<br />
|-<br />
|lucky7bs<br />
|SM-R861<br />
|Samsung Galaxy Watch FE (WiFi)<br />
|40mm<br />
|-<br />
|lucky7us<br />
|SM-R866<br />
|Samsung Galaxy Watch FE (LTE)<br />
|40mm<br />
<br />
|}<br />
<br />
See the GSMArena pages for [https://www.gsmarena.com/samsung_galaxy_watch4-11045.php Fresh], [https://www.gsmarena.com/samsung_galaxy_watch4_classic-11046.php Wise], and [https://www.gsmarena.com/samsung_galaxy_watch_fe-13112.php Lucky7] for more hardware details.<br />
<br />
==Port Status==<br />
<br />
===Fresh/Wise===<br />
No porting work has yet been done.<br />
<br />
===Lucky7===<br />
[[File:Lucky7-first-ui.jpg|alt=Lucky7 displaying the first-start UI|none|thumb|Lucky7 displaying the first-start UI]]<br />
<br />
<br />
A port using a [https://github.com/Aiden-Isik/linux/tree/lucky7-mainline close-to-mainline Linux kernel] is [https://github.com/Aiden-Isik/asteroid/tree/lucky7-mainline underway]. Currently, the watch can boot all the way up and display the launcher UI using software rendering, but nothing else works.<br />
<br />
==Bootloader Unlocking==<br />
'''WARNING: Unlocking the bootloader will trip Knox efuses! Connections inside the SoC will be irreversibly severed, you will permanently lose the ability to use features such as Samsung Pay, and you will get a warning on each startup stating that the device's software "may be corrupt" (this can be ignored).'''<br />
<br />
'''NOTE: While Samsung disabled bootloader unlocking on their phones with the OneUI 8 (Android 16) update, they did not do so for their watches (as of 26/02/2026). All firmware versions of this watch can be unlocked.'''<br />
<br />
The bootloader of the Galaxy Watch FE can be unlocked using the following steps, with the buttons facing to the right:<br />
<br />
*Open settings.<br />
*Go to "About watch" -> "Software information"<br />
*Tap the software version several times until you are informed that developer mode has been enabled.<br />
* Locate the "OEM unlocking" option in the developer options menu, and switch it on.<br />
*Hold both buttons on the side of the watch until the Samsung logo appears with the "rebooting..." text below it.<br />
*Quickly press the upper button three times to open the bootloader menu.<br />
*Use the upper button on the side of the watch to navigate to the "Bootloader unlock" option and select it. A short click moves to the next option and a long hold selects an option.<br />
* Press the upper button to unlock the bootloader.<br />
*After rebooting, if you end up in the recovery, follow the steps presented to wipe the device's data.<br />
* Your bootloader is now unlocked.<br />
<br />
== Repair==<br />
These watches are relatively easy to disassemble to repair. There are four Y00 screws on the back, then everything else just pulls apart.<br />
<br />
They use a rubber gasket for water resistance, so as long as it isn't damaged during disassembly it should be able to be reused, and water resistance not compromised.<br />
<br />
See the [https://www.ifixit.com/Device/Samsung_Galaxy_Watch_4 Fresh] (Lucky7) and [https://www.ifixit.com/Device/Samsung_Galaxy_Watch_4_Classic Wise] iFixit pages for detailed instructions for various repairs.<br />
<br />
==USB==<br />
There are no USB connections exposed anywhere on the exterior of this watch. There are however internal USB pads near the top edge of the watch, which can have a USB cable soldered onto them.<br />
<br />
The pinout, with the top edge facing towards you, is as follows from left to right:<br />
<br />
*Vcc<br />
*ID<br />
*D+<br />
*D-<br />
*GND<br />
<br />
To connect to the watch over USB, you must connect the ID pin to GND through approximately 150kOhms of resistance (it doesn't have to be exact).<br />
<br />
==UART==<br />
The internal USB pads can also be used for receiving 3V UART signals. <br />
<br />
The pinout, with the top edge facing towards you, is as follows from left to right:<br />
<br />
* Not connected<br />
*ID<br />
*TX<br />
*RX<br />
*GND<br />
<br />
To connect to the watch over UART, you must connect the ID pin to GND through 619kOhms of resistance. You should also either add a connector which can be unplugged between the watch and your UART adapter, or a switch on the ID line. This is required as in order for the watch to transmit serial data the ID pin must be disconnected then reconnected during the boot process.<br />
<br />
The bootloader does not transmit any data over UART.<br />
<br />
To get the kernel to transmit its logs over UART, add 'console=ttySAC0,115200n8 loglevel=7' to CONFIG_CMDLINE in the defconfig and recompile.<br />
<br />
RX Seems to be tied low, so the watch is unable to receive serial data.<br />
<br />
==Booting==<br />
====Boot Image Format (Lucky7) ====<br />
The boot image format used by the S-Boot bootloader on the Galaxy Watch FE is [https://source.android.com/docs/core/architecture/bootloader/boot-image-header#header-v4 Android boot version 4], with INIT_BOOT and DTBO. The partitions involved in booting Linux are therefore BOOT, INIT_BOOT, VENDOR_BOOT, and DTBO, along with VBMETA for signature enforcement.<br />
<br />
====Device Tree Format (Lucky7)====<br />
The device tree, used to specify to Linux which hardware the system has and where, in the absence of ACPI, is split into two. The main blob (mostly SoC-specific) part of the device tree is part of the VENDOR_BOOT partition, whereas the overlay blob (mostly board-specific) lives in its own partition, DTBO. The overlay is combined with the main blob by the bootloader to create one unified device tree for Linux to use.<br />
<br />
Both of these conform to the standard [https://devicetree-specification.readthedocs.io/en/stable/flattened-format.html device tree blob format] produced by DTC and the Linux build system, with an extra Android-specific header created by [https://android.googlesource.com/platform/system/libufdt/ libufdt] prepended to the beginning of the file.<br />
<br />
The main device tree blob in VENDOR_BOOT is a standard Android device tree blob as specified as above, except that the 'CUSTOM1' field is set to 0xFF (255). It can be generated using mkdtboimg.py from libufdt with the following command:<syntaxhighlight lang="sh"><br />
python3 mkdtboimg.py create --custom1=255 <output> <input><br />
</syntaxhighlight>The overlay device tree blob in DTBO is also a standard Android device tree blob, except that the 'CUSTOM1' field is set to 0x20 (32). It can be generated using mkdtboimg.py with the following command:<syntaxhighlight lang="sh"><br />
python3 mkdtboimg.py create --custom1=32 <output> <input><br />
</syntaxhighlight>The meaning of the values in the 'CUSTOM1' fields is not currently known. They are possibly just magic numbers to identify the different blobs.<br />
<br />
====Minimum Acceptable Device Tree (Lucky7)====<br />
The bootloader of this watch requires certain device tree nodes to be present, due to it applying its own overlay blob on top of the two supplied by the VENDOR_BOOT and DTBO partitions. If the nodes the bootloader wants to overlay onto are not present, it will refuse to boot. The most minimal device tree source which fulfills this requirement is as follows (note that it is useless for anything other than satisfying the bootloader):<syntaxhighlight lang="dts" line="1"><br />
/dts-v1/;<br />
<br />
/ {<br />
#address-cells = <0x02>;<br />
#size-cells = <0x01>;<br />
<br />
dpm: dpm {<br />
};<br />
<br />
itmon: itmon {<br />
};<br />
<br />
memlogger_policy: samsung,memlogger {<br />
};<br />
<br />
reserved_memory: reserved-memory {<br />
#address-cells = <0x02>;<br />
#size-cells = <0x01>;<br />
ranges;<br />
<br />
dss_rmem: debug_snapshot {<br />
#address-cells = <0x02>;<br />
#size-cells = <0x01>;<br />
<br />
log_platform: log_platform {<br />
};<br />
<br />
log_arrdumpreset: log_arrdumpreset {<br />
};<br />
<br />
log_arrdumppanic: log_arrdumppanic {<br />
};<br />
<br />
log_first: log_first {<br />
};<br />
<br />
log_kevents: log_kevents {<br />
};<br />
<br />
log_kevents_small: log_kevents_small {<br />
};<br />
<br />
log_s2d: log_s2d {<br />
};<br />
};<br />
};<br />
};<br />
</syntaxhighlight></div>Berosethttps://wiki.asteroidos.org/index.php?title=Nemo&diff=1007Nemo2026-07-09T11:51:06Z<p>Beroset: Shorten name of Model</p>
<hr />
<div>{{Watches<br />
|Name=nemo<br />
|Model=LG Watch Urbane 2<br />
|ReleaseDate=2015-11-01<br />
|Picture=nemo.png<br />
|Status=experimental<br />
|Stars=2<br />
|Chipset=msm8226<br />
|KernelVersion=3.10<br />
|AndroidVersion=marshmallow<br />
|StatusDisplay=good<br />
|StatusTouch=good<br />
|StatusBluetooth=bad<br />
|StatusHaptics=bad<br />
|StatusTiltToWake=bad<br />
|StatusLightSensor=good<br />
|StatusAlwaysOnDisplay=good<br />
|StatusDualDisplay=missing<br />
|StatusMicrophone=bad<br />
|StatusSpeaker=bad<br />
|StatusCompass=bad<br />
|StatusSteps=bad<br />
|StatusHeartRate=bad<br />
|StatusUSB=good<br />
|StatusWLAN=bad<br />
|StatusGPS=bad<br />
|StatusNFC=bad<br />
|StatusCellular=bad<br />
|StatusCamera=missing<br />
|StatusCrown=missing<br />
|StatusHands=missing<br />
}}<br />
Nemo (LG Watch Urbane 2nd Edition) is a large round watch with LTE. The port is currently a work in progress. <br />
----<br />
Warning: The LG Watch Urbane is a separate watch, see [[bass]]<br />
<br />
= Description =<br />
Nemo is large round watch with a steel case. This was the first android wear watch with cellular networking. The watch can be opened to reveal a SIM card slot. <br />
<br />
= Repair and customisation =<br />
The back of the watch is held on by glue, which means that disassembly will impact water resistance and is somewhat frustrating. Replacement housings-display modules and batteries are commonly available. You will likely need to replace the battery when buying these watches as they are getting quite old.<br />
<br />
== SIM card ==<br />
Getting to the SIM card requires a special triangular tool with three pins. Use this tool to rotate the back cover counterclockwise to the 'unlock' position and it should fall out. When reassembling, rotate the back cover in the clockwise direction.<br />
<br />
== Straps ==<br />
The straps on nemo are not standard and contain antennas, which allows the watch to have a steel case while keeping cellular functionality. These straps are held in with screws that go through the lugs. Due to the thin plastic around the brass inserts in the straps, the straps may crack and no longer mount securely to the watch. <br />
<br />
Straps are rare and expensive due to the fact that they contain antennae. There are two known variants:<br />
* rubber/plastic composite. These are most common and come in black or white. <br />
* rubber/plastic with leather on outside. These straps are even more rare than the standard straps. <br />
<br />
= Miscellaneous hardware docs =<br />
== Battery ==<br />
The battery is commonly sold as BL-S6<br />
<br />
== Keys ==<br />
The center key is the power button. The top and bottom keys map to volume up and down respectively. <br />
== Manually getting to fastboot ==<br />
Hold the lower button before and while powering on the device from power off state until the fastboot menu appears. Powering on can be either done by pressing the power button or by connecting a powered USB cable.</div>Berosethttps://wiki.asteroidos.org/index.php?title=Category:Watches&diff=975Category:Watches2026-07-08T14:26:08Z<p>Beroset: refactored to look better and to use template</p>
<hr />
<div>__NOTOC__<br />
=== Supported watches ===<br />
{{#cargo_query:<br />
tables=Watches<br />
|where=Status="supported"<br />
|fields=Picture,Name,Model,Stars,floor(Stars)=Stars,CONCAT("<b>",Model,"</b><br/>(",Name,")<br/>",floor(Stars)," stars")=capt,_pageName<br />
|order by=Watches.Stars DESC, Watches.Name ASC<br />
|format=template<br />
|template=WatchGalleryItem<br />
|named args=yes<br />
|intro=<div style="display:flex;flex-wrap:wrap;gap:16px;align-items:flex-start;"><br />
|outro=</div><br />
|default=<br />
}}<br />
=== Experimental watches ===<br />
{{#cargo_query:<br />
tables=Watches<br />
|where=Status="experimental"<br />
|fields=Picture,Model,Name,Stars,_pageName<br />
|order by=Watches.Stars DESC, Watches.Name ASC<br />
|format=template<br />
|template=WatchGalleryItem<br />
|named args=yes<br />
|intro=<div style="display:flex;flex-wrap:wrap;gap:16px;align-items:flex-start;"><br />
|outro=</div><br />
|default=<br />
}}<br />
<br />
=== Devices without a functioning port ===<br />
{{#cargo_query:<br />
tables=Watches<br />
|where=Status="port in progress"<br />
|fields=Picture,Name,CONCAT("<b>",Model,"</b><br/>(",Name,")<br/>",floor(Stars)," stars")=capt,_pageName<br />
|order by=Watches.Stars DESC, Watches.Name ASC<br />
|format=template<br />
|template=WatchGalleryItem<br />
|named args=yes<br />
|intro=<div style="display:flex;flex-wrap:wrap;gap:16px;align-items:flex-start;"><br />
|outro=</div><br />
|default=<br />
}}</div>Berosethttps://wiki.asteroidos.org/index.php?title=Template:WatchGalleryItem&diff=974Template:WatchGalleryItem2026-07-08T14:18:46Z<p>Beroset: </p>
<hr />
<div><div style="background:#eee; border:1px solid #ddd; border-radius:4px; display:flex; flex-direction:column; text-align:center; width:min-content"><br />
<div style="margin-bottom:6px;margin-top:6px;">[[File:{{{Picture|}}}|150px|link={{{_pageName|}}}]]</div><br />
<div style="font-weight:bold; height:10%">{{{Model|}}}</div><br />
<div>({{{Name|}}})</div><br />
<div style="margin-bottom:6px"><i>Support:</i>{{#rating: {{{Stars|0}}} }}</div><br />
</div></div>Berosethttps://wiki.asteroidos.org/index.php?title=Template:WatchGalleryItem&diff=973Template:WatchGalleryItem2026-07-08T14:15:50Z<p>Beroset: </p>
<hr />
<div><div style="background:#eee; border:1px solid #ddd; border-radius:4px; display:flex; flex-direction:column; vertical-align:top; text-align:center;"><br />
<div style="margin-bottom:6px;margin-top:6px;">[[File:{{{Picture|}}}|150px|link={{{_pageName|}}}]]</div><br />
<div style="font-weight:bold; height:10%">{{{Model|}}}</div><br />
<div>({{{Name|}}})</div><br />
<div style="margin-bottom:6px"><i>Support:</i>{{#rating: {{{Stars|0}}} }}</div><br />
</div></div>Berosethttps://wiki.asteroidos.org/index.php?title=Template:WatchGalleryItem&diff=972Template:WatchGalleryItem2026-07-08T14:14:12Z<p>Beroset: </p>
<hr />
<div><div style="background:#eee; border:1px solid #ddd; border-radius:4px; width:20%; display:flex; flex-direction:column; vertical-align:top; text-align:center;"><br />
<div style="margin-bottom:6px;margin-top:6px;">[[File:{{{Picture|}}}|150px|link={{{_pageName|}}}]]</div><br />
<div style="font-weight:bold; height:10%">{{{Model|}}}</div><br />
<div>({{{Name|}}})</div><br />
<div style="margin-bottom:6px"><i>Support:</i>{{#rating: {{{Stars|0}}} }}</div><br />
</div></div>Berosethttps://wiki.asteroidos.org/index.php?title=Template:WatchGalleryItem&diff=971Template:WatchGalleryItem2026-07-08T14:11:07Z<p>Beroset: </p>
<hr />
<div><div style="background:#eee; border:1px solid #ddd; border-radius:4px; width:18%; display:flex; flex-direction:column; vertical-align:top; text-align:center;"><br />
<div style="margin-bottom:6px;margin-top:6px;">[[File:{{{Picture|}}}|150px|link={{{_pageName|}}}]]</div><br />
<div style="font-weight:bold; height:10%">{{{Model|}}}</div><br />
<div>({{{Name|}}})</div><br />
<div style="margin-bottom:6px"><i>Support:</i>{{#rating: {{{Stars|0}}} }}</div><br />
</div></div>Berosethttps://wiki.asteroidos.org/index.php?title=Template:WatchGalleryItem&diff=970Template:WatchGalleryItem2026-07-08T14:10:02Z<p>Beroset: </p>
<hr />
<div><div style="background:#eee; border:1px solid #ddd; border-radius:4px; width:18%; display:flex; flex-direction:column; vertical-align:top; text-align:center;"><br />
<div style="margin-bottom:6px;margin-top:6px;">[[File:{{{Picture|}}}|150px|link={{{_pageName|}}}]]</div><br />
<div style="font-weight:bold">{{{Model|}}}</div><br />
<div style="height:10%">({{{Name|}}})</div><br />
<div style="margin-bottom:6px"><i>Support:</i>{{#rating: {{{Stars|0}}} }}</div><br />
</div></div>Berosethttps://wiki.asteroidos.org/index.php?title=Template:WatchGalleryItem&diff=969Template:WatchGalleryItem2026-07-08T14:08:36Z<p>Beroset: </p>
<hr />
<div><div style="background:#eee; border:1px solid #ddd; border-radius:4px; width:18%; display:flex; flex-direction:column; vertical-align:top; text-align:center;"><br />
<div style="margin-bottom:6px;margin-top:6px;">[[File:{{{Picture|}}}|150px|link={{{_pageName|}}}]]</div><br />
<div style="font-weight:bold">{{{Model|}}}</div><br />
<div>({{{Name|}}})</div><br />
<div style="margin-bottom:6px"><i>Support:</i>{{#rating: {{{Stars|0}}} }}</div><br />
</div></div>Berosethttps://wiki.asteroidos.org/index.php?title=Template:WatchGalleryItem&diff=968Template:WatchGalleryItem2026-07-08T14:07:38Z<p>Beroset: </p>
<hr />
<div><div style="background:#eee; border:1px solid #ddd; border-radius:4px; width:18.7%; margin:0.5%; display:flex; flex-direction:column; vertical-align:top; text-align:center;"><br />
<div style="margin-bottom:6px;margin-top:6px;">[[File:{{{Picture|}}}|150px|link={{{_pageName|}}}]]</div><br />
<div style="font-weight:bold">{{{Model|}}}</div><br />
<div>({{{Name|}}})</div><br />
<div style="margin-bottom:6px"><i>Support:</i>{{#rating: {{{Stars|0}}} }}</div><br />
</div></div>Berosethttps://wiki.asteroidos.org/index.php?title=Template:WatchGalleryItem&diff=967Template:WatchGalleryItem2026-07-08T13:57:59Z<p>Beroset: </p>
<hr />
<div><div style="background:#eee; border:1px solid #ddd; border-radius:4px; width:170px; display:flex; flex-direction:column; vertical-align:top; text-align:center;"><br />
<div style="margin-bottom:6px;margin-top:6px;">[[File:{{{Picture|}}}|150px|link={{{_pageName|}}}]]</div><br />
<div style="font-weight:bold">{{{Model|}}}</div><br />
<div>({{{Name|}}})</div><br />
<div style="margin-bottom:6px">{{#rating: {{{Stars|0}}} }}</div><br />
</div></div>Berosethttps://wiki.asteroidos.org/index.php?title=Template:WatchGalleryItem&diff=966Template:WatchGalleryItem2026-07-08T13:55:51Z<p>Beroset: </p>
<hr />
<div><div style="background:#eee; border:1px solid #ddd; border-radius:4px; width:205px; display:flex; flex-direction:column; vertical-align:top; text-align:center;"><br />
<div style="margin-bottom:6px;margin-top:6px;">[[File:{{{Picture|}}}|150px|link={{{_pageName|}}}]]</div><br />
<div style="font-weight:bold">{{{Model|}}}</div><br />
<div>({{{Name|}}})</div><br />
<div style="margin-bottom:6px">{{#rating: {{{Stars|0}}} }}</div><br />
</div></div>Berosethttps://wiki.asteroidos.org/index.php?title=Template:WatchGalleryItem&diff=965Template:WatchGalleryItem2026-07-08T13:55:09Z<p>Beroset: </p>
<hr />
<div><div style="background:#eee; border:1px solid #ddd; border-radius:4px; width:155px; display:flex; flex-direction:column; vertical-align:top; text-align:center;"><br />
<div style="margin-bottom:6px;margin-top:6px;">[[File:{{{Picture|}}}|200px|link={{{_pageName|}}}]]</div><br />
<div style="font-weight:bold">{{{Model|}}}</div><br />
<div>({{{Name|}}})</div><br />
<div style="margin-bottom:6px">{{#rating: {{{Stars|0}}} }}</div><br />
</div></div>Berosethttps://wiki.asteroidos.org/index.php?title=Template:WatchGalleryItem&diff=964Template:WatchGalleryItem2026-07-08T13:53:56Z<p>Beroset: </p>
<hr />
<div><div style="background:#eee; border:1px solid #ddd; border-radius:4px; width:155px; display:flex; flex-direction:column; vertical-align:top; text-align:center;"><br />
<div style="margin-bottom:6px;margin-top:6px;">[[File:{{{Picture|}}}|150px|link={{{_pageName|}}}]]</div><br />
<div style="font-weight:bold">{{{Model|}}}</div><br />
<div>({{{Name|}}})</div><br />
<div style="margin-bottom:6px">{{#rating: {{{Stars|0}}} }}</div><br />
</div></div>Berosethttps://wiki.asteroidos.org/index.php?title=Template:WatchGalleryItem&diff=963Template:WatchGalleryItem2026-07-08T13:51:52Z<p>Beroset: </p>
<hr />
<div><div style="background:#eee; border:1px solid #ddd; border-radius:4px; width:155px; display:flex; flex-direction:column; vertical-align:top; text-align:center;"><br />
<div style="margin-bottom:6px;margin-top:6px;">[[File:{{{Picture|}}}|150px|link={{{_pageName|}}}]]</div><br />
<div style="font-weight:bold">{{{Model|}}}</div><br />
<div>({{{Name|}}})</div><br />
<div>{{#rating: {{{Stars|0}}} }}</div><br />
</div></div>Berosethttps://wiki.asteroidos.org/index.php?title=Template:WatchGalleryItem&diff=962Template:WatchGalleryItem2026-07-08T13:49:57Z<p>Beroset: </p>
<hr />
<div><div style="background:#eee; border:1px solid #ddd; border-radius:4px; width:155px; display:flex; flex-direction:column; vertical-align:top; text-align:center;"><br />
<div style="margin-bottom:6px;">[[File:{{{Picture|}}}|150px|link={{{_pageName|}}}]]</div><br />
<div style="font-weight:bold">{{{Model|}}}</div><br />
<div>({{{Name|}}})</div><br />
<div>{{#rating: {{{Stars|0}}} }}</div><br />
</div></div>Berosethttps://wiki.asteroidos.org/index.php?title=Template:WatchGalleryItem&diff=961Template:WatchGalleryItem2026-07-08T13:49:01Z<p>Beroset: </p>
<hr />
<div><div style="background:#eee; border:1px solid #ddd; border-radius:4px; width:155px; display:flex; flex-direction:column; vertical-align:top; text-align:center;"><br />
<span style="margin-bottom:6px;"><br />
[[File:{{{Picture|}}}|150px|link={{{_pageName|}}}]]<br />
</span><br />
<div style="font-weight:bold">{{{Model|}}}</div><br />
<div>({{{Name|}}})</div><br />
<div>{{#rating: {{{Stars|0}}} }}</div><br />
</div></div>Berosethttps://wiki.asteroidos.org/index.php?title=Template:WatchGalleryItem&diff=960Template:WatchGalleryItem2026-07-08T13:47:46Z<p>Beroset: </p>
<hr />
<div><div style="background:#eee; border:1px solid #ddd; border-radius:4px; width:155px; display:flex; flex-direction:column; vertical-align:top; text-align:center;"><br />
<div style="margin-bottom:6px;"><br />
[[File:{{{Picture|}}}|150px|link={{{_pageName|}}}]]<br />
</div><br />
<div style="font-weight:bold">{{{Model|}}}</div><br />
<div>({{{Name|}}})</div><br />
<div>{{#rating: {{{Stars|0}}} }}</div><br />
</div></div>Berosethttps://wiki.asteroidos.org/index.php?title=Template:WatchGalleryItem&diff=959Template:WatchGalleryItem2026-07-08T13:38:28Z<p>Beroset: </p>
<hr />
<div><div style="background:#eee; border:1px solid #ddd; border-radius:4px; width:155px; display:flex; flex-direction:column; vertical-align:top;"><br />
<div style="text-align:center;margin-bottom:6px;"><br />
[[File:{{{Picture|}}}|150px|link={{{_pageName|}}}]]<br />
</div><br />
<div style="font-weight:bold;text-align:center">{{{Model|}}}</div><br />
<div style="text-align:center">({{{Name|}}})</div><br />
<div>{{#rating: {{{Stars|0}}} }}</div><br />
</div></div>Berosethttps://wiki.asteroidos.org/index.php?title=Template:WatchGalleryItem&diff=958Template:WatchGalleryItem2026-07-08T13:37:20Z<p>Beroset: </p>
<hr />
<div><div style="background:#eee; border:1px solid #ddd; padding:10px; border-radius:4px; width:180px; display:flex; flex-direction:column; vertical-align:top;"><br />
<div style="text-align:center;margin-bottom:6px;"><br />
[[File:{{{Picture|}}}|150px|link={{{_pageName|}}}]]<br />
</div><br />
<div style="font-weight:bold;text-align:center">{{{Model|}}}</div><br />
<div style="text-align:center">({{{Name|}}})</div><br />
<div>{{#rating: {{{Stars|0}}} }}</div><br />
</div></div>Berosethttps://wiki.asteroidos.org/index.php?title=Template:WatchGalleryItem&diff=957Template:WatchGalleryItem2026-07-08T13:35:19Z<p>Beroset: </p>
<hr />
<div><div style="background:#eee; border:1px solid #ddd; padding:10px; border-radius:4px; width:155px; display:flex; flex-direction:column; vertical-align:top;"><br />
<div style="text-align:center;margin-bottom:6px;"><br />
[[File:{{{Picture|}}}|150px|link={{{_pageName|}}}]]<br />
</div><br />
<div style="font-weight:bold;text-align:center">{{{Model|}}}</div><br />
<div style="text-align:center">({{{Name|}}})</div><br />
<div>{{#rating: {{{Stars|0}}} }}</div><br />
</div></div>Berosethttps://wiki.asteroidos.org/index.php?title=Template:Infobox_watch&diff=956Template:Infobox watch2026-07-08T13:23:29Z<p>Beroset: Added #rating for stars</p>
<hr />
<div><includeonly>{| class="infobox" style="width:24em; font-size:90%; border-collapse:collapse;"<br />
! colspan="2" style="text-align:left; font-size:110%; padding:0.6em;" |<br />
{{{Name|}}} {{#if:{{{Model|}}}|<span style="font-size:85%; color:#666"> — {{{Model}}}</span>}}<br />
|-<br />
| style="text-align:center; padding:0.4em;" colspan="2" |<br />
{{#if:{{{Picture|}}}<br />
| [[File:{{{Picture}}}|200px|alt={{{Name|}}}]]<br />
| <!-- no picture --><br />
}}<br />
|-<br />
| style="padding:0.2em 0.6em; width:40%;" | '''Status'''<br />
| style="padding:0.2em 0.6em;" | {{{Status|unknown}}}<br />
|-<br />
| style="padding:0.2em 0.6em; width:40%;" | '''Stars'''<br />
| style="padding:0.2em 0.6em;" | {{#rating: {{{Stars|0}}} }}<br />
|-<br />
! colspan="2" style="background:#f6f6f6; padding:0.45em 0.6em; text-align:left;" | Status details<br />
|-<br />
| style="width:50%; padding:0.25em 0.6em;" | Display<br />
| style="padding:0.25em 0.6em;" | {{{StatusDisplay|unknown}}}<br />
|-<br />
| style="padding:0.25em 0.6em;" | Touch<br />
| style="padding:0.25em 0.6em;" | {{{StatusTouch|unknown}}}<br />
|-<br />
| style="padding:0.25em 0.6em;" | Bluetooth<br />
| style="padding:0.25em 0.6em;" | {{{StatusBluetooth|unknown}}}<br />
|-<br />
| style="padding:0.25em 0.6em;" | Haptics<br />
| style="padding:0.25em 0.6em;" | {{{StatusHaptics|unknown}}}<br />
|-<br />
| style="padding:0.25em 0.6em;" | Tilt to wake<br />
| style="padding:0.25em 0.6em;" | {{{StatusTiltToWake|unknown}}}<br />
|-<br />
| style="padding:0.25em 0.6em;" | Light sensor<br />
| style="padding:0.25em 0.6em;" | {{{StatusLightSensor|unknown}}}<br />
|-<br />
| style="padding:0.25em 0.6em;" | Always-on display<br />
| style="padding:0.25em 0.6em;" | {{{StatusAlwaysOnDisplay|unknown}}}<br />
|-<br />
| style="padding:0.25em 0.6em;" | Dual display<br />
| style="padding:0.25em 0.6em;" | {{{StatusDualDisplay|unknown}}}<br />
|-<br />
| style="padding:0.25em 0.6em;" | Microphone<br />
| style="padding:0.25em 0.6em;" | {{{StatusMicrophone|unknown}}}<br />
|-<br />
| style="padding:0.25em 0.6em;" | Speaker<br />
| style="padding:0.25em 0.6em;" | {{{StatusSpeaker|unknown}}}<br />
|-<br />
| style="padding:0.25em 0.6em;" | Compass<br />
| style="padding:0.25em 0.6em;" | {{{StatusCompass|unknown}}}<br />
|-<br />
| style="padding:0.25em 0.6em;" | Steps<br />
| style="padding:0.25em 0.6em;" | {{{StatusSteps|unknown}}}<br />
|-<br />
| style="padding:0.25em 0.6em;" | Heart rate<br />
| style="padding:0.25em 0.6em;" | {{{StatusHeartRate|unknown}}}<br />
|-<br />
| style="padding:0.25em 0.6em;" | USB<br />
| style="padding:0.25em 0.6em;" | {{{StatusUSB|unknown}}}<br />
|-<br />
| style="padding:0.25em 0.6em;" | WLAN<br />
| style="padding:0.25em 0.6em;" | {{{StatusWLAN|unknown}}}<br />
|-<br />
| style="padding:0.25em 0.6em;" | GPS<br />
| style="padding:0.25em 0.6em;" | {{{StatusGPS|unknown}}}<br />
|-<br />
| style="padding:0.25em 0.6em;" | NFC<br />
| style="padding:0.25em 0.6em;" | {{{StatusNFC|unknown}}}<br />
|-<br />
| style="padding:0.25em 0.6em;" | Cellular<br />
| style="padding:0.25em 0.6em;" | {{{StatusCellular|unknown}}}<br />
|-<br />
| style="padding:0.25em 0.6em;" | Camera<br />
| style="padding:0.25em 0.6em;" | {{{StatusCamera|unknown}}}<br />
|-<br />
| style="padding:0.25em 0.6em;" | Crown<br />
| style="padding:0.25em 0.6em;" | {{{StatusCrown|unknown}}}<br />
|-<br />
| style="padding:0.25em 0.6em;" | Hands<br />
| style="padding:0.25em 0.6em;" | {{{StatusHands|unknown}}}<br />
|}<br />
</includeonly><br />
<noinclude><br />
Usage:<br />
{{Infobox watch<br />
|Name=<br />
|Model=<br />
|Picture=<br />
|Status=<br />
|Stars=<br />
|StatusDisplay=<br />
|StatusTouch=<br />
|StatusBluetooth=<br />
|StatusHaptics=<br />
|StatusTiltToWake=<br />
|StatusLightSensor=<br />
|StatusAlwaysOnDisplay=<br />
|StatusDualDisplay=<br />
|StatusMicrophone=<br />
|StatusSpeaker=<br />
|StatusCompass=<br />
|StatusSteps=<br />
|StatusHeartRate=<br />
|StatusUSB=<br />
|StatusWLAN=<br />
|StatusGPS=<br />
|StatusNFC=<br />
|StatusCellular=<br />
|StatusCamera=<br />
|StatusCrown=<br />
|StatusHands=<br />
}}</noinclude></div>Berosethttps://wiki.asteroidos.org/index.php?title=Template:WatchGalleryItem&diff=954Template:WatchGalleryItem2026-07-08T13:16:55Z<p>Beroset: </p>
<hr />
<div><div style="display:flex;flex-direction:column;width:155px;vertical-align:top;display:inline-block;margin-left: 1.6em;"><br />
<div style="text-align:center;margin-bottom:6px;"><br />
[[File:{{{Picture|}}}|150px|link={{{_pageName|}}}]]<br />
</div><br />
<div style="font-weight:bold;">{{{Model|}}}</div><br />
<div>({{{Name|}}})</div><br />
<div>{{#rating: {{{Stars|0}}} }}</div><br />
</div></div>Berosethttps://wiki.asteroidos.org/index.php?title=Template:WatchGalleryItem&diff=953Template:WatchGalleryItem2026-07-08T13:13:16Z<p>Beroset: </p>
<hr />
<div><div style="display:flex;flex-direction:column;width:155px;vertical-align:top;display:inline-block;margin-left: 1.6em;"><br />
<div style="text-align:center;margin-bottom:6px;"><br />
[[File:{{{Picture|}}}|150px|link={{{_pageName|}}}]]<br />
</div><br />
<div style="font-weight:bold;">{{{Model|}}}</div><br />
<div>({{{Name|}}})</div><br />
<div>{{{#rating: Stars|}}}</div><br />
</div></div>Berosethttps://wiki.asteroidos.org/index.php?title=Template:WatchGalleryItem&diff=952Template:WatchGalleryItem2026-07-08T13:10:55Z<p>Beroset: </p>
<hr />
<div><div style="display:flex;flex-direction:column;width:155px;vertical-align:top;display:inline-block;margin-left: 1.6em;"><br />
<div style="text-align:center;margin-bottom:6px;"><br />
[[File:{{{Picture|}}}|150px|link={{{_pageName|}}}]]<br />
</div><br />
<div style="font-weight:bold;">{{{Model|}}}</div><br />
<div>({{{Name|}}})</div><br />
<div class="field_Stars">{{{#Rating: Stars|}}}</div><br />
</div></div>Berosethttps://wiki.asteroidos.org/index.php?title=Template:WatchGalleryItem&diff=951Template:WatchGalleryItem2026-07-08T12:36:38Z<p>Beroset: </p>
<hr />
<div><div style="display:flex;flex-direction:column;width:155px;vertical-align:top;display:inline-block;margin-left: 1.6em;"><br />
<div style="text-align:center;margin-bottom:6px;"><br />
[[File:{{{Picture|}}}|150px|link={{{_pageName|}}}]]<br />
</div><br />
<div style="font-weight:bold;">{{{Model|}}}</div><br />
<div>({{{Name|}}})</div><br />
<div class="field_Stars">{{{Stars|}}}</div><br />
</div></div>Berosethttps://wiki.asteroidos.org/index.php?title=Template:WatchGalleryItem&diff=950Template:WatchGalleryItem2026-07-08T12:32:29Z<p>Beroset: Attempt to make stars field show stars</p>
<hr />
<div><div style="display:flex;flex-direction:column;width:155px;vertical-align:top;display:inline-block;margin-left: 1.6em;"><br />
<div style="text-align:center;margin-bottom:6px;"><br />
[[File:{{{Picture|}}}|150px|link={{{_pageName|}}}]]<br />
</div><br />
<div style="font-weight:bold;">{{{Model|}}}</div><br />
<div>({{{Name|}}})</div><br />
<div class="field_Stars">{{{Stars|}}} stars</div><br />
</div></div>Berosethttps://wiki.asteroidos.org/index.php?title=Template:WatchGalleryItem&diff=928Template:WatchGalleryItem2026-07-07T19:53:56Z<p>Beroset: </p>
<hr />
<div><div style="display:flex;flex-direction:column;width:220px;"><br />
<div style="text-align:center;margin-bottom:6px;"><br />
<a href="{{{_pageName|}}}"><br />
<img src="https://example.com/path/{{{Picture|}}}" style="width:200px;height:auto;" /><br />
</a><br />
</div><br />
<div style="font-weight:bold;">{{{Model|}}}</div><br />
<div>({{{Name|}}})</div><br />
<div>{{{Stars|}}} stars</div><br />
<br />
</div></div>Berosethttps://wiki.asteroidos.org/index.php?title=Template:WatchGalleryItem&diff=927Template:WatchGalleryItem2026-07-07T19:50:51Z<p>Beroset: </p>
<hr />
<div><div style="display:flex;flex-direction:column;width:220px;"><br />
<div style="text-align:center;margin-bottom:6px;"><br />
<a href="{{{_pageName|}}}"><br />
<img src="https://example.com/path/{{{Picture|}}}" style="width:200px;height:auto;" /><br />
</a><br />
</div><br />
<br />
<div style="font-weight:bold;">{{{Model|}}}</div><br />
<div>({{{Name|}}})</div><br />
<div>{{{Stars|}}} stars</div><br />
</div></div>Berosethttps://wiki.asteroidos.org/index.php?title=Template:WatchGalleryItem&diff=923Template:WatchGalleryItem2026-07-07T19:37:39Z<p>Beroset: </p>
<hr />
<div><!-- Template:WatchGalleryItem --><br />
<div class="gallerybox"><br />
<div class="watch-image">[[File:{{{Picture|}}}|thumb|200px]]</div><br />
<div class="watch-name"><b>{{{Model|}}}</b><br/>({{{Name|}}})</div><br />
<div class="watch-stars">{{{Stars|}}} stars</div><br />
</div></div>Beroset