Main Page

2022-01-02T17:12:04Z

Luke:

PINE64 is a community-driven company focused on creating high-quality, low-cost ARM devices and, more recently, RISC-V devices for individuals and businesses around the globe. PINE64 made its debut with the [[PINE A64|PINE A64]] single-board computer, which successfully launched on Kickstarter in 2015. PINE64 has since released a multitude of other devices, including both development boards and end-user devices.

PINE64 has a large, diverse and active community, and offers a variety of resources for hobbyists and businesses to successfully leverage various PINE64 products. To become connected and involved with the community, please see [[Main Page#Community and Support|Community and Support]] for a list of available channels and chat platforms. To learn more about PINE64, please visit the [https://www.pine64.org/ PINE64 website] and the [https://www.pine64.com/ PINE64 store]'''.

For information about PINE64 branding, including the usage of the PINE64 logo in non-commercial and other applications please read the [https://wiki.pine64.org/wiki/PINE64_brand_and_logo article about our brand and logo].

= Devices =

[[File:Marchupdate-1024x594.jpg|thumb|upright=1.2|[[Pinebook Pro]] (left) and [[PinePhone]] (right)]]

You can learn more about the following ARM and RISC-V devices manufactured by PINE64:

* Phones: '''[[PinePhone]]''' and '''[[PinePhone Pro]]'''
* Tablets: '''[[PineNote]]''' and '''[[PineTab]]'''
* Smartwatch: '''[[PineTime]]'''
* Laptops: '''[[Pinebook]]''', '''[[Pinebook Pro]]''' and '''[[Pinebook Pro Dock|Pinebook Pro Docking station]]'''
* Single-board computers: '''[[Quartz64]]''', '''[[ROCKPro64]]''', '''[[ROCK64]]''', '''[[PINE A64]]''', '''[[PINE A64-LTS/SOPine|PINE A64-LTS]]''' and '''[[PINE H64]]'''
* Clusters and modules: '''[[Clusterboard]]''', '''[[SOPine]]''', '''[[SOPine Baseboard]]''', '''[[SOEdge]]''' and '''[[SOQuartz]]'''
* IP camera: '''[[PineCube]]'''
* Makerspace: '''[[Pinecil]]''', '''[[PinePower]]''', '''[[PineCone]]''' and '''[[Pinedio]]'''
* Accessories: '''[[PinePhone Keyboard]]''', '''[[PinePhone add-on cases]]'''

= Community and Support =

Community collaboration and support is focused around the chat platforms and forums described below. As an example of the collaborative efforts of the community, recent activity has resulted in drafting a [[PineFlash|proposal]] for a new flash-based storage device. See [https://www.pine64.org/gettings-started/ Getting Started | PINE64] for tips about how to get started with the PINE64 community.

== Chat Platforms ==

PINE64 has a large and very active community. Community discussion takes place on a variety of chat platforms, which are all bridged together so the messages sent via one platform are sent to all other platforms automatically. The other networks and their users are represented by P64ProtocolBot.

{{note|1=The activity of community members varies depending on the time of day and the number of active users, so please be patient and do not expect questions to be answered immediately.}}

The community chat platforms are the following:
* '''Discord''': Use the [https://discordapp.com/invite/DgB7kzr invite link]. All channels are available.
* '''IRC''': The server is irc.pine64.org. Use <code>/list</code> command or the table below to see the full list of channels.
* '''Matrix and Telegram''': See the table below.

{| class="wikitable"
! Channel !! Matrix !! Telegram !! IRC
|-
| PINE64 News
| [https://app.element.io/#/room/#pine64-announcements:matrix.org #pine64-announcements:matrix.org]
| [https://t.me/PINE64_News @PINE64_News]
| Unavailable
|-
| General PINE64 chat
| [https://app.element.io/#/room/#pine64:matrix.org #pine64:matrix.org]
| [https://t.me/mtrx_pine64 @mtrx_pine64]
| #pine64
|-
| PINE A64(+), A64-LTS & SOPine
| [https://app.element.io/#/room/#pine64sopine:matrix.org #pine64sopine:matrix.org]
| [https://t.me/pine64sopine @pine64sopine]
| #lts-sopine
|-
| ROCK64 / ROCKPro64
| [https://app.element.io/#/room/#rock64:matrix.org #rock64:matrix.org]
| [https://t.me/mtrx_rock64 @mtrx_rock64]
| #rock64
|-
| Quartz64
| [https://app.element.io/#/room/#quartz64:matrix.org #quartz64:matrix.org]
| [https://t.me/joinchat/Vq50DXkH31e0_i-f Quartz64]
| #quartz64
|-
| Quartz64 Development
| [https://app.element.io/#/room/#quartz64-dev:matrix.org #quartz64-dev:matrix.org]
| [https://t.me/q64dev @q64dev]
| #quartz64-dev
|-
| Pinebook and Pinebook Pro
| [https://app.element.io/#/room/#pinebook:matrix.org #pinebook:matrix.org]
| [https://t.me/mtx_pinebook @mtx_pinebook]
| #pinebook
|-
| PinePhone
| [https://app.element.io/#/room/#pinephone:matrix.org #pinephone:matrix.org]
| [https://t.me/pinephone @pinephone]
| #pinephone
|-
| PineNote
| [https://app.element.io/#/room/#pinenote:matrix.org #pinenote:matrix.org]
| [https://t.me/pinenote @PineNote]
| #pinenote
|-
| PineTab
| [https://app.element.io/#/room/#pinetab64:matrix.org #pinetab64:matrix.org]
| [https://t.me/PineTab @PineTab]
| #pinetab
|-
| PineTime
| [https://app.element.io/#/room/#pinetime:matrix.org #pinetime:matrix.org]
| [https://t.me/pinetime @pinetime]
| #Pinetime
|-
| PineTime Development
| [https://app.element.io/#/room/#pinetime-dev:matrix.org #pinetime-dev:matrix.org]
| [https://t.me/pinetime_dev @pinetime_dev]
| #pinetime-dev
|-
| Pinecil
| [https://app.element.io/#/room/#pinecil:matrix.org #pinecil:matrix.org]
| [https://t.me/joinchat/Kmi2S1iej-_4DgrVf3jjnQ Pinecil]
| #pinecil
|-
| Pinetalk Podcast || Unavailable || Unavailable || Unavailable
|-
| Cube
| [https://app.element.io/#/room/#cube64:matrix.org #cube64:matrix.org]
| [https://t.me/pinecube @pinecube]
| #cube
|-
| Nutcracker
| [https://app.element.io/#/room/#pine64-nutcracker:matrix.org #pine64-nutcracker:matrix.org]
| [https://t.me/joinchat/Kmi2S0nOsT240emHk-aO6g Nutcracker]
| #nutcracker
|-
| LoRa
| [https://app.element.io/#/room/#pinelora:matrix.org #pinelora:matrix.org]
| [https://t.me/pine64lora @pine64lora]
| #lora
|-
| Off-topic
| [https://app.element.io/#/room/#offtopic64:matrix.org #offtopic64:matrix.org]
| [https://t.me/pine64offtopic @pine64offtopic]
| #Offtopic
|}

There is also an unofficial Matrix Space at [https://app.element.io/#/room/#pine64-space:matrix.org #pine64-space:matrix.org] for supported clients that organizes all of the above matrix channels into one place.

== Forums ==

PINE64 runs an official forum powered by the open-source forum server software MyBB. The forum can be used to report issues, help out other users, offer findings and new information and more. Users can also engage directly with the community and the developers of partner projects, as well as with the PINE64 members.

The official PINE64 forum can be accessed here:
* [https://forum.pine64.org/ Official PINE64 Forum]

Also, these are the official Subreddits:

* [https://www.reddit.com/r/PINE64official/ Official PINE64 Reddit]
* [https://www.reddit.com/r/PinePhoneOfficial/ Official PinePhone Reddit]

= Helpful Information for Beginners =

* '''[[NOOB | Getting started]]''': Basic information on setting up and handling PINE64 devices, such as how to write (flash) OS images to microSD cards and eMMC modules
* '''[[Notes | PINE64 Wiki contributing Notes]]''': Some notes on prioritized and suggested writing or editing to this Wiki, as well as long-term goals and wiki housekeeping tasks.
* '''[[:Category:Guide]]''': Lists other guide pages than those two above, some are delicated to spicific devices.

PineModems

2021-12-17T14:32:14Z

Luke: /* Modems used in Pine64 boards and devices */

= PINE64 position on alternative firmware =

PINE64 ships the PinePhone with a stock version of the Quectel EG25-G modem's firmware. Some administrative regions, in the EU and Asia in particular, require the entirety of the modem's firmware to be licensed. Therefore, the PinePhone cannot ship with an unlicensed firmware, and the PINE64 project cannot, officially encourage its userbase to use alternative modem firmware.

== Quectel EG25-G Modem ==

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

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

=== Specifications ===

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

=== NAND Partition table layout ===

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

=== Firmware Recovery ===

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

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

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

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

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

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

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

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

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

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

'''Get the Firmware Recovery Package'''

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

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

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

'''Execute the Quectel QFirehose utility'''

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

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

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

=== Bootloader unlocking ===

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

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

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

=== Custom Kernels and system images ===

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

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

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

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

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

[[Category:PinePhone]]

PinePhone Pro Developer Edition

2021-12-01T09:19:01Z

Luke: /* Introduction */

= Introduction =
The Developer Edition was the first edition of the PinePhone Pro, shipped to developers in December 2021. The aim of the the Developer Edition was to give development community access to the hardware prior to end-users, boost development efforts and allow for porting of existing mobile Linux operating systems to the new hardware.
It featured the same mainboard revision as the Explorer Edition that followed in early 2022.

= Getting started =
This post is aimed strictly at developers receiving their PinePhone Pro dev units. Please note that the following instructions do not apply to Explorer Edition or other future editions of the PinePhone Pro - everything below is only pertinent to the dev phones.

Consider this a crash course rather than a comprehensive overview; you are also welcome to participate in documenting the process (and everything else related to the PinePhone Pro) on the Wiki. You can either create a Wiki account or use your [forum.pine64.org PINE64 forum] credentials to log in.

== Getting the hardware ready ==
After unpacking the PinePhone Pro from its box, detach the back cover (looking at the back of the phone, there is a fingernail notch on the left leading edge) and remove the plastic tab between the battery and mainboard. You can also flip the headphone jack privacy switch at this point - this enables UART output via the headphone jack. Serial console works the [https://wiki.pine64.org/wiki/PinePhone#Serial_console same way as on the original PinePhone.]

= Factory hardware test image =

The PinePhone Pro developer edition ships with a BSP AOSP factory image flashed to the eMMC. This image includes a number of factory applications meant to validate operation of the sensors, the modem, cameras, LCD & touch panel, etc. You’ll have to nuke the AOSP build to run a Linux installation on the PinePhone Pro. Booting from SD with the AOSP factory build present on eMMC is not possible due to the SoCs native boot order.

== Nuking the factory AOSP installation ==
In the factory test image, navigate to setting (gear icon) > at the very bottom of the settings list you will find a phone icone with rk3999mid written underneath it > tap the last (bottom) setting 7 times in quick succession. Following this, you *may* need to do the following: open the Settings application and enable USB debugging in Settings > System > Developer Options > USB debugging. Then connect the PinePhone Pro to your PC with the supplied USB-C cable.

Please note: It is recommended to charge the device to at least 50% before proceeding with wiping the eMMC.

Connect the phone to your computer and check adb devices in the terminal. The phone should be registered as attached. Then enter adb shell followed by su to gain root access. At this point you can erase the eMMC installation:

cat /dev/zero > /dev/block/mmcblk1

The phone will freeze and then the screen will go blank. Let it sit for no less than 10 minutes and then power it off by holding down the power button. You’ll know the phone is powered down when the notification LED turns off.

== Flashing Linux ==
You will want to do all your testing and development on a SD card; you DO NOT want to flash an OS to eMMC at this time. Builds frequently break at this early development stage and recovering from a corrupted eMMC installation is presently time consuming and tedious. A fast 16-64GB micro SD card for $15 will work just fine.

There are a handful of OS builds available for the PinePhone Pro already. These can be found under the [https://wiki.pine64.org/wiki/PinePhone_Pro#Software_releases Software Releases] Wiki section.

If you are a developer porting your own distribution to the PinePhone Pro, please make sure to make an entry for it in the Software Releases section on the Wiki. If you want / need help with entering your build onto the Wiki please ping one of the mods or admins in the chats (see Forums and Chats drop-down menu).

= Resources =
Aside from the PINE64 Wiki there are also other useful resources scattered across different Wikis, repositories and blogs. In time these will be gathered into one place - the [https://gitlab.com/mobian1/devices/eg25-manager/-/merge_requests/41#note_744117720 DevZone] - which will help to streamline the development process.

At the time of publishing, these are *some* of the notable resource, listed in no particular order:

*[https://wiki.postmarketos.org/wiki/PINE64_PinePhone_Pro_(pine64-pinephonepro) postmarketOS Wiki]
*[https://xnux.eu/log/ Megi’s (b)log]
*[https://github.com/DanctNIX/danctnix DanctNIX repository]
*[https://github.com/manjaro-pinephone Manjaro repository]

= Development and discussion =
You will run into issues, there’s just no way around it, and doing it ‘on your own’ isn’t really a viable option since you’re one of the first people to hold a PinePhone Pro. The development process on a device such as this is a collaborative process, and I therefore encourage you to participate in the community. There are many ways to interact with other developers, including [https://matrix.to/#/!LZirCxnkkeBudrQzPj:matrix.org?via=matrix.org Matrix], [https://t.me/pinephone Telegram], [https://discord.gg/pine64 Discord] and IRC.

There is also a lesser known chat for developers only. Lesser known doesn’t mean top secret, but I will not be posting a link to it here to keep the number of non-dev participants to a minimum. If you join one of the general chats and let others know you received a dev phone, then I’m sure someone will point you in the right direction.

PinePhone Pro

2021-11-30T21:25:44Z

Luke: /* Software */

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

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

== Introduction ==

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

More information about the PinePhone Pro can be found on the device [https://www.pine64.org/pinephonepro/ main page].

=== State of the software ===

Presently, at the time of writing (late 2020), the PinePhone Pro is aimed solely at early adopters and developers. It will take time for all the PinePhone Pro’s functionality to reach software parity with the original PinePhone and for mobile Linux, in more general, to reach a higher degree of maturity.

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

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

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

*[https://wiki.pine64.org/wiki/PinePhone_Pro_Developer_Edition Developer Edition]
*Explorer Edition

=== Help and support ===

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

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

== First time setup ==

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

When shipped the battery is isolated from the mainboard contacts using a protective plastic tab, which is required to be removed before using the phone. The battery '''will not''' charge until it is removed and some of the device’s functionality may not function properly.

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

To remove the sticker after unboxing the phone:

# Carefully remove the back panel using the notch in the corner of the back cover without overbending it
# Remove the battery (if the battery is stuck in the device please check [[PinePhone_FAQ#The_battery_is_stuck_inside_the_phone|this]] paragraph for a fix)
# Peel off the clear plastic sticker below it, which isolates the charging contacts
# Reinsert the battery

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

== Software ==

At the time of the release, in late 2020, the PinePhone Pro is in an early development stage. That said, the device has benefited greatly from work done on the original PinePhone, which means that even early development images feature all core functionality, such as: functional UI, sensors and even the modem (to a degree).

The development is expected to proceed very quickly compared to progress done on the original PinePhone as much of the fundamental work can carry over to the new device.
You can follow development efforts on [https://xnux.eu/log/ Megi’s blog], the dedicated [[PinePhone Pro Development]] section as well as on individual project’s Wiki’s and repositories.

=== Software releases ===

{{Hint|Devenlopers, please add links to OS images, repositories or build instructions here.}}

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

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

* GitHub: [https://github.com/dreemurrs-embedded/Pine64-Arch/ dreemurrs-embedded/Pine64-Arch]

'''Download location'''

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

'''username/password'''

{| class="wikitable"
! Default user
| <code>alarm/123456</code>
|-
! root
| <code>root/root</code>
|}

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

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

'''Download location'''

* Phosh: [https://github.com/manjaro-pinephone/phosh-dev/releases Dev]
* Plasma Mobile: [https://github.com/manjaro-pinephone/plasma-mobile-dev/releases Dev]

'''username/password'''

{| class="wikitable"
! Default user
| <code>manjaro/123456</code>
|-
! root
| <code>root/root</code>
|}

=== Installation instructions ===

The PinePhone Pro does not share the original PinePhone’s boot priority - this means that you cannot boot from a SD card with an OS present on the device’s eMMC.

That said, booting from SD can be achieved using a modified u-boot (or a different bootloader) on eMMC, which seeks out a bootable partition on SD first. At the time of writing, this hasn’t been achieved yet but is a planned feature.

It is strongly recommended you perform all testing from a SD card, leaving the eMMC vacant.

== Specifications ==

* '''Dimensions:''' 160.8 x 76.6 x 11.1mm
* '''Weight:''' Approx. 220g
* '''SIM Card:''' Micro-SIM
* '''Display:'''
** '''Size:''' 6 inches (151mm) diagonal
** '''Type:''' 1440 x 720 in-cell IPS with Gorilla Glass 4™
** '''Resolution:''' 1440x720, 18:9 ratio
* '''System on Chip:''' Rockchip RK3399S 64bit SoC – 2x A72 and 4x A53 CPU cores @ 1.5GHz
* '''RAM:''' 4GB LPDDR4 @ 800MHz
* '''Internal Storage:''' 128GB eMMC, extendable up to 2TB via microSD, supports SDHC and SDXC
* '''Back [[#Camera|Camera]]:''' 13MP Sony IMX258 with Gorilla Glass 4™ protective layer, LED Flash
* '''Front Camera:''' 5MP OmniVision OV5640 front-facing camera
* '''Sound:''' Loudspeaker, 3.5mm jack & mic (jack doubles as hardware UART if hardware switch 6 is deactivated)
* '''Communication:'''
** '''[[#Modem|Modem]]:''' [https://www.quectel.com/product/lte-eg25-g/ Quectel EG25-G]
** '''LTE-FDD''': B1, B2, B3, B4, B5, B7, B8, B12, B13, B18, B19, B20, B25, B26, B28
** '''LTE-TDD''': B38, B39, B40, B41
** '''WCDMA''': B1, B2, B4, B5, B6, B8, B19
** '''GSM''': B2, B3, B5, B8 (850, 900, 1800, 1900 MHz)
** '''WLAN & Bluetooth:''' AMPAK AP6255 WiFi 11ac + Bluetooth V4.1
** '''GNSS:''' GPS/GLONASS/BeiDou/Galileo/QZSS, with A-GPS
* '''Sensors:''' Accelerometer, gyroscope, proximity, ambient light, compass
* '''Privacy switches:''' Modem, WiFi & Bluetooth, Microphone, Cameras
* '''[[#Battery|Battery]]:''' Lithium-ion, rated capacity 2800mAh (10.64Wh), typical capacity 3000mAh (11.40Wh) (nominally replaceable with any Samsung J7 form-factor battery)
* '''I/O:''' USB Type-C, USB Host, DisplayPort Alternate Mode output, 15W 5V 3A Quick Charge, follows USB PD specification

== Privacy switch configuration ==

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

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

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

== PinePhone board information, schematics and certifications ==

== Datasheets for components and peripherals ==

== Press ==

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

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

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

PinePhone Pro

2021-11-30T20:36:04Z

Luke: /* Editions and revisions */

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

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

== Introduction ==

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

More information about the PinePhone Pro can be found on the device [https://www.pine64.org/pinephonepro/ main page].

=== State of the software ===

Presently, at the time of writing (late 2020), the PinePhone Pro is aimed solely at early adopters and developers. It will take time for all the PinePhone Pro’s functionality to reach software parity with the original PinePhone and for mobile Linux, in more general, to reach a higher degree of maturity.

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

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

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

*[https://wiki.pine64.org/wiki/PinePhone_Pro_Developer_Edition Developer Edition]
*Explorer Edition

=== Help and support ===

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

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

== First time setup ==

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

When shipped the battery is isolated from the mainboard contacts using a protective plastic tab, which is required to be removed before using the phone. The battery '''will not''' charge until it is removed and some of the device’s functionality may not function properly.

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

To remove the sticker after unboxing the phone:

# Carefully remove the back panel using the notch in the corner of the back cover without overbending it
# Remove the battery (if the battery is stuck in the device please check [[PinePhone_FAQ#The_battery_is_stuck_inside_the_phone|this]] paragraph for a fix)
# Peel off the clear plastic sticker below it, which isolates the charging contacts
# Reinsert the battery

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

== Software ==

At the time of the release, in late 2020, the PinePhone Pro is in an early development stage. That said, the device has benefited greatly from work done on the original PinePhone, which means that even early development images feature all core functionality, such as: functional UI, sensors and even the modem (to a degree).

The development is expected to proceed very quickly compared to progress done on the original PinePhone as much of the fundamental work can carry over to the new device.
You can follow development efforts on [https://xnux.eu/log/ Megi’s blog], the dedicated [[PinePhone Pro Development]] section as well as on individual project’s Wiki’s and repositories.

=== Software releases ===

{{Hint|Devenlopers, please add links to OS images, repositories or build instructions here.}}

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

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

* GitHub: [https://github.com/dreemurrs-embedded/Pine64-Arch dreemurrs-embedded/Pine64-Arch]

'''Download location'''

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

'''username/password'''

{| class="wikitable"
! Default user
| <code>alarm/123456</code>
|-
! root
| <code>root/root</code>
|}

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

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

'''Download location'''

* Phosh: [https://github.com/manjaro-pinephone/phosh-dev/releases Dev]
* Plasma Mobile: [https://github.com/manjaro-pinephone/plasma-mobile-dev/releases Dev]

'''username/password'''

{| class="wikitable"
! Default user
| <code>manjaro/123456</code>
|-
! root
| <code>root/root</code>
|}

=== Installation instructions ===

The PinePhone Pro does not share the original PinePhone’s boot priority - this means that you cannot boot from a SD card with an OS present on the device’s eMMC.

That said, booting from SD can be achieved using a modified u-boot (or a different bootloader) on eMMC, which seeks out a bootable partition on SD first. At the time of writing, this hasn’t been achieved yet but is a planned feature.

It is strongly recommended you perform all testing from a SD card, leaving the eMMC vacant.

== Specifications ==

* '''Dimensions:''' 160.8 x 76.6 x 11.1mm
* '''Weight:''' Approx. 220g
* '''SIM Card:''' Micro-SIM
* '''Display:'''
** '''Size:''' 6 inches (151mm) diagonal
** '''Type:''' 1440 x 720 in-cell IPS with Gorilla Glass 4™
** '''Resolution:''' 1440x720, 18:9 ratio
* '''System on Chip:''' Rockchip RK3399S 64bit SoC – 2x A72 and 4x A53 CPU cores @ 1.5GHz
* '''RAM:''' 4GB LPDDR4 @ 800MHz
* '''Internal Storage:''' 128GB eMMC, extendable up to 2TB via microSD, supports SDHC and SDXC
* '''Back [[#Camera|Camera]]:''' 13MP Sony IMX258 with Gorilla Glass 4™ protective layer, LED Flash
* '''Front Camera:''' 5MP OmniVision OV5640 front-facing camera
* '''Sound:''' Loudspeaker, 3.5mm jack & mic (jack doubles as hardware UART if hardware switch 6 is deactivated)
* '''Communication:'''
** '''[[#Modem|Modem]]:''' [https://www.quectel.com/product/lte-eg25-g/ Quectel EG25-G]
** '''LTE-FDD''': B1, B2, B3, B4, B5, B7, B8, B12, B13, B18, B19, B20, B25, B26, B28
** '''LTE-TDD''': B38, B39, B40, B41
** '''WCDMA''': B1, B2, B4, B5, B6, B8, B19
** '''GSM''': B2, B3, B5, B8 (850, 900, 1800, 1900 MHz)
** '''WLAN & Bluetooth:''' AMPAK AP6255 WiFi 11ac + Bluetooth V4.1
** '''GNSS:''' GPS/GLONASS/BeiDou/Galileo/QZSS, with A-GPS
* '''Sensors:''' Accelerometer, gyroscope, proximity, ambient light, compass
* '''Privacy switches:''' Modem, WiFi & Bluetooth, Microphone, Cameras
* '''[[#Battery|Battery]]:''' Lithium-ion, rated capacity 2800mAh (10.64Wh), typical capacity 3000mAh (11.40Wh) (nominally replaceable with any Samsung J7 form-factor battery)
* '''I/O:''' USB Type-C, USB Host, DisplayPort Alternate Mode output, 15W 5V 3A Quick Charge, follows USB PD specification

== Privacy switch configuration ==

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

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

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

== PinePhone board information, schematics and certifications ==

== Datasheets for components and peripherals ==

== Press ==

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

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

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

PinePhone Pro Developer Edition

2021-11-30T20:34:28Z

Luke: /* Flashing Linux */

= Introduction =
The Developer Edition was the first edition of the PinePhone Pro, shipped to developers in December 2020. The aim of the the Developer Edition was to give development community access to the hardware prior to end-users, boost development efforts and allow for porting of existing mobile Linux operating systems to the new hardware.
It featured the same mainboard revision as the Explorer Edition that followed in early 2021.

= Getting started =
This post is aimed strictly at developers receiving their PinePhone Pro dev units. Please note that the following instructions do not apply to Explorer Edition or other future editions of the PinePhone Pro - everything below is only pertinent to the dev phones.

Consider this a crash course rather than a comprehensive overview; you are also welcome to participate in documenting the process (and everything else related to the PinePhone Pro) on the Wiki. You can either create a Wiki account or use your [forum.pine64.org PINE64 forum] credentials to log in.

== Getting the hardware ready ==
After unpacking the PinePhone Pro from its box, detach the back cover (looking at the back of the phone, there is a fingernail notch on the left leading edge) and remove the plastic tab between the battery and mainboard. You can also flip the headphone jack privacy switch at this point - this enables UART output via the headphone jack. Serial console works the [https://wiki.pine64.org/wiki/PinePhone#Serial_console same way as on the original PinePhone.]

= Factory hardware test image =

The PinePhone Pro developer edition ships with a BSP AOSP factory image flashed to the eMMC. This image includes a number of factory applications meant to validate operation of the sensors, the modem, cameras, LCD & touch panel, etc. You’ll have to nuke the AOSP build to run a Linux installation on the PinePhone Pro. Booting from SD with the AOSP factory build present on eMMC is not possible due to the SoCs native boot order.

== Nuking the factory AOSP installation ==
In the factory test image, navigate to setting (gear icon) > at the very bottom of the settings list you will find a phone icone with rk3999mid written underneath it > tap the last (bottom) setting 7 times in quick succession. Following this, you *may* need to do the following: open the Settings application and enable USB debugging in Settings > System > Developer Options > USB debugging. Then connect the PinePhone Pro to your PC with the supplied USB-C cable.

Please note: It is recommended to charge the device to at least 50% before proceeding with wiping the eMMC.

Connect the phone to your computer and check adb devices in the terminal. The phone should be registered as attached. Then enter adb shell followed by su to gain root access. At this point you can erase the eMMC installation:

cat /dev/zero > /dev/block/mmcblk1

The phone will freeze and then the screen will go blank. Let it sit for no less than 10 minutes and then power it off by holding down the power button. You’ll know the phone is powered down when the notification LED turns off.

== Flashing Linux ==
You will want to do all your testing and development on a SD card; you DO NOT want to flash an OS to eMMC at this time. Builds frequently break at this early development stage and recovering from a corrupted eMMC installation is presently time consuming and tedious. A fast 16-64GB micro SD card for $15 will work just fine.

There are a handful of OS builds available for the PinePhone Pro already. These can be found under the [https://wiki.pine64.org/wiki/PinePhone_Pro#Software_releases Software Releases] Wiki section.

If you are a developer porting your own distribution to the PinePhone Pro, please make sure to make an entry for it in the Software Releases section on the Wiki. If you want / need help with entering your build onto the Wiki please ping one of the mods or admins in the chats (see Forums and Chats drop-down menu).

= Resources =
Aside from the PINE64 Wiki there are also other useful resources scattered across different Wikis, repositories and blogs. In time these will be gathered into one place - the [https://gitlab.com/mobian1/devices/eg25-manager/-/merge_requests/41#note_744117720 DevZone] - which will help to streamline the development process.

At the time of publishing, these are *some* of the notable resource, listed in no particular order:

*[https://wiki.postmarketos.org/wiki/PINE64_PinePhone_Pro_(pine64-pinephonepro) postmarketOS Wiki]
*[https://xnux.eu/log/ Megi’s (b)log]
*[https://github.com/DanctNIX/danctnix DanctNIX repository]
*[https://github.com/manjaro-pinephone Manjaro repository]

= Development and discussion =
You will run into issues, there’s just no way around it, and doing it ‘on your own’ isn’t really a viable option since you’re one of the first people to hold a PinePhone Pro. The development process on a device such as this is a collaborative process, and I therefore encourage you to participate in the community. There are many ways to interact with other developers, including [https://matrix.to/#/!LZirCxnkkeBudrQzPj:matrix.org?via=matrix.org Matrix], [https://t.me/pinephone Telegram], [https://discord.gg/pine64 Discord] and IRC.

There is also a lesser known chat for developers only. Lesser known doesn’t mean top secret, but I will not be posting a link to it here to keep the number of non-dev participants to a minimum. If you join one of the general chats and let others know you received a dev phone, then I’m sure someone will point you in the right direction.

Luke: /* 1. Presentation and typography */

PINE64 and the PINE64 pinecone logo are trademarked by Pine Store Limited. The trademark extends to the PINE64 brand name in writing, the PINE64 pinecone logo (referred to as logo in the document) and in some instances also to logo derivatives (see section 4).

The brand and logo were first trademarked in 2015 by then Pine Microsystems Inc. Pine Store Ltd. permits the usage of the brand name, the logo and logo derivatives for all non-commercial software endeavours and non-software projects undertaken by PINE64’s Community and community projects (subject to the terms outlined in this document). Pine Store Ltd. may also permit the usage of the logo and branding for commercial software and non-software goods projects upon prior agreement. PINE64 Community also permits the usage of the logo and branding to sponsored projects or community endeavours and affiliate programs (see section 3.1).

We are highly protective of our trademark and copyrights, and will seek any and all legal measures to enforce guidelines contained in this document.
[[File:Pine64logowriting.jpg|500px|thumb|right|PINE64 pinecone logo with brand name]]
=1. Presentation and typography=

The PINE64 project logotype is always capitalised: PINE64
The logotype always uses high tonal contrast, all capital letters and is preceded by the logo.
The original logotype uses Arial Std Narrow Regular, but an acceptable and frequently used variant is written in Noto Sans Telugu UI.

The PINE64 logo is a polygon geometric pinecone representation. The original logo uses five shades of blue colour.

PINE64 logo colors in HTML notation, top to bottom:
*[#52accd]
*[#2f82c4]
*[#2969b1]
*[#3d5c8b]
*[#475677]

Other variants, including all-white logo and typography on black or transparent background, are in use and permitted for non-commercial usage. Other colour variations are also permitted for non-commercial use. Other variants than the official logotype may be used for commercial use following an inquiry with PINE64 Community representatives and/ or designated Pine Store Ltd. staff members.

==1.1. Slogan(s), look and branding==

The PINE64 community slogan is “Open. Friendly. Community Driven”.
PINE64 hardware packaging uses the tagline “Open Sesame”.

PINE64 uses a distinct brand look which makes use of the original colour scheme of the pine cone logo (see section 1.) in conjunction with black, grey and white as background colours.
The distinct look of PINE64 organization’s (pine64.org) website, the official forum (forum.pine64.org) and the Pine Store’s (pine64.com) website is restricted to official PINE64 portals and community services. It may not be copied or imitated by community run services such as forums or websites.

==1.2. Media kit==

We provide a PINE64 logo media kit in .zip format containing a range of acceptable variations in SVG file format.
The .zip file also contains a READ ME document with detailed information and instructions.

*[[:File:Pine64-logos.zip|Media kit in .zip format]]
*

==1.3. Branding on devices==

We choose to keep PINE64 branding on our devices to a minimum. Our design follows our inherent ideology that devices we sell belong to the end-users, not to us.

A PINE64 pinecone is always printed on the PCB of a single board computer or device, alongside with the hardware’s name and revision number version. The full brand name is never used on our devices.

The PINE64 pinecone is also discreetly placed between the torch and camera on the PinePhone, on the LCD of the PineTab and on the SUPER key on the Pinebook Pro. This minimal branding aesthetic will also be used for future PINE64 hardware.

Packaging of PINE64 devices varies in branding implementation, ranging from plain white boxes from recycled materials to the hallmark “Open Sesame” tagline alongside PINE64 logotype from recycled cardboard.
The PinePhone also uses a distinct “PINEPHONE” logotype written in Good Times Regular font.

=2. Non-commercial usage=

Any and all derivatives of the PINE64 brand name and pinecone logo, including alterations to the original logo per bounds in section 1, are permitted for non-commercial use.

Use of the logo and brand name is permitted in communities or projects, as long as it is clearly denoted that the software, community, portal, website, subreddit, etc., does not belong to and is not administered by PINE64 community nor Pine Store Ltd.

==2.1. Examples of appropriate non-commercial usage==
*Including PINE64 logo and brand name in open source software, offered freely and free of charge, written for PINE64 devices
*Including PINE64 logo and brand name on publicly available 3D files offered freely and free of charge
*Including PINE64 logo and brand name on software project websites to indicate that software compatibility with PINE64 hardware
*Including PINE64 logo on community run forums, subreddits, chats, etc.
*Including PINE64 logo to indicate that software is compatible with PINE64 hardware
*Any alterations to the logotype for private or community use - for example as freely distributed wallpapers, icons, emotes, etc.
*Including PINE64 slogan and distinct brand look in freely distributed and royalty free software

==2.2. Restrictions to non-commercial usage==

The PINE64 logo and logotype may not, under any circumstances, be used or associated with any software or hardware projects not related to PINE64 hardware. Our brand name look and slogan (see section 1.1) are also restricted to use on official PINE64 websites, chats, forums and hardware (but allowed on freely distributed software for PINE64 devices).

We reserve the right to request the PINE64 logo and logotype be removed if a non-profit endeavour or project doesn’t align with our rules and code of conduct. This includes, but is not limited to, any community project, endeavour or piece of software promoting any political, religious or social agendas outside the scope of what our rules and code of conduct guidelines permit.

The PINE64 logo and logotype may not, under any circumstances, be used to mislead existing or prospectus PINE64 community members into believing that software, social media account, community service, website, forum, subreddit, chat, social media account, etc., is representative of or run by official spokespersons of the PINE64 community or the Pine Store Ltd. staff members.
The PINE64 logo and brand name may not be used in a way that creates a false impression that a product or business is endorsed, sponsored by or associated with the PINE64 community or Pine Store Ltd.

=3. Commercial, affiliate and sponsorship usage=

Commercial use of the logo, logotype or brand name, as well as any derivatives or alterade logotypes, is not permitted without prior consent of Pine Store Ltd. This means that any software project, merchandise vendor or community endeavour that seeks to turn a financial profit based on the PINE64 brand name needs to first acquire appropriate consent from Pine Store Ltd.

The logo and logotype are copyrighted. Sale of any merchandise with PINE64 branding is not permitted without an agreement from the Pine Store Ltd. This applies to both goods in physical or digital form.

Projects, events or other engagements sponsored by PINE64 Community need to clearly indicate PINE64’s relation to the sponsorship by proceeding the logotype with text to the effect of “Sponsored by” or placing PINE64 branding in a dedicated “Sponsors” section. See 3.1 for details

We will seek any and all legal measures to enforce compliance with the use of all our copyrights and the PINE64 trademark.

==3.1. Commercial and affiliate use or as part of sponsorship==

Any use of the PINE64 logo and brand name in digital form should adhere to guidelines in section 1. PINE64 partner projects, business partners, affiliate programs, sponsored programs or events, etc. are welcome to reach out to PINE64 representatives and/ or Pine Store Ltd. staff members for graphical assets (e.g. the logo and logotype) and to consult usage.

Use of the PINE64 logo and branding on physical merchandise, such as T-shirts, hoodies, caps, cups, etc. needs to include a registered trademark symbol ® following the banding.

The PINE64 logo and brand name must appear less prominent than the business’ or project’s logo and brand name. The purpose for using the PINE64 logo or brand name needs to be indicated on a business’ or project’s website. In example, if the purpose of using PINE64 branding is to indicate partnership, then our branding should be preceded by text to the effect of “In partnership with PINE64” or by placing our branding in a dedicated “Partners” section on a website.

In the case of sponsorship, sponsors are asked to include an identification of PINE64’s affinity with the said sponsored project. This includes, but is not limited to, placing PINE64 logo and/ logotype in a “Sponsors” section or being processed by “Sponsored by” to indicate sponsorship.

==3.2 Applying for inclusion of branding in commercial application or sponsorship==

For business, partnership or sponsorship inquiries please email: info@pine64.org
Applications are reviewed on a case-by-case basis.

==3.3 Examples of appropriate commercial, sponsorship or affiliate usage==

*Including PINE64 logo and brand name on a dedicated “sponsors” page or in a designated “sponsors” section of a webpage
*Including PINE64 logo and brand name on a partner project’s website, with preceding text to the effect of “in partnership with PINE64” or in a designated “partners” section
*Including PINE64 logo and brand name on physical merchandise with a registered trademark symbol ®
*Including PINE64 logo on product packaging to indicate compatibility with PINE64 hardware
*Including PINE64 logo and brand name in paid software and associated promotional materials (e.g. on business’ website), to indicate compatibility with PINE64 hardware
*Including PINE64 logo as part of promotional materials by partner projects or affiliated businesses upon prior agreement

==3.4 Restrictions to commercial usage==

No business, sponsored project or affiliate may use the PINE64 logo and logotype to mislead existing or prospectus PINE64 community members into believing that software, community service, social media account, website, forum, subreddit, chat, social media account, etc., is representative of or run by official spokespersons of the PINE64 community or the Pine Store Ltd. staff members.
We reserve the right to request a sponsored event, affiliate program, business or partner project to remove PINE64 branding under particular circumstances.

=4. Creation of derivative logos and logotypes=

Anyone is allowed to create PINE64 derivatives for personal or community usage. This extends to any form of artwork, community-made mockups or any other clearly identifiable community-activity that does not mislead existing or prospectus community members to believe it is PINE64 official material.

Derivatives of the PINE64 logo and banding are permitted for non-commercial usage, granted they do not mislead prospectus or existing PINE64 community members into believing the material is PINE64 sanctioned or issued by PINE64. Derivatives of the logo and branding may not be used in a context that could cause brand damage nor for commercial purposes.

Derivatives of PINE64 branding may still be subject to our copyright and as such need to adhere to restrictions outlined in section 2.2. We may request the removal of PINE64 logo or logotype derivatives if we feel that they are misused, used for commercial purposes or result in damage to our brand name.

We strongly advise anyone willing to create a derivative of our logo or brand name to reach out to a PINE64 Community associate or a Pine Store Ltd. staff member.

2021-05-21T16:03:18Z

Luke:

PINE64 brand and logo

2021-05-21T16:01:28Z

Luke:

PINE64 and the PINE64 pinecone logo are trademarked by Pine Store Limited. The trademark extends to the PINE64 brand name in writing, the PINE64 pinecone logo (referred to as logo in the document) and in some instances also to logo derivatives (see section 4.).

The brand and logo were first trademarked in 2015 by then Pine Microsystems Inc. Pine Store Ltd. permits the usage of the brand name, the logo and logo derivatives for all non-commercial software endeavours and non-software projects undertaken by PINE64’s Community and community projects (subject to the terms outlined in this document). Pine Store Ltd. may also permit the usage of the logo and branding for commercial software and non-software goods projects upon prior agreement. PINE64 Community also permits the usage of the logo and branding to sponsored projects or community endeavours and affiliate programs (see section 3.1).

We are highly protective of our trademark and copyrights, and will seek any and all legal measures to enforce guidelines contained in this document.

=1. Presentation and typography=

The PINE64 project lototype is always capitalised: PINE64
The logotype always uses high tonal contrast, all capital letters and is preceded by the logo.
The original logotype uses Arial Std Narrow Regular, but an acceptable and frequently used variant is written in Noto Sans Telugu UI.

The PINE64 logo is a polygon geometric pinecone representation. The original logo uses five shades of blue colour.

[[File:Pine64logo.png|200px|thumb|right|PINE64 pinecone logo]]
PINE64 logo colors in HTML notation, top to bottom:
*[52accd]
*[2f82c4]
*[2969b1]
*[3d5c8b]
*[475677]

Other variants, including all-white logo and typography on black or transparent background, are in use and permitted for non-commercial usage. Other colour variations are also permitted for non-commercial use. Other variants than the official logotype may be used for commercial use following an inquiry with PINE64 Community representatives and/ or designated Pine Store Ltd. staff members.

==1.1. Slogan(s), look and branding==

The PINE64 community slogan is “Open. Friendly. Community Driven”.
PINE64 hardware packaging uses the tagline “Open Sesame”

PINE64 uses a distinct brand look which makes use of the original colour scheme of the pine cone logo (see section 1.) in conjunction with black, grey and white as background colours.
The distinct look of PINE64 organization’s (pine64.org) website, the official forum (forum.pine64.org) and the Pine Store’s (pine64.com) website is restricted to official PINE64 portals and community services. It may not be copied or imitated by community run services such as forums or websites.

==1.2. Branding on devices==

We choose to keep PINE64 branding on our devices to a minimum. Our design follows our inherent ideology that devices we sell belong to the end-users, not to us.

A PINE64 pinecone is always printed on the PCB of a single board computer or device, alongside with the hardware’s name and revision number. The full brand name is never used on our devices.

The PINE64 pinecone is also discreetly placed between the torch and camera on the PinePhone, on the LCD of the PineTab and on the SUPER key on the Pinebook Pro. This minimal branding aesthetic will also be used for future PINE64 hardware.

Packaging for PINE64 devices varies in brading implementation, ranging from plain white boxes from recycled materials to the hallmark “Open Sesame” tagline alongside PINE64 logotype from recycled cardboard.
The PinePhone also uses a distinct “PINEPHONE” logotype written in Good Times Regular font.

=2. Non-commercial usage=

Any and all derivatives of the PINE64 brand name and pinecone logo, including alterations to the original logo per bounds in section 1, are permitted for non-commercial use.

Use of the logo and brand name is permitted in communities or projects, as long as it is clearly denoted that the software, community, portal, website, subreddit, etc., does not belong to and is not administered by PINE64 community nor Pine Store Ltd.

==2.1. Examples of appropriate non-commercial usage==
*Including PINE64 logo and brand name in open source software, offered freely and free of charge, written for for PINE64 devices
*Including PINE64 logo and brand name on publicly available 3D files offered freely and free of charge
*Including PINE64 logo and brand name on software project websites to indicate that software compatibility with PINE64 hardware
*Including PINE64 logo on community run forums, subreddits, chats, etc.
*Including PINE64 logo to indicate that software is compatible with PINE64 hardware
*Any alterations to the logotype for private or community use - for example as freely distributed wallpapers, icons, emotes, etc.
*Including PINE64 slogan and distinct brand look in freely distributed and royalty free software

==2.2. Restrictions to non-commercial usage==

The PINE64 logo and logotype may not, under any circumstances, be used or associated with any software or hardware projects not related to PINE64 hardware. Our brand name look and slogan (see section 1.1) are also restricted to use on official PINE64 websites, chats, forums and hardware (but allowed on freely distributed software for PINE64 devices).

We reserve the right to request the PINE64 logo and logotype be removed if a non-profit endeavour or project doesn’t align with our rules and code of conduct. This includes, but is not limited to, any community project, endeavour or piece of software promoting any political, religious or social agendas outside the scope of what our rules and code of conduct guidelines permit.

The PINE64 logo and logotype may not, under any circumstances, be used to mislead existing or prospectus PINE64 community members into believing that software, social media account, community service, website, forum, subreddit, chat, social media account, etc., is representative of or run by official spokespersons of the PINE64 community or the Pine Store Ltd. staff members.
The PINE64 logo and brand name may not be used in a way that creates a false impression that a product or business is endorsed, sponsored by or associated with the PINE64 community or Pine Store Ltd.

=3. Commercial, affiliate and sponsorship usage=

Commercial use of the logo, logotype or brand name, as well as any derivatives or alterade logotypes, is not permitted without prior consent of Pine Store Ltd. This means that any software project, merchandise vendor or community endeavour that seeks to turn a financial profit based on the PINE64 brand name needs to first acquire appropriate consent from Pine Store Ltd.

The logo and logotype are copyrighted. Sale of any merchandise with PINE64 branding is not permitted without an agreement from the Pine Store Ltd. This applies to both goods in physical or digital form.

Projects, events or other engagements sponsored by PINE64 Community need to clearly indicate PINE64’s relation to the sponsorship by proceeding the logotype with text to the effect of “Sponsored by” or placing PINE64 branding in a dedicated “Sponsors” section. See 3.1 for details

We will seek any and all legal measures to enforce compliance with the use of all our copyrights and the PINE64 trademark.

==3.1. Commercial and affiliate use or as part of sponsorship==

Any use of the PINE64 logo and brand name in digital form should adhere to guidelines in section 1. PINE64 partner projects, business partners, affiliate programs, sponsored programs or events, etc. are welcome to reach out to PINE64 representatives and/ or Pine Store Ltd. staff members for graphical assets (e.g. the logo and logotype) and to consult usage.

Use of the PINE64 logo and branding on physical merchandise, such as T-shirts, hoodies, caps, cups, etc. needs to include a registered trademark symbol ® following the banding.

The PINE64 logo and brand name must appear less prominent than the business’ or project’s logo and brand name. The purpose for using the PINE64 logo or brand name needs to be indicated on a business’ or project’s website. In example, if the purpose of using PINE64 branding is to indicate partnership, then our branding should be preceded by text to the effect of “In partnership with PINE64” or by placing our branding in a dedicated “Partners” section on a website.

In the case of sponsorship, sponsors are asked to include an identification of PINE64’s affinity with the said sponsored project. This includes, but is not limited to, placing PINE64 logo and/ logotype in a “Sponsors” section or being processed by “Sponsored by” to indicate sponsorship.

==3.2 Applying for inclusion of branding in commercial application or sponsorship==

For business, partnership or sponsorship inquiries please email: info@pine64.org
Applications are reviewed on a case-by-case basis.

==3.3 Examples of appropriate commercial, sponsorship or affiliate usage==

*Including PINE64 logo and brand name on a dedicated “sponsors” page or in a designated “sponsors” section of a webpage
*Including PINE64 logo and brand name on a partner project’s website, with preceding text to the effect of “in partnership with PINE64” or in a designated “partners” section
*Including PINE64 logo and brand name on physical merchandise with a registered trademark symbol ®
*Including PINE64 logo on product packaging to indicate compatibility with PINE64 hardware
*Including PINE64 logo and brand name in paid software and associated promotional materials (e.g. on business’ website), to indicate compatibility with PINE64 hardware
*Including PINE64 logo as part of promotional materials by partner projects or affiliated businesses upon prior agreement

==3.4 Restrictions to commercial usage==

No business, sponsored project or affiliate may use the PINE64 logo and logotype to mislead existing or prospectus PINE64 community members into believing that software, community service, social media account, website, forum, subreddit, chat, social media account, etc., is representative of or run by official spokespersons of the PINE64 community or the Pine Store Ltd. staff members.
We reserve the right to request a sponsored event, affiliate program, business or partner project to remove PINE64 branding under particular circumstances.

=4. Creation of derivative logos and logotypes=

Anyone is allowed to create PINE64 derivatives for personal or community usage. This extends to any form of artwork, community-made mockups or any other activity clearly identifiable community-activity that does not mislead existing or prospectus community members to believe it is PINE64 official material.

Derivatives of the PINE64 logo and banding are permitted for non-commercial usage, granted they do not mislead prospectus or existing PINE64 community members into believing the material is PINE64 sanctioned or issued by PINE64. Derivatives of the logo and branding may not be used in a context that could cause brand damage nor for commercial purposes.

Derivatives of PINE64 branding may still be subject to our copyright and as such need to adhere to restrictions outlined in section 2.2. We may request the removal of PINE64 logo or logotype derivatives if we feel that they are misused, used for commercial purposes or result in damage to our brand name.

We strongly advise anyone willing to create a derivative of our logo or brand name to reach out to a PINE64 Community associate or a Pine Store Ltd. staff member.

2020-05-28T20:46:20Z

Luke:

The PinePhone is a smartphone created by Pine64, capable of running mainline Linux and supported by many partner projects. The BraveHeart Edition was the first publicly-available version of the phone, though it came without a fully functional OS (factory test image) and was geared specifically towards tinkerers and hackers. Its successor is the Community Edition, which is expected to be shipped in May 2020 and will be available for at least five years.

== First time installation ==

[[File:PinePhone-3.jpg|400px|thumb|right|PinePhone is capable of running a multitude of different Linux mobile OSes]]

From the factory the battery has a sticker on it that isolates the battery from the phone. The battery '''will not''' charge until this is removed.

After unboxing remove the back panel using the notch in the corner of the back panel. Then remove the battery and peel off the clear plastic sticker below it that isolates the charging contact. Then replace the battery. See [[PinePhone#Battery|Battery]] for more information.

== Specifications ==

'''Dimensions:''' 160.5 x 76.6 x 9.2mm 
'''Weight:''' Between 180-200 grams 
'''SIM Card:''' Micro-SIM 
'''Display:'''
: '''Size:''' 5.95 inches (151mm) diagonal
: '''Type:''' HD IPS capacitive touchscreen, 16M colors
: '''Resolution:''' 1440x720, 18:9 ratio 
'''System on Chip:''' [https://linux-sunxi.org/A64 Allwinner A64] 
'''RAM:''' 2GB LPDDR3 SDRAM 
'''Internal Storage:''' 16GB eMMC, extendable up to 2TB via microSD, supports SDHC and SDXC 
'''Back Camera:''' Single 5MP, 1/4", LED Flash 
'''Selfie Camera:''' Single 2MP, f/2.8, 1/5" 
'''Sound:''' Loudspeaker, 3.5mm jack & mic (jack doubles as hardware UART if killswitch 6 is deactivated) 
'''Communication: [http://files.pine64.org/doc/datasheet/project_anakin/LTE_module/Quectel_EG25-G_LTE_Specification_V1.1_Preliminary_20180522%20(002).pdf EG25-G]'''
: '''LTE:''' B1, B2, B3, B4, B5, B7, B8, B12, B13, B18, B19, B20, B25, B26, B28, B38, B39, B40, B41
: '''WCDMA:''' B1, B2, B4, B5, B6, B8, B19
: '''GSM:''' 850, 900, 1800, 1900 (MHz)
: '''WLAN:''' Wi-Fi 802.11 b/g/n, single-band, hotspot
: '''Bluetooth:''' 4.0, A2DP
: '''GNSS:''' GPS/GLONASS/BeiDou/Galileo/QZSS, with A-GPS
'''Sensors:''' Accelerometer, gyro, proximity, ambient light, compass 
'''[[#Killswitch configuration|Killswitches]]:''' Modem, Wifi & Bluetooth, Microphone, Cameras 
'''[[#Battery|Battery]]:''' [https://wiki.pine64.org/images/0/04/PinePhone_Battery_model_QZ01-396172-2750.pdf Lithium ion] Rated Capacity 2800mAh (10.64Wh), Typical Capacity 3000mAh (11.40Wh) (nominally replaceable with any Samsung J7 form-factor battery) 
'''I/O:''' USB Type-C, USB Host, DisplayPort Alternate Mode output, 15W 5V 3A Quick Charge, follows USB PD specification

== Hardware Revisions ==

# [[Project Anakin]]
# [[Project Don't be evil|"Project Don't Be Evil" devkit]]
# [[PinePhone v1.0 - Dev|PinePhone v1.0 - Developer batch]]
# [[PinePhone v1.1 - Braveheart]]
# [[PinePhone v1.2‎]] - Community Edition

== Hardware Addons ==

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

=== USB-C Connector ===

The USB-C can be used to power the device, and offers USB2 host and OTG possibilities, and also can make use of the USB-C capability to integrate HDMI signals. Some USB-C hubs are available that offer power throughput, USB connection, HDMI port and Ethernet connection. The driver that would make this connection available is not supported at this time.

=== Pogo Pins ===

The PinePhone has 6 pogo pins on the back allowing for custom hardware extensions such as wireless charging or an IR blaster. The pogo pins provide access to an interrupt line, power input to charge the battery, 3.3 V power source (disputed: see [[PinePhone_v1.1_-_Braveheart#Pogo_Pins_supply_5v0.2C_not_3v3]]), and an I2C interface.

'''A step/stl/stp (3D model) file for the back cover is [http://files.pine64.org/doc/PinePhone/PinePhone%20Back%20Cover%20ver%200.5.stp freely available] for creating custom cases that interface with the pogo pins.'''

=== Serial console ===

[[File:Uart pinephone connection.gif|250px|thumb|left|UART serial connector for PineBook and PinePhone]]
The PinePhone has a serial port in the headphone connector, it's activated by the 6th contact on the dipswitch. If the switch is on then the headphone connector is in audio mode, if it's off then it's in UART mode. This uart serial connection can also be used for communication with other devices from the PinePhone.

The UART is 115200n8

The pinout for the serial connector on the tablet side is:

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

The serial connection is 3.3V

You can also buy the debug cable from [https://store.pine64.org PINE64 Store]
The store cable uses a 4 ring plug, as seen in the [http://files.pine64.org/doc/pinebook/guide/Pinebook_Earphone_Serial_Console_Developer_Guide.pdf PDF], but a 3 ring plug works just as well. That cable uses a CH340 chipset based serial to USB converter, but any 3.3v serial connection can be used.

== Killswitch configuration ==

[[File:PinePhone switches.jpeg|400px|thumb|right|Photo of BraveHeart switches from OSAKANA TARO on Twitter]]

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

# Modem: On enables 2G/3G/4G communication and GNSS hardware, off disables.
# WiFi/BT: On enables Wi-Fi and Bluetooth communication hardware, off disables.
# Microphone: On enables audio input from on-board microphones (not 3.5mm jack), off disables.
# Rear camera: On enables the rear camera, off disables.
# Front camera: On enables the front camera, off disables.
# Headphone: On enables audio input and output via the 3.5mm audio jack, off switches the jack to hardware UART mode.

== Battery ==

The [https://wiki.pine64.org/images/0/04/PinePhone_Battery_model_QZ01-396172-2750.pdf supplied battery] is [https://forum.pine64.org/showthread.php?tid=8120&pid=53307#pid53307 meant to be] compatible with Samsung part number EB-BJ700BBC / BBE / CBE from the 2015 J7 phone. There is [https://forum.pine64.org/showthread.php?tid=8563&pid=55053#pid55053 a report] that the EB-BJ700CBE isn't quite the same size, causing the back not to fit properly.

The battery terminals, in order from nearest the edge to nearest the middle, are:

# +ve
# thermistor
# -ve
# not connected

The battery includes a protection circuit that isolates it in a number of fault conditions, including if it is discharged too far. The fully discharged battery [https://forum.pine64.org/showthread.php?tid=8563&pid=55377#pid55377 can be recharged] by connecting the phone to a charger. Once it has charged sufficiently you will be able to boot the phone.

If your battery is hard to remove from the phone, try loosening the screws around it. Possibly cutting up a piece of plastic and sliding it under the battery as a pull tab can work too.

{{Note|The BraveHeart Edition ships with a plastic sticker between the battery and the phone. You need to open the back cover (gently), then remove the battery and finally remove the sticker. This is to protect the device from turning on during shipping.}}

[[File:PinePhone battery1.png|600px|thumb|centre|Photo of Brave Heart case from OSAKANA TARO on Twitter]]
[[File:PinePhone battery3.jpeg|600px|thumb|centre|Photo of Brave Heart battery sticker from OSAKANA TARO on Twitter]]

{{Hint|The EG25 modem and RTL8723CS Wifi/bluetooth do not work without battery power, even if you are supplying enough power to the PinePhone with USB-C.}}

There has been [https://forum.pine64.org/showthread.php?tid=8960 a report on the forum] that this sticker can bend the pins that make connection between the battery and the phone: please check your setup carefully after removing the sticker.

== Modem and Carrier Support ==

{{Hint|There is a document about using the modem from January 18th 2020 by user ''megi'' [https://megous.com/dl/tmp/modem.txt here]. The script at the end to disable the modem before power off is pretty essential to avoid corrupting your modem's flash memory.}}

To check if the PinePhone is supported on your carrier:

Search for your carrier on [https://www.frequencycheck.com/ frequencycheck.com] and compare the carrier's LTE/GSM/WCDMA frequencies to the PinePhone's supported frequencies (listed under the [[#Specifications|specifications]] section).

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

=== Voice Mail ===

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

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

=== APN settings ===

For tested APN settings and how to apply them see [[PinePhone APN Settings]].

== Operating Systems ==

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

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

=== Installation instructions ===

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

=== Flashing eMMC using Jumpdrive ===

[[File:jumpdrive.jpg|400px|thumb|right|Jumpdrive running on the PinePhone]]
The internal eMMC flash storage can be flashed using the Jumpdrive utility by Danct12 and Martijn from postmarketOS.
This utility boots from micro SD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.
The process of flashing and OS to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a SD card. You can use the 'DD' command or a utility such as Etcher or Gnome Disks, etc.

Latest Jumpdrive can be found [https://github.com/dreemurrs-embedded/Jumpdrive/releases/ here].

==== Detailed Usage Instructions ====

# Download the Jumpdrive image
# Flash the Jumpdrive image to a micro SD card
# Boot the PinePhone from the Jumpdrive micro SD card
# Connect the PinePhone to your computer using USB-A -> USB-C cable
# Flash the exposed (mounted) PinePhone drive with a chosen OS image
# Once the flashing process is complete, disconnect the PinePhone from your PC, power it down and remove the Jumpdrive SD card
# The process is now finished, and you can boot from eMMC

Jumpdrive also acts as a rescue image in case if you messed up your installation. To do so, you can telnet to '''172.16.42.1''', mount rootfs and fix it!

==== Resize file system ====

If you flash a 4GB image distribution (such as phosh+debian) to your eMMC, your eMMC will only have a 3.7G partition on it. To use the entire 14.7G on the eMMC, run the following commands:

# sudo cfdisk /dev/sdX
# Change to [Resize] in the ncurses program, resize the 3.7G partition to 14.7G, and [Write]
# sudo resize2fs /dev/sdXY

Replace X with your drive's name. Replace Y with the partition you resized in cfdisk.

==== Feedback ====

If you've found an issue or want to improve the tool consider these sites:

* Issues: https://github.com/dreemurrs-embedded/Jumpdrive/issues
* Pull Requests: https://github.com/dreemurrs-embedded/Jumpdrive/pulls

== PinePhone Board Information, Schematics and Certifications ==
* PinePhone Main Board Schematic:
** [http://files.pine64.org/doc/PinePhone/PinePhone%20v1.2%20Released%20Schematic.pdf PinePhone mainboard Released Schematic ver 1.2]
** [[PinePhone_v1.2|PinePhone Schematic ver 1.2 change list]]
** [http://files.pine64.org/doc/PinePhone/PinePhone%20Schematic%20v1.1%2020191031.pdf "Braveheart" PinePhone mainboard Schematic ver 1.1]
** [http://files.pine64.org/doc/PinePhone/PinePhone%20mainboard%20top%20placement%20v1.1%2020191031.pdf "Braveheart" PinePhone mainboard component top placement drawing ver 1.1]
** [http://files.pine64.org/doc/PinePhone/PinePhone%20mainboard%20bottom%20placement%20v1.1%2020191031.pdf "Braveheart" PinePhone mainboard component bottom placement drawing ver 1.1]
* PinePhone USB-C Small Board Schematic:
** [http://files.pine64.org/doc/PinePhone/PinePhone%20USB-C%20small%20board%20schematic%20v1.0%2020190730.pdf PinePhone USB-C small board Schematic ver 1.0]
** [http://files.pine64.org/doc/PinePhone/PinePhone%20USB-C%20small%20board%20top%20placement%20v1.0%2020190730.pdf PinePhone USB-C small board component top placement drawing ver 1.0]
** [http://files.pine64.org/doc/PinePhone/PinePhone%20USB-C%20small%20board%20bottom%20placement%20v1.0%2020190730.pdf PinePhone USB-C small board component bottom placement drawing ver 1.0]
* PinePhone Certifications:
** [http://files.pine64.org/doc/cert/PinePhone%20FCC%20SDOC%20Certificate-S19112602605001.pdf PinePhone FCC Certificate]
** [https://fcc.report/FCC-ID/2AWAG-PINEPHONE RF Exposure SAR Information from FCC ID site]
** [http://files.pine64.org/doc/cert/PinePhone%20CE%20RED%20Certificate-S19112602602.pdf PinPhone CE RED Certificate]
** [http://files.pine64.org/doc/cert/PinePhone%20ROHS%20Report.pdf PinePhone ROHS Report]

== Datasheets for Components and Peripherals ==
* Allwinner A64 SoC information:
** [http://files.pine64.org/doc/datasheet/pine64/A64%20brief%20v1.0%2020150323.pdf Allwinner A64 SoC Brief Introduction]
** [http://files.pine64.org/doc/datasheet/pine64/A64_Datasheet_V1.1.pdf Allwinner A64 SoC Data Sheet V1.1 (Official Released Version)]
** [http://files.pine64.org/doc/datasheet/pine64/Allwinner_A64_User_Manual_V1.0.pdf Allwinner A64 SoC User Manual V1.0 (Official Release Version)]
* X-Powers AXP803 PMU (Power Management Unit) information:
** [http://files.pine64.org/doc/datasheet/pine64/AXP803_Datasheet_V1.0.pdf AXP803 PMIC Datasheet]
* LPDDR3 (178 Balls) SDRAM:
** [http://files.pine64.org/doc/datasheet/pinephone/ATL3A1632H12A_mobile_lpddr3_11x11.5_v1.0_1600.pdf Artmem LPDDR3 Datasheet]
* eMMC information:
** [http://files.pine64.org/doc/datasheet/pinephone/Kimtigo_fbga153_16_32_64_eMMC_datasheet_v1.3.pdf Kimtigo eMMC Datasheet]
* CMOS Camera module information:
** [http://files.pine64.org/doc/datasheet/pinephone/QZ01-rear-2019-0717(HW)%20Model.pdf PinePhone 5M Pixel Real CMOS Image Sensor Module]
** [http://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC for Rear Module Datasheet]
** [http://files.pine64.org/doc/datasheet/pinephone/QZ01-front-2019-0717(HW)%20Model.pdf PinePhone 2M Pixel Front CMOS Image Sensor Module]
** [http://files.pine64.org/doc/datasheet/pinephone/GC2145%20CSP%20DataSheet%20release%20V1.0_20131201.pdf GC2145 2MP CMOS Image Sensor SoC for Front Module Datasheet]
* LCD Touch Screen Panel information:
** [http://files.pine64.org/doc/datasheet/pinephone/PinePhone%20LCD-QZ01.pdf 5.99" 1440x720 LCD IPS Panel Specification]
** [http://files.pine64.org/doc/datasheet/pinephone/ST7703_DS_v01_20160128.pdf ST7703 LCD Controller Datasheet]

** [http://files.pine64.org/doc/datasheet/pinephone/GT917S-Datasheet.pdf GOODiX GT917S Capacitive Touch Controller Datasheet]
* Lithium Battery information:
** [http://files.pine64.org/doc/datasheet/pinephone/PinePhone%20QZ01%20Battery%20Specification.pdf PinePhone Lithium Battery Specification]
** [http://files.pine64.org/doc/datasheet/pinephone/PinePhone%20QZ01%20Battery%20ZCV%20Curve%20Chart.xlsx PinePhone Lithium Battery ZCV Curve Chart]
* Wifi/BT module information:

* LTE module information:
** [http://files.pine64.org/doc/datasheet/pinephone/Quectel_EG25-G_LTE_Specification_V1.0.pdf Quectel EG25-G LTE Module Specification]
** [[Media:Quectel EC25EC21 AT Commands Manual V1.2.pdf|EC25&EC21 AT Commands Manual]]
* Sensors:
** [https://www.st.com/en/mems-and-sensors/lis3mdl.html ST LIS3MDL 3-axis Magnetomater Datasheet]
** [https://www.invensense.com/products/motion-tracking/6-axis/mpu-6050/ InvenSense MPU-6050 Six-Axis (Gyro + Accelerometer) MEMS Datasheet]
** [http://www.sensortek.com.tw/en/product/Proximity_Sensor_with_ALS.html SensorTek STK3335 Ambient Light Sensor and Proximity Sensor]
* Digital Video to USB-C Bridge:
** [https://www.analogix.com/en/system/files/AA-002281-PB-6-ANX7688_Product_Brief.pdf ANX7688 Product Brief]
* Case information:
** [http://files.pine64.org/doc/datasheet/pinephone/PinePhone%20Exploded%20Diagram%20ver%201.0.pdf PinePhone Case Exploded Diagram]
** [http://files.pine64.org/doc/datasheet/pinephone/PinePhone%20Back%20Cover.stp PinePhone Back Battery Cover 3D file]

== Developer works ==
=== Megous ===

* [https://xnux.eu/howtos/pine64-pinephone-getting-started.html Getting start with PinePhone Hardware]
* [https://xnux.eu/devices/pine64-pinephone.html#toc-pine64-pinephone State of development progress]
* [https://xnux.eu/news.html PinePhone Technical News and Update, also applies to other Allwinner devices including PINE A64 SBC]

== External links ==
* [https://store.pine64.org/?post_type=product Pine64 shop]

File:PinePhone-3.jpg

2020-05-28T20:45:29Z

Luke:

Pinebook Pro

2020-05-28T13:21:53Z

Luke: /* Privacy Switches */

= User Guide =
== Introducing PineBook Pro ==
[[File:PBP.jpg|400px|thumb|right|Pinebook Pro running stock Debian with MATE]]

The Pinebook Pro is a Linux and *BSD ARM laptop from [https://www.pine64.org/ PINE64]

It is built to be a compelling alternative to mid-ranged Chromebooks that people convert into Linux laptops. It features an IPS 1080p 14″ LCD panel, a premium magnesium alloy shell, high capacity eMMC storage, a 10,000 mAh capacity battery, and the modularity that only an open source project can deliver.

Key features include: the RK3399 SOC; USB-C for data, video-out and power-in (3A 5V); privacy switches for the microphone, BT/WiFi module, and camera; and expandable storage via NVMe (PCIe 4x) with an optional adapter.

The Pinebook Pro is equipped with 4GB LPDDR4 system memory, high capacity eMMC flash storage, and 128Mb SPI boot Flash. The I/O includes: 1x micro SD card reader (bootable), 1x USB 2.0, 1x USB 3.0, 1x USB type C Host with DP 1.2 and power-in, PCIe 4x for an NVMe SSD drive (requires an optional adapter), and UART (via the headphone jack by setting an internal switch).

The keyboard and trackpad both use the USB 2.0 protocol. The LCD panel uses eDP MiPi display protocol.

Many different Operating Systems (OS) are freely available from the open source community and partner projects. These include various flavors of Linux (Ubuntu, Debian, Manjaro, etc.) and *BSD.

== Software and OS Image Downloads ==

=== Default Debian MATE Desktop Quick Start ===

The default Operating system that ships with the Pinebook Pro is Debian 9 with MATE desktop. It has been built by a community developer called MrFixIt2001, who can be reached on the PINE64 forum or in the chats.
The newest release of the build can downloaded directly from [https://github.com/mrfixit2001/debian_desktop/releases MrFixIt2001's GitHub].

'''The default username and password is:'''
* Username: rock
* Password: rock

You can change the default ''rock'' username and ''rock'' home directory by logging into root (credentials root/root) instead of the default 'rock' user and running the following in root terminal and substituting desired username for NewUser:
[[File:UpdateScript.png|350px|thumb|right|Location of update script applet icon on stock Debian with MATE]]
<pre>
usermod -l NewUser -d /home/NewUser -m rock
</pre>

Once you log back into your new user, Bluetooth will complain about no transfer folder location. To fix this open terminal and type:
<pre>
blueman-services
</pre>

From here, select incoming folder under the 'transfer' tab.

The build includes a custom updater capable of updating uboot, the Linux kernel and numerous packages. The update script can be ran from both the userspace and the commandline. You will find a small 'Update Script' applet icon in the bottom panel, next to time and date applet.

You can run the script from the terminal using:
<pre>
sudo /usr/bin/mrfixit_update.sh
</pre>

More information about the default OS build and version history can be found on the [https://forum.pine64.org/showthread.php?tid=7830 Default OS update log] PINE64 forum thread.

=== [[Pinebook Pro_Software_Release|Pinebook Pro images]] ===
Under [[Pinebook Pro Software Release|'Pinebook Pro Software and OS Image Download Section']] you will find a complete list of currently supported Operating System images that work with the Pinebook as well as other related software.

The list includes OS images and descriptions of:

[{{fullurl:PinebookPro_Software_Release#Debian_Desktop}} http://files.pine64.org/sw/pine64_installer/json/debian.png] [[PinebookPro_Software_Release#Debian Desktop|'''Debian Desktop (microSD and eMMC Boot)''']]

[{{fullurl:PinebookPro_Software_Release#Bionic_LXDE}} http://files.pine64.org/sw/pine64_installer/json/lxde.png] [[PinebookPro_Software_Release#Bionic LXDE|'''Bionic LXDE (microSD and eMMC Boot)''']]

[{{fullurl:PinebookPro_Software_Release#Bionic_Mate}} http://files.pine64.org/sw/pine64_installer/json/mate.png] [[PinebookPro_Software_Release#Bionic Mate|'''Bionic Mate (microSD and eMMC Boot)''']]

[{{fullurl:PinebookPro_Software_Release#Manjaro_ARM}} http://files.pine64.org/sw/pine64_installer/json/fedora.png] [[PinebookPro_Software_Release#Fedora|'''Fedora (microSD and eMMC Boot)''']]

[{{fullurl:PinebookPro_Software_Release#Manjaro_ARM}} http://files.pine64.org/sw/pine64_installer/json/manjaro.png] [[PinebookPro_Software_Release#Manjaro ARM|'''Manjaro ARM (microSD and eMMC Boot)''']]

note: When upgrading from a prior release of Manjaro to version 20.1, you may need to increase the backlight as the number of steps for the backlight exposed by the kernel was changed from 256 to 4096

[{{fullurl:PinebookPro_Software_Release#Manjaro_ARM}} http://files.pine64.org/sw/pine64_installer/json/opensuse.png] [[PinebookPro_Software_Release#OpenSUSE|'''OpenSUSE (microSD and eMMC Boot)''']]

[{{fullurl:PinebookPro_Software_Release#Q4OS}} http://files.pine64.org/sw/pine64_installer/json/q4os.png] [[PinebookPro_Software_Release#Q4OS|'''Q4OS (microSD and eMMC Boot)''']]

[{{fullurl:PinebookPro_Software_Release#Armbian}} http://files.pine64.org/sw/pine64_installer/json/armbian.png] [[PinebookPro_Software_Release#Armbian|'''Armbian (microSD and eMMC Boot)''']]

[{{fullurl:PinebookPro_Software_Release#NetBSD}} http://files.pine64.org/sw/pine64_installer/json/netbsd.png] [[PinebookPro_Software_Release#NetBSD|'''NetBSD (microSD and eMMC Boot)''']]

[{{fullurl:Pinebook_Pro_Software_Release#OpenBSD}} [[File:Puffy_mascot_openbsd.png|125px]]] [[Pinebook_Pro_Software_Release#OpenBSD|'''OpenBSD release for ARM64''']]

[{{fullurl:PinebookPro_Software_Release#Chropmium}} http://files.pine64.org/sw/pine64_installer/json/chromium.jpg] [[PinebookPro_Software_Release#Chromium|'''Chromium (microSD and eMMC Boot)''']]

[{{fullurl:PinebookPro_Software_Release#Android_7.1_microSD}} http://files.pine64.org/sw/pine64_installer/json/android_7.png] [[PinebookPro_Software_Release#Android_7.1_microSD|'''Android 7.1 (microSD Boot)''']]           [{{fullurl:PinebookPro_Software_Release#Android_7.1_eMMC}} http://files.pine64.org/sw/pine64_installer/json/android_7.png] [[PinebookPro_Software_Release#Android_7.1_eMMC|'''Android 7.1 (eMMC)''']]

[{{fullurl:PinebookPro_Software_Release#Debian_Installer_for_Pinebook_Pro}} http://files.pine64.org/sw/pine64_installer/json/debian.png] [[PinebookPro_Software_Release#Debian_Installer_for_Pinebook_Pro|'''Debian Installer for Pinebook Pro''']]

[{{fullurl:Pinebook_Pro_Software_Release#Gentoo_Script_for_Pinebook_Pro}} http://files.pine64.org/sw/pine64_installer/json/gentoo.png]
[[Pinebook_Pro_Software_Release#Gentoo_Script_for_Pinebook_Pro|'''Gentoo Script for Pinebook Pro''']]

[{{fullurl:PinebookPro_Software_Release#Kali}} [[File:Kali.jpeg|125px]]] [[PinebookPro_Software_Release#Kali|'''Kali Script for Pinebook Pro (microSD and eMMC Boot)''']]

=== Quick Links to OS Images Build Sources===
'''Some of the provided OS images are still in beta or nightly build and only fit for testing purposes. These images ought to be avoided for normal usage - use them at your own risk'''
* [https://github.com/ayufan-rock64/linux-build/releases/ ayufan's Linux build repo]
* [https://github.com/ayufan-rock64/chromiumos-build/releases ayufan's Chromium OS build repo]
* [https://github.com/mrfixit2001/debian_desktop/releases mrfixit2001's Linux debian desktop build repo]

== Keyboard ==
The Pinebook Pro is available in two keyboard configurations: ISO and ANSI. Both the keyboard and trackpad in the Pinebook Pro use the USB 2.0 protocol and show up as such in xinput. The keyboard features function (Fn) keys in the F-key row, which include display brightness controls, sound volume, trackpad lock, and other functionality. There is also a custom PINE64 logo key that functions as Menu/Super key. It has also a secondary functionality for setting the privacy switches.

The keyboard firmware binary can be flashed from userspace using the provided open source utility.

Documentation for the keyboard can be found in [[#Datasheets for Components and Peripherals|Datasheets for Components and Peripherals]].

=== Typing special characters ===
The [[Wikipedia:British_and_American_keyboards#Other_keyboard_layouts|UK ISO Layout]] does not have dedicated keys for characters like the German umlauts (Ä,Ö,Ü, etc). Certain characters can still be generated by means of either key combinations or key sequences.
{| class="wikitable"
!Character
!Key combination/sequence
|-
|Ä, Ö, Ü, ä, ö, ü
|[[Wikipedia:AltGr_key|[AltGr]]]+'[' followed by [A], [O], [U], [a], [o] or [u]
|-
|µ
|[AltGr]+[m]
|-
|Ø, ø
|[AltGr]+[O], [AltGr]+[o]
|-
|@
|[AltGr]+[q] (as on the German layout)
|-
|ß
|[AltGr]+[s]
|-
|§
|[AltGr]+[S]
|-
|°
|[AltGr]+[)]
|}

=== Privacy Switches ===
There are three privacy switches mapped to the F10, F11 and F12 keys on the Pinebook Pro keyboard. They de/activate the following:

{| class="wikitable"
|+ Privacy switch function and description
! Combination
! Effect
! Description
! Notes
|-
! scope=row | PINE64 logo key+F10
| Microphone Privacy switch || CAPs lock LED blinks. 2 blinks = enabled, 3 blinks = disabled
|-
! scope=row | PINE64 logo key+F11
| WiFi Privacy switch || NUM lock LED blinks. 2 blinks = enabled, 3 blinks = disabled.
| '''Re-enabling requires reboot''' (or a [//forum.pine64.org/showthread.php?tid=8313&pid=52645#pid52645 command line hack to bind/unbind]).
|-
! scope=row | PINE64 logo key+F12
| Camera privacy switch || CAPs lock and NUM lock LEDs blink together. 2 blinks = enabled, 3 blinks = disabled
|}

'''(Press the PINE64 logo key plus F10/F11/F12) for 3 seconds)'''

The keyboard uses special firmware that operates separately of the operating system. It detects if either the F10, F11 or F12 key, and the Pine key were pressed for 3 seconds. This disables the peripherals as listed above by cutting off their power. Which has the same result as cutting off the power to each peripheral with a physical switch. This implementation is very secure since the firmware that determines whether a peripheral gets power is not a part of the Pinebook Pro’s operating system. So the power state value for each peripheral cannot be overridden or accessed from the operating system. The power state setting for each peripheral is stored across reboots.

== Trackpad ==
The trackpad is a reasonable size, has a matte finish that that your finger can slide along easily, and two actuating buttons. It is the only component of the Pinebook Pro held in place with strong adhesive tape. It supports multi-touch functionality.
Documentation for the trackpad can be found in [[#Datasheets for Components and Peripherals|Datasheets for Components and Peripherals]].
The trackpad firmware binary can be flashed from userspace using the provided open source utility (https://github.com/ayufan-rock64/pinebook-pro-keyboard-updater).

'''Everyone with a Pinebook Pro produced in 2019 should update their keyboard and trackpad firmware.'''

Before you start:

Please refer to original documentation for details.

Your Pinebook Pro should be either fully charged or, preferably, running of mains. This utility will be writing chips on the keyboard and trackpad, so a loss of power during any stage of the update can result in irrecoverable damage to your trackpad or keyboard.

The scripts ought to work on all OSs available for the Pinebook Pro. Some OSs may, however, require installation of relevant dependencies.

There are two keyboard versions of the Pinebook Pro, ISO and ANSI. You need to know which model you have prior to running the updater.
FW update steps for both models are listed below.

What you will need:

*Your Pinebook Pro fully charged or running off of mains power
*Connection to WiFi
*An external USB keyboard & mouse. Or access to the Pinebebook Pro via SSH

'''ISO Model'''

From the terminal command line:

<pre>
git clone https://github.com/ayufan-rock64/pinebook-pro-keyboard-updater
cd pinebook-pro-keyboard-updater
sudo apt-get install build-essential libusb-1.0-0-dev xxd
make
</pre>

Step 1
<pre>
cd pinebook-pro-keyboard-updater
sudo ./updater step-1 iso
sudo reboot
</pre>

Step 2 (after reboot)
<pre>
cd pinebook-pro-keyboard-updater
sudo ./updater step-2 iso
sudo reboot
</pre>

----

'''ANSI Model'''

*NOTE: Running step-1 on the ansi keyboard model will make the keyboard and trackpad inaccessible until step-2 is run, so an external keyboard must be connected to complete the update on this model!

From the terminal command line:

<pre>
git clone https://github.com/ayufan-rock64/pinebook-pro-keyboard-updater
cd pinebook-pro-keyboard-updater
sudo apt-get install build-essential libusb-1.0-0-dev xxd
make
</pre>

Step 1
<pre>
cd pinebook-pro-keyboard-updater
sudo ./updater step-1 ansi
sudo reboot
</pre>

Step 2 (after reboot)
<pre>
cd pinebook-pro-keyboard-updater
sudo ./updater step-2 ansi
sudo reboot
</pre>
When done, if some of the keys produce in-correct characters, please check your OSes' language settings. For ANSI users, the default OS shipped with English UK as the default language. You can change it to English US if desired.

=== X-Windows & trackpad settings ===
Some forum members have found that an adjustment to X-Windows will allow finer motion in the trackpad. If you use the '''Synaptic''' mouse/trackpad driver use this command to make the change live;
<pre>synclient MinSpeed=0.25</pre>
You may experiment with different settings, but 0.25 was tested as helping noticably. 
 
To make the change persist across reboots, change the file <code>/etc/X11/xorg.conf</code> similar to below;
<pre> Section "InputClass"
Identifier "touchpad catchall"
Driver "synaptics"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Option "MinSpeed" "0.25"
EndSection</pre>
The line <code>Option "MinSpeed" "0.25"</code> is the change. 
 
Another forum user built on the above settings a little, and have found these to be very good:
<pre>synclient MinSpeed=0.25
synclient FingerLow=30
synclient PalmDetect=1
synclient VertScrollDelta=64
synclient HorizScrollDelta=64</pre>

<code>FingerLow</code> has the same value as 'FingerHigh' in one config (30). It is believed to help reduce mouse movement as you lift your finger, but it's not sure if synaptic works like this.
You may find this config to be comfortable for daily use.
 

The <code>right mouse click</code> is emulated by tapping with two fingers on the trackpad. If you feel that this is not very responsive you can try this value:
<pre> synclient MaxTapTime=250 </pre>.
 

== Power Supply ==
* Input Power: 5V DC @ 3A
* Mechanical: 3.5mm OD / 1.35mm ID, Barrel jack
* USB-C 15W PD quickcharge
* Only use one power input at a time, barrel jack OR USB-C

== LEDs ==
In total there are four LEDs on the Pinebook Pro, three of which are placed in the top left side of the keyboard, and one near the barrel-port:

:1. The red LED next to the barrel-port indicates charging. It will illuminate when mains power is supplied to the Pinebook Pro from either the standard power supply unit or a USB-C smartphone charger.

:2. The power indicator LED on the Pinebook Pro supports three different colours: green, amber and red. It is also capable of flashing/blinking to indicate activity. In the default Debian with MATE build, green LED means power and red means suspend (amber is unused).

:3. The Num lock, green LED.

:4. The Caps lock, green LED.

(The Num and Caps lock LEDs have a secondary function. When the privacy switches get activated they blink to confirm that switch has been activated.)

== Webcam ==
* Streaming video resolutions supported, (un-compressed):
** 320 x 240
** 640 x 480
** 800 x 600
** 1280 x 720
** 1600 x 1200
* Still frame resolutions supported:
** 160 x 120
** 176 x 144
** 320 x 240
** 352 x 288
** 640 x 480
** 800 x 600
** 1280 x 720
** 1600 x 1200
* Some people test with the application Cheese
WIP

== Microphones ==
While it has been said that some Pinebook Pro units contain only one microphone despite having two labeled microphone holes on the outer casing, other units do indeed contain two microphones. It is presently unclear which batches have either configuration; units from the initial community batch of 1000 units (following the initial 100) are believed to contain two, populating both labeled holes.

The wires leading to both microphones connect to the mainboard with a small white plastic connector, located directly adjacent to the ribbon cable attachment point for the keyboard interface.

'''Microphones not working?'''

If pavucontrol input doesn't show microphone activity try the [[Pinebook_Pro#Privacy_Switches]]; once that is set to on do the below; if that still hasn't fixed it you may want to check that the microphone connector is plugged in (see the [[Pinebook_Pro#Technical_Reference]]).

<pre>
run alsamixer from the command line > hit F6 and select the es8316 > hit F4 to get to the capture screen > select the bar labeled ADC >
> increase the gain to 0dB > change the audio profile in pavucontrol to another with input

Additionally:
you may want to modify ADC PGA to get the levels to where you want them
</pre>

== Bluetooth and WiFi ==
[[File:PinebookPro_WirelessIC_Location.jpg|400px|thumb|right|The Pinebook Pro's AP6256 wireless module]]
===Hardware Overview===
The Pinebook Pro contains an AMPAK AP6256 wireless module to provide Wi-Fi (compliant to IEEE 802.11ac) and Bluetooth (compliant to Bluetooth SIG revision 5.0). The module contains a Broadcom transceiver IC, believed to be the BCM43456, as well as the support electronics needed to allow the Wi-Fi and Bluetooth modes to share a single antenna.

The wireless module interfaces with the Pinebook Pro’s system-on-chip using a combination of three interfaces: Bluetooth functionality is operated by serial UART and PCM, while the Wi-Fi component uses SDIO. It is unknown if the module’s Bluetooth capabilites are usable under operating systems that do not support SDIO.

The module’s RF antenna pin is exposed on the mainboard via a standard Hirose U.FL connector, where a coaxial feedline links it to a flexible adhesive antenna situated near the upper right corner of the Pinebook Pro’s battery. As the RF connector is fragile and easily damaged, it should be handled carefully during connection and disconnection, and should not be reconnected frequently.

===Issues===
Problems have been reported with the Wi-Fi transceiver’s reliability during extended periods of high throughput, especially on the 2.4 GHz band. While the cause of this has yet to be determined, switching to the 5 GHz band may improve stability.

Since the Bluetooth transceiver shares both its spectrum and antenna with 2.4 GHz Wi-Fi, simultaneous use of these modes may cause interference, especially when listening to audio over Bluetooth. If Bluetooth audio cuts out frequently, switching to the 5 GHz band – or deactivating Wi-Fi – may help.

===Wi-Fi Capabilities===
Wi-Fi on the Pinebook Pro is capable of reaching a maximum data transfer rate of approximately 433 megabits per second, using one spatial stream. The transceiver does not support multiple spatial streams or 160-MHz channel bandwidths.

The Wi-Fi transceiver supports the lower thirteen standard channels on the 2.4 GHz band, using a bandwidth of 20 MHz. At least twenty-four channels are supported on the 5 GHz band, spanning frequencies from 5180 to 5320 MHz, 5500 to 5720 MHz, and 5745 to 5825 MHz, with bandwidths of 20, 40, or 80 MHz.

Maximum reception sensitivity for both bands is approximately -92 dBm. The receiver can tolerate input intensities of no more than -20 dBm on the 2.4 GHz band, and no more than -30 dBm on the 5 GHz band. Maximum transmission power is approximately +15 dBm for either band, falling further to approximately +10 dBm at higher data transfer rates on the 5 GHz band.

With current available drivers and firmware, the Wi-Fi interface supports infrastructure, ad-hoc, and access-point modes with satisfactory reliability. Monitor mode is not presently supported. Wi-Fi Direct features may be available, but it is unclear how to make use of them under Linux.

Be aware that Linux userspace utilities, such as <code>iw</code>, may report inaccurate information about the capabilities of wireless devices. Parameter values derived from vendor datasheets, or direct testing, should be preferred to the outputs of hardware-querying tools.

===Bluetooth Capabilities===
Bluetooth data transfer speeds have an indicated maximum of 3 megabits per second, but it is unclear what practical data rates can be expected. Audio streaming over Bluetooth is functioning normally, as is networking. Bluetooth Low-Energy functions, such as interacting with Bluetooth beacons, have not yet been tested conclusively.

The Bluetooth transceiver supports all 79 channel allocations, spanning frequencies from 2402 MHz to 2480 MHz. Reception sensitivity is approximately -85 dBm, with a maximum tolerable reception intensity of -20 dBm. Bluetooth transmission power is limited to +10 dBm.

===Disabling Bluetooth===
<pre>
#disable bluetooth once
sudo rfkill block bluetooth &&

#confirm
rfkill
</pre>

<pre>
#disable bluetooth on boot**
sudo systemctl enable rfkill-block@bluetooth
</pre>

<nowiki>**This does not do what one might want on certain distros, Manjaro XFCE for example. Try the below.</nowiki>

<pre>
right click on the bluetooth panel icon > select 'plugins' > PowerManager > configuration > deselect the auto power on option
</pre>

== LCD Panel ==
* Model: BOE NV140FHM-N49
* 14.0" (35.56cm) diagonal size
* 1920x1080 resolution
* 60hz refresh rate
* IPS
* 1000:1 contrast
* 250nt brightness
* 63% sRGB coverage
* 6 bit colour
* 30 pin eDP connection

Some people have tested hardware video decode using the following;
<pre>ffmpeg -benchmark -c:v h264_rkmpp -i file.mp4 -f null -</pre>

== External ports list ==
Here are a list of the external ports. See [[Pinebook_Pro#Expansion_Ports|Technical Reference - Expansion Ports]] for port specifications.
* Left side
** Barrel jack for power, (with LED)
** USB 3, Type A
** USB 3, Type C
* Right side
** USB 2, Type A
** Standard headset jack
** MicroSD card slot

== Using the UART ==
[[File:PBPUART.jpeg|400px|thumb|right|Headphone jack UART wiring reference.
 Swapping the tx and rx around from this also works and is more traditional.
 See [http://files.pine64.org/doc/pinebook/guide/Pinebook_Earphone_Serial_Console_Developer_Guide.pdf this] official Pine64 .pdf.]]

UART output is enabled by flipping the UART switch to the ON position (item 9). To do so you need to remove the Pinebook Pro's bottom cover - please follow [https://wiki.pine64.org/index.php/Pinebook_Pro_Main_Page#Accessing_the_Internals_-_Disassembly_and_Reassembly proper disassembly and reassembly protocol]. The OFF position is towards the touchpad, the ON position is towards the display hinges.

With the UART switch in the ON position, console is relayed via the audiojack and the laptop's sound is turned OFF. Please ensure that you are using a 3.3v interface (such as the CH340, FTDI-232R, or PL2303, which are sold in both 3.3v and 5v variants) to avoid damage to the CPU.

Insert the USB plug of the cable into an open USB port on the machine which will monitor. Run the following in a terminal:

<code>
$ lsusb
</code>

you should find a line similar to this:

<code>
Bus 001 Device 058: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
</code>

You may have to clean the USB contacts of the Serial cable to get a good connection if you do not find that line.

The audio jack of the Serial cable should be fully inserted into the Pinebook Pro audio port.

Serial output should now be accessible using screen, picocom or minicom (and others).
Examples:

<code>
screen /dev/ttyUSB0 1500000

picocom /dev/ttyUSB0 -b 1500000

minicom -D /dev/ttyUSB0 -b 1500000</code>

Old versions of U-Boot do not use the UART for console output. <strike>The console function is activated by the Linux kernel. Thus, if you use a non-Pinebook Pro Linux distro and want the UART as a console, you have to manually enable it.</strike>

== Using the optional NVMe adapter ==
The optional NVMe adapter allows the use of M.2 cards that support the NVMe standard, (but not SATA standard). The optional NVMe M.2 adapter supports '''M''' & '''M'''+'''B''' keyed devices, in both 2242 & 2280 physical sizes, the most common ones available. In addition, 2230 & 2260 are also supported, though NVMe devices that use those sizes are rare.

Once you have fitted and tested your NVMe drive, please add a note to this page [[Pinebook_Pro_Hardware_Accessory_Compatibility]] to help build a list of tried and tested devices.

=== Installing the adapter ===
The V2.1-2019-0809 SSD adapter that shipped with the initial Pinebook Pro batches had significant issues. A repair kit will be shipped to address those issues.
(If necessary, it can be modified to work. There is [https://forum.pine64.org/showthread.php?tid=8322&pid=52700#pid52700 an unofficial tutorial on the forums] describing these modifications.)

The updated SSD adapter, labeled V2-2019-1107, takes into account the prior problems with trackpad interference. New orders as of Feb. 22nd, 2020 will be the updated adapter.

Actual installation instructions are a work in progress.

=== Post NVMe install power limiting ===
Some NVMe SSDs allow reducing the maximum amount of power. Doing so may reduce the speed, but it may be needed in the Pinebook Pro to both improve reliability at lower battery levels. And to reduce power used, to maintain battery life.
Here are the commands to obtain and change the power settings. The package 'nvme-cli' is required to run these commands. The example shows how to find the available power states, and then sets it to the lowest, non-standby setting, (which is 3.8 watts for the device shown);
<pre>$ sudo nvme id-ctrl /dev/nvme0
NVME Identify Controller:
...
ps 0 : mp:9.00W operational enlat:0 exlat:0 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
ps 1 : mp:4.60W operational enlat:0 exlat:0 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
ps 2 : mp:3.80W operational enlat:0 exlat:0 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
ps 3 : mp:0.0450W non-operational enlat:2000 exlat:2000 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
ps 4 : mp:0.0040W non-operational enlat:6000 exlat:8000 rrt:4 rrl:4
rwt:4 rwl:4 idle_power:- active_power:-

$ sudo nvme get-feature /dev/nvme0 -f 2
get-feature:0x2 (Power Management), Current value:00000000
$ sudo nvme set-feature /dev/nvme0 -f 2 -v 2 -s
set-feature:02 (Power Management), value:0x000002</pre>
Some NVMe SSDs don't appear to allow saving the setting with "-s" option. In those cases, leave off the "-s" and use a startup script to set the non-default power state at boot. 
If you want to test performance without saving the new power setting semi-permanantly, then leave off the "-s" option. 
 
There is another power saving feature for NVMes, APST, (Autonomous Power State Transitions). This performs the power saving & transitions based on usage. To check if you have a NVMe SSD with this feature;
<pre>$ sudo nvme get-feature -f 0x0c -H /dev/nvme0</pre>
Information for this feature, (on a Pinebook Pro), is a work in progress.

=== Using as data drive ===
As long as the kernel in use has both the PCIe and NVMe drivers, you should be able to use a NVMe drive as a data drive. It can automatically mount when booting from either the eMMC or an SD card. This applies to Linux, FreeBSD, and Chromium, using the normal partitioning and file system creation tools. Android requires testing.

=== Using as OS root drive ===
The SoC does not include the NVMe boot code, so the NVMe is not in the SoC's boot order. However, using the [https://github.com/mrfixit2001/updates_repo/blob/v1.1/pinebook/filesystem/mrfixit_update.sh U-Boot update script] from the mrfixit2001 Debian or [https://pastebin.com/raw/EeK074XB Arglebargle's modified script], and [https://github.com/pcm720/rockchip-u-boot/releases the modified u-boot images] provided by forum user pcm720, you can now add support to boot from an NVMe drive. Binary images are useable with SD, eMMC, and [[Pinebook_Pro_SPI|SPI flash]]. For OS images using the mainline kernel, there are a few variants of U-Boot available that also support NVMe as the OS drive. Though these may require writing the U-Boot to the SPI flash for proper use of the NVMe as the OS drive.

The current boot order, per last testing, for this modified U-Boot is:
*MicroSD
*eMMC
*NVMe

For more information, please refer to [https://forum.pine64.org/showthread.php?tid=8439&pid=53764#pid53764 the forum post.]

It is also possible to initially boot off an eMMC or SD card, then transfer to a root file system on the NVMe. Currently, it is necessary to have the U-Boot code on an eMMC or SD card. (A forum member [https://forum.pine64.org/showthread.php?tid=8439 posted here] about using a modified version of U-Boot with NVMe drivers, that uses <code>/boot</code> and <code>/</code> off the NVMe drive. So this may change in the future.)

Please see [[Pinebook_Pro#Bootable Storage|Bootable Storage]].

== Caring for the PineBook Pro ==
=== Bypass Cables ===
The mainboard features two (disconnected by default) bypass cables that are only to be used with the battery disconnected. The female (10) male (6) ends of the bypass cables can be connected to provide power to the mainboard if you need to run the laptop without a battery. Please refer to this [http://files.pine64.org/doc/PinebookPro/PinebookPro_Engineering_Notice.pdf engineering notice].

WARNING: Do not connect the bypass cables with the battery connected. Using the bypass cables with the battery connected can permanently damage the computer.

=== [[Pinebook_Service_Step_by_Step_Guides|Pinebook Service Step-by-Step Guides]] ===
Placeholder for Pinebook Pro specific guides

Under [[Pinebook_Service_Step_by_Step_Guides|'Service Guides for Pinebook']] you can find instructions guides concerning disassembly of:

'''Note: The installation process on Pinebook Pro similar to 14" Pinebook'''

'''Note: The installation process is the reverse order of removal guide'''

* 14″ Pinebook Lithium Battery Pack Removal Guide
* 14″ Pinebook LCD Panel Screen Removal Guide
* 14″ Pinebook eMMC Module Removal Guide

== Using the SPI flash device ==
The Pinebook Pro comes with a 128Mbit, (16MByte), flash device suitable for initial boot target, to store the bootloader. The SoC used on the Pinebook Pro boots from this SPI flash device first, before eMMC or SD card. At present, April 19, 2020, the Pinebook Pros ship without anything programmed in the SPI flash device. So the SoC moves on to the next potential boot device, the eMMC. ARM/ARM64 computers do not have a standardized BIOS, yet.

Here is some information on using the SPI flash device:

* You need the kernel built with SPI flash device support, which will supply a device similar to: <code>/dev/mtd0</code> 
* The Linux package below, will need to be available: <code>mtd-utils</code> 
* You can then use this program from the package to write the SPI device: <code>flashcp <filename> /dev/mtd0</code> 

Even if you need to recover from a defective bootloader written to the SPI flash, you can simply short pin 6 of the SPI flash to GND and boot. This will render the SoC bootrom unable to read from the SPI flash and have it fall back to reading the bootloader from other boot media like the eMMC or Micro SD card.

The procedures described above are a lot less risky than attaching an external SPI flasher and do not require any additional hardware. 
 
At present, April 19th, 2020, there is no good bootloader image to flash into the SPI flash device. This is expected to change, as there are people working on issue.

== FAQ ==
What cool software works out of the box? [[Pinebook Pro OTB Experience]]

= Software tuning guide =
Details on how to get the most out of a Pinebook Pro & its RK3399 SoC.

== Customizing Pinebook Pro's factory OS ==
Here are some hints on what you can do to customize the Pinebook Pro's factory image (aka [https://github.com/mrfixit2001/debian_desktop mrfixit2001 debian build])

=== Initial user changes, password, name, etc ===
When you first get your Pinebook Pro, you should consider setting strong passwords and making the default account your own.

* Reboot (this is just to ensure all background processes belong to the user are not running... there are other ways to achieve this but this way is easy)
* Once the machine reboots press Alt-Ctrl-F1 to bring up a text terminal
* Login as root (login: root, password: root)
* Set a strong password for the root user using the following command and it's prompts:
<pre># passwd (and follow prompts)</pre>
* Rename the rock user to your prefered username (replace myself with whatever you like):
<pre># usermod -l myself -d /home/myself -m rock</pre>
* Rename the rock group to match your preferred username:
<pre># groupmod -n myself rock</pre>
* Put your name in the account, (replace "John A Doe" with your name):
<pre># chfn -f "John A Doe" myself</pre>
* Set a strong password for the normal user:
<pre># passwd myself</pre>
* Log out of the text terminal:
<pre># logout</pre>
* Press Alt-Ctrl-F7 to go back to the login screen and then login as the normal user
* Open text terminal to fix login error: "Configured directory for incoming files does not exist";
<pre>$ blueman-services</pre>
Select "Transfer" tab and set "Incoming Folder" to myself
OR
If adduser is in distro, this is MUCH easier
sudo adduser $USER ,, fill out requested data
Then,, sudo adduser $USER $GROUP,,, 1 group at a time
To see which groups to add,,, id $USER, id rock

=== Changing the default hostname ===
Debian 9 has a command to allow you to change the hostname. You can see the current settings using;
<pre>> sudo hostnamectl
Static hostname: Debian-Desktop
Icon name: computer
Machine ID: dccbddccbdccbdccbdccbdccbdccbccb
Boot ID: ea99ea99ea99ea99ea99ea99ea99ea99
Operating System: Debian GNU/Linux 9 (stretch)
Kernel: Linux 4.4.210
Architecture: arm64</pre>
To change, use this, (with "My_Hostname" used as the example);
<pre>> sudo hostnamectl set-hostname My_Hostname</pre>
Whence done, you can re-verify using the first example.

Then you should backup and edit your <code>/etc/hosts</code> entry's name;
<pre>> sudo cp -p /etc/hosts /etc/hosts.`date +%Y%m%d`
> sudo vi /etc/hosts
127.0.0.1 localhost
127.0.0.1 My_Hostname
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
127.0.1.1 linaro-alip</pre>

=== Disable Chromium browser's prompt for passphrase & password storage ===

Perform the following steps:

* On the tool bar, hover over the Chromium icon
* Using the right mouse button, select '''Properties'''
* In the '''Command:''' line section, add <code>--password-store=basic</code> before the <code>%U</code>
* Use the '''x Close''' button to save the change
This will of course, use basic password storage, meaning any saved passwords are not encrypted. Perfectly fine if you never use password storage.

=== Changing the boot splash picture ===

The default boot splash picture can be replaced using the following instructions:

* Install '''ImageMagick''' which will do the conversion
<pre>$ sudo apt-get install imagemagick</pre>
* Create a 1920 x 1080 picture. For the best results, use a PNG image (It supports lossless compression).
* From the directory in which your new image is stored run the following commands
* Convert your image to the bootsplash raw format using imagemagick convert.
<pre>$ convert yoursplashimage.png -separate +channel -swap 0,2 -combine -colorspace sRGB RGBO:splash.fb</pre>
* Create a backup copy of your current splash screen
<pre>$ sudo cp /usr/share/backgrounds/splash.fb /usr/share/backgrounds/splash_original.fb</pre>
* Copy your new splash screen into place
<pre>$ sudo cp splash.fb /usr/share/backgrounds/splash.fb</pre>
* Set the correct permissions on the splash.fb file
<pre>$ sudo chmod 644 /usr/share/backgrounds/splash.fb</pre>
* If you do not want to see kernel console text messages, make sure you don't have '''Plymouth''' installed

=== Enabling text boot time messages ===

By default most Linux distros have a boot screen with a picture. To see all the messages, use the following;

* Backup and edit the U-Boot configuration file:
<pre>cp -p /etc/default/u-boot /etc/default/u-boot.`date +%Y%m%d`
chmod a-w /etc/default/u-boot.`date +%Y%m%d`
vi /etc/default/u-boot</pre>
Remove the '''quiet''' and '''splash''' parameters. Leave everything else alone.
* Update the U-Boot configuration:
<pre>u-boot-update</pre>
* Test and verify you get what you think you should be seeing.

== Chromium tweaks ==

=== Flags ===

From the [https://github.com/mrfixit2001/updates_repo/blob/v1.8/pinebook/filesystem/default official Debian image]:

<pre>
--disable-low-res-tiling \
--num-raster-threads=6 \
--profiler-timing=0 \
--disable-composited-antialiasing \
--test-type \
--show-component-extension-options \
--ignore-gpu-blacklist \
--use-gl=egl \
--ppapi-flash-path=/usr/lib/chromium-browser/pepper/libpepflashplayer.so \
--ppapi-flash-version=32.0.0.255 \
--enable-pinch \
--flag-switches-begin \
--enable-gpu-rasterization \
--enable-oop-rasterization \
--flag-switches-end
</pre>

== GVIM has performance issue ==
It appears that using GTK3 can cause very slow scolling, while VIM in a terminal window works fine. 
Simply revert back to using GTK2, (how to do so, is somewhat Linux distro specific).

== Kernel options ==
Here are some Pinebook Pro & its RK3399 SoC Linux specific options. If kernel version, (or version range specific), it should list that information in the description.

To see if a specific feature is enabled in the current kernel, you can use something like this;

<pre>
$ zgrep -i rockchip_pcie /proc/config.gz
# CONFIG_ROCKCHIP_PCIE_DMA_OBJ is not set
CONFIG_PHY_ROCKCHIP_PCIE=m
</pre>
If it's listed as <code>=m</code>, then it's a module. You can see if the module is loaded with;
<pre>
$ lsmod | grep -i rockchip_pcie
phy_rockchip_pcie 16384 0
</pre>
Note modules are not loaded until needed. Thus, we sometimes check the kernel configuration instead to see if a feature is configured first, then see if it's a module.

=== Hardware video decoding ===
Here is a method to check for hardware video decoding by the VPU. There are special Linux kernel modules that perform this function. 
The default Debian uses Rockchip supplied kernel module <code>rk-vcodec</code>. To check, something like this can be used;
<pre>
$ lsmod | grep rk-vcodec
or
$ zgrep RK_VCODEC /proc/config.gz
CONFIG_RK_VCODEC=y
</pre>
Note that in the above example, the Rockchip video CODEC is not built as a module, but included into the kernel. Thus, it does not show up in the list modules check. 
 
Later kernels may use a different option in the configuration as below;
<pre>
$ zgrep HANTRO /proc/config.gz
CONFIG_VIDEO_HANTRO=m
CONFIG_VIDEO_HANTRO_ROCKCHIP=y
</pre>
  

= Troubleshooting guide =
Tips, tricks and other information for troubleshooting your Pinebook Pro
=== New from the factory - Pinebook Pro won't boot / power on ===
* Some Pinebook Pros came from the factory with the eMMC switch in the disabled position. It should be switched towards the back / hinge to enable the eMMC. 
* The eMMC may have come loose during shipment. [https://wiki.pine64.org/index.php/Pinebook_Pro_Main_Page#Accessing_the_Internals_-_Disassembly_and_Reassembly Open] the back and verify that the eMMC is firmly seated. 
* You may want to try unplugging the SD card daughterboard ribbon cable and see if it powers on (remove the battery and peel off a bit of the tape before unplugging it to avoid damage). If it does, try reseating it on both sides. It might have come loose during shipping.
* It's possible that your eMMC is empty from the factory. Simply create a bootable SD card and see if your Pinebook Pro boots. If so, you can then write an OS image to the eMMC.

=== Pinebook Pro will not power on after toggling the eMMC enable/disable switch ===
* This may happen if you meant to toggle the UART/Headphone switch (9) towards touchpad for headphone use and instead you toggled the eMMC enable/disable switch (24).
* After reenabling eMMC by toggling switch (24) towards hinge, if Pinebook Pro does not turn on then press the RESET button (28). It is clearly marked 'reset' on the PCB board.

=== Pinebook Pro will not power on after removing and replacing EMI shielding ===
* Closely inspect that the shielding is firmly seated in the clips on all sides. You can be seated in the clips on one axis, and have missed on an another axis.

=== Pinebook Pro won't boot when using UART console cable ===
* If you're using the UART cable sold on the Pine Store, you may want to see if it boots after you disconnect it. Some users report that custom-made cables based on FTDI UART adapters do not cause this issue.
* Make sure your USB to serial UART device is 3.3v. Many are 5v and some even +-12v. Pinebook Pro's only support 3.3v and may act eratically when using higher voltage. Further, higher voltage could permananetly damage the Pinebook Pro's SoC.

=== WiFi issues ===
* First, check the privacy switches to make sure your WiFi is enabled. They are persistant. See [[Pinebook_Pro_Main_Page#Privacy_Switches|Privacy Switches]]
* Next, you may have to modify the <code>/etc/NetworkManager/NetworkManager.conf</code> as root user, and replace <code>managed=false</code> with <code>managed=true</code>. Then reboot.
* For connections that drop and resume too often, it might be due to WiFi power management from earlier OS releases. Later OS releases either removed WiFi power management, or default to full power. (Power management can be turned off via command line with <code>iw dev wlan0 set power_save off</code> or <code>iwconfig wlan0 power off</code>, although it is not persistent through re-boot.)
* For connections that drop under load on the default Debian, remove <code>iwconfig wlan0 power off</code> in the file <code>/etc/rc.local</code>.
* If WiFi is un-usable or often crashes when using an alternate OS, then it might because its WiFi firmware is not appropriate for the WiFi chip in the Pinebook Pro. Try the latest firmware patch from [https://gitlab.manjaro.org/tsys/pinebook-firmware/tree/master/brcm https://gitlab.manjaro.org/tsys/pinebook-firmware/tree/master/brcm]
* After re-enabling WiFi via the privacy switch, you have to reboot to restore function. There is a work around for the default Debian, (and may work with others);
        <code>sudo tee /sys/bus/platform/drivers/dwmmc_rockchip/{un,}bind <<< 'fe310000.dwmmc'</code>

=== Bluetooth issues ===
* When connecting a Bluetooth device, such as a Bluetooth mouse, it does not automatically re-connect on re-boot. In the Bluetooth connection GUI, there is a yellow star for re-connect on boot. Use that button to enable a persistent connection. It can be changed back later.
* Bluetooth-attached speakers or headset require the pulseaudio-module-bluetooth package. If not already installed, it can be installed with a package manager or with: 
<pre>sudo apt-get install pulseaudio-module-bluetooth</pre>
* When using Bluetooth-attached speakers or headset and 2.4Ghz WiFi at the same time, you may experience stuttering of the audio. One solution is to use 5Ghz WiFi if you can. Or you may try using a different 2.4Ghz channel, perhaps channel 1 or the top channel, (11 in the USA, or 13/14 in some other countries).

=== Sound issues ===
* Many reports of no sound are due to the OS, incorrect settings, or other software problems (eg. PulseAudio). So first test to see if it is a software or hardware problem, by trying another OS via SD card. (For example, if Debian is installed on the eMMC, try Ubuntu on SD.)
* If you cannot get sound from the headphone jack, but can get sound from the speakers, then the headphone / UART console switch may be set to the UART mode. You can open the back and check the position of the switch. If set to UART mode, switch it to headphone mode. See the parts layout for the location and correct position of the switch.
* When using the USB C alternate DisplayPort mode, it is possible that the audio has been re-directed through this path. If your monitor has speakers, see if they work.
* See [https://gitlab.manjaro.org/manjaro-arm/packages/community/pinebookpro-post-install/blob/master/asound.state manjaro-arm/pinebookpro-post-install /var/lib/alsa/asound.state] for some ALSA tweaks.
* See [https://gitlab.manjaro.org/manjaro-arm/packages/community/pinebookpro-audio manjaro-arm/pinebookpro-audio] for how to handle 3.5mm jack plug/unplug events with ACPID.
* Serveral users have reported that one internal speaker had reversed polarity. Thus, sound from the speakers is like an echo effect.
** Their is a software fix using alsamixer and then enable either "R invert" or "L invert", however, now the headphones have incorrect audio.
** The permanent fix is to re-wire one speaker, though this requires soldering small wires.

=== USB docks & USB C alternate mode video ===
The Pinebook Pro uses the RK3399 SoC (System on a Chip). It supports a video pass through mode on the USB C port using DisplayPort alternate mode. This DisplayPort output comes from the same GPU used to display the built-in LCD.

Here are some selection criteria for successfully using the USB C alternate mode for video:
* The device must use USB C alternate mode DisplayPort. Not USB C alternate mode HDMI, or other.
* The device can have a HDMI, DVI, or VGA connector, if it uses an active translater.
* If USB 3 is also desired from a USB dock, the maximum resolution, frame rate and pixel depth is reduced to half the bandwidth. For example, 4K @ 30hz instead of 60hz.
* USB docks that also use USB C alternate mode DisplayPort will always have USB 2 available, (480Mbps, half-duplex).

=== Keys not registering / missing keys when typing ===
This issue occurs when your thumb or edge of the palm makes contact with left or right tip of the trackpad when you type. This is due to the palm rejection firmware being too forceful. Instead of only disabling the trackpad, so your cursor does not move all over the screen, it disables both the trackpad and the keyboard.

Using Fn+F7 to disable the touchpad will keep it from also disabling the keyboard.

A [[Pinebook_Pro#Trackpad|firmware update]] has been released to address this.

=== Key Mapping ===
* See this [https://gitlab.manjaro.org/manjaro-arm/packages/community/pinebookpro-post-install/blob/master/10-usb-kbd.hwdb /etc/udev/hwdb.d/10-usb-kbd.hwdb] for some key mapping tweaks

=== Pinebook Pro gets stuck after first reboot in Trackpad Firmware Update ===
This refers to the firmware update shown here:
https://github.com/ayufan-rock64/pinebook-pro-keyboard-updater#update-all-firmwares
* If the system is not responding after the 1st reboot, it's might be easiest to do a system restore, and follow up by running the second step of the trackpad firmware update.
* System restore https://forum.pine64.org/showthread.php?tid=8229
* Firmware update https://github.com/ayufan-rock64/pinebook-pro-keyboard-updater#update-all-firmwares

=== ANSI Fn + F keys wrong for F9, F10, F11 and F12 ===
There appears to be a minor firmware issue for ANSI keyboard models of the Pinebook Pro. Some discussion and fixes have been proposed;

* Discussion thread [https://forum.pine64.org/showthread.php?tid=8744&pid=57678#pid57678 Fn + F keys screwy for F9, F10, F11 and F12]
* Proposed fix [https://github.com/ayufan-rock64/pinebook-pro-keyboard-updater/issues/14#issuecomment-576825396 (ANSI) Fn + F(9-12) has wrong assignment after firmware update #14]
  

=== After changing builtin LCD resolution, blank screen ===
Some people find that the text or icons are too small, so they attempt to change the resolution of the built-in display. Afterwards, the display is blank. 
Use the following to fix when logged into a text console as yourself, (Control-Alt-F1 through F6). After listing the resolutions, select the native resolution, (1920x1080 aka 1080p).
<pre>export DISPLAY=:0.0
xrandr -q
xrandr -s [resolution]</pre>
Once your resolution is restored, try using the Tweak app to set scaling, instead. 
 
If the above fix did not work, you can try this:
* Using a text console, (Control-Alt-F1), login with your normal user ID
* Edit the file <code>nano ~/.config/monitors.xml</code>
* Change the "width" value to "1920"
* Change the "height" value to "1080"
* If there is more than one monitor configuration listed, edit that one too. 
      Be careful to make no other changes. If needed exit without saving and re-edit.
* Save the file and exit.
* Login using the GUI and test
* If you are still loggied in via the GUI, you will have to reboot using <code>sudo shutdown -r now</code>
      After the reboot, you should be able to login to the GUI login and have the resolution back to normal.

=== Cracks in the plastic ===
There have been multiple reports of cracks in the plastic keyboard & trackpad part of the case. These are generally near here;
* Hinges
* USB ports
* Top side, around the corners
This seems to apply to the first batches in 2019. Later versions of the keyboard & trackpad have used better plastic. With replacements now in the Pine64 Store, it's possible to simply order a replacement. 
 
There have been a few reports of cracks in the plastic around the LCD display, but these appear to be less common. There are replacement LCDs with bezel available in the Pine64 Store.

= [[Pinebook_Pro_Hardware_Accessory_Compatibility|PineBookPro Hardware Compatibility]] =

Please contribute to the hardware compatibility page, which lists hardware which has been tested with the PBP, whether successful or not!

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

= Technical Reference =
== Accessing the Internals - Disassembly and Reassembly ==
[[File:Standoffs.png|400px|thumb|right|Pinebook Screw stand-offs correct placement and location]]

'''WARNING:''' Do not open the laptop by lifting the lid while the Pinebook Pro bottom cover is removed - this can cause structural damage to the hinges and/or other plastic components of the chassis such as the IO port cut-outs.

'''WARNING:''' When removing the back cover plate, use care if sliding fingertips between back cover plate and palm rest assembly. The back cover plate edges are sharp.

When disassembling the laptop make sure that it is powered off and folded closed. To remove the bottom cover of the Pinebook Pro, first remove the ten (10) Phillips head screws that hold the bottom section of the laptop in place. Remove the cover from the back where the hinges are situated by lifting it up and away from the rest of the chassis.

During reassembly, make sure that the back-screw standoffs are in place and seated correctly. To reassemble the Pinebook Pro, slide the bottom section into place so it meets the front lip of the keyboard section. Secure the front section (where the trackpad is located) in place using the short screws in the front left and right corners. Then proceed to pop in the bottom panel into place. Secure the bottom section (where hinges are located) by screwing in the left and right corners. Then screw in the remaining screws and run your finger though the rim on the chassis to make sure its fitted correctly. Note that the front uses the remaining 2 short screws.

NOTE: The screws are small and should only be finger tight. Too much force will strip the threads. If after installing screws the back cover plate has not seated properly on one side, open the display and hold the base on either side of the keyboard and gently flex the base with both hands in opposing directions. Once the side pops further in, then recheck the screws on that side. If it does not pop back in, just let it be.

NOTE: a basic 3d model to print replacement back-screw standoffs is available on Thingiverse [https://www.thingiverse.com/thing:4226648] pending release of something more definitive

== Pinebook Pro Internal Layout ==
=== Main chips ===
* RK3399 system-on-chip (1)
* LPDDR4 SDRAM (21)
* SPI NOR flash memory (29)
* eMMC flash memory (26)
* WiFi/BT module (27)

=== Mainboard Switches and Buttons ===
There are two switches on the main board: disabling the eMMC (24), and enabling UART (9) via headphone jack.

The Reset and Recovery buttons (28): the reset button performs an immediate reset of the laptop. The Recovery button is used to place the device in maskrom mode; this mode allows flashing eMMC using Rockchip tools (e.g. rkflashtools).

[[File:PBPL_S.jpg]]

=== Key Internal Parts ===
{| class="wikitable"
|+ Numbered parts classification and description
! Number
! Type
! Descriptor
|-
! scope=row | 1
| Component || RK3399 System-On-Chip
|-
! scope=row | 2
| Socket || PCIe 4X socket for optional NVMe adapter
|-
! scope=row | 3
| Socket || Speakers socket
|-
! scope=row | 4
| Socket || Trackpad socket
|-
! scope=row | 5
| Component || Left speaker
|-
! scope=row | 6
| Connector || Male power bridge connector
|-
! scope=row | 7
| Socket || Keyboard Socket
|-
! scope=row | 8
| Component || Optional NVMe SSD adapter
|-
! scope=row | 9
| Switch || UART/Audio switch - outputs UART via headphone jack
|-
! scope=row | 10
| Socket || Female power bridge socket
|-
! scope=row | 11
| Socket || Battery socket
|-
! scope=row | 12
| Component || Trackpad
|-
! scope=row | 13
| Component || Battery
|-
! scope=row | 14
| Component || Right speaker
|-
! scope=row | 15
| Socket || MicroSD card slot
|-
! scope=row | 16
| Socket || Headphone / UART jack
|-
! scope=row | 17
| Socket || USB 2.0 Type A
|-
! scope=row | 18
| Socket || Daughterboard-to-mainboard ribbon cable socket
|-
! scope=row | 19
| Cable || Daughterboard-to-mainboard ribbon cable
|-
! scope=row | 20
| Component || microphone
|-
! scope=row | 21
| Component || LPDDR4 RAM
|-
! scope=row | 22
| Socket || Mainboard-to-daughterboard ribbon cable socket
|-
! scope=row | 23
| Socket || Microphone socket
|-
! scope=row | 24
| Switch || Switch to hardware disable eMMC
|-
! scope=row | 25
| Antenna || BT/WiFI antenna
|-
! scope=row | 26
| Component || eMMC flash memory module
|-
! scope=row | 27
| Component ||BT/WiFi module chip
|-
! scope=row | 28
| Buttons || Reset and recovery buttons
|-
! scope=row | 29
| Component || SPI flash storage
|-
! scope=row | 30
| Socket || eDP LCD socket
|-
! scope=row | 31
| Socket || Power in barrel socket
|-
! scope=row | 32
| Socket || USB 3.0 Type A
|-
! scope=row | 33
| Socket || USB 3.0 Type C
|}

=== Smallboard detailed picture ===

[[File:Pinebook_pro_smallboard.jpg]]

== Bootable Storage ==
The Pinebook Pro is capable of booting from eMMC, USB 2.0, USB 3.0, or an SD card. It cannot boot from USB-C. The boot order of the hard-coded ROM of its RK3399 SoC is: SPI NOR, eMMC, SD, USB OTG.

At this time, the Pinebook Pro ships with a Debian + MATE build with [https://www.denx.de/wiki/U-Boot/ uboot] on the eMMC. Its boot order is: SD, then eMMC. Booting off USB storage is not currently available, but will be in the future.

(An update has been pushed for the default Debian + MATE build that improves compatibility with booting other OSs from an SD card. In order to update, fully charge the battery, establish an internet connection, click the update icon in the toolbar, and then reboot your Pinebook Pro. Please see [https://forum.pine64.org/showthread.php?tid=7830 this log] for details.)

Please note that PCIe, the interface used for NVMe SSD on the Pinebook Pro, is not bootable on the RK3399 and therefore is not a part of the boot hierarchy. It is possible to run the desired OS from NVMe by pointing extlinux on the eMMC to rootfs on the SSD. This requires uboot, the Kernel image, DTB, and extlinux.conf
in a /boot partition on the eMMC.

=== eMMC information ===
The eMMC appears to be hot-pluggable. This can be useful if trying to recover data or a broken install. Best practice is probably to turn the eMMC switch to off position before changing modules.

The eMMC storage will show up as multiple block devices:
*mmcblk1boot0 - eMMC standard boot0 partition, may be 4MB
*mmcblk1boot1 - eMMC standard boot1 partition, may be 4MB
*mmcblk1rpmb - eMMC standard secure data partition, may be 16MB
*mmcblk1 - This block contains the user areas

Only the last is usable as regular storage device in the Pinebook Pro.
The device number of "1" shown above may vary, depending on kernel.

If the eMMC module is enabled after boot from an SD card, you can detect this change with the following command:
<pre>
echo 'fe330000.sdhci' | tee /sys/bus/platform/drivers/sdhci-arasan/unbind
echo 'fe330000.sdhci' | tee /sys/bus/platform/drivers/sdhci-arasan/bind
</pre>

=== Boot sequence details ===
The RK3399's mask 32KB ROM boot code looks for the next stage of code at byte off-set 32768, (sector 64 if using 512 byte sectors). This is where U-Boot code would reside on any media that is bootable.

== Pinebook Pro Dimensions ==
* Dimensions: 329mm x 220mm x 12mm (WxDxH)
* Weight: 1.26Kg
* Screws
** Philips head type screws
** M2 flat head machine screws (measurements in mm)
** 4 x Small screws (used along the front edge): Head - 3.44, Thread Diameter - 1.97, Thread Length - 2.1, Overall length - 3.05
** 6 x Large screws: Head - 3.44, Thread Diameter - 1.97, Thread Length - 4.41, Overall Length - 5.85
* Rubber Feet
** 18mm diameter
** 3mm height
** Dome shaped

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

=== CPU Architecture ===
* big.LITTLE architecture: Dual Cortex-A72 + Quad Cortex-A53, 64-bit CPU
** Full implementation of the ARM architecture v8-A instruction set (both AArch64 and AArch32)
** ARM Neon Advanced SIMD (single instruction, multiple data) support for accelerated media and signal processing computation
** ARMv8 Cryptography Extensions
** VFPv4 floating point unit supporting single and double-precision operations
** Hardware virtualization support
** TrustZone technology support
** Full CoreSight debug solution
** One isolated voltage domain to support DVFS
* Cortex-A72 (big cluster):
** [https://developer.arm.com/products/processors/cortex-a/cortex-a72 Dual-core Cortex-A72 up to 2.0GHz CPU]
** Superscalar, variable-length, out-of-order pipeline
** L1 cache 48KB Icache and 32KB Dcache for each A72
** L2 cache 1024KB for big cluster
* Cortex-A53 (little cluster):
** [https://developer.arm.com/products/processors/cortex-a/cortex-a53 Quad-core Cortex-A53 up to 1.5GHz CPU]
** In-order pipeline with symmetric dual-issue of most instructions
** L1 cache 32KB Icache and 32KB Dcache for each A53
** L2 cache 512KB for little cluster
* Cortex-M0 (control processors):
** [https://developer.arm.com/ip-products/processors/cortex-m/cortex-m0 Cortex-M0 CPU]
** Two Cortex-M0 cooperate with the central processors
** Architecture: Armv6-M
** Thumb/Thumb2 instruction set
** 32 bit only

=== 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 provide 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 ===
* RAM Memory:
** LPDDR4
** Dual memory channels on the CPU, each 32 bits wide
** Quad memory channels on the RAM chip, each 16 bits wide, 2 bonded together for each CPU channel
** 4GB as a single 366 pin mobile RAM chip
* Storage Memory:
** 64GB eMMC module, can be upgraded to a 128GB eMMC module. (The initial PINE64 community build version shipped with a 128GB eMMC.)
** eMMC version 5.1, HS400, 8 bit on RK3399 side

=== Video out ===
* USB-C Alt mode DP
* Up to 3840x2160 p60, dependant on adapter, (2 lanes verses 4 lanes)

=== Expansion Ports ===
* MicroSD card:
** Bootable
** Supports SD, SDHC and SDXC cards, up to 512GB tested. SDXC standard says 2TB is the maximum.
** Version SD3.0, (MMC 4.5), up to 50MB/s
** SD card Application Performance Class 1 (A1), (or better), recommended by some users, for better IOPS
* USB ports:
** 1 x USB 2.0 Type-A Host Port, bootable
** 1 x USB 3.0 Type-A Host Port, 5Gbps, is not bootable
** 1 x USB 3.0 Type-C OTG Port, 5Gbps, (includes laptop charging function), is not bootable
** Note that high power USB devices may not work reliably on a PBP. Or they may draw enough power to drain the battery even when the PBP is plugged into A.C. One alternative is externally powered USB devices.
* Headphone jack switchable to UART console mux circuit

== Additional hardware ==
Hardware that is not part of the SoC.

=== Battery ===
* Lithium Polymer Battery (10,000 mAH)

=== Display ===
* 14.0" 1920x1080 IPS LCD panel

=== Audio ===
* 3.5mm stereo earphone/microphone plug
* Built-in stereo speakers:
** Oval in design
** 3 mm high x 20 mm x 30 mm

=== Network ===
* WiFi:
** 802.11 b/g/n/ac
** Dual band: 2.4Ghz & 5Ghz
** Single antenna
* Bluetooth 5.0

=== Optional NVMe adapter ===
* PCIe 2.x, 5GT/s per lane
* 4 PCIe lanes, can not be bifurcated, (however, can be used with 1 or 2 lane NVMe cards)
* '''M''' keyed, though '''M'''+'''B''' keyed devices will work too
* Maximum length for M.2 card is 80mm (M.2 2280). The following sizes will also work: 2230, 2242, 2260
* Power: 2.5W continuous, 8.25W peak momentary
* Does not support SATA M.2 cards
* Does not support USB M.2 cards

== Pinebook Pro Schematics and Certifications ==
* Pinebook Pro Main Board Schematic And Silkscreen:
** [http://files.pine64.org/doc/PinebookPro/pinebookpro_v2.1_mainboard_schematic.pdf Pinebook Pro Main Board ver 2.1 Schematic]
** [https://wiki.pine64.org/images/3/30/Pinebookpro-v2.1-top-ref.pdf Pinebook Pro ver 2.1 Top Layer Silkscreen]
** [https://wiki.pine64.org/images/b/b7/Pinebookpro-v2.1-bottom-ref.pdf Pinebook Pro ver 2.1 Bottom Layer Silkscreen]
* Pinebook Pro Daughter Board Schematic:
** [http://files.pine64.org/doc/PinebookPro/pinebookpro_v2.1_daughterboard_schematic.pdf Pinebook Pro Daughter Board ver 2.1 Schematic]
* Optional Pinebook Pro NVMe Adapter Schematic:
** [http://files.pine64.org/doc/PinebookPro/pinebookpro_v2.1_NVMe-adapter_schematic.pdf Pinebook Pro NVMe Adapter Board ver 2.1 Schematic]
* Serial Console Earphone Jack Pinout:
** [http://files.pine64.org/doc/pinebook/guide/Pinebook_Earphone_Serial_Console_Developer_Guide.pdf Pinkbook Serial Console Earphone Jack Pinout]
* Pinebook Pro Case:
** [https://send.firefox.com/download/b34c14f3e0a3d66d/#15Cx1vBaGKmJr57y85U2qQ AutoCAD DWG File]
* Pinebook Pro Certifications:
** [http://files.pine64.org/doc/cert/Pinebook%20Pro%20FCC%20Certificate-S19071103501001.pdf Pinebook Pro FCC Certificate]
** [http://files.pine64.org/doc/cert/Pinebook%20Pro%20CE%20RED%20Certificate-S19051404304.pdf Pinebook Pro CE Certificate]
** [http://files.pine64.org/doc/cert/Pinebook%20Pro%20ROHS%20Compliance%20Certificate.pdf Pinebook Pro RoHS Certificate]

== Datasheets for Components and Peripherals ==
* Rockchip RK3399 SoC information:
** [http://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]
** [http://files.pine64.org/doc/datasheet/rockpro64/RK808%20datasheet%20V0.8.pdf Rockchip RK808 Datasheet V0.8]
* LPDDR4 (366 Balls) SDRAM:
** [http://files.pine64.org/doc/datasheet/PinebookPro/micron%20SM512M64Z01MD4BNK-053FT%20LPDDR4%20(366Ball).pdf Micron 366 balls Mobile LPDDR4 Datasheet]
* eMMC information:
** [http://files.pine64.org/doc/rock64/PINE64_eMMC_Module_20170719.pdf PINE64 eMMC module schematic]
** [http://files.pine64.org/doc/rock64/usb%20emmc%20module%20adapter%20v2.pdf PINE64 USB adapter for eMMC module V2 schematic]
** [http://files.pine64.org/doc/rock64/USB%20adapter%20for%20eMMC%20module%20PCB.tar PINE64 USB adapter for eMMC module PCB in JPEG]
** [http://files.pine64.org/doc/datasheet/pine64/SDINADF4-16-128GB-H%20data%20sheet%20v1.13.pdf SanDisk eMMC Datasheet]
* SPI NOR Flash information:
** [http://files.pine64.org/doc/datasheet/pine64/w25q128jv%20spi%20revc%2011162016.pdf WinBond 128Mb SPI Flash Datasheet]
** [https://wiki.pine64.org/images/b/b9/Ds-00220-gd25q127c-rev1-df2f4.pdf GigaDevice 128Mb SPI Flash Datasheet (UPDATED)]
* Wireless related info:
** [http://files.pine64.org/doc/datasheet/PinebookPro/AP6256%20datasheet_V1.7_12282018.pdf AMPAK AP6256 11AC Wi-Fi + Bluetooth5 Datasheet]
* Audio Codec (ES8316)
** [http://everest-semi.com/pdf/ES8316%20PB.pdf Everest ES8316 Audio Codec]
* LCD Panel:
** [http://files.pine64.org/doc/datasheet/PinebookPro/NV140FHM-N49_Rev.P0_20160804_201710235838.pdf 14" 1920x1080 IPS LCD Panel datasheet]
* Internal USB 2 hub:
** [https://wiki.pine64.org/images/3/39/GL850G_USB_Hub_1.07.pdf GL850G USB Hub 1.07.pdf]
* Touchpad information:
** [http://files.pine64.org/doc/datasheet/PinebookPro/YX%20HK-9562%20HID%20I2C%20Specification.pdf Touchpad Specification for Pinebook Pro model]
* Keyboard information:
** [http://www.sinowealth.com/ftp/ph/SH68F83/SH68F83V2.0.pdf Sinowealth SH68F83 Datasheet]
** US ANSI: XK-HS002 MB27716023
* Full HD Camera sensor:
** [http://files.pine64.org/doc/datasheet/PinebookPro/HK-2145-263.pdf Full HD Camera module specification in Chinese]
** [http://files.pine64.org/doc/datasheet/PinebookPro/GC2145%20CSP%20DataSheet%20release%20V1.0_20131201.pdf GalaxyCore GC2145 Full HD Camera Sensor Data Sheet]
* Lithium Battery information:
** [http://files.pine64.org/doc/datasheet/pinebook/40110175P%203.8V%2010000mAh规格书-14.pdf 10000mAH Lithium Battery Specification for 14" model]
* NVMe adapter:
** [https://datasheet.octopart.com/FH26W-35S-0.3SHW%2860%29-Hirose-datasheet-26676825.pdf Compatible, not OEM! Use FH26-35S-0.3SHW flat flex connector]

== Versions ==
Pinebook Pro v1 and v2 were prototype models that did not make it to the public. The "first batch" (First 100 forum preorders) onward are v2.1. [https://forum.pine64.org/showthread.php?tid=8111]

=Skinning and Case Customization=
* Template files for creating custom skins. Each includes template layers for art placement, and CUT lines.
**[https://drive.google.com/open?id=1UKFlC53DO0GJm3Hz1E_669n_HhI45e4n Case Lid Template]
**[https://drive.google.com/open?id=1Q6bKGarMDhvWz3HdGvhL5qDhyHb546ve Case Bottom Template]
**[https://drive.google.com/open?id=1ugI74ygNJ3EN5jXks5jKvdpEAoxIzHo4 Case Palmrest Template]

= Other Resources =
* [https://forum.pine64.org/forumdisplay.php?fid=111 Pinebook Pro Forum]
* [https://forum.pine64.org/forumdisplay.php?fid=98 ROCKPro64 Forum]
* [[RockPro64 Guides]]
* [https://riot.im/app/#/room/#pinebook:matrix.org Matrix Channel] (No login required to read)
* [http://www.pine64.xyz:9090/?channels=ROCK64 ROCK64/ROCKPro64 IRC Channel]
* [https://discordapp.com/channels/463237927984693259/622348681538043924 Discord Channel]
* [https://github.com/rockchip-linux Rockchip Linux GitHub Repo]
* [http://opensource.rock-chips.com/ Rockchip Open Source Wiki]