PINE64 - User contributions [en]

ROCKPro64 Hardware compatibility

2024-06-19T12:18:42Z

Wibble: /* PCIe devices */ add Marain Clara E Dante audio interface with link to manufacturer driver page

Hardware accessory compatibility for the [[ROCKPro64]]. Please contribute to the hardware compatibility page, which lists hardware which has been tested with the rockpro64, whether successful or not.

== Hardware compatibility ==
=== PCIe devices ===
{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Kernel || Result || Notes || Tester
|-
| NIC || Intel I350 Dual Port || || Mainline-5.4 || style="background:PaleGreen;" | good || SR-IOV fails
|-
| NIC || Intel I350 Quad Port || || || ? ||
|-
| NIC || Intel X520 Dual Port || 8086:10fb || Mainline-5.6 || style="background:PaleGreen;" | good || SR-IOV fails
|-
| NIC || Intel X550-T2 Dual Port || 8086:1563 || 5.15.0-trunk-arm64 (Debian) || style="background:PaleGreen;" | good || netperf throughput in FW mode, 20 streams: between 4136-6613mb/s across use cases.
|-
| NIC || Intel 82571EB Dual Port (HP NC360T) || || Mainline-5.6 || style="background:#F99;" | crash || kernel crash on boot
|-
| NIC || Intel 82575EB Dual Port (AOC-SG-I2) || || Mainline-5.10 || style="background:#F99;" | crash || kernel crash on boot
|-
| NIC || Intel 82575/82576 || 8086:1521 || OpenWrt 21.02-rc1 ; 5.4.111-1 || style="background:PaleGreen;" | good ||opkg: kmod-igb ; [https://wiki.pine64.org/wiki/ROCKPro64_Software_Release#OpenWrt_21.02 OpenWrt 21.02-rc1] 5.4.111-1 ; ~92.8 KB ; Kernel modules for Intel(R) 82575/82576 PCI-Express Gigabit Ethernet adapters.
|-
| NIC || Aquantia 10GBps AQC107 || 1d6a:07b1 || Mainline 5.16 || style="background:PaleGreen;" | good || Works perfectly out of the box.
|-
| GPU || nVidia GTX-645 || || Mainline-5.4 || style="background:#F99;" | crash || BAR size too small, triggers PCIe error handling bug
|-
| PCIe Switch || PCIE-EUX1-04 Ver.002 || || Mainline-5.4 || style="background:PaleGreen;" | good ||
|-
| SATA Controller || ASM1062 4-Port || || Mainline-5.6 || style="background:PaleGreen;" | good || tested only with one disk attached
|-hw
| SATA Controller || ASM1062 (rev 02) 4-Port ||1d87:0100|| Ayufan-4.4.190 || style="background:PaleGreen;" | good || tested with four disks, 3 in raid 5
|-
| SATA Controller || IOCrest (Same as Syba?) SI-PEX40063 4-port, Marvell 88SE9235 chip || 1b4b:9235 || Debian unstable 5.7, 5.8 || style="background:PaleGreen;" | good || Tested with two disks. SATA errors occurred with a WD Red drive in a cheap enclosure; resolved by connecting the same drive directly to the card.
|-
| SATA Controller || Ziyituod SATA Card ASM 1062+1093 6-Port || 1b21:0625 || Mainline-4.4 (armbian) || style="background:PaleGreen;" | good || tested with 6 disks ||
|-
| SATA Controller || BEYMEI RAID 4-Port, Marvell 88SE9230 chip || 1b4b:9230 || Ayufan-5.6.0-1137 || style="background:PaleGreen;" | good || Tested with 3 disks in RAID 5. I added pci=nomsi to /boot/extlinux/extlinux.conf kernel parameters and an udev rule before the disks were recognized: ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x1b4b", ATTR{device}=="0x9230", RUN+="/bin/bash -c 'echo %k > /sys/bus/pci/drivers/ahci/bind'"
|-
| SATA Controller || BEYIMEI SATA Card 6-Port, ASM1166 chip || || 5.10.0-16-arm64 (Debian) || style="background:PaleGreen;" | good || Tested with 4 disks. Built 2 separate software RAID-1 arrays without errors. Performance seems good enough for a NAS on gigabit LAN.
|-
| SATA Controller || PCE8SAT-A02 VER006S 2 Lanes, 8-Port, ASM1166 chip Odd because chip got only 6 ports?|| 1b21:1166 || 6.1.50-current-rockchip64 Armbian 23.8.1 Bookworm || style="background:#F99;" | unstable || Tested with 3 disks in SW-RAID 5. After 10 hours of burn in test one disk dropped from system *and* RAID. Hotplug does not work. || [[User:JPT|JPT]]
|-
| SATA Controller || BEYIMEI SATA Card 2-Port, ASM1062 chip || 1b21:0612 || 5.10.0-19-arm64 (Debian) || style="background:PaleGreen;" | good || Using with 2 SSDs in a software RAID-1 array (~190MB/sec for reading and writing)
|-
| SATA Controller || QNINE 4-Port, Marvell 88SE9215 chip || || Ayufan-5.6.0-1137 || style="background:LightYellow;" | very slow || Tested with 3 disks in RAID 5. Top speeds were around 50 MiB/s but quickly dropped to below 2 MiB/s due to SATA CRC errors
|-
| SATA Controller || DELOCK 90498, JMicron Technology Corp. JMB58x AHCI SATA controller || 197b:0585 || 5.18.0-0.bpo.1-arm64 (Debian bullseye + backports) || style="background:LightYellow;" | good, but…
|| Tested with 3 disks, two in RAID1, one standalone.
u-boot-rockchip_2023.07 cannot initialize the controller to boot off it.

|| [[User:Lrissman|Lrissman?]]

[[User:ChriChri|ChriChri(u-boot)]]
|-
| Host Bus Adapter || LSI SAS 9211-4i SAS2008 chip, 4-Port SAS/SATA, PCI 2.0, 8 lanes || 1000:0070 || Ayufan-4.4.197 || style="background:PaleGreen;" | good || tested with four disks attached
|-
| Host Bus Adapter || Fujitsu SAS MEGARAID LSI 2008B2 SAS2008 chip, 8-Port SAS/SATA, PCI 2.0, 8 lanes || TODO || 6.1.50-current-rockchip64 Armbian 23.8.1 Bookworm || style="background:PaleGreen;" | TODO || needs special MicroSAS cables. Must be flashed to HBA mode? ordered, not yet received || [[User:JPT|JPT]]
|-
| USB Controller || ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller || 1b21:1242 || Mainline-5.15.0-rc5 || style="background:PaleGreen;" | good ||
|-
| DTMB Quad Tuner || TBS Technologies || TSS6514 || Mainline-5.10.21 || style="background:PaleGreen;" | good || TV -> LAN streaming server, 7W idle, 8-10W with one FHD channel streaming
|-
| DVB-T2/C Quad Tuner || TBS Technologies || TBS6205 || 5.10.0-16-arm64 (Debian) || style="background:PaleGreen;" | good || Working well with Tvheadend
|-
| DVB-S2 Dual Tuner || Digital Devices || Octopus CI S2 Pro || 6.1.42-rockchip64 (armbian) || style="background:PaleGreen;" | good || All features are working flawlessly with the latest drivers from Digital Devices
|-
| Audio interface || MARIAN GmbH || Clara E || Armbian 23.8.3, Kernel 6.1 || ? || Dante interface. [https://www.marian.de/updates/linux-support-starting-now/?lang=en Manufacturer driver page] claims it is tested on ROCKPro64/Armbian
|}

=== NVMe SSD drives ===

{| class="wikitable sortable"
!Type || Make/Model || Size || Hardware IDs || Kernel || Result || Notes || Power options Active only || Save power setting?
|-
| NVMe || Samsung 970 Evo || 500 GB || || Mainline 5.6 || style="background:PaleGreen;" | good || - || defaults || defaults
|-
| NVMe || Samsung 960 Evo || 500 GB || 144d:a804 || Mainline 5.13-rc4 || style="background:#F99;" | doesn't work || Likely due to 64/32 BAR mismatch issue on Linux 5.11+ || defaults || defaults
|}

=== USB hardware ===

{| class="wikitable sortable"

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Kernel || Result || Notes || Tester
|-
||Zigbee Bridge || Conbee II || 1cf1:0030 || 6.1.50-current-rockchip64 Armbian 23.8.1 Bookworm || style="background:PaleGreen;" | good || seems to work fine || [[User:JPT|JPT]] ([[User talk:JPT|talk]])
|}

=== USB C alternate mode DP ===

Note that only USB C alternate mode Display Port will pass video. Any HDMI, DVI or VGA port must be converted internally by the device from Display Port - or the device won't work for video.

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Kernel || Result || Notes
|-
|}

=== eMMC / SD drives ===

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Kernel || Read Speed || Write Speed ||Result || Notes
|-
|}

=== Other hardware ===

{| class="wikitable sortable"
!Type || Make/Model || Hardware IDs || Kernel || Result || Notes
|-
|}

== Limitations ==

=== Older firmware overwrites actively used memory ===

Some people get system freeze when:

* use SATA disk with ROCKPro64 PCIe card. (maybe on newer PCIe card ASM1062 vs ASM1061)
* or do read or write 4GB to the flash. (not using PCIe)

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

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

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

The latest u-boot can boot the rockpro64 without any blobs from rockchip.

Install first arm-none-eabi-gcc and aarch64-linux-gnu-gcc compiler, then run the following commands:

Prerequisite packages (Debian/Ubuntu): <code>device-tree-compiler python gcc-arm-non-eabi flex bison gcc-aarch64-linux-gnu gcc make</code>

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

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

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

=== PCIe Controller Hardware Error Handling Bug ===

There is an issue with the rk3399 pcie controller that is currently unmitigated:

* [https://lore.kernel.org/linux-pci/CAMdYzYoTwjKz4EN8PtD5pZfu3+SX+68JL+dfvmCrSnLL=K6Few@mail.gmail.com/ LKML Original Thread]
* [https://lkml.org/lkml/2020/4/6/320 LKML Additional Information]

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

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

=== Virtualization ===

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

[[Category:ROCKPro64]]

PinePhone Installation Instructions

2022-11-24T17:52:01Z

Wibble: /* Using Tow-Boot */ clarification about needing tow-boot to have been installed first

This section has generic installation instructions.

For specific installation instructions for each distribution please see the software releases pages:

* for the '''PinePhone''': [[PinePhone Software Releases]]
* for the '''PinePhone Pro''': [[PinePhone Pro Software Releases]]

== Boot priority ==

=== PinePhone Pro ===

For details regarding the boot priority on the PinePhone Pro see [[PinePhone Pro#Boot order]].

=== PinePhone ===

The PinePhone always boots from the microSD card first. It is therefore recommended to have a microSD card handy. It is '''not''' possible to lock themself out of the phone when the installation on the internal storage (the eMMC) fails, as a correctly flashed microSD card will always boot. Note: Booting from USB is not supported by the hardware, a live USB stick will not boot.

The phone will also try to boot from microSD cards, which were previously flashed with an OS and formatted later, causing the phone to fail to boot. See [[#Reuse SD card for data storage on system booting from eMMC|reuse SD card]] on how to format the microSD card properly, including wiping the residues of u-boot.

== Installation to the microSD ==

To install an image to the microSD card:

# Download your chosen image from [[PinePhone Software Releases]] for the regular '''PinePhone''' and [[PinePhone Pro Software Releases]] for the '''PinePhone Pro'''
# Extract the compressed file
# Write the image to your microSD card, see below
# Plug microSD card into phone (make sure to use the top slot, not the bottom slot)
# On the '''PinePhone Pro''': The eMMC might have to be disconnected to boot from the microSD card, see [[PinePhone Pro#Boot order]]
# Boot phone

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

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

sudo dd if='''IMAGE.img''' of=/dev/'''[DEVICE]''' bs=1M status=progress conv=fsync

{{Info|The image needs to be written to the whole device, not to partition 1. Make sure you're NOT selecting ''/dev/sda1'' or ''/dev/mmcblk0p1'' as target.}}

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

Download the ''IMAGE.xz'' and the ''IMAGE.bmap'' files, then run <code>bmaptool copy --bmap '''IMAGE.bmap''' '''IMAGE.xz''' /dev/'''[DEVICE]'''</code>. This takes around 2.5 minutes to flash a 4 Gb file.

==== Using graphical tools ====
GUI applications such as Etcher and GNOME Disks can be used to flash the microSD too.

== Installation to the eMMC ==

=== Using Tow-Boot ===

This method requires the tow-boot bootloader to be present on your boot device already, usually from an earlier OS install.

The eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.

The process of flashing an OS to the eMMC is identical to that of any other storage medium - e.g. a microSD card. You can use the dd command or a utility such as Etcher or Gnome Disks, etc.

=== Using JumpDrive ===

{{Info|This only applies to the regular '''PinePhone''', not the '''PinePhone Pro'''.}}

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

# Download and extract [https://github.com/dreemurrs-embedded/Jumpdrive/releases the Jumpdrive image]
# Flash the Jumpdrive image to a microSD card
# Boot the PinePhone from the Jumpdrive microSD 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 <code>dmesg</code>, 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 microSD card
# The process is now finished, and you can boot from eMMC

The Jumpdrive image is smaller than 50MB. You can keep an microSD card specifically for using Jumpdrive, and there are 64MB microSD cards sold cheaply that will suffice. 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!

=== From the booted microSD OS ===
# Flash an OS to the microSD card (and optionally resize the partition, see below)
# Insert microSD card and boot the phone
# Download the desired OS' image on the booted OS or transfer it to the microSD card
# Extract the image file if it is archived
# Flash the image file to eMMC using <code>dd if='''IMAGE.img''' of=/dev/'''mmcblkX''' bs=1M status=progress conv=fsync</code> where X is the number label of the eMMC (of the disk, not the partition!). Use the command <code>lsblk</code> to check your devices: typically with the current kernel the microSD card is ''/dev/mmcblk0'' and the eMMC is ''/dev/mmcblk2'' but as always with ''dd'' be extremely cautious to get the devices correct.
# Turn off phone, remove microSD card and then turn on the phone.

=== SD to eMMC via installer ===

postmarketOS and Mobian installer images booted from microSD card will simply ask the user, if they want to install to eMMC. The feature lives in the distribution-agnostic calamares-extensions repository (see [https://github.com/calamares/calamares-extensions/pull/7 calamares-extensions#7]), so other distributions might adopt this in the future.

== Resize partition to fit disk space ==

{{Info|Many OSes already include a script, which is resizing the partition on first boot, where this step is not required.}}

Once you've flashed the OS to your microSD 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 microSD cards, insert the microSD 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 ====

Install growpart and run:
growpart /dev/'''mmcblkX''' '''Y'''
resize2fs /dev/'''mmcblkXpY'''
where ''X'' is the storage device and ''Y'' is the partition number (viewable from <code>lsblk</code>).

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

==== Using Parted ====

Parted's interactive mode and resize work well together. Do this before you put your microSD 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 resize2fs /dev/'''<the_second_sd_card_PARTITION>'''

=== Resize from within the PinePhone ===

eMMC: you would need to resize the partition on eMMC (flashed with the operating system) by booting another image from the microSD 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 microSD card, you can follow the above guidelines on how to resize from a computer.

MicroSD card: It is generally not possible to boot from eMMC to partition the unmounted microSD card, because of the boot order - you would have to write the image to the empty microSD card first, then resize partition, all without rebooting. It is also '''not recommended''' to resize the microSD card while booted from microSD 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 microSD 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 microSD 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 microSD card – as an example lets assume it is /dev/mmcblk0
then
sudo dd if=/dev/zero of=/dev/'''[DEVICE]''' bs=8k seek=1 count=4
will clear the relevant sectors of your card.

Since Danctnix (arch) switched to a gpt partition table from mbr in May of 2022 it installs u-boot at an offset of 128k instead of 8k, which means this command must be used instead
sudo dd if=/dev/zero of=/dev/'''[DEVICE]''' bs=32k seek=4 count=1

== Web resources ==

* [https://www.youtube.com/watch?v=7HMkU43P9hw Youtube video on how to flash OS images on the Pinephone (SD or eMMC) by Tech Pills]
* [https://www.youtube.com/watch?v=u65dofYFAPY Youtube video on How to install different OSes On the PinePhone plus an Mobian overview by Elatronion]

[[Category:PinePhone]][[Category:Guide]]

PinePhone Hardware Accessory Compatibility

2022-11-19T12:58:46Z

Wibble: /* Case */ add otterbox case info with forum link

The '''PinePhone''' and '''PinePhone Pro''' is compatible with a wide variety of accessories. A selection can be found here.

== Protection ==
=== Screen protector ===
The official screen protector can be found in the Pine64 store under [https://pine64.com/product/pinephone-tempered-glass-screen-protector/?v=0446c16e2e66 PinePhone Tempered Glass Screen Protector].

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

=== Case ===
The Pine store has official cases:

* [https://pine64.com/?product=pinephone-hard-protective-case&v=0446c16e2e66 PinePhone Hard Protective Case]
* [https://pine64.com/product/pinephone-soft-tpu-protective-case PinePhone Soft TPU Protective Case]

Tight-fit cases of other phones can't be used with the PinePhone because most times the proportions and/or camera notch won't fit. The phone can however be used with most "phone sleeves", such as those from fitBAG. The sleeve from fitBAG for the Xiaomi Redmi Note 8 Pro fits the PinePhone tightly.

The OtterBox uniVERSE Case for Samsung Galaxy XCover Pro is [https://forum.pine64.org/showthread.php?tid=17580&pid=114227 reported to fit well] without much modification.

== Add-ons ==
The PinePhone and PinePhone Pro can be extended by replacing the default back cover with custom accessory connecting to the pogo pins on the phone's midsection. Currently the keyboard case, the fingerprint reader, the wireless charging case and the PineDio LoRa case is available. Details can be found under:

* [[PinePhone (Pro) Add-ons]]
* [[PinePhone (Pro) Keyboard]]

== Community-built accessory ==

The following accessory is made by the community:

* [https://www.thingiverse.com/thing:4654013 PinePhone Development Stand at Thingverse]
* [https://www.thingiverse.com/thing:4658870 PinePhone Hard Case by _The3DmaN_ at Thingverse]
* [https://www.thingiverse.com/thing:5238124 PinePhone TPU Case by _The3DmaN_ at Thingverse]
* [https://www.thingiverse.com/thing:4651177 PinePhone Hard Case by blitzaxt at Thingverse]

== Peripheral equipment ==
=== Hubs ===
USB hubs do not require a custom driver and are therefore expected to be compatible with the PinePhone, as long as they are within the USB specification. On revisions the PinePhone mainboard revisions v1.1 and v1.2 the VCONN fix is required, on v1.2a and later the USB hub should work out of the box, see [[PinePhone#Hardware revisions]].

=== Bluetooth devices ===
In general, Bluetooth should be working. However, due to the audio setup on the PinePhone and PinePhone Pro being complicated due to the dynamic rerouting needed for phone calls.



[[Category:PinePhone]]

PinePhone APN Settings

2022-06-20T09:24:32Z

Wibble: /* External links */ update lineageos link to latest branch

The [https://en.wikipedia.org/wiki/Access_Point_Name APN] setting is the gateway between your carrier's cellular network and the '''public Internet'''. The APN setting - if not set automatically by the user's OS - has to be set by the user to enable the use of the mobile Internet on the phone.

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

== 4ka (Slovakia) ==
Name: 4ka Internet
APN: internet
Username: <empty>
Password: <empty>

Source: https://www.4ka.sk/vitajte/navody-a-nastavenia/detail-navodu

== AT&T-based ==

=== AT&T (USA) ===
APN: NXTGENPHONE
MMSC: http://mmsc.mobile.att.net
MMS proxy: proxy.mobile.att.net

APN: <code>phone</code> may alternatively work. (see

Source: https://www.att.com/support/article/wireless/KM1218306/

=== AT&T Mexico (Mexico) ===

APN: <code> wap.attmex.mx </code>

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

== Blau.de (Germany) ==
APN: internet.eplus.de
Username: eplus
Password: gprs

Source: https://www.my-gps.org/412-apn-einstellungen-deutschland

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

== Congstar - Telekom Net (Germany) ==
Name: Telekom Internet
APN: internet.telekom
Username: telekom
Password: telekom

Other settings seem to work, too. [https://forum.congstar.de/Tarife/Tarif-Produktberatung/46325-Mobil-surfen-mit-congstar-manuelle-Einstellungen-zum-mobilen-Internet-APN/ Congstar mentions]

Name: Congstar Internet
APN: internet.telekom
Username: congstar
Password: cs

== Eastlink Wireless (Canada) ==

Name: Eastlink Internet
APN: wisp.mobi.eastlink.ca
Username: <empty>
Password: <empty>

Source: https://www.apnsettings.org/canada/eastlink-ca/

== Free (France) ==

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

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

== Freedom Mobile (Canada) ==

Name: 1
APN: internet.freedommobile.ca
Username: <empty>
Password: <empty>

== Google Fi (USA) ==

These are settings that Google provides for their "data-only" SIM cards, but also appears to work fine with the normal SIM card for texting and calling.

Name: Google Fi
APN: h2g2
Username: <empty>
Password: <empty>

Source: https://support.google.com/fi/answer/6330195?hl=en

== Hofer Telekom (Austria) ==

Name: HoT Internet
APN: webaut
Username: <empty>
Password: <empty>

Source: https://www.hot.at/config/faqs/HoT_Einstellungen_Endgera_te.pdf

== kölbi (Costa Rica) ==
Name: Costa Rica:Kolbi:Internet
APN: kolbi3g
Username: <empty>
Password: <empty>

Note: alternatively <code>kolbi4g</code> also works as APN.

== Koodo (Canada) ==

Name: Internet/MMS 2
APN: sp.koodo.com
Username: <empty>
Password: <empty>

Source: https://www.4gapn.com/ca/en/koodo

== KT (South Korea) ==

Name: KT LTE
APN: lte.ktfwing.com
Username: <empty>
Password: <empty>

Name: KT 3G
APN: alwayson.ktfwing.com
Username: <empty>
Password: <empty>

Note: APN automatically detected in Manjaro Phosh. Use either KT LTE or KT 3G according to your subscription.

== Lebara (UK) ==
Name: Lebara
APN: uk.lebara.mobi
Username: wap
Password: wap

These settings work on 4G.

Ignore Default/asdamobiles.co.uk APN if present.

== Magenta LTE (Austria) ==

Name: Magenta
APN: internet.t-mobile.at
Username: t-mobile
Password: tm

Source: https://www.magenta.at/faq/entry/%7Etechnische-anfrage%7Esmartphone%7Efunktionen%26dienste/%7EInternet_APN%7Emaster

== Mineo (Japan) ==

Tested with S plan (Softbank) and D plan (Docomo). Mobile LTE data currently working only on Phosh-based OSes, because they use Network Manager and Modem Manager. Ubuntu Touch not working yet, see issue #58. https://gitlab.com/ubports/community-ports/pinephone/-/issues/58

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-

If the first one doesn't work try this one:

Name: Mobile Vikings
APN: web.be
Username: <empty>
Password: <empty>

Source: autoconfig on ubports

== Movistar (Colombia) ==

Name: Movistar Internet
APN: internet.movistar.com.co
Username: movistar
Password: movistar

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

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

== Orange (Poland) ==
Name: Internet IPv4
APN: internet
Username: internet
Password: internet

Source: https://www.orange.pl/omnibook/konfiguracja-internetu-mms-sms-w-telefonie#

Note: don't forget to activate sim-card using official android/ios app.

== Patriot Mobile (USA T-Mobile) ==
Internet
<pre>
Name: T-Mobile
APN: Fast.t-mobile.com
Username: <empty>
Password: <empty>
</pre>
MMS (requires chatty v0.6.1 and mmsd-tng v1.8) 
in /home/alarm/.mms/modemmanager/mms
<pre>
[Modem Manager]
CarrierMMSC=http://mms.msg.eng.t-mobile.com/mms/wapenc
MMS_APN=Fast.t-mobile.com
CarrierMMSProxy=NULL
DefaultModemNumber=NULL
AutoProcessOnConnection=true
AutoProcessSMSWAP=true

[Settings]
UseDeliveryReports=false
TotalMaxAttachmentSize=600000
MaxAttachments=25
AutoCreateSMIL=true
ForceCAres=false
</pre>

Source: https://www.t-mobile.com/support/devices/not-sold-by-t-mobile/byod-t-mobile-data-and-apn-settings

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

APN settings:

name: Red Pocket
APN: RESELLER

== Rogers (Canada) ==

Name: 4G/LTE Rogers Data
APN: ltemobile.apn
Username: <empty>
Password: <empty>

Name: 3G Rogers Data
APN: internet.com
Username: wapuser1
Password: wap

Source: https://communityforums.rogers.com/t5/Wireless-Knowledge-Base/Rogers-APN-Settings/ta-p/410438,

== Simyo (Spain) ==

APN settings:
APN: orangeworld

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

== SFR (France) ==

APN settings:
Name: SFR webphone
APN: sl2sfr
username: <empty>
password: <empty>

Source: https://assistance.sfr.fr/tel-mobile/utilisation-param/parametrer-apn-sfr-mobile.html

== Sunrise (Switzerland) ==

Name: Sunrise
APN: internet
Username: <empty>
Password: <empty>

== Swisscom (Switzerland) ==

Name: Swisscom
APN: gprs.swisscom.ch
Username: <empty>
Password: <empty>

== Tele2 (Sweden) ==
Name: tele2
APN: 4G.tele2.se
Username: <empty>
Password: <empty>

Source: https://www.tele2.se/support/felsokning-guider/tjanster-installningar/mms-och-data

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

== Telekom (Hungary) ==

APN settings:

Name: Default
APN: internet.telekom
Username: <empty>
Password: <empty>

== Telenor (Hungary) ==

Name: Telenor
APN: online
Username: <empty>
Password: <empty>

Source: https://apn.how/hungary/telenor-hungary

== Telenor (Sweden) ==

Name: Telenor SE
APN: services.telenor.se
Username: <empty>
Password: <empty>

Source: https://www.telenor.se/kundservice/vanliga-fragor/min-mobil-surfplatta/vad-har-telenor-for-apn-installningar/

== Telia (Finland) ==
Name: internet
APN: internet
Username: <empty>
Password: <empty>

== Telstra (Australia) ==

Name: Telstra Internet/WAP
APN: telstra.iph
Username: <empty>
Password: <empty>

== Three (UK) ==

Name: 3
APN: three.co.uk
Username: <empty>
Password: <empty>

== Ting (USA) ==
Using the X3 sim card:
Name: Ting Data
APN: wireless.dish.com
Username: <empty>
Password: <empty>

For MMS configuration had success using:
MMSC: http://wholesale.mmsmvno.com/mms/wapenc

The article mentions using this APN for a hotspot, but unconfirmed
Name: Ting Hotspot
APN: tethering.dish.com
Username: <empty>
Password: <empty>

Source: https://help.ting.com/hc/en-us/articles/205428698-APN-setup-guide#android-apn-settings-with-the-x3-sim-card-0-1

== Tracfone (USA) ==

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

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>

== Verizon Contract (USA) ==

There are several APN names which can be used, for example:

Name: 4G LTE Contract
APN: vzwinternet
Username: <empty>
Password: <empty>

Other APN names which appear, and may work if the above does not:

vzwapp
vzwims

== Videotron (Canada) ==

Name: Videotron
APN: media.ng
Username: free
Password: <empty>

== Virgin Mobile (Canada) ==

Settings might work with Bell Canada too since it is the same network.

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

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

== Vodafone (UK) ==
Name: Vodafone
APN: wap.vodafone.co.uk
Username: wap
Password: wap

These settings work on 4G.

Ignore Default/asdamobiles.co.uk APN if present.

== winSIM (Germany) ==
Name: winSIM
APN: internet
Username: <empty>
Passwort: <empty>

Source: https://service.winsim.de/help/showGeraeteeinstellungen (Requires login)

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

Sprint is currently not supported due to unknown issues, see also [[PinePhone Carrier Support#Sprint]]. Any input regarding this issue is highly appreciated.

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

== Visible (USA) ==

Visible does not have any way to approve unsupported phones, it might be possible through APN settings, but requires more research and dev time. Even activating a SIM using a supported phone, and then moving it to the Pinephone does not work.

== Other ==

Other VoLTE services.

= External links =

* See also https://forum.pine64.org/showthread.php?tid=9150
* LineageOS APN and MMS defaults - https://github.com/LineageOS/android_vendor_lineage/blob/lineage-19.1/prebuilt/common/etc/apns-conf.xml

[[Category:PinePhone]]

PinePhone APN Settings

2021-10-11T15:55:54Z

Wibble: /* External links */ add link to LineageOS default APN and MMS settings

The [https://en.wikipedia.org/wiki/Access_Point_Name APN] setting is the gateway between your carrier's cellular network and the '''public Internet'''. The APN setting - if not set automatically by the user's OS - has to be set by the user to enable the use of the mobile Internet on the phone.

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

== 4ka (Slovakia) ==
Name: 4ka Internet
APN: internet
Username: <empty>
Password: <empty>

Source: https://www.4ka.sk/vitajte/navody-a-nastavenia/detail-navodu

== AT&T-based ==

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

=== AT&T Mexico (Mexico) ===

APN: <code> wap.attmex.mx </code>

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

== Blau.de (Germany) ==
APN: internet.eplus.de
Username: eplus
Password: gprs

Source: https://www.my-gps.org/412-apn-einstellungen-deutschland

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

== Congstar - Telekom Net (Germany) ==
Name: Telekom Internet
APN: internet.telekom
Username: telekom
Password: telekom

Other settings seem to work, too. [https://forum.congstar.de/Tarife/Tarif-Produktberatung/46325-Mobil-surfen-mit-congstar-manuelle-Einstellungen-zum-mobilen-Internet-APN/ Congstar mentions]

Name: Congstar Internet
APN: internet.telekom
Username: congstar
Password: cs

== Eastlink Wireless (Canada) ==

Name: Eastlink Internet
APN: wisp.mobi.eastlink.ca
Username: <empty>
Password: <empty>

Source: https://www.apnsettings.org/canada/eastlink-ca/

== Free (France) ==

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

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

== Freedom Mobile (Canada) ==

Name: 1
APN: internet.freedommobile.ca
Username: <empty>
Password: <empty>

== Google Fi (USA) ==

These are settings that Google provides for their "data-only" SIM cards, but also appears to work fine with the normal SIM card for texting and calling.

Name: Google Fi
APN: h2g2
Username: <empty>
Password: <empty>

Source: https://support.google.com/fi/answer/6330195?hl=en

== Hofer Telekom (Austria) ==

Name: HoT Internet
APN: webaut
Username: <empty>
Password: <empty>

Source: https://www.hot.at/config/faqs/HoT_Einstellungen_Endgera_te.pdf

== kölbi (Costa Rica) ==
Name: Costa Rica:Kolbi:Internet
APN: kolbi3g
Username: <empty>
Password: <empty>

Note: alternatively <code>kolbi4g</code> also works as APN.

== Koodo (Canada) ==

Name: Internet/MMS 2
APN: sp.koodo.com
Username: <empty>
Password: <empty>

Source: https://www.4gapn.com/ca/en/koodo

== KT (South Korea) ==

Name: KT LTE
APN: lte.ktfwing.com
Username: <empty>
Password: <empty>

Name: KT 3G
APN: alwayson.ktfwing.com
Username: <empty>
Password: <empty>

Note: APN automatically detected in Manjaro Phosh. Use either KT LTE or KT 3G according to your subscription.

== Lebara (UK) ==
Name: Lebara
APN: uk.lebara.mobi
Username: wap
Password: wap

These settings work on 4G.

Ignore Default/asdamobiles.co.uk APN if present.

== Mineo (Japan) ==

Tested with S plan (Softbank) and D plan (Docomo). Mobile LTE data currently working only on Phosh-based OSes, because they use Network Manager and Modem Manager. Ubuntu Touch not working yet, see issue #58. https://gitlab.com/ubports/community-ports/pinephone/-/issues/58

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-

If the first one doesn't work try this one:

Name: Mobile Vikings
APN: web.be
Username: <empty>
Password: <empty>

Source: autoconfig on ubports

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

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.

APN settings:

name: Red Pocket
APN: RESELLER

== Rogers (Canada) ==

Name: 4G/LTE Rogers Data
APN: ltemobile.apn
Username: <empty>
Password: <empty>

Name: 3G Rogers Data
APN: internet.com
Username: wapuser1
Password: wap

Source: https://communityforums.rogers.com/t5/Wireless-Knowledge-Base/Rogers-APN-Settings/ta-p/410438,

== Simyo (Spain) ==

APN settings:
APN: orangeworld

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

== Sunrise (Switzerland) ==

Name: Sunrise
APN: internet
Username: <empty>
Password: <empty>

== Swisscom (Switzerland) ==

Name: Swisscom
APN: gprs.swisscom.ch
Username: <empty>
Password: <empty>

== Tele2 (Sweden) ==
Name: tele2
APN: 4G.tele2.se
Username: <empty>
Password: <empty>

Source: https://www.tele2.se/support/felsokning-guider/tjanster-installningar/mms-och-data

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

== Telekom (Hungary) ==

APN settings:

Name: Default
APN: internet.telekom
Username: <empty>
Password: <empty>

== Telenor (Hungary) ==

Name: Telenor
APN: online
Username: <empty>
Password: <empty>

Source: https://apn.how/hungary/telenor-hungary

== Telenor (Sweden) ==

Name: Telenor SE
APN: services.telenor.se
Username: <empty>
Password: <empty>

Source: https://www.telenor.se/kundservice/vanliga-fragor/min-mobil-surfplatta/vad-har-telenor-for-apn-installningar/

== Telia (Finland) ==
Name: internet
APN: internet
Username: <empty>
Password: <empty>

== Telstra (Australia) ==

Name: Telstra Internet/WAP
APN: telstra.iph
Username: <empty>
Password: <empty>

== Three (UK) ==

Name: 3
APN: three.co.uk
Username: <empty>
Password: <empty>

== Tracfone (USA) ==

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

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>

== Verizon Contract (USA) ==

There are several APN names which can be used, for example:

Name: 4G LTE Contract
APN: vzwinternet
Username: <empty>
Password: <empty>

Other APN names which appear, and may work if the above does not:

vzwapp
vzwims

== Videotron (Canada) ==

Name: Videotron
APN: media.ng
Username: free
Password: <empty>

== Virgin Mobile (Canada) ==

Settings might work with Bell Canada too since it is the same network.

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

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

== Vodafone (UK) ==
Name: Vodafone
APN: wap.vodafone.co.uk
Username: wap
Password: wap

These settings work on 4G.

Ignore Default/asdamobiles.co.uk APN if present.

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

Sprint is currently not supported due to unknown issues, see also [[PinePhone Carrier Support#Sprint]]. Any input regarding this issue is highly appreciated.

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

== Visible (USA) ==

Visible does not have any way to approve unsupported phones, it might be possible through APN settings, but requires more research and dev time. Even activating a SIM using a supported phone, and then moving it to the Pinephone does not work.

== Other ==

Other VoLTE services.

= External links =

* See also https://forum.pine64.org/showthread.php?tid=9150
* LineageOS APN and MMS defaults - https://github.com/LineageOS/android_vendor_lineage/blob/lineage-18.1/prebuilt/common/etc/apns-conf.xml

[[Category:PinePhone]]

PinePhone Modding

2021-04-07T16:11:24Z

Wibble:

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 compare the change, and don't need to disassemble the device to get the right pics later.

==Device Specific Mods ==
There are a number 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 has created a 3D-printable rear frame for the PinePhone and used it to create a folding keyboard design (work in progress), [[User:Silver/3d printed a folding keyboard mostly]].

https://ibb.co/album/ScDttH

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

==PCBs==

https://github.com/SMR404/PinephonePogoBreakout

https://github.com/jnavarro7/pinephone_flex_breakout_board_grove

[[Category:PinePhone]]

PinePhone Modding

2021-04-07T16:10:53Z

Wibble: add flex breakout pcb link

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 compare the change, and don't need to disassemble the device to get the right pics later.

==Device Specific Mods ==
There are a number 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 has created a 3D-printable rear frame for the PinePhone and used it to create a folding keyboard design (work in progress), [[User:Silver/3d printed a folding keyboard mostly]].

https://ibb.co/album/ScDttH

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

==PCBs==

https://github.com/SMR404/PinephonePogoBreakout
https://github.com/jnavarro7/pinephone_flex_breakout_board_grove

[[Category:PinePhone]]

2020-01-20T11:33:08Z

Wibble: /* Development efforts */ update mynewt port link

== Frequently asked questions ==

[https://wiki.pine64.org/index.php/Frequently_asked_questions_about_the_PineTime Click here to see frequently asked questions]

== Specifications ==
'''Dimensions:''' 37.5 x 40 x 11mm 
'''Weight:''' 38 grams 
'''IP Rating:''' IP67 (waterproof to 1 meter) 
'''Display:'''
: '''Size:''' 1.3 inches (33mm) diagonal
: '''Type:''' IPS capacitive touchscreen, RGB 65K colors
: '''Display Controller:''' ST7789
: '''Resolution:''' 240x240 pixels 
'''System on Chip:''' Nordic Semiconductor nRF52832 
'''Flash:''' 512KB with additional 4MB SPI NOR 
'''RAM:''' 64KB 
'''Bluetooth:''' 5.0 (including Bluetooth Low Energy) 
'''Sensors:''' Accelerometer, Heart rate sensor 
'''Feedback:''' Vibration motor 
'''Battery:''' 170-180mAh LiPo

== SWD Pinout ==
The devkits have exposed SWD pins for flashing and debugging. The pinout is:
[[File:PineTime_SWD_location.jpg]]

== Driving the peripherals ==

=== Display ===

Note: The factory-default software on the PineTime does not auto-detect the display being disconnected when it has already booted. That can cause garbled output, to fix it just restart the PineTime.

The display is driven using the ST7789 display controller. Use the following pins to drive the screen:

{| class="wikitable"
|-
! PineTime pin
! ST7789 pin
|-
| LCD_SCK (P0.02)
| SPI clock
|-
| LCD_SDI (P0.03)
| SPI MOSI
|-
| LCD_RS (P0.18)
| Clock/data pin (CD)
|-
| LCD_CS (P0.25)
| Chip select
|-
| LCD_RESET (P0.26)
| Display reset
|-
| LCD_BACKLIGHT_{LOW,MID,HIGH}
| Backlight (active low)
|}

Notes:

* Chip select must be held low while driving the display. It must be high when using other SPI devices on the same bus (such as external flash storage) so that the display controller won't respond to the wrong commands.
* SPI must be used in mode 3. Mode 0 (the default) won't work.
* LCD_DISPLAY_* is used to enable the backlight. Set at least one to low to see anything on the screen.
* Use SPI at 8MHz (the fastest clock available on the nRF52832) because otherwise refreshing will be super slow.

=== Battery ===

Reading whether the PineTime has power attached is easy: simply read the charge indication pin (P0.12). When it is high it is running on battery, when it is low it is charging.

Reading the battery voltage is a bit harder. For that you can use the battery voltage pin on P0.31 (AIN7). The returned value is 12 bits, which means it is 0..4095. You can get the measured voltage with the following formula, assuming a reference voltage of 3.3V (this is configurable in the ADC):

adcVoltage = adcValue / (4095 / 3.3)

The measured voltage is actually half of the actual battery voltage, because the ADC is connected between a voltage divider where both resistors are 1MΩ. This can be corrected by multiplying the value:

batteryVoltage = adcValue * 2 / (4095 / 3.3)

It's often better to avoid floating point values on embedded systems and in this case there is no reason to use float at all, we can just represent the value in millivolts. Therefore the formula can be simplified to:

batteryVoltage = adcValue * 2000 / (4095 / 3.3)
batteryVoltage = adcValue * 2000 / 1241

Converting this voltage to an estimated capacity in percent requires a more complicated algorithm, because Lithium-ion batteries have a non-linear discharge curve.

=== Button ===

The button on the side of the PineTime is disabled by default. To enable it, drive the button out pin (P0.15) high.

While enabled, the button in pin (P0.13) will be high when the button is pressed, and low when it is not pressed.

=== Touch panel ===

The touch panel is controlled by a Hynitron CST816S chips. Unfortunately, there is not much information about this chip on the internet apart from the datasheet below and a [https://github.com/lupyuen/hynitron_i2c_cst0xxse/ reference driver]. This is enough to implement a basic driver, but crucial information needed to implement advanced functionalities are missing (I²C protocol and registers, timings, power modes,...).

==== Pins ====

* P0.10 : Reset
* P0.28 : Interrupt (signal to the CPU when a touch event is detected)
* P0.06 : I²C SDA
* P0.07 : I²C SCL

==== I²C ====

* Device address : 0x15
* Frequency : from 10Khz to 400Khz

'''NOTE : ''' The controller go to sleep when no event is detected. In sleep mode, the controller does not communicate on the I²C bus (it appears disconnected). So, for the communication to work, you need to tap on the screen so that the chip wakes-up.

==== Touch events ====

Touch informations are available in the 63 first registers of the controller. Remember : the device is in sleep mode when no touch event is detected. It means that you can read the register only when the touch controller detected an event. You can use the ''Interrupt'' pin to detect such event in the software.

These 63 bytes contain up to 10 touch point (X, Y, event type, pressure,...) :

{| class="wikitable"
! Byte
! Bit7
! Bit6
! Bit5
! Bit4
! Bit3
! Bit2
! Bit1
! Bit0
|-
|0
|colspan="8"|?
|-
|1
|colspan="8"|GestureID : (Gesture code ,

0x00: no gesture,

0x01: on a slippery,

0x02: decline,

0x03: Left slip,

0x04: Right slide,

0x05: Click,

0x0B: Double-click,

0x0C: Press)
|-
|2
|colspan="4"|?
|colspan="4"|Number of touch points
|-
|3
|colspan="2"|Event (0 = Down, 1 = Up, 2 = Contact)
|colspan="2"|?
|colspan="4"|X (MSB) coordinate
|-
|4
|colspan="8"|X (LSB) coordinate
|-
|5
|colspan="2"|?
|colspan="2"|Touch ID
|colspan="4"|Y (MSB) coordinate
|-
|6
|colspan="8"|Y (LSB) coordinate
|-
|7
|colspan="8"|Pressure (?)
|-
|8
|colspan="8"|Miscellaneous (?)
|}

Bytes 3 to 8 are repeated 10 times (10*6 + 3 = 63 bytes).

'''NOTES'''

* The touch controller seems to report only 1 touch point
* Fields X, Y, Number of touch points and touch ID are updated. The others are always 0.

==== Registers ====

The reference driver specifies some registers and value, but there is no information about them:

{| class="wikitable"

!Register
!Address
!Description
|-
|HYN_REG_INT_CNT
|0x8F
|
|-
|HYN_REG_FLOW_WORK_CNT
|0x91
|
|-
|HYN_REG_WORKMODE
|0x00
|0 = WORK, 0x40 = FACTORY
|-
|HYN_REG_CHIP_ID
|0xA3
|
|-
|HYN_REG_CHIP_ID2
|0x9F
|-
|HYN_REG_POWER_MODE
|0xA5
|0x05 = SLEEP
|-
|HYN_REG_FW_VER
|0xA6
|
|-
|HYN_REG_VENDOR_ID
|0xA8
|
|-
|HYN_REG_LCD_BUSY_NUM
|0xAB
|
|-
|HYN_REG_FACE_DEC_MODE_EN
|0xB0
|
|-
|HYN_REG_GLOVE_MODE_EN
|0xC0
|
|-
|HYN_REG_COVER_MODE_EN
|0xC1
|
|-
|HYN_REG_CHARGER_MODE_EN
|0x8B
|
|-
|HYN_REG_GESTURE_EN
|0xD0
|
|-
|HYN_REG_GESTURE_OUTPUT_ADDRESS
|0xD3
|
|-
|HYN_REG_ESD_SATURATE 0xED
|0xED
|
|}

'''WARNING : ''' Writing the SLEEP command (write 0x05 in HYN_REG_POWER_MODE) seems to freeze the controller (it returns only static values) until the battery is totally drained and the whole system reset. Analysis and debugging is more than welcome!

== Programming firmware ==

=== Using JLink programmer and nrfjprog tools ===

The following steps have been tested with the Segger JLink embedded in the [https://www.nordicsemi.com/Software-and-Tools/Development-Kits/nRF52-DK NRF52-DK development board].

1. Connect the Pinetime SWD pins to the debugger (P20 on NRF52-DK)

{| class="wikitable"
!Pintime
!JLink
|-
|GND
|GND
|-
|SWDCLK
|SWDCLK
|-
|SWDIO
|SWDIO
|-
|VCC (3.3V)
|VTG (target detect)
|}

2. Unlock the device and erase the memory. '''You need to execute this step only once, to remove the read protection on the memory. Note that it will erase the whole flash memory of the MCU!''' :

nrfjporg -f NRF52 --recover

3. Program the BLE softdevice (if needed by the firmware). Replace PATH_TO_NRF_SDK by the path where you unzipped the [https://www.nordicsemi.com/Software-and-Tools/Software/nRF5-SDK NRF52 SDK] :

nrfjprog -f NRF52 --program /PATH_TO_NRF_SDK/components/softdevice/s132/hex/s132_nrf52_6.1.1_softdevice.hex --sectorerase

4. Program the firmware (replace firmware.hex by the actual filename of the firmware):

nrfjprog -f NRF52 --program firmware.hex --sectorerase

5. Reset and run the new firmware:

nrfjprog -f NRF52 --reset

== Manual / Articles ==

* [https://github.com/najnesnaj/pinetime-zephyr Beginner manual explained how you to programs and install zephyr on PineTime Dev Kit, big thanks to najnesnaj :-)]

* [https://medium.com/swlh/sneak-peek-of-pinetime-smart-watch-and-why-its-perfect-for-teaching-iot-81b74161c159 Sneak Peek of PineTime Smart Watch… And why it’s perfect for teaching IoT]

* [https://medium.com/@ly.lee/building-a-rust-driver-for-pinetimes-touch-controller-cbc1a5d5d3e9 Building a Rust Driver for PineTime’s Touch Controller]

* [https://medium.com/@ly.lee/porting-druid-rust-widgets-to-pinetime-smart-watch-7e1d5a5d977a Porting (druid) Rust Widgets to PineTime Smart Watch]

* [https://medium.com/@ly.lee/optimising-pinetimes-display-driver-with-rust-and-mynewt-3ba269ea2f5c Optimising PineTime’s Display Driver with Rust and Mynewt]

* [https://www.zephyrproject.org/getting-started-with-zephyr-rtos-on-nordic-nrf52832-hackable/ Getting Started with Zephyr RTOS on Nordic nRF52832 hackaBLE]

* [https://blog.aegrel.ee/absniffer-cmsis-dap-sniffer.html Removing the lock and installing another firmware on the nRF52832 using CMSIS-DAP dongle on Linux]

* [https://github.com/JF002/nrf52-baseproject/wiki/Build,-program-and-debug-NRF52-project-with-JLink,-CMake-and-CLion Build, program and debug NRF52 project with JLink, CMake and CLion]

* [https://www.nrbtech.io/blog/2020/1/4/using-clion-for-nordic-nrf52-projects Using CLion for Nordic nRF52 projects]

* [https://wiki.pine64.org/index.php/Frequently_asked_questions_about_the_PineTime Frequently asked questions about the dev kit]

* [https://dev.to/aaronc81/flashing-your-pinetime-using-an-st-link-and-openocd-54dd Flashing your PineTime using an ST-Link and OpenOCD]

== Development efforts ==

{| class="wikitable"
!
! Project Homepage
! Project Source
! PineTime Implementations

|-
! FreeRTOS
|https://www.freertos.org
| https://sourceforge.net/projects/freertos/
| [https://github.com/JF002/Pinetime JF002/Pinetime]
[https://github.com/kaythe/pinetime-os kaythe/pinetime-os]

|-
! Zephyr
| https://www.zephyrproject.org
| https://github.com/zephyrproject-rtos/zephyr
| [https://github.com/najnesnaj/pinetime-zephyr najnesnaj/pinetime-zephyr]
[https://github.com/SuperPrower/pinetime_zephyr_sample_fw SuperPrower/pinetime_zephyr_sample_fw]

|-
! mynewt
| https://mynewt.apache.org/about/
| https://github.com/apache/mynewt-core
| [https://github.com/lupyuen/pinetime-rust-mynewt lupyuen/pinetime-rust-mynewt]

|-
! MbedOS
| https://os.mbed.com
| https://github.com/ARMmbed/mbed-os
| [https://github.com/sethitow/awesome-pinetime sethitow/mbed-pinetime]

|-
! RIOT
| http://riot-os.org/
| https://github.com/RIOT-OS/RIOT/
| [https://github.com/bosmoment/PineTime-apps bosmoment/PineTime-apps]

|-
! TinyGo
| https://tinygo.org
| https://github.com/tinygo-org/tinygo
| [https://github.com/aykevl/go-smartwatch aykevl/go-smartwatch]
|-
|}

== Datasheets and Schematics ==

=== Schematics ===
* [http://files.pine64.org/doc/PineTime/PineTime%20Schematic-V1.0a-20191103.pdf PineTime Schematic ver1.0a]
* [http://files.pine64.org/doc/PineTime/PineTime%20Port%20Assignment%20rev1.0.pdf PineTime GPIO Port Assignment ver1.0]

=== Component Datasheets ===
* NORDIC SoC information:
** [http://files.pine64.org/doc/datasheet/pinetime/nRF52832%20product%20brief.pdf NORDIC nRF52832 Product Brief]
* PMU (Power Management Unit) information:
** [http://files.pine64.org/doc/datasheet/pinetime/SGM40561.pdf SGMicro SGM40561 Single Cell Charger Datasheet]
** [http://files.pine64.org/doc/datasheet/pinetime/SGMICRO-SGM2036.pdf SGMicro SGM2036 3.3V Low Power Low Dropout RF Linear Regulator Datasheet]
* SPI Flash information:
** [http://files.pine64.org/doc/datasheet/pinetime/MX25L6433F,%203V,%2064Mb,%20v1.6.pdf Macronix 64Mb(8MB) SPI NOR Flash]
** [http://files.pine64.org/doc/datasheet/pinetime/MX25L12835F,%203V,%20128Mb,%20v1.6.pdf Macronix 128Mb(16MB) SPI NOR Flash]
* LCD Panel:
** [http://files.pine64.org/doc/datasheet/pinetime/PineTime%20LCD%20Panel.jpg 1.3" 240x240 IPS LCD Panel Specification for PineTime]
** [https://wiki.pine64.org/images/5/54/ST7789V_v1.6.pdf 11.6" Sitronix LCD Driver/Controller Datasheet]
* Touchpad information:
** [http://files.pine64.org/doc/datasheet/pinetime/PineTime%20Touch%20Panel.jpg Touchpad Specification for PineTimel]
** [http://files.pine64.org/doc/datasheet/pinetime/CST816S数据手册V1.1.pdf 11.6" Hynitron CST816S Capacitive Touch Controller Datasheet in Chinese]
*** [https://wiki.pine64.org/images/5/51/CST816S%E6%95%B0%E6%8D%AE%E6%89%8B%E5%86%8CV1.1.en.pdf English Translation]
* Sensor:
** [http://files.pine64.org/doc/datasheet/pinetime/BST-BMA421-FL000.pdf BOSCH BMA421 Triaxial VAcceleration Sensor Product Brief]
** [http://files.pine64.org/doc/datasheet/pinetime/HRS3300%20Heart%20Rate%20Sensor.pdf TianYiHeXin HRS3300 PPG Heart Rate Sensor Data Sheet]

PinePhone

2019-12-31T11:06:19Z

Wibble: /* Battery */ add detail of charging from fully discharged

The PinePhone is a smartphone created by Pine64, capable of running mainline Linux and supported by many partner projects. A "braveheart" edition is currently available for purchase from the PINE64 store, though it should be noted that this version comes without a preinstalled OS, and is geared specifically towards tinkerers and hackers. People looking for a stable consumer-grade phone should wait for the final release, which is expected to occur in March 2020 and will be available for at least five years.

== Specifications ==

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

== Hardware Revisions ==

# [[Project Don't be evil|"Project Don't Be Evil" devkit]]
# PinePhone v1.0 - Developer batch
# [[PinePhone v1.1 - Braveheart]]

== Hardware Addons ==

The PinePhone has 6 "pogo pins" on the back allowing for custom hardware extensions such as wireless charging or an IR blaster. The pogo pins provide access to an interrupt line, power input to charge the battery, 3.3v power source, and an I2C interface.

A step file for the back cover is [https://app.box.com/s/g1n9cvg60cg66utdhs7m5my1ftvd0jj8 freely available] for creating custom cases that interface with the pogo pins.

== Killswitch configuration ==

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.

[[File:PinePhone-main-board.jpg|600px|thumb|centre|Photo of Developer mainboard courtesy of Martijn Braam, postmarketOS]]

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

== Battery ==

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

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

# +ve
# thermistor
# -ve
# not connected

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

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

== Operating Systems ==
The PinePhone will automatically boot from microSD if a bootable card is inserted. Although it is technically possible to use any ARM distro (because the PinePhone uses the mainline kernel), there are a few that are designed specifically for phones:
* [[#postmarketOS|postmarketOS]]
* [[#Ubuntu Touch|Ubuntu Touch]]
* [[#Sailfish OS|Sailfish OS]]
* [[#Maemo Leste|Maemo Leste]]
* [[#LuneOS|LuneOS]]

=== postmarketOS ===
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices. The latest builds can be downloaded from the [https://images.postmarketos.org/pinephone/ images page] to be flashed to the PinePhone.

More information is available at [https://postmarketos.org postmarketos.org] and on their [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) dedicated PinePhone wiki page].

=== Ubuntu Touch ===
[https://ubuntu-touch.io/ Ubuntu touch] is a mobile version of Ubuntu developed by the UBports community. Images can be downloaded from [https://ci.ubports.com/job/rootfs/job/rootfs-pinephone/ here]. The default password is <code>phablet</code>. In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://ubuntu-touch.io/get-ut UBports installer] GUI tool.

=== Sailfish OS ===
The latest Sailfish OS 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, 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>
# Execute it: <code>./flash-it.sh</code>
# Follow the instructions. Some commands in the script require root permissions.

=== Nemo Mobile ===
Nemo Mobile is the open source build of Sailfish OS. The latest images for the PinePhone are released [https://github.com/neochapay/nemo-device-dont_be_evil/releases here].

=== Maemo Leste ===
[https://maemo-leste.github.io/ Maemo Leste] images can be downloaded [https://maedevu.maemo.org/images/pinephone-dontbeevil/ here]. The default username is <code>root</code> and the password is <code>toor</code>

=== LuneOS ===
[https://www.webos-ports.org/wiki/Main_Page LuneOS] downloads are available [http://build.webos-ports.org/luneos-testing/images/pinephone/ here].

PinePhone

2019-12-22T00:53:46Z

Wibble: Add section with more detailed battery info

The PinePhone is a smartphone created by Pine64, capable of running mainline Linux and supported by many partner projects. A "braveheart" edition is currently available for purchase from the PINE64 store, though it should be noted that this version comes without a preinstalled OS, and is geared specifically towards tinkerers and hackers. People looking for a stable consumer-grade phone should wait for the final release, which is expected to occur in March 2020 and will be available for at least five years.

== Specifications ==

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

== Hardware Revisions ==

# [[Project Don't be evil|"Project Don't Be Evil" devkit]]
# PinePhone v1.0 - Developer batch
# [[PinePhone v1.1 - Braveheart]]

== Hardware Addons ==

The PinePhone has 6 "pogo pins" on the back allowing for custom hardware extensions such as wireless charging or an IR blaster. The pogo pins provide access to an interrupt line, power input to charge the battery, 3.3v power source, and an I2C interface.

A step file for the back cover is [https://app.box.com/s/g1n9cvg60cg66utdhs7m5my1ftvd0jj8 freely available] for creating custom cases that interface with the pogo pins.

== Killswitch configuration ==

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.

[[File:PinePhone-main-board.jpg|600px|thumb|centre|Photo of Developer mainboard courtesy of Martijn Braam, postmarketOS]]

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

== Battery ==

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

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

# +ve
# thermistor
# -ve
# not connected

The battery includes a protection circuit that isolates it in a number of fault conditions, including if it is discharged too far.

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

== Operating Systems ==
The PinePhone will automatically boot from microSD if a bootable card is inserted. Although it is technically possible to use any ARM distro (because the PinePhone uses the mainline kernel), there are a few that are designed specifically for phones:
* [[#postmarketOS|postmarketOS]]
* [[#Ubuntu Touch|Ubuntu Touch]]
* [[#Sailfish OS|Sailfish OS]]
* [[#Maemo Leste|Maemo Leste]]
* [[#LuneOS|LuneOS]]

=== postmarketOS ===
postmarketOS is a preconfigured version of [https://www.alpinelinux.org/ Alpine Linux] for mobile devices. The latest builds can be downloaded from the [https://images.postmarketos.org/pinephone/ images page] to be flashed to the PinePhone.

More information is available at [https://postmarketos.org postmarketos.org] and on their [https://wiki.postmarketos.org/wiki/PINE64_PinePhone_(pine64-pinephone) dedicated PinePhone wiki page].

=== Ubuntu Touch ===
[https://ubuntu-touch.io/ Ubuntu touch] is a mobile version of Ubuntu developed by the UBports community. Images can be downloaded from [https://ci.ubports.com/job/rootfs/job/rootfs-pinephone/ here]. The default password is <code>phablet</code>. In the future, Ubuntu Touch will be able to be installed onto the PinePhone with the [https://ubuntu-touch.io/get-ut UBports installer] GUI tool.

=== Sailfish OS ===
The latest Sailfish OS 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, 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>
# Execute it: <code>./flash-it.sh</code>
# Follow the instructions. Some commands in the script require root permissions.

=== Nemo Mobile ===
Nemo Mobile is the open source build of Sailfish OS.

* For more info please visit [https://github.com/neochapay/nemo-device-dont_be_evil neochapay's github page]
* DD image for 8GB micoSD card /16GB eMMC module and above:
** [http://files.pine64.org/os/PinePhone/NemoMobile/nemo-pine64-release2019.11.tar.bz2 Release build 0.3 direct download from pine64.org]
** MD5 (XZ file): CA25F72A97CEE57C1479B90F445F4A4B
** size: 325MB

=== Maemo Leste ===
[https://maemo-leste.github.io/ Maemo Leste] images can be downloaded [https://maedevu.maemo.org/images/pinephone-dontbeevil/ here]. The default username is <code>root</code> and the password is <code>toor</code>

=== LuneOS ===
[https://www.webos-ports.org/wiki/Main_Page LuneOS] downloads are available [http://build.webos-ports.org/luneos-testing/images/pinephone/ here].