...
 
Commits (85)
{
"phabricator.uri" : "https://phabricator.kde.org/"
}
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>
......
......@@ -17,7 +17,10 @@
<link rel='stylesheet' href='/css/fonts.css' type='text/css' media='all' />
<link rel='stylesheet' href='/plugins/easy-table/themes/default/style.css' type='text/css' media='all' />
<link rel="stylesheet" href="/plugins/modal-video/css/modal-video.min.css">
<link rel='stylesheet' type='text/css' href='/css/findyourway/style.css' title='Default'>
<link rel='stylesheet' type='text/css' href='/css/findyourway/plain.css' title='Bird Eye View'>
<!-- Java-Script -->
<script type='text/javascript' src='/js/jquery/jquery.js'></script>
<script type='text/javascript' src='/js/jquery/jquery-migrate.min.js'></script>
......
......@@ -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,25 @@
</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="/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>
<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="dashicons-megaphone mega-menu-link" href="https://forum.kde.org/viewforum.php?f=293" tabindex="0">Forums</a></li>
</ul>
</div>
</div>
......
<!DOCTYPE html>
<html>
{% include head.html %}
<body>
{% include header.html %}
{{ content }}
{% include footer.html %}
<script src="/js/findyourway/handlebars.runtime.js"></script>
<script src="/js/findyourway/way.js"></script>
<script src="/js/findyourway/displayRender.js"></script>
<script src="/js/findyourway/foopy.js"></script>
<script src="/js/findyourway/l10n.js"></script>
</body>
</html>
---
title: "Plasma Mobile at Akademy 2018"
created_at: 2018-08-23 15:30:00 UTC+1
author: Jonah Brüchert, Bhushan Shah
layout: post
---
Akademy is the annual world summit of KDE. It is a free, non-commercial event organized by the KDE Community. This year's Akademy was hosted at the [TU Wien](https://www.tuwien.ac.at/en/) from the 11th to the 17th of August. Like most KDE community members, Plasma Mobile team members also attended the Akademy and took part in the event, gave [various talks](https://conf.kde.org/en/Akademy2018/public/schedule) and also hosted/participated in various [BoF Sessions](https://community.kde.org/Akademy/2018/AllBoF). We would like to thank the organizers of the event for providing us with a great opportunity to meet, discuss and hack!
<img alt="Plasma Mobile in Vienna" src="/img/plasma-mobile-in-vienna.jpg" width="40%">
## Talks
Akademy 2018 featured several talks that were related to Plasma Mobile in one way or another. Here's a brief overview of some of those talks.
### Day #1
**Bhushan Shah** presented the collaborative efforts of the KDE community to use the mainline kernel instead of Halium on more open devices. Slides from the talk are available [on Bhushan Shah's website.](http://blog.bshah.in/slides/akademy2018/).
<img alt="Bhushan Shah" src="/img/bhushan-shah-talk.jpg" width="40%">
### Day #2
**Oliver Smith** (the founder of postmarketOS) gave a talk on the postmarketOS project. Slides from his talk are available [on the postmarketOS project website.](https://postmarketos.org/static/slides/2018-akademy/).
<img alt="Oliver Smith" src="/img/ollieparanoid-akademy.jpg" width="40%">
**Volker Krause** presented KDE Frameworks 5 for [Yocto Project](https://www.yoctoproject.org/), opensource collaboration project to help developers create custom Linux-based systems for the embedded products. Volker demonstrated Plasma Mobile running on Raspberry Pi 3 using the Yocto project. In another talk, Volker presented the cross-platform application that helps users manage their travel reservations - Itinerary, which also targets Plasma Mobile.
<img alt="Volker Krause" src="/img/volker-plamo-rpi.jpg" width="40%">
<img alt="Volker Krause" src="/img/volker-itinerary.jpg" width="40%">
**Camilo Higuita** talked about VVave, a cross-platform project which uses the Kirigami framework and targets the Plasma Mobile platform in addition to other projects.
<img alt="Camilo Higuita" src="/img/akademy-2018-vvave.jpg" width="40%">
## BoF Sessions
After two days of talks, Akademy progressed into a whole week of BoF (Birds of a Feather) sessions. There were so many great BoFs at this year's Akademy, and we tried to attend as many as possible! These sessions are a valuable opportunity for cross-collaboration between KDE teams. We get to exchange ideas, work together on plans for the future, and resolve problems thanks to fresh perspectives from people outside of our own bubble.
### Plasma Mobile BoF (Monday)
<img alt="Kirigami BoF 2" src="/img/akademy18-plamo-bof.jpg" width="40%">
The Plasma Mobile team hosted the Plasma Mobile BoF on Monday. In our BoF session, we discussed various things with other Plasma developers and community members, and came to the following conclusions:
- We should start making proper releases, to make it easier for packagers to bring Plasma Mobile to the users. Currently it is hard to know if the latest unreleased Plasma Mobile packages depend on an unreleased version of Plasma or not.
- Move KCMs which are not specific to the desktop platform out of plasma-desktop to make them available on Plasma Mobile. We still need to test which modules work fine on a mobile form factor, but we already know we can share, for example, the locale module.
- Bhushan Shah concluded that if we package the Maui Project's apps and write some basic apps that are still missing (like a timer application), Plasma Mobile could actually become usable as a daily driver!
### Flatpak and Snap BoF
We joined the Flatpak and Snap BoF to discuss the state of bundles on Plasma Mobile. Ideally, bundles should Just Work™ on open devices using the mainline kernel and open source drivers. However, currently they don't work with hardware accelerated graphics on libhybris based systems, since they don't include libhybris and don't have the permission to talk to the Android services. We discussed the potential solution for this problem with other developers.
### Onboarding new developers for Plasma Mobile
Plasma Mobile team met with the Neofytos Kolokotronis and Dimitris Kardarakos, who are working on the KDE community goal to improve and streamline the onboarding process for new contributors. We discussed how to establish a strategy to gain new contributors.
- We realized we need to communicate more about the work we do. Some people got the impression that Plasma Mobile wasn't progressing much, so we want to prove the opposite! This post is the first part of putting our plans into action.
- We want to create a list of all apps that are compatible with Plasma Mobile, to make it easier to find out which apps need to be packaged. This will also help new contributors discover applications that they can start working on.
- Another one of our goals is to make it easier to develop apps for Plasma Mobile in an emulator.
- After the BoF session, we were contacted by Louise Stolborg who provided some useful feedback for our [Find Your Way website](https://www.plasma-mobile.org/findyourway). She pointed out some good points about the website, and highlighted the pain points. Based on her feedback, we will work on improving the website in the upcoming days.
### Kirigami BoF
The Kirigami team hosted their own BoF session to discuss everything Kirigami. You can find more details about the session in the [blog post by Marco Martin.](http://notmart.org/blog/2018/08/akademy-2018/)
<img alt="Kirigami BoF 1" src="/img/akademy18-kirigami-1.jpg" width="40%">
<img alt="Kirigami BoF 2" src="/img/akademy18-kirigami-2.png" width="40%">
### MauiKit and VVave BoF
There were also VVave BoF and MauiKit BoF sessions. More details about them can be found in the [blog post by the developer of MauiKit.](https://medium.com/@temisclopeolimac/maui-roadmap-c303cacf21eb)
## Community
<img alt="The postmarketOS/Plasma Mobile Team" src="/img/community-group-photo.jpg" width="40%">
<img alt="The UBports/Plasma Mobile Team" src="/img/plamo-ubports-flohack.jpg" width="40%">
Of course, Akademy means socialization, and meeting new people! We used this opportunity to meet up with the postmarketOS developer team, UBports developer Florian Leeber, Purism team, one of the Bronze sponsors for KDE Akademy, and many other developers.
## Sounds exciting?
If you want to help us on our journey to implement this year's KDE goals, improve usability and privacy on Plasma Mobile, and come up with an easy way to contribute to software in the mobile space, please join our [communication channels](https://www.plasma-mobile.org/join/), [find a task](https://www.plasma-mobile.org/findyourway), and become one of us!
---
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
......@@ -3,11 +3,20 @@
pluto update planet.ini
ruby -r 'jekyll/planet' -e 'JekyllPlanet.main'
# Workaround for non-complete image urls in Bhushan Shah's blog
# Workaround for no https support on Marco Martin's and potentially other blogs
imgcachedir="img/cache"
mkdir -p $imgcachedir
for post in _posts/*; do
if grep "author:" $post | grep "Bhushan Shah" >/dev/null; then
sed -i -e 's_/images_http://blog.bshah.in/images_g' $post
fi
# Extract image urls and download them to the images folder
# Then update all image urls in the posts
for imageurl in $(grep -oP '<img\s+src="\K[^"]+' $post | grep 'http'); do
image_target_filename="$imgcachedir/$(echo $imageurl | sed 's,/,_,g')"
wget --continue $imageurl -O $image_target_filename
sed -i "s,$imageurl,/$image_target_filename,g" $post
done
done
jekyll build
---
title: Contributing
permalink: /contributing/
layout: default
---
This article describes how you can contribute to Plasma Mobile, take
part in its design and development. This page addresses a wider range of
skills, each paragraph explains how to get you going from a different
starting point. Where else do you have the opportunity to shape a
complete Mobile software environment?
Current open tasks for Plasma Mobile are listed on [phabricator board](https://phabricator.kde.org/tag/plasma%3A_mobile/), If you want to navigate through the tasks listed by categories, you can use [interactive guide](/findyourway/).
I am a designer
===============
For designers, the [Plasma Mobile
Forums](https://forum.kde.org/viewforum.php?f=293) provide a good start
to get in touch with others in the team. You can pick up ideas from
there, and post feedback or even your own designs to get input from
others.
I want to write an app
======================
There are multiple ways to bring your application to Plasma Mobile
- Write a native app: You can bring a new app that is already using
KDE Frameworks to Plasma Mobile. Make the UI touch-friendly, and
talk to us how it can best be integrated.
- Port an existing app: Plasma Mobile is an inclusive system, allowing
to run different apps. If your application is written using is ready
for the use on touchscreens and high-dpi displays, it's usually
possible to install it using the package manager. A first step is to
try it and fix possible issues.
- Android apps: Support for Android apps is currently
work-in-progress. Talk to us about its status
I want to work on the Plasma Mobile system
==========================================
If you want to the Plasma Mobile “core” system or functionality, a good
starting point is to subscribe to the [Plasma mailing
list](https://mail.kde.org/mailman/listinfo/plasma-devel) and let us
know what you're interested in for improvements. If you're up for
picking up any other task, let us know and we'll get you going.
I want to make Plasma Mobile available on my Linux distribution
===============================================================
We love your effort to bring Plasma Mobile to a wider audience, and
we're ready to help you with that. If you would like to offer Plasma
Mobile on a not-yet supported Linux distribution, the following
information is useful:
- The source code is hosted in git repositories at git.kde.org, an
overview of relevant repositories can be found
[here](https://community.kde.org/Plasma/Mobile/Code)
- KDE provides a reference image based on KDE Neon, you can use this to
test against, look at integration-level solutions and borrow its
tricks to get Plasma Mobile running
- If you want to improve things in an existing system, get in touch
with us via the Plasma mailing list, or talk directly to the people
working on the distro and packaging.
Do let us know of your efforts on the [Plasma mailing
list](https://mail.kde.org/mailman/listinfo/plasma-devel), so we can
help you to get going and provide advice that may save yourself time and
headaches.
I have this great idea for a new feature...
===========================================
...but I can't do it all by myself. A great way to find like-minded
people that may be able to help you make your idea a reality is to post
it to the [Plasma Mobile
Forums](https://forum.kde.org/viewforum.php?f=293) to gather feedback on
it. Maybe someone else has a similar goal, or you find people who want
to help you.
I just want to help, throw a task at me!
========================================
Great! We always need help. In order to find something that you find fun
and rewarding to work on, a good first step is to find out which itch
you have with Plasma Mobile, and how it can be scratched. What's nagging
you? Now give us a shout-out, best via the [Plasma mailing
list](https://mail.kde.org/mailman/listinfo/plasma-devel). You can also
make yourself known in the [Plasma Mobile
Forums](https://forum.kde.org/viewforum.php?f=293). There's plenty to
do, tasks for every skill and level, and you'll find it's fun to work on
and learn from each other.
.extra, #responses, #footer, select, #lang {
display: none !important;
}
.question {
display: block !important;
}
.question:before {
content: attr(data-l10n-id) ": ";
}
ul, li {
display: block !important;
sfont-size: 12pt !important;
}
li[target]:after {
content: " - " attr(target);
}
\ No newline at end of file
@charset "utf-8";
#wrapper {
font-weight: 300;
text-shadow: 0 1px 0 #fff;
color: #333;
margin-top:0px;
text-align: center;
padding-top: 2em;
padding-bottom: 1em;
}
@media screen and (max-width: 360px) {
#wrapper {
padding-top: 1em;
}
}
.choices li {
display: none;
}
.question {
display: none;
}
.question {
text-align: center;
padding-top: 60px;
}
.question {
font-size: 20pt;
padding: 0 10% 0 10%;
}
#responses {
padding-top: 1em;
font-size: 30pt;
background-image: -moz-radial-gradient(center top , ellipse farthest-side, rgba(140, 140, 140, 0.5), rgba(140, 140, 140, 0) 95%), -moz-radial-gradient(center top , ellipse farthest-side, rgba(220, 220, 220, 0.5), rgba(220, 220, 220, 0)), -moz-radial-gradient(center top , ellipse farthest-side, rgba(220, 220, 220, 0.3), rgba(220, 220, 220, 0));
background-image: -webkit-radial-gradient(center top , ellipse farthest-side, rgba(140, 140, 140, 0.5), rgba(140, 140, 140, 0) 95%), -webkit-radial-gradient(center top , ellipse farthest-side, rgba(220, 220, 220, 0.5), rgba(220, 220, 220, 0)), -webkit-radial-gradient(center top , ellipse farthest-side, rgba(220, 220, 220, 0.3), rgba(220, 220, 220, 0));
background-image: -o-radial-gradient(center top , ellipse farthest-side, rgba(140, 140, 140, 0.5), rgba(140, 140, 140, 0) 95%), -o-radial-gradient(center top , ellipse farthest-side, rgba(220, 220, 220, 0.5), rgba(220, 220, 220, 0)), -o-radial-gradient(center top , ellipse farthest-side, rgba(220, 220, 220, 0.3), rgba(220, 220, 220, 0));
background-image: radial-gradient(center top , ellipse farthest-side, rgba(140, 140, 140, 0.5), rgba(140, 140, 140, 0) 95%), radial-gradient(center top , ellipse farthest-side, rgba(220, 220, 220, 0.5), rgba(220, 220, 220, 0)), radial-gradient(center top , ellipse farthest-side, rgba(220, 220, 220, 0.3), rgba(220, 220, 220, 0));
background-size: 100% 5px, 100% 100px, 100% 100%;
background-repeat: no-repeat;
}
#responses div {
margin-bottom: 0.5em;
/**
* display:none needed in case if js is disabled
*/
display:none;
}
#responses div a:hover {
cursor: pointer;
box-shadow: 0 3px rgba(0, 0, 0, 0.1), 0 -4px rgba(0, 0, 0, 0.1) inset, 0px 3px 48px rgba(255,255,255,0.2) inset;
transition: all .12s ease-in-out;
}
#responses div a:active {
cursor: pointer;
box-shadow: 0 3px rgba(0, 0, 0, 0.1) inset, 0 1px rgb(255, 255, 255, 0.1), 0px 3px 48px rgba(0,0,0,0.2) inset;
transition: all .12s ease-in-out;
}
#responses div a {
text-decoration: none;
color: #fff;
text-shadow: 0 1px 0 rgba(0,0,0,0.5);
padding: 2px 10px 8px;
border-radius: 6px;
border: 0 none;
transition: all .12s ease-in-out;
display: inline-block;
max-width: 90%;
}
#ok a {
background-color: #84C83C;
background: -moz-linear-gradient(#84C83C, #66AA1E) repeat scroll 0 0 #84C83C;
background: -webkit-linear-gradient(#84C83C, #66AA1E) repeat scroll 0 0 #84C83C;
background: -o-linear-gradient(#84C83C, #66AA1E) repeat scroll 0 0 #84C83C;
background: linear-gradient(#84C83C, #66AA1E) repeat scroll 0 0 #84C83C;
box-shadow: 0 3px rgba(0, 0, 0, 0.1), 0 -4px rgba(0, 0, 0, 0.1) inset;
}
#next a {
background-color: #669BE1;
background: -moz-linear-gradient(#669BE1, #487DC3) repeat scroll 0 0 #669BE1;
background: -webkit-linear-gradient(#669BE1, #487DC3) repeat scroll 0 0 #669BE1;
background: -o-linear-gradient(#669BE1, #487DC3) repeat scroll 0 0 #669BE1;
background: linear-gradient(#669BE1, #487DC3) repeat scroll 0 0 #669BE1;
box-shadow: 0 3px rgba(0, 0, 0, 0.1), 0 -4px rgba(0, 0, 0, 0.1) inset;
}
#back a {
background-color: #F19932;
background: -moz-linear-gradient(#F19932, #D37B14) repeat scroll 0 0 #F19932;
background: -webkit-linear-gradient(#F19932, #D37B14) repeat scroll 0 0 #F19932;
background: -o-linear-gradient(#F19932, #D37B14) repeat scroll 0 0 #F19932;
background: linear-gradient(#F19932, #D37B14) repeat scroll 0 0 #F19932;
box-shadow: 0 3px rgba(0, 0, 0, 0.1), 0 -4px rgba(0, 0, 0, 0.1) inset;
}
.choices li {
font-size: 32pt;
font-weight: 600;
}
.extra {
color: #666;
font-size: 20pt;
font-weight: 600;
padding-bottom: 1em;
}
#footer {
margin-top: 6em;
color: #666;
}
#footer a {
color: #555;
}
.negative {
display: none;
}
.visible {
display: inline;
}
@media screen and (max-width: 499px) {
#responses{
font-size: 22pt;
}
.choices li {
font-size: 25pt;
}
}
/* RTL View */
html[dir="rtl"] * {
font-family: "Fira Sans", sans-serif;
}
html[dir="rtl"] #lang-selection {
background: center right transparent no-repeat;
padding-left: 0;
padding-right: 28px;
}
html[dir="rtl"] #lang {
text-align: left;
margin-left: 10px;
margin-right: unset;
}
html[dir="rtl"] header .plamo-logo {
float: right;
}
html[dir="rtl"] #lang {
text-align: left;
}
This diff is collapsed.
......@@ -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.
---
layout: findyourway
title: Find your way in Plasma Mobile
permalink: /findyourway/
---
<div id="wrapper">
<div id="responses">
<div id="ok"><a href="javascript:">Tell me more</a></div>
<div id="next">
<a href="javascript:">
<span class="negative">No, not interested</span>
<span class="negative">Show me something else</span>
<span class="negative">Any other task?</span>
<span class="negative">Not sure, something else please?</span>
<span class="negative">Not my line of expertise</span>
<span class="negative">Next please</span>
</a>
</div>
<div id="back"><a href="javascript:">I was wrong, take me back</a></div>
<noscript>
<span>Please enable JavaScript in your browser!</span>
</noscript>
</div>
<div id="footer">Based on <a href="https://github.com/jdm/asknot">asknot</a></div>
</div>
......@@ -11,54 +11,50 @@ 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:
[<span class="fa fa-download" /> generic](http://images.plasma-mobile.org/rootfs/)
[<span class="fa fa-download" /> caf](http://images.plasma-mobile.org/caf-rootfs/)
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" /> 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)**
**[<span class="fa fa-angle-right" /> Learn more](/neon-arch-reference-rootfs)**
postmarketOS
------------
![](/img/pmOS.svg){:width="100"}
Third-paty distribution especially (but not only) targeted at older devices, based on Alpine Linux.
Third-party distribution especially (but not only) targeted at older devices, based on Alpine Linux.
PostmarketOS (pmOS), is a touch-optimized, pre-configured Alpine Linux that can be installed on smartphones and other mobile devices. The project is at very early stages of development and is not usable for most users yet.
**[<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](http://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/)**
<svg width="48" xmlns="http://www.w3.org/2000/svg" height="48">
<defs>
<linearGradient id="a" x1="543.8" x2="503.8" gradientUnits="userSpaceOnUse" gradientTransform="matrix(0 1-1.16667 0-452.67-499.8)">
<stop stop-color="#197cf1"/>
<stop offset="1" stop-color="#21c9fb"/>
</linearGradient>
<linearGradient id="b" y1="547.8" x1="384.57" y2="530.48" x2="394.57" gradientUnits="userSpaceOnUse">
<stop stop-color="#ffffff" stop-opacity="0"/>
<stop offset="1" stop-color="#ffffff" stop-opacity=".314"/>
</linearGradient>
<linearGradient id="c" x1="384.57" x2="414.57" gradientUnits="userSpaceOnUse">
<stop stop-opacity=".275"/>
<stop offset="1" stop-color="#ffffff" stop-opacity="0"/>
</linearGradient>
<linearGradient id="d" y1="547.8" x1="432.57" y2="527.8" x2="421.02" gradientUnits="userSpaceOnUse">
<stop stop-opacity=".082"/>
<stop offset="1" stop-opacity="0"/>
</linearGradient>
<linearGradient id="e" y1="44" y2="20" x2="0" gradientUnits="userSpaceOnUse">
<stop stop-color="#eef1f2"/>
<stop offset="1" stop-color="#f9fafb"/>
</linearGradient>
<linearGradient id="f" y1="523.8" y2="507.8" gradientUnits="userSpaceOnUse" x2="0" gradientTransform="translate(0 4)">
<stop stop-color="#7cbaf8"/>
<stop offset="1" stop-color="#f4fcff"/>
</linearGradient>
<linearGradient id="g" y1="511.8" x1="414.57" y2="519.8" x2="422.57" gradientUnits="userSpaceOnUse">
<stop stop-color="#292c2f"/>
<stop offset="1" stop-opacity="0"/>
</linearGradient>
</defs>
<g transform="translate(-384.57-499.8)">
<g transform="translate(384.57 499.8)">
<path fill="#c8cfd3" fill-rule="evenodd" d="m24 8l-20 12 20 15 20-15z"/>
<path fill="url(#a)" d="m10 4v40h28v-32l-8-8z"/>
<path fill="url(#e)" d="m4 20v24h40v-24l-16 12h-8z"/>
</g>
<g fill-rule="evenodd">
<path fill="url(#c)" d="m388.57 543.8l16-12h8l16 12z"/>
<path fill="url(#d)" d="m428.57 543.8l-16-12 16-12z"/>
<path fill="url(#b)" d="m388.57 543.8l16-12-16-12z"/>
</g>
<rect width="40" x="388.57" y="542.8" fill="#d1d3d4" height="1"/>
<path fill="url(#f)" d="m404.57 511.8c-.554 0-1 .446-1 1 0 .554.446 1 1 1 .554 0 1-.446 1-1 0-.554-.446-1-1-1m7 0l-2 2 3 3-3 3 2 2 5-5zm-9.5 6c-.831 0-1.5.669-1.5 1.5 0 .831.669 1.5 1.5 1.5.831 0 1.5-.669 1.5-1.5 0-.831-.669-1.5-1.5-1.5m4.5 6c-1.108 0-2 .892-2 2 0 1.108.892 2 2 2 1.108 0 2-.892 2-2 0-1.108-.892-2-2-2"/>
<g fill-rule="evenodd">
<path fill="#313437" d="m422.57 511.8h-8v-8z"/>
<path opacity=".2" fill="url(#g)" d="m414.57 511.8h8v8z"/>
</g>
</g>
</svg>
This diff is collapsed.
......@@ -6,7 +6,7 @@ layout: default
Here is a link to amd64-compatible ISOs for intel-based devices (PCs,
laptops/netbooks or tablets like wetab, exopc) based on KDE Neon:
<http://images.plasma-mobile.org/iso>
<https://images.plasma-mobile.org/iso>
Prepare a USB stick with the ISO (using “dd” or diskimager).
Boot from USB, then, if asked, choose “Try Ubuntu” in boot-menu.
......@@ -6,11 +6,9 @@ layout: default
![Konqi](/img/424px-Mascot_konqi-app-internet.png){:width="200"}
There are various community groups and channels about Plasma Mobile available to join:
If you'd like to contribute to the amazing free software for mobile devices, [join us - we always have a task for you](/contributing/)!
### Forums:
* [![](/img/kde.png){:width="30"} Plasma Mobile subforum](https://forum.kde.org/viewforum.php?f=293)
Plasma Mobile community groups and channels:
### Plasma Mobile specific channels:
......@@ -20,8 +18,12 @@ There are various community groups and channels about Plasma Mobile available to
The Telegram and Matrix channels are bridged, so you don't have to join both
* [![](/img/mail.svg){:width="30"} Plasma Mobile mailing list](https://mail.kde.org/mailman/listinfo/plasma-mobile)
### Plasma Mobile and other topics:
* [![](/img/irc.png){:width="30"} IRC #plasma on Freenode](https://kiwiirc.com/nextclient/chat.freenode.net/#plasma)
* [![](/img/telegram.svg){:width="30"} Telegram #Halium](https://t.me/Halium)
* [![](/img/mail.svg){:width="30"} Plasma development mailing list](https://mail.kde.org/mailman/listinfo/plasma-devel)
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
/** Copyright (c) 2011-2012 Fabien Cazenave, Mozilla.
* Copyright (c) 2018 Dimitris Kardarakos, KDE
*
* Permission is hereby granted, free of charge, to any person obtaining a copy
* of this software and associated documentation files (the "Software"), to
* deal in the Software without restriction, including without limitation the
* rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
* sell copies of the Software, and to permit persons to whom the Software is
* furnished to do so, subject to the following conditions:
*
* The above copyright notice and this permission notice shall be included in
* all copies or substantial portions of the Software.
*
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
* AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
* LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
* FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
* IN THE SOFTWARE.
*/
/*jshint browser: true, devel: true, es5: true, globalstrict: true */
'use strict';
document.webL10n = (function(window, document, undefined) {
var gLanguage = 'en';
var gReadyState = 'loading';
// read-only setting -- we recommend to load l10n resources synchronously
var gAsyncResourceLoading = true;
// clear all l10n data
function clear() {
gLanguage = '';
}
// cross-browser API (sorry, oldIE doesn't support getters & setters)
return {
// get|set the document language
getLanguage: function() { return gLanguage; },
setLanguage: function(lang) { clear(); gLanguage = lang; },
// get the direction (ltr|rtl) of the current language
getDirection: function() {
// http://www.w3.org/International/questions/qa-scripts
// Arabic, Hebrew, Farsi, Pashto, Urdu
var rtlList = ['ar', 'he', 'fa', 'ps', 'ur'];
return (rtlList.indexOf(gLanguage) >= 0) ? 'rtl' : 'ltr';
},
// this can be used to prevent race conditions
getReadyState: function() { return gReadyState; }
};
}) (window, document);
{{#each groups}}
<div class="group" {{group_info}}
<ul class="choices">
{{#each choices}}
<li {{choice_info}}</li>
{{/each}}
</ul>
</div>
{{/each}}
(function() {
var template = Handlebars.template, templates = Handlebars.templates = Handlebars.templates || {};
templates['way'] = template({"1":function(container,depth0,helpers,partials,data) {
var stack1, helper, alias1=depth0 != null ? depth0 : (container.nullContext || {});
return "<div class=\"group\" "
+ container.escapeExpression(((helper = (helper = helpers.group_info || (depth0 != null ? depth0.group_info : depth0)) != null ? helper : helpers.helperMissing),(typeof helper === "function" ? helper.call(alias1,{"name":"group_info","hash":{},"data":data}) : helper)))
+ "\n <ul class=\"choices\">\n"
+ ((stack1 = helpers.each.call(alias1,(depth0 != null ? depth0.choices : depth0),{"name":"each","hash":{},"fn":container.program(2, data, 0),"inverse":container.noop,"data":data})) != null ? stack1 : "")
+ " </ul>\n</div>\n";
},"2":function(container,depth0,helpers,partials,data) {
var helper;
return " <li "
+ container.escapeExpression(((helper = (helper = helpers.choice_info || (depth0 != null ? depth0.choice_info : depth0)) != null ? helper : helpers.helperMissing),(typeof helper === "function" ? helper.call(depth0 != null ? depth0 : (container.nullContext || {}),{"name":"choice_info","hash":{},"data":data}) : helper)))
+ "</li>\n";
},"compiler":[7,">= 4.0.0"],"main":function(container,depth0,helpers,partials,data) {
var stack1;
return ((stack1 = helpers.each.call(depth0 != null ? depth0 : (container.nullContext || {}),(depth0 != null ? depth0.groups : depth0),{"name":"each","hash":{},"fn":container.program(1, data, 0),"inverse":container.noop,"data":data})) != null ? stack1 : "");
},"useData":true});
})();
\ No newline at end of file
......@@ -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.