 So, I am Pushan Shah and I am currently working on Plasma Mobile from like last year. So in previous year, Sebastian and I am proud to represent the Plasma Mobile to KD community and after that it's been a year. So this presentation is about the current status of the Plasma Mobile project and what we need to achieve in next milestone. So first I am going to give a small introduction about Plasma Mobile and the developments that have happened in year and how can you contribute to this project. So first thing is Plasma Mobile, if you don't know it's a free user friendly privacy and customizable platform for mobile device. Real images that were presented at previous academy were based in Ubuntu Touch and used to work on LG Nexus 5. Also Plasma Mobile is a successor of Plasma Active project. So after the academy, we decided to listen for Plasma Mobile. So it's a Plasma Mobile aims to become a complete software system for mobile devices. It is designed to give privacy of users back their full control over their information and communication. Plasma Mobile takes a pragmatic approach and it's inclusive to third party software allowing the user to choose which application and services to use. It provides a seamless experience across multiple devices. Plasma Mobile implements open standards and it is developed in the transparent process that is open for community to participate in. So for Plasma Mobile we are mostly using like 75% using the same stack that is used by Plasma Desktop. So if you are contributing to Plasma Desktop then you are as well contributing to Plasma Mobile. Another interesting development that happened was Kirigami. Kirigami is a successor of Plasma Mobile components. Plasma Mobile components were mainly used in Plasma Active and they were now redesigned to for Plasma Mobile and as well for another mobile systems. They are not just components but on VikiBase there are user interface guidelines so which you can follow and make your application. There are user interface guidelines which your application should follow. The first non-KDE application which started using Kirigami was the Subsurface Mobile. They started using Kirigami for their first mobile version and there are also IOS version working progress if I remember correctly. There are multiple Plasma Mobile applications including Peruse, Spacebar and also recently the Plasma Desktop look and feel explorer started using Kirigami. Another one of the other development I worked on was it was a stack based on Synogen mode. So in initial images we started using Ubuntu Touch but after a while it became like hard to maintain. Some of the reasons were compatibility issues. For example, Ubuntu Touch uses Qt 5.5. Ubuntu Touch used Qt 5.5 while our Plasma stack was using Qt 5.6. So there was incompatibility issues also about libhybris. So in libhybris they have like a forked version which have compatibility code and we wanted to use newer libhybris which have some better features for valent. But apparently the newer version and the Ubuntu patches couldn't apply with each other and they were not compatible at all and we wanted to use newer libhybris and also the current Ubuntu Touch version is based on VWid. I mean 15.04 while we wanted to use Xenial that's 16.04. The main reason to use newer stack was we didn't really had much resources to maintain separate repository for VWid and Xenial. We wanted to just reuse the packaging that is provided by KDE Neon. And so I came up with this. The Plasma team came up with this simplified stack in which the mobile device was the Sanogen mode or Android open source project based system and we start Plasma mobile system inside the Alexi container. That's the complete reverse of the Ubuntu Touch stack. In Ubuntu Touch they would say normal Linux system and puts the Android part in the Alexi container. Some of the advantages this newer stack gave us was it was easier to run Plasma mobile because after all the Plasma mobile shell was contained in the Alexi container so you can theoretically create a Alexi container which could be deployed on the same Sanogen mode system and as well we now have more control over how we want to start our Plasma mobile session on mobile device. And this Plasma mobile project also brought multiple improvements in Queen and Velen. So first thing was we have HWComposer backend so there are multiple improvements in the first thing is dynamic power management support in that backend. So like on the Android devices mainly you need to you need to set brightness color to black to turn it off. So when HWComposer backend gained support for that and as well on mobile we needed lock screen so I implemented the lock screen supporting Queen Velen and that development also due to that development Plasma desktop also benefited from that. In Queen Velen there are lots of improvements related to touch screen including different effects for touch screen and there is also Qt virtual keyboard supports Qt released this Qt virtual keyboard with 5.6 and they made in open source in 5.7 so currently Queen supports Qt virtual keyboard on desktop and as well mobile. There are multiple plans for future like enabling to run Plasma mobile on multiple devices more proper integration with Plasma desktop convergence and more third party applications the first point is enabling more device so this is the point where our Plasma team has sort because we don't have access to as much devices as other contributors would have so this requires a community interaction to actually port Plasma mobile to your device and make it run on your device integration with Plasma desktop that is on currently KDE we have KDE connect and there are multiple possibilities where we can integrate Plasma mobile with Plasma desktop and there is a convergence that's also in one of the two released for Qt like Automatic Rotation when Automatic Rotation and like when you plug in your phone with larger display so Plasma desktop probably and we also need more third party applications in Plasma mobile because currently we are quite lacking in the overall applications on Plasma mobile so if you want to contribute to Plasma mobile these were the multiple options like running Plasma on your Plasma or Plasma mobile on your mobile devices more applications and if you want to know more about this I am also taking a breakout session of Plasma mobile in Plasma above I guess that's it do you have any questions how is the status of running Android apps under Plasma mobile or is it even planned? actually it's a little bit different than Plasma mobile project because if you manage to run Android application on Linux stack then you can easily manage it to run it on Plasma mobile because after all Plasma mobile general Linux stack so basically you can run it because you are now based on Syogen no the thing is we strip out the actual Android stuff like the libraries Java libraries and those parts we strip off that is completely minimal CM version which just boots and runs binary blocks required for the hardware support and then it goes through then it passes the passes to the LXC container which in which it takes over and shows not more a question just a precisization of the question before if you are interested to try to have an Android application on Linux try another project that is called Shashlik that's what it does basically and that there is no interior not really a difference whatever the application is running on a normal Linux desktop or on a Plasma mobile any more questions? Hi so have you mentioned Qt virtual keyboard have you used the handwriting recognition features of it and if so how did you did you find the performance sufficient or currently Green doesn't support I guess touch get that's smart so when I tried it I was not able to compile it on Linux at all it looked like a Windows only feature so that makes it impossible then the packages to build it are not available in the standard Linux it's more like there are multiple dependencies which are probably not documented or we need to figure it out yeah it's mainly for the embedded Linux that's why I was interested because there are two back ends that can be used there one is coming from Nuance a commercial one and then there is the open source one the Nuance one is faster to recognize you can write like consecutive and then the open source one is much harder for the processor so that's why I was interested to try the open source one that did you sort of find it acceptable because often in the embedded devices especially if there's not so much processing power it requires to have the Nuance back end for like really smoothly working but on desktop the open source one also crunches fast enough but if you haven't yet so but let's sort it out I'm sure somebody can help it's intended to work with the Linux so it's yeah it should work anyone else yeah so about one year ago at last academy we also had the first announcement of the plasma mobile project right and we also had a demo that was quite surprising I would even say because a lot was already working like doing real phone calls and also some basic app management and so on the question now is what's the current state are we still where we were one year ago or are we maybe even further down the road and we can do more or did the stack underneath change so much and given the rather limited resources as I understand yeah we didn't much make much progress or what's the current take on that so the current thing is we had too much problems with the underlying stack that we had to mostly reverse some parts of it so the so actual visible development didn't really happen the first thing was like the demo that you saw at previous academy was based on older Ubuntu versions and now then we migrated to newer LTS Ubuntu LTS release and then then I had to rework on Sanogen mode stack so overall the actual plasma mobile project didn't see that much development compared to the whole back back end part I tried plasma mobile last year in RANDA and it took like 10 seconds to crash every time did the stability improve since then yes so the thing is since it is using hw composer back end and queen also have DRM back end so most of the valent issues are affecting DRM back end but some issues go through those hw composer back end so stability has improved and as well one thing is like we need to more stabilise the plasma on valent so plasma mobile will automatically improve itself the talk last year ended with an estimation that plasma mobile would be one year from being able to act productly used what is your current estimation as to that that's the tough question so actually as I said a lot of that depends on more people pitching in it's never going to happen if people stand around it and watch it and wait for it it's our thing that was clearly communicated as well if people don't pitch in we could make it happen within one year but a lot of people have been standing at the sidelines and looking at it and some people have been testing it we had pretty good feedback we talked a lot on the underlying stack to make the base system a lot better but there wasn't a single KDE developer who said how can I get my application running on plasma mobile and I think that's really the core problem if we want to make it happen it's not going to happen by itself so again speaking from blue systems perspective it's a good thing that the plasma desktop and plasma mobile share most of the underlying code so the benefit is with regards to Wayland we have a good testing platform and since both are using Wayland the upcoming plasma desktop we see issues early on and so for the last year mainly only Bushan worked on it and reworked most of the base to make it much more independent from Ubuntu Touch itself and using PPAs so we now have our own repositories we could port it easier to Debian or SUSE or any other platform and the main thing is it's still in a prototype state but if there would be a trend that goes to convergence or having a phone as a base that you connect to a larger screen I think it's pretty good that we in KDE have a system that if we put one or two more developers in for a certain time it could easily catch up with really professional systems like Canonica or Android even so this is more of an ongoing thing that we are very focused from blue systems on making plasma desktop stable prepare a plasma desktop on Wayland and so having plasma mobile is basically some fallout that we get the greatest just another little thing to add for who was already here for the talk from David one of the takeaways was Android desktop is coming and that could be true and one thing that could happen as a consequence that many that a lot of desktop hardware even real laptops and not only talking about tablets or phones the only way to run a complete Linux system on those laptops could be could be a stack like plasma mobile so on top of say an engine mod on top of maybe using revibraries and these could be not really happy scenario but I like to see a project like Plasma Mobile as an insurance against this possibility and also one other thing is I mean we need to wait till Plasma desktop runs Wayland completely and then we should switch then only we should consider Plasma Mobile as a stable because ultimately Plasma Mobile is using Wayland so if our Wayland stack is not completely stable then Plasma Mobile is never going to be as much as stable question here so by moving out from the 1.2.000 base to the Cyanogen Mod 1 did we actually lose the possibility to run 1.2.000 applications like browser and stuff that's not so bad so reusing them is cool so the thing is 1.2.000 applications can be done on Plasma Mobile but can be done on current stack but the problem is 1.2.000 applications problem is as I said the compatibility they are compiled with either Qt 5.5 or Qt 5.6 and we want to run it in 5.7 so that's a mismatch and that doesn't work out otherwise we can run any Linux application be it Ubuntu Touch application or whatever on Plasma Mobile in fact I had like every Ubuntu Touch application almost working 2 weeks back and then Ubuntu UI to stop working with Qt 5.7 and I couldn't manage to find how to build it so that's the point where I had to remove Ubuntu Touch application for some time okay any more question no? yeah just a remark related to the browser that there's also the Qt web engine based research browser that you could try try that one yeah it's yeah maybe we could even get it to work yeah not crash on Veylon thanks yeah I think it's Kai who may be able to deliver that but yes it's you are not the only one who doesn't want it to crash on Veylon yeah so I actually wrote a Qt web engine based small demo web browser I did newer ones I have a lot of features and I've been waiting since then to actually be able to run it on Plasma Mobile yeah we'd absolutely love to when you're up he's probably one of those who already made me explore because you're not the only one who needs it on Veylon yeah we totally want to currently you're catching all of the things you want to actually do that but that doesn't happen on mobile people on mobile act very much don't get out of there where it would not be able to get out of there but right now we're hoping okay not another question okay can we see a demonstration somewhere at this wonderful conference can I request we have a demonstration I can either set up a Plasma Mobile demonstration at Boots or maybe you can come to Plasma Mobile what's that you say you're going to set up a demonstration on the blue system stall excellent idea I look forward to seeing it I can set up that okay that's it I guess thank you Bousha yeah