PINE64 - User contributions [en]

ROCKPro64

2022-11-19T04:00:15Z

PineCone: Nobody uses RJ-45S ports anymore.

<div style="float: right; margin-left: 1ch; max-width: 24em;">__TOC__</div>

The [https://www.pine64.org/rockpro64/ '''ROCKPro64'''] is the most powerful Single Board Computer released by PINE64. It is powered by a Rockchip RK3399 Hexa-Core (dual ARM Cortex A72 and quad ARM Cortex A53) 64-Bit Processor with a Mali T-860 Quad-Core GPU.

Key features include a PCIe x4 open ended slot, the use of LPDDR4 RAM, and industry standard heatsink mounting holes.

The ROCKPro64 is equipped with 2GB or 4GB LPDDR4 system memory, and 128Mb SPI boot Flash. There is also an optional eMMC module (up to 128GB) and microSD slot for booting. The board is equipped with 1x USB 3.0 type C Host with DP 1.2, 1x USB 3.0 type A Host, 2x USB 2.0 Host, Gigabit Ethernet, PI-2 GPIO Bus, MiPi DSI interface, eDP interface, touch Panel interface, stereo MiPi CSI interface, as well as many other device interfaces such as UART, SPI, I2C, for makers to integrate with sensors and other peripherals. Many different Operating Systems (OS) are freely available from the open source community, such as Android, Linux (Ubuntu, Debian, Arch), and BSD.

= Board Pictures =
<gallery heights="400" mode="packed">
Image:ROCKPro64v21FRONT.jpg|A hi-res picture of v2.1 front.|alt="A hi-res picture of v2.1 front."
Image:ROCKPro64v21REAR.jpg|A hi-res picture of v2.1 rear.|alt="A hi-res picture of v2.1 rear."
Image:FLIR 20220619 125451 686.jpg|A thermal image of v2.1 front (upside-down).|alt="A thermal image of v2.1 front (upside-down)."
</gallery>

= Board Layout =
[[File:ROCKPro64_annotated.jpg|An annotated ROCKPro64]]

== Main Chips ==
* RK3399 system-on-chip (1)
* LPDDR4 SDRAM 1 (18)
* LPDDR4 SDRAM 2 (3)
* SPI NOR flash memory (17)
* RK808 power management (near 19)
* RTL8211 ethernet transceiver (near 25)
* ES8316 Sound Codec (on rear of board)
* The heatsink mounting holes around the RK3399 are 59 mm apart

== Switches ==

The Power button (11, SW3): is the same as on your mobile phone - press and release after about 1 second to power on. Press and hold for about 3 seconds to power off.

The Reset button (10, SW901): perfoms a reset.

The Recover button (28, SW900): used to enter maskrom mode.

== Connectors, Sockets and Headers ==
{| class="wikitable sortable" style="line-height: 1.4;"
|- style="font-size: .9em;"
! Diagram !! Schematic designator !! Silkscreen label !! Number of pins !! Description
|-
| style="text-align: center;" | 2 || U39 || PI-2-bus || style="text-align: center;" | 40 || Pi-2 bus
|-
| style="text-align: center;" | 4 || J8 || +FAN- || style="text-align: center;" | 2 || PWM controlled fan header
|-
| style="text-align: center;" | 5 || J10 || SPDIF || style="text-align: center;" | 3 || SPDIF header
|-
| style="text-align: center;" | 6 || U6 || +RTC- || style="text-align: center;" | 2 || RTC battery backup header
|-
| style="text-align: center;" | 7 || U31 || Wifi-BT || style="text-align: center;" | 16 || SDIO WIFI/BT module-MIMO 2
|-
| style="text-align: center;" | 8 || USB3 || || style="text-align: center;" | 9 || USB-3 and USB Type C
|-
| style="text-align: center;" | 9 || USB1 || || style="text-align: center;" | 2×4 || Dual USB-2
|-
| style="text-align: center;" | 12 || IR1 || IR || style="text-align: center;" | 3 || infrared receiver socket
|-
| style="text-align: center;" | 13 || J16 || Headphone+mic || style="text-align: center;" | 4 || Headphone + mic 3.5mm jack
|-
| style="text-align: center;" | - || CON16 || GND PWR RST GND || style="text-align: center;" | 4 || Power & reset, unpopulated header near Headphone jack
|-
| style="text-align: center;" | 14 || U29 || EMMC || style="text-align: center;" | 34 || eMMC connector
|-
| style="text-align: center;" | 14* || J13 || || style="text-align: center;" | 13 || TF-card, a.k.a. microSD (* under 14 on the bottom side)
|-
| style="text-align: center;" | 15 || U30 || || style="text-align: center;" | 14 || SDIO WIFI/BT module-MIMO 1
|-
| style="text-align: center;" | 16 || SW4 || || style="text-align: center;" | 2 || Jumper to [[#Disable eMMC]]
|-
| style="text-align: center;" | 19 || J15 || PCI || style="text-align: center;" | 64 || PCI-express X4 socket
|-
| style="text-align: center;" | 20 || J21 || DSI || style="text-align: center;" | 30 || DSI
|-
| style="text-align: center;" | 21 || J22 || EDP || style="text-align: center;" | 30 || LCD EDP
|-
| style="text-align: center;" | 22 || CON1 || TP || style="text-align: center;" | 6 || touch panel connector
|-
| style="text-align: center;" | 23 || CON15 || || style="text-align: center;" | 4 || DC out for SATA disk cable (direct connect from DC-IN)
|-
| style="text-align: center;" | 24 || J11 || DC-IN || style="text-align: center;" | 2 || Power input, positive tip; 12V/3A (minimum) recommended
|-
| style="text-align: center;" | 25 || U32 || || style="text-align: center;" | 8 || 8P8C
|-
| style="text-align: center;" | 26 || J14 || || style="text-align: center;" | 19 || HDMI
|-
| style="text-align: center;" | 27 || J17 || MIPI CAM || style="text-align: center;" | 32 || MIPI-1
|-
| style="text-align: center;" | 29 || J19 || MIPI CAM || style="text-align: center;" | 32 || MIPI-2
|-
| style="text-align: center;" | 30 || J18 || CIF || style="text-align: center;" | 26 || CIF
|}

== LEDs ==

A green LED next to the 12V input barrel connector will light as long as there is 12V applied to the connector. (Even if the RockPro64 is powered off.)

A white LED behind the reset button will light as long as the RockPro64 is running (it comes on a few seconds after power on, when control is passed to the operating system.)

A red LED behind the reset button is DIY - it is lit for example if the board is in OTG mode with an Ayufan image, or if an Android image is in standby mode.

Yellow and green LEDs on the LAN socket behave in a standard way.

== Jumpers ==
They are used for boot device selection, as described in the following section.

=== Disable eMMC ===

There is an unlabelled (on the PCB silk-screen) 2-pin jumper (16) between the eMMC socket (14) and the SPI chip (17). It is designated as SW4 on the [[#Board Information, Schematics and Certifications | schematic diagram]]. The default condition is OPEN (no jumper). It is useful for controlling the boot as follows:

Default boot device (with no SPI software) is eMMC, then SDcard. If both the eMMC and the SDcard contain bootable images then the eMMC can be disabled by installing the jumper. This completely removes the eMMC from the resulting OS. If you wish the eMMC to be visible in the booted OS the jumper should be removed 2 seconds after applying power (and before the white LED comes on).

The possible combinations are summarised in the table below.

* 1 = present
* 0 = not present

{| class="wikitable sortable" style="text-align: center;"
! µSD !! eMMC !! SW4 !! boot from
|-
| 0 || 0 || 0 || unsupported
|-
| 0 || 0 || 1 || unsupported
|-
| 0 || 1 || 0 || eMMC
|-
| 0 || 1 || 1 || unsupported
|-
| 1 || 0 || 0 || SDCard
|-
| 1 || 0 || 1 || SDCard
|-
| 1 || 1 || 0 || eMMC
|-
| 1 || 1 || 1 || SDCard
|}

=== Disable SPI (while booting) ===
There is a second possibility to jumper your ROCKPro64: If you mess-up your SPI and are unable to boot, jumpering pins 23 (CLK) and 25 pin (GND) on the PI-2-bus header will disable the SPI as a boot device. (This was taken from the IRC logs, 09 August 2018 @ 17:23) You have to remove the jumper 2 seconds after having started your RP64 (before the white LED turns ON) otherwise the SPI will be missing and you won't be able to flash it.
Ayufan images contain (at the moment) only one script for the SPI and the RP64, it's "rockpro64_reset_spi_flash". Other SPI scripts are dedicated to the R64 (as it is written on the name) and it will mess-up your RP64 SPI if you use them.

= Getting Started =

This section gives important information to get the board up and running.

== Software and OS Image Builds ==

In the [[ROCKPro64 Software Release]] page, you will find a complete list of currently supported Operating System images that work with the ROCKPro64, as well as other related software. The Software Release page has links to download the images as well as high level instructions to load each image.

The page includes many OS images and descriptions. Some links:

* [[ROCKPro64_Software_Release#Armbian | Armbian]]
* [[ROCKPro64_Software_Release#Debian | Debian]]
* [[ROCKPro64_Software_Release#DietPi | DietPi]]
* [[ROCKPro64_Software_Release#OpenMediaVault | Open Media Vault]]
* [[ROCKPro64_Software_Release#LibreELEC_.28KODI.29 | LibreELEC for KODI]]
* [[ROCKPro64_Software_Release#Retro-Center_R-Cade | R-Cade - Retro Gaming 4K Media Center]]
* [[ROCKPro64_Software_Release#Slackware | Slackware]]
* [[ROCKPro64_Software_Release#NextCloudPi | NextCloudPi]]
* [[ROCKPro64_Software_Release#Manjaro_ARM | Manjaro ARM]]
* [[ROCKPro64_Software_Release#OpenWrt | OpenWrt]]

Those linked OS support both microSD and eMMC Boot.

Please see the [[NOOB]] page for detailed discussion of what you need (prerequisites) as well as instructions if the high level instructions are insufficient.

== More Advanced Linux Bits ==

Some Linux tips are given below.

=== How to Update Your Linux ===

For Debian/Ubuntu images entering the following commands at a terminal prompt

<code>sudo apt-get update</code> 
<code>sudo apt-get upgrade</code>

will keep your installation up to date. To update Ayufan images to the next release (when available) use the following command

<code>sudo apt-get dist-upgrade</code>

If you are happy to update your system to pre-releases of Ayufan images then modify /etc/apt/sources.list.d/ayufan-rock64.list as per the comment in that file.

The kernel in Ayufan releases is under active development and, if you wish to install a later version, then it is best to use a package manager. In synaptic (for example), if you search for package names linux-image-4.4 you should see your currently installed version(s) as well as any more recent ones. Similarly if you wish to install the mainline kernel then searching for linux-image-4.18 will show you what is available. '''At the time of writing (August 2018) there are significant features missing from the mainline kernel for aarch64 processors (e.g. HDMI sound).'''

=== Useful Scripts ===
After you install an Ayufan image you will find some scripts in /usr/local/sbin/ and /usr/local/bin/ that may be useful. (Need to expand this section)

=== Video Playback ===
Hardware video acceleration is supported in recent kernels and user needs only to install the relevant Mesa packages/ports, specifically the Mesa DRI drivers for Mali GPUs (Midgard/Bifrost). One can confirm via software glxinfo, or having the library file such as .../lib/dri/panfrost_dri.so.

Ayufan has some old documentation on [https://github.com/ayufan-rock64/linux-build/blob/master/recipes/video-playback.md video playback here.] For your ROCKPro64 the install should be

<code>sudo apt-get install ffmpeg mpv libmali-rk-midgard-t86x-r14p0-gbm</code>

(These modules are included in the Ayufan deskop releases.) At which stage rkmpv myvideo.mp4 will play a fullscreen, hardware assisted, version of your video. rkmpv is at /usr/local/bin/rkmpv

=== Swapping Kernel Versions ===
extlinux is in use on Ayufan images (at least) which enables some switching between installed kernel versions - [https://github.com/ayufan-rock64/linux-build/blob/master/recipes/extlinux.md intro documentation is here.] In particular after you install any additional kernels, you can edit your /boot/extlinux/extlinux.conf file to specify which of the kernels you have installed to use for the next boot.

From Ayufan version 0.7.11 the script /usr/local/sbin/change-default-kernel.sh does a nice little menu swap for you if you run it as root (sudo).

=== Using an NVMe Disk as rootfs ===
Forum member Bullet64 has documented [https://forum.frank-mankel.org/topic/208/booten-von-der-nvme-platte how to move rootfs to an NVMe disk.] This is useful until we get a full SPI option to boot from the NVMe.

== More advanced bits related to any OS ==

This section gives some hints for advanced users.

=== Setup a Serial Console (UART2)===

{{warning|1=RockPro64 is designed to use 3VDC3A (3 Volts Direct Current 3 Ampere) for the connection, using 5VDC and more might damage the board!}}

To use Serial Console you will a need operating system that supports it on your RockPro64, by default the serial console is provided for baud 9 600 which is far too slow for rockpro64 so consider using 1 500 000 (1.5Mbps) instead IF your serial console device supports it (many doesn't which results in their unability to use the console).

{{warning|1=Do not connect RxD (pin 10) until the U-Boot SPL is running (see [[RK3399 boot sequence]]) or the SPL will not start}}

In terms of connections you need to perform the following from your serial console-capable device e.g. Pine64's Woodpecker available in store:
* GND <-> GND (pin 6)
* RxD <-> TxD (pin 8)
* TxD <-> RxD (pin 10)

After the configuration of your preferred operating system you can connect to the serial console using any of these commands:

$ screen /dev/ttyUSB0 1500000

$ picocom /dev/ttyUSB0 -b 1500000

$ minicom -D /dev/ttyUSB0 -b 1500000

NOTE: You might need a root permission if your user is not in the appropriate user-group e.g. <code>dialup</code> on GNU/Linux

Alternatively there is a detailed guide on forums: https://forum.pine64.org/showthread.php?tid=6387

==== GNU/Linux ====

With GNU/Linux on your RockPro64 the built-in support for serial console can be enabled by parsing parse e.g. <code>console=ttyS2,1500000n8</code> in the kernel command line, many distributions make this available by default, but consider verifying the contents of <code>/boot/extlinux/extlinux.conf</code> if you encounter issues.

NOTE: the <code>n8</code> in the kernel argument means no parity, 8 bits per character

=== Booting from USB or PXE ===

The default choice of boot device is first eMMC (if present) then SDcard. See [[ ROCKPro64_Main_Page#Disable_eMMC | jumpers above for details on adjusting this sequence.]]

It is possible to flash the SPI to extend the options for boot devices to USB drives or PXE. The preferred method is now the rock64_write_spi_flash.sh script (see [[ROCKPro64_Main_Page#Useful_scripts | useful scripts above.]]) The NOOB wiki page has more details [[NOOB#Flashing_u-boot_to_SPI_Flash | here.]]

Background info and historic details of this usage [https://github.com/ayufan-rock64/linux-build/blob/master/recipes/flash-spi.md can be found here.]

=== Booting from SPI using u-boot ===

{{warning|1=idbloader is not open-source}}

Always be prepared to recover from a broken SPI boot BEFORE flashing or you will end up with a broken boot.

In general the recovery is killswitching SPI through shorting pins 23 <-> 25 together and then loading u-boot from a storage device e.g. sd-card or eMMC where majority of GNU distributions e.g. Manjaro usually have u-boot packaged with the provided images.

Follow instructions in https://github.com/sigmaris/u-boot/wiki/Flashing-U-Boot-to-SPI#instructions-for-rockpro64

=== Boot sequence ===

The RockPro64 boot sequence has been documented [https://github.com/sigmaris/u-boot/wiki/RockPro64-boot-sequence here] by sigmaris.

=== OTG Mode ===

You can boot your ROCKPro64 into OTG mode with the use of the Recover button (see [[ROCKPro64_Main_Page#Switches | switch 28 above.]]) Note there are 2 OTG ports on your ROCKPro64: the type-C USB 3 socket is definitely one. From the schematic it appears the USB 3 (type A) socket is the other, but this has yet to be confirmed.

The method is to power off the board. Then push and hold the Recover button and push and release the Power button.
* If you have an Ayufan bootable image in either the SDcard or eMMC then there are 4 OTG modes [https://github.com/ayufan-rock64/linux-u-boot/commit/ea6efecdfecc57c853a6f32f78469d1b2417329b described here] including Android fastboot, RockUSB and MaskROM modes. Releasing the Recover button as soon as the white LED lights counts as 1 blink. Keeping it pressed you will get 2 blinks of the white LED etc. Once the board enters OTG mode the red LED will be lit. In mode 1 the boot and linux-root partitions of the card with the Ayufan image (partitions 6 & 7 of a linux installation) are made available as devices. In all cases the USB device made available at the host has device ID 18d1:d00d.
* If you do not have an Ayufan image in either the SDcard or the eMMC, then neither white nor red LEDs will light, but the board will enter MaskROM mode where the USB device made available at the host has device ID 2207:330c.

=== NVMe Drives ===
Please be aware that [https://pine64.com/product/rockpro64-pci-e-x4-to-m-2-ngff-nvme-ssd-interface-card the PINE64 SSD interface card] is intended for use with NVMe devices. These can be identified by the fact they have a single (Key M) notch, e.g. [https://www.wdc.com/content/dam/wdc/website/products/family/wd-black-pcie-ssd/wdfWDBlackSSD_PCIe_img1.jpg.imgw.500.500.jpg the WD Black devices.]

While M2/NGFF SATA devices (with a Key B notch, typically have Key M as well) will physically fit, they will not work. e.g. [https://www.wdc.com/content/dam/wdc/website/products/personal/internal_storage/wd_blue_3d_nand_sata_ssd/blue3d_product-overview.jpg.imgw.1000.1000.jpg WD Blue devices.]

=== SATA Drives ===
SATA drives can be connected directly via the [https://pine64.com/?product=rockpro64-pci-e-to-dual-sata-ii-interface-card ROCKPro64 PCIe interface card.] Please note the card does not include the power cable - that is a [https://pine64.com/?product=rockpro64-power-cable-for-dual-sata-drives separate item.] Equally you must be aware that connecting SATA drives in this manner means they will be drawing power from your ROCKPro64 - please ensure you are using a 5A or better power supply.

ExplainingComputers did a YouTube [https://www.youtube.com/watch?v=9CCQicHwfDI ROCKPro64 PCIe SATA card review and tests using a Ubuntu console and OpenMediaVault.]

=== Wi-Fi & Bluetooth Module ===
If you have bought the [https://pine64.com/product/rockpro64-1x1-dual-band-wifi-802-11ac-bluetooth-5-0-module Wi-Fi and Bluetooth module] from the Pine store then instructions for connecting it can be found on the accessories page [[ Accessories_Step_by_Step_Guides#Wifi.2FBluetooth_module | here.]] '''Please note that the 0.7.9 Ayufan's linux releases (August 2018) have deliberately DISABLED support for this module in the search for stability. It can be tested and used with the Android image.'''

It can also be used on Manjaro by installing ap6256-firmware and wireless-regdb packages.

=== 7" LCD Touch Screen ===
Instructions for connecting the [https://pine64.com/?product=7-lcd-touch-screen-panel LCD touch screen] from the Pine [[ Accessories_Step_by_Step_Guides#7.22_LCD_Touch_Screen_Panel | are here.]]

'''Note at present (August 2018) this screen is only supported by the Android image.'''

{{warning|1= When using the touchscreen ensure the cables are properly connected and tightened down and that you do not let the metal backplane touch the SBC}}

=== RTC Battery Backup ===
The Pine store has a couple of options for RTC battery backups: a [https://pine64.com/product/rtc-backup-battery-holder-2-x-aaa AAA version here] or a [https://pine64.com/product/rtc-backup-battery-holder-cr-2032 CR-2032 version here.] Instructions for plugging in either of them are also on the [[ Accessories_Step_by_Step_Guides| Accessories page ]]. For the ROCKPro64, the backup plugs into the RTC connector, number 6 in the board layout diagram above, next to the USB3 and case screw point.

=== Acrylic Open Enclosure ===
Assembly instructions for the [https://pine64.com/product/pine-a64-rockpro64-acrylic-open-enclosure acrylic enclosure] from the Pine store are also on the [[ Accessories_Step_by_Step_Guides| Accessories page ]]

=== NAS case ===
The [https://files.pine64.org/doc/rockpro64/ROCKPro64%20NAS%20Case%20Exploded%20View%20Diagram.pdf Exploded View Installation Diagram] for the [https://pine64.com/product/rockpro64-metal-desktop-nas-casing NAS case from the Pine store].

Detailed '''NAS Case overview and assembly instructions''' can be found [[NASCase | here]].

= [[ROCKPro64_Hardware_Accessory_Compatibility|Hardware Compatibility]] =
== Hardware Compatibility Page ==
Please contribute to the hardware compatibility page, which lists hardware which has been tested with the rockpro64, whether successful or not.

* [[ROCKPro64_Hardware_Accessory_Compatibility#PCIe devices|PCIe devices]]
* [[ROCKPro64_Hardware_Accessory_Compatibility#NVMe_SSD_drives|NVMe SSD drives]]
* [[ROCKPro64_Hardware_Accessory_Compatibility#USB_hardware|USB hardware]]
* [[ROCKPro64_Hardware_Accessory_Compatibility#USB_C_alternate_mode_DP|USB C alternate mode DP]]
* [[ROCKPro64_Hardware_Accessory_Compatibility#Other_hardware|Other hardware]]

== Limitations ==
=== Older firmware overwrites actively used memory ===
Some people get system freeze when:
* use SATA disk with ROCKPro64 PCIe card. (maybe on newer PCIe card ASM1062 vs ASM1061)
* or do read or write 4GB to the flash. (not using PCIe)

If you connect the serial console you will see a Linux kernel oops: (a)synchronous external abort.

Both issues are in fact the same software BUG. There is no hardware problem.
Currently, most OS do use uboot with a rockpro blob FW which use memory that Linux kernel is not aware of.

People are currently fixing this BUG, but it may take some time.
In the mean time, you can fix it manually.

The latest u-boot can boot the rockpro64 without any blobs from rockchip.
Install first arm-none-eabi-gcc and aarch64-linux-gnu-gcc compiler, then run the following commands:

git clone https://github.com/ARM-software/arm-trusted-firmware.git atf
make -C atf CROSS_COMPILE=aarch64-linux-gnu- PLAT=rk3399 bl31
git clone https://gitlab.denx.de/u-boot/u-boot.git u-boot
cd u-boot/
git checkout v2020.01-rc5
make rockpro64-rk3399_defconfig
BL31=../atf/build/rk3399/release/bl31/bl31.elf make ARCH=arm CROSS_COMPILE=aarch64-linux-gnu-

Which gives you idbloader.img and u-boot.itb.
Copy them to the rockpro64, and run the following: (Or put your SD card into your PC)

sudo dd if=idbloader.img of=/dev/mmcblk0 seek=64
sudo dd if=u-boot.itb of=/dev/mmcblk0 seek=16384
sync

=== PCIe Controller Hardware Error Handling Bug ===
There is an issue with the rk3399 pcie controller that is currently unmitigated:
* [https://lore.kernel.org/linux-pci/CAMdYz...gmail.com/ LKML Original Thread]
* [https://lkml.org/lkml/2020/4/6/320 LKML Additional Information]

The rk3399 pcie controller throws either a synchronous abort or a SError when a pcie device sends an unknown message.

The error type is determined by which cpu cluster handles the message.

=== Virtualization ===
The PCIe controller on the rk3399 is not behind an IOMMU.
This means it is not possible to safely pass through PCIe devices to a virtual machine.

= Board Features =

This section outlines the most important characteristics of the board and its components.

== SoC and Memory Specification ==
* Based on Rockchip RK3399
[[File:Rockchip_RK3399.png|right]]

=== CPU Architecture ===
* [https://developer.arm.com/products/processors/cortex-a/cortex-a72 Dual-core Cortex-A72 up to 2.0GHz CPU]
* [https://developer.arm.com/products/processors/cortex-a/cortex-a53 Quad-core Cortex-A53 up to 1.5GHz CPU]
* big.LITTLE architecture: Dual Cortex-A72 + Quad Cortex-A53, 64-bit CPU
* Cortex-A72:
** 1-4x Symmetrical Multiprocessing (SMP) within a single processor cluster, and multiple coherent SMP processor clusters through AMBA 5 CHI or AMBA 4 ACE technology
** AArch64 for 64-bit support and new architectural features
** L1 cache 48KB Icache and 32KB Dcache for each A72
** L2 cache 1024KB for big cluster
** DSP & SIMD extensions
** VFPv4 floating point
** Hardware virtualization support
* Cortex-A53:
** L1 cache 32KB Icache and 32KB Dcache for each A53
** L2 cache 512KB for little cluster
* Full implementation of the ARM architecture v8-A instruction set
* ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
* ARMv8 Cryptography Extensions
* In-order pipeline with symmetric dual-issue of most instructions
* Include VFP v3 hardware to support single and double-precision operations
* TrustZone technology support
* Full CoreSight debug solution
* One isolated voltage domain to support DVFS

=== GPU Architecture ===
* [https://developer.arm.com/products/graphics-and-multimedia/mali-gpus/mali-t860-and-mali-t880-gpus ARM Mali-T860MP4 Quad-core GPU]
* The highest performance GPUs built on Arm Mali’s famous Midgard architecture, the Mali-T860 GPU is designed for complex graphics use cases and provides stunning visuals for UHD content.
* Frequency: 650MHz
* Throughput: 1300Mtri/s, 10.4Gpix/s
* OpenGL® ES 1.1, 1.2, 2.0, 3.1, 3.2, Vulkan 1.0*, OpenCL™ 1.1, 1.2, DirectX® 11 FL11_1, RenderScript™.

=== System Memory ===
* LPDDR4 RAM Memory Variants: Dual Channels 2GB and 4GB.
* Storage Memory: 128Mb built-in SPI Flash memory (as at August 2018 only support for USB boot).

== Display ==
* Dual VOP: one supports resolutions up to 4096x2160 and [https://www.arm.com/why-arm/technologies/graphics-technologies/arm-frame-buffer-compression AFBC]; the other supports resolutions up to 2560x1600
* Dual channel MIPI-DSI (4 lanes per channel)
* eDP 1.3 (4 lanes with 10.8Gbps) to support displays, with PSR
* Digital Video port up to 4Kp60
* DisplayPort 1.2 (4 lanes, up to 4K 60Hz)
* Supports Rec.2020 and conversion to Rec.709

== Video ==
* Digital Video output up to 4K@60Hz
* 4K HDR @ 30fps
* H.264/AVC Base/Main/High/High10 profile @ level 5.1; up to 4Kx2K @ 60fps
* H.265/HEVC Main/Main10 profile @ level 5.1 High-tier; up to 4Kx2K @ 60fps
* VP9, up to 4Kx2K @ 60fps
* MPEG-1, ISO/IEC 11172-2, up to 1080P @ 60fps
* MPEG-2, ISO/IEC 13818-2, SP@ML, MP@HL, up to 1080P @ 60fps
* MPEG-4, ISO/IEC 14496-2, SP@L0-3, ASP@L0-5, up to 1080P @ 60fps
* VC-1, SP@ML, MP@HL, AP@L0-3, up to 1080P @ 60fps
* MVC is supported based on H.264 or H.265, up to 1080P @ 60fps

== Audio ==
* 3.5mm Phone Jack
* 3-pin S/PDIF header
* Audio via Digital Video port

== Camera ==
* Dual MIPI CSI，dual ISP, maximum input resolution of 13M pixels

== Network ==
* 10/100/1000Mbps Ethernet - Capable of pushing 941 MBit/s in iperf3
* Wi-Fi 802.11 ac/a/b/g/n with Bluetooth 4.01 (old version with 2x2) / Bluetooth 5 (new version with 1x1) (optional)

== Storage ==
* microSD - bootable, support SDHC and SDXC, storage up to 256GB
* eMMC - bootable (optional eMMC Module)
* 1 USB3.0 Host port
* 1 USB type C OTG port with DP output
* 2 USB2.0 Dedicated Host ports

== Expansion Ports ==
* 2x20 pins "Pi2" GPIO Header
* PCIe 2.1 (4 full-duplex lanes with 20Gbps) x4 open ended port

=== GPIO Pins ===

{| class="wikitable plainrowheaders" border="1"
! scope="col" style="width:20em;" | Assigned To
! scope="col" | Pin Nr.
! scope="col" | Pin Nr.
! scope="col" style="width:20em;" | Assigned To
|-
| style="text-align:right;"| 3.3 V
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 1
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 2
| style="text-align:left;"| 5 V
|-
| style="text-align:right;"| GPIO1_C4 (I2C8_SDA) a
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 3
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 4
| style="text-align:left;"| 5 V
|-
| style="text-align:right;"| GPIO1_C5 (I2C8_SCL) a
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 5
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 6
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO4_D0 (CPU_GPCLK)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 7
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 8
| style="text-align:left;"| GPIO4_C4 (UART2_TX)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 9
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 10
| style="text-align:left;"| GPIO4_C3 (UART2_RX)
|-
| style="text-align:right;"| GPIO1_C6
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 11
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 12
| style="text-align:left;"| GPIO3_D0 (I2S0_CLK)
|-
| style="text-align:right;"| GPIO1_C2
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 13
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 14
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO1_A1
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 15
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 16
| style="text-align:left;"| GPIO1_A4
|-
| style="text-align:right;"| 3.3 V
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 17
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 18
| style="text-align:left;"| GPIO4_C5 [SPDIF]
|-
| style="text-align:right;"| [UART4_TX] GPIO1_B0 (SPI1_TXD)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 19
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 20
| style="text-align:left;"| GND
|-
| style="text-align:right;"| [UART4_RX] GPIO1_A7 (SPI1_RXD)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 21
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 22
| style="text-align:left;"| GPIO4_D1
|-
| style="text-align:right;"| GPIO1_B1 (SPI1_CLK)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 23
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 24
| style="text-align:left;"| GPIO1_B2 (SPI1_CSN0)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 25
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 26
| style="text-align:left;"| GPIO1_B5
|-
| style="text-align:right;"| GPIO1_B3 (I2C4_SDA)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 27
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 28
| style="text-align:left;"| GPIO1_B4 (I2C4_SCL)
|-
| style="text-align:right;"| GPIO4_D3
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 29
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 30
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO4_D4
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 31
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 32
| style="text-align:left;"| GPIO3_D4 (I2S0_SDI1SDO3)
|-
| style="text-align:right;"| GPIO3_D5 (I2S0_SDI2SDO2)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 33
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 34
| style="text-align:left;"| GND
|-
| style="text-align:right;"| GPIO3_D2 (I2S0_LRCKTX)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 35
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 36
| style="text-align:left;"| GPIO3_D6 (I2S0_SDI3SDO1)
|-
| style="text-align:right;"| GPIO3_D1 (I2S0_LRCKRX)
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 37
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 38
| style="text-align:left;"| GPIO3_D3 (I2S0_SDI0)
|-
| style="text-align:right;"| GND
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 39
| style="text-align:center; background-color:black; color:gold; font-weight:bold;"| 40
| style="text-align:left;"| GPIO3_D7 (I2S0_SDO0)
|}

==== Notes ====
<ol style="list-style-type:lower-alpha">
<li>pulled high to 3.3V through 2.2kOhm resistor</li>
</ol>

==== Linux /dev/gpiochip Assignments ====

{| class="wikitable plainrowheaders" style="float: right; margin: 0 0 0 1ch; line-height: 1.4; text-align: center;"
|- style="font-size: .9em;"
! scope="col" | Pin Nr.
! scope="col" | Chip
! scope="col" | Line
|-
| 3 || 1 || 20
|-
| 5 || 1 || 21
|-
| 7 || 4 || 24
|-
| 8 || 4 || 20
|-
| 10 || 4 || 19
|-
| 11 || 1 || 22
|-
| 12 || 3 || 24
|-
| 13 || 1 || 18
|-
| 15 || 1 || 1
|-
| 16 || 1 || 4
|-
| 18 || 4 || 21
|-
| 19 || 1 || 8
|-
| 21 || 1 || 7
|-
| 22 || 4 || 25
|-
| 23 || 1 || 9
|-
| 24 || 1 || 10
|-
| 26 || 1 || 13
|-
| 27 || 1 || 11
|-
| 28 || 1 || 12
|-
| 29 || 4 || 27
|-
| 31 || 4 || 28
|-
| 32 || 3 || 28
|-
| 33 || 3 || 29
|-
| 35 || 3 || 26
|-
| 36 || 3 || 30
|-
| 37 || 3 || 25
|-
| 38 || 3 || 27
|-
| 40 || 3 || 31
|}

On Linux, using the new <code>/dev/gpiochip</code> API,
the <code>''n''</code> in <code>GPIO''n''_''XX''</code> appears to correlate to the number of the <code>/dev/gpiochip''n''</code>,
and the <code>''XX''</code> to the definition <code>RK_P''XX''</code> of lines in <code>include/dt-bindings/pinctrl/rockchip.h</code> of the Linux kernel source.
Having these named in the dts would be nice.

You can use [https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/ libgpiod] to drive them,
and test them with the included tools (<code>gpioinfo</code>, <code>gpioset</code>, ...)

For example, <code>gpioset 4 25=1</code> (run as root) would turn pin 22 on.
Do beware that poking the wrong GPIO pin can lock up your system.

The conversion table at right is also available as a [https://gist.github.com/CounterPillow/fe066655bf2d929148fe6eb3f15b1dd5 C header file].

<div style="clear: both;"></div>

== Working Features ==
<div style="overflow: auto">
{| class="wikitable sortable"
! Feature/Option
! Android
! Android Version
! Linux
! Linux Version
! Test/Verify Steps
! Notes
! Product Link
|-
| PINE64 LCD Touchscreen (Screen/Touch)
| Yes/Yes
|
| No/No
|
|
| Maybe [https://github.com/avafinger/pine64-touchscreen this] will help get this working?
| [https://pine64.com/?product=7-lcd-touch-screen-panel 7″ LCD Touch Screen Panel]
|-
| Wireless
ROCKPro64 2×2 MIMO Dual Band WiFi 802.11AC / Bluetooth 4.2 Module (old)
ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module (new)
| Yes/Yes
|
| No/No
|
|
| In 0.7.9 Ayufan linux releases this is deliberately disabled for stability reasons.
| [https://store.pine64.org/product/rockpro64-1x1-dual-band-wifi-802-11acbluetooth-5-0-module ROCKPro64 1x1 Dual Band WiFi 802.11AC / Bluetooth 5.0 Module]
|-
| USB OTG
|
|
|
|
| use this script: [https://github.com/ayufan-rock64/linux-package/blob/master/root-rockpro64/usr/local/sbin/rockpro64_enable_otg.sh rockpro64_enable_otg.sh], then configure ip on usb0: ifconfig usb0 169.169.222.222 and run iperf, you should likely see about 200-300MB/s
| [[ROCKPro64_Main_Page#OTG_mode]]
|
|-
| USB Mass Storage USB2/USB3
| Yes/yes
|
| Yes/Yes
|
|
|
|
|-
| Dedicated Fan Power (pwm1)
|
|
| Yes
|
|
| You might want to use [https://github.com/tuxd3v/ats ATS].
|
|-
| GPIO pins (raw or via RPI python scripts)
|
|
|
|
|
| Check out [https://forum.frank-mankel.org/topic/292/rockpro64-rp64-gpio/2 what Frank Mankel has done].
|
|-
| MIPI CSI Camera 1 and 2
|
|
|
|
|
|
|
|-
| eDP
|
|
|
|
|
|
|
|-
| HDMI Audio
| Yes
| 7.1.2
| Yes
| 4.4.132-1083 - 4.4.138-1100
|
| Stopped working in 4.4.154.1105. Ayufan is looking into it.
|
|-
| 3.5mm Audio/Mic
|
|
|
|
|
|
|
|-
| USB-C Host
|
|
|
|
|
|
|
|-
| Display via USB-C
| Yes
| 7.x and 8.x
|
|
|
| eDP via USB-C per tillim. No sound on Android 7.x. Sound does work on Android 8.x
|
|-
| ROCKPro64 PLAYBOX ENCLOSURE
| N/A
|
| N/A
|
| N/A
| Ventilation does not exist, thus requires manual changes to add venting. Case should be modified to account power adapter not being centered in cut holes. Opening the case once close without modifying it first is near impossible without special tools. Graphene heatsink is included and does well for Linux but not Android.
| https://pine64.com/?product=rockpro64-playbox-enclosure
|-
| ROCKPro64 30mm Tall Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| https://store.pine64.org/?product=rockpro64-heatsink
|-
| ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
|
| https://pine64.com/?product=rockpro64-20mm-mid-profile-heatsink
|-
| Fan For ROCKPro64 20mm Mid Profile Heatsink
| N/A
|
| N/A
|
| N/A
| You might want to use [https://github.com/tuxd3v/fanctl fanctl] to control the fan while keeping your CPU cool
| https://pine64.com/?product=fan-for-rockpro64-20mm-mid-profile-heatsink
|-
| HDMI output 4K@60Hz
|
|
|
|
|
|
|
|-
| PCIe 2.1
|
|
|
|
|
|
|
|-
| Real Time Clock (RTC) battery backup
|
|
|
|
|
|
| https://store.pine64.org/?product=rtc-backup-battery-cr-battery
|-
| Boot from USB/PXE
|
|
|
|
|
|
|
|}
</div>

RockChip themselves have tables of supported features at 4.4 and mainline kernel versions [http://opensource.rock-chips.com/wiki_Status_Matrix in their wiki here].

= Board Information, Schematics and Certifications =
* Board Dimensions: 133mm x 80mm x 19mm
* Input Power: +12V @3A/5A with 5.5mm/2.1mm Type M Barrel type DC connector
* [https://files.pine64.org/doc/rockpro64/rockpro64_v21-SCH.pdf ROCKPro64 Schematic v2.1 (Second Batch Production Release)]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.dxf ROCKPro64 v2.1 Board Top Outline in AutoCad DXF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.dxf ROCKPro64 v2.1 Board Bottom Outline in AutoCad DXF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-top.pdf ROCKPro64 v2.1 Board Top Outline in PDF format]
** [https://files.pine64.org/doc/rockpro64/RockPro64_v21_Boardoutline-bottom.pdf ROCKPro64 v2.1 Board Bottom Outline in PDF format]
* [https://files.pine64.org/doc/rockpro64/rockpro64_v20-SCH.pdf ROCKPro64 Schematic v2.0 (Pilot Production Release)]
** [https://files.pine64.org/doc/rockpro64/ROCKPRo64%20Engineering%20Change%20Notice%2020180628RP01.pdf Engineering Change Notice for v2.0 to turn on 3.3V power on PCIe]
* [https://files.pine64.org/doc/rockpro64/rockpro64_wifi_ap6359SA.pdf ROCKPro64 AP6359SA Wifi/BT Schematic]
* [https://files.pine64.org/doc/rockpro64/Rockpro64%20Pi-2%20Connector%20ver0.2.png ROCKPro64 Pi-2 Pin assignment and definition]
* [https://files.pine64.org/doc/rockpro64/RockPro-3D-model.zip ROCKPro64 3D model]

* Certifications:
** Disclaimer: Please note that PINE64 SBC is not a "final" product and in general certification is not necessary. However, PINE64 still submit the SBC for FCC, CE, and ROHS certification and obtain the certificates to proof that SBC board is capable on passing the testing. Please note a final commercial product needs to performs its owns testing and obtains its owns certificates.
** [https://files.pine64.org/doc/cert/ROCKPro64%20FCC%20SDOC%20Certificate.pdf ROCKPro64 FCC Certificate]
** [https://files.pine64.org/doc/cert/ROCKPro64%20CE-EMC%20Certificate.pdf ROCKPro64 CE Certificate]
** [https://files.pine64.org/doc/cert/ROCKPro64%20ROHS%20%20SEC180529404001E%20Report.pdf ROCKPro64 RoHS Report]

= Datasheets for Components and Peripherals =
* Rockchip RK3399 SoC information:
** [https://www.rock-chips.com/a/en/products/RK33_Series/2016/0419/758.html Rockchip RK3399 SoC Brief]
** [http://opensource.rock-chips.com/images/d/d7/Rockchip_RK3399_Datasheet_V2.1-20200323.pdf Rockchip RK3399 Datasheet V2.1]
** [http://opensource.rock-chips.com/images/e/ee/Rockchip_RK3399TRM_V1.4_Part1-20170408.pdf Rockchip RK3399 Technical Reference Manual part 1]
** [https://files.pine64.org/doc/datasheet/rockpro64/RK808%20datasheet%20V0.8.pdf Rockchip RK808 Datasheet V0.8]
* LPDDR4 (200 Balls) SDRAM:
** [https://files.pine64.org/doc/datasheet/rockpro64/SM512M32Z01MD2BNP(200BALL).pdf Micron LPDDR4 Mobile LPDDR4 Datasheet]
* eMMC information:
** [https://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]
** [https://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]
** [https://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]
** [https://files.pine64.org/doc/datasheet/pine64/E-00517%20FORESEE_eMMC_NCEMAM8B-16G%20SPEC.pdf 16GB Foresee eMMC Datasheet]
** [https://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf 32GB/64GB/128GB SanDisk eMMC Datasheet]
* SPI NOR Flash information:
** [https://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
** [https://files.pine64.org/doc/datasheet/pine64/GD25Q128C-Rev2.5.pdf GigaDevice 128Mb SPI Flash Datasheet]
* Heatsink related info:
** [https://files.pine64.org/doc/datasheet/rockpro64/Rockpro%20Passive%20Heatsink%20Spec.jpg ROCKPro64 Passive Heatsink Dimension Drawing]
** [https://files.pine64.org/doc/datasheet/rockpro64/LMS-TC150%20Silicon%20Thermal%20Pad.pdf Heatsink Thermal Pad Specification]
* Wireless related info:
** AMPAK AP6256 11AC WiFi + Bluetooth5.0 Datasheet [https://files.pine64.org/doc/datasheet/rockpro64/AP6256%20datasheet_V1.3_12202017.pdf (v. 1.3)] [http://files.pine64.org/doc/datasheet/PinebookPro/AP6256%20datasheet_V1.7_12282018.pdf (v. 1.7)]
* Ethernet related info:
** [https://files.pine64.org/doc/datasheet/rock64/RTL8211F-CG-Realtek.pdf Realtek RTL8211F 10/100/1000M Ethernet Transceiver Datasheet]
* Peripheral related info:
** [https://files.pine64.org/doc/datasheet/rockpro64/ASM1061_Data%20Sheet_R1_8.pdf asmedia ASM1061 PCIe SATA 2.0 Datasheet]
* Remote control button mapping
** [https://files.pine64.org/doc/Pine%20A64%20Schematic/remote-wit-logo.jpg Official Remote Control for the PINE64 Button Mapping]
* Audio Codec (ES8316) (Under Board)
** [http://everest-semi.com/pdf/ES8316%20PB.pdf Everest ES8316 Audio Codec]
* PWM controlled fan, SPDIF, and RTC Battery Backup headers
** [https://www.jst-mfg.com/product/pdf/eng/ePH.pdf JST-PH connector]

= Useful Articles and Blog Posts =

If you want to dive in to the ecosystem, here's a short list of various articles and blog posts that can help you set up your soft- or hardware development environment.

* [https://stikonas.eu/wordpress/2019/09/15/blobless-boot-with-rockpro64/ Blobless boot with RockPro64 by Andrius Štikonas]

* [https://marcin.juszkiewicz.com.pl/2020/06/17/ebbr-on-rockpro64/ EBBR on RockPro64 by Marcin Juszkiewicz]

* [[ROCKPro64 Device Tree Overlays on Mainline]]

= The NAS Case for the ROCKPro64 =
[[file:NASCaseMain.png|thumb|right|Front View of the PINE64 NAS Case for the ROCKPro64]]
Please [[NASCase | follow this this link]] for '''detailed instructions on how to assemble the ROCKPro64 NAS Case'''.

The NAS Case instructions also contains detailed information about:
*what the NAS Case ships with
*What additional things you need to purchase for your NAS Case
*What optional things you can consider purchasing for your NAS build
*What OS Image we recommend you use for your NAS build
*IO accessibility after installing the ROCKPro64 into the NAS Case
*[https://files.pine64.org/doc/rockpro64/ROCKPro64%20NAS%20Case%20Exploded%20View%20Diagram.pdf NAS Case Exploded View]
*[https://files.pine64.org/doc/rockpro64/NAS%20Case%20Drawing.dwg NAS Case Drawing]

= 3D printable ITX mounting brackets =
[[file:ITX-Bracket-Mounted.jpg|300px|thumb|right|A Quartz64-A mounted in an ITX case using 3D printed brackets]]

Allows mounting a ROCKPro64-A or Quartz64-A board inside a regular PC case that conforms to the ITX standard, using 3D printed brackets:

* AMF/STL/STEP files plus the original FreeCAD file used to create the models [[File:RP64-A_Q64-A_to_ITX_mounting_brackets.zip]]
* Make sure to flip the two brackets by 180 degrees on one of the horizontal axes (X/Y) in your slicer of choice before printing to avoid unnecessary supports
* To allow enough clearance between the board and the bracket you either need to print four copies of the washer model or add nut(s) between the board and the bracket
* If using nuts for the clearance between the board and the brackets, make sure it creates at least 3.2mm of spacing in between
* Depending on the accuracy and calibration of a 3D printer, slight deviation can occur and you likely need to manually widen some of the holes to allow screws to fit

= Other Resources =
* [https://forum.pine64.org/forumdisplay.php?fid=98 ROCKPro64 Forum]
* [https://pine64.com/?post_type=product PINE64 shop]
* [https://github.com/rockchip-linux Rockchip Linux GitHub Repo]
* [http://opensource.rock-chips.com/ Rockchip Open Source Wiki]
* ExplainingComputers have a video review [https://www.youtube.com/watch?v=CeoNHGFN_30 of the RockPro64 here, including linux first boot.]

= Troubleshooting =

== No Video or GPU Acceleration on Debian ==

If you can log in through serial but don't get any video or GPU acceleration on Debian, this is likely due to Debian's decision to compile the devfreq governors as loadable modules but not including them early enough for panfrost to be able to be provided with one of them.

The usual sign of this being the case is the following line in your log: <code>[drm:panfrost_devfreq_init [panfrost]] *ERROR* Couldn't initialize GPU devfreq</code>

Log in to your ROCKPro64, and run the following:

sudo -i
echo governor_simpleondemand >> /etc/initramfs-tools/modules && update-initramfs -u -k $(uname -r)
exit

Then, reboot.

[[Category:ROCKPro64]] [[Category:Rockchip RK3399]]

PinePhone (Pro) Keyboard

2022-07-30T08:28:58Z

PineCone: Updated the kernel driver names

[[File:PP_KB_Front-1024x576.jpg|400px|thumb|right|Picture of the PinePhone (Pro) Keyboard]]

The '''PinePhone (Pro) Keyboard Case''' is a case compatible with the [[PinePhone]] and [[PinePhone Pro]], adding a keyboard functionality to the phone. It features a clam-shell design and uses the pogo pins located on the smartphone’s midsection and attaches by replacing the default back cover. This add-on effectively turns the PinePhone (Pro) into a PDA with an in-built LTE modem.

== Getting started ==
[[File:Ppkb_description.png|thumb|upright=1.2|
① Contact pads 
② Battery switch 
③ USB-C connector]]

The keyboard case works with both the PinePhone and PinePhone Pro and features a clam-shell design. It uses pogo pins located on the phone’s midsection and attaches by replacing the default back cover. When folded, the phone’s screen and the keyboard rest securely against each other. The hinge features a 180° design, which not only allows for two-hand typing on a surface but also for comfortable thumb-typing when fully extended. The etched keycaps can be easily relocated for alternate layouts such as AZERTY or QWERTZ. The keyboard case runs an [https://xff.cz/git/pinephone-keyboard/ open firmware], which means that anyone with the know-how can alter existing functions or add new ones. The bottom (keyboard) and top (phone) sections of the assembly are well-balanced thanks to the large, 6000mAh, internal battery capable of charging the PinePhone (Pro) during operation. The internal battery effectively triples the phone’s battery life. The internal keyboard battery can be manually toggled on/off and the keyboard’s battery charge level can be read in the supported OSes; the keyboard remains functional with the battery fully depleted.

You do not lose access to the PinePhone (Pro)’s USB-C port, speaker, microphone, or any external features, such as volume and lock buttons, with the keyboard attached. There is also a cut-out for the camera, torch, and headphone jack. The USB-C port on the keyboard is capable of powering both the keyboard and PinePhone (Pro) simultaneously. <s>This means that you can plug in a USB mouse, a USB-C dongle, or some other peripheral while the phone and keyboard’s internal battery charge</s>.

{{warning|1=Do NOT plug any device into the phone USB-C port while the keyboard is attached. Doing so may result in damage or loss of the keyboard charging functionality. Technical details regarding the issue can be found in [https://www.pine64.org/2022/05/31/may-update-worth-the-wait/ this] blog post. Please see the [[PinePhone (Pro) Keyboard#Safety|safety]] section.}}

Please keep in mind that the keyboard case transforms the PinePhone (Pro) into a PDA, which means that taking calls will likely prove awkward without a wired or wireless headset connected (try speakerphone button if available).

=== Mounting the keyboard ===
Power off your PinePhone and remove the back case. To remove the back case of the PinePhone use your fingernail or another soft object to pry up the back case. A notch to easily remove the cover is located at the bottom left of the PinePhone with the backcover facing the user.

Open and place the keyboard flat on a hard surface with the hinge fully extended. Proceed to insert the PinePhone into the keyboard at an angle of approx. 15 degrees. Make sure that the PinePhone’s pogo pins and the corresponding pads ① on the keyboard are aligned. The leading edge with volume and power buttons should make contact first. Firmly press the PinePhone into place. Multiple clicks should be heard as the two snap into place. Pay special attention to the plastic pin below the camera hole. Firmly push from the rear, below the camera hole, to click it into position. Failing to do so may cause an insufficient pin contact and prevent the case from charging the phone.

The PinePhone can be removed from the keyboard easily using a notch similar to the one found on the back case. The notch is located at the bottom of the leading edge with the power and volume buttons.

=== Operation ===
The keyboard will function automatically once a PinePhone running a compatible operating system is mounted. For alterations to physical layout and firmware see the relevant sections respectively.

The keyboard features an in-built 6000mAh battery. The battery can be turned ON/OFF using the button on the right leading edge of the keyboard ②. A short button press activates the internal battery while a long (15 seconds) press or double press deactivates it. Compatible operating systems display both the PinePhone’s and keyboard’s battery status.

You should charge the PinePhone and the keyboard only using the USB-C ③ port on the keyboard. The keyboard’s USB-C port cannot be used for peripherals. The PinePhone’s USB-C port remains operational when mounted in the keyboard and can be used for data and peripherals.

=== Troubleshooting ===
There are multiple possible hardware issues users could face. It is recommend to check the following most common hardware issues and their solutions and workarounds.

==== Pogo pins not making proper contact ====
Under certain scenarios the keyboard's contacts are not making proper contact with the pogo pins of the phone. To address the issue:

* Power down the phone!
* Apply '''slight''' pressure in the upper mid of the PinePhone's backside until the plastic holder pin towards the upper middle of the keyboard cover, until an audible click can be heard.
* Make sure the contacts and pogo pins are clean and the pogo pins can be slightly pressed individually.
* If the above does not work, a shim under the keyboard's contacts might be required, as explained [https://xnux.eu/pinephone-keyboard/faq.html#ts FAQ troubleshooting section]. See also this [https://freiburg.social/system/media_attachments/files/107/684/243/421/870/279/original/a5e9c68ff3510ec8.jpeg photo of where to place the shim], or [https://www.youtube.com/watch?v=4ixPjz6SPIA this video].

==== Top row is less responsive ====
The keys of the top row may be less responsive. The issue can be worked around by adding inserts to the underside of the top row key caps to decrease the travel distance. More details regarding the workaround can be found in the corresponding section of the FAQ page of the developer megi: https://xnux.eu/pinephone-keyboard/faq.html#ts

==== Software issues ====
For any software issue please see the [[PinePhone (Pro) Keyboard#Software support|Software support section]] and the [[PinePhone (Pro) Keyboard#Frequently asked questions|FAQ section]].

== Safety ==

{{warning|1=Do NOT plug any device into the phone USB-C port while the keyboard is attached. Doing so may result in damage or loss of the keyboard charging functionality. Technical details regarding the issue can be found in [https://www.pine64.org/2022/05/31/may-update-worth-the-wait/ this] blog post. 

Due to this limitation users may want block the USB-C port of the phone while the keyboard is connected to prevent connecting any USB device to the phone under any circumstances. See for example [https://fosstodon.org/web/@silverhax/107783280758831068 here].}}

'''Please note:''' Only use mild isopropyl alcohol when wiping down the clamshell of the device. Stronger solutions may partially strip the coatings. Do not lube the keyboard with GPL 205G0 switch grease, it can cause problems with the key responsiveness and tactility.

== Software support ==

=== Kernel-space driver ===

Kernel driver implementation from Samuel Holland: CONFIG_IP5XXX_POWER (module ip5xxx_power) and CONFIG_KEYBOARD_PINEPHONE (module pinephone_keyboard) https://github.com/smaeul/linux/commits/wip/pp-keyboard

Note: If you've upgraded to >=5.18, don't forget to upgrade the dtb as kb151 now appears to be a stub.

=== User-space driver ===
The user-space driver is available [https://xff.cz/git/pinephone-keyboard/ here]. Use git to clone the repository. You're going to need sdcc 4.1+ installed to build it, so use your package manager to install that first. Next you'll cd into the directory you cloned pinephone-keyboard and use the command "make" to build. After the build is completed, cd into the build directory and you'll notice several new files starting with ppkb-. To use your keyboard case, you'll want to run the following command: <code>sudo ./ppkb-i2c-inputd</code>  Open something you can type into like a new terminal window or text editor and you should now be able to use the keyboard case!

=== Notes ===
Virtual keyboards such as squeekboard are opening whenever a text field is selected.

To disable this behavior under Linux running '''Phosh''' you can change the corresponding settings under ''Settings'' > ''Accessibility'' > ''Screen Keyboard'' (see [https://forum.pine64.org/showthread.php?tid=15789&pid=105152 here]). The virtual keyboard can also be disabled temporarily for one session using:

* To temporarily disable the virtual keyboard: <code>gsettings set org.gnome.desktop.a11y.applications screen-keyboard-enabled false</code>

* To temporarily enable the virtual keyboard: <code>gsettings set org.gnome.desktop.a11y.applications screen-keyboard-enabled true</code>

The virtual keyboard needs to be activated before removing the keyboard case again.

Under '''Plasma Mobile''' the keyboard can be disabled via a widget, see [https://forum.pine64.org/showthread.php?tid=14789&pid=105077#pid105077 here].

In '''Sxmo''' disabling the keyboard is not required, as the keyboard will only shown when the corresponding hotkey button is pressed.

== Keyboard layout ==
The keyboard features a default layout (pictured below) created and agreed upon by the community. The keyboard layout can be altered using software as well as by physically repositioning keycaps. All keycaps, with the exception of space and return keys, can be easily and safely relocated for alternative layouts corresponding to software settings.

<gallery mode="nolines" widths="500px" heights="400px">
Image:Ppkb_layout2.png|The keyboard layout how the keys were originally intended
</gallery>

== Keyboard firmware ==
PinePhone’s keyboard firmware was developed independently by Ondřej Jirman as a free-of-charge contribution to PINE64. The firmware source code is freely and publicly available and you can modify it, and the supporting utilities, using common FOSS tools.

=== Firmware and supporting utilities ===
The design of the firmware allows the keys, modifier keys, and their combinations to be handled in virtually unlimited ways, without a need to flash a customized version of the firmware. Mapping of keys is defined at runtime, using the supporting utilities, and is not hardcoded in the firmware. Different keyboard layouts can be loaded dynamically to support various use cases.

The repository that contains the source code of the firmware, supporting utilities and associated documentation is located at https://xnux.eu/pinephone-keyboard/.

You are welcome to contribute patches and improvements to the firmware and the supporting utilities. A summary of firmware development history is available at https://xnux.eu/log/ alongside other development updates from the firmware author.

Much time and effort went into the development of this firmware. If you wish to send a token of appreciation or support the development efforts in any way, please consider making a donation to the author via one of the methods listed at the bottom of this web page: https://xnux.eu/contribute.html.

=== Firmware License ===

<blockquote>Copyright (C) 2021 Ondřej Jirman <megi@xff.cz>

This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, with either version 3 of the License or
(at your discretion) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
See GNU General Public License for more details.

GNU General Public License http://www.gnu.org/licenses/</blockquote>

== Hardware ==
Key hardware specifications:
* Dimensions (closed): 161 x 95 x 25mm
* Weights (without / with PinePhone mounted): ~ 191 / ~391 grams
* Number of keys: 54
* Number of rows: 5
** Keyboard IC: Keyboard IC: EM85F684A 8-bit microcontroller with 256 bytes RAM, 2048/ bytes XRAM; 16kB for user’s own firmware
* Battery capacity: 6000mAh (22.2Wh 3.7V)
* Charger input: 5V, 3A (15W)
** Charging and battery IC chip: IP5209 power management IC with charge indicate controller and boost converter

== Frequently asked questions ==
{{Under construction}}

''' What is the keyboard driver situation? ''' 
See https://xnux.eu/pinephone-keyboard/faq.html#drivers

''' Are keyboard drivers included in my distribution? ''' 
See https://xnux.eu/pinephone-keyboard/faq.html#distros

''' What's the status of the existing software for the keyboard? ''' 
See https://xnux.eu/pinephone-keyboard/faq.html#sw-status

''' My keyboard doesn't work (well)! ''' 
See https://xnux.eu/pinephone-keyboard/faq.html#faq-ts

''' How does charging work? ''' 
See https://xnux.eu/pinephone-keyboard/faq.html#charging

''' What charger is best for the keyboard? ''' 
See https://xnux.eu/pinephone-keyboard/faq.html#chargers

''' How safe is the charger circuit in the keyboard? ''' 
See https://xnux.eu/pinephone-keyboard/faq.html#safety

''' Keyboard doesn't react to any key presses ''' 
See https://xnux.eu/pinephone-keyboard/faq.html#ts

''' Keyboard works but top row of keys is less responsive ''' 
See https://xnux.eu/pinephone-keyboard/faq.html#ts

''' Phone is not charging from the keyboard ''' 
See https://xnux.eu/pinephone-keyboard/faq.html#ts

''' Phone is charging slowly from the keyboard battery ''' 
See https://xnux.eu/pinephone-keyboard/faq.html#ts
and https://forum.pine64.org/showthread.php?tid=16979&pid=111414#pid111414#ts

''' Can you open the keyboard and add extra functionality? ''' 
It is possible to do so, however the production units can be extremely difficult to open. Do not attempt to open the keyboard if you do not want to risk cosmetic damage (scaring and scratching of the plastic).

''' How can I rotate the screen display in tty ? ''' 
Under Linux this can be done using the command <code>echo 1 | sudo tee /sys/class/graphics/fbcon/rotate</code>

''' Top row stopped displaying symbols! (kernel > 5.17) ''' 
* For Phosh (at the example of Mobian) see: https://wiki.mobian-project.org/doku.php?id=ppaccessories
* For TTY and SWMO see: https://codeberg.org/HazardChem/PinePhone_Keyboard

== Documents ==

* [https://files.pine64.org/doc/PinePhone/USER%20MANUAL-KEYBOARD-V2-EN-DE-FR-ES.pdf PinePhone Keyboard 4 language user manual ver 2.0 in PDF format]
* [https://files.pine64.org/doc/PinePhone/USER%20MANUAL-KEYBOARD-V2-EN-DE-FR-ES.odt PinePhone Keyboard 4 language user manual ver 2.0 in ODT format]

== Schematics, Datasheet and certifications ==

* Schematic:
** [https://files.pine64.org/doc/PinePhone/PinePhone%20Keyboard%20Schematic%20V1.0-20211009.pdf PinePhone Keyboard Schematic ver 1.0 20211009]

* Datasheet:
** [https://files.pine64.org/doc/datasheet/pinephone/EM85F684A.pdf PEM85F684A USB Microcontroller Datasheet]
** [https://files.pine64.org/doc/datasheet/pinephone/IP5209.pdf IP5209 Power Bank SOC Datasheet]
** [https://files.pine64.org/doc/datasheet/pinephone/txs0104e.pdf TXS0104E 4-Bit Bidirectional Voltage-Level Translator Datasheet]

* Certifications:
** [https://files.pine64.org/doc/cert/PinePhone%20Keyboard%20FCC%20Certificate-S21111804102001.pdf PinePhone Keyboard FCC Certificate]
** [https://files.pine64.org/doc/cert/PinePhone%20Keyboard%20CE%20Certificate-S21111804101001.pdf PinePhone Keyboard CE RED Certificate]

== External links ==
* [https://www.pine64.org/2022/01/11/pinephone-pro-explorer-edition-pre-orders-open-january-11/ Pre-order announcement]
* FAQ of the developer megous: https://xnux.eu/pinephone-keyboard/faq.html

PinePhone FAQ

2021-12-03T06:09:50Z

PineCone: Typo fix.

A list of frequently asked question.

== Hardware ==

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

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

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

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

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

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

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

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

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

=== General ===

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

The PinePhone is about on par with a Raspberry Pi 3 in terms of CPU performance, however it's Mali 400 MP2 is much weaker than the Pi 3's VideoCore IV. The Mali 400 was the first mobile OpenGL ES 2.0 GPU on the market back in 2008 when it was released, compared to the much newer Videocore IV released in 2010. The PinePhone has been shown to handle smooth H.264 1440p30 video playback using Cedrus and gstreamer as documented [https://xnux.eu/log/#001 here]. The device should be more than capable of a smooth phone experience when used in conjunction with well optimized software that makes use of its hardware features. It is also capable of running many light games (including 3D ones such as SuperTuxKart), and retro gaming. Expect further speed improvements over time as the drivers are improved, and in the meanwhile you can look into slightly [[overclocking]] the device (at your own risk).

=== Sound ===

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

=== Bluetooth ===
For some reason, using pipewire-pulse with bluetooth headphones (In my case, Sony WH1000X-M3) using the default LDAC codec causes the headphones to constantly connect and disconnect until they eventually give up pairing. A work around I've found is to quickly go into Sound settings and switch the codec to "SBC".

=== Modem ===

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

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

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

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

=== Battery ===

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

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

First, try loosening the screws to the left and right of the battery compartment and remove the battery, it should go much easier now. These screws may be the culprit as they seem to make the sides of the midframe grip the battery. Do not tighten them fully and the problem should go away.

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

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

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

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

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

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

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

=== Privacy Switches ===
==== What are the privacy switches doing? ====

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

=== Memory ===

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

=== GPS ===

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

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

Until aGPS support becomes standard you'll have to make some manual changes - see for example [https://wiki.mobian-project.org/doku.php?id=location Mobian wiki]

==== GPS can't determine direction ====

Currently, due to the magnetometer not being hooked up in software at this time, it is not possible for GPS software to use the phone's compass functionality. This means while you are walking it will not be possible to determine the direction of travel. This is not as much of an issue for vehicles as the faster speeds mean that it is possible to estimate the direction of travel, however it will still be an issue should the vehicle travel through a tunnel and lose GPS signal.

== Software ==

=== Installation ===

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

See [[PinePhone Installation Instructions]].

=== Updating ===

Read the [[PinePhone Updating Instructions]].

=== Booting ===

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

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

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

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

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

This can be the result of at least one situation:

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

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

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

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

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

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

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

==== The PinePhone does not boot ====

Most OSes on the PinePhone do not boot if the battery is not connected or if it is fully drained. If you received a new PinePhone make sure to remove the battery isolator as explained under [[PinePhone#First time installation]].

If you removed the battery isolator and the battery contacts are intact, the battery is either fully drained or there is no valid OS (or a corrupted OS or bootloader) installed on the eMMC or the SD card. Make sure to charge the phone with a compatible charger (500 mAh is not enough for modern phones), as well as the installation instruction under [[PinePhone Installation Instructions]]. If the OS got corrupted it is highly recommend to simply reflash.

If nothing works please don't hesitate to contact the community via [[Main Page#Chat Platforms]], they are eager to help and booting issues are usually very easy to solve (as they are typically either battery or installation related. The phones itself are all tested individually at the factory. Do not contact PINE64's support for booting issues.

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

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

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

=== Other ===

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

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

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

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

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

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

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

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

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

# The plastic tab between the battery and the device's battery contacts has been removed
# The battery is installed
# The Wi-Fi privacy switch (switch number two) on the rear of the device is switched "ON"

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

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

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

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

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

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

==== How can I turn on the backlight? ====

On some devices the default calibration of the backlight is not sufficient and the minimum setting of the brightness of the used OS can be too low, causing the backlight to completely shut down. In that case it is recommended to connect the phone to a charger and/or to shine a flashlight at the screen to adjust the brightness to a higher setting again.

On many Linux OSes the brightness setting is an integer between 0 and 1000 and available at runtime in /sys/class/backlight/backlight/brightness and stored at shutdown and loaded at boot from /var/lib/systemd/backlight/platform-backlight:backlight:backlight by systemd-backlight@backlight:backlight.service. Changing the brightness setting can be done at runtime, for example over SSH, by executing as root <code>echo 500 > /sys/class/backlight/backlight/brightness</code>. The stored brightness setting can be modified using another system, by mounting the root filesystem of the system you want to fix and by executing <code>echo 500 > [MOUNT LOCATION]/var/lib/systemd/backlight/platform-backlight\:backlight\:backlight</code>.

==== How can I contribute regarding the WiFi and Bluetooth firmware? ====

The PinePhone uses [https://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf Realtek RTL8723CS] for its Wi-Fi and Bluetooth connectivity. Unfortunately, just like the other Realtek wireless chipsets ''([https://en.wikipedia.org/wiki/Comparison_of_open-source_wireless_drivers see more info])'' - the RTL8723CS chipset requires proprietary firmware for Wi-Fi and Bluetooth functionality. For those who want to create replacement free software firmware, 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] (different chipsets, but still Realtek) could be a great starting point for further research.

=== SMS ===

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

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

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

You can access the ModemManager using the mmcli command.

'''Mobian:'''

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

'''Manjaro:'''

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

For Mobian, delete all the messages like this:

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

For Manjaro, delete all the messages like this:

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

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

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

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

=== When does the phone ship? ===
For up-to-date information when the phone's shipping date is estimated, see the edits in the corresponding forum thread.

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

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

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

== Accessories ==

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

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

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

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

Replacement batteries for US customers are available in the store.

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

=== External hardware ===

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

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

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

See [[PinePhone Hardware Accessory Compatibility]].

[[Category:PinePhone]]

PinePhone FAQ

2021-12-03T06:05:44Z

PineCone: Improved wording of note on wireless firmware.

A list of frequently asked question.

== Hardware ==

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

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

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

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

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

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

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

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

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

=== General ===

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

The PinePhone is about on par with a Raspberry Pi 3 in terms of CPU performance, however it's Mali 400 MP2 is much weaker than the Pi 3's VideoCore IV. The Mali 400 was the first mobile OpenGL ES 2.0 GPU on the market back in 2008 when it was released, compared to the much newer Videocore IV released in 2010. The PinePhone has been shown to handle smooth H.264 1440p30 video playback using Cedrus and gstreamer as documented [https://xnux.eu/log/#001 here]. The device should be more than capable of a smooth phone experience when used in conjunction with well optimized software that makes use of its hardware features. It is also capable of running many light games (including 3D ones such as SuperTuxKart), and retro gaming. Expect further speed improvements over time as the drivers are improved, and in the meanwhile you can look into slightly [[overclocking]] the device (at your own risk).

=== Sound ===

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

=== Bluetooth ===
For some reason, using pipewire-pulse with bluetooth headphones (In my case, Sony WH1000X-M3) using the default LDAC codec causes the headphones to constantly connect and disconnect until they eventually give up pairing. A work around I've found is to quickly go into Sound settings and switch the codec to "SBC".

=== Modem ===

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

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

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

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

=== Battery ===

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

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

First, try loosening the screws to the left and right of the battery compartment and remove the battery, it should go much easier now. These screws may be the culprit as they seem to make the sides of the midframe grip the battery. Do not tighten them fully and the problem should go away.

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

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

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

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

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

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

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

=== Privacy Switches ===
==== What are the privacy switches doing? ====

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

=== Memory ===

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

=== GPS ===

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

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

Until aGPS support becomes standard you'll have to make some manual changes - see for example [https://wiki.mobian-project.org/doku.php?id=location Mobian wiki]

==== GPS can't determine direction ====

Currently, due to the magnetometer not being hooked up in software at this time, it is not possible for GPS software to use the phone's compass functionality. This means while you are walking it will not be possible to determine the direction of travel. This is not as much of an issue for vehicles as the faster speeds mean that it is possible to estimate the direction of travel, however it will still be an issue should the vehicle travel through a tunnel and loose GPS signal.

== Software ==

=== Installation ===

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

See [[PinePhone Installation Instructions]].

=== Updating ===

Read the [[PinePhone Updating Instructions]].

=== Booting ===

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

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

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

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

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

This can be the result of at least one situation:

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

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

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

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

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

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

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

==== The PinePhone does not boot ====

Most OSes on the PinePhone do not boot if the battery is not connected or if it is fully drained. If you received a new PinePhone make sure to remove the battery isolator as explained under [[PinePhone#First time installation]].

If you removed the battery isolator and the battery contacts are intact, the battery is either fully drained or there is no valid OS (or a corrupted OS or bootloader) installed on the eMMC or the SD card. Make sure to charge the phone with a compatible charger (500 mAh is not enough for modern phones), as well as the installation instruction under [[PinePhone Installation Instructions]]. If the OS got corrupted it is highly recommend to simply reflash.

If nothing works please don't hesitate to contact the community via [[Main Page#Chat Platforms]], they are eager to help and booting issues are usually very easy to solve (as they are typically either battery or installation related. The phones itself are all tested individually at the factory. Do not contact PINE64's support for booting issues.

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

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

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

=== Other ===

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

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

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

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

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

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

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

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

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

# The plastic tab between the battery and the device's battery contacts has been removed
# The battery is installed
# The Wi-Fi privacy switch (switch number two) on the rear of the device is switched "ON"

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

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

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

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

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

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

==== How can I turn on the backlight? ====

On some devices the default calibration of the backlight is not sufficient and the minimum setting of the brightness of the used OS can be too low, causing the backlight to completely shut down. In that case it is recommended to connect the phone to a charger and/or to shine a flashlight at the screen to adjust the brightness to a higher setting again.

On many Linux OSes the brightness setting is an integer between 0 and 1000 and available at runtime in /sys/class/backlight/backlight/brightness and stored at shutdown and loaded at boot from /var/lib/systemd/backlight/platform-backlight:backlight:backlight by systemd-backlight@backlight:backlight.service. Changing the brightness setting can be done at runtime, for example over SSH, by executing as root <code>echo 500 > /sys/class/backlight/backlight/brightness</code>. The stored brightness setting can be modified using another system, by mounting the root filesystem of the system you want to fix and by executing <code>echo 500 > [MOUNT LOCATION]/var/lib/systemd/backlight/platform-backlight\:backlight\:backlight</code>.

==== How can I contribute regarding the WiFi and Bluetooth firmware? ====

The PinePhone uses [https://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf Realtek RTL8723CS] for its Wi-Fi and Bluetooth connectivity. Unfortunately, just like the other Realtek wireless chipsets ''([https://en.wikipedia.org/wiki/Comparison_of_open-source_wireless_drivers see more info])'' - the RTL8723CS chipset requires proprietary firmware for Wi-Fi and Bluetooth functionality. For those who want to create replacement free software firmware, 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] (different chipsets, but still Realtek) could be a great starting point for further research.

=== SMS ===

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

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

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

You can access the ModemManager using the mmcli command.

'''Mobian:'''

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

'''Manjaro:'''

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

For Mobian, delete all the messages like this:

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

For Manjaro, delete all the messages like this:

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

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

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

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

=== When does the phone ship? ===
For up-to-date information when the phone's shipping date is estimated, see the edits in the corresponding forum thread.

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

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

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

== Accessories ==

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

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

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

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

Replacement batteries for US customers are available in the store.

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

=== External hardware ===

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

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

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

See [[PinePhone Hardware Accessory Compatibility]].

[[Category:PinePhone]]