 The next speaker is Bishansha and he's going to talk about Plasma Mobile, the most perfect operating system for mobile phones and the most open one. So give a warm welcome to Bishansha. Thank you everyone. So I will talk about Plasma Mobile. We introduced Plasma Mobile in Academy 2015 at the corona. And since then we have been slowly, slowly moving towards open mobile platform. So and we also finalized the vision in 2016. So that was about full, that vision will provide a full control over your information and communication. And it's also inclusive to third party software and Plasma Mobile also aims to provide seamless cross-device experience. Like if you have your mobile, your mobile device can be you. You can use similar same software on your mobile device and you're also on your desktop device. So also Plasma Mobile aims to follow the open standards. So I'm here to talk about what's going on in Plasma Mobile project in general and where are we towards this vision we have. So for the year 2017 we have had several achievements. For instance we got a first Android Marshmallow or Android 6 based device board. Basically previously all the supported devices were based on Android 5, for example Nexus 5 and OnePlus 1. But in 2017 we ported it to Nexus 5X which comes pre-installed with Android Marshmallow. We also released Kirigami 2 which is a site of Qt Quick Controls 2 components which allows you to create applications for Plasma Mobile and also for the Plasma desktop which are both convergent and can work on both devices similarly. Also one more important project we started or joined was Project Halium. I will talk about it in next slides. Project Halium brought us some more officially and unofficially supported device boards. And this also brought us some potential new devices where Plasma Mobile can be easily supported but we haven't tried actually running a Plasma Mobile on them. So let me talk about Project Halium. So few months ago Canonical stopped developing the Ubuntu Touch. At that time community members of UB ports decided that they don't agree with decision made by Canonical and they will continue the Ubuntu Touch as always and this UB ports team decided that they will maintain the Ubuntu Touch. So in one of their initial meetings they also thought that it's a good idea that the other communities who are working towards the same goal which is reusing the Android binary blocks on the mobile devices. We should collaborate with them for such communities like SelfieSoice and more Plasma Mobile, Nemo Mobile, UNoice and such communities. This idea was presented. Then I discussed this idea with Maria Skripskar and we decided that we should do something like this together. We initially started with a Google document and a telegram group. In a Google document people documented various ideas on which factors we should collaborate with and which parts should be unified between these different projects. This Google document was of 11 to 12 pages long and we kept refining those ideas every day. We also had a telegram group where we discussed those ideas. Everyone came and gave their new ideas and there were several projects, members from several projects coming and giving us feedback on their ideas. After that we decided that we will use Nexus 5 as a reference device and have something working. Project Halium aims to provide a common Android base which you can use to reuse the Android drivers and Android binary blocks. We started with Nexus 5 as a reference root file system which allowed us to run various tests which can make sure that device functions properly. We can reuse all the Android binary blocks. After that I also ported Plasma Mobile to use the same Halium base. Later on we also started working on Halium 7.1 which I believe is currently just ShelfisOS and Halium Community are the only ones which are working on Android 7 based port. So Android 7 based port allows us to have open mobile operating systems on the really new devices. Previously in such projects I had to rely on older devices but with Android 7 based port this is not Android 7 based port. So this is the picture of Plasma Mobile running on Nexus 5, UP ports Touch 1604 running on the Nexus 5 and Plasma Mobile on Fairphone 2 all using the same Halium base. So important bit about this is the device you see over there Fairphone 2. No one from KDE community had to actually port to the Fairphone 2 because Halium base was already working there. We can just put our root file system on top of the Halium base and we got it working. So this allowed us some new devices for example Nexus 5, Nexus 5X, OnePlus 1, Fairphone 2 and Nexus 7 2013 GSM model. These are the devices on which Plasma Mobile is actually tested. There are other community ports but those are not functional yet. This also allows us to some potential new devices for example OnePlus 2, 3X and 5. I have put their code names also Nexus 6 and Nexus 6 5, 6P. And there are many more other devices but on which community is working to port and have Halium running on those devices. So there are too many devices so Halium community is actively working on porting those devices. So far I talked about everything good, every good things that have happened about Plasma Mobile. But the question is that is not everything that is good. There are several points where Plasma Mobile needs improvement. The one part is the quality and testing. So far we had two or three devices supported by the Plasma Mobile. So people who had no specific devices were not able to test those. And as a result we had no such bug reports or no such testing or quality assurance processes. So this is the place where we need improvement and also we will need help. Also currently there are two less applications supported by the Plasma Mobile. In theory Plasma Mobile is just a GNU Linux system so you can run any GNU Linux application on your Plasma Mobile. But still we are missing the touch optimized applications which can work nicely on the mobile devices. And another problem is the manpower. Partly this issue is solved by Project Halium where we offloaded the work of porting devices to Halium project. And so we can focus on the actual user interface and improvements on Plasma's side. And there are also the external factors affecting the Plasma Mobile projects. Android devices or the devices have really old version of kernel so and the really old version of kernel is a security nightmare. Because no one makes sure that those devices have a security fixes back ported. And also the devices are getting harder and harder to tinker with. Some devices have a totally locked boot loader which you cannot really unlock. And so you are stuck with whatever is provided by the vendor. Also Android have started doing forced encryption on system and data partition which you cannot work around easily. So these are the issues and also for example these devices even if they have open source kernel they require a closed source board support files to function to full extent. And those closed source board support project is basically it's basically a wall garden. You don't really know what's happening inside. For example modern firmware is the operating system in itself. You don't really know what it's doing. When you actually call, is it recording your data? Is it recording your metadata? You don't really know. And there is no way to reverse engineer those easily. So is everything about external factors wrong? I would say no. There are some good external factors affecting the Plasma Mobile project. For example there is a new project called Push Market OS. Push Market OS has a goal which is aiming for 10 year life cycle for smartphone. Push Market OS project was started by Oliver Smith. It aims for 10 year life cycle of the phones. It uses Alpine Linux as a minimal base because Alpine Linux is a famous to be used on embedded devices. Because it's really small. You can have a base installation as small as 6 to 7 MBs. It's using Western as a reference user interface. And it wants to use the Plasma Mobile as that user interface. Just before yesterday, part reverse with a nickname known as PureTryout packaged the Plasma Mobile on the Push Market OS. Which is a really great work. He basically started when I started my academic travel. And he have finished to build all the KDE frameworks, Plasma and Plasma Mobile components in just a few days. Which is really great. But they haven't actually tried to run it. But still it's packaging is a really huge work. Also there are projects to have open devices. For example open devices program by Sony where they aim to have a close source what support parts into mainline kernel. Sony is also working on effort to support devices with mainline kernel. Also Qualcomm is working on having a mainline kernel working on their devices. There are a few devices which already supports mainline kernel. Also Fairphone is one of the open devices which is open as open as it can be in both hardware and software terms. And there are also rumors that Purism is launching a Linux phone which will be open in depth. We don't really know it's just a rumor at this point. So the sense of it's a conclusion. So journey towards open mobile platform is actually hard. But we are not the only ones on the same path. There is a community like QBPORS, Shelfisware, Smart, Nemo, and we as a community should work together to have an open mobile platform. And yes that's the conclusion of my talk. If you have any questions let me know. So members of which other projects are currently in Hallium? Currently UBPORS, Nemo Mobile, Plasma Mobile, Astrodos and there is also an independent project called GNU-Linux support. Those developers are part of the Hallium project. And also people from Shelfisware community are present there. Is it possible to install Plasma Mobile on Jallaphone? Depends. Jallaphone doesn't actually have Android. I'm not really sure that Jallaphone has Android parts open source. It's a similar problem as the official Ubuntu touch devices where they don't have actually the Android parts open source. They just have a kernel open source. So if someone manages to port let's say Lineage OS for Synogen Mode to those devices it should be possible in theory but we don't really know. Any other questions? I was wondering what is currently working on the reference device for example Nexus 5x. Does the phone stack work? Message is the camera? Currently we have basic functions working for example. It's not Nexus 5x because Nexus 5x port is really just a week or two weeks old because we migrated to Android 7 based ports. For Nexus 5 we currently have audio calls and Wi-Fi and basic functions working but it's not as polished as users might expect. Any other questions? About the manpower you mentioned before. It seems to be clear that the manpower we have is very busy at the moment so we should try to get new manpower. How do you think we can get mobile phones? People are excited about mobile phones. It seems it shouldn't be that hard getting new people but it seems it is. Do we have a plan to try to bring new people in? I can tell you how to get involved into Plasma Mobile. For Plasma Mobile porting work is now offered to Halium projects so if you want to port it to your devices then it's the project Halium where you should go. If you want to help in packaging Plasma Mobile then we have kept the packaging out of the KDE for obvious reasons because we don't want to limit the distributions that can package Plasma Mobile. So if you want to package Plasma Mobile there is a Plasma Phone Packaging Kit Hub repository. If you want to work on actual Shell then there is a Plasma Phone Components repository on KDE where you can improve and work on Shell. That Shell package is also functional on the desktop so you can run it in embedded mode on the desktop and do development easily. If you want to work on HW Composer Packend and have the hardware parts working then you can do graphics and hardware parts if you want to get them working then the Queenwell and other Plasma base repositories are also part. So basically if you want to contribute to Plasma then you are also contributing to Plasma Mobile. If you have applications that is working on Plasma desktop and if you want to run it on Plasma Mobile then it's also easier with then you can also try it on your device or maybe on your desktop with a different form factor switch. It will also help if we can get some base applications working. So basically if you think you can help with anything of our tasks then I have a fabricator board where I document this task and the Plasma... and you can ask us in Plasma Developer Plasma IRC channel. One of the things that you could do is if you're developing a new application rewriting the UI of an application, take into account to have it work on mobile. One of the things that is really easy is to use the Kirigami framework which already gives you most of the tools by default. It makes it completely effortless to get at least the navigational bits working on different screen sizes and different input methods. And if you use that as a base, it is actually pretty easy to have applications not just work on the desktop use cases if that's your primary goal but to kind of port or have them work on Plasma Mobile as well. Thank you. Sorry, sorry, great. You'll have to clap again. Okay, well, this is not technically a question but it is a comment based on my experience on various Android phones. The devices where you have presented on the supported ones are mostly based on the Qualcomm-based chips which has quite a similar structure like graphics and communication modern and CPU cores and so on. But if you want to reach more and more Android devices like the devices using Samsung chips or MediaTek or Huawei and so on, then you might find that there are mysterious hardware bugs or mysterious GPU bugs which might not be abstracted by the Hylian project and which might need to be dealt by the Plasma Mobile instead from what I am understanding. Currently, as far as I know, the K-Win has various workarounds for various GPUs like NVIDIA or AMD and so on. And if you are trying to expand the support on various known Qualcomm devices then you might need to think about workarounds per CPUs or Android devices and so on. Yes, so one of the things which stumbled upon was yesterday someone managed to get basic graphics working on first Samsung devices in the Hylian project channel. Also Qualcomm devices don't really make it easy if you go for non-access devices. Basically, there is a... I can show you code, actually, just a little bit. So here is a crazy code. For example, some Qualcomm devices, despite LibHardware being an open API which you should not break, some Qualcomm devices decides that they should add this value and modify the existing structure of the code. So those devices break the ABI of the... ABI of everything, for example, Queenwell and LibHyris. So you have to have different root file system for those devices. So this is one of the packaging problems which I am currently stumbling upon to solve. So basically every device wants to be special. So this is also one of the major issues of porting to those mobile devices. For Plasma Mobile, have you already thought about other form factors like running it on 10-inch big tablets? Is it packaged for x86 compatible desktops? We don't have currently... Yes, we do have some ISO files for running it on. Basically you can just use it as a live series on your desktop as well. So yes, we do have AMD 64 packages. But we also need 32-bit packages because some devices have just 32-bit support on these devices. So yeah. So to recap, Sebastian's comment. If you use Kirigami Framework, it will work on mobile phones, tablets and desktop because you don't have a mic. Any more questions? If not, let's give a hand to Bushan. Also we have a Plasma Bob on 24 July at 11.30 am. And it's in room 2.3. So if you have any ideas or want to discuss about Plasma Mobile, then feel free to come.