PINE64 - User contributions [en]

PinePhone Hardware Issues

2024-11-19T20:06:25Z

Boud: /* USB-C Side Board */ My new USB-C side board seems to behave identically to my old one: mic is fine is U101 shimmed; USB-C connection is fine; vibra is inactive independently in tow-boot and with fftest/Mobian/trixie; the speaker seems to be inactive

{{Under construction}}

== Main Board ==

=== Sim Reader ===

The sim reader may fail to read a sim card (reporting 'sim-missing' in mmcli), possibly due to deformed pins (if you put your sim adapter in without a sim), or due to a warped sim card adapter.

A possible solution is to bend the pins back (using a plastic spudger), and/or use a different sim card adapter (which your carrier may provide to you).

== USB-C Side Board==

All USB-C Side Board issues can, in principle, be fixed by replacing the [https://pine64.com/product/pinephone-usb-c-side-board/ USB-C Side Board]

=== Internal Microphone ===

The microphone may stop working or occasionally stop working or give off static when power is plugged in.

One possible fix is to [[User:Earboxer/Shim_U101|shim U101]] (as seen on the [https://files.pine64.org/doc/PinePhone/PinePhone%20USB-C%20small%20board%20bottom%20placement%20v1.0%2020190730.pdf back side of the USB-C Side Board]) with a piece of paper or cardboard.

=== Bottom Speaker ===

The bottom speaker may stop working, especially if you have recently mishandled the USB-C Side Board, stressing the point of connection between the circuit board and the circuit flex. This can be fixed by touching up the solder between the two.

== Uncategorized Issues ==

Place new issues here.

== See Also ==

* [[PinePhone#Modifications_and_repairs]]
* [[PinePhone_v1.2]]
* [[PinePhone_v1.2a#Known_issues]]
* [[PinePhone_v1.2b#Known_issues]]

[[Category:PinePhone]]

Talk:PinePhone Hardware Issues

2024-11-01T00:58:51Z

Boud: /* Evidence for/against the shim U101 fix */ October is the *10th* month, not 11th (without Caesar it would still be the 8th ...)

== Evidence for/against the shim U101 fix ==
; Works for me 2024-10-06
I [[User:Earboxer/Shim_U101|shimmed my U101]] per the advice given here. Based on two days of a small handful of tests, and after [https://codeberg.org/boud/pinephone_hacks/src/branch/main/bug_reporting/bug_status.md having earlier had a variety of audio and non-audio bugs] on my PinePhone v1.2b running [https://wiki.debian.org/Mobian Mobian/trixie], including [https://salsa.debian.org/Mobian-team/devices/pinephone-support/-/issues/27 this difficult-to-reproduce bug], my microphone appears to be working. I now have [https://packages.mobian.org out-of-the-box alsa-ucm-conf 1.2.12-1mobian1] and other packages at the Mobian default, with modem: FLOSS firmware 0.7.2 + ADSP 30.006.30.006. [[User:Boud|Boud]] ([[User talk:Boud|talk]]) 13:49, 6 October 2024 (UTC)
:However, the out-of-the-box alsa-ucm-conf parameters still give bad audio quality as heard on the remote phone for phone calls "out in the field" as opposed to between people in nearby quiet rooms. [https://codeberg.org/boud/pinephone_hacks/src/branch/main/audio_hacks/Allwinner_A64_PinePhone/VoiceCall.conf This VoiceCall.conf file (commit `cf82dfb455`)], with the microphone U101 shimmed, has worked fine on several real-world tests. [[User:Boud|Boud]] ([[User talk:Boud|talk]]) 00:52, 1 November 2024 (UTC)

== Speculation about why the shim U101 fix may work ==
Any proper explanations? Some hypotheses include:
* electrical isolation/contacts:
** the shim improves an electrical contact that was too weak (not contacting properly); or
** prevents some weak electrical contact that causes current to go in the wrong direction.
* sound wave air transmission:
** the shim pushes the microphone slight higher above the back of the phone in order to better match the hole in the chassis.
[[User:Boud|Boud]] ([[User talk:Boud|talk]]) 13:49, 6 October 2024 (UTC)

I've updated the above list based on a matrix chat favouring "improving an electrical contact". [[User:Boud|Boud]] ([[User talk:Boud|talk]]) 17:52, 8 October 2024 (UTC)

Talk:PinePhone Hardware Issues

2024-11-01T00:55:09Z

Boud: /* Evidence for/against the shim U101 fix */ clarify that the main description of the procedure is at User:Earboxer/Shim_U101

== Evidence for/against the shim U101 fix ==
; Works for me 2024-11-06
I [[User:Earboxer/Shim_U101|shimmed my U101]] per the advice given here. Based on two days of a small handful of tests, and after [https://codeberg.org/boud/pinephone_hacks/src/branch/main/bug_reporting/bug_status.md having earlier had a variety of audio and non-audio bugs] on my PinePhone v1.2b running [https://wiki.debian.org/Mobian Mobian/trixie], including [https://salsa.debian.org/Mobian-team/devices/pinephone-support/-/issues/27 this difficult-to-reproduce bug], my microphone appears to be working. I now have [https://packages.mobian.org out-of-the-box alsa-ucm-conf 1.2.12-1mobian1] and other packages at the Mobian default, with modem: FLOSS firmware 0.7.2 + ADSP 30.006.30.006. [[User:Boud|Boud]] ([[User talk:Boud|talk]]) 13:49, 6 October 2024 (UTC)
:However, the out-of-the-box alsa-ucm-conf parameters still give bad audio quality as heard on the remote phone for phone calls "out in the field" as opposed to between people in nearby quiet rooms. [https://codeberg.org/boud/pinephone_hacks/src/branch/main/audio_hacks/Allwinner_A64_PinePhone/VoiceCall.conf This VoiceCall.conf file (commit `cf82dfb455`)], with the microphone U101 shimmed, has worked fine on several real-world tests. [[User:Boud|Boud]] ([[User talk:Boud|talk]]) 00:52, 1 November 2024 (UTC)

== Speculation about why the shim U101 fix may work ==
Any proper explanations? Some hypotheses include:
* electrical isolation/contacts:
** the shim improves an electrical contact that was too weak (not contacting properly); or
** prevents some weak electrical contact that causes current to go in the wrong direction.
* sound wave air transmission:
** the shim pushes the microphone slight higher above the back of the phone in order to better match the hole in the chassis.
[[User:Boud|Boud]] ([[User talk:Boud|talk]]) 13:49, 6 October 2024 (UTC)

I've updated the above list based on a matrix chat favouring "improving an electrical contact". [[User:Boud|Boud]] ([[User talk:Boud|talk]]) 17:52, 8 October 2024 (UTC)

Talk:PinePhone Hardware Issues

2024-11-01T00:53:02Z

Boud: /* Evidence for/against the shim U101 fix */ the shim U101 fix is fine, but the out-of-the-box VoiceCall.conf still has bad settings

== Evidence for/against the shim U101 fix ==
; Works for me 2024-11-06
I shimmed my U101 per the advice given here. Based on two days of a small handful of tests, and after [https://codeberg.org/boud/pinephone_hacks/src/branch/main/bug_reporting/bug_status.md having earlier had a variety of audio and non-audio bugs] on my PinePhone v1.2b running [https://wiki.debian.org/Mobian Mobian/trixie], including [https://salsa.debian.org/Mobian-team/devices/pinephone-support/-/issues/27 this difficult-to-reproduce bug], my microphone appears to be working. I now have [https://packages.mobian.org out-of-the-box alsa-ucm-conf 1.2.12-1mobian1] and other packages at the Mobian default, with modem: FLOSS firmware 0.7.2 + ADSP 30.006.30.006. [[User:Boud|Boud]] ([[User talk:Boud|talk]]) 13:49, 6 October 2024 (UTC)
:However, the out-of-the-box alsa-ucm-conf parameters still give bad audio quality as heard on the remote phone for phone calls "out in the field" as opposed to between people in nearby quiet rooms. [https://codeberg.org/boud/pinephone_hacks/src/branch/main/audio_hacks/Allwinner_A64_PinePhone/VoiceCall.conf This VoiceCall.conf file (commit `cf82dfb455`)], with the microphone U101 shimmed, has worked fine on several real-world tests. [[User:Boud|Boud]] ([[User talk:Boud|talk]]) 00:52, 1 November 2024 (UTC)

== Speculation about why the shim U101 fix may work ==
Any proper explanations? Some hypotheses include:
* electrical isolation/contacts:
** the shim improves an electrical contact that was too weak (not contacting properly); or
** prevents some weak electrical contact that causes current to go in the wrong direction.
* sound wave air transmission:
** the shim pushes the microphone slight higher above the back of the phone in order to better match the hole in the chassis.
[[User:Boud|Boud]] ([[User talk:Boud|talk]]) 13:49, 6 October 2024 (UTC)

I've updated the above list based on a matrix chat favouring "improving an electrical contact". [[User:Boud|Boud]] ([[User talk:Boud|talk]]) 17:52, 8 October 2024 (UTC)

User:Earboxer/Shim U101

2024-10-13T20:46:18Z

Boud: probably should be shifted to mainspace - in any case, this is a useful page

First, [[User:Earboxer/Deframe_PinePhone|remove the frame]]

Fold a small strip of cardstock three times over, leaving a tail

[[File:PinePhone-U101-shim-creation.jpg|300px]]

Slide it in, tail-first between U101 and the screen assembly, being careful not to lift up the USB-C Side Board.

[[File:PinePhone-U101-shim-installed.jpg|400px]]

(If you lift up the USB-C Side Board, you might mess up the connection between the PCB and PCF, which may [[PinePhone_Hardware_Issues#Bottom_Speaker|break the speaker/rumble]], and will require a soldering iron to fix)

[[File:PinePhone-U101-shim-example.jpg|300px]]

Reassemble the PinePhone

[[Category:PinePhone]]

Talk:PinePhone Hardware Issues

2024-10-08T17:52:27Z

Boud: /* Speculation about why the shim U101 fix may work */ restructure hypothesis list

== Evidence for/against the shim U101 fix ==
; Works for me 2024-11-06
I shimmed my U101 per the advice given here. Based on two days of a small handful of tests, and after [https://codeberg.org/boud/pinephone_hacks/src/branch/main/bug_reporting/bug_status.md having earlier had a variety of audio and non-audio bugs] on my PinePhone v1.2b running [https://wiki.debian.org/Mobian Mobian/trixie], including [https://salsa.debian.org/Mobian-team/devices/pinephone-support/-/issues/27 this difficult-to-reproduce bug], my microphone appears to be working. I now have [https://packages.mobian.org out-of-the-box alsa-ucm-conf 1.2.12-1mobian1] and other packages at the Mobian default, with modem: FLOSS firmware 0.7.2 + ADSP 30.006.30.006. [[User:Boud|Boud]] ([[User talk:Boud|talk]]) 13:49, 6 October 2024 (UTC)

== Speculation about why the shim U101 fix may work ==
Any proper explanations? Some hypotheses include:
* electrical isolation/contacts:
** the shim improves an electrical contact that was too weak (not contacting properly); or
** prevents some weak electrical contact that causes current to go in the wrong direction.
* sound wave air transmission:
** the shim pushes the microphone slight higher above the back of the phone in order to better match the hole in the chassis.
[[User:Boud|Boud]] ([[User talk:Boud|talk]]) 13:49, 6 October 2024 (UTC)

I've updated the above list based on a matrix chat favouring "improving an electrical contact". [[User:Boud|Boud]] ([[User talk:Boud|talk]]) 17:52, 8 October 2024 (UTC)

PinePhone Software Releases

2024-10-06T14:11:03Z

Boud: /* Mobian */ update and add dates so that this will still make sense if people forget to update when Debian/trixie becomes Debian/stable

This page contains a list of all available releases and tools for the [[PinePhone]] in alphabetical order.

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

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

== Software Releases ==

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

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

==== Download ====

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

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

==== Notes ====

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

=== ExpidusOS ===

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

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

==== Download ====

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

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

==== Notes ====

What works, what does not work:

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

How to contribute and report defects:

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

----

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

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

* Forum discussion: [https://forum.pine64.org/showthread.php?tid=9347 Fedora + Phosh for PinePhone]
* GitLab: [https://gitlab.com/fedora/sigs/mobility]

==== Download ====

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

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

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

==== Notes ====

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

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

----

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

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

==== Download ====

Overlay locations:

* https://git.gjdwebserver.nl/gjdwebserver/gjdwebserver-overlay

==== Notes ====

The documentation can be found here:

* https://blog.gjdwebserver.nl/ords/f?p=107:HOME:::::ARTICLE:gentoo-on-a-pinephone
* https://blog.gjdwebserver.nl/ords/f?p=107:HOME:::::ARTICLE:gentoo-on-a-pinephone-making-it-a-usable-phone
* https://blog.gjdwebserver.nl/ords/f?p=107:HOME:::::ARTICLE:gentoo-on-a-pinephone-pro
* https://wiki.gentoo.org/wiki/User:Dr41nU/PinePhone
* https://wiki.gentoo.org/wiki/PinePhone (incomplete)

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

----

=== GloDroid ===

A fully open-source port of Android and LineageOS to the PinePhone.

GitHub: [https://github.com/GloDroidCommunity/pine64-pinephone GloDroid]

==== Download ====

* Releases: [https://github.com/GloDroidCommunity/pine64-pinephone/releases GloDroid]

==== Notes ====

Feature overview:

* Works: WiFi, screen dimming, sound, touchscreen, charging and telephony(partially) works.
* Doesn't work: Bluetooth and GPS
* See more at [https://github.com/GloDroidCommunity/pine64-pinephone/issues/2 project status page]

----

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

The official Kali Nethunter images for PinePhone and PinePhone Pro have been released now. For older/unofficial releases, you can still download from the GitHub releases page. Get [https://github.com/Shubhamvis98/nethunter-pinephone Nethunter App] for your PinePhone's Kali Linux. Packet Injection is working now, use iwconfig instead of airmon-ng.

==== Download ====

* [https://github.com/Shubhamvis98/kali-pinephone/releases Kali Phosh Unofficial]
* [https://www.kali.org/get-kali/#kali-mobile Kali Nethunter Pro Official]

{{Warning|There are reports that the official Kali images fail to boot.}}

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

==== Notes ====

For the installation see the installation instructions under [[PinePhone Installation Instructions]]

----

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

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

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

==== Download ====

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

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

==== Notes ====

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

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

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

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

==== Download ====

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

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

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

==== Notes ====

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

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

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

----

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

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

==== Download ====

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

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

==== Notes ====

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

----

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

An unofficial [https://www.debian.org Debian] build for ARM64 running with Phosh. The base Debian systems available are an old version of [https://www.debian.org/releases/stable Debian stable] (Bookworm 12.0 since June 2023), and [https://www.debian.org/releases/testing Debian testing] (Trixie since June 2023). The ''testing'' version has many more features and bug fixes than the ''stable'' version, but new bugs are more likely; the ''stable'' version should be upgraded to the most recent stable release after installing. See the installation instructions [https://wiki.debian.org/InstallingDebianOn/PINE64/PinePhone on the Debian wiki]. If you have questions about Mobian, please ask them in the [https://matrix.to/#/#mobian:matrix.org Mobian Matrix room].

==== Download ====

* [https://images.mobian.org/pinephone/ Images] (top directory: ''Debian/stable''; "weekly" directory: ''Debian/testing'')

{{Info|[https://tow-boot.org/devices/pine64-pinephoneA64.html Tow-Boot is required] to be able to boot the images!}}

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

==== Notes ====
* Development is active. See [https://wiki.debian.org/Mobian the Mobian wiki].
* In order to connect to the device using SSH/SCP via WiFi, you need to install SSH on the device. You can do this by executing the following in a shell: "sudo apt-get install ssh", afterwards you can connect via SSH/SCP via WiFi using the PinePhone's IP address on port 22.

----

=== Multi-distro demo image ===

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

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

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

==== Download ====

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

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

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

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

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

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

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

==== Notes ====

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

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

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

Also see [[PinePhone Installation Instructions]].

----

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

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

==== Download ====

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

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

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

----

=== NixOS ===
[[File:NixOS.webp|right|100px]]

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

==== Download ====
There is a guided installer by the [https://mobile.nixos.org/devices/pine64-pinephone.html Mobile NixOS] project available. An installer image that can be flashed to a sdcard can be downloaded from the [https://hydra.nixos.org/job/mobile-nixos/unstable/installer.pine64-pinephone Hydra build instance].

Users that want to build a local image, are expected to follow the instructions in the [https://mobile.nixos.org/getting-started.html Getting Started page],
and [https://mobile.nixos.org/devices/pine64-pinephone.html Project's device page].

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

----

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

OpenMandriva Lx with Plasma Mobile as UI.

==== Download ====

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

==== Notes ====

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

----

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

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

==== Download ====

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

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

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

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

==== Notes ====

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

----

=== postmarketOS ===
[[File:PostmarketOS_logo.png|right|100px]]

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

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

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

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

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

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

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

----

=== Rhino Linux ===
[[File:rhino-linux-logo.png|right|100px]]

Rhino Linux is an Ubuntu-based distribution that uses the rolling-release model by tracking the <code>devel</code> branch of repositories. The port is currently maintained by Oren Klopfer (oklopfer).

Tow-Boot is required for installing Rhino Linux. Instructions for installing Tow-Boot to the PinePhone can be found [https://tow-boot.org/devices/pine64-pinephoneA64.html here]. After Tow-Boot has been installed to your device, Rhino Linux installation just requires flashing the <code>.img.xz</code> to an SD or the eMMC.

==== Download ====
[https://rhinolinux.org/download.html Rhino Linux Downloads] (select Pine64 on the dropdown)

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

==== Notes ====
Foundational to the distribution is [https://pacstall.dev Pacstall], a Debian-based user repository inspired by the AUR. Additionally, RL comes with [https://rhinolinux.org/unicorn/ Unicorn], a custom modified version of XFCE with various modernizations and improvements, including auto-rotation for mobile devices.

[https://discord.gg/reSvc8Ztk3 Discord] - [https://matrix.to/#/#rolling-rhino-remix:matrix.org Matrix] - [https://github.com/rhino-linux GitHub] - [https://rhinolinux.org/wiki.html Wiki]

----

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

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

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

==== Download ====

'''Flashing script'''

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

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

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

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

'''username/password'''

Set PIN on initialization.

==== Notes ====

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

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

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

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

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

See the documentation wiki at [https://github.com/sailfish-on-dontbeevil/documentation/wiki the github project] for help and links.

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

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

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

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

'''Notes'''

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

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

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

==== Download ====

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

==== Notes ====

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

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

Use configuration packages to configure distro:

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

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

----

=== Slackware ===

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

==== Download ====

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

==== Notes ====

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

----

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

A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community. The port is currently maintained by Oren Klopfer (oklopfer).

Tow-Boot is required for installing the latest version of Ubuntu Touch (20.04) on the PinePhone. Instructions for installing Tow-Boot to the PinePhone can be found [https://tow-boot.org/devices/pine64-pinephoneA64.html here].

Installation instructions can be found at
[https://ubports.com/en/blog/ubports-news-1/post/pinephone-and-pinephone-pro-3889 this UBports post]. After Tow-Boot has been installed to your device, Ubuntu Touch installation just requires flashing the <code>.img.xz</code> to an SD or the eMMC.

==== Download ====

[https://gitlab.com/ook37/pinephone-pro-debos/-/releases UBports 20.04 PinePhone Latest Releases]

[https://devices.ubuntu-touch.io/device/pinephone/release/focal UBports PinePhone Device Info]

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

==== Notes ====

Scroll down to the middle of [https://gitlab.com/ook37/pinephone-pro-debos/ the GitLab project page], or directly here [https://devices.ubuntu-touch.io/device/pinephone/release/focal/#deviceOverview at the UBports website] to see which features work.

Contributions and bug reports can be made at the [https://gitlab.com/ook37/pinephone-pro-debos/ UBports PinePhone GitLab page]. See [https://ubports.com/foundation/sponsors UBports website] for how to donate.

== Further Releases ==

=== Apache NuttX RTOS ===

[https://nuttx.apache.org/docs/latest Apache NuttX RTOS] is a Real-Time Operating System that supports PinePhone

* [https://nuttx.apache.org/docs/latest/platforms/arm/a64/boards/pinephone/index.html Apache NuttX RTOS on PINE64 PinePhone]

=== Sculpt Operating System (Genode OS Framework) ===

[https://genode.org/news/sculpt-os-release-23.04 Sculpt OS since version 23.04] supports PinePhone.
Ready-to-use system image available on the [https://genode.org/download/sculpt download page].

== Tools ==

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

=== JumpDrive ===

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

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

----

=== Tow-Boot ===

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

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

== Hardware test build ==

{{Warning|The factorytest image for hardware testing appears to be no longer maintained.}}

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 flash it to microSD and test from there. New versions are distributed as part of the postmarketOS distribution.

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

Links:

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

== Historic factory 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.

{{Warning|These images are for testing purposes only. If you are looking for an up-to-date image please select one from the [[#Software Releases|software releases]] section instead.}}

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

== Installing other ARM64 distributions ==

Other ARM64 distributions might be installed as well, however this requires some tinkering and may not work well.

{{Info|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.}}

General steps:

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

If you would like to see examples or specific commands for how to complete these steps, see:

* [https://github.com/nikhiljha/pp-fedora-sdsetup an example for Fedora], current unofficial [#Fedora] release
* [https://xnux.eu/howtos/install-arch-linux-arm.html an example for Arch Linux] by megi

== Other Resources ==

Community

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

Hardware information

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

Other software information

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

Other

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

[[Category:PinePhone]]

Talk:PinePhone Hardware Issues

2024-10-06T13:49:50Z

Boud: works for me

PinePhone

2024-10-05T15:16:00Z

Boud: /* Other hardware issues */ make the side page specific topics so far listed more findable by listing the component names here

[[File:PinePhone Beta Edition.png|400px|thumb|right|Rendering of the PinePhone Beta Edition]]

The '''PinePhone''' is a smartphone created by PINE64. It is capable of running mainline Linux and is supported by many partner projects.

The Braveheart Edition of the PinePhone was the first publicly available version of the phone. It shipped without a fully functional operating system and was geared specifically towards early adopters. The Braveheart Edition's successors were the Community Editions, which featured a branded backcover and box of selected community projects. The Community Editions became available in June 2020. The Beta Edition featuring Manjaro with Plasma Mobile is the latest edition, it became available in March 2021.

== Introduction ==

The PinePhone is not a regular phone and you might not get the latest and greatest hardware and this years' newest innovation. You will get a device with good mainline support with a great community behind it.

=== State of the software ===

First things first, the PinePhone is aimed solely at early adopters - more specifically, the units are solely intended to find their way into the hands of users with extensive operating system experience.

Bear in mind that the software for these smartphones is very early, with most of the software being in alpha or beta state. That's especially also the case for scalability of applications, their availability and practicability, any hardware function implementations and the firmware. The software is provided as is. There is no warranty for the software, not even for merchantability or fitness for a particular purpose.

If you have any questions regarding the current state of the software or of specific features working, please don't hesitate to ask in the community chat (see [[Main Page#Community and Support]])!

=== Help and support ===

Still have any questions regarding software, shipping, or ordering after reading this wiki? Please don't hesitate to contact the community in the bridged community channels for detailed answers or simply to chat with friendly people in the community! See [[Main Page#Community and Support]].

Please keep in mind that PINE64 is not like a regular company (see the [https://www.pine64.org/philosophy/ PINE64 philosophy]) and that support resources are limited - the best way to get support quickly is to ask in the community chat! Please only contact the PINE64 support directly if questions couldn't be solved via the community chat or this wiki.

== First time installation ==
[[File:Pinephone_warning.png|320px|thumb|right|A protection foil isolates the battery for the shipping.]]

When shipped the battery is isolated from the device using a protective plastic tab, which is required to be removed before using the phone. The battery '''will not''' charge or boot until it is removed and the battery is connected again.

{{Info|To remove the sticker after unboxing the phone: Carefully remove the back panel using the notch in the corner of the back cover without overbending it. Then remove the battery. Peel off the clear plastic sticker below it, which isolates the charging contacts and reinsert the battery.}}

The PinePhone's SIM slot only accepts a micro-SIM, please do not insert a nano-SIM without an adapter and make sure that the nano-SIM does not get released from its adapter. The SIM card has to be placed in the lower slot, while the microSD has to be placed in the upper slot.

{{Info|Do not insert an empty micro-SIM adapter into the phone and do not release the nano-SIM inside the adapter, as it will get stuck on the contact pins. If the nano-SIM got released inside the adapter inside the phone, carefully reinsert the nano-SIM card without moving the adapter. In that case do not pull on the empty adapter as it will get stuck on the contact pins and damage them!}}

[[File:Pinephone slots.png|600px|thumb|none|The microSD belongs in the upper slot, the micro-SIM in the lower slot.]]

An adapter from a nano to a micro-SIM might be included under tape in the camera notch of the phone's packaging. Some nano-SIMs will not fit firmly into that adapter that comes with the PinePhone and if the included adapter is used without a well-fitting nano-SIM, the contact pins might get damaged. In that case it is highly recommended to acquire a better fitting adapter.

== Operating systems ==

The PinePhone will automatically boot from microSD if a bootable card is inserted. Although it is technically possible to use any ARM distribution (because the PinePhone uses the mainline kernel), there are a few that are designed specifically for mobile use on devices like the PinePhone.

=== Software releases ===

The [[PinePhone Software Releases]] page has a complete list of currently supported phone-optimized Operating System images that work with the PinePhone as well as other related software information. As soon as more patches get mainlined and distributions ship with the updated kernel, they will also be able to run unmodified on the device. To update any installed operating system please see [[PinePhone Updating Instructions]].

=== Installation instructions ===

The instructions to install an operating system to the internal memory ("eMMC") or a microSD card can be found here: [[PinePhone Installation Instructions]].

=== Troubleshooting ===

If the PinePhone is not booting from eMMC and/or microSD card anymore it can have two causes:

==== The battery is drained ====

If the battery is fully drained, most operating systems and distributions won't boot anymore. One of the exceptions which still boots is the utility ''Jumpdrive'', which can usually be used to expose the eMMC and microSD card as drives to a USB-connected computer. Mind that JumpDrive won't expose the eMMC and microSD card with a drained battery but it still can be flashed and booted from microSD card to confirm that the phone still functions and boots up fine.

JumpDrive can be downloaded from [https://github.com/dreemurrs-embedded/Jumpdrive/releases/download/0.8/pine64-pinephone.img.xz here] (not compatible with the PinePhone Pro!).

{{Info|If JumpDrive boots and other releases do not boot, the battery is likely drained. In that case let it charge while running JumpDrive with a compatible charger for multiple hours and make sure to not fully drain the battery in the future anymore, as that significantly reduces the battery lifetime.}}

Alternatively to testing JumpDrive, the issue can also be diagnosed by checking the battery charge. Simply remove the battery from the device and measure the voltage on the (+) and (-) contacts on the battery. Make sure to not shorten the contacts as shorting battery pins is a severe life and safety danger.

==== The installation is corrupted or incorrect ====

If the installation of the prioritized boot medium is corrupted or incorrect, the PinePhone will not boot anymore. The following problems are common:

* The microSD card is in the wrong slot (see [[#First time installation|first time installation]])
* The image file was flashed to partition 1 (example: ''sdx1'', ''nvme0x1p1'') instead of the whole device (example: ''sdx'', ''nvme0x1'')
* An image without bootloader was flashed (mind the ''Tow-Boot'' bootloader requirements of ''Mobian'' and ''postmarketOS'')
* The operating systems got corrupted, for example after running updates (reflash the device, see [[PinePhone Installation Instructions]])
* An incompatible image was flashed (make sure that the images are compatible. Images for the PinePhone Pro won't boot on the PinePhone and vice versa. Check your invoice to see if you ordered a PinePhone or a PinePhone Pro).

== Specifications ==

* '''Dimensions:''' 160.5 x 76.6 x 9.2mm
* '''Weight:''' Between 180 ~ 200 grams
* '''SIM Card:''' Micro-SIM
* '''Display:'''
** '''Size:''' 5.95 inches (151mm) diagonal
** '''Type:''' HD IPS capacitive touchscreen, 16M colors
** '''Resolution:''' 1440x720, 18:9 ratio
* '''System on Chip:''' [https://linux-sunxi.org/A64 Allwinner A64]
* '''RAM:''' 2GB or 3GB LPDDR3 SDRAM
* '''Internal Storage:''' 16GB or 32GB eMMC, extendable up to 2TB via microSD, supports SDHC and SDXC
* '''Back Camera:''' Single 5MP, 1/4", LED Flash
* '''Front Camera:''' Single 2MP, f/2.8, 1/5"
* '''Sound:''' Loudspeaker, 3.5mm jack & mic (jack doubles as hardware UART if hardware switch 6 is deactivated)
* '''Communication:'''
** '''Modem:''' [https://www.quectel.com/product/lte-eg25-g/ Quectel EG25-G]
** '''LTE-FDD''': B1, B2, B3, B4, B5, B7, B8, B12, B13, B18, B19, B20, B25, B26, B28
** '''LTE-TDD''': B38, B39, B40, B41
** '''WCDMA''': B1, B2, B4, B5, B6, B8, B19
** '''GSM''': B2, B3, B5, B8 (850, 900, 1800, 1900 MHz)
** '''WLAN:''' Wi-Fi 802.11 b/g/n, single-band, hotspot
** '''Bluetooth:''' 4.0, A2DP
** '''GNSS:''' GPS/GLONASS/BeiDou/Galileo/QZSS, with A-GPS
* '''Sensors:''' Accelerometer, gyroscope, proximity, ambient light, compass
* '''Privacy switches:''' Modem, WiFi & Bluetooth, Microphone, Cameras
* '''Battery:''' Lithium-ion, rated capacity 2800mAh (10.64Wh), typical capacity 3000mAh (11.40Wh) (nominally replaceable with any Samsung J7 form-factor battery)
* '''I/O:''' USB Type-C, USB Host, DisplayPort Alternate Mode output, 15W 5V 3A Quick Charge, follows USB PD specification

== Components ==

{| class="wikitable"
! Component
! Model
|-
| Touchscreen
| Goodix GT917S
|-
| Rear camera
| OmniVision OV5640
|-
| Camera flash
| Awinic AW3641EDNR
|-
| Front camera
| GalaxyCore GC2145
|-
| LCD
| Xingbangda XBD599
|-
| WiFi
| Realtek RTL8723CS
|-
| Bluetooth
| Realtek RTL8723CS
|-
| Modem
| Quectel EG25-G
|-
| GNSS/GPS
| Quectel EG25-G
|-
| Magnetometer
| ST LIS3MDL
|-
| Ambient light / Proximity
| SensorTek STK3335
|-
| Accelerometer / Gyroscope
| InvenSense MPU-6050
|-
| Vibration motor
| Unknown model
|-
| Notification LED
| LED0603RGB
|-
| Volume buttons
| Buttons connected to the KEYADC
|-
| Power button
| X-Powers AXP803
|-
| Battery fuel gauge
| X-Powers AXP803
|}

See the [[PinePhone_component_list|PinePhone Component List]].

== Hardware revisions ==

[[File:Pinephone_revisions.png|400px|thumb|right|The history of the PinePhone CEs]]

The following are all hardware revisions of the PinePhone that have existed, ordered by the time of their releases:

* [[Project Anakin]] - Development kit
* [[Project Don't be evil]] - Development kit
* [[PinePhone v1.0 - Dev|PinePhone v1.0]] - Developer Edition
* [[PinePhone v1.1 - Braveheart|PinePhone v1.1]] - Braveheart Edition
* [[PinePhone v1.2]] - Ubports Community Edition
* [[PinePhone v1.2a]] - postmarketOS Community Edition
* [[PinePhone v1.2b]] - Manjaro Community Edition, KDE Community Edition, Mobian Community Edition and Beta Edition

== Hardware accessory ==

=== Add-ons ===
The PinePhone (and PinePhone Pro) is compatible with the official add-on cases, such as the keyboard, the LoRa add-on, the Qi wireless charging add-on and the fingerprint reader add-on. Details can be found under:

* [[PinePhone (Pro) Add-ons]]
* [[PinePhone (Pro) Keyboard]]

=== PinePhone Accessories ===
See [[PinePhone Hardware Accessory Compatibility]] for a list of devices working with the PinePhone (depending on their OS support).

The USB-C can be used to power the device, and offers USB2 host and OTG capabilities, and also can make use of the USB-C capability to integrate HDMI signals. Some USB-C hubs are available that offer power throughput, USB connection, an HDMI port and Ethernet connection.

=== Pogo pins ===

[[File:Pinephone pogo.png|400px|thumb|right|The pogo pins, as visible under the back cover.]]

The PinePhone has six pogo pins on the back allowing for custom hardware extensions such as wireless charging, an IR blaster, a keyboard extension or extended battery case. The pogo pins provide access to an interrupt line, power inputs/outputs and an I2C interface.

{| class="wikitable"
| Interrupt
| SDA
| SCL
|-
| DCIN
| USB-5V
| GND
|}

The DCIN pogo pin is connected to the VBUS line of the phone's USB Type-C connector, serving as another 5 V power input to the phone. However, the PinePhone may act as a USB host (providing 5 V at the USB Type-C connector's VBUS line to a connected device) or as a USB device (drawing from a 5 V source on the USB Type-C connector's VBUS line). Thus, connecting a 5 V power supply to DCIN in order to power the phone may not be safe to do in all conditions, e.g., when the phone is acting as a USB host to a connected USB device.

The USB-5V pogo pin is to used as an "always on" power output from the PinePhone. Depending on a number of factors, USB-5V may be at the battery voltage (between 3.0 V and 4.3 V), or at 5 V. Thus, if you are using USB-5V to power your pogo-pins expansion board, you will probably need to use DC/DC converters/regulators as appropriate. USB-5V is on even while the A64 SoC is powered down.

Pine Store offers the [https://pine64.com/product/pinephone-flex-break-out-board/?v=0446c16e2e66 PinePhone Flex Breakout Board]. With its 2.54 mm pitch, this breakout may have leads soldered directly to the contacts for use in a solderless breadboard. A non-soldered solution would be to use a [https://www.digikey.com/en/products/detail/te-connectivity-amp-connectors/5-520315-6/2258879 TE AMP Connector] that accepts a flat flexible cable with 2.54 mm pitch.

The following community projects use the pogo pin connections:
* The [https://github.com/SMR404/PinephonePogoBreakout ''PinephonePogoBreakout''] breakout board from the community member ''SMR404''
* Martijn Braams' [https://blog.brixit.nl/making-a-backcover-extension-for-the-pinephone/ ''Making a backcover extension for the PinePhone'']

=== Back cover ===
A step file for the back cover for creating custom cases is freely available [https://files.pine64.org/doc/PinePhone/PinePhone%20Back%20Cover%20ver%200.5.stp here].

=== Serial console ===

[[File:PinePhone_Serial_Cable.png|400px|thumb|right|Pinout of the serial adapter. This shows signals from the PinePhone's point of view, so connect the adapter's Rx to Ring 1 and Tx to Tip]]

The PinePhone has a serial port in the headphone connector, it's activated by the 6th contact on the dipswitch. If the switch is set to "on", the headphone connector is in audio mode, if it is set to "off" it's in UART mode. The UART serial connection can also be used for communication with other devices from the PinePhone.

The UART is 115200n8.

The pinout for the serial connector is:

* Tip: RX
* Ring: TX
* Sleeve: GND

You can buy a serial debug cable from the [https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/ PINE64 Store]. The store cable uses a 4 ring plug, as seen in the [https://files.pine64.org/doc/pinebook/guide/Pinebook_Earphone_Serial_Console_Developer_Guide.pdf here], but a 3 ring plug works just as well. The cable uses a CH340 chipset based serial to USB converter, but any 3.3v serial connection can be used. Because it is a "host"/DTE it means that you need a ''cross modem cable'' ([https://en.wikipedia.org/wiki/Null_modem Null Modem]) with TX on Tip to be connected to RX. A cable like e.g. [https://www.ftdichip.com/Products/Cables/USBTTLSerial.htm FTDI TTL-232R-3V3-AJ] which has TX on Tip and RX on Ring fits perfectly.

== Privacy switch configuration ==

[[File:PinePhone Kill Interruptors de Maquinari del PinePhone 4529.jpg|320px|thumb|right|Picture of the privacy switches]]

The PinePhone features six switches that can be used to configure its hardware. They are numbered 1-6, with switch 1 located nearest to the modem. Their "on" position is toward the top of the phone.

{| class="wikitable"
|-
! Number
! Name
! Explanation
! Description
|-
| 1
| Modem
| Pulls Q1501 gate up (FET killing modem power)
| "On" enables 2G/3G/4G communication and GNSS hardware, "off" disables it.
|-
| 2
| WiFi / Bluetooth
| Pulls up CHIP_EN
| "On" enables WiFi and Bluetooth communication hardware, "off" disables it.
|-
| 3
| Microphone
| Breaks microphone bias voltage from the SoC
| "On" enables audio input from on-board microphones (not 3.5 mm jack), "off" disables it.
|-
| 4
| Rear camera
| Pulls up PWDN on OV5640
| "On" enables the rear camera, "off" disables it.
|-
| 5
| Front camera
| Pulls up PWDN on GC2145
| "On" enables the front camera, "off" disables it.
|-
| 6
| Headphone
| Pulls up IN2 on analog switch BCT4717ETB
| "On" enables audio input and output via the 3.5 mm audio jack, "off" switches the jack to hardware UART mode.
|}

== Camera ==

The PinePhone has two cameras, OmniVision OV5640 with 5MP (up to 2592 x 1944 pixels) as rear camera and GalaxyCore GC2145 with 2MP (up to 1600 x 1200 pixels) as front camera.

[[File:Rose.jpg|400px|thumb|none|Example picture taken on the PinePhone's rear camera by Martijn Braam using his app ''Megapixels''.]]

Further details regarding the camera and the Megapixels camera app can be found on [https://blog.brixit.nl/tag/phones/ Martijn's blog].

== Battery ==

The phone ships with a protective plastic sticker between the battery and the phone to protect the device from turning on during shipping. You need to gently open the back cover, then remove the battery and finally remove the sticker and check that the pins aren't bent. Note: If the battery is stuck inside the phone, the mid screw in the lower part of the midframe needs to be slightly loosened, see [[PinePhone_FAQ#The_battery_is_stuck_inside_the_phone|here]].

{{Info|The EG25-G modem and the RTL8723CS WiFi and Bluetooth do not work without a battery and with a drained battery, even when enough power is supplied to the PinePhone via the USB Type-C port. Most operating systems won't boot without a battery or with a drained battery.}}

The [https://files.pine64.org/doc/datasheet/pinephone/PinePhone%20QZ01%20Battery%20Specification.pdf supplied battery] is meant to be compatible with Samsung part number EB-BJ700BBC / BBE / CBE from the 2015 J7 phone. The extended life aftermarket BBU does fit, although it is a tight fit.

{{Warning|Using an aftermarket battery with a higher capacity is done at own risk. Batteries with a higher capacity especially in combination with an external charger can lead to overvoltage, which fries the modem and/or the Bluetooth and WiFi chip.}}

The battery terminals, from the nearest to the battery edge to the nearest to the middle of battery, are as follows:

{| class="wikitable"
| style="min-width: 90px; text-align: center;" | +ve
| style="min-width: 90px; text-align: center;" | thermistor
| style="min-width: 90px; text-align: center;" | -ve
| style="min-width: 90px; text-align: center;" | not connected
|}

The battery includes a protection circuit that isolates it in a number of fault conditions, including if it is discharged too far. The fully discharged battery can be recharged by connecting the phone to a charger with a sufficient output. Once it has charged sufficiently you will be able to boot the phone.

== Modem ==

The PinePhone uses Quectel EG25-G as modem. AT commands are used to communicate with the modem.

=== AT commands ===

A list of documented AT commands can be found for example in this [[:File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_AT_Commands_Manual_V2.0.pdf|AT commands documentation]] from Quectel. Further undocumented AT commands found by the developer megi, who reverse-engineered parts of the modem and its firmware, can be found on megi's website [http://xnux.eu/devices/feature/modem-pp-reveng.html#toc-un-der-documented-at-commands here].

To send AT commands to the modem under Linux, <code>minicom</code> or the often-preinstalled <code>atinout</code> utility can be used.

atinout example (use single quotes instead of double quotes around the command if the command contains double quotes):
<pre>
echo "AT+<command here>" | sudo atinout - /dev/ttyUSB2 -
</pre>

minicom example (you may need to use sudo too):

<code>minicom -D /dev/ttyUSB2</code>

=== VoLTE ===

The PinePhone's modem supports VoLTE and comes with a few VoLTE profiles preloaded. Most operating systems try to set the correct profile automatically.

To list the available VoLTE profiles:

<pre>
AT+QMBNCFG="list"

+QMBNCFG: "List",0,1,1,"ROW_Generic_3GPP",0x0501081F,201901141
+QMBNCFG: "List",1,0,0,"VoLTE-ATT",0x0501033C,201909271
+QMBNCFG: "List",2,0,0,"hVoLTE-Verizon",0x05010141,201911251
+QMBNCFG: "List",3,0,0,"Sprint-VoLTE",0x05010205,201908141
+QMBNCFG: "List",4,0,0,"Commercial-TMO_VoLTE",0x05010505,201811231
+QMBNCFG: "List",5,0,0,"Telus-Commercial_VoLTE",0x05800C43,201912031
+QMBNCFG: "List",6,0,0,"Commercial-SBM",0x05011C18,201904021
+QMBNCFG: "List",7,0,0,"Commercial-DT",0x05011F1C,201905311
+QMBNCFG: "List",8,0,0,"Reliance_OpnMkt",0x05011B38,201910161
+QMBNCFG: "List",9,0,0,"TF_Germany_VoLTE",0x05010C1B,201909201
+QMBNCFG: "List",10,0,0,"TF_Spain_VoLTE",0x05010CFA,201909261
+QMBNCFG: "List",11,0,0,"Volte_OpenMkt-Commercial-CMCC",0x05012071,201904281
+QMBNCFG: "List",12,0,0,"OpenMkt-Commercial-CT",0x05011322,201911081
+QMBNCFG: "List",13,0,0,"OpenMkt-Commercial-CU",0x05011505,201807052
</pre>

To select a profile manually, select the best fitting one or a generic one if none fits:

<pre>
AT+QMBNCFG="select","ROW_Generic_3GPP"
</pre>

Then enable Voice over LTE using:

<pre>
AT+QCFG="ims",1
</pre>

And reboot the modem to apply the settings:

<pre>
AT+CFUN=1,1
</pre>

To check the status of VoLTE during a call, the AT command <code>CLCC</code> can be used:

<pre>
AT+CLCC

+CLCC: 1,1,0,1,0,"",128
+CLCC: 2,1,0,1,0,"",128
</pre>

In the fourth item of the list, "0" means voice and and "1" means data. If both rows have "1" then the voice call is being carried over VoLTE.

=== APN settings ===

The APN setting is only required for a public Internet connection ("data") on the phone. For tested APN settings and how to apply them see [[PinePhone APN Settings]].

=== Carrier support ===
The page [[PinePhone Carrier Support]] contains information about the frequency support of different carriers and hints on setting up cellular network connectivity.

=== Documents ===

Detailed information about the modem can be found on the [https://xnux.eu/devices/feature/modem-pp.html#toc-modem-on-pinephone page of the developer megi], including reverse-engineered parts of the firmware and its functions. There is also a document about using the modem from January 18th 2020 by megi [https://megous.com/dl/tmp/modem.txt here]. A script at the end of the document showcases a way to poweroff the modem before powering off the phone, which is integrated into most of the available operating systems.

=== Firmware update ===

There is a (nearly) free custom firmware and the stock firmware available for the PinePhone. Both can be updated to a newer version with new features and bug fixes.

==== Custom firmware ====

There is a (nearly) free custom firmware for the PinePhone modem by the developer ''biktorgj'', which can be found [https://github.com/the-modem-distro/pinephone_modem_sdk here].

The custom firmware has various advantages (and zero disadvantages) over the stock firmware, including:

* Signal tracking support with checks against the OpenCelliD database
* Persistent storage is optional and unexpected shutdowns don't mess up the modem
* A lower energy consumption due to the lower minimum clock frequency
* And many more, see [https://github.com/the-modem-distro/pinephone_modem_sdk#features-not-available-on-stock-firmware Features not available on stock firmware]

The custom firmware can be flashed using [https://wiki.postmarketos.org/wiki/Fwupd#Upgrading_Modem_Firmware_on_the_PinePhone_.28Pro.29 fwupd] or a [https://github.com/the-modem-distro/pinephone_modem_sdk/blob/kirkstone/docs/FLASHING.md flashing script].

==== Stock firmware ====

{{Hint|The following instructions are directed towards professional users. It is highly recommend to make sure the update process is not interrupted to prevent the modem from bricking.}}

The stock modem firmware can be updated to a newer version if it is outdated. The firmware version can be checked using the following AT command (at the example of <code>atinout</code>, alternatively <code>minicom</code> can be used to communicate with the modem too):

echo 'AT+QGMR' | sudo atinout - /dev/ttyUSB2 -

'''Pre-update checklist:'''

Please make sure all requirements of the checklist are fulfilled. If the update process is interrupted it will lead to a corrupted firmware of the modem, causing it to brick. Recovering a bricked modem is exponentially more complicated and requires the user to boot a special mode by physically bridging test points on the modem.

* The battery needs to be charged sufficiently
* The phone needs to be plugged into a charger
* Deep sleep is recommended to be disabled as it can interrupt the update process
* It is recommended to close all other running applications
* Use common sense while doing the update, don't do the update while being impaired in any way

To get the latest firmware, clone the repository of user Biktorgj on the phone:

git clone https://github.com/Biktorgj/quectel_eg25_recovery

After cloning the directory, open it with cd:

cd quectel_eg25_recovery

Then run qfirehose, which starts the flashing process:

sudo ./qfirehose -f ./

The modem will automatically reboot after the update process is done. The boot process takes around 30 to 60 seconds. After that it is highly recommended to reboot the device.

=== Firmware modifications ===

See [[PineModems]] for more information regarding modem bootloader unlocking, building a custom modem firmware and modem recovery.

=== GPS / GNSS ===
The GPS engine in the modem supports mutli-GNSS reception from GPS, GLONASS, BeiDou, Galileo and QZSS independent of a cellular connection. The operation of the GNSS subsystem can be controlled via a separate set of AT commands, or via qmi. The A-GPS data upload uses the file management AT commands, which also have their own manual. These are linked in the [[PinePhone#Datasheets for components and peripherals|documentation section]] below.

As with most smartphones, the PinePhone has a small antenna and has difficulty getting a first fix without assistance data, a cold start can take 15 minutes under good conditions. The ''eg25-mananger'' is configured to upload A-GPS data by default (see [https://gitlab.com/mobian1/eg25-manager/-/merge_requests/15 here]).

Basic testing of GNSS reception can be done by using the AT command interface (''/dev/ttyUSB2'') from a terminal program like ''minicom'' and the data output interface (''/dev/ttyUSB1'') to feed NMEA data into gpsmon or some other program that can parse standard NMEA sentences.

[[File:Gpsmon eg25g.png|400px|thumb|none|gpsmon decoding GPS data from ''/dev/ttyUSB1'']]

To check if GNSS data output is enabled, you can

cat /dev/ttyUSB1

this should display a stream of NMEA sentences

$GPVTG,,T,,M,,N,,K,N*2C
$GPGSA,A,1,,,,,,,,,,,,,,,,*32
$GPGGA,,,,,,0,,,,,,,,*66

Further details can be found under [[PinePhone Sensors and Navigation]].

=== Voice mail ===

The operating systems of the PinePhone may not have support for accessing your voicemail by holding down the 1-key. Carriers might support accessing the voice mail via an external number however.

== Safety ==

=== General recommendations ===

Due to the greater control the user is having over the device and its software comes also greater responsibility. It is necessary to verify the configuration of the device to make sure that responsible settings are used. The different operating systems may come with non-sane default settings, including SSH with weak password authentication being enabled by default and exposed to the public Internet, the absence of a firewall, default passwords, unencrypted files, too high temperature zones and emergency shutoff values or an enabled root account. The usage of public resources to verify such settings (such as the in case of GNU/Linux, the Arch Linux [https://wiki.archlinux.org/title/security security] wiki page, or the [https://wiki.archlinux.org/title/general_recommendations general recommendations]) as well as the corresponding operating system's or distribution's resources are strongly recommended.

=== Charging safety ===

The PinePhone supports up to 5V 3A (15W) Quick Charge, it follows the USB Power Delivery specification. Only compatible phone chargers may be used, charging the phone with incompatible chargers (for example laptop chargers with a higher voltage) is prohibited. Charging the phone releases heat, general safety recommendations must be followed, see the section ''Thermal safety''.

=== Thermal safety ===

With the Allwinner A64 being an older generation SoC with a large 40nm chip, the phone produces quite some heat with medium or higher use and especially also during charging or when using USB accessories, like a docking station. Measurements to prevent damage to the phone and to its surroundings need to be taken by the user. This includes especially a proper handling of the phone: do not charge the phone in a way where heat builds up around the phone without being able to escape. Especially don't charge your phone under a pillow, blankets, in pockets or bags. Charging the phone produces heat and charging the phone in a way, where the excessive heat can't dispose around the phone poses an immediate fire risk.

The user might notice that the phone gets warm under usage, compared to phones with more up-to-date hardware. Under normal circumstances these temperatures don't pose a risk while being in the levels within the safe operating temperatures (which lay far beyond the point where components can be too hot to touch). Higher temperatures might especially be experienced on the top side of the screen and on the inside of the phone at the RF shield of the modem. The higher temperature of the RF shield of the modem is commonly caused by the SoC on the opposite side of the mainboard, the RF shield of the modem is used to disperse heat of the SoC. In newer mainboard revisions starting from 1.2a there are also thermal pads on the back cover and between the SoC's RF shield and the screen, dispersing heat on the screen and on the back cover. In the past there has been safety issues regarding thermal safety functions, causing temperature reads to not properly work over an extended period of time, which was causing heat damage in some cases (see the documentation of that issue by the developer Megous [http://xnux.eu/log/#018 here] and [http://xnux.eu/log/#017 here]). While the developers are working hard to prevent such issues, they can't be excluded under all circumstances (see [[PinePhone#State_of_the_software|state of the software]]). The users are expected to monitor their phones' thermal safety at every point at this state of the software.

It is highly recommend to update the phone on a regular basis to always get the latest improvements. The default settings to throttle the performance and to shut down the phone when reaching critical temperatures might be set to a too high point depending on the specific usage and usage length. Under GNU/Linux the phone's thermal management behavior can be modified via the Thermal Sysfs driver to achieve lower temperatures and preventing the screen and other components to potentially take damage, see [[PinePhone Thermal Tweaks]] for the details.

== Frequently asked questions ==

For a list of frequently asked questions (including information regarding the shipping) see [[PinePhone FAQ]].

== Modifications and repairs ==

=== Swapping in a new mainboard revision ===

The mainboard can be replaced, for example for upgrading to a newer hardware revision or if it is faulty. The replacement board does not have an OS preinstalled, to test if everything is working after swapping the mainboard a flashed SD card is required. The mainboard also comes with a non-functional firmware on the ANX chip, a newer firmware version has to be flashed as explained below to get certain USB functionality to work.

==== Replacing the mainboard ====

{{Hint|Replacement boards come with an empty eMMC, which means that trying to boot from them looks like the board is faulty (no LEDs, no screen, no reaction of the phone). Please boot an OS from SD card.}}

Prior to replacing your PinePhone’s mainboard please read the steps outlined in bullet points below and watch the attached video.

# You’ll need a small Phillips screwdriver and a prying tool to swap out the PinePhone’s mainboard.
# Remove the PinePhone’s back cover. See your quick start guide for details.
# Remove the battery as well as any inserted SD and SIM cards.
# Unscrew all 15 Phillips head screws around the midframe of the phone.
# Gently pry up the midframe using a guitar pick or credit card corner. It is easiest to separate the midframe at one of the bottom edges. Work your way around all the sides of the phone until the midframe separates from the phone’s body.
# Detach all ribbon cables and “Lego” connectors. List of things to detach: 1) two “Lego” connects at the bottom of the mainboard. 2) u.FL antenna connect and touchscreen digitizer on PCD left side. 3) LCD ribbon cable top of mainboard, next to audio/ UART jack.
# Pry the mainboard up gently from the left-hand side.
# Remove front and main cameras and reset them into the new mainboard.
# Check that the rubber proximity sensor housing is in the chassis, not stuck to the removed mainboard.
# Place the new mainboard in the chassis, hooking in on the plastic tabs on left side and pressing down firmly on opposite side, and follow the steps (7-2) in reverse. When reattaching the midframe take care that no cables are out of place or trapped, as they may be damaged when tightening screws.

After swapping the mainboard the phone won't boot as there is no OS on the replacement board's eMMC preinstalled. To boot an OS insert a flashed SD card.

A video tutorial by Martijn Braam can be found here (or alternatively a video tutorial by user brigadan with additional notes about the camera swap and proximity sensor isolator [https://www.youtube.com/watch?v=J3AJEF7akkw here]):
[[File:Pinephone_martijn_pcb_replacement.png|thumb|none|600px|link=https://www.youtube.com/watch?v=5GbMoZ_zuZs|Watch Martijn Braam's video tutorial here: https://www.youtube.com/watch?v=5GbMoZ_zuZs.]]

==== Flashing the ANX firmware ====

===== Method 1 =====

After swapping the mainboard the ANX7688 chip has to be flashed for full USB functionality.

Under GNU/Linux this can be done by downloading the latest ANX7688 firmware image on the phone:

wget https://xff.cz/git/linux-firmware/plain/anx7688-fw.bin

and executing as root ("sudo su") on the phone:

cp anx7688-fw.bin /lib/firmware/
echo 1 > /sys/class/typec/port0/device/flash_eeprom

===== Method 2 =====

Booting a factory test image will automatically flash the ANX7688 chip. See [[PinePhone Software Releases#Factory Test OS|Factory Test OS]] for such an image.

=== Replacing the screen ===

Before attempting to replace the screen be sure to review the section on [[#Swapping in a new mainboard revision|replacing the mainboard]] since that will get you most of the way there. Be aware that the replacement screen is actually the entire front frame of the phone and there are components that will need to be swapped from your old screen.

* Make sure you have a precision screwdriver set that has the correct size Philips tip. The screws are very small and the heads can easily be stripped if the screwdriver is not correct - if you feel your screwdriver slipping, stop what you are doing and try one that is a better fit. A magnetized screwdriver will help in not losing screws, as will a magnetic parts holder to keep them in while working.

* There are a number of components and cables as well as the insulator sheet under the battery that are glued in place. A hair dryer will loosen the glue and make them much easier to remove. You may want to order extra cables along with the screen just in case.

* The vibration motor, which is part of the USB-C board assembly and glued into place, will come apart easily and be damaged if you pry it up in the wrong place. Make sure you pry from underneath the complete part, not midway on its housing. The ribbon cable attaching this to the USB-C board is small, thin, and fragile so be careful with that as well.

* The new screen comes with new side switches and insulator sheet but there are a number of parts that need to be transferred from the old screen, like the thin coax cable running up the side, the phone ear speaker, proximity sensor gasket, and a gold-colored mesh glued in place that needs to be transferred to a flexible circuit included on the new screen. If you don't swap over the proximity sensor rubber gasket the screen will immediately turn off after logging in. Be careful when routing the coax cable that it goes around the screw holes or you may drive a screw right through the cable.

Take your time, use the right tools, be careful and you should be rewarded with success.

=== Spare parts not available in the PINE64 store ===

* Earpiece: See [[PinePhone (Pro) replacement earpieces]]
* Loudspeaker dimensions: 15x11x3 mm. Compatible with Nokia N91, Lenovo A536 (requires soldering) and others, see [https://forum.pine64.org/showthread.php?tid=12046&pid=85698#pid85698 here]
* Proximity sensor rubber isolator

=== Other hardware issues ===
See also [[PinePhone Hardware Issues]] for more issues and how-to's on hardware components including the sim reader, the internal microphone, and the bottom speaker.

== Press ==

For an overview about media of the PinePhone you can use for the news, blogs, or similar see [[PinePhone Press]].

== PinePhone board information, schematics and certifications ==

PinePhone mainboard schematic:
* [https://files.pine64.org/doc/PinePhone/PinePhone%20v1.2b%20Released%20Schematic.pdf PinePhone mainboard Released Schematic ver 1.2b]
* [https://files.pine64.org/doc/PinePhone/PinePhone%20v1.2a%20Released%20Schematic.pdf PinePhone mainboard Released Schematic ver 1.2a]
* [https://files.pine64.org/doc/PinePhone/PinePhone%20v1.2%20Released%20Schematic.pdf PinePhone mainboard Released Schematic ver 1.2]
* [[PinePhone_v1.2|PinePhone schematic ver 1.2 change list]]
* [https://files.pine64.org/doc/PinePhone/PinePhone%20Schematic%20v1.1%2020191031.pdf "Braveheart" PinePhone mainboard Schematic ver 1.1]
* [https://files.pine64.org/doc/PinePhone/PinePhone%20mainboard%20top%20placement%20v1.1%2020191031.pdf "Braveheart" PinePhone mainboard component top placement drawing ver 1.1]
* [https://files.pine64.org/doc/PinePhone/PinePhone%20mainboard%20bottom%20placement%20v1.1%2020191031.pdf "Braveheart" PinePhone mainboard component bottom placement drawing ver 1.1]
* [[PinePhone component list]]

PinePhone USB-C small board schematic:
* [https://files.pine64.org/doc/PinePhone/PinePhone%20USB-C%20small%20board%20schematic%20v1.0%2020190730.pdf PinePhone USB-C small board Schematic ver 1.0]
* [https://files.pine64.org/doc/PinePhone/PinePhone%20USB-C%20small%20board%20top%20placement%20v1.0%2020190730.pdf PinePhone USB-C small board component top placement drawing ver 1.0]
* [https://files.pine64.org/doc/PinePhone/PinePhone%20USB-C%20small%20board%20bottom%20placement%20v1.0%2020190730.pdf PinePhone USB-C small board component bottom placement drawing ver 1.0]

PinePhone certifications:
* [https://files.pine64.org/doc/cert/PinePhone%20FCC%20SDOC%20Certificate-S19112602605001.pdf PinePhone FCC Certificate]
* [https://fcc.report/FCC-ID/2AWAG-PINEPHONE RF Exposure SAR Information from FCC ID site]
* [https://files.pine64.org/doc/cert/PinePhone%20CE%20RED%20Certificate-S19112602602.pdf PinePhone CE RED Certificate]
* [https://files.pine64.org/doc/cert/PinePhone%20ROHS%20Report.pdf PinePhone ROHS Report]
* Note: PinePhone's Type Allocation Code (TAC) is 86769804

== Datasheets for components and peripherals ==

Allwinner A64 SoC information:
* [https://files.pine64.org/doc/datasheet/pine64/A64%20brief%20v1.0%2020150323.pdf Allwinner A64 SoC brief introduction]
* [https://files.pine64.org/doc/datasheet/pine64/A64_Datasheet_V1.1.pdf Allwinner A64 SoC Data Sheet V1.1 (Official Released Version)]
* [https://files.pine64.org/doc/datasheet/pine64/Allwinner_A64_User_Manual_V1.0.pdf Allwinner A64 SoC User Manual V1.0 (Official Release Version)]

X-Powers AXP803 PMIC (Power Management IC) information:
* [https://files.pine64.org/doc/datasheet/pine64/AXP803_Datasheet_V1.0.pdf AXP803 PMIC datasheet]

LPDDR3 (178 Balls) SDRAM:
* [https://files.pine64.org/doc/datasheet/pinephone/ATL3A1632H12A_mobile_lpddr3_11x11.5_v1.0_1600.pdf Artmem LPDDR3 datasheet]

eMMC information:
* [https://files.pine64.org/doc/datasheet/pinephone/Kimtigo_fbga153_16_32_64_eMMC_datasheet_v1.3.pdf Kimtigo eMMC datasheet]

CMOS camera module information:
* [https://files.pine64.org/doc/datasheet/pinephone/QZ01-rear-2019-0717(HW)%20Model.pdf PinePhone 5M Pixel Real CMOS Image Sensor Module]
* [https://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC for Rear Module datasheet]
* [https://usermanual.wiki/Document/OV5640FirmwareUserGuideV10.952852672.pdf OV5640 Embedded Firmware User Guide – VCM AF Module]
* [https://files.pine64.org/doc/datasheet/pinephone/QZ01-front-2019-0717(HW)%20Model.pdf PinePhone 2M Pixel Front CMOS Image Sensor Module]
* [https://files.pine64.org/doc/datasheet/pinephone/GC2145%20CSP%20DataSheet%20release%20V1.0_20131201.pdf GC2145 2MP CMOS Image Sensor SoC for Front Module datasheet]

LCD touch screen panel information:
* [https://files.pine64.org/doc/datasheet/pinephone/PinePhone%20LCD-QZ01.pdf 5.99" 1440x720 LCD IPS Panel specification]
* [https://files.pine64.org/doc/datasheet/pinephone/ST7703_DS_v01_20160128.pdf ST7703 LCD Controller datasheet]
* [https://files.pine64.org/doc/datasheet/pinephone/GT917S-Datasheet.pdf GOODiX GT917S Capacitive Touch Controller datasheet]

Lithium battery information:
* [https://files.pine64.org/doc/datasheet/pinephone/PinePhone%20QZ01%20Battery%20Specification.pdf PinePhone Lithium Battery specification]
* [https://files.pine64.org/doc/datasheet/pinephone/PinePhone%20QZ01%20Battery%20ZCV%20Curve%20Chart.xlsx PinePhone Lithium Battery ZCV curve chart]
* [https://cad.onshape.com/documents/5194d6303f021e6f300b70a0/w/7b63ac4c32ed63dfd78c7840/e/5d43c0ce5b665bae10082a08 PinePhone Lithium Battery 3D onshape drawing]

WiFi/BT module information:
* [https://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf RTL8723BS/RTL8723CS specification]

LTE module information:
* [[File:Quectel_EG25-G_LTE_Standard_Specification_V1.3.pdf]]
* [[File:Quectel_EG25-G_Hardware_Design_V1.4.pdf]]
* [[File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_AT_Commands_Manual_V2.0.pdf]]
* [[File:Quectel_EC2xEG25-GEG9xEM05_FILE_AT_Commands_Manual_V1.0.pdf]]
* [[File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_GNSS_Application_Note_V1.3.pdf]]

Sensors:
* [https://www.st.com/en/mems-and-sensors/lis3mdl.html ST LIS3MDL 3-axis Magnetometer Datasheet]
* [https://www.invensense.com/products/motion-tracking/6-axis/mpu-6050/ InvenSense MPU-6050 Six-Axis (Gyro + Accelerometer) MEMS datasheet]
* [https://www.sensortek.com.tw/en/product/Proximity_Sensor_with_ALS.html SensorTek STK3335 Ambient Light Sensor and Proximity Sensor]

Digital video to USB-C bridge:
* [https://www.analogix.com/en/system/files/AA-002281-PB-6-ANX7688_Product_Brief.pdf ANX7688 product brief]

Case information:
* [https://files.pine64.org/doc/datasheet/pinephone/PinePhone%20Exploded%20Diagram%20ver%201.0.pdf PinePhone case exploded diagram]
* [https://files.pine64.org/doc/datasheet/pinephone/PinePhone%20Back%20Cover.stp PinePhone back cover 3D file]

Other components:
* See the [[PinePhone_component_list|Component List]]

== Resources ==

The following articles contain more specific information:
* [[PinePhone Accessibility]]
* [[PinePhone Power Management]]
* [[PinePhone Security]]
* [[PinePhone UBports OS Design Discussion]]

The following resources have been made available by Ondřej Jirman, a developer for the Pinephone:
* [https://xnux.eu/howtos/pine64-pinephone-getting-started.html Getting started with PinePhone Hardware]
* [https://xnux.eu/devices/pine64-pinephone.html State of development progress]
* [https://xnux.eu/log/ Development log]
* [https://xnux.eu/news.html PinePhone Technical News and Update, also applies to other Allwinner devices including PINE A64 SBC]
* [https://xnux.eu/contribute.html Contributions to the kernel development]

== External links ==
* [https://pine64.com/product-category/pinephone/ The PinePhone on the official Pine store]
* [https://pine64.com/product-category/smartphone-spare-parts/ PinePhone spare parts on the official Pine store]
* [https://pine64.com/product-category/smartphone-accessories/ PinePhone accessories on the official Pine store]

[[Category:PinePhone]] [[Category:Allwinner A64]]

User:Boud

2024-10-05T14:28:57Z

Boud: me as a pinephone owner

Pinephone owner since August 2021. See https://codeberg.org/boud/pinephone_hacks for several hacks that you may wish to try.