PINE64 - User contributions [en]

PinePhone Software Releases

2022-08-22T10:59:57Z

RainSlide: /* Notes */ Add offical zstd

This page contains a list of all available operating systems for the [[PinePhone]] in alphabetical order, as well as links to other resources.

{{Info|Some releases may not have a good setup for the backlight at low brightness. If configured too low, the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.}}

See [[PinePhone Installation Instructions]] on how to install the operating systems. Please see [[PinePhone Updating Instructions]] for how to update the phone.

== Software Releases ==

=== Multi-distro demo image ===

{{Warning | This is a demo image for testing different OSes before installing a regular image. Attempting to use this image productively is highly discouraged. The kernel is shared across the different OSes and is not updated.}}

This image allow users to try many Linux distributions easily, without having to figure out how to flash them individually and juggle with many microSD cards. Also called megi's 15-in-1 multi boot image.

* Main page: https://xnux.eu/p-boot-demo/
* Git repo: https://megous.com/git/pinephone-multi-boot/
* Forum discussion: [https://forum.pine64.org/showthread.php?tid=11347 15-distro multi-boot image for Pinephone]

==== Download ====

'''Update 2022-01-26, using megi's kernel 5.16.2'''

DD image to SD card and boot. This image is for 16GiB or larger SD cards, also works if flashed to eMMC.

This is also a good build for charging depleted battery. Just boot up this build with power supply connected, keep the PinePhone charging for 3 hours at power down stage.

For more info on this build, please visit its entry the "News" section of its [https://xnux.eu/p-boot-demo/ web page].

* [https://dl.xnux.eu/p-boot-multi-2022-01-26.torrent Download torrent file from author's website]
* [http://dl.xnux.eu/p-boot-multi-2022-01-26/ Download img.zst from author's website] (speed limited to 512KiB/s)
* [http://mirror.uxes.cz/dl.xnux.eu/ Download torrent and img.zst from discord user uxes' mirror]
** '''File name:''' multi.img.zst
** '''SHA-256:''' <span style="word-break: break-all">39915b9d2aa2f33fd78552ac9a0e665c4aef97dd68a9f9a6c76f9fa2f0ac049e</span>
** '''File Size:''' 6.9GiB

Due to its size, download though torrent is suggested by the author on its main page.

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! General
| <code>1111</code>
|-
! sxmo
| <code>user/1111</code>
|-
! Manjaro
| seems to insist on <code>123456</code>
|}

==== Notes ====

{{Info | Note about zstd) archive file (<code>.zst</code>):

On Linux, you may install or compile <code>zstd</code>, then write the image to SD card by piping <code>zstdcat</code> and <code>dd</code>. See the "Installation" section of its [https://xnux.eu/p-boot-demo/ web page] for command examples.

On Windows, instead of the offical [https://github.com/facebook/zstd zstd] command line program, you may use [https://github.com/mcmilk/7-Zip-zstd 7-zip-zstd]. Different installation method is provided in their README. Install 7-Zip-zstd / zstd, extract the disk image file (<code>.img</code>) from the zstd archive, and flash with tools like [https://sourceforge.net/projects/win32diskimager/ Win32 Disk Imager].}}

Also see [[PinePhone Installation Instructions]].

----

=== Arch Linux ARM ===
[[File:Archlinux-logo.png|right|100px]]

(Unofficial) Arch Linux ARM with choice of Phosh UI, Plasma Mobile, sxmo or barebones.
Currently being maintained by the [https://danctnix.org/ DanctNIX] community (GitHub: [https://github.com/DanctNIX/danctnix danctnix], [https://github.com/dreemurrs-embedded dreemurrs-embedded]).

==== Download ====

Get both stable and test builds at [https://github.com/dreemurrs-embedded/Pine64-Arch/releases GitHub releases].

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! Default user
| <code>alarm/123456</code>
|-
! root (barebone only)
| <code>root/root</code>
|}

==== Notes ====

* There are archmobile chat rooms on Matrix ([https://matrix.to/#/#archmobile:kde.org #archmobile:kde.org]) and Telegram ([https://t.me/archmobile @archmobile]).
* Feel free to send us [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls pull requests] and reports [https://github.com/dreemurrs-embedded/Pine64-Arch/issues issues] on [https://github.com/dreemurrs-embedded/Pine64-Arch GitHub].
----

=== ExpidusOS ===

A fork of [https://voidlinux.org Void Linux] with a custom fork of XFCE called [https://github.com/ExpidusOS/genesis Gensis] as the default desktop environment, developed by [https://midstall.com/ Midstall Software].

* [https://expidusos.com ExpidusOS official website]
* [https://wiki.expidusos.com/index.php/Main_Page ExpidusOS Wiki]
* [https://discord.gg/GVfBF2w Midstall Software Discord server]
* GitHub: [https://github.com/ExpidusOS ExpidusOS]

==== Download ====

Check the [https://expidusos.com/download download page] for that latest version, or the [https://build.expidusos.com/ image file list] for all versions, look for the filename that starts with "pinephone".

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! Default user
| <code>expidus/expidus</code>
|}

==== Notes ====

What works, what does not work:

* The ExpidusOS Wiki has a page detailing [https://wiki.expidusos.com/index.php/Device:PinePhone supported features].

How to contribute and report defects:

* Join the [https://discord.gg/GVfBF2w Discord server] or corresponding repo at GitHub ([https://github.com/orgs/ExpidusOS/repositories repo list]).

----

=== Fedora ===
[[File:Fedora-logo.png|right|100px]]

An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and [https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/ some additional packages] to tie it all together.
It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.

* Forum discussion: [https://forum.pine64.org/showthread.php?tid=9347 Fedora + Phosh for PinePhone]
* GitHub: [https://github.com/nikhiljha/pp-fedora-sdsetup nikhiljha/pp-fedora-sdsetup]

==== Download ====

* [https://github.com/nikhiljha/pp-fedora-sdsetup/releases Flashable images]
* [https://github.com/nikhiljha/pp-fedora-sdsetup Build scripts]
* [https://copr.fedorainfracloud.org/coprs/njha/mobile/ Packages (Fedora COPR)]

There is also an FTP server with images build every night @ ftp://pine.warpspeed.dk/nightly/pinephone/ (Mount this with something like Nautilus)

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! GitHub images
| <code>pine/123456</code>
|-
! Nightly images (via FTP)
| <code>pine/1111</code>
|}

==== Notes ====

WiFi, Bluetooth, SMS, Data, Calls all work! There are still a few bugs though, and [https://xnux.eu/devices/pine64-pinephone.html#toc-feature-driver-support-matrix some features don't have driver support yet] on any PinePhone distribution.

Please send your bug reports to [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker]. Be sure to include logs if applicable! Send us pull requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/pulls Github].

----

=== Gentoo ===
[[File:GentooLogo.png|right|100px]]

There are unofficial Gentoo overlays with ebuilds for the PinePhone. There are no images - the image must be built manually, including picking the kernel, bootloader and the desired desktop environment. The ARM64 version of Gentoo has to be selected.

==== Download ====

Overlay locations:

* https://gitlab.com/bingch/gentoo-overlay
* https://github.com/stealthgun/gjdwebserver-overlay

==== Notes ====

The documentation can be found here:

* https://stealthgun.tweakblogs.net/blog/19336/gentoo-on-a-pinephone
* https://wiki.gentoo.org/wiki/User:Dr41nU/PinePhone
* https://wiki.gentoo.org/wiki/PinePhone (incomplete)

{{Info|Please consider cross-compiling the software on the computer. Long compilation times and heat production can lead to a reduced lifespan of the phone.}}

----

=== GloDroid ===

A fully open source port of Android to the PinePhone.

GitHub: [https://github.com/GloDroid/ GloDroid]

==== Download ====

* Stable image: [https://github.com/GloDroid/glodroid_manifest/releases GloDroid]

==== Notes ====

Feature overview:

* Works: WiFi, screen dimming, sound, touchscreen, charging and telephony(partially) works.
* Doesn't work: Bluetooth and GPS

----

=== Kali Linux ===
[[File:Kali-logo.png|right|200px]]

An unofficial [https://www.kali.org Kali Linux] build for PinePhone running with Phosh.
This Kali Linux Phosh build contains only the Phosh GUI and a few other packages (ModemManager, WiFi chip firmware).
Now, Totally depends on The Kali repository. Get [https://github.com/Shubhamvis98/usb-arsenal-pinephone USB Arsenal] for your PinePhone's Kali Linux.

==== Download ====

* [https://github.com/Shubhamvis98/kali-pinephone/releases Kali Phosh]

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! Default user
| <code>kali/8888</code>
|}

==== Notes ====

Installation:

$ unxz -c Kali-PinePhone-{Release}.img.xz | dd of=/dev/{storage_block} bs=1M status=progress
$ growpart /dev/mmcblkX Y
$ e2fsck -y -f /dev/mmcblkXpY
$ resize2fs /dev/mmcblkXpY
# X: Storage Device Y: Partition Number

----

=== LuneOS ===
[[File:Luneos-logo-256.png|right|100px]]

LuneOS is one of the original multi-tasking OS-es that runs on Linux. Based on HP/Palm's webOS, merged with latest technology stack from LG called webOS OSE (a derivative of what LG uses on their Smart TV's), software such as Qt5 and makes use of the Yocto build system.

* [https://www.webos-ports.org/wiki/Main_Page WebOS Ports Wiki]
* [https://webos-ports.org/wiki/Pinephone_Info WebOS-Ports Wiki's Pinephone page]
* GitHub: [https://github.com/webOS-ports WebOS Ports]

==== Download ====

* LuneOS Preview images: [https://github.com/webOS-ports/meta-pine64-luneos/releases Downloads]

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! Default user
| <code>root</code>
|}

==== Notes ====

In order to connect to the device using SSH/SCP via WiFi: You can simply connect via SSH/SCP via WiFi using the PinePhone's IP address on port 22.
----

=== Maemo Leste ===
[[File:Maemoleste-logo.png|right|100px]]

[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices,
originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it. The more well-known devices Maemo supports are the OpenMoko and N900. The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices. You may be interested to learn more about the features in their [https://leste.maemo.org/Leste_FAQ Maemo Leste FAQ].

Maemo 8 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel.
The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK].

==== Download ====

* [http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds]

There is also an [https://github.com/maemo-leste/image-builder image builder], see the wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image]. For current status and instructions, please read their [https://leste.maemo.org/PinePhone PinePhone wiki page].

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! root
| <code>toor</code>
|-
! user
| <code>12345 (lockscreen)</code>
|}

==== Notes ====

Most discussion occurs at [ircs://irc.libera.chat:6697/#maemo-leste <code>#maemo-leste</code> on <code>irc.libera.chat</code>] and [https://talk.maemo.org/showthread.php?t=100192&page=60 this thread].

All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki.

Submit [https://github.com/maemo-leste/bugtracker/issues bug reports] on github.
To track known issues, you may use these search terms:
[https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone],
[https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64].

----

=== Manjaro ARM ===
[[File:Manjaro-logo.svg|right|100px]]

Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile and Phosh desktop environment.

==== Download ====

* Phosh: [https://github.com/manjaro-pinephone/phosh-dev/releases Dev] and [https://github.com/manjaro-pinephone/phosh/releases Stable]
* Plasma Mobile: [https://github.com/manjaro-pinephone/plasma-mobile-dev/releases Dev] and [https://github.com/manjaro-pinephone/plasma-mobile/releases Stable]
* Lomiri: [https://github.com/manjaro-pinephone/lomiri-dev Dev] (unmaintained)

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! Default user
| <code>manjaro/123456</code>
|-
! root
| <code>root/root</code>
|}

==== Notes ====

The installation of the stable images is strongly suggested. The dev images might break frequently.

----

=== Mobian ===
[[File:Debian-logo.png|right|100px]]

An unofficial [https://www.debian.org Debian] build for ARM64 running with Phosh (developed by Purism, uses Wayland instead of Xorg).
The base system is pure Debian, with only the GUI applications and a few others (ModemManager, WiFi chip firmware) being built from modified sources (as well as the kernel and u-boot).
Current version is Debian Bookworm.

==== Download ====

* [https://images.mobian.org/pinephone/ Images]

{{Info|Tow-Boot is required to be able to boot the images, see [https://wiki.mobian-project.org/doku.php?id=install-linux here]!}}

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! Default user
| <code>mobian/1234</code>
|}

==== Notes ====
The development is work in progress. See [https://gitlab.com/mobian1/devices/pinephone-support pinephone-support] for further information. The Mobian wiki can be found [https://wiki.mobian-project.org/ here].

In order to connect to the device using SSH/SCP via WiFi, you need to install SSH on the device. You can do this by executing the following in a shell: "sudo apt-get install ssh", afterwards you can connect via SSH/SCP via WiFi using the PinePhone's IP address on port 22.

----

=== Nemo Mobile ===
[[File:nemo_mobile.png|right|100px]]

Nemo Mobile is the open source build of Sailfish OS with a open source UI called [http://nemomobile.net/glacier-home/ Glacier], [http://nemomobile.net/pages/Hello_manjaro/ based on Manjaro].

==== Download ====

[https://img.nemomobile.net/2022.05/Manjaro-ARM-nemomobile-pinephone-0.9.img.xz Image]

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! Default user
| <code>manjaro/123456</code>
|-
! root
| <code>root/root</code>
|}

==== Notes ====
The website of the Nemo Mobile UX Team can be found [https://nemomobile.net/ here]. Please report bugs regarding the Nemo Mobile UI as [https://github.com/nemomobile-ux/main/issues GitHub issue].

----

=== NixOS ===
[[File:nixos.png|right|100px]]

NixOS is a Linux distribution built on top of the Nix package manager using declarative configuration to allow reliable system upgrades.

==== Download ====
There is no pre-built complete image.
For now users, are expected to follow the instructions in the [https://mobile.nixos.org/getting-started.html Getting Started page],
and [https://mobile.nixos.org/devices/pine64-pinephone.html Project's device page].

==== Notes ====
Project home page: [https://mobile.nixos.org/ Mobile NixOS]
----

=== OpenMandriva Lx ===
[[File:Oma-logo-22042013_300pp.png|right|100px]]

OpenMandriva Lx with Plasma Mobile as UI.

==== Download ====

The official image can be found [https://sourceforge.net/projects/openmandriva/files/release/4.2/RC/Pinephone/ at sourceforge.net].
See [https://www.openmandriva.org/en/news/article/openmandriva-lx-4-3-rc-available-for-testing here] for the offical announcement.

==== Notes ====

{{Info| This image is solely for testing purposes.}}

----

=== openSUSE ===
[[File:SLEM-OS-logo.png|right|100px]]

Our images use the same [https://en.opensuse.org/Portal:Tumbleweed openSUSE Tumbleweed] base as our desktop images,
except what needs to be changed for the PinePhone.
The images include <i>zypper</i> (RPM) as the default package manager,
and have access to virtually the same (open source) software as our desktop repositories,
thanks to the [https://en.opensuse.org/Portal:Factory Factory] ports.
Using [https://en.opensuse.org/SDB:DNF dnf] is possible, if preferred.

==== Download ====

* [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz Phosh] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz.sha256 SHA-256] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz.sha256.asc SHA-256 Signature]
* [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz Plasma Mobile] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz.sha256 SHA-256] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz.sha256.asc SHA-256 Signature]

To verify the images you need to import [https://build.opensuse.org/projects/devel:ARM:Factory:Contrib:PinePhone/public_key our GPG key].
Keep on mind that the first boot may stay on black screen for about a minute - consequent boots should be faster.

You can find install instructions at [https://en.opensuse.org/HCL:PinePhone#Installing_openSUSE_in_a_Pinephone this section] in the openSUSE Wiki.

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! Default user
| <code>pine/1234</code>
|-
! root
| <code>root/linux</code>
|}

==== Notes ====

You can find all information about the releases of the project [https://gitlab.com/slem.os/slem.os/-/blob/master/CHANGELOG.md here].
Detailed information, tips and troubleshooting suggestions are also provided at [https://en.opensuse.org/HCL:PinePhone the openSUSE Wiki].
You will also find information in our wiki on how to report issues (Contributing section).
----

=== postmarketOS ===
[[File:PostmarketOS-logo.png|right|100px]]

postmarketOS extends [https://www.alpinelinux.org/ Alpine Linux] to run on smartphones and other mobile devices.
It offers various user interfaces (Phosh, Plasma Mobile, Sxmo, Plasma Desktop, Gnome 3, Kodi, XFCE4, ...).

==== Download ====
[https://postmarketos.org/download/ Download page]

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! Test images user
| <code>user/147147</code>
|}

==== Notes ====
As of writing, official images are provided with Phosh, Plasma Mobile and Sxmo.
The official images come in two flavors, either as a test image to try out postmarketOS, or with the installer.

When using the installer images (recommended), it is possible to:
* encrypt the installation
* install from the SD card to eMMC

Power users may also create their own image with the distribution's install and development tool <code>pmbootstrap</code>.

See the [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) pine64-pinephone] page of the postmarketOS wiki for details.
----

=== Sailfish OS ===
[[File:Sailfish_logo.png|right|100px]]

[https://sailfishos.org/ Sailfish OS] is a Linux-based operating system based on open source projects such as [https://wiki.merproject.org/wiki/Main_Page Mer], and a closed source UI based on [https://sailfishos.org/wiki/Lipstick Lipstick].

* [https://wiki.merproject.org/wiki/Adaptations/PinePhone64 PinePhone Wiki Page] on Mer Wiki, for both Nemo Mobile and Sailfish OS.
* [https://gitlab.com/pinephone-sailfish-os/linux-kernel/ Linux kernel config repo]
* [https://gitlab.com/sailfishos-porters-ci/dont_be_evil-ci/ Sailfish OS repo]

==== Download ====

'''Flashing script'''

The Sailfish OS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].

The script downloads the image and bootloader from the CI, extracts everything and burns it onto the SD card.
Note: The script will format and erase the SD card!

Instructions:
# Download the flashing script
# Insert a microSD card in your device
# Make the script executable: <code>chmod +x flash-it.sh</code>
# Verify that you have the <code>bsdtar</code> package installed
# Execute it: <code>./flash-it.sh</code>
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).

* When asked where to flash, type 'raw' and it will build the image on your computer. Otherwise define the path /dev/.... to flash to card or internal emmc.

'''username/password'''

Set PIN on initialization.

==== Notes ====

* Sometimes the first run stalls before the tutorial. Reboot and it will start from setting the security pin.
* The homescreen may be locked unless you boot with a sim card inserted. An old expired sim will do. '''If you do not have a SIM card on hands, do NOT set a security code on first boot.'''
* When a screen with a loading circle is displayed, just left/right swipe it away.
* If you're not familiar with Sailfish OS, pay attention to the tutorial - the interface works great, but is not immediately obvious. If you are familiar with it, you can skip the tutorial by touching all 4 corners starting top left.

'''What works, what does not work'''

See the [https://wiki.merproject.org/wiki/Adaptations/PinePhone64#Hardware_Support Hardware Support section] on the Mer Wiki's PinePhone Page.

There is a limited selection of apps available from the Jolla store, the vast majority are hosted on openrepos.net. If the Storeman app for openrepos is not preinstalled, download the RPM and click to install.

'''How to contribute and report defects'''

See the [https://wiki.merproject.org/wiki/Adaptations/PinePhone64#Installation Installation section] on the Mer Wiki's PinePhone Page for compile, build and development.

Git repo links are at the top of this OS section. other repos that may be helpful:

* [https://github.com/sailfish-on-dontbeevil GitHub project page]
* [https://github.com/sailfish-on-dontbeevil/flash-it the repo of the flash-it.sh flashing script]
* [https://build.merproject.org/project/show/nemo:devel:hw:pine:dontbeevil Mer Open Build Service page] ([https://forum.sailfishos.org/t/changes-needed-to-merge-the-project-names-to-sailfish-os/1672 Mer is being assimilated into Sailfish OS] and [https://forum.sailfishos.org/t/obs-shut-down-and-next-steps/1814 OBS is shutting down], also see [https://specs.openstack.org/openstack/fuel-specs/specs/7.0/replace-obs.html OpenStack is replacing OBS with another build system based on Jenkins], if it's related, even OBS come back under Sailfish OS, it will be different.)

See the [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues Sailfish OS wiki] for links to their forum, as well as info required when reporting an issue. See the [https://sailfishos.org/wiki/SailfishOS Sailfish OS wiki main page] for options to contribute to Sailfish OS.

'''Notes'''

OTA is supported: <code>zypper refresh && zypper update</code> as root (<code>devel-su</code> to get root access). Things that need reflash are bootloader specific at the moment. If improvements like [[Crust]] or changes of partition layout are added, then you need to reflash.
----

=== SkiffOS ===
[[File:SkiffOS-Icon-1.png|right|100px]]

Minimal in-memory cross-compiled OS optimized for hosting multiple in parallel Docker containers. Provides the reliability of firmware with the ease-of-use of package managers.

==== Download ====

The repository and instructions can be found [https://github.com/skiffos/SkiffOS/tree/master/configs/pine64/phone here].

==== Notes ====

Upgrade over-the-air via a simple rsync script, or copying 3 files.

Uses the [http://buildroot.org Buildroot] cross-compilation tool for support for all Pine64 boards.

Use configuration packages to configure distro:

{| class="wikitable"
! Package !! Distro
|-
| core/pinephone_neon || KDE Neon via Ubuntu repositories
|-
| core/pinephone_nixos || Nixos Mobile
|-
| core/pinephone_gentoo || Gentoo with Link-time Optimization & KDE Mobile or Phosh
|-
| core/pinephone_ubports || Ubuntu Ports for PinePhone
|-
| core/pinephone_manjaro_kde || Manjaro for PinePhone: KDE variant
|-
| core/pinephone_manjaro_phosh || Manjaro for PinePhone: Phosh variant
|-
| core/pinephone_manjaro_lomiri || Manjaro for PinePhone: Lomiri variant
|}

The boot-up OS is upgraded independently from the containers.

----

=== Slackware ===

[https://arm.slackware.com/ Slackware] is the world's oldest actively developed Linux distribution, providing a modern user land (applications) and Linux Kernel, within a more classic Unix Operating System environment.

==== Download ====

* http://dl.fail.pp.ua/slackware/images/pinephone/

==== Notes ====

Discussion: [https://forum.pine64.org/showthread.php?tid=12181&highlight=slackware+pinephone Thread]

----

=== Ubuntu Touch ===
[[File:Ubports-logo.png|right|100px]]

A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.

Ubuntu touch is a mobile version of Ubuntu developed by the UBports community.
Installation instructions can be found on
[https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone the UBports PinePhone project].
There is also a [https://github.com/goddard/pinephone/ script] to download the latest image and flash to your PinePhone.
In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://devices.ubuntu-touch.io/installer UBports installer] GUI tool.

==== Download ====

[https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone UBports PinePhone project]

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! Default user
| Set during boot
|}

==== Notes ====

Scroll down to the bottom of [https://gitlab.com/ubports/community-ports/pinephone this page], or directly here [https://devices.ubuntu-touch.io/device/pinephone/#deviceOverview] to see which features work.

Contributions and bug reports can be made via. [https://gitlab.com/ubports/community-ports/pinephone UBports gitlab page]. See [https://ubports.com/foundation/sponsors UBports website] for how to donate.

== Tools ==

There are software tools, that can be booted on the PinePhone.

=== JumpDrive ===

JumpDrive can be used to flash the eMMC (and the microSD card), see [[PinePhone Installation Instructions#Using JumpDrive]].

See https://github.com/dreemurrs-embedded/Jumpdrive/releases for the latest image.
Make sure to download the "PinePhone" image and to unpack the archive before flashing.

----

=== Tow-Boot ===
Tow-Boot is a more user-friendly distribution of U-Boot. Can also mount internal storage as USB Mass Storage by holding the volume up button at startup before and during the second vibration and the LED will turn blue if done successfully.

See https://github.com/Tow-Boot/Tow-Boot/releases for the latest image.
Make sure to download the image with pinephoneA64 in the name.

== Factory Test OS ==

On the Braveheart model, there was a postmarketOS based basic Factory Test OS pre-installed on the eMMC.The developer Martijn Braam from postmarketOS has improved the functionality of the image considerably later. Since the 20200501 version, it is able to test all the hardware. It also includes functionality to install a new OS to the eMMC when using with an test image that includes that OS image. The downloadable image just does the hardware tests. Do not flash eMMC to test your device, just dd it to microSD and test from there. New versions are distributed as part of the postmarketOS distribution.

{{Info| The magnetometer test will fail on the new Beta Edition, as the factory image wasn't updated for it yet.}}

Links:
* [https://images.postmarketos.org/pinephone/ Software Images] (download the latest one named like pine-pinephone-yyyyMMdd-factorytestX.img.xz)
* [https://gitlab.com/MartijnBraam/factorytest Git repo]
* [https://gitlab.com/MartijnBraam/factorytest/-/blob/master/README.rst Documentation]

=== Factory-loaded OS builds ===

These are different operating system builds that was preloaded in the factory with testing utility.

Download the build, extract the image and dd it to a 8 GB or larger microSD card, then insert it into the PinePhone.
After power up or reboot, you may perform and complete the test routine, or apply the build from microSD card to eMMC.

All the download links below are direct download from pine64.org.

<div style="overflow: auto;">
{| class="wikitable" style="white-space: nowrap"
! OS
! Download Link
! File Size
! MD5
|-
| Beta Edition
| [https://files.pine64.org/os/PinePhone/BetaEdition/pine64-pinephone-plamo-beta-factorytest.img.xz pine64-pinephone-plamo-beta-factorytest.img.xz]
| 1.78GB
| <code>f16bce93504a52217540ac886863a418</code>
|-
| Mobian
| [https://files.pine64.org/os/PinePhone/Mobian/pine64-pinephone-20201207-factorytest-mobian.img.xz pine64-pinephone-20201207-factorytest-mobian.img.xz]
| 1.41GB
| <code>015be381ff4e650a7fca6d4eaa90d63d</code>
|-
| KDE
| [https://files.pine64.org/os/PinePhone/KDE/pine64-pinephone-20201208-factorytest-kde.img.xz pine64-pinephone-20201208-factorytest-kde.img.xz]
| 2.28GB
| <code>32979ff17b5ec4d358ce99f1aff0c77c</code>
|-
| Manjaro
| [https://files.pine64.org/os/PinePhone/Manjaro/pine64-pinephone-20201013-manjaro-stable-20201018-factory56.img.xz pine64-pinephone-20201013-manjaro-stable-20201018-factory56.img.xz]
| 1.04GB
| <code>4edfd4dceaefdd32a3417c1727161c29</code>
|-
| postmarketOS
| [https://files.pine64.org/os/PinePhone/PostMarketOS/pine64-pinephone-20200726-phosh-v20.05-factory.img.xz pine64-pinephone-20200726-phosh-v20.05-factory.img.xz]
| 517MB
| <code>244093be2f6d728fcbd1d29114607727</code>
|-
| Ubuntu Touch
| [https://files.pine64.org/os/PinePhone/UBPorts/PinePhone-flasher-ubuntu-7b.img.gz PinePhone-flasher-ubuntu-7b.img.gz]
| 1.05GB
| <code>2d7f5271e7a281db8f1b1219bedbe131</code>
|}
</div>

== Installing other ARM64 distributions ==

{{Warning|Distributions not on this page may not even boot after you follow this section. In the best case, they will be barely usable.
This is more for fun, or if you would like to port a new distribution to the PinePhone.}}

{{Hint|'''Note:''' This section uses megi's kernel releases, and not the official ones from Pine64. While it is possible to use the official (and in the future, mainline) kernel, megi provides binary releases, which makes it very easy.}}

General steps:

# Create a boot partition (from 4 MB to about 252 MB) and a root partition (from the end of boot to the end of the card) filesystem on the SD card.
# Format the boot partition with vfat, and the root partition with a supported filesystem like ext4 or f2fs.
# Extract the root filesystem from your distribution's ARM image into the root filesystem on the SD card. Do not copy the partition, copy the files instead (in archive mode, like <code>rsync -ar</code>).
# Edit <code>/etc/fstab</code> to match your partitions.
# Grab megi's kernel from https://xff.cz/kernels/, Follow the instructions in the [https://xff.cz/kernels/README README], which involves copying the kernel modules into the SD card rootfs, and writing u-boot and the bootloader.

If you would like to see examples or specific commands for how to complete these steps, see:
* [https://github.com/nikhiljha/pp-fedora-sdsetup an example for Fedora], current unofficial [#Fedora] release
* [https://xnux.eu/howtos/install-arch-linux-arm.html an example for Arch Linux] by megi

== Other Resources ==

Community
* [[Main_Page#Community_and_Support|Links to the community services]]

Hardware information
* [[PinePhone|General PinePhone hardware info]] in this Pine64 wiki
* Details specific to the Braveheart Edition: [[PinePhone_v1.1_-_Braveheart|PinePhone 1.1 Braveheart hardware details]]
* Details specific to the Community Edition: [[PinePhone_v1.2|PinePhone 1.2 hardware details]]
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here] and the preceding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here]

Other software information
* [https://linux-sunxi.org/Main_Page sunxi community wiki]
* [https://xnux.eu/devices/pine64-pinephone.html megi's feature/driver support matrix]
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)] see demonstration [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube]
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]

Other
* [https://pine64.com/?post_type=product Pine64 shop]
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on Linux distributions and desktop environments on mobile devices]
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing microSD cards]

[[Category:PinePhone]]

PinePhone Software Releases

2022-01-21T08:21:19Z

RainSlide: /* DanctNIX (Arch Linux ARM) */ Use unordered list for '''How to contribute and report defects '''

This page contains a list of all available OS releases for the [[PinePhone]], as well as links to other resources.

See [[PinePhone Installation Instructions]] on how to install the operating systems.<br>
However, if your phone came preloaded with software, Please see [[PinePhone Updating Instructions]].

{{Hint| '''Note:''' Some releases may not have a good setup for the backlight at low brightness.
If configured too low, the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.}}

= Software Releases =

This is a list of OSes that specifically support the PinePhone.
Since PinePhone support is included in Mainline Linux, in principle, any ARM Linux OS can be used if possible required patches are included.

== DanctNIX (Arch Linux ARM) ==
[[File:Archlinux-logo.png|right|100px]]

(Unofficial) Arch Linux ARM with choice of Phosh UI, Plasma Mobile, sxmo or barebones.
Currently being maintained by the [https://danctnix.org/ DanctNIX] community (GitHub: [https://github.com/DanctNIX/danctnix danctnix], [https://github.com/dreemurrs-embedded dreemurrs-embedded]).

* GitHub: [https://github.com/dreemurrs-embedded/Pine64-Arch dreemurrs-embedded/Pine64-Arch]

'''Download location'''

Get both stable and test builds at [https://github.com/dreemurrs-embedded/Pine64-Arch/releases GitHub releases].

'''username/password'''

{| class="wikitable"
! Default user
| <code>alarm/123456</code>
|-
! root
| <code>root/root</code>
|}

'''What works, what does not work'''

Most of the things should works

'''How to contribute and report defects'''

* There are archmobile chat rooms on Matrix ([https://matrix.to/#/#archmobile:kde.org #archmobile:kde.org]) and Telegram ([https://t.me/archmobile @archmobile]).
* You may find the Discord, Matrix and Telegram of DanctNIX community at [https://github.com/DanctNIX/danctnix/blob/master/README.md#channel-list the Channel list section of DanctNIX/README.md], read the [https://github.com/DanctNIX/danctnix/blob/master/docs/CODE_OF_CONDUCT.md Code of Conduct].
* Feel free to send us [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls pull requests] and report [https://github.com/dreemurrs-embedded/Pine64-Arch/issues issues] on [https://github.com/dreemurrs-embedded/Pine64-Arch GitHub].

== ExpidusOS ==

A fork of [https://voidlinux.org Void Linux] with a custom fork of XFCE called [https://github.com/ExpidusOS/genesis Gensis] as the default desktop environment, developed by [https://midstall.com/ Midstall Software].

* [https://expidusos.com ExpidusOS official website]
* [https://wiki.expidusos.com/index.php/Main_Page ExpidusOS Wiki]
* [https://discord.gg/GVfBF2w Midstall Software Discord server]
* GitHub: [https://github.com/ExpidusOS ExpidusOS]

'''Download location'''

Check the [https://expidusos.com/download download page] for that latest version, or the [https://build.expidusos.com/ image file list] for all versions, look for the file name that starts with "pinephone".

'''username/password'''

expidus/expidus

'''What works, what does not work'''

The ExpidusOS Wiki has a page detailing [https://wiki.expidusos.com/index.php/Device:PinePhone supported features].

'''How to contribute and report defects'''

Join the [https://discord.gg/GVfBF2w Discord server] or corresponding repo at GitHub ([https://github.com/orgs/ExpidusOS/repositories repo list]).

== Fedora ==
[[File:Fedora-logo.png|right|100px]]

An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and [https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/ some additional packages] to tie it all together.
It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.

* Forum discussion: [https://forum.pine64.org/showthread.php?tid=9347 Fedora + Phosh for PinePhone]
* GitHub: [https://github.com/nikhiljha/pp-fedora-sdsetup nikhiljha/pp-fedora-sdsetup]

'''Download location'''

* [https://github.com/nikhiljha/pp-fedora-sdsetup/releases Flashable images]
* [https://github.com/nikhiljha/pp-fedora-sdsetup Build scripts]
* [https://copr.fedorainfracloud.org/coprs/njha/mobile/ Packages (Fedora COPR)]

There is also an FTP server with images build every night @ ftp://pine.warpspeed.dk/nightly/pinephone/ (Mount this with something like Nautilus)

'''username/password'''

On github images use:
pine/123456

On Nightly images from FTP use
pine/1111

'''What works, what does not work'''

WiFi, Bluetooth, SMS, Data, Calls all work!

There are still a few bugs though, and [https://xnux.eu/devices/pine64-pinephone.html#toc-feature-driver-support-matrix some features don't have driver support yet] on any PinePhone distribution.

'''How to contribute and report defects'''

Please send your bug reports to [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker].
Be sure to include logs if applicable!
Send us pull requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/pulls Github].

== Gentoo ==
[[File:GentooLogo.png|right|100px]]

{{hint|Please consider cross-compiling the software on the computer.
Long compilation times and heat production can lead to a reduced lifespan of the phone.}}

There are unofficial Gentoo overlays with ebuilds for the PinePhone.
There are no images - you'll be building it yourself, picking which kernel, bootloader and desktop environment you want to use.
You will be using the arm64 version of Gentoo.

'''Documentation'''

* https://stealthgun.tweakblogs.net/blog/19336/gentoo-on-a-pinephone
* https://wiki.gentoo.org/wiki/User:Dr41nU/PinePhone
* https://wiki.gentoo.org/wiki/PinePhone (incomplete)

'''Overlay locations'''

* https://gitlab.com/bingch/gentoo-overlay
* https://github.com/stealthgun/gjdwebserver-overlay

== GloDroid ==

{{Hint|There can be large intervals between release update, so available images may be outdated and do not reflect the state of the current developments.}}

A fully open source port of Android to the PinePhone.

GitHub: [https://github.com/GloDroid/ GloDroid]

'''Download location'''

Stable image (last release at 2021-11-25)

[https://github.com/GloDroid/glodroid_manifest/releases GloDroid]

'''What works, what does not work'''

Works: WiFi, screen dimming, touchscreen and charging work.
Don't work: Bluetooth, Telephony, GPS, Sound

== LuneOS ==
[[File:WebOS-Ports-logo.png|right|100px]]

LuneOS is a open source mobile operating system based on [https://www.webosose.org/ webOS Open Source Edition]([https://github.com/webosose GitHub], previously known as [https://github.com/openwebos Open webOS]) by LG, comes with [https://webos-ports.org/wiki/Luna_Next Luna Next] UI, currently developed by the WebOS Ports community.

* [https://www.webos-ports.org/wiki/Main_Page WebOS Ports Wiki]
* [https://webos-ports.org/wiki/Pinephone_Info WebOS-Ports Wiki's Pinephone page]
* GitHub: [https://github.com/webOS-ports WebOS Ports]

'''Download location'''

* [http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]

It is recommended to use ''bmaptool'', which is faster than dd, and can decompress archived image files on-the-fly.

Syntax is:

bmaptool copy [from] [to]

For example:

bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-177.rootfs.wic.gz /dev/mmcblk0

.wic file can be treated as .img file when flashing. You may rename .wic file to .img when using GUI tools that require file extension to be .img.

== Maemo Leste ==
[[File:Maemoleste-logo.png|right|100px]]

[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices,
originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it.
The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices.

The new version Maemo 8 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel.
The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK].
The current version is Devuan Beowulf (Debian Buster) and has simultaneous support for both Devuan and Debian.

In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository].
To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's build]).
Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.

* [https://maemo-leste.github.io/ Maemo Leste website]
* [https://leste.maemo.org/Main_Page Maemo Leste Wiki]
** [https://leste.maemo.org/PinePhone PinePhone wiki page]
** [https://leste.maemo.org/Leste_FAQ Maemo Leste FAQ]
* GitHub: [https://github.com/maemo-leste maemo-leste]
* Twitter: [https://twitter.com/maemoleste @maemoleste]

'''Download location'''

[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds]. There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].

'''username/password'''

root/toor

You may use <code>sudo</code> directly.

'''What works, what does not work'''

For current status and workarounds, please read their [https://leste.maemo.org/PinePhone PinePhone wiki page].

'''How to contribute and report defects'''

Most discussion occurs at [ircs://irc.libera.chat:6697/#maemo-leste <code>#maemo-leste</code> on <code>irc.libera.chat</code>].
The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback.

All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki.

Submit [https://github.com/maemo-leste/bugtracker/issues bug reports] on github.
To track known issues, you may use these search terms:
[https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone],
[https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64].

Learn about
[https://leste.maemo.org/Development development],
[https://leste.maemo.org/Development/Porting_Packages porting packages],
[https://leste.maemo.org/Development/Building_Packages building packages],
[https://leste.maemo.org/Development/Tasks todo list],
and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian].
Some tasks have funding available.

== Manjaro ARM ==
[[File:Manjaro-logo.svg|right|100px]]

Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.

'''Download location'''

* Phosh: [https://github.com/manjaro-pinephone/phosh Stable] / [https://github.com/manjaro-pinephone/phosh-dev Dev]
* Plasma Mobile: [https://github.com/manjaro-pinephone/plasma-mobile Stable] / [https://github.com/manjaro-pinephone/plasma-mobile-dev Dev]
* Lomiri: [https://github.com/manjaro-pinephone/lomiri-dev Dev] (No longer maintained)

'''username/password'''

{| class="wikitable"
! Default user
| <code>manjaro/123456</code>
|-
! root
| <code>root/root</code>
|}

'''What works, what does not work'''

{{Hint| '''Note:''' At the first boot, the Phosh image will be loaded at a TTY login prompt for multiple minutes.}}

See Manjaro's release announcements on their forum.

'''How to contribute and report defects'''

See the end of the [https://forum.manjaro.org/t/manjaro-arm-beta7-with-phosh-pinephone/58901 announcement].

== Mobian ==
[[File:Debian-logo.png|right|100px]]

An unofficial [https://www.debian.org Debian] build for ARM64 running with Phosh (developed by Purism, uses Wayland instead of Xorg).
The base system is pure Debian, with only the GUI applications and a few others (ModemManager, WiFi chip firmware) being built from modified sources (as well as the kernel and u-boot).
Current version is Debian Bookworm.

'''Download location'''

[https://images.mobian-project.org/pinephone/weekly/ Weekly] /
[https://images.mobian-project.org/pinephone/installer/ Installer] /
[https://images.mobian-project.org/pinephone/ Stable]

Extract the image before installing:

$ gzip -d Downloads/mobian-pinephone-*.img.gz

See the [https://wiki.mobian-project.org/doku.php?id=install project page] for specific installation instructions.

'''username/password'''

mobian/1234

'''What works, what does not work'''

See [https://gitlab.com/mobian1/mobian-recipes/-/blob/master/README.md the project's README file] or [https://wiki.mobian-project.org/doku.php?id=pinephone the wiki] for most up to date status.

Check [https://gitlab.com/groups/mobian1/-/issues bug tracker] for known issues. Questions? Ask on our [https://forum.pine64.org/showthread.php?tid=9016 thread].

'''How to contribute and report defects'''

It is recommended that you log your bug reports in [https://gitlab.com/mobian1/issues the project's issue tracker].
As a general rule, issues with third-party apps (even the default ones) should be reported upstream.
A Mobian issue would be related to getting the hardware to work on the PinePhone,
but if unsure where the issue should be reported just open a ticket or ask.
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/mobian1 Gitlab].

'''Notes'''

See [https://wiki.mobian-project.org/doku.php?id=start the wiki] for additional information regarding screen resolution, USB networking, WiFi hotspot, Chatty and the repository.

== Multi-distro demo image ==

{{Warning | This is a demo image for testing different OSes before installing a regular image. Attempting to use this image productively is highly discouraged. The kernel is shared across the different OSes and is not updated.}}

This image allow users to try many of the above Linux distributions easily, without having to figure out how to flash them individually and juggle with many microSD cards. Also called megi's 15-in-1 multi boot image.

* Main page: https://xnux.eu/p-boot-demo/
* Git repo: https://megous.com/git/pinephone-multi-boot/
* Forum discussion: [https://forum.pine64.org/showthread.php?tid=11347 UPDATED (June 2021): 17-distro multi-boot image for Pinephone (incl. 3GiB variant)]

'''Update 2021-06-02, using megi's kernel 5.13-rc4'''

DD image to SD card and boot. This image is for 16GiB or larger SD cards, also works if flashed to eMMC.

This is also a good build for charging depleted battery. Just boot up this build with power supply connected, keep the PinePhone charging for 3 hours at power down stage.

For more info on this build, please visit its entry the "News" section of its [https://xnux.eu/p-boot-demo/ web page].

* [http://dl.xnux.eu/p-boot-multi-2021-06-02.torrent Download torrent file from author's website]
* [http://dl.xnux.eu/p-boot-multi-2021-06-02/ Download img.zst from author's website] (speed limited to 512KiB/s)
* [http://mirror.uxes.cz/dl.xnux.eu/ Download torrent and img.zst from discord user uxes' mirror]
** '''File name:''' multi.img.zst
** '''SHA-256:''' <span style="word-break: break-all">9b099cdfece3ba862348ca32af6c51a41a1d161b1d897f9928ae8be3c824a0b6</span>
** '''File Size:''' 6.57GiB

* [https://files.pine64.org/os/PinePhone/Multi/p-boot-multi-2021-06-02.img.gz Direct download img.gz from pine64.org] (re-zipped from zstd to gzip)
** '''File name:''' p-boot-multi-2021-06-02.img.gz
** '''MD5:''' 2abdaafb01dd7519f678b5a7c6538493
** '''File Size:''' 6.8GB

Due to its size, download though torrent is suggested by the author on its main page.

{{hint | '''Note about .zst archive file:'''

On Linux, you may install or compile <code>zstd</code>, and write the image to SD card by using <code>zstdcat</code> and <code>dd</code>. See the "Installation" section of its [https://xnux.eu/p-boot-demo/ web page] for command examples.

On Windows, you may use [https://github.com/mcmilk/7-Zip-zstd 7-zip-zstd], it provides different installation method in the README.md.Install and extract the .img file from the zst archive, and flash with tools like [https://sourceforge.net/projects/win32diskimager/ Win32 Disk Imager].}}

Also see [[PinePhone Installation Instructions]].

'''username/password'''

All passwords, including root passwords, are <code>1111</code>.
sxmo username is <code>user</code>.

== Nemo Mobile ==
[[File:nemo_mobile.png|right|100px]]

Nemo Mobile is the open source build of Sailfish OS with a open source UI called [http://nemomobile.net/glacier-home/ Glacier] ([https://wiki.merproject.org/wiki/Nemo/Glacier Mer Wiki]), [http://nemomobile.net/pages/Hello_manjaro/ based on Manjaro].

* Website: [https://nemomobile.net/ Nemo Mobile UX team]
* [https://wiki.merproject.org/wiki/Nemo Mer Wiki page]

'''Download location'''

See the [https://nemomobile.net/installation/ installation page] on their website for the newest release and installation guides.

'''What works, what does not work'''

Development is now moving very fast after rebasing. For the current devel image, Wifi, SMS and Bluetooth works.

'''How to contribute and report defects'''

For the Nemo Mobile UX itself:
* GitHub issues: https://github.com/nemomobile-ux/main/issues

For hardware:
* GitHub issues: https://github.com/neochapay/nemo-device-dont_be_evil/issues

== NixOS ==
[[File:nixos.png|right|100px]]

NixOS support is handled through the Mobile NixOS project.

* Project home page: [https://mobile.nixos.org/ Mobile NixOS]
* PinePhone device page: [https://mobile.nixos.org/devices/pine64-pinephone.html Pine64 PinePhone — Mobile NixOS]
* GitHub: [https://github.com/NixOS/mobile-nixos NixOS/mobile-nixos]

There is no pre-built complete image.
For now users, are expected to follow the instructions in the [https://mobile.nixos.org/getting-started.html Getting Started page],
and [https://mobile.nixos.org/devices/pine64-pinephone.html Project's device page].

'''What works, what does not work'''

Currently, it boots, it's just as compatible as the Android-based devices are with Mobile NixOS.
It even supports a bit more since it can use WiFi.

Support for all of the hardware will be coming, this project is a breadth-first work, where the work spans multiple devices in parallel.

'''How to contribute and report defects'''

On [https://github.com/NixOS/mobile-nixos/issues the project's repository].
Please specify that you are using a PinePhone when reporting issues.
Details about contributions and donations are on the [https://nixos.org/nixos/community.html NixOS website].

== OpenMandriva Lx ==
[[File:Oma-logo-22042013_300pp.png|right|100px]]

{{Hint| '''Note:''' This image is solely for testing purposes.}}

OpenMandriva Lx with Plasma Mobile as UI.

'''Download location'''

The official image can be found [https://sourceforge.net/projects/openmandriva/files/release/4.2/RC/Pinephone/ at sourceforge.net].
See [https://www.openmandriva.org/en/news/article/openmandriva-lx-4-3-rc-available-for-testing here] for the offical announcement.

'''What works, what does not work'''

From the [https://www.openmandriva.org/en/news/article/openmandriva-lx-4-3-rc-available-for-testing 4.3 announcement],
in future updates (4.3 and later), "Phone calls are working, and we have rewritten the camera app to be far more useful".

== openSUSE ==
[[File:SLEM-OS-logo.png|right|100px]]

Our images use the same [https://en.opensuse.org/Portal:Tumbleweed openSUSE Tumbleweed] base as our desktop images,
except what needs to be changed for the PinePhone.
The images include <i>zypper</i> (RPM) as the default package manager,
and have access to virtually the same (open source) software as our desktop repositories,
thanks to the [https://en.opensuse.org/Portal:Factory Factory] ports.
Using [https://en.opensuse.org/SDB:DNF dnf] is possible, if preferred.

'''Download links'''

* [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz Phosh] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz.sha256 SHA-256] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz.sha256.asc SHA-256 Signature]
* [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz Plasma Mobile] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz.sha256 SHA-256] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz.sha256.asc SHA-256 Signature]

To verify the images you need to import [https://build.opensuse.org/projects/devel:ARM:Factory:Contrib:PinePhone/public_key our GPG key].
Keep on mind that the first boot may stay on black screen for about a minute - consequent boots should be faster.

You can find install instructions at [https://en.opensuse.org/HCL:PinePhone#Installing_openSUSE_in_a_Pinephone this section] in the openSUSE Wiki.

'''Username/Password'''

The login credentials are pine/1234 and root/linux.
Change (or disable) the root password once you are set up.

'''What works and what does not work'''

You can find all information about the releases of the project [https://gitlab.com/slem.os/slem.os/-/blob/master/CHANGELOG.md here].
Detailed information, tips and troubleshooting suggestions are also provided at [https://en.opensuse.org/HCL:PinePhone the openSUSE Wiki].
You will also find information in our wiki on how to report issues (Contributing section).

== postmarketOS ==
[[File:PostmarketOS-logo.png|right|100px]]

postmarketOS extends [https://www.alpinelinux.org/ Alpine Linux] to run on smartphones and other mobile devices.
It offers various user interfaces (Phosh, Plasma Mobile, Sxmo, Plasma Desktop, Gnome 3, Kodi, XFCE4, ...).

As of writing, official images are provided with Phosh, Plasma Mobile and Sxmo.
The official images come in two flavors, either as a test image to try out postmarketOS, or with the installer.

When using the installer images (recommended), it is possible to:
* encrypt the installation
* install from the SD card to eMMC

Power users may also create their own image with the distribution's install and development tool <code>pmbootstrap</code>.

Please read the detailed [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation installation instructions] in the wiki.

'''Download location'''

* [https://postmarketos.org/download/ Download page]
* [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation Flashing instructions]

'''Username/password'''

* Test images: user/147147
* When using the installer images or building an image with pmbootstrap, you set your own username and password.
** The Phosh and Plasma Mobile lock screens only support numeric keyboard, so you should '''only use numbers''' in your password.

'''What works, what does not work'''

See the [https://gitlab.com/postmarketOS/pmaports/-/issues?label_name%5B%5D=device-pine64-pinephone issue tracker].

'''How to contribute and report defects'''

[https://gitlab.com/postmarketOS/pmaports/-/issues?label_name%5B%5D=device-pine64-pinephone postmarketOS issue tracker] for PinePhone support.
See [https://wiki.postmarketos.org/wiki/Contributing postmarketOS wiki] for options to contribute.

== PureOS ==
[[File:Pureos.png|right|100px]]

{{Warning|This project is no longer under development and has been abandoned. Use [https://wiki.pine64.org/wiki/PinePhone_Software_Releases#Mobian Mobian] instead}}

{{Hint|There is no prebuilt image, you'll need a Linux environment and build the image yourself.}}

[https://www.pureos.net/ PureOS] is a user friendly, secure and freedom respecting GNU/Linux distribution based on Debian and GNOME developed by the Purism community.

* [https://tracker.pureos.net/w/ PureOS Wiki], no PinePhone page there
* Mobile-optimized apps list from the [https://tracker.pureos.net/w/pureos/mobile_optimized_apps/ Software Center in PureOS] and [https://tracker.pureos.net/w/pureos/3rd-party_mobile_optimized_apps/ 3rd party repos]
* [https://github.com/rufferson/pureos-pinephone current PinePhone PureOS repo], A script to convert Librem5 PureOS to PinePhone Pure-OS

'''Download location'''

Use [https://raw.githubusercontent.com/rufferson/pureos-pinephone/master/build_image.sh the convert script] to download and build the image from u-boot, PinePhone linux kernel and Librem5 PureOS.

Also see:
* [https://forums.puri.sm/t/successful-installation-of-pureos-on-pinephone/8741/12 Successful installation of PureOS on PinePhone - PureOS - Purism community]
* The PureOS section of [https://www.ruff.mobi/go/mobi/pine.html PinePhone page] on ruff.mobi
* An [https://gitlab.com/a-wai/debos-pinephone archived repo] for PureOS on PinePhone
* A [https://mozzwald.com/pp/ file list] with [https://mozzwald.com/pp/pureos-pinephone-build-instructions.txt pureos pinephone build instructions] on mozzwald.com

== Sailfish OS ==
[[File:Sailfish_logo.png|right|100px]]

[https://sailfishos.org/ Sailfish OS] is a Linux-based operating system based on open source projects such as [https://wiki.merproject.org/wiki/Main_Page Mer], and a closed source UI based on [https://sailfishos.org/wiki/Lipstick Lipstick].

* [https://wiki.merproject.org/wiki/Adaptations/PinePhone64 PinePhone Wiki Page] on Mer Wiki, for both Nemo Mobile and Sailfish OS.
* [https://gitlab.com/pinephone-sailfish-os/linux-kernel/ Linux kernel config repo]
* [https://gitlab.com/sailfishos-porters-ci/dont_be_evil-ci/ Sailfish OS repo]

'''Download location'''

'''Flashing script'''

The Sailfish OS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].

The script downloads the image and bootloader from the CI, extracts everything and burns it onto the SD card.
Note: The script will format and erase the SD card!

Instructions:
# Download the flashing script
# Insert a microSD card in your device
# Make the script executable: <code>chmod +x flash-it.sh</code>
# Verify that you have the <code>bsdtar</code> package installed
# Execute it: <code>./flash-it.sh</code>
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).

* When asked where to flash, type 'raw' and it will build the image on your computer. Otherwise define the path /dev/.... to flash to card or internal emmc.

'''username/password'''

Set PIN on initialization.

* Sometimes the first run stalls before the tutorial. Reboot and it will start from setting the security pin.
* The homescreen may be locked unless you boot with a sim card inserted. An old expired sim will do. '''If you do not have a SIM card on hands, do NOT set a security code on first boot.'''
* When a screen with a loading circle is displayed, just left/right swipe it away.
* If you're not familiar with Sailfish OS, pay attention to the tutorial - the interface works great, but is not immediately obvious. If you are familiar with it, you can skip the tutorial by touching all 4 corners starting top left.

'''What works, what does not work'''

See the [https://wiki.merproject.org/wiki/Adaptations/PinePhone64#Hardware_Support Hardware Support section] on the Mer Wiki's PinePhone Page.

There is a limited selection of apps available from the Jolla store, the vast majority are hosted on openrepos.net. If the Storeman app for openrepos is not preinstalled, download the RPM and click to install.

'''How to contribute and report defects'''

See the [https://wiki.merproject.org/wiki/Adaptations/PinePhone64#Installation Installation section] on the Mer Wiki's PinePhone Page for compile, build and development.

Git repo links are at the top of this OS section. other repos that may be helpful:

* [https://github.com/sailfish-on-dontbeevil GitHub project page]
* [https://github.com/sailfish-on-dontbeevil/flash-it the repo of the flash-it.sh flashing script]
* [https://build.merproject.org/project/show/nemo:devel:hw:pine:dontbeevil Mer Open Build Service page] ([https://forum.sailfishos.org/t/changes-needed-to-merge-the-project-names-to-sailfish-os/1672 Mer is being assimilated into Sailfish OS] and [https://forum.sailfishos.org/t/obs-shut-down-and-next-steps/1814 OBS is shutting down], also see [https://specs.openstack.org/openstack/fuel-specs/specs/7.0/replace-obs.html OpenStack is replacing OBS with another build system based on Jenkins], if it's related, even OBS come back under Sailfish OS, it will be different.)

See the [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues Sailfish OS wiki] for links to their forum, as well as info required when reporting an issue. See the [https://sailfishos.org/wiki/SailfishOS Sailfish OS wiki main page] for options to contribute to Sailfish OS.

'''Notes'''

OTA is supported: <code>zypper refresh && zypper update</code> as root (<code>devel-su</code> to get root access). Things that need reflash are bootloader specific at the moment. If improvements like [[Crust]] or changes of partition layout are added, then you need to reflash.
== Slackware ==

Unofficial slackware images with xfce for the pinephone

Discussion thread: [https://forum.pine64.org/showthread.php?tid=12181&highlight=slackware+pinephone Thread]

Download link: http://dl.fail.pp.ua/slackware/images/pinephone/
== SkiffOS ==
[[File:SkiffOS-Icon-1.png|right|100px]]

Minimal in-memory cross-compiled OS optimized for hosting multiple in parallel Docker containers.

Provides the reliability of firmware with the ease-of-use of package managers.

Upgrade over-the-air via a simple rsync script, or copying 3 files.

Uses the [http://buildroot.org Buildroot] cross-compilation tool for support for all Pine64 boards.

Use configuration packages to configure distro:

{| class="wikitable"
! Package !! Distro
|-
| core/pinephone_neon || KDE Neon via Ubuntu repositories
|-
| core/pinephone_nixos || Nixos Mobile
|-
| core/pinephone_gentoo || Gentoo with Link-time Optimization & KDE Mobile or Phosh
|-
| core/pinephone_ubports || Ubuntu Ports for PinePhone
|-
| core/pinephone_manjaro_kde || Manjaro for PinePhone: KDE variant
|-
| core/pinephone_manjaro_phosh || Manjaro for PinePhone: Phosh variant
|-
| core/pinephone_manjaro_lomiri || Manjaro for PinePhone: Lomiri variant
|}

The boot-up OS is upgraded independently from the containers.

'''Download location'''

The repository and instructions can be found [https://github.com/skiffos/SkiffOS/tree/master/configs/pine64/phone here].

== Sxmo ==

A collection of Suckless programs to create a mobile UI. Based on postmarketOS.

'''Download location'''

Sxmo images can be found [https://images.postmarketos.org/bpo/ here] (in the ''/pine64-pinephone/sxmo/'' sections respectively).

'''username/password'''

user/147147

'''How to contribute and report defects'''

Contributing information is listed [https://man.sr.ht/~anjan/sxmo-docs-stable/CONTRIBUTING.md here].

== Ubuntu Touch ==
[[File:Ubports-logo.png|right|100px]]

A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.

Ubuntu touch is a mobile version of Ubuntu developed by the UBports community.
Installation instructions can be found on
[https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone the UBports PinePhone project].
There is also a [https://github.com/goddard/pinephone/ script] to download the latest image and flash to your PinePhone.
In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://devices.ubuntu-touch.io/installer UBports installer] GUI tool.

'''Download location'''

[https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone UBports PinePhone project]

'''username/password'''

Set up during boot

'''What works, what does not work'''

Scroll down to the bottom of [https://gitlab.com/ubports/community-ports/pinephone this page], or directly here [https://devices.ubuntu-touch.io/device/pinephone/#deviceOverview]

'''How to contribute and report defects'''

See [https://gitlab.com/ubports/community-ports/pinephone UBports gitlab page].
See [https://ubports.com/foundation/sponsors UBports website] for how to donate.

= Tools =

There are software tools, that can be booted on the PinePhone.

== JumpDrive ==

JumpDrive can be used to flash the eMMC (and the microSD card), see [[PinePhone Installation Instructions#Using JumpDrive]].

See https://github.com/dreemurrs-embedded/Jumpdrive/releases for the latest image.
Make sure to download the "PinePhone" image and to unpack the archive before flashing.

= Factory Test OS =

{{Hint|'''Note:''' The magnetometer test will fail on the new Beta Edition, as the factory image wasn't updated for it yet.}}

On the Braveheart model, there was a postmarketOS based basic Factory Test OS pre-installed on the eMMC.
The developer Martijn Braam from postmarketOS has improved the functionality of the image considerably later.
Since the 20200501 version, it is able to test all the hardware.
It also includes functionality to install a new OS to the eMMC when using with an test image that includes that OS image.
The downloadable image just does the hardware tests.
Do not flash eMMC to test your device, just dd it to microSD and test from there.
New versions are distributed as part of the postmarketOS distribution.

Links:
* [https://images.postmarketos.org/pinephone/ Software Images] (download the latest one named like pine-pinephone-yyyyMMdd-factorytestX.img.xz)
* [https://gitlab.com/MartijnBraam/factorytest Git repo]
* [https://gitlab.com/MartijnBraam/factorytest/-/blob/master/README.rst Documentation]

== Factory-loaded OS builds ==

These are different operating system builds that was preloaded in the factory with testing utility.

Download the build, extract the image and dd it to a 8 GB or larger microSD card, then insert it into the PinePhone.
After power up or reboot, you may perform and complete the test routine, or apply the build from microSD card to eMMC.

All the download links below are direct download from pine64.org.

<div style="overflow: auto;">
{| class="wikitable" style="white-space: nowrap"
! OS
! Download Link
! File Size
! MD5
|-
| Beta Edition
| [https://files.pine64.org/os/PinePhone/BetaEdition/pine64-pinephone-plamo-beta-factorytest.img.xz pine64-pinephone-plamo-beta-factorytest.img.xz]
| 1.78GB
| <code>f16bce93504a52217540ac886863a418</code>
|-
| Mobian
| [https://files.pine64.org/os/PinePhone/Mobian/pine64-pinephone-20201207-factorytest-mobian.img.xz pine64-pinephone-20201207-factorytest-mobian.img.xz]
| 1.41GB
| <code>015be381ff4e650a7fca6d4eaa90d63d</code>
|-
| KDE
| [https://files.pine64.org/os/PinePhone/KDE/pine64-pinephone-20201208-factorytest-kde.img.xz pine64-pinephone-20201208-factorytest-kde.img.xz]
| 2.28GB
| <code>32979ff17b5ec4d358ce99f1aff0c77c</code>
|-
| Manjaro
| [https://files.pine64.org/os/PinePhone/Manjaro/pine64-pinephone-20201013-manjaro-stable-20201018-factory56.img.xz pine64-pinephone-20201013-manjaro-stable-20201018-factory56.img.xz]
| 1.04GB
| <code>4edfd4dceaefdd32a3417c1727161c29</code>
|-
| postmarketOS
| [https://files.pine64.org/os/PinePhone/PostMarketOS/pine64-pinephone-20200726-phosh-v20.05-factory.img.xz pine64-pinephone-20200726-phosh-v20.05-factory.img.xz]
| 517MB
| <code>244093be2f6d728fcbd1d29114607727</code>
|-
| Ubuntu Touch
| [https://files.pine64.org/os/PinePhone/UBPorts/PinePhone-flasher-ubuntu-7b.img.gz PinePhone-flasher-ubuntu-7b.img.gz]
| 1.05GB
| <code>2d7f5271e7a281db8f1b1219bedbe131</code>
|}
</div>

= Installing other ARM64 distributions =

{{Warning|Distributions not on this page may not even boot after you follow this section. In the best case, they will be barely usable.
This is more for fun, or if you would like to port a new distribution to the PinePhone.}}

{{Hint|'''Note:''' This section uses megi's kernel releases, and not the official ones from Pine64. While it is possible to use the official (and in the future, mainline) kernel, megi provides binary releases, which makes it very easy.}}

General steps:

# Create a boot partition (from 4 MB to about 252 MB) and a root partition (from the end of boot to the end of the card) filesystem on the SD card.
# Format the boot partition with vfat, and the root partition with a supported filesystem like ext4 or f2fs.
# Extract the root filesystem from your distribution's ARM image into the root filesystem on the SD card. Do not copy the partition, copy the files instead (in archive mode, like <code>rsync -ar</code>).
# Edit <code>/etc/fstab</code> to match your partitions.
# Grab megi's kernel from https://xff.cz/kernels/, Follow the instructions in the [https://xff.cz/kernels/README README], which involves copying the kernel modules into the SD card rootfs, and writing u-boot and the bootloader.

If you would like to see examples or specific commands for how to complete these steps, see:
* [https://github.com/nikhiljha/pp-fedora-sdsetup an example for Fedora], current unofficial [#Fedora] release
* [https://xnux.eu/howtos/install-arch-linux-arm.html an example for Arch Linux] by megi

= Other Resources =
Community
* [[Main_Page#Community_and_Support|Links to the community services]]

Hardware information
* [[PinePhone|General PinePhone hardware info]] in this Pine64 wiki
* Details specific to the Braveheart Edition: [[PinePhone_v1.1_-_Braveheart|PinePhone 1.1 Braveheart hardware details]]
* Details specific to the Community Edition: [[PinePhone_v1.2|PinePhone 1.2 hardware details]]
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here] and the preceding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here]

Other software information
* [https://linux-sunxi.org/Main_Page sunxi community wiki]
* [https://xnux.eu/devices/pine64-pinephone.html megi's feature/driver support matrix]
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)] see demonstration [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube]
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]

Other
* [https://pine64.com/?post_type=product Pine64 shop]
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on Linux distributions and desktop environments on mobile devices]
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing microSD cards]

[[Category:PinePhone]]

Main Page

2022-01-21T07:08:11Z

RainSlide: Add a comma; adjust the note in Chat platforms; apply two space after period, won't affect output and looks better in wiki source code?

PINE64 is a community-driven company focused on creating high-quality, low-cost ARM devices and, more recently, RISC-V devices for individuals and businesses around the globe. PINE64 made its debut with the [[PINE A64|PINE A64]] single-board computer, which successfully launched on Kickstarter in 2015. PINE64 has since released a multitude of other devices, including both development boards and end-user devices.

PINE64 has a large, diverse and active community, and offers a variety of resources for hobbyists and businesses to successfully leverage various PINE64 products. To become connected and involved with the community, please see [[Main Page#Community and Support|Community and Support]] for a list of available channels and chat platforms. To learn more about PINE64, please visit the [https://www.pine64.org/ PINE64 website] and the [https://www.pine64.com/ PINE64 store]'''.

For information about PINE64 branding, including the usage of the PINE64 logo in non-commercial and other applications, please read the [https://wiki.pine64.org/wiki/PINE64_brand_and_logo article about our brand and logo].

= Devices =

[[File:Marchupdate-1024x594.jpg|thumb|upright=1.2|[[Pinebook Pro]] (left) and [[PinePhone]] (right)]]

You can learn more about the following ARM and RISC-V devices manufactured by PINE64:

* Phones: '''[[PinePhone]]''' and '''[[PinePhone Pro]]'''
* Phone accessories: '''[[PinePhone (Pro) Add-ons]]''' and '''[[PinePhone (Pro) Keyboard]]'''
* Tablets: '''[[PineNote]]''' and '''[[PineTab]]'''
* Smartwatch: '''[[PineTime]]'''
* Laptops: '''[[Pinebook]]''', '''[[Pinebook Pro]]''' and '''[[Pinebook Pro Dock|Pinebook Pro Docking station]]'''
* Single-board computers: '''[[Quartz64]]''', '''[[ROCKPro64]]''', '''[[ROCK64]]''', '''[[PINE A64]]''', '''[[PINE A64-LTS/SOPine|PINE A64-LTS]]''' and '''[[PINE H64]]'''
* Clusters and modules: '''[[Clusterboard]]''', '''[[SOPine]]''', '''[[SOPine Baseboard]]''', '''[[SOEdge]]''' and '''[[SOQuartz]]'''
* IP camera: '''[[PineCube]]'''
* Makerspace: '''[[Pinecil]]''', '''[[PinePower]]''', '''[[PineCone]]''' and '''[[Pinedio]]'''

= Community and Support =

Community collaboration and support is focused around the chat platforms and forums described below. As an example of the collaborative efforts of the community, recent activity has resulted in drafting a [[PineFlash|proposal]] for a new flash-based storage device. See [https://www.pine64.org/gettings-started/ Getting Started | PINE64] for tips about how to get started with the PINE64 community.

== Chat Platforms ==

PINE64 has a large and very active community. Community discussion takes place on a variety of chat platforms, which are all bridged together so the messages sent via one platform are sent to all other platforms automatically. The other networks and their users are represented by P64ProtocolBot.

{{hint|PINE64 community is not some always responding, restless commercial customer service, or some sort of almighty existence that can resolve all your problems. When participating in community discussions, please be patient and do not expect questions to be answered immediately, certainly, or currently.
* The activity of community members varies depending on the time of day and the number of active users.
* Whether your questions will be answered & whether the answers are right and definitive, depends on the information you provide, and, after all, difficulty of your questions & community members' ability.
* Read [http://www.catb.org/~esr/faqs/smart-questions.html How To Ask Questions The Smart Way] to learn more.}}

The community chat platforms are the following:
* '''Discord''': Use the [https://discordapp.com/invite/DgB7kzr invite link]. All channels are available.
* '''IRC''': The server is <i>irc.pine64.org</i>. Use <code>/list</code> command or the table below to see the full list of channels.
* '''Matrix and Telegram''': See the table below.

{| class="wikitable"
! Channel !! Matrix !! Telegram !! IRC
|-
| PINE64 News
| [https://app.element.io/#/room/#pine64-announcements:matrix.org #pine64-announcements:matrix.org]
| [https://t.me/PINE64_News @PINE64_News]
| Unavailable
|-
| General PINE64 chat
| [https://app.element.io/#/room/#pine64:matrix.org #pine64:matrix.org]
| [https://t.me/mtrx_pine64 @mtrx_pine64]
| #pine64
|-
| PINE A64(+), A64-LTS & SOPine
| [https://app.element.io/#/room/#pine64sopine:matrix.org #pine64sopine:matrix.org]
| [https://t.me/pine64sopine @pine64sopine]
| #lts-sopine
|-
| ROCK64 / ROCKPro64
| [https://app.element.io/#/room/#rock64:matrix.org #rock64:matrix.org]
| [https://t.me/mtrx_rock64 @mtrx_rock64]
| #rock64
|-
| Quartz64
| [https://app.element.io/#/room/#quartz64:matrix.org #quartz64:matrix.org]
| [https://t.me/joinchat/Vq50DXkH31e0_i-f Quartz64]
| #quartz64
|-
| Quartz64 Development
| [https://app.element.io/#/room/#quartz64-dev:matrix.org #quartz64-dev:matrix.org]
| [https://t.me/q64dev @q64dev]
| #quartz64-dev
|-
| Pinebook and Pinebook Pro
| [https://app.element.io/#/room/#pinebook:matrix.org #pinebook:matrix.org]
| [https://t.me/mtx_pinebook @mtx_pinebook]
| #pinebook
|-
| PinePhone
| [https://app.element.io/#/room/#pinephone:matrix.org #pinephone:matrix.org]
| [https://t.me/pinephone @pinephone]
| #pinephone
|-
| PineNote
| [https://app.element.io/#/room/#pinenote:matrix.org #pinenote:matrix.org]
| [https://t.me/pinenote @PineNote]
| #pinenote
|-
| PineTab
| [https://app.element.io/#/room/#pinetab64:matrix.org #pinetab64:matrix.org]
| [https://t.me/PineTab @PineTab]
| #pinetab
|-
| PineTime
| [https://app.element.io/#/room/#pinetime:matrix.org #pinetime:matrix.org]
| [https://t.me/pinetime @pinetime]
| #Pinetime
|-
| PineTime Development
| [https://app.element.io/#/room/#pinetime-dev:matrix.org #pinetime-dev:matrix.org]
| [https://t.me/pinetime_dev @pinetime_dev]
| #pinetime-dev
|-
| Pinecil
| [https://app.element.io/#/room/#pinecil:matrix.org #pinecil:matrix.org]
| [https://t.me/joinchat/Kmi2S1iej-_4DgrVf3jjnQ Pinecil]
| #pinecil
|-
| Pinetalk Podcast || Unavailable || Unavailable || Unavailable
|-
| Cube
| [https://app.element.io/#/room/#cube64:matrix.org #cube64:matrix.org]
| [https://t.me/pinecube @pinecube]
| #cube
|-
| Nutcracker
| [https://app.element.io/#/room/#pine64-nutcracker:matrix.org #pine64-nutcracker:matrix.org]
| [https://t.me/joinchat/Kmi2S0nOsT240emHk-aO6g Nutcracker]
| #nutcracker
|-
| LoRa
| [https://app.element.io/#/room/#pinelora:matrix.org #pinelora:matrix.org]
| [https://t.me/pine64lora @pine64lora]
| #lora
|-
| Off-topic
| [https://app.element.io/#/room/#offtopic64:matrix.org #offtopic64:matrix.org]
| [https://t.me/pine64offtopic @pine64offtopic]
| #Offtopic
|}

There is also an unofficial Matrix Space at [https://app.element.io/#/room/#pine64-space:matrix.org #pine64-space:matrix.org] for supported clients that organizes all of the above matrix channels into one place.

== Forums ==

PINE64 runs an official forum powered by the open-source forum server software MyBB. The forum can be used to report issues, help out other users, offer findings and new information and more. Users can also engage directly with the community and the developers of partner projects, as well as with the PINE64 members.

The official PINE64 forum can be accessed here:
* [https://forum.pine64.org/ Official PINE64 Forum]

Also, these are the official Subreddits:

* [https://www.reddit.com/r/PINE64official/ Official PINE64 Reddit]
* [https://www.reddit.com/r/PinePhoneOfficial/ Official PinePhone Reddit]

= Helpful Information for Beginners =

* '''[[NOOB | Getting started]]''': Basic information on setting up and handling PINE64 devices, such as how to write (flash) OS images to microSD cards and eMMC modules
* '''[[Notes | PINE64 Wiki contributing Notes]]''': Some notes on prioritized and suggested writing or editing to this Wiki, as well as long-term goals and wiki housekeeping tasks.
* '''[[:Category:Guide]]''': Lists other guide pages than those two above, some are delicated to spicific devices.

User:RainSlide/CSS Boxes

2022-01-21T07:02:49Z

RainSlide: web dev tools

This page is mainly for showing why [[Template:Hint]], [[Template:Note]] and [[Template:Warning]] uses <code>display: table</code> to archive compatibility for both adaptive width and floating sibling(s).

If a set of style is not compatible with adaptive width,
it span to its full width even when it don't need to.

If a set of style is not compatible with floating sibling(s),
the element may still work well with some short content in it;
in another word, it may still looks fine when its
''content width'' + ''margin'' + ''padding'' + ''border''
is lower than the "remaining width" lefted by the floating sibling(s).
So we have to use Lorem ipsum (as well as a floating box, for sure) to test it.

Ideally, you may just set the widths to fixed values,
and pretend nothing happens and CSS is awesome.
However, the content container of MediaWiki got adaptive width,
and maybe you are maintaining a MediaWiki [[Template:Template|Template]],
with only inline styles.

'''You may want to view this page with Web developer tools opened.'''

<div style="position: fixed; top: 12.5vh; font-size: 25vh; line-height: 1; font-weight: bold; white-space: pre; color: lightblue; opacity: .1; user-select: none; pointer-events: none;">CSS<br>is<br>Awesome</div>

== Table ==

=== <code>display: table</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid;">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width.</div>

<div style="display: table; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

</div>
==== The border-collapse & padding problem ====

{| class="wikitable"
! This is a wikitable
|-
| <div style="display: table; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No padding when it's in a wikitable.</div>
|}

This is beacuse <code>.wikitable</code> has <code>border-collapse: collapse</code> on it, and our box inherits it from <code>.wikitable</code>. <code>border-collapse: collapse</code> Disables padding on the table itself, allowing only padding on the table cells, to collapse the outer table borders.

To fix this padding problem in <code>.wikitable</code>s, one must apply <code>border-collapse: separate</code> to the box.
However, if one day, someone REALLY need to use the box as a CSS table,
the border of its cell will be separated by default, which may affect the visual.

{| class="wikitable"
! This is another wikitable
|-
| <div style="display: table; background-color: #FEE; border-collapse: separate;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">The padding is back with <code>border-collapse: separate</code>!</div>
|}

<table style="border-collapse: collapse; margin: .5em 0; padding: .5em 1em; border: 1px solid; background-color: #EFE;">
<tr>
<th colspan="2" style="padding: .25em .5em; border: 1px solid;">Here inside a <code>border-collapse: collapse</code> table...</th>
</tr>
<tr>
<td style="padding: .25em .5em; border: 1px solid;">Every thing is fine.</td>
<td style="padding: .25em .5em; border: 1px solid;">Just fine</td>
</tr>
</table>

<table style="border-collapse: separate; margin: .5em 0; padding: .5em 1em; border: 1px solid; background-color: #FEE;">
<tr>
<th colspan="2" style="padding: .25em .5em; border: 1px solid;">But, here inside a <code>border-collapse: separate</code> table...</th>
</tr>
<tr>
<td style="padding: .25em .5em; border: 1px solid;">The separated border...</td>
<td style="padding: .25em .5em; border: 1px solid;">Maybe that's not what we want.</td>
</tr>
</table>

For those who are interested,
to use the box or other elements with <code>display: table</code> as a CSS table and actually do something,
or to work around with this padding problem with an additional div,
see [https://chrisnager.github.io/ungrid/ ungrid].
<small>But, don't use two elements when you can just use one element + one CSS rule to archive the exact same result.</small>

Since I don't think the [[Template:Hint|Hint]], [[Template:Note|Note]] and [[Template:Warning|Warning]] boxes should be put into a <code>.wikitable</code>,
and it seems no one will use them as CSS tables any time sooner,
I'm not favouring either of those two usage, and keep those templates minimal.

=== <code>display: table-cell</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid;">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-cell; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width.</div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table cells are not blocky! Without this sentence, they are in the same row by now.</p>

<div style="display: table-cell; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table cells have no margin.</p>

</div>

=== <code>display: table-caption</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-caption; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No adaptive width.</div>

<div style="display: table-caption; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">It's hiding.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">There can only be one table caption per table, or, per anything.</p>

</div>

=== <code>display: table-row</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-row; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width?</div>

<div style="display: table-row; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for floating siblings?
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table rows have no margin, padding or border.</p>

</div>

=== <code>display: table-<em>others</em></code> ===

Other table display values works just like table rows, (<code>table-row-group</code>, <code>table-header-group</code> and <code>table-footer-group</code>), or won't even display its contents (<code>table-column</code> and <code>table-column-group</code>).

== A new block formatting context ==

See guide [https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Block_formatting_context Block formatting context] on MDN.

=== <code>float: left</code> ===

''Will everything go right with float set to left?''

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="float: left; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width.</div>

<div style="float: left; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">It falls off from its floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

</div>

''No, something falls down.''

== <code>display: inline-block</code> ==

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: inline-block; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width.</div>

<div style="display: inline-block; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">But inline blocks are inline.</div>

<div style="display: inline-block; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">It also falls off from its floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

</div>

== <code>display: flow-root</code> ==

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: flow-root; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No adaptive width.</div>

<div style="display: flow-root; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

</div>

== And… ==

This is the end of part one. Part two will feature <code>contain: content</code>, <code>width: fit-content</code>, <code>width: max-content</code>, <code>box-sizing: border-box; max-width: 100%</code>, <code>display: flex</code>, <code>display: grid</code>, and more, if I ever got time to work on the part two.

User:RainSlide/CSS Boxes

2022-01-21T07:01:33Z

RainSlide: /* The border-collapse & padding problem */

This page is mainly for showing why [[Template:Hint]], [[Template:Note]] and [[Template:Warning]] uses <code>display: table</code> to archive compatibility for both adaptive width and floating sibling(s).

If a set of style is not compatible with adaptive width,
it span to its full width even when it don't need to.

If a set of style is not compatible with floating sibling(s),
the element may still work well with some short content in it;
in another word, it may still looks fine when its
''content width'' + ''margin'' + ''padding'' + ''border''
is lower than the "remaining width" lefted by the floating sibling(s).
So we have to use Lorem ipsum (as well as a floating box, for sure) to test it.

Ideally, you may just set the widths to fixed values,
and pretend nothing happens and CSS is awesome.
However, the content container of MediaWiki got adaptive width,
and maybe you are maintaining a MediaWiki [[Template:Template|Template]],
with only inline styles.

<div style="position: fixed; top: 12.5vh; font-size: 25vh; line-height: 1; font-weight: bold; white-space: pre; color: lightblue; opacity: .1; user-select: none; pointer-events: none;">CSS<br>is<br>Awesome</div>

== Table ==

=== <code>display: table</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid;">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width.</div>

<div style="display: table; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

</div>
==== The border-collapse & padding problem ====

{| class="wikitable"
! This is a wikitable
|-
| <div style="display: table; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No padding when it's in a wikitable.</div>
|}

This is beacuse <code>.wikitable</code> has <code>border-collapse: collapse</code> on it, and our box inherits it from <code>.wikitable</code>. <code>border-collapse: collapse</code> Disables padding on the table itself, allowing only padding on the table cells, to collapse the outer table borders.

To fix this padding problem in <code>.wikitable</code>s, one must apply <code>border-collapse: separate</code> to the box.
However, if one day, someone REALLY need to use the box as a CSS table,
the border of its cell will be separated by default, which may affect the visual.

{| class="wikitable"
! This is another wikitable
|-
| <div style="display: table; background-color: #FEE; border-collapse: separate;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">The padding is back with <code>border-collapse: separate</code>!</div>
|}

<table style="border-collapse: collapse; margin: .5em 0; padding: .5em 1em; border: 1px solid; background-color: #EFE;">
<tr>
<th colspan="2" style="padding: .25em .5em; border: 1px solid;">Here inside a <code>border-collapse: collapse</code> table...</th>
</tr>
<tr>
<td style="padding: .25em .5em; border: 1px solid;">Every thing is fine.</td>
<td style="padding: .25em .5em; border: 1px solid;">Just fine</td>
</tr>
</table>

<table style="border-collapse: separate; margin: .5em 0; padding: .5em 1em; border: 1px solid; background-color: #FEE;">
<tr>
<th colspan="2" style="padding: .25em .5em; border: 1px solid;">But, here inside a <code>border-collapse: separate</code> table...</th>
</tr>
<tr>
<td style="padding: .25em .5em; border: 1px solid;">The separated border...</td>
<td style="padding: .25em .5em; border: 1px solid;">Maybe that's not what we want.</td>
</tr>
</table>

For those who are interested,
to use the box or other elements with <code>display: table</code> as a CSS table and actually do something,
or to work around with this padding problem with an additional div,
see [https://chrisnager.github.io/ungrid/ ungrid].
<small>But, don't use two elements when you can just use one element + one CSS rule to archive the exact same result.</small>

Since I don't think the [[Template:Hint|Hint]], [[Template:Note|Note]] and [[Template:Warning|Warning]] boxes should be put into a <code>.wikitable</code>,
and it seems no one will use them as CSS tables any time sooner,
I'm not favouring either of those two usage, and keep those templates minimal.

=== <code>display: table-cell</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid;">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-cell; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width.</div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table cells are not blocky! Without this sentence, they are in the same row by now.</p>

<div style="display: table-cell; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table cells have no margin.</p>

</div>

=== <code>display: table-caption</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-caption; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No adaptive width.</div>

<div style="display: table-caption; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">It's hiding.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">There can only be one table caption per table, or, per anything.</p>

</div>

=== <code>display: table-row</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-row; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width?</div>

<div style="display: table-row; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for floating siblings?
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table rows have no margin, padding or border.</p>

</div>

=== <code>display: table-<em>others</em></code> ===

Other table display values works just like table rows, (<code>table-row-group</code>, <code>table-header-group</code> and <code>table-footer-group</code>), or won't even display its contents (<code>table-column</code> and <code>table-column-group</code>).

== A new block formatting context ==

See guide [https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Block_formatting_context Block formatting context] on MDN.

=== <code>float: left</code> ===

''Will everything go right with float set to left?''

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="float: left; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width.</div>

<div style="float: left; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">It falls off from its floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

</div>

''No, something falls down.''

== <code>display: inline-block</code> ==

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: inline-block; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width.</div>

<div style="display: inline-block; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">But inline blocks are inline.</div>

<div style="display: inline-block; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">It also falls off from its floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

</div>

== <code>display: flow-root</code> ==

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: flow-root; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No adaptive width.</div>

<div style="display: flow-root; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

</div>

== And… ==

This is the end of part one. Part two will feature <code>contain: content</code>, <code>width: fit-content</code>, <code>width: max-content</code>, <code>box-sizing: border-box; max-width: 100%</code>, <code>display: flex</code>, <code>display: grid</code>, and more, if I ever got time to work on the part two.

User:RainSlide/CSS Boxes

2022-01-21T06:46:01Z

RainSlide: /* The border-collapse & padding problem */ lower title level

This page is mainly for showing why [[Template:Hint]], [[Template:Note]] and [[Template:Warning]] uses <code>display: table</code> to archive compatibility for both adaptive width and floating sibling(s).

If a set of style is not compatible with adaptive width,
it span to its full width even when it don't need to.

If a set of style is not compatible with floating sibling(s),
the element may still work well with some short content in it;
in another word, it may still looks fine when its
''content width'' + ''margin'' + ''padding'' + ''border''
is lower than the "remaining width" lefted by the floating sibling(s).
So we have to use Lorem ipsum (as well as a floating box, for sure) to test it.

Ideally, you may just set the widths to fixed values,
and pretend nothing happens and CSS is awesome.
However, the content container of MediaWiki got adaptive width,
and maybe you are maintaining a MediaWiki [[Template:Template|Template]],
with only inline styles.

<div style="position: fixed; top: 12.5vh; font-size: 25vh; line-height: 1; font-weight: bold; white-space: pre; color: lightblue; opacity: .1; user-select: none; pointer-events: none;">CSS<br>is<br>Awesome</div>

== Table ==

=== <code>display: table</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid;">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width.</div>

<div style="display: table; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

</div>
==== The border-collapse & padding problem ====

{| class="wikitable"
! This is a wikitable
|-
| <div style="display: table; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No padding when it's in a wikitable.</div>
|}

This is beacuse <code>.wikitable</code> has <code>border-collapse: collapse</code> on it, and our box inherits it from <code>.wikitable</code>. <code>border-collapse: collapse</code> Disables padding on the table itself, allowing only padding on the table cells, to collapse the outer table borders.

To fix this padding problem in <code>.wikitable</code>s, one must apply <code>border-collapse: separate</code> to the box.
However, if one day, someone REALLY need to use the box as a CSS table,
the border of its cell will be separated by default, which may affect the visual.

{| class="wikitable"
! This is another wikitable
|-
| <div style="display: table; background-color: #FEE; border-collapse: separate;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">The padding is back!</div>
|}

<div style="display: table; background-color: #FEE; border-collapse: separate;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
<div style="display: table-cell; padding: .25em .5em; border: 1px solid;>But...</div>
<div style="display: table-cell; padding: .25em .5em; border: 1px solid;>Maybe that's not what we want.</div>
</div>

For those who are interested,
to use the box or other elements with <code>display: table</code> as a CSS table and actually do something,
or to work around with this padding problem with an additional div,
see [https://chrisnager.github.io/ungrid/ ungrid].
<small>But, don't use two elements when you can just use one element + one CSS rule to archive the exact same result.</small>

Since I don't think the [[Template:Hint|Hint]], [[Template:Note|Note]] and [[Template:Warning|Warning]] boxes should be put into a <code>.wikitable</code>,
and it seems no one will use them as CSS tables any time sooner,
I'm not favouring either of those two usage, and keep those templates minimal.

=== <code>display: table-cell</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid;">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-cell; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width.</div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table cells are not blocky! Without this sentence, they are in the same row by now.</p>

<div style="display: table-cell; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table cells have no margin.</p>

</div>

=== <code>display: table-caption</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-caption; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No adaptive width.</div>

<div style="display: table-caption; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">It's hiding.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">There can only be one table caption per table, or, per anything.</p>

</div>

=== <code>display: table-row</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-row; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width?</div>

<div style="display: table-row; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for floating siblings?
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table rows have no margin, padding or border.</p>

</div>

=== <code>display: table-<em>others</em></code> ===

Other table display values works just like table rows, (<code>table-row-group</code>, <code>table-header-group</code> and <code>table-footer-group</code>), or won't even display its contents (<code>table-column</code> and <code>table-column-group</code>).

== A new block formatting context ==

See guide [https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Block_formatting_context Block formatting context] on MDN.

=== <code>float: left</code> ===

''Will everything go right with float set to left?''

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="float: left; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width.</div>

<div style="float: left; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">It falls off from its floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

</div>

''No, something falls down.''

== <code>display: inline-block</code> ==

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: inline-block; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width.</div>

<div style="display: inline-block; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">But inline blocks are inline.</div>

<div style="display: inline-block; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">It also falls off from its floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

</div>

== <code>display: flow-root</code> ==

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: flow-root; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No adaptive width.</div>

<div style="display: flow-root; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

</div>

== And… ==

This is the end of part one. Part two will feature <code>contain: content</code>, <code>width: fit-content</code>, <code>width: max-content</code>, <code>box-sizing: border-box; max-width: 100%</code>, <code>display: flex</code>, <code>display: grid</code>, and more, if I ever got time to work on the part two.

User:RainSlide

2021-11-01T08:12:10Z

RainSlide: noto-sans-cjk -> noto-fonts-cjk

If I ever feel better.

<hr>

== My personal setup for Arch Linux ARM ==

<pre style="overflow-wrap: break-word; white-space: pre-wrap">
# Use your choices of mirrors instead of mine,
# and pack your mirrorlist addition with your script, instead of download it, if possible!
curl -o mirrorlist.cn.txt -R --no-progress-meter https://pastebin.com/raw/RQn0DiVF

## In case you can't pack it with your script or access Pastebin:
# curl -o mirrorlist.cn.txt.gz -R --no-progress-meter https://wiki.pine64.org/images/9/9f/Mirrorlist.archlinuxarm.cn.txt.gz
# gzip mirrorlist.cn.txt.gz
# rm -f mirrorlist.cn.txt.gz

# Insert mirrorlist.cn.txt into pacman.d/mirrorlist at the 4th line
sudo sed -i '4r mirrorlist.cn.txt' /etc/pacman.d/mirrorlist

# Update the packages with those new mirrors
sudo pacman -Syu

# Install more packages
sudo pacman -S noto-fonts-cjk

# Then:
reboot
</pre>

=== Arch Linux ARM mirrorlist - China entries ===

<pre style="word-break: break-all; white-space: pre-wrap">
## China
Server = https://mirrors.aliyun.com/archlinuxarm/$arch/$repo
Server = https://mirrors.cloud.tencent.com/archlinuxarm/$arch/$repo
Server = https://mirrors.sjtug.sjtu.edu.cn/archlinuxarm/$arch/$repo
Server = https://mirrors.tuna.tsinghua.edu.cn/archlinuxarm/$arch/$repo
Server = https://mirrors.ustc.edu.cn/archlinuxarm/$arch/$repo
Server = https://mirrors.bfsu.edu.cn/archlinuxarm/$arch/$repo
Server = https://mirrors.nju.edu.cn/archlinuxarm/$arch/$repo
# Server = https://mirrors.xjtu.edu.cn/archlinuxarm/$arch/$repo
# Server = https://mirrors.cqu.edu.cn/archlinuxarm/$arch/$repo
# Server = https://mirrors.dgut.edu.cn/archlinuxarm/$arch/$repo
# Server = https://mirrors.hit.edu.cn/archlinuxarm/$arch/$repo
# Server = https://mirrors.neusoft.edu.cn/archlinuxarm/$arch/$repo
# Server = https://mirror.redrock.team/archlinuxarm/$arch/$repo
</pre>

== Quectel EG25-G ==

Quectel EG25-G is the modem used by [[PinePhone]].

=== Links ===

'''EG25-G'''
* English: [https://www.quectel.com/product/lte-eg25-g/ LTE EG25-G]
* Simplified Chinese: [https://www.quectel.com/product/eg25-g/?lang=zh-hans EG25-G]
* Old website (English): [http://47.100.183.34/product/eg25g.htm LTE Standard EG25-G]
* Old website (Simplified Chinese): [http://47.100.183.34/cn/product/eg25g.htm LTE Standard EG25-G]

'''Quectel'''
* English: https://www.quectel.com/
* Simplified Chinese: https://www.quectel.com/?lang=zh-hans
* Old website (English): http://47.100.183.34/
* Old website (Simplified Chinese): http://47.100.183.34/cn/

'''Quectel Open Source'''
* FTP: ftp://ftp2.quectel.com/
* English: https://www.quectel.com/quectel-open-source/
* Simplified Chinese: https://www.quectel.com/移远开源/?lang=zh-hans

=== Documentation ===

[https://www.google.com/search?q=Quectel+EG25-G+filetype%3Apdf Google Search: <code>Quectel EG25-G filetype:pdf</code>]

Specification:
* [https://static.abstore.pl/design/accounts/soyter/img/dokumentacje/quectel_eg25-g.pdf Quectel EG25-G LTE Specification V1.0] (2018, Preliminary version, from static.abstore.pl)
* [https://www.quectel.com/wp-content/uploads/pdfupload/Quectel_EG25-G_LTE_Specification_V1.1.pdf Quectel EG25-G LTE Specification V1.1] (2019-03)
* [https://www.quectel.com/wp-content/uploads/pdfupload/Quectel_EG25-G_LTE_Standard_Specification_V1.2.pdf Quectel EG25-G LTE Standard Specification V1.2] (2019-11)
* [https://forums.quectel.com/uploads/short-url/fznFTQYaeQKtW9BlJOhL6aXL1T9.pdf Quectel EG25-G LTE Standard Specification V1.3] (2020-05)
* ''''[https://www.quectel.com/wp-content/uploads/pdfupload/Quectel_EC25_Series_LTE_Standard_Specification_V2.1.pdf Quectel EC25 Series LTE Standard Specification V2.1]''' ('''2020-08''')

Specification (Simplified Chinese):
* [https://www.quectel.com/wp-content/uploads/pdfupload/Quectel_EG25-G_LTE_Standard_模块产品规格书_V1.0.pdf Quectel EG25-G LTE Standard 模块产品规格书 V1.0] (2019-11)
* '''[http://47.100.183.34/UploadFile/Product/Quectel_EG25-G_LTE_Standard_模块产品规格书_V1.1.pdf Quectel EG25-G LTE Standard 模块产品规格书 V1.1]''' ('''2020-11''')

Hardware Design:
* [https://www.quectel.com/wp-content/uploads/pdfupload/Quectel_EG25-G_Hardware_Design_V1.4.pdf Quectel EG25-G Hardware Design V1.0] (2018-12)
* [https://www.quectel.com/wp-content/uploads/pdfupload/Quectel_EG25-G_Hardware_Design_V1.4.pdf Quectel EG25-G Hardware Design V1.1] (2019-07)
* [https://www.quectel.com/wp-content/uploads/pdfupload/Quectel_EG25-G_Hardware_Design_V1.4.pdf Quectel EG25-G Hardware Design V1.2] (2019-07)
* [https://www.quectel.com/wp-content/uploads/pdfupload/Quectel_EG25-G_Hardware_Design_V1.4.pdf Quectel EG25-G Hardware Design V1.3] (2020-04)
* '''[https://www.quectel.com/wp-content/uploads/pdfupload/Quectel_EG25-G_Hardware_Design_V1.4.pdf Quectel EG25-G Hardware Design V1.4]''' ('''2020-09''')

AT Commands Manual:
* [https://www.quectel.com/wp-content/uploads/pdfupload/Quectel_EC25&EC21_AT_Commands_Manual_V1.2.pdf Quectel EC25 & E'''C'''21 AT Commands Manual V1.2] (2017-11, not for E'''G'''25 or E'''G'''25-G, but it is used as reference by some people)
* '''[https://www.quectel.com/wp-content/uploads/pdfupload/Quectel_EC2x&EG9x&EG2x-G&EM05_Series_AT_Commands_Manual_V2.0.pdf Quectel EC2x & EG9x & EG2x-G & EM05 Series AT Commands Manual V2.0]''' ('''2021-02''')

=== Firmware ===

Firmware versions (links are):
* [https://github.com/Biktorgj/quectel_eg25_recovery/tree/master EG25GGBR07A08M2G_01.001.01.001]
* [https://github.com/Biktorgj/quectel_eg25_recovery/tree/EG25GGBR07A08M2G_01.002.01.002 EG25GGBR07A08M2G_01.002.01.002]
* [https://github.com/Biktorgj/quectel_eg25_recovery/tree/EG25GGBR07A08M2G_01.002.07 EG25GGBR07A08M2G_01.002.07]
* [https://github.com/Biktorgj/quectel_eg25_recovery/tree/EG25GGBR07A08M2G_01.003.01.003 EG25GGBR07A08M2G_01.003.01.003]

Forum discussion:
* [https://forum.pine64.org/showthread.php?tid=11815 Latest firmware for PinePhone modem!] by Subsentient

'''About the latest firmware (version number 01.003.01.003):'''

In a [https://github.com/Biktorgj/quectel_eg25_recovery/issues/1#issuecomment-751193042 GitHub issue] sent by someone who updated their firmware to version number 01.003.01.003, repo owner Biktorgj replies:
<blockquote>
There have been some reports of '''some issues during sleep''' with the latest firmware, so you might actually want to downgrade to EG25GGBR07A08M2G_01.002.07, which looks more stable.<br>
Plus points, modem-power won't complain after downgrading
</blockquote>

=== Multimedia Messaging Service (MMS) ===

Wikipedia: [https://en.wikipedia.org/wiki/Multimedia_Messaging_Service Multimedia Messaging Service]

Forum discussion:
* [https://forum.pine64.org/showthread.php?tid=11994 Script to get MMS(!)]
* [https://forum.pine64.org/showthread.php?tid=12491 Beta support: MMS on chatty/mmsd on Modem Manager - help/testing wanted!]

<hr>

Thanks [https://github.com/Biktorgj Biktorgj] for all his work on it, that's one people vs. all the obstacle the hardware manufacturer creates.

User:RainSlide

2021-11-01T07:53:03Z

RainSlide:

If I ever feel better.

<hr>

== My personal setup for Arch Linux ARM ==

<pre style="overflow-wrap: break-word; white-space: pre-wrap">
# Use your choices of mirrors instead of mine,
# and pack your mirrorlist addition with your script, instead of download it, if possible!
curl -o mirrorlist.cn.txt -R --no-progress-meter https://pastebin.com/raw/RQn0DiVF

## In case you can't pack it with your script or access Pastebin:
# curl -o mirrorlist.cn.txt.gz -R --no-progress-meter https://wiki.pine64.org/images/9/9f/Mirrorlist.archlinuxarm.cn.txt.gz
# gzip mirrorlist.cn.txt.gz
# rm -f mirrorlist.cn.txt.gz

# Insert mirrorlist.cn.txt into pacman.d/mirrorlist at the 4th line
sudo sed -i '4r mirrorlist.cn.txt' /etc/pacman.d/mirrorlist

# Update the packages with those new mirrors
sudo pacman -Syu

# Install more packages
sudo pacman -S noto-sans-cjk

# Then:
reboot
</pre>

=== Arch Linux ARM mirrorlist - China entries ===

<pre style="word-break: break-all; white-space: pre-wrap">
## China
Server = https://mirrors.aliyun.com/archlinuxarm/$arch/$repo
Server = https://mirrors.cloud.tencent.com/archlinuxarm/$arch/$repo
Server = https://mirrors.sjtug.sjtu.edu.cn/archlinuxarm/$arch/$repo
Server = https://mirrors.tuna.tsinghua.edu.cn/archlinuxarm/$arch/$repo
Server = https://mirrors.ustc.edu.cn/archlinuxarm/$arch/$repo
Server = https://mirrors.bfsu.edu.cn/archlinuxarm/$arch/$repo
Server = https://mirrors.nju.edu.cn/archlinuxarm/$arch/$repo
# Server = https://mirrors.xjtu.edu.cn/archlinuxarm/$arch/$repo
# Server = https://mirrors.cqu.edu.cn/archlinuxarm/$arch/$repo
# Server = https://mirrors.dgut.edu.cn/archlinuxarm/$arch/$repo
# Server = https://mirrors.hit.edu.cn/archlinuxarm/$arch/$repo
# Server = https://mirrors.neusoft.edu.cn/archlinuxarm/$arch/$repo
# Server = https://mirror.redrock.team/archlinuxarm/$arch/$repo
</pre>

== Quectel EG25-G ==

Quectel EG25-G is the modem used by [[PinePhone]].

=== Links ===

'''EG25-G'''
* English: [https://www.quectel.com/product/lte-eg25-g/ LTE EG25-G]
* Simplified Chinese: [https://www.quectel.com/product/eg25-g/?lang=zh-hans EG25-G]
* Old website (English): [http://47.100.183.34/product/eg25g.htm LTE Standard EG25-G]
* Old website (Simplified Chinese): [http://47.100.183.34/cn/product/eg25g.htm LTE Standard EG25-G]

'''Quectel'''
* English: https://www.quectel.com/
* Simplified Chinese: https://www.quectel.com/?lang=zh-hans
* Old website (English): http://47.100.183.34/
* Old website (Simplified Chinese): http://47.100.183.34/cn/

'''Quectel Open Source'''
* FTP: ftp://ftp2.quectel.com/
* English: https://www.quectel.com/quectel-open-source/
* Simplified Chinese: https://www.quectel.com/移远开源/?lang=zh-hans

=== Documentation ===

[https://www.google.com/search?q=Quectel+EG25-G+filetype%3Apdf Google Search: <code>Quectel EG25-G filetype:pdf</code>]

Specification:
* [https://static.abstore.pl/design/accounts/soyter/img/dokumentacje/quectel_eg25-g.pdf Quectel EG25-G LTE Specification V1.0] (2018, Preliminary version, from static.abstore.pl)
* [https://www.quectel.com/wp-content/uploads/pdfupload/Quectel_EG25-G_LTE_Specification_V1.1.pdf Quectel EG25-G LTE Specification V1.1] (2019-03)
* [https://www.quectel.com/wp-content/uploads/pdfupload/Quectel_EG25-G_LTE_Standard_Specification_V1.2.pdf Quectel EG25-G LTE Standard Specification V1.2] (2019-11)
* [https://forums.quectel.com/uploads/short-url/fznFTQYaeQKtW9BlJOhL6aXL1T9.pdf Quectel EG25-G LTE Standard Specification V1.3] (2020-05)
* ''''[https://www.quectel.com/wp-content/uploads/pdfupload/Quectel_EC25_Series_LTE_Standard_Specification_V2.1.pdf Quectel EC25 Series LTE Standard Specification V2.1]''' ('''2020-08''')

Specification (Simplified Chinese):
* [https://www.quectel.com/wp-content/uploads/pdfupload/Quectel_EG25-G_LTE_Standard_模块产品规格书_V1.0.pdf Quectel EG25-G LTE Standard 模块产品规格书 V1.0] (2019-11)
* '''[http://47.100.183.34/UploadFile/Product/Quectel_EG25-G_LTE_Standard_模块产品规格书_V1.1.pdf Quectel EG25-G LTE Standard 模块产品规格书 V1.1]''' ('''2020-11''')

Hardware Design:
* [https://www.quectel.com/wp-content/uploads/pdfupload/Quectel_EG25-G_Hardware_Design_V1.4.pdf Quectel EG25-G Hardware Design V1.0] (2018-12)
* [https://www.quectel.com/wp-content/uploads/pdfupload/Quectel_EG25-G_Hardware_Design_V1.4.pdf Quectel EG25-G Hardware Design V1.1] (2019-07)
* [https://www.quectel.com/wp-content/uploads/pdfupload/Quectel_EG25-G_Hardware_Design_V1.4.pdf Quectel EG25-G Hardware Design V1.2] (2019-07)
* [https://www.quectel.com/wp-content/uploads/pdfupload/Quectel_EG25-G_Hardware_Design_V1.4.pdf Quectel EG25-G Hardware Design V1.3] (2020-04)
* '''[https://www.quectel.com/wp-content/uploads/pdfupload/Quectel_EG25-G_Hardware_Design_V1.4.pdf Quectel EG25-G Hardware Design V1.4]''' ('''2020-09''')

AT Commands Manual:
* [https://www.quectel.com/wp-content/uploads/pdfupload/Quectel_EC25&EC21_AT_Commands_Manual_V1.2.pdf Quectel EC25 & E'''C'''21 AT Commands Manual V1.2] (2017-11, not for E'''G'''25 or E'''G'''25-G, but it is used as reference by some people)
* '''[https://www.quectel.com/wp-content/uploads/pdfupload/Quectel_EC2x&EG9x&EG2x-G&EM05_Series_AT_Commands_Manual_V2.0.pdf Quectel EC2x & EG9x & EG2x-G & EM05 Series AT Commands Manual V2.0]''' ('''2021-02''')

=== Firmware ===

Firmware versions (links are):
* [https://github.com/Biktorgj/quectel_eg25_recovery/tree/master EG25GGBR07A08M2G_01.001.01.001]
* [https://github.com/Biktorgj/quectel_eg25_recovery/tree/EG25GGBR07A08M2G_01.002.01.002 EG25GGBR07A08M2G_01.002.01.002]
* [https://github.com/Biktorgj/quectel_eg25_recovery/tree/EG25GGBR07A08M2G_01.002.07 EG25GGBR07A08M2G_01.002.07]
* [https://github.com/Biktorgj/quectel_eg25_recovery/tree/EG25GGBR07A08M2G_01.003.01.003 EG25GGBR07A08M2G_01.003.01.003]

Forum discussion:
* [https://forum.pine64.org/showthread.php?tid=11815 Latest firmware for PinePhone modem!] by Subsentient

'''About the latest firmware (version number 01.003.01.003):'''

In a [https://github.com/Biktorgj/quectel_eg25_recovery/issues/1#issuecomment-751193042 GitHub issue] sent by someone who updated their firmware to version number 01.003.01.003, repo owner Biktorgj replies:
<blockquote>
There have been some reports of '''some issues during sleep''' with the latest firmware, so you might actually want to downgrade to EG25GGBR07A08M2G_01.002.07, which looks more stable.<br>
Plus points, modem-power won't complain after downgrading
</blockquote>

=== Multimedia Messaging Service (MMS) ===

Wikipedia: [https://en.wikipedia.org/wiki/Multimedia_Messaging_Service Multimedia Messaging Service]

Forum discussion:
* [https://forum.pine64.org/showthread.php?tid=11994 Script to get MMS(!)]
* [https://forum.pine64.org/showthread.php?tid=12491 Beta support: MMS on chatty/mmsd on Modem Manager - help/testing wanted!]

<hr>

Thanks [https://github.com/Biktorgj Biktorgj] for all his work on it, that's one people vs. all the obstacle the hardware manufacturer creates.

Getting started

2021-10-08T00:57:06Z

RainSlide: /* Setting Up Your device - What You’ll Need to Get Started */ Rework

== Setting Up Your Device - What do You Need to Get Started ==

You will need the following to get started with using your [[PINE A64|PINE A64(+)]], [[PINE A64-LTS/SOPine]], [[Pinebook]] or [[ROCK64]] board:
* A Windows / Linux PC or Mac device with a MicroSD Card Reader
* Internet connection / pre-downloaded OS image files
* Power Supply:
** '''PINE A64(+)''': Power Supply (PSU) and a micro usb cable. Please make sure to use a PSU rated at +5V @2A and a micro USB cable that is at least 26 AWG thick.
** '''SOPine/PINE A64-LTS''': Power Supply (PSU) with 3.5mm OD/1.5mm ID barrel DC Jack. Please make sure to use a PSU rated at +5V @2A.
** '''Pinebook''' and '''ROCK64''': Power Supply (PSU) with 3.5mm OD/1.5mm ID barrel DC Jack. Please make sure to use a PSU rated at +5V @3A.
* MicroSD card (Recommend: 8GB or higher capacity, 10MB/s or faster speed)
* HDMI cable (unless you wish to run [https://en.wikipedia.org/wiki/Headless_computer headless] / without a screen)
** For [[:Category:Allwinner A64|A64 devices]], Android and Remix OS supports 720p and 1080p, while Linux supports a [https://github.com/longsleep/sunxi-disp-tool#available-hdmi-output-names wider range of resolutions].
* Input device(s) such as: keyboard, mouse, remote, pointer, etc.

== Step-by-Step Instructions for Flashing MicroSD Cards ==

{{Note|'''Caution!''' Handle the Pine64 Single Board Computers' PCBs with care. Always hold bare boards by the edges and make sure to wear an anti-static wrist strap. Touching components on the front and back of the boards can result in an ESD discharge that may cause damage to the electronics. Avoid placing bare boards on materials such as carpets, plastics or other surfaces prone to electrostatic build-up}}

'''Begin by imaging the OS of your choice'''

The process of flashing PINE64 OS images to micro SD on your Windows, Linux or OSX device is the same for all devices. You will require a quality microSD card (8GB or greater; class 10 or faster). There are many [https://forum.pine64.org/showthread.php?tid=681 substandard and counterfeit cards] in circulation and even reputable vendors may unknowingly sell counterfeit microSD cards. Cards that do not meet the criteria outlined above are known to cause a variety of issues including, but not limited to, complete boot failure. There are ways of testing microSD cards prior to installing the operating system to make sure they are appropriate for use with your board. The main utility for checking microSD cards is [https://www.softpedia.com/get/System/System-Miscellaneous/H2testw.shtml#download H2testw 1.4]; yet another alternative is [https://github.com/AltraMayor/f3/archive/v6.0.zip F3]. Yet another overview of various options [https://www.raymond.cc/blog/test-and-detect-fake-or-counterfeit-usb-flash-drives-bought-from-ebay-with-h2testw/ Test and Detect Fake Cards]

Please refer to the relevant section below for instructions on how to image your microSD card:
* [[#Imaging microSD on Windows 7/8/8.1/10|Imaging microSD on Windows 7/8/8.1/10]]
* [[#Imaging microSD on Apple OSX|Imaging microSD on Apple OSX]]
* [[#Imaging microSD on Linux|Imaging microSD on Linux]]

Having successfully imaged your microSD card, insert it into the microSD slot.

'''Plug in the HDMI Cable, Ethernet Cable and Peripherals to your PINE64 SBC'''

Unless you are planning on running your board headless (without a monitor / as a server) you should plug in all necessary peripherals, including the HDMI and Ethernet cable, prior to powering ON the board. Do note, depending on which OS image you are using, some peripherals may or may not work.

'''Apply Power to Your Board'''

Once you have imaged your microSD and plugged everything in, you are ready to apply power to the PINE64 Single Board Computer. You'll need a good quality 5 Volt, 2 Amp PSU. Using a good quality PSU is very important as failing to meet the required specifications may prevent the board from booting correctly. A marginally higher PSU Voltage is acceptable (for instance, 5.1 volts - due to the nature of the micro usb connection, a 5.1v supply can help protect slightly against voltage drops which can cause undesirable results). However, a significantly higher voltage of 7 Volts or more will damage the PINE64 Single Board Computer and may render it inoperative.

For PINE A64(+) board, if you are using a separate micro USB cable with your PSU, make sure that the cable has a low resistance rating. Cables with high resistance will cause improper function and the unit may not boot at all or only partially. The thicker the internal cabling, the better [https://voyager8.blogspot.co.uk/2013/04/how-to-choose-good-usb-data-and.html i.e. AWG (American Wire Gauge) 20 is better than AWG 28]. In General, '''power-only microUSB''' cables come with red colour USB header.

Having completed the steps outlined above the PINE64 Single Board Computer will begin to boot. The onboard power-on LEDs will come on and Ethernet port LEDs will start to blink if you have an Ethernet cable plugged in.

----

=== Imaging microSD on Windows 7/8/8.1/10 ===

You will need the following utilities to get started with imaging the OS of your choice onto your microSD card:
* A compression utility (used to unarchive the OS image). We recommend you use [https://www.7-zip.org/download.html 7zip].
* A disk image utility (used to flash the .img to your SD card). We recommend you use either the [https://etcher.io/ Etcher] or [https://sourceforge.net/projects/win32diskimager/ Win32Imager] utility.

'''Optional for Allwinner A64 SoC based boards'''
* Phoenix Card image utility (used ONLY for phoenix card images). You can download it from [https://drive.google.com/file/d/0B0cEs0lxTtL3VmstaEFfbmU1NFk/view?usp=sharing here].

'''Downloading and extracting OS image(s)'''

You can find OS images for the respective devices in the [[Main_Page|device section]] on the main page.
Images designated ‘DD’ need to be flashed using Etcher or Win32imager, whilst images labelled ‘Phoenix Card Image’ require the Phoenix Card utility.

Having downloaded the required OS image proceed to use 7zip to unarchive it by right-clicking the archive, and selecting ‘Extract All’. Upon completion, note the destination of where the .img file was extracted (‘Downloads’ folder by default). Once the process has completed, you can proceed to imaging the .img file.

'''Imaging the microSD card (DD)'''

* Insert your microSD card into your laptop/USB card reader. You may require a SD → microSD converter, as most laptops and desktops only feature a full-size SD card reader. Once the microSD card is plugged into your computer, make sure to take note of the drive it has been assigned (the drive is assigned a letter, e.g. ‘F:’). You will need to remember the ‘letter’ it has been assigned when imaging the OS.

* Launch Win32diskImager.exe or etcher.exe. You will be presented with a field titled ‘path’ and a drop down menu labeled ‘device’. Click the ‘path’, navigate to and select the OS image you extracted from the archive earlier. Next, from the drop-down menu select the drive your microSD has been assigned. {{warning|'''N.B.''' Pay close attention to the selected drive (remember your letter) – the imaging process will permanently erase and format the selected drive. If you choose the wrong drive all your data will be lost.}}

* Having chosen the desired OS image and the correct driver press ‘write’. Once the image has been written to your microSD card you will receive a pop-up notification. Be sure to close the application and to eject/remove your SD card safely from Windows.

'''Imaging using Phoenix Card (applicable only to Allwinner A64 SoC based boards)'''

On Windows, you can also use Phoenix Card (for detailed instructions click [[PhoenixCard|here]]). The Phoenix Card utility works ONLY with images designated as ‘Phoenix Card’ in the downloads section. To use Phoenix Card follow these steps:

* Insert your microSD card into your laptop/USB card reader. You may require a SD → microSD converter, as most laptops and desktops only feature a full-size SD card reader. Once the microSD card is plugged into your computer, make sure to take note of the drive it has been assigned (the drive is assigned a letter, e.g. ‘F:’). You will need to remember the ‘letter’ it has been assigned when imaging the OS.

* Launch phoenixcard.exe. You will be presented with a ‘disk’ drop-down menu and a field denoted as ‘.img File’. Click on ‘.img File’ and navigate to and select the OS image have downloaded and unarchived. Next, make sure to select the disk that your microSD card has been assigned. {{warning|'''N.B.''' Pay close attention to the selected drive (remember your letter) – the imaging process will permanently erase and format the selected drive. If you choose the wrong drive all your data will be lost.}}

* Make sure to select ‘Startup!’ from the ‘Write mode’ window and click Burn. Once the image has been written to your microSD card you will receive a confirmation in the ‘option’ window. Be sure to close the application and to eject/remove your SD card safely from Windows.

----

=== Imaging microSD on macOS ===

You will need the following utilities to get started with imaging the OS of your choice onto your microSD card:

* A compression utility (used to unarchive the OS image). You may use [https://www.keka.io/en/ Keka].
* A disk image utility (used to flash the .img to your SD card in GUI). You may use [https://www.tweaking4all.com/software/macosx-software/applepi-baker-v2/#DownloadApplePiBaker ApplePi Baker v2] or [https://etcher.io/ Etcher].

{{hint|'''N.B.''' Phoenix Card utility and images are NOT available on macOS.}}

'''Downloading and extracting OS image(s), insert the SD card'''

You can find OS images for the respective devices in the [[Main_Page#Devices|device section]] of the main page.

Having downloaded the required OS image, proceed to use the compression utility to unarchive it and get the .img file.
Once the process has completed, you can proceed to write it to your SD card.

Insert your microSD card into your Mac laptop/USB card reader.
You may require a SD → microSD converter, as Apple’s laptops and desktops only feature a full-size SD card reader.
Once the microSD card is plugged into your computer, it should appear in Finder / on your desktop.

'''Imaging the microSD card (GUI)'''

Launch the imaging utility. Upon startup, the application may ask for your password.
When the application launches, you will be presented with a field titled ‘IMG file’ and a path of the mounted microSD card
(it will look like this: ‘/dev/diskX 32.0Gb SD card’).

To choose the OS image file, click the ‘IMG file’ button, navigate to and select the .img file you extracted from the archive earlier.
Then select the microSD card you want to write into.

{{warning|'''N.B.''' Pay close attention to the selected device, make sure it is the right SD card – the imaging process will permanently erase and format the selected storage device. If you choose the wrong device, all the data in it will be lost.}}

Having chosen the desired OS image and the correct device, press ‘Restore Backup’ or ‘Flash’.
Once the image has been written to your microSD card, you will receive a pop-up notification.
Close the application, then eject/remove your SD card from your Mac.

'''Imaging from Terminal'''

{{note|'''N.B.''' If you are not comfortable using the terminal, please use the GUI method outlined above instead.}}

Open up your terminal and navigate to the directory where you unarchived your OS image.

Before you start writing to the card, you will have to identify your microSD card.
Type: <code>diskutil list</code> and note the output.
The disk number should match the size of your SD card, and will likely be using <code>Fdisk_partition_scheme</code>.

Having identified the disk number execute the following commands
(substitute diskX for your disk and name of image for pine64-image-name.img):

diskutil unmountDisk /dev/diskX
sudo dd if=pine64-image-name.img of=/dev/disk2 bs=1M

Wait patiently for the process to complete, then eject/remove your SD card from your Mac.

----

=== Imaging microSD on Linux ===

You will need the following utilities to get started with imaging the OS of your choice onto your microSD card:
* A compression Utility (used to unarchive the OS image). We recommend you use [https://apps.kde.org/en/ark Ark].
* A disk image utility (used to flash the .img to your SD card in GUI). We recommend you use [https://etcher.io/ Etcher] or the [https://git.gnome.org/browse/gnome-disk-utility/ GUI Disks utility] that ships with most popular distros.
{{hint|'''N.B.''' Phoenix Card utility and images are NOT available on Linux.}}

'''Downloading and extracting OS image(s)'''

You can find OS images for the respective devices in the [[Main_Page|device section]] on the main page. On Linux you can only use images designated as ‘DD’.

Having downloaded the required OS image proceed to use 7zip to unarchive it by double clicking the archive, and selecting ‘Extract All’. Upon completion, note the destination where the .img file was extracted (‘Downloads’ folder by default). Once the process has completed, you can proceed to imaging the .img file.

'''Imaging the microSD card (GUI)'''

* Insert your microSD card into your Linux laptop/USB card reader. Once the microSD card is plugged into your computer it should appear in your File Manager / on your desktop.

* Launch Disks or the etcher utility (This tutorial outlines how to use Disks, if you wish to learn how to use Etcher please visit [https://etcher.io/ their website]).

* Upon launching Disks, you will be presented with all volumes visible to your computer. As a rule of thumb, your microSD card should be found at the bottom of listed volumes. Verify this by checking the size and mounting of the microSD card. {{warning|'''N.B.''' Pay close attention to the selected drive – the imaging process will permanently erase and format the selected drive. If you choose the wrong drive all your data will be lost.}}

* Having selected your microSD card, click the cog menu in top right corner and choose the ‘Restore Disk Image’ option from the drop-down list. Navigate to and select the OS image you extracted from the archive earlier. Once you select it, you will be asked to enter your password and to confirm writing to the chosen volume (microSD card).

* You will be given a predicted time, writing-speed and completion percentage. Once the image has been written to your microSD card you will receive a pop-up notification. Be sure to close the application and to eject/remove your SD card safely from your computer.

'''Imaging from Terminal'''

::{{note|'''N.B.''' If you are not comfortable using the terminal, please use the GUI method outlined above instead.}}

* Insert your microSD card into your Linux laptop/USB card reader. Once the microSD card is plugged into your computer it should appear in Finder / on your desktop.
* Open up your terminal and navigate to the directory where you unarchived your OS image. e.g. <code>cd Download</code>
* Before you start writing to the card, you will have to identify your microSD card.

* Type: <code>lsblk</code> and pay attention to the listed disks. Disks will appear as ''/dev/mmcblk0 /dev/mmcblk1'' etc.
::{{note|'''Hint''': the drive you currently have booted from has the <code>/</code> at the end of the line. This is the wrong drive. Look at the drive that matches your microSD card’s size.}}

* Now you are ready to write the image to the microSD card using this command: (replace the pine.img file with your image and mmcblkX with the correct device for the microSD card)
::<code>sudo umount /dev/mmcblkX</code>
::<code>sudo dd if=pine.img of=/dev/mmcblkX bs=1M status=progress conv=fsync</code>

* Wait patiently for the process to complete.
* use the command <code>sync</code> to ensure everything is written to the microSD card.
* The card is ready to boot

(sometimes this process fails and your microSD card can't boot, one way of fixing this is just to repeat the same thing, you can also try a different microSD card)

== Instructions to Flashing eMMC Modules ==

All PINE64 devices - with the '''notable exception of the original Pine A64(+) SBC''' - support eMMC modules as an alternative boot and storage solution to micro SD cards.
An eMMC module can be purchased for your device(s) from the [https://pine64.com/?post_type=product PINE64 store]. The only PINE64 device that ships with an eMMC module by default is the Pinebook.

The available modules come in three different capacities: 16Gb, 32Gb, 64Gb and 128Gb

There are a few ways to flash eMMC modules with the desired OS image. The following sections are a summary of the processes involved in flashing the OS image of your choice to the eMMC module.

----

=== Flashing Using the USB-to-eMMC Adapter (Preferred Way) ===

A USB-to-eMMC adapter is available from purchase from the [https://pine64.com/product/usb-adapter-for-emmc-module/ PINE64 Store] making it easy to mount the eMMC module as a volume in your Windows, Mac OS or Linux computer. The eMMC can hence be flashed directly from your computer with any image similarly to a micro SD card.

'''This installation method works for all devices that support eMMC modules regardless of the chipset''' and it is therefore the preferred way of flashing OS images to eMMC. All available OS images for your device can be installed on the eMMC module this way.

*This process of flashing an OS image to eMMC is '''literally identical to imaging micro SD cards''', so please read [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards|Step-by-Step Instructions to Flashing Micro SD Cards]] before you begin.

For this method you will need the following:

*A Windows, Linux or Mac OS computer
*A PINE64 eMMC module
*The PINE64 USB-to-eMMC adapter

'''Flashing eMMC using the adapter'''

*Insert the the eMMC module into the USB adaptor and plug it into your Windows, Linux or Mac OS computer. It should mount as a regular USB drive and show up in your file manager.
*If you are using Linux or Mac OS you can either use the dd terminal command or a GUI utility such as [https://etcher.io/ Etcher] to flash the chosen OS Image to eMMC.
*If you are using a Windows machine use [https://etcher.io/ Etcher] or [https://sourceforge.net/projects/win32diskimager/ Win32 Disk Imager] to flash the OS Image to the eMMC module.

Once the image has been flashed using your preferred method safely dismount the USB adaptor in your system and unplug it from your computer. Your eMMC is now ready to boot and can be inserted into the eMMC socket on your PINE64 device.

----

=== Flashing to eMMC from a SD Boot ===

Some of the available Linux images for Allwinner A64 devices recognise eMMC modules as mounted storage when the device is booted from a micro SD card. This is true for all recent releases of [https://github.com/ayufan-pine64/linux-build/releases ayufan's Linux images]. In result it is possible to flash an OS image to eMMC using the DD command in terminal or the Disks GUI utility included with the Mate desktop.

There are '''two ways''' in which an OS image can be flashed from within a micro SD boot:
*Via a script called Pine64_install_to_eMMC.sh found in ''/usr/local/sbin''. This script will install an Ubuntu Mate OS installation (identical to the on running on the SD) to the eMMC module. To execute the script navigate to its location in the terminal and type <code>sudo ./Pine64_install_to_eMMC.sh</code>. Follow the instructions.

*By manually downloading and flashing a OS image for your device using DD or the Disk GUI. This way of flashing an OS image to the eMMC is identical to that used on a Linux computer (e.g. for flashing an OS image to a SD card). For more information on how the process works please see the detailed guide on [[NOOB#Imaging_microSD_on_Linux|imaging OS images to SD card on Linux]].

For the latter of the two methods here is a summary of the process:
*Flash an OS image which recognizes eMMC as mounted storage to a micro SD card. For details on how to flash a micro SD card see [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards|section 3]]
*Insert both the micro SD and eMMC module into your device and power it on.
*Once the PINE64 device boots from micro SD, you cannot flash the contents of the micro SD card to the eMMC while you are running from the micro SD so you will actually use this session to download an OS image to flash to the eMMC. Depending on the distribution this may be the same image you just flashed to the micro SD card and booted from.
*Once the OS image downloads check in terminal or in Disks utility the eMMC's mounting location and unmount all but "/". Example command to show disks and mounts:
::<blockquote><code>$ lsblk</code></blockquote>
*Use the DD command or Disks utility to flash the downloaded image to the eMMC module. Note your output device may be mmcblk1 or mmcblk2, use the command above to verify the correct one. Example DD command:
::<blockquote><code>$ xzcat imagename.img.xz | sudo dd of=/dev/mmcblk1 bs=1M status=progress conv=fsync</code></blockquote>
*Once the flashing process is completed power down your device and remove the micro SD card. You should now be able to power your device back up and it will boot the image flashed to the eMMC module.

----

=== Flashing to eMMC using FEL (Allwinner A64 Devices Only) ===

Under particular circumstances it may prove difficult to rely on a SD card to flash an OS image to an Allwinner A64 device. In such instances OS images can be directly flashed by means of entering into FEL mode. FEL is a low-level subroutine in the BootROM, and the process of enabling FEL differs from one device to another. To learn more about FEL please refer to the [https://linux-sunxi.org/FEL SUNXI Wiki section] dedicated to the subject.

The process of flashing via FEL is more complex than utilising a micro SD and is therefore '''better suited for proficient and advanced users'''.

For the process of flashing an image to the eMMC on a device in FEL mode you will need:
*A computer running Mac OS or Linux
*An OTG USB A-to-A cable

To enter FEL you will need to:
*On the Pinebook, power down the Pinebook and remove the PSU, unscrew the bottom of the case and press down the FEL button on the PCB (REF). Plug in the OTG USB A-to-A cord to your computer and the OTG USB port on the Pinebook (on the right facing an open case). Reinsert the PSU cord and press the power button with the FEL button pressed down. Release the FEL button after 3 seconds.
*On the Pine A64(+) power down the board and remove the micro SD card and power cord. Plug in the OTG USB A-to-A cord to your computer and the OTG USB port on the Pine A64 (+) and SoPine (top port). Power on the device and immediately after insert a micro SD card [https://app.box.com/s/s3m7rb5zfe0jkwqhaiy1zytqq3436fqs with FEL code].

You can check if your device entered FEL mode using ''lsusb'' command in terminal. It should be listed as a device on the USB Bus.

The next step is to mount your device so that your computer recognizes the eMMC as mass storage (UMS). A script called boot-tools streamlining this process is available '''thanks to ayufan''' on [https://github.com/ayufan-pine64/boot-tools his github]. Follow his instructions and in terminal perform the following steps:

::<code>git clone <nowiki>https://github.com/ayufan-pine64/boot-tools.git</nowiki></code>

::<code>cd boot-tools</code>

::<code>make pinebook_ums</code>

or

::<code>make pine64_ums</code>

Once your device mounts as UMS it will appear in your file manager. In CLI you can check if the storage is listed using ''fdisk -l''.

This process of flashing an OS image to eMMC with the device in FEL mode and mounted as UMS is '''literally identical to imaging micro SD cards''', so please read [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards|Step-by-Step Instructions to Flashing Micro SD Cards]] and follow the procedure. You can use DD or Disks/ Disk Utility to flash the OS image directly to your device's eMMC.

Once the flashing process is completed, power down your device, remove the A-to-A USB OTG cable and after reapply power to boot your device from eMMC.

----

=== Flashing to eMMC using Rockchip Tools (Rock64 Only) ===

Rockchip has a different boot hierarchy to Allwinner's devices making it much more difficult to flash OS images using the micro SD-to-eMMC scheme used on A64. There are, however, flashing tools that make it possible to flash directly to eMMC on a Rock64 in loader and MarkROM modes.

To flash to the eMMC module using these tools you will need the following:
*A Windows, Mac OS or Linux computer
*An A-to-A USB cable
*The Rock64 board with the eMMC module inserted into the socket

'''Using Windows 7/8.1/10 '''
You will need to download the [https://github.com/rockchip-linux/tools/tree/master/windows DriverAssistant aka Rockchip driver] as well as the [https://github.com/rockchip-linux/tools/tree/master/windows AndroidTool_Release] used for flashing OS images. Having completed the downloads extract both archives.The Rockchip driver needs to be installed prior to using the AndroidTool utility.

Having installed the driver and flashing utility, follow these steps:
*Make sure that eMMC is inserted into the slot on the Rock64
*Place a jumper / short out the eMMC pins on the board (consult [https://files.pine64.org/doc/rock64/guide/ROCK64_Installing_Android_To_eMMC.pdf this PDF document] for more details.
*Insert one end of the A-to-A cable into your Windows PC and the other into your Rock64 OTG USB port (top)
*Inset the power cord into the Rock64
*Start AndroidTool; make sure that it reports 'Found One Maskrom Device' (if it does not recognise your device, please repeat previous steps)
*Select either the latest Stock Android build or ayufan's Android TV build with the suffic -update. Download and the extract the chosen image.
*In AndroidTool press the firmware tab and navigate to where you extracted the OS image and select it.
*Press the upgrade tab. You will be prompted when the flashing process is completed.
*Remove the USB A-to-A cable, power off your board and power it on again to boot into eMMC.

'''Using Linux or Mac OS'''

*Make sure that eMMC is inserted into the slot on the Rock64
*Download latest stable or pre-release (to be used at own risk) Android TV OS image from [https://github.com/ayufan-rock64/android-7.1/releases ayufan's github]. The image you wish to download is the one '''without a suffix'''; without -update or -raw in the OS image title.
*In terminal, download rkflashtool following instructions on [https://github.com/ayufan-rock64/android-7.1/blob/master/README.md ayufan's github]
*Extract the folder containing partitions of the OS image and place the script listed on ayufan's github in the folder
*Hold down the recovery button on the board
*Insert one end of the A-to-A cable into your Mac OS or Linux PC and the other into your Rock64 OTG USB port (top)
*Inset the power cord into the Rock64
*Check that your device is in loader mode by typing in the terminal <code>sudo rkflashtool n</code>. If rkflashtool doesn't detect the Rock64 please repeat last 3 steps
*In terminal navigate to where you extracted the Android folder containing the OS partitions and the script and type <code>rkinstall</code>; this will install the community Android TV build to eMMC.
*Remove the USB A-to-A cable, power off your board and power it on again to boot into eMMC.

----

=== Flashing to eMMC Android 'Update' OS Images on Linux (Rock64 Only) ===

It is possible to flash Android 'update' images to the Rock64 eMMC using a Linux PC. This process requires a tool called [https://www.haoyuelectronics.com/service/RK3066/tools/linux/Linux_Upgrade_Tool_v1.2.tar.gz Linux Upgrade Tool] and the full documentation of its functions can be found [https://www.hotmcu.com/wiki/Flashing_Firmware_Image_Files_Using_The_Rockchip_Tool#Using_Linux_Upgrade_Tool_to_flash_update.img here]. Make sure that you download v1.2 or newer, as older tools do not support the RK3328 used on the Rock64.

To flash the eMMC module using this method you will need the following:
*A Linux computer
*An A-to-A USB cable
*The Rock64 board with the eMMC module inserted into the socket

Start by downloading an Android '''update''' image for the Rock64. Both PINE64 and Ayufan provide such images for the board - and they are clearly designated as such on both this WiKi's download section and on ayufan's github. For the purpose of this example, I'll use the ayufan's ATV community build:

*Download latest stable or pre-release (to be used at own risk) Android TV OS image from [https://github.com/ayufan-rock64/android-7.1/releases ayufan's github]. The image you wish to download is the one '''with update suffix'''. You need to '''rename the downloaded image to update.img'''.
*Download the [https://www.haoyuelectronics.com/service/RK3066/tools/linux/Linux_Upgrade_Tool_v1.2.tar.gz Linux Upgrade Tool] to your Linux PC and unarchived it.
*Extract the archived update Android OS image somewhere where you will remember its path
*Hold down the recovery button on the board
*Insert one end of the A-to-A cable into your Mac OS or Linux PC and the other into your Rock64 OTG USB port (top)
*Inset the power cord into the Rock64
*In terminal, navigate to where you extracted Rockchip Update Tool and issue the following command substituting the correct path for where the Android Update OS Image is located:

::<code>sudo ./upgrade_tool uf /path/to/update.img</code>

*Wait as the utility installs Android to eMMC on your Rock64.
*Remove the USB A-to-A cable, power off your board and power it on again to boot into eMMC.

== Flashing u-boot to SPI Flash ==

Some of PINE64 devices, such as the Rock64 and SOPine, are equipped with SPI Flash. This allows users to flash u-boot onto the SPI and boot from an external USB 2.0 or USB 3.0 SSD/HDD/thumb-drive, thereby forgoing use of eMMC or microSD card.

To find out more about which images can used in conjunction for SPI booting please see [https://github.com/ayufan-rock64/ ayufan's github].

Writing u-boot to SPI Flash can be achieved in two ways:

=== Using a Stand-Alone Image to Write u-boot to SPI ===
This may be the simplest method of flashing u-boot to SPI. Download a dedicated image labelled '''u-boot-flash-spi.img.xz''' from [https://github.com/ayufan-rock64/linux-u-boot/releases ayufan's github] and flash it to a microSD card, the same as you would with any OS image (to learn how to flash OS images to microSD please follow steps outlined in [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards|Section 3]].

'''Having flashed the image follow these steps''':

*Insert the SD into the ROCK64
*Remove all other peripherals from the board
*'''Make sure that the eMMC module is disconnected from the board'''
*Apply power to the ROCK64
*Wait (few seconds) until the the LEDs on the board will blink continually
*Power off the board.

The board is now ready to boot from USB 2.0/3.0 storage.

=== Using a Script on Linux OS Images ===
Most of recent (newer than 0.6.9) Linux OS images contain a script called '''rock64_write_spi_flash.sh''', which is found in ''/usr/local/sbin'' directory. To run the script you will first need to flash a Linux OS image to a micro SD card (to learn how to flash OS images to micro SD please following steps outlined in [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards|Section 3]]). Before proceeding '''make sure that the eMMC module is disconnected''' from the board. Once you have booted into Linux on your PINE64 device all you have to do is run the aforementioned script using this command:

::<code>sudo ./rock64_write_spi_flash.sh</code>

Once the script finishes its operation, power off your board and remove the microSD card.
The board is now ready to boot from USB 2.0/3.0 storage.

=== Erasing and Rewriting SPI ===
There are two ways of removing u-boot from SPI. You can either download '''u-boot-flash-spi.img.xz''' from [https://github.com/ayufan-rock64/linux-u-boot/releases ayufan's github] or use a script found on Linux OS images titled:'''rock64_erase_spi_flash.sh'''. Follow the instructions in the previous sub-sections for the chosen method of removing u-boot from SPI; the instructions are are identical, as the process of erasing u-boot is the exact opposite of flashing it.

{{hint|'''N.B.''' You can also erase SPI manually.}}
To do so, you need to download mtd-utils. on Debian or Ubuntu follow these instructions:

::<code>sudo apt-get install mtd-utils</code>

::<code>sudo flash_eraseall /dev/mtd0</code>

=== Booting an OS image from USB 2.0/3.0 Storage ===
To boot an OS image from USB 2.0/3.0 Storage such as a SSD/HDD or a thumbdrive you first need to have u-boot written to your SPI flash. Please follow the instructions in the previous sub-sections to learn how to write u-boot to SPI on your PINE64 device.

Once you have u-boot on your SPI, the process of booting is very similar to booting from microSD or eMMC.
*Download one of the supported OS images for your PINE64 device
*Flash the OS image to your USB 2.0/USB 3.0 storage device (to learn how to flash OS images please following steps outlined in [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards|Section 3]] The instructions are identical for all types of storage, including USB 2.0/USB 3.0 HDDs and thumb-drives.)
*Insert the USB storage device with the flashed OS image into one of the USB ports on your PINE64 device
*Apply power

If you have followed all the steps correctly, the board should boot from your USB 2.0/3.0 storage device.

== Troubleshooting Your Device ==

A number of things can prevent the PINE64 board from booting up properly. The most common culprits of a failed boot are: (to find out more click [https://forum.pine64.org/showthread.php?tid=514 here])

* Subpar or counterfeit microSD card
* Subpar Power Supply
* High resistance (thin) or a very long microUSB cable
* Failed imaging of the microSD card or eMMC module

Make sure to have the newest version of the OS image your are running. On Allwinner A64 devices running Linux you can update the kernel and uboot using scripts located in the following directory: /usr/local/sbin

* To navigate to the directory type (in terminal): <code>cd /usr/local/sbin</code>
* You list all the available scripts by typing (in terminal): <code>ls</code>
* To run the script required update script run the following command: <code>sudo ./update_script.sh</code> (substitute the relevant update script for <code>update_script</code>)

'''Troubleshooting Step by Step'''

Follow these steps to determine the cause of your problem:

* Check your PSU and microUSB cable ratings
* Download and image a base image of Linux
* Plug in power and Ethernet into your PINE64 device
* Watch Ethernet port LED activity
* Check your router for your device's IP
* Attempt to ssh into your device's from your computer

If your PSU and microUSB meet the criteria, and you have correctly followed the instructions to image your card and power on the board, but you are not seeing any LED activity and cannot ssh into your device then either the imaging process failed (possibly due to a subpar microSD) OR the PSU / microUSB cable is/are faulty.

If your PSU and microUSB meet the criteria, and you have correctly imaged the OS to your card and power on the board and your can ssh into your PINE A64(+) but get no video feed, then it's likely that the native resolution of your monitor/TV is not supported.

If neither of the above mentioned scenarios fits the problem you are facing, please consult this thread (thanks to Ghost for compiling the list): https://forum.pine64.org/showthread.php?tid=680

If you cannot find a solution to your problem you can submit a ticket at: https://support.pine64.org/

[[Category:Guide]]

Getting started

2021-10-08T00:41:51Z

RainSlide: /* Imaging microSD on Apple OSX */ Rework

== Setting Up Your device - What You’ll Need to Get Started ==

You will need the following to get started with using your PINE A64(+), SOPine/PINE A64-LTS, Pinebook or ROCK64 board:
* Windows / Linux PC or MAC with a MicroSD Card Reader and connection to the Internet.
* Power Supply
:: For PINE A64(+): Power Supply (PSU) and a micro usb cable. Please make sure to use a PSU rated at +5V @2A and a micro USB cable that is at least 26 AWG thick.
:: For SOPine/PINE A64-LTS: Power Supply (PSU) with 3.5mm OD/1.5mm ID barrel DC Jack. Please make sure to use a PSU rated at +5V @2A.
:: For Pinebook and ROCK64: Power Supply (PSU) with 3.5mm OD/1.5mm ID barrel DC Jack. Please make sure to use a PSU rated at +5V @3A.
* MicroSD card (8GB or higher capacity) rated 'class 10' or better.
* HDMI cable (unless you wish to run headless / without a monitor). On '''A64 Devices''' Android and Remix OS support 720p and 1080p, while Linux supports a [https://github.com/longsleep/sunxi-disp-tool#available-hdmi-output-names wider range of resolutions].
* Input device(s) such as: keyboard, mouse, remote, pointer, etc.

== Step-by-Step Instructions for Flashing MicroSD Cards ==

{{Note|'''Caution!''' Handle the Pine64 Single Board Computers' PCBs with care. Always hold bare boards by the edges and make sure to wear an anti-static wrist strap. Touching components on the front and back of the boards can result in an ESD discharge that may cause damage to the electronics. Avoid placing bare boards on materials such as carpets, plastics or other surfaces prone to electrostatic build-up}}

'''Begin by imaging the OS of your choice'''

The process of flashing PINE64 OS images to micro SD on your Windows, Linux or OSX device is the same for all devices. You will require a quality microSD card (8GB or greater; class 10 or faster). There are many [https://forum.pine64.org/showthread.php?tid=681 substandard and counterfeit cards] in circulation and even reputable vendors may unknowingly sell counterfeit microSD cards. Cards that do not meet the criteria outlined above are known to cause a variety of issues including, but not limited to, complete boot failure. There are ways of testing microSD cards prior to installing the operating system to make sure they are appropriate for use with your board. The main utility for checking microSD cards is [https://www.softpedia.com/get/System/System-Miscellaneous/H2testw.shtml#download H2testw 1.4]; yet another alternative is [https://github.com/AltraMayor/f3/archive/v6.0.zip F3]. Yet another overview of various options [https://www.raymond.cc/blog/test-and-detect-fake-or-counterfeit-usb-flash-drives-bought-from-ebay-with-h2testw/ Test and Detect Fake Cards]

Please refer to the relevant section below for instructions on how to image your microSD card:
* [[#Imaging microSD on Windows 7/8/8.1/10|Imaging microSD on Windows 7/8/8.1/10]]
* [[#Imaging microSD on Apple OSX|Imaging microSD on Apple OSX]]
* [[#Imaging microSD on Linux|Imaging microSD on Linux]]

Having successfully imaged your microSD card, insert it into the microSD slot.

'''Plug in the HDMI Cable, Ethernet Cable and Peripherals to your PINE64 SBC'''

Unless you are planning on running your board headless (without a monitor / as a server) you should plug in all necessary peripherals, including the HDMI and Ethernet cable, prior to powering ON the board. Do note, depending on which OS image you are using, some peripherals may or may not work.

'''Apply Power to Your Board'''

Once you have imaged your microSD and plugged everything in, you are ready to apply power to the PINE64 Single Board Computer. You'll need a good quality 5 Volt, 2 Amp PSU. Using a good quality PSU is very important as failing to meet the required specifications may prevent the board from booting correctly. A marginally higher PSU Voltage is acceptable (for instance, 5.1 volts - due to the nature of the micro usb connection, a 5.1v supply can help protect slightly against voltage drops which can cause undesirable results). However, a significantly higher voltage of 7 Volts or more will damage the PINE64 Single Board Computer and may render it inoperative.

For PINE A64(+) board, if you are using a separate micro USB cable with your PSU, make sure that the cable has a low resistance rating. Cables with high resistance will cause improper function and the unit may not boot at all or only partially. The thicker the internal cabling, the better [https://voyager8.blogspot.co.uk/2013/04/how-to-choose-good-usb-data-and.html i.e. AWG (American Wire Gauge) 20 is better than AWG 28]. In General, '''power-only microUSB''' cables come with red colour USB header.

Having completed the steps outlined above the PINE64 Single Board Computer will begin to boot. The onboard power-on LEDs will come on and Ethernet port LEDs will start to blink if you have an Ethernet cable plugged in.

----

=== Imaging microSD on Windows 7/8/8.1/10 ===

You will need the following utilities to get started with imaging the OS of your choice onto your microSD card:
* A compression utility (used to unarchive the OS image). We recommend you use [https://www.7-zip.org/download.html 7zip].
* A disk image utility (used to flash the .img to your SD card). We recommend you use either the [https://etcher.io/ Etcher] or [https://sourceforge.net/projects/win32diskimager/ Win32Imager] utility.

'''Optional for Allwinner A64 SoC based boards'''
* Phoenix Card image utility (used ONLY for phoenix card images). You can download it from [https://drive.google.com/file/d/0B0cEs0lxTtL3VmstaEFfbmU1NFk/view?usp=sharing here].

'''Downloading and extracting OS image(s)'''

You can find OS images for the respective devices in the [[Main_Page|device section]] on the main page.
Images designated ‘DD’ need to be flashed using Etcher or Win32imager, whilst images labelled ‘Phoenix Card Image’ require the Phoenix Card utility.

Having downloaded the required OS image proceed to use 7zip to unarchive it by right-clicking the archive, and selecting ‘Extract All’. Upon completion, note the destination of where the .img file was extracted (‘Downloads’ folder by default). Once the process has completed, you can proceed to imaging the .img file.

'''Imaging the microSD card (DD)'''

* Insert your microSD card into your laptop/USB card reader. You may require a SD → microSD converter, as most laptops and desktops only feature a full-size SD card reader. Once the microSD card is plugged into your computer, make sure to take note of the drive it has been assigned (the drive is assigned a letter, e.g. ‘F:’). You will need to remember the ‘letter’ it has been assigned when imaging the OS.

* Launch Win32diskImager.exe or etcher.exe. You will be presented with a field titled ‘path’ and a drop down menu labeled ‘device’. Click the ‘path’, navigate to and select the OS image you extracted from the archive earlier. Next, from the drop-down menu select the drive your microSD has been assigned. {{warning|'''N.B.''' Pay close attention to the selected drive (remember your letter) – the imaging process will permanently erase and format the selected drive. If you choose the wrong drive all your data will be lost.}}

* Having chosen the desired OS image and the correct driver press ‘write’. Once the image has been written to your microSD card you will receive a pop-up notification. Be sure to close the application and to eject/remove your SD card safely from Windows.

'''Imaging using Phoenix Card (applicable only to Allwinner A64 SoC based boards)'''

On Windows, you can also use Phoenix Card (for detailed instructions click [[PhoenixCard|here]]). The Phoenix Card utility works ONLY with images designated as ‘Phoenix Card’ in the downloads section. To use Phoenix Card follow these steps:

* Insert your microSD card into your laptop/USB card reader. You may require a SD → microSD converter, as most laptops and desktops only feature a full-size SD card reader. Once the microSD card is plugged into your computer, make sure to take note of the drive it has been assigned (the drive is assigned a letter, e.g. ‘F:’). You will need to remember the ‘letter’ it has been assigned when imaging the OS.

* Launch phoenixcard.exe. You will be presented with a ‘disk’ drop-down menu and a field denoted as ‘.img File’. Click on ‘.img File’ and navigate to and select the OS image have downloaded and unarchived. Next, make sure to select the disk that your microSD card has been assigned. {{warning|'''N.B.''' Pay close attention to the selected drive (remember your letter) – the imaging process will permanently erase and format the selected drive. If you choose the wrong drive all your data will be lost.}}

* Make sure to select ‘Startup!’ from the ‘Write mode’ window and click Burn. Once the image has been written to your microSD card you will receive a confirmation in the ‘option’ window. Be sure to close the application and to eject/remove your SD card safely from Windows.

----

=== Imaging microSD on macOS ===

You will need the following utilities to get started with imaging the OS of your choice onto your microSD card:

* A compression utility (used to unarchive the OS image). You may use [https://www.keka.io/en/ Keka].
* A disk image utility (used to flash the .img to your SD card in GUI). You may use [https://www.tweaking4all.com/software/macosx-software/applepi-baker-v2/#DownloadApplePiBaker ApplePi Baker v2] or [https://etcher.io/ Etcher].

{{hint|'''N.B.''' Phoenix Card utility and images are NOT available on macOS.}}

'''Downloading and extracting OS image(s), insert the SD card'''

You can find OS images for the respective devices in the [[Main_Page#Devices|device section]] of the main page.

Having downloaded the required OS image, proceed to use the compression utility to unarchive it and get the .img file.
Once the process has completed, you can proceed to write it to your SD card.

Insert your microSD card into your Mac laptop/USB card reader.
You may require a SD → microSD converter, as Apple’s laptops and desktops only feature a full-size SD card reader.
Once the microSD card is plugged into your computer, it should appear in Finder / on your desktop.

'''Imaging the microSD card (GUI)'''

Launch the imaging utility. Upon startup, the application may ask for your password.
When the application launches, you will be presented with a field titled ‘IMG file’ and a path of the mounted microSD card
(it will look like this: ‘/dev/diskX 32.0Gb SD card’).

To choose the OS image file, click the ‘IMG file’ button, navigate to and select the .img file you extracted from the archive earlier.
Then select the microSD card you want to write into.

{{warning|'''N.B.''' Pay close attention to the selected device, make sure it is the right SD card – the imaging process will permanently erase and format the selected storage device. If you choose the wrong device, all the data in it will be lost.}}

Having chosen the desired OS image and the correct device, press ‘Restore Backup’ or ‘Flash’.
Once the image has been written to your microSD card, you will receive a pop-up notification.
Close the application, then eject/remove your SD card from your Mac.

'''Imaging from Terminal'''

{{note|'''N.B.''' If you are not comfortable using the terminal, please use the GUI method outlined above instead.}}

Open up your terminal and navigate to the directory where you unarchived your OS image.

Before you start writing to the card, you will have to identify your microSD card.
Type: <code>diskutil list</code> and note the output.
The disk number should match the size of your SD card, and will likely be using <code>Fdisk_partition_scheme</code>.

Having identified the disk number execute the following commands
(substitute diskX for your disk and name of image for pine64-image-name.img):

diskutil unmountDisk /dev/diskX
sudo dd if=pine64-image-name.img of=/dev/disk2 bs=1M

Wait patiently for the process to complete, then eject/remove your SD card from your Mac.

----

=== Imaging microSD on Linux ===

You will need the following utilities to get started with imaging the OS of your choice onto your microSD card:
* A compression Utility (used to unarchive the OS image). We recommend you use [https://apps.kde.org/en/ark Ark].
* A disk image utility (used to flash the .img to your SD card in GUI). We recommend you use [https://etcher.io/ Etcher] or the [https://git.gnome.org/browse/gnome-disk-utility/ GUI Disks utility] that ships with most popular distros.
{{hint|'''N.B.''' Phoenix Card utility and images are NOT available on Linux.}}

'''Downloading and extracting OS image(s)'''

You can find OS images for the respective devices in the [[Main_Page|device section]] on the main page. On Linux you can only use images designated as ‘DD’.

Having downloaded the required OS image proceed to use 7zip to unarchive it by double clicking the archive, and selecting ‘Extract All’. Upon completion, note the destination where the .img file was extracted (‘Downloads’ folder by default). Once the process has completed, you can proceed to imaging the .img file.

'''Imaging the microSD card (GUI)'''

* Insert your microSD card into your Linux laptop/USB card reader. Once the microSD card is plugged into your computer it should appear in your File Manager / on your desktop.

* Launch Disks or the etcher utility (This tutorial outlines how to use Disks, if you wish to learn how to use Etcher please visit [https://etcher.io/ their website]).

* Upon launching Disks, you will be presented with all volumes visible to your computer. As a rule of thumb, your microSD card should be found at the bottom of listed volumes. Verify this by checking the size and mounting of the microSD card. {{warning|'''N.B.''' Pay close attention to the selected drive – the imaging process will permanently erase and format the selected drive. If you choose the wrong drive all your data will be lost.}}

* Having selected your microSD card, click the cog menu in top right corner and choose the ‘Restore Disk Image’ option from the drop-down list. Navigate to and select the OS image you extracted from the archive earlier. Once you select it, you will be asked to enter your password and to confirm writing to the chosen volume (microSD card).

* You will be given a predicted time, writing-speed and completion percentage. Once the image has been written to your microSD card you will receive a pop-up notification. Be sure to close the application and to eject/remove your SD card safely from your computer.

'''Imaging from Terminal'''

::{{note|'''N.B.''' If you are not comfortable using the terminal, please use the GUI method outlined above instead.}}

* Insert your microSD card into your Linux laptop/USB card reader. Once the microSD card is plugged into your computer it should appear in Finder / on your desktop.
* Open up your terminal and navigate to the directory where you unarchived your OS image. e.g. <code>cd Download</code>
* Before you start writing to the card, you will have to identify your microSD card.

* Type: <code>lsblk</code> and pay attention to the listed disks. Disks will appear as ''/dev/mmcblk0 /dev/mmcblk1'' etc.
::{{note|'''Hint''': the drive you currently have booted from has the <code>/</code> at the end of the line. This is the wrong drive. Look at the drive that matches your microSD card’s size.}}

* Now you are ready to write the image to the microSD card using this command: (replace the pine.img file with your image and mmcblkX with the correct device for the microSD card)
::<code>sudo umount /dev/mmcblkX</code>
::<code>sudo dd if=pine.img of=/dev/mmcblkX bs=1M status=progress conv=fsync</code>

* Wait patiently for the process to complete.
* use the command <code>sync</code> to ensure everything is written to the microSD card.
* The card is ready to boot

(sometimes this process fails and your microSD card can't boot, one way of fixing this is just to repeat the same thing, you can also try a different microSD card)

== Instructions to Flashing eMMC Modules ==

All PINE64 devices - with the '''notable exception of the original Pine A64(+) SBC''' - support eMMC modules as an alternative boot and storage solution to micro SD cards.
An eMMC module can be purchased for your device(s) from the [https://pine64.com/?post_type=product PINE64 store]. The only PINE64 device that ships with an eMMC module by default is the Pinebook.

The available modules come in three different capacities: 16Gb, 32Gb, 64Gb and 128Gb

There are a few ways to flash eMMC modules with the desired OS image. The following sections are a summary of the processes involved in flashing the OS image of your choice to the eMMC module.

----

=== Flashing Using the USB-to-eMMC Adapter (Preferred Way) ===

A USB-to-eMMC adapter is available from purchase from the [https://pine64.com/product/usb-adapter-for-emmc-module/ PINE64 Store] making it easy to mount the eMMC module as a volume in your Windows, Mac OS or Linux computer. The eMMC can hence be flashed directly from your computer with any image similarly to a micro SD card.

'''This installation method works for all devices that support eMMC modules regardless of the chipset''' and it is therefore the preferred way of flashing OS images to eMMC. All available OS images for your device can be installed on the eMMC module this way.

*This process of flashing an OS image to eMMC is '''literally identical to imaging micro SD cards''', so please read [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards|Step-by-Step Instructions to Flashing Micro SD Cards]] before you begin.

For this method you will need the following:

*A Windows, Linux or Mac OS computer
*A PINE64 eMMC module
*The PINE64 USB-to-eMMC adapter

'''Flashing eMMC using the adapter'''

*Insert the the eMMC module into the USB adaptor and plug it into your Windows, Linux or Mac OS computer. It should mount as a regular USB drive and show up in your file manager.
*If you are using Linux or Mac OS you can either use the dd terminal command or a GUI utility such as [https://etcher.io/ Etcher] to flash the chosen OS Image to eMMC.
*If you are using a Windows machine use [https://etcher.io/ Etcher] or [https://sourceforge.net/projects/win32diskimager/ Win32 Disk Imager] to flash the OS Image to the eMMC module.

Once the image has been flashed using your preferred method safely dismount the USB adaptor in your system and unplug it from your computer. Your eMMC is now ready to boot and can be inserted into the eMMC socket on your PINE64 device.

----

=== Flashing to eMMC from a SD Boot ===

Some of the available Linux images for Allwinner A64 devices recognise eMMC modules as mounted storage when the device is booted from a micro SD card. This is true for all recent releases of [https://github.com/ayufan-pine64/linux-build/releases ayufan's Linux images]. In result it is possible to flash an OS image to eMMC using the DD command in terminal or the Disks GUI utility included with the Mate desktop.

There are '''two ways''' in which an OS image can be flashed from within a micro SD boot:
*Via a script called Pine64_install_to_eMMC.sh found in ''/usr/local/sbin''. This script will install an Ubuntu Mate OS installation (identical to the on running on the SD) to the eMMC module. To execute the script navigate to its location in the terminal and type <code>sudo ./Pine64_install_to_eMMC.sh</code>. Follow the instructions.

*By manually downloading and flashing a OS image for your device using DD or the Disk GUI. This way of flashing an OS image to the eMMC is identical to that used on a Linux computer (e.g. for flashing an OS image to a SD card). For more information on how the process works please see the detailed guide on [[NOOB#Imaging_microSD_on_Linux|imaging OS images to SD card on Linux]].

For the latter of the two methods here is a summary of the process:
*Flash an OS image which recognizes eMMC as mounted storage to a micro SD card. For details on how to flash a micro SD card see [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards|section 3]]
*Insert both the micro SD and eMMC module into your device and power it on.
*Once the PINE64 device boots from micro SD, you cannot flash the contents of the micro SD card to the eMMC while you are running from the micro SD so you will actually use this session to download an OS image to flash to the eMMC. Depending on the distribution this may be the same image you just flashed to the micro SD card and booted from.
*Once the OS image downloads check in terminal or in Disks utility the eMMC's mounting location and unmount all but "/". Example command to show disks and mounts:
::<blockquote><code>$ lsblk</code></blockquote>
*Use the DD command or Disks utility to flash the downloaded image to the eMMC module. Note your output device may be mmcblk1 or mmcblk2, use the command above to verify the correct one. Example DD command:
::<blockquote><code>$ xzcat imagename.img.xz | sudo dd of=/dev/mmcblk1 bs=1M status=progress conv=fsync</code></blockquote>
*Once the flashing process is completed power down your device and remove the micro SD card. You should now be able to power your device back up and it will boot the image flashed to the eMMC module.

----

=== Flashing to eMMC using FEL (Allwinner A64 Devices Only) ===

Under particular circumstances it may prove difficult to rely on a SD card to flash an OS image to an Allwinner A64 device. In such instances OS images can be directly flashed by means of entering into FEL mode. FEL is a low-level subroutine in the BootROM, and the process of enabling FEL differs from one device to another. To learn more about FEL please refer to the [https://linux-sunxi.org/FEL SUNXI Wiki section] dedicated to the subject.

The process of flashing via FEL is more complex than utilising a micro SD and is therefore '''better suited for proficient and advanced users'''.

For the process of flashing an image to the eMMC on a device in FEL mode you will need:
*A computer running Mac OS or Linux
*An OTG USB A-to-A cable

To enter FEL you will need to:
*On the Pinebook, power down the Pinebook and remove the PSU, unscrew the bottom of the case and press down the FEL button on the PCB (REF). Plug in the OTG USB A-to-A cord to your computer and the OTG USB port on the Pinebook (on the right facing an open case). Reinsert the PSU cord and press the power button with the FEL button pressed down. Release the FEL button after 3 seconds.
*On the Pine A64(+) power down the board and remove the micro SD card and power cord. Plug in the OTG USB A-to-A cord to your computer and the OTG USB port on the Pine A64 (+) and SoPine (top port). Power on the device and immediately after insert a micro SD card [https://app.box.com/s/s3m7rb5zfe0jkwqhaiy1zytqq3436fqs with FEL code].

You can check if your device entered FEL mode using ''lsusb'' command in terminal. It should be listed as a device on the USB Bus.

The next step is to mount your device so that your computer recognizes the eMMC as mass storage (UMS). A script called boot-tools streamlining this process is available '''thanks to ayufan''' on [https://github.com/ayufan-pine64/boot-tools his github]. Follow his instructions and in terminal perform the following steps:

::<code>git clone <nowiki>https://github.com/ayufan-pine64/boot-tools.git</nowiki></code>

::<code>cd boot-tools</code>

::<code>make pinebook_ums</code>

or

::<code>make pine64_ums</code>

Once your device mounts as UMS it will appear in your file manager. In CLI you can check if the storage is listed using ''fdisk -l''.

This process of flashing an OS image to eMMC with the device in FEL mode and mounted as UMS is '''literally identical to imaging micro SD cards''', so please read [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards|Step-by-Step Instructions to Flashing Micro SD Cards]] and follow the procedure. You can use DD or Disks/ Disk Utility to flash the OS image directly to your device's eMMC.

Once the flashing process is completed, power down your device, remove the A-to-A USB OTG cable and after reapply power to boot your device from eMMC.

----

=== Flashing to eMMC using Rockchip Tools (Rock64 Only) ===

Rockchip has a different boot hierarchy to Allwinner's devices making it much more difficult to flash OS images using the micro SD-to-eMMC scheme used on A64. There are, however, flashing tools that make it possible to flash directly to eMMC on a Rock64 in loader and MarkROM modes.

To flash to the eMMC module using these tools you will need the following:
*A Windows, Mac OS or Linux computer
*An A-to-A USB cable
*The Rock64 board with the eMMC module inserted into the socket

'''Using Windows 7/8.1/10 '''
You will need to download the [https://github.com/rockchip-linux/tools/tree/master/windows DriverAssistant aka Rockchip driver] as well as the [https://github.com/rockchip-linux/tools/tree/master/windows AndroidTool_Release] used for flashing OS images. Having completed the downloads extract both archives.The Rockchip driver needs to be installed prior to using the AndroidTool utility.

Having installed the driver and flashing utility, follow these steps:
*Make sure that eMMC is inserted into the slot on the Rock64
*Place a jumper / short out the eMMC pins on the board (consult [https://files.pine64.org/doc/rock64/guide/ROCK64_Installing_Android_To_eMMC.pdf this PDF document] for more details.
*Insert one end of the A-to-A cable into your Windows PC and the other into your Rock64 OTG USB port (top)
*Inset the power cord into the Rock64
*Start AndroidTool; make sure that it reports 'Found One Maskrom Device' (if it does not recognise your device, please repeat previous steps)
*Select either the latest Stock Android build or ayufan's Android TV build with the suffic -update. Download and the extract the chosen image.
*In AndroidTool press the firmware tab and navigate to where you extracted the OS image and select it.
*Press the upgrade tab. You will be prompted when the flashing process is completed.
*Remove the USB A-to-A cable, power off your board and power it on again to boot into eMMC.

'''Using Linux or Mac OS'''

*Make sure that eMMC is inserted into the slot on the Rock64
*Download latest stable or pre-release (to be used at own risk) Android TV OS image from [https://github.com/ayufan-rock64/android-7.1/releases ayufan's github]. The image you wish to download is the one '''without a suffix'''; without -update or -raw in the OS image title.
*In terminal, download rkflashtool following instructions on [https://github.com/ayufan-rock64/android-7.1/blob/master/README.md ayufan's github]
*Extract the folder containing partitions of the OS image and place the script listed on ayufan's github in the folder
*Hold down the recovery button on the board
*Insert one end of the A-to-A cable into your Mac OS or Linux PC and the other into your Rock64 OTG USB port (top)
*Inset the power cord into the Rock64
*Check that your device is in loader mode by typing in the terminal <code>sudo rkflashtool n</code>. If rkflashtool doesn't detect the Rock64 please repeat last 3 steps
*In terminal navigate to where you extracted the Android folder containing the OS partitions and the script and type <code>rkinstall</code>; this will install the community Android TV build to eMMC.
*Remove the USB A-to-A cable, power off your board and power it on again to boot into eMMC.

----

=== Flashing to eMMC Android 'Update' OS Images on Linux (Rock64 Only) ===

It is possible to flash Android 'update' images to the Rock64 eMMC using a Linux PC. This process requires a tool called [https://www.haoyuelectronics.com/service/RK3066/tools/linux/Linux_Upgrade_Tool_v1.2.tar.gz Linux Upgrade Tool] and the full documentation of its functions can be found [https://www.hotmcu.com/wiki/Flashing_Firmware_Image_Files_Using_The_Rockchip_Tool#Using_Linux_Upgrade_Tool_to_flash_update.img here]. Make sure that you download v1.2 or newer, as older tools do not support the RK3328 used on the Rock64.

To flash the eMMC module using this method you will need the following:
*A Linux computer
*An A-to-A USB cable
*The Rock64 board with the eMMC module inserted into the socket

Start by downloading an Android '''update''' image for the Rock64. Both PINE64 and Ayufan provide such images for the board - and they are clearly designated as such on both this WiKi's download section and on ayufan's github. For the purpose of this example, I'll use the ayufan's ATV community build:

*Download latest stable or pre-release (to be used at own risk) Android TV OS image from [https://github.com/ayufan-rock64/android-7.1/releases ayufan's github]. The image you wish to download is the one '''with update suffix'''. You need to '''rename the downloaded image to update.img'''.
*Download the [https://www.haoyuelectronics.com/service/RK3066/tools/linux/Linux_Upgrade_Tool_v1.2.tar.gz Linux Upgrade Tool] to your Linux PC and unarchived it.
*Extract the archived update Android OS image somewhere where you will remember its path
*Hold down the recovery button on the board
*Insert one end of the A-to-A cable into your Mac OS or Linux PC and the other into your Rock64 OTG USB port (top)
*Inset the power cord into the Rock64
*In terminal, navigate to where you extracted Rockchip Update Tool and issue the following command substituting the correct path for where the Android Update OS Image is located:

::<code>sudo ./upgrade_tool uf /path/to/update.img</code>

*Wait as the utility installs Android to eMMC on your Rock64.
*Remove the USB A-to-A cable, power off your board and power it on again to boot into eMMC.

== Flashing u-boot to SPI Flash ==

Some of PINE64 devices, such as the Rock64 and SOPine, are equipped with SPI Flash. This allows users to flash u-boot onto the SPI and boot from an external USB 2.0 or USB 3.0 SSD/HDD/thumb-drive, thereby forgoing use of eMMC or microSD card.

To find out more about which images can used in conjunction for SPI booting please see [https://github.com/ayufan-rock64/ ayufan's github].

Writing u-boot to SPI Flash can be achieved in two ways:

=== Using a Stand-Alone Image to Write u-boot to SPI ===
This may be the simplest method of flashing u-boot to SPI. Download a dedicated image labelled '''u-boot-flash-spi.img.xz''' from [https://github.com/ayufan-rock64/linux-u-boot/releases ayufan's github] and flash it to a microSD card, the same as you would with any OS image (to learn how to flash OS images to microSD please follow steps outlined in [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards|Section 3]].

'''Having flashed the image follow these steps''':

*Insert the SD into the ROCK64
*Remove all other peripherals from the board
*'''Make sure that the eMMC module is disconnected from the board'''
*Apply power to the ROCK64
*Wait (few seconds) until the the LEDs on the board will blink continually
*Power off the board.

The board is now ready to boot from USB 2.0/3.0 storage.

=== Using a Script on Linux OS Images ===
Most of recent (newer than 0.6.9) Linux OS images contain a script called '''rock64_write_spi_flash.sh''', which is found in ''/usr/local/sbin'' directory. To run the script you will first need to flash a Linux OS image to a micro SD card (to learn how to flash OS images to micro SD please following steps outlined in [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards|Section 3]]). Before proceeding '''make sure that the eMMC module is disconnected''' from the board. Once you have booted into Linux on your PINE64 device all you have to do is run the aforementioned script using this command:

::<code>sudo ./rock64_write_spi_flash.sh</code>

Once the script finishes its operation, power off your board and remove the microSD card.
The board is now ready to boot from USB 2.0/3.0 storage.

=== Erasing and Rewriting SPI ===
There are two ways of removing u-boot from SPI. You can either download '''u-boot-flash-spi.img.xz''' from [https://github.com/ayufan-rock64/linux-u-boot/releases ayufan's github] or use a script found on Linux OS images titled:'''rock64_erase_spi_flash.sh'''. Follow the instructions in the previous sub-sections for the chosen method of removing u-boot from SPI; the instructions are are identical, as the process of erasing u-boot is the exact opposite of flashing it.

{{hint|'''N.B.''' You can also erase SPI manually.}}
To do so, you need to download mtd-utils. on Debian or Ubuntu follow these instructions:

::<code>sudo apt-get install mtd-utils</code>

::<code>sudo flash_eraseall /dev/mtd0</code>

=== Booting an OS image from USB 2.0/3.0 Storage ===
To boot an OS image from USB 2.0/3.0 Storage such as a SSD/HDD or a thumbdrive you first need to have u-boot written to your SPI flash. Please follow the instructions in the previous sub-sections to learn how to write u-boot to SPI on your PINE64 device.

Once you have u-boot on your SPI, the process of booting is very similar to booting from microSD or eMMC.
*Download one of the supported OS images for your PINE64 device
*Flash the OS image to your USB 2.0/USB 3.0 storage device (to learn how to flash OS images please following steps outlined in [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards|Section 3]] The instructions are identical for all types of storage, including USB 2.0/USB 3.0 HDDs and thumb-drives.)
*Insert the USB storage device with the flashed OS image into one of the USB ports on your PINE64 device
*Apply power

If you have followed all the steps correctly, the board should boot from your USB 2.0/3.0 storage device.

== Troubleshooting Your Device ==

A number of things can prevent the PINE64 board from booting up properly. The most common culprits of a failed boot are: (to find out more click [https://forum.pine64.org/showthread.php?tid=514 here])

* Subpar or counterfeit microSD card
* Subpar Power Supply
* High resistance (thin) or a very long microUSB cable
* Failed imaging of the microSD card or eMMC module

Make sure to have the newest version of the OS image your are running. On Allwinner A64 devices running Linux you can update the kernel and uboot using scripts located in the following directory: /usr/local/sbin

* To navigate to the directory type (in terminal): <code>cd /usr/local/sbin</code>
* You list all the available scripts by typing (in terminal): <code>ls</code>
* To run the script required update script run the following command: <code>sudo ./update_script.sh</code> (substitute the relevant update script for <code>update_script</code>)

'''Troubleshooting Step by Step'''

Follow these steps to determine the cause of your problem:

* Check your PSU and microUSB cable ratings
* Download and image a base image of Linux
* Plug in power and Ethernet into your PINE64 device
* Watch Ethernet port LED activity
* Check your router for your device's IP
* Attempt to ssh into your device's from your computer

If your PSU and microUSB meet the criteria, and you have correctly followed the instructions to image your card and power on the board, but you are not seeing any LED activity and cannot ssh into your device then either the imaging process failed (possibly due to a subpar microSD) OR the PSU / microUSB cable is/are faulty.

If your PSU and microUSB meet the criteria, and you have correctly imaged the OS to your card and power on the board and your can ssh into your PINE A64(+) but get no video feed, then it's likely that the native resolution of your monitor/TV is not supported.

If neither of the above mentioned scenarios fits the problem you are facing, please consult this thread (thanks to Ghost for compiling the list): https://forum.pine64.org/showthread.php?tid=680

If you cannot find a solution to your problem you can submit a ticket at: https://support.pine64.org/

[[Category:Guide]]

Main Page

2021-10-08T00:09:50Z

RainSlide: /* Chat Platforms */ Make changes according to Talk:Main_Page#Riot_is_now_Element

PINE64 is a community-driven company focused on creating high-quality, low-cost ARM devices and, more recently, RISC-V devices for individuals and businesses around the globe. PINE64 made its debut with the [[PINE A64|PINE A64]] single-board computer, which successfully launched on Kickstarter in 2015. PINE64 has since released a multitude of other devices, including both development boards and end-user devices.

PINE64 has a large, diverse and active community, and offers a variety of resources for hobbyists and businesses to successfully leverage various PINE64 products. To become connected and involved with the community, please see [[Main Page#Community and Support|Community and Support]] for a list of available channels and chat platforms. To learn more about PINE64, please visit the [https://www.pine64.org/ PINE64 website] and the [https://www.pine64.com/ PINE64 store]'''.

For information about PINE64 branding, including the usage of the PINE64 logo in non-commercial and other applications please read the [https://wiki.pine64.org/wiki/PINE64_brand_and_logo article about our brand and logo].

= Devices =

[[File:Marchupdate-1024x594.jpg|thumb|upright=1.2|[[Pinebook Pro]] (left) and [[PinePhone]] (right)]]

You can learn more about the following ARM and RISC-V devices manufactured by PINE64:

* Phones and tablets: '''[[PinePhone]]''', '''[[PineNote]]''' and '''[[PineTab]]'''
* Smartwatches: '''[[PineTime]]'''
* Laptops: '''[[Pinebook]]''', '''[[Pinebook Pro]]''' and '''[[Pinebook Pro Dock|Pinebook Pro Docking station]]'''
* Single-board computers: '''[[Quartz64]]''', '''[[ROCKPro64]]''', '''[[ROCK64]]''', '''[[PINE A64]]''', '''[[PINE A64-LTS/SOPine|PINE A64-LTS]]''' and '''[[PINE H64]]'''
* Clusters and modules: '''[[Clusterboard]]''', '''[[SOPine]]''', '''[[SOPine Baseboard]]''' and '''[[SOEdge]]'''
* IP cameras: '''[[PineCube]]'''
* Makerspace: '''[[Pinecil]]''', '''[[PinePower]]''', '''[[PineCone]]''' and '''[[Pinedio]]'''

= Community and Support =

Community collaboration and support is focused around the chat platforms and forums described below. As an example of the collaborative efforts of the community, recent activity has resulted in drafting a [[PineFlash|proposal]] for a new flash-based storage device. See [https://www.pine64.org/gettings-started/ Getting Started | PINE64] for tips about how to get started with the PINE64 community.

== Chat Platforms ==

PINE64 has a large and very active community. Community discussion takes place on a variety of chat platforms, which are all bridged together so the messages sent via one platform are sent to all other platforms automatically. The community chat platforms are the following:

* '''Discord''': use the [https://discordapp.com/invite/DgB7kzr invite link]. All channels are available.
* '''Matrix''' and '''Telegram''':
{| class="wikitable"
! Channel !! Matrix !! Telegram
|-
| PINE64 News
| [https://app.element.io/#/room/#pine64-announcements:matrix.org #pine64-announcements:matrix.org]
| [https://t.me/PINE64_News @PINE64_News]
|-
| General PINE64 chat
| [https://app.element.io/#/room/#pine64:matrix.org #pine64:matrix.org]
| [https://t.me/mtrx_pine64 @mtrx_pine64]
|-
| PINE A64(+), A64-LTS & SOPine
| [https://app.element.io/#/room/#pine64sopine:matrix.org #pine64sopine:matrix.org]
| [https://t.me/pine64sopine @pine64sopine]
|-
| ROCK64 / ROCKPro64
| [https://app.element.io/#/room/#rock64:matrix.org #rock64:matrix.org]
| [https://t.me/mtrx_rock64 @mtrx_rock64]
|-
| Quartz64
| [https://app.element.io/#/room/#quartz64:matrix.org #quartz64:matrix.org]
| [https://t.me/joinchat/Vq50DXkH31e0_i-f Quartz64]
|-
| Quartz64 Development
| [https://app.element.io/#/room/#quartz64-dev:matrix.org #quartz64-dev:matrix.org]
| [https://t.me/q64dev @q64dev]
|-
| Pinebook and Pinebook Pro
| [https://app.element.io/#/room/#pinebook:matrix.org #pinebook:matrix.org]
| [https://t.me/mtx_pinebook @mtx_pinebook]
|-
| PinePhone
| [https://app.element.io/#/room/#pinephone:matrix.org #pinephone:matrix.org]
| [https://t.me/pinephone @pinephone]
|-
| PineNote
| [https://app.element.io/#/room/#pinenote:matrix.org #pinenote:matrix.org]
| [https://t.me/pinenote @PineNote]
|-
| PineTab
| [https://app.element.io/#/room/#pinetab:pine64.org #pinetab:matrix.org]
| [https://t.me/PineTab @PineTab]
|-
| PineTime
| [https://app.element.io/#/room/#pinetime:matrix.org #pinetime:matrix.org]
| [https://t.me/pinetime @pinetime]
|-
| PineTime Development
| [https://app.element.io/#/room/#pinetime-dev:matrix.org #pinetime-dev:matrix.org]
| [https://t.me/pinetime_dev @pinetime_dev]
|-
| Pinecil
| [https://app.element.io/#/room/#pinecil:matrix.org #pinecil:matrix.org]
| [https://t.me/joinchat/Kmi2S1iej-_4DgrVf3jjnQ Pinecil]
|-
| Pinetalk Podcast || Unavailable || Unavailable
|-
| Cube
| [https://app.element.io/#/room/#cube64:matrix.org #cube64:matrix.org]
| [https://t.me/pinecube @pinecube]
|-
| Nutcracker
| [https://app.element.io/#/room/#pine64-nutcracker:matrix.org #pine64-nutcracker:matrix.org]
| [https://t.me/joinchat/Kmi2S0nOsT240emHk-aO6g Nutcracker]
|-
| LoRa
| [https://app.element.io/#/room/#pinelora:matrix.org #pinelora:matrix.org]
| [https://t.me/pine64lora @pine64lora]
|-
| Off-topic
| [https://app.element.io/#/room/#offtopic64:matrix.org #offtopic64:matrix.org]
| [https://t.me/pine64offtopic @pine64offtopic]
|}

* '''Matrix Space''': There is an unofficial Matrix Space at [https://app.element.io/#/room/#pine64-space:matrix.org #pine64-space:matrix.org] that organizes all of the channels into one place. Requires the spaces beta to be enabled in Element or other supported clients.

* '''IRC''': The IRC channels can be reached via <i>irc.pine64.org</i>. Support requests via IRC are discouraged, users are advised to look into the Matrix communication protocol as contemporary solution instead.

== Forums ==

PINE64 runs an official forum powered by the open-source forum server software MyBB. The forum can be used to report issues, help out other users, offer findings and new information and more. Users can also engage directly with the community and the developers of partner projects, as well as with the PINE64 members.

The official PINE64 forum can be accessed here:
* [https://forum.pine64.org/ Official PINE64 Forum]

Also, these are the official Subreddits:

* [https://www.reddit.com/r/PINE64official/ Official PINE64 Reddit]
* [https://www.reddit.com/r/PinePhoneOfficial/ Official PinePhone Reddit]

= Helpful Information for Beginners =

* '''[[NOOB | Getting started]]''': Basic information on setting up and handling PINE64 devices, such as how to write (flash) OS images to microSD cards and eMMC modules
* '''[[Notes | PINE64 Wiki contributing Notes]]''': Some notes on prioritized and suggested writing or editing to this Wiki, as well as long-term goals and wiki housekeeping tasks.
* '''[[:Category:Guide]]''': Lists other guide pages than those two above, some are delicated to spicific devices.

Talk:Main Page

2021-10-08T00:09:08Z

RainSlide: /* Riot is now Element */

== Account email ==

Hi Pine64 wiki administrator,<BR/>
    I don't see where to add my email address for watchlist notification emails (and password reset) on this MediaWiki instance. Please can you enable email support?<BR/>
—[[User:JRHaigh|JRHaigh]] ([[User talk:JRHaigh|talk]]) 2020-08-07Fri16:09:45‎Z

: For the admin: this is $wgEnotifWatchlist, see https://www.mediawiki.org/wiki/Manual:Configuration_settings#Email_notification_(Enotif)_settings. --[[User:Fxc|Fxc]] ([[User talk:Fxc|talk]]) 11:32, 9 August 2020 (UTC)

== MediaWiki time substitution ==

Hi Pine64 wiki administrator,<BR/>
    Please can you enable the [//en.Wikipedia.org/wiki/Help:Time_function time function] on this MediaWiki instance such that my usual MediaWiki signature works correctly:
<nowiki>—{{subst:nowrap|[[User:JRHaigh|]] ([[User talk:JRHaigh|talk]]) {{subst:#time: Y-m-d}}{{subst:color|grey|{{subst:#time: D}}}}{{subst:#time: H:i:s}}Z}}</nowiki>
—[[User:JRHaigh|JRHaigh]] ([[User talk:JRHaigh|talk]]) 2020-08-07Fri16:27:51‎Z

: Please use the usual sign function in the talk pages, which is <nowiki>--~~~~</nowiki>. --[[User:Fxc|Fxc]] ([[User talk:Fxc|talk]]) 11:28, 9 August 2020 (UTC)

== Riot is now Element ==

Please update the URLs to riot.io to point to app.element.io. [[User:Pander|Pander]] ([[User talk:Pander|talk]]) 22:26, 16 November 2020 (UTC)

: Should we use https://matrix.to/ links instead? It looks nice, but it adds additional interaction steps. - [[User:RainSlide|RainSlide]] ([[User talk:RainSlide|talk]]) 00:07, 8 October 2021 (UTC)

== Add descriptions ==

Please add descriptions to each set of communications channels, i.e. which are bridges and which not (e.g. IRC). [[User:Pander|Pander]] ([[User talk:Pander|talk]]) 10:46, 17 November 2020 (UTC)

: I've implemented your suggestion, thanks. For IRC it's hard to list all missing channels as just a few of them are bridged to IRC as of now. If you have suggestions let me know or feel free to implement them, cheers. --[[User:Fxc|Fxc]] ([[User talk:Fxc|talk]]) 00:20, 26 January 2021 (UTC)

== Pine64 keep version verizon ==

Hello all just got my phone I have a activated verizon sim in my current phone I popped out the sim used the adaptor and put it in the pine64 when I check sim all info is there my ime and phone number when I check modem it is listed but when I look at apn it is blank so i cannot make calls is there a way to edit in the verizon info been searching but the instructions I find do not fit with what I see like the + button on the apn screen I do not have any help would be appreciated. [[User:Bregga|Bregga]] ([[User talk:Bregga|talk]]) 03:55, 23 January 2021‎ (UTC)

: Please use the bridged chat channels for support, not the wiki page. The APN settings are only for mobile data Internet, not for calls. The setting doesn't do anything on Plasma Mobile yet. Details in the chat then. --[[User:Fxc|Fxc]] ([[User talk:Fxc|talk]]) 23:16, 25 January 2021 (UTC)

Talk:Main Page

2021-10-08T00:08:07Z

RainSlide: /* Riot is now Element */ matrix.to?

== Account email ==

Hi Pine64 wiki administrator,<BR/>
    I don't see where to add my email address for watchlist notification emails (and password reset) on this MediaWiki instance. Please can you enable email support?<BR/>
—[[User:JRHaigh|JRHaigh]] ([[User talk:JRHaigh|talk]]) 2020-08-07Fri16:09:45‎Z

: For the admin: this is $wgEnotifWatchlist, see https://www.mediawiki.org/wiki/Manual:Configuration_settings#Email_notification_(Enotif)_settings. --[[User:Fxc|Fxc]] ([[User talk:Fxc|talk]]) 11:32, 9 August 2020 (UTC)

== MediaWiki time substitution ==

Hi Pine64 wiki administrator,<BR/>
    Please can you enable the [//en.Wikipedia.org/wiki/Help:Time_function time function] on this MediaWiki instance such that my usual MediaWiki signature works correctly:
<nowiki>—{{subst:nowrap|[[User:JRHaigh|]] ([[User talk:JRHaigh|talk]]) {{subst:#time: Y-m-d}}{{subst:color|grey|{{subst:#time: D}}}}{{subst:#time: H:i:s}}Z}}</nowiki>
—[[User:JRHaigh|JRHaigh]] ([[User talk:JRHaigh|talk]]) 2020-08-07Fri16:27:51‎Z

: Please use the usual sign function in the talk pages, which is <nowiki>--~~~~</nowiki>. --[[User:Fxc|Fxc]] ([[User talk:Fxc|talk]]) 11:28, 9 August 2020 (UTC)

== Riot is now Element ==

Please update the URLs to riot.io to point to app.element.io. [[User:Pander|Pander]] ([[User talk:Pander|talk]]) 22:26, 16 November 2020 (UTC)

Should we use https://matrix.to/ links instead? It looks nice, but it adds additional interaction steps. - [[User:RainSlide|RainSlide]] ([[User talk:RainSlide|talk]]) 00:07, 8 October 2021 (UTC)

== Add descriptions ==

Please add descriptions to each set of communications channels, i.e. which are bridges and which not (e.g. IRC). [[User:Pander|Pander]] ([[User talk:Pander|talk]]) 10:46, 17 November 2020 (UTC)

: I've implemented your suggestion, thanks. For IRC it's hard to list all missing channels as just a few of them are bridged to IRC as of now. If you have suggestions let me know or feel free to implement them, cheers. --[[User:Fxc|Fxc]] ([[User talk:Fxc|talk]]) 00:20, 26 January 2021 (UTC)

== Pine64 keep version verizon ==

Hello all just got my phone I have a activated verizon sim in my current phone I popped out the sim used the adaptor and put it in the pine64 when I check sim all info is there my ime and phone number when I check modem it is listed but when I look at apn it is blank so i cannot make calls is there a way to edit in the verizon info been searching but the instructions I find do not fit with what I see like the + button on the apn screen I do not have any help would be appreciated. [[User:Bregga|Bregga]] ([[User talk:Bregga|talk]]) 03:55, 23 January 2021‎ (UTC)

: Please use the bridged chat channels for support, not the wiki page. The APN settings are only for mobile data Internet, not for calls. The setting doesn't do anything on Plasma Mobile yet. Details in the chat then. --[[User:Fxc|Fxc]] ([[User talk:Fxc|talk]]) 23:16, 25 January 2021 (UTC)

PinePhone Software Releases

2021-10-07T23:06:42Z

RainSlide: Fix templates, add archmobile & DanctNIX Code of Conduct links

This page contains a list of all available OS releases for the [[PinePhone]], as well as links to other resources.

See [[PinePhone Installation Instructions]] on how to install the operating systems.<br>
However, if your phone came preloaded with software, Please see [[PinePhone Updating Instructions]].

{{Hint| '''Note:''' Some releases may not have a good setup for the backlight at low brightness.
If configured too low, the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.}}

= Software Releases =

This is a list of OSes that specifically support the PinePhone.
Since PinePhone support is included in Mainline Linux, in principle, any ARM Linux OS can be used if possible required patches are included.

== Arch Linux ARM ==
[[File:Archlinux-logo.png|right|100px]]

(Unofficial) Arch Linux ARM with choice of Phosh UI, Plasma Mobile, or barebones.
Currently being maintained by the [https://danctnix.org/ DanctNIX] community (GitHub: [https://github.com/DanctNIX/danctnix danctnix], [https://github.com/dreemurrs-embedded dreemurrs-embedded]).

* GitHub: [https://github.com/dreemurrs-embedded/Pine64-Arch dreemurrs-embedded/Pine64-Arch]

'''Download location'''

Get both stable and test builds at [https://github.com/dreemurrs-embedded/Pine64-Arch/releases GitHub releases].

'''username/password'''

{| class="wikitable"
! Default user
| <code>alarm/123456</code>
|-
! root
| <code>root/root</code>
|}

'''What works, what does not work'''

Most of the things now works, there are some minor issues with [[Crust]].

'''How to contribute and report defects'''

There are archmobile chat rooms on Matrix ([https://matrix.to/#/#archmobile:kde.org #archmobile:kde.org]) and Telegram ([https://t.me/archmobile @archmobile]).
You may find the Discord, Matrix and Telegram of DanctNIX community at [https://github.com/DanctNIX/danctnix/blob/master/README.md#channel-list the Channel list section of DanctNIX/README.md], read the [https://github.com/DanctNIX/danctnix/blob/master/docs/CODE_OF_CONDUCT.md Code of Conduct].

Feel free to send us [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls pull requests] and report [https://github.com/dreemurrs-embedded/Pine64-Arch/issues issues] on [https://github.com/dreemurrs-embedded/Pine64-Arch GitHub].

== ExpidusOS ==

A fork of [https://voidlinux.org Void Linux] with a custom fork of XFCE called [https://github.com/ExpidusOS/genesis Gensis] as the default desktop environment, developed by [https://midstall.com/ Midstall Software].

* [https://expidusos.com ExpidusOS official website]
* [https://wiki.expidusos.com/index.php/Main_Page ExpidusOS Wiki]
* [https://discord.gg/GVfBF2w Midstall Software Discord server]
* GitHub: [https://github.com/ExpidusOS ExpidusOS]

'''Download location'''

Check the [https://expidusos.com/download download page] for that latest version, or the [https://build.expidusos.com/ image file list] for all versions, look for the file name that starts with "pinephone".

'''username/password'''

expidus/expidus

'''What works, what does not work'''

The ExpidusOS Wiki has a page detailing [https://wiki.expidusos.com/index.php/Device:PinePhone supported features].

'''How to contribute and report defects'''

Join the [https://discord.gg/GVfBF2w Discord server] or corresponding repo at GitHub ([https://github.com/orgs/ExpidusOS/repositories repo list]).

== Fedora ==
[[File:Fedora-logo.png|right|100px]]

An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and [https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/ some additional packages] to tie it all together.
It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.

* Forum discussion: [https://forum.pine64.org/showthread.php?tid=9347 Fedora + Phosh for PinePhone]
* GitHub: [https://github.com/nikhiljha/pp-fedora-sdsetup nikhiljha/pp-fedora-sdsetup]

'''Download location'''

* [https://github.com/nikhiljha/pp-fedora-sdsetup/releases Flashable images]
* [https://github.com/nikhiljha/pp-fedora-sdsetup Build scripts]
* [https://copr.fedorainfracloud.org/coprs/njha/mobile/ Packages (Fedora COPR)]

There is also an FTP server with a full Fedora 34 workstation build with phosh: ftp://pine.warpspeed.dk/nightly/pinephone/ (Mount this with something like Nautilus)

'''username/password'''

pine/123456

'''What works, what does not work'''

WiFi, Bluetooth, SMS, Data, Calls all work!

There are still a few bugs though, and [https://xnux.eu/devices/pine64-pinephone.html#toc-feature-driver-support-matrix some features don't have driver support yet] on any PinePhone distribution.

'''How to contribute and report defects'''

Please send your bug reports to [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker].
Be sure to include logs if applicable!
Send us pull requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/pulls Github].

== Gentoo ==
[[File:GentooLogo.png|right|100px]]

{{hint|Please consider cross-compiling the software on the computer.
Long compilation times and heat production can lead to a reduced lifespan of the phone.}}

There are unofficial Gentoo overlays with ebuilds for the PinePhone.
There are no images - you'll be building it yourself, picking which kernel, bootloader and desktop environment you want to use.
You will be using the arm64 version of Gentoo.

'''Documentation'''

* https://stealthgun.tweakblogs.net/blog/19336/gentoo-on-a-pinephone
* https://wiki.gentoo.org/wiki/User:Dr41nU/PinePhone
* https://wiki.gentoo.org/wiki/PinePhone (incomplete)

'''Overlay locations'''

* https://gitlab.com/bingch/gentoo-overlay
* https://github.com/stealthgun/gjdwebserver-overlay

== GloDroid ==

{{Hint|There can be large intervals between release update, so available images may be outdated and do not reflect the state of the current developments.}}

A fully open source port of Android to the PinePhone.

* GitHub: [https://github.com/GloDroid GloDroid]

'''Download location'''

https://github.com/GloDroid/glodroid_manifest/releases (last release at 2021-05-20)

'''What works, what does not work'''

Works: WiFi, screen dimming, touchscreen and charging work.
Don't work: Bluetooth, Telephony, GPS, Sound

== LuneOS ==
[[File:WebOS-Ports-logo.png|right|100px]]

LuneOS is a open source mobile operating system based on [https://www.webosose.org/ webOS Open Source Edition]([https://github.com/webosose GitHub], previously known as [https://github.com/openwebos Open webOS]) by LG, comes with [https://webos-ports.org/wiki/Luna_Next Luna Next] UI, currently developed by the WebOS Ports community.

* [https://www.webos-ports.org/wiki/Main_Page WebOS Ports Wiki]
* [https://webos-ports.org/wiki/Pinephone_Info WebOS-Ports Wiki's Pinephone page]
* GitHub: [https://github.com/webOS-ports WebOS Ports]

'''Download location'''

* [http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]

It is recommended to use ''bmaptool'', which is faster than dd, and can decompress archived image files on-the-fly.

Syntax is:

bmaptool copy [from] [to]

For example:

bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-140.rootfs.wic.gz /dev/mmcblk0

.wic file can be treated as .img file when flashing. You may rename .wic file to .img when using GUI tools that require file extension to be .img.

== Maemo Leste ==
[[File:Maemoleste-logo.png|right|100px]]

[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices,
originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it.
The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices.

The new version Maemo 8 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel.
The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK].
The current version is Devuan Beowulf (Debian Buster) and has simultaneous support for both Devuan and Debian.

In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository].
To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's build]).
Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.

* [https://maemo-leste.github.io/ Maemo Leste website]
* [https://leste.maemo.org/Main_Page Maemo Leste Wiki]
** [https://leste.maemo.org/PinePhone PinePhone wiki page]
** [https://leste.maemo.org/Leste_FAQ Maemo Leste FAQ]
* GitHub: [https://github.com/maemo-leste maemo-leste]
* Twitter: [https://twitter.com/maemoleste @maemoleste]

'''Download location'''

[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds]. There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].

'''username/password'''

root/toor

You may use <code>sudo</code> directly.

'''What works, what does not work'''

For current status and workarounds, please read their [https://leste.maemo.org/PinePhone PinePhone wiki page].

'''How to contribute and report defects'''

Most discussion occurs at [ircs://irc.libera.chat:6697/#maemo-leste <code>#maemo-leste</code> on <code>irc.libera.chat</code>].
The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback.

All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki.

Submit [https://github.com/maemo-leste/bugtracker/issues bug reports] on github.
To track known issues, you may use these search terms:
[https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone],
[https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64].

Learn about
[https://leste.maemo.org/Development development],
[https://leste.maemo.org/Development/Porting_Packages porting packages],
[https://leste.maemo.org/Development/Building_Packages building packages],
[https://leste.maemo.org/Development/Tasks todo list],
and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian].
Some tasks have funding available.

== Manjaro ARM ==
[[File:Manjaro-logo.svg|right|100px]]

Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.

'''Download location'''

* Phosh: [https://github.com/manjaro-pinephone/phosh Stable] / [https://github.com/manjaro-pinephone/phosh-dev Dev]
* Plasma Mobile: [https://github.com/manjaro-pinephone/plasma-mobile Stable] / [https://github.com/manjaro-pinephone/plasma-mobile-dev Dev]
* Lomiri: [https://github.com/manjaro-pinephone/lomiri-dev Dev] (No longer maintained)

'''username/password'''

{| class="wikitable"
! Default user
| <code>manjaro/123456</code>
|-
! root
| <code>root/root</code>
|}

'''What works, what does not work'''

{{Hint| '''Note:''' At the first boot, the Phosh image will be loaded at a TTY login prompt for multiple minutes.}}

See Manjaro's release announcements on their forum.
Recent ones:
[https://forum.manjaro.org/t/manjaro-arm-beta12-with-phosh-pinephone/73099 Phosh],
[https://forum.manjaro.org/t/manjaro-arm-beta5-with-plasma-mobile-pinephone/69318 Plasma] and
[https://forum.manjaro.org/t/manjaro-arm-alpha3-with-lomiri-pinephone/49923 Lomiri].

'''How to contribute and report defects'''

See the end of the [https://forum.manjaro.org/t/manjaro-arm-beta7-with-phosh-pinephone/58901 announcement].

== Mobian ==
[[File:Debian-logo.png|right|100px]]

An unofficial [https://www.debian.org Debian] build for ARM64 running with Phosh (developed by Purism, uses Wayland instead of Xorg).
The base system is pure Debian, with only the GUI applications and a few others (ModemManager, WiFi chip firmware) being built from modified sources (as well as the kernel and u-boot).
Current version is Debian Bookworm.

'''Download location'''

[https://images.mobian-project.org/pinephone/nightly/ Nightly] /
[https://images.mobian-project.org/pinephone/installer/ Installer] /
[https://images.mobian-project.org/pinephone/ Stable]

Extract the image before installing:

$ gzip -d Downloads/mobian-pinephone-*.img.gz

See the [https://wiki.mobian-project.org/doku.php?id=install project page] for specific installation instructions.

'''username/password'''

mobian/1234

'''What works, what does not work'''

See [https://gitlab.com/mobian1/mobian-recipes/-/blob/master/README.md the project's README file] or [https://wiki.mobian-project.org/doku.php?id=pinephone the wiki] for most up to date status.

Check [https://gitlab.com/groups/mobian1/-/issues bug tracker] for known issues. Questions? Ask on our [https://forum.pine64.org/showthread.php?tid=9016 thread].

'''How to contribute and report defects'''

It is recommended that you log your bug reports in [https://gitlab.com/mobian1/issues the project's issue tracker].
As a general rule, issues with third-party apps (even the default ones) should be reported upstream.
A Mobian issue would be related to getting the hardware to work on the PinePhone,
but if unsure where the issue should be reported just open a ticket or ask.
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/mobian1 Gitlab].

'''Notes'''

See [https://wiki.mobian-project.org/doku.php?id=start the wiki] for additional information regarding screen resolution, USB networking, WiFi hotspot, Chatty and the repository.

== Multi-distro demo image ==

{{Warning | This is an demo image for testing different OSes before installing a regular image. It is highly discouraged attempting to use the image productively. The kernel is shared across the different OSes and is not being updated.}}

This image allow users to try many of the above Linux distributions easily, without having to figure out how to flash them individually and juggle with many microSD cards. Also called megi's 15-in-1 multi boot image.

* Main page: https://xnux.eu/p-boot-demo/
* Git repo: https://megous.com/git/pinephone-multi-boot/
* Forum discussion: [https://forum.pine64.org/showthread.php?tid=11347 UPDATED (June 2021): 17-distro multi-boot image for Pinephone (incl. 3GiB variant)]

'''Update 2021-06-02, using megi's kernel 5.13-rc4'''

DD image to SD card and boot. This image is for 16GiB or larger SD cards, also works if flashed to eMMC.

This is also a good build for charging depleted battery. Just boot up this build with power supply connected, keep the PinePhone charging for 3 hours at power down stage.

For more info on this build, please visit its entry the "News" section of its [https://xnux.eu/p-boot-demo/ web page].

* [http://dl.xnux.eu/p-boot-multi-2021-06-02.torrent Download torrent file from author's website]
* [http://dl.xnux.eu/p-boot-multi-2021-06-02/ Download img.zst from author's website] (speed limited to 512KiB/s)
* [http://mirror.uxes.cz/dl.xnux.eu/ Download torrent and img.zst from discord user uxes' mirror]
** '''File name:''' multi.img.zst
** '''SHA-256:''' <span style="word-break: break-all">9b099cdfece3ba862348ca32af6c51a41a1d161b1d897f9928ae8be3c824a0b6</span>
** '''File Size:''' 6.57GiB

* [https://files.pine64.org/os/PinePhone/Multi/p-boot-multi-2021-06-02.img.gz Direct download img.gz from pine64.org] (re-zipped from zstd to gzip)
** '''File name:''' p-boot-multi-2021-06-02.img.gz
** '''MD5:''' 2abdaafb01dd7519f678b5a7c6538493
** '''File Size:''' 6.8GB

Due to its size, download though torrent is suggested by the author on its main page.

{{hint | '''Note about .zst archive file:'''

On Linux, you may install or compile <code>zstd</code>, and write the image to SD card by using <code>zstdcat</code> and <code>dd</code>. See the "Installation" section of its [https://xnux.eu/p-boot-demo/ web page] for command examples.

On Windows, you may use [https://github.com/mcmilk/7-Zip-zstd 7-zip-zstd], it provides different installation method in the README.md.Install and extract the .img file from the zst archive, and flash with tools like [https://sourceforge.net/projects/win32diskimager/ Win32 Disk Imager].}}

Also see [[PinePhone Installation Instructions]].

'''username/password'''

All passwords, including root passwords, are <code>1111</code>.
sxmo username is <code>user</code>.

== Nemo Mobile ==
[[File:nemo_mobile.png|right|100px]]

Nemo Mobile is the open source build of Sailfish OS with a open source UI called [http://nemomobile.net/glacier-home/ Glacier] ([https://wiki.merproject.org/wiki/Nemo/Glacier Mer Wiki]), [http://nemomobile.net/pages/Hello_manjaro/ based on Manjaro].

* Website: [https://nemomobile.net/ Nemo Mobile UX team]
* [https://wiki.merproject.org/wiki/Nemo Mer Wiki page]

'''Download location'''

See the [https://nemomobile.net/installation/ installation page] on their website for the newest release and installation guides.

'''What works, what does not work'''

Development is now moving very fast after rebasing. For the current devel image, Wifi and Bluetooth works. Waydroid also works after switching to unstable.

'''How to contribute and report defects'''

For the Nemo Mobile UX itself:
* GitHub issues: https://github.com/nemomobile-ux/main/issues

For hardware:
* GitHub issues: https://github.com/neochapay/nemo-device-dont_be_evil/issues

== NixOS ==
[[File:nixos.png|right|100px]]

NixOS support is handled through the Mobile NixOS project.

* Project home page: [https://mobile.nixos.org/ Mobile NixOS]
* PinePhone device page: [https://mobile.nixos.org/devices/pine64-pinephone.html Pine64 PinePhone — Mobile NixOS]
* GitHub: [https://github.com/NixOS/mobile-nixos NixOS/mobile-nixos]

There is no pre-built complete image.
For now users, are expected to follow the instructions in the [https://mobile.nixos.org/getting-started.html Getting Started page],
and [https://mobile.nixos.org/devices/pine64-pinephone.html Project's device page].

'''What works, what does not work'''

Currently, it boots, it's just as compatible as the Android-based devices are with Mobile NixOS.
It even supports a bit more since it can use WiFi.

Support for all of the hardware will be coming, this project is a breadth-first work, where the work spans multiple devices in parallel.

'''How to contribute and report defects'''

On [https://github.com/NixOS/mobile-nixos/issues the project's repository].
Please specify that you are using a PinePhone when reporting issues.
Details about contributions and donations are on the [https://nixos.org/nixos/community.html NixOS website].

== OpenMandriva Lx ==
[[File:Oma-logo-22042013_300pp.png|right|100px]]

{{Hint| '''Note:''' This image is solely for testing purposes.}}

OpenMandriva Lx with Plasma Mobile as UI.

'''Download location'''

The official image can be found [https://sourceforge.net/projects/openmandriva/files/release/4.2/RC/Pinephone/ at sourceforge.net].
See [https://www.openmandriva.org/en/news/article/openmandriva-lx-4-3-rc-available-for-testing here] for the offical announcement.

'''What works, what does not work'''

From the [https://www.openmandriva.org/en/news/article/openmandriva-lx-4-3-rc-available-for-testing 4.3 announcement],
in future updates (4.3 and later), "Phone calls are working, and we have rewritten the camera app to be far more useful".

== openSUSE ==
[[File:SLEM-OS-logo.png|right|100px]]

Our images use the same [https://en.opensuse.org/Portal:Tumbleweed openSUSE Tumbleweed] base as our desktop images,
except what needs to be changed for the PinePhone.
The images include <i>zypper</i> (RPM) as the default package manager,
and have access to virtually the same (open source) software as our desktop repositories,
thanks to the [https://en.opensuse.org/Portal:Factory Factory] ports.
Using [https://en.opensuse.org/SDB:DNF dnf] is possible, if preferred.

'''Download links'''

* [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz Phosh] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz.sha256 SHA-256] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz.sha256.asc SHA-256 Signature]
* [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz Plasma Mobile] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz.sha256 SHA-256] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz.sha256.asc SHA-256 Signature]

To verify the images you need to import [https://build.opensuse.org/projects/devel:ARM:Factory:Contrib:PinePhone/public_key our GPG key].
Keep on mind that the first boot may stay on black screen for about a minute - consequent boots should be faster.

You can find install instructions at [https://en.opensuse.org/HCL:PinePhone#Installing_openSUSE_in_a_Pinephone this section] in the openSUSE Wiki.

'''Username/Password'''

The login credentials are pine/1234 and root/linux.
Change (or disable) the root password once you are set up.

'''What works and what does not work'''

You can find all information about the releases of the project [https://gitlab.com/slem.os/slem.os/-/blob/master/CHANGELOG.md here].
Detailed information, tips and troubleshooting suggestions are also provided at [https://en.opensuse.org/HCL:PinePhone the openSUSE Wiki].
You will also find information in our wiki on how to report issues (Contributing section).

== postmarketOS ==
[[File:PostmarketOS-logo.png|right|100px]]

postmarketOS extends [https://www.alpinelinux.org/ Alpine Linux] to run on smartphones and other mobile devices.
It offers various user interfaces (Phosh, Plasma Mobile, Sxmo, Plasma Desktop, Gnome 3, Kodi, XFCE4, ...).

As of writing, official images are provided with Phosh, Plasma Mobile and Sxmo.
The official images come in two flavors, either as a test image to try out postmarketOS, or with the installer.

When using the installer images (recommended), it is possible to:
* encrypt the installation
* install from the SD card to eMMC

Power users may also create their own image with the distribution's install and development tool <code>pmbootstrap</code>.

Please read the detailed [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation installation instructions] in the wiki.

'''Download location'''

* [https://postmarketos.org/download/ Download page]
* [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation Flashing instructions]

'''Username/password'''

* Test images: user/147147
* When using the installer images or building an image with pmbootstrap, you set your own username and password.
** The Phosh and Plasma Mobile lock screens only support numeric keyboard, so you should '''only use numbers''' in your password.

'''What works, what does not work'''

See the [https://gitlab.com/postmarketOS/pmaports/-/issues?label_name%5B%5D=device-pine64-pinephone issue tracker].

'''How to contribute and report defects'''

[https://gitlab.com/postmarketOS/pmaports/-/issues?label_name%5B%5D=device-pine64-pinephone postmarketOS issue tracker] for PinePhone support.
See [https://wiki.postmarketos.org/wiki/Contributing postmarketOS wiki] for options to contribute.

== PureOS ==
[[File:Pureos.png|right|100px]]

{{Warning|This project is no longer under development and has been abandoned. Use [https://wiki.pine64.org/wiki/PinePhone_Software_Releases#Mobian Mobian] instead}}

{{Hint|There is no prebuilt image, you'll need a Linux environment and build the image yourself.}}

[https://www.pureos.net/ PureOS] is a user friendly, secure and freedom respecting GNU/Linux distribution based on Debian and GNOME developed by the Purism community.

* [https://tracker.pureos.net/w/ PureOS Wiki], no PinePhone page there
* Mobile-optimized apps list from the [https://tracker.pureos.net/w/pureos/mobile_optimized_apps/ Software Center in PureOS] and [https://tracker.pureos.net/w/pureos/3rd-party_mobile_optimized_apps/ 3rd party repos]
* [https://github.com/rufferson/pureos-pinephone current PinePhone PureOS repo], A script to convert Librem5 PureOS to PinePhone Pure-OS

'''Download location'''

Use [https://raw.githubusercontent.com/rufferson/pureos-pinephone/master/build_image.sh the convert script] to download and build the image from u-boot, PinePhone linux kernel and Librem5 PureOS.

Also see:
* [https://forums.puri.sm/t/successful-installation-of-pureos-on-pinephone/8741/12 Successful installation of PureOS on PinePhone - PureOS - Purism community]
* The PureOS section of [https://www.ruff.mobi/go/mobi/pine.html PinePhone page] on ruff.mobi
* An [https://gitlab.com/a-wai/debos-pinephone archived repo] for PureOS on PinePhone
* A [https://mozzwald.com/pp/ file list] with [https://mozzwald.com/pp/pureos-pinephone-build-instructions.txt pureos pinephone build instructions] on mozzwald.com

== Sailfish OS ==
[[File:Sailfish_logo.png|right|100px]]

[https://sailfishos.org/ Sailfish OS] is a Linux-based operating system based on open source projects such as [https://wiki.merproject.org/wiki/Main_Page Mer], and a closed source UI based on [https://sailfishos.org/wiki/Lipstick Lipstick].

* [https://wiki.merproject.org/wiki/Adaptations/PinePhone64 PinePhone Wiki Page] on Mer Wiki, for both Nemo Mobile and Sailfish OS.
* [https://gitlab.com/pinephone-sailfish-os/linux-kernel/ Linux kernel config repo]
* [https://gitlab.com/sailfishos-porters-ci/dont_be_evil-ci/ Sailfish OS repo]

'''Download location'''

'''Flashing script'''

The Sailfish OS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].

The script downloads the image and bootloader from the CI, extracts everything and burns it onto the SD card.
Note: The script will format and erase the SD card!

Instructions:
# Download the flashing script
# Insert a microSD card in your device
# Make the script executable: <code>chmod +x flash-it.sh</code>
# Verify that you have the <code>bsdtar</code> package installed
# Execute it: <code>./flash-it.sh</code>
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).

* When asked where to flash, type 'raw' and it will build the image on your computer. Otherwise define the path /dev/.... to flash to card or internal emmc.

'''username/password'''

Set PIN on initialization.

* Sometimes the first run stalls before the tutorial. Reboot and it will start from setting the security pin.
* The homescreen may be locked unless you boot with a sim card inserted. An old expired sim will do. '''If you do not have a SIM card on hands, do NOT set a security code on first boot.'''
* When a screen with a loading circle is displayed, just left/right swipe it away.
* If you're not familiar with Sailfish OS, pay attention to the tutorial - the interface works great, but is not immediately obvious. If you are familiar with it, you can skip the tutorial by touching all 4 corners starting top left.

'''What works, what does not work'''

See the [https://wiki.merproject.org/wiki/Adaptations/PinePhone64#Hardware_Support Hardware Support section] on the Mer Wiki's PinePhone Page.

There is a limited selection of apps available from the Jolla store, the vast majority are hosted on openrepos.net. If the Storeman app for openrepos is not preinstalled, download the RPM and click to install.

'''How to contribute and report defects'''

See the [https://wiki.merproject.org/wiki/Adaptations/PinePhone64#Installation Installation section] on the Mer Wiki's PinePhone Page for compile, build and development.

Git repo links are at the top of this OS section. other repos that may be helpful:

* [https://github.com/sailfish-on-dontbeevil GitHub project page]
* [https://github.com/sailfish-on-dontbeevil/flash-it the repo of the flash-it.sh flashing script]
* [https://build.merproject.org/project/show/nemo:devel:hw:pine:dontbeevil Mer Open Build Service page] ([https://forum.sailfishos.org/t/changes-needed-to-merge-the-project-names-to-sailfish-os/1672 Mer is being assimilated into Sailfish OS] and [https://forum.sailfishos.org/t/obs-shut-down-and-next-steps/1814 OBS is shutting down], also see [https://specs.openstack.org/openstack/fuel-specs/specs/7.0/replace-obs.html OpenStack is replacing OBS with another build system based on Jenkins], if it's related, even OBS come back under Sailfish OS, it will be different.)

See the [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues Sailfish OS wiki] for links to their forum, as well as info required when reporting an issue. See the [https://sailfishos.org/wiki/SailfishOS Sailfish OS wiki main page] for options to contribute to Sailfish OS.

'''Notes'''

OTA is supported: <code>zypper refresh && zypper update</code> as root (<code>devel-su</code> to get root access). Things that need reflash are bootloader specific at the moment. If improvements like [[Crust]] or changes of partition layout are added, then you need to reflash.

== SkiffOS ==
[[File:SkiffOS-Icon-1.png|right|100px]]

Minimal in-memory cross-compiled OS optimized for hosting multiple in parallel Docker containers.

Provides the reliability of firmware with the ease-of-use of package managers.

Upgrade over-the-air via a simple rsync script, or copying 3 files.

Uses the [http://buildroot.org Buildroot] cross-compilation tool for support for all Pine64 boards.

Use configuration packages to configure distro:

{| class="wikitable"
! Package !! Distro
|-
| core/pinephone_neon || KDE Neon via Ubuntu repositories
|-
| core/pinephone_nixos || Nixos Mobile
|-
| core/pinephone_gentoo || Gentoo with Link-time Optimization & KDE Mobile or Phosh
|-
| core/pinephone_ubports || Ubuntu Ports for PinePhone
|-
| core/pinephone_manjaro_kde || Manjaro for PinePhone: KDE variant
|-
| core/pinephone_manjaro_phosh || Manjaro for PinePhone: Phosh variant
|-
| core/pinephone_manjaro_lomiri || Manjaro for PinePhone: Lomiri variant
|}

The boot-up OS is upgraded independently from the containers.

'''Download location'''

The repository and instructions can be found [https://github.com/skiffos/SkiffOS/tree/master/configs/pine64/phone here].

== Sxmo ==

A collection of Suckless programs to create a mobile UI. Based on postmarketOS.

'''Download location'''

Sxmo images can be found [https://images.postmarketos.org/bpo/ here] (in the ''/pine64-pinephone/sxmo/'' sections respectively).

'''username/password'''

user/147147

'''How to contribute and report defects'''

Contributing information is listed [https://git.sr.ht/~mil/sxmo-docs/tree/master/CONTRIBUTING.md here].

== Ubuntu Touch ==
[[File:Ubports-logo.png|right|100px]]

A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.

Ubuntu touch is a mobile version of Ubuntu developed by the UBports community.
Installation instructions can be found on
[https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone the UBports PinePhone project].
There is also a [https://github.com/goddard/pinephone/ script] to download the latest image and flash to your PinePhone.
In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://devices.ubuntu-touch.io/installer UBports installer] GUI tool.

'''Download location'''

[https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone UBports PinePhone project]

'''username/password'''

Set up during boot

'''What works, what does not work'''

Scroll down to the bottom of [https://gitlab.com/ubports/community-ports/pinephone this page].

'''How to contribute and report defects'''

See [https://gitlab.com/ubports/community-ports/pinephone UBports gitlab page].
See [https://ubports.com/foundation/sponsors UBports website] for how to donate.

= Tools =

There are software tools, that can be booted on the PinePhone.

== JumpDrive ==

JumpDrive can be used to flash the eMMC (and the microSD card), see [[PinePhone Installation Instructions#Using JumpDrive]].

See https://github.com/dreemurrs-embedded/Jumpdrive/releases for the latest image.
Make sure to download the "PinePhone" image and to unpack the archive before flashing.

= Factory Test OS =

{{Hint|'''Note:''' The magnetometer test will fail on the new Beta Edition, as the factory image wasn't updated for it yet.}}

On the Braveheart model, there was a postmarketOS based basic Factory Test OS pre-installed on the eMMC.
The developer Martijn Braam from postmarketOS has improved the functionality of the image considerably later.
Since the 20200501 version, it is able to test all the hardware.
It also includes functionality to install a new OS to the eMMC when using with an test image that includes that OS image.
The downloadable image just does the hardware tests.
Do not flash eMMC to test your device, just dd it to microSD and test from there.
New versions are distributed as part of the postmarketOS distribution.

Links:
* [https://images.postmarketos.org/pinephone/ Software Images] (download the latest one named like pine-pinephone-yyyyMMdd-factorytestX.img.xz)
* [https://gitlab.com/MartijnBraam/factorytest Git repo]
* [https://gitlab.com/MartijnBraam/factorytest/-/blob/master/README.rst Documentation]

== Factory-loaded OS builds ==

These are different operating system builds that was preloaded in the factory with testing utility.

Download the build, extract the image and dd it to a 8 GB or larger microSD card, then insert it into the PinePhone.
After power up or reboot, you may perform and complete the test routine, or apply the build from microSD card to eMMC.

All the download links below are direct download from pine64.org.

<div style="overflow: auto;">
{| class="wikitable" style="white-space: nowrap"
! OS
! Download Link
! File Size
! MD5
|-
| Beta Edition
| [https://files.pine64.org/os/PinePhone/BetaEdition/pine64-pinephone-plamo-beta-factorytest.img.xz pine64-pinephone-plamo-beta-factorytest.img.xz]
| 1.78GB
| <code>f16bce93504a52217540ac886863a418</code>
|-
| Mobian
| [https://files.pine64.org/os/PinePhone/Mobian/pine64-pinephone-20201207-factorytest-mobian.img.xz pine64-pinephone-20201207-factorytest-mobian.img.xz]
| 1.41GB
| <code>015be381ff4e650a7fca6d4eaa90d63d</code>
|-
| KDE
| [https://files.pine64.org/os/PinePhone/KDE/pine64-pinephone-20201208-factorytest-kde.img.xz pine64-pinephone-20201208-factorytest-kde.img.xz]
| 2.28GB
| <code>32979ff17b5ec4d358ce99f1aff0c77c</code>
|-
| Manjaro
| [https://files.pine64.org/os/PinePhone/Manjaro/pine64-pinephone-20201013-manjaro-stable-20201018-factory56.img.xz pine64-pinephone-20201013-manjaro-stable-20201018-factory56.img.xz]
| 1.04GB
| <code>4edfd4dceaefdd32a3417c1727161c29</code>
|-
| postmarketOS
| [https://files.pine64.org/os/PinePhone/PostMarketOS/pine64-pinephone-20200726-phosh-v20.05-factory.img.xz pine64-pinephone-20200726-phosh-v20.05-factory.img.xz]
| 517MB
| <code>244093be2f6d728fcbd1d29114607727</code>
|-
| Ubuntu Touch
| [https://files.pine64.org/os/PinePhone/UBPorts/PinePhone-flasher-ubuntu-7b.img.gz PinePhone-flasher-ubuntu-7b.img.gz]
| 1.05GB
| <code>2d7f5271e7a281db8f1b1219bedbe131</code>
|}
</div>

= Installing other ARM64 distributions =

{{Warning|Distributions not on this page may not even boot after you follow this section. In the best case, they will be barely usable.
This is more for fun, or if you would like to port a new distribution to the PinePhone.}}

{{Hint|'''Note:''' This section uses megi's kernel releases, and not the official ones from Pine64. While it is possible to use the official (and in the future, mainline) kernel, megi provides binary releases, which makes it very easy.}}

General steps:

# Create a boot partition (from 4 MB to about 252 MB) and a root partition (from the end of boot to the end of the card) filesystem on the SD card.
# Format the boot partition with vfat, and the root partition with a supported filesystem like ext4 or f2fs.
# Extract the root filesystem from your distribution's ARM image into the root filesystem on the SD card. Do not copy the partition, copy the files instead (in archive mode, like <code>rsync -ar</code>).
# Edit <code>/etc/fstab</code> to match your partitions.
# Grab megi's kernel from https://xff.cz/kernels/, Follow the instructions in the [https://xff.cz/kernels/README README], which involves copying the kernel modules into the SD card rootfs, and writing u-boot and the bootloader.

If you would like to see examples or specific commands for how to complete these steps, see:
* [https://github.com/nikhiljha/pp-fedora-sdsetup an example for Fedora], current unofficial [#Fedora] release
* [https://xnux.eu/howtos/install-arch-linux-arm.html an example for Arch Linux] by megi

= Other Resources =
Community
* [[Main_Page#Community_and_Support|Links to the community services]]

Hardware information
* [[PinePhone|General PinePhone hardware info]] in this Pine64 wiki
* Details specific to the Braveheart Edition: [[PinePhone_v1.1_-_Braveheart|PinePhone 1.1 Braveheart hardware details]]
* Details specific to the Community Edition: [[PinePhone_v1.2|PinePhone 1.2 hardware details]]
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here] and the preceding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here]

Other software information
* [https://linux-sunxi.org/Main_Page sunxi community wiki]
* [https://xnux.eu/devices/pine64-pinephone.html megi's feature/driver support matrix]
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)] see demonstration [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube]
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]

Other
* [https://pine64.com/?post_type=product Pine64 shop]
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on Linux distributions and desktop environments on mobile devices]
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing microSD cards]

[[Category:PinePhone]]

User talk:RainSlide

2021-10-07T22:55:16Z

RainSlide: /* Template changes whitespace */ Fixed

== Template changes whitespace ==

Hi RainSlide, could you look into how the template changes introduced the strange new lines before and after the templates? AFAIK that wasn't the case with the old versions. See for example https://wiki.pine64.org/wiki/User:Fxc#Test_2 and https://wiki.pine64.org/wiki/PinePhone_Thermal_Tweaks. Thanks, --[[User:Fxc|Fxc]] ([[User talk:Fxc|talk]]) 12:26, 30 September 2021 (UTC)

I noticed this, but I didn't look into them carefully, and just removed the new lines before and after the templates from the article code, instead of fixing the templates. Thanks for informing about this, now It's fixed. - [[User:RainSlide|RainSlide]] ([[User talk:RainSlide|talk]]) 8 Oct 2021

Template:Note

2021-10-07T22:54:21Z

RainSlide: Fix the new line problem, thanks fxc for point ths out, and https://stackoverflow.com/questions/686898

<noinclude>
{{Template}}

A note box for showing important notes.

== Usage ==

<nowiki>{{Note|note content}}</nowiki>

== Examples ==

<nowiki>{{Note|This is an note.}}</nowiki>

{{Note | This is an note.}}

For a more flexible usage, it doesn't start with "'''Note:'''" by default,
you may add it manually with <code><nowiki>'''Note:'''</nowiki></code>:

<nowiki>{{Note|'''Note:''' This is an note.}}</nowiki>

{{Note | '''Note:''' This is an note.}}

== Technical notes ==

The boxes use <code>display: table</code> to support both adaptive width and floating siblings, all other alternatives can't archive them as perfect as this solution within just one HTML element. However, it has its own flaw, if you put it into another table, its padding will gone. Avoid putting hints, notes and warnings into any tables until solution was found, or we give up and use two elements for just one box.

This template uses class <code>.template-box</code> and <code>.template-note</code>.
In the future, if the [https://www.mediawiki.org/wiki/Extension:TemplateStyles TemplateStyles Extension] is installed on this MediaWiki instance,
one may move the embedded inline styles to Template Style files.

== See also ==

* [https://wiki.archlinux.org/title/Template:Note ArchWiki: Template:Note]: the template on which this one is based on
* [[Template:Hint]]
* [[Template:Warning]]
</noinclude><includeonly><div role="note" class="template-box template-hint" style="
display: table;
min-width: 16em;
min-height: 1.6em;
margin: .5em 0 1em;
padding: .5em 1em;
border: 1px solid #fc3;
color: #705000;
background-color: #fef6e7;
">{{{1|}}}</div></includeonly>

Template:Hint

2021-10-07T22:53:49Z

RainSlide: Fix the new line problem, thanks fxc for point ths out, and https://stackoverflow.com/questions/686898

<noinclude>
{{Template}}

A hint box for showing helpful hints.

== Usage ==

<nowiki>{{Hint|hint content}}</nowiki>

== Example ==

<nowiki>{{Hint|This is an hint.}}</nowiki>

{{Hint | This is an hint.}}

For a more flexible usage, it doesn't start with "'''Hint:'''" by default,
you may add it manually with <code><nowiki>'''Hint:'''</nowiki></code>:

<nowiki>{{Hint|'''Hint:''' This is another hint.}}</nowiki>

{{Hint | '''Hint:''' This is another hint.}}

== Technical notes ==

The boxes use <code>display: table</code> to support both adaptive width and floating siblings, all other alternatives can't archive them as perfect as this solution within just one HTML element. However, it has its own flaw, if you put it into another table, its padding will gone. Avoid putting hints, notes and warnings into any tables until solution was found, or we give up and use two elements for just one box.

This template uses class <code>.template-box</code> and <code>.template-hint</code>.
In the future, if the [https://www.mediawiki.org/wiki/Extension:TemplateStyles TemplateStyles Extension] is installed on this MediaWiki instance,
one may move the embedded inline styles to Template Style files.

== See also ==

* [https://wiki.archlinux.org/title/Template:Tip ArchWiki: Template:Tip]: the template on which this one is based on
* [[Template:Note]]
* [[Template:Warning]]
</noinclude><includeonly><div role="note" class="template-box template-hint" style="
display: table;
min-width: 16em;
min-height: 1.6em;
margin: .5em 0;
padding: .5em 1em;
border: 1px solid #9bcdfd;
color: #003670;
background-color: #d1ecfd;
">{{{1|}}}</div></includeonly>

Template:Warning

2021-10-07T22:47:58Z

RainSlide: Try fix the new line problem

<noinclude>
{{Template}}

A waring box for highlighting dangerous actions and security warnings. It starts with "'''Warning:'''" by default.

== Usage ==

<nowiki>{{Warning|warning content}}</nowiki>

== Example ==

<nowiki>{{Warning|This is a warning.}}</nowiki>

{{Warning|This is a warning.}}

== Technical notes ==

The boxes use <code>display: table</code> to support both adaptive width and floating siblings, all other alternatives can't archive them as perfect as this solution within just one HTML element. However, it has its own flaw, if you put it into another table, its padding will gone. Avoid putting hints, notes and warnings into any tables until solution was found, or we give up and use two elements for just one box.

This template uses class <code>.template-box</code> and <code>.template-warning</code>.
In the future, if the [https://www.mediawiki.org/wiki/Extension:TemplateStyles TemplateStyles Extension] is installed on this MediaWiki instance,
one may move the embedded inline styles to Template Style files.

== See also ==

* [https://wiki.archlinux.org/title/Template:Warning ArchWiki: Template:Warning]: the template on which this one is based on
* [[Template:Hint]]
* [[Template:Note]]
</noinclude><includeonly><div role="note" class="template-box" style="
display: table;
min-width: 16em;
min-height: 1.6em;
margin: .5em 0 1em;
padding: .5em 1em;
border: 1px solid #d33;
color: black;
background-color: #fee7e6;
"><strong>Warning:</strong> {{{1|}}}</div></includeonly>

User talk:RainSlide

2021-10-07T22:37:02Z

RainSlide:

== Template changes whitespace ==

Hi RainSlide, could you look into how the template changes introduced the strange new lines before and after the templates? AFAIK that wasn't the case with the old versions. See for example https://wiki.pine64.org/wiki/User:Fxc#Test_2 and https://wiki.pine64.org/wiki/PinePhone_Thermal_Tweaks. Thanks, --[[User:Fxc|Fxc]] ([[User talk:Fxc|talk]]) 12:26, 30 September 2021 (UTC)

I noticed this, but I didn't look into them carefully, and just removed the new lines before and after the templates from the article code instead of fixing the templates. Thanks for informing about this, will fix them ASAP! - [[User:RainSlide|RainSlide]] ([[User talk:RainSlide|talk]]) 8 Oct 2021

User talk:RainSlide

2021-10-07T22:35:03Z

RainSlide: /* Template changes whitespace */ Reply

== Template changes whitespace ==

Hi RainSlide, could you look into how the template changes introduced the strange new lines before and after the templates? AFAIK that wasn't the case with the old versions. See for example https://wiki.pine64.org/wiki/User:Fxc#Test_2 and https://wiki.pine64.org/wiki/PinePhone_Thermal_Tweaks. Thanks, --[[User:Fxc|Fxc]] ([[User talk:Fxc|talk]]) 12:26, 30 September 2021 (UTC)

I noticed this and just removed the new lines before and after the templates and didn't look into them carefully, thanks for informing about this, will fix them ASAP! - [[User:RainSlide|RainSlide]] ([[User talk:RainSlide|talk]]) 8 Oct 2021

User:RainSlide/CSS Boxes

2021-09-27T15:16:22Z

RainSlide: /* The border-collapse & padding problem */ add a CSS table

This page is mainly for showing why [[Template:Hint]], [[Template:Note]] and [[Template:Warning]] uses <code>display: table</code> to archive compatibility for both adaptive width and floating sibling(s).

If a set of style is not compatible with adaptive width,
it span to its full width even when it don't need to.

If a set of style is not compatible with floating sibling(s),
the element may still work well with some short content in it;
in another word, it may still looks fine when its
''content width'' + ''margin'' + ''padding'' + ''border''
is lower than the "remaining width" lefted by the floating sibling(s).
So we have to use Lorem ipsum (as well as a floating box, for sure) to test it.

Ideally, you may just set the widths to fixed values,
and pretend nothing happens and CSS is awesome.
However, the content container of MediaWiki got adaptive width,
and maybe you are maintaining a MediaWiki [[Template:Template|Template]],
with only inline styles.

<div style="position: fixed; top: 12.5vh; font-size: 25vh; line-height: 1; font-weight: bold; white-space: pre; color: lightblue; opacity: .1; user-select: none; pointer-events: none;">CSS<br>is<br>Awesome</div>

== Table ==

=== <code>display: table</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid;">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width.</div>

<div style="display: table; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

</div>
=== The border-collapse & padding problem ===

{| class="wikitable"
! This is a wikitable
|-
| <div style="display: table; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No padding when it's in a wikitable.</div>
|}

This is beacuse <code>.wikitable</code> has <code>border-collapse: collapse</code> on it, and our box inherits it from <code>.wikitable</code>. <code>border-collapse: collapse</code> Disables padding on the table itself, allowing only padding on the table cells, to collapse the outer table borders.

To fix this padding problem in <code>.wikitable</code>s, one must apply <code>border-collapse: separate</code> to the box.
However, if one day, someone REALLY need to use the box as a CSS table,
the border of its cell will be separated by default, which may affect the visual.

{| class="wikitable"
! This is another wikitable
|-
| <div style="display: table; background-color: #FEE; border-collapse: separate;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">The padding is back!</div>
|}

<div style="display: table; background-color: #FEE; border-collapse: separate;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
<div style="display: table-cell; padding: .25em .5em; border: 1px solid;>But...</div>
<div style="display: table-cell; padding: .25em .5em; border: 1px solid;>Maybe that's not what we want.</div>
</div>

For those who are interested,
to use the box or other elements with <code>display: table</code> as a CSS table and actually do something,
or to work around with this padding problem with an additional div,
see [https://chrisnager.github.io/ungrid/ ungrid].
<small>But, don't use two elements when you can just use one element + one CSS rule to archive the exact same result.</small>

Since I don't think the [[Template:Hint|Hint]], [[Template:Note|Note]] and [[Template:Warning|Warning]] boxes should be put into a <code>.wikitable</code>,
and it seems no one will use them as CSS tables any time sooner,
I'm not favouring either of those two usage, and keep those templates minimal.

=== <code>display: table-cell</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid;">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-cell; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width.</div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table cells are not blocky! Without this sentence, they are in the same row by now.</p>

<div style="display: table-cell; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table cells have no margin.</p>

</div>

=== <code>display: table-caption</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-caption; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No adaptive width.</div>

<div style="display: table-caption; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">It's hiding.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">There can only be one table caption per table, or, per anything.</p>

</div>

=== <code>display: table-row</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-row; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width?</div>

<div style="display: table-row; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for floating siblings?
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table rows have no margin, padding or border.</p>

</div>

=== <code>display: table-<em>others</em></code> ===

Other table display values works just like table rows, (<code>table-row-group</code>, <code>table-header-group</code> and <code>table-footer-group</code>), or won't even display its contents (<code>table-column</code> and <code>table-column-group</code>).

== A new block formatting context ==

See guide [https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Block_formatting_context Block formatting context] on MDN.

=== <code>float: left</code> ===

''Will everything go right with float set to left?''

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="float: left; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width.</div>

<div style="float: left; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">It falls off from its floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

</div>

''No, something falls down.''

== <code>display: inline-block</code> ==

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: inline-block; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width.</div>

<div style="display: inline-block; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">But inline blocks are inline.</div>

<div style="display: inline-block; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">It also falls off from its floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

</div>

== <code>display: flow-root</code> ==

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: flow-root; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No adaptive width.</div>

<div style="display: flow-root; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

</div>

== And… ==

This is the end of part one. Part two will feature <code>contain: content</code>, <code>width: fit-content</code>, <code>width: max-content</code>, <code>box-sizing: border-box; max-width: 100%</code>, <code>display: flex</code>, <code>display: grid</code>, and more, if I ever got time to work on the part two.

User:RainSlide/CSS Boxes

2021-09-27T13:57:11Z

RainSlide: /* display: table */ border-collapse: separate

This page is mainly for showing why [[Template:Hint]], [[Template:Note]] and [[Template:Warning]] uses <code>display: table</code> to archive compatibility for both adaptive width and floating sibling(s).

If a set of style is not compatible with adaptive width,
it span to its full width even when it don't need to.

If a set of style is not compatible with floating sibling(s),
the element may still work well with some short content in it;
in another word, it may still looks fine when its
''content width'' + ''margin'' + ''padding'' + ''border''
is lower than the "remaining width" lefted by the floating sibling(s).
So we have to use Lorem ipsum (as well as a floating box, for sure) to test it.

Ideally, you may just set the widths to fixed values,
and pretend nothing happens and CSS is awesome.
However, the content container of MediaWiki got adaptive width,
and maybe you are maintaining a MediaWiki [[Template:Template|Template]],
with only inline styles.

<div style="position: fixed; top: 12.5vh; font-size: 25vh; line-height: 1; font-weight: bold; white-space: pre; color: lightblue; opacity: .1; user-select: none; pointer-events: none;">CSS<br>is<br>Awesome</div>

== Table ==

=== <code>display: table</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid;">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width.</div>

<div style="display: table; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

</div>
=== The border-collapse & padding problem ===

{| class="wikitable"
! This is a wikitable
|-
| <div style="display: table; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No padding when it's in a wikitable.</div>
|}

This is beacuse <code>.wikitable</code> has <code>border-collapse: collapse</code> on it, and our box inherits it from <code>.wikitable</code>. <code>border-collapse: collapse</code> Disables padding on the table itself, allowing only padding on the table cells, to collapse the outer table borders.

To fix this padding problem in <code>.wikitable</code>s, one must apply <code>border-collapse: separate</code> to the box.
However, if one day, someone REALLY need to use the box as a CSS table,
the border of its cell will be separated by default, which may affect the visual.

{| class="wikitable"
! This is another wikitable
|-
| <div style="display: table; background-color: #FEE; border-collapse: separate;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">The padding is back!</div>
|}

For those who are interested,
to use the box or other elements with <code>display: table</code> as a CSS table and actually do something,
or to work around with this padding problem with an additional div,
see [https://chrisnager.github.io/ungrid/ ungrid].
<small>But, don't use two elements when you can just use one element + one CSS rule to archive the exact same result.</small>

Since I don't think the [[Template:Hint|Hint]], [[Template:Note|Note]] and [[Template:Warning|Warning]] boxes should be put into a <code>.wikitable</code>,
and it seems no one will use them as CSS tables any time sooner,
I'm not favouring either of those two usage, and keep those templates minimal.

=== <code>display: table-cell</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid;">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-cell; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width.</div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table cells are not blocky! Without this sentence, they are in the same row by now.</p>

<div style="display: table-cell; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table cells have no margin.</p>

</div>

=== <code>display: table-caption</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-caption; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No adaptive width.</div>

<div style="display: table-caption; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">It's hiding.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">There can only be one table caption per table, or, per anything.</p>

</div>

=== <code>display: table-row</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-row; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width?</div>

<div style="display: table-row; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for floating siblings?
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table rows have no margin, padding or border.</p>

</div>

=== <code>display: table-<em>others</em></code> ===

Other table display values works just like table rows, (<code>table-row-group</code>, <code>table-header-group</code> and <code>table-footer-group</code>), or won't even display its contents (<code>table-column</code> and <code>table-column-group</code>).

== A new block formatting context ==

See guide [https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Block_formatting_context Block formatting context] on MDN.

=== <code>float: left</code> ===

''Will everything go right with float set to left?''

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="float: left; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width.</div>

<div style="float: left; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">It falls off from its floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

</div>

''No, something falls down.''

== <code>display: inline-block</code> ==

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: inline-block; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width.</div>

<div style="display: inline-block; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">But inline blocks are inline.</div>

<div style="display: inline-block; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">It also falls off from its floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

</div>

== <code>display: flow-root</code> ==

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: flow-root; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No adaptive width.</div>

<div style="display: flow-root; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

</div>

== And… ==

This is the end of part one. Part two will feature <code>contain: content</code>, <code>width: fit-content</code>, <code>width: max-content</code>, <code>box-sizing: border-box; max-width: 100%</code>, <code>display: flex</code>, <code>display: grid</code>, and more, if I ever got time to work on the part two.

User:RainSlide/CSS Boxes

2021-09-27T13:14:14Z

RainSlide: /* display: flow-root */

This page is mainly for showing why [[Template:Hint]], [[Template:Note]] and [[Template:Warning]] uses <code>display: table</code> to archive compatibility for both adaptive width and floating sibling(s).

If a set of style is not compatible with adaptive width,
it span to its full width even when it don't need to.

If a set of style is not compatible with floating sibling(s),
the element may still work well with some short content in it;
in another word, it may still looks fine when its
''content width'' + ''margin'' + ''padding'' + ''border''
is lower than the "remaining width" lefted by the floating sibling(s).
So we have to use Lorem ipsum (as well as a floating box, for sure) to test it.

Ideally, you may just set the widths to fixed values,
and pretend nothing happens and CSS is awesome.
However, the content container of MediaWiki got adaptive width,
and maybe you are maintaining a MediaWiki [[Template:Template|Template]],
with only inline styles.

<div style="position: fixed; top: 12.5vh; font-size: 25vh; line-height: 1; font-weight: bold; white-space: pre; color: lightblue; opacity: .1; user-select: none; pointer-events: none;">CSS<br>is<br>Awesome</div>

== Table ==

=== <code>display: table</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid;">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width.</div>

<div style="display: table; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

</div>

{| class="wikitable"
! This is a wikitable
|-
| <div style="display: table; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No padding when it's in another table, however.</div>
|}

=== <code>display: table-cell</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid;">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-cell; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width.</div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table cells are not blocky! Without this sentence, they are in the same row by now.</p>

<div style="display: table-cell; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table cells have no margin.</p>

</div>

=== <code>display: table-caption</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-caption; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No adaptive width.</div>

<div style="display: table-caption; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">It's hiding.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">There can only be one table caption per table, or, per anything.</p>

</div>

=== <code>display: table-row</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-row; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width?</div>

<div style="display: table-row; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for floating siblings?
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table rows have no margin, padding or border.</p>

</div>

=== <code>display: table-<em>others</em></code> ===

Other table display values works just like table rows, (<code>table-row-group</code>, <code>table-header-group</code> and <code>table-footer-group</code>), or won't even display its contents (<code>table-column</code> and <code>table-column-group</code>).

== A new block formatting context ==

See guide [https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Block_formatting_context Block formatting context] on MDN.

=== <code>float: left</code> ===

''Will everything go right with float set to left?''

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="float: left; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width.</div>

<div style="float: left; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">It falls off from its floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

</div>

''No, something falls down.''

== <code>display: inline-block</code> ==

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: inline-block; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width.</div>

<div style="display: inline-block; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">But inline blocks are inline.</div>

<div style="display: inline-block; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">It also falls off from its floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

</div>

== <code>display: flow-root</code> ==

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: flow-root; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No adaptive width.</div>

<div style="display: flow-root; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

</div>

== And… ==

This is the end of part one. Part two will feature <code>contain: content</code>, <code>width: fit-content</code>, <code>width: max-content</code>, <code>box-sizing: border-box; max-width: 100%</code>, <code>display: flex</code>, <code>display: grid</code>, and more, if I ever got time to work on the part two.

User:RainSlide/CSS Boxes

2021-09-27T05:16:30Z

RainSlide: Add display: table-others

This page is mainly for showing why [[Template:Hint]], [[Template:Note]] and [[Template:Warning]] uses <code>display: table</code> to archive compatibility for both adaptive width and floating sibling(s).

If a set of style is not compatible with adaptive width,
it span to its full width even when it don't need to.

If a set of style is not compatible with floating sibling(s),
the element may still work well with some short content in it;
in another word, it may still looks fine when its
''content width'' + ''margin'' + ''padding'' + ''border''
is lower than the "remaining width" lefted by the floating sibling(s).
So we have to use Lorem ipsum (as well as a floating box, for sure) to test it.

Ideally, you may just set the widths to fixed values,
and pretend nothing happens and CSS is awesome.
However, the content container of MediaWiki got adaptive width,
and maybe you are maintaining a MediaWiki [[Template:Template|Template]],
with only inline styles.

<div style="position: fixed; top: 12.5vh; font-size: 25vh; line-height: 1; font-weight: bold; white-space: pre; color: lightblue; opacity: .1; user-select: none; pointer-events: none;">CSS<br>is<br>Awesome</div>

== Table ==

=== <code>display: table</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid;">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width.</div>

<div style="display: table; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

</div>

{| class="wikitable"
! This is a wikitable
|-
| <div style="display: table; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No padding when it's in another table, however.</div>
|}

=== <code>display: table-cell</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid;">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-cell; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width.</div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table cells are not blocky! Without this sentence, they are in the same row by now.</p>

<div style="display: table-cell; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table cells have no margin.</p>

</div>

=== <code>display: table-caption</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-caption; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No adaptive width.</div>

<div style="display: table-caption; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">It's hiding.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">There can only be one table caption per table, or, per anything.</p>

</div>

=== <code>display: table-row</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-row; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width?</div>

<div style="display: table-row; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for floating siblings?
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table rows have no margin, padding or border.</p>

</div>

=== <code>display: table-<em>others</em></code> ===

Other table display values works just like table rows, (<code>table-row-group</code>, <code>table-header-group</code> and <code>table-footer-group</code>), or won't even display its contents (<code>table-column</code> and <code>table-column-group</code>).

== A new block formatting context ==

See guide [https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Block_formatting_context Block formatting context] on MDN.

=== <code>float: left</code> ===

''Will everything go right with float set to left?''

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="float: left; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width.</div>

<div style="float: left; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">It falls off from its floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

</div>

''No, something falls down.''

== <code>display: inline-block</code> ==

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: inline-block; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width.</div>

<div style="display: inline-block; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">But inline blocks are inline.</div>

<div style="display: inline-block; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">It also falls off from its floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

</div>

== <code>display: flow-root</code> ==

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: flow-root; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No adaptive width.</div>

<div style="display: flow-root; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

</div>

This is the end of part one. Part two will feature <code>contain: content</code>, <code>width: max-content</code>, <code>box-sizing: border-box; max-width: 100%</code>, <code>display: flex</code>, <code>display: grid</code>, and more, if I ever got time to work on the part two.

User:RainSlide/CSS Boxes

2021-09-27T05:11:52Z

RainSlide: Adjust styles

This page is mainly for showing why [[Template:Hint]], [[Template:Note]] and [[Template:Warning]] uses <code>display: table</code> to archive compatibility for both adaptive width and floating sibling(s).

If a set of style is not compatible with adaptive width,
it span to its full width even when it don't need to.

If a set of style is not compatible with floating sibling(s),
the element may still work well with some short content in it;
in another word, it may still looks fine when its
''content width'' + ''margin'' + ''padding'' + ''border''
is lower than the "remaining width" lefted by the floating sibling(s).
So we have to use Lorem ipsum (as well as a floating box, for sure) to test it.

Ideally, you may just set the widths to fixed values,
and pretend nothing happens and CSS is awesome.
However, the content container of MediaWiki got adaptive width,
and maybe you are maintaining a MediaWiki [[Template:Template|Template]],
with only inline styles.

<div style="position: fixed; top: 12.5vh; font-size: 25vh; line-height: 1; font-weight: bold; white-space: pre; color: lightblue; opacity: .1; user-select: none; pointer-events: none;">CSS<br>is<br>Awesome</div>

== Table ==

=== <code>display: table</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid;">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width.</div>

<div style="display: table; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

</div>

{| class="wikitable"
! This is a wikitable
|-
| <div style="display: table; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No padding when it's in another table, however.</div>
|}

=== <code>display: table-cell</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid;">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-cell; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width.</div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table cells are not blocky! Without this sentence, they are in the same row by now.</p>

<div style="display: table-cell; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table cells have no margin.</p>

</div>

=== <code>display: table-caption</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-caption; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No adaptive width.</div>

<div style="display: table-caption; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">It's hiding.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">There can only be one table caption per table, or, per anything.</p>

</div>

=== <code>display: table-row</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-row; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width?</div>

<div style="display: table-row; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for floating siblings?
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table rows have no margin, padding or border.</p>

</div>

Other table display values works like table rows, or won't even display its contents.

== A new block formatting context ==

See guide [https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Block_formatting_context Block formatting context] on MDN.

=== <code>float: left</code> ===

''Will everything go right with float set to left?''

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="float: left; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width.</div>

<div style="float: left; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">It falls off from its floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

</div>

''No, something falls down.''

== <code>display: inline-block</code> ==

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: inline-block; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for adaptive width.</div>

<div style="display: inline-block; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">But inline blocks are inline.</div>

<div style="display: inline-block; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">It also falls off from its floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

</div>

== <code>display: flow-root</code> ==

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: flow-root; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No adaptive width.</div>

<div style="display: flow-root; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">No problem for floating siblings.
<span style="display: block; opacity: .5; text-align: justify;">Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</span></div>

</div>

This is the end of part one. Part two will feature <code>contain: content</code>, <code>width: max-content</code>, <code>box-sizing: border-box; max-width: 100%</code>, <code>display: flex</code>, <code>display: grid</code>, and more, if I ever got time to work on the part two.

User:RainSlide/CSS Boxes

2021-09-27T04:28:38Z

RainSlide: /* float: left */ modify desc

This page is mainly for showing why [[Template:Hint]], [[Template:Note]] and [[Template:Warning]] uses <code>display: table</code> to archive compatibility for both adaptive width and floating sibling(s).

If a set of style is not compatible with adaptive width,
it span to its full width even when it don't need to.

If a set of style is not compatible with floating sibling(s),
the element may still work well with some short content in it;
in another word, it may still looks fine when its
''content width'' + ''margin'' + ''padding'' + ''border''
is lower than the "remaining width" lefted by the floating sibling(s).
So we have to use Lorem ipsum (as well as a floating box, for sure) to test it.

Ideally, you may just set the widths to fixed values,
and pretend nothing happens and CSS is awesome.
However, the content container of MediaWiki got adaptive width,
and maybe you are maintaining a MediaWiki [[Template:Template|Template]],
with only inline styles.

<div style="position: fixed; top: 12.5vh; font-size: 25vh; line-height: 1; font-weight: bold; white-space: pre; color: lightblue; opacity: .1; user-select: none; pointer-events: none;">CSS<br>is<br>Awesome</div>

== Table ==

=== <code>display: table</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid;">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for adaptive width.</div>

<div style="display: table; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for floating siblings.<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

</div>

{| class="wikitable"
! This is a wikitable
|-
| <div style="display: table; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No padding when it's in another table, however.</div>
|}

=== <code>display: table-cell</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid;">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-cell; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for adaptive width.</div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table cells are not blocky! Without this sentence, they are in the same row by now.</p>

<div style="display: table-cell; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for floating siblings.<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table cells have no margin.</p>

</div>

=== <code>display: table-caption</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-caption; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No adaptive width.</div>

<div style="display: table-caption; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
It's hiding.<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">There can only be one table caption per table, or, per anything.</p>

</div>

=== <code>display: table-row</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-row; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for adaptive width?</div>

<div style="display: table-row; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for floating siblings?<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table rows have no margin, padding or border.</p>

</div>

Other table display values works like table rows, or won't even display its contents.

== A new block formatting context ==

See guide [https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Block_formatting_context Block formatting context] on MDN.

=== <code>float: left</code> ===

''Will everything go right with float set to left?''

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="float: left; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for adaptive width.</div>

<div style="float: left; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
It falls off from its floating siblings.<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

</div>

''No, something falls down.''

== <code>display: inline-block</code> ==

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: inline-block; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for adaptive width.</div>

<div style="display: inline-block; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
But inline blocks are inline.</div>

<div style="display: inline-block; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
It also falls off from its floating siblings.<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

</div>

== <code>display: flow-root</code> ==

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: flow-root; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No adaptive width.</div>

<div style="display: flow-root; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for floating siblings.<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

</div>

This is the end of part one. Part two will feature <code>contain: content</code>, <code>width: max-content</code>, <code>box-sizing: border-box; max-width: 100%</code>, <code>display: flex</code>, <code>display: grid</code>, and more, if I ever got time to work on the part two.

PinePhone Software Releases

2021-09-22T11:49:28Z

RainSlide: Multiple fixes

This page contains a list of all available OS releases for the [[PinePhone]], as well as links to other resources.

See [[PinePhone Installation Instructions]] on how to install the operating systems.<br>
However, if your phone came preloaded with software, Please see [[PinePhone Updating Instructions]].{{Hint| '''Note:''' Some releases may not have a good setup for the backlight at low brightness.
If configured too low, the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.}}= Software Releases =

This is a list of OSes that specifically support the PinePhone.
Since PinePhone support is included in Mainline Linux, in principle, any ARM Linux OS can be used if possible required patches are included.

== Arch Linux ARM ==
[[File:Archlinux-logo.png|right|100px]]

(Unofficial) Arch Linux ARM with choice of Phosh UI, Plasma Mobile, or barebones.
Currently being maintained by the [https://danctnix.org/ DanctNIX] community (GitHub: [https://github.com/DanctNIX/danctnix danctnix], [https://github.com/dreemurrs-embedded dreemurrs-embedded]).

* GitHub: [https://github.com/dreemurrs-embedded/Pine64-Arch dreemurrs-embedded/Pine64-Arch]

'''Download location'''

Get the latest image here: https://github.com/dreemurrs-embedded/Pine64-Arch/releases

'''username/password'''

{| class="wikitable"
! Default user
| <code>alarm/123456</code>
|-
! root
| <code>root/root</code>
|}

'''What works, what does not work'''

Most of the things now works, there are some minor issues with [[Crust]].

'''How to contribute and report defects'''

You may find the Discord, Matrix and Telegram of DanctNIX community at [https://github.com/DanctNIX/danctnix/blob/master/README.md#channel-list the Channel list section of DanctNIX/README.md].

Feel free to send us [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls pull requests] and report [https://github.com/dreemurrs-embedded/Pine64-Arch/issues issues] on [https://github.com/dreemurrs-embedded/Pine64-Arch GitHub].

== ExpidusOS ==

A fork of [https://voidlinux.org Void Linux] with a custom fork of XFCE called [https://github.com/ExpidusOS/genesis Gensis] as the default desktop environment, developed by [https://midstall.com/ Midstall Software].

* [https://expidusos.com ExpidusOS official website]
* [https://wiki.expidusos.com/index.php/Main_Page ExpidusOS Wiki]
* [https://discord.gg/GVfBF2w Midstall Software Discord server]
* GitHub: [https://github.com/ExpidusOS ExpidusOS]

'''Download location'''

Check the [https://expidusos.com/download download page] for that latest version, or the [https://build.expidusos.com/ image file list] for all versions, look for the file name that starts with "pinephone".

'''username/password'''

expidus/expidus

'''What works, what does not work'''

The ExpidusOS Wiki has a page detailing [https://wiki.expidusos.com/index.php/Device:PinePhone supported features].

'''How to contribute and report defects'''

Join the [https://discord.gg/GVfBF2w Discord server] or corresponding repo at GitHub ([https://github.com/orgs/ExpidusOS/repositories repo list]).

== Fedora ==
[[File:Fedora-logo.png|right|100px]]

An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and [https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/ some additional packages] to tie it all together.
It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.

* Forum discussion: [https://forum.pine64.org/showthread.php?tid=9347 Fedora + Phosh for PinePhone]
* GitHub: [https://github.com/nikhiljha/pp-fedora-sdsetup nikhiljha/pp-fedora-sdsetup]

'''Download location'''

* [https://github.com/nikhiljha/pp-fedora-sdsetup/releases Flashable images]
* [https://github.com/nikhiljha/pp-fedora-sdsetup Build scripts]
* [https://copr.fedorainfracloud.org/coprs/njha/mobile/ Packages (Fedora COPR)]

There is also an FTP server with a full Fedora 34 workstation build with phosh: ftp://pine.warpspeed.dk/nightly/pinephone/ (Mount this with something like Nautilus)

'''username/password'''

pine/123456

'''What works, what does not work'''

WiFi, Bluetooth, SMS, Data, Calls all work!

There are still a few bugs though, and [https://xnux.eu/devices/pine64-pinephone.html#toc-feature-driver-support-matrix some features don't have driver support yet] on any PinePhone distribution.

'''How to contribute and report defects'''

Please send your bug reports to [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker].
Be sure to include logs if applicable!
Send us pull requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/pulls Github].

== Gentoo ==
[[File:GentooLogo.png|right|100px]]{{hint|Please consider cross-compiling the software on the computer.
Long compilation times and heat production can lead to a reduced lifespan of the phone.}}There are unofficial Gentoo overlays with ebuilds for the PinePhone.
There are no images - you'll be building it yourself, picking which kernel, bootloader and desktop environment you want to use.
You will be using the arm64 version of Gentoo.

'''Documentation'''

* https://stealthgun.tweakblogs.net/blog/19336/gentoo-on-a-pinephone
* https://wiki.gentoo.org/wiki/User:Dr41nU/PinePhone
* https://wiki.gentoo.org/wiki/PinePhone (incomplete)

'''Overlay locations'''

* https://gitlab.com/bingch/gentoo-overlay
* https://github.com/stealthgun/gjdwebserver-overlay

== GloDroid ==

{{Hint|There can be large intervals between release update, so available images may be outdated and do not reflect the state of the current developments.}}A fully open source port of Android to the PinePhone.

* GitHub: [https://github.com/GloDroid GloDroid]

'''Download location'''

https://github.com/GloDroid/glodroid_manifest/releases (last release at 2021-05-20)

'''What works, what does not work'''

Works: WiFi, screen dimming, touchscreen and charging work.
Don't work: Bluetooth, Telephony, GPS, Sound

== LuneOS ==
[[File:WebOS-Ports-logo.png|right|100px]]

LuneOS is a open source mobile operating system based on [https://www.webosose.org/ webOS Open Source Edition]([https://github.com/webosose GitHub], previously known as [https://github.com/openwebos Open webOS]) by LG, comes with [https://webos-ports.org/wiki/Luna_Next Luna Next] UI, currently developed by the WebOS Ports community.

* [https://www.webos-ports.org/wiki/Main_Page WebOS Ports Wiki]
* [https://webos-ports.org/wiki/Pinephone_Info WebOS-Ports Wiki's Pinephone page]
* GitHub: [https://github.com/webOS-ports WebOS Ports]

'''Download location'''

* [http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]

It is recommended to use ''bmaptool'', which is faster than dd, and can decompress archived image files on-the-fly.

Syntax is:

bmaptool copy [from] [to]

For example:

bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-140.rootfs.wic.gz /dev/mmcblk0

.wic file can be treated as .img file when flashing. You may rename .wic file to .img when using GUI tools that require file extension to be .img.

== Maemo Leste ==
[[File:Maemoleste-logo.png|right|100px]]

[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices,
originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it.
The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices.

The new version Maemo 8 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel.
The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK].
The current version is Devuan Beowulf (Debian Buster) and has simultaneous support for both Devuan and Debian.

In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository].
To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's build]).
Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.

* [https://maemo-leste.github.io/ Maemo Leste website]
* [https://leste.maemo.org/Main_Page Maemo Leste Wiki]
** [https://leste.maemo.org/PinePhone PinePhone wiki page]
** [https://leste.maemo.org/Leste_FAQ Maemo Leste FAQ]
* GitHub: [https://github.com/maemo-leste maemo-leste]
* Twitter: [https://twitter.com/maemoleste @maemoleste]

'''Download location'''

[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds]. There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].

'''username/password'''

root/toor

You may use <code>sudo</code> directly.

'''What works, what does not work'''

For current status and workarounds, please read their [https://leste.maemo.org/PinePhone PinePhone wiki page].

'''How to contribute and report defects'''

Most discussion occurs at [ircs://irc.libera.chat:6697/#maemo-leste <code>#maemo-leste</code> on <code>irc.libera.chat</code>].
The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback.

All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki.

Submit [https://github.com/maemo-leste/bugtracker/issues bug reports] on github.
To track known issues, you may use these search terms:
[https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone],
[https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64].

Learn about
[https://leste.maemo.org/Development development],
[https://leste.maemo.org/Development/Porting_Packages porting packages],
[https://leste.maemo.org/Development/Building_Packages building packages],
[https://leste.maemo.org/Development/Tasks todo list],
and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian].
Some tasks have funding available.

== Manjaro ARM ==
[[File:Manjaro-logo.svg|right|100px]]

Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.

'''Download location'''

* Phosh: [https://github.com/manjaro-pinephone/phosh Stable] / [https://github.com/manjaro-pinephone/phosh-dev Dev]
* Plasma Mobile: [https://github.com/manjaro-pinephone/plasma-mobile Stable] / [https://github.com/manjaro-pinephone/plasma-mobile-dev Dev]
* Lomiri: [https://github.com/manjaro-pinephone/lomiri-dev Dev] (No longer maintained)

'''username/password'''

{| class="wikitable"
! Default user
| <code>manjaro/123456</code>
|-
! root
| <code>root/root</code>
|}

'''What works, what does not work'''{{Hint| '''Note:''' At the first boot, the Phosh image will be loaded at a TTY login prompt for multiple minutes.}}See Manjaro's release announcements on their forum.
Recent ones:
[https://forum.manjaro.org/t/manjaro-arm-beta12-with-phosh-pinephone/73099 Phosh],
[https://forum.manjaro.org/t/manjaro-arm-beta5-with-plasma-mobile-pinephone/69318 Plasma] and
[https://forum.manjaro.org/t/manjaro-arm-alpha3-with-lomiri-pinephone/49923 Lomiri].

'''How to contribute and report defects'''

See the end of the [https://forum.manjaro.org/t/manjaro-arm-beta7-with-phosh-pinephone/58901 announcement].

== Mobian ==
[[File:Debian-logo.png|right|100px]]

An unofficial [https://www.debian.org Debian] build for ARM64 running with Phosh (developed by Purism, uses Wayland instead of Xorg).
The base system is pure Debian, with only the GUI applications and a few others (ModemManager, WiFi chip firmware) being built from modified sources (as well as the kernel and u-boot).
Current version is Debian Bookworm.

'''Download location'''

[https://images.mobian-project.org/pinephone/nightly/ Nightly] /
[https://images.mobian-project.org/pinephone/installer/ Installer] /
[https://images.mobian-project.org/pinephone/ Stable]

Extract the image before installing:

$ gzip -d Downloads/mobian-pinephone-*.img.gz

See the [https://wiki.mobian-project.org/doku.php?id=install project page] for specific installation instructions.

'''username/password'''

mobian/1234

'''What works, what does not work'''

See [https://gitlab.com/mobian1/mobian-recipes/-/blob/master/README.md the project's README file] or [https://wiki.mobian-project.org/doku.php?id=pinephone the wiki] for most up to date status.

Check [https://gitlab.com/groups/mobian1/-/issues bug tracker] for known issues. Questions? Ask on our [https://forum.pine64.org/showthread.php?tid=9016 thread].

'''How to contribute and report defects'''

It is recommended that you log your bug reports in [https://gitlab.com/mobian1/issues the project's issue tracker].
As a general rule, issues with third-party apps (even the default ones) should be reported upstream.
A Mobian issue would be related to getting the hardware to work on the PinePhone,
but if unsure where the issue should be reported just open a ticket or ask.
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/mobian1 Gitlab].

'''Notes'''

See [https://wiki.mobian-project.org/doku.php?id=start the wiki] for additional information regarding screen resolution, USB networking, WiFi hotspot, Chatty and the repository.

== Multi-distro demo image ==

{{Warning | This is an demo image for testing different OSes before installing a regular image. It is highly discouraged attempting to use the image productively. The kernel is shared across the different OSes and is not being updated.}}

This image allow users to try many of the above Linux distributions easily, without having to figure out how to flash them individually and juggle with many microSD cards. Also called megi's 15-in-1 multi boot image.

* Main page: https://xnux.eu/p-boot-demo/
* Git repo: https://megous.com/git/pinephone-multi-boot/
* Forum discussion: [https://forum.pine64.org/showthread.php?tid=11347 UPDATED (June 2021): 17-distro multi-boot image for Pinephone (incl. 3GiB variant)]

'''Update 2021-06-02, using megi's kernel 5.13-rc4'''

DD image to SD card and boot. This image is for 16GiB or larger SD cards, also works if flashed to eMMC.

This is also a good build for charging depleted battery. Just boot up this build with power supply connected, keep the PinePhone charging for 3 hours at power down stage.

For more info on this build, please visit its entry the "News" section of its [https://xnux.eu/p-boot-demo/ web page].

* [http://dl.xnux.eu/p-boot-multi-2021-06-02.torrent Download torrent file from author's website]
* [http://dl.xnux.eu/p-boot-multi-2021-06-02/ Download img.zst from author's website] (speed limited to 512KiB/s)
* [http://mirror.uxes.cz/dl.xnux.eu/ Download torrent and img.zst from discord user uxes' mirror]
** '''File name:''' multi.img.zst
** '''SHA-256:''' <span style="word-break: break-all">9b099cdfece3ba862348ca32af6c51a41a1d161b1d897f9928ae8be3c824a0b6</span>
** '''File Size:''' 6.57GiB

* [https://files.pine64.org/os/PinePhone/Multi/p-boot-multi-2021-06-02.img.gz Direct download img.gz from pine64.org] (re-zipped from zstd to gzip)
** '''File name:''' p-boot-multi-2021-06-02.img.gz
** '''MD5:''' 2abdaafb01dd7519f678b5a7c6538493
** '''File Size:''' 6.8GB

Due to its size, download though torrent is suggested by the author on its main page.{{hint | '''Note about .zst archive file:'''

On Linux, you may install or compile <code>zstd</code>, and write the image to SD card by using <code>zstdcat</code> and <code>dd</code>. See the "Installation" section of its [https://xnux.eu/p-boot-demo/ web page] for command examples.

On Windows, you may use [https://github.com/mcmilk/7-Zip-zstd 7-zip-zstd], it provides different installation method in the README.md.Install and extract the .img file from the zst archive, and flash with tools like [https://sourceforge.net/projects/win32diskimager/ Win32 Disk Imager].}}Also see [[PinePhone Installation Instructions]].

'''username/password'''

All passwords, including root passwords, are <code>1111</code>.
sxmo username is <code>user</code>.

== Nemo Mobile ==
[[File:nemo_mobile.png|right|100px]]

Nemo Mobile is the open source build of Sailfish OS with a open source UI called [http://nemomobile.net/glacier-home/ Glacier] ([https://wiki.merproject.org/wiki/Nemo/Glacier Mer Wiki]), [http://nemomobile.net/pages/Hello_manjaro/ based on Manjaro].

* Website: [https://nemomobile.net/ Nemo Mobile UX team]
* [https://wiki.merproject.org/wiki/Nemo Mer Wiki page]

'''Download location'''

See the [https://nemomobile.net/installation/ installation page] on their website for the newest release and installation guides.

'''What works, what does not work'''

Development is now moving very fast after rebasing. For the current devel image, Wifi and Bluetooth works.

'''How to contribute and report defects'''

For the Nemo Mobile UX itself:
* GitHub issues: https://github.com/nemomobile-ux/main/issues

For hardware:
* GitHub issues: https://github.com/neochapay/nemo-device-dont_be_evil/issues

== NixOS ==
[[File:nixos.png|right|100px]]

NixOS support is handled through the Mobile NixOS project.

* Project home page: [https://mobile.nixos.org/ Mobile NixOS]
* PinePhone device page: [https://mobile.nixos.org/devices/pine64-pinephone.html Pine64 PinePhone — Mobile NixOS]
* GitHub: [https://github.com/NixOS/mobile-nixos NixOS/mobile-nixos]

There is no pre-built complete image.
For now users, are expected to follow the instructions in the [https://mobile.nixos.org/getting-started.html Getting Started page],
and [https://mobile.nixos.org/devices/pine64-pinephone.html Project's device page].

'''What works, what does not work'''

Currently, it boots, it's just as compatible as the Android-based devices are with Mobile NixOS.
It even supports a bit more since it can use WiFi.

Support for all of the hardware will be coming, this project is a breadth-first work, where the work spans multiple devices in parallel.

'''How to contribute and report defects'''

On [https://github.com/NixOS/mobile-nixos/issues the project's repository].
Please specify that you are using a PinePhone when reporting issues.
Details about contributions and donations are on the [https://nixos.org/nixos/community.html NixOS website].

== OpenMandriva Lx ==
[[File:Oma-logo-22042013_300pp.png|right|100px]]{{Hint| '''Note:''' This image is solely for testing purposes.}}OpenMandriva Lx with Plasma Mobile as UI.

'''Download location'''

The official image can be found [https://sourceforge.net/projects/openmandriva/files/release/4.2/RC/Pinephone/ at sourceforge.net].
See [https://www.openmandriva.org/en/news/article/openmandriva-lx-4-3-rc-available-for-testing here] for the offical announcement.

'''What works, what does not work'''

From the [https://www.openmandriva.org/en/news/article/openmandriva-lx-4-3-rc-available-for-testing 4.3 announcement],
in future updates (4.3 and later), "Phone calls are working, and we have rewritten the camera app to be far more useful".

== openSUSE ==
[[File:SLEM-OS-logo.png|right|100px]]

Our images use the same [https://en.opensuse.org/Portal:Tumbleweed openSUSE Tumbleweed] base as our desktop images,
except what needs to be changed for the PinePhone.
The images include <i>zypper</i> (RPM) as the default package manager,
and have access to virtually the same (open source) software as our desktop repositories,
thanks to the [https://en.opensuse.org/Portal:Factory Factory] ports.
Using [https://en.opensuse.org/SDB:DNF dnf] is possible, if preferred.

'''Download links'''

* [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz Phosh] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz.sha256 SHA-256] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz.sha256.asc SHA-256 Signature]
* [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz Plasma Mobile] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz.sha256 SHA-256] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz.sha256.asc SHA-256 Signature]

To verify the images you need to import [https://build.opensuse.org/projects/devel:ARM:Factory:Contrib:PinePhone/public_key our GPG key].
Keep on mind that the first boot may stay on black screen for about a minute - consequent boots should be faster.

You can find install instructions at [https://en.opensuse.org/HCL:PinePhone#Installing_openSUSE_in_a_Pinephone this section] in the openSUSE Wiki.

'''Username/Password'''

The login credentials are pine/1234 and root/linux.
Change (or disable) the root password once you are set up.

'''What works and what does not work'''

You can find all information about the releases of the project [https://gitlab.com/slem.os/slem.os/-/blob/master/CHANGELOG.md here].
Detailed information, tips and troubleshooting suggestions are also provided at [https://en.opensuse.org/HCL:PinePhone the openSUSE Wiki].
You will also find information in our wiki on how to report issues (Contributing section).

== postmarketOS ==
[[File:PostmarketOS-logo.png|right|100px]]

postmarketOS extends [https://www.alpinelinux.org/ Alpine Linux] to run on smartphones and other mobile devices.
It offers various user interfaces (Phosh, Plasma Mobile, Sxmo, Plasma Desktop, Gnome 3, Kodi, XFCE4, ...).

As of writing, official images are provided with Phosh, Plasma Mobile and Sxmo.
The official images come in two flavors, either as a test image to try out postmarketOS, or with the installer.

When using the installer images (recommended), it is possible to:
* encrypt the installation
* install from the SD card to eMMC

Power users may also create their own image with the distribution's install and development tool <code>pmbootstrap</code>.

Please read the detailed [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation installation instructions] in the wiki.

'''Download location'''

* [https://postmarketos.org/download/ Download page]
* [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation Flashing instructions]

'''Username/password'''

* Test images: user/147147
* When using the installer images or building an image with pmbootstrap, you set your own username and password.
** The Phosh and Plasma Mobile lock screens only support numeric keyboard, so you should '''only use numbers''' in your password.

'''What works, what does not work'''

See the [https://gitlab.com/postmarketOS/pmaports/-/issues?label_name%5B%5D=device-pine64-pinephone issue tracker].

'''How to contribute and report defects'''

[https://gitlab.com/postmarketOS/pmaports/-/issues?label_name%5B%5D=device-pine64-pinephone postmarketOS issue tracker] for PinePhone support.
See [https://wiki.postmarketos.org/wiki/Contributing postmarketOS wiki] for options to contribute.

== PureOS ==
[[File:Pureos.png|right|100px]]

{{Warning|This project is no longer under development and has been abandoned. Use [https://wiki.pine64.org/wiki/PinePhone_Software_Releases#Mobian Mobian] instead}}{{Hint|There is no prebuilt image, you'll need a Linux environment and build the image yourself.}}[https://www.pureos.net/ PureOS] is a user friendly, secure and freedom respecting GNU/Linux distribution based on Debian and GNOME developed by the Purism community.

* [https://tracker.pureos.net/w/ PureOS Wiki], no PinePhone page there
* Mobile-optimized apps list from the [https://tracker.pureos.net/w/pureos/mobile_optimized_apps/ Software Center in PureOS] and [https://tracker.pureos.net/w/pureos/3rd-party_mobile_optimized_apps/ 3rd party repos]
* [https://github.com/rufferson/pureos-pinephone current PinePhone PureOS repo], A script to convert Librem5 PureOS to PinePhone Pure-OS

'''Download location'''

Use [https://raw.githubusercontent.com/rufferson/pureos-pinephone/master/build_image.sh the convert script] to download and build the image from u-boot, PinePhone linux kernel and Librem5 PureOS.

Also see:
* [https://forums.puri.sm/t/successful-installation-of-pureos-on-pinephone/8741/12 Successful installation of PureOS on PinePhone - PureOS - Purism community]
* The PureOS section of [https://www.ruff.mobi/go/mobi/pine.html PinePhone page] on ruff.mobi
* An [https://gitlab.com/a-wai/debos-pinephone archived repo] for PureOS on PinePhone
* A [https://mozzwald.com/pp/ file list] with [https://mozzwald.com/pp/pureos-pinephone-build-instructions.txt pureos pinephone build instructions] on mozzwald.com

== Sailfish OS ==
[[File:Sailfish_logo.png|right|100px]]

[https://sailfishos.org/ Sailfish OS] is a Linux-based operating system based on open source projects such as [https://wiki.merproject.org/wiki/Main_Page Mer], and a closed source UI based on [https://sailfishos.org/wiki/Lipstick Lipstick].

* [https://wiki.merproject.org/wiki/Adaptations/PinePhone64 PinePhone Wiki Page] on Mer Wiki, for both Nemo Mobile and Sailfish OS.
* [https://gitlab.com/pinephone-sailfish-os/linux-kernel/ Linux kernel config repo]
* [https://gitlab.com/sailfishos-porters-ci/dont_be_evil-ci/ Sailfish OS repo]

'''Download location'''

'''Flashing script'''

The Sailfish OS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].

The script downloads the image and bootloader from the CI, extracts everything and burns it onto the SD card.
Note: The script will format and erase the SD card!

Instructions:
# Download the flashing script
# Insert a microSD card in your device
# Make the script executable: <code>chmod +x flash-it.sh</code>
# Verify that you have the <code>bsdtar</code> package installed
# Execute it: <code>./flash-it.sh</code>
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).

* When asked where to flash, type 'raw' and it will build the image on your computer. Otherwise define the path /dev/.... to flash to card or internal emmc.

'''username/password'''

Set PIN on initialization.

* Sometimes the first run stalls before the tutorial. Reboot and it will start from setting the security pin.
* The homescreen may be locked unless you boot with a sim card inserted. An old expired sim will do. '''If you do not have a SIM card on hands, do NOT set a security code on first boot.'''
* When a screen with a loading circle is displayed, just left/right swipe it away.
* If you're not familiar with Sailfish OS, pay attention to the tutorial - the interface works great, but is not immediately obvious. If you are familiar with it, you can skip the tutorial by touching all 4 corners starting top left.

'''What works, what does not work'''

See the [https://wiki.merproject.org/wiki/Adaptations/PinePhone64#Hardware_Support Hardware Support section] on the Mer Wiki's PinePhone Page.

There is a limited selection of apps available from the Jolla store, the vast majority are hosted on openrepos.net. If the Storeman app for openrepos is not preinstalled, download the RPM and click to install.

'''How to contribute and report defects'''

See the [https://wiki.merproject.org/wiki/Adaptations/PinePhone64#Installation Installation section] on the Mer Wiki's PinePhone Page for compile, build and development.

Git repo links are at the top of this OS section. other repos that may be helpful:

* [https://github.com/sailfish-on-dontbeevil GitHub project page]
* [https://github.com/sailfish-on-dontbeevil/flash-it the repo of the flash-it.sh flashing script]
* [https://build.merproject.org/project/show/nemo:devel:hw:pine:dontbeevil Mer Open Build Service page] ([https://forum.sailfishos.org/t/changes-needed-to-merge-the-project-names-to-sailfish-os/1672 Mer is being assimilated into Sailfish OS] and [https://forum.sailfishos.org/t/obs-shut-down-and-next-steps/1814 OBS is shutting down], also see [https://specs.openstack.org/openstack/fuel-specs/specs/7.0/replace-obs.html OpenStack is replacing OBS with another build system based on Jenkins], if it's related, even OBS come back under Sailfish OS, it will be different.)

See the [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues Sailfish OS wiki] for links to their forum, as well as info required when reporting an issue. See the [https://sailfishos.org/wiki/SailfishOS Sailfish OS wiki main page] for options to contribute to Sailfish OS.

'''Notes'''

OTA is supported: <code>zypper refresh && zypper update</code> as root (<code>devel-su</code> to get root access). Things that need reflash are bootloader specific at the moment. If improvements like [[Crust]] or changes of partition layout are added, then you need to reflash.

== SkiffOS ==
[[File:SkiffOS-Icon-1.png|right|100px]]

Minimal in-memory cross-compiled OS optimized for hosting multiple in parallel Docker containers.

Provides the reliability of firmware with the ease-of-use of package managers.

Upgrade over-the-air via a simple rsync script, or copying 3 files.

Uses the [http://buildroot.org Buildroot] cross-compilation tool for support for all Pine64 boards.

Use configuration packages to configure distro:

{| class="wikitable"
! Package !! Distro
|-
| core/pinephone_neon || KDE Neon via Ubuntu repositories
|-
| core/pinephone_nixos || Nixos Mobile
|-
| core/pinephone_gentoo || Gentoo with Link-time Optimization & KDE Mobile or Phosh
|-
| core/pinephone_ubports || Ubuntu Ports for PinePhone
|-
| core/pinephone_manjaro_kde || Manjaro for PinePhone: KDE variant
|-
| core/pinephone_manjaro_phosh || Manjaro for PinePhone: Phosh variant
|-
| core/pinephone_manjaro_lomiri || Manjaro for PinePhone: Lomiri variant
|}

The boot-up OS is upgraded independently from the containers.

'''Download location'''

The repository and instructions can be found [https://github.com/skiffos/SkiffOS/tree/master/configs/pine64/phone here].

== Sxmo ==

A collection of Suckless programs to create a mobile UI. Based on postmarketOS.

'''Download location'''

Sxmo images can be found [https://images.postmarketos.org/bpo/ here] (in the ''/pine64-pinephone/sxmo/'' sections respectively).

'''username/password'''

user/147147

'''How to contribute and report defects'''

Contributing information is listed [https://git.sr.ht/~mil/sxmo-docs/tree/master/CONTRIBUTING.md here].

== Ubuntu Touch ==
[[File:Ubports-logo.png|right|100px]]

A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.

Ubuntu touch is a mobile version of Ubuntu developed by the UBports community.
Installation instructions can be found on
[https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone the UBports PinePhone project].
There is also a [https://github.com/goddard/pinephone/ script] to download the latest image and flash to your PinePhone.
In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://devices.ubuntu-touch.io/installer UBports installer] GUI tool.

'''Download location'''

[https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone UBports PinePhone project]

'''username/password'''

Set up during boot

'''What works, what does not work'''

Scroll down to the bottom of [https://gitlab.com/ubports/community-ports/pinephone this page].

'''How to contribute and report defects'''

See [https://gitlab.com/ubports/community-ports/pinephone UBports gitlab page].
See [https://ubports.com/foundation/sponsors UBports website] for how to donate.

= Tools =

There are software tools, that can be booted on the PinePhone.

== JumpDrive ==

JumpDrive can be used to flash the eMMC (and the microSD card), see [[PinePhone Installation Instructions#Using JumpDrive]].

See https://github.com/dreemurrs-embedded/Jumpdrive/releases for the latest image.
Make sure to download the "PinePhone" image and to unpack the archive before flashing.

= Factory Test OS =

{{Hint|'''Note:''' The magnetometer test will fail on the new Beta Edition, as the factory image wasn't updated for it yet.}}On the Braveheart model, there was a postmarketOS based basic Factory Test OS pre-installed on the eMMC.
The developer Martijn Braam from postmarketOS has improved the functionality of the image considerably later.
Since the 20200501 version, it is able to test all the hardware.
It also includes functionality to install a new OS to the eMMC when using with an test image that includes that OS image.
The downloadable image just does the hardware tests.
Do not flash eMMC to test your device, just dd it to microSD and test from there.
New versions are distributed as part of the postmarketOS distribution.

Links:
* [https://images.postmarketos.org/pinephone/ Software Images] (download the latest one named like pine-pinephone-yyyyMMdd-factorytestX.img.xz)
* [https://gitlab.com/MartijnBraam/factorytest Git repo]
* [https://gitlab.com/MartijnBraam/factorytest/-/blob/master/README.rst Documentation]

== Factory-loaded OS builds ==

These are different operating system builds that was preloaded in the factory with testing utility.

Download the build, extract the image and dd it to a 8 GB or larger microSD card, then insert it into the PinePhone.
After power up or reboot, you may perform and complete the test routine, or apply the build from microSD card to eMMC.

All the download links below are direct download from pine64.org.

<div style="overflow: auto;">
{| class="wikitable" style="white-space: nowrap"
! OS
! Download Link
! File Size
! MD5
|-
| Beta Edition
| [https://files.pine64.org/os/PinePhone/BetaEdition/pine64-pinephone-plamo-beta-factorytest.img.xz pine64-pinephone-plamo-beta-factorytest.img.xz]
| 1.78GB
| <code>f16bce93504a52217540ac886863a418</code>
|-
| Mobian
| [https://files.pine64.org/os/PinePhone/Mobian/pine64-pinephone-20201207-factorytest-mobian.img.xz pine64-pinephone-20201207-factorytest-mobian.img.xz]
| 1.41GB
| <code>015be381ff4e650a7fca6d4eaa90d63d</code>
|-
| KDE
| [https://files.pine64.org/os/PinePhone/KDE/pine64-pinephone-20201208-factorytest-kde.img.xz pine64-pinephone-20201208-factorytest-kde.img.xz]
| 2.28GB
| <code>32979ff17b5ec4d358ce99f1aff0c77c</code>
|-
| Manjaro
| [https://files.pine64.org/os/PinePhone/Manjaro/pine64-pinephone-20201013-manjaro-stable-20201018-factory56.img.xz pine64-pinephone-20201013-manjaro-stable-20201018-factory56.img.xz]
| 1.04GB
| <code>4edfd4dceaefdd32a3417c1727161c29</code>
|-
| postmarketOS
| [https://files.pine64.org/os/PinePhone/PostMarketOS/pine64-pinephone-20200726-phosh-v20.05-factory.img.xz pine64-pinephone-20200726-phosh-v20.05-factory.img.xz]
| 517MB
| <code>244093be2f6d728fcbd1d29114607727</code>
|-
| Ubuntu Touch
| [https://files.pine64.org/os/PinePhone/UBPorts/PinePhone-flasher-ubuntu-7b.img.gz PinePhone-flasher-ubuntu-7b.img.gz]
| 1.05GB
| <code>2d7f5271e7a281db8f1b1219bedbe131</code>
|}
</div>

= Installing other ARM64 distributions =

{{Warning|Distributions not on this page may not even boot after you follow this section. In the best case, they will be barely usable.
This is more for fun, or if you would like to port a new distribution to the PinePhone.}}{{Hint|'''Note:''' This section uses megi's kernel releases, and not the official ones from Pine64. While it is possible to use the official (and in the future, mainline) kernel, megi provides binary releases, which makes it very easy.}}General steps:

# Create a boot partition (from 4 MB to about 252 MB) and a root partition (from the end of boot to the end of the card) filesystem on the SD card.
# Format the boot partition with vfat, and the root partition with a supported filesystem like ext4 or f2fs.
# Extract the root filesystem from your distribution's ARM image into the root filesystem on the SD card. Do not copy the partition, copy the files instead (in archive mode, like <code>rsync -ar</code>).
# Edit <code>/etc/fstab</code> to match your partitions.
# Grab megi's kernel from https://xff.cz/kernels/, Follow the instructions in the [https://xff.cz/kernels/README README], which involves copying the kernel modules into the SD card rootfs, and writing u-boot and the bootloader.

If you would like to see examples or specific commands for how to complete these steps, see:
* [https://github.com/nikhiljha/pp-fedora-sdsetup an example for Fedora], current unofficial [#Fedora] release
* [https://xnux.eu/howtos/install-arch-linux-arm.html an example for Arch Linux] by megi

= Other Resources =
Community
* [[Main_Page#Community_and_Support|Links to the community services]]

Hardware information
* [[PinePhone|General PinePhone hardware info]] in this Pine64 wiki
* Details specific to the Braveheart Edition: [[PinePhone_v1.1_-_Braveheart|PinePhone 1.1 Braveheart hardware details]]
* Details specific to the Community Edition: [[PinePhone_v1.2|PinePhone 1.2 hardware details]]
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here] and the preceding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here]

Other software information
* [https://linux-sunxi.org/Main_Page sunxi community wiki]
* [https://xnux.eu/devices/pine64-pinephone.html megi's feature/driver support matrix]
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)] see demonstration [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube]
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]

Other
* [https://pine64.com/?post_type=product Pine64 shop]
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on Linux distributions and desktop environments on mobile devices]
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing microSD cards]

[[Category:PinePhone]]

User:RainSlide/CSS Boxes

2021-09-22T11:44:05Z

RainSlide: Add more desc

This page is mainly for showing why [[Template:Hint]], [[Template:Note]] and [[Template:Warning]] uses <code>display: table</code> to archive compatibility for both adaptive width and floating sibling(s).

If a set of style is not compatible with adaptive width,
it span to its full width even when it don't need to.

If a set of style is not compatible with floating sibling(s),
the element may still work well with some short content in it;
in another word, it may still looks fine when its
''content width'' + ''margin'' + ''padding'' + ''border''
is lower than the "remaining width" lefted by the floating sibling(s).
So we have to use Lorem ipsum (as well as a floating box, for sure) to test it.

Ideally, you may just set the widths to fixed values,
and pretend nothing happens and CSS is awesome.
However, the content container of MediaWiki got adaptive width,
and maybe you are maintaining a MediaWiki [[Template:Template|Template]],
with only inline styles.

<div style="position: fixed; top: 12.5vh; font-size: 25vh; line-height: 1; font-weight: bold; white-space: pre; color: lightblue; opacity: .1; user-select: none; pointer-events: none;">CSS<br>is<br>Awesome</div>

== Table ==

=== <code>display: table</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid;">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for adaptive width.</div>

<div style="display: table; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for floating siblings.<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

</div>

{| class="wikitable"
! This is a wikitable
|-
| <div style="display: table; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No padding when it's in another table, however.</div>
|}

=== <code>display: table-cell</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid;">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-cell; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for adaptive width.</div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table cells are not blocky! Without this sentence, they are in the same row by now.</p>

<div style="display: table-cell; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for floating siblings.<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table cells have no margin.</p>

</div>

=== <code>display: table-caption</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-caption; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No adaptive width.</div>

<div style="display: table-caption; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
It's hiding.<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">There can only be one table caption per table, or, per anything.</p>

</div>

=== <code>display: table-row</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-row; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for adaptive width?</div>

<div style="display: table-row; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for floating siblings?<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table rows have no margin, padding or border.</p>

</div>

Other table display values works like table rows, or won't even display its contents.

== A new block formatting context ==

See guide [https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Block_formatting_context Block formatting context] on MDN.

=== <code>float: left</code> ===

''Will everything go right?''

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="float: left; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for adaptive width.</div>

<div style="float: left; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
It falls off from its floating siblings.<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

</div>

''No, something falls down.''

== <code>display: inline-block</code> ==

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: inline-block; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for adaptive width.</div>

<div style="display: inline-block; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
But inline blocks are inline.</div>

<div style="display: inline-block; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
It also falls off from its floating siblings.<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

</div>

== <code>display: flow-root</code> ==

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: flow-root; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No adaptive width.</div>

<div style="display: flow-root; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for floating siblings.<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

</div>

This is the end of part one. Part two will feature <code>contain: content</code>, <code>width: max-content</code>, <code>box-sizing: border-box; max-width: 100%</code>, <code>display: flex</code>, <code>display: grid</code>, and more, if I ever got time to work on the part two.

Template:Warning

2021-09-22T11:30:43Z

RainSlide: Fix

<noinclude>

{{Template}}

A waring box for highlighting dangerous actions and security warnings. It starts with "'''Warning:'''" by default.

== Usage ==

<nowiki>{{Warning|warning content}}</nowiki>

== Example ==

<nowiki>{{Warning|This is a warning.}}</nowiki>

{{Warning|This is a warning.}}

== Technical notes ==

The boxes use <code>display: table</code> to support both adaptive width and floating siblings, all other alternatives can't archive them as perfect as this solution within just one HTML element. However, it has its own flaw, if you put it into another table, its padding will gone. Avoid putting hints, notes and warnings into any tables until solution was found, or we give up and use two elements for just one box.

This template uses class <code>.template-box</code> and <code>.template-warning</code>.
In the future, if the [https://www.mediawiki.org/wiki/Extension:TemplateStyles TemplateStyles Extension] is installed on this MediaWiki instance,
one may move the embedded inline styles to Template Style files.

== See also ==

* [https://wiki.archlinux.org/title/Template:Warning ArchWiki: Template:Warning]: the template on which this one is based on
* [[Template:Hint]]
* [[Template:Note]]

</noinclude><includeonly>

<div role="note" class="template-box" style="
display: table;
min-width: 16em;
min-height: 1.6em;
margin: .5em 0 1em;
padding: .5em 1em;
border: 1px solid #d33;
color: black;
background-color: #fee7e6;
"><strong>Warning:</strong> {{{1|}}}</div>

</includeonly>

Template:Warning

2021-09-22T11:27:09Z

RainSlide: Add more technical notes

<noinclude>

{{Template}}

A waring box for highlighting dangerous actions and security warnings. It starts with "'''Warning:'''" by default.

== Usage ==

<nowiki>{{Warning|warning content}}</nowiki>

== Example ==

<nowiki>{{Warning|This is a warning.}}</nowiki>

{{Warning|This is a warning.}}

== Technical notes ==

The boxes use <code>display: table</code> to support both adaptive width and floating siblings, all other alternatives can't archive them as perfect as this solution within just one HTML element. However, it has its own flaw, if you put it into another table, its padding will gone. Avoid putting hints, notes and warnings into any tables until solution was found, or we give up and use two elements for just one box.

This template uses class <code>.template-box</code> and <code>.template-warning</code>.
In the future, if the [https://www.mediawiki.org/wiki/Extension:TemplateStyles TemplateStyles Extension] is installed on this MediaWiki instance,
one may move the embedded inline styles to Template Style files.

== See also ==

* [https://wiki.archlinux.org/title/Template:Warning ArchWiki: Template:Warning]: the template on which this one is based on
* [[Template:Hint]]
* [[Template:Note]]

</noinclude><includeonly>

<div role="note" class="template-box template-warning" style="
display: table;
min-width: 16em;
min-height: 1.6em;
margin: .5em 0 1em;
padding: .5em 1em;
border: 1px solid #d33;
color: black;
background-color: #fee7e6;
">{{{1|}}}</div>

</includeonly>

Template:Hint

2021-09-22T11:27:06Z

RainSlide: Add more technical notes

<noinclude>

{{Template}}

A hint box for showing helpful hints.

== Usage ==

<nowiki>{{Hint|hint content}}</nowiki>

== Example ==

<nowiki>{{Hint|This is an hint.}}</nowiki>

{{Hint | This is an hint.}}

For a more flexible usage, it doesn't start with "'''Hint:'''" by default,
you may add it manually with <code><nowiki>'''Hint:'''</nowiki></code>:

<nowiki>{{Hint|'''Hint:''' This is another hint.}}</nowiki>

{{Hint | '''Hint:''' This is another hint.}}

== Technical notes ==

The boxes use <code>display: table</code> to support both adaptive width and floating siblings, all other alternatives can't archive them as perfect as this solution within just one HTML element. However, it has its own flaw, if you put it into another table, its padding will gone. Avoid putting hints, notes and warnings into any tables until solution was found, or we give up and use two elements for just one box.

This template uses class <code>.template-box</code> and <code>.template-hint</code>.
In the future, if the [https://www.mediawiki.org/wiki/Extension:TemplateStyles TemplateStyles Extension] is installed on this MediaWiki instance,
one may move the embedded inline styles to Template Style files.

== See also ==

* [https://wiki.archlinux.org/title/Template:Tip ArchWiki: Template:Tip]: the template on which this one is based on
* [[Template:Note]]
* [[Template:Warning]]

</noinclude><includeonly>

<div role="note" class="template-box template-hint" style="
display: table;
min-width: 16em;
min-height: 1.6em;
margin: .5em 0;
padding: .5em 1em;
border: 1px solid #9bcdfd;
color: #003670;
background-color: #d1ecfd;
">{{{1|}}}</div>

</includeonly>

Template:Note

2021-09-22T11:27:04Z

RainSlide: Add more technical notes

<noinclude>

{{Template}}

A note box for showing important notes.

== Usage ==

<nowiki>{{Note|note content}}</nowiki>

== Examples ==

<nowiki>{{Note|This is an note.}}</nowiki>

{{Note | This is an note.}}

For a more flexible usage, it doesn't start with "'''Note:'''" by default,
you may add it manually with <code><nowiki>'''Note:'''</nowiki></code>:

<nowiki>{{Note|'''Note:''' This is an note.}}</nowiki>

{{Note | '''Note:''' This is an note.}}

== Technical notes ==

The boxes use <code>display: table</code> to support both adaptive width and floating siblings, all other alternatives can't archive them as perfect as this solution within just one HTML element. However, it has its own flaw, if you put it into another table, its padding will gone. Avoid putting hints, notes and warnings into any tables until solution was found, or we give up and use two elements for just one box.

This template uses class <code>.template-box</code> and <code>.template-note</code>.
In the future, if the [https://www.mediawiki.org/wiki/Extension:TemplateStyles TemplateStyles Extension] is installed on this MediaWiki instance,
one may move the embedded inline styles to Template Style files.

== See also ==

* [https://wiki.archlinux.org/title/Template:Note ArchWiki: Template:Note]: the template on which this one is based on
* [[Template:Hint]]
* [[Template:Warning]]

</noinclude><includeonly>

<div role="note" class="template-box template-hint" style="
display: table;
min-width: 16em;
min-height: 1.6em;
margin: .5em 0 1em;
padding: .5em 1em;
border: 1px solid #fc3;
color: #705000;
background-color: #fef6e7;
">{{{1|}}}</div>

</includeonly>

User:RainSlide/CSS Boxes

2021-09-22T11:18:33Z

RainSlide: /* A new block formatting context */ Add MDN link

If a set of style is not compactable with adaptive width,
it span to its full width even when it don't need to.

If a set of style is not compactable with floating sibling(s),
the element may still work well with some short content in it;
in another word, it may still looks fine when its
''content width'' + ''margin'' + ''padding'' + ''border''
is lower than the "remaining width" lefted by the floating sibling(s).
So we have to use Lorem ipsum (as well as a floating box, for sure) to test it.

Ideally, you may just set the widths to fixed values,
and pretend nothing happens and CSS is awesome.
However, the content container of MediaWiki got adaptive width,
and maybe you are maintaining a MediaWiki [[Template:Template|Template]],
with only inline styles.

== Table ==

=== <code>display: table</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid;">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for adaptive width.</div>

<div style="display: table; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for floating siblings.<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

</div>

{| class="wikitable"
! This is a wikitable
|-
| <div style="display: table; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No padding when it's in another table, however.</div>
|}

=== <code>display: table-cell</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid;">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-cell; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for adaptive width.</div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table cells are not blocky! Without this sentence, they are in the same row by now.</p>

<div style="display: table-cell; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for floating siblings.<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table cells have no margin.</p>

</div>

=== <code>display: table-caption</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-caption; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No adaptive width.</div>

<div style="display: table-caption; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
It's hiding.<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">There can only be one table caption per table, or, per anything.</p>

</div>

=== <code>display: table-row</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-row; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for adaptive width?</div>

<div style="display: table-row; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for floating siblings?<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table rows have no margin, padding or border.</p>

</div>

Other table display values works like table rows, or won't even display its contents.

== A new block formatting context ==

See guide [https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Block_formatting_context Block formatting context] on MDN.

=== <code>float: left</code> ===

''Will everything go right?''

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="float: left; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for adaptive width.</div>

<div style="float: left; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
It falls off from its floating siblings.<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

</div>

''No, something falls down.''

== <code>display: inline-block</code> ==

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: inline-block; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for adaptive width.</div>

<div style="display: inline-block; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
But inline blocks are inline.</div>

<div style="display: inline-block; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
It also falls off from its floating siblings.<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

</div>

== <code>display: flow-root</code> ==

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: flow-root; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No adaptive width.</div>

<div style="display: flow-root; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for floating siblings.<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

</div>

This is the end of part one. Part two will feature <code>contain: content</code>, <code>width: max-content</code>, <code>box-sizing: border-box; max-width: 100%</code>, <code>display: flex</code>, <code>display: grid</code>, and more, if I ever got time to work on the part two.

User:RainSlide/CSS Boxes

2021-09-22T11:17:06Z

RainSlide: /* float: right */ It's left

If a set of style is not compactable with adaptive width,
it span to its full width even when it don't need to.

If a set of style is not compactable with floating sibling(s),
the element may still work well with some short content in it;
in another word, it may still looks fine when its
''content width'' + ''margin'' + ''padding'' + ''border''
is lower than the "remaining width" lefted by the floating sibling(s).
So we have to use Lorem ipsum (as well as a floating box, for sure) to test it.

Ideally, you may just set the widths to fixed values,
and pretend nothing happens and CSS is awesome.
However, the content container of MediaWiki got adaptive width,
and maybe you are maintaining a MediaWiki [[Template:Template|Template]],
with only inline styles.

== Table ==

=== <code>display: table</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid;">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for adaptive width.</div>

<div style="display: table; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for floating siblings.<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

</div>

{| class="wikitable"
! This is a wikitable
|-
| <div style="display: table; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No padding when it's in another table, however.</div>
|}

=== <code>display: table-cell</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid;">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-cell; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for adaptive width.</div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table cells are not blocky! Without this sentence, they are in the same row by now.</p>

<div style="display: table-cell; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for floating siblings.<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table cells have no margin.</p>

</div>

=== <code>display: table-caption</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-caption; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No adaptive width.</div>

<div style="display: table-caption; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
It's hiding.<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">There can only be one table caption per table, or, per anything.</p>

</div>

=== <code>display: table-row</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-row; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for adaptive width?</div>

<div style="display: table-row; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for floating siblings?<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table rows have no margin, padding or border.</p>

</div>

Other table display values works like table rows, or won't even display its contents.

== A new block formatting context ==

=== <code>float: left</code> ===

''Will everything go right?''

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="float: left; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for adaptive width.</div>

<div style="float: left; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
It falls off from its floating siblings.<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

</div>

''No, something falls down.''

== <code>display: inline-block</code> ==

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: inline-block; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for adaptive width.</div>

<div style="display: inline-block; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
But inline blocks are inline.</div>

<div style="display: inline-block; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
It also falls off from its floating siblings.<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

</div>

== <code>display: flow-root</code> ==

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: flow-root; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No adaptive width.</div>

<div style="display: flow-root; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for floating siblings.<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

</div>

This is the end of part one. Part two will feature <code>contain: content</code>, <code>width: max-content</code>, <code>box-sizing: border-box; max-width: 100%</code>, <code>display: flex</code>, <code>display: grid</code>, and more, if I ever got time to work on the part two.

User:RainSlide/CSS Boxes

2021-09-22T11:16:25Z

RainSlide: CSS Boxes, part one

If a set of style is not compactable with adaptive width,
it span to its full width even when it don't need to.

If a set of style is not compactable with floating sibling(s),
the element may still work well with some short content in it;
in another word, it may still looks fine when its
''content width'' + ''margin'' + ''padding'' + ''border''
is lower than the "remaining width" lefted by the floating sibling(s).
So we have to use Lorem ipsum (as well as a floating box, for sure) to test it.

Ideally, you may just set the widths to fixed values,
and pretend nothing happens and CSS is awesome.
However, the content container of MediaWiki got adaptive width,
and maybe you are maintaining a MediaWiki [[Template:Template|Template]],
with only inline styles.

== Table ==

=== <code>display: table</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid;">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for adaptive width.</div>

<div style="display: table; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for floating siblings.<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

</div>

{| class="wikitable"
! This is a wikitable
|-
| <div style="display: table; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No padding when it's in another table, however.</div>
|}

=== <code>display: table-cell</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid;">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-cell; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for adaptive width.</div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table cells are not blocky! Without this sentence, they are in the same row by now.</p>

<div style="display: table-cell; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for floating siblings.<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table cells have no margin.</p>

</div>

=== <code>display: table-caption</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-caption; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No adaptive width.</div>

<div style="display: table-caption; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
It's hiding.<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">There can only be one table caption per table, or, per anything.</p>

</div>

=== <code>display: table-row</code> ===

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: table-row; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for adaptive width?</div>

<div style="display: table-row; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for floating siblings?<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

<p style="display: table; background-color: #FEE; padding: 0 1ch; border: 1px solid;">Table rows have no margin, padding or border.</p>

</div>

Other table display values works like table rows, or won't even display its contents.

== A new block formatting context ==

=== <code>float: right</code> ===

''Will everything go right?''

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="float: left; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for adaptive width.</div>

<div style="float: left; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
It falls off from its floating siblings.<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

</div>

''No, something falls down.''

== <code>display: inline-block</code> ==

<div style="overflow: auto;">

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: inline-block; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for adaptive width.</div>

<div style="display: inline-block; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
But inline blocks are inline.</div>

<div style="display: inline-block; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
It also falls off from its floating siblings.<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

</div>

== <code>display: flow-root</code> ==

<div style="float: right; margin: .5em 0 .5em .5em; padding: .5em 1em; border: 1px solid; background-color: ">
This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.<br>This is a floating box.</div>

<div style="display: flow-root; background-color: #FEE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No adaptive width.</div>

<div style="display: flow-root; background-color: #EFE;
margin: .5em 0; padding: .5em 1em; border: 1px solid;">
No problem for floating siblings.<br>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</div>

</div>

This is the end of part one. Part two will feature <code>contain: content</code>, <code>width: max-content</code>, <code>box-sizing: border-box; max-width: 100%</code>, <code>display: flex</code>, <code>display: grid</code>, and more, if I ever got time to work on the part two.

Template:Hint

2021-09-22T09:05:06Z

RainSlide: Add content to Usage and Example

<noinclude>

{{Template}}

A hint box for showing helpful hints.

== Usage ==

<nowiki>{{Hint|hint content}}</nowiki>

== Example ==

<nowiki>{{Hint|This is an hint.}}</nowiki>

{{Hint | This is an hint.}}

For a more flexible usage, it doesn't start with "'''Hint:'''" by default,
you may add it manually with <code><nowiki>'''Hint:'''</nowiki></code>:

<nowiki>{{Hint|'''Hint:''' This is another hint.}}</nowiki>

{{Hint | '''Hint:''' This is another hint.}}

== Technical notes ==

The boxes use

This template uses class <code>.template-box</code> and <code>.template-hint</code>.
In the future, if the [https://www.mediawiki.org/wiki/Extension:TemplateStyles TemplateStyles Extension] is installed on this MediaWiki instance,
one may move the embedded inline styles to Template Style files.

== See also ==

* [https://wiki.archlinux.org/title/Template:Tip ArchWiki: Template:Tip]: the template on which this one is based on
* [[Template:Note]]
* [[Template:Warning]]

</noinclude><includeonly>

<div role="note" class="template-box template-hint" style="
display: table;
min-width: 16em;
min-height: 1.6em;
margin: .5em 0;
padding: .5em 1em;
border: 1px solid #9bcdfd;
color: #003670;
background-color: #d1ecfd;
">{{{1|}}}</div>

</includeonly>

Template:Warning

2021-09-22T09:05:01Z

RainSlide: Enhance Example

<noinclude>

{{Template}}

A waring box for highlighting dangerous actions and security warnings. It starts with "'''Warning:'''" by default.

== Usage ==

<nowiki>{{Warning|warning content}}</nowiki>

== Example ==

<nowiki>{{Warning|This is a warning.}}</nowiki>

{{Warning|This is a warning.}}

== Technical notes ==

This template uses class <code>.template-box</code> and <code>.template-warning</code>.
In the future, if the [https://www.mediawiki.org/wiki/Extension:TemplateStyles TemplateStyles Extension] is installed on this MediaWiki instance,
one may move the embedded inline styles to Template Style files.

== See also ==

* [https://wiki.archlinux.org/title/Template:Warning ArchWiki: Template:Warning]: the template on which this one is based on
* [[Template:Hint]]
* [[Template:Note]]

</noinclude><includeonly>

<div role="note" class="template-box template-warning" style="
display: table;
min-width: 16em;
min-height: 1.6em;
margin: .5em 0 1em;
padding: .5em 1em;
border: 1px solid #d33;
color: black;
background-color: #fee7e6;
">{{{1|}}}</div>

</includeonly>

Template:Note

2021-09-22T09:04:54Z

RainSlide: Enhance Example

<noinclude>

{{Template}}

A note box for showing important notes.

== Usage ==

<nowiki>{{Note|note content}}</nowiki>

== Examples ==

<nowiki>{{Note|This is an note.}}</nowiki>

{{Note | This is an note.}}

For a more flexible usage, it doesn't start with "'''Note:'''" by default,
you may add it manually with <code><nowiki>'''Note:'''</nowiki></code>:

<nowiki>{{Note|'''Note:''' This is an note.}}</nowiki>

{{Note | '''Note:''' This is an note.}}

== Technical notes ==

This template uses class <code>.template-box</code> and <code>.template-note</code>.
In the future, if the [https://www.mediawiki.org/wiki/Extension:TemplateStyles TemplateStyles Extension] is installed on this MediaWiki instance,
one may move the embedded inline styles to Template Style files.

== See also ==

* [https://wiki.archlinux.org/title/Template:Note ArchWiki: Template:Note]: the template on which this one is based on
* [[Template:Hint]]
* [[Template:Warning]]

</noinclude><includeonly>

<div role="note" class="template-box template-hint" style="
display: table;
min-width: 16em;
min-height: 1.6em;
margin: .5em 0 1em;
padding: .5em 1em;
border: 1px solid #fc3;
color: #705000;
background-color: #fef6e7;
">{{{1|}}}</div>

</includeonly>

PinePhone Software Releases

2021-09-22T08:30:18Z

RainSlide: /* Multi-distro demo image */ Remove empty lines

This page contains a list of all available OS releases for the [[PinePhone]], as well as links to other resources.

See [[PinePhone Installation Instructions]] on how to install the operating systems.<br>
However, if your phone came preloaded with software, Please see [[PinePhone Updating Instructions]].

{{Hint| '''Note:''' Some releases may not have a good setup for the backlight at low brightness.
If configured too low, the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.}}

= Software Releases =

This is a list of OSes that specifically support the PinePhone.
Since PinePhone support is included in Mainline Linux, in principle, any ARM Linux OS can be used if possible required patches are included.

== Arch Linux ARM ==
[[File:Archlinux-logo.png|right|100px]]

(Unofficial) Arch Linux ARM with choice of Phosh UI, Plasma Mobile, or barebones.
Currently being maintained by the [https://danctnix.org/ DanctNIX] community (GitHub: [https://github.com/DanctNIX/danctnix danctnix], [https://github.com/dreemurrs-embedded dreemurrs-embedded]).

* GitHub: [https://github.com/dreemurrs-embedded/Pine64-Arch dreemurrs-embedded/Pine64-Arch]

'''Download location'''

Get the latest image here: https://github.com/dreemurrs-embedded/Pine64-Arch/releases

'''username/password'''

{| class="wikitable"
! Default user || <code>alarm/123456</code>
! root || <code>root/root</code>
|}

'''What works, what does not work'''

Most of the things now works, there are some minor issues with [[Crust]].

'''How to contribute and report defects'''

You may find the Discord, Matrix and Telegram of DanctNIX community at [https://github.com/DanctNIX/danctnix/blob/master/README.md#channel-list the Channel list section of DanctNIX/README.md].

Feel free to send us [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls pull requests] and report [https://github.com/dreemurrs-embedded/Pine64-Arch/issues issues] on [https://github.com/dreemurrs-embedded/Pine64-Arch GitHub].

== ExpidusOS ==

A fork of [https://voidlinux.org Void Linux] with a custom fork of XFCE called [https://github.com/ExpidusOS/genesis Gensis] as the default desktop environment, developed by [https://midstall.com/ Midstall Software].

* [https://expidusos.com ExpidusOS official website]
* [https://wiki.expidusos.com/index.php/Main_Page ExpidusOS Wiki]
* [https://discord.gg/GVfBF2w Midstall Software Discord server]
* GitHub: [https://github.com/ExpidusOS ExpidusOS]

'''Download location'''

Check the [https://expidusos.com/download download page] for that latest version, or the [https://build.expidusos.com/ image file list] for all versions, look for the file name that starts with "pinephone".

'''username/password'''

expidus/expidus

'''What works, what does not work'''

The ExpidusOS Wiki has a page detailing [https://wiki.expidusos.com/index.php/Device:PinePhone supported features].

'''How to contribute and report defects'''

Join the [https://discord.gg/GVfBF2w Discord server] or corresponding repo at GitHub ([https://github.com/orgs/ExpidusOS/repositories repo list]).

== Fedora ==
[[File:Fedora-logo.png|right|100px]]

An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and [https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/ some additional packages] to tie it all together.
It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.

* Forum discussion: [https://forum.pine64.org/showthread.php?tid=9347 Fedora + Phosh for PinePhone]
* GitHub: [https://github.com/nikhiljha/pp-fedora-sdsetup nikhiljha/pp-fedora-sdsetup]

'''Download location'''

* [https://github.com/nikhiljha/pp-fedora-sdsetup/releases Flashable images]
* [https://github.com/nikhiljha/pp-fedora-sdsetup Build scripts]
* [https://copr.fedorainfracloud.org/coprs/njha/mobile/ Packages (Fedora COPR)]

There is also an FTP server with a full Fedora 34 workstation build with phosh: ftp://pine.warpspeed.dk/nightly/pinephone/ (Mount this with something like Nautilus)

'''username/password'''

pine/123456

'''What works, what does not work'''

WiFi, Bluetooth, SMS, Data, Calls all work!

There are still a few bugs though, and [https://xnux.eu/devices/pine64-pinephone.html#toc-feature-driver-support-matrix some features don't have driver support yet] on any PinePhone distribution.

'''How to contribute and report defects'''

Please send your bug reports to [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker].
Be sure to include logs if applicable!
Send us pull requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/pulls Github].

== Gentoo ==
[[File:GentooLogo.png|right|100px]]{{hint|Please consider cross-compiling the software on the computer.
Long compilation times and heat production can lead to a reduced lifespan of the phone.}}There are unofficial Gentoo overlays with ebuilds for the PinePhone.
There are no images - you'll be building it yourself, picking which kernel, bootloader and desktop environment you want to use.
You will be using the arm64 version of Gentoo.

'''Documentation'''

* https://stealthgun.tweakblogs.net/blog/19336/gentoo-on-a-pinephone
* https://wiki.gentoo.org/wiki/User:Dr41nU/PinePhone
* https://wiki.gentoo.org/wiki/PinePhone (incomplete)

'''Overlay locations'''

* https://gitlab.com/bingch/gentoo-overlay
* https://github.com/stealthgun/gjdwebserver-overlay

== GloDroid ==

{{Hint|There can be large intervals between release update, so available images may be outdated and do not reflect the state of the current developments.}}A fully open source port of Android to the PinePhone.

* GitHub: [https://github.com/GloDroid GloDroid]

'''Download location'''

https://github.com/GloDroid/glodroid_manifest/releases (last release at 2021-05-20)

'''What works, what does not work'''

Works: WiFi, screen dimming, touchscreen and charging work.
Don't work: Bluetooth, Telephony, GPS, Sound

== LuneOS ==
[[File:WebOS-Ports-logo.png|right|100px]]

LuneOS is a open source mobile operating system based on [https://www.webosose.org/ webOS Open Source Edition]([https://github.com/webosose GitHub], previously known as [https://github.com/openwebos Open webOS]) by LG, comes with [https://webos-ports.org/wiki/Luna_Next Luna Next] UI, currently developed by the WebOS Ports community.

* [https://www.webos-ports.org/wiki/Main_Page WebOS Ports Wiki]
* [https://webos-ports.org/wiki/Pinephone_Info WebOS-Ports Wiki's Pinephone page]
* GitHub: [https://github.com/webOS-ports WebOS Ports]

'''Download location'''

* [http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]

It is recommended to use ''bmaptool'', which is faster than dd, and can decompress archived image files on-the-fly.

Syntax is:

bmaptool copy [from] [to]

For example:

bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-140.rootfs.wic.gz /dev/mmcblk0

.wic file can be treated as .img file when flashing. You may rename .wic file to .img when using GUI tools that require file extension to be .img.

== Maemo Leste ==
[[File:Maemoleste-logo.png|right|100px]]

[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices,
originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it.
The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices.

The new version Maemo 8 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel.
The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK].
The current version is Devuan Beowulf (Debian Buster) and has simultaneous support for both Devuan and Debian.

In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository].
To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's build]).
Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.

* [https://maemo-leste.github.io/ Maemo Leste website]
* [https://leste.maemo.org/Main_Page Maemo Leste Wiki]
** [https://leste.maemo.org/PinePhone PinePhone wiki page]
** [https://leste.maemo.org/Leste_FAQ Maemo Leste FAQ]
* GitHub: [https://github.com/maemo-leste maemo-leste]
* Twitter: [https://twitter.com/maemoleste @maemoleste]

'''Download location'''

[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds]. There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].

'''username/password'''

root/toor

You may use <code>sudo</code> directly.

'''What works, what does not work'''

For current status and workarounds, please read their [https://leste.maemo.org/PinePhone PinePhone wiki page].

'''How to contribute and report defects'''

Most discussion occurs at [ircs://irc.libera.chat:6697/#maemo-leste <code>#maemo-leste</code> on <code>irc.libera.chat</code>].
The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback.

All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki.

Submit [https://github.com/maemo-leste/bugtracker/issues bug reports] on github.
To track known issues, you may use these search terms:
[https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone],
[https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64].

Learn about
[https://leste.maemo.org/Development development],
[https://leste.maemo.org/Development/Porting_Packages porting packages],
[https://leste.maemo.org/Development/Building_Packages building packages],
[https://leste.maemo.org/Development/Tasks todo list],
and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian].
Some tasks have funding available.

== Manjaro ARM ==
[[File:Manjaro-logo.svg|right|100px]]

Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.

'''Download location'''

* Phosh: [https://github.com/manjaro-pinephone/phosh Stable] / [https://github.com/manjaro-pinephone/phosh-dev Dev]
* Plasma Mobile: [https://github.com/manjaro-pinephone/plasma-mobile Stable] / [https://github.com/manjaro-pinephone/plasma-mobile-dev Dev]
* Lomiri: [https://github.com/manjaro-pinephone/lomiri-dev Dev] (No longer maintained)

'''username/password'''

{| class="wikitable"
! Default user || <code>manjaro/123456</code>
! root || <code>root/root</code>
|}

'''What works, what does not work'''{{Hint| '''Note:''' At the first boot, the Phosh image will be loaded at a TTY login prompt for multiple minutes.}}See Manjaro's release announcements on their forum.
Recent ones:
[https://forum.manjaro.org/t/manjaro-arm-beta12-with-phosh-pinephone/73099 Phosh],
[https://forum.manjaro.org/t/manjaro-arm-beta5-with-plasma-mobile-pinephone/69318 Plasma] and
[https://forum.manjaro.org/t/manjaro-arm-alpha3-with-lomiri-pinephone/49923 Lomiri].

'''How to contribute and report defects'''

See the end of the [https://forum.manjaro.org/t/manjaro-arm-beta7-with-phosh-pinephone/58901 announcement].

== Mobian ==
[[File:Debian-logo.png|right|100px]]

An unofficial [https://www.debian.org Debian] build for ARM64 running with Phosh (developed by Purism, uses Wayland instead of Xorg).
The base system is pure Debian, with only the GUI applications and a few others (ModemManager, WiFi chip firmware) being built from modified sources (as well as the kernel and u-boot).
Current version is Debian Bookworm.

'''Download location'''

[https://images.mobian-project.org/pinephone/nightly/ Nightly] /
[https://images.mobian-project.org/pinephone/installer/ Installer] /
[https://images.mobian-project.org/pinephone/ Stable]

Extract the image before installing:

$ gzip -d Downloads/mobian-pinephone-*.img.gz

See the [https://wiki.mobian-project.org/doku.php?id=install project page] for specific installation instructions.

'''username/password'''

mobian/1234

'''What works, what does not work'''

See [https://gitlab.com/mobian1/mobian-recipes/-/blob/master/README.md the project's README file] or [https://wiki.mobian-project.org/doku.php?id=pinephone the wiki] for most up to date status.

Check [https://gitlab.com/groups/mobian1/-/issues bug tracker] for known issues. Questions? Ask on our [https://forum.pine64.org/showthread.php?tid=9016 thread].

'''How to contribute and report defects'''

It is recommended that you log your bug reports in [https://gitlab.com/mobian1/issues the project's issue tracker].
As a general rule, issues with third-party apps (even the default ones) should be reported upstream.
A Mobian issue would be related to getting the hardware to work on the PinePhone,
but if unsure where the issue should be reported just open a ticket or ask.
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/mobian1 Gitlab].

'''Notes'''

See [https://wiki.mobian-project.org/doku.php?id=start the wiki] for additional information regarding screen resolution, USB networking, WiFi hotspot, Chatty and the repository.

== Multi-distro demo image ==

{{Warning | This is an demo image for testing different OSes before installing a regular image. It is highly discouraged attempting to use the image productively. The kernel is shared across the different OSes and is not being updated.}}

This image allow users to try many of the above Linux distributions easily, without having to figure out how to flash them individually and juggle with many microSD cards. Also called megi's 15-in-1 multi boot image.

* Main page: https://xnux.eu/p-boot-demo/
* Git repo: https://megous.com/git/pinephone-multi-boot/
* Forum discussion: [https://forum.pine64.org/showthread.php?tid=11347 UPDATED (June 2021): 17-distro multi-boot image for Pinephone (incl. 3GiB variant)]

'''Update 2021-06-02, using megi's kernel 5.13-rc4'''

DD image to SD card and boot. This image is for 16GiB or larger SD cards, also works if flashed to eMMC.

This is also a good build for charging depleted battery. Just boot up this build with power supply connected, keep the PinePhone charging for 3 hours at power down stage.

For more info on this build, please visit its entry the "News" section of its [https://xnux.eu/p-boot-demo/ web page].

* [http://dl.xnux.eu/p-boot-multi-2021-06-02.torrent Download torrent file from author's website]
* [http://dl.xnux.eu/p-boot-multi-2021-06-02/ Download img.zst from author's website] (speed limited to 512KiB/s)
* [http://mirror.uxes.cz/dl.xnux.eu/ Download torrent and img.zst from discord user uxes' mirror]
** '''File name:''' multi.img.zst
** '''SHA-256:''' <span style="word-break: break-all">9b099cdfece3ba862348ca32af6c51a41a1d161b1d897f9928ae8be3c824a0b6</span>
** '''File Size:''' 6.57GiB

* [https://files.pine64.org/os/PinePhone/Multi/p-boot-multi-2021-06-02.img.gz Direct download img.gz from pine64.org] (re-zipped from zstd to gzip)
** '''File name:''' p-boot-multi-2021-06-02.img.gz
** '''MD5:''' 2abdaafb01dd7519f678b5a7c6538493
** '''File Size:''' 6.8GB

Due to its size, download though torrent is suggested by the author on its main page.{{hint | '''Note about .zst archive file:'''

On Linux, you may install or compile <code>zstd</code>, and write the image to SD card by using <code>zstdcat</code> and <code>dd</code>. See the "Installation" section of its [https://xnux.eu/p-boot-demo/ web page] for command examples.

On Windows, you may use [https://github.com/mcmilk/7-Zip-zstd 7-zip-zstd], it provides different installation method in the README.md.Install and extract the .img file from the zst archive, and flash with tools like [https://sourceforge.net/projects/win32diskimager/ Win32 Disk Imager].}}Also see [[PinePhone Installation Instructions]].

'''username/password'''

All passwords, including root passwords, are <code>1111</code>.
sxmo username is <code>user</code>.

== Nemo Mobile ==
[[File:nemo_mobile.png|right|100px]]

Nemo Mobile is the open source build of Sailfish OS with a open source UI called [http://nemomobile.net/glacier-home/ Glacier] ([https://wiki.merproject.org/wiki/Nemo/Glacier Mer Wiki]), [http://nemomobile.net/pages/Hello_manjaro/ based on Manjaro].

* Website: [https://nemomobile.net/ Nemo Mobile UX team]
* [https://wiki.merproject.org/wiki/Nemo Mer Wiki page]

'''Download location'''

See the [https://nemomobile.net/installation/ installation page] on their website for the newest release and installation guides.

'''What works, what does not work'''

Development is now moving very fast after rebasing. For the current devel image, Wifi and Bluetooth works.

'''How to contribute and report defects'''

For the Nemo Mobile UX itself:
* GitHub issues: https://github.com/nemomobile-ux/main/issues

For hardware:
* GitHub issues: https://github.com/neochapay/nemo-device-dont_be_evil/issues

== NixOS ==
[[File:nixos.png|right|100px]]

NixOS support is handled through the Mobile NixOS project.

* Project home page: [https://mobile.nixos.org/ Mobile NixOS]
* PinePhone device page: [https://mobile.nixos.org/devices/pine64-pinephone.html Pine64 PinePhone — Mobile NixOS]
* GitHub: [https://github.com/NixOS/mobile-nixos NixOS/mobile-nixos]

There is no pre-built complete image.
For now users, are expected to follow the instructions in the [https://mobile.nixos.org/getting-started.html Getting Started page],
and [https://mobile.nixos.org/devices/pine64-pinephone.html Project's device page].

'''What works, what does not work'''

Currently, it boots, it's just as compatible as the Android-based devices are with Mobile NixOS.
It even supports a bit more since it can use WiFi.

Support for all of the hardware will be coming, this project is a breadth-first work, where the work spans multiple devices in parallel.

'''How to contribute and report defects'''

On [https://github.com/NixOS/mobile-nixos/issues the project's repository].
Please specify that you are using a PinePhone when reporting issues.
Details about contributions and donations are on the [https://nixos.org/nixos/community.html NixOS website].

== OpenMandriva Lx ==
[[File:Oma-logo-22042013_300pp.png|right|100px]]{{Hint| '''Note:''' This image is solely for testing purposes.}}OpenMandriva Lx with Plasma Mobile as UI.

'''Download location'''

The official image can be found [https://sourceforge.net/projects/openmandriva/files/release/4.2/RC/Pinephone/ at sourceforge.net].
See [https://www.openmandriva.org/en/news/article/openmandriva-lx-4-3-rc-available-for-testing here] for the offical announcement.

'''What works, what does not work'''

From the [https://www.openmandriva.org/en/news/article/openmandriva-lx-4-3-rc-available-for-testing 4.3 announcement],
in future updates (4.3 and later), "Phone calls are working, and we have rewritten the camera app to be far more useful".

== openSUSE ==
[[File:SLEM-OS-logo.png|right|100px]]

Our images use the same [https://en.opensuse.org/Portal:Tumbleweed openSUSE Tumbleweed] base as our desktop images,
except what needs to be changed for the PinePhone.
The images include <i>zypper</i> (RPM) as the default package manager,
and have access to virtually the same (open source) software as our desktop repositories,
thanks to the [https://en.opensuse.org/Portal:Factory Factory] ports.
Using [https://en.opensuse.org/SDB:DNF dnf] is possible, if preferred.

'''Download links'''

* [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz Phosh] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz.sha256 SHA-256] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz.sha256.asc SHA-256 Signature]
* [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz Plasma Mobile] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz.sha256 SHA-256] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz.sha256.asc SHA-256 Signature]

To verify the images you need to import [https://build.opensuse.org/projects/devel:ARM:Factory:Contrib:PinePhone/public_key our GPG key].
Keep on mind that the first boot may stay on black screen for about a minute - consequent boots should be faster.

You can find install instructions at [https://en.opensuse.org/HCL:PinePhone#Installing_openSUSE_in_a_Pinephone this section] in the openSUSE Wiki.

'''Username/Password'''

The login credentials are pine/1234 and root/linux.
Change (or disable) the root password once you are set up.

'''What works and what does not work'''

You can find all information about the releases of the project [https://gitlab.com/slem.os/slem.os/-/blob/master/CHANGELOG.md here].
Detailed information, tips and troubleshooting suggestions are also provided at [https://en.opensuse.org/HCL:PinePhone the openSUSE Wiki].
You will also find information in our wiki on how to report issues (Contributing section).

== postmarketOS ==
[[File:PostmarketOS-logo.png|right|100px]]

postmarketOS extends [https://www.alpinelinux.org/ Alpine Linux] to run on smartphones and other mobile devices.
It offers various user interfaces (Phosh, Plasma Mobile, Sxmo, Plasma Desktop, Gnome 3, Kodi, XFCE4, ...).

As of writing, official images are provided with Phosh, Plasma Mobile and Sxmo.
The official images come in two flavors, either as a test image to try out postmarketOS, or with the installer.

When using the installer images (recommended), it is possible to:
* encrypt the installation
* install from the SD card to eMMC

Power users may also create their own image with the distribution's install and development tool <code>pmbootstrap</code>.

Please read the detailed [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation installation instructions] in the wiki.

'''Download location'''

* [https://postmarketos.org/download/ Download page]
* [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation Flashing instructions]

'''Username/password'''

* Test images: user/147147
* When using the installer images or building an image with pmbootstrap, you set your own username and password.
** The Phosh and Plasma Mobile lock screens only support numeric keyboard, so you should '''only use numbers''' in your password.

'''What works, what does not work'''

See the [https://gitlab.com/postmarketOS/pmaports/-/issues?label_name%5B%5D=device-pine64-pinephone issue tracker].

'''How to contribute and report defects'''

[https://gitlab.com/postmarketOS/pmaports/-/issues?label_name%5B%5D=device-pine64-pinephone postmarketOS issue tracker] for PinePhone support.
See [https://wiki.postmarketos.org/wiki/Contributing postmarketOS wiki] for options to contribute.

== PureOS ==
[[File:Pureos.png|right|100px]]

{{Warning|This project is no longer under development and has been abandoned. Use [https://wiki.pine64.org/wiki/PinePhone_Software_Releases#Mobian Mobian] instead}}

{{Hint|There is no prebuilt image, you'll need a Linux environment and build the image yourself.}}

[https://www.pureos.net/ PureOS] is a user friendly, secure and freedom respecting GNU/Linux distribution based on Debian and GNOME developed by the Purism community.

* [https://tracker.pureos.net/w/ PureOS Wiki], no PinePhone page there
* Mobile-optimized apps list from the [https://tracker.pureos.net/w/pureos/mobile_optimized_apps/ Software Center in PureOS] and [https://tracker.pureos.net/w/pureos/3rd-party_mobile_optimized_apps/ 3rd party repos]
* [https://github.com/rufferson/pureos-pinephone current PinePhone PureOS repo], A script to convert Librem5 PureOS to PinePhone Pure-OS

'''Download location'''

Use [https://raw.githubusercontent.com/rufferson/pureos-pinephone/master/build_image.sh the convert script] to download and build the image from u-boot, PinePhone linux kernel and Librem5 PureOS.

Also see:
* [https://forums.puri.sm/t/successful-installation-of-pureos-on-pinephone/8741/12 Successful installation of PureOS on PinePhone - PureOS - Purism community]
* The PureOS section of [https://www.ruff.mobi/go/mobi/pine.html PinePhone page] on ruff.mobi
* An [https://gitlab.com/a-wai/debos-pinephone archived repo] for PureOS on PinePhone
* A [https://mozzwald.com/pp/ file list] with [https://mozzwald.com/pp/pureos-pinephone-build-instructions.txt pureos pinephone build instructions] on mozzwald.com

== Sailfish OS ==
[[File:Sailfish_logo.png|right|100px]]

[https://sailfishos.org/ Sailfish OS] is a Linux-based operating system based on open source projects such as [https://wiki.merproject.org/wiki/Main_Page Mer], and a closed source UI based on [https://sailfishos.org/wiki/Lipstick Lipstick].

* [https://wiki.merproject.org/wiki/Adaptations/PinePhone64 PinePhone Wiki Page] on Mer Wiki, for both Nemo Mobile and Sailfish OS.
* [https://gitlab.com/pinephone-sailfish-os/linux-kernel/ Linux kernel config repo]
* [https://gitlab.com/sailfishos-porters-ci/dont_be_evil-ci/ Sailfish OS repo]

'''Download location'''

'''Flashing script'''

The Sailfish OS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].

The script downloads the image and bootloader from the CI, extracts everything and burns it onto the SD card.
Note: The script will format and erase the SD card!

Instructions:
# Download the flashing script
# Insert a microSD card in your device
# Make the script executable: <code>chmod +x flash-it.sh</code>
# Verify that you have the <code>bsdtar</code> package installed
# Execute it: <code>./flash-it.sh</code>
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).

* When asked where to flash, type 'raw' and it will build the image on your computer. Otherwise define the path /dev/.... to flash to card or internal emmc.

'''username/password'''

Set PIN on initialization.

* Sometimes the first run stalls before the tutorial. Reboot and it will start from setting the security pin.
* The homescreen may be locked unless you boot with a sim card inserted. An old expired sim will do. '''If you do not have a SIM card on hands, do NOT set a security code on first boot.'''
* When a screen with a loading circle is displayed, just left/right swipe it away.
* If you're not familiar with Sailfish OS, pay attention to the tutorial - the interface works great, but is not immediately obvious. If you are familiar with it, you can skip the tutorial by touching all 4 corners starting top left.

'''What works, what does not work'''

See the [https://wiki.merproject.org/wiki/Adaptations/PinePhone64#Hardware_Support Hardware Support section] on the Mer Wiki's PinePhone Page.

There is a limited selection of apps available from the Jolla store, the vast majority are hosted on openrepos.net. If the Storeman app for openrepos is not preinstalled, download the RPM and click to install.

'''How to contribute and report defects'''

See the [https://wiki.merproject.org/wiki/Adaptations/PinePhone64#Installation Installation section] on the Mer Wiki's PinePhone Page for compile, build and development.

Git repo links are at the top of this OS section. other repos that may be helpful:

* [https://github.com/sailfish-on-dontbeevil GitHub project page]
* [https://github.com/sailfish-on-dontbeevil/flash-it the repo of the flash-it.sh flashing script]
* [https://build.merproject.org/project/show/nemo:devel:hw:pine:dontbeevil Mer Open Build Service page] ([https://forum.sailfishos.org/t/changes-needed-to-merge-the-project-names-to-sailfish-os/1672 Mer is being assimilated into Sailfish OS] and [https://forum.sailfishos.org/t/obs-shut-down-and-next-steps/1814 OBS is shutting down], also see [https://specs.openstack.org/openstack/fuel-specs/specs/7.0/replace-obs.html OpenStack is replacing OBS with another build system based on Jenkins], if it's related, even OBS come back under Sailfish OS, it will be different.)

See the [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues Sailfish OS wiki] for links to their forum, as well as info required when reporting an issue. See the [https://sailfishos.org/wiki/SailfishOS Sailfish OS wiki main page] for options to contribute to Sailfish OS.

'''Notes'''

OTA is supported: <code>zypper refresh && zypper update</code> as root (<code>devel-su</code> to get root access). Things that need reflash are bootloader specific at the moment. If improvements like [[Crust]] or changes of partition layout are added, then you need to reflash.

== SkiffOS ==
[[File:SkiffOS-Icon-1.png|right|100px]]

Minimal in-memory cross-compiled OS optimized for hosting multiple in parallel Docker containers.

Provides the reliability of firmware with the ease-of-use of package managers.

Upgrade over-the-air via a simple rsync script, or copying 3 files.

Uses the [http://buildroot.org Buildroot] cross-compilation tool for support for all Pine64 boards.

Use configuration packages to configure distro:

{| class="wikitable"
! core/pinephone_neon || KDE Neon via Ubuntu repositories
|-
! core/pinephone_nixos || Nixos Mobile
|-
! core/pinephone_gentoo || Gentoo with Link-time Optimization & KDE Mobile or Phosh
|-
! core/pinephone_ubports || Ubuntu Ports for PinePhone
|-
! core/pinephone_manjaro_kde || Manjaro for PinePhone: KDE variant
|-
! core/pinephone_manjaro_phosh || Manjaro for PinePhone: Phosh variant
|-
! core/pinephone_manjaro_lomiri || Manjaro for PinePhone: Lomiri variant
|}

The boot-up OS is upgraded independently from the containers.

'''Download location'''

The repository and instructions can be found [https://github.com/skiffos/SkiffOS/tree/master/configs/pine64/phone here].

== Sxmo ==

A collection of Suckless programs to create a mobile UI. Based on postmarketOS.

'''Download location'''

Sxmo images can be found [https://images.postmarketos.org/bpo/ here] (in the ''/pine64-pinephone/sxmo/'' sections respectively).

'''username/password'''

user/147147

'''How to contribute and report defects'''

Contributing information is listed [https://git.sr.ht/~mil/sxmo-docs/tree/master/CONTRIBUTING.md here].

== Ubuntu Touch ==
[[File:Ubports-logo.png|right|100px]]

A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.

Ubuntu touch is a mobile version of Ubuntu developed by the UBports community.
Installation instructions can be found on
[https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone the UBports PinePhone project].
There is also a [https://github.com/goddard/pinephone/ script] to download the latest image and flash to your PinePhone.
In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://devices.ubuntu-touch.io/installer UBports installer] GUI tool.

'''Download location'''

[https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone UBports PinePhone project]

'''username/password'''

Set up during boot

'''What works, what does not work'''

Scroll down to the bottom of [https://gitlab.com/ubports/community-ports/pinephone this page].

'''How to contribute and report defects'''

See [https://gitlab.com/ubports/community-ports/pinephone UBports gitlab page].
See [https://ubports.com/foundation/sponsors UBports website] for how to donate.

= Tools =

There are software tools, that can be booted on the PinePhone.

== JumpDrive ==

JumpDrive can be used to flash the eMMC (and the microSD card), see [[PinePhone Installation Instructions#Using JumpDrive]].

See https://github.com/dreemurrs-embedded/Jumpdrive/releases for the latest image.
Make sure to download the "PinePhone" image and to unpack the archive before flashing.

= Factory Test OS =

{{Hint|'''Note:''' The magnetometer test will fail on the new Beta Edition, as the factory image wasn't updated for it yet.}}

On the Braveheart model, there was a postmarketOS based basic Factory Test OS pre-installed on the eMMC.
The developer Martijn Braam from postmarketOS has improved the functionality of the image considerably later.
Since the 20200501 version, it is able to test all the hardware.
It also includes functionality to install a new OS to the eMMC when using with an test image that includes that OS image.
The downloadable image just does the hardware tests.
Do not flash eMMC to test your device, just dd it to microSD and test from there.
New versions are distributed as part of the postmarketOS distribution.

Links:
* [https://images.postmarketos.org/pinephone/ Software Images] (download the latest one named like pine-pinephone-yyyyMMdd-factorytestX.img.xz)
* [https://gitlab.com/MartijnBraam/factorytest Git repo]
* [https://gitlab.com/MartijnBraam/factorytest/-/blob/master/README.rst Documentation]

== Factory-loaded OS builds ==

These are different operating system builds that was preloaded in the factory with testing utility.

Download the build, extract the image and dd it to a 8 GB or larger microSD card, then insert it into the PinePhone.
After power up or reboot, you may perform and complete the test routine, or apply the build from microSD card to eMMC.

All the download links below are direct download from pine64.org.

<div style="overflow: auto;">
{| class="wikitable" style="white-space: nowrap"
! OS
! Download Link
! File Size
! MD5
|-
| Beta Edition
| [https://files.pine64.org/os/PinePhone/BetaEdition/pine64-pinephone-plamo-beta-factorytest.img.xz pine64-pinephone-plamo-beta-factorytest.img.xz]
| 1.78GB
| <code>f16bce93504a52217540ac886863a418</code>
|-
| Mobian
| [https://files.pine64.org/os/PinePhone/Mobian/pine64-pinephone-20201207-factorytest-mobian.img.xz pine64-pinephone-20201207-factorytest-mobian.img.xz]
| 1.41GB
| <code>015be381ff4e650a7fca6d4eaa90d63d</code>
|-
| KDE
| [https://files.pine64.org/os/PinePhone/KDE/pine64-pinephone-20201208-factorytest-kde.img.xz pine64-pinephone-20201208-factorytest-kde.img.xz]
| 2.28GB
| <code>32979ff17b5ec4d358ce99f1aff0c77c</code>
|-
| Manjaro
| [https://files.pine64.org/os/PinePhone/Manjaro/pine64-pinephone-20201013-manjaro-stable-20201018-factory56.img.xz pine64-pinephone-20201013-manjaro-stable-20201018-factory56.img.xz]
| 1.04GB
| <code>4edfd4dceaefdd32a3417c1727161c29</code>
|-
| postmarketOS
| [https://files.pine64.org/os/PinePhone/PostMarketOS/pine64-pinephone-20200726-phosh-v20.05-factory.img.xz pine64-pinephone-20200726-phosh-v20.05-factory.img.xz]
| 517MB
| <code>244093be2f6d728fcbd1d29114607727</code>
|-
| Ubuntu Touch
| [https://files.pine64.org/os/PinePhone/UBPorts/PinePhone-flasher-ubuntu-7b.img.gz PinePhone-flasher-ubuntu-7b.img.gz]
| 1.05GB
| <code>2d7f5271e7a281db8f1b1219bedbe131</code>
|}
</div>

= Installing other ARM64 distributions =

{{Warning|Distributions not on this page may not even boot after you follow this section. In the best case, they will be barely usable.
This is more for fun, or if you would like to port a new distribution to the PinePhone.}}

{{Hint|'''Note:''' This section uses megi's kernel releases, and not the official ones from Pine64. While it is possible to use the official (and in the future, mainline) kernel, megi provides binary releases, which makes it very easy.}}

General steps:

# Create a boot partition (from 4 MB to about 252 MB) and a root partition (from the end of boot to the end of the card) filesystem on the SD card.
# Format the boot partition with vfat, and the root partition with a supported filesystem like ext4 or f2fs.
# Extract the root filesystem from your distribution's ARM image into the root filesystem on the SD card. Do not copy the partition, copy the files instead (in archive mode, like <code>rsync -ar</code>).
# Edit <code>/etc/fstab</code> to match your partitions.
# Grab megi's kernel from https://xff.cz/kernels/, Follow the instructions in the [https://xff.cz/kernels/README README], which involves copying the kernel modules into the SD card rootfs, and writing u-boot and the bootloader.

If you would like to see examples or specific commands for how to complete these steps, see:
* [https://github.com/nikhiljha/pp-fedora-sdsetup an example for Fedora], current unofficial [#Fedora] release
* [https://xnux.eu/howtos/install-arch-linux-arm.html an example for Arch Linux] by megi

= Other Resources =
Community
* [[Main_Page#Community_and_Support|Links to the community services]]

Hardware information
* [[PinePhone|General PinePhone hardware info]] in this Pine64 wiki
* Details specific to the Braveheart Edition: [[PinePhone_v1.1_-_Braveheart|PinePhone 1.1 Braveheart hardware details]]
* Details specific to the Community Edition: [[PinePhone_v1.2|PinePhone 1.2 hardware details]]
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here] and the preceding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here]

Other software information
* [https://linux-sunxi.org/Main_Page sunxi community wiki]
* [https://xnux.eu/devices/pine64-pinephone.html megi's feature/driver support matrix]
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)] see demonstration [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube]
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]

Other
* [https://pine64.com/?post_type=product Pine64 shop]
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on Linux distributions and desktop environments on mobile devices]
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing microSD cards]

[[Category:PinePhone]]

PinePhone Software Releases

2021-09-22T08:29:17Z

RainSlide: /* Manjaro ARM */ Remove empty lines

This page contains a list of all available OS releases for the [[PinePhone]], as well as links to other resources.

See [[PinePhone Installation Instructions]] on how to install the operating systems.<br>
However, if your phone came preloaded with software, Please see [[PinePhone Updating Instructions]].

{{Hint| '''Note:''' Some releases may not have a good setup for the backlight at low brightness.
If configured too low, the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.}}

= Software Releases =

This is a list of OSes that specifically support the PinePhone.
Since PinePhone support is included in Mainline Linux, in principle, any ARM Linux OS can be used if possible required patches are included.

== Arch Linux ARM ==
[[File:Archlinux-logo.png|right|100px]]

(Unofficial) Arch Linux ARM with choice of Phosh UI, Plasma Mobile, or barebones.
Currently being maintained by the [https://danctnix.org/ DanctNIX] community (GitHub: [https://github.com/DanctNIX/danctnix danctnix], [https://github.com/dreemurrs-embedded dreemurrs-embedded]).

* GitHub: [https://github.com/dreemurrs-embedded/Pine64-Arch dreemurrs-embedded/Pine64-Arch]

'''Download location'''

Get the latest image here: https://github.com/dreemurrs-embedded/Pine64-Arch/releases

'''username/password'''

{| class="wikitable"
! Default user || <code>alarm/123456</code>
! root || <code>root/root</code>
|}

'''What works, what does not work'''

Most of the things now works, there are some minor issues with [[Crust]].

'''How to contribute and report defects'''

You may find the Discord, Matrix and Telegram of DanctNIX community at [https://github.com/DanctNIX/danctnix/blob/master/README.md#channel-list the Channel list section of DanctNIX/README.md].

Feel free to send us [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls pull requests] and report [https://github.com/dreemurrs-embedded/Pine64-Arch/issues issues] on [https://github.com/dreemurrs-embedded/Pine64-Arch GitHub].

== ExpidusOS ==

A fork of [https://voidlinux.org Void Linux] with a custom fork of XFCE called [https://github.com/ExpidusOS/genesis Gensis] as the default desktop environment, developed by [https://midstall.com/ Midstall Software].

* [https://expidusos.com ExpidusOS official website]
* [https://wiki.expidusos.com/index.php/Main_Page ExpidusOS Wiki]
* [https://discord.gg/GVfBF2w Midstall Software Discord server]
* GitHub: [https://github.com/ExpidusOS ExpidusOS]

'''Download location'''

Check the [https://expidusos.com/download download page] for that latest version, or the [https://build.expidusos.com/ image file list] for all versions, look for the file name that starts with "pinephone".

'''username/password'''

expidus/expidus

'''What works, what does not work'''

The ExpidusOS Wiki has a page detailing [https://wiki.expidusos.com/index.php/Device:PinePhone supported features].

'''How to contribute and report defects'''

Join the [https://discord.gg/GVfBF2w Discord server] or corresponding repo at GitHub ([https://github.com/orgs/ExpidusOS/repositories repo list]).

== Fedora ==
[[File:Fedora-logo.png|right|100px]]

An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and [https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/ some additional packages] to tie it all together.
It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.

* Forum discussion: [https://forum.pine64.org/showthread.php?tid=9347 Fedora + Phosh for PinePhone]
* GitHub: [https://github.com/nikhiljha/pp-fedora-sdsetup nikhiljha/pp-fedora-sdsetup]

'''Download location'''

* [https://github.com/nikhiljha/pp-fedora-sdsetup/releases Flashable images]
* [https://github.com/nikhiljha/pp-fedora-sdsetup Build scripts]
* [https://copr.fedorainfracloud.org/coprs/njha/mobile/ Packages (Fedora COPR)]

There is also an FTP server with a full Fedora 34 workstation build with phosh: ftp://pine.warpspeed.dk/nightly/pinephone/ (Mount this with something like Nautilus)

'''username/password'''

pine/123456

'''What works, what does not work'''

WiFi, Bluetooth, SMS, Data, Calls all work!

There are still a few bugs though, and [https://xnux.eu/devices/pine64-pinephone.html#toc-feature-driver-support-matrix some features don't have driver support yet] on any PinePhone distribution.

'''How to contribute and report defects'''

Please send your bug reports to [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker].
Be sure to include logs if applicable!
Send us pull requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/pulls Github].

== Gentoo ==
[[File:GentooLogo.png|right|100px]]{{hint|Please consider cross-compiling the software on the computer.
Long compilation times and heat production can lead to a reduced lifespan of the phone.}}There are unofficial Gentoo overlays with ebuilds for the PinePhone.
There are no images - you'll be building it yourself, picking which kernel, bootloader and desktop environment you want to use.
You will be using the arm64 version of Gentoo.

'''Documentation'''

* https://stealthgun.tweakblogs.net/blog/19336/gentoo-on-a-pinephone
* https://wiki.gentoo.org/wiki/User:Dr41nU/PinePhone
* https://wiki.gentoo.org/wiki/PinePhone (incomplete)

'''Overlay locations'''

* https://gitlab.com/bingch/gentoo-overlay
* https://github.com/stealthgun/gjdwebserver-overlay

== GloDroid ==

{{Hint|There can be large intervals between release update, so available images may be outdated and do not reflect the state of the current developments.}}A fully open source port of Android to the PinePhone.

* GitHub: [https://github.com/GloDroid GloDroid]

'''Download location'''

https://github.com/GloDroid/glodroid_manifest/releases (last release at 2021-05-20)

'''What works, what does not work'''

Works: WiFi, screen dimming, touchscreen and charging work.
Don't work: Bluetooth, Telephony, GPS, Sound

== LuneOS ==
[[File:WebOS-Ports-logo.png|right|100px]]

LuneOS is a open source mobile operating system based on [https://www.webosose.org/ webOS Open Source Edition]([https://github.com/webosose GitHub], previously known as [https://github.com/openwebos Open webOS]) by LG, comes with [https://webos-ports.org/wiki/Luna_Next Luna Next] UI, currently developed by the WebOS Ports community.

* [https://www.webos-ports.org/wiki/Main_Page WebOS Ports Wiki]
* [https://webos-ports.org/wiki/Pinephone_Info WebOS-Ports Wiki's Pinephone page]
* GitHub: [https://github.com/webOS-ports WebOS Ports]

'''Download location'''

* [http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]

It is recommended to use ''bmaptool'', which is faster than dd, and can decompress archived image files on-the-fly.

Syntax is:

bmaptool copy [from] [to]

For example:

bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-140.rootfs.wic.gz /dev/mmcblk0

.wic file can be treated as .img file when flashing. You may rename .wic file to .img when using GUI tools that require file extension to be .img.

== Maemo Leste ==
[[File:Maemoleste-logo.png|right|100px]]

[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices,
originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it.
The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices.

The new version Maemo 8 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel.
The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK].
The current version is Devuan Beowulf (Debian Buster) and has simultaneous support for both Devuan and Debian.

In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository].
To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's build]).
Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.

* [https://maemo-leste.github.io/ Maemo Leste website]
* [https://leste.maemo.org/Main_Page Maemo Leste Wiki]
** [https://leste.maemo.org/PinePhone PinePhone wiki page]
** [https://leste.maemo.org/Leste_FAQ Maemo Leste FAQ]
* GitHub: [https://github.com/maemo-leste maemo-leste]
* Twitter: [https://twitter.com/maemoleste @maemoleste]

'''Download location'''

[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds]. There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].

'''username/password'''

root/toor

You may use <code>sudo</code> directly.

'''What works, what does not work'''

For current status and workarounds, please read their [https://leste.maemo.org/PinePhone PinePhone wiki page].

'''How to contribute and report defects'''

Most discussion occurs at [ircs://irc.libera.chat:6697/#maemo-leste <code>#maemo-leste</code> on <code>irc.libera.chat</code>].
The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback.

All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki.

Submit [https://github.com/maemo-leste/bugtracker/issues bug reports] on github.
To track known issues, you may use these search terms:
[https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone],
[https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64].

Learn about
[https://leste.maemo.org/Development development],
[https://leste.maemo.org/Development/Porting_Packages porting packages],
[https://leste.maemo.org/Development/Building_Packages building packages],
[https://leste.maemo.org/Development/Tasks todo list],
and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian].
Some tasks have funding available.

== Manjaro ARM ==
[[File:Manjaro-logo.svg|right|100px]]

Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.

'''Download location'''

* Phosh: [https://github.com/manjaro-pinephone/phosh Stable] / [https://github.com/manjaro-pinephone/phosh-dev Dev]
* Plasma Mobile: [https://github.com/manjaro-pinephone/plasma-mobile Stable] / [https://github.com/manjaro-pinephone/plasma-mobile-dev Dev]
* Lomiri: [https://github.com/manjaro-pinephone/lomiri-dev Dev] (No longer maintained)

'''username/password'''

{| class="wikitable"
! Default user || <code>manjaro/123456</code>
! root || <code>root/root</code>
|}

'''What works, what does not work'''{{Hint| '''Note:''' At the first boot, the Phosh image will be loaded at a TTY login prompt for multiple minutes.}}See Manjaro's release announcements on their forum.
Recent ones:
[https://forum.manjaro.org/t/manjaro-arm-beta12-with-phosh-pinephone/73099 Phosh],
[https://forum.manjaro.org/t/manjaro-arm-beta5-with-plasma-mobile-pinephone/69318 Plasma] and
[https://forum.manjaro.org/t/manjaro-arm-alpha3-with-lomiri-pinephone/49923 Lomiri].

'''How to contribute and report defects'''

See the end of the [https://forum.manjaro.org/t/manjaro-arm-beta7-with-phosh-pinephone/58901 announcement].

== Mobian ==
[[File:Debian-logo.png|right|100px]]

An unofficial [https://www.debian.org Debian] build for ARM64 running with Phosh (developed by Purism, uses Wayland instead of Xorg).
The base system is pure Debian, with only the GUI applications and a few others (ModemManager, WiFi chip firmware) being built from modified sources (as well as the kernel and u-boot).
Current version is Debian Bookworm.

'''Download location'''

[https://images.mobian-project.org/pinephone/nightly/ Nightly] /
[https://images.mobian-project.org/pinephone/installer/ Installer] /
[https://images.mobian-project.org/pinephone/ Stable]

Extract the image before installing:

$ gzip -d Downloads/mobian-pinephone-*.img.gz

See the [https://wiki.mobian-project.org/doku.php?id=install project page] for specific installation instructions.

'''username/password'''

mobian/1234

'''What works, what does not work'''

See [https://gitlab.com/mobian1/mobian-recipes/-/blob/master/README.md the project's README file] or [https://wiki.mobian-project.org/doku.php?id=pinephone the wiki] for most up to date status.

Check [https://gitlab.com/groups/mobian1/-/issues bug tracker] for known issues. Questions? Ask on our [https://forum.pine64.org/showthread.php?tid=9016 thread].

'''How to contribute and report defects'''

It is recommended that you log your bug reports in [https://gitlab.com/mobian1/issues the project's issue tracker].
As a general rule, issues with third-party apps (even the default ones) should be reported upstream.
A Mobian issue would be related to getting the hardware to work on the PinePhone,
but if unsure where the issue should be reported just open a ticket or ask.
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/mobian1 Gitlab].

'''Notes'''

See [https://wiki.mobian-project.org/doku.php?id=start the wiki] for additional information regarding screen resolution, USB networking, WiFi hotspot, Chatty and the repository.

== Multi-distro demo image ==

{{Warning | This is an demo image for testing different OSes before installing a regular image. It is highly discouraged attempting to use the image productively. The kernel is shared across the different OSes and is not being updated.}}

This image allow users to try many of the above Linux distributions easily, without having to figure out how to flash them individually and juggle with many microSD cards. Also called megi's 15-in-1 multi boot image.

* Main page: https://xnux.eu/p-boot-demo/
* Git repo: https://megous.com/git/pinephone-multi-boot/
* Forum discussion: [https://forum.pine64.org/showthread.php?tid=11347 UPDATED (June 2021): 17-distro multi-boot image for Pinephone (incl. 3GiB variant)]

'''Update 2021-06-02, using megi's kernel 5.13-rc4'''

DD image to SD card and boot. This image is for 16GiB or larger SD cards, also works if flashed to eMMC.

This is also a good build for charging depleted battery. Just boot up this build with power supply connected, keep the PinePhone charging for 3 hours at power down stage.

For more info on this build, please visit its entry the "News" section of its [https://xnux.eu/p-boot-demo/ web page].

* [http://dl.xnux.eu/p-boot-multi-2021-06-02.torrent Download torrent file from author's website]
* [http://dl.xnux.eu/p-boot-multi-2021-06-02/ Download img.zst from author's website] (speed limited to 512KiB/s)
* [http://mirror.uxes.cz/dl.xnux.eu/ Download torrent and img.zst from discord user uxes' mirror]
** '''File name:''' multi.img.zst
** '''SHA-256:''' <span style="word-break: break-all">9b099cdfece3ba862348ca32af6c51a41a1d161b1d897f9928ae8be3c824a0b6</span>
** '''File Size:''' 6.57GiB

* [https://files.pine64.org/os/PinePhone/Multi/p-boot-multi-2021-06-02.img.gz Direct download img.gz from pine64.org] (re-zipped from zstd to gzip)
** '''File name:''' p-boot-multi-2021-06-02.img.gz
** '''MD5:''' 2abdaafb01dd7519f678b5a7c6538493
** '''File Size:''' 6.8GB

Due to its size, download though torrent is suggested by the author on its main page.

{{hint | '''Note about .zst archive file:'''

On Linux, you may install or compile <code>zstd</code>, and write the image to SD card by using <code>zstdcat</code> and <code>dd</code>. See the "Installation" section of its [https://xnux.eu/p-boot-demo/ web page] for command examples.

On Windows, you may use [https://github.com/mcmilk/7-Zip-zstd 7-zip-zstd], it provides different installation method in the README.md. Install and extract the .img file from the zst archive, and flash with tools like [https://sourceforge.net/projects/win32diskimager/ Win32 Disk Imager].

Also see [[PinePhone Installation Instructions]].
}}

'''username/password'''

All passwords, including root passwords, are <code>1111</code>.
sxmo username is <code>user</code>.

== Nemo Mobile ==
[[File:nemo_mobile.png|right|100px]]

Nemo Mobile is the open source build of Sailfish OS with a open source UI called [http://nemomobile.net/glacier-home/ Glacier] ([https://wiki.merproject.org/wiki/Nemo/Glacier Mer Wiki]), [http://nemomobile.net/pages/Hello_manjaro/ based on Manjaro].

* Website: [https://nemomobile.net/ Nemo Mobile UX team]
* [https://wiki.merproject.org/wiki/Nemo Mer Wiki page]

'''Download location'''

See the [https://nemomobile.net/installation/ installation page] on their website for the newest release and installation guides.

'''What works, what does not work'''

Development is now moving very fast after rebasing. For the current devel image, Wifi and Bluetooth works.

'''How to contribute and report defects'''

For the Nemo Mobile UX itself:
* GitHub issues: https://github.com/nemomobile-ux/main/issues

For hardware:
* GitHub issues: https://github.com/neochapay/nemo-device-dont_be_evil/issues

== NixOS ==
[[File:nixos.png|right|100px]]

NixOS support is handled through the Mobile NixOS project.

* Project home page: [https://mobile.nixos.org/ Mobile NixOS]
* PinePhone device page: [https://mobile.nixos.org/devices/pine64-pinephone.html Pine64 PinePhone — Mobile NixOS]
* GitHub: [https://github.com/NixOS/mobile-nixos NixOS/mobile-nixos]

There is no pre-built complete image.
For now users, are expected to follow the instructions in the [https://mobile.nixos.org/getting-started.html Getting Started page],
and [https://mobile.nixos.org/devices/pine64-pinephone.html Project's device page].

'''What works, what does not work'''

Currently, it boots, it's just as compatible as the Android-based devices are with Mobile NixOS.
It even supports a bit more since it can use WiFi.

Support for all of the hardware will be coming, this project is a breadth-first work, where the work spans multiple devices in parallel.

'''How to contribute and report defects'''

On [https://github.com/NixOS/mobile-nixos/issues the project's repository].
Please specify that you are using a PinePhone when reporting issues.
Details about contributions and donations are on the [https://nixos.org/nixos/community.html NixOS website].

== OpenMandriva Lx ==
[[File:Oma-logo-22042013_300pp.png|right|100px]]{{Hint| '''Note:''' This image is solely for testing purposes.}}OpenMandriva Lx with Plasma Mobile as UI.

'''Download location'''

The official image can be found [https://sourceforge.net/projects/openmandriva/files/release/4.2/RC/Pinephone/ at sourceforge.net].
See [https://www.openmandriva.org/en/news/article/openmandriva-lx-4-3-rc-available-for-testing here] for the offical announcement.

'''What works, what does not work'''

From the [https://www.openmandriva.org/en/news/article/openmandriva-lx-4-3-rc-available-for-testing 4.3 announcement],
in future updates (4.3 and later), "Phone calls are working, and we have rewritten the camera app to be far more useful".

== openSUSE ==
[[File:SLEM-OS-logo.png|right|100px]]

Our images use the same [https://en.opensuse.org/Portal:Tumbleweed openSUSE Tumbleweed] base as our desktop images,
except what needs to be changed for the PinePhone.
The images include <i>zypper</i> (RPM) as the default package manager,
and have access to virtually the same (open source) software as our desktop repositories,
thanks to the [https://en.opensuse.org/Portal:Factory Factory] ports.
Using [https://en.opensuse.org/SDB:DNF dnf] is possible, if preferred.

'''Download links'''

* [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz Phosh] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz.sha256 SHA-256] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz.sha256.asc SHA-256 Signature]
* [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz Plasma Mobile] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz.sha256 SHA-256] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz.sha256.asc SHA-256 Signature]

To verify the images you need to import [https://build.opensuse.org/projects/devel:ARM:Factory:Contrib:PinePhone/public_key our GPG key].
Keep on mind that the first boot may stay on black screen for about a minute - consequent boots should be faster.

You can find install instructions at [https://en.opensuse.org/HCL:PinePhone#Installing_openSUSE_in_a_Pinephone this section] in the openSUSE Wiki.

'''Username/Password'''

The login credentials are pine/1234 and root/linux.
Change (or disable) the root password once you are set up.

'''What works and what does not work'''

You can find all information about the releases of the project [https://gitlab.com/slem.os/slem.os/-/blob/master/CHANGELOG.md here].
Detailed information, tips and troubleshooting suggestions are also provided at [https://en.opensuse.org/HCL:PinePhone the openSUSE Wiki].
You will also find information in our wiki on how to report issues (Contributing section).

== postmarketOS ==
[[File:PostmarketOS-logo.png|right|100px]]

postmarketOS extends [https://www.alpinelinux.org/ Alpine Linux] to run on smartphones and other mobile devices.
It offers various user interfaces (Phosh, Plasma Mobile, Sxmo, Plasma Desktop, Gnome 3, Kodi, XFCE4, ...).

As of writing, official images are provided with Phosh, Plasma Mobile and Sxmo.
The official images come in two flavors, either as a test image to try out postmarketOS, or with the installer.

When using the installer images (recommended), it is possible to:
* encrypt the installation
* install from the SD card to eMMC

Power users may also create their own image with the distribution's install and development tool <code>pmbootstrap</code>.

Please read the detailed [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation installation instructions] in the wiki.

'''Download location'''

* [https://postmarketos.org/download/ Download page]
* [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation Flashing instructions]

'''Username/password'''

* Test images: user/147147
* When using the installer images or building an image with pmbootstrap, you set your own username and password.
** The Phosh and Plasma Mobile lock screens only support numeric keyboard, so you should '''only use numbers''' in your password.

'''What works, what does not work'''

See the [https://gitlab.com/postmarketOS/pmaports/-/issues?label_name%5B%5D=device-pine64-pinephone issue tracker].

'''How to contribute and report defects'''

[https://gitlab.com/postmarketOS/pmaports/-/issues?label_name%5B%5D=device-pine64-pinephone postmarketOS issue tracker] for PinePhone support.
See [https://wiki.postmarketos.org/wiki/Contributing postmarketOS wiki] for options to contribute.

== PureOS ==
[[File:Pureos.png|right|100px]]

{{Warning|This project is no longer under development and has been abandoned. Use [https://wiki.pine64.org/wiki/PinePhone_Software_Releases#Mobian Mobian] instead}}

{{Hint|There is no prebuilt image, you'll need a Linux environment and build the image yourself.}}

[https://www.pureos.net/ PureOS] is a user friendly, secure and freedom respecting GNU/Linux distribution based on Debian and GNOME developed by the Purism community.

* [https://tracker.pureos.net/w/ PureOS Wiki], no PinePhone page there
* Mobile-optimized apps list from the [https://tracker.pureos.net/w/pureos/mobile_optimized_apps/ Software Center in PureOS] and [https://tracker.pureos.net/w/pureos/3rd-party_mobile_optimized_apps/ 3rd party repos]
* [https://github.com/rufferson/pureos-pinephone current PinePhone PureOS repo], A script to convert Librem5 PureOS to PinePhone Pure-OS

'''Download location'''

Use [https://raw.githubusercontent.com/rufferson/pureos-pinephone/master/build_image.sh the convert script] to download and build the image from u-boot, PinePhone linux kernel and Librem5 PureOS.

Also see:
* [https://forums.puri.sm/t/successful-installation-of-pureos-on-pinephone/8741/12 Successful installation of PureOS on PinePhone - PureOS - Purism community]
* The PureOS section of [https://www.ruff.mobi/go/mobi/pine.html PinePhone page] on ruff.mobi
* An [https://gitlab.com/a-wai/debos-pinephone archived repo] for PureOS on PinePhone
* A [https://mozzwald.com/pp/ file list] with [https://mozzwald.com/pp/pureos-pinephone-build-instructions.txt pureos pinephone build instructions] on mozzwald.com

== Sailfish OS ==
[[File:Sailfish_logo.png|right|100px]]

[https://sailfishos.org/ Sailfish OS] is a Linux-based operating system based on open source projects such as [https://wiki.merproject.org/wiki/Main_Page Mer], and a closed source UI based on [https://sailfishos.org/wiki/Lipstick Lipstick].

* [https://wiki.merproject.org/wiki/Adaptations/PinePhone64 PinePhone Wiki Page] on Mer Wiki, for both Nemo Mobile and Sailfish OS.
* [https://gitlab.com/pinephone-sailfish-os/linux-kernel/ Linux kernel config repo]
* [https://gitlab.com/sailfishos-porters-ci/dont_be_evil-ci/ Sailfish OS repo]

'''Download location'''

'''Flashing script'''

The Sailfish OS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].

The script downloads the image and bootloader from the CI, extracts everything and burns it onto the SD card.
Note: The script will format and erase the SD card!

Instructions:
# Download the flashing script
# Insert a microSD card in your device
# Make the script executable: <code>chmod +x flash-it.sh</code>
# Verify that you have the <code>bsdtar</code> package installed
# Execute it: <code>./flash-it.sh</code>
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).

* When asked where to flash, type 'raw' and it will build the image on your computer. Otherwise define the path /dev/.... to flash to card or internal emmc.

'''username/password'''

Set PIN on initialization.

* Sometimes the first run stalls before the tutorial. Reboot and it will start from setting the security pin.
* The homescreen may be locked unless you boot with a sim card inserted. An old expired sim will do. '''If you do not have a SIM card on hands, do NOT set a security code on first boot.'''
* When a screen with a loading circle is displayed, just left/right swipe it away.
* If you're not familiar with Sailfish OS, pay attention to the tutorial - the interface works great, but is not immediately obvious. If you are familiar with it, you can skip the tutorial by touching all 4 corners starting top left.

'''What works, what does not work'''

See the [https://wiki.merproject.org/wiki/Adaptations/PinePhone64#Hardware_Support Hardware Support section] on the Mer Wiki's PinePhone Page.

There is a limited selection of apps available from the Jolla store, the vast majority are hosted on openrepos.net. If the Storeman app for openrepos is not preinstalled, download the RPM and click to install.

'''How to contribute and report defects'''

See the [https://wiki.merproject.org/wiki/Adaptations/PinePhone64#Installation Installation section] on the Mer Wiki's PinePhone Page for compile, build and development.

Git repo links are at the top of this OS section. other repos that may be helpful:

* [https://github.com/sailfish-on-dontbeevil GitHub project page]
* [https://github.com/sailfish-on-dontbeevil/flash-it the repo of the flash-it.sh flashing script]
* [https://build.merproject.org/project/show/nemo:devel:hw:pine:dontbeevil Mer Open Build Service page] ([https://forum.sailfishos.org/t/changes-needed-to-merge-the-project-names-to-sailfish-os/1672 Mer is being assimilated into Sailfish OS] and [https://forum.sailfishos.org/t/obs-shut-down-and-next-steps/1814 OBS is shutting down], also see [https://specs.openstack.org/openstack/fuel-specs/specs/7.0/replace-obs.html OpenStack is replacing OBS with another build system based on Jenkins], if it's related, even OBS come back under Sailfish OS, it will be different.)

See the [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues Sailfish OS wiki] for links to their forum, as well as info required when reporting an issue. See the [https://sailfishos.org/wiki/SailfishOS Sailfish OS wiki main page] for options to contribute to Sailfish OS.

'''Notes'''

OTA is supported: <code>zypper refresh && zypper update</code> as root (<code>devel-su</code> to get root access). Things that need reflash are bootloader specific at the moment. If improvements like [[Crust]] or changes of partition layout are added, then you need to reflash.

== SkiffOS ==
[[File:SkiffOS-Icon-1.png|right|100px]]

Minimal in-memory cross-compiled OS optimized for hosting multiple in parallel Docker containers.

Provides the reliability of firmware with the ease-of-use of package managers.

Upgrade over-the-air via a simple rsync script, or copying 3 files.

Uses the [http://buildroot.org Buildroot] cross-compilation tool for support for all Pine64 boards.

Use configuration packages to configure distro:

{| class="wikitable"
! core/pinephone_neon || KDE Neon via Ubuntu repositories
|-
! core/pinephone_nixos || Nixos Mobile
|-
! core/pinephone_gentoo || Gentoo with Link-time Optimization & KDE Mobile or Phosh
|-
! core/pinephone_ubports || Ubuntu Ports for PinePhone
|-
! core/pinephone_manjaro_kde || Manjaro for PinePhone: KDE variant
|-
! core/pinephone_manjaro_phosh || Manjaro for PinePhone: Phosh variant
|-
! core/pinephone_manjaro_lomiri || Manjaro for PinePhone: Lomiri variant
|}

The boot-up OS is upgraded independently from the containers.

'''Download location'''

The repository and instructions can be found [https://github.com/skiffos/SkiffOS/tree/master/configs/pine64/phone here].

== Sxmo ==

A collection of Suckless programs to create a mobile UI. Based on postmarketOS.

'''Download location'''

Sxmo images can be found [https://images.postmarketos.org/bpo/ here] (in the ''/pine64-pinephone/sxmo/'' sections respectively).

'''username/password'''

user/147147

'''How to contribute and report defects'''

Contributing information is listed [https://git.sr.ht/~mil/sxmo-docs/tree/master/CONTRIBUTING.md here].

== Ubuntu Touch ==
[[File:Ubports-logo.png|right|100px]]

A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.

Ubuntu touch is a mobile version of Ubuntu developed by the UBports community.
Installation instructions can be found on
[https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone the UBports PinePhone project].
There is also a [https://github.com/goddard/pinephone/ script] to download the latest image and flash to your PinePhone.
In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://devices.ubuntu-touch.io/installer UBports installer] GUI tool.

'''Download location'''

[https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone UBports PinePhone project]

'''username/password'''

Set up during boot

'''What works, what does not work'''

Scroll down to the bottom of [https://gitlab.com/ubports/community-ports/pinephone this page].

'''How to contribute and report defects'''

See [https://gitlab.com/ubports/community-ports/pinephone UBports gitlab page].
See [https://ubports.com/foundation/sponsors UBports website] for how to donate.

= Tools =

There are software tools, that can be booted on the PinePhone.

== JumpDrive ==

JumpDrive can be used to flash the eMMC (and the microSD card), see [[PinePhone Installation Instructions#Using JumpDrive]].

See https://github.com/dreemurrs-embedded/Jumpdrive/releases for the latest image.
Make sure to download the "PinePhone" image and to unpack the archive before flashing.

= Factory Test OS =

{{Hint|'''Note:''' The magnetometer test will fail on the new Beta Edition, as the factory image wasn't updated for it yet.}}

On the Braveheart model, there was a postmarketOS based basic Factory Test OS pre-installed on the eMMC.
The developer Martijn Braam from postmarketOS has improved the functionality of the image considerably later.
Since the 20200501 version, it is able to test all the hardware.
It also includes functionality to install a new OS to the eMMC when using with an test image that includes that OS image.
The downloadable image just does the hardware tests.
Do not flash eMMC to test your device, just dd it to microSD and test from there.
New versions are distributed as part of the postmarketOS distribution.

Links:
* [https://images.postmarketos.org/pinephone/ Software Images] (download the latest one named like pine-pinephone-yyyyMMdd-factorytestX.img.xz)
* [https://gitlab.com/MartijnBraam/factorytest Git repo]
* [https://gitlab.com/MartijnBraam/factorytest/-/blob/master/README.rst Documentation]

== Factory-loaded OS builds ==

These are different operating system builds that was preloaded in the factory with testing utility.

Download the build, extract the image and dd it to a 8 GB or larger microSD card, then insert it into the PinePhone.
After power up or reboot, you may perform and complete the test routine, or apply the build from microSD card to eMMC.

All the download links below are direct download from pine64.org.

<div style="overflow: auto;">
{| class="wikitable" style="white-space: nowrap"
! OS
! Download Link
! File Size
! MD5
|-
| Beta Edition
| [https://files.pine64.org/os/PinePhone/BetaEdition/pine64-pinephone-plamo-beta-factorytest.img.xz pine64-pinephone-plamo-beta-factorytest.img.xz]
| 1.78GB
| <code>f16bce93504a52217540ac886863a418</code>
|-
| Mobian
| [https://files.pine64.org/os/PinePhone/Mobian/pine64-pinephone-20201207-factorytest-mobian.img.xz pine64-pinephone-20201207-factorytest-mobian.img.xz]
| 1.41GB
| <code>015be381ff4e650a7fca6d4eaa90d63d</code>
|-
| KDE
| [https://files.pine64.org/os/PinePhone/KDE/pine64-pinephone-20201208-factorytest-kde.img.xz pine64-pinephone-20201208-factorytest-kde.img.xz]
| 2.28GB
| <code>32979ff17b5ec4d358ce99f1aff0c77c</code>
|-
| Manjaro
| [https://files.pine64.org/os/PinePhone/Manjaro/pine64-pinephone-20201013-manjaro-stable-20201018-factory56.img.xz pine64-pinephone-20201013-manjaro-stable-20201018-factory56.img.xz]
| 1.04GB
| <code>4edfd4dceaefdd32a3417c1727161c29</code>
|-
| postmarketOS
| [https://files.pine64.org/os/PinePhone/PostMarketOS/pine64-pinephone-20200726-phosh-v20.05-factory.img.xz pine64-pinephone-20200726-phosh-v20.05-factory.img.xz]
| 517MB
| <code>244093be2f6d728fcbd1d29114607727</code>
|-
| Ubuntu Touch
| [https://files.pine64.org/os/PinePhone/UBPorts/PinePhone-flasher-ubuntu-7b.img.gz PinePhone-flasher-ubuntu-7b.img.gz]
| 1.05GB
| <code>2d7f5271e7a281db8f1b1219bedbe131</code>
|}
</div>

= Installing other ARM64 distributions =

{{Warning|Distributions not on this page may not even boot after you follow this section. In the best case, they will be barely usable.
This is more for fun, or if you would like to port a new distribution to the PinePhone.}}

{{Hint|'''Note:''' This section uses megi's kernel releases, and not the official ones from Pine64. While it is possible to use the official (and in the future, mainline) kernel, megi provides binary releases, which makes it very easy.}}

General steps:

# Create a boot partition (from 4 MB to about 252 MB) and a root partition (from the end of boot to the end of the card) filesystem on the SD card.
# Format the boot partition with vfat, and the root partition with a supported filesystem like ext4 or f2fs.
# Extract the root filesystem from your distribution's ARM image into the root filesystem on the SD card. Do not copy the partition, copy the files instead (in archive mode, like <code>rsync -ar</code>).
# Edit <code>/etc/fstab</code> to match your partitions.
# Grab megi's kernel from https://xff.cz/kernels/, Follow the instructions in the [https://xff.cz/kernels/README README], which involves copying the kernel modules into the SD card rootfs, and writing u-boot and the bootloader.

If you would like to see examples or specific commands for how to complete these steps, see:
* [https://github.com/nikhiljha/pp-fedora-sdsetup an example for Fedora], current unofficial [#Fedora] release
* [https://xnux.eu/howtos/install-arch-linux-arm.html an example for Arch Linux] by megi

= Other Resources =
Community
* [[Main_Page#Community_and_Support|Links to the community services]]

Hardware information
* [[PinePhone|General PinePhone hardware info]] in this Pine64 wiki
* Details specific to the Braveheart Edition: [[PinePhone_v1.1_-_Braveheart|PinePhone 1.1 Braveheart hardware details]]
* Details specific to the Community Edition: [[PinePhone_v1.2|PinePhone 1.2 hardware details]]
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here] and the preceding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here]

Other software information
* [https://linux-sunxi.org/Main_Page sunxi community wiki]
* [https://xnux.eu/devices/pine64-pinephone.html megi's feature/driver support matrix]
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)] see demonstration [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube]
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]

Other
* [https://pine64.com/?post_type=product Pine64 shop]
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on Linux distributions and desktop environments on mobile devices]
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing microSD cards]

[[Category:PinePhone]]

PinePhone Software Releases

2021-09-22T08:28:19Z

RainSlide: /* GloDroid */ remove an empty line

This page contains a list of all available OS releases for the [[PinePhone]], as well as links to other resources.

See [[PinePhone Installation Instructions]] on how to install the operating systems.<br>
However, if your phone came preloaded with software, Please see [[PinePhone Updating Instructions]].

{{Hint| '''Note:''' Some releases may not have a good setup for the backlight at low brightness.
If configured too low, the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.}}

= Software Releases =

This is a list of OSes that specifically support the PinePhone.
Since PinePhone support is included in Mainline Linux, in principle, any ARM Linux OS can be used if possible required patches are included.

== Arch Linux ARM ==
[[File:Archlinux-logo.png|right|100px]]

(Unofficial) Arch Linux ARM with choice of Phosh UI, Plasma Mobile, or barebones.
Currently being maintained by the [https://danctnix.org/ DanctNIX] community (GitHub: [https://github.com/DanctNIX/danctnix danctnix], [https://github.com/dreemurrs-embedded dreemurrs-embedded]).

* GitHub: [https://github.com/dreemurrs-embedded/Pine64-Arch dreemurrs-embedded/Pine64-Arch]

'''Download location'''

Get the latest image here: https://github.com/dreemurrs-embedded/Pine64-Arch/releases

'''username/password'''

{| class="wikitable"
! Default user || <code>alarm/123456</code>
! root || <code>root/root</code>
|}

'''What works, what does not work'''

Most of the things now works, there are some minor issues with [[Crust]].

'''How to contribute and report defects'''

You may find the Discord, Matrix and Telegram of DanctNIX community at [https://github.com/DanctNIX/danctnix/blob/master/README.md#channel-list the Channel list section of DanctNIX/README.md].

Feel free to send us [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls pull requests] and report [https://github.com/dreemurrs-embedded/Pine64-Arch/issues issues] on [https://github.com/dreemurrs-embedded/Pine64-Arch GitHub].

== ExpidusOS ==

A fork of [https://voidlinux.org Void Linux] with a custom fork of XFCE called [https://github.com/ExpidusOS/genesis Gensis] as the default desktop environment, developed by [https://midstall.com/ Midstall Software].

* [https://expidusos.com ExpidusOS official website]
* [https://wiki.expidusos.com/index.php/Main_Page ExpidusOS Wiki]
* [https://discord.gg/GVfBF2w Midstall Software Discord server]
* GitHub: [https://github.com/ExpidusOS ExpidusOS]

'''Download location'''

Check the [https://expidusos.com/download download page] for that latest version, or the [https://build.expidusos.com/ image file list] for all versions, look for the file name that starts with "pinephone".

'''username/password'''

expidus/expidus

'''What works, what does not work'''

The ExpidusOS Wiki has a page detailing [https://wiki.expidusos.com/index.php/Device:PinePhone supported features].

'''How to contribute and report defects'''

Join the [https://discord.gg/GVfBF2w Discord server] or corresponding repo at GitHub ([https://github.com/orgs/ExpidusOS/repositories repo list]).

== Fedora ==
[[File:Fedora-logo.png|right|100px]]

An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and [https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/ some additional packages] to tie it all together.
It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.

* Forum discussion: [https://forum.pine64.org/showthread.php?tid=9347 Fedora + Phosh for PinePhone]
* GitHub: [https://github.com/nikhiljha/pp-fedora-sdsetup nikhiljha/pp-fedora-sdsetup]

'''Download location'''

* [https://github.com/nikhiljha/pp-fedora-sdsetup/releases Flashable images]
* [https://github.com/nikhiljha/pp-fedora-sdsetup Build scripts]
* [https://copr.fedorainfracloud.org/coprs/njha/mobile/ Packages (Fedora COPR)]

There is also an FTP server with a full Fedora 34 workstation build with phosh: ftp://pine.warpspeed.dk/nightly/pinephone/ (Mount this with something like Nautilus)

'''username/password'''

pine/123456

'''What works, what does not work'''

WiFi, Bluetooth, SMS, Data, Calls all work!

There are still a few bugs though, and [https://xnux.eu/devices/pine64-pinephone.html#toc-feature-driver-support-matrix some features don't have driver support yet] on any PinePhone distribution.

'''How to contribute and report defects'''

Please send your bug reports to [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker].
Be sure to include logs if applicable!
Send us pull requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/pulls Github].

== Gentoo ==
[[File:GentooLogo.png|right|100px]]{{hint|Please consider cross-compiling the software on the computer.
Long compilation times and heat production can lead to a reduced lifespan of the phone.}}There are unofficial Gentoo overlays with ebuilds for the PinePhone.
There are no images - you'll be building it yourself, picking which kernel, bootloader and desktop environment you want to use.
You will be using the arm64 version of Gentoo.

'''Documentation'''

* https://stealthgun.tweakblogs.net/blog/19336/gentoo-on-a-pinephone
* https://wiki.gentoo.org/wiki/User:Dr41nU/PinePhone
* https://wiki.gentoo.org/wiki/PinePhone (incomplete)

'''Overlay locations'''

* https://gitlab.com/bingch/gentoo-overlay
* https://github.com/stealthgun/gjdwebserver-overlay

== GloDroid ==

{{Hint|There can be large intervals between release update, so available images may be outdated and do not reflect the state of the current developments.}}A fully open source port of Android to the PinePhone.

* GitHub: [https://github.com/GloDroid GloDroid]

'''Download location'''

https://github.com/GloDroid/glodroid_manifest/releases (last release at 2021-05-20)

'''What works, what does not work'''

Works: WiFi, screen dimming, touchscreen and charging work.
Don't work: Bluetooth, Telephony, GPS, Sound

== LuneOS ==
[[File:WebOS-Ports-logo.png|right|100px]]

LuneOS is a open source mobile operating system based on [https://www.webosose.org/ webOS Open Source Edition]([https://github.com/webosose GitHub], previously known as [https://github.com/openwebos Open webOS]) by LG, comes with [https://webos-ports.org/wiki/Luna_Next Luna Next] UI, currently developed by the WebOS Ports community.

* [https://www.webos-ports.org/wiki/Main_Page WebOS Ports Wiki]
* [https://webos-ports.org/wiki/Pinephone_Info WebOS-Ports Wiki's Pinephone page]
* GitHub: [https://github.com/webOS-ports WebOS Ports]

'''Download location'''

* [http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]

It is recommended to use ''bmaptool'', which is faster than dd, and can decompress archived image files on-the-fly.

Syntax is:

bmaptool copy [from] [to]

For example:

bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-140.rootfs.wic.gz /dev/mmcblk0

.wic file can be treated as .img file when flashing. You may rename .wic file to .img when using GUI tools that require file extension to be .img.

== Maemo Leste ==
[[File:Maemoleste-logo.png|right|100px]]

[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices,
originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it.
The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices.

The new version Maemo 8 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel.
The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK].
The current version is Devuan Beowulf (Debian Buster) and has simultaneous support for both Devuan and Debian.

In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository].
To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's build]).
Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.

* [https://maemo-leste.github.io/ Maemo Leste website]
* [https://leste.maemo.org/Main_Page Maemo Leste Wiki]
** [https://leste.maemo.org/PinePhone PinePhone wiki page]
** [https://leste.maemo.org/Leste_FAQ Maemo Leste FAQ]
* GitHub: [https://github.com/maemo-leste maemo-leste]
* Twitter: [https://twitter.com/maemoleste @maemoleste]

'''Download location'''

[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds]. There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].

'''username/password'''

root/toor

You may use <code>sudo</code> directly.

'''What works, what does not work'''

For current status and workarounds, please read their [https://leste.maemo.org/PinePhone PinePhone wiki page].

'''How to contribute and report defects'''

Most discussion occurs at [ircs://irc.libera.chat:6697/#maemo-leste <code>#maemo-leste</code> on <code>irc.libera.chat</code>].
The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback.

All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki.

Submit [https://github.com/maemo-leste/bugtracker/issues bug reports] on github.
To track known issues, you may use these search terms:
[https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone],
[https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64].

Learn about
[https://leste.maemo.org/Development development],
[https://leste.maemo.org/Development/Porting_Packages porting packages],
[https://leste.maemo.org/Development/Building_Packages building packages],
[https://leste.maemo.org/Development/Tasks todo list],
and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian].
Some tasks have funding available.

== Manjaro ARM ==
[[File:Manjaro-logo.svg|right|100px]]

Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.

'''Download location'''

* Phosh: [https://github.com/manjaro-pinephone/phosh Stable] / [https://github.com/manjaro-pinephone/phosh-dev Dev]
* Plasma Mobile: [https://github.com/manjaro-pinephone/plasma-mobile Stable] / [https://github.com/manjaro-pinephone/plasma-mobile-dev Dev]
* Lomiri: [https://github.com/manjaro-pinephone/lomiri-dev Dev] (No longer maintained)

'''username/password'''

{| class="wikitable"
! Default user || <code>manjaro/123456</code>
! root || <code>root/root</code>
|}

'''What works, what does not work'''

{{Hint| Note: At the first boot, the Phosh image will be loaded at a TTY login prompt for multiple minutes.}}

See Manjaro's release announcements on their forum.
Recent ones:
[https://forum.manjaro.org/t/manjaro-arm-beta12-with-phosh-pinephone/73099 Phosh],
[https://forum.manjaro.org/t/manjaro-arm-beta5-with-plasma-mobile-pinephone/69318 Plasma] and
[https://forum.manjaro.org/t/manjaro-arm-alpha3-with-lomiri-pinephone/49923 Lomiri].

'''How to contribute and report defects'''

See the end of the [https://forum.manjaro.org/t/manjaro-arm-beta7-with-phosh-pinephone/58901 announcement].

== Mobian ==
[[File:Debian-logo.png|right|100px]]

An unofficial [https://www.debian.org Debian] build for ARM64 running with Phosh (developed by Purism, uses Wayland instead of Xorg).
The base system is pure Debian, with only the GUI applications and a few others (ModemManager, WiFi chip firmware) being built from modified sources (as well as the kernel and u-boot).
Current version is Debian Bookworm.

'''Download location'''

[https://images.mobian-project.org/pinephone/nightly/ Nightly] /
[https://images.mobian-project.org/pinephone/installer/ Installer] /
[https://images.mobian-project.org/pinephone/ Stable]

Extract the image before installing:

$ gzip -d Downloads/mobian-pinephone-*.img.gz

See the [https://wiki.mobian-project.org/doku.php?id=install project page] for specific installation instructions.

'''username/password'''

mobian/1234

'''What works, what does not work'''

See [https://gitlab.com/mobian1/mobian-recipes/-/blob/master/README.md the project's README file] or [https://wiki.mobian-project.org/doku.php?id=pinephone the wiki] for most up to date status.

Check [https://gitlab.com/groups/mobian1/-/issues bug tracker] for known issues. Questions? Ask on our [https://forum.pine64.org/showthread.php?tid=9016 thread].

'''How to contribute and report defects'''

It is recommended that you log your bug reports in [https://gitlab.com/mobian1/issues the project's issue tracker].
As a general rule, issues with third-party apps (even the default ones) should be reported upstream.
A Mobian issue would be related to getting the hardware to work on the PinePhone,
but if unsure where the issue should be reported just open a ticket or ask.
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/mobian1 Gitlab].

'''Notes'''

See [https://wiki.mobian-project.org/doku.php?id=start the wiki] for additional information regarding screen resolution, USB networking, WiFi hotspot, Chatty and the repository.

== Multi-distro demo image ==

{{Warning | This is an demo image for testing different OSes before installing a regular image. It is highly discouraged attempting to use the image productively. The kernel is shared across the different OSes and is not being updated.}}

This image allow users to try many of the above Linux distributions easily, without having to figure out how to flash them individually and juggle with many microSD cards. Also called megi's 15-in-1 multi boot image.

* Main page: https://xnux.eu/p-boot-demo/
* Git repo: https://megous.com/git/pinephone-multi-boot/
* Forum discussion: [https://forum.pine64.org/showthread.php?tid=11347 UPDATED (June 2021): 17-distro multi-boot image for Pinephone (incl. 3GiB variant)]

'''Update 2021-06-02, using megi's kernel 5.13-rc4'''

DD image to SD card and boot. This image is for 16GiB or larger SD cards, also works if flashed to eMMC.

This is also a good build for charging depleted battery. Just boot up this build with power supply connected, keep the PinePhone charging for 3 hours at power down stage.

For more info on this build, please visit its entry the "News" section of its [https://xnux.eu/p-boot-demo/ web page].

* [http://dl.xnux.eu/p-boot-multi-2021-06-02.torrent Download torrent file from author's website]
* [http://dl.xnux.eu/p-boot-multi-2021-06-02/ Download img.zst from author's website] (speed limited to 512KiB/s)
* [http://mirror.uxes.cz/dl.xnux.eu/ Download torrent and img.zst from discord user uxes' mirror]
** '''File name:''' multi.img.zst
** '''SHA-256:''' <span style="word-break: break-all">9b099cdfece3ba862348ca32af6c51a41a1d161b1d897f9928ae8be3c824a0b6</span>
** '''File Size:''' 6.57GiB

* [https://files.pine64.org/os/PinePhone/Multi/p-boot-multi-2021-06-02.img.gz Direct download img.gz from pine64.org] (re-zipped from zstd to gzip)
** '''File name:''' p-boot-multi-2021-06-02.img.gz
** '''MD5:''' 2abdaafb01dd7519f678b5a7c6538493
** '''File Size:''' 6.8GB

Due to its size, download though torrent is suggested by the author on its main page.

{{hint | '''Note about .zst archive file:'''

On Linux, you may install or compile <code>zstd</code>, and write the image to SD card by using <code>zstdcat</code> and <code>dd</code>. See the "Installation" section of its [https://xnux.eu/p-boot-demo/ web page] for command examples.

On Windows, you may use [https://github.com/mcmilk/7-Zip-zstd 7-zip-zstd], it provides different installation method in the README.md. Install and extract the .img file from the zst archive, and flash with tools like [https://sourceforge.net/projects/win32diskimager/ Win32 Disk Imager].

Also see [[PinePhone Installation Instructions]].
}}

'''username/password'''

All passwords, including root passwords, are <code>1111</code>.
sxmo username is <code>user</code>.

== Nemo Mobile ==
[[File:nemo_mobile.png|right|100px]]

Nemo Mobile is the open source build of Sailfish OS with a open source UI called [http://nemomobile.net/glacier-home/ Glacier] ([https://wiki.merproject.org/wiki/Nemo/Glacier Mer Wiki]), [http://nemomobile.net/pages/Hello_manjaro/ based on Manjaro].

* Website: [https://nemomobile.net/ Nemo Mobile UX team]
* [https://wiki.merproject.org/wiki/Nemo Mer Wiki page]

'''Download location'''

See the [https://nemomobile.net/installation/ installation page] on their website for the newest release and installation guides.

'''What works, what does not work'''

Development is now moving very fast after rebasing. For the current devel image, Wifi and Bluetooth works.

'''How to contribute and report defects'''

For the Nemo Mobile UX itself:
* GitHub issues: https://github.com/nemomobile-ux/main/issues

For hardware:
* GitHub issues: https://github.com/neochapay/nemo-device-dont_be_evil/issues

== NixOS ==
[[File:nixos.png|right|100px]]

NixOS support is handled through the Mobile NixOS project.

* Project home page: [https://mobile.nixos.org/ Mobile NixOS]
* PinePhone device page: [https://mobile.nixos.org/devices/pine64-pinephone.html Pine64 PinePhone — Mobile NixOS]
* GitHub: [https://github.com/NixOS/mobile-nixos NixOS/mobile-nixos]

There is no pre-built complete image.
For now users, are expected to follow the instructions in the [https://mobile.nixos.org/getting-started.html Getting Started page],
and [https://mobile.nixos.org/devices/pine64-pinephone.html Project's device page].

'''What works, what does not work'''

Currently, it boots, it's just as compatible as the Android-based devices are with Mobile NixOS.
It even supports a bit more since it can use WiFi.

Support for all of the hardware will be coming, this project is a breadth-first work, where the work spans multiple devices in parallel.

'''How to contribute and report defects'''

On [https://github.com/NixOS/mobile-nixos/issues the project's repository].
Please specify that you are using a PinePhone when reporting issues.
Details about contributions and donations are on the [https://nixos.org/nixos/community.html NixOS website].

== OpenMandriva Lx ==
[[File:Oma-logo-22042013_300pp.png|right|100px]]{{Hint| '''Note:''' This image is solely for testing purposes.}}OpenMandriva Lx with Plasma Mobile as UI.

'''Download location'''

The official image can be found [https://sourceforge.net/projects/openmandriva/files/release/4.2/RC/Pinephone/ at sourceforge.net].
See [https://www.openmandriva.org/en/news/article/openmandriva-lx-4-3-rc-available-for-testing here] for the offical announcement.

'''What works, what does not work'''

From the [https://www.openmandriva.org/en/news/article/openmandriva-lx-4-3-rc-available-for-testing 4.3 announcement],
in future updates (4.3 and later), "Phone calls are working, and we have rewritten the camera app to be far more useful".

== openSUSE ==
[[File:SLEM-OS-logo.png|right|100px]]

Our images use the same [https://en.opensuse.org/Portal:Tumbleweed openSUSE Tumbleweed] base as our desktop images,
except what needs to be changed for the PinePhone.
The images include <i>zypper</i> (RPM) as the default package manager,
and have access to virtually the same (open source) software as our desktop repositories,
thanks to the [https://en.opensuse.org/Portal:Factory Factory] ports.
Using [https://en.opensuse.org/SDB:DNF dnf] is possible, if preferred.

'''Download links'''

* [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz Phosh] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz.sha256 SHA-256] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz.sha256.asc SHA-256 Signature]
* [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz Plasma Mobile] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz.sha256 SHA-256] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz.sha256.asc SHA-256 Signature]

To verify the images you need to import [https://build.opensuse.org/projects/devel:ARM:Factory:Contrib:PinePhone/public_key our GPG key].
Keep on mind that the first boot may stay on black screen for about a minute - consequent boots should be faster.

You can find install instructions at [https://en.opensuse.org/HCL:PinePhone#Installing_openSUSE_in_a_Pinephone this section] in the openSUSE Wiki.

'''Username/Password'''

The login credentials are pine/1234 and root/linux.
Change (or disable) the root password once you are set up.

'''What works and what does not work'''

You can find all information about the releases of the project [https://gitlab.com/slem.os/slem.os/-/blob/master/CHANGELOG.md here].
Detailed information, tips and troubleshooting suggestions are also provided at [https://en.opensuse.org/HCL:PinePhone the openSUSE Wiki].
You will also find information in our wiki on how to report issues (Contributing section).

== postmarketOS ==
[[File:PostmarketOS-logo.png|right|100px]]

postmarketOS extends [https://www.alpinelinux.org/ Alpine Linux] to run on smartphones and other mobile devices.
It offers various user interfaces (Phosh, Plasma Mobile, Sxmo, Plasma Desktop, Gnome 3, Kodi, XFCE4, ...).

As of writing, official images are provided with Phosh, Plasma Mobile and Sxmo.
The official images come in two flavors, either as a test image to try out postmarketOS, or with the installer.

When using the installer images (recommended), it is possible to:
* encrypt the installation
* install from the SD card to eMMC

Power users may also create their own image with the distribution's install and development tool <code>pmbootstrap</code>.

Please read the detailed [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation installation instructions] in the wiki.

'''Download location'''

* [https://postmarketos.org/download/ Download page]
* [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation Flashing instructions]

'''Username/password'''

* Test images: user/147147
* When using the installer images or building an image with pmbootstrap, you set your own username and password.
** The Phosh and Plasma Mobile lock screens only support numeric keyboard, so you should '''only use numbers''' in your password.

'''What works, what does not work'''

See the [https://gitlab.com/postmarketOS/pmaports/-/issues?label_name%5B%5D=device-pine64-pinephone issue tracker].

'''How to contribute and report defects'''

[https://gitlab.com/postmarketOS/pmaports/-/issues?label_name%5B%5D=device-pine64-pinephone postmarketOS issue tracker] for PinePhone support.
See [https://wiki.postmarketos.org/wiki/Contributing postmarketOS wiki] for options to contribute.

== PureOS ==
[[File:Pureos.png|right|100px]]

{{Warning|This project is no longer under development and has been abandoned. Use [https://wiki.pine64.org/wiki/PinePhone_Software_Releases#Mobian Mobian] instead}}

{{Hint|There is no prebuilt image, you'll need a Linux environment and build the image yourself.}}

[https://www.pureos.net/ PureOS] is a user friendly, secure and freedom respecting GNU/Linux distribution based on Debian and GNOME developed by the Purism community.

* [https://tracker.pureos.net/w/ PureOS Wiki], no PinePhone page there
* Mobile-optimized apps list from the [https://tracker.pureos.net/w/pureos/mobile_optimized_apps/ Software Center in PureOS] and [https://tracker.pureos.net/w/pureos/3rd-party_mobile_optimized_apps/ 3rd party repos]
* [https://github.com/rufferson/pureos-pinephone current PinePhone PureOS repo], A script to convert Librem5 PureOS to PinePhone Pure-OS

'''Download location'''

Use [https://raw.githubusercontent.com/rufferson/pureos-pinephone/master/build_image.sh the convert script] to download and build the image from u-boot, PinePhone linux kernel and Librem5 PureOS.

Also see:
* [https://forums.puri.sm/t/successful-installation-of-pureos-on-pinephone/8741/12 Successful installation of PureOS on PinePhone - PureOS - Purism community]
* The PureOS section of [https://www.ruff.mobi/go/mobi/pine.html PinePhone page] on ruff.mobi
* An [https://gitlab.com/a-wai/debos-pinephone archived repo] for PureOS on PinePhone
* A [https://mozzwald.com/pp/ file list] with [https://mozzwald.com/pp/pureos-pinephone-build-instructions.txt pureos pinephone build instructions] on mozzwald.com

== Sailfish OS ==
[[File:Sailfish_logo.png|right|100px]]

[https://sailfishos.org/ Sailfish OS] is a Linux-based operating system based on open source projects such as [https://wiki.merproject.org/wiki/Main_Page Mer], and a closed source UI based on [https://sailfishos.org/wiki/Lipstick Lipstick].

* [https://wiki.merproject.org/wiki/Adaptations/PinePhone64 PinePhone Wiki Page] on Mer Wiki, for both Nemo Mobile and Sailfish OS.
* [https://gitlab.com/pinephone-sailfish-os/linux-kernel/ Linux kernel config repo]
* [https://gitlab.com/sailfishos-porters-ci/dont_be_evil-ci/ Sailfish OS repo]

'''Download location'''

'''Flashing script'''

The Sailfish OS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].

The script downloads the image and bootloader from the CI, extracts everything and burns it onto the SD card.
Note: The script will format and erase the SD card!

Instructions:
# Download the flashing script
# Insert a microSD card in your device
# Make the script executable: <code>chmod +x flash-it.sh</code>
# Verify that you have the <code>bsdtar</code> package installed
# Execute it: <code>./flash-it.sh</code>
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).

* When asked where to flash, type 'raw' and it will build the image on your computer. Otherwise define the path /dev/.... to flash to card or internal emmc.

'''username/password'''

Set PIN on initialization.

* Sometimes the first run stalls before the tutorial. Reboot and it will start from setting the security pin.
* The homescreen may be locked unless you boot with a sim card inserted. An old expired sim will do. '''If you do not have a SIM card on hands, do NOT set a security code on first boot.'''
* When a screen with a loading circle is displayed, just left/right swipe it away.
* If you're not familiar with Sailfish OS, pay attention to the tutorial - the interface works great, but is not immediately obvious. If you are familiar with it, you can skip the tutorial by touching all 4 corners starting top left.

'''What works, what does not work'''

See the [https://wiki.merproject.org/wiki/Adaptations/PinePhone64#Hardware_Support Hardware Support section] on the Mer Wiki's PinePhone Page.

There is a limited selection of apps available from the Jolla store, the vast majority are hosted on openrepos.net. If the Storeman app for openrepos is not preinstalled, download the RPM and click to install.

'''How to contribute and report defects'''

See the [https://wiki.merproject.org/wiki/Adaptations/PinePhone64#Installation Installation section] on the Mer Wiki's PinePhone Page for compile, build and development.

Git repo links are at the top of this OS section. other repos that may be helpful:

* [https://github.com/sailfish-on-dontbeevil GitHub project page]
* [https://github.com/sailfish-on-dontbeevil/flash-it the repo of the flash-it.sh flashing script]
* [https://build.merproject.org/project/show/nemo:devel:hw:pine:dontbeevil Mer Open Build Service page] ([https://forum.sailfishos.org/t/changes-needed-to-merge-the-project-names-to-sailfish-os/1672 Mer is being assimilated into Sailfish OS] and [https://forum.sailfishos.org/t/obs-shut-down-and-next-steps/1814 OBS is shutting down], also see [https://specs.openstack.org/openstack/fuel-specs/specs/7.0/replace-obs.html OpenStack is replacing OBS with another build system based on Jenkins], if it's related, even OBS come back under Sailfish OS, it will be different.)

See the [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues Sailfish OS wiki] for links to their forum, as well as info required when reporting an issue. See the [https://sailfishos.org/wiki/SailfishOS Sailfish OS wiki main page] for options to contribute to Sailfish OS.

'''Notes'''

OTA is supported: <code>zypper refresh && zypper update</code> as root (<code>devel-su</code> to get root access). Things that need reflash are bootloader specific at the moment. If improvements like [[Crust]] or changes of partition layout are added, then you need to reflash.

== SkiffOS ==
[[File:SkiffOS-Icon-1.png|right|100px]]

Minimal in-memory cross-compiled OS optimized for hosting multiple in parallel Docker containers.

Provides the reliability of firmware with the ease-of-use of package managers.

Upgrade over-the-air via a simple rsync script, or copying 3 files.

Uses the [http://buildroot.org Buildroot] cross-compilation tool for support for all Pine64 boards.

Use configuration packages to configure distro:

{| class="wikitable"
! core/pinephone_neon || KDE Neon via Ubuntu repositories
|-
! core/pinephone_nixos || Nixos Mobile
|-
! core/pinephone_gentoo || Gentoo with Link-time Optimization & KDE Mobile or Phosh
|-
! core/pinephone_ubports || Ubuntu Ports for PinePhone
|-
! core/pinephone_manjaro_kde || Manjaro for PinePhone: KDE variant
|-
! core/pinephone_manjaro_phosh || Manjaro for PinePhone: Phosh variant
|-
! core/pinephone_manjaro_lomiri || Manjaro for PinePhone: Lomiri variant
|}

The boot-up OS is upgraded independently from the containers.

'''Download location'''

The repository and instructions can be found [https://github.com/skiffos/SkiffOS/tree/master/configs/pine64/phone here].

== Sxmo ==

A collection of Suckless programs to create a mobile UI. Based on postmarketOS.

'''Download location'''

Sxmo images can be found [https://images.postmarketos.org/bpo/ here] (in the ''/pine64-pinephone/sxmo/'' sections respectively).

'''username/password'''

user/147147

'''How to contribute and report defects'''

Contributing information is listed [https://git.sr.ht/~mil/sxmo-docs/tree/master/CONTRIBUTING.md here].

== Ubuntu Touch ==
[[File:Ubports-logo.png|right|100px]]

A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.

Ubuntu touch is a mobile version of Ubuntu developed by the UBports community.
Installation instructions can be found on
[https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone the UBports PinePhone project].
There is also a [https://github.com/goddard/pinephone/ script] to download the latest image and flash to your PinePhone.
In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://devices.ubuntu-touch.io/installer UBports installer] GUI tool.

'''Download location'''

[https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone UBports PinePhone project]

'''username/password'''

Set up during boot

'''What works, what does not work'''

Scroll down to the bottom of [https://gitlab.com/ubports/community-ports/pinephone this page].

'''How to contribute and report defects'''

See [https://gitlab.com/ubports/community-ports/pinephone UBports gitlab page].
See [https://ubports.com/foundation/sponsors UBports website] for how to donate.

= Tools =

There are software tools, that can be booted on the PinePhone.

== JumpDrive ==

JumpDrive can be used to flash the eMMC (and the microSD card), see [[PinePhone Installation Instructions#Using JumpDrive]].

See https://github.com/dreemurrs-embedded/Jumpdrive/releases for the latest image.
Make sure to download the "PinePhone" image and to unpack the archive before flashing.

= Factory Test OS =

{{Hint|'''Note:''' The magnetometer test will fail on the new Beta Edition, as the factory image wasn't updated for it yet.}}

On the Braveheart model, there was a postmarketOS based basic Factory Test OS pre-installed on the eMMC.
The developer Martijn Braam from postmarketOS has improved the functionality of the image considerably later.
Since the 20200501 version, it is able to test all the hardware.
It also includes functionality to install a new OS to the eMMC when using with an test image that includes that OS image.
The downloadable image just does the hardware tests.
Do not flash eMMC to test your device, just dd it to microSD and test from there.
New versions are distributed as part of the postmarketOS distribution.

Links:
* [https://images.postmarketos.org/pinephone/ Software Images] (download the latest one named like pine-pinephone-yyyyMMdd-factorytestX.img.xz)
* [https://gitlab.com/MartijnBraam/factorytest Git repo]
* [https://gitlab.com/MartijnBraam/factorytest/-/blob/master/README.rst Documentation]

== Factory-loaded OS builds ==

These are different operating system builds that was preloaded in the factory with testing utility.

Download the build, extract the image and dd it to a 8 GB or larger microSD card, then insert it into the PinePhone.
After power up or reboot, you may perform and complete the test routine, or apply the build from microSD card to eMMC.

All the download links below are direct download from pine64.org.

<div style="overflow: auto;">
{| class="wikitable" style="white-space: nowrap"
! OS
! Download Link
! File Size
! MD5
|-
| Beta Edition
| [https://files.pine64.org/os/PinePhone/BetaEdition/pine64-pinephone-plamo-beta-factorytest.img.xz pine64-pinephone-plamo-beta-factorytest.img.xz]
| 1.78GB
| <code>f16bce93504a52217540ac886863a418</code>
|-
| Mobian
| [https://files.pine64.org/os/PinePhone/Mobian/pine64-pinephone-20201207-factorytest-mobian.img.xz pine64-pinephone-20201207-factorytest-mobian.img.xz]
| 1.41GB
| <code>015be381ff4e650a7fca6d4eaa90d63d</code>
|-
| KDE
| [https://files.pine64.org/os/PinePhone/KDE/pine64-pinephone-20201208-factorytest-kde.img.xz pine64-pinephone-20201208-factorytest-kde.img.xz]
| 2.28GB
| <code>32979ff17b5ec4d358ce99f1aff0c77c</code>
|-
| Manjaro
| [https://files.pine64.org/os/PinePhone/Manjaro/pine64-pinephone-20201013-manjaro-stable-20201018-factory56.img.xz pine64-pinephone-20201013-manjaro-stable-20201018-factory56.img.xz]
| 1.04GB
| <code>4edfd4dceaefdd32a3417c1727161c29</code>
|-
| postmarketOS
| [https://files.pine64.org/os/PinePhone/PostMarketOS/pine64-pinephone-20200726-phosh-v20.05-factory.img.xz pine64-pinephone-20200726-phosh-v20.05-factory.img.xz]
| 517MB
| <code>244093be2f6d728fcbd1d29114607727</code>
|-
| Ubuntu Touch
| [https://files.pine64.org/os/PinePhone/UBPorts/PinePhone-flasher-ubuntu-7b.img.gz PinePhone-flasher-ubuntu-7b.img.gz]
| 1.05GB
| <code>2d7f5271e7a281db8f1b1219bedbe131</code>
|}
</div>

= Installing other ARM64 distributions =

{{Warning|Distributions not on this page may not even boot after you follow this section. In the best case, they will be barely usable.
This is more for fun, or if you would like to port a new distribution to the PinePhone.}}

{{Hint|'''Note:''' This section uses megi's kernel releases, and not the official ones from Pine64. While it is possible to use the official (and in the future, mainline) kernel, megi provides binary releases, which makes it very easy.}}

General steps:

# Create a boot partition (from 4 MB to about 252 MB) and a root partition (from the end of boot to the end of the card) filesystem on the SD card.
# Format the boot partition with vfat, and the root partition with a supported filesystem like ext4 or f2fs.
# Extract the root filesystem from your distribution's ARM image into the root filesystem on the SD card. Do not copy the partition, copy the files instead (in archive mode, like <code>rsync -ar</code>).
# Edit <code>/etc/fstab</code> to match your partitions.
# Grab megi's kernel from https://xff.cz/kernels/, Follow the instructions in the [https://xff.cz/kernels/README README], which involves copying the kernel modules into the SD card rootfs, and writing u-boot and the bootloader.

If you would like to see examples or specific commands for how to complete these steps, see:
* [https://github.com/nikhiljha/pp-fedora-sdsetup an example for Fedora], current unofficial [#Fedora] release
* [https://xnux.eu/howtos/install-arch-linux-arm.html an example for Arch Linux] by megi

= Other Resources =
Community
* [[Main_Page#Community_and_Support|Links to the community services]]

Hardware information
* [[PinePhone|General PinePhone hardware info]] in this Pine64 wiki
* Details specific to the Braveheart Edition: [[PinePhone_v1.1_-_Braveheart|PinePhone 1.1 Braveheart hardware details]]
* Details specific to the Community Edition: [[PinePhone_v1.2|PinePhone 1.2 hardware details]]
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here] and the preceding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here]

Other software information
* [https://linux-sunxi.org/Main_Page sunxi community wiki]
* [https://xnux.eu/devices/pine64-pinephone.html megi's feature/driver support matrix]
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)] see demonstration [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube]
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]

Other
* [https://pine64.com/?post_type=product Pine64 shop]
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on Linux distributions and desktop environments on mobile devices]
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing microSD cards]

[[Category:PinePhone]]

PinePhone Software Releases

2021-09-22T08:27:53Z

RainSlide: /* OpenMandriva Lx */ Remove empty lines

This page contains a list of all available OS releases for the [[PinePhone]], as well as links to other resources.

See [[PinePhone Installation Instructions]] on how to install the operating systems.<br>
However, if your phone came preloaded with software, Please see [[PinePhone Updating Instructions]].

{{Hint| '''Note:''' Some releases may not have a good setup for the backlight at low brightness.
If configured too low, the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.}}

= Software Releases =

This is a list of OSes that specifically support the PinePhone.
Since PinePhone support is included in Mainline Linux, in principle, any ARM Linux OS can be used if possible required patches are included.

== Arch Linux ARM ==
[[File:Archlinux-logo.png|right|100px]]

(Unofficial) Arch Linux ARM with choice of Phosh UI, Plasma Mobile, or barebones.
Currently being maintained by the [https://danctnix.org/ DanctNIX] community (GitHub: [https://github.com/DanctNIX/danctnix danctnix], [https://github.com/dreemurrs-embedded dreemurrs-embedded]).

* GitHub: [https://github.com/dreemurrs-embedded/Pine64-Arch dreemurrs-embedded/Pine64-Arch]

'''Download location'''

Get the latest image here: https://github.com/dreemurrs-embedded/Pine64-Arch/releases

'''username/password'''

{| class="wikitable"
! Default user || <code>alarm/123456</code>
! root || <code>root/root</code>
|}

'''What works, what does not work'''

Most of the things now works, there are some minor issues with [[Crust]].

'''How to contribute and report defects'''

You may find the Discord, Matrix and Telegram of DanctNIX community at [https://github.com/DanctNIX/danctnix/blob/master/README.md#channel-list the Channel list section of DanctNIX/README.md].

Feel free to send us [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls pull requests] and report [https://github.com/dreemurrs-embedded/Pine64-Arch/issues issues] on [https://github.com/dreemurrs-embedded/Pine64-Arch GitHub].

== ExpidusOS ==

A fork of [https://voidlinux.org Void Linux] with a custom fork of XFCE called [https://github.com/ExpidusOS/genesis Gensis] as the default desktop environment, developed by [https://midstall.com/ Midstall Software].

* [https://expidusos.com ExpidusOS official website]
* [https://wiki.expidusos.com/index.php/Main_Page ExpidusOS Wiki]
* [https://discord.gg/GVfBF2w Midstall Software Discord server]
* GitHub: [https://github.com/ExpidusOS ExpidusOS]

'''Download location'''

Check the [https://expidusos.com/download download page] for that latest version, or the [https://build.expidusos.com/ image file list] for all versions, look for the file name that starts with "pinephone".

'''username/password'''

expidus/expidus

'''What works, what does not work'''

The ExpidusOS Wiki has a page detailing [https://wiki.expidusos.com/index.php/Device:PinePhone supported features].

'''How to contribute and report defects'''

Join the [https://discord.gg/GVfBF2w Discord server] or corresponding repo at GitHub ([https://github.com/orgs/ExpidusOS/repositories repo list]).

== Fedora ==
[[File:Fedora-logo.png|right|100px]]

An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and [https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/ some additional packages] to tie it all together.
It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.

* Forum discussion: [https://forum.pine64.org/showthread.php?tid=9347 Fedora + Phosh for PinePhone]
* GitHub: [https://github.com/nikhiljha/pp-fedora-sdsetup nikhiljha/pp-fedora-sdsetup]

'''Download location'''

* [https://github.com/nikhiljha/pp-fedora-sdsetup/releases Flashable images]
* [https://github.com/nikhiljha/pp-fedora-sdsetup Build scripts]
* [https://copr.fedorainfracloud.org/coprs/njha/mobile/ Packages (Fedora COPR)]

There is also an FTP server with a full Fedora 34 workstation build with phosh: ftp://pine.warpspeed.dk/nightly/pinephone/ (Mount this with something like Nautilus)

'''username/password'''

pine/123456

'''What works, what does not work'''

WiFi, Bluetooth, SMS, Data, Calls all work!

There are still a few bugs though, and [https://xnux.eu/devices/pine64-pinephone.html#toc-feature-driver-support-matrix some features don't have driver support yet] on any PinePhone distribution.

'''How to contribute and report defects'''

Please send your bug reports to [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker].
Be sure to include logs if applicable!
Send us pull requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/pulls Github].

== Gentoo ==
[[File:GentooLogo.png|right|100px]]{{hint|Please consider cross-compiling the software on the computer.
Long compilation times and heat production can lead to a reduced lifespan of the phone.}}There are unofficial Gentoo overlays with ebuilds for the PinePhone.
There are no images - you'll be building it yourself, picking which kernel, bootloader and desktop environment you want to use.
You will be using the arm64 version of Gentoo.

'''Documentation'''

* https://stealthgun.tweakblogs.net/blog/19336/gentoo-on-a-pinephone
* https://wiki.gentoo.org/wiki/User:Dr41nU/PinePhone
* https://wiki.gentoo.org/wiki/PinePhone (incomplete)

'''Overlay locations'''

* https://gitlab.com/bingch/gentoo-overlay
* https://github.com/stealthgun/gjdwebserver-overlay

== GloDroid ==

{{Hint|There can be large intervals between release update, so available images may be outdated and do not reflect the state of the current developments.}}

A fully open source port of Android to the PinePhone.

* GitHub: [https://github.com/GloDroid GloDroid]

'''Download location'''

https://github.com/GloDroid/glodroid_manifest/releases (last release at 2021-05-20)

'''What works, what does not work'''

Works: WiFi, screen dimming, touchscreen and charging work.
Don't work: Bluetooth, Telephony, GPS, Sound

== LuneOS ==
[[File:WebOS-Ports-logo.png|right|100px]]

LuneOS is a open source mobile operating system based on [https://www.webosose.org/ webOS Open Source Edition]([https://github.com/webosose GitHub], previously known as [https://github.com/openwebos Open webOS]) by LG, comes with [https://webos-ports.org/wiki/Luna_Next Luna Next] UI, currently developed by the WebOS Ports community.

* [https://www.webos-ports.org/wiki/Main_Page WebOS Ports Wiki]
* [https://webos-ports.org/wiki/Pinephone_Info WebOS-Ports Wiki's Pinephone page]
* GitHub: [https://github.com/webOS-ports WebOS Ports]

'''Download location'''

* [http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]

It is recommended to use ''bmaptool'', which is faster than dd, and can decompress archived image files on-the-fly.

Syntax is:

bmaptool copy [from] [to]

For example:

bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-140.rootfs.wic.gz /dev/mmcblk0

.wic file can be treated as .img file when flashing. You may rename .wic file to .img when using GUI tools that require file extension to be .img.

== Maemo Leste ==
[[File:Maemoleste-logo.png|right|100px]]

[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices,
originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it.
The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices.

The new version Maemo 8 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel.
The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK].
The current version is Devuan Beowulf (Debian Buster) and has simultaneous support for both Devuan and Debian.

In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository].
To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's build]).
Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.

* [https://maemo-leste.github.io/ Maemo Leste website]
* [https://leste.maemo.org/Main_Page Maemo Leste Wiki]
** [https://leste.maemo.org/PinePhone PinePhone wiki page]
** [https://leste.maemo.org/Leste_FAQ Maemo Leste FAQ]
* GitHub: [https://github.com/maemo-leste maemo-leste]
* Twitter: [https://twitter.com/maemoleste @maemoleste]

'''Download location'''

[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds]. There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].

'''username/password'''

root/toor

You may use <code>sudo</code> directly.

'''What works, what does not work'''

For current status and workarounds, please read their [https://leste.maemo.org/PinePhone PinePhone wiki page].

'''How to contribute and report defects'''

Most discussion occurs at [ircs://irc.libera.chat:6697/#maemo-leste <code>#maemo-leste</code> on <code>irc.libera.chat</code>].
The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback.

All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki.

Submit [https://github.com/maemo-leste/bugtracker/issues bug reports] on github.
To track known issues, you may use these search terms:
[https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone],
[https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64].

Learn about
[https://leste.maemo.org/Development development],
[https://leste.maemo.org/Development/Porting_Packages porting packages],
[https://leste.maemo.org/Development/Building_Packages building packages],
[https://leste.maemo.org/Development/Tasks todo list],
and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian].
Some tasks have funding available.

== Manjaro ARM ==
[[File:Manjaro-logo.svg|right|100px]]

Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.

'''Download location'''

* Phosh: [https://github.com/manjaro-pinephone/phosh Stable] / [https://github.com/manjaro-pinephone/phosh-dev Dev]
* Plasma Mobile: [https://github.com/manjaro-pinephone/plasma-mobile Stable] / [https://github.com/manjaro-pinephone/plasma-mobile-dev Dev]
* Lomiri: [https://github.com/manjaro-pinephone/lomiri-dev Dev] (No longer maintained)

'''username/password'''

{| class="wikitable"
! Default user || <code>manjaro/123456</code>
! root || <code>root/root</code>
|}

'''What works, what does not work'''

{{Hint| Note: At the first boot, the Phosh image will be loaded at a TTY login prompt for multiple minutes.}}

See Manjaro's release announcements on their forum.
Recent ones:
[https://forum.manjaro.org/t/manjaro-arm-beta12-with-phosh-pinephone/73099 Phosh],
[https://forum.manjaro.org/t/manjaro-arm-beta5-with-plasma-mobile-pinephone/69318 Plasma] and
[https://forum.manjaro.org/t/manjaro-arm-alpha3-with-lomiri-pinephone/49923 Lomiri].

'''How to contribute and report defects'''

See the end of the [https://forum.manjaro.org/t/manjaro-arm-beta7-with-phosh-pinephone/58901 announcement].

== Mobian ==
[[File:Debian-logo.png|right|100px]]

An unofficial [https://www.debian.org Debian] build for ARM64 running with Phosh (developed by Purism, uses Wayland instead of Xorg).
The base system is pure Debian, with only the GUI applications and a few others (ModemManager, WiFi chip firmware) being built from modified sources (as well as the kernel and u-boot).
Current version is Debian Bookworm.

'''Download location'''

[https://images.mobian-project.org/pinephone/nightly/ Nightly] /
[https://images.mobian-project.org/pinephone/installer/ Installer] /
[https://images.mobian-project.org/pinephone/ Stable]

Extract the image before installing:

$ gzip -d Downloads/mobian-pinephone-*.img.gz

See the [https://wiki.mobian-project.org/doku.php?id=install project page] for specific installation instructions.

'''username/password'''

mobian/1234

'''What works, what does not work'''

See [https://gitlab.com/mobian1/mobian-recipes/-/blob/master/README.md the project's README file] or [https://wiki.mobian-project.org/doku.php?id=pinephone the wiki] for most up to date status.

Check [https://gitlab.com/groups/mobian1/-/issues bug tracker] for known issues. Questions? Ask on our [https://forum.pine64.org/showthread.php?tid=9016 thread].

'''How to contribute and report defects'''

It is recommended that you log your bug reports in [https://gitlab.com/mobian1/issues the project's issue tracker].
As a general rule, issues with third-party apps (even the default ones) should be reported upstream.
A Mobian issue would be related to getting the hardware to work on the PinePhone,
but if unsure where the issue should be reported just open a ticket or ask.
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/mobian1 Gitlab].

'''Notes'''

See [https://wiki.mobian-project.org/doku.php?id=start the wiki] for additional information regarding screen resolution, USB networking, WiFi hotspot, Chatty and the repository.

== Multi-distro demo image ==

{{Warning | This is an demo image for testing different OSes before installing a regular image. It is highly discouraged attempting to use the image productively. The kernel is shared across the different OSes and is not being updated.}}

This image allow users to try many of the above Linux distributions easily, without having to figure out how to flash them individually and juggle with many microSD cards. Also called megi's 15-in-1 multi boot image.

* Main page: https://xnux.eu/p-boot-demo/
* Git repo: https://megous.com/git/pinephone-multi-boot/
* Forum discussion: [https://forum.pine64.org/showthread.php?tid=11347 UPDATED (June 2021): 17-distro multi-boot image for Pinephone (incl. 3GiB variant)]

'''Update 2021-06-02, using megi's kernel 5.13-rc4'''

DD image to SD card and boot. This image is for 16GiB or larger SD cards, also works if flashed to eMMC.

This is also a good build for charging depleted battery. Just boot up this build with power supply connected, keep the PinePhone charging for 3 hours at power down stage.

For more info on this build, please visit its entry the "News" section of its [https://xnux.eu/p-boot-demo/ web page].

* [http://dl.xnux.eu/p-boot-multi-2021-06-02.torrent Download torrent file from author's website]
* [http://dl.xnux.eu/p-boot-multi-2021-06-02/ Download img.zst from author's website] (speed limited to 512KiB/s)
* [http://mirror.uxes.cz/dl.xnux.eu/ Download torrent and img.zst from discord user uxes' mirror]
** '''File name:''' multi.img.zst
** '''SHA-256:''' <span style="word-break: break-all">9b099cdfece3ba862348ca32af6c51a41a1d161b1d897f9928ae8be3c824a0b6</span>
** '''File Size:''' 6.57GiB

* [https://files.pine64.org/os/PinePhone/Multi/p-boot-multi-2021-06-02.img.gz Direct download img.gz from pine64.org] (re-zipped from zstd to gzip)
** '''File name:''' p-boot-multi-2021-06-02.img.gz
** '''MD5:''' 2abdaafb01dd7519f678b5a7c6538493
** '''File Size:''' 6.8GB

Due to its size, download though torrent is suggested by the author on its main page.

{{hint | '''Note about .zst archive file:'''

On Linux, you may install or compile <code>zstd</code>, and write the image to SD card by using <code>zstdcat</code> and <code>dd</code>. See the "Installation" section of its [https://xnux.eu/p-boot-demo/ web page] for command examples.

On Windows, you may use [https://github.com/mcmilk/7-Zip-zstd 7-zip-zstd], it provides different installation method in the README.md. Install and extract the .img file from the zst archive, and flash with tools like [https://sourceforge.net/projects/win32diskimager/ Win32 Disk Imager].

Also see [[PinePhone Installation Instructions]].
}}

'''username/password'''

All passwords, including root passwords, are <code>1111</code>.
sxmo username is <code>user</code>.

== Nemo Mobile ==
[[File:nemo_mobile.png|right|100px]]

Nemo Mobile is the open source build of Sailfish OS with a open source UI called [http://nemomobile.net/glacier-home/ Glacier] ([https://wiki.merproject.org/wiki/Nemo/Glacier Mer Wiki]), [http://nemomobile.net/pages/Hello_manjaro/ based on Manjaro].

* Website: [https://nemomobile.net/ Nemo Mobile UX team]
* [https://wiki.merproject.org/wiki/Nemo Mer Wiki page]

'''Download location'''

See the [https://nemomobile.net/installation/ installation page] on their website for the newest release and installation guides.

'''What works, what does not work'''

Development is now moving very fast after rebasing. For the current devel image, Wifi and Bluetooth works.

'''How to contribute and report defects'''

For the Nemo Mobile UX itself:
* GitHub issues: https://github.com/nemomobile-ux/main/issues

For hardware:
* GitHub issues: https://github.com/neochapay/nemo-device-dont_be_evil/issues

== NixOS ==
[[File:nixos.png|right|100px]]

NixOS support is handled through the Mobile NixOS project.

* Project home page: [https://mobile.nixos.org/ Mobile NixOS]
* PinePhone device page: [https://mobile.nixos.org/devices/pine64-pinephone.html Pine64 PinePhone — Mobile NixOS]
* GitHub: [https://github.com/NixOS/mobile-nixos NixOS/mobile-nixos]

There is no pre-built complete image.
For now users, are expected to follow the instructions in the [https://mobile.nixos.org/getting-started.html Getting Started page],
and [https://mobile.nixos.org/devices/pine64-pinephone.html Project's device page].

'''What works, what does not work'''

Currently, it boots, it's just as compatible as the Android-based devices are with Mobile NixOS.
It even supports a bit more since it can use WiFi.

Support for all of the hardware will be coming, this project is a breadth-first work, where the work spans multiple devices in parallel.

'''How to contribute and report defects'''

On [https://github.com/NixOS/mobile-nixos/issues the project's repository].
Please specify that you are using a PinePhone when reporting issues.
Details about contributions and donations are on the [https://nixos.org/nixos/community.html NixOS website].

== OpenMandriva Lx ==
[[File:Oma-logo-22042013_300pp.png|right|100px]]{{Hint| '''Note:''' This image is solely for testing purposes.}}OpenMandriva Lx with Plasma Mobile as UI.

'''Download location'''

The official image can be found [https://sourceforge.net/projects/openmandriva/files/release/4.2/RC/Pinephone/ at sourceforge.net].
See [https://www.openmandriva.org/en/news/article/openmandriva-lx-4-3-rc-available-for-testing here] for the offical announcement.

'''What works, what does not work'''

From the [https://www.openmandriva.org/en/news/article/openmandriva-lx-4-3-rc-available-for-testing 4.3 announcement],
in future updates (4.3 and later), "Phone calls are working, and we have rewritten the camera app to be far more useful".

== openSUSE ==
[[File:SLEM-OS-logo.png|right|100px]]

Our images use the same [https://en.opensuse.org/Portal:Tumbleweed openSUSE Tumbleweed] base as our desktop images,
except what needs to be changed for the PinePhone.
The images include <i>zypper</i> (RPM) as the default package manager,
and have access to virtually the same (open source) software as our desktop repositories,
thanks to the [https://en.opensuse.org/Portal:Factory Factory] ports.
Using [https://en.opensuse.org/SDB:DNF dnf] is possible, if preferred.

'''Download links'''

* [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz Phosh] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz.sha256 SHA-256] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz.sha256.asc SHA-256 Signature]
* [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz Plasma Mobile] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz.sha256 SHA-256] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz.sha256.asc SHA-256 Signature]

To verify the images you need to import [https://build.opensuse.org/projects/devel:ARM:Factory:Contrib:PinePhone/public_key our GPG key].
Keep on mind that the first boot may stay on black screen for about a minute - consequent boots should be faster.

You can find install instructions at [https://en.opensuse.org/HCL:PinePhone#Installing_openSUSE_in_a_Pinephone this section] in the openSUSE Wiki.

'''Username/Password'''

The login credentials are pine/1234 and root/linux.
Change (or disable) the root password once you are set up.

'''What works and what does not work'''

You can find all information about the releases of the project [https://gitlab.com/slem.os/slem.os/-/blob/master/CHANGELOG.md here].
Detailed information, tips and troubleshooting suggestions are also provided at [https://en.opensuse.org/HCL:PinePhone the openSUSE Wiki].
You will also find information in our wiki on how to report issues (Contributing section).

== postmarketOS ==
[[File:PostmarketOS-logo.png|right|100px]]

postmarketOS extends [https://www.alpinelinux.org/ Alpine Linux] to run on smartphones and other mobile devices.
It offers various user interfaces (Phosh, Plasma Mobile, Sxmo, Plasma Desktop, Gnome 3, Kodi, XFCE4, ...).

As of writing, official images are provided with Phosh, Plasma Mobile and Sxmo.
The official images come in two flavors, either as a test image to try out postmarketOS, or with the installer.

When using the installer images (recommended), it is possible to:
* encrypt the installation
* install from the SD card to eMMC

Power users may also create their own image with the distribution's install and development tool <code>pmbootstrap</code>.

Please read the detailed [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation installation instructions] in the wiki.

'''Download location'''

* [https://postmarketos.org/download/ Download page]
* [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation Flashing instructions]

'''Username/password'''

* Test images: user/147147
* When using the installer images or building an image with pmbootstrap, you set your own username and password.
** The Phosh and Plasma Mobile lock screens only support numeric keyboard, so you should '''only use numbers''' in your password.

'''What works, what does not work'''

See the [https://gitlab.com/postmarketOS/pmaports/-/issues?label_name%5B%5D=device-pine64-pinephone issue tracker].

'''How to contribute and report defects'''

[https://gitlab.com/postmarketOS/pmaports/-/issues?label_name%5B%5D=device-pine64-pinephone postmarketOS issue tracker] for PinePhone support.
See [https://wiki.postmarketos.org/wiki/Contributing postmarketOS wiki] for options to contribute.

== PureOS ==
[[File:Pureos.png|right|100px]]

{{Warning|This project is no longer under development and has been abandoned. Use [https://wiki.pine64.org/wiki/PinePhone_Software_Releases#Mobian Mobian] instead}}

{{Hint|There is no prebuilt image, you'll need a Linux environment and build the image yourself.}}

[https://www.pureos.net/ PureOS] is a user friendly, secure and freedom respecting GNU/Linux distribution based on Debian and GNOME developed by the Purism community.

* [https://tracker.pureos.net/w/ PureOS Wiki], no PinePhone page there
* Mobile-optimized apps list from the [https://tracker.pureos.net/w/pureos/mobile_optimized_apps/ Software Center in PureOS] and [https://tracker.pureos.net/w/pureos/3rd-party_mobile_optimized_apps/ 3rd party repos]
* [https://github.com/rufferson/pureos-pinephone current PinePhone PureOS repo], A script to convert Librem5 PureOS to PinePhone Pure-OS

'''Download location'''

Use [https://raw.githubusercontent.com/rufferson/pureos-pinephone/master/build_image.sh the convert script] to download and build the image from u-boot, PinePhone linux kernel and Librem5 PureOS.

Also see:
* [https://forums.puri.sm/t/successful-installation-of-pureos-on-pinephone/8741/12 Successful installation of PureOS on PinePhone - PureOS - Purism community]
* The PureOS section of [https://www.ruff.mobi/go/mobi/pine.html PinePhone page] on ruff.mobi
* An [https://gitlab.com/a-wai/debos-pinephone archived repo] for PureOS on PinePhone
* A [https://mozzwald.com/pp/ file list] with [https://mozzwald.com/pp/pureos-pinephone-build-instructions.txt pureos pinephone build instructions] on mozzwald.com

== Sailfish OS ==
[[File:Sailfish_logo.png|right|100px]]

[https://sailfishos.org/ Sailfish OS] is a Linux-based operating system based on open source projects such as [https://wiki.merproject.org/wiki/Main_Page Mer], and a closed source UI based on [https://sailfishos.org/wiki/Lipstick Lipstick].

* [https://wiki.merproject.org/wiki/Adaptations/PinePhone64 PinePhone Wiki Page] on Mer Wiki, for both Nemo Mobile and Sailfish OS.
* [https://gitlab.com/pinephone-sailfish-os/linux-kernel/ Linux kernel config repo]
* [https://gitlab.com/sailfishos-porters-ci/dont_be_evil-ci/ Sailfish OS repo]

'''Download location'''

'''Flashing script'''

The Sailfish OS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].

The script downloads the image and bootloader from the CI, extracts everything and burns it onto the SD card.
Note: The script will format and erase the SD card!

Instructions:
# Download the flashing script
# Insert a microSD card in your device
# Make the script executable: <code>chmod +x flash-it.sh</code>
# Verify that you have the <code>bsdtar</code> package installed
# Execute it: <code>./flash-it.sh</code>
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).

* When asked where to flash, type 'raw' and it will build the image on your computer. Otherwise define the path /dev/.... to flash to card or internal emmc.

'''username/password'''

Set PIN on initialization.

* Sometimes the first run stalls before the tutorial. Reboot and it will start from setting the security pin.
* The homescreen may be locked unless you boot with a sim card inserted. An old expired sim will do. '''If you do not have a SIM card on hands, do NOT set a security code on first boot.'''
* When a screen with a loading circle is displayed, just left/right swipe it away.
* If you're not familiar with Sailfish OS, pay attention to the tutorial - the interface works great, but is not immediately obvious. If you are familiar with it, you can skip the tutorial by touching all 4 corners starting top left.

'''What works, what does not work'''

See the [https://wiki.merproject.org/wiki/Adaptations/PinePhone64#Hardware_Support Hardware Support section] on the Mer Wiki's PinePhone Page.

There is a limited selection of apps available from the Jolla store, the vast majority are hosted on openrepos.net. If the Storeman app for openrepos is not preinstalled, download the RPM and click to install.

'''How to contribute and report defects'''

See the [https://wiki.merproject.org/wiki/Adaptations/PinePhone64#Installation Installation section] on the Mer Wiki's PinePhone Page for compile, build and development.

Git repo links are at the top of this OS section. other repos that may be helpful:

* [https://github.com/sailfish-on-dontbeevil GitHub project page]
* [https://github.com/sailfish-on-dontbeevil/flash-it the repo of the flash-it.sh flashing script]
* [https://build.merproject.org/project/show/nemo:devel:hw:pine:dontbeevil Mer Open Build Service page] ([https://forum.sailfishos.org/t/changes-needed-to-merge-the-project-names-to-sailfish-os/1672 Mer is being assimilated into Sailfish OS] and [https://forum.sailfishos.org/t/obs-shut-down-and-next-steps/1814 OBS is shutting down], also see [https://specs.openstack.org/openstack/fuel-specs/specs/7.0/replace-obs.html OpenStack is replacing OBS with another build system based on Jenkins], if it's related, even OBS come back under Sailfish OS, it will be different.)

See the [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues Sailfish OS wiki] for links to their forum, as well as info required when reporting an issue. See the [https://sailfishos.org/wiki/SailfishOS Sailfish OS wiki main page] for options to contribute to Sailfish OS.

'''Notes'''

OTA is supported: <code>zypper refresh && zypper update</code> as root (<code>devel-su</code> to get root access). Things that need reflash are bootloader specific at the moment. If improvements like [[Crust]] or changes of partition layout are added, then you need to reflash.

== SkiffOS ==
[[File:SkiffOS-Icon-1.png|right|100px]]

Minimal in-memory cross-compiled OS optimized for hosting multiple in parallel Docker containers.

Provides the reliability of firmware with the ease-of-use of package managers.

Upgrade over-the-air via a simple rsync script, or copying 3 files.

Uses the [http://buildroot.org Buildroot] cross-compilation tool for support for all Pine64 boards.

Use configuration packages to configure distro:

{| class="wikitable"
! core/pinephone_neon || KDE Neon via Ubuntu repositories
|-
! core/pinephone_nixos || Nixos Mobile
|-
! core/pinephone_gentoo || Gentoo with Link-time Optimization & KDE Mobile or Phosh
|-
! core/pinephone_ubports || Ubuntu Ports for PinePhone
|-
! core/pinephone_manjaro_kde || Manjaro for PinePhone: KDE variant
|-
! core/pinephone_manjaro_phosh || Manjaro for PinePhone: Phosh variant
|-
! core/pinephone_manjaro_lomiri || Manjaro for PinePhone: Lomiri variant
|}

The boot-up OS is upgraded independently from the containers.

'''Download location'''

The repository and instructions can be found [https://github.com/skiffos/SkiffOS/tree/master/configs/pine64/phone here].

== Sxmo ==

A collection of Suckless programs to create a mobile UI. Based on postmarketOS.

'''Download location'''

Sxmo images can be found [https://images.postmarketos.org/bpo/ here] (in the ''/pine64-pinephone/sxmo/'' sections respectively).

'''username/password'''

user/147147

'''How to contribute and report defects'''

Contributing information is listed [https://git.sr.ht/~mil/sxmo-docs/tree/master/CONTRIBUTING.md here].

== Ubuntu Touch ==
[[File:Ubports-logo.png|right|100px]]

A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.

Ubuntu touch is a mobile version of Ubuntu developed by the UBports community.
Installation instructions can be found on
[https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone the UBports PinePhone project].
There is also a [https://github.com/goddard/pinephone/ script] to download the latest image and flash to your PinePhone.
In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://devices.ubuntu-touch.io/installer UBports installer] GUI tool.

'''Download location'''

[https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone UBports PinePhone project]

'''username/password'''

Set up during boot

'''What works, what does not work'''

Scroll down to the bottom of [https://gitlab.com/ubports/community-ports/pinephone this page].

'''How to contribute and report defects'''

See [https://gitlab.com/ubports/community-ports/pinephone UBports gitlab page].
See [https://ubports.com/foundation/sponsors UBports website] for how to donate.

= Tools =

There are software tools, that can be booted on the PinePhone.

== JumpDrive ==

JumpDrive can be used to flash the eMMC (and the microSD card), see [[PinePhone Installation Instructions#Using JumpDrive]].

See https://github.com/dreemurrs-embedded/Jumpdrive/releases for the latest image.
Make sure to download the "PinePhone" image and to unpack the archive before flashing.

= Factory Test OS =

{{Hint|'''Note:''' The magnetometer test will fail on the new Beta Edition, as the factory image wasn't updated for it yet.}}

On the Braveheart model, there was a postmarketOS based basic Factory Test OS pre-installed on the eMMC.
The developer Martijn Braam from postmarketOS has improved the functionality of the image considerably later.
Since the 20200501 version, it is able to test all the hardware.
It also includes functionality to install a new OS to the eMMC when using with an test image that includes that OS image.
The downloadable image just does the hardware tests.
Do not flash eMMC to test your device, just dd it to microSD and test from there.
New versions are distributed as part of the postmarketOS distribution.

Links:
* [https://images.postmarketos.org/pinephone/ Software Images] (download the latest one named like pine-pinephone-yyyyMMdd-factorytestX.img.xz)
* [https://gitlab.com/MartijnBraam/factorytest Git repo]
* [https://gitlab.com/MartijnBraam/factorytest/-/blob/master/README.rst Documentation]

== Factory-loaded OS builds ==

These are different operating system builds that was preloaded in the factory with testing utility.

Download the build, extract the image and dd it to a 8 GB or larger microSD card, then insert it into the PinePhone.
After power up or reboot, you may perform and complete the test routine, or apply the build from microSD card to eMMC.

All the download links below are direct download from pine64.org.

<div style="overflow: auto;">
{| class="wikitable" style="white-space: nowrap"
! OS
! Download Link
! File Size
! MD5
|-
| Beta Edition
| [https://files.pine64.org/os/PinePhone/BetaEdition/pine64-pinephone-plamo-beta-factorytest.img.xz pine64-pinephone-plamo-beta-factorytest.img.xz]
| 1.78GB
| <code>f16bce93504a52217540ac886863a418</code>
|-
| Mobian
| [https://files.pine64.org/os/PinePhone/Mobian/pine64-pinephone-20201207-factorytest-mobian.img.xz pine64-pinephone-20201207-factorytest-mobian.img.xz]
| 1.41GB
| <code>015be381ff4e650a7fca6d4eaa90d63d</code>
|-
| KDE
| [https://files.pine64.org/os/PinePhone/KDE/pine64-pinephone-20201208-factorytest-kde.img.xz pine64-pinephone-20201208-factorytest-kde.img.xz]
| 2.28GB
| <code>32979ff17b5ec4d358ce99f1aff0c77c</code>
|-
| Manjaro
| [https://files.pine64.org/os/PinePhone/Manjaro/pine64-pinephone-20201013-manjaro-stable-20201018-factory56.img.xz pine64-pinephone-20201013-manjaro-stable-20201018-factory56.img.xz]
| 1.04GB
| <code>4edfd4dceaefdd32a3417c1727161c29</code>
|-
| postmarketOS
| [https://files.pine64.org/os/PinePhone/PostMarketOS/pine64-pinephone-20200726-phosh-v20.05-factory.img.xz pine64-pinephone-20200726-phosh-v20.05-factory.img.xz]
| 517MB
| <code>244093be2f6d728fcbd1d29114607727</code>
|-
| Ubuntu Touch
| [https://files.pine64.org/os/PinePhone/UBPorts/PinePhone-flasher-ubuntu-7b.img.gz PinePhone-flasher-ubuntu-7b.img.gz]
| 1.05GB
| <code>2d7f5271e7a281db8f1b1219bedbe131</code>
|}
</div>

= Installing other ARM64 distributions =

{{Warning|Distributions not on this page may not even boot after you follow this section. In the best case, they will be barely usable.
This is more for fun, or if you would like to port a new distribution to the PinePhone.}}

{{Hint|'''Note:''' This section uses megi's kernel releases, and not the official ones from Pine64. While it is possible to use the official (and in the future, mainline) kernel, megi provides binary releases, which makes it very easy.}}

General steps:

# Create a boot partition (from 4 MB to about 252 MB) and a root partition (from the end of boot to the end of the card) filesystem on the SD card.
# Format the boot partition with vfat, and the root partition with a supported filesystem like ext4 or f2fs.
# Extract the root filesystem from your distribution's ARM image into the root filesystem on the SD card. Do not copy the partition, copy the files instead (in archive mode, like <code>rsync -ar</code>).
# Edit <code>/etc/fstab</code> to match your partitions.
# Grab megi's kernel from https://xff.cz/kernels/, Follow the instructions in the [https://xff.cz/kernels/README README], which involves copying the kernel modules into the SD card rootfs, and writing u-boot and the bootloader.

If you would like to see examples or specific commands for how to complete these steps, see:
* [https://github.com/nikhiljha/pp-fedora-sdsetup an example for Fedora], current unofficial [#Fedora] release
* [https://xnux.eu/howtos/install-arch-linux-arm.html an example for Arch Linux] by megi

= Other Resources =
Community
* [[Main_Page#Community_and_Support|Links to the community services]]

Hardware information
* [[PinePhone|General PinePhone hardware info]] in this Pine64 wiki
* Details specific to the Braveheart Edition: [[PinePhone_v1.1_-_Braveheart|PinePhone 1.1 Braveheart hardware details]]
* Details specific to the Community Edition: [[PinePhone_v1.2|PinePhone 1.2 hardware details]]
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here] and the preceding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here]

Other software information
* [https://linux-sunxi.org/Main_Page sunxi community wiki]
* [https://xnux.eu/devices/pine64-pinephone.html megi's feature/driver support matrix]
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)] see demonstration [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube]
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]

Other
* [https://pine64.com/?post_type=product Pine64 shop]
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on Linux distributions and desktop environments on mobile devices]
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing microSD cards]

[[Category:PinePhone]]

PinePhone Software Releases

2021-09-22T08:27:23Z

RainSlide: /* Gentoo */ Remove empty lines

This page contains a list of all available OS releases for the [[PinePhone]], as well as links to other resources.

See [[PinePhone Installation Instructions]] on how to install the operating systems.<br>
However, if your phone came preloaded with software, Please see [[PinePhone Updating Instructions]].

{{Hint| '''Note:''' Some releases may not have a good setup for the backlight at low brightness.
If configured too low, the backlight shuts down completely, but the screen is still displayed and usable in bright front-light.}}

= Software Releases =

This is a list of OSes that specifically support the PinePhone.
Since PinePhone support is included in Mainline Linux, in principle, any ARM Linux OS can be used if possible required patches are included.

== Arch Linux ARM ==
[[File:Archlinux-logo.png|right|100px]]

(Unofficial) Arch Linux ARM with choice of Phosh UI, Plasma Mobile, or barebones.
Currently being maintained by the [https://danctnix.org/ DanctNIX] community (GitHub: [https://github.com/DanctNIX/danctnix danctnix], [https://github.com/dreemurrs-embedded dreemurrs-embedded]).

* GitHub: [https://github.com/dreemurrs-embedded/Pine64-Arch dreemurrs-embedded/Pine64-Arch]

'''Download location'''

Get the latest image here: https://github.com/dreemurrs-embedded/Pine64-Arch/releases

'''username/password'''

{| class="wikitable"
! Default user || <code>alarm/123456</code>
! root || <code>root/root</code>
|}

'''What works, what does not work'''

Most of the things now works, there are some minor issues with [[Crust]].

'''How to contribute and report defects'''

You may find the Discord, Matrix and Telegram of DanctNIX community at [https://github.com/DanctNIX/danctnix/blob/master/README.md#channel-list the Channel list section of DanctNIX/README.md].

Feel free to send us [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls pull requests] and report [https://github.com/dreemurrs-embedded/Pine64-Arch/issues issues] on [https://github.com/dreemurrs-embedded/Pine64-Arch GitHub].

== ExpidusOS ==

A fork of [https://voidlinux.org Void Linux] with a custom fork of XFCE called [https://github.com/ExpidusOS/genesis Gensis] as the default desktop environment, developed by [https://midstall.com/ Midstall Software].

* [https://expidusos.com ExpidusOS official website]
* [https://wiki.expidusos.com/index.php/Main_Page ExpidusOS Wiki]
* [https://discord.gg/GVfBF2w Midstall Software Discord server]
* GitHub: [https://github.com/ExpidusOS ExpidusOS]

'''Download location'''

Check the [https://expidusos.com/download download page] for that latest version, or the [https://build.expidusos.com/ image file list] for all versions, look for the file name that starts with "pinephone".

'''username/password'''

expidus/expidus

'''What works, what does not work'''

The ExpidusOS Wiki has a page detailing [https://wiki.expidusos.com/index.php/Device:PinePhone supported features].

'''How to contribute and report defects'''

Join the [https://discord.gg/GVfBF2w Discord server] or corresponding repo at GitHub ([https://github.com/orgs/ExpidusOS/repositories repo list]).

== Fedora ==
[[File:Fedora-logo.png|right|100px]]

An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and [https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/ some additional packages] to tie it all together.
It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution.

* Forum discussion: [https://forum.pine64.org/showthread.php?tid=9347 Fedora + Phosh for PinePhone]
* GitHub: [https://github.com/nikhiljha/pp-fedora-sdsetup nikhiljha/pp-fedora-sdsetup]

'''Download location'''

* [https://github.com/nikhiljha/pp-fedora-sdsetup/releases Flashable images]
* [https://github.com/nikhiljha/pp-fedora-sdsetup Build scripts]
* [https://copr.fedorainfracloud.org/coprs/njha/mobile/ Packages (Fedora COPR)]

There is also an FTP server with a full Fedora 34 workstation build with phosh: ftp://pine.warpspeed.dk/nightly/pinephone/ (Mount this with something like Nautilus)

'''username/password'''

pine/123456

'''What works, what does not work'''

WiFi, Bluetooth, SMS, Data, Calls all work!

There are still a few bugs though, and [https://xnux.eu/devices/pine64-pinephone.html#toc-feature-driver-support-matrix some features don't have driver support yet] on any PinePhone distribution.

'''How to contribute and report defects'''

Please send your bug reports to [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker].
Be sure to include logs if applicable!
Send us pull requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/pulls Github].

== Gentoo ==
[[File:GentooLogo.png|right|100px]]{{hint|Please consider cross-compiling the software on the computer.
Long compilation times and heat production can lead to a reduced lifespan of the phone.}}There are unofficial Gentoo overlays with ebuilds for the PinePhone.
There are no images - you'll be building it yourself, picking which kernel, bootloader and desktop environment you want to use.
You will be using the arm64 version of Gentoo.

'''Documentation'''

* https://stealthgun.tweakblogs.net/blog/19336/gentoo-on-a-pinephone
* https://wiki.gentoo.org/wiki/User:Dr41nU/PinePhone
* https://wiki.gentoo.org/wiki/PinePhone (incomplete)

'''Overlay locations'''

* https://gitlab.com/bingch/gentoo-overlay
* https://github.com/stealthgun/gjdwebserver-overlay

== GloDroid ==

{{Hint|There can be large intervals between release update, so available images may be outdated and do not reflect the state of the current developments.}}

A fully open source port of Android to the PinePhone.

* GitHub: [https://github.com/GloDroid GloDroid]

'''Download location'''

https://github.com/GloDroid/glodroid_manifest/releases (last release at 2021-05-20)

'''What works, what does not work'''

Works: WiFi, screen dimming, touchscreen and charging work.
Don't work: Bluetooth, Telephony, GPS, Sound

== LuneOS ==
[[File:WebOS-Ports-logo.png|right|100px]]

LuneOS is a open source mobile operating system based on [https://www.webosose.org/ webOS Open Source Edition]([https://github.com/webosose GitHub], previously known as [https://github.com/openwebos Open webOS]) by LG, comes with [https://webos-ports.org/wiki/Luna_Next Luna Next] UI, currently developed by the WebOS Ports community.

* [https://www.webos-ports.org/wiki/Main_Page WebOS Ports Wiki]
* [https://webos-ports.org/wiki/Pinephone_Info WebOS-Ports Wiki's Pinephone page]
* GitHub: [https://github.com/webOS-ports WebOS Ports]

'''Download location'''

* [http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]

It is recommended to use ''bmaptool'', which is faster than dd, and can decompress archived image files on-the-fly.

Syntax is:

bmaptool copy [from] [to]

For example:

bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-140.rootfs.wic.gz /dev/mmcblk0

.wic file can be treated as .img file when flashing. You may rename .wic file to .img when using GUI tools that require file extension to be .img.

== Maemo Leste ==
[[File:Maemoleste-logo.png|right|100px]]

[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices,
originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it.
The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices.

The new version Maemo 8 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel.
The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK].
The current version is Devuan Beowulf (Debian Buster) and has simultaneous support for both Devuan and Debian.

In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository].
To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's build]).
Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.

* [https://maemo-leste.github.io/ Maemo Leste website]
* [https://leste.maemo.org/Main_Page Maemo Leste Wiki]
** [https://leste.maemo.org/PinePhone PinePhone wiki page]
** [https://leste.maemo.org/Leste_FAQ Maemo Leste FAQ]
* GitHub: [https://github.com/maemo-leste maemo-leste]
* Twitter: [https://twitter.com/maemoleste @maemoleste]

'''Download location'''

[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds]. There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].

'''username/password'''

root/toor

You may use <code>sudo</code> directly.

'''What works, what does not work'''

For current status and workarounds, please read their [https://leste.maemo.org/PinePhone PinePhone wiki page].

'''How to contribute and report defects'''

Most discussion occurs at [ircs://irc.libera.chat:6697/#maemo-leste <code>#maemo-leste</code> on <code>irc.libera.chat</code>].
The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback.

All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki.

Submit [https://github.com/maemo-leste/bugtracker/issues bug reports] on github.
To track known issues, you may use these search terms:
[https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone],
[https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64].

Learn about
[https://leste.maemo.org/Development development],
[https://leste.maemo.org/Development/Porting_Packages porting packages],
[https://leste.maemo.org/Development/Building_Packages building packages],
[https://leste.maemo.org/Development/Tasks todo list],
and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian].
Some tasks have funding available.

== Manjaro ARM ==
[[File:Manjaro-logo.svg|right|100px]]

Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile desktop environment.

'''Download location'''

* Phosh: [https://github.com/manjaro-pinephone/phosh Stable] / [https://github.com/manjaro-pinephone/phosh-dev Dev]
* Plasma Mobile: [https://github.com/manjaro-pinephone/plasma-mobile Stable] / [https://github.com/manjaro-pinephone/plasma-mobile-dev Dev]
* Lomiri: [https://github.com/manjaro-pinephone/lomiri-dev Dev] (No longer maintained)

'''username/password'''

{| class="wikitable"
! Default user || <code>manjaro/123456</code>
! root || <code>root/root</code>
|}

'''What works, what does not work'''

{{Hint| Note: At the first boot, the Phosh image will be loaded at a TTY login prompt for multiple minutes.}}

See Manjaro's release announcements on their forum.
Recent ones:
[https://forum.manjaro.org/t/manjaro-arm-beta12-with-phosh-pinephone/73099 Phosh],
[https://forum.manjaro.org/t/manjaro-arm-beta5-with-plasma-mobile-pinephone/69318 Plasma] and
[https://forum.manjaro.org/t/manjaro-arm-alpha3-with-lomiri-pinephone/49923 Lomiri].

'''How to contribute and report defects'''

See the end of the [https://forum.manjaro.org/t/manjaro-arm-beta7-with-phosh-pinephone/58901 announcement].

== Mobian ==
[[File:Debian-logo.png|right|100px]]

An unofficial [https://www.debian.org Debian] build for ARM64 running with Phosh (developed by Purism, uses Wayland instead of Xorg).
The base system is pure Debian, with only the GUI applications and a few others (ModemManager, WiFi chip firmware) being built from modified sources (as well as the kernel and u-boot).
Current version is Debian Bookworm.

'''Download location'''

[https://images.mobian-project.org/pinephone/nightly/ Nightly] /
[https://images.mobian-project.org/pinephone/installer/ Installer] /
[https://images.mobian-project.org/pinephone/ Stable]

Extract the image before installing:

$ gzip -d Downloads/mobian-pinephone-*.img.gz

See the [https://wiki.mobian-project.org/doku.php?id=install project page] for specific installation instructions.

'''username/password'''

mobian/1234

'''What works, what does not work'''

See [https://gitlab.com/mobian1/mobian-recipes/-/blob/master/README.md the project's README file] or [https://wiki.mobian-project.org/doku.php?id=pinephone the wiki] for most up to date status.

Check [https://gitlab.com/groups/mobian1/-/issues bug tracker] for known issues. Questions? Ask on our [https://forum.pine64.org/showthread.php?tid=9016 thread].

'''How to contribute and report defects'''

It is recommended that you log your bug reports in [https://gitlab.com/mobian1/issues the project's issue tracker].
As a general rule, issues with third-party apps (even the default ones) should be reported upstream.
A Mobian issue would be related to getting the hardware to work on the PinePhone,
but if unsure where the issue should be reported just open a ticket or ask.
Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/mobian1 Gitlab].

'''Notes'''

See [https://wiki.mobian-project.org/doku.php?id=start the wiki] for additional information regarding screen resolution, USB networking, WiFi hotspot, Chatty and the repository.

== Multi-distro demo image ==

{{Warning | This is an demo image for testing different OSes before installing a regular image. It is highly discouraged attempting to use the image productively. The kernel is shared across the different OSes and is not being updated.}}

This image allow users to try many of the above Linux distributions easily, without having to figure out how to flash them individually and juggle with many microSD cards. Also called megi's 15-in-1 multi boot image.

* Main page: https://xnux.eu/p-boot-demo/
* Git repo: https://megous.com/git/pinephone-multi-boot/
* Forum discussion: [https://forum.pine64.org/showthread.php?tid=11347 UPDATED (June 2021): 17-distro multi-boot image for Pinephone (incl. 3GiB variant)]

'''Update 2021-06-02, using megi's kernel 5.13-rc4'''

DD image to SD card and boot. This image is for 16GiB or larger SD cards, also works if flashed to eMMC.

This is also a good build for charging depleted battery. Just boot up this build with power supply connected, keep the PinePhone charging for 3 hours at power down stage.

For more info on this build, please visit its entry the "News" section of its [https://xnux.eu/p-boot-demo/ web page].

* [http://dl.xnux.eu/p-boot-multi-2021-06-02.torrent Download torrent file from author's website]
* [http://dl.xnux.eu/p-boot-multi-2021-06-02/ Download img.zst from author's website] (speed limited to 512KiB/s)
* [http://mirror.uxes.cz/dl.xnux.eu/ Download torrent and img.zst from discord user uxes' mirror]
** '''File name:''' multi.img.zst
** '''SHA-256:''' <span style="word-break: break-all">9b099cdfece3ba862348ca32af6c51a41a1d161b1d897f9928ae8be3c824a0b6</span>
** '''File Size:''' 6.57GiB

* [https://files.pine64.org/os/PinePhone/Multi/p-boot-multi-2021-06-02.img.gz Direct download img.gz from pine64.org] (re-zipped from zstd to gzip)
** '''File name:''' p-boot-multi-2021-06-02.img.gz
** '''MD5:''' 2abdaafb01dd7519f678b5a7c6538493
** '''File Size:''' 6.8GB

Due to its size, download though torrent is suggested by the author on its main page.

{{hint | '''Note about .zst archive file:'''

On Linux, you may install or compile <code>zstd</code>, and write the image to SD card by using <code>zstdcat</code> and <code>dd</code>. See the "Installation" section of its [https://xnux.eu/p-boot-demo/ web page] for command examples.

On Windows, you may use [https://github.com/mcmilk/7-Zip-zstd 7-zip-zstd], it provides different installation method in the README.md. Install and extract the .img file from the zst archive, and flash with tools like [https://sourceforge.net/projects/win32diskimager/ Win32 Disk Imager].

Also see [[PinePhone Installation Instructions]].
}}

'''username/password'''

All passwords, including root passwords, are <code>1111</code>.
sxmo username is <code>user</code>.

== Nemo Mobile ==
[[File:nemo_mobile.png|right|100px]]

Nemo Mobile is the open source build of Sailfish OS with a open source UI called [http://nemomobile.net/glacier-home/ Glacier] ([https://wiki.merproject.org/wiki/Nemo/Glacier Mer Wiki]), [http://nemomobile.net/pages/Hello_manjaro/ based on Manjaro].

* Website: [https://nemomobile.net/ Nemo Mobile UX team]
* [https://wiki.merproject.org/wiki/Nemo Mer Wiki page]

'''Download location'''

See the [https://nemomobile.net/installation/ installation page] on their website for the newest release and installation guides.

'''What works, what does not work'''

Development is now moving very fast after rebasing. For the current devel image, Wifi and Bluetooth works.

'''How to contribute and report defects'''

For the Nemo Mobile UX itself:
* GitHub issues: https://github.com/nemomobile-ux/main/issues

For hardware:
* GitHub issues: https://github.com/neochapay/nemo-device-dont_be_evil/issues

== NixOS ==
[[File:nixos.png|right|100px]]

NixOS support is handled through the Mobile NixOS project.

* Project home page: [https://mobile.nixos.org/ Mobile NixOS]
* PinePhone device page: [https://mobile.nixos.org/devices/pine64-pinephone.html Pine64 PinePhone — Mobile NixOS]
* GitHub: [https://github.com/NixOS/mobile-nixos NixOS/mobile-nixos]

There is no pre-built complete image.
For now users, are expected to follow the instructions in the [https://mobile.nixos.org/getting-started.html Getting Started page],
and [https://mobile.nixos.org/devices/pine64-pinephone.html Project's device page].

'''What works, what does not work'''

Currently, it boots, it's just as compatible as the Android-based devices are with Mobile NixOS.
It even supports a bit more since it can use WiFi.

Support for all of the hardware will be coming, this project is a breadth-first work, where the work spans multiple devices in parallel.

'''How to contribute and report defects'''

On [https://github.com/NixOS/mobile-nixos/issues the project's repository].
Please specify that you are using a PinePhone when reporting issues.
Details about contributions and donations are on the [https://nixos.org/nixos/community.html NixOS website].

== OpenMandriva Lx ==
[[File:Oma-logo-22042013_300pp.png|right|100px]]

{{Hint| '''Note:''' This image is solely for testing purposes.}}

OpenMandriva Lx with Plasma Mobile as UI.

'''Download location'''

The official image can be found [https://sourceforge.net/projects/openmandriva/files/release/4.2/RC/Pinephone/ at sourceforge.net].
See [https://www.openmandriva.org/en/news/article/openmandriva-lx-4-3-rc-available-for-testing here] for the offical announcement.

'''What works, what does not work'''

From the [https://www.openmandriva.org/en/news/article/openmandriva-lx-4-3-rc-available-for-testing 4.3 announcement],
in future updates (4.3 and later), "Phone calls are working, and we have rewritten the camera app to be far more useful".

== openSUSE ==
[[File:SLEM-OS-logo.png|right|100px]]

Our images use the same [https://en.opensuse.org/Portal:Tumbleweed openSUSE Tumbleweed] base as our desktop images,
except what needs to be changed for the PinePhone.
The images include <i>zypper</i> (RPM) as the default package manager,
and have access to virtually the same (open source) software as our desktop repositories,
thanks to the [https://en.opensuse.org/Portal:Factory Factory] ports.
Using [https://en.opensuse.org/SDB:DNF dnf] is possible, if preferred.

'''Download links'''

* [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz Phosh] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz.sha256 SHA-256] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PHOSH-pinephone.aarch64.raw.xz.sha256.asc SHA-256 Signature]
* [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz Plasma Mobile] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz.sha256 SHA-256] / [https://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/PinePhone/images/openSUSE-Tumbleweed-ARM-PLAMO-pinephone.aarch64.raw.xz.sha256.asc SHA-256 Signature]

To verify the images you need to import [https://build.opensuse.org/projects/devel:ARM:Factory:Contrib:PinePhone/public_key our GPG key].
Keep on mind that the first boot may stay on black screen for about a minute - consequent boots should be faster.

You can find install instructions at [https://en.opensuse.org/HCL:PinePhone#Installing_openSUSE_in_a_Pinephone this section] in the openSUSE Wiki.

'''Username/Password'''

The login credentials are pine/1234 and root/linux.
Change (or disable) the root password once you are set up.

'''What works and what does not work'''

You can find all information about the releases of the project [https://gitlab.com/slem.os/slem.os/-/blob/master/CHANGELOG.md here].
Detailed information, tips and troubleshooting suggestions are also provided at [https://en.opensuse.org/HCL:PinePhone the openSUSE Wiki].
You will also find information in our wiki on how to report issues (Contributing section).

== postmarketOS ==
[[File:PostmarketOS-logo.png|right|100px]]

postmarketOS extends [https://www.alpinelinux.org/ Alpine Linux] to run on smartphones and other mobile devices.
It offers various user interfaces (Phosh, Plasma Mobile, Sxmo, Plasma Desktop, Gnome 3, Kodi, XFCE4, ...).

As of writing, official images are provided with Phosh, Plasma Mobile and Sxmo.
The official images come in two flavors, either as a test image to try out postmarketOS, or with the installer.

When using the installer images (recommended), it is possible to:
* encrypt the installation
* install from the SD card to eMMC

Power users may also create their own image with the distribution's install and development tool <code>pmbootstrap</code>.

Please read the detailed [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation installation instructions] in the wiki.

'''Download location'''

* [https://postmarketos.org/download/ Download page]
* [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation Flashing instructions]

'''Username/password'''

* Test images: user/147147
* When using the installer images or building an image with pmbootstrap, you set your own username and password.
** The Phosh and Plasma Mobile lock screens only support numeric keyboard, so you should '''only use numbers''' in your password.

'''What works, what does not work'''

See the [https://gitlab.com/postmarketOS/pmaports/-/issues?label_name%5B%5D=device-pine64-pinephone issue tracker].

'''How to contribute and report defects'''

[https://gitlab.com/postmarketOS/pmaports/-/issues?label_name%5B%5D=device-pine64-pinephone postmarketOS issue tracker] for PinePhone support.
See [https://wiki.postmarketos.org/wiki/Contributing postmarketOS wiki] for options to contribute.

== PureOS ==
[[File:Pureos.png|right|100px]]

{{Warning|This project is no longer under development and has been abandoned. Use [https://wiki.pine64.org/wiki/PinePhone_Software_Releases#Mobian Mobian] instead}}

{{Hint|There is no prebuilt image, you'll need a Linux environment and build the image yourself.}}

[https://www.pureos.net/ PureOS] is a user friendly, secure and freedom respecting GNU/Linux distribution based on Debian and GNOME developed by the Purism community.

* [https://tracker.pureos.net/w/ PureOS Wiki], no PinePhone page there
* Mobile-optimized apps list from the [https://tracker.pureos.net/w/pureos/mobile_optimized_apps/ Software Center in PureOS] and [https://tracker.pureos.net/w/pureos/3rd-party_mobile_optimized_apps/ 3rd party repos]
* [https://github.com/rufferson/pureos-pinephone current PinePhone PureOS repo], A script to convert Librem5 PureOS to PinePhone Pure-OS

'''Download location'''

Use [https://raw.githubusercontent.com/rufferson/pureos-pinephone/master/build_image.sh the convert script] to download and build the image from u-boot, PinePhone linux kernel and Librem5 PureOS.

Also see:
* [https://forums.puri.sm/t/successful-installation-of-pureos-on-pinephone/8741/12 Successful installation of PureOS on PinePhone - PureOS - Purism community]
* The PureOS section of [https://www.ruff.mobi/go/mobi/pine.html PinePhone page] on ruff.mobi
* An [https://gitlab.com/a-wai/debos-pinephone archived repo] for PureOS on PinePhone
* A [https://mozzwald.com/pp/ file list] with [https://mozzwald.com/pp/pureos-pinephone-build-instructions.txt pureos pinephone build instructions] on mozzwald.com

== Sailfish OS ==
[[File:Sailfish_logo.png|right|100px]]

[https://sailfishos.org/ Sailfish OS] is a Linux-based operating system based on open source projects such as [https://wiki.merproject.org/wiki/Main_Page Mer], and a closed source UI based on [https://sailfishos.org/wiki/Lipstick Lipstick].

* [https://wiki.merproject.org/wiki/Adaptations/PinePhone64 PinePhone Wiki Page] on Mer Wiki, for both Nemo Mobile and Sailfish OS.
* [https://gitlab.com/pinephone-sailfish-os/linux-kernel/ Linux kernel config repo]
* [https://gitlab.com/sailfishos-porters-ci/dont_be_evil-ci/ Sailfish OS repo]

'''Download location'''

'''Flashing script'''

The Sailfish OS image is built on Gitlab CI. The latest image can be installed using the [https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh flashing script].

The script downloads the image and bootloader from the CI, extracts everything and burns it onto the SD card.
Note: The script will format and erase the SD card!

Instructions:
# Download the flashing script
# Insert a microSD card in your device
# Make the script executable: <code>chmod +x flash-it.sh</code>
# Verify that you have the <code>bsdtar</code> package installed
# Execute it: <code>./flash-it.sh</code>
# Follow the instructions. Some commands in the script require root permissions (for example: mounting and flashing the SD card).

* When asked where to flash, type 'raw' and it will build the image on your computer. Otherwise define the path /dev/.... to flash to card or internal emmc.

'''username/password'''

Set PIN on initialization.

* Sometimes the first run stalls before the tutorial. Reboot and it will start from setting the security pin.
* The homescreen may be locked unless you boot with a sim card inserted. An old expired sim will do. '''If you do not have a SIM card on hands, do NOT set a security code on first boot.'''
* When a screen with a loading circle is displayed, just left/right swipe it away.
* If you're not familiar with Sailfish OS, pay attention to the tutorial - the interface works great, but is not immediately obvious. If you are familiar with it, you can skip the tutorial by touching all 4 corners starting top left.

'''What works, what does not work'''

See the [https://wiki.merproject.org/wiki/Adaptations/PinePhone64#Hardware_Support Hardware Support section] on the Mer Wiki's PinePhone Page.

There is a limited selection of apps available from the Jolla store, the vast majority are hosted on openrepos.net. If the Storeman app for openrepos is not preinstalled, download the RPM and click to install.

'''How to contribute and report defects'''

See the [https://wiki.merproject.org/wiki/Adaptations/PinePhone64#Installation Installation section] on the Mer Wiki's PinePhone Page for compile, build and development.

Git repo links are at the top of this OS section. other repos that may be helpful:

* [https://github.com/sailfish-on-dontbeevil GitHub project page]
* [https://github.com/sailfish-on-dontbeevil/flash-it the repo of the flash-it.sh flashing script]
* [https://build.merproject.org/project/show/nemo:devel:hw:pine:dontbeevil Mer Open Build Service page] ([https://forum.sailfishos.org/t/changes-needed-to-merge-the-project-names-to-sailfish-os/1672 Mer is being assimilated into Sailfish OS] and [https://forum.sailfishos.org/t/obs-shut-down-and-next-steps/1814 OBS is shutting down], also see [https://specs.openstack.org/openstack/fuel-specs/specs/7.0/replace-obs.html OpenStack is replacing OBS with another build system based on Jenkins], if it's related, even OBS come back under Sailfish OS, it will be different.)

See the [https://sailfishos.org/wiki/Collaborative_Development#Reporting_issues Sailfish OS wiki] for links to their forum, as well as info required when reporting an issue. See the [https://sailfishos.org/wiki/SailfishOS Sailfish OS wiki main page] for options to contribute to Sailfish OS.

'''Notes'''

OTA is supported: <code>zypper refresh && zypper update</code> as root (<code>devel-su</code> to get root access). Things that need reflash are bootloader specific at the moment. If improvements like [[Crust]] or changes of partition layout are added, then you need to reflash.

== SkiffOS ==
[[File:SkiffOS-Icon-1.png|right|100px]]

Minimal in-memory cross-compiled OS optimized for hosting multiple in parallel Docker containers.

Provides the reliability of firmware with the ease-of-use of package managers.

Upgrade over-the-air via a simple rsync script, or copying 3 files.

Uses the [http://buildroot.org Buildroot] cross-compilation tool for support for all Pine64 boards.

Use configuration packages to configure distro:

{| class="wikitable"
! core/pinephone_neon || KDE Neon via Ubuntu repositories
|-
! core/pinephone_nixos || Nixos Mobile
|-
! core/pinephone_gentoo || Gentoo with Link-time Optimization & KDE Mobile or Phosh
|-
! core/pinephone_ubports || Ubuntu Ports for PinePhone
|-
! core/pinephone_manjaro_kde || Manjaro for PinePhone: KDE variant
|-
! core/pinephone_manjaro_phosh || Manjaro for PinePhone: Phosh variant
|-
! core/pinephone_manjaro_lomiri || Manjaro for PinePhone: Lomiri variant
|}

The boot-up OS is upgraded independently from the containers.

'''Download location'''

The repository and instructions can be found [https://github.com/skiffos/SkiffOS/tree/master/configs/pine64/phone here].

== Sxmo ==

A collection of Suckless programs to create a mobile UI. Based on postmarketOS.

'''Download location'''

Sxmo images can be found [https://images.postmarketos.org/bpo/ here] (in the ''/pine64-pinephone/sxmo/'' sections respectively).

'''username/password'''

user/147147

'''How to contribute and report defects'''

Contributing information is listed [https://git.sr.ht/~mil/sxmo-docs/tree/master/CONTRIBUTING.md here].

== Ubuntu Touch ==
[[File:Ubports-logo.png|right|100px]]

A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.

Ubuntu touch is a mobile version of Ubuntu developed by the UBports community.
Installation instructions can be found on
[https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone the UBports PinePhone project].
There is also a [https://github.com/goddard/pinephone/ script] to download the latest image and flash to your PinePhone.
In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://devices.ubuntu-touch.io/installer UBports installer] GUI tool.

'''Download location'''

[https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone UBports PinePhone project]

'''username/password'''

Set up during boot

'''What works, what does not work'''

Scroll down to the bottom of [https://gitlab.com/ubports/community-ports/pinephone this page].

'''How to contribute and report defects'''

See [https://gitlab.com/ubports/community-ports/pinephone UBports gitlab page].
See [https://ubports.com/foundation/sponsors UBports website] for how to donate.

= Tools =

There are software tools, that can be booted on the PinePhone.

== JumpDrive ==

JumpDrive can be used to flash the eMMC (and the microSD card), see [[PinePhone Installation Instructions#Using JumpDrive]].

See https://github.com/dreemurrs-embedded/Jumpdrive/releases for the latest image.
Make sure to download the "PinePhone" image and to unpack the archive before flashing.

= Factory Test OS =

{{Hint|'''Note:''' The magnetometer test will fail on the new Beta Edition, as the factory image wasn't updated for it yet.}}

On the Braveheart model, there was a postmarketOS based basic Factory Test OS pre-installed on the eMMC.
The developer Martijn Braam from postmarketOS has improved the functionality of the image considerably later.
Since the 20200501 version, it is able to test all the hardware.
It also includes functionality to install a new OS to the eMMC when using with an test image that includes that OS image.
The downloadable image just does the hardware tests.
Do not flash eMMC to test your device, just dd it to microSD and test from there.
New versions are distributed as part of the postmarketOS distribution.

Links:
* [https://images.postmarketos.org/pinephone/ Software Images] (download the latest one named like pine-pinephone-yyyyMMdd-factorytestX.img.xz)
* [https://gitlab.com/MartijnBraam/factorytest Git repo]
* [https://gitlab.com/MartijnBraam/factorytest/-/blob/master/README.rst Documentation]

== Factory-loaded OS builds ==

These are different operating system builds that was preloaded in the factory with testing utility.

Download the build, extract the image and dd it to a 8 GB or larger microSD card, then insert it into the PinePhone.
After power up or reboot, you may perform and complete the test routine, or apply the build from microSD card to eMMC.

All the download links below are direct download from pine64.org.

<div style="overflow: auto;">
{| class="wikitable" style="white-space: nowrap"
! OS
! Download Link
! File Size
! MD5
|-
| Beta Edition
| [https://files.pine64.org/os/PinePhone/BetaEdition/pine64-pinephone-plamo-beta-factorytest.img.xz pine64-pinephone-plamo-beta-factorytest.img.xz]
| 1.78GB
| <code>f16bce93504a52217540ac886863a418</code>
|-
| Mobian
| [https://files.pine64.org/os/PinePhone/Mobian/pine64-pinephone-20201207-factorytest-mobian.img.xz pine64-pinephone-20201207-factorytest-mobian.img.xz]
| 1.41GB
| <code>015be381ff4e650a7fca6d4eaa90d63d</code>
|-
| KDE
| [https://files.pine64.org/os/PinePhone/KDE/pine64-pinephone-20201208-factorytest-kde.img.xz pine64-pinephone-20201208-factorytest-kde.img.xz]
| 2.28GB
| <code>32979ff17b5ec4d358ce99f1aff0c77c</code>
|-
| Manjaro
| [https://files.pine64.org/os/PinePhone/Manjaro/pine64-pinephone-20201013-manjaro-stable-20201018-factory56.img.xz pine64-pinephone-20201013-manjaro-stable-20201018-factory56.img.xz]
| 1.04GB
| <code>4edfd4dceaefdd32a3417c1727161c29</code>
|-
| postmarketOS
| [https://files.pine64.org/os/PinePhone/PostMarketOS/pine64-pinephone-20200726-phosh-v20.05-factory.img.xz pine64-pinephone-20200726-phosh-v20.05-factory.img.xz]
| 517MB
| <code>244093be2f6d728fcbd1d29114607727</code>
|-
| Ubuntu Touch
| [https://files.pine64.org/os/PinePhone/UBPorts/PinePhone-flasher-ubuntu-7b.img.gz PinePhone-flasher-ubuntu-7b.img.gz]
| 1.05GB
| <code>2d7f5271e7a281db8f1b1219bedbe131</code>
|}
</div>

= Installing other ARM64 distributions =

{{Warning|Distributions not on this page may not even boot after you follow this section. In the best case, they will be barely usable.
This is more for fun, or if you would like to port a new distribution to the PinePhone.}}

{{Hint|'''Note:''' This section uses megi's kernel releases, and not the official ones from Pine64. While it is possible to use the official (and in the future, mainline) kernel, megi provides binary releases, which makes it very easy.}}

General steps:

# Create a boot partition (from 4 MB to about 252 MB) and a root partition (from the end of boot to the end of the card) filesystem on the SD card.
# Format the boot partition with vfat, and the root partition with a supported filesystem like ext4 or f2fs.
# Extract the root filesystem from your distribution's ARM image into the root filesystem on the SD card. Do not copy the partition, copy the files instead (in archive mode, like <code>rsync -ar</code>).
# Edit <code>/etc/fstab</code> to match your partitions.
# Grab megi's kernel from https://xff.cz/kernels/, Follow the instructions in the [https://xff.cz/kernels/README README], which involves copying the kernel modules into the SD card rootfs, and writing u-boot and the bootloader.

If you would like to see examples or specific commands for how to complete these steps, see:
* [https://github.com/nikhiljha/pp-fedora-sdsetup an example for Fedora], current unofficial [#Fedora] release
* [https://xnux.eu/howtos/install-arch-linux-arm.html an example for Arch Linux] by megi

= Other Resources =
Community
* [[Main_Page#Community_and_Support|Links to the community services]]

Hardware information
* [[PinePhone|General PinePhone hardware info]] in this Pine64 wiki
* Details specific to the Braveheart Edition: [[PinePhone_v1.1_-_Braveheart|PinePhone 1.1 Braveheart hardware details]]
* Details specific to the Community Edition: [[PinePhone_v1.2|PinePhone 1.2 hardware details]]
* The postmarketOS wiki has a detailed page on the PinePhone hardware [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) here] and the preceding devkit [https://wiki.postmarketos.org/wiki/PINE64_Don%27t_be_evil_devkit_(pine64-dontbeevil) here]

Other software information
* [https://linux-sunxi.org/Main_Page sunxi community wiki]
* [https://xnux.eu/devices/pine64-pinephone.html megi's feature/driver support matrix]
* [https://megous.com/dl/tmp/README.bootui megi bootUI notes (for dualbooting/multibooting)] see demonstration [https://www.youtube.com/watch?v=ZL1GREqoqx8 on YouTube]
* [https://github.com/ayufan-pine64/boot-tools ayufan boot tools]

Other
* [https://pine64.com/?post_type=product Pine64 shop]
* [https://www.pine64.org/2020/01/24/setting-the-record-straight-pinephone-misconceptions/ Pine64 blog on blobs]
* [https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/ Martijn Braam Librem 5 comparison, especially covering openness/blobs]
* [https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html Bart Ribbers blog on Linux distributions and desktop environments on mobile devices]
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing microSD cards]

[[Category:PinePhone]]

Template:Note

2021-09-22T05:31:16Z

RainSlide: Refactor

<noinclude>

{{Template}}

A note box for showing important notes.

== Usage ==

<nowiki>{{Note|This is an note.}}</nowiki>

== Example ==

{{Note|This is an note.}}

== Technical notes ==

This template uses class <code>.template-box</code> and <code>.template-note</code> to make the output HTML more parsable.
In the future, if the [https://www.mediawiki.org/wiki/Extension:TemplateStyles TemplateStyles Extension] is installed on this MediaWiki instance,
one may move the embedded inline styles to Template Style files.

== See also ==

* [https://wiki.archlinux.org/title/Template:Note ArchWiki: Template:Note]: the template on which this one is based on
* [[Template:Hint]]
* [[Template:Warning]]

</noinclude><includeonly>

<div role="note" class="template-box template-hint" style="
display: table;
min-width: 16em;
min-height: 1.6em;
margin: .5em 0 1em;
padding: .5em 1em;
border: 1px solid #fc3;
color: #705000;
background-color: #fef6e7;
">{{{1|}}}</div>

</includeonly>

Template:Hint

2021-09-22T05:24:44Z

RainSlide: Remove empty line

<noinclude>

{{Template}}

A hint box for showing helpful hints.

== Usage ==

<nowiki>{{Hint|This is an hint.}}</nowiki>

== Example ==

{{Hint|This is an hint.}}

== Technical notes ==

This template uses class <code>.template-box</code> and <code>.template-hint</code> to make the output HTML more parsable.
In the future, if the [https://www.mediawiki.org/wiki/Extension:TemplateStyles TemplateStyles Extension] is installed on this MediaWiki instance,
one may move the embedded inline styles to Template Style files.

== See also ==

* [https://wiki.archlinux.org/title/Template:Tip ArchWiki: Template:Tip]: the template on which this one is based on
* [[Template:Note]]
* [[Template:Warning]]

</noinclude><includeonly>

<div role="note" class="template-box template-hint" style="
display: table;
min-width: 16em;
min-height: 1.6em;
margin: .5em 0 1em;
padding: .5em 1em;
border: 1px solid #9bcdfd;
color: #003670;
background-color: #d1ecfd;
">{{{1|}}}</div>

</includeonly>

Template:Hint

2021-09-22T05:20:51Z

RainSlide: Refactor again

<noinclude>

{{Template}}

A hint box for showing helpful hints.

== Usage ==

<nowiki>{{Hint|This is an hint.}}</nowiki>

== Example ==

{{Hint|This is an hint.}}

== Technical notes ==

This template uses class <code>.template-box</code> and <code>.template-hint</code> to make the output HTML more parsable.
In the future, if the [https://www.mediawiki.org/wiki/Extension:TemplateStyles TemplateStyles Extension] is installed on this MediaWiki instance,
one may move the embedded inline styles to Template Style files.

== See also ==

* [https://wiki.archlinux.org/title/Template:Tip ArchWiki: Template:Tip]: the template on which this one is based on
* [[Template:Note]]
* [[Template:Warning]]

</noinclude><includeonly>

<div role="note" class="template-box template-hint" style="
display: table;
min-width: 16em;
min-height: 1.6em;
margin: .5em 0 1em;
padding: .5em 1em;
border: 1px solid #9bcdfd;
color: #003670;
background-color: #d1ecfd;
">{{{1|}}}</div>

</includeonly>

Template:Note

2021-09-22T03:24:31Z

RainSlide: use class="warningbox"

<noinclude>
{{Template}}

== Usage ==

<pre><nowiki>{{Note|This is an note.}}</nowiki></pre>

== Example ==

{{Note|This is an note.}}
</noinclude><includeonly><div role="note" class="warningbox" style="
display: table;
min-width: 16em;
min-height: 1.6em;
margin: .5em 0;
color: #705000;
">{{{1|}}}</div></includeonly>

Template:Hint

2021-09-22T03:17:21Z

RainSlide: Use class="messagebox"

<noinclude>
{{Template}}

== Usage ==

<pre><nowiki>{{Hint|This is an hint.}}</nowiki></pre>

== Example ==

{{Hint|This is an hint.}}
</noinclude><includeonly><div class="messagebox" style="

display: table;
min-width: 16em;
min-height: 1.6em;
margin: .5em 0;
color: #003670;
background-color: #d1ecfd;
border-color: #9bcdfd;

">{{{1|}}}</div></includeonly>

Main Page

2021-09-22T03:09:12Z

RainSlide: /* Helpful Information for Beginners */ Fix

PINE64 is a community-driven company focused on creating high-quality, low-cost ARM devices and, more recently, RISC-V devices for individuals and businesses around the globe. PINE64 made its debut with the [[PINE A64|PINE A64]] single-board computer, which successfully launched on Kickstarter in 2015. PINE64 has since released a multitude of other devices, including both development boards and end-user devices.

PINE64 has a large, diverse and active community, and offers a variety of resources for hobbyists and businesses to successfully leverage various PINE64 products. To become connected and involved with the community, please see [[Main Page#Community and Support|Community and Support]] for a list of available channels and chat platforms. To learn more about PINE64, please visit the [https://www.pine64.org/ PINE64 website] and the [https://www.pine64.com/ PINE64 store]'''.

For information about PINE64 branding, including the usage of the PINE64 logo in non-commercial and other applications please read the [https://wiki.pine64.org/wiki/PINE64_brand_and_logo article about our brand and logo].

= Devices =

[[File:Marchupdate-1024x594.jpg|thumb|upright=1.2|[[Pinebook Pro]] (left) and [[PinePhone]] (right)]]

You can learn more about the following ARM and RISC-V devices manufactured by PINE64:

* Phones and tablets: '''[[PinePhone]]''', '''[[PineNote]]''' and '''[[PineTab]]'''
* Smartwatches: '''[[PineTime]]'''
* Laptops: '''[[Pinebook]]''', '''[[Pinebook Pro]]''' and '''[[Pinebook Pro Dock|Pinebook Pro Docking station]]'''
* Single-board computers: '''[[Quartz64]]''', '''[[ROCKPro64]]''', '''[[ROCK64]]''', '''[[PINE A64]]''', '''[[PINE A64-LTS/SOPine|PINE A64-LTS]]''' and '''[[PINE H64]]'''
* Clusters and modules: '''[[Clusterboard]]''', '''[[SOPine]]''', '''[[SOPine Baseboard]]''' and '''[[SOEdge]]'''
* IP cameras: '''[[PineCube]]'''
* Makerspace: '''[[Pinecil]]''', '''[[PinePower]]''', '''[[PineCone]]''' and '''[[Pinedio]]'''

= Community and Support =

Community collaboration and support is focused around the chat platforms and forums described below. As an example of the collaborative efforts of the community, recent activity has resulted in drafting a [[PineFlash|proposal]] for a new flash-based storage device. See [https://www.pine64.org/gettings-started/ Getting Started | PINE64] for tips about how to get started with the PINE64 community.

== Chat Platforms ==

PINE64 has a large and very active community. Community discussion takes place on a variety of chat platforms, which are all bridged together so the messages sent via one platform are sent to all other platforms automatically. The community chat platforms are the following:

* '''Discord''': use the [https://discordapp.com/invite/DgB7kzr invite link]. All channels are available.
* '''Matrix''' and '''Telegram''':
{| class="wikitable"
! Channel !! Matrix !! Telegram
|-
| PINE64 News || Unavailable || [https://t.me/PINE64_News @PINE64_News]
|-
| General PINE64 chat || [https://riot.im/app/#/room/#pine64:matrix.org #pine64:matrix.org] || [https://t.me/mtrx_pine64 @mtrx_pine64]
|-
| PINE A64 LTS & SOPine || [https://riot.im/app/#/room/#pine64sopine:matrix.org #pine64sopine:matrix.org] || [https://t.me/pine64sopine @pine64sopine]
|-
| ROCK64 / ROCKPro64 || [https://riot.im/app/#/room/#rock64:matrix.org #rock64:matrix.org] || [https://t.me/mtrx_rock64 @mtrx_rock64]
|-
| Quartz64 || [https://riot.im/app/#/room/#quartz64:matrix.org #quartz64:matrix.org] || [https://t.me/joinchat/Vq50DXkH31e0_i-f Quartz64]
|-
| Quartz64 Development || [https://riot.im/app/#/room/#quartz64-dev:matrix.org #quartz64-dev:matrix.org] || [https://t.me/q64dev @q64dev]
|-
| Pinebook and Pinebook Pro || [https://riot.im/app/#/room/#pinebook:matrix.org #pinebook:matrix.org] || [https://t.me/mtx_pinebook @mtx_pinebook]
|-
| PinePhone || [https://riot.im/app/#/room/#pinephone:matrix.org #pinephone:matrix.org] || [https://t.me/pinephone @pinephone]
|-
| PineNote || [https://riot.im/app/#/room/#pinenote:matrix.org #pinenote:matrix.org] || [https://t.me/pinenote @PineNote]
|-
| PineTab || [https://riot.im/app/#/room/#pinetab:pine64.org #pinetab:matrix.org] || [https://t.me/PineTab @PineTab]
|-
| PineTime || [https://riot.im/app/#/room/#pinetime:matrix.org #pinetime:matrix.org] || [https://t.me/pinetime @pinetime]
|-
| PineTime Development || [https://riot.im/app/#/room/#pinetime-dev:matrix.org #pinetime-dev:matrix.org] || [https://t.me/pinetime_dev @pinetime_dev]
|-
| Accessories || Unavailable || Unavailable
|-
| Pinecil || [https://riot.im/app/#/room/#pinecil:matrix.org #pinecil:matrix.org] || [https://t.me/joinchat/Kmi2S1iej-_4DgrVf3jjnQ Pinecil]
|-
| Pinetalk || Unavailable || Unavailable
|-
| Cube || [https://riot.im/app/#/room/#cube64:matrix.org #cube64:matrix.org] || Unavailable
|-
| Nutcracker || [https://riot.im/app/#/room/#pine64-nutcracker:matrix.org #pine64-nutcracker:matrix.org] || [https://t.me/joinchat/Kmi2S0nOsT240emHk-aO6g Nutcracker]
|-
| LoRa || [https://riot.im/app/#/room/#pinelora:matrix.org #pinelora:matrix.org] || [https://t.me/pine64lora @pine64lora]
|-
| Off-topic || [https://riot.im/app/#/room/#offtopic64:matrix.org #offtopic64:matrix.org] || [https://t.me/pine64offtopic @pine64offtopic]
|-
|}
* '''IRC''': The IRC channels can be reached via <i>irc.pine64.org</i>. Support requests via IRC are discouraged, users are advised to look into the Matrix communication protocol as contemporary solution instead.

== Forums ==

PINE64 runs an official forum powered by the open-source forum server software MyBB. The forum can be used to report issues, help out other users, offer findings and new information and more. Users can also engage directly with the community and the developers of partner projects, as well as with the PINE64 members.

The official PINE64 forum can be accessed here:
* [https://forum.pine64.org/ Official PINE64 Forum]

Also, these are the official Subreddits:

* [https://www.reddit.com/r/PINE64official/ Official PINE64 Reddit]
* [https://www.reddit.com/r/PinePhoneOfficial/ Official PinePhone Reddit]

= Helpful Information for Beginners =

* '''[[NOOB | Getting started]]''': Basic information on setting up and handling PINE64 devices, such as how to write (flash) OS images to microSD cards and eMMC modules
* '''[[Notes | PINE64 Wiki contributing Notes]]''': Some notes on prioritized and suggested writing or editing to this Wiki, as well as long-term goals and wiki housekeeping tasks.
* '''[[:Category:Guide]]''': Lists other guide pages than those two above, some are delicated to spicific devices.

Main Page

2021-09-22T03:02:19Z

RainSlide: /* Helpful Information for Beginners */ Add Notes and Category:Guide

PINE64 is a community-driven company focused on creating high-quality, low-cost ARM devices and, more recently, RISC-V devices for individuals and businesses around the globe. PINE64 made its debut with the [[PINE A64|PINE A64]] single-board computer, which successfully launched on Kickstarter in 2015. PINE64 has since released a multitude of other devices, including both development boards and end-user devices.

PINE64 has a large, diverse and active community, and offers a variety of resources for hobbyists and businesses to successfully leverage various PINE64 products. To become connected and involved with the community, please see [[Main Page#Community and Support|Community and Support]] for a list of available channels and chat platforms. To learn more about PINE64, please visit the [https://www.pine64.org/ PINE64 website] and the [https://www.pine64.com/ PINE64 store]'''.

For information about PINE64 branding, including the usage of the PINE64 logo in non-commercial and other applications please read the [https://wiki.pine64.org/wiki/PINE64_brand_and_logo article about our brand and logo].

= Devices =

[[File:Marchupdate-1024x594.jpg|thumb|upright=1.2|[[Pinebook Pro]] (left) and [[PinePhone]] (right)]]

You can learn more about the following ARM and RISC-V devices manufactured by PINE64:

* Phones and tablets: '''[[PinePhone]]''', '''[[PineNote]]''' and '''[[PineTab]]'''
* Smartwatches: '''[[PineTime]]'''
* Laptops: '''[[Pinebook]]''', '''[[Pinebook Pro]]''' and '''[[Pinebook Pro Dock|Pinebook Pro Docking station]]'''
* Single-board computers: '''[[Quartz64]]''', '''[[ROCKPro64]]''', '''[[ROCK64]]''', '''[[PINE A64]]''', '''[[PINE A64-LTS/SOPine|PINE A64-LTS]]''' and '''[[PINE H64]]'''
* Clusters and modules: '''[[Clusterboard]]''', '''[[SOPine]]''', '''[[SOPine Baseboard]]''' and '''[[SOEdge]]'''
* IP cameras: '''[[PineCube]]'''
* Makerspace: '''[[Pinecil]]''', '''[[PinePower]]''', '''[[PineCone]]''' and '''[[Pinedio]]'''

= Community and Support =

Community collaboration and support is focused around the chat platforms and forums described below. As an example of the collaborative efforts of the community, recent activity has resulted in drafting a [[PineFlash|proposal]] for a new flash-based storage device. See [https://www.pine64.org/gettings-started/ Getting Started | PINE64] for tips about how to get started with the PINE64 community.

== Chat Platforms ==

PINE64 has a large and very active community. Community discussion takes place on a variety of chat platforms, which are all bridged together so the messages sent via one platform are sent to all other platforms automatically. The community chat platforms are the following:

* '''Discord''': use the [https://discordapp.com/invite/DgB7kzr invite link]. All channels are available.
* '''Matrix''' and '''Telegram''':
{| class="wikitable"
! Channel !! Matrix !! Telegram
|-
| PINE64 News || Unavailable || [https://t.me/PINE64_News @PINE64_News]
|-
| General PINE64 chat || [https://riot.im/app/#/room/#pine64:matrix.org #pine64:matrix.org] || [https://t.me/mtrx_pine64 @mtrx_pine64]
|-
| PINE A64 LTS & SOPine || [https://riot.im/app/#/room/#pine64sopine:matrix.org #pine64sopine:matrix.org] || [https://t.me/pine64sopine @pine64sopine]
|-
| ROCK64 / ROCKPro64 || [https://riot.im/app/#/room/#rock64:matrix.org #rock64:matrix.org] || [https://t.me/mtrx_rock64 @mtrx_rock64]
|-
| Quartz64 || [https://riot.im/app/#/room/#quartz64:matrix.org #quartz64:matrix.org] || [https://t.me/joinchat/Vq50DXkH31e0_i-f Quartz64]
|-
| Quartz64 Development || [https://riot.im/app/#/room/#quartz64-dev:matrix.org #quartz64-dev:matrix.org] || [https://t.me/q64dev @q64dev]
|-
| Pinebook and Pinebook Pro || [https://riot.im/app/#/room/#pinebook:matrix.org #pinebook:matrix.org] || [https://t.me/mtx_pinebook @mtx_pinebook]
|-
| PinePhone || [https://riot.im/app/#/room/#pinephone:matrix.org #pinephone:matrix.org] || [https://t.me/pinephone @pinephone]
|-
| PineNote || [https://riot.im/app/#/room/#pinenote:matrix.org #pinenote:matrix.org] || [https://t.me/pinenote @PineNote]
|-
| PineTab || [https://riot.im/app/#/room/#pinetab:pine64.org #pinetab:matrix.org] || [https://t.me/PineTab @PineTab]
|-
| PineTime || [https://riot.im/app/#/room/#pinetime:matrix.org #pinetime:matrix.org] || [https://t.me/pinetime @pinetime]
|-
| PineTime Development || [https://riot.im/app/#/room/#pinetime-dev:matrix.org #pinetime-dev:matrix.org] || [https://t.me/pinetime_dev @pinetime_dev]
|-
| Accessories || Unavailable || Unavailable
|-
| Pinecil || [https://riot.im/app/#/room/#pinecil:matrix.org #pinecil:matrix.org] || [https://t.me/joinchat/Kmi2S1iej-_4DgrVf3jjnQ Pinecil]
|-
| Pinetalk || Unavailable || Unavailable
|-
| Cube || [https://riot.im/app/#/room/#cube64:matrix.org #cube64:matrix.org] || Unavailable
|-
| Nutcracker || [https://riot.im/app/#/room/#pine64-nutcracker:matrix.org #pine64-nutcracker:matrix.org] || [https://t.me/joinchat/Kmi2S0nOsT240emHk-aO6g Nutcracker]
|-
| LoRa || [https://riot.im/app/#/room/#pinelora:matrix.org #pinelora:matrix.org] || [https://t.me/pine64lora @pine64lora]
|-
| Off-topic || [https://riot.im/app/#/room/#offtopic64:matrix.org #offtopic64:matrix.org] || [https://t.me/pine64offtopic @pine64offtopic]
|-
|}
* '''IRC''': The IRC channels can be reached via <i>irc.pine64.org</i>. Support requests via IRC are discouraged, users are advised to look into the Matrix communication protocol as contemporary solution instead.

== Forums ==

PINE64 runs an official forum powered by the open-source forum server software MyBB. The forum can be used to report issues, help out other users, offer findings and new information and more. Users can also engage directly with the community and the developers of partner projects, as well as with the PINE64 members.

The official PINE64 forum can be accessed here:
* [https://forum.pine64.org/ Official PINE64 Forum]

Also, these are the official Subreddits:

* [https://www.reddit.com/r/PINE64official/ Official PINE64 Reddit]
* [https://www.reddit.com/r/PinePhoneOfficial/ Official PinePhone Reddit]

= Helpful Information for Beginners =

* '''[[NOOB | Getting started]]''': Basic information on setting up and handling PINE64 devices, such as how to write (flash) OS images to microSD cards and eMMC modules
* '''[[Notes | PINE64 Wiki contributing Notes]]''': Some notes on prioritized and suggested writing or editing to this Wiki, as well as Long-term goals and wiki housekeeping tasks.
* '''[[Category:Guide]]''': Lists other guide pages than those two above, some are delicated to spicific devices.