Plasma Mobile: Difference between revisions
Rahmanshaber (talk | contribs) mNo edit summary |
Rahmanshaber (talk | contribs) mNo edit summary |
||
Line 29: | Line 29: | ||
You can read the log output with <code>logread -f</code>. Anything related to Plasma and KDE will have a <code>$username:plasma-mobile</code> prefix. | You can read the log output with <code>logread -f</code>. Anything related to Plasma and KDE will have a <code>$username:plasma-mobile</code> prefix. | ||
=== Logging isn't verbose === | |||
One needs to enable debug logging for certain components in <code>~/.config/QtProject/qtlogging.ini</code>. Without that, you barely see any log output. We [https://github.com/postmarketOS/pmbootstrap/blob/917f03d5f9f015fa9fc0be8093d87b7f21d98d4a/aports/main/postmarketos-ui-plasma-mobile/APKBUILD#L27 ship such a qtlogging.ini file] in <code>postmarketos-ui-plasma-mobile</code> because Plasma Mobile is relatively new and we want to be able to debug it properly. | One needs to enable debug logging for certain components in <code>~/.config/QtProject/qtlogging.ini</code>. Without that, you barely see any log output. We [https://github.com/postmarketOS/pmbootstrap/blob/917f03d5f9f015fa9fc0be8093d87b7f21d98d4a/aports/main/postmarketos-ui-plasma-mobile/APKBUILD#L27 ship such a qtlogging.ini file] in <code>postmarketos-ui-plasma-mobile</code> because Plasma Mobile is relatively new and we want to be able to debug it properly. | ||
Revision as of 14:19, 13 March 2019
![]() Plasma Mobile running on LG Nexus 5 (hammerhead) | |
Name | Plasma Mobile |
---|---|
Graphics stack | KWin on Wayland or Xorg |
Toolkit | Qt 5 |
In postmarketOS | |
Package | postmarketos-ui-plasma-mobile |
Status | Available |
A mobile variant of the KDE Plasma user interface, optimized for touchscreen.
Status
Plasma Mobile is known to have problem with Android's framebuffer drivers (e.g. #1647). Works best with mainlined devices. |
It works on most devices with a working display, both with hardware acceleration and software rendering. There is however an issue making it unable to run on armhf devices without hardware acceleration.
Installation
Run pmbootstrap init
and choose plasma-mobile
in the interface section.
After installation, the shell will automatically launch upon boot. If it doesn't, have a look at /etc/profile.d/start_plasma.sh
and /usr/bin/plasma-phone
.
For the official KDE instructions on running Plasma Mobile, see their website.
Troubleshooting
Software rendering
Plasma can also be used if your device doesn't support hardware acceleration (if it's a non-armhf device) yet by using software rendering. Please note that the interface will be slow, and it might not be usable for the average user.
Software rendering will be enabled automatically if no hardware acceleration is detected, just make sure mesa-dri-swrast
is installed.
Log output
You can read the log output with logread -f
. Anything related to Plasma and KDE will have a $username:plasma-mobile
prefix.
Logging isn't verbose
One needs to enable debug logging for certain components in ~/.config/QtProject/qtlogging.ini
. Without that, you barely see any log output. We ship such a qtlogging.ini file in postmarketos-ui-plasma-mobile
because Plasma Mobile is relatively new and we want to be able to debug it properly.
If the file did not get installed for you, please double check if it is there and report in 1038.
KWin doesn't work
Plasma Mobile shell uses some Wayland protocols, so you can't run it on X11 in case you tried to do that. |
Please follow these instructions for debugging.
Guide
Follow the Display guide to change and fix display related issues.