Difference between revisions of "PinePhone Software Releases"

Jump to navigation Jump to search
Sort up the links, rework multiple paragraphs
Tags: Mobile web edit Mobile edit
(Sort up the links, rework multiple paragraphs)
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 [[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 ==
== 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, 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'''
Line 20: Line 26:
'''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'''
Line 27: Line 36:


'''How to contribute and report defects'''
'''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].
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].
Line 32: Line 43:
== 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 64:
'''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 a full Fedora 34 workstation build with phosh: ftp://pine.warpspeed.dk/nightly/pinephone/ (Mount this with something like Nautilus)


'''username/password'''
'''username/password'''
Line 75: Line 91:
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]]


{{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.}}
{{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 ==
Line 107: Line 124:
{{warning|Available images are 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'''
Line 124: Line 143:


* [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]
* [http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image 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-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 .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 build]). 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 192:
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.


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.
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 ==
== Manjaro ARM ==
Line 179: Line 225:
'''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 || <code>manjaro/123456</code>
root/root
! 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:
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].
[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 253:
[[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/nightly/ Nightly] /
[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 275:
'''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 281:
'''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 242: Line 299:
* 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 325:
{{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]].
}}
}}


Line 285: Line 341:
[[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 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 367:
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 384:
'''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 397:
'''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 420:
* [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 427:
'''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 442:
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 390: Line 462:
user/147147
user/147147


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


'''What  
'''What  
Line 399: Line 472:
'''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. Use [https://wiki.pine64.org/wiki/PinePhone_Software_Releases#Mobian 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.}}
Line 439: Line 513:
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 495: Line 570:


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"
! 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 595:
== 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 607:
'''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://git.sr.ht/~mil/sxmo-docs/tree/master/CONTRIBUTING.md here].


== Ubuntu Touch ==
== Ubuntu Touch ==
Line 531: Line 614:
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 547: Line 634:
'''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 645:
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 652:
{{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 669:
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 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.


dd the image on a 8 GB microSD card or larger.
dd the image on a 8 GB microSD card or larger.
Line 617: Line 713:
= 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:
If you would like to see specific commands for how to complete these steps, see:
130

edits

Navigation menu