Some watchfaces (e.g. the unofficial-watchface collection) bring their own installation script. If you wish to install a watchface that has no installation script or is not provided as a package you can install it manually using the following instructions.
Installing a watchface only requires pushing the .qml file and the required assets (e.g.
fonts, images, etc.) in the
/usr/share/asteroid-launcher/watchfaces/ directory on your watch.
scp watchface-name.qml email@example.com:/usr/share/asteroid-launcher/watchfaces/
If the watchface has additional dependencies on assets you can push them the same way.
scp image.png firstname.lastname@example.org:/usr/share/asteroid-launcher/watchfaces/
Some watchfaces include their own font.
scp fontname.ttf email@example.com:/usr/share/fonts/
If you wish to install a wallpaper that has no installation script or is not provided as a package you can install it manually using the following instructions.
scp wallpapername.png firstname.lastname@example.org:/usr/share/asteroid-launcher/wallpapers/
While AsteroidOS has a package manager, there is currently no graphical app store.
Installation of local packages
Before you can install the package you need to push it to the watch.
After that you can use SSH to login and install the package
scp packagename.ipk email@example.com:/home/root
When the package is installed you can remove the installation package from your root users home-directory and close the SSH connection to your watch.
opkg install packagename.ipk
Reinstallation of local packages
If you need to reinstall a package you can add the
--force-reinstall flag to the opkg command.
opkg install --force-reinstall packagename.ipk
Using scp results in a
REMOTE HOST IDENTIFICATION HAS CHANGED! warning
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:
ssh-keygen -R 192.168.2.15
Mssing dependencies detected during package install
The package you are trying to install may depend on other packages and their versions. You can install the
dependencies first, add the
--force-depends flag to your install command or decide to not install the
package. Ignoring the dependencies can lead to broken or unstable packages.
opkg install --force-depends packagename.ipk