Boot Process - Revision history

Beroset: /* Troubleshooting the boot process */ point to current meta-smartwatch version of kernel configuration line

2025-12-22T12:54:45Z

Troubleshooting the boot process: point to current meta-smartwatch version of kernel configuration line

← Older revision		Revision as of 12:54, 22 December 2025
Line 25:		Line 25:

	The default initramfs has a section to enable adbd on the watch before booting into the rootfs. You can enable it by appending <code>debug-ramdisk</code> to the boot kernel’s parameters for example with <code>fastboot -c</code> or <code>fastboot --command</code> for some versions of fastboot. For example, if you have a <code>dory</code> watch and the watch's fastboot file in your current directory on your computer, you can do this with this command:<pre>fastboot --cmdline debug-ramdisk boot zImage-dtb-dory.fastboot</pre> When you boot the watch, you will be able to access a command line on the ramdisk with <code>adb shell</code>.		The default initramfs has a section to enable adbd on the watch before booting into the rootfs. You can enable it by appending <code>debug-ramdisk</code> to the boot kernel’s parameters for example with <code>fastboot -c</code> or <code>fastboot --command</code> for some versions of fastboot. For example, if you have a <code>dory</code> watch and the watch's fastboot file in your current directory on your computer, you can do this with this command:<pre>fastboot --cmdline debug-ramdisk boot zImage-dtb-dory.fastboot</pre> When you boot the watch, you will be able to access a command line on the ramdisk with <code>adb shell</code>.
	Here is an example [[https://github.com/AsteroidOS/meta-asteroid/blob/b0dd1970844206a34bbba4477691ec7940bebcf7/recipes-core/initrdscripts/initramfs-scripts-android/init.sh#L42 initscript]] and the [[https://github.com/AsteroidOS/meta-~~bass-hybris~~/blob/master/recipes-kernel~~%2Flinux%2Flinux~~-bass~~%2Fimg_info~~#L10 kernel configuration line]] of bass.		Here is an example [[https://github.com/AsteroidOS/meta-asteroid/blob/b0dd1970844206a34bbba4477691ec7940bebcf7/recipes-core/initrdscripts/initramfs-scripts-android/init.sh#L42 initscript]] and the [[https://github.com/AsteroidOS/meta-smartwatch/blob/master/meta-bass/recipes-kernel/linux/linux-bass/img_info#L10 kernel configuration line]] of bass.
	== Troubleshooting systemd ==		== Troubleshooting systemd ==
	If you see the AsteroidOS logo (even for a split second), the watch is able to boot into the rootfs and launch systemd.		If you see the AsteroidOS logo (even for a split second), the watch is able to boot into the rootfs and launch systemd.

Mosen at 19:46, 3 July 2023

2023-07-03T19:46:19Z

← Older revision		Revision as of 19:46, 3 July 2023
Line 1:		Line 1:
	[[Category:Porters]]~~<pre>~~		[[Category:Porters]]
	This page describes the basis of the AsteroidOS’ boot process. It’s focused on the LG G Watch but it should be similar on most other Android watches.		This page describes the basis of the AsteroidOS’ boot process. It’s focused on the LG G Watch but it should be similar on most other Android watches.

Mosen at 19:45, 3 July 2023

2023-07-03T19:45:47Z

← Older revision		Revision as of 19:45, 3 July 2023
Line 1:		Line 1:
	[[Category:Porters]]		[[Category:Porters]]<pre>
	This page describes the basis of the AsteroidOS’ boot process. It’s focused on the LG G Watch but it should be similar on most other Android watches.		This page describes the basis of the AsteroidOS’ boot process. It’s focused on the LG G Watch but it should be similar on most other Android watches.

Line 29:		Line 29:
	If you see the AsteroidOS logo (even for a split second), the watch is able to boot into the rootfs and launch systemd.		If you see the AsteroidOS logo (even for a split second), the watch is able to boot into the rootfs and launch systemd.
	Logs are normally stored in a tmpfs filesystem which is lost whenever the watch is rebooted. To disable the tmpfs mount, first mount the sdcard card containing the rootfs, and then the rootfs. Execute these commands as root on the watch:		Logs are normally stored in a tmpfs filesystem which is lost whenever the watch is rebooted. To disable the tmpfs mount, first mount the sdcard card containing the rootfs, and then the rootfs. Execute these commands as root on the watch:
	<pre>. /machine.conf		<pre>. /machine.conf</pre>
	mkdir /sdcard /rfs		<pre>mkdir /sdcard /rfs</pre>
	mount /dev/$sdcard_partition /sdcard		<pre>mount /dev/$sdcard_partition /sdcard</pre>
	mount -o loop /sdcard/media/0/asteroidos.ext4 /rfs		<pre>mount -o loop /sdcard/media/0/asteroidos.ext4 /rfs</pre>
	</pre>
	You can then disable the <code>/var/volatile</code> tmpfs mount and enable systemd journal logging (<code>/var/log</code> is a symlink to <code>/var/volatile/log</code>):		You can then disable the <code>/var/volatile</code> tmpfs mount and enable systemd journal logging (<code>/var/log</code> is a symlink to <code>/var/volatile/log</code>):
	<pre>sed -i '/volatile/d' /rfs/etc/fstab</pre>		<pre>sed -i '/volatile/d' /rfs/etc/fstab</pre>
	<pre>mkdir /rfs/var/log/journal		<pre>mkdir /rfs/var/log/journal</pre>
	</pre>
	Once you reboot into the rootfs partition (it’ll fail again), you can hop back into the <code>adb shell</code> and read the journal:		Once you reboot into the rootfs partition (it’ll fail again), you can hop back into the <code>adb shell</code> and read the journal:
	<pre>chroot /rfs /bin/journalctl		<pre>chroot /rfs /bin/journalctl</pre>
	</pre>

Mosen at 19:43, 3 July 2023

2023-07-03T19:43:56Z

← Older revision		Revision as of 19:43, 3 July 2023
Line 35:		Line 35:
	</pre>		</pre>
	You can then disable the <code>/var/volatile</code> tmpfs mount and enable systemd journal logging (<code>/var/log</code> is a symlink to <code>/var/volatile/log</code>):		You can then disable the <code>/var/volatile</code> tmpfs mount and enable systemd journal logging (<code>/var/log</code> is a symlink to <code>/var/volatile/log</code>):
	<pre>sed -i '/volatile/d' /rfs/etc/fstab		<pre>sed -i '/volatile/d' /rfs/etc/fstab</pre>
	mkdir /rfs/var/log/journal		<pre>mkdir /rfs/var/log/journal
	</pre>		</pre>
	Once you reboot into the rootfs partition (it’ll fail again), you can hop back into the <code>adb shell</code> and read the journal:		Once you reboot into the rootfs partition (it’ll fail again), you can hop back into the <code>adb shell</code> and read the journal:
	<pre>chroot /rfs /bin/journalctl		<pre>chroot /rfs /bin/journalctl
	</pre>		</pre>

Beroset: add category

2023-06-17T22:11:18Z

add category

← Older revision		Revision as of 22:11, 17 June 2023
Line 1:		Line 1:
			[[Category:Porters]]
	This page describes the basis of the AsteroidOS’ boot process. It’s focused on the LG G Watch but it should be similar on most other Android watches.		This page describes the basis of the AsteroidOS’ boot process. It’s focused on the LG G Watch but it should be similar on most other Android watches.

Beroset: /* Troubleshooting the boot process */

2023-06-17T16:32:26Z

Troubleshooting the boot process

← Older revision		Revision as of 16:32, 17 June 2023
Line 23:		Line 23:
	= Troubleshooting the boot process =		= Troubleshooting the boot process =

	The default initramfs has a section to enable adbd on the watch before booting into the rootfs. You can enable it by appending <code>debug-ramdisk</code> to the boot kernel’s parameters for example with <code>fastboot -c</code> or <code>fastboot --command</code> for some versions of fastboot. For example, if you have a <code>dory</code> watch and the watch's fastboot file in your current directory on your computer, you can do this with this command:<pre~~><code~~>fastboot --cmdline debug-ramdisk boot zImage-dtb-dory.fastboot~~</code>~~</pre> When you boot the watch, you will be able to access a command line on the ramdisk with <code>adb shell</code>.		The default initramfs has a section to enable adbd on the watch before booting into the rootfs. You can enable it by appending <code>debug-ramdisk</code> to the boot kernel’s parameters for example with <code>fastboot -c</code> or <code>fastboot --command</code> for some versions of fastboot. For example, if you have a <code>dory</code> watch and the watch's fastboot file in your current directory on your computer, you can do this with this command:<pre>fastboot --cmdline debug-ramdisk boot zImage-dtb-dory.fastboot</pre> When you boot the watch, you will be able to access a command line on the ramdisk with <code>adb shell</code>.
	Here is an example [[https://github.com/AsteroidOS/meta-asteroid/blob/b0dd1970844206a34bbba4477691ec7940bebcf7/recipes-core/initrdscripts/initramfs-scripts-android/init.sh#L42 initscript]] and the [[https://github.com/AsteroidOS/meta-bass-hybris/blob/master/recipes-kernel%2Flinux%2Flinux-bass%2Fimg_info#L10 kernel configuration line]] of bass.		Here is an example [[https://github.com/AsteroidOS/meta-asteroid/blob/b0dd1970844206a34bbba4477691ec7940bebcf7/recipes-core/initrdscripts/initramfs-scripts-android/init.sh#L42 initscript]] and the [[https://github.com/AsteroidOS/meta-bass-hybris/blob/master/recipes-kernel%2Flinux%2Flinux-bass%2Fimg_info#L10 kernel configuration line]] of bass.
	== Troubleshooting systemd ==		== Troubleshooting systemd ==

Beroset: /* Troubleshooting systemd */

2023-06-17T16:31:02Z

Troubleshooting systemd

← Older revision		Revision as of 16:31, 17 June 2023
Line 28:		Line 28:
	If you see the AsteroidOS logo (even for a split second), the watch is able to boot into the rootfs and launch systemd.		If you see the AsteroidOS logo (even for a split second), the watch is able to boot into the rootfs and launch systemd.
	Logs are normally stored in a tmpfs filesystem which is lost whenever the watch is rebooted. To disable the tmpfs mount, first mount the sdcard card containing the rootfs, and then the rootfs. Execute these commands as root on the watch:		Logs are normally stored in a tmpfs filesystem which is lost whenever the watch is rebooted. To disable the tmpfs mount, first mount the sdcard card containing the rootfs, and then the rootfs. Execute these commands as root on the watch:
	<pre~~><code~~>. /machine.conf		<pre>. /machine.conf
	mkdir /sdcard /rfs		mkdir /sdcard /rfs
	mount /dev/$sdcard_partition /sdcard		mount /dev/$sdcard_partition /sdcard
	mount -o loop /sdcard/media/0/asteroidos.ext4 /rfs		mount -o loop /sdcard/media/0/asteroidos.ext4 /rfs
	~~</code>~~</pre>		</pre>
	You can then disable the <code>/var/volatile</code> tmpfs mount and enable systemd journal logging (<code>/var/log</code> is a symlink to <code>/var/volatile/log)</code>:		You can then disable the <code>/var/volatile</code> tmpfs mount and enable systemd journal logging (<code>/var/log</code> is a symlink to <code>/var/volatile/log</code>):
	<pre~~><code~~>sed -i '/volatile/d' /rfs/etc/fstab		<pre>sed -i '/volatile/d' /rfs/etc/fstab
	mkdir /rfs/var/log/journal		mkdir /rfs/var/log/journal
	~~</code>~~</pre>		</pre>
	Once you reboot into the rootfs partition (it’ll fail again), you can hop back into the <code>adb shell</code> and read the journal:		Once you reboot into the rootfs partition (it’ll fail again), you can hop back into the <code>adb shell</code> and read the journal:
	<pre~~><code~~>chroot /rfs /bin/journalctl		<pre>chroot /rfs /bin/journalctl
	~~</code>~~</pre>		</pre>

Beroset: inserted graphic

2023-06-17T16:26:41Z

inserted graphic

← Older revision		Revision as of 16:26, 17 June 2023
Line 17:		Line 17:
	* Asteroid-Launcher which is the desktop and wayland compositior.		* Asteroid-Launcher which is the desktop and wayland compositior.

			<br>
	[[File:Boot-process.jpg\|thumb\|Boot process]]		[[File:Boot-process.jpg\|thumb\|Boot process]]
			<br>

	= Troubleshooting the boot process =		= Troubleshooting the boot process =

Beroset: /* General description */

2023-06-17T16:20:56Z

General description

← Older revision		Revision as of 16:20, 17 June 2023
Line 17:		Line 17:
	* Asteroid-Launcher which is the desktop and wayland compositior.		* Asteroid-Launcher which is the desktop and wayland compositior.

	~~<img src="{{assets}}/img/boot~~-process.jpg~~" style="width:100%"/>~~		[[File:Boot-process.jpg\|thumb\|Boot process]]


	= Troubleshooting the boot process =		= Troubleshooting the boot process =

Beroset: initial version of boot process

2023-06-17T15:42:36Z

initial version of boot process

New page

This page describes the basis of the AsteroidOS’ boot process. It’s focused on the LG G Watch but it should be similar on most other Android watches.

= General description =

The first component loaded by the LG G Watch is the bootloader, this component is proprietary and can’t be modified, by default it is locked and only allows to boot Android, but we can access it by swiping the screen from top left to bottom right when booting up or with the <code>adb reboot bootloader</code> from a PC connected to a running Android or AsteroidOS instance with adb mode enabled.
This bootloader supports the <code>fastboot</code> protocol which is also the name of the command used on the computer to communicate with the bootloader. Fastboot allows to unlock the bootloader and then to flash partitions remotely and boot selected kernels. The bootloader can load three kernels, the one flashed on the <code>BOOT</code> partition, the one flashed on the <code>RECOVERY</code> partition and one sent via usb with the <code>fastboot boot boot.img</code> command. Kernels are stored in the boot.img format which is a concatenation of a kernel (sometimes with device tree) and an initramdisk. The boot.img format can be packed or unpacked with the mkbootimg and unmkbootimg tools. The AsteroidOS’s kernel is a slightly modified Android Kernel with, for example, a backported Bluetooth subsystem. The AsteroidOS’s ramdisk mostly load the init program of the rootfs which is systemd by default.
Systemd loads many components like

* Psplash which is a lightweight splashscreen software.
* Android’s init which loads the Android log daemon and servicemanager, both needed to run Asteroid-Launcher.
* DBus which is needed for inter-process communication.
* Adbd which is a daemon implementing the Android Debug Bridge protocol and which is used to get a remote shell and to push/pull files from a connected computer.
* MCE which handles the power consumption, inputs and screen…
* Patchram which loads a proprietary firmware to the broadcom bluetooth chip.
* Bluetoothd which is the BlueZ5 daemon handling bluetooth.
* Asteroid-Launcher which is the desktop and wayland compositior.

<img src="{{assets}}/img/boot-process.jpg" style="width:100%"/>

= Troubleshooting the boot process =

The default initramfs has a section to enable adbd on the watch before booting into the rootfs. You can enable it by appending <code>debug-ramdisk</code> to the boot kernel’s parameters for example with <code>fastboot -c</code> or <code>fastboot --command</code> for some versions of fastboot. For example, if you have a <code>dory</code> watch and the watch's fastboot file in your current directory on your computer, you can do this with this command:<pre><code>fastboot --cmdline debug-ramdisk boot zImage-dtb-dory.fastboot</code></pre> When you boot the watch, you will be able to access a command line on the ramdisk with <code>adb shell</code>.
Here is an example [[https://github.com/AsteroidOS/meta-asteroid/blob/b0dd1970844206a34bbba4477691ec7940bebcf7/recipes-core/initrdscripts/initramfs-scripts-android/init.sh#L42 initscript]] and the [[https://github.com/AsteroidOS/meta-bass-hybris/blob/master/recipes-kernel%2Flinux%2Flinux-bass%2Fimg_info#L10 kernel configuration line]] of bass.
== Troubleshooting systemd ==
If you see the AsteroidOS logo (even for a split second), the watch is able to boot into the rootfs and launch systemd.
Logs are normally stored in a tmpfs filesystem which is lost whenever the watch is rebooted. To disable the tmpfs mount, first mount the sdcard card containing the rootfs, and then the rootfs. Execute these commands as root on the watch:
<pre><code>. /machine.conf
mkdir /sdcard /rfs
mount /dev/$sdcard_partition /sdcard
mount -o loop /sdcard/media/0/asteroidos.ext4 /rfs
</code></pre>
You can then disable the <code>/var/volatile</code> tmpfs mount and enable systemd journal logging (<code>/var/log</code> is a symlink to <code>/var/volatile/log)</code>:
<pre><code>sed -i '/volatile/d' /rfs/etc/fstab
mkdir /rfs/var/log/journal
</code></pre>
Once you reboot into the rootfs partition (it’ll fail again), you can hop back into the <code>adb shell</code> and read the journal:
<pre><code>chroot /rfs /bin/journalctl
</code></pre>