Congrats on making it this far, you’re halfway there!
Seriously, when home assistant starts, it will also run its own dependency retrieval for several of its components.
Which means you need to wait some more and monitor for potential issues in the log (or the console, since you launch it directly in the console in verbose mode).
“Domains to be set up” tells you it’s going to be setting up all those internal components. So you need to wait for this to happen. At this stage, if you look at processes, you will see the individual python processes installing the dependencies. Note that it might start deploying the web UI even before it finishes this. But it needs its essential components to achieve that. Either way, since it’s a first setup for you, I suggest waiting for everything.
Hopefully after some time it will manage to go through all the dependencies. If not, check what fails, try to install it manually in pip to check for errors, and refer to previous posts in this topic for hopefully a solution.
Once you are done with this, you can start thinking about proper ways to launch things automatically.
Personally I use a derivative of the one from the first post. A startup script for termux.boot looking this way:
#!/data/data/com.termux/files/usr/bin/bash
# prevent system from sleeping
termux-wake-lock
# enable remote access
sshd
# start MQTT in the background
mosquitto -d -c /data/data/com.termux/files/usr/etc/mosquitto/mosquitto.conf
# start home assistant in the background
source ~/hass/bin/activate
daemonize /data/data/com.termux/files/home/hass/bin/hass
deactivate
That said it has been explained in a previous post that I’m not using daemonize exactly properly, so it launches it in background it doesn’t really do what it should. A better way would be to follow this post: Home Assistant Core on Android Tablet - #75 by pure_evil