Difference between revisions of "Plasma Mobile"

From postmarketOS
Jump to: navigation, search
m (Logging isn't verbose)
m (Status)
 
(7 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 +
{{note|Plasma Mobile doesn't work on armhf due to an [https://gitlab.com/postmarketOS/pmaports/issues/75 issue with <code>qt5-qtdeclarative</code>]. If your device is actually armv7 but still runs on armhf, please change it.}}
 +
 
{{Infobox interface
 
{{Infobox interface
 
| name = Plasma Mobile
 
| name = Plasma Mobile
 
| image = File:Plasma-mobile-hammerhead.jpg
 
| image = File:Plasma-mobile-hammerhead.jpg
 
| imagecaption = Plasma Mobile running on LG Nexus 5 (hammerhead)
 
| imagecaption = Plasma Mobile running on LG Nexus 5 (hammerhead)
| graphics = KWin on Wayland or Xorg
+
| graphics = KWin on Wayland
 
| toolkit = Qt 5
 
| toolkit = Qt 5
 
}}
 
}}
Line 12: Line 14:
 
{{note|Plasma Mobile is known to have problem with Android's framebuffer drivers (e.g. {{issue|1647}}). Works best with mainlined devices.}}
 
{{note|Plasma Mobile is known to have problem with Android's framebuffer drivers (e.g. {{issue|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.
 
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.
 +
 +
 +
Do note that this interface is unbearably slow without hardware acceleration and isn't recommended at all without it.
  
 
== Installation ==
 
== Installation ==
Run <code>pmbootstrap init</code> and choose <code>plasma-mobile</code> in the interface section.
+
Run <code>pmbootstrap init</code> and choose <code>plasma-mobile</code> in the interface section. If you already have postmarketOS installed, you can install Plasma Mobile by running <code># apk add postmarketos-ui-plasma-mobile</code>. Make sure you uninstall any other UI before you do this.
  
After installation, the shell will automatically launch upon boot. If it doesn't, have a look at <code>/etc/profile.d/start_plasma.sh</code> and <code>/usr/bin/plasma-phone</code>.
+
After installation, the shell will automatically launch upon boot using LightDM. If it doesn't, have a look at <code>$ logread | grep plasma-mobile</code> and <code>/usr/bin/plasma-phone</code>.
  
 
For the official KDE instructions on running Plasma Mobile, see [https://community.kde.org/Plasma/Mobile/RunningApps their website].
 
For the official KDE instructions on running Plasma Mobile, see [https://community.kde.org/Plasma/Mobile/RunningApps their website].
Line 29: Line 34:
 
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 ====
+
=== 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.
  
Line 37: Line 42:
 
{{note|Plasma Mobile shell uses some Wayland protocols, so you can't run it on X11 in case you tried to do that.}}
 
{{note|Plasma Mobile shell uses some Wayland protocols, so you can't run it on X11 in case you tried to do that.}}
 
Please follow [https://blog.martin-graesslin.com/blog/2016/07/why-does-kwin_wayland-not-start/ these instructions] for debugging.
 
Please follow [https://blog.martin-graesslin.com/blog/2016/07/why-does-kwin_wayland-not-start/ these instructions] for debugging.
 +
 +
== Guide ==
 +
Follow the [https://wiki.postmarketos.org/wiki/Display Display] guide to change and fix display related issues.
  
 
== See also ==
 
== See also ==

Latest revision as of 04:21, 24 June 2019

Plasma Mobile doesn't work on armhf due to an issue with qt5-qtdeclarative. If your device is actually armv7 but still runs on armhf, please change it.
Plasma Mobile
Plasma Mobile running on LG Nexus 5 (hammerhead)
Plasma Mobile running on LG Nexus 5 (hammerhead)
Name Plasma Mobile
Graphics stack KWin on Wayland
Toolkit Qt 5

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.


Do note that this interface is unbearably slow without hardware acceleration and isn't recommended at all without it.

Installation

Run pmbootstrap init and choose plasma-mobile in the interface section. If you already have postmarketOS installed, you can install Plasma Mobile by running # apk add postmarketos-ui-plasma-mobile. Make sure you uninstall any other UI before you do this.

After installation, the shell will automatically launch upon boot using LightDM. If it doesn't, have a look at $ logread | grep plasma-mobile 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.

See also