Registered Member
|
Good afternoon,
I am searching (as many many others *)) for an touch interface for my Raspberry Pi 3 with original 7'' display. Plasma-Mobile looks for my like the missing link enabling a touch interface for a widely used (mobile) linux machine. Since the RPi is used in education and science this would enable fast propagation for plasma-mobile among interested young people in completely new applications. So in short: Is there any effort taken to bring plasma-mobile on the RPI?? Debian-Linux is already there; the hardware is tested and working; so where are the problems if there are any?? BR WilHo *) see for instance sailpi https://sailpi.wordpress.com/ or android-rpi https://groups.google.com/forum/#!forum/android-rpi |
Registered Member
|
UPDATE 2:
There are now packages ready for install: http://mobile.neon.pangea.pub/pool/main/p/plasma-mobile/ You just need to add this lines to the sources.list file of your raspberry Pi and installl the needed packages: Make sure you have root privilegs (su -) before running this
If you cant install the packages, try using an older raspberry pi: the packages are for armhf, which is the normal architecture for phones, but the raspi 3 uses the newer arm64. UPDATE 1: Here are the packaging informations: https://github.com/plasma-phone-packaging/plasma-mobile-packaging You can grab the sourcecode from here https://quickgit.kde.org/?p=plasma-mobile.git and add the debian folder. After that you can build the package on your Raspberry Pi. Maybe this toutorial can help you https://www.debian.org/doc/manuals/pack ... ial.en.pdf (look at page 28). You just need to make debian packages for plasma-mobile and a fresh version of wayland (if you are on debian sid, the wayland version should be new enough) I haven't found precompiled debian packages, but there are some for arch linux. If you find any repositorys hosting plasma mobile, please post the links here. I don't know if you are a developer, but if you make debian packages for armhf (raspi architecture) and amd64 please tell me. I have a small apt server running so I would like to get packages . Here is the needed sourcecode: https://quickgit.kde.org/?p=plasma-mobile.git, https://quickgit.kde.org/?p=plasma-mobile-config.git, https://quickgit.kde.org/?p=plasma-mobile-design-docs.git
Last edited by JBB on Sun Sep 04, 2016 2:17 pm, edited 6 times in total.
|
Registered Member
|
DELETED (my post was duplicated)
|
Registered Member
|
Hi, I'd love to know if it works for you because when i tried on raspbian lite it failed:
The following packages have unmet dependencies: /*...*/ ->installation failed. |
Registered Member
|
Ohh Thats probably for one of this reasons:
[1] You are on raspbian jessie which serves to old packages [2] KDE Neon Packages could be needed. So You could Install https://www.raspberrypi.org/downloads/ Snappy Ubuntu core on a second sdcard and add KDE Neon to /etc/apt/sources.list.d/neon.list and install plasma-mobile again.
|
Registered Member
|
Hi,
So I installed ubuntu server and installed plasma-mobile, I used startx to lunch plasma because when I use startplasmacompositor I have this error: could not start d-bus. can you call qdbus. Is it normal that it's extremely slow, even unusable? |
Registered Member
|
You probably need a extra graphics driver which isn't included in ubuntu server because you usually don't use monitor's on servers.
|
Registered Member
|
Dear JBB, Dear olivedesc,
I am writeing this post from my RPi3 with plasma-mobile using the official touch display and an external K400r keyboard. I installed Ubuntu mate 16.04 first and inserted the given repostitories as listed in the 'update 2 post'. The installation was basically straight forward (I first had to upgrade everything). I used mate to have all necessary drivers like for the touch-display pre-installed. A few things that work out of the box followed with some things which do not work or should be fixed: + The official touch screen worked out of the box. External hmdi screens do work also even if the UI seems to be not optimized for the small resolution of the touch display but also for large screens. + The power management of the RPi including the display seems to be good supported. Brightness controll works and switching the display of after some minutes when unused works also well. + firefox works very well and is automatically opened in 'full screen'. Watching videos on youtube is also working ok. But opening the Menu or the bookmarks menu does not work, maybe an overlay problem. - Nevertheless the interface is not fully working and is sometimes slow. I also have to admit that I do not fully understand the complete concept. This could also be a problem with old packages. -- The three buttons on the bottom of the screen including 'apps', 'Home' and 'close' do not work or at least do not show any effect when trying to close an app or going back to the home screen. --widgets are to big or like the watch on the home screen while the search bar on the top seems to be longer as the screen width. -- some windows cant be closed (no Alt-F4), maybe it is a problem in connections with mate apps -- onscreen keyboard is missing (the one from mate does not work in a first attempt) Thank you very much for your work. I hope this will be further enhanced. It has great potential . I will further test some apps like libreoffice, chromium, pdf readers and report back. BR |
Registered Member
|
HI JBB, Any news on the support of Raspberry pi 3 and 4? I am willing to test it on both in combination with a official touch-screen. This is in my opinion a really low-cost and generic hardware and should be supported from plasma-mobile. Thanks in advance, BR, HoWil |
Registered Member
|
I recall reading a web page written by a gentleman who had an interest in installing straight Debian on his pi...
He wanted to keep the nifty pi bits, but wanted a more pure system. His main issue was caused by the change in architecture of the processors in raspberry pi. He ended up with a non-functional hodgepodge of 32 & 64 bit Debian. Since plasma mobile is 32 bit (even though a number of the phones that use it are now 64 bit)... This seems like the very same thing happening here. His solution was quite similar to what I see here as well. Start with the older distro, selectively upgrade, purge, and don't go mixing 32 & 64 bit programs. The Linux doesn't seem to like it much. I'll look for the page again, and report back with a link. |
Registered users: Bing [Bot], Google [Bot], kesang, Yahoo [Bot]