PINE64 - User contributions [en]

PinePhone (Pro) replacement earpieces

2023-07-13T01:17:23Z

Sethi: Clarify that earpiece may be referred to as earpiece speaker.

The '''earpiece''' (or earpiece speaker) refers to the small speaker at the top of the phone.

This part is not available to purchase from the PINE64 Store. However, it is possible to buy a replacement earpiece for another device, and install it in a PinePhone or PinePhone Pro. This documents earpieces that have been tested by the community, and verified to work.

Note that the earpiece dimensions for both the PinePhone and PinePhone Pro are 12x6x2 mm. When looking into earpieces not found in this list, aim for these dimensions.

{| class="wikitable sortable"
! Earpiece !! PinePhone !! PinePhone Pro !! Where to Buy
|-
| LG K8 2017 M200N
| style="background:#FFB; | Kind of ¹
| style="background:#FFC7C7; | Broken
| [https://www.replacebase.co.uk/for-lg-k8-2017-m200n-replacement-ear-piece-speaker-oem Replace Base]
|-
| Nokia 5
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/for-nokia-5-replacement-ear-piece-speaker-with-adhesive-oem Replace Base]
|-
| Nokia 7
| style="background:#9EFF9E; | Works ²
| style="background:#9EFF9E; | Works ²
| [https://www.replacebase.co.uk/for-nokia-7-replacement-ear-piece-speaker-unit-module-oem Replace Base]
|-
| Nokia X5
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/for-nokia-x5-replacement-earpiece-speaker-unit-oem Replace Base]
|-
| OnePlus One
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.ifixit.com/products/oneplus-one-earpiece-speaker iFixit], [https://www.replacebase.co.uk/oneplus-one-replacement-earpiece-speaker-original Replace Base]
|-
| OnePlus X
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/oneplus-x-replacement-earpiece-speaker-original Replace Base]
|-
| PinePhone
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
|
|-
| Xiaomi Mi A1
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/for-xiaomi-mi-a1-replacement-ear-piece-speaker-oem Replace Base]
|-
| Xiaomi Redmi Note 4
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/for-xiaomi-redmi-note-4-replacement-ear-piece-speaker-oem Replace Base]
|}

'''Notes'''

¹ The earpiece is too thin, it can work with padding to keep the contacts together.

² Audio playback is very low quality.

==List of earpieces that are too large for the PinePhone (Pro)==

The following devices are known to have replacement earpieces with dimensions too large to fit inside the PinePhone or PinePhone Pro.

* Blackberry Classic Q20
* HTC Desire 500
* HTC M10
* Huawei Honor 7A
* Huawei Mate 10 Pro
* Huawei Y7 Prime 2018
* OnePlus 2
* Oppo Reno 5 4G
* Sony Xperia X Compact
* Sony Xperia XA1 Ultra
* Sony Xperia XP X Performance
* Sony Xperia XZ

PinePhone (Pro) replacement earpieces

2023-07-13T01:16:15Z

Sethi: Add iFixit link for OnePlus One

The '''earpiece''' refers to the small speaker at the top of the phone.

This part is not available to purchase from the PINE64 Store. However, it is possible to buy a replacement earpiece for another device, and install it in a PinePhone or PinePhone Pro. This documents earpieces that have been tested by the community, and verified to work.

Note that the earpiece dimensions for both the PinePhone and PinePhone Pro are 12x6x2 mm. When looking into earpieces not found in this list, aim for these dimensions.

{| class="wikitable sortable"
! Earpiece !! PinePhone !! PinePhone Pro !! Where to Buy
|-
| LG K8 2017 M200N
| style="background:#FFB; | Kind of ¹
| style="background:#FFC7C7; | Broken
| [https://www.replacebase.co.uk/for-lg-k8-2017-m200n-replacement-ear-piece-speaker-oem Replace Base]
|-
| Nokia 5
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/for-nokia-5-replacement-ear-piece-speaker-with-adhesive-oem Replace Base]
|-
| Nokia 7
| style="background:#9EFF9E; | Works ²
| style="background:#9EFF9E; | Works ²
| [https://www.replacebase.co.uk/for-nokia-7-replacement-ear-piece-speaker-unit-module-oem Replace Base]
|-
| Nokia X5
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/for-nokia-x5-replacement-earpiece-speaker-unit-oem Replace Base]
|-
| OnePlus One
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.ifixit.com/products/oneplus-one-earpiece-speaker iFixit], [https://www.replacebase.co.uk/oneplus-one-replacement-earpiece-speaker-original Replace Base]
|-
| OnePlus X
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/oneplus-x-replacement-earpiece-speaker-original Replace Base]
|-
| PinePhone
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
|
|-
| Xiaomi Mi A1
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/for-xiaomi-mi-a1-replacement-ear-piece-speaker-oem Replace Base]
|-
| Xiaomi Redmi Note 4
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/for-xiaomi-redmi-note-4-replacement-ear-piece-speaker-oem Replace Base]
|}

'''Notes'''

¹ The earpiece is too thin, it can work with padding to keep the contacts together.

² Audio playback is very low quality.

==List of earpieces that are too large for the PinePhone (Pro)==

The following devices are known to have replacement earpieces with dimensions too large to fit inside the PinePhone or PinePhone Pro.

* Blackberry Classic Q20
* HTC Desire 500
* HTC M10
* Huawei Honor 7A
* Huawei Mate 10 Pro
* Huawei Y7 Prime 2018
* OnePlus 2
* Oppo Reno 5 4G
* Sony Xperia X Compact
* Sony Xperia XA1 Ultra
* Sony Xperia XP X Performance
* Sony Xperia XZ

PinePhone

2023-07-13T01:09:40Z

Sethi: Link to PinePhone Pro replacement earpieces page

[[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 ===

For instructions on how to install the operating systems to the eMMC or SD card see [[PinePhone Installation Instructions]].

Relevant subsections of the article for installing operating systems to the PinePhone are:

* [[PinePhone Installation Instructions#Boot_priority|Boot priority]]
* [[PinePhone Installation Instructions#Installation_to_the_microSD|Installation to the microSD]]
* [[PinePhone Installation Instructions#Installation_to_the_eMMC|Installation to the eMMC]]
* [[PinePhone Installation Instructions#Resize_partition_to_fit_disk_space|Resize partition to fit disk space]]
* [[PinePhone Installation Instructions#Reuse_SD_card_for_data_storage_on_system_booting_from_eMMC|Reuse SD card for data storage on system booting from eMMC]]

=== 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!). 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
| SGMICRO SGM3140
|-
| Front camera
| GalaxyCore GC2145
|-
| LCD
| Xingbangda XBD599
|-
| WiFi
| Realtek RTL8723CS
|-
| Bluetooth
| Realtek RTL8723CS
|-
| Modem
| [http://static.abstore.pl/design/accounts/soyter/img/dokumentacje/quectel_eg25-g.pdf Quectel EG25-G]
|-
| GNSS/GPS
| [http://static.abstore.pl/design/accounts/soyter/img/dokumentacje/quectel_eg25-g.pdf 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
|}

DCIN and USB-5V are the names used in the schematics. The actual behavior of these pogo pins is not obvious based on their names. DCIN is connected both to the VBUS line of the USB Type-C connector and to the ACIN/VBUS inputs on the PMIC. This means that, depending on a number of factors, DCIN may be at 0 V or 5 V. USB-5V is connected at the output of an LP6226 DC/DC boost converter (5 V), which in turn is fed by the PS output of the PMIC. The boost converter is enabled or disabled by a GPIO output from the A64 SoC, controlled by software (e.g. the Linux kernel). Depending on inputs and decision made by the PMIC, PS may be at the battery voltage (fed "directly" by the battery through a [https://www.zxcompo.com/ transistor] controlled by the PMIC), or at the "USB" voltage (fed by the PMIC's ACIN/VBUS inputs). This means that depending on a number of factors, USB-5V may be at battery voltage (between 3.0 V and 4.3 V), or at 5 V.

Because the PinePhone may act as a USB host (providing 5 V at the USB Type-C connector's VBUS to a connected device) or as a USB device (drawing from a 5 V source on the USB Type-C connector's VBUS), DCIN is actually not strictly an input nor an output. Some community analysis of the PinePhone schematic (and some testing) indicates that you can connect a 5 V power supply to DCIN in order to power the phone at the PMIC's ACIN/VBUS inputs (and, as a side effect, charge the battery). This 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. It should also be safe to use DCIN as a power output from the PinePhone, e.g., when a USB Type-C charger is connected, you can draw current directly from the USB Type-C port's VBUS, which is provided by the charger. Please note that, when using DCIN as an output from the PinePhone, DCIN isn't "always on"; it may be 0 V. It is currently not documented on how much current can be safely drawn.

USB-5V should be safe to use as an "always on" power output from the PinePhone. Depending on a number of factors, voltage may be from 3 V to 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.

The I2C and interrupt lines have pull-ups on the phone side. The I2C lines are pulled up to 3v3 by the phone.

For a breakout board see [https://github.com/SMR404/PinephonePogoBreakout here]. For an example project see Martijn's blog post [https://blog.brixit.nl/making-a-backcover-extension-for-the-pinephone/ "Making a backcover extension for the PinePhone"].

PINE64 store currently sells the [https://pine64.com/product/pinephone-flex-break-out-board/?v=0446c16e2e66 PinePhone Flex Breakout Board]. With the pitch being 2.54 mm, this Flex Breakout Board may have leads soldered directly to the contacts for use in a solderless board. 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 will accept a Flat Flexible Cable 2.54 mm pitch.

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

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:
<pre>
echo "AT+<command here>" | sudo atinout - /dev/ttyUSB2 -
</pre>

minicom example:

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

== 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]]

PinePhone Pro

2023-07-13T01:08:57Z

Sethi: Link to PinePhone Pro replacement earpieces page

[[File:Pinephone_double.png|400px|thumb|right|Rendering of the PinePhone Pro]]

The '''PinePhone Pro''' is PINE64's flagship smartphone announced on October 15, 2021. It features 4GB of RAM, an 128GB eMMC and is using an Rockchip RK3399S SoC, which is a specialized version of the RK3399 made specifically for the PinePhone Pro.

== Introduction ==

The PinePhone Pro is PINE64’s second smartphone and a successor to the original PinePhone. It does not, however, replace the original PinePhone. It should also not be considered a second generation PinePhone; it is a higher-end device, with much better specs, aimed at those who wish to daily-drive a open system stack. Achieving this goal will, however, take time as the software and overall smartphone software ecosystem needs to mature.

=== State of the software ===
([[PinePhone Pro Software State|view separately]])

{{:PinePhone Pro Software State}}

=== Editions and revisions ===
Similarly to the original PinePhone, various PinePhone Pro editions are planned, the first of which is the Developer Edition (aimed at developers, as the name entails) followed by the Explorer Edition, which is aimed at early adopters.

* [[PinePhone Pro Developer Edition]]
* PinePhone Pro Explorer Edition

=== 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 setup ==
[[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 SIM card has to be placed in the lower slot, while the microSD has to be placed in the upper slot. Devices shipped after the end of July 2022 do only accept a nano-SIM, the SIM is inserted into a carriage released by slightly pulling on the handle in the lower slot (for information regarding devices shipped prior to end of July 2022 see below).

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

{{Info|Information regarding devices shipped prior to end of July 2022: The PinePhone Pros shipped prior to the end of July 2022 come with a micro-SIM slot instead of a nano-SIM slot. 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!}}

== Software ==

The software section explains how to install the available software releases for the PinePhone Pro to the internal eMMC or a microSD card, how to boot them and how to solve common booting issues.

=== Software releases ===

The [[PinePhone Pro Software Releases]] page has a complete list of currently supported phone-optimized operating system images that work with the PinePhone Pro.

{{Info|Images of the regular PinePhone are not compatible with the PinePhone Pro.}}

=== Boot order ===

The RK3399S processor in the PinePhone Pro searches for the bootloader (such as ''U-Boot'' or ''Tow-Boot'') in the following order:

# SPI flash
# eMMC (the internal memory)
# MicroSD card

==== Boot from microSD card temporarily ====

To temporarily boot from an inserted '''microSD card''' do the following:

* On the '''Explorer Edition ordered after July 2022''' hold the ''volume down key'' while powering on the device. The batches bought after July 2022 come with ''Tow-Boot'' flashed to the SPI, which offers additional functionality over ''U-Boot'' as bootloader.

* On the '''Explorer Edition ordered between January and July 2022''' hold the ''RE'' button underneath the cover for a few seconds, while powering on the device. If the button is labeled ''RESET'' instead of ''RE'' please verify if the device is a regular [[PinePhone]] (or the Developer Edition). This is required because older batches don't ship with ''Tow-Boot'' on the SPI. Flashing ''Tow-Boot'' can be caught up by following [https://tow-boot.org/devices/pine64-pinephonePro.html this] instruction. Note: If ''Tow-Boot'' is flashed later, the microSD card can be selected at boot with the volume down key as well.

* On the '''Developer Edition (sold to selected developers only)''' the SPI and the eMMC can be bypassed by shorting the bypass test points while booting. The process is explained in the article [[PinePhone Pro Developer Edition#Nuking the factory AOSP installation|PinePhone Pro Developer Edition]]. Please join the community chat for any questions regarding the process.

The RE button disables the SPI and the eMMC at the hardware level while the button is held and the PinePhone Pro will try to boot from the next available boot medium, which is the microSD card. Note: When holding the ''RE'' button (or when shorting the contact points in case of the ''Developer Edition'') for a longer time at boot the operating system will not initialize the SPI and eMMC and it will not be possible to write to these storage mediums until the next reboot.

{{Template:Info|The bootloader uses its own boot order for loading the kernel and other core operating system components at boot, which for example may result in the boot loader residing on the eMMC loading and booting the kernel from a microSD card.}}

==== Boot from microSD card permanently ====

The bootloader (such as ''U-Boot'') resides in the free space in front of the first partition. Wiping the bootloader from the eMMC to make the PinePhone Pro boot from microSD card can be done using <code>sudo dd if=/dev/zero of=/dev/mmcblk2 seek=64 count=400 conv=fsync</code>. Formatting the drive or deleting the partition table is not sufficient to wipe the bootloader.

==== Notes ====

If you received your device after July of 2022, the bootloader (''Tow-Boot'') resides on the SPI. To boot to an SD card, place the SD card in your PinePhone Pro and turn it on. The phone will vibrate once. At this point, hold down the volume down button until you feel the device vibrate again then release the button. The LED color should change to blue and your display should remain black for a few seconds. In a few seconds you should see the SD card booting, the indications of which are dependent on what image you chose. If the LED is flashing instead, the boot from SD failed. Erasing the SPI can be achieved via the Tow-Boot installer image. Instructions are available here [https://tow-boot.org/devices/pine64-pinephonePro.html Tow-Boot PinePhone Pro Instructions].

See [[RK3399 boot sequence]] for further details regarding the boot sequence.

=== Installation instructions ===

The software releases can be installed (the process is being referred to as ''flashing'') to the eMMC or to an microSD card.

==== Flashing to microSD card ====
To install an image to the microSD card:

# Download a compatible image from [[PinePhone Pro Software Releases]].
# '''Important:''' Typically the image will be compressed in an archive file to reduce the download size (such as ''.gz'' or ''.xz''). Extract the image from its archive file to get the file with the file extension ''.img''.
# Write the image to your microSD card using your favorite method, examples:
#* Using ''dd'': On the device you're flashing the microSD card from, find the correct device under <code>lsblk</code> and then flash the image to the microSD card using <code>sudo dd if='''IMAGE.img''' of=/dev/'''[DEVICE]''' bs=1M status=progress conv=fsync</code>. Make sure the target is the whole microSD card and not its first partition (''sdc1'' or ''mmcblk0p1'' are wrong!).
#* Using ''bmaptool'': Make sure to select the correct device using <code>lsblk</code>. Then run bmaptool with the correct device: Download the ''IMAGE.xz'' and the ''IMAGE.bmap'' files, then run <code>bmaptool copy --bmap '''IMAGE.bmap''' '''IMAGE.xz''' /dev/'''[DEVICE]'''</code>. This takes around 2.5 minutes to flash a 4 GB file.
#* Using ''a graphical tool'': A graphical tool such as Gnome Disks under Linux or Etcher under Windows may also be used.
# Insert the microSD card into the top slot of the PinePhone Pro. Make sure the microSD card is inserted all the way and that the notch of the right side of the microSD card is not visible anymore, see [[:File:Pinephone_slots.png|here]].
# Boot the device using the following method:
#* On the '''Explorer Edition ordered after July 2022''' hold the ''volume down key'' while booting.
#* On the '''Explorer Edition ordered between January and July 2022''' hold the ''RE'' button underneath the back cover while booting (or use the ''volume down key'' if you flashed ''Tow-Boot'').
#* On the '''Developer Edition (sold to selected developers only)''' apply the bypass by shorting the testing pads while booting according to the datasheet (or use the ''volume down key'' if you flashed ''Tow-Boot'').

Details regarding the boot order can be found in the [[PinePhone Pro#Boot order|Boot order]] section.

==== Flashing to the eMMC ====
Flashing to the eMMC can either be done using ''Tow-Boot'''s USB Mass Storage mode (see [[#Boot order]] if you are unsure if the device comes with Tow-Bot pre-installed) or by booting an operating system from the microSD (see the section [[PinePhone Pro#Flashing to microSD card|Flashing to microSD card]]) and by writing to the eMMC directly from there:

By using Tow-Boot:
# Power off the device
# Power on the device and hold the ''volume up'' key before and during the second vibration
# The LED will turn blue if done successfully. This will only work if Tow-Boot is installed
# When connecting the device to a computer via USB it will behave like an USB drive now
# Check if the eMMC appears under <code>lsblk</code>
# '''Important:''' Typically the image will be compressed in an archive file to reduce the download size (such as ''.gz'' or ''.xz''). Extract the image from its archive file to get the file with the file extension ''.img''
# Flash the image file using <code>sudo dd if='''IMAGE.img''' of=/dev/'''DEVICE''' bs=1M status=progress conv=fsync</code> (replace ''IMAGE.img'' with the filename of the image you want to flash and make sure it has the file extension ''.img'' and replace ''DEVICE'' with the correct device from the ''lsblk'' command)
# Reboot the PinePhone Pro

By booting a microSD card:

# Boot an operating system [[PinePhone Pro#Flashing to microSD card|from the microSD card]]. If there is already a bootloader on the eMMC installed see the section [[PinePhone Pro#Boot order|Boot order]] to bypass it.
# Download or copy the desired image to the microSD card as file
# Check if the eMMC appears under <code>lsblk</code>. If it doesn't appear in the output of the command, the eMMC wasn't initialized due to applying the above explained bypass method for a too long time during the boot
# '''Important:''' Typically the image will be compressed in an archive file to reduce the download size (such as ''.gz'' or ''.xz''). Extract the image from its archive file to get the file with the file extension ''.img''.
# Flash the image file using <code>sudo dd if='''IMAGE.img''' of=/dev/mmcblk2 bs=1M status=progress conv=fsync</code> (replace ''IMAGE.img'' with the filename of the image you want to flash and make sure it has the file extension ''.img'').
# Reboot the PinePhone Pro

=== Troubleshooting ===

If the PinePhone Pro is not booting (either booting incompletely into a boot splash or tty or if the PinePhone Pro is showing no signs of life) this will typically have the following two reasons:

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

If the battery is drained then the board can reset during boot causing a boot loop because of undervoltage condition. It can happen on all stages of the boot including ''U-Boot'' bootloader, display initialization and USB (re-)configuration. In that case it is not possible to charge the phone. The battery can be charged by interrupting the boot loop by booting the PinePhone Pro into ''Maskrom mode'' or by charging the battery externally. It is possible to follow these instructions without a computer by using a wall charger, however it would not be possible to determine if Maskrom mode was started successfully. To boot the PinePhone Pro into ''Maskrom mode'':

* Remove any microSD card from the phone and keep it removed for the below procedure
* Remove the battery, any USB cable and any serial cable
* Reinsert the battery
* Hold the ''RE'' button underneath the back cover of your ''Explorer Edition'' (or short the bypass contact points on the ''Developer Edition'')
{{Info|Confirm that the label of the button says ''RE'' and not ''RESET''! If the button label says ''RESET'' instead you probably have a regular PinePhone and you're reading the wrong page.}}
* Connect the phone to an USB port of a computer, while still holding the button for some time
* Confirm if the phone was booted in Maskrom mode:
** On ''Linux'' check if the Maskrom mode appears as device in the output of the terminal command <code>lsusb</code> on the computer, the expected ''VID:PID'' of the device is ''2207:330c''.
** On ''Windows'' this can be checked using the ''Device Manager'' and checking the VID "2207" and PID "330c" of an ''Unknown device'' appears.
** On ''macOS'' this can be checked in ''/Applications/Utilities/System Information.app'' under ''USB'' and by checking if the VID "2207" and PID "330c" is appearing for a ''Composite Device''.
* Let the phone charge for multiple hours

{{Info|If the device doesn't appear under ''lsusb'' please try again with a different known good USB-C cable and make sure that there is no microSD card in the phone inserted.}}

The device should now be able to boot from the boot medium again. If that is not the case the installation got corrupted, as explained below.

==== The installation is corrupted ====
The PinePhone Pro won't be able to boot if the installation on the SPI flash, the eMMC or the microSD card got corrupted. To boot a working operating system:

* Prepare a microSD card as explained in the section [[PinePhone Pro#Flashing to microSD card|Flashing to microSD card]]
* Remove any USB-C cable or device or add-on case from the PinePhone Pro
* Make sure the device is powered off by shortly removing the battery for a second
* Insert the microSD card into the top slot of the PinePhone Pro. Make sure the microSD card is inserted all the way and that the notch of the right side of the microSD card is not visible anymore.
* Power on the device while bypassing the SPI and eMMC as explained under [[PinePhone Pro#Boot order|Boot order]]

The device should now boot from the microSD card. If the phone does not boot from the microSD card the microSD card was flashed with an incompatible image or the battery got drained as explained above.

=== Bootloaders ===
The following section contains notes regarding compatible bootloaders with the PinePhone Pro.

==== U-Boot ====
The pre-installed operating system on the PinePhone Pro Explorer Edition, if sold prior to the end of July of 2022, is using [[U-Boot]] as default bootloader. Batches sold after July of 2022 are using ''Tow-Boot''

==== Tow-Boot ====
Current batches of the PinePhone Pro ship with ''Tow-Boot'' pre-installed to the SPI flash, which is an opinionated distribution of ''U-Boot'' and brings numerous advantages over stock ''U-Boot'', such as the possibility to choose from booting the eMMC or microSD card using the volume buttons during boot, as well as a ''USB Mass Storage mode'', where the device can be written to by connecting the device to a computer via USB.

The user can flash Tow-Boot to the PinePhone Pro using the [https://tow-boot.org/devices/pine64-pinephonePro.html instructions on the Tow-Boot website].

==== levinboot ====
The levinboot bootloader is another option for the PinePhone Pro. The project repository can be found [https://gitlab.com/DeltaGem/levinboot/-/tree/master/ here]. (Pinephone Pro supporting fork is [https://xff.cz/git/levinboot/ here].)

== 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
! Description
|-
| 1
| Modem
| "On" enables 2G/3G/4G communication and GNSS hardware, "off" disables it.
|-
| 2
| WiFi / Bluetooth
| "On" enables WiFi and Bluetooth communication hardware, "off" disables it.
|-
| 3
| Microphone
| "On" enables audio input from on-board microphones (not 3.5 mm jack), "off" disables it.
|-
| 4
| Rear camera
| "On" enables the rear camera, "off" disables it.
|-
| 5
| Front camera
| "On" enables the front camera, "off" disables it.
|-
| 6
| Headphone
| "On" enables audio input and output via the 3.5 mm audio jack, "off" switches the jack to hardware UART¹ mode.
|}

¹ Note: The baud rate may be 1500000 instead of 115200.

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

echo "AT+<command here>" | sudo atinout - /dev/ttyUSB2 -

''minicom'' example:

minicom -D /dev/ttyUSB2

=== VoLTE ===

The PinePhone and PinePhone Pro 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:

AT+QMBNCFG="select","ROW_Generic_3GPP"

Then enable Voice over LTE using:

AT+QCFG="ims",1

And reboot the modem to apply the settings:

AT+CFUN=1,1

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 power off 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 Pro. 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 and PinePhone Pro 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 documentation section.

As with most smartphones, the PinePhone Pro 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 Pro 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.

== Specifications ==

* '''Dimensions:''' 160.8 x 76.6 x 11.1mm
* '''Weight:''' Approx. 220g
* '''SIM Card:''' Nano-SIM (Micro-SIM before 07/2022)
* '''Display:'''
** '''Size:''' 6 inches (151mm) diagonal
** '''Type:''' 1440 x 720 in-cell IPS with Gorilla Glass 4™
** '''Resolution:''' 1440x720, 18:9 ratio
* '''System on Chip:''' Rockchip RK3399S 64bit SoC – 2x A72 and 4x A53 CPU cores @ 1.5GHz
* '''RAM:''' 4GB LPDDR4 @ 800MHz
* '''Internal Storage:''' 128GB eMMC, extendable up to 2TB via microSD, supports SDHC and SDXC
* '''NOR Flash:''' Listed as [GigaDevices] GD25LQ128EWIGR, but physical inspection found a SiliconKaiser SK25LP128.
* '''Back Camera:''' 13MP Sony IMX258 with Gorilla Glass 4™ protective layer, LED Flash
* '''Front Camera:''' 8MP, OmniVision OV8858 front-facing camera
* '''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 & Bluetooth:''' Wi-Fi 802.11AC, hotspot capable + Bluetooth V5.0
** '''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; unglue bottom black plastic with your nail from Samsung battery before installation in order to match the dimensions)
* '''I/O:''' USB Type-C, USB Host, DisplayPort Alternate Mode output, 15W 5V 3A Quick Charge, follows USB PD specification

== Modifications and repairs ==

Most parts are available from the [https://pine64.com/product-category/pinephonepro-spare-parts/ Pine store]. Take care to use this link to avoid unintentionally ordering parts for the original PinePhone instead.

=== Replacing the mainboard ===

The mainboard can be replaced if it is faulty. The replacement board does not have an operating system pre-installed, to test if everything is working after swapping the mainboard a flashed SD card is required.

{{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 operating system from a microSD card.}}

Prior to replacing your PinePhone Pro’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 mainboard.
# Remove the phone'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, including the screw under the warranty sticker.
# 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 and UART jack.
# Pry the mainboard up gently from the left-hand side.
# Remove front and main cameras and reset them into the new 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 for the regular PinePhone can be found [https://www.youtube.com/watch?v=5GbMoZ_zuZs 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].

=== Replacing the screen ===

Before attempting to replace the screen be sure to review the section on [[#Replacing the mainboard|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 silver-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 Pine Store ===

The following parts are not available on the Pine Store for the '''regular PinePhone'''. The replacements are listed below and have not been validated for the PinePhone Pro.

* 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

== Components ==

{| class="wikitable"
! Component
! Model
|-
| Touchscreen
| Goodix GT917S
|-
| LCD
| Himax HX8394 compatible
|-
| Rear camera
| IMX258
|-
| Front camera
| OV8858
|-
| Camera flash
| AW3641EDNR
|-
| WiFi + Bluetooth
| [https://www.azurewave.com/img/wireless-modules/AW_CM256SM_DS_Rev15_CYW.pdf AzureWave AW-CM256SM]
|-
| Modem
| [http://static.abstore.pl/design/accounts/soyter/img/dokumentacje/quectel_eg25-g.pdf Quectel EG25-G]
|-
| GNSS/GPS
| [http://static.abstore.pl/design/accounts/soyter/img/dokumentacje/quectel_eg25-g.pdf Quectel EG25-G]
|-
| <s>3 Axis Magnetometer</s>
| <s>[https://www.st.com/en/mems-and-sensors/lis3mdl.html ST LIS3MDL]</s> '''''Note:''''' The ''AF8133J'' is used instead.
|-
| Geo Magnetic Sensor
| [http://www.voltafield.com/products01.html Voltafield AF8133J]
|-
| Ambient light / Proximity
| STK3311-A
|-
| Accelerometer / Gyroscope
| [https://invensense.tdk.com/products/motion-tracking/6-axis/mpu-6500/ TDK MPU-6500]
|-
| Vibration motor
|
|-
| Notification LED
| LED0603RGB
|-
| Audio Codec
| ALC5616 and ALC5640
|-
| Volume buttons
| Buttons connected to the KEYADC
|-
| Power button
|
|-
| Battery fuel gauge
| [https://rockchip.fr/RK818%20datasheet%20V1.0.pdf RK818]
|}

== Datasheets, schematics and certifications ==

PinePhone Pro mainboard schematic:
* [https://files.pine64.org/doc/PinePhonePro/PinephonePro-Schematic-V1.0-20211127.pdf PinePhone Pro mainboard Explorer Edition Released Schematic ver 1.0 20211127]
* [https://files.pine64.org/doc/PinePhonePro/PinephonePro_PCB_Component_Placement-V02_20211127-top.pdf PinePhone Pro mainboard Explorer Edition component top placement ver 1.0 20211127]
* [https://files.pine64.org/doc/PinePhonePro/PinephonePro_PCB_Component_Placement-V02_20211127-bottom.pdf PinePhone Pro mainboard Explorer Edition component bottom placement ver 1.0 20211127]

PinePhone Pro USB-C small board schematic:
* TBD

Certifications:
* [https://files.pine64.org/doc/cert/PinePhone%20Pro%20FCC%20Certificate-S21101902805001.pdf PinePhone Pro FCC Certificate]
* [https://files.pine64.org/doc/cert/PinePhonePro%20SAR%20Evaluation%20Report-S21101902806001.pdf PinePhone Pro SAR Evaluation Report]
* [https://files.pine64.org/doc/cert/PinePhone%20Pro%20CE%20RED%20Certificate-S21101902802-R1.pdf PinePhone Pro CE RED Certificate]
* [https://files.pine64.org/doc/cert/PinePhonePro%20RoHS%20Test%20Report.pdf PinePhone Pro ROHS Test Report]

== Factory Test Build for Hardware Checking ==
[[File:PPP_Abdroid_Test_Utility-5.jpg|400px|right]]

Please note that this Android build solely for PinePhone Pro hardware checking purpose and solely used by the support team. This is NOT a general release build.

Download:
* [http://files.pine64.org/os/PinePhonePro/pinephone_pro_dd_android9_QC_Test_SDboot_20220215-8GB.img.gz Direct download] from ''pine64.org'' (722MB, for 8GB microSD cards or bigger, MD5 of the GZip file ''214e063c8205c1a98d44b2015a21bb5d'')

Instructions:
* Download the build, extract the image and dd it to a 8 GB or larger microSD card, take out the PinePhone Pro Explorer Edition, then insert it into microSD slot (upper slot).
* Insert battery, press the RE button (bypass SPI and eMMC boot) underneath the back cover while plugging in the USB-C power. After 3 seconds release the RE button.
* When powering up, a battery icon screen will show up blow, press power key for two seconds, then the Rockchip logo screen shows up.


* Wait for the home screen, double tap on the test app icon (mark red circuit) and this will bring up the factory test screen. Please note that the SD test is disabled due in this is SD boot build.
* After running a particular test function, please snapshot the test result and pass it back to support team

Notes:
* Please insert a functional SIM card when performing the SIM test
* When perform GPS test, the first result may fail and please ignore this false message.
* For light sensing test, please have a light shine to the PinePhone Pro when performing the test.


== Using Factory Test Build for Battery charging ==
[[File:PPP_Abdroid_Test_Utility-1.jpg|300px|right]]

Please note that this Android build solely for PinePhone Pro hardware checking purpose and solely used by support team. This is NOT a general release build.

Download:
* [http://files.pine64.org/os/PinePhonePro/pinephone_pro_dd_android9_QC_Test_SDboot_20220215-8GB.img.gz Direct download] from ''pine64.org'' (722MB, for 8GB microSD cards or bigger, MD5 of the GZip file ''214e063c8205c1a98d44b2015a21bb5d'')

Instructions:
* Download the build, extract the image and dd it to a 8 GB or larger microSD card, takes out the PinePhone Pro Explorer Edition then insert it into microSD slot (upper slot).
* Insert battery, press RE button (bypass SPI and eMMC boot) while plug in USB-C power. After 3 seconds release RE button.
* When power up, below battery icon screen show up and battery will start charging.
* The battery icon display for few seconds and then LCD panel turn off while charging. To check charging status, just quick press power button (about 0.5 second) and battery icon will display progress.

== Press ==

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

== External links ==
* [https://www.pine64.org/pinephonepro/ Product Page]
* [https://www.youtube.com/watch?v=wP2-6Z74W44 Announcement video]
* [https://www.pine64.org/2021/10/15/october-update-introducing-the-pinephone-pro/ Blog post] with the announcement

[[Category:PinePhone Pro]][[Category:Rockchip RK3399]]

PinePhone (Pro) replacement earpieces

2023-07-13T00:53:58Z

Sethi: Fix typo.

The '''earpiece''' refers to the small speaker at the top of the phone.

This part is not available to purchase from the PINE64 Store. However, it is possible to buy a replacement earpiece for another device, and install it in a PinePhone or PinePhone Pro. This documents earpieces that have been tested by the community, and verified to work.

Note that the earpiece dimensions for both the PinePhone and PinePhone Pro are 12x6x2 mm. When looking into earpieces not found in this list, aim for these dimensions.

{| class="wikitable sortable"
! Earpiece !! PinePhone !! PinePhone Pro !! Where to Buy
|-
| LG K8 2017 M200N
| style="background:#FFB; | Kind of ¹
| style="background:#FFC7C7; | Broken
| [https://www.replacebase.co.uk/for-lg-k8-2017-m200n-replacement-ear-piece-speaker-oem Replace Base]
|-
| Nokia 5
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/for-nokia-5-replacement-ear-piece-speaker-with-adhesive-oem Replace Base]
|-
| Nokia 7
| style="background:#9EFF9E; | Works ²
| style="background:#9EFF9E; | Works ²
| [https://www.replacebase.co.uk/for-nokia-7-replacement-ear-piece-speaker-unit-module-oem Replace Base]
|-
| Nokia X5
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/for-nokia-x5-replacement-earpiece-speaker-unit-oem Replace Base]
|-
| OnePlus One
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/oneplus-one-replacement-earpiece-speaker-original Replace Base]
|-
| OnePlus X
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/oneplus-x-replacement-earpiece-speaker-original Replace Base]
|-
| PinePhone
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
|
|-
| Xiaomi Mi A1
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/for-xiaomi-mi-a1-replacement-ear-piece-speaker-oem Replace Base]
|-
| Xiaomi Redmi Note 4
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/for-xiaomi-redmi-note-4-replacement-ear-piece-speaker-oem Replace Base]
|}

'''Notes'''

¹ The earpiece is too thin, it can work with padding to keep the contacts together.

² Audio playback is very low quality.

==List of earpieces that are too large for the PinePhone (Pro)==

The following devices are known to have replacement earpieces with dimensions too large to fit inside the PinePhone or PinePhone Pro.

* Blackberry Classic Q20
* HTC Desire 500
* HTC M10
* Huawei Honor 7A
* Huawei Mate 10 Pro
* Huawei Y7 Prime 2018
* OnePlus 2
* Oppo Reno 5 4G
* Sony Xperia X Compact
* Sony Xperia XA1 Ultra
* Sony Xperia XP X Performance
* Sony Xperia XZ

PinePhone (Pro) replacement earpieces

2023-07-13T00:52:50Z

Sethi: Minor rewording and formatting.

The '''earpiece''' refers to the small speaker at the top of the phone.

This part is not available to purchase from the PINE64 Store. However, it is possible to buy a replacement earpiece for another device, and install it in a PinePhone or PinePhone Pro. This documents earpieces that have been tested by the community, and verified to work.

Note that the earpiece dimensions for both the PinePhone and PinePhone Pro are 12x6x2 mm. When looking into other earpieces not found in this list, aim for these dimensions.

{| class="wikitable sortable"
! Earpiece !! PinePhone !! PinePhone Pro !! Where to Buy
|-
| LG K8 2017 M200N
| style="background:#FFB; | Kind of ¹
| style="background:#FFC7C7; | Broken
| [https://www.replacebase.co.uk/for-lg-k8-2017-m200n-replacement-ear-piece-speaker-oem Replace Base]
|-
| Nokia 5
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/for-nokia-5-replacement-ear-piece-speaker-with-adhesive-oem Replace Base]
|-
| Nokia 7
| style="background:#9EFF9E; | Works ²
| style="background:#9EFF9E; | Works ²
| [https://www.replacebase.co.uk/for-nokia-7-replacement-ear-piece-speaker-unit-module-oem Replace Base]
|-
| Nokia X5
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/for-nokia-x5-replacement-earpiece-speaker-unit-oem Replace Base]
|-
| OnePlus One
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/oneplus-one-replacement-earpiece-speaker-original Replace Base]
|-
| OnePlus X
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/oneplus-x-replacement-earpiece-speaker-original Replace Base]
|-
| PinePhone
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
|
|-
| Xiaomi Mi A1
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/for-xiaomi-mi-a1-replacement-ear-piece-speaker-oem Replace Base]
|-
| Xiaomi Redmi Note 4
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/for-xiaomi-redmi-note-4-replacement-ear-piece-speaker-oem Replace Base]
|}

'''Notes'''

¹ The earpiece is too thin, it can work with padding to keep the contacts together.

² Audio playback is very low quality.

==List of earpieces that are too large for the PinePhone (Pro)==

The following devices are known to have replacement earpieces with dimensions too large to fit inside the PinePhone or PinePhone Pro.

* Blackberry Classic Q20
* HTC Desire 500
* HTC M10
* Huawei Honor 7A
* Huawei Mate 10 Pro
* Huawei Y7 Prime 2018
* OnePlus 2
* Oppo Reno 5 4G
* Sony Xperia X Compact
* Sony Xperia XA1 Ultra
* Sony Xperia XP X Performance
* Sony Xperia XZ

PinePhone (Pro) replacement earpieces

2023-07-13T00:47:58Z

Sethi: Clarify what is low quality about the LG earpiece.

The "earpiece" refers to the small speaker at the top of the phone.

The earpiece is not available to purchase from the PINE64 Store. However, it is possible to buy a replacement earpiece for another device, and install it in a PinePhone or PinePhone Pro. This documents earpieces that have been tested by the community, and verified to work.

Note that the earpiece dimensions for both the PinePhone and PinePhone Pro are 12x6x2 mm. When looking into other earpieces not found in this list, aim for these dimensions.

{| class="wikitable sortable"
! Earpiece !! PinePhone !! PinePhone Pro !! Where to Buy
|-
| LG K8 2017 M200N
| style="background:#FFB; | Kind of ¹
| style="background:#FFC7C7; | Broken
| [https://www.replacebase.co.uk/for-lg-k8-2017-m200n-replacement-ear-piece-speaker-oem Replace Base]
|-
| Nokia 5
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/for-nokia-5-replacement-ear-piece-speaker-with-adhesive-oem Replace Base]
|-
| Nokia 7
| style="background:#9EFF9E; | Works ²
| style="background:#9EFF9E; | Works ²
| [https://www.replacebase.co.uk/for-nokia-7-replacement-ear-piece-speaker-unit-module-oem Replace Base]
|-
| Nokia X5
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/for-nokia-x5-replacement-earpiece-speaker-unit-oem Replace Base]
|-
| OnePlus One
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/oneplus-one-replacement-earpiece-speaker-original Replace Base]
|-
| OnePlus X
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/oneplus-x-replacement-earpiece-speaker-original Replace Base]
|-
| PinePhone
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
|
|-
| Xiaomi Mi A1
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/for-xiaomi-mi-a1-replacement-ear-piece-speaker-oem Replace Base]
|-
| Xiaomi Redmi Note 4
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/for-xiaomi-redmi-note-4-replacement-ear-piece-speaker-oem Replace Base]
|}

'''Notes'''

¹ The earpiece is too thin, it can work with padding to keep the contacts together.

² Audio playback is very low quality.

==List of earpieces that are too large for the PinePhone (Pro)==

The following devices are known to have replacement earpieces with dimensions too large to fit inside the PinePhone or PinePhone Pro.

* Blackberry Classic Q20
* HTC Desire 500
* HTC M10
* Huawei Honor 7A
* Huawei Mate 10 Pro
* Huawei Y7 Prime 2018
* OnePlus 2
* Oppo Reno 5 4G
* Sony Xperia X Compact
* Sony Xperia XA1 Ultra
* Sony Xperia XP X Performance
* Sony Xperia XZ

PinePhone (Pro) replacement earpieces

2023-07-13T00:46:09Z

Sethi:

The "earpiece" refers to the small speaker at the top of the phone.

The earpiece is not available to purchase from the PINE64 Store. However, it is possible to buy a replacement earpiece for another device, and install it in a PinePhone or PinePhone Pro. This documents earpieces that have been tested by the community, and verified to work.

Note that the earpiece dimensions for both the PinePhone and PinePhone Pro are 12x6x2 mm. When looking into other earpieces not found in this list, aim for these dimensions.

{| class="wikitable sortable"
! Earpiece !! PinePhone !! PinePhone Pro !! Where to Buy
|-
| LG K8 2017 M200N
| style="background:#FFB; | Kind of ¹
| style="background:#FFC7C7; | Broken
| [https://www.replacebase.co.uk/for-lg-k8-2017-m200n-replacement-ear-piece-speaker-oem Replace Base]
|-
| Nokia 5
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/for-nokia-5-replacement-ear-piece-speaker-with-adhesive-oem Replace Base]
|-
| Nokia 7
| style="background:#9EFF9E; | Works ²
| style="background:#9EFF9E; | Works ²
| [https://www.replacebase.co.uk/for-nokia-7-replacement-ear-piece-speaker-unit-module-oem Replace Base]
|-
| Nokia X5
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/for-nokia-x5-replacement-earpiece-speaker-unit-oem Replace Base]
|-
| OnePlus One
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/oneplus-one-replacement-earpiece-speaker-original Replace Base]
|-
| OnePlus X
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/oneplus-x-replacement-earpiece-speaker-original Replace Base]
|-
| PinePhone
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
|
|-
| Xiaomi Mi A1
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/for-xiaomi-mi-a1-replacement-ear-piece-speaker-oem Replace Base]
|-
| Xiaomi Redmi Note 4
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/for-xiaomi-redmi-note-4-replacement-ear-piece-speaker-oem Replace Base]
|}

'''Notes'''

¹ The earpiece is too thin, it can work with padding to keep the contacts together.

² Very low quality.

==List of earpieces that are too large for the PinePhone (Pro)==

The following devices are known to have replacement earpieces with dimensions too large to fit inside the PinePhone or PinePhone Pro.

* Blackberry Classic Q20
* HTC Desire 500
* HTC M10
* Huawei Honor 7A
* Huawei Mate 10 Pro
* Huawei Y7 Prime 2018
* OnePlus 2
* Oppo Reno 5 4G
* Sony Xperia X Compact
* Sony Xperia XA1 Ultra
* Sony Xperia XP X Performance
* Sony Xperia XZ

PinePhone (Pro) replacement earpieces

2023-07-13T00:43:41Z

Sethi: Document various replacement earpieces that can or can't be used with the PinePhone or PinePhone Pro.

The "earpiece" refers to the small speaker at the top of the phone.

The earpiece is not available to purchase from the PINE64 Store. However, it is possible to buy a replacement earpiece for another device, and install it in a PinePhone or PinePhone Pro. This documents earpieces that have been tested by the community, and verified to work.

Note that the earpiece dimensions for both the PinePhone and PinePhone Pro are 12x6x2 mm. When looking into other earpieces not found in this list, aim for these dimensions.

{| class="wikitable sortable"
! Earpiece !! PinePhone !! PinePhone Pro !! Where to Buy
|-
| LG K8 2017 M200N
| style="background:#FFB; | Kind of ¹
| style="background:#FFC7C7; | Broken
| [https://www.replacebase.co.uk/for-lg-k8-2017-m200n-replacement-ear-piece-speaker-oem Replace Base]
|-
| Nokia 5
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/for-nokia-5-replacement-ear-piece-speaker-with-adhesive-oem Replace Base]
|-
| Nokia 7
| style="background:#9EFF9E; | Works ²
| style="background:#9EFF9E; | Works ²
| [https://www.replacebase.co.uk/for-nokia-7-replacement-ear-piece-speaker-unit-module-oem Replace Base]
|-
| Nokia X5
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/for-nokia-x5-replacement-earpiece-speaker-unit-oem Replace Base]
|-
| OnePlus One
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/oneplus-one-replacement-earpiece-speaker-original Replace Base]
|-
| OnePlus X
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/oneplus-x-replacement-earpiece-speaker-original Replace Base]
|-
| PinePhone
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
|
|-
| Xiaomi Mi A1
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/for-xiaomi-mi-a1-replacement-ear-piece-speaker-oem Replace Base]
|-
| Xiaomi Redmi Note 4
| style="background:#9EFF9E; | Works
| style="background:#9EFF9E; | Works
| [https://www.replacebase.co.uk/for-xiaomi-redmi-note-4-replacement-ear-piece-speaker-oem Replace Base]
|}

'''Notes'''

¹ The earpiece is too thin, it can work with some padding to keep the contacts together.

² Very low quality.

==List of earpieces that are too large for the PinePhone (Pro)==

The following devices are known to have replacement earpieces with dimensions too large to fit inside the PinePhone or PinePhone Pro.

* Blackberry Classic Q20
* HTC Desire 500
* HTC M10
* Huawei Honor 7A
* Huawei Mate 10 Pro
* Huawei Y7 Prime 2018
* OnePlus 2
* Oppo Reno 5 4G
* Sony Xperia X Compact
* Sony Xperia XA1 Ultra
* Sony Xperia XP X Performance
* Sony Xperia XZ

PinePhone Carrier Support

2023-07-09T21:07:06Z

Sethi: Updated row I originally created to show stable calling support.

{{under construction}}

This page contains hints on setting up cellular network connectivity for specific carriers.
For more general information, see the carrier support section of [[PinePhone#Modem]]. For the APN settings see [[PinePhone APN Settings]].

== Check compatibility ==

To check if the PinePhone is supported on your carrier:

Search for your carrier on [https://www.frequencycheck.com/ frequencycheck.com] and compare the carrier's LTE/GSM/WCDMA frequencies to the PinePhone's supported frequencies (listed in the [[File:Quectel_EG25-G_LTE_Standard_Specification_V1.3.pdf]] modem specification sheet).

It is likely that there will be a few frequencies that your carrier uses which are not supported by the PinePhone. Not all of the carrier's frequencies need to be supported by the PinePhone for it to work - as long as ''most'' of them are supported, you will still get good coverage.

== Tested and working carriers ==

The following is a list of carriers which has been tested by users and confirmed to be working (excerpt):

=== Asia ===

{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
| Japan || SoftBank Mobile || Not tested || Unsupported by carrier || No || No || Mobian Phosh, December 2020
|-
| Japan || 楽天モバイル / Rakuten Mobile || Unsupported by carrier || Unsupported by carrier || Yes || Yes || Mobian Phosh, January 2021
|-
| Japan || 楽天モバイル / Rakuten Mobile || Unsupported by carrier || Unsupported by carrier || Yes || No || Manjaro Plasma Mobile February 2021
|-
| Japan || NTT Docomo || Yes || Not tested || Yes || Yes || Mobian Phosh, February 2021
|-
| India || Vodafone / Vi India || Yes || Not tested || Yes || Yes || DanctNIX (Arch Linux ARM) with Phosh, March 2021
|-
| Malaysia || Celcom || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| Malaysia || Maxis || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| Malaysia || U-Mobile || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| Malaysia || Yes || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| South Korea || KT || Yes || Not tested || Yes || Yes || Manjaro Phosh, June 2021
|-
| China || China Mobile || Yes || Not tested || Yes || No || Mobile NixOS, December 2021
|-
| China || China Telecom || Yes (hack needed) || Not tested || Yes (hack needed) || No || AOSC OS Phosh, January 2022
|-
| Japan || 楽天モバイル / Rakuten Mobile || Yes || Not tested || Yes || Yes || Mobian Phosh, January 2022 (revised from January 2021)
|-
| China || China Unicom || Yes || Not tested || Yes || Yes || [https://postmarketos.org/ pmOS] 22.06.3 Phosh, [[PineModems#Bootloader_unlocking | BLunlck'd]], [[PinePhone#Firmware_update|upd'd]] to [https://github.com/Biktorgj/quectel_eg25_recovery/tree/EG25GGBR07A08M2G_30.006.30.006 *8M2G_30.006*], November 2022
|}

=== Africa ===

{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129
|-
|}

=== Europe ===
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Ukraine || KyivStar || Yes || Not tested || Yes || Yes || Mobian Phosh(11Nov21)
|-
|-
| Ukraine || Vodafone || Yes || Not tested || Yes || Yes || Manjaro ARM Phosh(29Jun22)
|-
| Sweden || Fello (uses Telia network) || Yes || No (data and MMS APN are different) || Yes || Yes || Mobian Phosh, October 2022
|-
| Sweden || Hallon (uses Tre network) || Yes || Yes (when manually selecting the MMS APN) || Yes || Yes || Mobian Phosh, October 2022
|-
| Sweden || Comviq (uses Tele2 network) || Yes || Yes (when manually selecting the MMS APN) || Yes || Yes || Mobian Phosh, October 2022
|-
| Sweden || Tele2 || Yes || Not tested || Yes || Not tested || Manjaro ARM Posh
|-
| Sweden || Telenor SE || Not tested || Not tested (should NOT work, data and MMS APN are different) || Yes || Not tested || Manjaro Plasma Mobile beta2
|-
| UK || RWG || Yes || Not tested || Yes || Yes [https://neilzone.co.uk/2022/06/rwg-mobile-apn-for-non-data-sims (special APN)] || postmarketOS Phosh (Edge) - 11 March 2023
|-
| UK || Three || Yes || Not tested || Yes || Yes || Manjaro Plasma Mobile beta2
|-
| UK || Vodafone || Yes || Not tested || Yes || Yes || ALARM & pmOS (Phosh?), modem FW latest - 26 Feb 21
|-
| UK || Sky Mobile (O2) || Yes || Not tested || Yes || Yes || ArchLinux Phosh (20210908 image, fully updated) - 3 October 2021
|-
| UK || Smarty Mobile (Three) || Yes || Yes || Yes || Yes || Arch Linux SXMO (Wayland) - 23 March 2022
|-
| UK || Honest Mobile (Three) || Yes || No || Yes || Yes || postmarketOS 23.06 (Phosh) - 9 July 2023
|-
| France || Orange || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021
|-
| France || SFR || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021
|-
| France || Free || Yes || Not tested || Yes || Yes || pmOS SXMO (Wayland) - 27 March 2022
|-
| Czech Republic || O2 || Yes (only on 2G) || Not tested || Yes || Yes || Mobian Phosh (20210517 image up to date) - 2 June 2021
|-
| Germany || Congstar || Yes || Not tested || Yes || Yes (IPv4 & IPv6) || Mobian (Megi's kernel 5.13.0-rc4, apt up-to-date) with Phosh, 2021-06-07
|-
| Germany || E-Plus || Yes (sending only 2G) || Not tested || Yes || Yes || Manjaro Phosh and postmarketOS, 2021-10-15
|-
| Germany || Telekom || Yes || Not tested || Yes || Not tested || Mobian Phosh (5.10-sunxi64), 2021-07-28
|-
| Germany || O2 / Telefonica || Yes || Not tested || Yes || Not tested || Plasma Mobile
|-
| Hungary || Telekom || Yes || Not tested || Yes || Yes (IPv4) || Manjaro Phosh Beta 12, 2021-07-30
|-
| Hungary || Telenor/Yettel || Yes || Not tested || Yes || Yes || Mobian-Phosh-20210517, 2021-09-24
|-
| Denmark || CBB || Yes || Not tested || Yes || Yes || Manjaro Plasma Mobile Beta 5, 2021-06-30
|-
| Belgium || Telenet || Yes || Not tested || Yes || Yes || postmarketOS v20.05, v21.03, v21.06 and edge, 2021-08-15
|-
| Belgium || CARREFOUR || Yes || Not tested || Yes || Yes || postmarketOS v20.05, v21.03, v21.06 and edge, 2021-08-15
|-
| Poland || Play || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta 18, 2021-11-14
|-
| Poland || Orange || Yes || No || Yes || Yes (IPv4 & IPv6) || Manjaro Phosh v21.10, 2021-12-23
|-
| Poland || Premium Mobile || Yes || No || Yes || Yes || Manjaro Phosh v22.01, 2022-01-13
|-
| Italy || WindTre Italy || Yes || Not tested || Yes || Yes || Archlinux ARM Plasma Mobile
|-
| Switzerland || Salt || Yes || Not tested || Yes || Yes || Phosh on Mobian + Arch
|}

=== North America ===

{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| USA || AT&T || Yes || Yes || Yes || Yes ||
* Mobian - Phosh
|-
| USA || T-Mobile || Yes || No || Yes || Yes ||
* Arch Linux Arm 2020/11/29
* Mobian - Phosh
* Manjaro - KDE Plasma Mobile
|-
| USA || T-Mobile || Yes || Yes || Yes || Yes ||
* Mobian Bookworm (Phosh) (2022-03-08)
|-
| USA || MetroPCS (T-Mobile) || Yes || No || Yes || Yes ||
* Arch Linux Arm (Phosh,SXMO) 2021/04/29
* Manjaro - Phosh 2021/04/29
* Mobian - Phosh 2021/3/20
|-
| USA || T-Mobile || Yes - buggy || No || Yes - buggy || Yes - buggy ||
* Manjaro - Plasma Dev 2020/11/21
* Ubuntu Touch - 2020/11/26
* KDE Neon 2020/11/02
|-
| USA || Mint Mobile (T-Mobile) || Yes || Yes || Yes || Yes ||
* Mobian - Phosh 2021/3/14
* postMarketOS - Phosh, Sxmo, Plasma Mobile 2021/5/26
* Ubuntu Touch 2021/5/24
* Manjaro - Phosh 2022/3/25
|-
| USA || Patriot Mobile (T-Mobile) || Yes || Yes || Yes || Yes ||
* DanctNIX (Arch Linux ARM) - Phosh 2023/03/29
|-
| USA || Tello (T-Mobile) || Yes || Yes || Yes || Yes ||
* DanctNIX (Arch Linux ARM) - Phosh 2022-07-09
|-
| USA || TracFone || No || No || No || No ||
* postMarketOS - Phosh 2022/06/28
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
* Mobian - Phosh 2021/3/1
|-
| USA || US Mobile || Yes || Not tested || Yes || Not Tested ||
* Mobian - Phosh 2022/01/09
|-
| USA || Verizon || No || No || No || No ||
* Ubuntu Touch 2021/5/24 (You can occasionally get the settings to work with Verizon, but it seems like the settings automatically changes the carrier to the wrong one after a few minutes)
|-
| USA || Verizon || Not tested || Not tested || Yes || Not via gui ||
* Manjaro - KDE Plasma Mobile 2021/5/10
|-
| USA || Verizon || Yes || Not tested || Yes || Not via gui ||
* Manjaro - Phosh 2021/5/31
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
* postmarketOS - Phosh 2021/5/31
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
* Arch - Phosh 2021/5/31
|-
| Canada || Freedom || Yes || Not tested || Yes || Yes ||
*Arch Pinephone - Phosh (APN: internet.windmobile.ca), 2021/4/25
|-
| Canada || SpeakOut || Yes || Not tested || Yes || Not tested ||
* Mobian - Phosh 2021/11/18
|-
| USA || Consumer Cellular (AT&T) || Yes || No || Yes || Yes ||
* Manjaro - Phosh 2021/06/26
|-
| USA || Google Fi (T-Mobile) || Yes || No || Yes || Yes ||
* Arch Linux Arm - Phosh 0.10.2 2021/05/29
|-
| Mexico || Telcel || Yes || Not tested || Yes || Yes ||
* Mobian - Phosh Weekly 2022/04/13
* PostmarketOS - SXMO De Sway v21.12 (stable) 2022/04/13
* PostmarketOS - Phosh v21.12 (stable) 2022/04/13
* PostmarketOS - Plasma Mobile v21.12 (stable) 2022/04/13
* PostmarketOS - sxmo edge 2021/09/09
|-
| USA || Ting || Yes || Yes - buggy || Yes || Yes ||
* Manjaro - Phosh 2021/12/10
|-
| USA || Simple Mobile || Yes || Yes || Yes || Yes ||
* Mobian - Phosh - Make sure APN is "Simple" in settings (note uppercase S)
|-
|}

=== South America ===

{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129
|-
|}

=== Australia / Oceania ===

{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129
|-
| Australia || Aldi Mobile（Telstra） || Yes || Untested || Yes || Untested || Mobian, mobian 6.1-rockchip kernel, 2023-06-08 with Phosh and Plasma (modem needs to be enabled from Phosh)
|-
| Australia || Beyond (Telstra) || Yes || Yes || Yes || Yes || Manjaro Phosh Beta 20.
|-
| Australia || Belong (Telstra) || Yes || Yes || Yes || Yes || Arch (Danctnix), Feb 2022.
|-
| Australia || Optus || Yes || No. Ticket lodged with Chatty and mmsd re multiple APN issue || Yes || Yes || Manjaro Phosh Beta 20. Manjaro Plasma Mobile Beta 9 (Data working with this release). SXMO (Danctnix and PMOS edge December 2021).
|-
| Australia || Amaysim (Optus) || Yes || No. Ticket lodged with Chatty and mmsd re multiple APN issue || Yes || Yes || Manjaro Phosh
|-
| Australia || OPTUS (Dodo) || || ||Yes|| || Manjaro Plasma Mobile 5.23.4, 2021-12.27 (deepsleep disrupts settings)
|-
| Australia || Kogan Mobile（Vodafone） || Yes || Yes after manually configure MMS APN in Phosh Chat || Yes || Yes || Mobian, mobian 6.1-rockchip kernel, 2023-06-08 with Phosh and Plasma (modem needs to be enabled from Phosh)
|-
| Australia || Vodafone || Yes || Yes || Yes (No VoLTE) || Yes || pmOS Edge 5.15.3 kernel, 2022-02-10 with Phosh
|}

=== Middle East ===
{| class="wikitable sortable"
!Country || Carrier name || SMS working || USSD working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Israel|| Cellcom prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Cellcom Talkman|| receive+notify|| YES || YES (when manually selecting the MMS APN) || ring(VoLTE not working) || YES || on mobian Feb 04, 2022, Earthquake early warning system did not show a notification on Feb 07, 2022
|-
|-
| Israel|| Cellcom Talkman|| NO || NO || NO || ring+ notify (VoLTE not working)|| YES || on Plasma Mobile Feb 04, 2022
|-
|-
| Israel|| Golan TC || receive+notify|| YES || NA || ring+ notify (VoLTE not working) || Yes || on mobian/phosh March 13 2022
|-
|-
| Israel|| Partner prepay || receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Pelephone prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Hot prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| 019 prepay|| No || NA || NA ||Bars only || NA || on PmOS Sxmo May 14 2021.
|-
|}

== Special carrier notes ==

{{Warning|This section contains providers which do not work or require special settings or actions to work.}}

Some carriers might support only certain frequencies or might require certain settings in Ofono or ModemManager. The following is a list of collected notes for carriers regarding special settings, hints or information:

=== USA ===

==== AT&T ====

According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page], AT&T's primary bands are 12 and 17 - 700ac and 700 MHz respectively. Phone and SMS with PinePhone work out-of-the-box with AT&T. If you transfer a SIM card from another phone you were using with AT&T, you may need to activate the PinePhone through [https://www.att.com/buy/wireless/byod/byod AT&T's website]. Calls and SMS messages work. 4G and MMS work if [https://www.att.com/support/article/wireless/KM1062162/ these settings] are used for APN, MMSC, and Proxy.

AT&T may drop support with their network upgrade in the near future like their child company Cricket Wireless already has. [https://www.att.com/ecms/dam/att/consumer/help/pdf/Devices-Working-on-ATT-Network.pdf This page] lists their supported devices for their new network.

==== Consumer Cellular ====

Consumer Cellular is a MVNO that uses both AT&T and T-Mobile networks. On the AT&T network LTE data works without special configuration. If you transfer a SIM card from another phone to the PinePhone, you may need to contact customer support in order for them to register the IMEI association to the correct hardware; in one case it was first incorrectly identified as a Samsung Google Nexus Prime before later being correctly identified by the modem model Quectel EG25-G. Customer support also explicitly enabled VoLTE on the device. After VoLTE instructions on this site were followed and APN instructions on the Consumer Cellular site were followed, VoLTE was confirmed working.

==== Cricket Wireless ====

Cricket wireless is a MVNO that uses AT&T's network. VoLTE was fully supported, but the PinePhone is no longer considered a compatible device in the US by the carrier (as of March 2021).

==== Faith Wireless ====

Faith Wireless is a MVNO that uses AT&T's network. VoLTE was fully supported, but the PinePhone comes up as a Mobile Broadband Device. Faith Wireless does not service Mobile Broadband Devices. (As of February 2022)

==== SimpleMobile ====

SimpleMobile is a T-Mobile prepaid MVNO operating in the United States. 4G LTE, VoLTE, data, and SMS all work on the PinePhone after activation. Activation can be done online without extra software or assistance, go to https://www.simplemobile.com/activation/byopcollectsim and make sure you have your SIM card and IMEI ready.

==== Sprint ====

Sprint is currently not supported due to unknown reasons. Any input regarding this issue is highly appreciated.

==== T-Mobile ====

According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page], T-Mobile's primary frequency band for the United States is 12 (700ac MHz).

T-Mobile's bands and protocols are summarized on [https://www.frequencycheck.com/carriers/t-mobile-united-states this page].

While the PinePhone's modem does support all LTE bands that T-Mobile uses in the US (And is one of the best choices for band support with the PinePhone's modem in the US), VoLTE is still listed as "Under development" by the modem manufacturer. T-Mobile's system also does not list the PinePhone as a compatible device due to this lack of official VoLTE support. The modem is capable of working on T-Mobile with VoLTE support enabled.

==== Verizon ====

According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page], Verizon's primary frequency band for the United States is 13 (700 MHz). Verizon's bands and protocols are summarized on [https://www.frequencycheck.com/carriers/verizon-wireless-united-states this page]. According to the same page, Verizon might restrict their network to only approved devices.

Some users reported that they were able to activate their Verizon SIM by using an Verizon-approved burner phone and then inserting the SIM into the PinePhone.

==== TracFone ====

Following TracFone's [https://www.verizon.com/about/news/verizon-completes-tracfone-wireless-inc-acquisition acquisition by Verizon], support for the AT&T and T-Mobile bands has been deprecated as of early June 2022. TracFone has the same issues with connecting as Verizon, as they now exclusively use Verizon's frequency band.

==== Google Fi ====

Only T-Mobile service works currently, not US Cellular or Sprint. The APN is <code>h2g2</code>. Information from [https://forum.pine64.org/showthread.php?tid=11675&page=7 the forum].

Bear in mind that initial activation of the SIM card is not possible without an Android phone running Google Apps.

It should also be noted that Google uses a non-standard MMS implementation that is unlikely to be supported on the PinePhone at any point.

=== Europe ===

==== Telekom Germany ====

With low signal, there may be loud interference noise audible in calls on the receiving end. It has not yet been tested whether or not this problem is carrier specific. An easy fix is extending the modem antenna with aluminum foil (or similar) inside the back cover of the phone.

==== Orange Poland ====

Setting up dual stack IPv4 and IPv6 may require [https://etherpad.gnome.org/p/dx7pbkPMCytMLMRl1eyo extra work], because the carrier provides IPv4 connectivity on internetipv6 APN via a protocol called CLAT/NAT64.

==== Sweden ====

Calls, SMS, and data (2G, 3G, and 4G) should work out of the box (tested three carriers on Mobian Phosh). On about half of Swedish carriers, MMS works when set manually, the rest have different data APN and MMS APN. VoLTE (i.e. 4G calls) did not work out of the box ([https://github.com/Eliot-Roxbergh/notes_pinephone for me]) but worked well after [https://github.com/the-modem-distro/pinephone_modem_sdk/blob/kirkstone/docs/FLASHING.md#adsp-versions updating firmware] to ADSP Version 01.003.01.003 and installing [https://github.com/the-modem-distro/pinephone_modem_sdk Pinephone Modem SDK]. Regarding call quality, from my experience; 3G has the best quality, then 4G also works well although you often hear electrical white noise sound (on your side), 2G works well but there is a risk of strong noise when on bad coverage (this can affect both sides of the call). Voicemail should work, you should get a SMS when you have a missed call etc. Only issue I had was that when getting sent to voicemail in a call, for some target carriers (?) it was completely silent.

=== Asia ===

==== China Telecom ====

The baseband itself ships with bad (for CDMA, which isn't supported by EG25-G) MBN file for CT, so a force change of MBN file to the generic one is needed to get VoLTE (thus SMS+Call) work.

Run the following AT commands to force ROW_Generic_3GPP which can support VoLTE on CT:

AT+QMBNCFG="autosel",0
AT+QMBNCFG="select","ROW_Generic_3GPP"
AT+QCFG="ims",1

==== SoftBank ====

SoftBank USIM cards are IMEI-locked, and on top of that will only work on either Android or iOS. A free SIM is available, but that one is data only. The same problem might exist with MVNO's who make use of the SoftBank network, and therefore it's advised to pick either NTT docomo or au as the MNO.

== Known issues ==

Known issues:

* The [https://www.frequencycheck.com/models FrequencyCheck model page] does not list either Pine64 or the PinePhone.
* T-Mobile's system does not list the PinePhone as a compatible device due to the lack of official VoLTE support from the manufacturer, despite the fact that it does work.
* MMS doesn't currently work in any distribution on the PinePhone by default. This means images and group chats will not work in text messages.
* Some providers may allow only certain known devices identified by their [https://en.wikipedia.org/wiki/Type_Allocation_Code Type Allocation Code].

== MMS workarounds ==

These scripts allow partial MMS support on a [[PinePhone]] in distributions without working MMS support:

* JMMS: [https://git.sr.ht/~amindfv/jmms]
* silvermms: [https://gitlab.com/5ilver/silvermms]
* MMS via Matrix with mmmpuppet: [[PinePhone MMS with Matrix]]

There is a Haskel MMS client. MMS can also be manually composed with mmsd on the command line.

== Resources ==

* IMEI - [https://en.wikipedia.org/wiki/International_Mobile_Equipment_Identity International Mobile Equipment Identity]

[[Category:PinePhone]]

User:Sethi

2023-03-25T09:29:24Z

Sethi:

Hey! Welcome to my profile, though I think you'd be better off stalking me somewhere else.

* https://gitlab.com/SethFalco
* https://github.com/SethFalco
* https://fosstodon.org/@Sethi

ROCKPro64 Software Releases

2023-03-20T17:33:43Z

Sethi: /* postmarketOS */

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

== Linux ==
=== AOSC ===
[[File:aosc.png|right|100px]]

'''AOSC OS''' is a general purpose Linux distribution that strives to simplify user experience and improve free and open source software for day-to-day productivity. Originally AnthonOS (an OpenSUSE derivative built with SUSE Studio), then remade as a Debian derivative with customized KDE 4 UI and CJK support. To learn more about AOSC, please visit the official [https://aosc.io/ AOSC website]

Download:
* https://aosc.io/downloads/ (supports the microSD card and eMMC, 8GB or more)

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

----

=== Armbian ===
[[File:armbian.png|right|100px]]

'''Armbian''' is a Linux distribution designed for ARM boards. They are usually Debian or Ubuntu flavored. To find out more about Armbian and available options please visit their [https://www.armbian.com/rockpro64/ site]. If you are booting from a Micro SD card, then both Linux kernel versions will work. If you are trying to boot from an eMMC module then the 4.4.y will work, but the newer 5.10.y will not.

Download:
* https://dl.armbian.com/rockpro64/archive/

----

=== Batocera Linux ===
[[File:batocera.png|right|100px]]

'''Batocera Linux''' is an open-source and completely free retro-gaming distribution that can be copied to a USB stick or an SD card with the aim of turning any computer/nano computer into a gaming console during a game or permanently. Visit the project's website here (https://batocera.org/). You can follow the ongoing discussion about batocera.linux on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=7084)

Download:
* https://batocera.org/download

----

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

'''Debian''' is an operating system and a distribution of free software. See the forum thread [https://forum.pine64.org/showthread.php?tid=9744 here].

Download:
* [https://deb.debian.org/debian/dists/bullseye/main/installer-arm64/current/images/netboot/SD-card-images/ Debian 11 Bullseye] (recommended)
* [https://deb.debian.org/debian/dists/bookworm/main/installer-arm64/current/images/netboot/SD-card-images/ Debian 12 Bookworm]
* [https://d-i.debian.org/daily-images/arm64/ Daily netboot images]

Instructions:
* Download: <code>firmware.rockpro64-rk3399.img.gz</code>
* Download: <code>partition.img.gz</code>
* Create the disk image:
** For Linux: <code>zcat firmware.rockpro64-rk3399.img.gz partition.img.gz > complete_image.img</code>
** For Mac: <code>gzcat firmware.rockpro64-rk3399.img.gz partition.img.gz > complete_image.img</code>
* Write the image to your boot device:
** For Linux: <code>dd if=complete_image.img of=your_chosen_boot_device bs=4M</code>
** For Mac: see [[Getting started]]

Notes:
* An Ethernet connection is required for the above installer
* Remember to leave some space before your first partition for u-boot! You can do this by creating a 32M size unused partition at the start of the device.
* See the [[ROCKPro64#No_Video_or_GPU_Acceleration_on_Debian|troubleshooting section]] if you encounter issues with GPU acceleration.

----

=== DietPi ===
[[File:dietpi.png|right|100px]]

'''DietPi''' is a lightweight, yet easy to setup and feature-rich Linux distribution, based on Debian. To find out more about DietPi, please visit the [https://dietpi.com/docs/ official documentation]. Discuss the ROCKPro64 build on the [https://forum.pine64.org/showthread.php?tid=12532 PINE64 forum thread].

Download:
* [https://dietpi.com/downloads/images/DietPi_ROCKPro64-ARMv8-Bullseye.7z Direct download from dietpi.com]

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

----

=== LibreELEC ===
[[File:libreelec.jpg|right|100px]]
'''LibreELEC''' is a lightweight 'Just enough OS' Linux distribution purpose-built for Kodi on current and popular mediacentre hardware.

Download:
* [https://libreelec.tv/downloads/rockchip/ Official LibreELEC build image] (look for PINE64 RockPro64-LibreELEC-RK3399.arm-x.x.x-rockpro64.img.gz, supports microSD card and the eMMC module of 8GB or more.)

{{Info|Unzip and flash the image to a microSD card or eMMC module, for example using ''dd''.}}

----

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

'''Manjaro''' is a user-friendly Linux distribution based on the independently developed Arch operating system. To learn more about Manjaro please visit [https://forum.manjaro.org/c/arm/releases/102 Manjaro forum].

Download:
* [https://github.com/manjaro-arm/rockpro64-images/releases from Github]

Notes:
* Decompress the image (<tt>unxz</tt>) before flashing, or decompress on the fly while flashing (<tt>xzcat</tt> in a root shell, Etcher, ...)
* A display and keyboard will be required for first boot.
* Initial setup includes: keyboard layout, locale, username, user password, and root password.
* The installer will expand the root partition to use the remaining space on the storage device you've flashed.

----

=== Nems Linux ===
[[File:nems.jpg|right|100px]]

'''NEMS''' stands for ''Nagios Enterprise Monitoring Server'' and it is a modern pre-configured, customized and ready-to-deploy Nagios Core image designed to run on low-cost micro computers. To find out more about NEMS on the PINE64 and available tweaks to the installation please visit the [https://forum.pine64.org/showthread.php?tid=7306 PINE64 forum thread].

Download:
* [https://nemslinux.com/download/nagios-for-pine64.php Download page] with torrent seed or direct download.

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

----

=== 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. More information can be found on the [https://nixos.wiki/wiki/NixOS_on_ARM/PINE64_ROCKPro64 NixOS wiki].

Download:
* [https://github.com/AshyIsMe/nixos-installer-rockpro64 nixos-installer-rockpro64]

----

=== OpenMediaVault ===
[[File:omv.png|right|100px]]

'''OpenMediaVault''' is the next generation network attached storage (NAS) solution, [https://www.openmediavault.org/ click this link to OMV main page] to learn more. Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6308 here]

Download:
{{Outdated release}}
* Stretch 32bit (armhf): [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/stretch-openmediavault-rockpro64-0.8.3-1141-armhf.img.xz Direct download from ayufan's github]
* Stretch 64bit (aarch64): [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/stretch-openmediavault-rockpro64-0.8.3-1141-arm64.img.xz Direct download from ayufan's github]

Notes:
* You need to enable root login in OMV WebGUI
* [http://omv-extras.org/joomla/index.php/omv-plugins-3/3-stable OpenMediaVault Plugins]

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! TTY and SSH, except OMV
| <code>rock64/rock64</code>
|-
! WebGUI Login
| <code>admin/openmediavault</code>
|-
! TTY and SSH
| <code>root/openmediavault</code>
|}

----

=== OpenWrt ===
[[File:Openwrt logo square.png|right|100px]]

'''OpenWrt''' is a highly extensible GNU/Linux distribution for embedded devices (typically wireless routers). Unlike many other distributions for these routers, OpenWrt is built from the ground up to be a full-featured, easily modifiable operating system for your router. In practice, this means that you can have all the features you need with none of the bloat, powered by a Linux kernel that's more recent than most other distributions.

Download:
* https://openwrt.org/toh/pine64/rockpro64_v2.1

----

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

postmarketOS extends [https://www.alpinelinux.org/ Alpine Linux] to run on smartphones and other devices.
At the time of writing, the only user interface provided through prebuilt images for the ROCKPro64 is [https://plasma-bigscreen.org/ Plasma Bigscreen].

Download:
* https://postmarketos.org/download/

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

----

=== R-Cade ===
[[File:RCadeLogo.jpg|right|100px]]

Retro Center's '''R-Cade''', the 4K Media Center Arcade. [https://www.retro-center.com/about-r-cade/ RCade] Features 100+ retro-gaming systems, a lightweight web browser, and full 4K UHD media playback.

Download:
* [https://github.com/retro-center/rcade_releases/releases Direct download from Retro Center's GitHub] (USB, microSD and eMMC boot)

----

=== Recalbox ===
[[File:RB.png|right|100px]]

'''Recalbox''' allows you to re-play a variety of videogame consoles and platforms in your living room, with ease! Visit the project's website here (https://www.recalbox.com/). You can follow the ongoing discussion about Recalbox on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=7194)

Download:
{{Template:Outdated release}}
* [https://github.com/mrfixit2001/recalbox_rockpro64/releases download] release from mrfixit2001 github.

----

=== Retro Arena ===
[[File:retroarena.png|right|100px]]

'''Retro Arena''' community build for microSD and eMMC boot. This is a BETA and therefore is not update-able nor supported, however bugs or issues are appreciated to be identified and shared via the issues tab on our GitHub so that we can address them in the future. The Roshambo Case support is baked in with one major caveat due to kernel limitation: You can power the unit off by the POWER switch and the RESET button works 100% however to power the unit on you will need to manually plug/unplug the power cord. This limitation will not be present in future releases. You can follow the ongoing discussion about Retro Arena on the [https://forum.pine64.org/showthread.php?tid=7555 forum]

Download:
{{Outdated release}}
* [http://files.pine64.org/os/ROCKPro64/odroidretroarena/TheRA-RP64-BETA-0.8-FINAL.img.gz Direct download from pine64.org]

----

=== SkiffOS ===
[[File:SkiffOS-Icon-1.png|right|100px]]
Minimal cross-compiled OS optimized for hosting distributions in Docker containers. Provides the reliability of firmware with the ease-of-use of package managers. Uses the [http://buildroot.org Buildroot] cross-compilation tool for support for all Pine64 boards.

Use configuration packages to configure the distribution:
* core/gentoo: Gentoo optimized for Rockpro64
* core/nixos: NixOS arm64

You can also configure the skiff core yaml file to configure multiple distributions to run in parallel.

The boot-up OS can be upgraded independently from the containers.

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

----

=== Slackware ===
[[File:slackware.jpg|right|100px]]

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

Resources:
* [https://docs.slackware.com/slackwarearm:inst Installation instructions].
* [https://www.youtube.com/watch?v=uXAL9jz-yaA&list=PL1XOSJnvang3VLmqke2QbRitKtOD6Rm3t Installation video guide]

----

=== slarm64 ===

'''slarm64''' is an unofficial aarch64 / riscv64 Slackware Linux port. You can follow the ongoing discussion about slarm64 on the RockPro64 on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=6823) or this forum thread for more general slarm64 information: https://www.linuxquestions.org/questions/slackware-arm-108/slarm64-aarch64-unofficial-slackware-4175613287/.

Downloads:
* [http://dl.fail.pp.ua/slackware/images/rockpro64/ download] (supports microSD card, look for slarm64-current-aarch64-xfce-rockpro64-x.xx.x-build-xxxxxxxx.img.zst)

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

Flashing the distribution to the eMMC:
* Flash the image to micro SD, power up the board with micro SD and login
* Copy the image file to micro SD by using SFTP. The image file must have the ''.img'' file extension.
* After finish copy the file, power off the board and add eMMC module to the board
* Boot the board, run below command for flashing to eMMC module
* Run <code>dd if=[image file] of=/dev/mmcblkX bs=10M</code> (example: ''sudo dd if=slack-current-aarch64-xfce_29Sep18-4.4.162-rockpro64-build-20181126.img of=/dev/mmcblkX bs=10M'')
* then edit these two files in eMMC module:
** <code>mount /dev/mmcblk1p1 /media</code>
** <code>echo "rootdev=/dev/mmcblk1p1" >> /media/boot/uEnv.txt</code>
** <code>sed -i 's:mmcblk0p1:mmcblk1p1:' /media/etc/fstab</code>
* After that, power off the board and remove the microSD card. Then boot with only the eMMC module.

----

=== Twister OS ===
[[File:Twister_OS.png|right|100px]]

'''Twister OS''' brings a desktop computing experience for SBCs, right out-of-the-box. Including themes, applications, tools, and optimizations to get the most out of your SBC. For more information on Twister OS, please visit the [https://twisteros.com/ official site]. You can follow the ongoing discussion about Twister OS on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=12192).

Download:
* [https://twisteros.com/twisterarmbian.html Twister OS Armbian-Reforged XFCE Desktop image] (2.8GB, supports the microSD card and eMMC modules with 16GB and more)

{{Info|After flashing image with Etcher, edit /boot/armbianEnv.txt, replace the dtb name with rk3399-rockpro64.dtb.}}

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

----

=== Void Linux ===
'''Void Linux''' is a general purpose operating system, based on the monolithic Linux kernel. The official guide can be found at [https://docs.voidlinux.org/installation/guides/arm-devices/index.html Guide]. At this time there are no RockPro64 images available.

The following creates a bootable image from an existing Void Linux installation:
* <code>xbps-insall -Syu</code> to update the xbps installation of the installation
* create ROCKPro64 image with the ''void-mklive'' software (from github.com):
** create a rootfs via ''mkrootfs.sh'': <code>sh mkrootfs.sh -o void-aarch64-muls-ROOTFS-yyyymmdd.tar.xz</code>
** <code>sh mkplatformfs.sh rockpro64 void-aarch64-muls-ROOTFS-yyyymmdd.tar.xz</code>
** <code>sh mkimage.sh -s 7GiB void-rockpro64-PLATFORMFS-yyyymmdd.tar.xz</code>
* write image to sdcard or eMMC: <code>dd if='''IMAGE-FILENAME''' of='''DEVICENAME''' bs=2M</code>
* If ''mkplatformfs.sh'' errors with ''ROCKPro64 not supported'', install ''xbps-src'' from https://github.com/void-linux/void-packages and build the ROCKPro64 package.
* Tip: write a new U-Boot to the image if you see on the serial console the boot-up stalls:
** get the two U-Boot files from [https://pkgs.org/download/u-boot-rockpro64 pkgs.org], the aarch64 files:
** <code>dd if=idbloader.img of=DEVICENAME seek=64</code>
** <code>dd if=u-boot.itb of=DEVICENAME seek=16384</code>

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

== BSD Images ==
=== FreeBSD ===
[[File:Freebsd_Logo.png|right|100px]]

'''FreeBSD''' is an operating system used to power modern servers, desktops, and embedded platforms. The [https://wiki.freebsd.org/arm/RockChip#RockPro64 RockChip FreeBSD page] has instructions for installing FreeBSD. Version 13.0 and greater include prebuilt images.

Download:
* Images for various FreeBSD releases can be found [https://www.freebsd.org/where/ here]

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! SSH user (enabled by default)
| <code>freebsd/freebsd</code>
|-
! Root user
| <code>root/root</code>
|}

Notes:

* The wiki has instructions on [https://wiki.freebsd.org/arm/RockChip#Fan_Control_on_RockPro64 enabling the PWM cooling fan].

----

=== NetBSD ===
[[File:netbsd.png|right|100px]]
'''NetBSD''' is a free, fast, secure, and highly portable Unix-like Open Source operating system. To learn more about NetBSD please visit [https://www.netbsd.org/ NetBSD main page]

Download:
* [https://armbsd.org/ download] latest release build from NetBSD by select 64bit - RockPro64 (size: 339 MB)

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! Root user and SSH login
| <code>root/[none]</code>
|}

Notes:
* Instructions concerning enabling SSH can be found [https://www.netbsd.org/docs/guide/en/chap-boot.html#chap-boot-ssh here] or the bootable image from armbsd.org can have the MSDOS partition modified to setup SSH using [https://man.netbsd.org/creds_msdos.8 this] method.

----

=== OpenBSD ===
[[File:Puffy_mascot_openbsd.png|right|100px]]

'''OpenBSD''' is a security-focused, free and open-source, Unix-like operating system based on the Berkeley Software Distribution. Official instruction to get OpenBSD on ROCKPro64 is [https://www.openbsd.org/arm64.html here], and blogs on installation [https://github.com/jasperla/openbsd-rockpro64 is here] and [https://bsandro.tech/posts/openbsd-7.1-on-pine64-rockpro64/ here]. Forum discussion is [https://forum.pine64.org/forumdisplay.php?fid=109 here].

== Chromium OS ==
[[File:chromium.jpg|right|100px]]

The '''Chromium OS''' community build image for microSD card and eMMC module, version beta (R76). To learn more please visit the [https://forum.pine64.org/showthread.php?tid=7659 forum].

Download:
{{Outdated release}}
* https://github.com/ayufan-rock64/chromiumos-build/releases/

{{Info|Flash the image to a microSD card or an eMMC module, for example using ''dd''.}}

== Android ==
[[File:Android_logo_2019_(stacked).svg|right|100px]]

=== Android 9.0.0 ===

'''Stock for DD method [eMMC Boot] [20200804]'''
* Use 'dd' to write the image to the eMMC module using the USB-to-eMMC adapter module and boot. Using [https://www.balena.io/etcher/ Etcher] or another specialized SD writing tool is preferred.
* Please allow 3-5 minutes boot up time on first time for initialization
* Supports new RockPro64 AP6256 Wifi/BT module
* Support Sony IMX214 camera module and works on both MiPi-CSI ports
* This build supports PINE64 7" LCD panel with tablet UI (not Android TV)
* DD image for 8GB eMMC module
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200804_stock_android_9.0_emmcboot-8GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 7287fd0846616354615c8d3eff6a2a92
*** File Size: 602MB
* DD image for 16GB eMMC module
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200804_stock_android_9.0_emmcboot-16GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 78352bbf21198d062af8bab2217ee691
*** File Size: 611MB
* DD image for 32GB eMMC module
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200804_stock_android_9.0_emmcboot-32GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): c5c8dce419478f75f85f893ee4808dbd
*** File Size: 624MB
* DD image for 64GB eMMC module
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200804_stock_android_9.0_emmcboot-64GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): aab1cf4d30c4d16e6ce2672f3ecae935
*** File Size: 666MB

'''Stock for RK Flash tool [eMMC Boot] [20200804]'''
* Please unzip first and then using Android tool to flash in
* The OTG port located at USB type-C connector, needs USB type A to type C cable.
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20200708_stock_android_9.0_emmcboot.img.gz Direct download from pine64.org]
** MD5 (GZip file): 9ac830527814521e15b009fa2503c9e3
** File Size: 589MB

'''Stock for DD method [eMMC Boot] [20200708]
* Use 'dd' to write the image to the eMMC module using the USB-to-eMMC adapter module and boot. Using [https://www.balena.io/etcher/ Etcher] or another specialized SD writing tool is preferred.
* Please allow 3-5 minutes boot up time on first time for initialization
* Supports new RockPro64 AP6256 Wifi/BT module
* This build supports PINE64 7" LCD panel with tablet UI (not Android TV)
* DD image for 8GB eMMC module
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200708_stock_android_9.0_emmcboot-8GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): ef5f5a890a9270734e0adee21f006837
*** File Size: 597MB
* DD image for 16GB eMMC module
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200708_stock_android_9.0_emmcboot-16GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 179bd684a468f800a86f7c658a543bef
*** File Size: 606MB
* DD image for 32GB eMMC module
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200708_stock_android_9.0_emmcboot-32GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): d930b757c4427be07b83c37a9c8494a1
*** File Size: 630MB
* DD image for 64GB eMMC module
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200708_stock_android_9.0_emmcboot-64GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 09a970d68a10bdb3d6495d55860940e6
*** File Size: 660MB

'''Stock for RK Flash tool [eMMC Boot] [20200708]'''
* Please unzip first and then using Android tool to flash in
* The OTG port located at USB type-C connector, needs USB type A to type C cable.
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20200708_stock_android_9.0_emmcboot.img.gz Direct download from pine64.org]
** MD5 (GZip file): 6d060ddd47ebcfd5cfcdbf90ec042c97
** File Size: 589MB

'''Stock for DD method [eMMC Boot] [20190427]'''
* Use 'dd' to write the image to the eMMC module using the USB-to-eMMC adapter module and boot. Using [https://www.balena.io/etcher/ Etcher] or another specialized SD writing tool is preferred.
* Please allow 3-5 minutes boot up time on first time for initialization
* Please ignore "internal problem with your device" popup message if appear on Android boot-up page.
* This build supports PINE64 7" LCD panel with tablet UI (not Android TV)
* DD image for 16GB eMMC module
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-16GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 3BA4C72D81BCFC4C21B3B5D2BCB4F9F7
*** File Size: 609MB
* DD image for 32GB eMMC module
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-32GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 4965CCF50A8F06CEB2E4A6828A21F31C
*** File Size: 627MB
* DD image for 64GB eMMC module
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-64GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 748EC28FE5D5395D33E858C913D744BF
*** File Size: 663MB

'''Stock for DD method [microSD Boot] [20190506]'''
* DD image to microSD card and boot.
* Use 'dd' to write the image to the eMMC module using the USB-to-eMMC adapter module and boot. Using [https://www.balena.io/etcher/ Etcher] or another specialized SD writing tool is preferred.
* Please allow 3-5 minutes boot up time on first time for initialization
* Please ignore "internal problem with your device" popup message if appear on Android boot-up page.
* This build supports PINE64 7" LCD panel with tablet UI (not Android TV)
* DD image for 8GB microSD card
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-8GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): E1C551E8106E178841E1C3F71432194A
*** File Size: 599MB
* DD image for 16GB microSD card
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-16GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 73592FDD5A2F52F08020F16AD99E8C8C
*** File Size: 609MB
* DD image for 32GB microSD card
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-32GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 74DE0FE528F210E4DD483B411A71904B
*** File Size: 627MB
* DD image for 64GB microSD card
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-64GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): D7626BD50443A88AEB9254C88C575284
*** File Size: 663MB

'''Stock for RK Flash tool [eMMC Boot] [20190427]'''
* Please unzip first and then using Android tool to flash in
* The OTG port located at USB type-C connector, needs USB type A to type C cable.
* Please allow 3-5 minutes boot up time on first time for initialization
* This build supports PINE64 7" LCD panel with tablet UI (not Android TV)
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20190417_stock_android_9.0_emmcboot.img.gz Direct download from pine64.org]
** MD5 (GZip file): 046BA4A07933120809FBE1B9577B7341
** File Size: 592MB

----

=== Android 8.1.0 ===
'''Stock for DD method [eMMC Boot] [20180828]'''
* Use 'dd' to write the image to the eMMC module using the USB-to-eMMC adapter module and boot. Using [https://www.balena.io/etcher/ Etcher] or another specialized SD writing tool is preferred.
* Please allow 3-5 minutes boot up time on first time for initialization
* This build supports PINE64 7" LCD panel with tablet UI (not Android TV)
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180828_stock_android_8.1_emmcboot.img.xz Direct download from pine64.org]
** MD5 (XZ file): 9AEE21BC1B9DE886DCB0E64FA123988A
** File Size: 414MB

'''Stock for DD method [microSD Boot] [20181212]'''
* Use 'dd' to write the image to the eMMC module using the USB-to-eMMC adapter module and boot. Using [https://www.balena.io/etcher/ Etcher] or another specialized SD writing tool is preferred.
* Please allow 3-5 minutes boot up time on first time for initialization
* This build supports PINE64 7" LCD panel with tablet UI (not Android TV)
* DD image (for 8GB microSD card and above)
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20181212_stock_android_8.1_sdboot.img.xz Direct download from pine64.org]
** MD5 (XZ file): 5A6BB7FCD7B3F77FCEE99CE462AE7405
** File Size: 616MB

'''Stock for RK Flash tool [eMMC Boot] [20180828]'''
* Please unzip first and then using Android tool to flash in
* The OTG port located at USB type-C connector, needs USB type A to type C cable.
* Please allow 3-5 minutes boot up time on first time for initialization
* This build supports PINE64 7" LCD panel with tablet UI (not Android TV)
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180828_stock_android_8.1_emmcboot.img.xz Direct download from pine64.org]
** MD5 (XZ file): 4DACFE927BB09EE9C56B5232A7F624EE
** File Size: 415MB

----

=== Android 7.1.2 ===
'''Stock for DD method [eMMC Boot] [20180809]'''
* Use 'dd' to write the image to the eMMC module using the USB-to-eMMC adapter module and boot. Using [https://www.balena.io/etcher/ Etcher] or another specialized SD writing tool is preferred.
* Please allow 3-5 minutes boot up time on first time for initialization
* This build supports PINE64 7" LCD panel with tablet UI (not Android TV)
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180809_stock_android_7.1_emmcboot.img.gz Direct download from pine64.org]
** MD5 (XZ file): 00F194017557017C2588724686E90CEA
** File Size: 498MB

'''Stock for RK Flash tool [eMMC Boot] [20180809]'''
* Please unzip first and then using Android tool to flash in
* The OTG port located at USB type-C connector, needs USB type A to type C cable.
* Please allow 3-5 minutes boot up time on first time for initialization
* This build supports PINE64 7" LCD panel with tablet UI (not Android TV)
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180809_stock_android_7.1_emmcboot.img.gz Direct download from pine64.org]
** MD5 (XZ file): 197A9905B48441D8655E7542F4643FE9
** File Size: 483MB

'''Stock for DD method [microSD Boot] [20180920]'''
* Use 'dd' to write the image to the eMMC module using the USB-to-eMMC adapter module and boot. Using [https://www.balena.io/etcher/ Etcher] or another specialized SD writing tool is preferred.
* Please allow 3-5 minutes boot up time on first time for initialization
* This build supports PINE64 7" LCD panel with tablet UI (not Android TV)
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180920_stock_android_7.1_sdboot.img.gz Direct download from pine64.org]
** MD5 (XZ file): CE39642A379B357BB3E4BC80ACA2E0CE
** File Size: 765MB

'''Stock for DD method [eMMC Boot] [20180518]'''
* Use 'dd' to write the image to the eMMC module using the USB-to-eMMC adapter module and boot. Using [https://www.balena.io/etcher/ Etcher] or another specialized SD writing tool is preferred.
* Please allow 3-5 minutes boot up time on first time for initialization
* This build supports PINE64 7" LCD panel with tablet UI (not Android TV)
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180518_stock_android_7.1_emmcboot.img.xz Direct download from pine64.org]
** MD5 (XZ file): 33622034ACDBC31A7D7BB01ED634E29B
** File Size: 345MB

'''Stock for RK Flash tool [eMMC Boot] [20180518]'''
* Please unzip first and then using Android tool to flash in
* The OTG port located at USB type-C connector, needs USB type A to type C cable.
* Please allow 3-5 minutes boot up time on first time for initialization
* This build supports PINE64 7" LCD panel with tablet UI (not Android TV)
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180518_stock_android_7.1_emmcboot.img.xz Direct download from pine64.org]
** MD5 (XZ file): 90C1991DADAE13ADC94E927F171F8920
** File Size: 342MB

'''Stock for install from SDcard to eMMC [microSD Boot] [20180921]'''
* Use 'dd' to write the image to the eMMC module using the USB-to-eMMC adapter module and boot. Using [https://www.balena.io/etcher/ Etcher] or another specialized SD writing tool is preferred.
* Please allow 3-5 minutes boot up time on first time for initialization
* This build supports PINE64 7" LCD panel with tablet UI (not Android TV)
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180921_stock_android_7.1_sdboot.img.xz Direct download from pine64.org]
** MD5 (XZ file): c6900e82a1d6ef397dcac241f76f43c9
** File Size: 350MB

----

=== Android SDK ===
'''Android P SDK [v9.0]'''
* [http://files.pine64.org/SDK/ROCKPro64/ROCKPro64_SDK_android9.0.tar.gz Direct Download from pine64.org]
** MD5 (TAR-GZip file): 3CEBEEFD1A873BEEEC149148A785D92E
** File Size: 125.16GB

----

=== Slash TV OS ===
Android 7 based system including Play Store, working only from SD card (does not boot when installed on eMMC)
* https://drive.google.com/drive/folders/1K5YhWaB7Xstuv2HCo1HkpglCEm9x-RIM

== Development resources ==

The Ayufan github page
* [https://github.com/ayufan-rock64/linux-build/releases github.com/ayufan-rock64/linux-build/]

Below are the LPDDR4 driver for RK3399

* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_loader_v1.10.112_support_1CS.bin rk3399_loader_v1.10.112_support_1CS.bin, this is 800Mhz version used in Android Build]
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_ddr_666MHz_v1.11.bin rk3399_ddr_666MHz_v1.11.bin, this is alpha version]
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_ddr_933MHz_v1.11.bin rk3399_ddr_933MHz_v1.11.bin, this is alpha version]

ROCKPro64 related files

* [http://files.pine64.org/os/ROCKPro64/driver/kernel_rockpro64.tar.gz ROCKPro64 Kernel file]
* [http://files.pine64.org/os/ROCKPro64/driver/trust.img trust.img]

== Miscellaneous tools ==

* [http://files.pine64.org/doc/rock64/tools/DriverAssitant_v4.5.zip Windows ADB driver package]
* [[ROCK64 MAC Address]]
* [http://files.pine64.org/doc/rock64/guide/ROCK64_Installing_Android_To_eMMC.pdf Guide to install stock Android build to eMMC module]
* [http://files.pine64.org/doc/rock64/tools/SD_Firmware_Tool._v1.46.zip Tools to burn Android build into a bootable microSD card]
* [http://files.pine64.org/doc/rock64/tools/AndroidTool_Release_v2.38.zip Tools that allows developer flash image into eMMC's Loader/Parameter/Misc/Kernal/Boot/Recovery/System/Backup partition]

[[Category:ROCKPro64]]

ROCKPro64 Software Releases

2023-03-20T17:32:05Z

Sethi: Include postmarketOS (Plasma Bigscreen) in the list.

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

== Linux ==
=== AOSC ===
[[File:aosc.png|right|100px]]

'''AOSC OS''' is a general purpose Linux distribution that strives to simplify user experience and improve free and open source software for day-to-day productivity. Originally AnthonOS (an OpenSUSE derivative built with SUSE Studio), then remade as a Debian derivative with customized KDE 4 UI and CJK support. To learn more about AOSC, please visit the official [https://aosc.io/ AOSC website]

Download:
* https://aosc.io/downloads/ (supports the microSD card and eMMC, 8GB or more)

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

----

=== Armbian ===
[[File:armbian.png|right|100px]]

'''Armbian''' is a Linux distribution designed for ARM boards. They are usually Debian or Ubuntu flavored. To find out more about Armbian and available options please visit their [https://www.armbian.com/rockpro64/ site]. If you are booting from a Micro SD card, then both Linux kernel versions will work. If you are trying to boot from an eMMC module then the 4.4.y will work, but the newer 5.10.y will not.

Download:
* https://dl.armbian.com/rockpro64/archive/

----

=== Batocera Linux ===
[[File:batocera.png|right|100px]]

'''Batocera Linux''' is an open-source and completely free retro-gaming distribution that can be copied to a USB stick or an SD card with the aim of turning any computer/nano computer into a gaming console during a game or permanently. Visit the project's website here (https://batocera.org/). You can follow the ongoing discussion about batocera.linux on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=7084)

Download:
* https://batocera.org/download

----

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

'''Debian''' is an operating system and a distribution of free software. See the forum thread [https://forum.pine64.org/showthread.php?tid=9744 here].

Download:
* [https://deb.debian.org/debian/dists/bullseye/main/installer-arm64/current/images/netboot/SD-card-images/ Debian 11 Bullseye] (recommended)
* [https://deb.debian.org/debian/dists/bookworm/main/installer-arm64/current/images/netboot/SD-card-images/ Debian 12 Bookworm]
* [https://d-i.debian.org/daily-images/arm64/ Daily netboot images]

Instructions:
* Download: <code>firmware.rockpro64-rk3399.img.gz</code>
* Download: <code>partition.img.gz</code>
* Create the disk image:
** For Linux: <code>zcat firmware.rockpro64-rk3399.img.gz partition.img.gz > complete_image.img</code>
** For Mac: <code>gzcat firmware.rockpro64-rk3399.img.gz partition.img.gz > complete_image.img</code>
* Write the image to your boot device:
** For Linux: <code>dd if=complete_image.img of=your_chosen_boot_device bs=4M</code>
** For Mac: see [[Getting started]]

Notes:
* An Ethernet connection is required for the above installer
* Remember to leave some space before your first partition for u-boot! You can do this by creating a 32M size unused partition at the start of the device.
* See the [[ROCKPro64#No_Video_or_GPU_Acceleration_on_Debian|troubleshooting section]] if you encounter issues with GPU acceleration.

----

=== DietPi ===
[[File:dietpi.png|right|100px]]

'''DietPi''' is a lightweight, yet easy to setup and feature-rich Linux distribution, based on Debian. To find out more about DietPi, please visit the [https://dietpi.com/docs/ official documentation]. Discuss the ROCKPro64 build on the [https://forum.pine64.org/showthread.php?tid=12532 PINE64 forum thread].

Download:
* [https://dietpi.com/downloads/images/DietPi_ROCKPro64-ARMv8-Bullseye.7z Direct download from dietpi.com]

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

----

=== LibreELEC ===
[[File:libreelec.jpg|right|100px]]
'''LibreELEC''' is a lightweight 'Just enough OS' Linux distribution purpose-built for Kodi on current and popular mediacentre hardware.

Download:
* [https://libreelec.tv/downloads/rockchip/ Official LibreELEC build image] (look for PINE64 RockPro64-LibreELEC-RK3399.arm-x.x.x-rockpro64.img.gz, supports microSD card and the eMMC module of 8GB or more.)

{{Info|Unzip and flash the image to a microSD card or eMMC module, for example using ''dd''.}}

----

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

'''Manjaro''' is a user-friendly Linux distribution based on the independently developed Arch operating system. To learn more about Manjaro please visit [https://forum.manjaro.org/c/arm/releases/102 Manjaro forum].

Download:
* [https://github.com/manjaro-arm/rockpro64-images/releases from Github]

Notes:
* Decompress the image (<tt>unxz</tt>) before flashing, or decompress on the fly while flashing (<tt>xzcat</tt> in a root shell, Etcher, ...)
* A display and keyboard will be required for first boot.
* Initial setup includes: keyboard layout, locale, username, user password, and root password.
* The installer will expand the root partition to use the remaining space on the storage device you've flashed.

----

=== Nems Linux ===
[[File:nems.jpg|right|100px]]

'''NEMS''' stands for ''Nagios Enterprise Monitoring Server'' and it is a modern pre-configured, customized and ready-to-deploy Nagios Core image designed to run on low-cost micro computers. To find out more about NEMS on the PINE64 and available tweaks to the installation please visit the [https://forum.pine64.org/showthread.php?tid=7306 PINE64 forum thread].

Download:
* [https://nemslinux.com/download/nagios-for-pine64.php Download page] with torrent seed or direct download.

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

----

=== 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. More information can be found on the [https://nixos.wiki/wiki/NixOS_on_ARM/PINE64_ROCKPro64 NixOS wiki].

Download:
* [https://github.com/AshyIsMe/nixos-installer-rockpro64 nixos-installer-rockpro64]

----

=== OpenMediaVault ===
[[File:omv.png|right|100px]]

'''OpenMediaVault''' is the next generation network attached storage (NAS) solution, [https://www.openmediavault.org/ click this link to OMV main page] to learn more. Forum thread concerning this release can be found [https://forum.pine64.org/showthread.php?tid=6308 here]

Download:
{{Outdated release}}
* Stretch 32bit (armhf): [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/stretch-openmediavault-rockpro64-0.8.3-1141-armhf.img.xz Direct download from ayufan's github]
* Stretch 64bit (aarch64): [https://github.com/ayufan-rock64/linux-build/releases/download/0.8.3/stretch-openmediavault-rockpro64-0.8.3-1141-arm64.img.xz Direct download from ayufan's github]

Notes:
* You need to enable root login in OMV WebGUI
* [http://omv-extras.org/joomla/index.php/omv-plugins-3/3-stable OpenMediaVault Plugins]

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! TTY and SSH, except OMV
| <code>rock64/rock64</code>
|-
! WebGUI Login
| <code>admin/openmediavault</code>
|-
! TTY and SSH
| <code>root/openmediavault</code>
|}

----

=== OpenWrt ===
[[File:Openwrt logo square.png|right|100px]]

'''OpenWrt''' is a highly extensible GNU/Linux distribution for embedded devices (typically wireless routers). Unlike many other distributions for these routers, OpenWrt is built from the ground up to be a full-featured, easily modifiable operating system for your router. In practice, this means that you can have all the features you need with none of the bloat, powered by a Linux kernel that's more recent than most other distributions.

Download:
* https://openwrt.org/toh/pine64/rockpro64_v2.1

----

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

postmarketOS extends [https://www.alpinelinux.org/ Alpine Linux] to run on smartphones and other devices.
At the time of writing, the only user interface for images built for the ROCKPro64 is [https://plasma-bigscreen.org/ Plasma Bigscreen].

Download:
* https://postmarketos.org/download/

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

----

=== R-Cade ===
[[File:RCadeLogo.jpg|right|100px]]

Retro Center's '''R-Cade''', the 4K Media Center Arcade. [https://www.retro-center.com/about-r-cade/ RCade] Features 100+ retro-gaming systems, a lightweight web browser, and full 4K UHD media playback.

Download:
* [https://github.com/retro-center/rcade_releases/releases Direct download from Retro Center's GitHub] (USB, microSD and eMMC boot)

----

=== Recalbox ===
[[File:RB.png|right|100px]]

'''Recalbox''' allows you to re-play a variety of videogame consoles and platforms in your living room, with ease! Visit the project's website here (https://www.recalbox.com/). You can follow the ongoing discussion about Recalbox on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=7194)

Download:
{{Template:Outdated release}}
* [https://github.com/mrfixit2001/recalbox_rockpro64/releases download] release from mrfixit2001 github.

----

=== Retro Arena ===
[[File:retroarena.png|right|100px]]

'''Retro Arena''' community build for microSD and eMMC boot. This is a BETA and therefore is not update-able nor supported, however bugs or issues are appreciated to be identified and shared via the issues tab on our GitHub so that we can address them in the future. The Roshambo Case support is baked in with one major caveat due to kernel limitation: You can power the unit off by the POWER switch and the RESET button works 100% however to power the unit on you will need to manually plug/unplug the power cord. This limitation will not be present in future releases. You can follow the ongoing discussion about Retro Arena on the [https://forum.pine64.org/showthread.php?tid=7555 forum]

Download:
{{Outdated release}}
* [http://files.pine64.org/os/ROCKPro64/odroidretroarena/TheRA-RP64-BETA-0.8-FINAL.img.gz Direct download from pine64.org]

----

=== SkiffOS ===
[[File:SkiffOS-Icon-1.png|right|100px]]
Minimal cross-compiled OS optimized for hosting distributions in Docker containers. Provides the reliability of firmware with the ease-of-use of package managers. Uses the [http://buildroot.org Buildroot] cross-compilation tool for support for all Pine64 boards.

Use configuration packages to configure the distribution:
* core/gentoo: Gentoo optimized for Rockpro64
* core/nixos: NixOS arm64

You can also configure the skiff core yaml file to configure multiple distributions to run in parallel.

The boot-up OS can be upgraded independently from the containers.

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

----

=== Slackware ===
[[File:slackware.jpg|right|100px]]

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

Resources:
* [https://docs.slackware.com/slackwarearm:inst Installation instructions].
* [https://www.youtube.com/watch?v=uXAL9jz-yaA&list=PL1XOSJnvang3VLmqke2QbRitKtOD6Rm3t Installation video guide]

----

=== slarm64 ===

'''slarm64''' is an unofficial aarch64 / riscv64 Slackware Linux port. You can follow the ongoing discussion about slarm64 on the RockPro64 on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=6823) or this forum thread for more general slarm64 information: https://www.linuxquestions.org/questions/slackware-arm-108/slarm64-aarch64-unofficial-slackware-4175613287/.

Downloads:
* [http://dl.fail.pp.ua/slackware/images/rockpro64/ download] (supports microSD card, look for slarm64-current-aarch64-xfce-rockpro64-x.xx.x-build-xxxxxxxx.img.zst)

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

Flashing the distribution to the eMMC:
* Flash the image to micro SD, power up the board with micro SD and login
* Copy the image file to micro SD by using SFTP. The image file must have the ''.img'' file extension.
* After finish copy the file, power off the board and add eMMC module to the board
* Boot the board, run below command for flashing to eMMC module
* Run <code>dd if=[image file] of=/dev/mmcblkX bs=10M</code> (example: ''sudo dd if=slack-current-aarch64-xfce_29Sep18-4.4.162-rockpro64-build-20181126.img of=/dev/mmcblkX bs=10M'')
* then edit these two files in eMMC module:
** <code>mount /dev/mmcblk1p1 /media</code>
** <code>echo "rootdev=/dev/mmcblk1p1" >> /media/boot/uEnv.txt</code>
** <code>sed -i 's:mmcblk0p1:mmcblk1p1:' /media/etc/fstab</code>
* After that, power off the board and remove the microSD card. Then boot with only the eMMC module.

----

=== Twister OS ===
[[File:Twister_OS.png|right|100px]]

'''Twister OS''' brings a desktop computing experience for SBCs, right out-of-the-box. Including themes, applications, tools, and optimizations to get the most out of your SBC. For more information on Twister OS, please visit the [https://twisteros.com/ official site]. You can follow the ongoing discussion about Twister OS on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=12192).

Download:
* [https://twisteros.com/twisterarmbian.html Twister OS Armbian-Reforged XFCE Desktop image] (2.8GB, supports the microSD card and eMMC modules with 16GB and more)

{{Info|After flashing image with Etcher, edit /boot/armbianEnv.txt, replace the dtb name with rk3399-rockpro64.dtb.}}

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

----

=== Void Linux ===
'''Void Linux''' is a general purpose operating system, based on the monolithic Linux kernel. The official guide can be found at [https://docs.voidlinux.org/installation/guides/arm-devices/index.html Guide]. At this time there are no RockPro64 images available.

The following creates a bootable image from an existing Void Linux installation:
* <code>xbps-insall -Syu</code> to update the xbps installation of the installation
* create ROCKPro64 image with the ''void-mklive'' software (from github.com):
** create a rootfs via ''mkrootfs.sh'': <code>sh mkrootfs.sh -o void-aarch64-muls-ROOTFS-yyyymmdd.tar.xz</code>
** <code>sh mkplatformfs.sh rockpro64 void-aarch64-muls-ROOTFS-yyyymmdd.tar.xz</code>
** <code>sh mkimage.sh -s 7GiB void-rockpro64-PLATFORMFS-yyyymmdd.tar.xz</code>
* write image to sdcard or eMMC: <code>dd if='''IMAGE-FILENAME''' of='''DEVICENAME''' bs=2M</code>
* If ''mkplatformfs.sh'' errors with ''ROCKPro64 not supported'', install ''xbps-src'' from https://github.com/void-linux/void-packages and build the ROCKPro64 package.
* Tip: write a new U-Boot to the image if you see on the serial console the boot-up stalls:
** get the two U-Boot files from [https://pkgs.org/download/u-boot-rockpro64 pkgs.org], the aarch64 files:
** <code>dd if=idbloader.img of=DEVICENAME seek=64</code>
** <code>dd if=u-boot.itb of=DEVICENAME seek=16384</code>

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

== BSD Images ==
=== FreeBSD ===
[[File:Freebsd_Logo.png|right|100px]]

'''FreeBSD''' is an operating system used to power modern servers, desktops, and embedded platforms. The [https://wiki.freebsd.org/arm/RockChip#RockPro64 RockChip FreeBSD page] has instructions for installing FreeBSD. Version 13.0 and greater include prebuilt images.

Download:
* Images for various FreeBSD releases can be found [https://www.freebsd.org/where/ here]

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! SSH user (enabled by default)
| <code>freebsd/freebsd</code>
|-
! Root user
| <code>root/root</code>
|}

Notes:

* The wiki has instructions on [https://wiki.freebsd.org/arm/RockChip#Fan_Control_on_RockPro64 enabling the PWM cooling fan].

----

=== NetBSD ===
[[File:netbsd.png|right|100px]]
'''NetBSD''' is a free, fast, secure, and highly portable Unix-like Open Source operating system. To learn more about NetBSD please visit [https://www.netbsd.org/ NetBSD main page]

Download:
* [https://armbsd.org/ download] latest release build from NetBSD by select 64bit - RockPro64 (size: 339 MB)

{| class="wikitable"
!colspan="2" style="background: #a7d7f9;"| Default credentials
|-
! Root user and SSH login
| <code>root/[none]</code>
|}

Notes:
* Instructions concerning enabling SSH can be found [https://www.netbsd.org/docs/guide/en/chap-boot.html#chap-boot-ssh here] or the bootable image from armbsd.org can have the MSDOS partition modified to setup SSH using [https://man.netbsd.org/creds_msdos.8 this] method.

----

=== OpenBSD ===
[[File:Puffy_mascot_openbsd.png|right|100px]]

'''OpenBSD''' is a security-focused, free and open-source, Unix-like operating system based on the Berkeley Software Distribution. Official instruction to get OpenBSD on ROCKPro64 is [https://www.openbsd.org/arm64.html here], and blogs on installation [https://github.com/jasperla/openbsd-rockpro64 is here] and [https://bsandro.tech/posts/openbsd-7.1-on-pine64-rockpro64/ here]. Forum discussion is [https://forum.pine64.org/forumdisplay.php?fid=109 here].

== Chromium OS ==
[[File:chromium.jpg|right|100px]]

The '''Chromium OS''' community build image for microSD card and eMMC module, version beta (R76). To learn more please visit the [https://forum.pine64.org/showthread.php?tid=7659 forum].

Download:
{{Outdated release}}
* https://github.com/ayufan-rock64/chromiumos-build/releases/

{{Info|Flash the image to a microSD card or an eMMC module, for example using ''dd''.}}

== Android ==
[[File:Android_logo_2019_(stacked).svg|right|100px]]

=== Android 9.0.0 ===

'''Stock for DD method [eMMC Boot] [20200804]'''
* Use 'dd' to write the image to the eMMC module using the USB-to-eMMC adapter module and boot. Using [https://www.balena.io/etcher/ Etcher] or another specialized SD writing tool is preferred.
* Please allow 3-5 minutes boot up time on first time for initialization
* Supports new RockPro64 AP6256 Wifi/BT module
* Support Sony IMX214 camera module and works on both MiPi-CSI ports
* This build supports PINE64 7" LCD panel with tablet UI (not Android TV)
* DD image for 8GB eMMC module
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200804_stock_android_9.0_emmcboot-8GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 7287fd0846616354615c8d3eff6a2a92
*** File Size: 602MB
* DD image for 16GB eMMC module
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200804_stock_android_9.0_emmcboot-16GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 78352bbf21198d062af8bab2217ee691
*** File Size: 611MB
* DD image for 32GB eMMC module
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200804_stock_android_9.0_emmcboot-32GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): c5c8dce419478f75f85f893ee4808dbd
*** File Size: 624MB
* DD image for 64GB eMMC module
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200804_stock_android_9.0_emmcboot-64GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): aab1cf4d30c4d16e6ce2672f3ecae935
*** File Size: 666MB

'''Stock for RK Flash tool [eMMC Boot] [20200804]'''
* Please unzip first and then using Android tool to flash in
* The OTG port located at USB type-C connector, needs USB type A to type C cable.
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20200708_stock_android_9.0_emmcboot.img.gz Direct download from pine64.org]
** MD5 (GZip file): 9ac830527814521e15b009fa2503c9e3
** File Size: 589MB

'''Stock for DD method [eMMC Boot] [20200708]
* Use 'dd' to write the image to the eMMC module using the USB-to-eMMC adapter module and boot. Using [https://www.balena.io/etcher/ Etcher] or another specialized SD writing tool is preferred.
* Please allow 3-5 minutes boot up time on first time for initialization
* Supports new RockPro64 AP6256 Wifi/BT module
* This build supports PINE64 7" LCD panel with tablet UI (not Android TV)
* DD image for 8GB eMMC module
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200708_stock_android_9.0_emmcboot-8GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): ef5f5a890a9270734e0adee21f006837
*** File Size: 597MB
* DD image for 16GB eMMC module
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200708_stock_android_9.0_emmcboot-16GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 179bd684a468f800a86f7c658a543bef
*** File Size: 606MB
* DD image for 32GB eMMC module
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200708_stock_android_9.0_emmcboot-32GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): d930b757c4427be07b83c37a9c8494a1
*** File Size: 630MB
* DD image for 64GB eMMC module
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20200708_stock_android_9.0_emmcboot-64GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 09a970d68a10bdb3d6495d55860940e6
*** File Size: 660MB

'''Stock for RK Flash tool [eMMC Boot] [20200708]'''
* Please unzip first and then using Android tool to flash in
* The OTG port located at USB type-C connector, needs USB type A to type C cable.
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20200708_stock_android_9.0_emmcboot.img.gz Direct download from pine64.org]
** MD5 (GZip file): 6d060ddd47ebcfd5cfcdbf90ec042c97
** File Size: 589MB

'''Stock for DD method [eMMC Boot] [20190427]'''
* Use 'dd' to write the image to the eMMC module using the USB-to-eMMC adapter module and boot. Using [https://www.balena.io/etcher/ Etcher] or another specialized SD writing tool is preferred.
* Please allow 3-5 minutes boot up time on first time for initialization
* Please ignore "internal problem with your device" popup message if appear on Android boot-up page.
* This build supports PINE64 7" LCD panel with tablet UI (not Android TV)
* DD image for 16GB eMMC module
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-16GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 3BA4C72D81BCFC4C21B3B5D2BCB4F9F7
*** File Size: 609MB
* DD image for 32GB eMMC module
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-32GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 4965CCF50A8F06CEB2E4A6828A21F31C
*** File Size: 627MB
* DD image for 64GB eMMC module
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190417_stock_android_9.0_emmcboot-64GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 748EC28FE5D5395D33E858C913D744BF
*** File Size: 663MB

'''Stock for DD method [microSD Boot] [20190506]'''
* DD image to microSD card and boot.
* Use 'dd' to write the image to the eMMC module using the USB-to-eMMC adapter module and boot. Using [https://www.balena.io/etcher/ Etcher] or another specialized SD writing tool is preferred.
* Please allow 3-5 minutes boot up time on first time for initialization
* Please ignore "internal problem with your device" popup message if appear on Android boot-up page.
* This build supports PINE64 7" LCD panel with tablet UI (not Android TV)
* DD image for 8GB microSD card
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-8GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): E1C551E8106E178841E1C3F71432194A
*** File Size: 599MB
* DD image for 16GB microSD card
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-16GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 73592FDD5A2F52F08020F16AD99E8C8C
*** File Size: 609MB
* DD image for 32GB microSD card
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-32GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 74DE0FE528F210E4DD483B411A71904B
*** File Size: 627MB
* DD image for 64GB microSD card
** [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20190506_stock_android_9.0_sdboot-64GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): D7626BD50443A88AEB9254C88C575284
*** File Size: 663MB

'''Stock for RK Flash tool [eMMC Boot] [20190427]'''
* Please unzip first and then using Android tool to flash in
* The OTG port located at USB type-C connector, needs USB type A to type C cable.
* Please allow 3-5 minutes boot up time on first time for initialization
* This build supports PINE64 7" LCD panel with tablet UI (not Android TV)
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20190417_stock_android_9.0_emmcboot.img.gz Direct download from pine64.org]
** MD5 (GZip file): 046BA4A07933120809FBE1B9577B7341
** File Size: 592MB

----

=== Android 8.1.0 ===
'''Stock for DD method [eMMC Boot] [20180828]'''
* Use 'dd' to write the image to the eMMC module using the USB-to-eMMC adapter module and boot. Using [https://www.balena.io/etcher/ Etcher] or another specialized SD writing tool is preferred.
* Please allow 3-5 minutes boot up time on first time for initialization
* This build supports PINE64 7" LCD panel with tablet UI (not Android TV)
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180828_stock_android_8.1_emmcboot.img.xz Direct download from pine64.org]
** MD5 (XZ file): 9AEE21BC1B9DE886DCB0E64FA123988A
** File Size: 414MB

'''Stock for DD method [microSD Boot] [20181212]'''
* Use 'dd' to write the image to the eMMC module using the USB-to-eMMC adapter module and boot. Using [https://www.balena.io/etcher/ Etcher] or another specialized SD writing tool is preferred.
* Please allow 3-5 minutes boot up time on first time for initialization
* This build supports PINE64 7" LCD panel with tablet UI (not Android TV)
* DD image (for 8GB microSD card and above)
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20181212_stock_android_8.1_sdboot.img.xz Direct download from pine64.org]
** MD5 (XZ file): 5A6BB7FCD7B3F77FCEE99CE462AE7405
** File Size: 616MB

'''Stock for RK Flash tool [eMMC Boot] [20180828]'''
* Please unzip first and then using Android tool to flash in
* The OTG port located at USB type-C connector, needs USB type A to type C cable.
* Please allow 3-5 minutes boot up time on first time for initialization
* This build supports PINE64 7" LCD panel with tablet UI (not Android TV)
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180828_stock_android_8.1_emmcboot.img.xz Direct download from pine64.org]
** MD5 (XZ file): 4DACFE927BB09EE9C56B5232A7F624EE
** File Size: 415MB

----

=== Android 7.1.2 ===
'''Stock for DD method [eMMC Boot] [20180809]'''
* Use 'dd' to write the image to the eMMC module using the USB-to-eMMC adapter module and boot. Using [https://www.balena.io/etcher/ Etcher] or another specialized SD writing tool is preferred.
* Please allow 3-5 minutes boot up time on first time for initialization
* This build supports PINE64 7" LCD panel with tablet UI (not Android TV)
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180809_stock_android_7.1_emmcboot.img.gz Direct download from pine64.org]
** MD5 (XZ file): 00F194017557017C2588724686E90CEA
** File Size: 498MB

'''Stock for RK Flash tool [eMMC Boot] [20180809]'''
* Please unzip first and then using Android tool to flash in
* The OTG port located at USB type-C connector, needs USB type A to type C cable.
* Please allow 3-5 minutes boot up time on first time for initialization
* This build supports PINE64 7" LCD panel with tablet UI (not Android TV)
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180809_stock_android_7.1_emmcboot.img.gz Direct download from pine64.org]
** MD5 (XZ file): 197A9905B48441D8655E7542F4643FE9
** File Size: 483MB

'''Stock for DD method [microSD Boot] [20180920]'''
* Use 'dd' to write the image to the eMMC module using the USB-to-eMMC adapter module and boot. Using [https://www.balena.io/etcher/ Etcher] or another specialized SD writing tool is preferred.
* Please allow 3-5 minutes boot up time on first time for initialization
* This build supports PINE64 7" LCD panel with tablet UI (not Android TV)
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180920_stock_android_7.1_sdboot.img.gz Direct download from pine64.org]
** MD5 (XZ file): CE39642A379B357BB3E4BC80ACA2E0CE
** File Size: 765MB

'''Stock for DD method [eMMC Boot] [20180518]'''
* Use 'dd' to write the image to the eMMC module using the USB-to-eMMC adapter module and boot. Using [https://www.balena.io/etcher/ Etcher] or another specialized SD writing tool is preferred.
* Please allow 3-5 minutes boot up time on first time for initialization
* This build supports PINE64 7" LCD panel with tablet UI (not Android TV)
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_dd_20180518_stock_android_7.1_emmcboot.img.xz Direct download from pine64.org]
** MD5 (XZ file): 33622034ACDBC31A7D7BB01ED634E29B
** File Size: 345MB

'''Stock for RK Flash tool [eMMC Boot] [20180518]'''
* Please unzip first and then using Android tool to flash in
* The OTG port located at USB type-C connector, needs USB type A to type C cable.
* Please allow 3-5 minutes boot up time on first time for initialization
* This build supports PINE64 7" LCD panel with tablet UI (not Android TV)
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180518_stock_android_7.1_emmcboot.img.xz Direct download from pine64.org]
** MD5 (XZ file): 90C1991DADAE13ADC94E927F171F8920
** File Size: 342MB

'''Stock for install from SDcard to eMMC [microSD Boot] [20180921]'''
* Use 'dd' to write the image to the eMMC module using the USB-to-eMMC adapter module and boot. Using [https://www.balena.io/etcher/ Etcher] or another specialized SD writing tool is preferred.
* Please allow 3-5 minutes boot up time on first time for initialization
* This build supports PINE64 7" LCD panel with tablet UI (not Android TV)
* [http://files.pine64.org/os/ROCKPro64/android/ROCKPro64_20180921_stock_android_7.1_sdboot.img.xz Direct download from pine64.org]
** MD5 (XZ file): c6900e82a1d6ef397dcac241f76f43c9
** File Size: 350MB

----

=== Android SDK ===
'''Android P SDK [v9.0]'''
* [http://files.pine64.org/SDK/ROCKPro64/ROCKPro64_SDK_android9.0.tar.gz Direct Download from pine64.org]
** MD5 (TAR-GZip file): 3CEBEEFD1A873BEEEC149148A785D92E
** File Size: 125.16GB

----

=== Slash TV OS ===
Android 7 based system including Play Store, working only from SD card (does not boot when installed on eMMC)
* https://drive.google.com/drive/folders/1K5YhWaB7Xstuv2HCo1HkpglCEm9x-RIM

== Development resources ==

The Ayufan github page
* [https://github.com/ayufan-rock64/linux-build/releases github.com/ayufan-rock64/linux-build/]

Below are the LPDDR4 driver for RK3399

* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_loader_v1.10.112_support_1CS.bin rk3399_loader_v1.10.112_support_1CS.bin, this is 800Mhz version used in Android Build]
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_ddr_666MHz_v1.11.bin rk3399_ddr_666MHz_v1.11.bin, this is alpha version]
* [http://files.pine64.org/os/ROCKPro64/driver/rk3399_ddr_933MHz_v1.11.bin rk3399_ddr_933MHz_v1.11.bin, this is alpha version]

ROCKPro64 related files

* [http://files.pine64.org/os/ROCKPro64/driver/kernel_rockpro64.tar.gz ROCKPro64 Kernel file]
* [http://files.pine64.org/os/ROCKPro64/driver/trust.img trust.img]

== Miscellaneous tools ==

* [http://files.pine64.org/doc/rock64/tools/DriverAssitant_v4.5.zip Windows ADB driver package]
* [[ROCK64 MAC Address]]
* [http://files.pine64.org/doc/rock64/guide/ROCK64_Installing_Android_To_eMMC.pdf Guide to install stock Android build to eMMC module]
* [http://files.pine64.org/doc/rock64/tools/SD_Firmware_Tool._v1.46.zip Tools to burn Android build into a bootable microSD card]
* [http://files.pine64.org/doc/rock64/tools/AndroidTool_Release_v2.38.zip Tools that allows developer flash image into eMMC's Loader/Parameter/Misc/Kernal/Boot/Recovery/System/Backup partition]

[[Category:ROCKPro64]]

PinePhone Carrier Support

2023-02-20T21:49:12Z

Sethi:

{{under construction}}

This page contains hints on setting up cellular network connectivity for specific carriers.
For more general information, see the carrier support section of [[PinePhone#Modem]]. For the APN settings see [[PinePhone APN Settings]].

= Check compatibility =
To check if the PinePhone is supported on your carrier:

Search for your carrier on [https://www.frequencycheck.com/ frequencycheck.com] and compare the carrier's LTE/GSM/WCDMA frequencies to the PinePhone's supported frequencies (listed in the [[File:Quectel_EG25-G_LTE_Standard_Specification_V1.3.pdf]] modem specification sheet).

It is likely that there will be a few frequencies that your carrier uses which are not supported by the PinePhone. Not all of the carrier's frequencies need to be supported by the PinePhone for it to work - as long as ''most'' of them are supported, you will still get good coverage.

= Tested and working carriers =

The following is a list of carriers which has been tested by users and confirmed to be working (excerpt):

== Asia ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
| Japan || [[wikipedia:SoftBank_Group#SoftBank_Mobile|SoftBank]] || Not tested || Unsupported by carrier || No || No || Mobian Phosh, December 2020
|-
| Japan || [[wikipedia:ja:楽天モバイル|Rakuten Mobile]] || Unsupported by carrier || Unsupported by carrier || Yes || Yes || Mobian Phosh, January 2021
|-
| Japan || [[wikipedia:ja:楽天モバイル|Rakuten Mobile]] || Unsupported by carrier || Unsupported by carrier || Yes || No || Manjaro Plasma Mobile February 2021
|-
| Japan || [[wikipedia:NTT Docomo|Docomo]] || Yes || Not tested || Yes || Yes || Mobian Phosh, February 2021
|-
| India || Vodafone / Vi India || Yes || Not tested || Yes || Yes || DanctNIX (Arch Linux ARM) with Phosh, March 2021
|-
| Malaysia || Celcom || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| Malaysia || Maxis || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| Malaysia || U-Mobile || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| Malaysia || Yes || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| South Korea || KT || Yes || Not tested || Yes || Yes || Manjaro Phosh, June 2021
|-
| China || [[wikipedia:China Mobile|China Mobile]] || Yes || Not tested || Yes || No || Mobile NixOS, December 2021
|-
| China || [[wikipedia:China Telecom|China Telecom]] || Yes (hack needed) || Not tested || Yes (hack needed) || No || AOSC OS Phosh, January 2022
|-
| Japan || [[wikipedia:ja:楽天モバイル|Rakuten Mobile]] || Yes || Not tested || Yes || Yes || Mobian Phosh, January 2022 (rivised from January 2021)
|-
| China || [[wikipedia:China Unicom|China Unicom]] || Yes || Not tested || Yes || Yes || [https://postmarketos.org/ pmOS] 22.06.3 Phosh, [[PineModems#Bootloader_unlocking | BLunlck'd]], [[PinePhone#Firmware_update|upd'd]] to [https://github.com/Biktorgj/quectel_eg25_recovery/tree/EG25GGBR07A08M2G_30.006.30.006 *8M2G_30.006*], November 2022
|}

== Africa ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129
|-
|}

== Europe ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Ukraine || KyivStar || Yes || Not tested || Yes || Yes || Mobian Phosh(11Nov21)
|-
|-
| Ukraine || Vodafone || Yes || Not tested || Yes || Yes || Manjaro ARM Phosh(29Jun22)
|-
| Sweden || Fello (uses Telia network) || Yes || No (data and MMS APN are different) || Yes || Yes || Mobian Phosh, October 2022
|-
| Sweden || Hallon (uses Tre network) || Yes || Yes (when manually selecting the MMS APN) || Yes || Yes || Mobian Phosh, October 2022
|-
| Sweden || Comviq (uses Tele2 network) || Yes || Yes (when manually selecting the MMS APN) || Yes || Yes || Mobian Phosh, October 2022
|-
| Sweden || Tele2 || Yes || Not tested || Yes || Not tested || Manjaro ARM Posh
|-
| Sweden || Telenor SE || Not tested || Not tested (should NOT work, data and MMS APN are different) || Yes || Not tested || Manjaro Plasma Mobile beta2
|-
| UK || Three || Yes || Not tested || Yes || Yes || Manjaro Plasma Mobile beta2
|-
| UK || Vodafone || Yes || Not tested || Yes || Yes || ALARM & pmOS (Phosh?), modem FW latest - 26 Feb 21
|-
| UK || Sky Mobile (O2) || Yes || Not tested || Yes || Yes || ArchLinux Phosh (20210908 image, fully updated) - 3 October 2021
|-
| UK || Smarty Mobile (Three) || Yes || Yes || Yes || Yes || Arch Linux SXMO (Wayland) - 23 March 2022
|-
| UK || Honest Mobile (Three) || Yes || No || Yes - buggy || Yes || postmarketOS 22.12 (Phosh) - 20 February 2023
|-
| France || Orange || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021
|-
| France || SFR || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021
|-
| France || Free || Yes || Not tested || Yes || Yes || pmOS SXMO (Wayland) - 27 March 2022
|-
| Czech Republic || O2 || Yes (only on 2G) || Not tested || Yes || Yes || Mobian Phosh (20210517 image up to date) - 2 June 2021
|-
| Germany || Congstar || Yes || Not tested || Yes || Yes (IPv4 & IPv6) || Mobian (Megi's kernel 5.13.0-rc4, apt up-to-date) with Phosh, 2021-06-07
|-
| Germany || E-Plus || Yes (sending only 2G) || Not tested || Yes || Yes || Manjaro Phosh and postmarketOS, 2021-10-15
|-
| Germany || Telekom || Yes || Not tested || Yes || Not tested || Mobian Phosh (5.10-sunxi64), 2021-07-28
|-
| Germany || O2 / Telefonica || Yes || Not tested || Yes || Not tested || KPlasma
|-
| Hungary || Telekom || Yes || Not tested || Yes || Yes (IPv4) || Manjaro Phosh Beta 12, 2021-07-30
|-
| Hungary || Telenor/Yettel || Yes || Not tested || Yes || Yes || Mobian-Phosh-20210517, 2021-09-24
|-
| Denmark || CBB || Yes || Not tested || Yes || Yes || Manjaro Plasma Mobile Beta 5, 2021-06-30
|-
| Belgium || Telenet || Yes || Not tested || Yes || Yes || postmarketOS v20.05, v21.03, v21.06 and edge, 2021-08-15
|-
| Belgium || CARREFOUR || Yes || Not tested || Yes || Yes || postmarketOS v20.05, v21.03, v21.06 and edge, 2021-08-15
|-
| Poland || Play || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta 18, 2021-11-14
|-
| Poland || Orange || Yes || No || Yes || Yes (IPv4 & IPv6) || Manjaro Phosh v21.10, 2021-12-23
|-
| Poland || Premium Mobile || Yes || No || Yes || Yes || Manjaro Phosh v22.01, 2022-01-13
|-
| Italy || WindTre Italy || Yes || Not tested || Yes || Yes || Archlinux ARM Plasma Mobile
|-
| Switzerland || Salt || Yes || Not tested || Yes || Yes || Phosh on Mobian + Arch
|}

== North America ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI || Modem Firmware
|-
|-
| USA || AT&T || Yes || Yes || Yes || Yes ||
* Mobian - Phosh
|-
| USA || T-Mobile || Yes || No || Yes || Yes ||
* Arch Linux Arm 2020/11/29
* Mobian - Phosh
* Manjaro - KDE Plasma Mobile
|-
| USA || T-Mobile || Yes || Yes || Yes || Yes ||
* Mobian Bookworm (Phosh) (2022-03-08)
|| EG25GGBR07A08M2G_01.003.01.003
|-
| USA || MetroPCS (T-Mobile) || Yes || No || Yes || Yes ||
*Arch Linux Arm (Phosh,SXMO) 2021/04/29
*Manjaro - Phosh 2021/04/29
*Mobian - Phosh 2021/3/20
|-
| USA || T-Mobile || Yes - buggy || No || Yes - buggy || Yes - buggy ||
*Manjaro - Plasma Dev 2020/11/21
*Ubuntu Touch - 2020/11/26
*KDE Neon 2020/11/02
|-
| USA || Mint Mobile (T-Mobile) || Yes || Yes || Yes || Yes ||
*Mobian - Phosh 2021/3/14
*postMarketOS - Phosh, Sxmo, Plasma Mobile 2021/5/26
*Ubuntu Touch 2021/5/24
*Manjaro - Phosh 2022/3/25
|-
| USA || Patriot Mobile (T-Mobile) || Yes || Yes chatty v0.6.1 mmsd-tng v1.8 || Yes || Yes ||
*Arch Linux Arm - Phosh 2022/01/12
|-
| USA || Tello (T-Mobile) || Yes || Yes || Yes || Yes ||
*DanctNIX (Arch Linux ARM) - Phosh 2022-07-09
|-
| USA || TracFone || No || No || No || No ||
*postMarketOS - Phosh 2022/06/28
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
*Mobian - Phosh 2021/3/1
|-
| USA || US Mobile || Yes || Not tested || Yes || Not Tested ||
*Mobian - Phosh 2022/01/09
|-
| USA || Verizon || No || No || No || No ||
*Ubuntu Touch 2021/5/24 (You can occasionally get the settings to work with Verizon, but it seems like the settings automatically changes the carrier to the wrong one after a few minutes)
|-
| USA || Verizon || Not tested || Not tested || Yes || Not via gui ||
*Manjaro - KDE Plasma Mobile 2021/5/10
|-
| USA || Verizon || Yes || Not tested || Yes || Not via gui ||
*Manjaro - Phosh 2021/5/31
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
*postmarketOS - Phosh 2021/5/31
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
*Arch - Phosh 2021/5/31
|-
| Canada || Freedom || Yes || Not tested || Yes || Yes ||
*Arch Pinephone - Phosh (APN: internet.windmobile.ca), 2021/4/25
|-
| Canada || SpeakOut || Yes || Not tested || Yes || Not tested ||
*Mobian - Phosh 2021/11/18
|-
| USA || Consumer Cellular (AT&T) || Yes || No || Yes || Yes ||
*Manjaro - Phosh 2021/06/26
|-
| USA || Google Fi (T-Mobile) || Yes || No || Yes || Yes ||
*Arch Linux Arm - Phosh 0.10.2 2021/05/29
|-
| Mexico || Telcel || Yes || Not tested || Yes || Yes ||
*Mobian - Phosh Weekly 2022/04/13
*PostmarketOS - SXMO De Sway v21.12 (stable) 2022/04/13
*PostmarketOS - Phosh v21.12 (stable) 2022/04/13
*PostmarketOS - Plasma Mobile v21.12 (stable) 2022/04/13
*PostmarketOS - sxmo edge 2021/09/09
|-
| USA || Ting || Yes || Yes - buggy || Yes || Yes ||
*Manjaro - Phosh 2021/12/10
|-
| USA || Simple Mobile || Yes || Yes || Yes || Yes ||
*Mobian - Phosh - Make sure APN is "Simple" in settings (note uppercase S)
|-
|}

== South America ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129
|-
|}

== Australia / Oceania ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129
|-
| Australia || Beyond (Telstra) || Yes || Yes || Yes || Yes || Manjaro Phosh Beta 20.
|-
| Australia || Belong (Telstra) || Yes || Yes || Yes || Yes || Arch (Danctnix), Feb 2022.
|-
| Australia || Optus || Yes || No. Ticket lodged with Chatty and mmsd re multiple APN issue || Yes || Yes || Manjaro Phosh Beta 20. Manjaro Plasma Mobile Beta 9 (Data working with this release). SXMO (Danctnix and PMOS edge December 2021).
|-
| Australia || Amaysim (Optus) || Yes || No. Ticket lodged with Chatty and mmsd re multiple APN issue || Yes || Yes || Manjaro Phosh
|-
| Australia || OPTUS (Dodo) || || ||Yes|| || Manjaro Plasma Mobile 5.23.4, 2021-12.27 (deepsleep disrupts settings)
|-
| Australia || Vodafone || Yes || Yes || Yes (No VoLTE) || Yes || pmOS Edge 5.15.3 kernel, 2022-02-10 with Phosh
|}

== Middle East ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || USSD working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Israel|| Cellcom prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Cellcom Talkman|| receive+notify|| YES || YES (when manually selecting the MMS APN) || ring(VoLTE not working) || YES || on mobian Feb 04, 2022, Earthquake early warning system did not show a notification on Feb 07, 2022
|-
|-
| Israel|| Cellcom Talkman|| NO || NO || NO || ring+ notify (VoLTE not working)|| YES || on Plasma Mobile Feb 04, 2022
|-
|-
| Israel|| Golan TC || receive+notify|| YES || NA || ring+ notify (VoLTE not working) || Yes || on mobian/phosh March 13 2022
|-
|-
| Israel|| Partner prepay || receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Pelephone prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Hot prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| 019 prepay|| No || NA || NA ||Bars only || NA || on PmOS Sxmo May 14 2021.
|-

|}

= Special carrier notes =

{{Warning|This section contains providers which do not work or require special settings or actions to work.}}

Some carriers might support only certain frequencies or might require certain settings in Ofono or ModemManager. The following is a list of collected notes for carriers regarding special settings, hints or information:

== USA ==
=== AT&T ===
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page], AT&T's primary bands are 12 and 17 - 700ac and 700 MHz respectively. Phone and SMS with PinePhone work out-of-the-box with AT&T. If you transfer a SIM card from another phone you were using with AT&T, you may need to activate the PinePhone through [https://www.att.com/buy/wireless/byod/byod AT&T's website]. Calls and SMS messages work. 4G and MMS work if [https://www.att.com/support/article/wireless/KM1062162/ these settings] are used for APN, MMSC, and Proxy.

AT&T may drop support with their network upgrade in the near future like their child company Cricket Wireless already has. [https://www.att.com/ecms/dam/att/consumer/help/pdf/Devices-Working-on-ATT-Network.pdf This page] lists their supported devices for their new network.

=== Consumer Cellular ===

Consumer Cellular is a MVNO that uses both AT&T and T-Mobile networks. On the AT&T network LTE data works without special configuration. If you transfer a SIM card from another phone to the PinePhone, you may need to contact customer support in order for them to register the IMEI association to the correct hardware; in one case it was first incorrectly identified as a Samsung Google Nexus Prime before later being correctly identified by the modem model Quectel EG25-G. Customer support also explicitly enabled VoLTE on the device. After VoLTE instructions on this site were followed and APN instructions on the Consumer Cellular site were followed, VoLTE was confirmed working.

=== Cricket Wireless ===
Cricket wireless is a MVNO that uses AT&T's network. VoLTE was fully supported, but the PinePhone is no longer considered a compatible device in the US by the carrier (as of March 2021).

=== Faith Wireless ===
Faith Wireless is a MVNO that uses AT&T's network. VoLTE was fully supported, but the PinePhone comes up as a Mobile Broadband Device. Faith Wireless does not service Mobile Broadband Devices. (As of February 2022)

=== SimpleMobile ===
SimpleMobile is a T-Mobile prepaid MVNO operating in the United States. 4G LTE, VoLTE, data, and SMS all work on the PinePhone after activation. Activation can be done online without extra software or assistance, go to https://www.simplemobile.com/activation/byopcollectsim and make sure you have your SIM card and IMEI ready.

=== Sprint ===
Sprint is currently not supported due to unknown reasons. Any input regarding this issue is highly appreciated.

=== T-Mobile ===
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page],
T-Mobile's primary frequency band for the United States is 12 (700ac MHz).

T-Mobile's bands and protocols are summarized on
[https://www.frequencycheck.com/carriers/t-mobile-united-states this page].

While the PinePhone's modem does support all LTE bands that T-Mobile uses in the US (And is one of the best choices for band support with the PinePhone's modem in the US), VoLTE is still listed as "Under development" by the modem manufacturer. T-Mobile's system also does not list the PinePhone as a compatible device due to this lack of official VoLTE support. The modem is capable of working on T-Mobile with VoLTE support enabled.

=== Verizon ===
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page],
Verizon's primary frequency band for the United States is 13 (700 MHz). Verizon's bands and protocols are summarized on
[https://www.frequencycheck.com/carriers/verizon-wireless-united-states this page]. According to the same page, Verizon might restrict their network to only approved devices.

Some users reported that they were able to activate their Verizon SIM by using an Verizon-approved burner phone and then inserting the SIM into the PinePhone.

=== TracFone ===
Following TracFone's [https://www.verizon.com/about/news/verizon-completes-tracfone-wireless-inc-acquisition acquisition by Verizon], support for the AT&T and T-Mobile bands has been deprecated as of early June 2022. TracFone has the same issues with connecting as Verizon, as they now exclusively use Verizon's frequency band.

=== Google Fi ===
Only T-Mobile service works currently, not US Cellular or Sprint.
The APN is h2g2.
Information from [https://forum.pine64.org/showthread.php?tid=11675&page=7 the forum].

Bear in mind that initial activation of the SIM card is not possible without an Android phone running Google Apps.

It should also be noted that Google uses a non-standard MMS implementation that is unlikely to be supported on the PinePhone at any point.

== Europe ==
=== Telekom Germany ===
With low signal, there may be loud interference noise audible in calls on the receiving end. It has not yet been tested whether or not this problem is carrier specific. An easy fix is extending the modem antenna with aluminum foil (or similar) inside the back cover of the phone.

=== Orange Poland ===
Setting up dual stack IPv4 and IPv6 may require [https://etherpad.gnome.org/p/dx7pbkPMCytMLMRl1eyo extra work], because the carrier provides IPv4 connectivity on internetipv6 APN via a protocol called CLAT/NAT64.

=== Sweden ===
Calls, SMS, and data (2G, 3G, and 4G) should work out of the box (tested three carriers on Mobian Phosh).
On about half of Swedish carriers, MMS works when set manually, the rest have different data APN and MMS APN. VoLTE (i.e. 4G calls) did not work out of the box ([https://github.com/Eliot-Roxbergh/notes_pinephone for me]) but worked well after [https://github.com/the-modem-distro/pinephone_modem_sdk/blob/kirkstone/docs/FLASHING.md#adsp-versions updating firmware] to ADSP Version 01.003.01.003 and installing [https://github.com/the-modem-distro/pinephone_modem_sdk Pinephone Modem SDK]. Regarding call quality, from my experience; 3G has the best quality, then 4G also works well although you often hear electrical white noise sound (on your side), 2G works well but there is a risk of strong noise when on bad coverage (this can affect both sides of the call).
Voicemail should work, you should get a SMS when you have a missed call etc. Only issue I had was that when getting sent to voicemail in a call, for some target carriers (?) it was completely silent.

== Asia ==
=== China Telecom ===
The baseband itself ships with bad (for CDMA, which isn't supported by EG25-G) MBN file for CT, so a force change of MBN file to the generic one is needed to get VoLTE (thus SMS+Call) work.

Run the following AT commands to force ROW_Generic_3GPP which can support VoLTE on CT:
<pre>
AT+QMBNCFG="autosel",0
AT+QMBNCFG="select","ROW_Generic_3GPP"
AT+QCFG="ims",1
</pre>

=== SoftBank ===
SoftBank USIM cards are IMEI-locked, and on top of that will only work on either Android or iOS. A free SIM is available, but that one is data only. The same problem might exist with MVNO's who make use of the SoftBank network, and therefore it's advised to pick either NTT docomo or au as the MNO.

= Known issues =
Known issues:
* The [https://www.frequencycheck.com/models FrequencyCheck model page] does not list either Pine64 or the PinePhone.
* T-Mobile's system does not list the PinePhone as a compatible device due to the lack of official VoLTE support from the manufacturer, despite the fact that it does work.
* MMS doesn't currently work in any distribution on the PinePhone by default. This means images and group chats will not work in text messages.
* Some providers may allow only certain known devices identified by their [https://en.wikipedia.org/wiki/Type_Allocation_Code Type Allocation Code].

= MMS workarounds =
These scripts allow partial MMS support on a [[PinePhone]] in distributions without working MMS support:

* JMMS: [https://git.sr.ht/~amindfv/jmms]
* silvermms: [https://gitlab.com/5ilver/silvermms]
* MMS via Matrix with mmmpuppet: [[PinePhone MMS with Matrix]]

There is a Haskel MMS client. MMS can also be manually composed with mmsd on the command line.

= Resources =
* IMEI - [https://en.wikipedia.org/wiki/International_Mobile_Equipment_Identity International Mobile Equipment Identity]

[[Category:PinePhone]]

PinePhone Carrier Support

2023-02-20T21:16:56Z

Sethi: Add Honest Mobile to table.

{{under construction}}

This page contains hints on setting up cellular network connectivity for specific carriers.
For more general information, see the carrier support section of [[PinePhone#Modem]]. For the APN settings see [[PinePhone APN Settings]].

= Check compatibility =
To check if the PinePhone is supported on your carrier:

Search for your carrier on [https://www.frequencycheck.com/ frequencycheck.com] and compare the carrier's LTE/GSM/WCDMA frequencies to the PinePhone's supported frequencies (listed in the [[File:Quectel_EG25-G_LTE_Standard_Specification_V1.3.pdf]] modem specification sheet).

It is likely that there will be a few frequencies that your carrier uses which are not supported by the PinePhone. Not all of the carrier's frequencies need to be supported by the PinePhone for it to work - as long as ''most'' of them are supported, you will still get good coverage.

= Tested and working carriers =

The following is a list of carriers which has been tested by users and confirmed to be working (excerpt):

== Asia ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
| Japan || [[wikipedia:SoftBank_Group#SoftBank_Mobile|SoftBank]] || Not tested || Unsupported by carrier || No || No || Mobian Phosh, December 2020
|-
| Japan || [[wikipedia:ja:楽天モバイル|Rakuten Mobile]] || Unsupported by carrier || Unsupported by carrier || Yes || Yes || Mobian Phosh, January 2021
|-
| Japan || [[wikipedia:ja:楽天モバイル|Rakuten Mobile]] || Unsupported by carrier || Unsupported by carrier || Yes || No || Manjaro Plasma Mobile February 2021
|-
| Japan || [[wikipedia:NTT Docomo|Docomo]] || Yes || Not tested || Yes || Yes || Mobian Phosh, February 2021
|-
| India || Vodafone / Vi India || Yes || Not tested || Yes || Yes || DanctNIX (Arch Linux ARM) with Phosh, March 2021
|-
| Malaysia || Celcom || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| Malaysia || Maxis || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| Malaysia || U-Mobile || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| Malaysia || Yes || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| South Korea || KT || Yes || Not tested || Yes || Yes || Manjaro Phosh, June 2021
|-
| China || [[wikipedia:China Mobile|China Mobile]] || Yes || Not tested || Yes || No || Mobile NixOS, December 2021
|-
| China || [[wikipedia:China Telecom|China Telecom]] || Yes (hack needed) || Not tested || Yes (hack needed) || No || AOSC OS Phosh, January 2022
|-
| Japan || [[wikipedia:ja:楽天モバイル|Rakuten Mobile]] || Yes || Not tested || Yes || Yes || Mobian Phosh, January 2022 (rivised from January 2021)
|-
| China || [[wikipedia:China Unicom|China Unicom]] || Yes || Not tested || Yes || Yes || [https://postmarketos.org/ pmOS] 22.06.3 Phosh, [[PineModems#Bootloader_unlocking | BLunlck'd]], [[PinePhone#Firmware_update|upd'd]] to [https://github.com/Biktorgj/quectel_eg25_recovery/tree/EG25GGBR07A08M2G_30.006.30.006 *8M2G_30.006*], November 2022
|}

== Africa ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129
|-
|}

== Europe ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Ukraine || KyivStar || Yes || Not tested || Yes || Yes || Mobian Phosh(11Nov21)
|-
|-
| Ukraine || Vodafone || Yes || Not tested || Yes || Yes || Manjaro ARM Phosh(29Jun22)
|-
| Sweden || Fello (uses Telia network) || Yes || No (data and MMS APN are different) || Yes || Yes || Mobian Phosh, October 2022
|-
| Sweden || Hallon (uses Tre network) || Yes || Yes (when manually selecting the MMS APN) || Yes || Yes || Mobian Phosh, October 2022
|-
| Sweden || Comviq (uses Tele2 network) || Yes || Yes (when manually selecting the MMS APN) || Yes || Yes || Mobian Phosh, October 2022
|-
| Sweden || Tele2 || Yes || Not tested || Yes || Not tested || Manjaro ARM Posh
|-
| Sweden || Telenor SE || Not tested || Not tested (should NOT work, data and MMS APN are different) || Yes || Not tested || Manjaro Plasma Mobile beta2
|-
| UK || Three || Yes || Not tested || Yes || Yes || Manjaro Plasma Mobile beta2
|-
| UK || Vodafone || Yes || Not tested || Yes || Yes || ALARM & pmOS (Phosh?), modem FW latest - 26 Feb 21
|-
| UK || Sky Mobile (O2) || Yes || Not tested || Yes || Yes || ArchLinux Phosh (20210908 image, fully updated) - 3 October 2021
|-
| UK || Smarty Mobile (Three) || Yes || Yes || Yes || Yes || Arch Linux SXMO (Wayland) - 23 March 2022
|-
| UK || Honest Mobile (Three) || Yes || No || Yes - buggy || Yes - buggy || postmarketOS 22.12 (Phosh) - 20 February 2023
|-
| France || Orange || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021
|-
| France || SFR || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021
|-
| France || Free || Yes || Not tested || Yes || Yes || pmOS SXMO (Wayland) - 27 March 2022
|-
| Czech Republic || O2 || Yes (only on 2G) || Not tested || Yes || Yes || Mobian Phosh (20210517 image up to date) - 2 June 2021
|-
| Germany || Congstar || Yes || Not tested || Yes || Yes (IPv4 & IPv6) || Mobian (Megi's kernel 5.13.0-rc4, apt up-to-date) with Phosh, 2021-06-07
|-
| Germany || E-Plus || Yes (sending only 2G) || Not tested || Yes || Yes || Manjaro Phosh and postmarketOS, 2021-10-15
|-
| Germany || Telekom || Yes || Not tested || Yes || Not tested || Mobian Phosh (5.10-sunxi64), 2021-07-28
|-
| Germany || O2 / Telefonica || Yes || Not tested || Yes || Not tested || KPlasma
|-
| Hungary || Telekom || Yes || Not tested || Yes || Yes (IPv4) || Manjaro Phosh Beta 12, 2021-07-30
|-
| Hungary || Telenor/Yettel || Yes || Not tested || Yes || Yes || Mobian-Phosh-20210517, 2021-09-24
|-
| Denmark || CBB || Yes || Not tested || Yes || Yes || Manjaro Plasma Mobile Beta 5, 2021-06-30
|-
| Belgium || Telenet || Yes || Not tested || Yes || Yes || postmarketOS v20.05, v21.03, v21.06 and edge, 2021-08-15
|-
| Belgium || CARREFOUR || Yes || Not tested || Yes || Yes || postmarketOS v20.05, v21.03, v21.06 and edge, 2021-08-15
|-
| Poland || Play || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta 18, 2021-11-14
|-
| Poland || Orange || Yes || No || Yes || Yes (IPv4 & IPv6) || Manjaro Phosh v21.10, 2021-12-23
|-
| Poland || Premium Mobile || Yes || No || Yes || Yes || Manjaro Phosh v22.01, 2022-01-13
|-
| Italy || WindTre Italy || Yes || Not tested || Yes || Yes || Archlinux ARM Plasma Mobile
|-
| Switzerland || Salt || Yes || Not tested || Yes || Yes || Phosh on Mobian + Arch
|}

== North America ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI || Modem Firmware
|-
|-
| USA || AT&T || Yes || Yes || Yes || Yes ||
* Mobian - Phosh
|-
| USA || T-Mobile || Yes || No || Yes || Yes ||
* Arch Linux Arm 2020/11/29
* Mobian - Phosh
* Manjaro - KDE Plasma Mobile
|-
| USA || T-Mobile || Yes || Yes || Yes || Yes ||
* Mobian Bookworm (Phosh) (2022-03-08)
|| EG25GGBR07A08M2G_01.003.01.003
|-
| USA || MetroPCS (T-Mobile) || Yes || No || Yes || Yes ||
*Arch Linux Arm (Phosh,SXMO) 2021/04/29
*Manjaro - Phosh 2021/04/29
*Mobian - Phosh 2021/3/20
|-
| USA || T-Mobile || Yes - buggy || No || Yes - buggy || Yes - buggy ||
*Manjaro - Plasma Dev 2020/11/21
*Ubuntu Touch - 2020/11/26
*KDE Neon 2020/11/02
|-
| USA || Mint Mobile (T-Mobile) || Yes || Yes || Yes || Yes ||
*Mobian - Phosh 2021/3/14
*postMarketOS - Phosh, Sxmo, Plasma Mobile 2021/5/26
*Ubuntu Touch 2021/5/24
*Manjaro - Phosh 2022/3/25
|-
| USA || Patriot Mobile (T-Mobile) || Yes || Yes chatty v0.6.1 mmsd-tng v1.8 || Yes || Yes ||
*Arch Linux Arm - Phosh 2022/01/12
|-
| USA || Tello (T-Mobile) || Yes || Yes || Yes || Yes ||
*DanctNIX (Arch Linux ARM) - Phosh 2022-07-09
|-
| USA || TracFone || No || No || No || No ||
*postMarketOS - Phosh 2022/06/28
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
*Mobian - Phosh 2021/3/1
|-
| USA || US Mobile || Yes || Not tested || Yes || Not Tested ||
*Mobian - Phosh 2022/01/09
|-
| USA || Verizon || No || No || No || No ||
*Ubuntu Touch 2021/5/24 (You can occasionally get the settings to work with Verizon, but it seems like the settings automatically changes the carrier to the wrong one after a few minutes)
|-
| USA || Verizon || Not tested || Not tested || Yes || Not via gui ||
*Manjaro - KDE Plasma Mobile 2021/5/10
|-
| USA || Verizon || Yes || Not tested || Yes || Not via gui ||
*Manjaro - Phosh 2021/5/31
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
*postmarketOS - Phosh 2021/5/31
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
*Arch - Phosh 2021/5/31
|-
| Canada || Freedom || Yes || Not tested || Yes || Yes ||
*Arch Pinephone - Phosh (APN: internet.windmobile.ca), 2021/4/25
|-
| Canada || SpeakOut || Yes || Not tested || Yes || Not tested ||
*Mobian - Phosh 2021/11/18
|-
| USA || Consumer Cellular (AT&T) || Yes || No || Yes || Yes ||
*Manjaro - Phosh 2021/06/26
|-
| USA || Google Fi (T-Mobile) || Yes || No || Yes || Yes ||
*Arch Linux Arm - Phosh 0.10.2 2021/05/29
|-
| Mexico || Telcel || Yes || Not tested || Yes || Yes ||
*Mobian - Phosh Weekly 2022/04/13
*PostmarketOS - SXMO De Sway v21.12 (stable) 2022/04/13
*PostmarketOS - Phosh v21.12 (stable) 2022/04/13
*PostmarketOS - Plasma Mobile v21.12 (stable) 2022/04/13
*PostmarketOS - sxmo edge 2021/09/09
|-
| USA || Ting || Yes || Yes - buggy || Yes || Yes ||
*Manjaro - Phosh 2021/12/10
|-
| USA || Simple Mobile || Yes || Yes || Yes || Yes ||
*Mobian - Phosh - Make sure APN is "Simple" in settings (note uppercase S)
|-
|}

== South America ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129
|-
|}

== Australia / Oceania ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129
|-
| Australia || Beyond (Telstra) || Yes || Yes || Yes || Yes || Manjaro Phosh Beta 20.
|-
| Australia || Belong (Telstra) || Yes || Yes || Yes || Yes || Arch (Danctnix), Feb 2022.
|-
| Australia || Optus || Yes || No. Ticket lodged with Chatty and mmsd re multiple APN issue || Yes || Yes || Manjaro Phosh Beta 20. Manjaro Plasma Mobile Beta 9 (Data working with this release). SXMO (Danctnix and PMOS edge December 2021).
|-
| Australia || Amaysim (Optus) || Yes || No. Ticket lodged with Chatty and mmsd re multiple APN issue || Yes || Yes || Manjaro Phosh
|-
| Australia || OPTUS (Dodo) || || ||Yes|| || Manjaro Plasma Mobile 5.23.4, 2021-12.27 (deepsleep disrupts settings)
|-
| Australia || Vodafone || Yes || Yes || Yes (No VoLTE) || Yes || pmOS Edge 5.15.3 kernel, 2022-02-10 with Phosh
|}

== Middle East ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || USSD working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Israel|| Cellcom prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Cellcom Talkman|| receive+notify|| YES || YES (when manually selecting the MMS APN) || ring(VoLTE not working) || YES || on mobian Feb 04, 2022, Earthquake early warning system did not show a notification on Feb 07, 2022
|-
|-
| Israel|| Cellcom Talkman|| NO || NO || NO || ring+ notify (VoLTE not working)|| YES || on Plasma Mobile Feb 04, 2022
|-
|-
| Israel|| Golan TC || receive+notify|| YES || NA || ring+ notify (VoLTE not working) || Yes || on mobian/phosh March 13 2022
|-
|-
| Israel|| Partner prepay || receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Pelephone prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Hot prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| 019 prepay|| No || NA || NA ||Bars only || NA || on PmOS Sxmo May 14 2021.
|-

|}

= Special carrier notes =

{{Warning|This section contains providers which do not work or require special settings or actions to work.}}

Some carriers might support only certain frequencies or might require certain settings in Ofono or ModemManager. The following is a list of collected notes for carriers regarding special settings, hints or information:

== USA ==
=== AT&T ===
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page], AT&T's primary bands are 12 and 17 - 700ac and 700 MHz respectively. Phone and SMS with PinePhone work out-of-the-box with AT&T. If you transfer a SIM card from another phone you were using with AT&T, you may need to activate the PinePhone through [https://www.att.com/buy/wireless/byod/byod AT&T's website]. Calls and SMS messages work. 4G and MMS work if [https://www.att.com/support/article/wireless/KM1062162/ these settings] are used for APN, MMSC, and Proxy.

AT&T may drop support with their network upgrade in the near future like their child company Cricket Wireless already has. [https://www.att.com/ecms/dam/att/consumer/help/pdf/Devices-Working-on-ATT-Network.pdf This page] lists their supported devices for their new network.

=== Consumer Cellular ===

Consumer Cellular is a MVNO that uses both AT&T and T-Mobile networks. On the AT&T network LTE data works without special configuration. If you transfer a SIM card from another phone to the PinePhone, you may need to contact customer support in order for them to register the IMEI association to the correct hardware; in one case it was first incorrectly identified as a Samsung Google Nexus Prime before later being correctly identified by the modem model Quectel EG25-G. Customer support also explicitly enabled VoLTE on the device. After VoLTE instructions on this site were followed and APN instructions on the Consumer Cellular site were followed, VoLTE was confirmed working.

=== Cricket Wireless ===
Cricket wireless is a MVNO that uses AT&T's network. VoLTE was fully supported, but the PinePhone is no longer considered a compatible device in the US by the carrier (as of March 2021).

=== Faith Wireless ===
Faith Wireless is a MVNO that uses AT&T's network. VoLTE was fully supported, but the PinePhone comes up as a Mobile Broadband Device. Faith Wireless does not service Mobile Broadband Devices. (As of February 2022)

=== SimpleMobile ===
SimpleMobile is a T-Mobile prepaid MVNO operating in the United States. 4G LTE, VoLTE, data, and SMS all work on the PinePhone after activation. Activation can be done online without extra software or assistance, go to https://www.simplemobile.com/activation/byopcollectsim and make sure you have your SIM card and IMEI ready.

=== Sprint ===
Sprint is currently not supported due to unknown reasons. Any input regarding this issue is highly appreciated.

=== T-Mobile ===
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page],
T-Mobile's primary frequency band for the United States is 12 (700ac MHz).

T-Mobile's bands and protocols are summarized on
[https://www.frequencycheck.com/carriers/t-mobile-united-states this page].

While the PinePhone's modem does support all LTE bands that T-Mobile uses in the US (And is one of the best choices for band support with the PinePhone's modem in the US), VoLTE is still listed as "Under development" by the modem manufacturer. T-Mobile's system also does not list the PinePhone as a compatible device due to this lack of official VoLTE support. The modem is capable of working on T-Mobile with VoLTE support enabled.

=== Verizon ===
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page],
Verizon's primary frequency band for the United States is 13 (700 MHz). Verizon's bands and protocols are summarized on
[https://www.frequencycheck.com/carriers/verizon-wireless-united-states this page]. According to the same page, Verizon might restrict their network to only approved devices.

Some users reported that they were able to activate their Verizon SIM by using an Verizon-approved burner phone and then inserting the SIM into the PinePhone.

=== TracFone ===
Following TracFone's [https://www.verizon.com/about/news/verizon-completes-tracfone-wireless-inc-acquisition acquisition by Verizon], support for the AT&T and T-Mobile bands has been deprecated as of early June 2022. TracFone has the same issues with connecting as Verizon, as they now exclusively use Verizon's frequency band.

=== Google Fi ===
Only T-Mobile service works currently, not US Cellular or Sprint.
The APN is h2g2.
Information from [https://forum.pine64.org/showthread.php?tid=11675&page=7 the forum].

Bear in mind that initial activation of the SIM card is not possible without an Android phone running Google Apps.

It should also be noted that Google uses a non-standard MMS implementation that is unlikely to be supported on the PinePhone at any point.

== Europe ==
=== Telekom Germany ===
With low signal, there may be loud interference noise audible in calls on the receiving end. It has not yet been tested whether or not this problem is carrier specific. An easy fix is extending the modem antenna with aluminum foil (or similar) inside the back cover of the phone.

=== Orange Poland ===
Setting up dual stack IPv4 and IPv6 may require [https://etherpad.gnome.org/p/dx7pbkPMCytMLMRl1eyo extra work], because the carrier provides IPv4 connectivity on internetipv6 APN via a protocol called CLAT/NAT64.

=== Sweden ===
Calls, SMS, and data (2G, 3G, and 4G) should work out of the box (tested three carriers on Mobian Phosh).
On about half of Swedish carriers, MMS works when set manually, the rest have different data APN and MMS APN. VoLTE (i.e. 4G calls) did not work out of the box ([https://github.com/Eliot-Roxbergh/notes_pinephone for me]) but worked well after [https://github.com/the-modem-distro/pinephone_modem_sdk/blob/kirkstone/docs/FLASHING.md#adsp-versions updating firmware] to ADSP Version 01.003.01.003 and installing [https://github.com/the-modem-distro/pinephone_modem_sdk Pinephone Modem SDK]. Regarding call quality, from my experience; 3G has the best quality, then 4G also works well although you often hear electrical white noise sound (on your side), 2G works well but there is a risk of strong noise when on bad coverage (this can affect both sides of the call).
Voicemail should work, you should get a SMS when you have a missed call etc. Only issue I had was that when getting sent to voicemail in a call, for some target carriers (?) it was completely silent.

== Asia ==
=== China Telecom ===
The baseband itself ships with bad (for CDMA, which isn't supported by EG25-G) MBN file for CT, so a force change of MBN file to the generic one is needed to get VoLTE (thus SMS+Call) work.

Run the following AT commands to force ROW_Generic_3GPP which can support VoLTE on CT:
<pre>
AT+QMBNCFG="autosel",0
AT+QMBNCFG="select","ROW_Generic_3GPP"
AT+QCFG="ims",1
</pre>

=== SoftBank ===
SoftBank USIM cards are IMEI-locked, and on top of that will only work on either Android or iOS. A free SIM is available, but that one is data only. The same problem might exist with MVNO's who make use of the SoftBank network, and therefore it's advised to pick either NTT docomo or au as the MNO.

= Known issues =
Known issues:
* The [https://www.frequencycheck.com/models FrequencyCheck model page] does not list either Pine64 or the PinePhone.
* T-Mobile's system does not list the PinePhone as a compatible device due to the lack of official VoLTE support from the manufacturer, despite the fact that it does work.
* MMS doesn't currently work in any distribution on the PinePhone by default. This means images and group chats will not work in text messages.
* Some providers may allow only certain known devices identified by their [https://en.wikipedia.org/wiki/Type_Allocation_Code Type Allocation Code].

= MMS workarounds =
These scripts allow partial MMS support on a [[PinePhone]] in distributions without working MMS support:

* JMMS: [https://git.sr.ht/~amindfv/jmms]
* silvermms: [https://gitlab.com/5ilver/silvermms]
* MMS via Matrix with mmmpuppet: [[PinePhone MMS with Matrix]]

There is a Haskel MMS client. MMS can also be manually composed with mmsd on the command line.

= Resources =
* IMEI - [https://en.wikipedia.org/wiki/International_Mobile_Equipment_Identity International Mobile Equipment Identity]

[[Category:PinePhone]]

User:Sethi

2021-09-05T10:57:02Z

Sethi:

Hey! Welcome to my profile, though I think you'd be better off stalking me somewhere else.

* https://gitlab.com/SethFalco
* https://github.com/SethFalco
* https://fosstodon.org/web/accounts/250195

User:Sethi

2021-05-02T23:40:51Z

Sethi: Created page with "Hey! Welcome to my profile, though I think you'd be better off stalking me somewhere else. * https://github.com/SethFalco * https://gitlab.com/SethFalco * https://twitter.com..."

Hey! Welcome to my profile, though I think you'd be better off stalking me somewhere else.

* https://github.com/SethFalco
* https://gitlab.com/SethFalco
* https://twitter.com/SethFalco

PinePhone FAQ

2021-05-02T23:36:55Z

Sethi: Fixed typos, made spelling of Wi-Fi consistent, and made capitalization of nouns consistent.

A list of frequently asked question.

== Hardware ==

=== Revisions ===
==== What are Community Editions? ====
Community Editions of the PinePhone were versions of the PinePhone which came preinstalled with the operating system of a partner project and featured the logo of the project on the back panel. The Community Edition was intended to help partner projects developing these systems: "Community editions are meant to bring exposure to partner-projects operating systems and communities, as well as help finance ongoing development.", [https://www.pine64.org/2020/04/02/pinephone-ubports-community-edition-pre-orders-now-open/ source].

==== Is the Community Edition hardware the latest revision? ====
The Community Edition program (featuring the mainboard numbers 1.2 through 1.2b and branded back covers) which provided the branded PinePhones has since ended, and a Beta Edition has since been released. The only difference between each Community Edition is the inclusion of crucial bug fixes, with the last issue being fixed with the 1.2b motherboard shipping with the Manjaro CE PinePhones. The 1.2b motherboard is also currently used in the Beta Edition PinePhones, however the Beta Edition units do not ship with any back cover branding. There are currently no plans for further hardware revisions.

Aside from the back cover, the only other difference between each Community Edition is that starting with the postmarketOS PinePhone, a convergence package option was released that adds another gigabyte of ram to the phone and a 32GB eMMC instead of a 16GB eMMC. Convergence packages also included a dock for plugging in USB peripherals and connecting to an HDMI monitor, however you can purchase a generic USB-C dock to use with a 2GB PinePhone.

The predecessor to the Convergence Edition PinePhones was the Braveheart Edition intended for developers to bring up the platform, which had the version number 1.1. For more details about the topic see [[PinePhone#Hardware Revisions]].

==== Will there be other Community Editions? ====
Five Community Editions have been announced: [https://www.pine64.org/2020/04/02/pinephone-ubports-community-edition-pre-orders-now-open/ UBports], [https://www.pine64.org/2020/06/15/june-update-postmarketos-ce-pinephone-shipping-pine64-cluster/ postmarketOS], [https://www.pine64.org/2020/08/31/pinephone-manjaro-community-edition/ Manjaro], [https://www.pine64.org/2020/12/01/kde-community-edition-is-now-available/ KDE], and [https://www.pine64.org/2021/01/17/mobian-community-edition/ Mobian]. Since the release of the Mobian edition, the Beta Edition PinePhones have been released and the Community Edition Program has ended.

==== In simple terms, what are the differences between Braveheart and the new Community Edition? ====
The Braveheart PinePhone was the first public revision of the PinePhone which was intended solely for developers and Linux enthusiasts. The UBports Community Edition was the next revision of the PinePhone with an updated mainboard based on feedback from the Braveheart Edition, see [[PinePhone#Hardware Revisions]]. All current revisions of the PinePhone continue to be intended for developers and enthusiasts, however Pine64 will be starting to offer partnered retail units of the PinePhone which will have a better warranty and technical support (keep in mind even then it is not intended for a broader audience at this time, as the software still needs work and the hardware does not hold up well to modern consumer standards).

==== Will there be a newer revision after the Community Editions? ====
Starting with the UBports Community Edition the PinePhone has gotten CE and FCC certifications, repeating the certification process due to changes in the hardware design is very expensive, so the 1.2b motherboard is viewed as the final revision. The PinePhone (and parts for them) will be produced and sold for at least 5 years.

==== Will there be hardware differences between the Community Editions? ====

Besides the varied back covers, starting with the launch of the PostmarketOS CE there has been the release of a convergence package option for the PinePhone which includes more ram and storage, and an included dock for convenience. There has also been multiple hardware changes starting with the UBports CE (mainboard 1.2) and ending with the Manjaro CE (mainboard revision 1.2b). There are currently no plans for future hardware changes for a few years.

==== How powerful is the PinePhone's hardware? ====

The PinePhone is about on par with a Raspberry Pi 3 in terms of CPU power, however going by GFLOPS it has half the GPU power. The Pi 3's Videocore IV does 24 GFLOPS, and the Mali 400 MP2 on the PinePhone only 10.8.

Despite this, using software rendering the PinePhone is capable of smoothly rendering at 1080p resolution or higher. However, with a fully GPU-accelerated mobile environment you should expect a more sluggish experience outputting to such resolutions. Unfortunately, the Mali 400 MP2 (a 2008 arm mobile GPU) simply isn't intended to push 1080p resolution. With that said, the VPU of the PinePhone has been shown to handle smooth H.264 1440p30 video playback using Cedrus and gstreamer as documented [https://xnux.eu/log/#001 here]. Further, the PinePhone should be more than capable of a smooth phone experience when used in conjunction with well optimized software that makes use of its hardware features. It is also more than capable of running many light games (including 3D ones such as SuperTuxKart), and retro gaming. Expect further speed improvements over time as the drivers are improved, and in the meanwhile you can look into slightly [[overclocking]] the device (at your own risk).

=== Sound ===

The default ringtone for Mobian Phosh can be found at /usr/share/sounds/freedesktop/stereo/phone-incoming-call.oga

=== Modem ===

==== The modem isn't working ====

In order to use the modem and Wi-Fi/Bluetooth, you need to ensure the battery is inside the device and has a sufficient charge. Even when supplying the phone with enough power, the modem and Wi-Fi chip will not work without a connected battery. Further, double check that you have not put the SD card into the sim card slot, or vice versa.

==== Does the PinePhone only wake up from sleep for calls and texts? ====

Yes. Unless the PinePhone is configured to wake up every few minutes from deep sleep in crust (At the cost of battery life. However, in the future there may be other solutions), then there is not any way to get any notifications for applications. The modem on the PinePhone will wake the device for incoming calls and texts however, and the real-time clock is also capable of waking the device for alarms.

=== Battery ===

==== The battery is stuck inside the phone ====

The battery can be stuck in the phone if the screws of the frame are overtightened.

If your battery is stuck inside the PinePhone, grab a screwdriver and completely unscrew all the screws of the midframe. Then pull out the battery (you may have to fully take off the midframe in some cases to get it out). And then rescrew the midframe, but only tighten the screws to the point where they are just barely tight to hold. This should allow you to remove the battery easily.

==== The battery is discharging while the phone is powered off (Braveheart Edition) ====

The issue is not present on the Community Edition. Due to a hardware bug, after power off, the phone still consumes 20–30mA which drains the battery in 3-4 days. A manual procedure to fix the hardware bug is described [https://xnux.eu/devices/pp-pmic-fix.jpg here].

==== The battery only charges to ~84% ====

Some pre-made OSes using megi's kernel limit the maximum amount of charge to roughly ~84% in the hope of prolonging the battery life, as repeatedly reaching the upper level of battery charge reduces the battery's lifetime (this is not a safety feature!). The same effect however also applies when repeatedly draining the battery to a low level - users are therefore advised to consider if that setting is reasonable depending on their usage. The setting can be overwritten via Sysfs, to let the battery fully charge (this can lower the replaceable's battery lifetime considerably depending on the charging behavior!):

{{warning|The following instructions are directed towards expert-level users and developers!}}

<code>echo 4350000 > /sys/class/power_supply/axp20x-battery/voltage_max_design</code>

=== Kill Switches ===
==== What are the kill switches doing? ====

{| 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
| Wi-Fi / Bluetooth
| Pulls up CHIP_EN
| "On" enables Wi-Fi 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.5mm 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.5mm audio jack, "off" switches the jack to hardware UART mode.
|}

=== Memory ===

==== What's the speed difference between the eMMC and SD cards? ====
Maximum transfer speed of the eMMC is around 85 MB/s, while SD cards are limited to approximately 23 MB/s (even with faster cards).

=== GPS ===

==== GPS doesn't work ====

Like almost all smartphones, the PinePhone GPS antenna is small and can only get a first fix unassisted if the GPS signal is very strong. To make first fix faster and more reliable, phones download assistance data either from the phone network or from the internet. The GPS in the PinePhone modem supports the internet based assistance method, as detailed in the modem documentation, but this isn't yet supported out of the box by any of the distros. There is a [https://gist.github.com/alastair-dm/263209b54d01209be28828e555fa6628 proof of concept script] to show that it can work.

Until AGPS support makes its way into the distros you'll have to make some manual changes - see for example [https://wiki.mobian-project.org/doku.php?id=location Mobian wiki]

== Software ==

=== Installation ===

==== How can I install an operating system on the SD card / eMMC? ====

See [[PinePhone Installation Instructions]].

=== Updating ===

Read the [[PinePhone Updating Instructions]].

=== Booting ===

==== What's the boot order for SD cards and eMMC? ====

The PinePhone will automatically boot from microSD if a bootable card is inserted. If no (bootable) microSD is found, it will boot from eMMC.

==== How can I select different OSes at boot? ====

There was a project by Danct12 which allows the user to select different OSes at boot, but the repository has since been archived: https://github.com/dreemurrs-embedded/Pineloader.

==== I turned on my Manjaro CE PinePhone. The red LED and screen backlight are briefly lit, then both are not and it will not boot. ====

This can be the result of at least one situation:

# The eMMC installation became corrupt or otherwise unbootable
# An SD card is present but not bootable (consider [[PinePhone#Detailed usage instructions]])

If there is an installation of Manjaro on both the eMMC & an SD card, the SD card will always boot first on the device. Try taking the SD card out and booting the installation that is on the eMMC. If the problem persists, it is likely there is an issue with both installations and you will need to reinstall your distribution. You may also want to check with your distribution's maintainers if boot issues are a common problem in a recent update.

==== I did not install an update in Ubuntu Touch and I'm stuck on the Pine64 logo after rebooting. ====

# Use a USB A-C cable to plug your phone into your PC
# Hold the PinePhone's power button for 4 seconds or more to power it off.
# Wait 5 seconds
# Hold the Volume Up and Power buttons on the PinePhone to boot into recovery. You should see the LED light red, then yellow, then green. The "Installing update" screen will appear, but a progress bar to indicate update progress will not. Ignore the "Installing update" part.
# Your PC may automatically mount the PinePhone's partitions. If it does, Safely Remove or Eject all of them.
# Open a terminal on your PC. Type <code>telnet 172.16.42.1</code>
# You should receive the text 'Welcome to Rescue SD Shell!'
# In the new Rescue SD shell, type <code>umount /dev/mmcblk2p10; e2fsck -fy /dev/mmcblk2p10 && sync</code>
# Once this command pipeline finishes, type <code>sync && reboot -f</code>

Your PinePhone should reboot into Ubuntu Touch. Now head to Settings -> Updates and install the new update!

If these steps did not solve your issue, please create a new thread here on the Pine64 forums, note what the problem looks like, then say that you've tried these steps already.

This is caused by corruption on the userdata partition. Normally this should be fixed by 'e2fsck' in the initramfs, however an error in image creation means that that version of e2fsck is unable to correct corruption. This has been fixed in all new PinePhone updates, so if you update from the factory image to any other image available to the PinePhone now, you will not experience this issue any longer.

==== I turned on my PinePhone running Ubuntu Touch. The red LED is lit and it will not boot. ====
# Hold the power button until the light turns off
# Hold the power button until the light turns on

You may need to repeat these steps more than once.

This is caused by u-boot apparently trying to use the eMMC before it is ready. We are not entirely sure why this occurs yet.

==== Can I install a different OS on my Community Edition? ====

Yes! While all the Community Edition PinePhones come with an OS preinstalled, you are free to use any OS on the integrated storage (the eMMC) or an SD card, see [[PinePhone Installation Instructions]] and [[PinePhone Software Releases]] on how to install them.

=== Other ===

==== How can I enable SSH? ====

In Ubuntu Touch you can run "sudo start ssh" to get a one-time start, or edit /etc/init/ssh.override and remove the manual line to make it auto-start.

In other distributions you may have to install SSH through its package manager and then proceed to use its init system to enable it. For Manjaro, Arch, and Mobian you can use "systemctl enable" and "systemctl start" command to enable and start ssh.

==== What works, what doesn't? ====

For Ubuntu Touch see https://gitlab.com/ubports/community-ports/pinephone#what-works-what-doesnt.

Other distributions will have different levels of functionality. Please refer to the release page of your chosen distribution for further information.

==== I can't connect to a 2.4Ghz Wi-Fi network in Ubuntu Touch. ====

Reboot your device by holding the power button until the "Power" dialog appears, then pressing "Restart".

If that does not fix the issue, note that all the following conditions must be met to use Wi-Fi on the PinePhone:

# The plastic tab between the battery and the device's battery contacts has been removed
# The battery is installed
# The Wi-Fi killswitch, #2, on the rear of the device is switched "ON"

Wi-Fi in the PinePhone only seems stable after a warm reboot like this.

==== What's the status of Android for the PinePhone? ====

Currently, there isn't any major push to get Android running well on the PinePhone. The developer Icenowy did get a Android image to run and partly work, it was however slow and buggy, with major functions not working. A solution for running some of your android apps may be found in Anbox as of now. Anbox is currently not included in Ubuntu Touch. In other distributions your millage may vary on what applications will run and how well.

==== Why are my apps loading slower than on my Android phone? ====

Android has multiple techniques in place to speed up launching applications after the first launch, such as the "Dalvik cache".

Using an alternative filesystem such as F2FS on the eMMC (which is considerably faster than running software on the SD card) may help improve performance slightly. Over time you can expect further optimizations and improvements in various distributions that will help speed up the PinePhone.

=== SMS ===

==== The phone does not receive SMS ====

Sometimes incoming SMS messages are not being received, but outgoing ones, phone calls and data are working fine. One potential cause could be SMS messages that linger in the modem's queue (10 or more of them). This queue appears to be persistent across reboots and also re-imaging the OS.

On Mobian and Manjaro, the ModemManager does all the communications with the 3G modem including phone calls, cellular data, GPS and SMS. This may not be the case with other PinePhone OSes.

You can access the ModemManager using the mmcli command.

'''Mobian:'''

<pre>$ sudo mmcli -m 0 --messaging-list-sms
Found 10 SMS messages:
/org/freedesktop/ModemManager1/SMS/0 (received)</pre>

'''Manjaro:'''

<pre>$ sudo mmcli -m 3 --messaging-list-sms
/org/freedesktop/ModemManager1/SMS/77 (received)</pre>

For Mobian, delete all the messages like this:

<code>$ sudo mmcli -m 0 --messaging-delete-sms=1</code> (Repeat with 1 through 10 to delete all the messages)

For Manjaro, delete all the messages like this:

<code>$ sudo mmcli -m 3 --messaging-delete-sms=77</code> (Repeat with all listed messages)

Note that the "-m 0" or "-m 3" refers to modem 0 or 3 (the only one in a PinePhone). For more help on the messaging related actions available in mmcli you can check the help with <code>mmcli --help-messaging.</code> This article is also helpful in learning: https://electronproton.com/mmcli-command-examples/. For your particular configuration, you may need to try different "-m #" combinations, e.g., "-m 2" or "-m 4." "-m 0" is not always the default.

It should also be noted that recent releases of Mobian and postmarketOS now include a userspace daemon called [https://gitlab.com/mobian1/devices/eg25-manager eg25-manager], which helps manage the modem and ensure proper operation.

== Shipping ==
=== I did not receive an order confirmation ===
Check your "spam" folder. It was reported that some users did not receive an order confirmation. You will also still get a shipping notification when the device ships out, even if you didn't get an order confirmation email.

=== When does the phone ship? ===
For up-to-date information when the phone's shipping date is estimated, see the edits in this forum post: https://forum.pine64.org/showthread.php?tid=9942.

=== It is shipping day but I did not receive a shipping notification ===
For shipments with DHL the shipping notification is sent out as soon as the packet reached DHL's warehouse and scanned (it can take up to 24 hours after scanning after the shipment is added to DHL's database). For all other shipments (via Ascendia) the notification is sent out sometime after shipment.

=== When does my phone ship if I order now? ===
Orders made after Friday, 22nd May 2020 are shipped after the first bulk of pre-orders has been shipped. The exact date is not known yet due to various reasons, it may be a few weeks after the first bulk shipped. [https://forum.pine64.org/showthread.php?tid=9942 The forum] will be edited with updated information and you will receive a shipping notification when the device was shipped.

=== What about import taxes? ===
Import taxes have to be paid by the buyer depending on the jurisdiction of the country of the buyer. Please check with your local laws if there are import taxes to pay and if so how to do the tax filing.

== Accessories ==

=== Protection ===
==== Which screen protector should I use? ====

Protecting your screen is important, especially for devices like the PinePhone that doesn't have access to the newest glass technology.
The Braveheart and Community Editions of the PinePhone comes with a plastic film screen protector installed, and Pine64 sells a tempered glass screen protector [https://pine64.com/product/pinephone-tempered-glass-screen-protector/ in their store].

You can also buy a third-party screen protector, as the screen protectors for the iPhone 11 Pro Max/XS Max fit the PinePhone pretty well based on [https://forum.pine64.org/showthread.php?tid=8458&pid=65409#pid65409 this] forum post.

=== Batteries ===
==== I want a replacement battery, which one should I buy? ====

Replacement batteries for US customers are available in the store.

Currently the PinePhone battery is known to be compatible with replacement batteries for the Samsung J700. Specifically, models "EB-BJ700BBC" and "EB-BJ700BBE" are compatible with all PinePhone models, and "EB-BJ700CBE" is compatible with Community Editions [https://www.reddit.com/r/PINE64official/comments/kcof97/pinephone_replacement_battery_found_and_tested/gfrx4p2/?utm_source=reddit&utm_medium=web2x&context=3 after UBPorts] (due to plastic tabs on its bottom which only the newer phones [https://forum.pine64.org/showthread.php?tid=11901 have tolerance for]).

=== External hardware ===

==== Will Pine64 sell other add-ons made for the PinePhone? ====

Yes, currently there is a keyboard case [https://forum.pine64.org/showthread.php?tid=8537&pid=55396#pid55396 with similarities to the Psion 5] which includes an internal battery, and a [https://www.pine64.org/2020/05/15/may-update-pinetab-pre-orders-pinephone-qi-charging-more/ Qi wireless charging] add-on planned, both of which Pine64 intends to directly sell. There is the potential for future add-ons such as a game pad, however that is currently just an idea and not in any way planned.

==== Which 3rd party hardware can connect to my PinePhone? ====

See [[PinePhone Hardware Accessory Compatibility]].

[[Category:PinePhone]]

PinePhone FAQ

2021-05-02T23:28:32Z

Sethi: Replaced that Pineloader is a work-in-progress with the fact it's been archived.

A list of frequently asked question.

== Hardware ==

=== Revisions ===
==== What are Community Editions? ====
Community Editions of the PinePhone were versions of the PinePhone which came preinstalled with the operating system of a partner project and featured the logo of the project on the back panel. The Community Edition was intended to help partner projects developing these systems: "Community editions are meant to bring exposure to partner-projects operating systems and communities, as well as help finance ongoing development.", [https://www.pine64.org/2020/04/02/pinephone-ubports-community-edition-pre-orders-now-open/ source].

==== Is the Community Edition hardware the latest revision? ====
The Community Edition program (featuring the mainboard numbers 1.2 through 1.2b and branded back covers) which provided the branded Pinephones has since ended, and a Beta Edition has since been released. The only difference between each Community Edition is the inclusion of crucial bug fixes, with the last issue being fixed with the 1.2b motherboard shipping with the Manjaro CE PinePhones. The 1.2b motherboard is also currently used in the Beta Edition PinePhones, however the Beta Edition units do not ship with any back cover branding. There is currently no plans for further hardware revisions.

Aside from the back cover, the only other difference between each Community Edition is that starting with the postmarketOS PinePhone, a convergence package option was released that adds another gigabyte of ram to the phone and a 32GB eMMC instead of a 16GB eMMC. Convergence packages also included a dock for plugging in USB peripherals and connecting to a HDMI monitor, however you can purchase a generic USB-C dock to use with a 2GB PinePhone.

The predecessor to the Convergence Edition PinePhones was the Braveheart Edition intended for developers to bring up the platform, which had the version number 1.1. For more details about the topic see [[PinePhone#Hardware Revisions]].

==== Will there be other Community Editions? ====
Five Community Editions have been announced: [https://www.pine64.org/2020/04/02/pinephone-ubports-community-edition-pre-orders-now-open/ UBports], [https://www.pine64.org/2020/06/15/june-update-postmarketos-ce-pinephone-shipping-pine64-cluster/ postmarketOS], [https://www.pine64.org/2020/08/31/pinephone-manjaro-community-edition/ Manjaro], [https://www.pine64.org/2020/12/01/kde-community-edition-is-now-available/ KDE], and [https://www.pine64.org/2021/01/17/mobian-community-edition/ Mobian]. Since the release of the Mobian edition, the Beta Edition PinePhones have been released and the Community Edition Program has ended.

==== In simple terms, what are the differences between Braveheart and the new Community Edition? ====
The Braveheart PinePhone was the first public revision of the PinePhone which was intended solely for developers and Linux enthusiasts. The Ubports Community Edition was the next revision of the PinePhone with an updated mainboard based on feedback from the Braveheart Edition, see [[PinePhone#Hardware Revisions]]. All current revisions of the PinePhone continue to be intended for developers and enthusiasts, however Pine64 will be starting to offer partnered retail units of the PinePhone which will have a better warranty and technical support (keep in mind even then it is not intended for a broader audience at this time, as the software still needs work and the hardware does not hold up well to modern consumer standards).

==== Will there be a newer revision after the Community Editions? ====
Starting with the Ubports Community Edition the PinePhone has gotten CE and FCC certifications, repeating the certification process due to changes in the hardware design is very expensive, so the 1.2b motherboard is viewed as the final revision. The PinePhone (and parts for them) will be produced and sold for at least 5 years.

==== Will there be hardware differences between the Community Editions? ====

Besides the varied back covers, starting with the launch of the PostmarketOS CE there has been the release of a convergence package option for the PinePhone which includes more ram and storage, and a included dock for convenience. There has also been multiple hardware changes starting with the Ubports CE (mainboard 1.2) and ending with the Manjaro CE (mainboard revision 1.2b). There is currently no plans for future hardware changes for a few years.

==== How powerful is the PinePhone's hardware? ====

The PinePhone is about on par with a Raspberry Pi 3 in terms of CPU power, however going by GFLOPS it has half the GPU power. The Pi 3's Videocore IV does 24 GFLOPS, and the Mali 400 MP2 on the PinePhone only 10.8.

Despite this, using software rendering the PinePhone is capable of smoothly rendering at 1080p resolution or higher. However, with a fully GPU-accelerated mobile environment you should expect a more sluggish experience outputting to such resolutions. Unfortunately the Mali 400 MP2 (a 2008 arm mobile GPU) simply isn't intended to push 1080p resolution. With that said, the VPU of the PinePhone has been shown to handle smooth H.264 1440p30 video playback using Cedrus and gstreamer as documented [https://xnux.eu/log/#001 here]. Further, the PinePhone should be more than capable of a smooth phone experience when used in conjunction with well optimized software that makes use of its hardware features. It is also more than capable of running many light games (including 3D ones such as Supertuxkart), and retro gaming. Expect further speed improvements over time as the drivers are improved, and in the meanwhile you can look into slightly [[overclocking]] the device (at your own risk).

=== Sound ===

The default ringtone for Mobian Phosh can be found at /usr/share/sounds/freedesktop/stereo/phone-incoming-call.oga

=== Modem ===

==== The modem isn't working ====

In order to use the modem and WiFi/Bluetooth, you need to ensure the battery is inside the device and has a sufficient charge. Even when supplying the phone with enough power, the modem and WiFi chip will not work without a connected battery. Further, double check that you have no put the SD card into the sim card slot, or vice versa.

==== Does the PinePhone only wakeup from sleep for calls and texts? ====

Yes. Unless the PinePhone is configured to wakeup every few minutes from deep sleep in crust (At the cost of battery life. However, in the future there may be other solutions), then there is not any way to get any notifications for applications. The modem on the PinePhone will wake the device for incoming calls and texts however, and the real time clock is also capable of waking the device for alarms.

=== Battery ===

==== The battery is stuck inside the phone ====

The battery can be stuck in the phone if the screws of the frame are overtightened.

If your battery is stuck inside the PinePhone, grab a screw driver and completely unscrew all the screws of the midframe. Then pull out the battery (you may have to fully take off the midframe in some cases to get it out). And then rescrew the midframe, but only tighten the screws to the point where they are just barely tight to hold. This should allow you to remove the battery easily.

==== The battery is discharging while the phone is powered off (Braveheart Edition) ====

The issue is not present on the Community Edition. Due to a hardware bug, after poweroff, the phone still consumes 20–30mA which drains the battery in 3-4 days. A manual procedure to fix the hardware bug is described [https://xnux.eu/devices/pp-pmic-fix.jpg here].

==== The battery only charges to ~84% ====

Some pre-made OSes using megi's kernel limit the maximum amount of charge to roughly ~84% in the hope of prolonging the battery life, as repeatedly reaching the upper level of battery charge reduces the battery's lifetime (this is not a safety feature!). The same effect however also applies when repeatedly draining the battery to a low level - users are therefore advised to consider if that setting is reasonable depending on their usage. The setting can be overwritten via Sysfs, to let the battery fully charge (this can lower the replaceable's battery lifetime considerably depending on the charging behavior!):

{{warning|The following instructions are directed towards expert-level users and developers!}}

<code>echo 4350000 > /sys/class/power_supply/axp20x-battery/voltage_max_design</code>

=== Kill Switches ===
==== What are the kill switches doing? ====

{| 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.5mm 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.5mm audio jack, "off" switches the jack to hardware UART mode.
|}

=== Memory ===

==== What's the speed difference between the eMMC and SD cards? ====
Maximum transfer speed of the eMMC is around 85 MB/s, while SD cards are limited to approximately 23 MB/s (even with faster cards).

=== GPS ===

==== GPS doesn't work ====

Like almost all smartphones, the PinePhone GPS antenna is small and can only get a first fix unassisted if the GPS signal is very strong. To make first fix faster and more reliable, phones download assistance data either from the phone network or from the internet. The GPS in the PinePhone modem supports the internet based assistance method, as detailed in the modem documentation, but this isn't yet supported out of the box by any of the distros. There is a [https://gist.github.com/alastair-dm/263209b54d01209be28828e555fa6628 proof of concept script] to show that it can work.

Until AGPS support makes its way into the distros you'll have to make some manual changes - see for example [https://wiki.mobian-project.org/doku.php?id=location Mobian wiki]

== Software ==

=== Installation ===

==== How can I install an operating system on the SD card / eMMC? ====

See [[PinePhone Installation Instructions]].

=== Updating ===

Read the [[PinePhone Updating Instructions]].

=== Booting ===

==== What's the boot order for SD cards and eMMC? ====

The PinePhone will automatically boot from microSD if a bootable card is inserted. If no (bootable) microSD is found, it will boot from eMMC.

==== How can I select different OSes at boot? ====

There was a project by Danct12 which allows the user to select different OSes at boot, but the repository has since been archived: https://github.com/dreemurrs-embedded/Pineloader.

==== I turned on my Manjaro CE PinePhone. The red LED and screen backlight are briefly lit, then both are not and it will not boot. ====

This can be the result of at least one situation:

# The eMMC installation became corrupt or otherwise unbootable
# An SD card is present but not bootable (consider [[PinePhone#Detailed usage instructions]])

If there is an installation of Manjaro on both the eMMC & an SD card, the SD card will always boot first on the device. Try taking the SD card out and booting the installation that is on the eMMC. If the problem persists, it is likely there is an issue with both installations and you will need to reinstall your distribution. You may also want to check with your distribution's maintainers if boot issues are a common problem in a recent update.

==== I did not install an update in Ubuntu Touch and I'm stuck on the Pine64 logo after rebooting. ====

# Use a USB A-C cable to plug your phone into your PC
# Hold the PinePhone's power button for 4 seconds or more to power it off.
# Wait 5 seconds
# Hold the Volume Up and Power buttons on the PinePhone to boot into recovery. You should see the LED light red, then yellow, then green. The "Installing update" screen will appear, but a progress bar to indicate update progress will not. Ignore the "Installing update" part.
# Your PC may automatically mount the PinePhone's partitions. If it does, Safely Remove or Eject all of them.
# Open a terminal on your PC. Type <code>telnet 172.16.42.1</code>
# You should receive the text 'Welcome to Rescue SD Shell!'
# In the new Rescue SD shell, type <code>umount /dev/mmcblk2p10; e2fsck -fy /dev/mmcblk2p10 && sync</code>
# Once this command pipeline finishes, type <code>sync && reboot -f</code>

Your PinePhone should reboot into Ubuntu Touch. Now head to Settings -> Updates and install the new update!

If these steps did not solve your issue, please create a new thread here on the Pine64 forums, note what the problem looks like, then say that you've tried these steps already.

This is caused by corruption on the userdata partition. Normally this should be fixed by 'e2fsck' in the initramfs, however an error in image creation means that that version of e2fsck is unable to correct corruption. This has been fixed in all new PinePhone updates, so if you update from the factory image to any other image available to the PinePhone now, you will not experience this issue any longer.

==== I turned on my PinePhone running Ubuntu Touch. The red LED is lit and it will not boot. ====
# Hold the power button until the light turns off
# Hold the power button until the light turns on

You may need to repeat these steps more than once.

This is caused by u-boot apparently trying to use the eMMC before it is ready. We are not entirely sure why this occurs yet.

==== Can I install a different OS on my Community Edition? ====

Yes! While all of the Community Edition Pinephones come with an OS preinstalled, you are free to use any OS on the integrated storage (the eMMC) or an SD card, see [[PinePhone Installation Instructions]] and [[PinePhone Software Releases]] on how to install them.

=== Other ===

==== How can I enable SSH? ====

In Ubuntu Touch you can run "sudo start ssh" to get a one-time start, or edit /etc/init/ssh.override and remove the manual line to make it auto-start.

In other distributions you may have to install SSH through its package manager and then proceed to use its init system to enable it. For Manjaro, Arch, and Mobian you can use "systemctl enable" and "systemctl start" command to enable and start ssh.

==== What works, what doesn't? ====

For Ubuntu Touch see https://gitlab.com/ubports/community-ports/pinephone#what-works-what-doesnt.

Other distributions will have different levels of functionality. Please refer to the release page of your chosen distribution for further information.

==== I can't connect to a 2.4Ghz Wi-Fi network in Ubuntu Touch. ====

Reboot your device by holding the power button until the "Power" dialog appears, then pressing "Restart".

If that does not fix the issue, note that all the following conditions must be met to use WiFi on the PinePhone:

# The plastic tab between the battery and the device's battery contacts has been removed
# The battery is installed
# The WiFi killswitch, #2, on the rear of the device is switched "ON"

Wi-Fi in the PinePhone only seems stable after a warm reboot like this.

==== What's the status of Android for the PinePhone? ====

Currently, there isn't any major push to get Android running well on the PinePhone. The developer Icenowy did get a Android image to run and partly work, it was however slow and buggy, with major functions not working. A solution for running some of your android apps may be found in Anbox as of now. Anbox is currently not included in Ubuntu Touch. In other distributions your millage may vary on what applications will run and how well.

==== Why are my apps loading slower than on my Android phone? ====

Android has multiple techniques in place to speed up launching applications after the first launch, such as the "Dalvik cache".

Using a alternative filesystem such as F2FS on the eMMC (which is considerably faster than running software on the SD card) may help improve performance slightly. Over time you can expect further optimizations and improvements in various distributions that will help speed up the PinePhone.

=== SMS ===

==== The phone does not receive SMS ====

Sometimes incoming SMS messages are not being received, but outgoing ones, phone calls and data are working fine. One potential cause could be SMS messages that linger in the modem's queue (10 or more of them). This queue appears to be persistent across reboots and also re-imaging the OS.

On Mobian and Manjaro, the ModemManager does all of the communications with the 3G modem including phone calls, cellular data, GPS and SMS. This may not be the case with other PinePhone OSes.

You can access the ModemManager using the mmcli command.

'''Mobian:'''

<pre>$ sudo mmcli -m 0 --messaging-list-sms
Found 10 SMS messages:
/org/freedesktop/ModemManager1/SMS/0 (received)</pre>

'''Manjaro:'''

<pre>$ sudo mmcli -m 3 --messaging-list-sms
/org/freedesktop/ModemManager1/SMS/77 (received)</pre>

For Mobian, delete all of the messages like this:

<code>$ sudo mmcli -m 0 --messaging-delete-sms=1</code> (Repeat with 1 through 10 to delete all of the messages)

For Manjaro, delete all of the messages like this:

<code>$ sudo mmcli -m 3 --messaging-delete-sms=77</code> (Repeat with all listed messages)

Note that the "-m 0" or "-m 3" refers to modem 0 or 3 (the only one in a PinePhone). For more help on the messaging related actions available in mmcli you can check the help with <code>mmcli --help-messaging.</code> This article is also helpful in learning: https://electronproton.com/mmcli-command-examples/. For your particular configuration, you may need to try different "-m #" combinations, e.g., "-m 2" or "-m 4." "-m 0" is not always the default.

It should also be noted that recent releases of Mobian and postmarketOS now include a userspace daemon called [https://gitlab.com/mobian1/devices/eg25-manager eg25-manager], which helps manage the modem and ensure proper operation.

== Shipping ==
=== I did not receive an order confirmation ===
Check your "spam" folder. It was reported that some users did not receive an order confirmation. You will also still get a shipping notification when the device ships out, even if you didn't get a order confirmation email.

=== When does the phone ship? ===
For up-to-date information when the phone's shipping date is estimated, see the edits in this forum post: https://forum.pine64.org/showthread.php?tid=9942.

=== It is shipping day but I did not receive a shipping notification ===
For shipments with DHL the shipping notification is sent out as soon as the packet reached DHL's warehouse and scanned (it can take up to 24 hours after scanning after the shipment is added to DHL's database). For all other shipments (via Ascendia) the notification is sent out sometime after shipment.

=== When does my phone ship if I order now? ===
Orders made after Friday, 22nd May 2020 are shipped after the first bulk of pre-orders has been shipped. The exact date is not known yet due to various reasons, it may be a few weeks after the first bulk shipped. [https://forum.pine64.org/showthread.php?tid=9942 The forum] will be edited with updated information and you will receive a shipping notification when the device was shipped.

=== What about import taxes? ===
Import taxes have to be payed by the buyer depending on the jurisdiction of the country of the buyer. Please check with your local laws if there are import taxes to pay and if so how to do the tax filing.

== Accessories ==

=== Protection ===
==== Which screen protector should i use? ====

Protecting your screen is important, especially for devices like the PinePhone that doesn't have access to the newest glass technology.
The Braveheart and Community Editions of the PinePhone comes with a plastic film screen protector installed, and Pine64 sells a tempered glass screen protector [https://pine64.com/product/pinephone-tempered-glass-screen-protector/ in their store].

You can also buy a third party screen protector, as the screen protectors for the iPhone 11 Pro Max/XS Max fit the PinePhone pretty well based on [https://forum.pine64.org/showthread.php?tid=8458&pid=65409#pid65409 this] forum post.

=== Batteries ===
==== I want a replacement battery, which one should I buy? ====

Replacement batteries for US customers are available in the store.

Currently the PinePhone battery is known to be compatible with replacement batteries for the Samsung J700. Specifically, models "EB-BJ700BBC" and "EB-BJ700BBE" are compatible with all PinePhone models, and "EB-BJ700CBE" is compatible with Community Editions [https://www.reddit.com/r/PINE64official/comments/kcof97/pinephone_replacement_battery_found_and_tested/gfrx4p2/?utm_source=reddit&utm_medium=web2x&context=3 after UBPorts] (due to plastic tabs on its bottom which only the newer phones [https://forum.pine64.org/showthread.php?tid=11901 have tolerance for]).

=== External hardware ===

==== Will Pine64 sell other addons made for the PinePhone? ====

Yes, currently there is a keyboard case [https://forum.pine64.org/showthread.php?tid=8537&pid=55396#pid55396 with similarities to the Psion 5] which includes an internal battery, and a [https://www.pine64.org/2020/05/15/may-update-pinetab-pre-orders-pinephone-qi-charging-more/ Qi wireless charging] add-on planned, both of which Pine64 intends to directly sell. There is the potential for future add-ons such as a game pad, however that is currently just an idea and not in any way planned.

==== Which 3rd party hardware can connect to my PinePhone? ====

See [[PinePhone Hardware Accessory Compatibility]].

[[Category:PinePhone]]