...
 
Commits (40)
include: 'https://invent.kde.org/sysadmin/ci-tooling/raw/master/invent/websites-jekyll.yml'
cache:
paths:
- planet.db
- vendor/
variables:
WEBSITE_DIR: plasma-mobile.org
pages:
stage: deploy
script:
- bundle exec pluto update planet.ini
- bundle exec build.rb
- bundle exec jekyll build -d public
- rsync -Hav --delete public/ "sitedeployer@olios.kde.org:/srv/www/generated/$WEBSITE_DIR/"
only:
- master@websites/plasma-mobile-org
GEM
remote: https://rubygems.org/
specs:
activemodel (5.2.2)
activesupport (= 5.2.2)
activerecord (5.2.2)
activemodel (= 5.2.2)
activesupport (= 5.2.2)
arel (>= 9.0)
activerecord-utils (0.4.0)
activerecord
logutils
activesupport (5.2.2)
concurrent-ruby (~> 1.0, >= 1.0.2)
i18n (>= 0.7, < 2)
minitest (~> 5.1)
tzinfo (~> 1.1)
activityutils (0.1.1)
logutils (>= 0.5)
addressable (2.6.0)
public_suffix (>= 2.0.2, < 4.0)
arel (9.0.0)
colorator (1.1.0)
concurrent-ruby (1.1.4)
em-websocket (0.5.1)
eventmachine (>= 0.12.9)
http_parser.rb (~> 0.6.0)
eventmachine (1.2.7)
feedfilter (1.1.1)
textutils (>= 1.0.1)
feedparser (2.1.1)
logutils (>= 0.6.1)
textutils (>= 1.0.0)
fetcher (0.4.5)
logutils (>= 0.6)
ffi (1.10.0)
forwardable-extended (2.6.0)
gli (2.18.0)
http_parser.rb (0.6.0)
i18n (0.9.5)
concurrent-ruby (~> 1.0)
iniparser (0.1.0)
jekyll (3.8.5)
addressable (~> 2.4)
colorator (~> 1.0)
em-websocket (~> 0.5)
i18n (~> 0.7)
jekyll-sass-converter (~> 1.0)
jekyll-watch (~> 2.0)
kramdown (~> 1.14)
liquid (~> 4.0)
mercenary (~> 0.3.3)
pathutil (~> 0.9)
rouge (>= 1.7, < 4)
safe_yaml (~> 1.0)
jekyll-feed (0.11.0)
jekyll (~> 3.3)
jekyll-planet (0.2.1)
pluto-models (>= 1.3.0)
jekyll-sass-converter (1.5.2)
sass (~> 3.4)
jekyll-watch (2.1.2)
listen (~> 3.0)
kramdown (1.17.0)
liquid (4.0.1)
listen (3.1.5)
rb-fsevent (~> 0.9, >= 0.9.4)
rb-inotify (~> 0.9, >= 0.9.7)
ruby_dep (~> 1.2)
logutils (0.6.1)
logutils-activerecord (0.2.1)
activerecord
logutils (>= 0.6.1)
mercenary (0.3.6)
minitest (5.11.3)
pakman (1.1.0)
fetcher (>= 0.4.5)
liquid (>= 4.0.0)
logutils (>= 0.6.1)
pathutil (0.16.2)
forwardable-extended (~> 2.6)
pluto (1.3.1)
gli (>= 2.12.2)
pluto-merge (>= 1.1.0)
pluto-models (>= 1.4.0)
pluto-tasks (>= 1.5.2)
pluto-update (>= 1.6.0)
sqlite3
pluto-feedfetcher (0.1.1)
fetcher (>= 0.4.4)
pluto-models (>= 1.3.2)
pluto-merge (1.1.0)
fetcher (>= 0.4.4)
pakman (>= 0.5.0)
pluto-models (>= 1.2.2)
pluto-models (1.5.0)
activerecord
activerecord-utils (>= 0.4.0)
activityutils (>= 0.1.1)
feedfilter (>= 1.1.1)
feedparser (>= 2.1.0)
logutils (>= 0.6.1)
logutils-activerecord (>= 0.2.1)
props (>= 1.2.0)
props-activerecord (>= 0.2.0)
textutils (>= 1.4.0)
pluto-tasks (1.5.3)
pluto-models (>= 1.4.0)
pluto-update (>= 1.6.0)
pluto-update (1.6.0)
fetcher (>= 0.4.4)
pluto-feedfetcher (>= 0.1.0)
pluto-models (>= 1.4.0)
preproc (>= 0.1.0)
preproc (0.1.0)
fetcher
logutils
props (1.2.0)
iniparser (>= 0.1.0)
props-activerecord (0.2.0)
activerecord
props (>= 1.2.0)
public_suffix (3.0.3)
rb-fsevent (0.10.3)
rb-inotify (0.10.0)
ffi (~> 1.0)
rouge (3.3.0)
ruby_dep (1.5.0)
rubyzip (1.2.2)
safe_yaml (1.0.4)
sass (3.7.3)
sass-listen (~> 4.0.0)
sass-listen (4.0.0)
rb-fsevent (~> 0.9, >= 0.9.4)
rb-inotify (~> 0.9, >= 0.9.7)
sqlite3 (1.3.13)
textutils (1.4.0)
activesupport
logutils (>= 0.6.1)
props (>= 1.1.2)
rubyzip (>= 1.0.0)
thread_safe (0.3.6)
tzinfo (1.2.5)
thread_safe (~> 0.1)
PLATFORMS
ruby
DEPENDENCIES
jekyll
jekyll-feed
jekyll-planet
pluto
......@@ -17,4 +17,12 @@ url: ""
plugins:
- jekyll-feed
exclude:
- vendor
- build.rb
- Gemfile
- Gemfile.lock
- build.sh
- planet.*
markdown: kramdown
......@@ -6,7 +6,7 @@
<div class="textwidget">
<ul class="footer-links">
<li><a href="https://dot.kde.org/2015/07/25/plasma-mobile-free-mobile-platform/" target="_blank">KDE Dot!</a></li>
<li><a href="http://planetkde.org/" target="_blank">Planet KDE</a></li>
<li><a href="https://planet.kde.org/" target="_blank">Planet KDE</a></li>
</ul>
</div>
</article>
......@@ -22,7 +22,8 @@
<h3>Social</h3>
<div class="textwidget">
<ul class="footer-links">
<li><a href="https://twitter.com/hashtag/kde plasma?f=tweets&amp;vertical=default" target="_blank">#Plasma on Twitter</a></li>
<li><a href="https://twitter.com/kdecommunity" target="_blank">KDE Community on Twitter</a></li>
<li><a href="https://mastodon.technology/@kde" target="_blank">KDE on Mastodon</a></l$
</ul>
</div>
</article>
......
......@@ -5,7 +5,7 @@
<h1 class="logo">
<a href="/index.html">
<img src="/img/logo.svg" alt="plasma-mobile | Plasma in your pocket">
<img src="/img/logo.svg" alt="Plasma Mobile">
</a>
</h1>
......@@ -20,12 +20,24 @@
</div>
<ul id="mega-menu-primary" class="mega-menu mega-menu-horizontal mega-no-js" data-event="hover_intent" data-effect="disabled" data-effect-speed="200" data-second-click="close" data-document-click="collapse" data-vertical-behaviour="standard" data-breakpoint="991" data-unbind="true">
<li class='mega-menu-item mega-menu-item-type-custom mega-menu-item-object-custom mega-align-bottom-left mega-menu-flyout mega-has-icon'><a class="mega-menu-link" href="/index.html" tabindex="0">Home</a></li>
<li class='mega-menu-item mega-menu-item-type-custom mega-menu-item-object-custom mega-align-bottom-left mega-menu-flyout mega-has-icon'><a class="mega-menu-link" href="/vision" tabindex="0">Vision</a></li>
<li class='mega-menu-item mega-menu-item-type-custom mega-menu-item-object-custom mega-align-bottom-left mega-menu-flyout mega-has-icon'><a class="mega-menu-link" href="/overview" tabindex="0">Technology</a></li>
<li class='mega-menu-item mega-menu-item-type-custom mega-menu-item-object-custom mega-align-bottom-left mega-menu-flyout mega-has-icon'><a class="mega-menu-link" href="/findyourway" tabindex="0">Contributing</a></li>
<li class='mega-menu-item mega-menu-item-type-custom mega-menu-item-object-custom mega-align-bottom-left mega-menu-flyout mega-has-icon'><a class="mega-menu-link" href="/join" tabindex="0">Join</a></li>
<li class='mega-menu-item mega-menu-item-type-custom mega-menu-item-object-custom mega-align-bottom-left mega-menu-flyout mega-has-icon'><a class="mega-menu-link" href="/get" aria-haspopup="true" tabindex="0">Getting Plasma Mobile</a></li>
<li class='mega-menu-item mega-menu-item-type-custom mega-menu-item-object-custom mega-align-bottom-left mega-menu-flyout mega-has-icon'><a class="mega-menu-link" href="/tips" tabindex="0">Tips</a></li>
<li class="mega-nav-link mega-menu-item mega-menu-item-type-post_type mega-menu-item-object-page mega-menu-item-has-children mega-align-bottom-left mega-menu-flyout mega-menu-item-51"><a class="mega-menu-link" href="">Project</a>
<ul class="mega-sub-menu">
<li class='mega-menu-item mega-menu-item-type-custom mega-menu-item-object-custom mega-align-bottom-left mega-menu-flyout mega-has-icon'><a class="mega-menu-link" href="/vision" tabindex="0">Vision</a></li>
<li class='mega-menu-item mega-menu-item-type-custom mega-menu-item-object-custom mega-align-bottom-left mega-menu-flyout mega-has-icon'><a class="mega-menu-link" href="/overview" tabindex="0">Technology</a></li>
<li class='mega-menu-item mega-menu-item-type-custom mega-menu-item-object-custom mega-align-bottom-left mega-menu-flyout mega-has-icon'><a class="mega-menu-link" href="/screenshots" tabindex="0">Screenshots</a></li>
<li class='mega-menu-item mega-menu-item-type-custom mega-menu-item-object-custom mega-align-bottom-left mega-menu-flyout mega-has-icon'><a class="mega-menu-link" href="https://phabricator.kde.org/project/view/28/" tabindex="0">Task Board</a></li>
<li class='mega-menu-item mega-menu-item-type-custom mega-menu-item-object-custom mega-align-bottom-left mega-menu-flyout mega-has-icon'><a class="mega-menu-link" href="https://docs.plasma-mobile.org">Documentation</a></li>
<li class='mega-menu-item mega-menu-item-type-custom mega-menu-item-object-custom mega-align-bottom-left mega-menu-flyout mega-has-icon'><a class="mega-menu-link" href="/faq">FAQ</a></li>
<li class='mega-menu-item mega-menu-item-type-custom mega-menu-item-object-custom mega-align-bottom-left mega-menu-flyout mega-has-icon'><a class="mega-menu-link" href="/roadmap">Roadmap</a></li>
</ul>
</li>
<li class="mega-nav-link mega-menu-item mega-menu-item-type-post_type mega-menu-item-object-page mega-menu-item-has-children mega-align-bottom-left mega-menu-flyout mega-menu-item-51"><a class="mega-menu-link" href="" tabindex="0">Community</a>
<ul class="mega-sub-menu">
<li class='mega-menu-item mega-menu-item-type-custom mega-menu-item-object-custom mega-align-bottom-left mega-menu-flyout mega-has-icon'><a class="mega-menu-link" href="/findyourway" tabindex="0">Contributing</a></li>
<li class='mega-menu-item mega-menu-item-type-custom mega-menu-item-object-custom mega-align-bottom-left mega-menu-flyout mega-has-icon'><a class="mega-menu-link" href="/join" tabindex="0">Join</a></li>
</ul>
</li>
<li class='mega-menu-item mega-menu-item-type-custom mega-menu-item-object-custom mega-align-bottom-left mega-menu-flyout mega-has-icon'><a class="mega-menu-link" href="/get" tabindex="0">Install</a></li>
<li class='mega-menu-item mega-menu-item-type-custom mega-menu-item-object-custom mega-align-bottom-left mega-menu-flyout mega-has-icon'><a class="mega-menu-link" href="/blog" tabindex="0">Blog</a></li>
</ul>
</div>
......
---
title: "Plasma Mobile at FOSSCOMM 2018"
created_at: 2018-10-31 11:30:00 UTC+2
author: Dimitris Kardarakos
layout: post
---
<img style="float: right;" alt="FOSSCOMM 2018" src="/img/fscm2018-logo.gif" width="25%">
On the 13th and the 14th of October, we visited Heraklion, Greece and participated in [FOSSCOMM 2018](https://fosscomm2018.gr/index.php/front-page-en/). FOSSCOMM is an annual conference about free software organized by free software enthusiasts and contributors that live in Greece. This year’s event took place in the University of Crete, in Heraklion, organized by the Radio Station of the University of Crete, the Graduate Students Union of the Computer Science Department and the toLABaki hackerspace.
No doubt a foss conference is the perfect place to meet old friends, strengthen community and socials bonds, talk with interesting persons and make new friendships. But apart from "socializing and networking”, we also gave a talk on Saturday about free software on mobile devices and, in particular, Plasma Mobile.
In general, FOSSCOMM has been a great event, hosting over 60 talks and workshops, covering a wide range of interesting topics. The conference provided a great opportunity to foss contributors, university students and many others to attend talks about Linux desktop, privacy, politics, even about satellites. Moreover, the organizers emphasized on holding an event full of community spirit and free software values. Thanks to the efforts of the FOSSCOMM volunteers and organizers, the event has been quite successful in terms of content, participation and vibes.
<figure style="float: left; padding: 1ex; margin-right: 1ex;"><img alt="KDE el" src="/img/kde-el.png" width="400"></figure>
In our [presentation](https://share.kde.org/s/QAfe8fQFqPFbRFD/download), we talked on the importance of working on mobile phones that run free software and we presented the suggestion of KDE. At first, we tried to explain the correlation between free software on mobile and users’ rights and make clear that the proprietary mobile platforms do not fit our needs. After discussing on the technical factors that result to a difficult environment to work in, we talked on our suggestion for a complete and open software system. We also introduced Kirigami to the audience, the KDE framework that makes us dream of a touch friendly Linux application ecosystem. Finally, we talked a little bit about [Halium](https://halium.org/), the project that creates a common ground to interact with Android as well as about [postmarketOS](https://postmarketos.org/) and its goal to provide a touch optimized free Linux distribution based on mainline kernel.
Many people attended our talk asking several interesting questions about Plasma Mobile and, in general, about free software on mobile. Although we had already talked a lot about collaboration with other communities during the presentation, many of the audience questions had a lot to do with our relationship with communities and device manufacturers. In our opinion, this fact stresses the importance of cooperation, knowledge sharing and coordination between mobile foss initiatives.
All these make us think that we managed to raise awareness of the importance of free software on mobile as well as of the value of [contributing](/findyourway) to Plasma Mobile. See you at FOSSCOMM 2019!
<figure style="padding: 1ex; 1ex; border: 1px solid grey; text-align: center;"><a href="/img/fosscomm_volunteers.jpg"><img alt="Our presentation" src="/img/fosscomm_volunteers.jpg" width="900" heigh="508"></a><figcaption>FOSSCOMM volunteers and organizers</figcaption></figure>
---
title: "New documentation"
created_at: 2018-12-28 13:30:00 UTC+1
author: Jonah Brüchert
layout: post
---
<figure style="border: 1px solid grey; text-align: center;">
<a href="/img/docs-plasma-mobile-org.png"><img src="/img/docs-plasma-mobile-org.png"></a>
</figure>
Today we released our new documentation website, which can be found on [docs.plasma-mobile.org](https://docs.plasma-mobile.org).
The new documentation is based on sphinx and replaces our part of the KDE community wiki.
All existing content from the wiki has been migrated, and can be further edited and improved by sending merge requests to the [repository](https://invent.kde.org/websites/docs-plasma-mobile-org) on the KDE GitLab instance.
Thanks to the KDE VDG team and to ReadTheDocs for creating the sphinx design we are using!
#!/usr/bin/env ruby
require 'jekyll/planet'
JekyllPlanet.main
......@@ -619,6 +619,7 @@ h6 {
.main-footer h2,
.main-footer h3 {
font: 20px 'Open Sans';
color: #eff0f1;
line-height: 1.5em;
font-weight: 300;
font-style: normal;
......
......@@ -8,7 +8,6 @@ layout: default
Supported Devices:
- [Nexus 5 (hammerhead)](/nexus-5/) – State: Solid
- [Nexus 5X (bullhead)](/nexus-5/) – State: Solid
* States are: Excellent, Good, Solid, Base works, Experimental, Very
......
---
title: FAQ
permalink: /faq/
layout: default
---
Frequently Asked Questions
==========================
Why is Plasma Mobile not using Mer/Nemomobile?
----------------------------------------------
Plasma Mobile is a software platform for mobile devices. It is not an
operating system in of itself, it consists of Qt5, the KDE Frameworks,
Plasma and various software that's part of the application set. Plasma
Mobile can work on top of the Mer distribution, but due to a lack of
time and resources, we're currently focusing on Halium as a base for
testing and development.
Can Android apps work on Plasma Mobile?
---------------------------------------
In the future, potentially, but currently no. There are projects like
[Anbox](https://anbox.io/) which are seeking to have Android apps run on the Linux desktop without any performance loss, and with full
integration. This could be leveraged in the future to have Android apps
running on top of a GNU/Linux system with the Plasma Mobile platform,
but it's a complicated task, and it's not a priority right now.
Can I run Plasma Mobile on my mobile device?
--------------------------------------------
Currently, Plasma Mobile runs on the following device types:
* **(Recommended) Nexus 5X:** We offer official
installation scripts for the Nexus 5X. The images are
built on top o
f Halium and KDE Neon. You can find more
information on the Plasma Mobile [documentation](http://docs.plasma-mobile.org).
* **x86-based:** If you want to try out Plasma Mobile on an Intel
tablet, desktop/laptop, or virtual machine, the x86_64 Neon-based
Plasma Mobile [image](https://www.plasma-mobile.org/get/) is for
you. Information on how to permanently
install it can be found on the Plasma Mobile [documentation](http://docs.plasma-mobile.org).
* **postmarketOS devices:** postmarketOS is a touch-optimized,
pre-configured Alpine Linux that can be installed on Android
smartphones and other mobile devices. This project is in *very early
stages of development* but it does currently offer support for a
fairly wide range of devices, and it offers Plasma Mobile as an
available interface. Please find your device from the [list of
supported devices](https://wiki.postmarketos.org/wiki/Devices) and
see what's working, then you can follow the [pmOS installation
guide](https://wiki.postmarketos.org/wiki/Installation_guide) to
install it on your device. Your mileage may vary, and it is **not**
necessarily representative of the current state of Plasma Mobile.
* **Other:** If your device is not listed here, you can manually
install the Plasma Mobile rootfs onto your device if it's supported
by Halium. You can check
[here](https://github.com/Halium/projectmanagement/labels/Ports) to see if your device is listed, and if so, you can see the status
and the functional device features. Assuming your device is listed
and well-supported, you can follow the [Halium Porting
Guide](https://docs.halium.org/en/latest/) to install it on your
own device, and reuse the manifest linked in the device-specific page
on the Github. If there are no reports for your device, you can still
install Halium on it similarly, but you'll have to follow the
instructions in the porting guide to create the manifest yourself.
What are requirements of device for porting Plasma Mobile?
----------------------------------------------------------
For Android based devices (ARM and x86) a Halium port is required:
* Device tree & Kernel source
* Kernel version must be 3.8.0 or later
* Devices with MediaTek chipsets are not recommended
* 16 GiB of storage is recommended, but 8 GiB could also work
* 1 GiB of RAM is needed
Intel or AMD based devices (with open source firmware) just can use the x86 ISO
I've installed Plasma Mobile, what is the login password?
---------------------------------------------------------
If you've installed it onto your Nexus 5X via the installation script,
the password should be "1234", and you can then change it afterwards by
running "passwd" in Konsole.
If you're using the x86 image, no password is set by
default, and you'll have to set it by running "passwd" in Konsole before
you can authenticate for anything.
What's the state of the project?
--------------------------------
Plasma Mobile is currently under heavy development and is not intended
to be used as a daily driver. If you are interested in contributing, [join](/findyourway) the game.
......@@ -11,20 +11,29 @@ Distributions offering Plasma Mobile
----------
Neon based reference rootfs (recommended)
----------------------------------------
-----------------------------------------
![](/img/neon.svg){:width="100"}
"Official" image, based on KDE Neon. Targeted at newer devices (with 1GB+ RAM).
KDE Neon itself is based upon Ubuntu 16.04 (xenial), (not Ubuntu Touch).
This image is based on the dev-unstable branch of KDE Neon, and always ships the latest versions of KDE frameworks, kwin and Plasma Mobile.
This image uses Halium as hardware adaption layer.
KDE Neon itself is based upon Ubuntu 18.04 (bionic). This image is based on the dev-unstable branch of KDE Neon, and always ships the latest versions of KDE frameworks, kwin and Plasma Mobile. It also uses Halium as hardware adaption layer.
Manual download:
Download:
[<span class="fa fa-download" /> generic](https://images.plasma-mobile.org/rootfs/)
[<span class="fa fa-download" /> caf](https://images.plasma-mobile.org/caf-rootfs/)
**[<span class="fa fa-angle-right" /> Learn more](/neon-arch-reference-rootfs)**
**[<span class="fa fa-angle-right" /> Installation Guide](https://docs.plasma-mobile.org/Installation.html)**
Debian based reference rootfs
-----------------------------
![](https://www.debian.org/Pics/logo-50.jpg){:width="75"}
Prebuilt rootfs images for devices supported by Halium and by the mainline kernel. Currently, these images support i386, armhf and some arm64 devices (experimental).
**[<span class="fa fa-angle-right" /> Learn more](https://jbbgameich.github.io/debian-pm)**
postmarketOS
------------
......@@ -37,28 +46,15 @@ PostmarketOS (pmOS), is a touch-optimized, pre-configured Alpine Linux that can
**[<span class="fa fa-angle-right" /> Learn more](https://postmarketos.org)**
Arch Linux based reference rootfs (deprecated)
----------------------------------------------
![](/img/archlinux.png){:width="100"}
Arch Linux based image also made by the Plasma Mobile developers. Known not to be as stable as the Neon based rootfs.
This image uses Halium as hardware adaption layer.
Manual download:
[<span class="fa fa-download" /> generic](https://images.plasma-mobile.org/arch-rootfs/)
**[<span class="fa fa-angle-right" /> Learn more](/neon-arch-reference-rootfs)**
**Desktop**
-----------
Neon based ISO image
--------------------
Neon based amd64 ISO image
---------------------------
![](/img/neon.svg){:width="100"}
ISO image using the same packages as the Neon based reference rootfs, just compiled for amd64.
This image can be tested on non-android intel tablets, PCs and virtual machines.
This ISO image is using the same packages as the Neon based reference rootfs, just compiled for amd64. It can be tested on non-android intel tablets, PCs and virtual machines.
**[<span class="fa fa-angle-right" /> Learn more](/intel-based-devices)**
**[<span class="fa fa-angle-right" /> Download](https://images.plasma-mobile.org/iso/)**
This diff is collapsed.
......@@ -112,7 +112,7 @@
target: "https://phabricator.kde.org/T8963",
choiceId: "target-kirigami-design",
description: "Kirigami application design",
extraInfo: "joining KDE Visual Design Group and desigining applications following the Kirigami Human Interface Guidelines"
extraInfo: "joining the KDE Visual Design Group and desigining applications following the KDE Human Interface Guidelines"
},
{
type: "leaf",
......
......@@ -6,7 +6,7 @@ layout: default
## Plasma Phone Reference System
Supported Devices: **Nexus 5X (bullhead), Nexus 5 (hammerhead)**
Supported Device: **Nexus 5X (bullhead)**
Needed software tools: **adb, fastboot**
......@@ -17,14 +17,12 @@ step 2 for future flashing.
### 1A. Unlock (skip if already unlocked)
Unlock the Nexus 5:
<https://www.androidpit.com/how-to-unlock-nexus-5-bootloader>
Unlock the Nexus 5X:
<https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930>
### 1B. Put into firmware mode and run once:
**CAUTION: This will erase the complete memory of your Nexus 5 device!
**CAUTION: This will erase the complete memory of your Nexus 5X device!
Please ensure you have a backup of all your data before you proceed.**
$ fastboot format cache
......@@ -32,7 +30,7 @@ Please ensure you have a backup of all your data before you proceed.**
### 2. Flashing Plasma Mobile (PM)
Put your Nexus 5/X in fastboot mode (press volume down + power button
Put your Nexus 5X in fastboot mode (press volume down + power button
at once), then open a terminal and run
$ git clone https://github.com/plasma-phone-packaging/pm-flashtool.git
......@@ -42,8 +40,8 @@ at once), then open a terminal and run
The -c parameter of script can be used to re-use the **cache** instead
of downloading all the files again.
The -p ***platform*** parameter currently accepts ***neon*** or
***arch***
The -p ***platform*** parameter currently accepts ***neon***, ***arch***
and ***edge***. Edge rootfs is the latest development snapshot of Plasma Mobile and the platform recommended for testing new features and bug fixes.
It will download all files required and store them in cache subdir, e.g.
for Nexus 5X (*bullhead)*:
......
......@@ -14,3 +14,8 @@ title = Planet Plasma Mobile
title = Martin Kacej
link = https://mkacej.wordpress.com
feed = https://mkacej.wordpress.com/feed/
[ilyabizyaev]
title = Ilya Bizyaev
link = https://ilyabiz.com/tag/plasma-mobile
feed = https://ilyabiz.com/tag/plasma-mobile/feed/
This diff is collapsed.
---
title: Roadmap
permalink: /roadmap/
layout: default
---
Roadmap
=======
This page describes the plan about Plasma Mobile development from a
high-level viewpoint. Day-to-day development and planning is done in KDE's
Phabricator system.
Milestones
----------
We have defined a number of Milestones which will be followed "mostly"
in this order. You can follow the process in more detail on the [Plasma
Mobile Workboard](https://phabricator.kde.org/project/view/28/).
### Plasma Mobile 0.1 "Prototype" (finished) ###
The Plasma Mobile prototype shows the viability of Plasma on a handheld
device. The prototype boots a reference device, it is able to make phone
calls, select contacts from an address book and contains partly
functional outlook on how handset running Plasma could look like. [Plasma Mobile 0.1](https://www.youtube.com/watch?v=auuQA0Q8qpM) provides:
* Phone stack definition (libhybris if necessary, Frameworks 5 and
Plasma on top)
* Basic proof-of-concept Plasma Shell providing the handset UI,
including:
* App launcher
* Draggable top panel
* Task switcher
* Settings application
* Proof-of-concept set of apps
### Plasma Mobile 1.0 "Feature Phone" (WIP) ###
Plasma Mobile 1.0 provides an end-user ready experience with a minimal,
useful feature set. This includes the underlying OS and plumbing layers,
a workspace to launch and manage apps, some basic system functions to
set up the network, show connection status, etc. Functions that Plasma Mobile 1.0
should provide:
* Answering and initiating phone calls
* Contacts / address book
* Sending and receiving SMS, possibly other IM service as well
* Input: good virtual keyboard with several layouts support, localization and right-to-left layouts support
* Hardware functions
* Volume control
* Network control (wifi and Mobile), incl. airplane mode
* Basic settings
* Language / Locale
* Clock / Timezone
* Ringtone / Notification sounds / Do-not-disturb
* Mobile network functions and settings
* Roaming
* APN
* Tethering
* Data Limits
* Web browser with basic functions (possibly 3rd party)
* SDK: A software development kit allowing to hack on Plasma Mobile core and 3rd party apps
* Appstore, installing, updating and removing apps
* Photo / Video camera: allows recording photos and videos
* Image / photo gallery
* Video player
See [Plasma Mobile 1.0](https://phabricator.kde.org/project/profile/247/)
### Plasma Mobile 2.0 "Basic Smartphone" ###
Plasma Mobile 2.0 builds upon the basic functionality provided in 1.0,
and provides more functions:
* Personal Information Management
* Email reading and sending
* Calendar
* Reminders
* Multimedia
* Listening to audio / music
* Mobile file manager
* Accessing files through MTP (or equivalent protocol)
* Applications ecosystem
See [Plasma Mobile 2.0](https://phabricator.kde.org/project/view/248/)
Plasma Mobile 3.0 "Featured Smartphone"
--------------------------------------
In the milestone we are going to work on the following features:
* Cloud storage integration
* Games
* Cool apps
* Working Android emulation
---
title: Screenshots
permalink: /screenshots/
layout: default
---
![plasma-screen-1](/img/plasma-screen-1.png){:width="45%"}
![plasma-screen-7](/img/plasma-screen-7.png){:width="45%"}
![plasma-screen-5](/img/plasma-screen-5.png){:width="45%"}
![plasma-screen-4](/img/plasma-screen-4.png){:width="45%"}
......@@ -100,6 +100,7 @@ span a, h1 a, h2 a, h3 a, h4 a, h5 a, h6 a, p a, a {
.main-footer h1, .main-footer h2, .main-footer h3 {
font-size: 20px;
color: #dddddd;
line-height: 0.3em;
margin: 0;
}
......@@ -125,6 +126,10 @@ a:focus {
color: #222222;
}
.developerLinks a {
color: #fcfcfc;
}
.button, input[type="submit"], #submit, .wpcf7-submit, .action-icon.normal:after, .action-icon.normal:hover,
.social-icon-container .social-icon:hover, .main-footer a.tag:hover, .pagination .current, .pagination>.active>a,
.pagination>.active>span, .pagination>.active>a:hover, .pagination>.active>span:hover, .pagination>.active>a:focus,
......@@ -240,10 +245,12 @@ display: none;
.features-list-left h3 {
color: #2ebd62;
font-weight: bold;
}
.features-list-right h3 {
color: #9b5ab5;
font-weight: bold;
}
......
......@@ -24,17 +24,19 @@ ssh:
The password is “1234”.
Once connected, you can resize the /-root partition, to be able to
install more programs:
$ sudo resize-root-partition
$ sudo reboot
To easily establish a wifi connection, execute:
$ nmcli dev wifi con "ssid" password "password"
To resize the root partition on the phone, First reboot to recovery
and then from adb shell, run following.
# e2fsck -yf /data/rootfs.img
# resize2fs -f /data/rootfs.img 1024000
This will double the size of the rootfs.
Notes:
-----
- Root-Password on the phone is ‘1234’.
- Use sudo to access the root user on phone, password for phablet user is 1234
---
title: What's Plasma Mobile?
permalink: /what-is/
layout: default
---
#### Plasma Mobile is a complete software stack for mobile devices that consists of the following technologies:
* Plasma Phone (a
[plasma](https://de.wikipedia.org/wiki/KDE_Plasma_Workspaces)
workspace for touch devices)
* [KWIN/Wayland](https://community.kde.org/KWin/Wayland)
* [libhybris](https://en.wikipedia.org/wiki/Hybris_%28software%29) on
ARM – [DRM (Direct Rendering
Manager)](https://en.wikipedia.org/wiki/Direct_Rendering_Manager) on
intel
* [Ofono](https://01.org/ofono)
* [RIL](https://en.wikipedia.org/wiki/Radio_Interface_Layer)
* [Telepathy](https://en.wikipedia.org/wiki/Telepathy_%28software%29)
* [pulseaudio](https://en.wikipedia.org/wiki/PulseAudio)
![plasma-screen-1](/img/plasma-screen-1.png)
![plasma-screen-7](/img/plasma-screen-7.png)
![plasma-screen-5](/img/plasma-screen-5.png)
![plasma-screen-4](/img/plasma-screen-4.png)
#### It is build to be potentially running many Qt/GTK/X11-based applications, for example:
Plasma apps, Ubuntu Touch (.click) apps, Gnome apps (e.g.GnomeChess),
X11 (e.g.xmame) and possibly other Qt-based apps like Sailfish OS or
Nemo. Packages can be installed by `apt-get install packagename`.