Last updated 5/20/2020
Refer to kapper1224's blog and Official wiki. However, since the official wiki does not have related items, it is necessary to use a lot of searches. Other reliable sources of information are Official GitLab Mainly Issue and OSAKANA TARO. This article uses Nexus 7 2012 grouper.
It's faster than Plasma-mobile, but overall heavier. There is no interaction with tap operations. If you tap and succeed, you will get up in about 40 seconds, and if you fail to tap, there is no reaction, so you just have to wait.
There is a Terminal disappearing bug. Be sure to install gnome-terminal and other working Terminals. As officially stated, if you use a password other than a number, you will not be able to unlock it and it will get stuck.
Bluetooth GUI Setting does not work properly. From Terminal
sudo apk add bluez-depricated
sudo /etc/init.d/bluetooth start
sudo hciconfig hci0 up
sudo blutoothctl
After that, [Arch Linux Wiki](https://wiki.archlinux.jp/index.php/Bluetooth#CLI_.E3.81.AB.E3.82.88.E3.82.8B.E8.A8.AD.E5.AE Same as .9A).
Around ʻapk search font, for the time being, around sudo apk add font-ipa`.
There is surprising information in categories such as Apps.
By default, most browsers disappear without error immediately after startup or while drawing a web page. Firefox has been confirmed to work with Settings here. For the time being, it works only with MOZ_ENABLE_WAYLAND = 1. Dillo started as it is, but there is something wrong with the input from the virtual keyboard.
Anbox Also on the Official wiki, but not available on Armv7. However, I tried to use it without noticing it, but the error was different, so it seems to be a bug bug.
Some grabs require the --display = gtk option for pmbootstrap qemu. You can use --host-qemu because of lack of qemu driver in chroot.
The collision detection of the mouse arrow is not at the tip of the arrow, but in the upward direction of the arrow.
It was also created arbitrarily in $ HOME / .config / pmbootstrap.cfg. From the behavior, I could assume a configuration file that I could not find in the document, so I found it by reading helpers / envkernel.sh. Documents and google searches aren't very reliable, and you can't do anything without reading the source.
Normally, the power cannot be turned off from the Power button. There is a power mark on the top, and it is possible from there. However, there is no confirmation that the power is off. Battery-related displays are unreliable. On Android, the battery that lasts for more than a day runs out in about two hours. If it runs out on the Nexus 7, it will be recharged from the promised overdischarge. It will not be possible to use it on the go. If it runs out, the screen will gradually darken.
Overuse of sudo. You should be able to reduce it further by setting. Is xorg-server-xwayland not included in the initial stage? <I checked the source and found it. Overall, wayland and xwayland are suspicious. Is it issue of this? Many gtk3 apps from GDK_BACKEND = wayland cannot be started. Terminal-related things aren't working properly either. Termite works fine, isn't it suspicious about xwayland? phosh: incorrect keyboard input in Xwayland apps Even with termite, I can't input control keys with a standard keyboard. Some keys such as up and down home can be arranged from the lower right of ABC mode. Keyboard-related research will be required even if it is used only with CUI.
At present, transplantation seems to be working hard. There are more supported models and UI options than Ubuntu touch, and I feel the efforts of the people involved. As long as you follow the official method and use it in an environment close to the official one, you can enjoy using it without feeling any problems. The development status and support seem to be active.
I had an unpleasant feeling when I was mainly using Python, but I feel it ad hoc from the design stage, such as how to place settings and configuration files. It is organized and not in the right place. It's distributed and the only way to find it is to read the source. pmbootstrap etc. are also compacted. It is a huge black box, and there is no processing such as halfway through. This is the opposite of simple routes such as Arch Linux or Alpine Linux. Only the options considered in advance are set as positive, and the options are passed to the callee for the time being. From the above, there is a strong impression that the correctness of the developer is being pushed to the user. Also, it is very difficult to play because it requires modification from the source level.
The installation is interesting and recommended, and it seems to be troublesome for engineers to actually use it on mobile phones. Due to the huge technical debt, there is a concern that something a little will follow the same path as conventional mobile Linux.
Recommended Posts