Commit d1ef659f authored by Script Kiddy's avatar Script Kiddy
Browse files

GIT_SILENT Add new file (after extraction)

parent 3f495f89
Pipeline #88256 skipped
---
menu:
main:
weight: 1
title: Plasma Bigscreen
---
---
layout: page
menu:
main:
name: PMF
parent: project
weight: 5
title: Preguntes més freqüents
---
## Ajuda! El control remot de la meva TV no funciona, com ho arreglo?
Molts fabricants de TV requereixen que s'activi manualment el mode HDMI-CEC. Cal remetre's a la guia d'usuari de la TV per entendre com configurar l'opció HDMI-CEC de l'aparell de TV. L'opció HDMI-CEC es pot trobar amb diversos nom depenent del fabricant de la TV. Per exemple TCL: T-Link, Panasonic: Viera Link, Samsung: Anynet+, Sony: Bravia Sync.
Verifiqueu també que el dispositiu Plasma Bigscreen sigui realment compatible amb la «libcec», [comproveu el maquinari compatible](https://github.com/Pulse-Eight/libcec#supported-hardware).
## Alguns botons del control remot de la meva TV no funcionen. No puc sortir d'una aplicació o usar el botó adequadament. Com ho soluciono?
El HDMI-CEC de la imatge beta és en fase de proves. Només hem pogut provar les característiques en una petita mostra seleccionada d'aparells de TV i hem mapat els controls remots de les TV en aquests dispositius que funcionen. Podeu mapar i provar el control remot de la vostra TV seguint uns pocs passos senzills de depuració i editant els fitxers que es llisten a sota.
_Prova si la tecla KEY funciona amb el HDMI-CEC i extreure el seu codi de tecla KEY CODE:_
```sh
cd ~/.config./autostart-scripts/
python3 cec-daemon.py
```
Un cop s'hagi executat l'script, premeu el botó del control remot de la TV per extreure el seu codi de tecla (KEY CODE). Si no es troba cap KEY CODE, podria ser que la tecla KEY no formi part dels controls HDMI-CEC activats a l'aparell de TV. Remeteu-vos a la guia d'usuari de la TV per a conèixer quines tecles s'han activat a la implementació HDMI-CEC del fabricant de la vostra TV.
_Afegint el KEY CODE trobat i mapar-lo en el dimoni CEC:_
```sh
cd ~\.config\autostart-scripts\
nano cec-daemon.py
```
- Localitzeu KEYMAP = {} en l'script del dimoni
- Afegiu el vostre KEY CODE en el format següent a la llista: «9: u.KEY\_HOMEPAGE»
- A l'exemple «u.KEY\_HOMEPAGE» està mapat al botó d'inici que s'usa per a sortir d'una aplicació
- «9» és el codi de tecla (Key Code)
- «u.KEY\_HOMEPAGE» és l'acció que hauria d'executar la tecla
## Tinc un control remot USB genèric, però li manca la tecla inici. Com surto de les aplicacions?
No tots els controls remots USB genèrics estan construïts de la mateixa manera, per tant, recomanem usar un producte provat com el «Wechip G20 Air Mouse With Microphone Remote». Si no en podeu aconseguir un, també podreu mapar una tecla existent en el control remot.
_Mapar el botó de tancament de finestra a un botó d'un control remot USB:_
```sh
cd ~\.config\
nano kglobalshortcutsrc
```
- Trobeu l'entrada «Window Close» situada sota `[Kwin]`
- Assigneu el botó a l'entrada «Window Close»
- Exemple: `Window Close=Alt+F4\t’AquíElVostreBotó’,Alt+F4\t’AquíElVostreBotó’,Close Window`
## Les aplicacions de veu no s'inicien en arrencar i veig una pantalla negra. Què hauria de fer?
Les aplicacions de veu són accessibles després d'iniciar el MyCroft i un cop estigui preparat. Veureu una notificació en el plafó superior quan el MyCroft s'hagi iniciat i estigui en estat de preparat.
## Com surto de les aplicacions usant un teclat extern?
«Alt+F4» és la drecera general assignada a tancar aplicacions usant un teclat extern. Es poden assignar tecles personalitzades en el fitxer següent per a diverses accions:
```sh
cd ~\.config\
nano kglobalshortcutsrc
```
## Quina és la tecla de drecera assignada per activar el control de veu del MyCroft sense un control remot USB de micròfon?
No hi ha cap drecera de teclat assignada al MyCroft. El control remot USB genèric que té un botó de micròfon només activa l'entrada del micròfon en el maquinari del control remot USB. Per a usar el MyCroft cal activar-lo amb la paraula clau «Hey Mycroft».
Per a usar el MyCroft no es requereix cap control remot USB amb micròfon activat en especial, hauria de funcionar qualsevol micròfon que es pugui connectar al dispositiu.
Per a les qüestions i problemes quan no funciona el micròfon, podeu veure: https://mycroft-ai.gitbook.io/docs/using-mycroft-ai/troubleshooting/audio-troubleshooting.
## Com col·laborar i pujar el vostre mapa de teclat personalitat del CEC?
Actualment, el repositori de desenvolupament del domini CEC es pot trobar a https://invent.kde.org/adityam/easycec amb les instruccions sobre com afegir un dispositiu amb un mapa de teclat personalitzat.
## Les aplicacions Android funcionen en el Plasma Bigscreen?
Hi ha projectes com l'[Anbox](https://anbox.io/) que és un Android executant-se dins un contenidor Linux, i usa el nucli del Linux per executar aplicacions per aconseguir un rendiment gairebé natiu. Això es podria potenciar en el futur per tenir aplicacions Android executant-se sobre d'un sistema GNU/Linux amb la plataforma Plasma Bigscreen, però és una tasca complicada, i a data d'*avui* (5 d'agost de 2021) diverses distribucions ja admeten l'Anbox i es pot executar el Plasma Bigscreen en aquestes distribucions.
## Puc executar el Plasma Bigscreen a la meva TV o sintonitzador digital?
Actualment, el Plasma Bigscreen funciona en els tipus de dispositius següents:
* **(Recomanat) Raspberry Pi 4:** Oferim imatges oficials construïdes per a la Raspberry Pi 4 a sobre del KDE Neon.
* **Dispositius postmarketOS:** El postmarketOS és una distribució basada en el Linux Alpine que es pot instal·lar en els telèfons intel·ligents Android i també en SBC com la Raspberry Pi 4 i altres dispositius. Cerqueu el vostre dispositiu a la [llista de dispositius compatibles](https://wiki.postmarketos.org/wiki/Devices) i vegeu què funciona, després podreu seguir la [guia d'instal·lació del pmOS](https://wiki.postmarketos.org/wiki/Installation_guide) per a instal·lar-lo en el vostre dispositiu. La vostra experiència pot variar segons el dispositiu en ús i si useu un dispositiu de la categoria en proves, i **no** necessàriament serà representativa de l'estat actual del Plasma Bigscreen.
## He instal·lat el Plasma Bigscreen, quina és la contrasenya de connexió?
Si heu instal·lat la imatge de referència del KDE Neon per a la Raspberry Pi 4, la contrasenya i el nom d'usuari són «mycroft», i després podeu la contrasenya executant «passwd» des d'un «tty».
## Quin és l'estat del projecte?
Actualment el Plasma Bigscreen està en desenvolupament intens i no està destinat a un ús diari.
---
menu:
main:
name: Instal·lació
weight: 4
sassFiles:
- scss/get.scss
title: Distribucions que ofereixen el Plasma Bigscreen
---
## «rootfs» de referència basada en Neon
![](/img/neon.svg)
Imatge basada en KDE Neon. La pròpia KDE Neon està basada en Ubuntu 20.04 (focal). Aquesta imatge està basada en la branca «dev-unstable» de KDE Neon, i sempre distribueix la darrera versió dels Frameworks, KWin i Plasma Bigscreen de KDE compilats a partir de «git master».
##### Baixada:
* [Raspberry Pi 4](https://sourceforge.net/projects/bigscreen/files/rpi4/beta)
### Instal·lació
Baixeu la imatge, descomprimiu-la i graveu-la a una targeta SD usant `dd` o una eina gràfica. La Raspberry Pi arrencarà automàticament des de la targeta SD.
Per a una guia completa pas a pas, [feu clic aquí](/manual).
## postmarketOS
![](/img/pmOS.svg)
El PostmarketOS (pmOS), és un Alpine Linux preconfigurat que es pot instal·lar en telèfons intel·ligents, SBC i altres dispositius mòbils. Reviseu la [llista de dispositius](https://wiki.postmarketos.org/wiki/Devices) per a veure el progrés per acceptar el vostre dispositiu.
Per a dispositius que no tenen imatges preconstruïdes, cal gravar la seva memòria flaix interna manualment amb la utilitat `pmbootstrap`. Seguiu les instruccions [aquí](https://wiki.postmarketos.org/wiki/Installation_guide). Assegureu-vos també de verificar la pàgina wiki del dispositiu per a trobar més informació quant a què funciona.
[Apreneu-ne més](https://postmarketos.org)
##### Baixada:
* [Dispositius de la comunitat](https://postmarketos.org/download/)
---
konqi: /img/424px-Mascot_konqi-app-internet.png
menu:
main:
parent: community
weight: 2
sassFiles:
- scss/join.scss
title: Uniu-vos al Plasma Bigscreen
---
Si us agradaria col·laborar amb l'impressionant programari lliure per a TV i sintonitzadors digitals, [uniu-vos - sempre hi ha una tasca per a vós](/contributing/)!
### Canals específics del Plasma Bigscreen:
* [![](/img/matrix.svg)Matrix (més actiu)](https://matrix.to/#/#plasma-bigscreen:kde.org)
* [![](/img/telegram.svg)Telegram](https://t.me/plasmabigscreen)
### Canals de projectes relacionats amb el Plasma Bigscreen:
* [![](/img/irc.png)#plasma al Freenode (IRC)](https://kiwiirc.com/nextclient/chat.freenode.net/#plasma)
* [![](/img/mail.svg)Llista de correu de desenvolupament del Plasma](https://mail.kde.org/mailman/listinfo/plasma-devel)
---
jsFiles:
- https://cdn.kde.org/aether-devel/version/kde-org/applications.3e16ae06.js
layout: page
menu:
main:
parent: project
weight: 2
sassFiles:
- scss/screenshots.scss
- scss/components/swiper.scss
screenshots:
- url: /img/pages/screenshots/screenshot-2.png
- url: /img/pages/screenshots/screenshot-3.png
- url: /img/pages/screenshots/screenshot-4.png
- url: /img/pages/screenshots/screenshot-5.png
- url: /img/pages/screenshots/screenshot-6.png
- url: /img/pages/screenshots/screenshot-7.png
- name: Pantalla d'inici del Plasma Bigscreen
url: /img/pages/screenshots/screenshot-8.png
title: Captures de pantalla
---
{{< screenshots name="screenshots" >}}
---
konqi: /img/mascot_20140702_konqui-plasma_wee_0.png
layout: page
menu:
main:
name: Visió
parent: project
weight: 1
title: La nostra visió
---
El Plasma Bigscreen té com a objectiu arribar a ser un sistema complet i de programari lliure per a TV i sintonitzadors digitals.<br /> Està dissenyat per donar als usuaris conscients de la privacitat el control sobre la seva informació i la comunicació.
El Plasma Bigscreen té un enfocament pragmàtic i és inclusiu per al programari de tercers, permetent que l'usuari triï les aplicacions i serveis a usar, mentre proporciona un experiència transparent entre múltiples dispositius.<br />El Plasma Bigscreen implementa estàndards oberts i està desenvolupat en un procés transparent que està obert a la participació de tothom.
---
menu:
main:
weight: 1
title: Plasma Bigscreen
---
---
layout: page
menu:
main:
name: PF
parent: project
weight: 5
title: Preguntas frecuentes
---
## ¡Ayuda! El mando a distancia de mi TV no funciona. ¿Cómo puedo arreglarlo?
Many TV manufacturers require HDMI-CEC mode to be enabled manually, one needs to refer to the TV user guide to figure out how to configure the HDMI-CEC option on their television set. The HDMI-CEC option can be found under various names depending on the TV manufacturers, some for example: (TCL TV: T-Link, Panasonic TV: Viera Link, Samsung TV: Anynet+, Sony TV: Bravia Sync).
Also make sure your Plasma Bigscreen device is actually supported by libcec, [check their supported hardware](https://github.com/Pulse-Eight/libcec#supported-hardware).
## Some buttons on my TV remote are not working, I can’t exit an application or use the back button properly. How do I fix it?
HDMI-CEC on the beta image is in a testing phase. We have only been able to test the functionality on a few selected range of TV sets and have mapped TV remotes on the basis of those working devices. You can map and test your TV remote following a few simple steps of debugging and editing files listed below.
_Test if the KEY is working with HDMI-CEC and extract it’s KEY CODE:_
```sh
cd ~/.config./autostart-scripts/
python3 cec-daemon.py
```
Once the script it running, press the button on your TV remote to extract its KEY CODE, if no KEY CODE is found the KEY might not be part of HDMI-CEC controls enabled on your TV set, refer to the TV User Guide to know which keys are enabled under your TV manufacturers HDMI-CEC implementation.
_Adding the found KEY CODE and mapping it in the CEC daemon:_
```sh
cd ~\.config\autostart-scripts\
nano cec-daemon.py
```
- Locate KEYMAP = {} in the daemon script
- Add your KEY CODE in the following format to the list: “9: u.KEY\_HOMEPAGE”
- In the below example “u.KEY\_HOMEPAGE” is mapped to the home button that is used to exit an application
- “9” being the Key Code
- “u.KEY\_HOMEPAGE” being the action the key should perform
## I have a generic USB remote but it’s missing the home key, how do I exit applications?
Not all generic USB remotes are built alike, therefore we recommend using a tested product like the “Wechip G20 Air Mouse With Microphone Remote”. If in-case you are unable to get your hands on one, you can still map an existing key on the remote.
_Mapping the window close button to a button on a USB remote:_
```sh
cd ~\.config\
nano kglobalshortcutsrc
```
- Find the entry “Window Close” located under `[Kwin]`
- Assign your button to the “Window Close” entry
- Example: `Window Close=Alt+F4\t’YourButtonHere’,Alt+F4\t’YourButtonHere’,Close Window`
## Voice applications do not start on boot and I see a blank screen. What should I do?
Voice applications are only accessible once MyCroft is ready and has started, you will be notified on the top panel when MyCroft has started and is in a ready state.
## How do I exit applications using a external keyboard?
“Alt+F4” is the general shortcut assigned to closing applications using a external keyboard. Custom keys can be assigned to the following file for various actions:
```sh
cd ~\.config\
nano kglobalshortcutsrc
```
## What is the hot key assigned to activate MyCroft voice control without a USB mic remote?
There is no hotkey assigned to MyCroft, the Generic USB remotes that have a mic button only activate the mic input on the USB remote hardware, to use MyCroft one needs to activate it with the hot word “Hey Mycroft”.
To use MyCroft one does not require a USB mic enabled remote specifically, any microphone that can be connected to your device should work.
For issues and troubleshooting your microphone not working one can refer to: https://mycroft-ai.gitbook.io/docs/using-mycroft-ai/troubleshooting/audio-troubleshooting.
## How to contribute & upload your custom keymap for CEC?
Currently the development repository of the CEC daemon can be found at https://invent.kde.org/adityam/easycec with instructions on how to add a device with custom keymap.
## Can Android apps work on Plasma Bigscreen?
There are projects out there like [Anbox](https://anbox.io/) which is Android running inside a Linux container, and use the Linux kernel to execute applications to achieve near-native performance. This could be leveraged in the future to have Android apps running on top of a GNU/Linux system with the Plasma Bigscreen platform but it's a complicated task, and as of *today* (August 5th, 2021) some distributions already support Anbox and you can run Plasma Bigscreen on top of those distributions.
## Can I run Plasma Bigscreen on my TV or setup-box?
Currently, Plasma Bigscreen runs on the following device types:
* **(Recommended) Raspberry Pi 4:** We offer official images built for the Raspberry Pi 4 on top of KDE Neon.
* **postmarketOS devices:** postmarketOS is a distribution based on Alpine Linux that can be installed on Android smartphones but also on SBC's like the Raspberry Pi 4 and other devices. 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 depending on the device in use and when you use a device in the testing category it is **not** necessarily representative of the current state of Plasma Bigscreen.
## I've installed Plasma Bigscreen, what is the login password?
If you've installed the reference KDE Neon image for the Raspberry Pi 4, the password and username are both "mycroft", and you can then change the password afterwards by running "passwd" from a tty.
## What's the state of the project?
Plasma Bigscreen is currently under heavy development and is not intended to be used as a daily driver.
---
menu:
main:
name: Instalar
weight: 4
sassFiles:
- scss/get.scss
title: Distribuciones que ofrecen Plasma Bigscreen
---
## Neon based reference rootfs
![](/img/neon.svg)
Image based on KDE Neon. KDE Neon itself is based upon Ubuntu 20.04 (focal). This image is based on the dev-unstable branch of KDE Neon, and always ships the latest versions of KDE frameworks, KWin and Plasma Bigscreen compiled from git master.
##### Descargar:
* [Raspberry Pi 4](https://sourceforge.net/projects/bigscreen/files/rpi4/beta)
### Instalación
Download the image, uncompress it and flash it to a SD-card using `dd` or a graphical tool. The Raspberry Pi will automatically boot from a SD-Card.
For a complete step-by-step readme, [click here](/manual).
## postmarketOS
![](/img/pmOS.svg)
PostmarketOS (pmOS) is a pre-configured Alpine Linux that can be installed on smartphones, SBC's and other mobile devices. View the [device list](https://wiki.postmarketos.org/wiki/Devices) to see the progress for supporting your device.
For devices that do not have prebuilt images, you will need to flash it manually using the `pmbootstrap` utility. Follow instructions [here](https://wiki.postmarketos.org/wiki/Installation_guide). Be sure to also check the device's wiki page for more information on what is working.
[Learn more](https://postmarketos.org)
##### Descargar:
* [Community Devices](https://postmarketos.org/download/)
---
konqi: /img/424px-Mascot_konqi-app-internet.png
menu:
main:
parent: community
weight: 2
sassFiles:
- scss/join.scss
title: Join Plasma Bigscreen
---
If you'd like to contribute to the amazing free software for TV's and setup-boxes, [join us - we always have a task for you](/contributing/)!
### Canales específicos de Plasma Bigscreen:
* [![](/img/matrix.svg)Matrix (más activo)](https://matrix.to/#/#plasma-bigscreen:kde.org)
* [![](/img/telegram.svg)Telegram](https://t.me/plasmabigscreen)
### Canales de proyectos relacionados con Plasma Bigscreen:
* [![](/img/irc.png)#plasma en Freenode (IRC)](https://kiwiirc.com/nextclient/chat.freenode.net/#plasma)
* [![](/img/mail.svg)Lista de distribución del desarrollo de Plasma](https://mail.kde.org/mailman/listinfo/plasma-devel)
---
jsFiles:
- https://cdn.kde.org/aether-devel/version/kde-org/applications.3e16ae06.js
layout: page
menu:
main:
parent: project
weight: 2
sassFiles:
- scss/screenshots.scss
- scss/components/swiper.scss
screenshots:
- url: /img/pages/screenshots/screenshot-2.png
- url: /img/pages/screenshots/screenshot-3.png
- url: /img/pages/screenshots/screenshot-4.png
- url: /img/pages/screenshots/screenshot-5.png
- url: /img/pages/screenshots/screenshot-6.png
- url: /img/pages/screenshots/screenshot-7.png
- name: Página inicial de Plasma Bigscreen
url: /img/pages/screenshots/screenshot-8.png
title: Capturas de pantalla
---
{{< screenshots name="screenshots" >}}
---
konqi: /img/mascot_20140702_konqui-plasma_wee_0.png
layout: page
menu:
main:
name: Visión
parent: project
weight: 1
title: Nuestra visión
---
Plasma Bigscreen aims to become a complete and open software system for TV's and setup-boxes.<br /> It is designed to give privacy-aware users back control over their information, communication and media.
Plasma Bigscreen takes a pragmatic approach and is inclusive to 3rd party software, allowing the user to choose which applications and services to use, while providing a seamless experience across multiple devices.<br /> Plasma Bigscreen implements open standards and is developed in a transparent process that is open for anyone to participate in.
---
menu:
main:
weight: 1
title: Plasma Bigscreen
---
---
layout: page
menu:
main:
name: FAQ
parent: project
weight: 5
title: Foire aux questions
---
## Help! My TV remote does not work, how do I fix it?
Many TV manufacturers require HDMI-CEC mode to be enabled manually, one needs to refer to the TV user guide to figure out how to configure the HDMI-CEC option on their television set. The HDMI-CEC option can be found under various names depending on the TV manufacturers, some for example: (TCL TV: T-Link, Panasonic TV: Viera Link, Samsung TV: Anynet+, Sony TV: Bravia Sync).
Also make sure your Plasma Bigscreen device is actually supported by libcec, [check their supported hardware](https://github.com/Pulse-Eight/libcec#supported-hardware).
## Some buttons on my TV remote are not working, I can’t exit an application or use the back button properly. How do I fix it?
HDMI-CEC on the beta image is in a testing phase. We have only been able to test the functionality on a few selected range of TV sets and have mapped TV remotes on the basis of those working devices. You can map and test your TV remote following a few simple steps of debugging and editing files listed below.
_Test if the KEY is working with HDMI-CEC and extract it’s KEY CODE:_
```sh
cd ~/.config./autostart-scripts/
python3 cec-daemon.py
```
Once the script it running, press the button on your TV remote to extract its KEY CODE, if no KEY CODE is found the KEY might not be part of HDMI-CEC controls enabled on your TV set, refer to the TV User Guide to know which keys are enabled under your TV manufacturers HDMI-CEC implementation.
_Adding the found KEY CODE and mapping it in the CEC daemon:_
```sh
cd ~\.config\autostart-scripts\
nano cec-daemon.py
```
- Locate KEYMAP = {} in the daemon script
- Add your KEY CODE in the following format to the list: “9: u.KEY\_HOMEPAGE”
- In the below example “u.KEY\_HOMEPAGE” is mapped to the home button that is used to exit an application
- “9” being the Key Code
- “u.KEY\_HOMEPAGE” being the action the key should perform
## I have a generic USB remote but it’s missing the home key, how do I exit applications?
Not all generic USB remotes are built alike, therefore we recommend using a tested product like the “Wechip G20 Air Mouse With Microphone Remote”. If in-case you are unable to get your hands on one, you can still map an existing key on the remote.
_Mapping the window close button to a button on a USB remote:_
```sh
cd ~\.config\
nano kglobalshortcutsrc
```
- Find the entry “Window Close” located under `[Kwin]`
- Assign your button to the “Window Close” entry
- Example: `Window Close=Alt+F4\t’YourButtonHere’,Alt+F4\t’YourButtonHere’,Close Window`
## Voice applications do not start on boot and I see a blank screen. What should I do?
Voice applications are only accessible once MyCroft is ready and has started, you will be notified on the top panel when MyCroft has started and is in a ready state.
## How do I exit applications using a external keyboard?
“Alt+F4” is the general shortcut assigned to closing applications using a external keyboard. Custom keys can be assigned to the following file for various actions:
```sh
cd ~\.config\
nano kglobalshortcutsrc
```
## What is the hot key assigned to activate MyCroft voice control without a USB mic remote?
There is no hotkey assigned to MyCroft, the Generic USB remotes that have a mic button only activate the mic input on the USB remote hardware, to use MyCroft one needs to activate it with the hot word “Hey Mycroft”.
To use MyCroft one does not require a USB mic enabled remote specifically, any microphone that can be connected to your device should work.
For issues and troubleshooting your microphone not working one can refer to: https://mycroft-ai.gitbook.io/docs/using-mycroft-ai/troubleshooting/audio-troubleshooting.
## How to contribute & upload your custom keymap for CEC?
Currently the development repository of the CEC daemon can be found at https://invent.kde.org/adityam/easycec with instructions on how to add a device with custom keymap.
## Can Android apps work on Plasma Bigscreen?
There are projects out there like [Anbox](https://anbox.io/) which is Android running inside a Linux container, and use the Linux kernel to execute applications to achieve near-native performance. This could be leveraged in the future to have Android apps running on top of a GNU/Linux system with the Plasma Bigscreen platform but it's a complicated task, and as of *today* (August 5th, 2021) some distributions already support Anbox and you can run Plasma Bigscreen on top of those distributions.
## Can I run Plasma Bigscreen on my TV or setup-box?
Currently, Plasma Bigscreen runs on the following device types:
* **(Recommended) Raspberry Pi 4:** We offer official images built for the Raspberry Pi 4 on top of KDE Neon.
* **postmarketOS devices:** postmarketOS is a distribution based on Alpine Linux that can be installed on Android smartphones but also on SBC's like the Raspberry Pi 4 and other devices. 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 depending on the device in use and when you use a device in the testing category it is **not** necessarily representative of the current state of Plasma Bigscreen.
## I've installed Plasma Bigscreen, what is the login password?
If you've installed the reference KDE Neon image for the Raspberry Pi 4, the password and username are both "mycroft", and you can then change the password afterwards by running "passwd" from a tty.
## Quel est l'avancement du projet ?
Plasma Bigscreen is currently under heavy development and is not intended to be used as a daily driver.
---
menu:
main:
name: Installer
weight: 4
sassFiles:
- scss/get.scss
title: Distributions offering Plasma Bigscreen
---
## Référence à « rootfs » reposant sur Neon
![](/img/neon.svg)
Image based on KDE Neon. KDE Neon itself is based upon Ubuntu 20.04 (focal). This image is based on the dev-unstable branch of KDE Neon, and always ships the latest versions of KDE frameworks, KWin and Plasma Bigscreen compiled from git master.
##### Télécharger :
* [Raspberry Pi 4](https://sourceforge.net/projects/bigscreen/files/rpi4/beta)
### Installation
Download the image, uncompress it and flash it to a SD-card using `dd` or a graphical tool. The Raspberry Pi will automatically boot from a SD-Card.
For a complete step-by-step readme, [click here](/manual).
## postmarketOS
![](/img/pmOS.svg)
PostmarketOS (pmOS) is a pre-configured Alpine Linux that can be installed on smartphones, SBC's and other mobile devices. View the [device list](https://wiki.postmarketos.org/wiki/Devices) to see the progress for supporting your device.
Pour les appareils n'ayant pas d'images pré construites, vous devrez le flasher manuellement en utilisant l'utilitaire « pmbootstrap ». Veuillez suivre les instructions [ici] (https://wiki.postmarketos.org/wiki/Installation_guide). Veuillez vérifiez également la page wiki de l'appareil pour plus d'informations sur ce qui fonctionne.
[En savoir plus](https://postmarketos.org)
##### Télécharger :
* [Périphériques de la communauté](https://postmarketos.org/download/)
---
jsFiles:
- https://cdn.kde.org/aether-devel/version/kde-org/applications.3e16ae06.js
layout: page
menu:
main:
parent: project
weight: 2
sassFiles:
- scss/screenshots.scss
- scss/components/swiper.scss
screenshots:
- url: /img/pages/screenshots/screenshot-2.png
- url: /img/pages/screenshots/screenshot-3.png
- url: /img/pages/screenshots/screenshot-4.png
- url: /img/pages/screenshots/screenshot-5.png
- url: /img/pages/screenshots/screenshot-6.png
- url: /img/pages/screenshots/screenshot-7.png
- name: Plasma Bigscreen homescreen
url: /img/pages/screenshots/screenshot-8.png
title: Copies d'écran
---
{{< screenshots name="screenshots" >}}
---
konqi: /img/mascot_20140702_konqui-plasma_wee_0.png
layout: page
menu:
main:
name: Vision
parent: project
weight: 1
title: Notre vision
---
Plasma Bigscreen aims to become a complete and open software system for TV's and setup-boxes.<br /> It is designed to give privacy-aware users back control over their information, communication and media.
Plasma Bigscreen takes a pragmatic approach and is inclusive to 3rd party software, allowing the user to choose which applications and services to use, while providing a seamless experience across multiple devices.<br /> Plasma Bigscreen implements open standards and is developed in a transparent process that is open for anyone to participate in.
---
menu:
main:
weight: 1
title: Plasma Bigscreen
---
---
layout: page
menu:
main:
name: FAQ
parent: project