Difference between revisions of "PinePhone Software Releases"

From PINE64
Jump to navigation Jump to search
(→‎Gentoo: wiki style)
(+word)
(47 intermediate revisions by 13 users not shown)
Line 1: Line 1:
This page contains a list of all available releases for the [[PinePhone]] as well as links to other resources.
This page contains a list of all available OS releases for the regular [[PinePhone]], as well as links to other resources.


See [[PinePhone Installation Instructions]] on how to install the operating systems. However, if your phone came preloaded with software, Please see [[PinePhone Updating Instructions]]
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.}}
{{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 =
= Software Releases =


This is a list of OSes that specifically support the PinePhone, but as support is included in Mainline Linux, in principle any ARM Linux OS can be used, if possible required patches are included.
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 ==
== DanctNIX (Arch Linux ARM) ==
[[File:Archlinux-logo.png|right|100px]]
[[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 1] [https://github.com/dreemurrs-embedded 2]).
(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'''
'''Download location'''


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


'''username/password'''
'''username/password'''


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


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


Most of the things now works, there are some minor issues with [[Crust]].
Most of the things should work.


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


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].
* 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 ==
== ExpidusOS ==


A fork of [https://voidlinux.org Void Linux] with a custom fork of XFCE as the default desktop environment, developed by [https://midstall.com/ Midstall Software].
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://expidusos.com ExpidusOS official website]
* [https://wiki.expidusos.com/index.php/Main_Page ExpidusOS Wiki]
* [https://wiki.expidusos.com/index.php/Main_Page ExpidusOS Wiki]
* [https://discord.gg/GVfBF2w Midstall Software Discord server]
* [https://discord.gg/GVfBF2w Midstall Software Discord server]
* GitHub: [https://github.com/ExpidusOS ExpidusOS]


'''Download location'''
'''Download location'''
Line 52: Line 67:
'''How to contribute and report defects'''
'''How to contribute and report defects'''


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


== Fedora ==
== Fedora ==
[[File:Fedora-logo.png|right|100px]]
[[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.
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.


See [https://forum.pine64.org/showthread.php?tid=9347 this thread in the forum].
* 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'''
'''Download location'''


[https://github.com/nikhiljha/pp-fedora-sdsetup/releases/ flashable images] or [https://github.com/nikhiljha/pp-fedora-sdsetup/ build scripts]
* [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 full a full Fedora 34 workstation build with phosh: ftp://pine.warpspeed.dk/nightly/pinephone/ (Mount this with something like Nautilus)
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'''
'''username/password'''


On github images use:
pine/123456
pine/123456


On Nightly images from FTP use
pine/1111
'''What works, what does not work'''
'''What works, what does not work'''


WiFi, Bluetooth, SMS, Data, Calls all 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.  
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'''
'''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 merge requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/ Github].
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 ==
== Gentoo ==
[[File:GentooLogo.png|right|100px]]
[[File:GentooLogo.png|right|100px]]


{{note|Please consider cross-compiling the software on the computer. Long compilation times and heat production can lead to a reduced lifespan of the phone.}}
{{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.
There are unofficial Gentoo overlays with ebuilds for the PinePhone.
You will be using the arm64 version of Gentoo.  
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'''
'''Documentation'''


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


'''Overlay locations'''
'''Overlay locations'''


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


https://github.com/stealthgun/gjdwebserver-overlay/
== GloDroid ==


== 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.}}


{{warning|Available images are outdated and do not reflect the state of the current developments.}}
A fully open source port of Android to the PinePhone.


A fully open source port of Android to the PinePhone
GitHub: [https://github.com/GloDroid/ GloDroid]


'''Download location'''
'''Download location'''


https://github.com/GloDroid/glodroid_manifest/releases
Stable image (last release at 2021-11-25)
 
[https://github.com/GloDroid/glodroid_manifest/releases GloDroid]


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


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


== LuneOS ==
== LuneOS ==
[[File:WebOS-Ports-logo.png|right|100px]]
[[File:Luneos-logo-256.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.
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://www.webos-ports.org/wiki/Main_Page WebOS Ports Wiki]
* [https://github.com/webOS-ports WebOS Ports GitHub]
* [https://webos-ports.org/wiki/Pinephone_Info WebOS-Ports Wiki's Pinephone page]
* [https://webos-ports.org/wiki/Pinephone_Info WebOS-Ports Wiki's Pinephone page]
* GitHub: [https://github.com/webOS-ports WebOS Ports]


'''Download location'''
'''Download location'''


[http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]
* [https://github.com/webOS-ports/meta-pine64-luneos/releases LuneOS test images for PinePhone]


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


Syntax is:
Syntax is:


<code>bmaptool copy [from] [to]</code>
bmaptool copy [from] [to]


For example:
For example:


<code>bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-140.rootfs.wic.gz /dev/mmcblk0</code>
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 .img files.
.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 ==
== Maemo Leste ==
[[File:Maemoleste-logo.png|right|100px]]
[[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.  
[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.


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 buildd]). Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.
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.


More detailed information can be found on [https://leste.maemo.org/Main_Page the Maemo Leste wiki], or follow [https://maemo-leste.github.io/ announcements on their website], and check out [https://leste.maemo.org/Leste_FAQ Frequently Asked Questions].  
* [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'''
'''Download location'''
Line 160: Line 203:
root/toor
root/toor


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


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


For current status and workarounds please read their [https://leste.maemo.org/PinePhone PinePhone wiki page], and update as necessary (make sure to notify them of new issues by leaving a report on the project's  Github page, see below).
For current status and workarounds, please read their [https://leste.maemo.org/PinePhone PinePhone wiki page].


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


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


All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki. You should [https://github.com/maemo-leste/bugtracker/issues submit 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.
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 ==
== Manjaro ARM ==
Line 179: Line 236:
'''Download location'''
'''Download location'''


*Phosh: [https://github.com/manjaro-pinephone/phosh Stable] / [https://github.com/manjaro-pinephone/phosh-dev Dev]
* 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]
* 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)
* Lomiri: [https://github.com/manjaro-pinephone/lomiri-dev Dev] (No longer maintained)


'''username/password'''
'''username/password'''


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


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


{{Hint| Note: The Phosh image the boot will load at a TTY login prompt for multiple minutes at the first boot.}}
{{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.
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'''
'''How to contribute and report defects'''
Line 204: Line 263:
[[File:Debian-logo.png|right|100px]]
[[File:Debian-logo.png|right|100px]]


An unofficial [https://www.debian.org Debian] build for ARM64 running with the Phosh user interface (developed by Purism, Phosh 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.
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'''
'''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]
[https://images.mobian-project.org/pinephone/weekly/ Weekly] /
[https://images.mobian-project.org/pinephone/installer/ Installer] /
[https://images.mobian-project.org/pinephone/ Stable]


Don't forget to extract the image before installing:
Extract the image before installing:


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


See the [https://wiki.mobian-project.org/doku.php?id=install project page] for specific installation instructions.
See the [https://wiki.mobian-project.org/doku.php?id=install project page] for specific installation instructions.
Line 222: Line 285:
'''What works, what does not work'''
'''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.
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].
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].
Line 228: Line 291:
'''How to contribute and report defects'''
'''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].
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'''
'''Notes'''
Line 236: Line 303:
== Multi-distro demo image ==
== 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.}}
{{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.
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.
Line 242: Line 309:
* Main page: https://xnux.eu/p-boot-demo/
* Main page: https://xnux.eu/p-boot-demo/
* Git repo: https://megous.com/git/pinephone-multi-boot/
* Git repo: https://megous.com/git/pinephone-multi-boot/
* [https://forum.pine64.org/showthread.php?tid=11347 Discussion on the forum]
* 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'''
'''Update 2021-06-02, using megi's kernel 5.13-rc4'''
Line 268: Line 335:
{{hint | '''Note about .zst archive file:'''
{{hint | '''Note about .zst archive file:'''


On Linux, you may install or compile package <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 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].
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]].
Also see [[PinePhone Installation Instructions]].
}}


'''username/password'''
'''username/password'''
Line 285: Line 349:
[[File:nemo_mobile.png|right|100px]]
[[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]. See their website [https://nemomobile.net/ Nemo Mobile UX team] and [https://wiki.merproject.org/wiki/Nemo Mer Wiki page].
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'''
'''Download location'''


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


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


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


'''How to contribute and report defects'''
'''How to contribute and report defects'''
Line 310: Line 375:
NixOS support is handled through the Mobile NixOS project.
NixOS support is handled through the Mobile NixOS project.


* [https://mobile.nixos.org/ Project home page]
* 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]


* [https://github.com/NixOS/mobile-nixos Source code repository]
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],
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 on [https://mobile.nixos.org/devices/pine64-pinephone-braveheart.html the device's page].
and [https://mobile.nixos.org/devices/pine64-pinephone.html Project's device page].


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


This information may change, but 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.
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.
Support for all of the hardware will be coming, this project is a breadth-first work, where the work spans multiple devices in parallel.
Line 324: Line 392:
'''How to contribute and report defects'''
'''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].
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 ==
== OpenMandriva Lx ==
Line 335: Line 405:
'''Download location'''
'''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.
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'''
'''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".
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 ==
== openSUSE ==
[[File:SLEM-OS-logo.png|right|100px]]
[[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.
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'''
'''Download links'''
Line 351: Line 428:
* [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]
* [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.
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.
You can find install instructions at [https://en.opensuse.org/HCL:PinePhone#Installing_openSUSE_in_a_Pinephone this section] in the openSUSE Wiki.
Line 357: Line 435:
'''Username/Password'''
'''Username/Password'''


The login credentials are pine/1234 and root/linux. Change (or disable) the root password once you are set up.
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'''
'''What works and what does not work'''
Line 371: Line 450:
It offers various user interfaces (Phosh, Plasma Mobile, Sxmo, Plasma Desktop, Gnome 3, Kodi, XFCE4, ...).
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.
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:
When using the installer images (recommended), it is possible to:
Line 388: Line 468:
'''Username/password'''
'''Username/password'''


user/147147
* Test images: user/147147
 
* When using the installer images or building an image with pmbootstrap, you set your own username and password.
This is for the test images only - 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 require your password, but they only present a numeric keyboard, so you should use '''only''' numbers in your password.
** The Phosh and Plasma Mobile lock screens only support numeric keyboard, so you should '''only use numbers''' in your password.


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


See the [https://gitlab.com/postmarketOS/pmaports/-/issues?label_name%5B%5D=device-pine64-pinephone issue tracker].
See the [https://gitlab.com/postmarketOS/pmaports/-/issues?label_name%5B%5D=device-pine64-pinephone issue tracker].
Line 399: Line 478:
'''How to contribute and report defects'''
'''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.
[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 ==
== PureOS ==
[[File:Pureos.png|right|100px]]
[[File:Pureos.png|right|100px]]


{{Warning|This project is no longer under development and has been abandoned. Similar experience can be achived by using [https://wiki.pine64.org/wiki/PinePhone_Software_Releases#Mobia Mobian]}}
{{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.}}
{{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 Buster and GNOME developed by the Purism community.
[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
* [https://tracker.pureos.net/w/ PureOS Wiki], no PinePhone page there
Line 439: Line 519:
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 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!
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:
Instructions:
Line 450: Line 531:


* 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.  
* 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'''
'''username/password'''
Line 482: Line 562:


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.
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 ==
== SkiffOS ==
[[File:SkiffOS-Icon-1.png|right|100px]]
[[File:SkiffOS-Icon-1.png|right|100px]]
Line 495: Line 581:


Use configuration packages to configure distro:
Use configuration packages to configure 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


{| 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.
The boot-up OS is upgraded independently from the containers.
Line 512: Line 608:
== Sxmo ==
== Sxmo ==


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


'''Download location'''
'''Download location'''


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


'''username/password'''
'''username/password'''
Line 524: Line 620:
'''How to contribute and report defects'''
'''How to contribute and report defects'''


All the contributing information is [https://git.sr.ht/~mil/sxmo-docs/tree/master/CONTRIBUTING.md here].
Contributing information is listed [https://man.sr.ht/~anjan/sxmo-docs-stable/CONTRIBUTING.md here].


== Ubuntu Touch ==
== Ubuntu Touch ==
Line 531: Line 627:
A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.
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.
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'''
'''Download location'''
Line 543: Line 643:
'''What works, what does not work'''
'''What works, what does not work'''


Scroll down to the bottom of [https://gitlab.com/ubports/community-ports/pinephone this page].
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'''
'''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.
See [https://gitlab.com/ubports/community-ports/pinephone UBports gitlab page].
See [https://ubports.com/foundation/sponsors UBports website] for how to donate.


= Tools =
= Tools =
Line 557: Line 658:
JumpDrive can be used to flash the eMMC (and the microSD card), see [[PinePhone Installation Instructions#Using 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.
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 =
= Factory Test OS =
Line 563: Line 665:
{{Hint|'''Note:''' The magnetometer test will fail on the new Beta Edition, as the factory image wasn't updated for it yet.}}
{{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.
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:
Links:
[https://images.postmarketos.org/pinephone/ Software Images] (download the latest one that is marked pine-pinephone-YYYYMMDD-factorytestX.img.xz)
* [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 Git repo]
[https://gitlab.com/MartijnBraam/factorytest/-/blob/master/README.rst Documentation]
* [https://gitlab.com/MartijnBraam/factorytest/-/blob/master/README.rst Documentation]


== Factory-loaded OS builds ==
== Factory-loaded OS builds ==
Line 574: Line 682:
These are different operating system builds that was preloaded in the factory with testing utility.
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 the microSD and then insert it into the phone. Power up the PinePhone, perform and complete the test routine, then apply the build from microSD card to eMMC.
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.


dd the image on a 8 GB microSD card or larger.
All the download links below are direct download from pine64.org.


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


= Installing other ARM64 distributions =
= 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.}}
{{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.}}
{{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.}}


If you would like to see specific commands for how to complete these steps, see:
General steps:
* https://github.com/nikhiljha/pp-fedora-sdsetup (an example for Fedora) or
* https://xnux.eu/howtos/install-arch-linux-arm.html (an example for Arch Linux).


General step:
# 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.
 
# Create a boot (from 4 MB to about 252 MB) and root (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.
# 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 (in archive mode: like <code>rsync -ar</code>).
# 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.
# Edit <code>/etc/fstab</code> to match your partitions.
# Grab megi's kernel from https://xff.cz/kernels/
# 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.
# Follow the README instructions, 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 =
= Other Resources =
Line 656: Line 767:
* [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://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]
* [https://www.jeffgeerling.com/blog/2019/a2-class-microsd-cards-offer-no-better-performance-raspberry-pi Jeff Geerling on testing microSD cards]


[[Category:PinePhone]]
[[Category:PinePhone]]

Revision as of 20:27, 27 January 2022

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

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

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)

Archlinux-logo.png

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

Download location

Get both stable and test builds at GitHub releases.

username/password

Default user alarm/123456
root root/root

What works, what does not work

Most of the things should work.

How to contribute and report defects

ExpidusOS

A fork of Void Linux with a custom fork of XFCE called Gensis as the default desktop environment, developed by Midstall Software.

Download location

Check the download page for that latest version, or the 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 supported features.

How to contribute and report defects

Join the Discord server or corresponding repo at GitHub (repo list).

Fedora

Fedora-logo.png

An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and 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.

Download location

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 some features don't have driver support yet on any PinePhone distribution.

How to contribute and report defects

Please send your bug reports to the project's issue tracker. Be sure to include logs if applicable! Send us pull requests on Github.


Gentoo

GentooLogo.png
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

Overlay locations

GloDroid

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: GloDroid

Download location

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

GloDroid

What works, what does not work

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

LuneOS

Luneos-logo-256.png

LuneOS is a open source mobile operating system based on webOS Open Source Edition(GitHub, previously known as Open webOS) by LG, comes with Luna Next UI, currently developed by the WebOS Ports community.

Download location

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

Maemoleste-logo.png

Maemo is a trimmed-down version of Debian for mobile devices, originally a collaboration between Nokia and many open source projects (the 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 Devuan (Debian without systemd) and runs the mainline Linux kernel. The default user interface stack is Hildon, Xorg, Matchbox WM, and 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 announced a community repository. To keep updated they use automation in their package maintenance with jenkins (similar to 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.

Download location

Maemo Leste test builds. There is also an image builder, see their wiki for instructions on how to build a custom image.

username/password

root/toor

You may use sudo directly.

What works, what does not work

For current status and workarounds, please read their PinePhone wiki page.

How to contribute and report defects

Most discussion occurs at #maemo-leste on irc.libera.chat. The Maemo website also has an ongoing forum thread for feedback.

All other contact information is listed on the main page of the Maemo wiki.

Submit bug reports on github. To track known issues, you may use these search terms: pinephone, pine64.

Learn about development, porting packages, building packages, todo list, and general info on how to package for Debian. Some tasks have funding available.

Manjaro ARM

Error creating thumbnail: File missing

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

Download location

username/password

Default user manjaro/123456
root root/root

What works, what does not work

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 announcement.

Mobian

Debian-logo.png

An unofficial 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

Weekly / Installer / Stable

Extract the image before installing:

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

See the project page for specific installation instructions.

username/password

mobian/1234

What works, what does not work

See the project's README file or the wiki for most up to date status.

Check bug tracker for known issues. Questions? Ask on our thread.

How to contribute and report defects

It is recommended that you log your bug reports in 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 Gitlab.

Notes

See 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.

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 web page.

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

Note about .zst archive file:

On Linux, you may install or compile zstd, and write the image to SD card by using zstdcat and dd. See the "Installation" section of its web page for command examples.

On Windows, you may use 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 Win32 Disk Imager.

Also see PinePhone Installation Instructions.

username/password

All passwords, including root passwords, are 1111. sxmo username is user.

Nemo Mobile

Nemo mobile.png

Nemo Mobile is the open source build of Sailfish OS with a open source UI called Glacier (Mer Wiki), based on Manjaro.

Download location

See the 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:

For hardware:

NixOS

NixOS support is handled through the Mobile NixOS project.

There is no pre-built complete image. For now users, are expected to follow the instructions in the Getting Started page, and 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 the project's repository. Please specify that you are using a PinePhone when reporting issues. Details about contributions and donations are on the NixOS website.

OpenMandriva Lx

Oma-logo-22042013 300pp.png
Note: This image is solely for testing purposes.

OpenMandriva Lx with Plasma Mobile as UI.

Download location

The official image can be found at sourceforge.net. See here for the offical announcement.

What works, what does not work

From the 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

SLEM-OS-logo.png

Our images use the same openSUSE Tumbleweed base as our desktop images, except what needs to be changed for the PinePhone. The images include zypper (RPM) as the default package manager, and have access to virtually the same (open source) software as our desktop repositories, thanks to the Factory ports. Using dnf is possible, if preferred.

Download links

To verify the images you need to import 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 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 here. Detailed information, tips and troubleshooting suggestions are also provided at the openSUSE Wiki. You will also find information in our wiki on how to report issues (Contributing section).

postmarketOS

postmarketOS extends 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 pmbootstrap.

Please read the detailed installation instructions in the wiki.

Download location

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 issue tracker.

How to contribute and report defects

postmarketOS issue tracker for PinePhone support. See postmarketOS wiki for options to contribute.

PureOS

Warning: This project is no longer under development and has been abandoned. Use Mobian instead
There is no prebuilt image, you'll need a Linux environment and build the image yourself.

PureOS is a user friendly, secure and freedom respecting GNU/Linux distribution based on Debian and GNOME developed by the Purism community.

Download location

Use the convert script to download and build the image from u-boot, PinePhone linux kernel and Librem5 PureOS.

Also see:

Sailfish OS

Sailfish OS is a Linux-based operating system based on open source projects such as Mer, and a closed source UI based on Lipstick.

Download location

Flashing script

The Sailfish OS image is built on Gitlab CI. The latest image can be installed using the 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:

  1. Download the flashing script
  2. Insert a microSD card in your device
  3. Make the script executable: chmod +x flash-it.sh
  4. Verify that you have the bsdtar package installed
  5. Execute it: ./flash-it.sh
  6. 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 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 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:

See the Sailfish OS wiki for links to their forum, as well as info required when reporting an issue. See the Sailfish OS wiki main page for options to contribute to Sailfish OS.

Notes

OTA is supported: zypper refresh && zypper update as root (devel-su 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: Thread

Download link: http://dl.fail.pp.ua/slackware/images/pinephone/

SkiffOS

SkiffOS-Icon-1.png

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 Buildroot cross-compilation tool for support for all Pine64 boards.

Use configuration packages to configure distro:

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 here.

Sxmo

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

Download location

Sxmo images can be found here (in the /pine64-pinephone/sxmo/ sections respectively).

username/password

user/147147

How to contribute and report defects

Contributing information is listed here.

Ubuntu Touch

Ubports-logo.png

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 the UBports PinePhone project. There is also a 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 UBports installer GUI tool.

Download location

UBports PinePhone project

username/password

Set up during boot

What works, what does not work

Scroll down to the bottom of this page, or directly here [1]

How to contribute and report defects

See UBports gitlab page. See 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

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:

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.

OS Download Link File Size MD5
Beta Edition pine64-pinephone-plamo-beta-factorytest.img.xz 1.78GB f16bce93504a52217540ac886863a418
Mobian pine64-pinephone-20201207-factorytest-mobian.img.xz 1.41GB 015be381ff4e650a7fca6d4eaa90d63d
KDE pine64-pinephone-20201208-factorytest-kde.img.xz 2.28GB 32979ff17b5ec4d358ce99f1aff0c77c
Manjaro pine64-pinephone-20201013-manjaro-stable-20201018-factory56.img.xz 1.04GB 4edfd4dceaefdd32a3417c1727161c29
postmarketOS pine64-pinephone-20200726-phosh-v20.05-factory.img.xz 517MB 244093be2f6d728fcbd1d29114607727
Ubuntu Touch PinePhone-flasher-ubuntu-7b.img.gz 1.05GB 2d7f5271e7a281db8f1b1219bedbe131

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.
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:

  1. 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.
  2. Format the boot partition with vfat, and the root partition with a supported filesystem like ext4 or f2fs.
  3. 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 rsync -ar).
  4. Edit /etc/fstab to match your partitions.
  5. Grab megi's kernel from https://xff.cz/kernels/, Follow the instructions in the 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:

Other Resources

Community

Hardware information

Other software information

Other