PINE64 - User contributions [en]

User talk:Fxc

2021-08-22T12:34:35Z

MikeBanon: /* Re: Your edits in PinePhone */ new section

== Carrier Support ==
Can you please explain why you keep removing my additions to [[PinePhone_Carrier_Support]] -- [[User:Mikehenson|Mike]] 02:22:09 29 April 2021 (UTC)
: You keep adding your provider in the wrong section. You want to add it in the section "Tested and working" but you keep adding it to the section "Does not work / special notes". Regards --[[User:Fxc|Fxc]] ([[User talk:Fxc|talk]]) 12:13, 29 April 2021 (UTC)
:: Thank you! I added it to [[PinePhone_Carrier_Support#North_America]] -- [[User:Mikehenson|Mike]] 17:09:09 29 April 2021 (UTC)

== Discussion on what to do with the Rock64 page ==

Hi, I'm asking you about this since you seem to be one of the more active contributors of the wiki.

I recently noticed that there are two ROCK64 pages, one is [[ROCK64]], the other is [[Rock64]]. They seem to duplicate a lot of information, and the latter appears to contain a large list of links already covered in the software releases page.

What should be done about this? Should we delete [[Rock64]] and make it a redirect? --[[User:CounterPillow|CounterPillow]] ([[User talk:CounterPillow|talk]]) 19:20, 13 May 2021 (UTC)

:For now I've decided to make it a redirect, upon seeing that the user who created it also created other pages which were just carbon copies of the respective actual pages at the time. Maybe some spam thing? --[[User:CounterPillow|CounterPillow]] ([[User talk:CounterPillow|talk]]) 06:24, 14 May 2021 (UTC)

:: Yup, I would have recommended a redirect too. The SBC articles and especially their naming is quite chaotic so (radically) cleaning up the wiki and finding a better structure between different articles is something which has to be done sooner or later anyway. --[[User:Fxc|Fxc]] ([[User talk:Fxc|talk]]) 12:38, 14 May 2021 (UTC)

== Re: Your edits in PinePhone ==

Good day, Fxc! Thank you very much for your help in moving my recent edits to their more suitable places: this stuff took me plenty of time to figure out & test, and hopefully our work could be valuable to the fellow PinePhone users.

Unfortunately, I noticed that "IMEI check and change" has been reverted for the reason "Illegal wiki contents removed". Please tell, "illegal" - in what country? I.e. PINE64 is a Hong Kong company, while a Pine64 wiki website is hosted in Slovakia, - and I can't any info that changing IMEI in either Hong Kong or Slovakia is illegal, or at least posting the "how-to" information about this. And what isn't forbidden - is allowed. For the majority of countries ''(not taking some totalitarian ones into account)'', changing IMEI is as legal as changing the MAC address which has been allowed to stay.

Since a "pinephone change imei" seems to be a popular Google request (it's even more popular than "pinephone change os"), I'd like to preserve this information for the public usage. If, to be able to do that, I need to re-word/extend the warning about the possible legal issues (something like "please check the laws of your country before doing that") - please let me know.

At the same time I understand this advanced information is probably not suitable for the main PinePhone page. Please tell what's the more appropriate place in your opinion - [[PineModems]], [[PinePhone_Software_Tweaks]] or [[PinePhone_FAQ#Modem]] ?

PinePhone

2021-08-20T17:57:50Z

MikeBanon: /* Autostart control */ improve the formatting

[[File:PinePhone Beta Edition.png|500px|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 Linux experience.

Bear in mind that the software for Linux on phones 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 [https://www.pine64.org/philosophy/ PINE64 philosophy]), and currently that support resources are sparse - the best way to get support quickly is to ask in the community chat! Please only contact PINE64 directly if questions couldn't be solved via the community chat or this wiki.

== First time installation ==

{{Hint|Do not insert an empty micro SIM adapter into the phone, as it will get stuck on the contact pins.}}

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 until this is removed and the modem, WiFi and Bluetooth will not work until the battery is connected.

The PinePhone's SIM slot only accepts a micro SIM, please do not insert a nano SIM without an adapter. An adapter from a nano to a micro SIM might be included under tape in the camera notch of the phone's packaging. The SIM card has to be placed in the lower slot, while the microSD has to be placed in the upper slot. Notice: Do not insert an empty micro SIM adapter into the phone, as it will get stuck on the contact pins.

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
# Remove the battery (if the battery is stuck in the device please check [[PinePhone_FAQ#The_battery_is_stuck_inside_the_phone|this]] paragraph for a fix)
# Peel off the clear plastic sticker below it, which isolates the charging contacts
# Reinsert the battery

<gallery mode="nolines" widths="400px" heights="400px">
Image:Pinephone_warning.png|A protection foil isolates the battery for the shipping.
Image:Pinephone_backside.png|The microSD belongs in the upper slot, the micro SIM in the lower slot.
</gallery>

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

== 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|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 killswitch 6 is deactivated)
* '''Communication:'''
** '''[[#Modem|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
* '''Killswitches:''' Modem, WiFi & Bluetooth, Microphone, Cameras
* '''[[#Battery|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 ==

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

* [[Project Anakin]]
* [[Project Don't be evil|"Project Don't Be Evil"]] – development kit (devkit)
* [[PinePhone v1.0 - Dev|PinePhone v1.0]] – developer batch
* [[PinePhone v1.1 - Braveheart|PinePhone v1.1]] – Braveheart
* [[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 ==

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

=== USB-C connector ===

The USB-C can be used to power the device, and offers USB2 host and OTG possibilities, 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, 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 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].

=== Community-built accessories ===
* [https://www.thingiverse.com/thing:4654013 PinePhone Development Stand at Thingverse]
* [https://www.thingiverse.com/thing:4658870 PinePhone Hard Case by _The3DmaN_ at Thingverse]
* [https://www.thingiverse.com/thing:4651177 PinePhone Hard Case by blitzaxt at Thingverse]

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

== Killswitch configuration ==

[[File:PinePhone Kill Interruptors de Maquinari del PinePhone 4529.jpg|320px|thumb|right|Detail of DIP switch]]

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 ==
{{Hint|The EG25-G modem and the RTL8723CS WiFi and Bluetooth combo do not work without battery power, even when enough power is supplied to the PinePhone via the USB Type-C port.}}

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

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.

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.

== Connectivity ==

=== Autostart control ===

If your PinePhone's Linux distribution uses a NetworkManager for connectivity, it memorizes the last used "Enable/Disable" settings in a <code>/var/lib/NetworkManager/NetworkManager.state</code> file:

<pre>
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
</pre>

- and it follows them during the next boot. For security reasons, you may want to set up your PinePhone so that WiFi and Modem connections are always disabled on each boot - regardless of the last used settings! - and these connections could be manually enabled by you in Settings after boot when there's a need. To set up this, add the following lines to the NetworkManager init script just before the launch of a NetworkManager itself:

<pre>
sed "s/^WirelessEnabled=true/WirelessEnabled=false/" -i /var/lib/NetworkManager/NetworkManager.state && sync
sed "s/^WWANEnabled=true/WWANEnabled=false/" -i /var/lib/NetworkManager/NetworkManager.state && sync
</pre>

In example, if your PinePhone's Linux distro ''(i.e. postmarketOS)'' uses OpenRC as an init manager, open <code>/etc/init.d/networkmanager</code> init script and add the following section after <code>depend()</code> section:

<pre>
start_pre() {
sed "s/^WirelessEnabled=true/WirelessEnabled=false/" -i /var/lib/NetworkManager/NetworkManager.state && sync
sed "s/^WWANEnabled=true/WWANEnabled=false/" -i /var/lib/NetworkManager/NetworkManager.state && sync
}
</pre>

=== WiFi and Bluetooth ===

The PinePhone uses [https://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf Realtek RTL8723CS] for its WiFi and Bluetooth connectivity. Unfortunately, just like the other Realteks ''([https://en.wikipedia.org/wiki/Comparison_of_open-source_wireless_drivers see more info])'' - this RTL8723CS chip requires a proprietary closed-source binary blob firmware, unlike a famous Atheros ath9k family which sadly didn't find a way into the PinePhone. For those who have the capability to reverse-engineer the Realtek firmware of this chip to create the opensource replacement, resources like [https://libreplanet.org/wiki/Group:Hardware/research/e-readers/Kobo/Aura_H2O_Edition_2#Firmwares this] and [https://8051enthusiast.github.io/2021/07/05/002-wifi_fun.html this] could be a great starting point for your further research.

If your PinePhone's Linux distribution uses a NetworkManager for connectivity, for the anonymity purposes it is possible to randomize the WiFi MAC address for each re-connection. Open the <code>/etc/NetworkManager/NetworkManager.conf</code> file with a text editor ''(you may need the sudo rights)'' - and under the existing configuration like:

<pre>
[main]
dhcp=internal
</pre>

add the following lines:

<pre>
[device]
wifi.scan-rand-mac-address=yes

[connection]
wifi.cloned-mac-address=random
</pre>

'''TODO:''' It seems a Bluetooth also has a MAC address. How to spoof it as well?

=== Modem ===

The PinePhone uses Quectel EG25-G as modem. AT commands are used to communicate with the modem. To send them under Linux, you can use either <code>minicom</code> - <code>sudo minicom -D /dev/EG25.AT</code> - or the often-preinstalled <code>atinout</code> utility:

<pre>
sudo su
atinout - /dev/EG25.AT out.txt << EOF
> AT+... command here
> EOF
cat ./out.txt # to see the result of a command execution
</pre>

==== AT commands ====

A list of documented AT commands can be found in the [[File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_AT_Commands_Manual_V2.0.pdf]] from Quectel. In example, to '''show the current IMEI number''':

<pre>
sudo su
atinout - /dev/EG25.AT out.txt << EOF
> AT+EGMR=0,7
> EOF
cat ./out.txt # to see the IMEI
</pre>

Also, there are certain undocumented AT commands. In example, to '''change the PinePhone IMEI number''' to a valid newIMEI one:

<pre>
sudo su
atinout - /dev/EG25.AT out.txt << EOF
> AT+EGMR=1,7,"newIMEI"
> EOF
cat ./out.txt # should output OK
</pre>

Then use <code>AT+EGMR=0,7</code> to see if IMEI has been changed successfully, - and, to see that IMEI change is persistent: shutdown a phone, remove a battery, press a power button to discharge the motherboard, put a battery back, turn on the phone and run <code>AT+EGMR=0,7</code> again.

Such a command has to be approached with caution: although in the majority of countries changing IMEI '''by itself''' is not illegal ''(or at least not prosecuted unless you are doing something malicious using this capability)'', still a cellphone service provider may ban your IMEI and/or phone number if it sees two cellphones with the same IMEI being used simultaneously. So it should be done with common sense: in example, if you don't want your cellphone service provider ''(or the governmental/commercial entities it could be supplying with information)'' to know that you have replaced your old phone, you could change the IMEI of your PinePhone to be identical to your old phone's, just avoid using them simultaneously or at least don't connect them to the same provider.

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

==== VoLTE ====

The PinePhone's modem supports VoLTE and comes with a few VoLTE profiles preloaded. Most OSes 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 OSes.

==== Firmware update ====

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

You can check the modem firmware version with a following AT command:

<pre>
sudo su
atinout - /dev/EG25.AT out.txt << EOF
> AT+QGMR
> EOF
cat ./out.txt # should output OK
</pre>

If it is 01.001.01.001 ''(EG25GGBR07A08M2G_01.001.01.001)'', then it's recommended to update it to 01.002.01.002 ''(EG25GGBR07A08M2G_01.002.01.002)'' - because "002" has a better performance than "001", and according to Biktorgj it is more stable than the latest "003". However,

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

<pre>git clone https://github.com/Biktorgj/quectel_eg25_recovery</pre>

After cloning the directory, open it with cd:

<pre>cd quectel_eg25_recovery</pre>

Then run qfirehose, which starts the flashing process:

<pre>sudo ./qfirehose -f ./</pre>

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 is controlled via a separate set of AT commands. The AGPS 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. While the hardware supports AGPS data upload, it isn't yet implemented in current distributions. There is a [https://gist.github.com/alastair-dm/263209b54d01209be28828e555fa6628 proof of concept script] which can be made to work, but support needs to be added to ModemManager, oFono etc. before it will be easy to use.

Basic testing of GNSS reception can be done by using the AT command interface (/dev/ttyUSB2) from a terminal progam like minicom and the data output interface (/dev/ttyUSB1) to feed NMEA data into gpsmon or some other progam 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

==== Voice mail ====

Some phone operating systems may not have support for accessing your voicemail by holding down the 1 key. If you are in Canada and using rogers or a rogers associated carrier (such as ''Chatr''), you can access your voice mail by calling an external number, see: https://www.howardforums.com/showthread.php/913346-Rogers-GSM-Voicemail-Retrieval-Numbers

In America, AT&T also has support for accessing your voicemail via an external phone number: https://www.att.com/support/article/wireless/KM1009101/

In Canada, Rogers voicemail can be called by dialing *98

== 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 Phillip’s 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 Phillip’s 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.

Download the latest ANX7688 firmware image on the phone:

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

Execute 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 dimensions: 12x6x2 mm. Compatible with Xiaomi Mi2 / Mi3 / Mi4, Lenovo A536 and others, see [https://forum.pine64.org/showthread.php?tid=12046&pid=85698#pid85698 here]
* Loudspeaker dimensions: 15x11x3 mm. Compatible with Nokia N91, Lenovo A536 and others, see [https://forum.pine64.org/showthread.php?tid=12046&pid=85698#pid85698 here]
* Proximity sensor rubber isolator

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

== Developer works ==

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

2021-08-20T17:55:46Z

MikeBanon: /* Connectivity */ add the Autostart control section

[[File:PinePhone Beta Edition.png|500px|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 Linux experience.

Bear in mind that the software for Linux on phones 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 [https://www.pine64.org/philosophy/ PINE64 philosophy]), and currently that support resources are sparse - the best way to get support quickly is to ask in the community chat! Please only contact PINE64 directly if questions couldn't be solved via the community chat or this wiki.

== First time installation ==

{{Hint|Do not insert an empty micro SIM adapter into the phone, as it will get stuck on the contact pins.}}

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 until this is removed and the modem, WiFi and Bluetooth will not work until the battery is connected.

The PinePhone's SIM slot only accepts a micro SIM, please do not insert a nano SIM without an adapter. An adapter from a nano to a micro SIM might be included under tape in the camera notch of the phone's packaging. The SIM card has to be placed in the lower slot, while the microSD has to be placed in the upper slot. Notice: Do not insert an empty micro SIM adapter into the phone, as it will get stuck on the contact pins.

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
# Remove the battery (if the battery is stuck in the device please check [[PinePhone_FAQ#The_battery_is_stuck_inside_the_phone|this]] paragraph for a fix)
# Peel off the clear plastic sticker below it, which isolates the charging contacts
# Reinsert the battery

<gallery mode="nolines" widths="400px" heights="400px">
Image:Pinephone_warning.png|A protection foil isolates the battery for the shipping.
Image:Pinephone_backside.png|The microSD belongs in the upper slot, the micro SIM in the lower slot.
</gallery>

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

== 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|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 killswitch 6 is deactivated)
* '''Communication:'''
** '''[[#Modem|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
* '''Killswitches:''' Modem, WiFi & Bluetooth, Microphone, Cameras
* '''[[#Battery|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 ==

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

* [[Project Anakin]]
* [[Project Don't be evil|"Project Don't Be Evil"]] – development kit (devkit)
* [[PinePhone v1.0 - Dev|PinePhone v1.0]] – developer batch
* [[PinePhone v1.1 - Braveheart|PinePhone v1.1]] – Braveheart
* [[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 ==

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

=== USB-C connector ===

The USB-C can be used to power the device, and offers USB2 host and OTG possibilities, 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, 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 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].

=== Community-built accessories ===
* [https://www.thingiverse.com/thing:4654013 PinePhone Development Stand at Thingverse]
* [https://www.thingiverse.com/thing:4658870 PinePhone Hard Case by _The3DmaN_ at Thingverse]
* [https://www.thingiverse.com/thing:4651177 PinePhone Hard Case by blitzaxt at Thingverse]

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

== Killswitch configuration ==

[[File:PinePhone Kill Interruptors de Maquinari del PinePhone 4529.jpg|320px|thumb|right|Detail of DIP switch]]

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 ==
{{Hint|The EG25-G modem and the RTL8723CS WiFi and Bluetooth combo do not work without battery power, even when enough power is supplied to the PinePhone via the USB Type-C port.}}

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

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.

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.

== Connectivity ==

=== Autostart control ===

If your PinePhone's Linux distribution uses a NetworkManager for connectivity, it memorizes the last used "Enable/Disable" settings in a <code>/var/lib/NetworkManager/NetworkManager.state</code> file:

<pre>
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
</pre>

- and it follows them during the next boot. For security reasons, you may want to set up your PinePhone so that WiFi and Modem connections are always disabled on each boot - regardless of the last used settings! - and these connections could be manually enabled by you in Settings after boot when there's a need. To set up this, add the following lines to the NetworkManager init script just before the launch of a NetworkManager itself:

<pre>
sed "s/^WirelessEnabled=true/WirelessEnabled=false/" -i /var/lib/NetworkManager/NetworkManager.state && sync
sed "s/^WWANEnabled=true/WWANEnabled=false/" -i /var/lib/NetworkManager/NetworkManager.state && sync
</pre>

In example, if your PinePhone's Linux distro uses OpenRC as an init manager ''(i.e. postmarketOS)'', open /etc/init.d/networkmanager init script and add the following section after <code>depend()</code> section:

<pre>
start_pre() {
sed "s/^WirelessEnabled=true/WirelessEnabled=false/" -i /var/lib/NetworkManager/NetworkManager.state && sync
sed "s/^WWANEnabled=true/WWANEnabled=false/" -i /var/lib/NetworkManager/NetworkManager.state && sync
}
</pre>

=== WiFi and Bluetooth ===

The PinePhone uses [https://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf Realtek RTL8723CS] for its WiFi and Bluetooth connectivity. Unfortunately, just like the other Realteks ''([https://en.wikipedia.org/wiki/Comparison_of_open-source_wireless_drivers see more info])'' - this RTL8723CS chip requires a proprietary closed-source binary blob firmware, unlike a famous Atheros ath9k family which sadly didn't find a way into the PinePhone. For those who have the capability to reverse-engineer the Realtek firmware of this chip to create the opensource replacement, resources like [https://libreplanet.org/wiki/Group:Hardware/research/e-readers/Kobo/Aura_H2O_Edition_2#Firmwares this] and [https://8051enthusiast.github.io/2021/07/05/002-wifi_fun.html this] could be a great starting point for your further research.

If your PinePhone's Linux distribution uses a NetworkManager for connectivity, for the anonymity purposes it is possible to randomize the WiFi MAC address for each re-connection. Open the <code>/etc/NetworkManager/NetworkManager.conf</code> file with a text editor ''(you may need the sudo rights)'' - and under the existing configuration like:

<pre>
[main]
dhcp=internal
</pre>

add the following lines:

<pre>
[device]
wifi.scan-rand-mac-address=yes

[connection]
wifi.cloned-mac-address=random
</pre>

'''TODO:''' It seems a Bluetooth also has a MAC address. How to spoof it as well?

=== Modem ===

The PinePhone uses Quectel EG25-G as modem. AT commands are used to communicate with the modem. To send them under Linux, you can use either <code>minicom</code> - <code>sudo minicom -D /dev/EG25.AT</code> - or the often-preinstalled <code>atinout</code> utility:

<pre>
sudo su
atinout - /dev/EG25.AT out.txt << EOF
> AT+... command here
> EOF
cat ./out.txt # to see the result of a command execution
</pre>

==== AT commands ====

A list of documented AT commands can be found in the [[File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_AT_Commands_Manual_V2.0.pdf]] from Quectel. In example, to '''show the current IMEI number''':

<pre>
sudo su
atinout - /dev/EG25.AT out.txt << EOF
> AT+EGMR=0,7
> EOF
cat ./out.txt # to see the IMEI
</pre>

Also, there are certain undocumented AT commands. In example, to '''change the PinePhone IMEI number''' to a valid newIMEI one:

<pre>
sudo su
atinout - /dev/EG25.AT out.txt << EOF
> AT+EGMR=1,7,"newIMEI"
> EOF
cat ./out.txt # should output OK
</pre>

Then use <code>AT+EGMR=0,7</code> to see if IMEI has been changed successfully, - and, to see that IMEI change is persistent: shutdown a phone, remove a battery, press a power button to discharge the motherboard, put a battery back, turn on the phone and run <code>AT+EGMR=0,7</code> again.

Such a command has to be approached with caution: although in the majority of countries changing IMEI '''by itself''' is not illegal ''(or at least not prosecuted unless you are doing something malicious using this capability)'', still a cellphone service provider may ban your IMEI and/or phone number if it sees two cellphones with the same IMEI being used simultaneously. So it should be done with common sense: in example, if you don't want your cellphone service provider ''(or the governmental/commercial entities it could be supplying with information)'' to know that you have replaced your old phone, you could change the IMEI of your PinePhone to be identical to your old phone's, just avoid using them simultaneously or at least don't connect them to the same provider.

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

==== VoLTE ====

The PinePhone's modem supports VoLTE and comes with a few VoLTE profiles preloaded. Most OSes 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 OSes.

==== Firmware update ====

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

You can check the modem firmware version with a following AT command:

<pre>
sudo su
atinout - /dev/EG25.AT out.txt << EOF
> AT+QGMR
> EOF
cat ./out.txt # should output OK
</pre>

If it is 01.001.01.001 ''(EG25GGBR07A08M2G_01.001.01.001)'', then it's recommended to update it to 01.002.01.002 ''(EG25GGBR07A08M2G_01.002.01.002)'' - because "002" has a better performance than "001", and according to Biktorgj it is more stable than the latest "003". However,

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

<pre>git clone https://github.com/Biktorgj/quectel_eg25_recovery</pre>

After cloning the directory, open it with cd:

<pre>cd quectel_eg25_recovery</pre>

Then run qfirehose, which starts the flashing process:

<pre>sudo ./qfirehose -f ./</pre>

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 is controlled via a separate set of AT commands. The AGPS 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. While the hardware supports AGPS data upload, it isn't yet implemented in current distributions. There is a [https://gist.github.com/alastair-dm/263209b54d01209be28828e555fa6628 proof of concept script] which can be made to work, but support needs to be added to ModemManager, oFono etc. before it will be easy to use.

Basic testing of GNSS reception can be done by using the AT command interface (/dev/ttyUSB2) from a terminal progam like minicom and the data output interface (/dev/ttyUSB1) to feed NMEA data into gpsmon or some other progam 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

==== Voice mail ====

Some phone operating systems may not have support for accessing your voicemail by holding down the 1 key. If you are in Canada and using rogers or a rogers associated carrier (such as ''Chatr''), you can access your voice mail by calling an external number, see: https://www.howardforums.com/showthread.php/913346-Rogers-GSM-Voicemail-Retrieval-Numbers

In America, AT&T also has support for accessing your voicemail via an external phone number: https://www.att.com/support/article/wireless/KM1009101/

In Canada, Rogers voicemail can be called by dialing *98

== 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 Phillip’s 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 Phillip’s 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.

Download the latest ANX7688 firmware image on the phone:

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

Execute 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 dimensions: 12x6x2 mm. Compatible with Xiaomi Mi2 / Mi3 / Mi4, Lenovo A536 and others, see [https://forum.pine64.org/showthread.php?tid=12046&pid=85698#pid85698 here]
* Loudspeaker dimensions: 15x11x3 mm. Compatible with Nokia N91, Lenovo A536 and others, see [https://forum.pine64.org/showthread.php?tid=12046&pid=85698#pid85698 here]
* Proximity sensor rubber isolator

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

== Developer works ==

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

2021-08-20T17:34:29Z

MikeBanon: /* Connectivity */ Share how to randomize the MAC address

[[File:PinePhone Beta Edition.png|500px|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 Linux experience.

Bear in mind that the software for Linux on phones 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 [https://www.pine64.org/philosophy/ PINE64 philosophy]), and currently that support resources are sparse - the best way to get support quickly is to ask in the community chat! Please only contact PINE64 directly if questions couldn't be solved via the community chat or this wiki.

== First time installation ==

{{Hint|Do not insert an empty micro SIM adapter into the phone, as it will get stuck on the contact pins.}}

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 until this is removed and the modem, WiFi and Bluetooth will not work until the battery is connected.

The PinePhone's SIM slot only accepts a micro SIM, please do not insert a nano SIM without an adapter. An adapter from a nano to a micro SIM might be included under tape in the camera notch of the phone's packaging. The SIM card has to be placed in the lower slot, while the microSD has to be placed in the upper slot. Notice: Do not insert an empty micro SIM adapter into the phone, as it will get stuck on the contact pins.

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
# Remove the battery (if the battery is stuck in the device please check [[PinePhone_FAQ#The_battery_is_stuck_inside_the_phone|this]] paragraph for a fix)
# Peel off the clear plastic sticker below it, which isolates the charging contacts
# Reinsert the battery

<gallery mode="nolines" widths="400px" heights="400px">
Image:Pinephone_warning.png|A protection foil isolates the battery for the shipping.
Image:Pinephone_backside.png|The microSD belongs in the upper slot, the micro SIM in the lower slot.
</gallery>

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

== 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|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 killswitch 6 is deactivated)
* '''Communication:'''
** '''[[#Modem|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
* '''Killswitches:''' Modem, WiFi & Bluetooth, Microphone, Cameras
* '''[[#Battery|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 ==

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

* [[Project Anakin]]
* [[Project Don't be evil|"Project Don't Be Evil"]] – development kit (devkit)
* [[PinePhone v1.0 - Dev|PinePhone v1.0]] – developer batch
* [[PinePhone v1.1 - Braveheart|PinePhone v1.1]] – Braveheart
* [[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 ==

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

=== USB-C connector ===

The USB-C can be used to power the device, and offers USB2 host and OTG possibilities, 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, 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 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].

=== Community-built accessories ===
* [https://www.thingiverse.com/thing:4654013 PinePhone Development Stand at Thingverse]
* [https://www.thingiverse.com/thing:4658870 PinePhone Hard Case by _The3DmaN_ at Thingverse]
* [https://www.thingiverse.com/thing:4651177 PinePhone Hard Case by blitzaxt at Thingverse]

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

== Killswitch configuration ==

[[File:PinePhone Kill Interruptors de Maquinari del PinePhone 4529.jpg|320px|thumb|right|Detail of DIP switch]]

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 ==
{{Hint|The EG25-G modem and the RTL8723CS WiFi and Bluetooth combo do not work without battery power, even when enough power is supplied to the PinePhone via the USB Type-C port.}}

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

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.

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.

== Connectivity ==

=== WiFi and Bluetooth ===

The Pinephone uses [https://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf Realtek RTL8723CS] for its WiFi and Bluetooth connectivity. Unfortunately, just like the other Realteks ''([https://en.wikipedia.org/wiki/Comparison_of_open-source_wireless_drivers see more info])'' - this RTL8723CS chip requires a proprietary closed-source binary blob firmware, unlike a famous Atheros ath9k family which sadly didn't find a way into the Pinephone. For those who have the capability to reverse-engineer the Realtek firmware of this chip to create the opensource replacement, resources like [https://libreplanet.org/wiki/Group:Hardware/research/e-readers/Kobo/Aura_H2O_Edition_2#Firmwares this] and [https://8051enthusiast.github.io/2021/07/05/002-wifi_fun.html this] could be a great starting point for your further research.

If your Pinephone's Linux distribution uses a NetworkManager for connectivity, for the anonymity purposes it is possible to randomize the WiFi MAC address for each re-connection. Open the <code>/etc/NetworkManager/NetworkManager.conf</code> with a text editor ''(you may need the sudo rights)'' - and under the existing configuration like:

<pre>
[main]
dhcp=internal
</pre>

add the following lines:

<pre>
[device]
wifi.scan-rand-mac-address=yes

[connection]
wifi.cloned-mac-address=random
</pre>

'''TODO:''' It seems a Bluetooth also has a MAC address. How to spoof it as well?

=== Modem ===

The PinePhone uses Quectel EG25-G as modem. AT commands are used to communicate with the modem. To send them under Linux, you can use either <code>minicom</code> - <code>sudo minicom -D /dev/EG25.AT</code> - or the often-preinstalled <code>atinout</code> utility:

<pre>
sudo su
atinout - /dev/EG25.AT out.txt << EOF
> AT+... command here
> EOF
cat ./out.txt # to see the result of a command execution
</pre>

==== AT commands ====

A list of documented AT commands can be found in the [[File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_AT_Commands_Manual_V2.0.pdf]] from Quectel. In example, to '''show the current IMEI number''':

<pre>
sudo su
atinout - /dev/EG25.AT out.txt << EOF
> AT+EGMR=0,7
> EOF
cat ./out.txt # to see the IMEI
</pre>

Also, there are certain undocumented AT commands. In example, to '''change the PinePhone IMEI number''' to a valid newIMEI one:

<pre>
sudo su
atinout - /dev/EG25.AT out.txt << EOF
> AT+EGMR=1,7,"newIMEI"
> EOF
cat ./out.txt # should output OK
</pre>

Then use <code>AT+EGMR=0,7</code> to see if IMEI has been changed successfully, - and, to see that IMEI change is persistent: shutdown a phone, remove a battery, press a power button to discharge the motherboard, put a battery back, turn on the phone and run <code>AT+EGMR=0,7</code> again.

Such a command has to be approached with caution: although in the majority of countries changing IMEI '''by itself''' is not illegal ''(or at least not prosecuted unless you are doing something malicious using this capability)'', still a cellphone service provider may ban your IMEI and/or phone number if it sees two cellphones with the same IMEI being used simultaneously. So it should be done with common sense: in example, if you don't want your cellphone service provider ''(or the governmental/commercial entities it could be supplying with information)'' to know that you have replaced your old phone, you could change the IMEI of your PinePhone to be identical to your old phone's, just avoid using them simultaneously or at least don't connect them to the same provider.

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

==== VoLTE ====

The PinePhone's modem supports VoLTE and comes with a few VoLTE profiles preloaded. Most OSes 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 OSes.

==== Firmware update ====

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

You can check the modem firmware version with a following AT command:

<pre>
sudo su
atinout - /dev/EG25.AT out.txt << EOF
> AT+QGMR
> EOF
cat ./out.txt # should output OK
</pre>

If it is 01.001.01.001 ''(EG25GGBR07A08M2G_01.001.01.001)'', then it's recommended to update it to 01.002.01.002 ''(EG25GGBR07A08M2G_01.002.01.002)'' - because "002" has a better performance than "001", and according to Biktorgj it is more stable than the latest "003". However,

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

<pre>git clone https://github.com/Biktorgj/quectel_eg25_recovery</pre>

After cloning the directory, open it with cd:

<pre>cd quectel_eg25_recovery</pre>

Then run qfirehose, which starts the flashing process:

<pre>sudo ./qfirehose -f ./</pre>

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 is controlled via a separate set of AT commands. The AGPS 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. While the hardware supports AGPS data upload, it isn't yet implemented in current distributions. There is a [https://gist.github.com/alastair-dm/263209b54d01209be28828e555fa6628 proof of concept script] which can be made to work, but support needs to be added to ModemManager, oFono etc. before it will be easy to use.

Basic testing of GNSS reception can be done by using the AT command interface (/dev/ttyUSB2) from a terminal progam like minicom and the data output interface (/dev/ttyUSB1) to feed NMEA data into gpsmon or some other progam 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

==== Voice mail ====

Some phone operating systems may not have support for accessing your voicemail by holding down the 1 key. If you are in Canada and using rogers or a rogers associated carrier (such as ''Chatr''), you can access your voice mail by calling an external number, see: https://www.howardforums.com/showthread.php/913346-Rogers-GSM-Voicemail-Retrieval-Numbers

In America, AT&T also has support for accessing your voicemail via an external phone number: https://www.att.com/support/article/wireless/KM1009101/

In Canada, Rogers voicemail can be called by dialing *98

== 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 Phillip’s 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 Phillip’s 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.

Download the latest ANX7688 firmware image on the phone:

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

Execute 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 dimensions: 12x6x2 mm. Compatible with Xiaomi Mi2 / Mi3 / Mi4, Lenovo A536 and others, see [https://forum.pine64.org/showthread.php?tid=12046&pid=85698#pid85698 here]
* Loudspeaker dimensions: 15x11x3 mm. Compatible with Nokia N91, Lenovo A536 and others, see [https://forum.pine64.org/showthread.php?tid=12046&pid=85698#pid85698 here]
* Proximity sensor rubber isolator

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

== Developer works ==

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

2021-08-20T17:13:00Z

MikeBanon: Add the "WiFi and Bluetooth" section, and move both it and "Modem" into the "Connectivity" for the further expansion

[[File:PinePhone Beta Edition.png|500px|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 Linux experience.

Bear in mind that the software for Linux on phones 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 [https://www.pine64.org/philosophy/ PINE64 philosophy]), and currently that support resources are sparse - the best way to get support quickly is to ask in the community chat! Please only contact PINE64 directly if questions couldn't be solved via the community chat or this wiki.

== First time installation ==

{{Hint|Do not insert an empty micro SIM adapter into the phone, as it will get stuck on the contact pins.}}

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 until this is removed and the modem, WiFi and Bluetooth will not work until the battery is connected.

The PinePhone's SIM slot only accepts a micro SIM, please do not insert a nano SIM without an adapter. An adapter from a nano to a micro SIM might be included under tape in the camera notch of the phone's packaging. The SIM card has to be placed in the lower slot, while the microSD has to be placed in the upper slot. Notice: Do not insert an empty micro SIM adapter into the phone, as it will get stuck on the contact pins.

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
# Remove the battery (if the battery is stuck in the device please check [[PinePhone_FAQ#The_battery_is_stuck_inside_the_phone|this]] paragraph for a fix)
# Peel off the clear plastic sticker below it, which isolates the charging contacts
# Reinsert the battery

<gallery mode="nolines" widths="400px" heights="400px">
Image:Pinephone_warning.png|A protection foil isolates the battery for the shipping.
Image:Pinephone_backside.png|The microSD belongs in the upper slot, the micro SIM in the lower slot.
</gallery>

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

== 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|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 killswitch 6 is deactivated)
* '''Communication:'''
** '''[[#Modem|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
* '''Killswitches:''' Modem, WiFi & Bluetooth, Microphone, Cameras
* '''[[#Battery|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 ==

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

* [[Project Anakin]]
* [[Project Don't be evil|"Project Don't Be Evil"]] – development kit (devkit)
* [[PinePhone v1.0 - Dev|PinePhone v1.0]] – developer batch
* [[PinePhone v1.1 - Braveheart|PinePhone v1.1]] – Braveheart
* [[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 ==

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

=== USB-C connector ===

The USB-C can be used to power the device, and offers USB2 host and OTG possibilities, 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, 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 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].

=== Community-built accessories ===
* [https://www.thingiverse.com/thing:4654013 PinePhone Development Stand at Thingverse]
* [https://www.thingiverse.com/thing:4658870 PinePhone Hard Case by _The3DmaN_ at Thingverse]
* [https://www.thingiverse.com/thing:4651177 PinePhone Hard Case by blitzaxt at Thingverse]

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

== Killswitch configuration ==

[[File:PinePhone Kill Interruptors de Maquinari del PinePhone 4529.jpg|320px|thumb|right|Detail of DIP switch]]

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 ==
{{Hint|The EG25-G modem and the RTL8723CS WiFi and Bluetooth combo do not work without battery power, even when enough power is supplied to the PinePhone via the USB Type-C port.}}

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

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.

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.

== Connectivity ==

=== WiFi and Bluetooth ===

The Pinephone uses [https://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf Realtek RTL8723CS] for its WiFi and Bluetooth connectivity. Unfortunately, just like the other Realteks ''([https://en.wikipedia.org/wiki/Comparison_of_open-source_wireless_drivers see more info])'' - this RTL8723CS chip requires a proprietary closed-source binary blob firmware, unlike a famous Atheros ath9k family which sadly didn't find a way into the Pinephone. For those who have the capability to reverse-engineer the Realtek firmware of this chip to create the opensource replacement, resources like [https://libreplanet.org/wiki/Group:Hardware/research/e-readers/Kobo/Aura_H2O_Edition_2#Firmwares this] and [https://8051enthusiast.github.io/2021/07/05/002-wifi_fun.html this] could be a great starting point for your further research.

=== Modem ===

The PinePhone uses Quectel EG25-G as modem. AT commands are used to communicate with the modem. To send them under Linux, you can use either <code>minicom</code> - <code>sudo minicom -D /dev/EG25.AT</code> - or the often-preinstalled <code>atinout</code> utility:

<pre>
sudo su
atinout - /dev/EG25.AT out.txt << EOF
> AT+... command here
> EOF
cat ./out.txt # to see the result of a command execution
</pre>

==== AT commands ====

A list of documented AT commands can be found in the [[File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_AT_Commands_Manual_V2.0.pdf]] from Quectel. In example, to '''show the current IMEI number''':

<pre>
sudo su
atinout - /dev/EG25.AT out.txt << EOF
> AT+EGMR=0,7
> EOF
cat ./out.txt # to see the IMEI
</pre>

Also, there are certain undocumented AT commands. In example, to '''change the PinePhone IMEI number''' to a valid newIMEI one:

<pre>
sudo su
atinout - /dev/EG25.AT out.txt << EOF
> AT+EGMR=1,7,"newIMEI"
> EOF
cat ./out.txt # should output OK
</pre>

Then use <code>AT+EGMR=0,7</code> to see if IMEI has been changed successfully, - and, to see that IMEI change is persistent: shutdown a phone, remove a battery, press a power button to discharge the motherboard, put a battery back, turn on the phone and run <code>AT+EGMR=0,7</code> again.

Such a command has to be approached with caution: although in the majority of countries changing IMEI '''by itself''' is not illegal ''(or at least not prosecuted unless you are doing something malicious using this capability)'', still a cellphone service provider may ban your IMEI and/or phone number if it sees two cellphones with the same IMEI being used simultaneously. So it should be done with common sense: in example, if you don't want your cellphone service provider ''(or the governmental/commercial entities it could be supplying with information)'' to know that you have replaced your old phone, you could change the IMEI of your PinePhone to be identical to your old phone's, just avoid using them simultaneously or at least don't connect them to the same provider.

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

==== VoLTE ====

The PinePhone's modem supports VoLTE and comes with a few VoLTE profiles preloaded. Most OSes 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 OSes.

==== Firmware update ====

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

You can check the modem firmware version with a following AT command:

<pre>
sudo su
atinout - /dev/EG25.AT out.txt << EOF
> AT+QGMR
> EOF
cat ./out.txt # should output OK
</pre>

If it is 01.001.01.001 ''(EG25GGBR07A08M2G_01.001.01.001)'', then it's recommended to update it to 01.002.01.002 ''(EG25GGBR07A08M2G_01.002.01.002)'' - because "002" has a better performance than "001", and according to Biktorgj it is more stable than the latest "003". However,

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

<pre>git clone https://github.com/Biktorgj/quectel_eg25_recovery</pre>

After cloning the directory, open it with cd:

<pre>cd quectel_eg25_recovery</pre>

Then run qfirehose, which starts the flashing process:

<pre>sudo ./qfirehose -f ./</pre>

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 is controlled via a separate set of AT commands. The AGPS 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. While the hardware supports AGPS data upload, it isn't yet implemented in current distributions. There is a [https://gist.github.com/alastair-dm/263209b54d01209be28828e555fa6628 proof of concept script] which can be made to work, but support needs to be added to ModemManager, oFono etc. before it will be easy to use.

Basic testing of GNSS reception can be done by using the AT command interface (/dev/ttyUSB2) from a terminal progam like minicom and the data output interface (/dev/ttyUSB1) to feed NMEA data into gpsmon or some other progam 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

==== Voice mail ====

Some phone operating systems may not have support for accessing your voicemail by holding down the 1 key. If you are in Canada and using rogers or a rogers associated carrier (such as ''Chatr''), you can access your voice mail by calling an external number, see: https://www.howardforums.com/showthread.php/913346-Rogers-GSM-Voicemail-Retrieval-Numbers

In America, AT&T also has support for accessing your voicemail via an external phone number: https://www.att.com/support/article/wireless/KM1009101/

In Canada, Rogers voicemail can be called by dialing *98

== 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 Phillip’s 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 Phillip’s 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.

Download the latest ANX7688 firmware image on the phone:

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

Execute 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 dimensions: 12x6x2 mm. Compatible with Xiaomi Mi2 / Mi3 / Mi4, Lenovo A536 and others, see [https://forum.pine64.org/showthread.php?tid=12046&pid=85698#pid85698 here]
* Loudspeaker dimensions: 15x11x3 mm. Compatible with Nokia N91, Lenovo A536 and others, see [https://forum.pine64.org/showthread.php?tid=12046&pid=85698#pid85698 here]
* Proximity sensor rubber isolator

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

== Developer works ==

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

PineModems

2021-08-20T16:24:44Z

MikeBanon: Add a couple of AT command references

= Modems used in Pine64 boards and devices =

== Quectel EG25-G Modem ==

Quectel EG25-G is an LTE Cat 4 module optimized specially for M2M and IoT applications. It is used in the [[PinePhone]].

* Specifications: [[File:Quectel_EG25-G_LTE_Standard_Specification_V1.3.pdf]]
* Hardware design: [[File:Quectel_EG25-G_Hardware_Design_V1.4.pdf]]
* AT Interface reference manual:
** 1.3 for EC25: [[File:Quectel_EC25&EC21_AT_Commands_Manual_V1.3.pdf]]
** 2.0 for EC25 and EG25-G: [[File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_AT_Commands_Manual_V2.0.pdf]]
* AT Interface file operations: [[File:Quectel_EC2xEG25-GEG9xEM05_FILE_AT_Commands_Manual_V1.0.pdf]]
* GNSS Application note: [[File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_GNSS_Application_Note_V1.3.pdf]]

=== Specifications ===

{| class="wikitable"
| Processor Family || Qualcomm MDM9607
|-
| CPU || Qualcomm MDM9207
|-
| Cores || 1 ACPU Core, Qualcomm Hexagon DSP
|-
| Total RAM || 256Mb
|-
| Total flash space || 256Mb
|-
| Available RAM for the ACPU || 160Mb
|}

=== NAND Partition table layout ===

{| class="wikitable"
! Index
! Name
! Description
|-
| MTD0 || <code>SBL</code>
| Secondary Bootloader, called from the BootROM. Used to start the TrustZone kernel and the Application Bootloader (LK). Also used to enter Quectel's recovery mode
|-
| MTD1 || <code>mibib</code>
| Unknown, used by the DSP
|-
| MTD2 || <code>EFS2</code>
| Unexplored, probably NVRAM data, Used by the DSP
|-
| MTD3 || <code>sys_rev</code>
| Unexplored
|-
| MTD4 || <code>rawdata</code>
| This is where FOTA update data exists before being commited to system or recoveryfs partitions
|-
| MTD5 || <code>tz</code>
| TrustZone kernel
|-
| MTD6 || <code>rpm</code>
| Resource / Power Manager
|-
| MTD7 || <code>cust_info</code>
| Unexplored
|-
| MTD8 || <code>aboot</code>
| Application Bootloader. Uses [https://github.com/littlekernel/lk LK] (LittleKernel, LK embedded kernel) as the bootloader. By default it allows flashing unsigned images but won't allow booting them, soft-bricking the modem until you enter EDL mode
|-
| MTD9 || <code>boot</code>
| [https://www.openembedded.org/wiki/Main_Page OpenEmbedded] boot kernel + DTB
|-
| MTD10 || <code>recovery</code>
| Recovery kernel (normally unused)
|-
| MTD11 || <code>modem</code>
| ADSP firmware blobs
|-
| MTD12 || <code>misc</code>
| Unexplored
|-
| MTD13 || <code>recoveryfs</code>
| Recovery filesystem image (FOTA updates)
|-
| MTD14 || <code>usr_data</code>
| User data partition (<code>/data</code> when mounted by OpenEmbedded)
|-
| MTD15 || <code>sec</code>
| Used to blow fuses in the mdm9207 from images generated by Qualcomm Sectools
|-
| MTD16 || <code>system</code>
| Linux OpenEmbedded root image, formatted in UBIFS (Unsorted Block Image File System, [https://en.wikipedia.org/wiki/UBIFS Wikipedia])
|}

=== Firmware Recovery ===

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

The System partition is mounted as read-only mode, but the data partition is writable. It might be possible, if there's an unexpected reset or power is lost while running, that the data partition gets corrupt and thus unable to boot.

[[File:Pinephone-EG25-Recovery.jpg|thumb|right|PinePhone USB_BOOT test points]]

The modem has 4 different boot modes:
* Normal boot
* Recovery mode (used by the modem usually to install a FOTA update)
* Fastboot mode
* Qualcomm EDL Mode

If the modem is unable to boot, depending on the type of crash, it might:
* not show anywhere (USB device missing)
* or malfunction (no radio but USB working)
* or enter EDL mode, if the entire flash is corrupt.

'''Boot the device in EDL mode'''

To check if the device is booted in EDL mode, run <code>lsusb</code> (a part of the <code>usbutils</code> package) in a terminal and inspect the output. You should see the following device listed:

Bus 003 Device 003: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

In any scenario, the modem can be triggered to enter EDL mode by shorting two test pins on the PinePhone motherboard.

# Power off the phone
# short the two test points
# boot the phone while keeping the test points shorted until fully booted up, at least until you hear the camera clicking twice (which is normally when the modem is powered).

'''Get the Firmware Recovery Package'''

The Firmware Recovery Package is at: https://github.com/Biktorgj/quectel_eg25_recovery

Either clone its repo with git, or download its archive & unzip it.

As you should have no access to the Internet on PinePhone when its modem need a Recovery, you can fetch it on other devices and copy it to the Pinephone.

'''Execute the Quectel QFirehose utility'''

Once in EDL mode, open a terminal, navigate to the root directory of the recovery package, and run:

* If you use an ARM64 distribution (most likely): <code>sudo ./qfirehose -f ./</code> or <code>sudo ./qfirehose_arm64 -f ./</code>
* If you use an ARMHF (32 bit) distribution: <code>sudo ./qfirehose_armhf -f ./</code>

It will reboot the modem after finished. After about 30 seconds, it will get back up and running. To check the firmware version after that, use an AT command <code>AT+QGMR</code> like at [[PinePhone#Firmware_update]].

=== Bootloader unlocking ===

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

The Modem has a locked bootloader. It won't allow to boot unsigned Kernel images, but will allow to flash them, making it easy to brick the modem. To fix this, you can flash an unlocked bootloader, which will then allow you to do as you please with the hardware.

Unlocked bootloader:
* Source code: https://github.com/Biktorgj/quectel_lk
* Prebuilt binary releases: https://github.com/Biktorgj/quectel_lk/releases

=== Custom Kernels and system images ===

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

Custom kernel builds and system images can be created for the modem, though they require a couple of things to be correctly built and be bootable.

* The source code release for the kernel provided by the manufacturer is incomplete and won't build
* Common Android tools like mkbootimg and dtbtool won't build a bootable image, even if the kernel is correctly compiled and all the DTBs attached.
* Further, there's no source for the OpenEmbedded parts, so building a new system image must be done from scratch, and retrieving the mandatory binary blobs to use the ADSP part of the modem.

There's a '''work in progress''' SDK to allow creating custom kernels and system images, which can be downloaded from the following repository: https://github.com/Biktorgj/pinephone_modem_sdk

See its readme for infomations and instructions. Once downloaded, you should run the <code>init.sh</code> script, which will create all the base directories and download all the different repositories required to build. After the initial setup is complete, run<code>make</code> without arguments to list the available options.

=== IMEI number checking and changing ===

See the examples ''(with a small warning)'' at [[PinePhone#AT_commands]].

[[Category:PinePhone]]

PinePhone

2021-08-20T16:20:43Z

MikeBanon: /* AT commands */ Added slightly more info

[[File:PinePhone Beta Edition.png|500px|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 Linux experience.

Bear in mind that the software for Linux on phones 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 [https://www.pine64.org/philosophy/ PINE64 philosophy]), and currently that support resources are sparse - the best way to get support quickly is to ask in the community chat! Please only contact PINE64 directly if questions couldn't be solved via the community chat or this wiki.

== First time installation ==

{{Hint|Do not insert an empty micro SIM adapter into the phone, as it will get stuck on the contact pins.}}

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 until this is removed and the modem, WiFi and Bluetooth will not work until the battery is connected.

The PinePhone's SIM slot only accepts a micro SIM, please do not insert a nano SIM without an adapter. An adapter from a nano to a micro SIM might be included under tape in the camera notch of the phone's packaging. The SIM card has to be placed in the lower slot, while the microSD has to be placed in the upper slot. Notice: Do not insert an empty micro SIM adapter into the phone, as it will get stuck on the contact pins.

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
# Remove the battery (if the battery is stuck in the device please check [[PinePhone_FAQ#The_battery_is_stuck_inside_the_phone|this]] paragraph for a fix)
# Peel off the clear plastic sticker below it, which isolates the charging contacts
# Reinsert the battery

<gallery mode="nolines" widths="400px" heights="400px">
Image:Pinephone_warning.png|A protection foil isolates the battery for the shipping.
Image:Pinephone_backside.png|The microSD belongs in the upper slot, the micro SIM in the lower slot.
</gallery>

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

== 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|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 killswitch 6 is deactivated)
* '''Communication:'''
** '''[[#Modem|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
* '''Killswitches:''' Modem, WiFi & Bluetooth, Microphone, Cameras
* '''[[#Battery|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 ==

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

* [[Project Anakin]]
* [[Project Don't be evil|"Project Don't Be Evil"]] – development kit (devkit)
* [[PinePhone v1.0 - Dev|PinePhone v1.0]] – developer batch
* [[PinePhone v1.1 - Braveheart|PinePhone v1.1]] – Braveheart
* [[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 ==

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

=== USB-C connector ===

The USB-C can be used to power the device, and offers USB2 host and OTG possibilities, 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, 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 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].

=== Community-built accessories ===
* [https://www.thingiverse.com/thing:4654013 PinePhone Development Stand at Thingverse]
* [https://www.thingiverse.com/thing:4658870 PinePhone Hard Case by _The3DmaN_ at Thingverse]
* [https://www.thingiverse.com/thing:4651177 PinePhone Hard Case by blitzaxt at Thingverse]

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

== Killswitch configuration ==

[[File:PinePhone Kill Interruptors de Maquinari del PinePhone 4529.jpg|320px|thumb|right|Detail of DIP switch]]

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 ==
{{Hint|The EG25-G modem and the RTL8723CS WiFi and Bluetooth combo do not work without battery power, even when enough power is supplied to the PinePhone via the USB Type-C port.}}

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

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.

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. To send them under Linux, you can use either <code>minicom</code> - <code>sudo minicom -D /dev/EG25.AT</code> - or the often-preinstalled <code>atinout</code> utility:

<pre>
sudo su
atinout - /dev/EG25.AT out.txt << EOF
> AT+... command here
> EOF
cat ./out.txt # to see the result of a command execution
</pre>

=== AT commands ===

A list of documented AT commands can be found in the [[File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_AT_Commands_Manual_V2.0.pdf]] from Quectel. In example, to '''show the current IMEI number''':

<pre>
sudo su
atinout - /dev/EG25.AT out.txt << EOF
> AT+EGMR=0,7
> EOF
cat ./out.txt # to see the IMEI
</pre>

Also, there are certain undocumented AT commands. In example, to '''change the PinePhone IMEI number''' to a valid newIMEI one:

<pre>
sudo su
atinout - /dev/EG25.AT out.txt << EOF
> AT+EGMR=1,7,"newIMEI"
> EOF
cat ./out.txt # should output OK
</pre>

Then use <code>AT+EGMR=0,7</code> to see if IMEI has been changed successfully, - and, to see that IMEI change is persistent: shutdown a phone, remove a battery, press a power button to discharge the motherboard, put a battery back, turn on the phone and run <code>AT+EGMR=0,7</code> again.

Such a command has to be approached with caution: although in the majority of countries changing IMEI '''by itself''' is not illegal ''(or at least not prosecuted unless you are doing something malicious using this capability)'', still a cellphone service provider may ban your IMEI and/or phone number if it sees two cellphones with the same IMEI being used simultaneously. So it should be done with common sense: in example, if you don't want your cellphone service provider ''(or the governmental/commercial entities it could be supplying with information)'' to know that you have replaced your old phone, you could change the IMEI of your PinePhone to be identical to your old phone's, just avoid using them simultaneously or at least don't connect them to the same provider.

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

=== VoLTE ===

The PinePhone's modem supports VoLTE and comes with a few VoLTE profiles preloaded. Most OSes 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 OSes.

=== Firmware update ===

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

You can check the modem firmware version with a following AT command:

<pre>
sudo su
atinout - /dev/EG25.AT out.txt << EOF
> AT+QGMR
> EOF
cat ./out.txt # should output OK
</pre>

If it is 01.001.01.001 ''(EG25GGBR07A08M2G_01.001.01.001)'', then it's recommended to update it to 01.002.01.002 ''(EG25GGBR07A08M2G_01.002.01.002)'' - because "002" has a better performance than "001", and according to Biktorgj it is more stable than the latest "003". However,

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

<pre>git clone https://github.com/Biktorgj/quectel_eg25_recovery</pre>

After cloning the directory, open it with cd:

<pre>cd quectel_eg25_recovery</pre>

Then run qfirehose, which starts the flashing process:

<pre>sudo ./qfirehose -f ./</pre>

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 is controlled via a separate set of AT commands. The AGPS 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. While the hardware supports AGPS data upload, it isn't yet implemented in current distributions. There is a [https://gist.github.com/alastair-dm/263209b54d01209be28828e555fa6628 proof of concept script] which can be made to work, but support needs to be added to ModemManager, oFono etc. before it will be easy to use.

Basic testing of GNSS reception can be done by using the AT command interface (/dev/ttyUSB2) from a terminal progam like minicom and the data output interface (/dev/ttyUSB1) to feed NMEA data into gpsmon or some other progam 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

=== Voice mail ===

Some phone operating systems may not have support for accessing your voicemail by holding down the 1 key. If you are in Canada and using rogers or a rogers associated carrier (such as ''Chatr''), you can access your voice mail by calling an external number, see: https://www.howardforums.com/showthread.php/913346-Rogers-GSM-Voicemail-Retrieval-Numbers

In America, AT&T also has support for accessing your voicemail via an external phone number: https://www.att.com/support/article/wireless/KM1009101/

In Canada, Rogers voicemail can be called by dialing *98

== 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 Phillip’s 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 Phillip’s 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.

Download the latest ANX7688 firmware image on the phone:

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

Execute 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 dimensions: 12x6x2 mm. Compatible with Xiaomi Mi2 / Mi3 / Mi4, Lenovo A536 and others, see [https://forum.pine64.org/showthread.php?tid=12046&pid=85698#pid85698 here]
* Loudspeaker dimensions: 15x11x3 mm. Compatible with Nokia N91, Lenovo A536 and others, see [https://forum.pine64.org/showthread.php?tid=12046&pid=85698#pid85698 here]
* Proximity sensor rubber isolator

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

== Developer works ==

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

2021-08-20T16:06:45Z

MikeBanon: My dmesg didn't have a modem firmware info. Replaced with a more reliable way of modem firmware version checking

[[File:PinePhone Beta Edition.png|500px|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 Linux experience.

Bear in mind that the software for Linux on phones 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 [https://www.pine64.org/philosophy/ PINE64 philosophy]), and currently that support resources are sparse - the best way to get support quickly is to ask in the community chat! Please only contact PINE64 directly if questions couldn't be solved via the community chat or this wiki.

== First time installation ==

{{Hint|Do not insert an empty micro SIM adapter into the phone, as it will get stuck on the contact pins.}}

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 until this is removed and the modem, WiFi and Bluetooth will not work until the battery is connected.

The PinePhone's SIM slot only accepts a micro SIM, please do not insert a nano SIM without an adapter. An adapter from a nano to a micro SIM might be included under tape in the camera notch of the phone's packaging. The SIM card has to be placed in the lower slot, while the microSD has to be placed in the upper slot. Notice: Do not insert an empty micro SIM adapter into the phone, as it will get stuck on the contact pins.

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
# Remove the battery (if the battery is stuck in the device please check [[PinePhone_FAQ#The_battery_is_stuck_inside_the_phone|this]] paragraph for a fix)
# Peel off the clear plastic sticker below it, which isolates the charging contacts
# Reinsert the battery

<gallery mode="nolines" widths="400px" heights="400px">
Image:Pinephone_warning.png|A protection foil isolates the battery for the shipping.
Image:Pinephone_backside.png|The microSD belongs in the upper slot, the micro SIM in the lower slot.
</gallery>

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

== 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|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 killswitch 6 is deactivated)
* '''Communication:'''
** '''[[#Modem|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
* '''Killswitches:''' Modem, WiFi & Bluetooth, Microphone, Cameras
* '''[[#Battery|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 ==

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

* [[Project Anakin]]
* [[Project Don't be evil|"Project Don't Be Evil"]] – development kit (devkit)
* [[PinePhone v1.0 - Dev|PinePhone v1.0]] – developer batch
* [[PinePhone v1.1 - Braveheart|PinePhone v1.1]] – Braveheart
* [[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 ==

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

=== USB-C connector ===

The USB-C can be used to power the device, and offers USB2 host and OTG possibilities, 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, 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 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].

=== Community-built accessories ===
* [https://www.thingiverse.com/thing:4654013 PinePhone Development Stand at Thingverse]
* [https://www.thingiverse.com/thing:4658870 PinePhone Hard Case by _The3DmaN_ at Thingverse]
* [https://www.thingiverse.com/thing:4651177 PinePhone Hard Case by blitzaxt at Thingverse]

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

== Killswitch configuration ==

[[File:PinePhone Kill Interruptors de Maquinari del PinePhone 4529.jpg|320px|thumb|right|Detail of DIP switch]]

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 ==
{{Hint|The EG25-G modem and the RTL8723CS WiFi and Bluetooth combo do not work without battery power, even when enough power is supplied to the PinePhone via the USB Type-C port.}}

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

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.

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. To send them under Linux, you can use either <code>minicom</code> - <code>sudo minicom -D /dev/EG25.AT</code> - or the often-preinstalled <code>atinout</code> utility:

<pre>
sudo su
atinout - /dev/EG25.AT out.txt << EOF
> AT+... command here
> EOF
cat ./out.txt # to see the result of a command execution
</pre>

=== AT commands ===

A list of documented AT commands can be found in the [[File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_AT_Commands_Manual_V2.0.pdf]] from Quectel. In example, to '''show the current IMEI number''':

<pre>
sudo su
atinout - /dev/EG25.AT out.txt << EOF
> AT+EGMR=0,7
> EOF
cat ./out.txt # to see the IMEI
</pre>

Also, there are certain undocumented AT commands. In example, to '''change the PinePhone IMEI number''' to a valid newIMEI one:

<pre>
sudo su
atinout - /dev/EG25.AT out.txt << EOF
> AT+EGMR=1,7,"newIMEI"
> EOF
cat ./out.txt # should output OK
</pre>

Such a command has to be approached with caution: although in the majority of countries changing IMEI '''by itself''' is not illegal ''(or at least not prosecuted unless you are doing something malicious using this capability)'', still a cellphone service provider may ban your IMEI and/or phone number if it sees two cellphones with the same IMEI being used simultaneously. So it should be done with common sense: in example, if you don't want your cellphone service provider ''(or the governmental/commercial entities it could be supplying with information)'' to know that you have replaced your old phone, you could change the IMEI of your PinePhone to be identical to your old phone's, just avoid using them simultaneously or at least don't connect them to the same provider.

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

=== VoLTE ===

The PinePhone's modem supports VoLTE and comes with a few VoLTE profiles preloaded. Most OSes 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 OSes.

=== Firmware update ===

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

You can check the modem firmware version with a following AT command:

<pre>
sudo su
atinout - /dev/EG25.AT out.txt << EOF
> AT+QGMR
> EOF
cat ./out.txt # should output OK
</pre>

If it is 01.001.01.001 ''(EG25GGBR07A08M2G_01.001.01.001)'', then it's recommended to update it to 01.002.01.002 ''(EG25GGBR07A08M2G_01.002.01.002)'' - because "002" has a better performance than "001", and according to Biktorgj it is more stable than the latest "003". However,

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

<pre>git clone https://github.com/Biktorgj/quectel_eg25_recovery</pre>

After cloning the directory, open it with cd:

<pre>cd quectel_eg25_recovery</pre>

Then run qfirehose, which starts the flashing process:

<pre>sudo ./qfirehose -f ./</pre>

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 is controlled via a separate set of AT commands. The AGPS 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. While the hardware supports AGPS data upload, it isn't yet implemented in current distributions. There is a [https://gist.github.com/alastair-dm/263209b54d01209be28828e555fa6628 proof of concept script] which can be made to work, but support needs to be added to ModemManager, oFono etc. before it will be easy to use.

Basic testing of GNSS reception can be done by using the AT command interface (/dev/ttyUSB2) from a terminal progam like minicom and the data output interface (/dev/ttyUSB1) to feed NMEA data into gpsmon or some other progam 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

=== Voice mail ===

Some phone operating systems may not have support for accessing your voicemail by holding down the 1 key. If you are in Canada and using rogers or a rogers associated carrier (such as ''Chatr''), you can access your voice mail by calling an external number, see: https://www.howardforums.com/showthread.php/913346-Rogers-GSM-Voicemail-Retrieval-Numbers

In America, AT&T also has support for accessing your voicemail via an external phone number: https://www.att.com/support/article/wireless/KM1009101/

In Canada, Rogers voicemail can be called by dialing *98

== 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 Phillip’s 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 Phillip’s 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.

Download the latest ANX7688 firmware image on the phone:

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

Execute 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 dimensions: 12x6x2 mm. Compatible with Xiaomi Mi2 / Mi3 / Mi4, Lenovo A536 and others, see [https://forum.pine64.org/showthread.php?tid=12046&pid=85698#pid85698 here]
* Loudspeaker dimensions: 15x11x3 mm. Compatible with Nokia N91, Lenovo A536 and others, see [https://forum.pine64.org/showthread.php?tid=12046&pid=85698#pid85698 here]
* Proximity sensor rubber isolator

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

== Developer works ==

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

2021-08-20T15:52:01Z

MikeBanon: Expand the modem section with some AT commands

[[File:PinePhone Beta Edition.png|500px|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 Linux experience.

Bear in mind that the software for Linux on phones 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 [https://www.pine64.org/philosophy/ PINE64 philosophy]), and currently that support resources are sparse - the best way to get support quickly is to ask in the community chat! Please only contact PINE64 directly if questions couldn't be solved via the community chat or this wiki.

== First time installation ==

{{Hint|Do not insert an empty micro SIM adapter into the phone, as it will get stuck on the contact pins.}}

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 until this is removed and the modem, WiFi and Bluetooth will not work until the battery is connected.

The PinePhone's SIM slot only accepts a micro SIM, please do not insert a nano SIM without an adapter. An adapter from a nano to a micro SIM might be included under tape in the camera notch of the phone's packaging. The SIM card has to be placed in the lower slot, while the microSD has to be placed in the upper slot. Notice: Do not insert an empty micro SIM adapter into the phone, as it will get stuck on the contact pins.

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
# Remove the battery (if the battery is stuck in the device please check [[PinePhone_FAQ#The_battery_is_stuck_inside_the_phone|this]] paragraph for a fix)
# Peel off the clear plastic sticker below it, which isolates the charging contacts
# Reinsert the battery

<gallery mode="nolines" widths="400px" heights="400px">
Image:Pinephone_warning.png|A protection foil isolates the battery for the shipping.
Image:Pinephone_backside.png|The microSD belongs in the upper slot, the micro SIM in the lower slot.
</gallery>

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

== 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|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 killswitch 6 is deactivated)
* '''Communication:'''
** '''[[#Modem|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
* '''Killswitches:''' Modem, WiFi & Bluetooth, Microphone, Cameras
* '''[[#Battery|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 ==

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

* [[Project Anakin]]
* [[Project Don't be evil|"Project Don't Be Evil"]] – development kit (devkit)
* [[PinePhone v1.0 - Dev|PinePhone v1.0]] – developer batch
* [[PinePhone v1.1 - Braveheart|PinePhone v1.1]] – Braveheart
* [[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 ==

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

=== USB-C connector ===

The USB-C can be used to power the device, and offers USB2 host and OTG possibilities, 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, 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 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].

=== Community-built accessories ===
* [https://www.thingiverse.com/thing:4654013 PinePhone Development Stand at Thingverse]
* [https://www.thingiverse.com/thing:4658870 PinePhone Hard Case by _The3DmaN_ at Thingverse]
* [https://www.thingiverse.com/thing:4651177 PinePhone Hard Case by blitzaxt at Thingverse]

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

== Killswitch configuration ==

[[File:PinePhone Kill Interruptors de Maquinari del PinePhone 4529.jpg|320px|thumb|right|Detail of DIP switch]]

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 ==
{{Hint|The EG25-G modem and the RTL8723CS WiFi and Bluetooth combo do not work without battery power, even when enough power is supplied to the PinePhone via the USB Type-C port.}}

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

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.

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. To send them under Linux, you can use either <code>minicom</code> - <code>sudo minicom -D /dev/EG25.AT</code> - or the often-preinstalled <code>atinout</code> utility:

<pre>
sudo su
atinout - /dev/EG25.AT out.txt << EOF
> AT+... command here
> EOF
cat ./out.txt # to see the result of a command execution
</pre>

=== AT commands ===

A list of documented AT commands can be found in the [[File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_AT_Commands_Manual_V2.0.pdf]] from Quectel. In example, to '''show the current IMEI number''':

<pre>
sudo su
atinout - /dev/EG25.AT out.txt << EOF
> AT+EGMR=0,7
> EOF
cat ./out.txt # to see the IMEI
</pre>

Also, there are certain undocumented AT commands. In example, to '''change the PinePhone IMEI number''' to a valid newIMEI one:

<pre>
sudo su
atinout - /dev/EG25.AT out.txt << EOF
> AT+EGMR=1,7,"newIMEI"
> EOF
cat ./out.txt # should output OK
</pre>

Such a command has to be approached with caution: although in the majority of countries changing IMEI '''by itself''' is not illegal ''(or at least not prosecuted unless you are doing something malicious using this capability)'', still a cellphone service provider may ban your IMEI and/or phone number if it sees two cellphones with the same IMEI being used simultaneously. So it should be done with common sense: in example, if you don't want your cellphone service provider ''(or the governmental/commercial entities it could be supplying with information)'' to know that you have replaced your old phone, you could change the IMEI of your PinePhone to be identical to your old phone's, just avoid using them simultaneously or at least don't connect them to the same provider.

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

=== VoLTE ===

The PinePhone's modem supports VoLTE and comes with a few VoLTE profiles preloaded. Most OSes 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 OSes.

=== Firmware update ===

{{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 modem firmware can be updated to the latest version if it is outdated and ''dmesg'' returns the following message:

<pre>modem-power serial1-0: Your modem has an outdated firmware. Latest know version is EG25GGBR07A08M2G_[...]. Consider updating.</pre>

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

<pre>git clone https://github.com/Biktorgj/quectel_eg25_recovery</pre>

After cloning the directory, open it with cd:

<pre>cd quectel_eg25_recovery</pre>

Then run qfirehose, which starts the flashing process:

<pre>sudo ./qfirehose -f ./</pre>

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 is controlled via a separate set of AT commands. The AGPS 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. While the hardware supports AGPS data upload, it isn't yet implemented in current distributions. There is a [https://gist.github.com/alastair-dm/263209b54d01209be28828e555fa6628 proof of concept script] which can be made to work, but support needs to be added to ModemManager, oFono etc. before it will be easy to use.

Basic testing of GNSS reception can be done by using the AT command interface (/dev/ttyUSB2) from a terminal progam like minicom and the data output interface (/dev/ttyUSB1) to feed NMEA data into gpsmon or some other progam 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

=== Voice mail ===

Some phone operating systems may not have support for accessing your voicemail by holding down the 1 key. If you are in Canada and using rogers or a rogers associated carrier (such as ''Chatr''), you can access your voice mail by calling an external number, see: https://www.howardforums.com/showthread.php/913346-Rogers-GSM-Voicemail-Retrieval-Numbers

In America, AT&T also has support for accessing your voicemail via an external phone number: https://www.att.com/support/article/wireless/KM1009101/

In Canada, Rogers voicemail can be called by dialing *98

== 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 Phillip’s 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 Phillip’s 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.

Download the latest ANX7688 firmware image on the phone:

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

Execute 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 dimensions: 12x6x2 mm. Compatible with Xiaomi Mi2 / Mi3 / Mi4, Lenovo A536 and others, see [https://forum.pine64.org/showthread.php?tid=12046&pid=85698#pid85698 here]
* Loudspeaker dimensions: 15x11x3 mm. Compatible with Nokia N91, Lenovo A536 and others, see [https://forum.pine64.org/showthread.php?tid=12046&pid=85698#pid85698 here]
* Proximity sensor rubber isolator

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

== Developer works ==

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 Carrier Support

2021-08-20T13:14:29Z

MikeBanon: fix the Quectel document references

{{under construction}}

{{hint|MMS currently doesn't work in any distribution on the PinePhone without a [[PinePhone_Carrier_Support#MMS_workarounds|script]]! This means images and group chats will not work in text messages.}}

This page contains hints on setting up cellular network connectivity for specific carriers.
For more general information, see [[PinePhone#Modem_and_carrier_support|Modem and carrier support]]. 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 || 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 2020
|-
| Japan || Rakuten Mobile || Unsupported by carrier || Unsupported by carrier || Yes || No || Manjaro Plasma Mobile February 2021
|-
| Japan || 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
|-
| South Korea || KT || Yes || Not tested || Yes || Yes || Manjaro Phosh, June 2021
|}

== 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
|-
|-
| Sweden || Telenor SE || Not tested || Not tested || 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
|-
| 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 || Not tested || ArchLinux - 30 July 2021
|-
| 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 || 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
|-
| 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
|-
|}

== North America ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| USA || T-Mobile || Yes || No || Yes || Yes ||
* Arch Linux Arm 2020/11/29
* Mobian - Phosh
* Manjaro - KDE Plasma Mobile
|-
| 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 || Not tested || Yes || Yes ||
*Mobian - Phosh 2021/3/14
*postMarketOS - Phosh, Sxmo, Plasma Mobile 2021/5/26
*Ubuntu Touch 2021/5/24
|-
| USA || Tello (T-Mobile) || Yes || No || Yes || Yes ||
*postMarketOS - Phosh 2021/8/15
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
*Mobian - Phosh 2021/3/1
|-
| 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
|-
| USA || FaithWireless (AT&T) || Yes || No || Yes || Yes ||
*Arch Linux Arm - Phosh 2021/04/29 (version 0.10.1-1, see the [[PinePhone_Carrier_Support#AT.26T|AT&T issues]] below.)
|-
| 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
|}

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

== Middle East ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Israel|| Cellcom prepay|| receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-

|-
| Israel|| Golan TC || receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Partner prepay || receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Pelephone prepay|| receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Hot prepay|| receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| 019 prepay|| No || 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. The PinePhone seems to work out-of-the-box with AT&T. If you transfer a SIM card from another phone you were using with AT&T, you need to activate the PinePhone through [https://www.att.com/buy/wireless/byod/byod AT&T's website]. Calls and SMS messages work. VoLTE is as yet untested.

However, it is likely AT&T will 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).

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

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

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

* 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 component list

2021-08-20T13:12:56Z

MikeBanon: /* P.15 MODEM-4G */ fix the Quectel document references

The following list of components are found in the [https://files.pine64.org/doc/PinePhone/PinePhone%20v1.2b%20Released%20Schematic.pdf schematic] for the PinePhone 1.2b.

===Abreviations used in schematic===

The following [https://www.electronics-notes.com/articles/analogue_circuits/circuits-symbols-diagrams/electronics-circuit-symbols-overview.php abbreviations] are used as the starting letter(s) to identify the components in the PinePhone schematics:

* '''ANT''': antenna
* '''C''' : [https://www.electronics-notes.com/articles/analogue_circuits/circuits-symbols-diagrams/capacitors-polar-nonpolar-variable.php capacitor]
* '''D''' : [https://www.electronics-notes.com/articles/analogue_circuits/circuits-symbols-diagrams/diode-semiconductor.php diode]
* '''DU''' : Only used in the "DU1", which is an integrated circuit for memory
* '''ED''' : Zener diode to protect against electrostatic discharge
* '''FB''' : [https://en.wikipedia.org/wiki/Ferrite_bead ferrite bead]
* '''J''' : [https://www.electronics-notes.com/articles/analogue_circuits/circuits-symbols-diagrams/wires-switches-connectors.php wire link] (i.e. a connector)
* '''R''' : [https://www.electronics-notes.com/articles/analogue_circuits/circuits-symbols-diagrams/resistors-fixed-variable.php resistor]
* '''L''' : [https://www.electronics-notes.com/articles/analogue_circuits/circuits-symbols-diagrams/inductors-chokes-coils-transformers.php inductor]
* '''NC/''' : not connected (i.e. the part probably isn't placed on the board, but there are circuits in the PCB for it)
* '''Q''' : transistor
* '''SW''' : switch
* '''T''' : test point
* '''U''' : integrated circuit (i.e. a silicon chip)
* '''X''' : crystal oscillator (used for clocks)

===P.4 LPDDR3 FPGA178===

<div style="margin-left:20px">'''''Note:''''' The title of this schematic page should be changed from "LPDDR3 FPGA178" to "LPDDR3 FBGA178", because the RAM chip is a 178-pin fine pitch ball grid array (FBGA), not a field-programmable gate array (FPGA).</div>

* DU1: Artmem [http://files.pine64.org/doc/datasheet/pinephone/ATL3A1632H12A_mobile_lpddr3_11x11.5_v1.0_1600.pdf ATL3A1632H12A] 2GB 800MHz LPDDR3-1600 SDRAM, FBGA-178 11.0x11.5x0.93 mm '''''Note:''''' RAM will be clocked slower, since the Allwinner A64 only supports up to 3GB DDR3-1333 (666.5MHz) and doesn't specify the top supported LPDDR3 speed.

===P.5 CPU===

* U1: Allwinner [http://files.pine64.org/doc/datasheet/pine64/A64_Datasheet_V1.1.pdf A64] 1.2Ghz 4x Cortex-A53, 64-bit, superscalar, 32KB instruction & 32KB data L1 cache per core, 512KB L2 shared cache, ARM Mali-400 MP2 (Utgard) GPU, HDMI 1.4 (up to 4K@30), USB 2.0 with OTG, MIPI CSI, 4 channels in/out, 24-bit, 8-48 KHz audio, video encode: H.264 1080p@60, video decode: H.265 4K@30, H.265 1080p@120, H.264, MPEG1/2/4 / VP8 / AVS / AVS+ 1080p@60, FBGA-396 15x15 mm '''''Note:''''' Clocked at 1.152Ghz on the PinePhone.
* X501: Axtal [https://pdf1.alldatasheet.com/datasheet-pdf/view/228815/AXTAL/AXX3225/+Q2J83JVYUyCLcEbcvvzE+/datasheet.pdf AXX3225] 24MHz ±10ppm quartz crystal oscillator in SMD package, 3.2x2.5 mm
* D500: Will Semiconductor [https://pdf1.alldatasheet.com/datasheet-pdf/view/1136979/WILLSEMI/ESD5451X/+01_7-9BXuHlLuHRMflaL..hDk+/datasheet.pdf ESD5451X] 1-line, bi-directional, transient voltage suppressor, EDS protection up to ±30kV and 8A.
* X500: Seiko Instruments Inc. (SII) [https://www.sii.co.jp/en/quartz/files/2013/03/SC-32S_Leaflet_e20151217.pdf SC32S] 32.768KHz crystal oscillator '''''Note:''''' Not clear if using the [https://www.mouser.com/ProductDetail/Seiko-Instruments-Micro-Energy/SC32S-125PF20PPM?qs=3CPZD7qAgihedyqH7awUjg%3D%3D SC32S-12.5PF20PPM] or the [https://www.mouser.com/ProductDetail/Seiko-Semiconductors/SC32S-7PF20PPM?qs=3CPZD7qAgigZSR1ASVAS6w%3D%3D SC32S-7PF20PPM] 

===P.6 POWER===

* ED600: Will Semiconductor (WILLSEMI) [https://pdf1.alldatasheet.com/datasheet-pdf/view/1136979/WILLSEMI/ESD5451X/+01_7-9BXuHlLuHRMflaL..hDk+/datasheet.pdf ESD5451X] 1-line, bi-directional, transient voltage suppressor, EDS protection up to ±30kV and 8A. '''''Note:''''' This part is marked as optional in the schematic and may not be included.
* U600: X-Powers [https://raw.githubusercontent.com/OLIMEX/OLINUXINO/master/DOCUMENTS/A64-PDFs/AXP803_Datasheet_V1.0.pdf AXP803] power management integrated circuit (PMIC) optimized for multi-core systems, li-ion battery fuel gauge, USB charger (up to 2.8A), QFN 68-pin, 8x8 mm
* Q600: Will Semiconductor [http://monitor.espec.ws/files/wpm1481_186.pdf WPM1481] single P-channel, -12V, -5.5A, power MOSFET
* J600: BA5924211-R battery connector '''''Note:''''' [http://biz.everychina.com/ddream-r/z2eb2904-lateralpressure_ba5924211_r.html Picture] shows this part as having 8 pins, but the schematic shows 6 pins. [http://biz.everychina.com/ddream-r/z2eb2904-lateralpressure_ba5924211_r.html One page] says that it is made by LateralPressure, but [https://www.worldwayelec.com/pro/rohm-semiconductor/ba5924211-r/3528348 another] says it is made by ROHM.
* L606: IND_252010 2.2uH-2A inductor '''''Note:''''' Maybe this is the TDK [https://product.tdk.com/info/en/catalog/datasheets/inductor_commercial_power_vls252010hbu_en.pdf VLS252010HBU].
* U601: LowPowerSemi [https://datasheet.lcsc.com/szlcsc/2004281203_LOWPOWER-LP6226CB6F_C517054.pdf LP6226CB6F] high efficiency boost DC/DC converter with 33V, 1.5A power MOSFET, SOT23-6 package
* D600: On semiconductor [https://www.onsemi.com/pub/Collateral/SS24-D.PDF SS24] Schottky power rectifier, [https://www.nexperia.com/packages/SOD123.html SOD123] package 

===P.7 NAND/eMMC===

* U700: Kimtigo [http://files.pine64.org/doc/datasheet/pinephone/Kimtigo_fbga153_16_32_64_eMMC_datasheet_v1.3.pdf KM110SS0016GxA-DDD00WT] 16GB eMMC 5.1 TLC NAND Flash memory, FBGA-153 11.5×13.0×1.0 mm. '''''Note 1:''''' The schematic says the package is BGA-169, but the Kimtigo documentation says it is FBGA-153. '''''Note 2:''''' The A64 only supports up to eMMC 5.0. '''''Note 3:''''' The schematic lists the part as KM110SS0016GxA-DDD00WT, but [https://xnux.eu/devices/photos/pp-1.1.html these photos] show that its variant, the KM111SS0016GxA-DDD00WT, is being used in the 16GB PinePhone. 

===P.8 AUDIO===

* ED800, ED801, ED802, ED803, ED804, ED805, ED806: Will Semiconductor [https://pdf1.alldatasheet.com/datasheet-pdf/view/1136979/WILLSEMI/ESD5451X/+01_7-9BXuHlLuHRMflaL..hDk+/datasheet.pdf ESD5451X] 1-line, bi-directional, transient voltage suppressor, EDS protection up to ±30kV and 8A.
* U801: Broadchip [http://www.broadchip.com/upLoad/product/month_2003/202003191750413832.pdf BCT4717ETB-TR] 4.0Ω, 300MHz bandwidth, dual bi-directional SPDT (single-pole/double-throw) analog switch
* J800: EAROUTN-A64 receiver
* J801: JA-3606-001AA 3.5mm audio jack
* Q801: Toshiba [https://toshiba.semicon-storage.com/info/docget.jsp?did=10004&prodName=SSM3K35MFV SSM3K35MFV] field-effect transistor, silicon N-channel MOS type
* U800: Shanghai awinic technology [https://www.awinic.com/Cn/Index/pageView/catid/107/id/45.html AW8737SCSR] high efficiency (80%), low noise (53μV), ultra-low distortion (0.008%), constant large volume, 7th generation class K audio amplifier, 1.6×1.68 mm CSP-14 package, 0.4mm pitch [https://pdf1.alldatasheet.com/datasheet-pdf/view/1147555/AWINIC/AW8737SCSR/+014J7J8XvUpOKG+Gc..whdxee+/datasheet.pdf [datasheet]]
* FB800, FB801: 600ohm at 100MHz ferrite bead in a [https://www.electronics-notes.com/articles/electronic_components/surface-mount-technology-smd-smt/packages.php 0402] package ([https://uk.farnell.com/c/passive-components/emc-rfi-suppression/ferrites-ferrite-assortments/ferrite-beads?impedance-100mhz=600ohm examples])

===P.9 T-CADD/USB===

* Q901, Q902, Q903: Toshiba [https://toshiba.semicon-storage.com/info/docget.jsp?did=10004&prodName=SSM3K35MFV SSM3K35MFV] field-effect transistor, silicon N-channel MOS type
* ED900, ED901, ED902: Will Semiconductor [https://pdf1.alldatasheet.com/datasheet-pdf/view/1136979/WILLSEMI/ESD5451X/+01_7-9BXuHlLuHRMflaL..hDk+/datasheet.pdf ESD5451X] 1-line, bi-directional, transient voltage suppressor, EDS protection up to ±30kV and 8A.
* J901: SA-2202-112 25-pin Micro-SIM and TF slot 

===P.10 CAMERA===

* J1000: T03-1025-FG01 27-pin connector to the rear camera. '''''Note:''''' The schematic says “GC2035-200W”, which is a mistake because the rear camera is the OmniVision [http://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV6540].
* J1001: T03-1025-FG01 27-pin connector to the front camera. '''''Note:''''' The schematic says “GC2035-200W”, which is a mistake because the rear camera is the GalaxyCore [http://files.pine64.org/doc/datasheet/pinephone/GC2145%20CSP%20DataSheet%20release%20V1.0_20131201.pdf GC2145], not the GalaxyCore [https://g2g9w6w7.stackpathcdn.com/pdf-down/G/C/2/GC2035-GalaxyCore.pdf GC2035].
* U1000: Shanghai awinic technology [https://pdf1.alldatasheet.com/datasheet-pdf/view/1147538/AWINIC/AW3641EDNR/+014J75AXvUpOKG+GczEDzOOae+/datasheet.pdf AW3641EDNR] flash LED driver with programmable timer and PWM dimming torch mode, 1A, 8 current levels. 

===P.11 LCM/CTP===

<div style="margin-left:20px">'''''Note:''''' "LCM/CTP" means "liquid crystal display monitor/capacitive touch panel". An LCM generally includes an LCD screen + LED backlight + PCB with the LCD controller + frame.</div>

* J1100: FPC24-PT05B, OK-24F-04 28-pin connector to the MIPI-DSI LCD
* LED2: RGB LED
* J1101: CON6-0.5, TP_6PIN-ZQ01 8-pin connector to the capacitive touch panel controller '''''Note:''''' The label says that the connector has 6-pins, but the schematic shows 8-pins.
* ED1100, ED1101, ED1102, ED1103: Will Semiconductor [https://pdf1.alldatasheet.com/datasheet-pdf/view/1136979/WILLSEMI/ESD5451X/+01_7-9BXuHlLuHRMflaL..hDk+/datasheet.pdf ESD5451X] 1-line, bi-directional, transient voltage suppressor, EDS protection up to ±30kV and 8A.
* U1100: Chipown [http://www.datasheet39.com/download.php?id=924200 AP3127B025] step-up DC/DC converter series, white LED backlight driver, 6-pin SOT-23-6L package.

===P.12 SENSORS/MT/KEY===

* J1200: 8-pin connector to test points
* ED1200, ED1201: Will Semiconductor [https://pdf1.alldatasheet.com/datasheet-pdf/view/1136979/WILLSEMI/ESD5451X/+01_7-9BXuHlLuHRMflaL..hDk+/datasheet.pdf ESD5451X] 1-line, bi-directional, transient voltage suppressor, EDS protection up to ±30kV and 8A.
* U1200: STmicroelectronics [https://www.st.com/en/mems-and-sensors/lis3mdl.html LIS3MDL] ultra-low-power three-axis magnetometer, LGA-12 2.0x2.0x1.0 mm [https://www.st.com/resource/en/datasheet/lis3mdl.pdf [datasheet]] '''''Note:''''' The LIS3MDL is currently unavailable, so it [https://www.pine64.org/2021/03/15/march-update/#comment-4273 has been replaced] in the PinePhone Beta Edition with the Voltafield AF8133L e-Compass, which is unlisted on the Voltafield web site, but the [http://www.voltafield.com/products01.html AF8133J] is listed. Presumably U1200 will be unpopulated and U1203 will be populated in the Beta Edition, since they appear to be alternatives.
* U1201: SensorTek [https://web.archive.org/web/20190601120915/http://www.sensortek.com.tw/en/product/Proximity_Sensor_with_ALS.html STK3311-A] proximity and ambient light sensor (large gap) with built-in infrared LED, DFN-8 3.94x2.36x1.35 mm [https://cdn.datasheetspdf.com/pdf-down/S/T/K/STK3310-Sensortek.pdf [datasheet]]
* U1202: TDK InvenSense [https://invensense.tdk.com/products/motion-tracking/6-axis/mpu-6050/ MPU6050] six-axis, low-power MEMS gyroscope and accelerometer, QFN-24 4x4x0.9 mm [https://invensense.tdk.com/wp-content/uploads/2015/02/MPU-6000-Datasheet1.pdf [datasheet]]
* U1203: Asahi Kasei Microdevices (AKM) [https://static6.arrow.com/aropdfconversion/19f6bc6e0891877d596c7b1da69df3d2ea4388a5/31ak09911.pdf AK09911] 3-axis electronic compass IC with Hall sensor, 8-pin WL-CSP (BGA), 1.2×1.2×0.5 mm '''''or''''' Voltafield Technology Corp. (VTC) [http://www.winforcetek.com/pdf/PD-DST-0011-00%20AF8133J%20V03.pdf AF8133J] 3-axis electronic compass with proprietary anisotropic magneto resistive (AMR) technology, 8-pin WLCSP 1.2x1.2x0.5 mm '''''Note:''''' These parts appear to be alternatives to be used if the LIS3MDL is unavailable, so U1203 was probably unpopulated in BraveHeart and the Community Editions, but will be populated in the Beta Edition.
* U1204: Bosch Sensortek [https://datasheet.lcsc.com/szlcsc/1912111437_Bosch-Sensortec-BMI120_C437657.pdf BMI120] 3-axis gyroscope and accelerometer, LGA-14 2.5x3.0x0.83 mm '''''Note:''''' Listed as “NC/BMI120”, where “NC” probably means “not connected”, so there may be circuits in the PCB for the part, but it is not placed on the board. This is probably an alternative to the TDK InvenSense MPU6050, in case it isn't available or costs too much.
* Q1200: Toshiba [https://toshiba.semicon-storage.com/info/docget.jsp?did=10004&prodName=SSM3K35MFV SSM3K35MFV] field-effect transistor, silicon N-channel MOS type
* D1200: Torex [https://www.torexsemi.com/file/xbs104s14r/XBS104S14R.pdf XBS104S14] Schottky barrier diode, 1A, 40V, SOD-123A package
* J1201: 2-pin connector to a motor, 1x1.8 mm '''''Note:''''' Presumably this is a vibration motor. 

===P.13 DIGITAL VIDEO===

* J1300: OK-50F-04 40-pin connector '''''Note:''''' This part is probably produced by Shenzhen Yaqi Technology Co., which is part of OCN in Taiwan, and uses the Archie brand name.
* U1304: Analogix [https://www.analogix.com/en/system/files/AA-002281-PB-6-ANX7688_Product_Brief_0.pdf ANX7688] HDMI to USB-C bridge with MUX, converts HDMI 2.0 to DisplayPort Alternate Mode, USB-C Power Delivery (PD), BGA-64. '''''Note 1:''''' The schematic lists this part as “ANX7688S”, but it is unclear what the “S” at the end stands for. '''''Note 2:''''' xnux.eu provides [https://xnux.eu/devices/feature/anx7688.html more info] on the ANX7688, including flashing the firmware.
* U1300: America Techcode Semiconductor [http://techcodesemi.com/datasheet/TD6817.pdf TD6817] 1.5MHz 2A synchronous step-down regulator dropout, SOT23-5 package '''''or''''' Diodes Incorporated [https://media.digikey.com/pdf/Data%20Sheets/Diodes%20PDFs/AP3406.pdf AP3406K-ADJTRG1] buck switching regulator IC positive adjustable 0.6V 650mA [https://media.digikey.com/pdf/Data%20Sheets/Diodes%20PDFs/AP3406.pdf [datasheet]]
* U1302: LowPowerSemi [https://cdn.datasheetspdf.com/pdf-down/L/P/W/LPW5206-LowPowerSemi.pdf LPW5206H] USB power loading switch, N-channel MOSFET, SOT23-5 package
* U1303: Texas Instruments [https://www.ti.com/lit/ds/symlink/txb0104.pdf TXB0104YZT] 4-bit bidirectional voltage-level translator with automatic direction sensing and ±15-kV ESD protection, 12-pin DSBGA 1.40×1.90 mm
* Q1300, Q1301, Q1302, Q1304, Q1305: Toshiba [https://toshiba.semicon-storage.com/info/docget.jsp?did=10004&prodName=SSM3K35MFV SSM3K35MFV] field-effect transistor, silicon N-channel MOS type
* U1305, U1309: Will Semiconductor [https://pdf1.alldatasheet.com/datasheet-pdf/view/1140651/WILLSEMI/WS4621C/+014QJJ4XuHlLuHRMfdaDGDwO+/datasheet.pdf WS4621C-1X1] 2A, 38 mΩ, 290nA quiescent current and 70nA standby current load switch, CSP-4L 1x1 mm.
* U1308: Shanghai awinic technology [https://pdf1.alldatasheet.com/datasheet-pdf/view/1147535/AWINIC/AW3632/+014J758XvUpOKG+GczEww+/datasheet.pdf AW3632] high efficiency, low profile, fixed 5V output pump power supply, QFN-8 package
* X1300: Mercury United Electronics [https://rf.cdiweb.com/products/detail/x322500018p3020207060r-mercury-united-electronics-inc/71942/ X3225] 27.000 MHz crystal oscillator 

===P.14 WIFI+BT===

* U1400: Realtek [http://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf RTL8723CS] 802.11 b/g/n, single-band (2.4 GHz), Bluetooth 4.0, with SDIO for WiFi and UART for Bluetooth, LGA-40 12x12x1.6 mm.
* X1400: 24Mhz ±10ppm crystal oscillator
* D1400: SXSEMI [http://sxsemi.com/upfile/AU0511P1.pdf AU0511P1] low capacitance ESD protection diode, SOD-882
* ANT1400 Antenna 

===P.15 MODEM-4G===

* U1500: [https://www.quectel.com/product/lte-eg25-g/ Quectel EG25-G][[File:Quectel_EG25-G_LTE_Standard_Specification_V1.3.pdf]] GSM/UMTS/LTE cellular modem and GNSS (GPS/Galileo/GLONASS/BeiDou/QZSS, with A-GPS), LGA-144 9.0x32.0x2.4 mm
* U1502, 1503, 1504: Texas Instruments [https://www.ti.com/lit/ds/symlink/txb0104.pdf TXB0104YZT] 4-bit bidirectional voltage-level translator with automatic direction sensing and ±15-kV ESD protection, 12-pin DSBGA 1.40×1.90 mm
* Q1501, Q1503, Q1504, Q1505: Toshiba [https://toshiba.semicon-storage.com/info/docget.jsp?did=10004&prodName=SSM3K35MFV SSM3K35MFV] field-effect transistor, silicon N-channel MOS type
* J1500, J1502: MRF004-P01A 4-pin connector
* Q1500: Will Semiconductor [http://monitor.espec.ws/files/wpm1481_186.pdf WPM1481] single P-channel, -12V, -5.5A, power MOSFET '''''Note:''''' The documentation shows 6 pins, but the schematic shows 8 pins.
 

===Component Counts===

{| class="wikitable"
! Type of component !! Main PCB !! USB PCB
|-
| Antenna connectors (ANT''xxx'') || 6 || 4
|-
| Capacitors (C''xxx'') || 296 || 16
|-
| Diodes (D''xxx'') || 5 || 0
|-
| Zener diodes (ED''xxx'') || 17 || 0
|-
| Ferrite beads (FB''xxx'') || 6 || 0
|-
| Wire links / connectors (J''xxx'') || 14 || 4
|-
| Resistors (R''xxx'') || 222 || 0
|-
| Inductors (L''xxx'') || 15 || 0
|-
| Transistors (Q''xxx'') || 16 || 19*
|-
| Switches (SW''xxx'') || 1 || 0
|-
| Test points (T''xxx'') || 27 || 3
|-
| Integrated circuits (U/DU''xxx'') || 24† || 2
|-
| Crystal oscillators (X''xxx'') || 5 || 0
|-
| '''Total without test points''' || '''627''' || '''45'''
|-
| '''Total with test points''' || '''654''' || '''48'''
|}
 

Here is how the PinePhone compares with the Librem 5 in terms of components:

{| class="wikitable"
! Type of component !! Librem 5 main !! Librem 5 USB !! PinePhone main !! PinePhone USB
|-
| Antenna connectors (ANT''xxx'') || 3 || 2 || 6 || 4
|-
| Capacitors (C''xxx'') || 521 || 11 || 296 || 16
|-
| Diodes (D/TVS/ED''xxx'') || 59 || 1 || 22 || 0
|-
| Connectors (J/CON''xxx'') || 26 || 10 || 14 || 4
|-
| Resistors (R/F''xxx'') || 348 || 8 || 222 || 0
|-
| Inductors (L/FB''xxx'') || 79 || 7 || 21 || 0
|-
| Transistors (Q''xxx'') || 17 || 0 || 16 || 19*
|-
| Switches (SW''xxx'') || 5 || 0 || 1 || 0
|-
| Test points (T/TC/TP/TS/TV''xxx'') || 126 || 4 || 27 || 3
|-
| Integrated circuits (U/DU''xxx'') || 65 || 2 || 24† || 2
|-
| Crystal oscillators (Y/X''xxx'') || 10 || 0 || 5 || 0
|-
| '''Total without test points''' ||'''1133'''||'''41'''||'''627'''||'''45'''
|-
| '''Total with test points''' ||'''1259'''||'''45'''||'''654'''||'''48'''
|}

<nowiki>*</nowiki> 18 parts for the PinePhone USB-C port are labeled as T''xxx'' in the schematic with the image of transistors, but it is possible that these are resistors and capacitors.

† There are 26 U/DU''xxx'' listed in the PinePhone schematic, but the two extra are for an alternative magnetometer (U1200 / U1203) and an alternative gyroscope and accelerometer (U1202 / U1204) which are unpopulated.

Source: [https://forums.puri.sm/t/component-counts-in-the-librem-5-and-pinephone/11240 Amos Batto]

===Other components not in the schematics===

* SGMICRO [http://www.sg-micro.com/uploads/soft/20190829/1567071622.pdf SGM3140] 500mA buck/boost charge pump LED driver for camera flash and torch, TDFN-10 3x3x0.75 mm '''''Note:''''' The [[PinePhone#Components|PinePhone page]] lists the SGM3140, but the schematics contain the U1000: awinic AW3641EDNR, so it is unclear why the SGM3140 is needed.
* Goodix [http://files.pine64.org/doc/datasheet/pinephone/GT917S-Datasheet.pdf GT917S] touch controller
* Sitronix [http://files.pine64.org/doc/datasheet/pinephone/ST7703_DS_v01_20160128.pdf ST7703] MIPI LCD driver
* Xingbangda [https://lkml.org/lkml/2020/6/16/1654 XBD599] 5.99″ IPS LCD, 720x1440 pixels, 16.7M colors, hardened glass

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

PinePhone

2021-08-20T13:07:54Z

MikeBanon: fix the Quectel document references

[[File:PinePhone Beta Edition.png|500px|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 Linux experience.

Bear in mind that the software for Linux on phones 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 [https://www.pine64.org/philosophy/ PINE64 philosophy]), and currently that support resources are sparse - the best way to get support quickly is to ask in the community chat! Please only contact PINE64 directly if questions couldn't be solved via the community chat or this wiki.

== First time installation ==

{{Hint|Do not insert an empty micro SIM adapter into the phone, as it will get stuck on the contact pins.}}

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 until this is removed and the modem, WiFi and Bluetooth will not work until the battery is connected.

The PinePhone's SIM slot only accepts a micro SIM, please do not insert a nano SIM without an adapter. An adapter from a nano to a micro SIM might be included under tape in the camera notch of the phone's packaging. The SIM card has to be placed in the lower slot, while the microSD has to be placed in the upper slot. Notice: Do not insert an empty micro SIM adapter into the phone, as it will get stuck on the contact pins.

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
# Remove the battery (if the battery is stuck in the device please check [[PinePhone_FAQ#The_battery_is_stuck_inside_the_phone|this]] paragraph for a fix)
# Peel off the clear plastic sticker below it, which isolates the charging contacts
# Reinsert the battery

<gallery mode="nolines" widths="400px" heights="400px">
Image:Pinephone_warning.png|A protection foil isolates the battery for the shipping.
Image:Pinephone_backside.png|The microSD belongs in the upper slot, the micro SIM in the lower slot.
</gallery>

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

== 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|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 killswitch 6 is deactivated)
* '''Communication:'''
** '''[[#Modem|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
* '''Killswitches:''' Modem, WiFi & Bluetooth, Microphone, Cameras
* '''[[#Battery|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 ==

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

* [[Project Anakin]]
* [[Project Don't be evil|"Project Don't Be Evil"]] – development kit (devkit)
* [[PinePhone v1.0 - Dev|PinePhone v1.0]] – developer batch
* [[PinePhone v1.1 - Braveheart|PinePhone v1.1]] – Braveheart
* [[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 ==

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

=== USB-C connector ===

The USB-C can be used to power the device, and offers USB2 host and OTG possibilities, 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, 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 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].

=== Community-built accessories ===
* [https://www.thingiverse.com/thing:4654013 PinePhone Development Stand at Thingverse]
* [https://www.thingiverse.com/thing:4658870 PinePhone Hard Case by _The3DmaN_ at Thingverse]
* [https://www.thingiverse.com/thing:4651177 PinePhone Hard Case by blitzaxt at Thingverse]

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

== Killswitch configuration ==

[[File:PinePhone Kill Interruptors de Maquinari del PinePhone 4529.jpg|320px|thumb|right|Detail of DIP switch]]

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 ==
{{Hint|The EG25-G modem and the RTL8723CS WiFi and Bluetooth combo do not work without battery power, even when enough power is supplied to the PinePhone via the USB Type-C port.}}

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

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.

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. The software <code>minicom</code> can be used to send the commands under Linux.

To connect with the modem under Linux:

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

=== AT commands ===

A list of documented AT commands can be found in the [[File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_AT_Commands_Manual_V2.0.pdf]] 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].

=== VoLTE ===

The PinePhone's modem supports VoLTE and comes with a few VoLTE profiles preloaded. Most OSes 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 OSes.

=== Firmware update ===

{{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 modem firmware can be updated to the latest version if it is outdated and ''dmesg'' returns the following message:

<pre>modem-power serial1-0: Your modem has an outdated firmware. Latest know version is EG25GGBR07A08M2G_[...]. Consider updating.</pre>

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

<pre>git clone https://github.com/Biktorgj/quectel_eg25_recovery</pre>

After cloning the directory, open it with cd:

<pre>cd quectel_eg25_recovery</pre>

Then run qfirehose, which starts the flashing process:

<pre>sudo ./qfirehose -f ./</pre>

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 is controlled via a separate set of AT commands. The AGPS 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. While the hardware supports AGPS data upload, it isn't yet implemented in current distributions. There is a [https://gist.github.com/alastair-dm/263209b54d01209be28828e555fa6628 proof of concept script] which can be made to work, but support needs to be added to ModemManager, oFono etc. before it will be easy to use.

Basic testing of GNSS reception can be done by using the AT command interface (/dev/ttyUSB2) from a terminal progam like minicom and the data output interface (/dev/ttyUSB1) to feed NMEA data into gpsmon or some other progam 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

=== Voice mail ===

Some phone operating systems may not have support for accessing your voicemail by holding down the 1 key. If you are in Canada and using rogers or a rogers associated carrier (such as ''Chatr''), you can access your voice mail by calling an external number, see: https://www.howardforums.com/showthread.php/913346-Rogers-GSM-Voicemail-Retrieval-Numbers

In America, AT&T also has support for accessing your voicemail via an external phone number: https://www.att.com/support/article/wireless/KM1009101/

In Canada, Rogers voicemail can be called by dialing *98

== 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 Phillip’s 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 Phillip’s 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.

Download the latest ANX7688 firmware image on the phone:

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

Execute 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 dimensions: 12x6x2 mm. Compatible with Xiaomi Mi2 / Mi3 / Mi4, Lenovo A536 and others, see [https://forum.pine64.org/showthread.php?tid=12046&pid=85698#pid85698 here]
* Loudspeaker dimensions: 15x11x3 mm. Compatible with Nokia N91, Lenovo A536 and others, see [https://forum.pine64.org/showthread.php?tid=12046&pid=85698#pid85698 here]
* Proximity sensor rubber isolator

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

== Developer works ==

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

PineModems

2021-08-20T13:06:48Z

MikeBanon: Add one more reference document

= Modems used in Pine64 boards and devices =

== Quectel EG25-G Modem ==

Quectel EG25-G is an LTE Cat 4 module optimized specially for M2M and IoT applications. It is used in the PinePhone.

* Specifications: [[File:Quectel_EG25-G_LTE_Standard_Specification_V1.3.pdf]]
* Hardware design: [[File:Quectel_EG25-G_Hardware_Design_V1.4.pdf]]
* AT Interface reference manual:
** 1.3 for EC25: [[File:Quectel_EC25&EC21_AT_Commands_Manual_V1.3.pdf]]
** 2.0 for EC25 and EG25-G: [[File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_AT_Commands_Manual_V2.0.pdf]]
* AT Interface file operations: [[File:Quectel_EC2xEG25-GEG9xEM05_FILE_AT_Commands_Manual_V1.0.pdf]]
* GNSS Application note: [[File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_GNSS_Application_Note_V1.3.pdf]]

=== Specifications ===

{| class="wikitable"
| Processor Family || Qualcomm MDM9607
|-
| CPU || Qualcomm MDM9207
|-
| Cores || 1 ACPU Core, Qualcomm Hexagon DSP
|-
| Total RAM || 256Mb
|-
| Total flash space || 256Mb
|-
| Available RAM for the ACPU || 160Mb
|}

=== NAND Partition table layout ===

{| class="wikitable"
! Index
! Name
! Description
|-
| MTD0 || <code>SBL</code>
| Secondary Bootloader, called from the BootROM. Used to start the TrustZone kernel and the Application Bootloader (LK). Also used to enter Quectel's recovery mode
|-
| MTD1 || <code>mibib</code>
| Unknown, used by the DSP
|-
| MTD2 || <code>EFS2</code>
| Unexplored, probably NVRAM data, Used by the DSP
|-
| MTD3 || <code>sys_rev</code>
| Unexplored
|-
| MTD4 || <code>rawdata</code>
| This is where FOTA update data exists before being commited to system or recoveryfs partitions
|-
| MTD5 || <code>tz</code>
| TrustZone kernel
|-
| MTD6 || <code>rpm</code>
| Resource / Power Manager
|-
| MTD7 || <code>cust_info</code>
| Unexplored
|-
| MTD8 || <code>aboot</code>
| Application Bootloader. Uses [https://github.com/littlekernel/lk LK] (LittleKernel, LK embedded kernel) as the bootloader. By default it allows flashing unsigned images but won't allow booting them, soft-bricking the modem until you enter EDL mode
|-
| MTD9 || <code>boot</code>
| [https://www.openembedded.org/wiki/Main_Page OpenEmbedded] boot kernel + DTB
|-
| MTD10 || <code>recovery</code>
| Recovery kernel (normally unused)
|-
| MTD11 || <code>modem</code>
| ADSP firmware blobs
|-
| MTD12 || <code>misc</code>
| Unexplored
|-
| MTD13 || <code>recoveryfs</code>
| Recovery filesystem image (FOTA updates)
|-
| MTD14 || <code>usr_data</code>
| User data partition (<code>/data</code> when mounted by OpenEmbedded)
|-
| MTD15 || <code>sec</code>
| Used to blow fuses in the mdm9207 from images generated by Qualcomm Sectools
|-
| MTD16 || <code>system</code>
| Linux OpenEmbedded root image, formatted in UBIFS (Unsorted Block Image File System, [https://en.wikipedia.org/wiki/UBIFS Wikipedia])
|}

=== Firmware Recovery ===

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

The System partition is mounted as read-only mode, but the data partition is writable. It might be possible, if there's an unexpected reset or power is lost while running, that the data partition gets corrupt and thus unable to boot.

[[File:Pinephone-EG25-Recovery.jpg|thumb|right|PinePhone USB_BOOT test points]]

The modem has 4 different boot modes:
* Normal boot
* Recovery mode (used by the modem usually to install a FOTA update)
* Fastboot mode
* Qualcomm EDL Mode

If the modem is unable to boot, depending on the type of crash, it might:
* not show anywhere (USB device missing)
* or malfunction (no radio but USB working)
* or enter EDL mode, if the entire flash is corrupt.

'''Boot the device in EDL mode'''

To check if the device is booted in EDL mode, run <code>lsusb</code> (a part of the <code>usbutils</code> package) in a terminal and inspect the output. You should see the following device listed:

Bus 003 Device 003: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

In any scenario, the modem can be triggered to enter EDL mode by shorting two test pins on the PinePhone motherboard.

# Power off the phone
# short the two test points
# boot the phone while keeping the test points shorted until fully booted up, at least until you hear the camera clicking twice (which is normally when the modem is powered).

'''Get the Firmware Recovery Package'''

The Firmware Recovery Package is at: https://github.com/Biktorgj/quectel_eg25_recovery

Either clone its repo with git, or download its archive & unzip it.

As you should have no access to the Internet on PinePhone when its modem need a Recovery, you can fetch it on other devices and copy it to the Pinephone.

'''Execute the Quectel QFirehose utility'''

Once in EDL mode, open a terminal, navigate to the root directory of the recovery package, and run:

* If you use an ARM64 distribution (most likely): <code>sudo ./qfirehose -f ./</code> or <code>sudo ./qfirehose_arm64 -f ./</code>
* If you use an ARMHF (32 bit) distribution: <code>sudo ./qfirehose_armhf -f ./</code>

It will reboot the modem after finished. After about 30 seconds, it will get back up and running.

=== Bootloader unlocking ===

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

The Modem has a locked bootloader. It won't allow to boot unsigned Kernel images, but will allow to flash them, making it easy to brick the modem. To fix this, you can flash an unlocked bootloader, which will then allow you to do as you please with the hardware.

Unlocked bootloader:
* Source code: https://github.com/Biktorgj/quectel_lk
* Prebuilt binary releases: https://github.com/Biktorgj/quectel_lk/releases

=== Custom Kernels and system images ===

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

Custom kernel builds and system images can be created for the modem, though they require a couple of things to be correctly built and be bootable.

* The source code release for the kernel provided by the manufacturer is incomplete and won't build
* Common Android tools like mkbootimg and dtbtool won't build a bootable image, even if the kernel is correctly compiled and all the DTBs attached.
* Further, there's no source for the OpenEmbedded parts, so building a new system image must be done from scratch, and retrieving the mandatory binary blobs to use the ADSP part of the modem.

There's a '''work in progress''' SDK to allow creating custom kernels and system images, which can be downloaded from the following repository: https://github.com/Biktorgj/pinephone_modem_sdk

See its readme for infomations and instructions. Once downloaded, you should run the <code>init.sh</code> script, which will create all the base directories and download all the different repositories required to build. After the initial setup is complete, run<code>make</code> without arguments to list the available options.

[[Category:PinePhone]]

File:Quectel EG25-G Hardware Design V1.4.pdf

2021-08-20T13:02:09Z

MikeBanon:

File:Quectel EC2x&EG9x&EG2x-G&EM05 Series GNSS Application Note V1.3.pdf

2021-08-20T13:00:16Z

MikeBanon:

PineModems

2021-08-20T12:44:38Z

MikeBanon: fix the Quectel document references

= Modems used in Pine64 boards and devices =

== Quectel EG25-G Modem ==

Quectel EG25-G is an LTE Cat 4 module optimized specially for M2M and IoT applications. It is used in the PinePhone.

* Specifications: [[File:Quectel_EG25-G_LTE_Standard_Specification_V1.3.pdf]]
* Hardware design: [[File:EG25-G_Hardware_Design_V1.4.pdf]]
* AT Interface reference manual:
** 1.3 for EC25: [[File:Quectel_EC25&EC21_AT_Commands_Manual_V1.3.pdf]]
** 2.0 for EC25 and EG25-G: [[File:Quectel_EC2x&EG9x&EG2x-G&EM05_Series_AT_Commands_Manual_V2.0.pdf]]
* AT Interface file operations: [[File:Quectel_EC2xEG25-GEG9xEM05_FILE_AT_Commands_Manual_V1.0.pdf]]

=== Specifications ===

{| class="wikitable"
| Processor Family || Qualcomm MDM9607
|-
| CPU || Qualcomm MDM9207
|-
| Cores || 1 ACPU Core, Qualcomm Hexagon DSP
|-
| Total RAM || 256Mb
|-
| Total flash space || 256Mb
|-
| Available RAM for the ACPU || 160Mb
|}

=== NAND Partition table layout ===

{| class="wikitable"
! Index
! Name
! Description
|-
| MTD0 || <code>SBL</code>
| Secondary Bootloader, called from the BootROM. Used to start the TrustZone kernel and the Application Bootloader (LK). Also used to enter Quectel's recovery mode
|-
| MTD1 || <code>mibib</code>
| Unknown, used by the DSP
|-
| MTD2 || <code>EFS2</code>
| Unexplored, probably NVRAM data, Used by the DSP
|-
| MTD3 || <code>sys_rev</code>
| Unexplored
|-
| MTD4 || <code>rawdata</code>
| This is where FOTA update data exists before being commited to system or recoveryfs partitions
|-
| MTD5 || <code>tz</code>
| TrustZone kernel
|-
| MTD6 || <code>rpm</code>
| Resource / Power Manager
|-
| MTD7 || <code>cust_info</code>
| Unexplored
|-
| MTD8 || <code>aboot</code>
| Application Bootloader. Uses [https://github.com/littlekernel/lk LK] (LittleKernel, LK embedded kernel) as the bootloader. By default it allows flashing unsigned images but won't allow booting them, soft-bricking the modem until you enter EDL mode
|-
| MTD9 || <code>boot</code>
| [https://www.openembedded.org/wiki/Main_Page OpenEmbedded] boot kernel + DTB
|-
| MTD10 || <code>recovery</code>
| Recovery kernel (normally unused)
|-
| MTD11 || <code>modem</code>
| ADSP firmware blobs
|-
| MTD12 || <code>misc</code>
| Unexplored
|-
| MTD13 || <code>recoveryfs</code>
| Recovery filesystem image (FOTA updates)
|-
| MTD14 || <code>usr_data</code>
| User data partition (<code>/data</code> when mounted by OpenEmbedded)
|-
| MTD15 || <code>sec</code>
| Used to blow fuses in the mdm9207 from images generated by Qualcomm Sectools
|-
| MTD16 || <code>system</code>
| Linux OpenEmbedded root image, formatted in UBIFS (Unsorted Block Image File System, [https://en.wikipedia.org/wiki/UBIFS Wikipedia])
|}

=== Firmware Recovery ===

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

The System partition is mounted as read-only mode, but the data partition is writable. It might be possible, if there's an unexpected reset or power is lost while running, that the data partition gets corrupt and thus unable to boot.

[[File:Pinephone-EG25-Recovery.jpg|thumb|right|PinePhone USB_BOOT test points]]

The modem has 4 different boot modes:
* Normal boot
* Recovery mode (used by the modem usually to install a FOTA update)
* Fastboot mode
* Qualcomm EDL Mode

If the modem is unable to boot, depending on the type of crash, it might:
* not show anywhere (USB device missing)
* or malfunction (no radio but USB working)
* or enter EDL mode, if the entire flash is corrupt.

'''Boot the device in EDL mode'''

To check if the device is booted in EDL mode, run <code>lsusb</code> (a part of the <code>usbutils</code> package) in a terminal and inspect the output. You should see the following device listed:

Bus 003 Device 003: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

In any scenario, the modem can be triggered to enter EDL mode by shorting two test pins on the PinePhone motherboard.

# Power off the phone
# short the two test points
# boot the phone while keeping the test points shorted until fully booted up, at least until you hear the camera clicking twice (which is normally when the modem is powered).

'''Get the Firmware Recovery Package'''

The Firmware Recovery Package is at: https://github.com/Biktorgj/quectel_eg25_recovery

Either clone its repo with git, or download its archive & unzip it.

As you should have no access to the Internet on PinePhone when its modem need a Recovery, you can fetch it on other devices and copy it to the Pinephone.

'''Execute the Quectel QFirehose utility'''

Once in EDL mode, open a terminal, navigate to the root directory of the recovery package, and run:

* If you use an ARM64 distribution (most likely): <code>sudo ./qfirehose -f ./</code> or <code>sudo ./qfirehose_arm64 -f ./</code>
* If you use an ARMHF (32 bit) distribution: <code>sudo ./qfirehose_armhf -f ./</code>

It will reboot the modem after finished. After about 30 seconds, it will get back up and running.

=== Bootloader unlocking ===

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

The Modem has a locked bootloader. It won't allow to boot unsigned Kernel images, but will allow to flash them, making it easy to brick the modem. To fix this, you can flash an unlocked bootloader, which will then allow you to do as you please with the hardware.

Unlocked bootloader:
* Source code: https://github.com/Biktorgj/quectel_lk
* Prebuilt binary releases: https://github.com/Biktorgj/quectel_lk/releases

=== Custom Kernels and system images ===

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

Custom kernel builds and system images can be created for the modem, though they require a couple of things to be correctly built and be bootable.

* The source code release for the kernel provided by the manufacturer is incomplete and won't build
* Common Android tools like mkbootimg and dtbtool won't build a bootable image, even if the kernel is correctly compiled and all the DTBs attached.
* Further, there's no source for the OpenEmbedded parts, so building a new system image must be done from scratch, and retrieving the mandatory binary blobs to use the ADSP part of the modem.

There's a '''work in progress''' SDK to allow creating custom kernels and system images, which can be downloaded from the following repository: https://github.com/Biktorgj/pinephone_modem_sdk

See its readme for infomations and instructions. Once downloaded, you should run the <code>init.sh</code> script, which will create all the base directories and download all the different repositories required to build. After the initial setup is complete, run<code>make</code> without arguments to list the available options.

[[Category:PinePhone]]

File:Quectel EC2x&EG9x&EG2x-G&EM05 Series AT Commands Manual V2.0.pdf

2021-08-20T12:42:51Z

MikeBanon:

File:Quectel EC2xEG25-GEG9xEM05 FILE AT Commands Manual V1.0.pdf

2021-08-20T12:41:28Z

MikeBanon:

File:EC2x&EG9x&EG2x-G&EM05 Series AT Commands Manual V2.0.pdf

2021-08-20T12:39:13Z

MikeBanon:

File:Quectel EC25&EC21 AT Commands Manual V1.3.pdf

2021-08-20T12:38:16Z

MikeBanon:

File:EG25-G Hardware Design V1.4.pdf

2021-08-20T12:32:42Z

MikeBanon:

File:Quectel EG25-G LTE Standard Specification V1.3.pdf

2021-08-20T12:30:47Z

MikeBanon: