From 7272e2e94ccfddf91993444fccd4ad096af29157 Mon Sep 17 00:00:00 2001 From: faveoled <85760289+faveoled@users.noreply.github.com> Date: Wed, 13 Aug 2025 22:30:07 +0300 Subject: [PATCH 1/2] Fix typos --- debugging-tips.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/debugging-tips.md b/debugging-tips.md index c8cd60e..3a37cf0 100644 --- a/debugging-tips.md +++ b/debugging-tips.md @@ -8,7 +8,7 @@ Table of contents * [Summary](#summary) * [Pre boot tips](#pre-boot-tips) -* [Tips for when the systen is booted with shell](#tips-for-when-the-systen-is-booted-with-shell) +* [Tips for when the system is booted with shell](#tips-for-when-the-system-is-booted-with-shell) * [Tips for when the system is up with Phosh](#tips-for-when-the-system-is-up-with-phosh) Summary @@ -51,7 +51,7 @@ logs might be looked for in recovery. Nightly releases embed devtools on the rootfs. If you have trouble installing devtools on a snapshot release, consider trying a nightly image so that you don't need to install -it separatedly. +it separately. ### Double-check cmdline for the `systempart=` option @@ -196,7 +196,7 @@ Put the content of the service file (recovery)$ systemctl enable ssh-fix -Tips for when the systen is booted with shell +Tips for when the system is booted with shell --------------------------------------------- **Before proceeding, read the previous section, those tips might be useful as well.** @@ -299,7 +299,7 @@ Save and reboot. ### Vendor is not mounted -It is possible that the vendor partition doesn't get mounted by init and as a result the Halium contianer cannot start much of the services. +It is possible that the vendor partition doesn't get mounted by init and as a result the Halium container cannot start much of the services. First off check if the vendor image is mounted @@ -323,7 +323,7 @@ Make sure to come back to this issue later to find a proper solution. ### lxc@android and phosh started but no output -If phosh and lxc@android have started with udev rules in plcae but there is no output on the screen, it is possible that vndservicemanager is crashing. +If phosh and lxc@android have started with udev rules in place but there is no output on the screen, it is possible that vndservicemanager is crashing. On some Halium 10 devices, a patched version of vndservicemanager might be used to have vndservicemanager start. a patched version of vndservicemanager can be found [here](https://github.com/droidian-devices/adaptation-droidian-starqlte/blob/droidian/usr/lib/droid-vendor-overlay/bin/vndservicemanager). @@ -372,7 +372,7 @@ and put [phoc.ini](https://github.com/droidian-devices/adaptation-droidian-miato the value for `output:HWCOMPOSER-1` can be adjusted as needed. -### vendor parititon overlay +### vendor partiton overlay To overlay a file over the vendor partition, `droid-vendor-overlay` directory can be used From 1f8d8ff1367b216f2a04e89067e2a7c4d3fc53f0 Mon Sep 17 00:00:00 2001 From: faveoled <85760289+faveoled@users.noreply.github.com> Date: Wed, 13 Aug 2025 22:32:14 +0300 Subject: [PATCH 2/2] Fix typos --- debugging-tips.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debugging-tips.md b/debugging-tips.md index 3a37cf0..19a1795 100644 --- a/debugging-tips.md +++ b/debugging-tips.md @@ -372,7 +372,7 @@ and put [phoc.ini](https://github.com/droidian-devices/adaptation-droidian-miato the value for `output:HWCOMPOSER-1` can be adjusted as needed. -### vendor partiton overlay +### vendor partition overlay To overlay a file over the vendor partition, `droid-vendor-overlay` directory can be used