PINE64 - User contributions [en]

PinePhone 1.2 VCONN Hardware Fix

2020-09-02T11:47:53Z

Jbit: Add to PinePhone category

This page details a hardware fix for an issue that affects some early PinePhone units (fixed since 1.2a included).

The issue was [[PinePhone_v1.1_-_Braveheart#USB-C_CC_pins_are_pulled_to_the_GND_by_AW3512_.28VCONN_switches.29_when_VCONN_is_off | originally reported here]] by megi.

TODO: Add more pictures and schematics, better reference the fix origin and tradeofs, remove TODOs/FIXMEs.

== Affected Units ==
# (FIXME confirm this) [[Project Don't be evil|"Project Don't Be Evil" devkit]]
# (FIXME confirm this)[[PinePhone v1.0 - Dev|PinePhone v1.0 - Developer batch]]
# [[PinePhone v1.1 - Braveheart]]
# [[PinePhone v1.2‎]] - Community Edition

== Disclaimer ==

This fix requires desoldering tiny (1 mm per 1 mm, from the datasheet) BGA components, therefore some experience with soldering is highly recommended.

== Issue description ==
[[File:Martjin_VCONN_switches_1.1.jpg|thumb|frame|Close-up picture of the two identical switches the issue originates from, with the ANX USB controller in the frame]]

[[File:Schematic_VCONN_switches.png|thumb|frame|Excerpt from the PinePhone schematic showing the two components.]]

The USB standard [https://microchipdeveloper.com/usb:tc-pins specifies] that both halves (top and bottom) of the USB-C port contains one "CC" pin (CC1 and CC2, respectively). A regular cable will connect a CC pin from one end to the other end. This allows detecting which way the cable is plugged. Some active USB-C cables exist (both "e-marked" and "managed active cables"); they contain a chip, which needs to be powered. This is done by having one of the cable end connect its CC pins to 5V and VCONN, and requires switches to plug the right CC pin to the right voltage.

The issue arises due to the switches that were chosen up to v1.2a (the a revision excluded) of the PCB assembly: the [https://www.awinic.com/cn/index/pageview/catid/122/id/2.html infamous AW3512], labelled U1305 and U1309 on the schematic. Instead of leaving the output pin "dangling" with a high impedance when disabled, the switch pull the output down. This feature is intended for discharging a capacitor, hence its "Quick output discharge" name. This is an excerpt from the datasheet:

<q> The AW3512/AW35122 includes the Quick Output Discharge (QOD) feature, in order to discharge the application capacitor connected on OUT pin.When EN pin is set to low level (disable state), a discharge resistance with a typical value of 276Ω (AW35122: 75Ω)is connected between the output and ground, pull down the output and prevent it from floating when the device is disabled.</q>

This issue prevents cable plug/orientation detection and USB-PD communication. ANX always sees cable as plugged even if none is plugged. There's no SW workaround for automatic detection of cable plug or power role.

In SW this could theoretically be worked around by manual selection of PinePhone's data and power role by the user, but hasn't been attempted, and might damage hardware if done incorrectly.

== Workaround ==

HW workaround is desoldering U1305 and U1309 switches (BGA like packages). This will void the VCONN control, but it will release the CC pins for their proper connection detection and negotiation roles.

=== Tradeoffs ===
Voiding the VCONN control might (TODO: gather more data) prevent some accessories from working, notably those using an active cable.

== Proper fix ==

HW fix is to replace AW3512 with a variant of the chip that preserves the EN signal polarity and that doesn't have the "quick discharge function" that ties the output to the GND via a 75 Ohm resistor when the switch is OFF. mozzwald used NCP334FCT2G as a replacement.

PCBA revision 1.2a onwards should incorporate that fix. (TODO: confirm this).

== Sources and tutorials ==
* [https://megous.com/dl/tmp/pp-usbc-fix.jpg megi's writeup]
* [https://xnux.eu/devices/feature/anx7688.html another writeup from megi] with a few words on firmware
* [https://www.youtube.com/watch?v=xf8OJtjNWUM Video: "The right way"] with a hot air gun/reflow station, by mozzwald
* [https://www.youtube.com/watch?v=ZqOb45N2sMc Vdeo: "The equally stupid way"], workaround video by Dalton, using a soldering iron. Less chances to permanently damage the board than the next if you are handy with a soldering iron, but still high.
* [https://www.youtube.com/watch?v=j3jc7Mvn9Eo Video: "The stupid way"] workaround video by Lukasz, with pliers. Slightly damages the circuit board, preventing you from soldering the replacement chips at a later point. You might be fine with this.

[[Category:PinePhone]]

PinePhone Hardware Accessory Compatibility

2020-09-02T11:45:45Z

Jbit: Add to PinePhone category

List of devices that have been tried on the PinePhone, and the results.

== Peripheral equipment ==

{| class="wikitable sortable"

!Type || Make/Model || Connected via || Hardware IDs || Result || Tested OS || Notes
|-
|5-1 USB-C hub || [https://www.aliexpress.com/item/32954358411.html from aliexpress] || USBC || 05e3:0626 hub || PD not working, rest not working yet ||UBPorts/pmOS || HDMI, GBit eth, 2xUSB-3, USB-C PD [http://www.sympato.ch/~dryak/files/usbc-dock.jpg image]
|-
|Generic Bluetooth keyboard || generic || BT || -- || No pairing via ui, but functional via terminal || pmOS || [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Bluetooth Instructions]
|-
|UMAX U-Connect Type-C Multiport H7 || [https://www.tsbohemia.cz/umax-u-connect-type-c-multiport-h7_d350000.html ts-bohemia] || USBC || - || USB-A ports, PD, HDMI works, SD card reader not enumerating on PP with removed VCONN switches (may need VCONN) || Arch Linux || HDMI, 3xUSB-3, USB-C PD, SD reader
|-
|Google Pixel USB-C to 3.5mm adapter || [https://store.google.com/?srp=/product/usb_c_headphone_adapter google] || USBC || 18d1:5029 || Works, recognized as usb soundcard, but only if a cable is plugged in || pmOS ||
|-
|-
|Anker PowerExpand+ 7-in-1 USB-C PD Ethernet Hub || [https://www.anker.com/products/variant/powerexpand--7in1-usbc-pd-ethernet-hub/A83520A1 Anker] || USBC || -- || USB Ports and HDMI Port work, can charge while using this device (needs VCONN HW mod) || [https://wiki.mobian-project.org/doku.php?id=mods Mobian] || HDMI, USB3, Ethernet, PD-USBC, SD Card, Micro SD Card
|-
|Dell WD-15 Docking station || [https://www.dell.com/support/article/en-us/sln296829/how-to-use-and-troubleshoot-dell-docking-station-wd15?lang=en Dell] || USB-C || 0424:2807 || USB Ports and charging works. Audio sinks and DP status changes are detected (needs VCONN HW mod and ANX firmware) || pmOS || HDMI, VGA and DP might work after a kernel update. ANX firmware is needed for charging after VCONN mod.
|-
|Microsoft HD-500 Dock || [https://www.microsoft.com/en-us/mobile/accessory/hd-500/specifications Microsoft Docs] || USB-C || -- || USB Hub, Display Out, and Power Delivery all works. (needs VCONN HW mod and ANX firmware) || [https://wiki.mobian-project.org/doku.php?id=mods Mobian] ||
|-
|HP Elite x3 LapDock || [https://support.hp.com/us-en/product/hp-elite-x3-lap-dock/12088822/document/c05320203 HP Product Info] || USB-C || -- || Dock display, keyboard/trackpad, and Power Delivery all works. (needs VCONN HW mod and ANX firmware) || [https://wiki.mobian-project.org/doku.php?id=mods Mobian] || Haven't tested micro-HDMI port or the internal USB-C hub.
|-
|}

== Protection ==

=== Screen protector ===

Official: [https://store.pine64.org/product/pinephone-tempered-glass-screen-protector/ PinePhone Tempered Glass Screen Protector]

Most screen protectors for the iPhone 11 Pro Max and the iPhone XS Max fit the PinePhone (if the top notch is not obscured by a black foil or similar).

=== Case ===

The Pine store got official cases:

* [https://store.pine64.org/?product=pinephone-hard-protective-case PinePhone Hard Protective Case]
* [https://store.pine64.org/?product=pinephone-soft-tpu-protective-case-reduce-digital-gap-donation-program PinePhone Soft TPU Protective Case - "Reduce Digital Gap" Donation Program]

Tight-fit cases of other phones can't be alienated for the PinePhone due as most times the proportions and/or camera notch won't fit. The phone can however also be used with "phone sleeves", such as those from fitBAG.

[[Category:PinePhone]]

Category:PinePhone

2020-09-02T10:24:54Z

Jbit: Make a category for PinePhone articles

Articles related to [[PinePhone]]

User:Oogwaymaki/PinePhone Multiboot

2020-09-02T10:23:38Z

Jbit: Add to PinePhone category

== Tips on creating a Multi Boot Configuration for an SDCARD and EMMC ==

= Manual MultiBoot Configuration =

First, and foremost these steps do the following for you:

* HOLD VOLUME UP AND POWER => BOOT JUMPDRIVE
* HOLD VOLUME DOWN AND POWER => BOOT YOUR SD CARD OS
* HOLD NOTHING REGULAR BOOT => BOOT EMMC DRIVE

Below is series of steps, which will enable MultiBoot on an external SD Card for the PinePhone.
You will not be required to edit the EMMC in any way at all, leaving the the EMMC intact with original software
or with your own Primary OS, that is only for stable use of the phone, without worrying about breaking your permanent software.

You could potentially use this for 3 OS's, but ideally only 2 with this current instruction set because you want to keep JumpDrive to make it easy to mount the cards with an option on booting the device.

After reading and following these steps, you should able to do the following with a bit more research and a
few tweaks:

* Change the PostMarketOS to Mobian or another Distro of your choice pretty easily.
* Use these instructions to create a More Advanced boot structure, using Volume Up and Volume Down with a menu system (This endeavour may take you a while this is a programming exercise within Uboot.scr)

Essentially you are experimenting without the risk of complications with your EMMC.

For example of these instructions , with slight differences for Mobian see below:

https://www.youtube.com/user/enterusernamo/featured

==Summary==

After following these steps:
----
* You'll have a Custom UBOOT (Crust ENABLED) that allows MultiBOOT Using 3 different OS's depending on key combo of volume up / volume down or none pressing on boot
* You'll be able to experiment on SD Card without Touching your EMMC
* You'll learn how to take a part a PINE PHONE IMAGE (most, and put each OS On one partition
----
All the information here, has been discussed in the open source community on web sites. I have simply developed a process on how to do this on the pine phone.

We use utilities such as Cross Compilation, Uboot, Patches, which will be credited.

First step, make sure you have a cross compiler for your Computer, for particularly the arm device, you will need to download a few packages, I assume we're using Debian Linux (if your using another OS you can find similar commands by searching on the web or to make it simpler download a docker Debian image, and install the pre-requisites which I will list here for Debian)

You an also use vagrant/virtual box VMware or other virtualization platforms.

the tools mentioned are the following (in my words possible not maintainers):

Below are all more or less free:

Vagrant: A multi/functional wrapper tool to make using Virtual Box, VMWARE , and other virtualization components easier. There are default images(Preconfigured operating systems you can download) or you can make your own.

VirtualBox: This is a free virtualization tool, I don't think you can use prebundled images as without vagrant, but it allows you to freshly install operating systems from disk. It's like using a computer within a computer to install an OS.

Docker: A linux container system, that allows you to have many different snapshots running in the same linux environment. Similar to jails, quicker and faster than Vagrant and VirtualBox, and not an actual computer emulation....

Commercial Tools available, non free:

VMWARE...numerous ones.

pick your poison! j/k

===Installing Dependencies===
First please install these Dependencies:

apt-get install gcc-aarch64-linux-gnu g++-aarch64-linux-gnu build-essential autoconf libtool cmake pkg-config git python-dev swig3.0 libpcre3-dev nodejs-dev crossbuild-essential-arm64 git losetup rsync

The following main sources are needed:

This will download quite a few sources needed for Uboot and existing OS's available to PinePhone

https://github.com/crust-firmware/meta.git

We will also apply this patch:

https://megous.com/git/u-boot/patch/?id=0ab6225154c3d8b74f06fb3b181b52a9a64b4602

(I will attach the one I used I had to modify the above patch to work with the code.)

The crust-firmware also says you need to download the or1k compiler:

https://musl.cc/or1k-linux-musl-cross.tgz

I suggest untarring this in the /opt folder.

===Preparing Crust===

* You will see we are patching crust, from the original code, the reason why we are doing this is to ENABLE the Volume UP and VOLUME DOWN Environment variables
* so the script knows when a user presses up and down on the volume button on pine phone
* Without the patch this functionality isn't there.
* Feel free to look through the patch to see how its done, I did not make this patch its found on a gmail thread through another site. I just cleaned it up so it won't have rejects.

Once you have these dependencies:

# cd /usr/src
# git clone https://github.com/crust-firmware/meta.git
# cd /usr/src/meta

Edit the following file Make file

# Cross compiler
CROSS_aarch64 = aarch64-linux-musl-
CROSS_or1k = or1k-linux-musl-

# General options
DEBUG ?= 0
REPRODUCIBLE ?= 0

# Board selection
BOARD ?= pinebook

Example:

# Cross compiler
CROSS_aarch64 = /usr/bin/aarch64-linux-gnu-
CROSS_or1k = /opt/or1k-linux-musl-cross/bin/or1k-linux-musl-

# General options
DEBUG ?= 0
REPRODUCIBLE ?= 0

# Board selection
BOARD ?= pinephone

# make

(this should take a 10-30 mins depending on speed..I hope less than 30 mins!!)k

# cd u-boot
# make clean
# cd ..

FIND THIS PATCH AT END OF DOCUMENT CUT AND PASTE INTO FILE

# patch -p1 < volumecontrol.patch
# make
===Partitioning===
now, go to your sdcard (use a CLEAN scard NO Partitions)

fdisk /dev/sd#
create 4 primary partitions,
the 1rst one should be the "boot" partition containing Uboot stuff, I'd suggest a gigabyte
the other 3 could be your choice

After creating partitions, flash the image:

# cd build/pinephone

Do not use wrong drive, and copy exactly as this erases and puts the new Uboot on the sdcard
the first 512 sectors are partition you do NOT want to write that or you lose your partition
# dd if=u-boot-sunxi-with-spl.bin of=/dev/sdb bs=1024 seek=8 conv=sync

Make sure your disk is OK.

# fdisk -l
<pre>
Disk model: e microSD
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x50fdd1d4

Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 2099199 2097152 1G 83 Linux
/dev/sdb2 2099200 65013759 62914560 30G 83 Linux
/dev/sdb3 65013760 127928319 62914560 30G 83 Linux
/dev/sdb4 127928320 251131903 123203584 58.8G 83 Linux
root@wifirouter:/usr/src#
</pre>
If it looks like above its ok.

===Flashing JumpDrive===
Lets start with the first OS were going to use:

JumpDrive (allows booting the EMMC and fixing it if we break it!!!)

Download it here:

https://github.com/dreemurrs-embedded/Jumpdrive/releases/download/0.4/pine64-pinephone.img.xz

then use losetup to mount the image to copy the files needed

root@wifirouter:/home/dave# losetup -P -f pine64-pinephone.img

it'll mount a loop back

root@wifirouter:/home/dave# ls /dev/loop0*
/dev/loop0 /dev/loop0p1

Mount there first image:

root@wifirouter:/home/dave# mkdir /media/jumpdrive
root@wifirouter:/home/dave# mount /dev/loop0p1 /media/jumpdrive/

mount the sd card:

root@wifirouter:/media# mkdir /media/boot
root@wifirouter:/media# fdisk -l

Your sd card should look like below:
<pre>

Disk /dev/sdb: 119.8 GiB, 128579534848 bytes, 251131904 sectors
Disk model: e microSD
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x50fdd1d4

Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 2099199 2097152 1G 83 Linux
/dev/sdb2 2099200 65013759 62914560 30G 83 Linux
/dev/sdb3 65013760 127928319 62914560 30G 83 Linux
/dev/sdb4 127928320 251131903 123203584 58.8G 83 Linux
</pre>

root@wifirouter:/media# mount /dev/sdb1 /media/boot/
root@wifirouter:/media# cd /media/boot
root@wifirouter:/media/boot# mkdir boot

root@wifirouter:/media/boot# mkdir -p multiboot/jumpdrive
root@wifirouter:/media/boot# cp * multiboot/jumpdrive

End result should be like this ( this is complete file)

root@wifirouter:/media/boot/multiboot/jumpdrive# ls -la
<pre>
total 4988
drwxr-xr-x 2 root root 4096 Jun 25 05:51 .
drwxr-xr-x 3 root root 4096 Jun 25 05:46 ..
-rwxr-xr-x 1 32011 32011 3991895 Jun 25 05:45 Image.gz
-rwxr-xr-x 1 32011 32011 1068435 Jun 25 05:45 initramfs.gz
-rwxr-xr-x 1 32011 32011 33457 Jun 25 05:45 sun50i-a64-pinephone.dtb
</pre>
root@wifirouter:/media/boot/multiboot/jumpdrive# pwd

Now we need to create the boot.txt for uboot to load:

Your text file should look like this:
<pre>
setenv kernel_addr_z 0x44080000

setenv bootargs loglevel=0 silent console=tty0 vt.global_cursor_default=0

if test "${volume_key}" = "up" ; then
echo "yes im here"
setenv devtype mmc
setenv devnum 0
setenv distro_bootpart 1
if load ${devtype} ${devnum}:${distro_bootpart} ${kernel_addr_z} /multiboot/jumpdrive/Image.gz; then
unzip ${kernel_addr_z} ${kernel_addr_r}
if load ${devtype} ${devnum}:${distro_bootpart} ${fdt_addr_r} /multiboot/jumpdrive/sun50i-a64-pinephone.dtb; then
if load ${devtype} ${devnum}:${distro_bootpart} ${ramdisk_addr_r} /multiboot/jumpdrive/initramfs.gz; then
booti ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r};
else
booti ${kernel_addr_r} - ${fdt_addr_r};
fi;
fi;
fi
exit
fi
if test "${volume_key}" = "down" ; then
echo "down"
ext4load mmc 0:2 ${kernel_addr_r} /boot/Image
ext4load mmc 0:2 ${fdt_addr_r} /boot/dtb/sun50i-a64-pinephone-1.2.dtb
setenv bootargs root=/dev/mmcblk0p2 rw console=ttyS0,115200 console=tty1 initrd=/boot/initrd.img quiet
booti ${kernel_addr_r} - ${fdt_addr_r}
else
setenv devtype mmc
setenv devnum 1
setenv partnum 4
load ${devtype} ${devnum}:2 ${scriptaddr} /boot.scr
source ${scriptaddr}
fi
</pre>

Compile the boot script:

mkimage -C none -A arm -T script -d boot.text boot.scr
cp boot.scr /media/boot/boot

This should now be working with JumpDrive..

===Flashing PostMarketOS===
Now lets download PostMarketOS

# wget http://images.postmarketos.org/pinephone/pine-pinephone-20200624-phosh-crust.img.xz

root@wifirouter:/home/dave# unxz pine-pinephone-20200624-phosh-crust.img.xz
root@wifirouter:/home/dave# losetup -P -f pine-pinephone-20200624-phosh-crust.img

root@wifirouter:/home/dave# ls /dev/loop1*
/dev/loop1 /dev/loop1p1 /dev/loop1p2

root@wifirouter:/home/dave# mount /dev/loop1p1 /media/postmarketboot/
root@wifirouter:/home/dave# mount /dev/loop1p2 /media/postmarket/

root@wifirouter:/home/dave# fdisk -l /dev/loop1
<pre>
Disk /dev/loop1: 1.4 GiB, 1504706560 bytes, 2938880 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0eef1887

Device Boot Start End Sectors Size Id Type
/dev/loop1p1 * 2048 249855 247808 121M 83 Linux
/dev/loop1p2 249856 2938879 2689024 1.3G 83 Linux
</pre>
root@wifirouter:/media# ls -la /media/postmarketboot/
<pre>
total 40202
drwxr-xr-x 3 root root 1024 Jun 24 08:40 .
drwxr-xr-x 16 root root 4096 Jun 25 21:24 ..
-rw-r--r-- 1 root root 949 Jun 17 05:19 boot.scr
-rw-r--r-- 1 root root 1431266 Jun 24 08:40 initramfs-postmarketos-allwinner
-rw-r--r-- 1 root root 6875596 Jun 24 08:40 initramfs-postmarketos-allwinner-extra
drwx------ 2 root root 12288 Jun 24 08:42 lost+found
-rw-r--r-- 1 root root 33835 Jun 24 08:40 sun50i-a64-pinephone-1.1.dtb
-rw-r--r-- 1 root root 15601736 Jun 24 08:40 uImage-postmarketos-allwinner
-rw-r--r-- 1 root root 1431330 Jun 24 08:40 uInitrd-postmarketos-allwinner
-rw-r--r-- 1 root root 15601672 Jun 21 16:57 vmlinuz-postmarketos-allwinner
</pre>
Take a look at how the boot.scr works with postmarketos:

root@wifirouter:/media# cat /media/postmarketboot/boot.scr
<pre>
'Vi?_^??;u??npostmarketosmgpio set 98
gpio set 114

if test ${mmc_bootdev} -eq 0 ; then
echo "Booting from SD";
setenv bootdev 0;
else
echo "Booting from eMMC";
setenv bootdev 2;
fi;

setenv bootargs init=/init.sh rw console=tty0 console=ttyS0,115200 no_console_suspend earlycon=uart,mmio32,0x01c28000 panic=10 consoleblank=0 loglevel=1 cma=256M PMOS_NO_OUTPUT_REDIRECT pmos_boot=/dev/mmcblk${bootdev}p1 pmos_root=/dev/mmcblk${bootdev}p2

printenv

echo Loading DTB
load mmc ${mmc_bootdev}:1 ${fdt_addr_r} sun50i-a64-pinephone-1.1.dtb

echo Loading Initramfs
load mmc ${mmc_bootdev}:1 ${ramdisk_addr_r} uInitrd-postmarketos-allwinner

echo Loading Kernel
load mmc ${mmc_bootdev}:1 ${kernel_addr_r} vmlinuz-postmarketos-allwinner

gpio set 115

echo Resizing FDT
fdt addr ${fdt_addr_r}
fdt resize

echo Booting kernel
gpio set 116
gpio clear 98
booti ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r}
</pre>

# mkdir -p /media/boot/multiboot/postmarketos/
# cd /media/postmarketboot
# cp -r * /media/boot/multiboot/postmarketos/

# mkfs.ext4 /dev/sdb#
# mkdir -p /media/newpostmarketbin
# mount /dev/sdb# /media/newpostmarketbin
# cd /media/postmarketos
# rsync -avh * /media/newpostmarketbin
# cp /media/postmarketboot /media/newpostmarketbin/boot
# cp /media/postmarketboot /media/newpostmarketbin/

=== This is the script UBOOT with load and ch use different OS's ===

now edit the boot.text to reflect the changes of the images
<pre>
setenv kernel_addr_z 0x44080000

setenv bootargs loglevel=0 silent console=tty0 vt.global_cursor_default=0

# This if statement boots up jumpdrive, if you notice there is an environment variable
# which is what the uboot patch does, it allows you to have an environment variable
# if someone holds the volume UP key it is set

if test "${volume_key}" = "up" ; then
echo "yes im here"
setenv devtype mmc
setenv devnum 0
setenv distro_bootpart 1
if load ${devtype} ${devnum}:${distro_bootpart} ${kernel_addr_z} /multiboot/jumpdrive/Image.gz; then
unzip ${kernel_addr_z} ${kernel_addr_r}
if load ${devtype} ${devnum}:${distro_bootpart} ${fdt_addr_r} /multiboot/jumpdrive/sun50i-a64-pinephone.dtb; then
if load ${devtype} ${devnum}:${distro_bootpart} ${ramdisk_addr_r} /multiboot/jumpdrive/initramfs.gz; then
booti ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r};
else
booti ${kernel_addr_r} - ${fdt_addr_r};
fi;
fi;
fi
exit
fi
# BOOT UP SECONDARY OS, this is customized for Postmarket OS make your changes here to change the OS LOADED
# and specific boot OPTIONS For your Second boot environment
# Again if the volume_key is pressed down, do this which is set by environment variable

if test "${volume_key}" = "down" ; then
echo "down"

setenv bootdev 0
setenv bootargs init=/init.sh rw console=tty0 console=ttyS0,115200 no_console_suspend earlycon=uart,mmio32,0x01c28000 panic=10 consoleblank=0 loglevel=1 cma=256M PMOS_NO_OUTPUT_REDIRECT pmos_boot=/dev/mmcblk${bootdev}p3 pmos_root=/dev/mmcblk${bootdev}p3

printenv

echo Loading DTB
load mmc ${mmc_bootdev}:1 ${fdt_addr_r} /multiboot/postmarketos/sun50i-a64-pinephone-1.1.dtb

echo Loading Initramfs
load mmc ${mmc_bootdev}:1 ${ramdisk_addr_r} /multiboot/postmarketos/uInitrd-postmarketos-allwinner

echo Loading Kernel
load mmc ${mmc_bootdev}:1 ${kernel_addr_r} /multiboot/postmarketos/vmlinuz-postmarketos-allwinner

gpio set 115

echo Resizing FDT
fdt addr ${fdt_addr_r}
fdt resize

echo Booting kernel
gpio set 116
gpio clear 98
booti ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r}

# This ELSE statement assumes you have UBUNTU PORTS on your EMMC by default it says the following
# If nothing is being pressed than load the boot script on the EMMC drive, 1,4 where the boot script resides
# on UBUNTU PORTS EMMC device

else

setenv devtype mmc
setenv devnum 1
setenv partnum 4
load ${devtype} ${devnum}:2 ${scriptaddr} /boot.scr
source ${scriptaddr}
fi
</pre>

compile it:

# mkimage -C none -A arm -T script -d boot.text boot.scr

Once booted, you will need to run depmod -a after logging into it.

===Sites Referenced/Inspiration===

* https://www.96boards.org/documentation/iot/
* https://github.com/dreemurrs-embedded/Jumpdrive
* https://github.com/dreemurrs-embedded/Pineloader
* https://www.thegeekstuff.com/2014/12/patch-command-examples/
* https://stackoverflow.com/questions/9980186/how-to-create-a-patch-for-a-whole-directory-to-update-it
* https://courses.linuxchix.org/kernel-hacking-2002/11-creating-applying-and-submitting-patches.html

=== Patch To Cut And Paste into file for uboot ===
PATCH BELOW CUT AND PASTE INTO FILE!

volumecontrol.patch

<pre>
diff -urN u-boot2/board/sunxi/Makefile u-boot/board/sunxi/Makefile
--- u-boot2/board/sunxi/Makefile 2020-06-27 01:09:17.687936000 +0000
+++ u-boot/board/sunxi/Makefile 2020-06-27 01:11:32.102472000 +0000
@@ -11,3 +11,4 @@
obj-$(CONFIG_MACH_SUN4I) += dram_sun4i_auto.o
obj-$(CONFIG_MACH_SUN5I) += dram_sun5i_auto.o
obj-$(CONFIG_MACH_SUN7I) += dram_sun5i_auto.o
+obj-$(CONFIG_MACH_SUN50I) += lradc.o
diff -urN u-boot2/board/sunxi/board.c u-boot/board/sunxi/board.c
--- u-boot2/board/sunxi/board.c 2020-06-27 01:09:17.687936000 +0000
+++ u-boot/board/sunxi/board.c 2020-06-27 01:19:15.609314000 +0000
@@ -44,6 +44,7 @@
#include <spl.h>
#include <sy8106a.h>
#include <asm/setup.h>
+#include "lradc.h"

#if defined CONFIG_VIDEO_LCD_PANEL_I2C && !(defined CONFIG_SPL_BUILD)
/* So that we can use pin names in Kconfig and sunxi_name_to_gpio() */
@@ -639,6 +640,11 @@
void sunxi_board_init(void)
{
int power_failed = 0;
+#ifdef CONFIG_MACH_SUN50I
+ // we init the lradc in SPL to get the ADC started early to have
+ // a valid sample when U-Boot main binary gets executed.
+ lradc_enable();
+#endif

#ifdef CONFIG_SY8106A_POWER
power_failed = sy8106a_set_vout1(CONFIG_SY8106A_VOUT1_VOLT);
@@ -899,6 +905,17 @@
env_set("fdtfile", str);
}

+#ifdef CONFIG_MACH_SUN50I
+ int key = lradc_get_pressed_key();
+ if (key == KEY_VOLUMEDOWN)
+ env_set("volume_key", "down");
+ else if (key == KEY_VOLUMEUP)
+ env_set("volume_key", "up");
+
+ // no longer needed
+ lradc_disable();
+#endif
+
setup_environment(gd->fdt_blob);

#ifdef CONFIG_USB_ETHER
diff -urN u-boot2/board/sunxi/board.c.orig u-boot/board/sunxi/board.c.orig
--- u-boot2/board/sunxi/board.c.orig 1970-01-01 00:00:00.000000000 +0000
+++ u-boot/board/sunxi/board.c.orig 2020-06-27 01:03:03.795626000 +0000
@@ -0,0 +1,982 @@
+// SPDX-License-Identifier: GPL-2.0+
+/*
+ * (C) Copyright 2012-2013 Henrik Nordstrom <henrik@henriknordstrom.net>
+ * (C) Copyright 2013 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
+ *
+ * (C) Copyright 2007-2011
+ * Allwinner Technology Co., Ltd. <www.allwinnertech.com>
+ * Tom Cubie <tangliang@allwinnertech.com>
+ *
+ * Some board init for the Allwinner A10-evb board.
+ */
+
+#include <common.h>
+#include <dm.h>
+#include <env.h>
+#include <hang.h>
+#include <image.h>
+#include <init.h>
+#include <log.h>
+#include <mmc.h>
+#include <axp_pmic.h>
+#include <generic-phy.h>
+#include <phy-sun4i-usb.h>
+#include <asm/arch/clock.h>
+#include <asm/arch/cpu.h>
+#include <asm/arch/display.h>
+#include <asm/arch/dram.h>
+#include <asm/arch/gpio.h>
+#include <asm/arch/mmc.h>
+#include <asm/arch/prcm.h>
+#include <asm/arch/spl.h>
+#include <linux/delay.h>
+#include <u-boot/crc.h>
+#ifndef CONFIG_ARM64
+#include <asm/armv7.h>
+#endif
+#include <asm/gpio.h>
+#include <asm/io.h>
+#include <u-boot/crc.h>
+#include <env_internal.h>
+#include <linux/libfdt.h>
+#include <nand.h>
+#include <net.h>
+#include <spl.h>
+#include <sy8106a.h>
+#include <asm/setup.h>
+
+#if defined CONFIG_VIDEO_LCD_PANEL_I2C && !(defined CONFIG_SPL_BUILD)
+/* So that we can use pin names in Kconfig and sunxi_name_to_gpio() */
+int soft_i2c_gpio_sda;
+int soft_i2c_gpio_scl;
+
+static int soft_i2c_board_init(void)
+{
+ int ret;
+
+ soft_i2c_gpio_sda = sunxi_name_to_gpio(CONFIG_VIDEO_LCD_PANEL_I2C_SDA);
+ if (soft_i2c_gpio_sda < 0) {
+ printf("Error invalid soft i2c sda pin: '%s', err %d\n",
+ CONFIG_VIDEO_LCD_PANEL_I2C_SDA, soft_i2c_gpio_sda);
+ return soft_i2c_gpio_sda;
+ }
+ ret = gpio_request(soft_i2c_gpio_sda, "soft-i2c-sda");
+ if (ret) {
+ printf("Error requesting soft i2c sda pin: '%s', err %d\n",
+ CONFIG_VIDEO_LCD_PANEL_I2C_SDA, ret);
+ return ret;
+ }
+
+ soft_i2c_gpio_scl = sunxi_name_to_gpio(CONFIG_VIDEO_LCD_PANEL_I2C_SCL);
+ if (soft_i2c_gpio_scl < 0) {
+ printf("Error invalid soft i2c scl pin: '%s', err %d\n",
+ CONFIG_VIDEO_LCD_PANEL_I2C_SCL, soft_i2c_gpio_scl);
+ return soft_i2c_gpio_scl;
+ }
+ ret = gpio_request(soft_i2c_gpio_scl, "soft-i2c-scl");
+ if (ret) {
+ printf("Error requesting soft i2c scl pin: '%s', err %d\n",
+ CONFIG_VIDEO_LCD_PANEL_I2C_SCL, ret);
+ return ret;
+ }
+
+ return 0;
+}
+#else
+static int soft_i2c_board_init(void) { return 0; }
+#endif
+
+DECLARE_GLOBAL_DATA_PTR;
+
+void i2c_init_board(void)
+{
+#ifdef CONFIG_I2C0_ENABLE
+#if defined(CONFIG_MACH_SUN4I) || \
+ defined(CONFIG_MACH_SUN5I) || \
+ defined(CONFIG_MACH_SUN7I) || \
+ defined(CONFIG_MACH_SUN8I_R40)
+ sunxi_gpio_set_cfgpin(SUNXI_GPB(0), SUN4I_GPB_TWI0);
+ sunxi_gpio_set_cfgpin(SUNXI_GPB(1), SUN4I_GPB_TWI0);
+ clock_twi_onoff(0, 1);
+#elif defined(CONFIG_MACH_SUN6I)
+ sunxi_gpio_set_cfgpin(SUNXI_GPH(14), SUN6I_GPH_TWI0);
+ sunxi_gpio_set_cfgpin(SUNXI_GPH(15), SUN6I_GPH_TWI0);
+ clock_twi_onoff(0, 1);
+#elif defined(CONFIG_MACH_SUN8I)
+ sunxi_gpio_set_cfgpin(SUNXI_GPH(2), SUN8I_GPH_TWI0);
+ sunxi_gpio_set_cfgpin(SUNXI_GPH(3), SUN8I_GPH_TWI0);
+ clock_twi_onoff(0, 1);
+#elif defined(CONFIG_MACH_SUN50I)
+ sunxi_gpio_set_cfgpin(SUNXI_GPH(0), SUN50I_GPH_TWI0);
+ sunxi_gpio_set_cfgpin(SUNXI_GPH(1), SUN50I_GPH_TWI0);
+ clock_twi_onoff(0, 1);
+#endif
+#endif
+
+#ifdef CONFIG_I2C1_ENABLE
+#if defined(CONFIG_MACH_SUN4I) || \
+ defined(CONFIG_MACH_SUN7I) || \
+ defined(CONFIG_MACH_SUN8I_R40)
+ sunxi_gpio_set_cfgpin(SUNXI_GPB(18), SUN4I_GPB_TWI1);
+ sunxi_gpio_set_cfgpin(SUNXI_GPB(19), SUN4I_GPB_TWI1);
+ clock_twi_onoff(1, 1);
+#elif defined(CONFIG_MACH_SUN5I)
+ sunxi_gpio_set_cfgpin(SUNXI_GPB(15), SUN5I_GPB_TWI1);
+ sunxi_gpio_set_cfgpin(SUNXI_GPB(16), SUN5I_GPB_TWI1);
+ clock_twi_onoff(1, 1);
+#elif defined(CONFIG_MACH_SUN6I)
+ sunxi_gpio_set_cfgpin(SUNXI_GPH(16), SUN6I_GPH_TWI1);
+ sunxi_gpio_set_cfgpin(SUNXI_GPH(17), SUN6I_GPH_TWI1);
+ clock_twi_onoff(1, 1);
+#elif defined(CONFIG_MACH_SUN8I)
+ sunxi_gpio_set_cfgpin(SUNXI_GPH(4), SUN8I_GPH_TWI1);
+ sunxi_gpio_set_cfgpin(SUNXI_GPH(5), SUN8I_GPH_TWI1);
+ clock_twi_onoff(1, 1);
+#elif defined(CONFIG_MACH_SUN50I)
+ sunxi_gpio_set_cfgpin(SUNXI_GPH(2), SUN50I_GPH_TWI1);
+ sunxi_gpio_set_cfgpin(SUNXI_GPH(3), SUN50I_GPH_TWI1);
+ clock_twi_onoff(1, 1);
+#endif
+#endif
+
+#ifdef CONFIG_I2C2_ENABLE
+#if defined(CONFIG_MACH_SUN4I) || \
+ defined(CONFIG_MACH_SUN7I) || \
+ defined(CONFIG_MACH_SUN8I_R40)
+ sunxi_gpio_set_cfgpin(SUNXI_GPB(20), SUN4I_GPB_TWI2);
+ sunxi_gpio_set_cfgpin(SUNXI_GPB(21), SUN4I_GPB_TWI2);
+ clock_twi_onoff(2, 1);
+#elif defined(CONFIG_MACH_SUN5I)
+ sunxi_gpio_set_cfgpin(SUNXI_GPB(17), SUN5I_GPB_TWI2);
+ sunxi_gpio_set_cfgpin(SUNXI_GPB(18), SUN5I_GPB_TWI2);
+ clock_twi_onoff(2, 1);
+#elif defined(CONFIG_MACH_SUN6I)
+ sunxi_gpio_set_cfgpin(SUNXI_GPH(18), SUN6I_GPH_TWI2);
+ sunxi_gpio_set_cfgpin(SUNXI_GPH(19), SUN6I_GPH_TWI2);
+ clock_twi_onoff(2, 1);
+#elif defined(CONFIG_MACH_SUN8I)
+ sunxi_gpio_set_cfgpin(SUNXI_GPE(12), SUN8I_GPE_TWI2);
+ sunxi_gpio_set_cfgpin(SUNXI_GPE(13), SUN8I_GPE_TWI2);
+ clock_twi_onoff(2, 1);
+#elif defined(CONFIG_MACH_SUN50I)
+ sunxi_gpio_set_cfgpin(SUNXI_GPE(14), SUN50I_GPE_TWI2);
+ sunxi_gpio_set_cfgpin(SUNXI_GPE(15), SUN50I_GPE_TWI2);
+ clock_twi_onoff(2, 1);
+#endif
+#endif
+
+#ifdef CONFIG_I2C3_ENABLE
+#if defined(CONFIG_MACH_SUN6I)
+ sunxi_gpio_set_cfgpin(SUNXI_GPG(10), SUN6I_GPG_TWI3);
+ sunxi_gpio_set_cfgpin(SUNXI_GPG(11), SUN6I_GPG_TWI3);
+ clock_twi_onoff(3, 1);
+#elif defined(CONFIG_MACH_SUN7I) || \
+ defined(CONFIG_MACH_SUN8I_R40)
+ sunxi_gpio_set_cfgpin(SUNXI_GPI(0), SUN7I_GPI_TWI3);
+ sunxi_gpio_set_cfgpin(SUNXI_GPI(1), SUN7I_GPI_TWI3);
+ clock_twi_onoff(3, 1);
+#endif
+#endif
+
+#ifdef CONFIG_I2C4_ENABLE
+#if defined(CONFIG_MACH_SUN7I) || \
+ defined(CONFIG_MACH_SUN8I_R40)
+ sunxi_gpio_set_cfgpin(SUNXI_GPI(2), SUN7I_GPI_TWI4);
+ sunxi_gpio_set_cfgpin(SUNXI_GPI(3), SUN7I_GPI_TWI4);
+ clock_twi_onoff(4, 1);
+#endif
+#endif
+
+#ifdef CONFIG_R_I2C_ENABLE
+#ifdef CONFIG_MACH_SUN50I
+ clock_twi_onoff(5, 1);
+ sunxi_gpio_set_cfgpin(SUNXI_GPL(8), SUN50I_GPL_R_TWI);
+ sunxi_gpio_set_cfgpin(SUNXI_GPL(9), SUN50I_GPL_R_TWI);
+#else
+ clock_twi_onoff(5, 1);
+ sunxi_gpio_set_cfgpin(SUNXI_GPL(0), SUN8I_H3_GPL_R_TWI);
+ sunxi_gpio_set_cfgpin(SUNXI_GPL(1), SUN8I_H3_GPL_R_TWI);
+#endif
+#endif
+}
+
+#if defined(CONFIG_ENV_IS_IN_MMC) && defined(CONFIG_ENV_IS_IN_FAT)
+enum env_location env_get_location(enum env_operation op, int prio)
+{
+ switch (prio) {
+ case 0:
+ return ENVL_FAT;
+
+ case 1:
+ return ENVL_MMC;
+
+ default:
+ return ENVL_UNKNOWN;
+ }
+}
+#endif
+
+#ifdef CONFIG_DM_MMC
+static void mmc_pinmux_setup(int sdc);
+#endif
+
+/* add board specific code here */
+int board_init(void)
+{
+ __maybe_unused int id_pfr1, ret, satapwr_pin, macpwr_pin;
+
+ gd->bd->bi_boot_params = (PHYS_SDRAM_0 + 0x100);
+
+#ifndef CONFIG_ARM64
+ asm volatile("mrc p15, 0, %0, c0, c1, 1" : "=r"(id_pfr1));
+ debug("id_pfr1: 0x%08x\n", id_pfr1);
+ /* Generic Timer Extension available? */
+ if ((id_pfr1 >> CPUID_ARM_GENTIMER_SHIFT) & 0xf) {
+ uint32_t freq;
+
+ debug("Setting CNTFRQ\n");
+
+ /*
+ * CNTFRQ is a secure register, so we will crash if we try to
+ * write this from the non-secure world (read is OK, though).
+ * In case some bootcode has already set the correct value,
+ * we avoid the risk of writing to it.
+ */
+ asm volatile("mrc p15, 0, %0, c14, c0, 0" : "=r"(freq));
+ if (freq != COUNTER_FREQUENCY) {
+ debug("arch timer frequency is %d Hz, should be %d, fixing ...\n",
+ freq, COUNTER_FREQUENCY);
+#ifdef CONFIG_NON_SECURE
+ printf("arch timer frequency is wrong, but cannot adjust it\n");
+#else
+ asm volatile("mcr p15, 0, %0, c14, c0, 0"
+ : : "r"(COUNTER_FREQUENCY));
+#endif
+ }
+ }
+#endif /* !CONFIG_ARM64 */
+
+ ret = axp_gpio_init();
+ if (ret)
+ return ret;
+
+#ifdef CONFIG_SATAPWR
+ satapwr_pin = sunxi_name_to_gpio(CONFIG_SATAPWR);
+ gpio_request(satapwr_pin, "satapwr");
+ gpio_direction_output(satapwr_pin, 1);
+ /* Give attached sata device time to power-up to avoid link timeouts */
+ mdelay(500);
+#endif
+#ifdef CONFIG_MACPWR
+ macpwr_pin = sunxi_name_to_gpio(CONFIG_MACPWR);
+ gpio_request(macpwr_pin, "macpwr");
+ gpio_direction_output(macpwr_pin, 1);
+#endif
+
+#ifdef CONFIG_DM_I2C
+ /*
+ * Temporary workaround for enabling I2C clocks until proper sunxi DM
+ * clk, reset and pinctrl drivers land.
+ */
+ i2c_init_board();
+#endif
+
+#ifdef CONFIG_DM_MMC
+ /*
+ * Temporary workaround for enabling MMC clocks until a sunxi DM
+ * pinctrl driver lands.
+ */
+ mmc_pinmux_setup(CONFIG_MMC_SUNXI_SLOT);
+#if CONFIG_MMC_SUNXI_SLOT_EXTRA != -1
+ mmc_pinmux_setup(CONFIG_MMC_SUNXI_SLOT_EXTRA);
+#endif
+#endif /* CONFIG_DM_MMC */
+
+ /* Uses dm gpio code so do this here and not in i2c_init_board() */
+ return soft_i2c_board_init();
+}
+
+/*
+ * On older SoCs the SPL is actually at address zero, so using NULL as
+ * an error value does not work.
+ */
+#define INVALID_SPL_HEADER ((void *)~0UL)
+
+static struct boot_file_head * get_spl_header(uint8_t req_version)
+{
+ struct boot_file_head *spl = (void *)(ulong)SPL_ADDR;
+ uint8_t spl_header_version = spl->spl_signature[3];
+
+ /* Is there really the SPL header (still) there? */
+ if (memcmp(spl->spl_signature, SPL_SIGNATURE, 3) != 0)
+ return INVALID_SPL_HEADER;
+
+ if (spl_header_version < req_version) {
+ printf("sunxi SPL version mismatch: expected %u, got %u\n",
+ req_version, spl_header_version);
+ return INVALID_SPL_HEADER;
+ }
+
+ return spl;
+}
+
+static const char *get_spl_dt_name(void)
+{
+ struct boot_file_head *spl = get_spl_header(SPL_DT_HEADER_VERSION);
+
+ /* Check if there is a DT name stored in the SPL header. */
+ if (spl != INVALID_SPL_HEADER && spl->dt_name_offset)
+ return (char *)spl + spl->dt_name_offset;
+
+ return NULL;
+}
+
+static void set_spl_dt_name(const char *name)
+{
+ struct boot_file_head *spl = get_spl_header(SPL_ENV_HEADER_VERSION);
+
+ if (spl == INVALID_SPL_HEADER)
+ return;
+
+ /* Promote the header version for U-Boot proper, if needed. */
+ if (spl->spl_signature[3] < SPL_DT_HEADER_VERSION)
+ spl->spl_signature[3] = SPL_DT_HEADER_VERSION;
+
+ strcpy((char *)&spl->string_pool, name);
+ spl->dt_name_offset = offsetof(struct boot_file_head, string_pool);
+}
+
+int dram_init(void)
+{
+ struct boot_file_head *spl = get_spl_header(SPL_DRAM_HEADER_VERSION);
+
+ if (spl == INVALID_SPL_HEADER)
+ gd->ram_size = get_ram_size((long *)PHYS_SDRAM_0,
+ PHYS_SDRAM_0_SIZE);
+ else
+ gd->ram_size = (phys_addr_t)spl->dram_size << 20;
+
+ if (gd->ram_size > CONFIG_SUNXI_DRAM_MAX_SIZE)
+ gd->ram_size = CONFIG_SUNXI_DRAM_MAX_SIZE;
+
+ return 0;
+}
+
+#if defined(CONFIG_NAND_SUNXI)
+static void nand_pinmux_setup(void)
+{
+ unsigned int pin;
+
+ for (pin = SUNXI_GPC(0); pin <= SUNXI_GPC(19); pin++)
+ sunxi_gpio_set_cfgpin(pin, SUNXI_GPC_NAND);
+
+#if defined CONFIG_MACH_SUN4I || defined CONFIG_MACH_SUN7I
+ for (pin = SUNXI_GPC(20); pin <= SUNXI_GPC(22); pin++)
+ sunxi_gpio_set_cfgpin(pin, SUNXI_GPC_NAND);
+#endif
+ /* sun4i / sun7i do have a PC23, but it is not used for nand,
+ * only sun7i has a PC24 */
+#ifdef CONFIG_MACH_SUN7I
+ sunxi_gpio_set_cfgpin(SUNXI_GPC(24), SUNXI_GPC_NAND);
+#endif
+}
+
+static void nand_clock_setup(void)
+{
+ struct sunxi_ccm_reg *const ccm =
+ (struct sunxi_ccm_reg *)SUNXI_CCM_BASE;
+
+ setbits_le32(&ccm->ahb_gate0, (CLK_GATE_OPEN << AHB_GATE_OFFSET_NAND0));
+#if defined CONFIG_MACH_SUN6I || defined CONFIG_MACH_SUN8I || \
+ defined CONFIG_MACH_SUN9I || defined CONFIG_MACH_SUN50I
+ setbits_le32(&ccm->ahb_reset0_cfg, (1 << AHB_GATE_OFFSET_NAND0));
+#endif
+ setbits_le32(&ccm->nand0_clk_cfg, CCM_NAND_CTRL_ENABLE | AHB_DIV_1);
+}
+
+void board_nand_init(void)
+{
+ nand_pinmux_setup();
+ nand_clock_setup();
+#ifndef CONFIG_SPL_BUILD
+ sunxi_nand_init();
+#endif
+}
+#endif
+
+#ifdef CONFIG_MMC
+static void mmc_pinmux_setup(int sdc)
+{
+ unsigned int pin;
+ __maybe_unused int pins;
+
+ switch (sdc) {
+ case 0:
+ /* SDC0: PF0-PF5 */
+ for (pin = SUNXI_GPF(0); pin <= SUNXI_GPF(5); pin++) {
+ sunxi_gpio_set_cfgpin(pin, SUNXI_GPF_SDC0);
+ sunxi_gpio_set_pull(pin, SUNXI_GPIO_PULL_UP);
+ sunxi_gpio_set_drv(pin, 2);
+ }
+ break;
+
+ case 1:
+ pins = sunxi_name_to_gpio_bank(CONFIG_MMC1_PINS);
+
+#if defined(CONFIG_MACH_SUN4I) || defined(CONFIG_MACH_SUN7I) || \
+ defined(CONFIG_MACH_SUN8I_R40)
+ if (pins == SUNXI_GPIO_H) {
+ /* SDC1: PH22-PH-27 */
+ for (pin = SUNXI_GPH(22); pin <= SUNXI_GPH(27); pin++) {
+ sunxi_gpio_set_cfgpin(pin, SUN4I_GPH_SDC1);
+ sunxi_gpio_set_pull(pin, SUNXI_GPIO_PULL_UP);
+ sunxi_gpio_set_drv(pin, 2);
+ }
+ } else {
+ /* SDC1: PG0-PG5 */
+ for (pin = SUNXI_GPG(0); pin <= SUNXI_GPG(5); pin++) {
+ sunxi_gpio_set_cfgpin(pin, SUN4I_GPG_SDC1);
+ sunxi_gpio_set_pull(pin, SUNXI_GPIO_PULL_UP);
+ sunxi_gpio_set_drv(pin, 2);
+ }
+ }
+#elif defined(CONFIG_MACH_SUN5I)
+ /* SDC1: PG3-PG8 */
+ for (pin = SUNXI_GPG(3); pin <= SUNXI_GPG(8); pin++) {
+ sunxi_gpio_set_cfgpin(pin, SUN5I_GPG_SDC1);
+ sunxi_gpio_set_pull(pin, SUNXI_GPIO_PULL_UP);
+ sunxi_gpio_set_drv(pin, 2);
+ }
+#elif defined(CONFIG_MACH_SUN6I)
+ /* SDC1: PG0-PG5 */
+ for (pin = SUNXI_GPG(0); pin <= SUNXI_GPG(5); pin++) {
+ sunxi_gpio_set_cfgpin(pin, SUN6I_GPG_SDC1);
+ sunxi_gpio_set_pull(pin, SUNXI_GPIO_PULL_UP);
+ sunxi_gpio_set_drv(pin, 2);
+ }
+#elif defined(CONFIG_MACH_SUN8I)
+ if (pins == SUNXI_GPIO_D) {
+ /* SDC1: PD2-PD7 */
+ for (pin = SUNXI_GPD(2); pin <= SUNXI_GPD(7); pin++) {
+ sunxi_gpio_set_cfgpin(pin, SUN8I_GPD_SDC1);
+ sunxi_gpio_set_pull(pin, SUNXI_GPIO_PULL_UP);
+ sunxi_gpio_set_drv(pin, 2);
+ }
+ } else {
+ /* SDC1: PG0-PG5 */
+ for (pin = SUNXI_GPG(0); pin <= SUNXI_GPG(5); pin++) {
+ sunxi_gpio_set_cfgpin(pin, SUN8I_GPG_SDC1);
+ sunxi_gpio_set_pull(pin, SUNXI_GPIO_PULL_UP);
+ sunxi_gpio_set_drv(pin, 2);
+ }
+ }
+#endif
+ break;
+
+ case 2:
+ pins = sunxi_name_to_gpio_bank(CONFIG_MMC2_PINS);
+
+#if defined(CONFIG_MACH_SUN4I) || defined(CONFIG_MACH_SUN7I)
+ /* SDC2: PC6-PC11 */
+ for (pin = SUNXI_GPC(6); pin <= SUNXI_GPC(11); pin++) {
+ sunxi_gpio_set_cfgpin(pin, SUNXI_GPC_SDC2);
+ sunxi_gpio_set_pull(pin, SUNXI_GPIO_PULL_UP);
+ sunxi_gpio_set_drv(pin, 2);
+ }
+#elif defined(CONFIG_MACH_SUN5I)
+ if (pins == SUNXI_GPIO_E) {
+ /* SDC2: PE4-PE9 */
+ for (pin = SUNXI_GPE(4); pin <= SUNXI_GPD(9); pin++) {
+ sunxi_gpio_set_cfgpin(pin, SUN5I_GPE_SDC2);
+ sunxi_gpio_set_pull(pin, SUNXI_GPIO_PULL_UP);
+ sunxi_gpio_set_drv(pin, 2);
+ }
+ } else {
+ /* SDC2: PC6-PC15 */
+ for (pin = SUNXI_GPC(6); pin <= SUNXI_GPC(15); pin++) {
+ sunxi_gpio_set_cfgpin(pin, SUNXI_GPC_SDC2);
+ sunxi_gpio_set_pull(pin, SUNXI_GPIO_PULL_UP);
+ sunxi_gpio_set_drv(pin, 2);
+ }
+ }
+#elif defined(CONFIG_MACH_SUN6I)
+ if (pins == SUNXI_GPIO_A) {
+ /* SDC2: PA9-PA14 */
+ for (pin = SUNXI_GPA(9); pin <= SUNXI_GPA(14); pin++) {
+ sunxi_gpio_set_cfgpin(pin, SUN6I_GPA_SDC2);
+ sunxi_gpio_set_pull(pin, SUNXI_GPIO_PULL_UP);
+ sunxi_gpio_set_drv(pin, 2);
+ }
+ } else {
+ /* SDC2: PC6-PC15, PC24 */
+ for (pin = SUNXI_GPC(6); pin <= SUNXI_GPC(15); pin++) {
+ sunxi_gpio_set_cfgpin(pin, SUNXI_GPC_SDC2);
+ sunxi_gpio_set_pull(pin, SUNXI_GPIO_PULL_UP);
+ sunxi_gpio_set_drv(pin, 2);
+ }
+
+ sunxi_gpio_set_cfgpin(SUNXI_GPC(24), SUNXI_GPC_SDC2);
+ sunxi_gpio_set_pull(SUNXI_GPC(24), SUNXI_GPIO_PULL_UP);
+ sunxi_gpio_set_drv(SUNXI_GPC(24), 2);
+ }
+#elif defined(CONFIG_MACH_SUN8I_R40)
+ /* SDC2: PC6-PC15, PC24 */
+ for (pin = SUNXI_GPC(6); pin <= SUNXI_GPC(15); pin++) {
+ sunxi_gpio_set_cfgpin(pin, SUNXI_GPC_SDC2);
+ sunxi_gpio_set_pull(pin, SUNXI_GPIO_PULL_UP);
+ sunxi_gpio_set_drv(pin, 2);
+ }
+
+ sunxi_gpio_set_cfgpin(SUNXI_GPC(24), SUNXI_GPC_SDC2);
+ sunxi_gpio_set_pull(SUNXI_GPC(24), SUNXI_GPIO_PULL_UP);
+ sunxi_gpio_set_drv(SUNXI_GPC(24), 2);
+#elif defined(CONFIG_MACH_SUN8I) || defined(CONFIG_MACH_SUN50I)
+ /* SDC2: PC5-PC6, PC8-PC16 */
+ for (pin = SUNXI_GPC(5); pin <= SUNXI_GPC(6); pin++) {
+ sunxi_gpio_set_cfgpin(pin, SUNXI_GPC_SDC2);
+ sunxi_gpio_set_pull(pin, SUNXI_GPIO_PULL_UP);
+ sunxi_gpio_set_drv(pin, 2);
+ }
+
+ for (pin = SUNXI_GPC(8); pin <= SUNXI_GPC(16); pin++) {
+ sunxi_gpio_set_cfgpin(pin, SUNXI_GPC_SDC2);
+ sunxi_gpio_set_pull(pin, SUNXI_GPIO_PULL_UP);
+ sunxi_gpio_set_drv(pin, 2);
+ }
+#elif defined(CONFIG_MACH_SUN50I_H6)
+ /* SDC2: PC4-PC14 */
+ for (pin = SUNXI_GPC(4); pin <= SUNXI_GPC(14); pin++) {
+ sunxi_gpio_set_cfgpin(pin, SUNXI_GPC_SDC2);
+ sunxi_gpio_set_pull(pin, SUNXI_GPIO_PULL_UP);
+ sunxi_gpio_set_drv(pin, 2);
+ }
+#elif defined(CONFIG_MACH_SUN9I)
+ /* SDC2: PC6-PC16 */
+ for (pin = SUNXI_GPC(6); pin <= SUNXI_GPC(16); pin++) {
+ sunxi_gpio_set_cfgpin(pin, SUNXI_GPC_SDC2);
+ sunxi_gpio_set_pull(pin, SUNXI_GPIO_PULL_UP);
+ sunxi_gpio_set_drv(pin, 2);
+ }
+#endif
+ break;
+
+ case 3:
+ pins = sunxi_name_to_gpio_bank(CONFIG_MMC3_PINS);
+
+#if defined(CONFIG_MACH_SUN4I) || defined(CONFIG_MACH_SUN7I) || \
+ defined(CONFIG_MACH_SUN8I_R40)
+ /* SDC3: PI4-PI9 */
+ for (pin = SUNXI_GPI(4); pin <= SUNXI_GPI(9); pin++) {
+ sunxi_gpio_set_cfgpin(pin, SUNXI_GPI_SDC3);
+ sunxi_gpio_set_pull(pin, SUNXI_GPIO_PULL_UP);
+ sunxi_gpio_set_drv(pin, 2);
+ }
+#elif defined(CONFIG_MACH_SUN6I)
+ if (pins == SUNXI_GPIO_A) {
+ /* SDC3: PA9-PA14 */
+ for (pin = SUNXI_GPA(9); pin <= SUNXI_GPA(14); pin++) {
+ sunxi_gpio_set_cfgpin(pin, SUN6I_GPA_SDC3);
+ sunxi_gpio_set_pull(pin, SUNXI_GPIO_PULL_UP);
+ sunxi_gpio_set_drv(pin, 2);
+ }
+ } else {
+ /* SDC3: PC6-PC15, PC24 */
+ for (pin = SUNXI_GPC(6); pin <= SUNXI_GPC(15); pin++) {
+ sunxi_gpio_set_cfgpin(pin, SUN6I_GPC_SDC3);
+ sunxi_gpio_set_pull(pin, SUNXI_GPIO_PULL_UP);
+ sunxi_gpio_set_drv(pin, 2);
+ }
+
+ sunxi_gpio_set_cfgpin(SUNXI_GPC(24), SUN6I_GPC_SDC3);
+ sunxi_gpio_set_pull(SUNXI_GPC(24), SUNXI_GPIO_PULL_UP);
+ sunxi_gpio_set_drv(SUNXI_GPC(24), 2);
+ }
+#endif
+ break;
+
+ default:
+ printf("sunxi: invalid MMC slot %d for pinmux setup\n", sdc);
+ break;
+ }
+}
+
+int board_mmc_init(bd_t *bis)
+{
+ __maybe_unused struct mmc *mmc0, *mmc1;
+
+ mmc_pinmux_setup(CONFIG_MMC_SUNXI_SLOT);
+ mmc0 = sunxi_mmc_init(CONFIG_MMC_SUNXI_SLOT);
+ if (!mmc0)
+ return -1;
+
+#if CONFIG_MMC_SUNXI_SLOT_EXTRA != -1
+ mmc_pinmux_setup(CONFIG_MMC_SUNXI_SLOT_EXTRA);
+ mmc1 = sunxi_mmc_init(CONFIG_MMC_SUNXI_SLOT_EXTRA);
+ if (!mmc1)
+ return -1;
+#endif
+
+ return 0;
+}
+#endif
+
+#ifdef CONFIG_SPL_BUILD
+
+static void sunxi_spl_store_dram_size(phys_addr_t dram_size)
+{
+ struct boot_file_head *spl = get_spl_header(SPL_DT_HEADER_VERSION);
+
+ if (spl == INVALID_SPL_HEADER)
+ return;
+
+ /* Promote the header version for U-Boot proper, if needed. */
+ if (spl->spl_signature[3] < SPL_DRAM_HEADER_VERSION)
+ spl->spl_signature[3] = SPL_DRAM_HEADER_VERSION;
+
+ spl->dram_size = dram_size >> 20;
+}
+
+void sunxi_board_init(void)
+{
+ int power_failed = 0;
+
+#ifdef CONFIG_SY8106A_POWER
+ power_failed = sy8106a_set_vout1(CONFIG_SY8106A_VOUT1_VOLT);
+#endif
+
+#if defined CONFIG_AXP152_POWER || defined CONFIG_AXP209_POWER || \
+ defined CONFIG_AXP221_POWER || defined CONFIG_AXP809_POWER || \
+ defined CONFIG_AXP818_POWER
+ power_failed = axp_init();
+
+#if defined CONFIG_AXP221_POWER || defined CONFIG_AXP809_POWER || \
+ defined CONFIG_AXP818_POWER
+ power_failed |= axp_set_dcdc1(CONFIG_AXP_DCDC1_VOLT);
+#endif
+ power_failed |= axp_set_dcdc2(CONFIG_AXP_DCDC2_VOLT);
+ power_failed |= axp_set_dcdc3(CONFIG_AXP_DCDC3_VOLT);
+#if !defined(CONFIG_AXP209_POWER) && !defined(CONFIG_AXP818_POWER)
+ power_failed |= axp_set_dcdc4(CONFIG_AXP_DCDC4_VOLT);
+#endif
+#if defined CONFIG_AXP221_POWER || defined CONFIG_AXP809_POWER || \
+ defined CONFIG_AXP818_POWER
+ power_failed |= axp_set_dcdc5(CONFIG_AXP_DCDC5_VOLT);
+#endif
+
+#if defined CONFIG_AXP221_POWER || defined CONFIG_AXP809_POWER || \
+ defined CONFIG_AXP818_POWER
+ power_failed |= axp_set_aldo1(CONFIG_AXP_ALDO1_VOLT);
+#endif
+ power_failed |= axp_set_aldo2(CONFIG_AXP_ALDO2_VOLT);
+#if !defined(CONFIG_AXP152_POWER)
+ power_failed |= axp_set_aldo3(CONFIG_AXP_ALDO3_VOLT);
+#endif
+#ifdef CONFIG_AXP209_POWER
+ power_failed |= axp_set_aldo4(CONFIG_AXP_ALDO4_VOLT);
+#endif
+
+#if defined(CONFIG_AXP221_POWER) || defined(CONFIG_AXP809_POWER) || \
+ defined(CONFIG_AXP818_POWER)
+ power_failed |= axp_set_dldo(1, CONFIG_AXP_DLDO1_VOLT);
+ power_failed |= axp_set_dldo(2, CONFIG_AXP_DLDO2_VOLT);
+#if !defined CONFIG_AXP809_POWER
+ power_failed |= axp_set_dldo(3, CONFIG_AXP_DLDO3_VOLT);
+ power_failed |= axp_set_dldo(4, CONFIG_AXP_DLDO4_VOLT);
+#endif
+ power_failed |= axp_set_eldo(1, CONFIG_AXP_ELDO1_VOLT);
+ power_failed |= axp_set_eldo(2, CONFIG_AXP_ELDO2_VOLT);
+ power_failed |= axp_set_eldo(3, CONFIG_AXP_ELDO3_VOLT);
+#endif
+
+#ifdef CONFIG_AXP818_POWER
+ power_failed |= axp_set_fldo(1, CONFIG_AXP_FLDO1_VOLT);
+ power_failed |= axp_set_fldo(2, CONFIG_AXP_FLDO2_VOLT);
+ power_failed |= axp_set_fldo(3, CONFIG_AXP_FLDO3_VOLT);
+#endif
+
+#if defined CONFIG_AXP809_POWER || defined CONFIG_AXP818_POWER
+ power_failed |= axp_set_sw(IS_ENABLED(CONFIG_AXP_SW_ON));
+#endif
+#endif
+ printf("DRAM:");
+ gd->ram_size = sunxi_dram_init();
+ printf(" %d MiB\n", (int)(gd->ram_size >> 20));
+ if (!gd->ram_size)
+ hang();
+
+ sunxi_spl_store_dram_size(gd->ram_size);
+
+ /*
+ * Only clock up the CPU to full speed if we are reasonably
+ * assured it's being powered with suitable core voltage
+ */
+ if (!power_failed)
+ clock_set_pll1(CONFIG_SYS_CLK_FREQ);
+ else
+ printf("Failed to set core voltage! Can't set CPU frequency\n");
+}
+#endif
+
+#ifdef CONFIG_USB_GADGET
+int g_dnl_board_usb_cable_connected(void)
+{
+ struct udevice *dev;
+ struct phy phy;
+ int ret;
+
+ ret = uclass_get_device(UCLASS_USB_GADGET_GENERIC, 0, &dev);
+ if (ret) {
+ pr_err("%s: Cannot find USB device\n", __func__);
+ return ret;
+ }
+
+ ret = generic_phy_get_by_name(dev, "usb", &phy);
+ if (ret) {
+ pr_err("failed to get %s USB PHY\n", dev->name);
+ return ret;
+ }
+
+ ret = generic_phy_init(&phy);
+ if (ret) {
+ pr_err("failed to init %s USB PHY\n", dev->name);
+ return ret;
+ }
+
+ ret = sun4i_usb_phy_vbus_detect(&phy);
+ if (ret == 1) {
+ pr_err("A charger is plugged into the OTG\n");
+ return -ENODEV;
+ }
+
+ return ret;
+}
+#endif
+
+#ifdef CONFIG_SERIAL_TAG
+void get_board_serial(struct tag_serialnr *serialnr)
+{
+ char *serial_string;
+ unsigned long long serial;
+
+ serial_string = env_get("serial#");
+
+ if (serial_string) {
+ serial = simple_strtoull(serial_string, NULL, 16);
+
+ serialnr->high = (unsigned int) (serial >> 32);
+ serialnr->low = (unsigned int) (serial & 0xffffffff);
+ } else {
+ serialnr->high = 0;
+ serialnr->low = 0;
+ }
+}
+#endif
+
+/*
+ * Check the SPL header for the "sunxi" variant. If found: parse values
+ * that might have been passed by the loader ("fel" utility), and update
+ * the environment accordingly.
+ */
+static void parse_spl_header(const uint32_t spl_addr)
+{
+ struct boot_file_head *spl = get_spl_header(SPL_ENV_HEADER_VERSION);
+
+ if (spl == INVALID_SPL_HEADER)
+ return;
+
+ if (!spl->fel_script_address)
+ return;
+
+ if (spl->fel_uEnv_length != 0) {
+ /*
+ * data is expected in uEnv.txt compatible format, so "env
+ * import -t" the string(s) at fel_script_address right away.
+ */
+ himport_r(&env_htab, (char *)(uintptr_t)spl->fel_script_address,
+ spl->fel_uEnv_length, '\n', H_NOCLEAR, 0, 0, NULL);
+ return;
+ }
+ /* otherwise assume .scr format (mkimage-type script) */
+ env_set_hex("fel_scriptaddr", spl->fel_script_address);
+}
+
+/*
+ * Note this function gets called multiple times.
+ * It must not make any changes to env variables which already exist.
+ */
+static void setup_environment(const void *fdt)
+{
+ char serial_string[17] = { 0 };
+ unsigned int sid[4];
+ uint8_t mac_addr[6];
+ char ethaddr[16];
+ int i, ret;
+
+ ret = sunxi_get_sid(sid);
+ if (ret == 0 && sid[0] != 0) {
+ /*
+ * The single words 1 - 3 of the SID have quite a few bits
+ * which are the same on many models, so we take a crc32
+ * of all 3 words, to get a more unique value.
+ *
+ * Note we only do this on newer SoCs as we cannot change
+ * the algorithm on older SoCs since those have been using
+ * fixed mac-addresses based on only using word 3 for a
+ * long time and changing a fixed mac-address with an
+ * u-boot update is not good.
+ */
+#if !defined(CONFIG_MACH_SUN4I) && !defined(CONFIG_MACH_SUN5I) && \
+ !defined(CONFIG_MACH_SUN6I) && !defined(CONFIG_MACH_SUN7I) && \
+ !defined(CONFIG_MACH_SUN8I_A23) && !defined(CONFIG_MACH_SUN8I_A33)
+ sid[3] = crc32(0, (unsigned char *)&sid[1], 12);
+#endif
+
+ /* Ensure the NIC specific bytes of the mac are not all 0 */
+ if ((sid[3] & 0xffffff) == 0)
+ sid[3] |= 0x800000;
+
+ for (i = 0; i < 4; i++) {
+ sprintf(ethaddr, "ethernet%d", i);
+ if (!fdt_get_alias(fdt, ethaddr))
+ continue;
+
+ if (i == 0)
+ strcpy(ethaddr, "ethaddr");
+ else
+ sprintf(ethaddr, "eth%daddr", i);
+
+ if (env_get(ethaddr))
+ continue;
+
+ /* Non OUI / registered MAC address */
+ mac_addr[0] = (i << 4) | 0x02;
+ mac_addr[1] = (sid[0] >> 0) & 0xff;
+ mac_addr[2] = (sid[3] >> 24) & 0xff;
+ mac_addr[3] = (sid[3] >> 16) & 0xff;
+ mac_addr[4] = (sid[3] >> 8) & 0xff;
+ mac_addr[5] = (sid[3] >> 0) & 0xff;
+
+ eth_env_set_enetaddr(ethaddr, mac_addr);
+ }
+
+ if (!env_get("serial#")) {
+ snprintf(serial_string, sizeof(serial_string),
+ "%08x%08x", sid[0], sid[3]);
+
+ env_set("serial#", serial_string);
+ }
+ }
+}
+
+int misc_init_r(void)
+{
+ const char *spl_dt_name;
+ uint boot;
+
+ env_set("fel_booted", NULL);
+ env_set("fel_scriptaddr", NULL);
+ env_set("mmc_bootdev", NULL);
+
+ boot = sunxi_get_boot_device();
+ /* determine if we are running in FEL mode */
+ if (boot == BOOT_DEVICE_BOARD) {
+ env_set("fel_booted", "1");
+ parse_spl_header(SPL_ADDR);
+ /* or if we booted from MMC, and which one */
+ } else if (boot == BOOT_DEVICE_MMC1) {
+ env_set("mmc_bootdev", "0");
+ } else if (boot == BOOT_DEVICE_MMC2) {
+ env_set("mmc_bootdev", "1");
+ }
+
+ /* Set fdtfile to match the FIT configuration chosen in SPL. */
+ spl_dt_name = get_spl_dt_name();
+ if (spl_dt_name) {
+ char *prefix = IS_ENABLED(CONFIG_ARM64) ? "allwinner/" : "";
+ char str[64];
+
+ snprintf(str, sizeof(str), "%s%s.dtb", prefix, spl_dt_name);
+ env_set("fdtfile", str);
+ }
+
+ setup_environment(gd->fdt_blob);
+
+#ifdef CONFIG_USB_ETHER
+ usb_ether_init();
+#endif
+
+ return 0;
+}
+
+int ft_board_setup(void *blob, bd_t *bd)
+{
+ int __maybe_unused r;
+
+ /*
+ * Call setup_environment again in case the boot fdt has
+ * ethernet aliases the u-boot copy does not have.
+ */
+ setup_environment(blob);
+
+#ifdef CONFIG_VIDEO_DT_SIMPLEFB
+ r = sunxi_simplefb_setup(blob);
+ if (r)
+ return r;
+#endif
+ return 0;
+}
+
+#ifdef CONFIG_SPL_LOAD_FIT
+int board_fit_config_name_match(const char *name)
+{
+ const char *best_dt_name = get_spl_dt_name();
+ int ret;
+
+#ifdef CONFIG_DEFAULT_DEVICE_TREE
+ if (best_dt_name == NULL)
+ best_dt_name = CONFIG_DEFAULT_DEVICE_TREE;
+#endif
+
+ if (best_dt_name == NULL) {
+ /* No DT name was provided, so accept the first config. */
+ return 0;
+ }
+#ifdef CONFIG_PINE64_DT_SELECTION
+ else if (strstr(best_dt_name, "-pine64-plus")) {
+ /* Differentiate the Pine A64 boards by their DRAM size. */
+ if ((gd->ram_size == 512 * 1024 * 1024))
+ best_dt_name = "sun50i-a64-pine64";
+ }
+#endif
+#ifdef CONFIG_PINEPHONE_DT_SELECTION
+ else if (strstr(best_dt_name, "-pinephone")) {
+ /* Differentiate the PinePhone revisions by GPIO inputs. */
+ prcm_apb0_enable(PRCM_APB0_GATE_PIO);
+ sunxi_gpio_set_pull(SUNXI_GPL(6), SUNXI_GPIO_PULL_UP);
+ sunxi_gpio_set_cfgpin(SUNXI_GPL(6), SUNXI_GPIO_INPUT);
+ udelay(100);
+
+ /* PL6 is pulled low by the modem on v1.2. */
+ if (gpio_get_value(SUNXI_GPL(6)) == 0)
+ best_dt_name = "sun50i-a64-pinephone-1.2";
+ else
+ best_dt_name = "sun50i-a64-pinephone-1.1";
+
+ sunxi_gpio_set_cfgpin(SUNXI_GPL(6), SUNXI_GPIO_DISABLE);
+ sunxi_gpio_set_pull(SUNXI_GPL(6), SUNXI_GPIO_PULL_DISABLE);
+ prcm_apb0_disable(PRCM_APB0_GATE_PIO);
+ }
+#endif
+
+ ret = strcmp(name, best_dt_name);
+
+ /*
+ * If one of the FIT configurations matches the most accurate DT name,
+ * update the SPL header to provide that DT name to U-Boot proper.
+ */
+ if (ret == 0)
+ set_spl_dt_name(best_dt_name);
+
+ return ret;
+}
+#endif
diff -urN u-boot2/board/sunxi/board.c.rej u-boot/board/sunxi/board.c.rej
--- u-boot2/board/sunxi/board.c.rej 1970-01-01 00:00:00.000000000 +0000
+++ u-boot/board/sunxi/board.c.rej 2020-06-27 01:11:32.103472000 +0000
@@ -0,0 +1,15 @@
+--- board/sunxi/board.c
++++ board/sunxi/board.c
+@@ -623,6 +624,12 @@ void sunxi_board_init(void)
+ {
+ int power_failed = 0;
+
++#ifdef CONFIG_MACH_SUN50I
++ // we init the lradc in SPL to get the ADC started early to have
++ // a valid sample when U-Boot main binary gets executed.
++ lradc_enable();
++#endif
++
+ #ifdef CONFIG_PINEPHONE_LEDS
+ /* PD18:G PD19:R PD20:B */
+ gpio_request(SUNXI_GPD(18), "led:green");
diff -urN u-boot2/board/sunxi/lradc.c u-boot/board/sunxi/lradc.c
--- u-boot2/board/sunxi/lradc.c 1970-01-01 00:00:00.000000000 +0000
+++ u-boot/board/sunxi/lradc.c 2020-06-27 01:11:32.104472000 +0000
@@ -0,0 +1,81 @@
+#include <common.h>
+#include <asm/io.h>
+#include "lradc.h"
+
+#define LRADC_BASE 0x1c21800
+
+#define LRADC_CTRL (LRADC_BASE + 0x00)
+#define LRADC_INTC (LRADC_BASE + 0x04)
+#define LRADC_INTS (LRADC_BASE + 0x08)
+#define LRADC_DATA0 (LRADC_BASE + 0x0c)
+#define LRADC_DATA1 (LRADC_BASE + 0x10)
+
+/* LRADC_CTRL bits */
+#define FIRST_CONVERT_DLY(x) ((x) << 24) /* 8 bits */
+#define CHAN_SELECT(x) ((x) << 22) /* 2 bits */
+#define CONTINUE_TIME_SEL(x) ((x) << 16) /* 4 bits */
+#define KEY_MODE_SEL(x) ((x) << 12) /* 2 bits */
+#define LEVELA_B_CNT(x) ((x) << 8) /* 4 bits */
+#define HOLD_KEY_EN(x) ((x) << 7)
+#define HOLD_EN(x) ((x) << 6)
+#define LEVELB_VOL(x) ((x) << 4) /* 2 bits */
+#define SAMPLE_RATE(x) ((x) << 2) /* 2 bits */
+#define ENABLE(x) ((x) << 0)
+
+/* LRADC_INTC and LRADC_INTS bits */
+#define CHAN1_KEYUP_IRQ BIT(12)
+#define CHAN1_ALRDY_HOLD_IRQ BIT(11)
+#define CHAN1_HOLD_IRQ BIT(10)
+#define CHAN1_KEYDOWN_IRQ BIT(9)
+#define CHAN1_DATA_IRQ BIT(8)
+#define CHAN0_KEYUP_IRQ BIT(4)
+#define CHAN0_ALRDY_HOLD_IRQ BIT(3)
+#define CHAN0_HOLD_IRQ BIT(2)
+#define CHAN0_KEYDOWN_IRQ BIT(1)
+#define CHAN0_DATA_IRQ BIT(0)
+
+// this is for PinePhone only
+
+int lradc_get_pressed_key(void)
+{
+ uint32_t val;
+ uint32_t vref = 3000000 * 2 / 3;
+
+ val = readl(LRADC_DATA0) & 0x3f;
+ val = val * vref / 63;
+
+// printf("lradc=%u\n", val);
+
+ if (val < 200000) // 158730
+ return KEY_VOLUMEUP;
+ else if (val < 400000) // 349206
+ return KEY_VOLUMEDOWN;
+
+ return 0;
+}
+
+void lradc_enable(void)
+{
+ // aldo3 is always on and defaults to 3V
+
+ writel(0xffffffff, LRADC_INTS);
+ writel(0, LRADC_INTC);
+
+ /*
+ * Set sample time to 4 ms / 250 Hz. Wait 2 * 4 ms for key to
+ * stabilize on press, wait (1 + 1) * 4 ms for key release
+ */
+ writel(FIRST_CONVERT_DLY(0) | LEVELA_B_CNT(0) | HOLD_EN(0) |
+ SAMPLE_RATE(0) | ENABLE(1), LRADC_CTRL);
+
+}
+
+void lradc_disable(void)
+{
+ writel(0xffffffff, LRADC_INTS);
+ writel(0, LRADC_INTC);
+
+ /* Disable lradc, leave other settings unchanged */
+ writel(FIRST_CONVERT_DLY(2) | LEVELA_B_CNT(1) | HOLD_EN(1) |
+ SAMPLE_RATE(2), LRADC_CTRL);
+}
diff -urN u-boot2/board/sunxi/lradc.h u-boot/board/sunxi/lradc.h
--- u-boot2/board/sunxi/lradc.h 1970-01-01 00:00:00.000000000 +0000
+++ u-boot/board/sunxi/lradc.h 2020-06-27 01:11:32.104472000 +0000
@@ -0,0 +1,11 @@
+#pragma once
+
+enum {
+ KEY_NONE = 0,
+ KEY_VOLUMEDOWN = 1,
+ KEY_VOLUMEUP = 2,
+};
+
+int lradc_get_pressed_key(void);
+void lradc_enable(void);
+void lradc_disable(void);
diff -urN u-boot2/volumepatchfirst.patch u-boot/volumepatchfirst.patch
--- u-boot2/volumepatchfirst.patch 1970-01-01 00:00:00.000000000 +0000
+++ u-boot/volumepatchfirst.patch 2020-06-27 01:11:04.466880000 +0000
@@ -0,0 +1,177 @@
+From 0ab6225154c3d8b74f06fb3b181b52a9a64b4602 Mon Sep 17 00:00:00 2001
+From: Ondrej Jirman
+Date: Tue, 11 Feb 2020 14:10:05 +0100
+Subject: pinephone: Add volume_key environment variable
+
+When the user has a volume key pressed volume_key variable will
+contain either value 'down' or 'up', otherwise it will be empty.
+
+Signed-off-by: Ondrej Jirman <megous@megous.com>
+---
+ board/sunxi/Makefile | 1 +
+ board/sunxi/board.c | 18 ++++++++++++
+ board/sunxi/lradc.c | 81 ++++++++++++++++++++++++++++++++++++++++++++++++++++
+ board/sunxi/lradc.h | 11 +++++++
+ 4 files changed, 111 insertions(+)
+ create mode 100644 board/sunxi/lradc.c
+ create mode 100644 board/sunxi/lradc.h
+
+diff --git a/board/sunxi/Makefile b/board/sunxi/Makefile
+index c4e13f8c38..6a8a2f5b42 100644
+--- a/board/sunxi/Makefile
++++ b/board/sunxi/Makefile
+@@ -11,3 +11,4 @@ obj-$(CONFIG_SUN7I_GMAC) += gmac.o
+ obj-$(CONFIG_MACH_SUN4I) += dram_sun4i_auto.o
+ obj-$(CONFIG_MACH_SUN5I) += dram_sun5i_auto.o
+ obj-$(CONFIG_MACH_SUN7I) += dram_sun5i_auto.o
++obj-$(CONFIG_MACH_SUN50I) += lradc.o
+diff --git a/board/sunxi/board.c b/board/sunxi/board.c
+index 6de4b53b11..2bedf7a16a 100644
+--- a/board/sunxi/board.c
++++ b/board/sunxi/board.c
+@@ -39,6 +39,7 @@
+ #include <spl.h>
+ #include <sy8106a.h>
+ #include <asm/setup.h>
++#include "lradc.h"
+
+ #if defined CONFIG_VIDEO_LCD_PANEL_I2C && !(defined CONFIG_SPL_BUILD)
+ /* So that we can use pin names in Kconfig and sunxi_name_to_gpio() */
+@@ -622,6 +623,12 @@ void sunxi_board_init(void)
+ {
+ int power_failed = 0;
+
++#ifdef CONFIG_MACH_SUN50I
++ // we init the lradc in SPL to get the ADC started early to have
++ // a valid sample when U-Boot main binary gets executed.
++ lradc_enable();
++#endif
++
+ #ifdef CONFIG_PINEPHONE_LEDS
+ /* PD18:G PD19:R PD20:B */
+ gpio_request(SUNXI_GPD(18), "led:green");
+@@ -905,6 +912,17 @@ int misc_init_r(void)
+ env_set("mmc_bootdev", "1");
+ }
+
++#ifdef CONFIG_MACH_SUN50I
++ int key = lradc_get_pressed_key();
++ if (key == KEY_VOLUMEDOWN)
++ env_set("volume_key", "down");
++ else if (key == KEY_VOLUMEUP)
++ env_set("volume_key", "up");
++
++ // no longer needed
++ lradc_disable();
++#endif
++
+ setup_environment(gd->fdt_blob);
+
+ #ifdef CONFIG_USB_ETHER
+diff --git a/board/sunxi/lradc.c b/board/sunxi/lradc.c
+new file mode 100644
+index 0000000000..693b198e25
+--- /dev/null
++++ b/board/sunxi/lradc.c
+@@ -0,0 +1,81 @@
++#include <common.h>
++#include <asm/io.h>
++#include "lradc.h"
++
++#define LRADC_BASE 0x1c21800
++
++#define LRADC_CTRL (LRADC_BASE + 0x00)
++#define LRADC_INTC (LRADC_BASE + 0x04)
++#define LRADC_INTS (LRADC_BASE + 0x08)
++#define LRADC_DATA0 (LRADC_BASE + 0x0c)
++#define LRADC_DATA1 (LRADC_BASE + 0x10)
++
++/* LRADC_CTRL bits */
++#define FIRST_CONVERT_DLY(x) ((x) << 24) /* 8 bits */
++#define CHAN_SELECT(x) ((x) << 22) /* 2 bits */
++#define CONTINUE_TIME_SEL(x) ((x) << 16) /* 4 bits */
++#define KEY_MODE_SEL(x) ((x) << 12) /* 2 bits */
++#define LEVELA_B_CNT(x) ((x) << 8) /* 4 bits */
++#define HOLD_KEY_EN(x) ((x) << 7)
++#define HOLD_EN(x) ((x) << 6)
++#define LEVELB_VOL(x) ((x) << 4) /* 2 bits */
++#define SAMPLE_RATE(x) ((x) << 2) /* 2 bits */
++#define ENABLE(x) ((x) << 0)
++
++/* LRADC_INTC and LRADC_INTS bits */
++#define CHAN1_KEYUP_IRQ BIT(12)
++#define CHAN1_ALRDY_HOLD_IRQ BIT(11)
++#define CHAN1_HOLD_IRQ BIT(10)
++#define CHAN1_KEYDOWN_IRQ BIT(9)
++#define CHAN1_DATA_IRQ BIT(8)
++#define CHAN0_KEYUP_IRQ BIT(4)
++#define CHAN0_ALRDY_HOLD_IRQ BIT(3)
++#define CHAN0_HOLD_IRQ BIT(2)
++#define CHAN0_KEYDOWN_IRQ BIT(1)
++#define CHAN0_DATA_IRQ BIT(0)
++
++// this is for PinePhone only
++
++int lradc_get_pressed_key(void)
++{
++ uint32_t val;
++ uint32_t vref = 3000000 * 2 / 3;
++
++ val = readl(LRADC_DATA0) & 0x3f;
++ val = val * vref / 63;
++
++// printf("lradc=%u\n", val);
++
++ if (val < 200000) // 158730
++ return KEY_VOLUMEUP;
++ else if (val < 400000) // 349206
++ return KEY_VOLUMEDOWN;
++
++ return 0;
++}
++
++void lradc_enable(void)
++{
++ // aldo3 is always on and defaults to 3V
++
++ writel(0xffffffff, LRADC_INTS);
++ writel(0, LRADC_INTC);
++
++ /*
++ * Set sample time to 4 ms / 250 Hz. Wait 2 * 4 ms for key to
++ * stabilize on press, wait (1 + 1) * 4 ms for key release
++ */
++ writel(FIRST_CONVERT_DLY(0) | LEVELA_B_CNT(0) | HOLD_EN(0) |
++ SAMPLE_RATE(0) | ENABLE(1), LRADC_CTRL);
++
++}
++
++void lradc_disable(void)
++{
++ writel(0xffffffff, LRADC_INTS);
++ writel(0, LRADC_INTC);
++
++ /* Disable lradc, leave other settings unchanged */
++ writel(FIRST_CONVERT_DLY(2) | LEVELA_B_CNT(1) | HOLD_EN(1) |
++ SAMPLE_RATE(2), LRADC_CTRL);
++}
+diff --git a/board/sunxi/lradc.h b/board/sunxi/lradc.h
+new file mode 100644
+index 0000000000..c908401b5b
+--- /dev/null
++++ b/board/sunxi/lradc.h
+@@ -0,0 +1,11 @@
++#pragma once
++
++enum {
++ KEY_NONE = 0,
++ KEY_VOLUMEDOWN = 1,
++ KEY_VOLUMEUP = 2,
++};
++
++int lradc_get_pressed_key(void);
++void lradc_enable(void);
++void lradc_disable(void);
+--
+cgit v1.2.3
+
</pre>

[[Category:PinePhone]]

PinePhone 1.1 VBUS power usage Hardware Fix

2020-09-02T10:23:34Z

Jbit: Add to PinePhone category

This page details a hardware fix for an issue that affects some early [[PinePhone#Hardware_revisions | PinePhone]] units, namely [[PinePhone v1.1 - Braveheart | v1.1 Braveheart]] units (fixed since [[PinePhone v1.2 | 1.2 community edition]] included).

The issue was [[PinePhone_v1.1_-_Braveheart#Excess_power_usage_while_driving_VBUS | originally reported here]] by megi.

TODO: Add more pictures and schematics, better reference the fix origin and tradeofs, remove TODOs/FIXMEs.

== Affected Units ==
# [[PinePhone v1.1 - Braveheart]]

FIXME: confirm [[Project Don't be evil|"Project Don't Be Evil" devkit]] and [[PinePhone v1.0 - Dev|PinePhone v1.0 - Developer batch]] are unaffected.

== Disclaimer ==

Though easier to perform than the [[PinePhone 1.2 VCONN Hardware Fix]], this fix requires desoldering relatively small Surface Mount Technology (SMT) components, therefore some experience with soldering is recommended.

== Issue description ==
TODO: pictures

The AXP803 cannot detect when the USB port is powered by the battery. Therefore, the Power Management IC (PMIC) continues draining current from it. This is especially problematic since this USB port is powered from the battery with the USB OTG boost regulator. One of the symptoms is the battery discharging rather quickly even when the phone is powered off.

== Workaround ==

HW workaround is desoldering the U1301 regulator (TODO: describe its role) and shorting pads for R1309 on the PCB (this is a "0 ohm" resistor on the schematic, so it's completely fine).

Shorting the pads is easy to do with some solder (while carefully avoiding to short it with nearby resistors).

Desoldering the regulator is harder to do, since its large pads are designed to use the PCB as a heatsink and will happily cool down while you are trying to melt it. It should be possible to use properly sized pliers to cut the pins first, please edit if you attempt this.

Please be careful not to overheat nearby components trough the PCB traces when applying heat to the regulator. It can be helpful to start the operation with melting some leaded solder tin together with the pads, and lifting the regulator while applying heat also helps. Start with the side that has only one pad: though it is bigger, it should be easier to lift up. It might be useful to apply a relatively large quantity of molten solder tin to each pin, in turn, while lifting the regulator, to reduce the PCB heatsink effectiveness.

Feel free to add your experiences and tips here.

=== Tradeoffs ===
TODO: Unknown to the author

== Proper fix ==
TODO

== Sources and tutorials ==
* [https://xnux.eu/devices/pp-pmic-fix.jpg Tutorial from megi]
* [https://xnux.eu/devices/feature/anx7688.html Description from megi] at the end of the page

[[Category:PinePhone]]

PinePhone UBports OS Design Discussion

2020-09-02T10:23:33Z

Jbit: Add to PinePhone category

==Why this page==
As I saw a lot of bad things said about the UBPorts OS shipped with their Community Edition, and a lot of people were ready to give up on it, I asked UniversalSuperBox and the rest of the UBPorts people to help the general PinePhone community out, providing answers to some misunderstandings people have about the reasoning behind the Operating System and the choices they made to make sure it is a robust system to provide to casual users that do not yet see the option to contribute as viable.

I personally think the UBPorts team has made some very smart decisions to make Linux more secure in a device that is always vulnerable to physical attacks, as it is moving around in the world, as opposed to the traditional Linux machine in a protected serverroom. Linux is very robust, it just does not try to protect against all Threat Models. UBPorts already provides a lot of devices with their OS, so they have a lot of experience and thought put into the system already, and it would be good to leverage that for other projects as well, once they are ready to look into those. Maybe they will use a different reasoning, but it still is good to learn how the UBPorts community solved their issues.

Specifically I asked for an answer to the reasoning behind the formatting scheme and creation of the UBPorts image, which is one of the things a lot of the people seem to struggle with. There are more issues that seemingly stop users from using their OS as a open system to experiment on, but these are for great reasons as weel, in my opinion. If we could understand those reasons better, all of our communities could improve.

UniversalSuperBox was willing to provide us with some answers, and as always, presented them very well, and it was very interesting to read. Thank you for that!

As I think it would be sad to leave such valuable info in the backlog of the chat, I would like to post it here as well, and try to make the most sense out of them. I hope many will add their conclusions, so we all learn. Later on, I hope we can look into other differences of the UBPorts system, and look into the specific solutions other OSs found for some common problems.

==Chat log==
So first, UniversalSuperBox chat log:

UniversalSuperBox: abcde, there are 10 partitions on the device. Loader, scr, persist, boot_a, boot_b, recovery_a, recovery_b, cache, system, data.
UniversalSuperBox: loader is the u-boot bootloader. It's not at sector 16 like on most OSes so that a full GPT table can be available at any time.
UniversalSuperBox: scr stores the boot.scr script which allows the system to boot at all
UniversalSuperBox: persist is a 5M-ish partition for storing things that need to persist between reboots. Right now that's exclusively the reboot-recovery file which tells the bootscript to boot to the recovery partition (later we'll probably put the selected boot slot there)
UniversalSuperBox: boot stores the kernel, dtb, initramfs, and kernel modules. There is an A and B boot partition. This is for A/B slot booting someday.
UniversalSuperBox: recovery stores the Jumpdrive-based recovery image which is used for updating the system and recovering when things go sideways.
UniversalSuperBox: There is an A and B slot.
UniversalSuperBox: https://github.com/ubports/jumpdrive
UniversalSuperBox: cache and system are the same size. System is where the root filesystem is stored. It is mounted as / in a booted system.
UniversalSuperBox: Cache stores update files which are applied to the system partition by recovery on an update.
UniversalSuperBox: Cache and system are the same size so that cache can be system_a and system can be system_b someday
UniversalSuperBox: Data stores all of the writable data on the system.

Unaddressed part:
UniversalSuperBox: The system is set up on boot by the initramfs at https://github.com/ubports/initramfs-tools-ubuntu-touch/tree/xenial_-_edge_-_pine.
UniversalSuperBox: Specifically, look at the halium script in the scripts folder
UniversalSuperBox: I know it's called halium. It is not exclusively for halium.
UniversalSuperBox: The kernel, initramfs, and such are all pulled together by the scripts inside https://gitlab.com/ubports/community-ports/pinephone
UniversalSuperBox: As well as u-boot and the rest
UniversalSuperBox: They are all placed into a device image (.tar.xz) which is applied by the system-image upgrader after the ubports image is applied.
UniversalSuperBox: All of that logic is inside a script in the jumpdrive repo
UniversalSuperBox: But you can find the other constituent parts of a single image (or a delta) at https://system-image.ubports.com/16.04/arm64/mainline/devel/pinephone/index.json
UniversalSuperBox: The system-image client is also https://github.com/ubports/system-image
UniversalSuperBox: And the server files are built by https://github.com/ubports/system-image-server
UniversalSuperBox: There are several problems that make me cautious to release a stable image right now. The most important one is https://bugreports.qt.io/browse/QTBUG-85802
UniversalSuperBox: Which causes the browser to crash for seemingly no reason and it's really annoying. There are also issues with keeping time which are unacceptable and must be fixed.
UniversalSuperBox: There is ongoing work to enable the camera and GPS is working at least somewhat some of the time now. All in devel.

==Analysis==
So we can at first learn some basics, the existence of 10! partitions on the flashable image. This explains the need for the bmaptools use, as if you need to separate things so well, normally you actually have to -time consuming- write the whole image if using dd and then resize the rest to gain usable free space, and bmaptools can write partitions where they are needed, and just mark the empty parts as free. This is why bmaptools is so much faster, and it even uses some checks to secure the image and the flashing process. Dd only provides blind block copying, no regard for tests etc. My conclusion about finding out about bmaptools was that it might be a good idea to move away drom dd wherever we can. That is a lot of info in such a short line :)

Then there is a list of all the partitions: "Loader, scr, persist, boot_a, boot_b, recovery_a, recovery_b, cache, system, data." Each of the names provides an indication about its function, but lets try to make a nice list out of it here on the wiki:
===UBPorts Partition list===
#loader
#scr
#persist
#boot_a
#boot_b
#recovery_a
#recovery_b
#cache
#system
#data

It is immediately clear that this is a well thought out system, protecting against a lot of possible mishaps. Some sound like they should clearly be usable to a lot of other distributions. But the next info clears up what each partition does, so lets try to add that to the list.
===UBPorts Partitions and their functions===
*loader: loader is the u-boot bootloader. It's not at sector 16 like on most OSes so that a full GPT table can be available at any time.
*scr: scr stores the boot.scr script which allows the system to boot at all
*persist: persist is a 5M-ish partition for storing things that need to persist between reboots. Right now that's exclusively the reboot-recovery file which tells the bootscript to boot to the recovery partition (later we'll probably put the selected boot slot there)
*boot_a: boot stores the kernel, dtb, initramfs, and kernel modules. There is an A and B boot partition. This is for A/B slot booting someday.
*boot_b:
*recovery_a: recovery stores the Jumpdrive-based recovery image which is used for updating the system and recovering when things go sideways. There is an A and B slot. https://github.com/ubports/jumpdrive
*recovery_b:
*cache: Cache stores update files which are applied to the system partition by recovery on an update. Cache and system are the same size so that cache can be system_a and system can be system_b someday
*system: System is where the root filesystem is stored. It is mounted as / in a booted system.
*data: Data stores all of the writable data on the system.

We can see immediately that all the partitions have a distinct use case, and from their existence alone we can deduce a lot. there seems to be only one partition that is used for the user to store the data in. It is the last of them, called data, and is expanded after writing the image, to fill the rest of the available space. This is left alone during upgrades, so we can place our personal stuff in there, and backup just our that.

Also there is a lot of talk about A and B partitions. They ensure that even if things go horribly wrong, there are ways to get back in a usable state. I will expand on that later...

More will follow :) If you want to show off your reasoning in the OS you like, talk to me on IRC (irc.pine64.org) or any of the connected chat channels. I am abcde :)

[[Category:PinePhone]]

User:Oogwaymaki/Kernel Installation

2020-09-02T10:23:29Z

Jbit: Add to PinePhone category

===Why would you want to install a custom kernel?===

The reasons why you'd want to instal a custom kernel is if there were fixes in the kernel
that allows the device to function better than it was before, or if you want to deviate with probably better functionality that the mass user base isn't configured for.
You can experiment with new features that are not yet documented or ready but could provide a great functionality when using your phone or device or operating system

Other reason is that the newest rc kernel contains code that is closest to getting mainlined into the Linus' kernel tree, so giving it some testing helps with catching
issues prior to these issues potentially affecting more people than necessary. You'll be helping the development.

===Things to look out for when installing a custom kernel and problems that can happen===

Some things to look out for when installing a custom kernel are the following:

* Does the kernel have all the modules you need installed for the system to boot liked
* Drivers
* Functionality

If you don't have the proper drivers for your particular kernel such as if you use a particular file system or
feature it will not work if not compiled into the kernel.

===What to do if the kernel does not have all your functionality but you want the patch it fixes or address?===

You would want to compile the kernel from scratch, adding all the features and functionality you need, and using the patch utility and methods you need. This takes added time like 30 min to several hours.

===Installing Megi's pre-compiled kernel===

prereqs:

You'll need a uart or a way to connect to your device to call

<pre>
depmod -a

</pre>

Install dependencies:

* u-boot-tools allows you to make images
* rsync allows you to copy and backup

<pre>
# apt-get update
# apt-get install rsync u-boot-tools
</pre>

First, download the the PinePhone CE (1.2) Kernel:

<pre>
# wget https://xff.cz/kernels/5.8/pp2.tar.gz
</pre>

Extract the kernel:

Create a separate folder for organization and separation:
Extract the a "tar" "gz" file using tar.

<pre>
# tar -zxvf pp2.tar.gz
</pre>

A default Mobian Installation looks like this:

<pre>
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 1953 250000 248048 121.1M 83 Linux
/dev/sda2 250001 7421874 7171874 3.4G 83 Linux
</pre>

Notice the small size on the /boot partition.

This means we probably will have to, either ignore the the first partition or resize both partitions so we can
keep existing structure.

Easiest thing to do:

Please all all the new files on the /dev/sda2 (they'll probably be more than 121 M)

Next we need to update the initrd image, to have the new modules, (the initrd image is a RAM disk helping the system to boot and needs kernel drivers while booting):

How to get and update initrd image:

Mount Mobian boot image:
Make sure your the root user for this for ease of installation:
Delete the old kernel modules and put the new latest ones there
<pre>
# mkdir debianboot
# mount /dev/sda1 /media/debianboot
# cd /usr/src
# mkdir initrd
# cd /usr/src/initrd
# cp /media/debianboot/initrd.img-5.7-pinephone .
# zcat initrd.img-5.7-pinephone | cpio -idmv
# rm initrd.img-5.7-pinephone
# cd /usr/src/initrd/lib/modules
# rm -rf /usr/src/initrd/lib/modules/5.7-pinephone
# rsync -avh pp2-5.8/modules/lib/modules/ initrd/lib/modules/

</pre>

Repackage the Mobian Boot Image after new kernel modules installed and copy over to main mobian image now

<pre>

# find . | cpio -o -c | gzip -9 > initrd.img-5.8-pinephone
# mkdir /media/mobianroot
# mount /dev/sda2 /media/mobianroot
# cp initrd/initrd.img-5.8-pinephone /media/mobianroot/boot/
</pre>

Copy the pp 2.8 kernel and dab definition files to Mobian boot folder and update the boot.scr
<pre>
# cp pp2-5.8/board.dtb /media/mobianroot/boot/
# cp pp2-5.8/Image /media/mobianroot/boot/
</pre>

Change the old boot.cmd to the new settings:

<pre>
if test ${mmc_bootdev} -eq 0; then
echo "Booting from SD"
setenv linux_mmcdev 0
else
echo "Booting from eMMC"
setenv linux_mmcdev 2
fi

# If we have at least 2 partitions, then the 1st one is /boot, and / is #2
if fstype mmc ${mmc_bootdev}:2; then
setenv rootpart 2
else
setenv rootpart 1
setenv bootdir "/boot"
fi

setenv bootargs console=ttyS0,115200 no_console_suspend panic=10 consoleblank=0 loglevel=7 root=/dev/mmcblk${linux_mmcdev}p${rootpart} rw splash plymouth.ignore-serial-consoles vt.global_cursor_default=0

led 1 on

echo "Loading kernel..."
load mmc ${mmc_bootdev}:1 ${ramdisk_addr_r} ${bootdir}/Image.gz

echo "Uncompressing kernel..."
unzip ${ramdisk_addr_r} ${kernel_addr_r}

echo "Loading initramfs..."
load mmc ${mmc_bootdev}:1 ${ramdisk_addr_r} ${bootdir}/initrd.img
setenv ramdisk_size ${filesize}

echo "Loading dtb..."
load mmc ${mmc_bootdev}:1 ${fdt_addr_r} ${bootdir}/dtb/${fdtfile}

led 2 on

echo "Booting..."
booti ${kernel_addr_r} ${ramdisk_addr_r}:0x${ramdisk_size} ${fdt_addr_r}

</pre>

Remove the old boot.cmd

<pre>

# rm boot.cmd

</pre>
to this, we removed the configuration of the first disk we won't be using it
we also pointed everything to second disk for kernel and boot images

<pre>

if test ${mmc_bootdev} -eq 0; then
echo "Booting from SD"
setenv linux_mmcdev 0
else
echo "Booting from eMMC"
setenv linux_mmcdev 2
fi

# If we have at least 2 partitions, then the 1st one is /boot, and / is #2
if fstype mmc ${mmc_bootdev}:2; then
setenv rootpart 2
setenv bootdir "/boot"
else
setenv rootpart 2
setenv bootdir "/boot"
fi

setenv bootargs console=ttyS0,115200 no_console_suspend panic=10 consoleblank=0 loglevel=7 root=/dev/mmcblk${linux_mmcdev}p${rootpart} rw splash plymouth.ignore-serial-consoles vt.global_cursor_default=0 initrd=/boot/initrd.img-5.8-pinephone

led 1 on

echo "Loading kernel..."
load mmc ${mmc_bootdev}:2 ${kernel_addr_r} ${bootdir}/Image

echo "Loading dtb..."
load mmc ${mmc_bootdev}:2 ${fdt_addr_r} /boot/board.dtb

led 2 on

echo "Booting..."
booti ${kernel_addr_r} - ${fdt_addr_r}
</pre>

Save new boot.cmd to /dev/sda1 root folder (where the old boot.cmd was)

# cd /media/mobianboot
<pre>
# mkimage -C none -A arm64 -T script -d boot.cmd boot.scr
root@wifirouter:/media/mobianboot# mkimage -C none -A arm64 -T script -d boot.cmd boot.scr
Image Name:
Created: Mon Jun 29 19:13:19 2020
Image Type: AArch64 Linux Script (uncompressed)
Data Size: 876 Bytes = 0.86 KiB = 0.00 MiB
Load Address: 00000000
Entry Point: 00000000
Contents:
Image 0: 868 Bytes = 0.85 KiB = 0.00 MiB
</pre>
<pre>
# e2label /dev/sda2 ROOT
# make fstab look like this:
LABEL=ROOT / ext4 defaults 0 0
</pre>
boot up device.l
== References ==

* https://access.redhat.com/solutions/24029
* https://linux-sunxi.org/U-Boot

[[Category:PinePhone]]

PinePhone Carrier Support

2020-09-02T10:18:21Z

Jbit: Add to PinePhone category

{{warning|1=MMS doesn't currently work in any distro on the Pinephone by default! This means images and group chats will not work in text messages.}}
{{warning|1=Calls are regressed currently as there is a clock mismatch from the modem to the mainboard, this should be resolved soon.}}
{{hint|This page is incomplete, you're welcome to improve it.}}

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

= Carriers=

== T-Mobile ==

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

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

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

== Cricket Wireless ==

Cricket wireless is a MVNO that uses AT&T's network. VoLTE is fully supported and the pinephone is considered a compatible device in the US by the carrier.

== Verizon ==

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

Verizon's bands and protocols are summarized on
[https://www.frequencycheck.com/carriers/verizon-wireless-united-states this page].
However, it also says:

<blockquote>
This carrier only accepts approved devices on its network.
Even if a device supports some or all of the required frequencies for this carrier,
it will not be able to connect unless the device is approved for this network.
Check with the network operator to confirm whether a device is approved or not.
</blockquote>

{{hint|Needs more info. If verizon works for you please edit this section with details on what does/doesn't work.}}

= Issues =

The [https://www.frequencycheck.com/models FrequencyCheck model page]
does not list either Pine64 or the PinePhone.

Tmobile's system does not list the pinephone as a compatible device due to the lack of official VoLTE support from the manufacturer, despite the fact that it does work.

MMS doesn't currently work in any distro on the pinephone by default. This means images and group chats will not work in text messages.

= Resources =

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

[[Category:PinePhone]]

PinePhone Installation Instructions

2020-09-02T10:18:19Z

Jbit: Add to PinePhone category

This section has generic installation instructions. Please see the [[PinePhone Software Releases]] section for specific installation instructions for each distribution.

== Boot priority ==

The default PinePhone boot priority is first the SD card and then the eMMC so inserting your own SD card with your preferred release will result in the phone booting your image.

== Preparation of SD card ==

# Download your chosen image from the options below
# Extract the compressed file
# Write the image to your SD card
# Plug SD card into phone
# Boot phone

If you need step-by-step instructions for writing an image to an SD card, check [[NOOB#Step-by-Step_Instructions_to_Flashing_MicroSD_Cards|the NOOB guide]], then return to this page.

=== bmaptool ===
Download the .img.xz and the .img.bmap files, then run <code>bmaptool copy --bmap image.bmap image.xz /dev/sdX</code>. This takes 2.5mins to flash a 4Gb file.

=== dd ===
Make sure to select the correct device using <code>lsblk</code>. Then run dd with the correct device:

<code>sudo dd if=pine.img of=/dev/[DEVICE] bs=1M status=progress conv=fsync</code>

== Installation to eMMC (Optional) ==

=== Method Using Factory Installed Tools ===

The initial OS you get with your phone has the option to flash an image on SD card to eMMC.

# Copy (not flash) the image file to a formatted SD card.
# Insert SD card into powered-off phone.
# Turn on phone and select option to install to eMMC.

=== Safe & Easy Method ===

[https://forum.pine64.org/showthread.php?tid=9444 Jumpdrive thread]

# download and extract [https://github.com/dreemurrs-embedded/Jumpdrive/releases the Jumpdrive image]
# flash the Jumpdrive image to a SD card
# boot from the 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 as you'd flash any SD card, and resize partitions (optional, see below)
# disconnect the PinePhone from your PC, power it down and remove the Jumpdrive SD card
# boot into your OS of choice on eMMC

The Jumpdrive image is smaller than 50MB. You can keep an SD card specifically for using Jumpdrive, and there are 64MB micro SD cards sold cheaply that will suffice.

=== Safe With No Extra Tools, But Slower ===

# Prepare a formatted SD card, flash desired OS to the SD card, and (optionally) resize the partition (see below)
# Insert SD card and boot the phone
# Open terminal and <code>git clone [url]</code> your desired project OR: Open web browser and download the desired OS image file.
# Build the OS (Optional)
# Flash the resulting image file you got by downloading or by building, to eMMC, using <code>dd if=new-pinephone-image.img of=/dev/mmcblkY bs=1M status=progress</code> where X is the number label of the SD card, and Y is the number label of the eMMC. Use the command ''lsblk'' to check your devices: typically with the current kernel the SD card is /dev/mmcblk0 and the eMMC is /dev/mmcblk2 but as always with ''dd'' be extremely cautious to get the devices correct. Then, resize partition to fill up entire disk (see below).
# Turn off phone, remove SD card. Turn on phone.

=== Risky Method ===

Warning: This copies a mounted filesystem, which can lead to instability, erratic behavior, and data corruption. Do not use long term.

# Prepare a new SD card, flash desired OS to the SD card
# Boot the phone with your new SD card image
# Within the booted OS, flash/clone the running OS to eMMC, e.g. using dd. It will take about 15 minutes (depending on the speed of your card), and in the end it may show an error about not enough space - just ignore it.
# Turn off phone, take out SD card, and try booting the phone which should load up the new OS from eMMC.
# Open terminal and resize partition to fill up entire disk (see below).

== Resize partition to fit disk space ==

Once you've flashed the OS to your SD card or eMMC storage, you may also need to expand the partition to fill all the available space.

=== Resize SD card's partition using computer ===

For SD cards, insert the SD card and resize the partitions through the computer. For eMMC, insert the phone cable and use Jumpdrive to access the eMMC directly, and resize the partition after flashing the image. To do the flashing you have two options:

====Using Growpart: ====

Locate growpart (<code>apt-cache search growpart</code> and install the package in the search results) and run:
growpart /dev/mmcblkX Y
resize2fs /dev/mmcblkXpY
where X is the storage device and Y is the partition number (viewable from lsblk).

If you get any errors about missing or unknown commands, use apt-cache search to find and install the needed software. Also don't forget to use sudo.

====Using Parted: ====

Parted's interactive mode and resize work well together. Do this before you put your SD card into the PinePhone for the first time for best results.

sudo parted /dev/<your_sd_card_device>
(parted) resizepart 2 100%
(parted) quit
sudo resize /dev/<the_second_sd_card_PARTITION>

=== Resize from within PinePhone: ===

eMMC: you would need to resize the partition on eMMC (flashed with the operating system) by booting another image from the SD card: that way, the eMMC will be unmounted. It is '''not recommended''' to resize eMMC while booted from eMMC! Resizing a currently mounted partition can have weird results. If you booted from the SD card, you can follow the above guidelines on how to resize from a computer.

SD card: It is generally not possible to boot from eMMC to partition the unmounted SD card, because of the boot order -- you would have to write the image to the empty SD card first, then resize partition, all without rebooting. It is also '''not recommended''' to resize the SD card while booted from SD card! Resizing a currently mounted partition can have weird results.

== Reuse SD card for data storage on system booting from eMMC==
Once you have installed your release of choice to eMMC, you may wish to use an SD card for data storage. If you choose to re-use a card you have previously used to boot from, you will find your phone will not boot if you just reformat the card and insert it. This is because the Allwinner firmware in the PinePhone uses some (normally) unused space at the front of the SD card to store boot software, which you need to clear.

This can be done as follows on any linux system:
lsblk
to check the device of your SD card – as an example lets assume it is /dev/mmcblk0
then
sudo dd if=/dev/zero of=/dev/mmcblk0 bs=8k seek=1 count=4
will clear the relevant sectors of your card.

[[Category:PinePhone]]

PinePhone

2020-09-02T10:18:14Z

Jbit:

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, the first Community Edition started to ship in June 2020. The phone 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]]

[[File:PinePhoneSides.svg|400px|thumb|right|Backward and front of PinePhone UBPorts Edition]]

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 or 3GB LPDDR3 SDRAM 
'''Internal Storage:''' 16GB or 32GB eMMC, extendable up to 2TB via microSD, supports SDHC and SDXC 
'''Back Camera:''' Single 5MP, 1/4", LED Flash 
'''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: G25-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 
'''Killswitches:''' Modem, WiFi & Bluetooth, Microphone, Cameras 
'''Battery:''' Lithium-ion, rated capacity 2800mAh (10.64Wh), typical capacity 3000mAh (11.40Wh) (nominally replaceable with any Samsung J7 form-factor battery) 
'''I/O:''' USB Type-C, USB Host, DisplayPort Alternate Mode output, 15W 5V 3A Quick Charge, follows USB PD specification

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

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

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

=== USB-C connector ===

The USB-C can be used to power the device, and offers USB2 host and OTG possibilities, and also can make use of the USB-C capability to integrate HDMI signals. Some USB-C hubs are available that offer power throughput, USB connection, HDMI port and Ethernet connection. 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, an IR blaster, a keyboard extension or extended battery case. The pogo pins provide access to an interrupt line, power input to charge the battery, power source and an I2C interface.

[[File:Pinephone pogo.png|none|400px]]

{| class="wikitable"
| Interrupt
| SDA
| SCL
|-
| 5V / VBUS
| VBAT
| GND
|}

The VBUS pin is powered by USB and is 5V. The second power pin is VBAT, which connects to the battery voltage. The I2C and interrupt lines have pull-ups on the phone side. The I2C lines are pulled up to 3V3 by the phone.

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

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

=== Serial console ===

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

The UART is 115200n8.

The pinout for the serial connector is:

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

[[File:PinePhone_Serial_Cable.png|none|400px]]

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

== Killswitch configuration ==

[[File:PinePhone 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.

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

== Battery ==

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

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.
* The extended life aftermarket BBU do fit, however, somewhat firmly.
* 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 phone 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 and check that the pins aren't bent. This is to protect the device from turning on during shipping.}}

If using an aftermarket battery on the CE edition phones, removing the lower tabs is not necessary as there is space supplied in the compartment.

<gallery mode="packed", heights=300px>
Image:PinePhone battery1.png|Photo of Brave Heart case from OSAKANA TARO on Twitter
Image:PinePhone battery3.jpeg|Photo of Brave Heart battery sticker from OSAKANA TARO on Twitter
</gallery>

== Modem and carrier support ==
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]].

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

=== Documents ===

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.

== 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 get mainlined and distributions ship with the updated kernel, they will also be able to run unmodified on the device.

=== Installation instructions ===

For instructions on how to install the operating systems to 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 an 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 PinePhone drive (e.g. /dev/mm..., check for the right device in dmesg, GNOME disks, or similar, and make sure it's unmounted) with your 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.7GB partition on it. To use the entire 14.7GB on the eMMC, run the following commands:

# sudo cfdisk /dev/sdX
# Change to [Resize] in the ncurses program, resize the 3.7GB partition to 14.7GB, 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

== Frequently asked questions ==

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

== PinePhone board information, schematics and certifications ==
* PinePhone mainboard schematic:
** [http://files.pine64.org/doc/PinePhone/PinePhone%20v1.2a%20Released%20Schematic.pdf PinePhone mainboard Released Schematic ver 1.2a]
** [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]
* [[PinePhone component list]]

== 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:
** [http://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf RTL8723BS/RTL8723CS specification]

* LTE module information:
** [https://www.quectel.com/UploadFile/Product/Quectel_EG25-G_LTE_Standard_Specification_V1.2.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 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]

[[Category:PinePhone]]

PinePhone APN Settings

2020-09-02T10:15:02Z

Jbit: Add to PinePhone category

= Setting the APN =

The location of the APN setting depend on the user interface the distribution is using.

== Distributions with Phosh ==

APN settings are either located in <code>Settings > Mobile > Access Point Names</code> (Arch Linux ARM, PureOS, Debian + Phosh) or <code> Settings > Network > Network Dropdown > Add new connection</code> (pmOS, Fedora).



= List of tested carriers =

Disclaimer: Go to the websites of or speak to the customer support lines of those carriers which you want to use. No guarantees. This list is simply user-generated and serves to demonstrate examples of what worked for them. This list is not exhaustive, does not cover all possible carriers.

== AT&T-based (USA) ==

=== AT&T ===
APN: <code>phone</code> or <code>NXTGENPHONE</code> if "phone" does not work (see https://www.att.com/support/article/wireless/KM1218306/).

=== Cricket ===
APN: <code>phone</code> or <code>ndo</code> or <code>NXTGENPHONE</code>

== Bouygues Telecom (France) ==
Name: Bouygues Telecom
APN: mmsbouygtel.com
Username: <empty>
Password: <empty>

Source: https://www.assistance.bouyguestelecom.fr/s/article/parametrage-mobile-email-mms-internet

== Free (France) ==

Name: Free
APN: free
Username: free
Password: <empty>

Source: https://mobile.free.fr/assistance/46.html

== Mineo (Japan) ==

Tested with S plan (Softbank) and D plan (Docomo). AU plan requires VoLTE so will probably not work. Softbank plan also failed to have the SIM card detected by any of the OSes tested (pmOS, UBT, Sailfish).

Mobile LTE data currently working only on Phosh-based OSes, because they use Network Manager and Modem Manager. UBT not working yet, see issue #58. https://gitlab.com/ubports/community-ports/pinephone/-/issues/58

APNs are provided by Mineo

Name: Mineo
APN: mineo-d.jp
Username: mineo@k-opti.com
Password: mineo

Source: https://support.mineo.jp/manual/network_setup_d.html

== Mint Mobile (USA) ==

Call their customer service to activate using the number on their website, or activate on their [https://my.mintmobile.com/activation website]. You may also need to reboot your phone.

Use the following APN settings:

Name: Ultra
APN: Wholesale

Source: https://www.mintmobile.com/setup-for-android/

== Mobile Vikings (Belgium) ==

Name: Mobile Vikings
APN: web.be
Username: web
Password: web

Source: https://support.vikingco.com/hc/en-us/articles/202836041-I-don-t-have-any-mobile-internet-What-do-I-do-

== Orange Telecom (France) ==
Name: Orange Internet
APN: orange
Username: <empty>
Password: <empty>

Source:https://assistance.orange.fr/mobile-tablette/tous-les-mobiles-et-tablettes/depanner/probleme-avec-un-service-d-orange-internet-sms-mms-mails-cloud-tv/mms/configurer-un-apn-internet-et-mms_192948-738196

== Penny Mobil (Germany) ==

APN settings:

name: Penny Mobil
APN: internet.t-mobile
username: t-mobile
password: tm

== Public Mobile (Canada) ==
Internet only, mms not tested.

Name: Public Mobile
APN: sp.mb.com
Username: <empty>
Password: <empty>

Source: https://productioncommunity.publicmobile.ca/t5/Phones-Hardware/How-do-I-set-up-data-APN-on-my-smartphone/td-p/3

== Red Pocket (USA) ==

You can choose AT&T, Verizon, T-Mobile or Sprint network. Known to work with the GSMA (ATT) SIM, calls and SMS work.

APN settings:

name: Red Pocket
APN: RESELLER

== Simyo (Spain) ==

APN settings:
APN: orangeworld

Source: https://blog.simyo.es/simyo-configuracion-internet-wap-mms/configura-tu-movil/

== Telekom (Germany) ==

APN settings:

Name: Telekom
APN: internet.t-mobile
Username: t-mobile
Password: tm

Source: https://www.telekom.de/hilfe/mobilfunk-mobiles-internet/mobiles-internet-e-mail/apn-mobilfunk/wie-lauten-die-apn-fuer-mobilfunk?samChecked=true

== Tracfone (USA) ==

''BYOP SIM Card Kit'' works with T-Mobile and AT&T compatible SIM cards provided in BYOP kit.

Calls, SMS and 3G/4G data known to work with Verizon & AT&T SIMs (most likely works for T-Mobile as well).

Use the following APN settings:

Name: Tracfone
APN: RESELLER
Username: <empty>
Password: <empty>

To use Verizon's network:

Name: Tracfone
APN: TRACFONE.VZWENTP
Username: <empty>
Password: <empty>

== Virgin Mobile (Canada) ==

Settings might work with Bell Canada too since it is the same network. Calls, SMS and 4G data appear to be working fine. Note that SIM may well be nano-sim but pinephone is micro-sim and may require an adapter.

Name: Mobile Fast Web
APN: pda2.bell.ca
Username:
Password:

== Vodafone (Czech republic) ==
Name: internet
APN: internet
Username: <empty>
Password: <empty>

Source: https://www.vodafone.cz/pece/osobni-a-firemni/otazky/zaciname-s-chytrym-telefonem/pripojeni-nastaveni-internetu-v-telefonu/

= Carriers that do not work =

== FreedomPop (USA) ==
VoIP-service. Customer service said they require Android 4.3+, and their free calling and texting works only with the Google Play app they make you use. So calls and texts don't work with non-smart phones and won't work with the PinePhone (even though it is a smart phone) because of software incompatibility. However, the data part still work if APN has been seen correctly set to '''fp.com.attz'''. You get 200MB free data per month. However, please watch out that you will get ding by $20 top up charge when over 200MB limit.

APN: <code>fp.com.attz</code>

== Sprint (USA) ==

VoLTE service. Recently some distributions got VoLTE working using AT commands (see for example the [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#VoLTE postmarketOS wiki]), please update this paragraph when having tested Sprint successfully.

APN: <code>cinet.spcs</code>

== Verizon (USA) ==

VoLTE service.

== Other ==

Other VoLTE services.

= External links =

* See also https://forum.pine64.org/showthread.php?tid=9150

[[Category:PinePhone]]

PinePhone Software Releases

2020-09-02T10:15:00Z

Jbit: Add to PinePhone category

This page contains a list of all available releases for the PinePhone as well as links to further resources.

See [[PinePhone Installation Instructions]] on how to install the operating systems.

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

= Software Releases =
This is a list of OSes that specifically support the PinePhone, but as support is included in Mainline Linux, in principle any ARM Linux OS can be used, if possible required patches are included.

== postmarketOS ==
[[File:PostmarketOS-logo.png|100px]]

postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices that offers a choice of several desktop environments including Plasma Mobile and Phosh.

* ''' Download location '''
Rather than downloading a demo image, postmarketOS [https://wiki.postmarketos.org/wiki/Installation_guide recommends the use of their script], pmbootstrap, that can tailor build your SD card for you.

Note: pmbootstrap offers an option [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone)#Installation to install to the eMMC].

Demo images can be found [http://images.postmarketos.org/pinephone/ here].

* ''' username/password '''
demo/147147 (for demo images only - when building an image with pmbootstrap you set your own username and password (the Phosh lock screen requires your password, but only presents a numeric keyboard, so you should use only numbers in your password).

* ''' What works, what does not work '''
See [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) postmarketOS dedicated PinePhone wiki page]

If you install Firefox browser (or are using a demo image that already has it installed) then [https://wiki.postmarketos.org/wiki/Firefox these hints] in the pmOS wiki are recommended.

* ''' How to contribute and report defects '''
[https://gitlab.com/postmarketOS/postmarketos/issues/3 postmarketOS issue tracker] for PinePhone support. See [https://wiki.postmarketos.org/wiki/Contributing postmarketOS wiki] for options to contribute.

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

A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community.

Ubuntu touch is a mobile version of Ubuntu developed by the UBports community. Installation instructions can be found on [https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone the UBports PinePhone project]. There is also a [https://github.com/goddard/pinephone/ script] to download the latest image and flash to your PinePhone. In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://devices.ubuntu-touch.io/installer UBports installer] GUI tool.

* ''' Download location '''
[https://gitlab.com/ubports/community-ports/pinephone#how-do-i-install-ubuntu-touch-on-my-pinephone UBports PinePhone project]

* ''' username/password '''
Set up during boot

* ''' What works, what does not work '''
Scroll down to the bottom of [https://gitlab.com/ubports/community-ports/pinephone this page].

* ''' How to contribute and report defects '''
See [https://gitlab.com/ubports/community-ports/pinephone UBports gitlab page]. See [https://ubports.com/foundation/sponsors UBports website] for how to donate.

== Mobian ==
[[File:Debian-logo.png]]

An unofficial Debian build for ARM64 running with the Phosh user interface (developed by Purism, Phosh uses Wayland instead of Xorg). The base system is pure Debian, with only the GUI applications and a few others (ModemManager, WiFi chip firmware) being built from modified sources (as well as the kernel and u-boot). Current version is Debian Bullseye.

* ''' Download location '''
[http://images.mobian-project.org/ Mobian downloadable images]

Don't forget to extract the image before installing:
$ gzip -d Downloads/mobian-pinephone-*.img.gz

See the [https://wiki.mobian-project.org/doku.php?id=install project page] for specific installation instructions.

* ''' username/password '''
mobian/1234

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

See [https://gitlab.com/mobian1/mobian-recipes/-/blob/master/README.md the project's README file] or [https://wiki.mobian-project.org/doku.php?id=pinephone the wiki]for most up to date status.

Check [https://gitlab.com/a-wai/debos-pinephone/-/issues bug tracker] for known issues. Questions? Ask on our [https://forum.pine64.org/showthread.php?tid=9016 thread].

* ''' How to contribute and report defects '''
It is recommended that you log your bug reports in [https://gitlab.com/mobian1/issues the project's issue tracker]. As a general rule, issues with third-party apps (even the default ones) should be reported upstream. A Mobian issue would be related to getting the hardware to work on the PinePhone, but if unsure where the issue should be reported just open a ticket or ask. Feel free to pick an open issue to work on, or send a merge request on [https://gitlab.com/mobian1 Gitlab].

* ''' Notes '''
See [[Mobian for PinePhone]] or [https://wiki.mobian-project.org/doku.php?id=start the wiki] for additional information regarding screen resolution, USB networking, WiFi hotspot, Chatty and the repository.

== SailfishOS ==


Sailfish OS is a Linux-based operating system based on open source projects such as Mer and including a closed source UI.

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

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

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

Set PIN on initialization.

* ''' What works, what does not work '''
May 4th 2020: The SFOS image is now the latest 3.3.0.16 release. This has resolved many problems (for example MTP file transfer now works) but there are several glitches, the most serious being very intermittent wifi. Random hissing noise for about 10 seconds. This release of SF has Nextcloud integration.

May 24th 2020: Voice calls now work but not available in public builds yet. If you have a Jolla registration a minor bug means you have to submit the request twice. WiFi still intermittent. The battery indicator previously only showed level at boot, now improved but far from reliable.

If you're not familiar with SFOS pay attention to the tutorial - the interface works great but isn't immediately obvious. If you are familiar with SF you can skip the tutorial by touching all 4 corners starting top left. There is a limited selection of apps available from the Jolla store, the vast majority are hosted on openrepos.net. The Storeman app for openrepos is now preinstalled, and also Webcat browser as the built in browser is not working at the moment.

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

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

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

== PureOS ==
[[File:Pureos.png]]

PureOS is a GNU/Linux distribution focusing on privacy and security, using the GNOME desktop environment. It is developed and maintained by Purism.

* ''' Download location '''
This is an unofficial/unsupported PinePhone port by ''mozzwald'' and maintained by clover that can be downloaded [https://www.ironrobin.net/pureos/droppy/#/Images here].

* ''' source code '''
If you want to report a bug or look at what goes into the PinePhone build of PureOS, visit the Git [https://www.ironrobin.net/pureos/git/clover/pinephone/ repository].

* ''' username/password '''
purism/123456

* ''' Build instructions '''
If you want to build it yourself you can follow the instructions posted [https://mozzwald.com/pp/pureos-pinephone-build-instructions.txt here].

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

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

See [https://forum.pine64.org/showthread.php?tid=9347 this thread in the forum].

* ''' Download location '''
[https://github.com/nikhiljha/pp-fedora-sdsetup/releases/ flashable images] or [https://github.com/nikhiljha/pp-fedora-sdsetup/tree/image build scripts]

* ''' username/password '''
pine/1111

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

* ''' How to contribute and report defects '''
Please send your bug reports at [https://github.com/nikhiljha/pp-fedora-sdsetup/issues the project's issue tracker]. Be sure to include logs if applicable! Send us merge requests on [https://github.com/nikhiljha/pp-fedora-sdsetup/ Github].

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

(Unofficial) Arch Linux ARM with Phosh as the UI selection, it's usable on the PinePhone and currently being maintained by the DanctNIX community.

* ''' Download location '''
Get the latest image here: https://github.com/dreemurrs-embedded/Pine64-Arch/releases

* ''' username/password '''
alarm/123456

* ''' What works, what does not work '''
Most of the things now works, there are some minor issues with crust.

* ''' How to contribute and report defects '''
Feel free to send us merge requests and report issues on [https://github.com/dreemurrs-embedded/Pine64-Arch/pulls GitHub].

== Manjaro ARM ==
[[File:Manjaro-logo.svg|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://forum.manjaro.org/t/manjaro-arm-alpha2-with-phosh-pinephone/148 See Manjaro forum announcement of Alpha2 version]

Plasma: [https://osdn.net/projects/manjaro-arm/storage/pinephone/plasma-mobile/alpha7/ Download link for the Alpha7 version of the Plasma Mobile release]

* ''' username/password '''
** manjazo/123456
** root/root

* ''' What works, what does not work '''
See Manjaro's [https://forum.manjaro.org/t/manjaro-arm-alpha5-for-pinephone-testing-branch/136614 announcement]. In particular, phone calls do not yet work from the Phone application.

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

See the end of the [https://forum.manjaro.org/t/manjaro-arm-alpha5-for-pinephone-testing-branch/136614 announcement].

== Maemo Leste ==


[https://en.wikipedia.org/wiki/Maemo Maemo] is a trimmed-down version of Debian for mobile devices, originally a collaboration between Nokia and many open source projects (the [http://maemo.org/intro/ Maemo community]) before Nokia abandoned it. The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices.

The new version Maemo 7 "Leste" is an ARM64 port of [https://devuan.org/ Devuan] (Debian without systemd) and runs the mainline Linux kernel. The default user interface stack is [https://en.wikipedia.org/wiki/Hildon Hildon], [https://en.wikipedia.org/wiki/X.Org_Server Xorg], [https://en.wikipedia.org/wiki/Matchbox_(window_manager) Matchbox WM], and [https://en.wikipedia.org/wiki/GTK GTK]. The current version is Devuan Ascii (Debian Stretch) and they are working on an upgrade to Devuan Beowulf (Debian Buster) as well as simultaneous support for both Devuan and Debian. In addition to the main repository, they [https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html announced] a [https://github.com/maemo-leste-extras/bugtracker community repository]. To keep updated they use automation in their package maintenance with [https://github.com/maemo-leste/jenkins-integration jenkins] (similar to [https://www.debian.org/devel/buildd/ debian's buildd]). Porting packages to Maemo Leste is basically a simple matter of porting to arm64 version of Debian/Devuan, which benefits both projects.

More detailed information can be found on [https://leste.maemo.org/Main_Page the Maemo Leste wiki], or follow [https://maemo-leste.github.io/ announcements on their website], and check out [https://leste.maemo.org/Leste_FAQ Frequently Asked Questions].

* ''' Download location '''
[http://maedevu.maemo.org/images/pinephone/ Maemo Leste test builds]. There is also an [https://github.com/maemo-leste/image-builder image builder], see their wiki for instructions on how to [https://leste.maemo.org/Image_Builder build a custom image].

* ''' username/password '''
root/toor

You may use "sudo" directly.

* ''' What works, what does not work '''
For current status and work arounds please read their [https://leste.maemo.org/PinePhone PinePhone wiki page], and update as necessary (make sure to notify them of new issues by leaving a report on their github, see below).

* ''' How to contribute and report defects '''
Most discussion occurs at #maemo-leste on freenode IRC. The Maemo website also has an [https://talk.maemo.org/showthread.php?p=1565822 ongoing forum thread] for feedback about Maemo Leste on the PinePhone BraveHeart edition.

All other contact information is listed on the [https://leste.maemo.org/Main_Page main page] of the Maemo wiki. You should [https://github.com/maemo-leste/bugtracker/issues submit bug reports] on github. To track known issues, you may use these search terms: [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pinephone pinephone], [https://github.com/maemo-leste/bugtracker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+pine64 pine64]. Learn about [https://leste.maemo.org/Development development], [https://leste.maemo.org/Development/Porting_Packages porting packages], [https://leste.maemo.org/Development/Building_Packages building packages], [https://leste.maemo.org/Development/Tasks todo list], and general info on [https://wiki.debian.org/HowToPackageForDebian how to package for Debian]. Some tasks have funding available.

== Nemo Mobile ==


Nemo Mobile is the open source build of Sailfish OS, see the new website nemomobile.net.

You can install Nemo on any device that runs Sailfish, see the above website for details. Or you can flash the image to SD card/emmc on the PinePhone, download here https://yadi.sk/d/8oSZp-frGidscw (requires Yandex Disk account).

* ''' Download location '''
Download location is [https://github.com/neochapay/nemo-device-dont_be_evil/ here on GitHub]. The latest version is not an image file and therefore not for beginners!

Alternative easy installation method: install Sailfish on your PP first (follow instructions on this page under Sailfish). Enable developer mode.
In the terminal run as root (devel-su):

ssu ar nemo-devel-ux http://repo.merproject.org/obs/home:/neochapay:/nemo-ux/sailfish_latest_armv7hl/

then
pkcon refresh

then install the nemo-specific Glacier packages:

pkcon install lipstick-glacier-home-qt5

If necessary, reboot.

* ''' username/password '''

* ''' What works, what does not work '''
Scroll down the page [https://github.com/neochapay/nemo-device-dont_be_evil/ here].

* ''' How to contribute and report defects '''
For more info please visit [https://github.com/neochapay/nemo-device-dont_be_evil neochapay's Github page]

== KDE Neon ==


Based on KDE Neon for the desktop, comes with Plasma Mobile.

* ''' Download location '''
Plasma mobile images can be found [https://images.plasma-mobile.org/pinephone/ here].

* ''' username/password '''
phablet/1234

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

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

== NixOS ==


''NixOS support is handled through the Mobile NixOS project.''

* [https://mobile.nixos.org/ Project home page]
* [https://github.com/NixOS/mobile-nixos Source code repository]

There is no pre-built complete image. For now users are expected to follow the instructions in the [https://mobile.nixos.org/getting-started.html Getting Started page], and on [https://mobile.nixos.org/devices/pine64-pinephone-braveheart.html the device's page].

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

This information may change, but currently it boots, it's as compatible as the Android-based devices are with Mobile NixOS. It even supports a bit more since it can use Wi-Fi.

<cite>
Support for all of the hardware will be coming, this project is a breadth-first work, where the work spans multiple devices in parallel.
</cite>

* ''' How to contribute and report defects '''
On [https://github.com/NixOS/mobile-nixos/issues the project's repository]. Please specify that you are using a PinePhone when reporting issues. Details about contributions and donations are on the [https://nixos.org/nixos/community.html NixOS website].

== LuneOS ==


Based on WebOS by LG, comes with Luna Next desktop environment.

* ''' Download location '''
[http://build.webos-ports.org/luneos-testing/images/pinephone/ LuneOS test image for PinePhone]
Tofe recommends using bmaptool ; for example "bmaptool copy http://build.webos-ports.org/luneos-testing/images/pinephone/luneos-dev-image-pinephone-testing-0-15.rootfs.wic.gz /dev/mmcblk0". Rename .wic file to .img for standard dd usage.

* ''' username/password '''

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

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

== Sxmo ==

A collection of Suckless programs to create a mobile UI. Based on Postmarket OS

* ''' Download location '''
Sxmo images can be found [http://images.lrdu.org/pinephone/ here].

* ''' username/password '''
mo/mo

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

PinePhone's backlight turns off at 2/10 brightness.

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

All the contributing information is [https://git.sr.ht/~mil/sxmo-docs/tree/master/CONTRIBUTING.md here].

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

openSUSE running on the PinePhone

* ''' Download location '''
openSUSE images can be found [http://images.alefnode.com/ here].

Nightly images [http://images.alefnode.com/nightly/ here].

CI/CD for nightly images [https://jenkins.alefnode.com/job/public/job/slemos-imagebuilder/ here].

* ''' username/password'''
pine/1234

* ''' What works, what does not work '''
You can find all information about the progress of the project [https://gitlab.com/slem.os/slem.os/-/blob/master/CHANGELOG.md here].

== AVMultiPhone ==

AVMultimedia linux running on the PinePhone

* ''' Download location '''

https://de.osdn.net/projects/avmultimedia/releases/

* ''' username/password'''
archivista/1234

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

All linux applications (Firefox, LibreOffice, Gimp, Inkscape, Kodi etc.). Phone calls and SMS (text messages), primitiv acces to camera (1280x720).

AVMultiPhone offers a classic Linux desktop (Mate) on the PinePhone. The basis is PostmarketOS. In contrast to other PinePhone distributions, AVMultiPhone offers real Linux feeling without sacrificing the functionality of a smartphone.

== GloDroid ==

A fully open source port of Android to the PinePhone

* ''' Download location '''

https://github.com/GloDroid/glodroid_manifest/releases

* ''' username/password'''
* ''' What works, what does not work '''
WiFi, screen dimming, touchscreen and charging all work. No Bluetooth support yet.

= Factory Test OS =
On the BraveHeart model there was a pmOS based basic factory test OS pre-installed on the eMMC. Martijn Braam from pmOS has improved the functionality of the image considerably.

Since the 20200501 version it is able to test all the hardware. It also includes functionality to install a new OS to the eMMC when using with an test image that includes that OS image. The downloadable image just does the hardware tests.

Do not flash eMMC to test your device, just copy it to mSD and test from there. New versions are distributed as part of the pmOS distribution.

Links:
* [https://images.postmarketos.org/pinephone/ Software Images] (download the latest one that is marked pine-pinephone-YYYYMMDD-factorytestX.img.xz)
* [https://gitlab.com/MartijnBraam/factorytest Git repo]
* [https://gitlab.com/MartijnBraam/factorytest/-/blob/master/README.rst Documentation]

= Installing other ARM64 distributions =
'''Warning:''' Distributions not on this page may not even boot after you follow this section. In the best case, they will be barely usable. This is more for fun, or if you would like to port a new distribution to the PinePhone.

'''Note:''' This section uses megi's kernel releases, and not the official ones from PINE64. While it is possible to use the official (and in the future, mainline) kernel, megi provides binary releases, which makes it very easy.

If you would like to see specific commands for how to complete these steps, see https://github.com/nikhiljha/pp-fedora-sdsetup (an example for Fedora) or https://xnux.eu/howtos/install-arch-linux-arm.html (an example for Arch Linux).

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

= Other Resources =
Community
* [[Main_Page#Community_and_Support|Links to the community services]]

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

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

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

[[Category:PinePhone]]

PinePhone v1.1 - Braveheart

2020-09-02T10:14:58Z

Jbit: Add to PinePhone category

The PinePhone v1.1 "Braveheart" is a hardware revision of the PinePhone that shipped in January 2020.

This page contains resources which are exclusive to the 1.1 revision of the PinePhone. For other revisions, or for resources related to all PinePhone revisions, see [[PinePhone]].

== Schematic ==

[http://files.pine64.org/doc/PinePhone/PinePhone_Schematic_v1.1_20191031.pdf Hardware schematic]

== Changes from 1.0 ==

Braveheart is slightly different from the 1.0 revision of the Pinephone. These differences should not require creating different images.

# Added CPU shielding and cover plate
# Swap PC3 to FLASH_EN and PD24 to FLASH_TRIGOUT, where previously they were reversed
# Add pulldown resistor on PD24 (FLASH_TRIGOUT) so the flash LED does not light on boot
# Connect WiFi enable to VD33
# Set the EG25G's PWRKEY on by default (see resistor R1526)
# Add R630 resistor location, populate with 0K by default. Allows adjusting to different battery thermistors in case this is not possible in software.
# Add voltage shift to Pogo pins I2C-CLK, I2C-DATA, and INT. The Pogo Pin specified voltage is 3.3v while the A64's I2C is 2.8V.
# A64 LINEOUTN is disconnected from the speaker amplifier, making the speaker output single-ended instead of differential

== DIY Hardware fixes ==
Some of the known issues can be fixed with more or less involved hardware modifications:
* USB-C CC pins are pulled to GND: [[PinePhone_1.2_VCONN_Hardware_Fix| Removing small switches]] can make USB OTG work.A proper fix is to replace those with another component.

== Known issues ==

This section lists problems known on the 1.1 revision hardware, possibly because they carried over from the 1.0 revision. Most of these were fixed in the 1.2 revision mainboard.

=== Need a way to distinguish v1.1 from v1.2 from U-Boot SPL ===

''Resolved in v1.2 by PL6 being connected directly to the modem, instead of through the level shifter, so it is pulled low at boot.''

To load the correct device tree, there needs to be some hardware feature that can distinguish the two versions. This can be as simple as an I/O pin that is pulled differently by default between v1.1 and v1.2. Reading the pin in SPL will tell us which device tree to use.

=== WiFi module cannot be disabled or reset in software ===

''Resolved in v1.2 by connecting PL2 to the WiFi module's WiFi reset pin.''

Neither the <tt>WL-REG-ON</tt> nor <tt>WL-PMU-EN</tt> signal is connected to anything, and the WiFi module's <tt>CHIP_EN</tt> pin is connected (through the killswitch) to a regulator that cannot be turned off (easily, if at all). So while the killswitch works, there's no way to disable the WiFi module in software. This will lead to excess power consumption when WiFi is turned off.

=== Magnetometer's IRQ signal is routed to the wrong pin ===

''Resolved in v1.2 by connecting the magnetometer's <tt>DRDY</tt> pin to PB1.''

It needs to go to DRDY, not to INT. The kernel driver expects the trigger events to be fired when DRDY changes, and does not even configure the interrupts to be enabled on the INT pin.

Software workaround is to disable magnetometer interrupt in the devicetree, and use a hrtimer or some other software triggering mechanism for IIO devices.

=== Speaker output could be differential ===

''Resolved in v1.2 by connecting <tt>LINEOUTP</tt> to the speaker amplifier's <tt>INP</tt> input.''

Using a differential connection to the speaker amplifier would significantly lower the noise floor of the speaker, and would allow doubling the max volume.

=== Modem AP_READY signal is not connected ===

''Resolved in v1.2 by connecting PH7 to <tt>AP_READY</tt> instead of <tt>WAKEUP_IN</tt>.''

The [https://www.quectel.com/UploadImage/Downlad/Quectel_EC2x&EG9x_Power_Management_Application_Note_V1.0.pdf modem's power management documentation] describes how to implement modem power saving. The modem can wake up the host using either the Ring Indicator pin (section 4.5) or USB remote wakeup (section 4.3). Either way, it suggests the <tt>AP_READY</tt> signal needs to be connected. The modem needs that signal to know when the host is asleep (and the modem needs to queue its messages and wake it up), and when the host has finished waking up (and is ready to receive the queued messages).

=== Modem RI signal routing prevents wakeup ===

''Resolved in v1.2 by connecting <tt>RI</tt> to PL6.''

The EG25G's Ring Indicator (RI) pin is currently routed to GPIO pin PB2. The A64 needs to receive interrupts via this pin while suspended, so the modem can wake up the A64 (for incoming calls and text messages). The only GPIO bank that can receive interrupts while the A64 is suspended is Port L (on <tt>R_PIO</tt>).

'''Note''': Port L is powered by VCC-PL, and runs at 1v8, so it should ''not'' have a level shift to DCDC1/3v3 between the AP and the modem, like DTR currently has. The way DTR is currently connected is a bug.

=== Excess power usage while driving VBUS ===

''Resolved in v1.2 by connecting PL9 and <tt>VBUS_CTRL</tt> on the ANX7688 to <tt>N_VBUSEN</tt> on the PMIC.''

The <tt>N_VBUSEN/DRIVEVBUS</tt> input on the AXP803 PMIC, labeled <tt>USB-DRVVBUS</tt> on the schematic, is not connected to the USB OTG boost regulator enable input, because R1300 is marked "NC". This prevents the AXP803 from automatically detecting when the USB port is being powered from the battery. Thus, the PMIC continues to draw power from the USB port, and this doubles the drain on the battery (since the whole phone is being powered by the USB OTG boost regulator). This could be fixed by populating R1300.

The ANX7688's VBUS_CTRL pin should also be connected to the DRVVBUS signal to perform role switching in hardware without needing OS interaction. In that case PD6 becomes an input. Otherwise, we would need to hook up the VBUS status change interrupt from the ANX7688 to control the USB PHY driver.

=== ANX7688 power supply situation is problematic ===

''Resolved in v1.2 by powering always-on 3v3 from DCDC1, video-related 3v3 from DLDO1, 1v8 from GPIO-LDO1, and 1v0 controlled by PD11.''

ANX7688 has four power inputs: 3v3, 1v8, 1v0, and HDMI_VT (which is also 3v3).
* The main 3v3 input, to AVDD33, should always be on according to the datasheet. For this reason, it should be connected to an always-on regulator, such as DCDC1, so DLDO1 can be turned off when the screen is off. It has extremely low power consumption.
* HDMI_VT is only needed during video transmission, and should remain connected to DLDO1.
* The only other 3v3 consumer is the VCONN_EN pull-ups. These could be pulled to GPIO1-LDO (1.8V) instead; the pins are open drain.
* The DVDD18 input should also always be on according to the datasheet. It has extremely low power consumption. I recommend connecting it and the PL11 pull-up to VCC-PL, so GPIO1-LDO can be turned off.
* The remaining 1v8 inputs only need to be enabled when a USB cable is connected (supply or OTG). They are connected to their own regulator (GPIO1-LDO), so that is fine. (Note that the next issue suggests removing the pull-ups for POWER_EN and RESET_N.)
* The 1v0 input is only needed when a USB cable is connected (supply or OTG). It is currently controlled by DLDO1, but I think controlling it with GPIO1-LDO would be an improvement. That way DLDO1 only needs to be enabled when transmitting video, not always when a cable is connected.

=== Modem PWR_KEY signal resistor population ===

''Resolved in v1.2 by separating the modem <tt>PWRKEY</tt> (PB3) and <tt>STATUS</tt> (PH9) signals.''

On the dev phone (1.0) this signal was connected to PB3. This allows for turning on/off the modem via GPIO from a kernel driver. If proper power down is to be implemented in the kernel for the modem, to allow safe shutdown of the modem before turning off the 4g-pwr-bat, kernel has to be able to signal to the modem to shut down and wait 30s. This is not possible on braveheart. Without this signal, kernel can't do anything to shut down the modem, and would have to rely on userspace to properly manage the modem power up/down sequence. Relying on userspace risks users shutting down the modem without proper wait time of 30s, risking modem damage (flash data corruption).

It would be nice to also have access to the STATUS signal from the modem, so that the driver can detect whether the modem is on or off (userspace might have turned modem off already via AT commands). Given that PWR_KEY pulse will either turn the modem on or off, based on the current status, it's necessary to know the current status before sending the pulse.

There's a STATUS signal routed to PWR_KEY on BraveHeart, that keeps the PWRKEY deasserted when the modem is on and it's not possible to pull it up from PB3, even if R1516 would be optionally mounted.

So after powerup you can't change PWR_KEY signal anymore from PB3 even if R1516 is mounted, and it's not possible to turn off the modem via PB3.

=== Modem has access to sensors on I2C1 ===

''Resolved in v1.2 by disconnecting the modem's I2C port.''

The modem is a master on the I2C1 bus. A malicious firmware on the modem would be able to read the phone's gravity/light/proximity sensors and prevent the main Linux OS from reading them. The [https://www.quectel.com/UploadImage/Downlad/Quectel_WCDMA&LTE_Audio_Design_Note_V1.1.pdf modem's audio design note] describes the <tt>AT+QIIC</tt> command which can be used to read and write registers on I2C devices.

According to the modem documentation, its I2C interface is only used for direct connection to a standalone audio codec. On the PinePhone, since the modem's audio is routed through the A64 SoC, the modem's I2C interface has no legitimate use.

The modem's I2C interface should be left floating. U1503 pins A1, A2, B1, and B2 can be disconnected, and R1527/R1528 can be removed.

=== Allow access the modem debug UART ===

''Not resolved in v1.2 -- would have required moving several other GPIOs.''

Instead of the modem's I2C pins, which aren't very useful (see above), it would be great to have access to the modem's debug UART, for debugging/updating the modem. This could be on UART3 (PD0-PD1, no flow control), while the main modem UART is on UART4 (PD2-PD5, with flow control).

=== Modem UART flow control is broken ===

''Not resolved in v1.2 -- assumption is that USB will be used for high-bandwidth modem I/O.''

BB-TX and BB-RX are connected to UART3 (PD0/PD1). BB-RTS and BB-CTS are connected to UART4 (PD4/PD5). To use hardware flow control, TX/RX would need to be connected to UART4, swapping PD0/PD1 with the motor control and rear camera reset GPIOs at PD2/PD3. This would need a device tree change.

Hardware flow control can be disabled with the <tt>AT+IFC</tt> command, and USB can also be used for commands instead of the UART. So the impact of this problem is unclear.

=== ANX7688 power/reset control pulled the wrong way ===

''Not resolved in v1.2 -- this has minimal impact.''

Both <tt>ANX_POWER_EN</tt> and <tt>ANX_RESET_N</tt> have pull-ups when they should not. Both signals need to be pulled low by default. They only need to be brought high (turning the chip on) when a USB cable is attached; and they should only be brought high after the 1v8 and 1v0 regulators are turned on. <tt>ANX_POWER_EN</tt> needs an external pull-down. <tt>ANX_RESET_N</tt> has an internal pull-down.

=== VCONN_EN signals are possibly inverted ===

''Further investigation determined that the hardware is correct as-is in v1.1, so no change was made.''

I don't have a datasheet for the AW3512 chips, but I assume the enable input is active-high. VCONN1_EN and VCONN2_EN are open-drain. When they are open, it appears that VCONN should be enabled. But right now, when they are open, VCONN is disabled, because the AW3512 EN pin will be pulled low by the FET.

=== Cameras have the same default I2C address ===

''Resolved in software by reprogramming the one of the cameras' I2C addresses at boot.''

This makes it hard to keep both of them powered at the same time and switch quickly between them (on the per-frame basis) without having to re-initialize the sensors on each switch, which takes some time.

=== USB-C CC pins are pulled to the GND by AW3512 (VCONN switches) when VCONN is off ===

'''This issue is also present on the PinePhone 1.2 (CE) version.''' It was fixed with revision 1.2a. [[PinePhone_1.2_VCONN_Hardware_Fix|See the workaround]].

This issue prevents cable plug/orientation detection and USB-PD communication. ANX always sees cable as plugged even if none is plugged. There's no SW workaround for automatic detection of cable plug or power role.

In SW this can only be worked around by manual selection of PinePhone's data and power role by the user.

HW workaround is desoldering U1305 and U1309 switches (BGA like packages). This will void the VCONN control, but it will release the CC pins for their proper connection detection and negotiation roles. I confirmed that desoldering fixes the issue. (Howto: https://megous.com/dl/tmp/pp-usbc-fix.jpg)

HW fix is to replace AW3512 with a variant of the chip that preserves the EN signal polarity and that doesn't have the "quick discharge function" that ties the output to the GND via a 75 Ohm resistor when the switch is OFF. mozzwald used NCP334FCT2G as a replacement.

=== Pogo Pins supply 5v0, not 3v3 ===

''No hardware change suggested, to maintain accessory compatibility.''

This is possibly just a documentation issue. [https://wiki.pine64.org/index.php/PinePhone#Pogo_Pins The wiki claims] they provide a "3.3v power source", and on this page, "The Pogo Pin specified voltage is 3.3v". But according to the schematic, they are connected to <tt>USB-5V</tt>, the output of the 5V boost regulator.

[[Category:PinePhone]]

PinePhone v1.0 - Dev

2020-09-02T10:14:56Z

Jbit: Add to PinePhone category

The PinePhone v1.0 is the developer hardware revision of the PinePhone.

This page contains resources which are exclusive to the 1.0 revision of the PinePhone. For other revisions, or for resources related to all PinePhone revisions, see [[PinePhone]].

== Schematic ==
* [https://wiki.pine64.org/images/3/30/PinePhone_Schematic_v1.0_20190708.pdf PinePhone v1.0 Schematic 20190708]

* [https://wiki.pine64.org/images/4/41/PinePhone_mainboard_v1.0_component_placement_top.pdf Pinephone V1.0 Mainboard Top Layer Silkscreen]
* [https://wiki.pine64.org/images/0/09/PinePhone_mainboard_v1.0_component_placement_bottom.pdf Pinephone V1.0 Mainboard Bottom Layer Silkscreen]
* [https://wiki.pine64.org/images/d/df/PinePhone_daughterboard_v1.0_component_placement_top.pdf Pinephone V1.0 Daughterboard Top Layer Silkscreen]
* [https://wiki.pine64.org/images/9/9f/PinePhone_daughterboard_v1.0_component_placement_bottom.pdf Pinephone V1.0 Daughterboard Bottom Layer Silkscreen]

== Changes from Don't Be Evil ==

== Known issues ==

See [[PinePhone_v1.1_-_Braveheart#Known_issues|the known issues with v1.1 (Braveheart)]], which are all carried forward from v1.0.

[[Category:PinePhone]]

PinePhone Press

2020-09-02T10:11:33Z

Jbit: Add to PinePhone category

Vector images and photos you can freely use for projects and press inquiries. Attribute the author if attribution is required via the license (such as with CC BY).

== Vector ==
[[File:PinePhoneSides.svg|none|thumb|Author: Jedi2light, License: CC BY 4.0]]

[[File:PinePhone_Vector.svg|none|thumb|Author: Funeral, License: CC0]]

<gallery>
File:Pinephone drawing1.svg|Author: Funeral, License: CC0
File:Pinephone drawing2.svg|Author: Funeral, License: CC0
File:Pinephone drawing3.svg|Author: Funeral, License: CC0
</gallery>

<gallery>
File:Pinephone drawing1 manual.svg|Author: Funeral, License: CC0
File:Pinephone drawing2 manual.svg|Author: Funeral, License: CC0
File:Pinephone drawing3 manual.svg|Author: Funeral, License: CC0
</gallery>

== 3D models ==
* https://www.thingiverse.com/thing:4520124

== Photos ==

[[Category:PinePhone]]

PinePhone Accessibility

2020-09-02T10:10:03Z

Jbit: Add to PinePhone category

Although most accessibility support is implemented in software, the underlying hardware is still relevant.
This page discusses some issues and options.
For more general information, see the [[Accessibility]] page.

= Input =

== Braille ==

Various portable devices, such as Apple's iPhone, support braille input.
This uses multi-touch capability on the device's capacitative touch screen.
The gating factors for this input mode are the dimensions of the screen
and the number of contact points that can be distinguished.

The PinePhone screen has 1440 × 720 pixel resolution and measures 5.95" diagonally.
Assuming that the pixels are square, the screen dimensions should be about 2.68" by 5.37".
This should provide plenty of room for four fingertips on each of the long sides.
Indeed, there is a bit of space left over for control functions, etc.

== Keyboard ==

The PinePhone can support either Bluetooth or USB keyboards.
So, a device such as the
[https://www.jellycomb.com/Foldable-Bluetooth-Keyboard-B003-p798959.html Jelly Comb Foldable Bluetooth Keyboard B003]
might be a reasonable input device.

== Speech ==

The PinePhone should be able to accept speech input using either Bluetooth or its built-in microphone.
According to
[https://www.seeedstudio.com/blog/2020/01/23/offline-speech-recognition-on-raspberry-pi-4-with-respeaker this page],
Mozilla's DeepSpeech ASR (automatic speech recognition) engine works pretty well on a Raspberry Pi 4,
using only a single core.
Assuming that the PinePhone's more limited (2 or 3 GB) RAM isn't a constraint,
the phone should be able to produce similar results.

= Output =

== Speech ==

The PinePhone's processor should have plenty of capacity to generate clear speech.
This can be output using either the 3.5 mm audio jack or a Bluetooth connection.

[[Category:PinePhone]]

PinePhone Modding

2020-09-02T10:09:00Z

Jbit: Add to PinePhone category

There are a number of options to hardware mod the PinePhone.

Some are upgrades to fix issues that were not done optimally in the production of that version of the electronics, and some are to add options that were not part of the phone spec.

== PRO TIP ==
Make pictures of the situation before and after your mods, so you can comare the change, and don't need to disassemble the device to get the right pics later.

==Device Specific Mods ==
There are a nr of upgrades possible for the different versions of the PinePhone.

=== "Don't be evil" ===
*

=== BraveHeart ===
*PMIC mod - Stops the battery drain from a shutdown phone, draining the battery to 0V.
*VCONN mod - Unblocks the USB-C power negotiation rail, so convergence functions are unlocked.

=== UBPorts Community edition ===
*VCONN mod - Unblocks the USB-C power negotiation rail, so convergence functions are unlocked.

There are also a number of mods that can be done adding more functions by adding extra hardware to the pogo pins, and a number of options to change the screen protector.

At this moment there are not many pogo addons, and most are just connector boards. Likely the makers will add links to these projects to this page. Pine is looking into adding a N900 style keyboard attached to these pins.

== PMIC mod ==
[[PinePhone_1.1_VBUS_power_usage_Hardware_Fix]]
The original description of this fix is given on megi's pager here https://xnux.eu/devices/pp-pmic-fix.jpg
== VCONN mod ==
The original description of this fix is given on megi's pager here https://xnux.eu/devices/pp-usbc-fix.jpg
There is a discussion on the merits of the different ways to do the fix

=== VCONN mod, Removal only ===
[[PinePhone_1.2_VCONN_Hardware_Fix]]

There are now a few documented ways,
*Removal only, the tweezer "stupid" way: https://www.youtube.com/watch?v=j3jc7Mvn9Eo
*Removal only, the soldering iron "less stupid" way: https://www.youtube.com/watch?v=ZqOb45N2sMc
There are hopefully videos coming doing it the proper way, and so they can be linked here.

After this the firmware for the power negotiation chip needs to be upgraded, this can be done by running the factory test image, version http://images.postmarketos.org/pinephone/pine64-pinephone-20200724-factorytest55.img.xz or higher. This will do the firmware flashing and respond with a message indicating the state. After this the phone is ready for its added functions.
ANX states:
*No CC Fix - Fix not applied
*No USB Cable - No USBC connection, cannot upgrade firmware
*OK - Firmware Applied, you are all set

=== VCONN mod, Replacement ===
Using 2x NCP334FCT2G you could do the full fix, making VCONN powered devices able to negotiate power. IT needs the parts to be removed first without damaging the pads, and then replacing the parts.

==Laser cut parts==
Mcyam2 has created some laser cut templates for the rear facing components here:

https://imgur.com/a/LAUatOa

https://anonfiles.com/L0BeK5L5oe/ppsvg-backplate-CUTOUT_svg

Originally based on silver's work on a 3d printed rear frame

==3D Printed parts==

[[Silver 3d printed a folding keyboard mostly]]

Silver has created a 3d printable rear frame for pinephone, and used it to create a folding keyboard design (work in progress).

https://ibb.co/album/ScDttH

https://www.youmagine.com/designs/pinephone-folding-keyboard-mockup

[[Category:PinePhone]]

PinePhone v1.2

2020-09-02T10:08:09Z

Jbit: Add to PinePhone category

The PinePhone v1.2 is a hardware revision of the PinePhone that shipped in 2020.

This page contains information and resources which are specific to the v1.2 revision of the PinePhone. For other revisions or for resources related to all PinePhone revisions, see [[PinePhone]].

== Schematics ==

* [http://files.pine64.org/doc/PinePhone/PinePhone%20v1.2%20Released%20Schematic.pdf Hardware schematic v1.2] (2020-03-10, for Community Edition: UBports)
* [http://files.pine64.org/doc/PinePhone/PinePhone%20v1.2a%20Released%20Schematic.pdf Hardware schematic v1.2a] (2020-06-08, for Community Edition: postmarketOS)

== Changes from v1.1 ==

The v1.2 mainboard revision changes the routing of several GPIOs to fix bugs and to improve power management. Therefore, it needs an updated device tree. The state of PL6 at boot can be used to distinguish between v1.1 (it can be pulled high) and v1.2 (it will remain low).

# The WiFi module's <tt>CHIP_EN</tt> input (connected to the kill switch) is now pulled down, so the WiFi will turn off reliably when the switch is off.
# PL2 is now connected to the WiFi module's reset pin, allowing the WiFi to be turned off or reset in software.
# The magnetometer's <tt>DRDY</tt> pin is now connected to PB1, allowing interrupt-driven periodic sensor readings.
# <tt>LINEOUTP</tt> is again connected to the speaker amplifier's INP input (like in v1.0), increasing the SNR of the rear speaker.
# PH7 is now connected to the modem's <tt>AP_READY</tt> input (instead of <tt>WAKEUP_IN</tt>), allowing the modem to buffer URCs (interrupts) while the phone is asleep.
# The modem's <tt>RI</tt> output and <tt>DTR</tt> input had their GPIOs swapped between PL6 and PB2, so the <tt>RI</tt> signal can be detected without powering the main pin controller.
# Both PL9 and <tt>VBUS_CTRL</tt> (from the ANX7688) are now connected to <tt>N_VBUSEN</tt> on the PMIC. This causes the PMIC to automatically stop drawing power from the USB port when supplying power to a USB-OTG peripheral. It also allows the ANX7688 to automatically control the direction of current flowing through the USB port.
# As part of the previous change, the ANX7688's reset input was moved to PD6; this pin previously controlled the USB OTG power.
# Some of the regulators supplying the ANX7688 were rearranged, to reduce power consumption when the USB port is not connected and not being used to transmit video.
# As part of the previous change, PD11 now controls the ANX7688's 1v0 digital power domain.
# The modem's <tt>STATUS</tt> output is now connected to PH9, allowing the modem on/off state to be visible in software (note: this only works while the modem is powered). Since it is no longer connected to PB3, reading <tt>STATUS</tt> no longer turns the modem on.
# The modem no longer has access to the I2C bus containing the sensors.
# <tt>HBIAS</tt> is now connected to the headphone jack.

== Quirks ==

=== Backlight ===

Backlight LED current regulation depends on gpio0-ldo voltage stability due to feedback voltage from current sensing resistor being modified via SoC's PWM pin and pullup resistor to gpio0-ldo. gpio0-ldo also powers the CTP controller and light/proximity sensor, among other things. When backlight brightness is very low and the CTP controller actively communicates on the I2C bus the backlight blinks heavily. It's not a very good idea to tie boost converter's current regulating feedback circuit to the potential source of noise, especially since the noise will have much larger effect when the backlight LED current is low. It's possible this can be mitigated if C1110 can be raised to 22-47uF range, or by changing the resistor values in the feedback circuit.

PWM duty cycle for the lowest brightness of the backlight is also not very predictable, varying from 7-20% (tested with a small sample size of 2 devices). Therefore it's not possible to come up with a single device tree brightness settings that will work for everyone, requiring per-device calibration.

On PinePhone 1.0, this was not the case, PWM signal was directly fed to the CE pin of the regulator, and lowest brightness setting seems more stable. On the other hand, the lowest achievable brightness was brighter than on 1.1+.

=== USB ===

[[PinePhone_v1.1_-_Braveheart#USB-C_CC_pins_are_pulled_to_the_GND_by_AW3512_.28VCONN_switches.29_when_VCONN_is_off|USB-C CC pin issues from BraveHeart]] are still present in the original 1.2 revision boards, since they were discovered after production of 1.2. Revision 1.2a fixes these.

[[Category:PinePhone]]

PinePhone FAQ

2020-09-02T10:03:01Z

Jbit: Add to PinePhone category

A list of frequently asked question.

== Hardware ==

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

==== Is the Community Edition the latest revision? ====
Yes, it is! The Community Edition is the latest version of the PinePhone, featuring the mainboard numbers 1.2 and 1.2a. It's predecessor was the BraveHeart Edition intended for tinkerers and developers, which had the version number 1.1. For more details about the topic see [[PinePhone#Hardware Revisions]].

==== Will there be other Community Editions? ====
Three Community Editions have been announced: [https://www.pine64.org/2020/04/02/pinephone-ubports-community-edition-pre-orders-now-open/ UBports], [https://www.pine64.org/2020/06/15/june-update-postmarketos-ce-pinephone-shipping-pine64-cluster/ PostmarketOS] and [https://www.pine64.org/2020/08/31/pinephone-manjaro-community-edition/ Manjaro]. Other Community Editions might follow, this however depends on multiple factors, including if the software is ready to be released on the consumer market.

==== In simple terms, what are the differences between BraveHeart and the new Community Edition? ====
The BraveHeart Edition was the revision intended for developers and tinkerers, while the Community Edition is the latest revision with an updated mainboard based on feedback for the BraveHeart Edition, see [[PinePhone#Hardware Revisions]].

==== Will there be a newer revision after the Community Edition? ====
That's unlikely for the near future (unless major issues are found in the latest revision). The Community Edition got certificates such as CE, repeating the certification process due to changes in the hardware design is very expensive, so the Community Edition(s) are viewed as the final revision.

The Community Edition (and parts for it) will be produced and sold for at least 5 years.

There are plans for a newer revision with updated hardware, which is however multiple years away (3-5 years).

==== Will there be hardware differences between the Community Editions? ====
Ideally, only the logo on the back panel will differ. However there are minor differences between the Community Edition:
* The UBPorts Community Edition has hardware [https://wiki.pine64.org/index.php?title=PinePhone_1.2_VCONN_Hardware_Fix USB-C issues] that are fixed in later editions.
* The PostmarketOS and Manjaro Community Editions have a 3GB/32GB version available in the Convergence Package.

=== Sound ===
=== Modem ===

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

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

=== Battery ===

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

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

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

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

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

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

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

=== Memory ===

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

== Software ==

=== Installation ===

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

See [[PinePhone Installation Instructions]].

=== Updating ===

Read the [[PinePhone Updating Instructions]].

=== Booting ===

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

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

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

There is a project by Danct12 which allows the user to select different OSes at boot, the software is currently work-in-progress: https://github.com/dreemurrs-embedded/Pineloader.

=== Ubuntu Touch ===

==== Can I install a different OS on the Ubports Community Edition? ====

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

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

Run "sudo start ssh" to get a one-time start or edit /etc/init/ssh.override and remove the manual line to make it auto-start.

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

See https://gitlab.com/ubports/community-ports/pinephone#what-works-what-doesnt.

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

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

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

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

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

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

You may need to repeat these steps more than once.

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

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

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

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

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

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

==== I can't update or install packages through apt ====

<code>W: Problem unlinking the file /var/lib/apt/lists/partial/ports.ubuntu.com_ubuntu-ports_dists_xenial_InRelease - PrepareFiles (30: Read-only file system)</code>

Remount the root filesystem as read-write:

<code> phablet@ubuntu-phablet:~$ sudo mount -o remount,rw / </code>

Now you should be able to run updates and install new packages

=== Android ===

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

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

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

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

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

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

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

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

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

== Accessories ==

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

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

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

=== Batteries ===
==== I'm outside the US and want a replacement battery, which one should I buy? ====

Currently the PinePhone battery is known to be compatible with replacement batteries for the Samsung J700, specifically models "EB-BJ700BBC", "EB-BJ700BBE" and maybe "EB-BJ700CBE" are compatible. There is [https://forum.pine64.org/showthread.php?tid=8563&pid=55053#pid55053 a report] that model "EB-BJ700CBE" might be incompatible so it's probably safer to go with either the BBC or BBE models.

=== External hardware ===

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

Yes, currently there is a [https://forum.pine64.org/showthread.php?tid=8537&pid=55396#pid55396 keyboard case], [https://www.pine64.org/2020/05/15/may-update-pinetab-pre-orders-pinephone-qi-charging-more/ Qi wireless charging] and a [https://www.pine64.org/2020/05/15/may-update-pinetab-pre-orders-pinephone-qi-charging-more/ 5000mAh battery case] planned, these are the products Pine64 will make and sell for sure. Pine is also exploring other possibilities like a keyboard case in the style of a Nokia N900, an external battery charger and a gamepad, but these aren't really decided on yet.

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

See [[PinePhone Hardware Accessory Compatibility]].

[[Category:PinePhone]]

PinePhone FAQ

2020-09-02T07:17:19Z

Jbit: /* Hardware */ Update FAQ to include information about the new community editions

PinePhone

2020-09-02T06:53:44Z

Jbit: /* Specifications */ Add convergence specs (3GB RAM + 32GB eMMC)

PinePhone

2020-09-02T06:49:03Z

Jbit: /* Components */ (Formatting fix, oops)

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, the first Community Edition started to ship in June 2020. The phone 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]]

[[File:PinePhoneSides.svg|400px|thumb|right|Backward and front of PinePhone UBPorts Edition]]

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: G25-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 
'''Killswitches:''' Modem, WiFi & Bluetooth, Microphone, Cameras 
'''Battery:''' Lithium-ion, rated capacity 2800mAh (10.64Wh), typical capacity 3000mAh (11.40Wh) (nominally replaceable with any Samsung J7 form-factor battery) 
'''I/O:''' USB Type-C, USB Host, DisplayPort Alternate Mode output, 15W 5V 3A Quick Charge, follows USB PD specification

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

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

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

=== USB-C connector ===

The USB-C can be used to power the device, and offers USB2 host and OTG possibilities, and also can make use of the USB-C capability to integrate HDMI signals. Some USB-C hubs are available that offer power throughput, USB connection, HDMI port and Ethernet connection. 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, an IR blaster, a keyboard extension or extended battery case. The pogo pins provide access to an interrupt line, power input to charge the battery, power source and an I2C interface.

[[File:Pinephone pogo.png|none|400px]]

{| class="wikitable"
| Interrupt
| SDA
| SCL
|-
| 5V / VBUS
| VBAT
| GND
|}

The VBUS pin is powered by USB and is 5V. The second power pin is VBAT, which connects to the battery voltage. The I2C and interrupt lines have pull-ups on the phone side. The I2C lines are pulled up to 3V3 by the phone.

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

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

=== Serial console ===

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

The UART is 115200n8.

The pinout for the serial connector is:

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

[[File:PinePhone_Serial_Cable.png|none|400px]]

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

== Killswitch configuration ==

[[File:PinePhone 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.

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

== Battery ==

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

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.
* The extended life aftermarket BBU do fit, however, somewhat firmly.
* 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 phone 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 and check that the pins aren't bent. This is to protect the device from turning on during shipping.}}

If using an aftermarket battery on the CE edition phones, removing the lower tabs is not necessary as there is space supplied in the compartment.

<gallery mode="packed", heights=300px>
Image:PinePhone battery1.png|Photo of Brave Heart case from OSAKANA TARO on Twitter
Image:PinePhone battery3.jpeg|Photo of Brave Heart battery sticker from OSAKANA TARO on Twitter
</gallery>

== Modem and carrier support ==
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]].

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

=== Documents ===

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.

== 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 get mainlined and distributions ship with the updated kernel, they will also be able to run unmodified on the device.

=== Installation instructions ===

For instructions on how to install the operating systems to 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 an 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 PinePhone drive (e.g. /dev/mm..., check for the right device in dmesg, GNOME disks, or similar, and make sure it's unmounted) with your 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.7GB partition on it. To use the entire 14.7GB on the eMMC, run the following commands:

# sudo cfdisk /dev/sdX
# Change to [Resize] in the ncurses program, resize the 3.7GB partition to 14.7GB, 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

== Frequently asked questions ==

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

== PinePhone board information, schematics and certifications ==
* PinePhone mainboard schematic:
** [http://files.pine64.org/doc/PinePhone/PinePhone%20v1.2a%20Released%20Schematic.pdf PinePhone mainboard Released Schematic ver 1.2a]
** [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]
* [[PinePhone component list]]

== 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:
** [http://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf RTL8723BS/RTL8723CS specification]

* LTE module information:
** [https://www.quectel.com/UploadFile/Product/Quectel_EG25-G_LTE_Standard_Specification_V1.2.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 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]

PinePhone

2020-09-02T06:47:21Z

Jbit: /* Components */ Change modem component from EC25 to EG25, since EC25 is a different part which isn't used.

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, the first Community Edition started to ship in June 2020. The phone 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]]

[[File:PinePhoneSides.svg|400px|thumb|right|Backward and front of PinePhone UBPorts Edition]]

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: G25-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 
'''Killswitches:''' Modem, WiFi & Bluetooth, Microphone, Cameras 
'''Battery:''' Lithium-ion, rated capacity 2800mAh (10.64Wh), typical capacity 3000mAh (11.40Wh) (nominally replaceable with any Samsung J7 form-factor battery) 
'''I/O:''' USB Type-C, USB Host, DisplayPort Alternate Mode output, 15W 5V 3A Quick Charge, follows USB PD specification

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

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

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

=== USB-C connector ===

The USB-C can be used to power the device, and offers USB2 host and OTG possibilities, and also can make use of the USB-C capability to integrate HDMI signals. Some USB-C hubs are available that offer power throughput, USB connection, HDMI port and Ethernet connection. 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, an IR blaster, a keyboard extension or extended battery case. The pogo pins provide access to an interrupt line, power input to charge the battery, power source and an I2C interface.

[[File:Pinephone pogo.png|none|400px]]

{| class="wikitable"
| Interrupt
| SDA
| SCL
|-
| 5V / VBUS
| VBAT
| GND
|}

The VBUS pin is powered by USB and is 5V. The second power pin is VBAT, which connects to the battery voltage. The I2C and interrupt lines have pull-ups on the phone side. The I2C lines are pulled up to 3V3 by the phone.

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

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

=== Serial console ===

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

The UART is 115200n8.

The pinout for the serial connector is:

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

[[File:PinePhone_Serial_Cable.png|none|400px]]

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

== Killswitch configuration ==

[[File:PinePhone 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.

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

== Battery ==

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

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.
* The extended life aftermarket BBU do fit, however, somewhat firmly.
* 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 phone 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 and check that the pins aren't bent. This is to protect the device from turning on during shipping.}}

If using an aftermarket battery on the CE edition phones, removing the lower tabs is not necessary as there is space supplied in the compartment.

<gallery mode="packed", heights=300px>
Image:PinePhone battery1.png|Photo of Brave Heart case from OSAKANA TARO on Twitter
Image:PinePhone battery3.jpeg|Photo of Brave Heart battery sticker from OSAKANA TARO on Twitter
</gallery>

== Modem and carrier support ==
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]].

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

=== Documents ===

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.

== 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 get mainlined and distributions ship with the updated kernel, they will also be able to run unmodified on the device.

=== Installation instructions ===

For instructions on how to install the operating systems to 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 an 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 PinePhone drive (e.g. /dev/mm..., check for the right device in dmesg, GNOME disks, or similar, and make sure it's unmounted) with your 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.7GB partition on it. To use the entire 14.7GB on the eMMC, run the following commands:

# sudo cfdisk /dev/sdX
# Change to [Resize] in the ncurses program, resize the 3.7GB partition to 14.7GB, 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

== Frequently asked questions ==

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

== PinePhone board information, schematics and certifications ==
* PinePhone mainboard schematic:
** [http://files.pine64.org/doc/PinePhone/PinePhone%20v1.2a%20Released%20Schematic.pdf PinePhone mainboard Released Schematic ver 1.2a]
** [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]
* [[PinePhone component list]]

== 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:
** [http://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf RTL8723BS/RTL8723CS specification]

* LTE module information:
** [https://www.quectel.com/UploadFile/Product/Quectel_EG25-G_LTE_Standard_Specification_V1.2.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 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]

PinePhone Hardware Accessory Compatibility

2020-07-16T06:01:35Z

Jbit: /* Screen protector */ Make the link prettier

PinePhone Hardware Accessory Compatibility

2020-07-16T05:59:49Z

Jbit: /* Screen protector */ Add link to official screen protector