https://wiki.pine64.org/api.php?action=feedcontributions&user=Tahayassen&feedformat=atomPINE64 - User contributions [en]2024-03-29T06:04:08ZUser contributionsMediaWiki 1.37.1https://wiki.pine64.org/index.php?title=PinePhone_Carrier_Support&diff=11810PinePhone Carrier Support2021-11-18T05:17:55Z<p>Tahayassen: /* North America */</p>
<hr />
<div>{{under construction}}<br />
<br />
{{hint|MMS currently doesn't work in any distribution on the PinePhone without a [[PinePhone_Carrier_Support#MMS_workarounds|script]]! This means images and group chats will not work in text messages.}}<br />
<br />
This page contains hints on setting up cellular network connectivity for specific carriers.<br />
For more general information, see the carrier support section of [[PinePhone#Modem]]. For the APN settings see [[PinePhone APN Settings]].<br />
<br />
= Check compatibility =<br />
To check if the PinePhone is supported on your carrier:<br />
<br />
Search for your carrier on [https://www.frequencycheck.com/ frequencycheck.com] and compare the carrier's LTE/GSM/WCDMA frequencies to the PinePhone's supported frequencies (listed in the [[File:Quectel_EG25-G_LTE_Standard_Specification_V1.3.pdf]] modem specification sheet).<br />
<br />
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.<br />
<br />
= Tested and working carriers =<br />
<br />
The following is a list of carriers which has been tested by users and confirmed to be working (excerpt):<br />
<br />
== Asia ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
| Japan || SoftBank || Not tested || Unsupported by carrier || No || No || Mobian Phosh, December 2020<br />
|-<br />
| Japan || Rakuten Mobile || Unsupported by carrier || Unsupported by carrier || Yes || Yes || Mobian Phosh, January 2020<br />
|-<br />
| Japan || Rakuten Mobile || Unsupported by carrier || Unsupported by carrier || Yes || No || Manjaro Plasma Mobile February 2021<br />
|-<br />
| Japan || Docomo || Yes || Not tested || Yes || Yes || Mobian Phosh, February 2021<br />
|-<br />
| India || Vodafone / Vi India || Yes || Not tested || Yes || Yes || DanctNIX (Arch Linux ARM) with Phosh, March 2021<br />
|-<br />
| South Korea || KT || Yes || Not tested || Yes || Yes || Manjaro Phosh, June 2021<br />
|}<br />
<br />
== Africa ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129<br />
|-<br />
|}<br />
<br />
== Europe ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Ukraine || KyivStar || Yes || Not tested || Not tested || Yes || Mobian Phosh(11Nov21)<br />
|-<br />
| Sweden || Telenor SE || Not tested || Not tested || Yes || Not tested || Manjaro Plasma Mobile beta2<br />
|-<br />
| UK || Three || Yes || Not tested || Yes || Yes || Manjaro Plasma Mobile beta2<br />
|-<br />
| UK || Vodafone || Yes || Not tested || Yes || Yes || ALARM & pmOS (Phosh?), modem FW latest - 26 Feb 21<br />
|-<br />
| UK || Sky Mobile || Yes || Not tested || Yes || Yes || ArchLinux Phosh (20210908 image, fully updated) - 3 October 2021<br />
|-<br />
| France || Orange || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021<br />
|-<br />
| France || SFR || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021<br />
|-<br />
| France || Free || Yes || Not tested || Yes || Not tested || ArchLinux - 30 July 2021<br />
|-<br />
| Czech Republic || O2 || Yes (only on 2G) || Not tested || Yes || Yes || Mobian Phosh (20210517 image up to date) - 2 June 2021<br />
|-<br />
| Germany || Congstar || Yes || Not tested || Yes || Yes (IPv4 & IPv6) || Mobian (Megi's kernel 5.13.0-rc4, apt up-to-date) with Phosh, 2021-06-07<br />
|-<br />
| Germany || E-Plus || Yes (sending only 2G) || Not tested || Yes || Yes || Manjaro Phosh and postmarketOS, 2021-10-15<br />
|-<br />
| Germany || Telekom || Yes || Not tested || Yes || Not tested || Mobian Phosh (5.10-sunxi64), 2021-07-28<br />
|-<br />
| Germany || O2 / Telefonica || Yes || Not tested || Yes || Not tested || KPlasma<br />
|-<br />
| Hungary || Telekom || Yes || Not tested || Yes || Yes (IPv4) || Manjaro Phosh Beta 12, 2021-07-30<br />
|-<br />
| Hungary || Telenor || Yes || Not tested || Yes || Yes || Mobian-Phosh-20210517, 2021-09-24<br />
|-<br />
| Denmark || CBB || Yes || Not tested || Yes || Yes || Manjaro Plasma Mobile Beta 5, 2021-06-30<br />
|-<br />
| Belgium || Telenet || Yes || Not tested || Yes || Yes || postmarketOS v20.05, v21.03, v21.06 and edge, 2021-08-15<br />
|-<br />
| Belgium || CARREFOUR || Yes || Not tested || Yes || Yes || postmarketOS v20.05, v21.03, v21.06 and edge, 2021-08-15<br />
|-<br />
|}<br />
<br />
== North America ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| USA || T-Mobile || Yes || No || Yes || Yes || <br />
* Arch Linux Arm 2020/11/29 <br />
* Mobian - Phosh <br />
* Manjaro - KDE Plasma Mobile<br />
|-<br />
| USA || MetroPCS (T-Mobile) || Yes || No || Yes || Yes || <br />
*Arch Linux Arm (Phosh,SXMO) 2021/04/29 <br />
*Manjaro - Phosh 2021/04/29 <br />
*Mobian - Phosh 2021/3/20<br />
|-<br />
| USA || T-Mobile || Yes - buggy || No || Yes - buggy || Yes - buggy || <br />
*Manjaro - Plasma Dev 2020/11/21 <br />
*Ubuntu Touch - 2020/11/26 <br />
*KDE Neon 2020/11/02<br />
|-<br />
| USA || Mint Mobile (T-Mobile) || Yes || Not tested || Yes || Yes || <br />
*Mobian - Phosh 2021/3/14<br />
*postMarketOS - Phosh, Sxmo, Plasma Mobile 2021/5/26<br />
*Ubuntu Touch 2021/5/24<br />
|-<br />
| USA || Tello (T-Mobile) || Yes || No || Yes || Yes || <br />
*postMarketOS - Phosh 2021/8/15<br />
|-<br />
| USA || TracFone (T-Mobile) || Yes || Not tested || Yes || Yes || <br />
*Arch - Phosh 2021-10-06<br />
|-<br />
| USA || Verizon || Yes || Not tested || Yes || Yes || <br />
*Mobian - Phosh 2021/3/1<br />
|-<br />
| USA || Verizon || No || No || No || No ||<br />
*Ubuntu Touch 2021/5/24 (You can occasionally get the settings to work with Verizon, but it seems like the settings automatically changes the carrier to the wrong one after a few minutes) <br />
|-<br />
| USA || Verizon || Not tested || Not tested || Yes || Not via gui || <br />
*Manjaro - KDE Plasma Mobile 2021/5/10 <br />
|-<br />
| USA || Verizon || Yes || Not tested || Yes || Not via gui || <br />
*Manjaro - Phosh 2021/5/31 <br />
|-<br />
| USA || Verizon || Yes || Not tested || Yes || Yes || <br />
*postmarketOS - Phosh 2021/5/31 <br />
|-<br />
| USA || Verizon || Yes || Not tested || Yes || Yes || <br />
*Arch - Phosh 2021/5/31 <br />
|-<br />
| Canada || Freedom || Yes || Not tested || Yes || Yes || <br />
*Arch Pinephone - Phosh (APN: internet.windmobile.ca), 2021/4/25 <br />
|-<br />
| Canada || SpeakOut || Yes || Not tested || Yes || Not tested || <br />
*Mobian - Phosh 2021/11/18<br />
|-<br />
| USA || FaithWireless (AT&T) || Yes || No || Yes || Yes || <br />
*Arch Linux Arm - Phosh 2021/04/29 (version 0.10.1-1, see the [[PinePhone_Carrier_Support#AT.26T|AT&T issues]] below.)<br />
|-<br />
| USA || Consumer Cellular (AT&T) || Yes || No || Yes || Yes || <br />
*Manjaro - Phosh 2021/06/26<br />
|-<br />
| USA || Google Fi (T-Mobile) || Yes || No || Yes || Yes || <br />
*Arch Linux Arm - Phosh 0.10.2 2021/05/29<br />
|-<br />
| Mexico || Telcel || Yes || Not tested || Yes || Yes ||<br />
*PostmarketOS - sxmo edge 2021/09/09<br />
|-<br />
|}<br />
<br />
== South America ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129<br />
|-<br />
|}<br />
<br />
== Australia / Oceania ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129<br />
|-<br />
|}<br />
<br />
== Middle East ==<br />
{| class="wikitable sortable"<br />
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI<br />
|-<br />
|-<br />
| Israel|| Cellcom prepay|| receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
<br />
|-<br />
| Israel|| Golan TC || receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
|-<br />
| Israel|| Partner prepay || receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
|-<br />
| Israel|| Pelephone prepay|| receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
|-<br />
| Israel|| Hot prepay|| receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
|-<br />
| Israel|| 019 prepay|| No || NA ||Bars only || NA || on PmOS Sxmo May 14 2021.<br />
|-<br />
<br />
<br />
<br />
<br />
<br />
|}<br />
<br />
= Special carrier notes =<br />
<br />
{{Warning|This section contains providers which do not work or require special settings or actions to work.}}<br />
<br />
Some carriers might support only certain frequencies or might require certain settings in Ofono or ModemManager. The following is a list of collected notes for carriers regarding special settings, hints or information:<br />
<br />
== USA ==<br />
=== AT&T ===<br />
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page], AT&T's primary bands are 12 and 17 - 700ac and 700 MHz respectively. The PinePhone seems to work out-of-the-box with AT&T. If you transfer a SIM card from another phone you were using with AT&T, you need to activate the PinePhone through [https://www.att.com/buy/wireless/byod/byod AT&T's website]. Calls and SMS messages work. VoLTE is as yet untested.<br />
<br />
However, it is likely AT&T will drop support with their network upgrade in the near future like their child company Cricket Wireless already has. [https://www.att.com/ecms/dam/att/consumer/help/pdf/Devices-Working-on-ATT-Network.pdf This page] lists their supported devices for their new network.<br />
<br />
=== Consumer Cellular ===<br />
<br />
Consumer Cellular is a MVNO that uses both AT&T and T-Mobile networks. On the AT&T network LTE data works without special configuration. If you transfer a SIM card from another phone to the PinePhone, you may need to contact customer support in order for them to register the IMEI association to the correct hardware; in one case it was first incorrectly identified as a Samsung Google Nexus Prime before later being correctly identified by the modem model Quectel EG25-G. Customer support also explicitly enabled VoLTE on the device. After VoLTE instructions on this site were followed and APN instructions on the Consumer Cellular site were followed, VoLTE was confirmed working.<br />
<br />
=== Cricket Wireless ===<br />
Cricket wireless is a MVNO that uses AT&T's network. VoLTE was fully supported, but the PinePhone is no longer considered a compatible device in the US by the carrier (as of March 2021).<br />
<br />
=== SimpleMobile ===<br />
SimpleMobile is a T-Mobile prepaid MVNO operating in the United States. 4G LTE, VoLTE, data, and SMS all work on the PinePhone after activation. Activation can be done online without extra software or assistance, go to https://www.simplemobile.com/activation/byopcollectsim and make sure you have your SIM card and IMEI ready.<br />
<br />
=== Sprint ===<br />
Sprint is currently not supported due to unknown reasons. Any input regarding this issue is highly appreciated.<br />
<br />
=== T-Mobile ===<br />
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page],<br />
T-Mobile's primary frequency band for the United States is 12 (700ac MHz).<br />
<br />
T-Mobile's bands and protocols are summarized on<br />
[https://www.frequencycheck.com/carriers/t-mobile-united-states this page].<br />
<br />
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.<br />
<br />
=== Verizon ===<br />
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page],<br />
Verizon's primary frequency band for the United States is 13 (700 MHz). Verizon's bands and protocols are summarized on<br />
[https://www.frequencycheck.com/carriers/verizon-wireless-united-states this page]. According to the same page, Verizon might restrict their network to only approved devices.<br />
<br />
Some users reported that they were able to activate their Verizon SIM by using an Verizon-approved burner phone and then inserting the SIM into the PinePhone.<br />
<br />
=== Google Fi ===<br />
Only T-Mobile service works currently, not US Cellular or Sprint.<br />
The APN is h2g2.<br />
Information from [https://forum.pine64.org/showthread.php?tid=11675&page=7 the forum].<br />
<br />
Bear in mind that initial activation of the SIM card is not possible without an Android phone running Google Apps. <br />
<br />
It should also be noted that Google uses a non-standard MMS implementation that is unlikely to be supported on the PinePhone at any point.<br />
<br />
== Europe ==<br />
=== Telekom Germany ===<br />
With low signal, there may be loud interference noise audible in calls on the receiving end. It has not yet been tested whether or not this problem is carrier specific. An easy fix is extending the modem antenna with aluminum foil (or similar) inside the back cover of the phone.<br />
<br />
= Known issues =<br />
Known issues:<br />
* The [https://www.frequencycheck.com/models FrequencyCheck model page] does not list either Pine64 or the PinePhone.<br />
* T-Mobile's system does not list the PinePhone as a compatible device due to the lack of official VoLTE support from the manufacturer, despite the fact that it does work.<br />
* MMS doesn't currently work in any distribution on the PinePhone by default. This means images and group chats will not work in text messages.<br />
* Some providers may allow only certain known devices identified by their [https://en.wikipedia.org/wiki/Type_Allocation_Code Type Allocation Code].<br />
<br />
= MMS workarounds =<br />
These scripts allow partial MMS support on a [[PinePhone]]:<br />
<br />
* JMMS: [https://git.sr.ht/~amindfv/jmms]<br />
* silvermms: [https://gitlab.com/5ilver/silvermms]<br />
* MMS via Matrix with mmmpuppet: [[PinePhone MMS with Matrix]]<br />
<br />
There is a Haskel MMS client. MMS can also be manually composed with mmsd on the command line.<br />
<br />
= Resources =<br />
* IMEI - [https://en.wikipedia.org/wiki/International_Mobile_Equipment_Identity International Mobile Equipment Identity]<br />
<br />
<br />
[[Category:PinePhone]]</div>Tahayassenhttps://wiki.pine64.org/index.php?title=PinePhone&diff=10511PinePhone2021-05-25T06:22:12Z<p>Tahayassen: /* Battery */</p>
<hr />
<div>[[File:PinePhone Beta Edition.png|500px|thumb|right|Rendering of the PinePhone Beta Edition]]<br />
<br />
The '''PinePhone''' is a smartphone created by PINE64. It is capable of running mainline Linux and is supported by many partner projects.<br />
<br />
The Braveheart Edition of the PinePhone was the first publicly available version of the phone. It shipped without a fully functional operating system and was geared specifically towards early adopters. The Braveheart Edition's successors were the Community Editions, which featured a branded backcover and box of selected community projects. The Community Editions became available in June 2020. The Beta Edition featuring Manjaro with Plasma Mobile is the latest edition, it became available in March 2021.<br />
<br />
== Introduction ==<br />
<br />
The PinePhone is not a regular phone and you might not get the latest and greatest hardware and this years' newest innovation. You will get a device with good mainline support with a great community behind it.<br />
<br />
=== State of the software ===<br />
<br />
First things first, the PinePhone is aimed solely at early adopters - more specifically, the only intend for these units is to find their way into the hands of users with extensive Linux experience.<br />
<br />
Bear in mind that the software for Linux on phones is very early, with most of the software being in alpha or beta state. That's especially also the case for scalability of applications, their availability and practicability, any hardware function implementations and the firmware. The software is provided as is. There is no warranty for the software, not even for merchantability or fitness for a particular purpose.<br />
<br />
If you have any questions regarding the current state of the software or of specific features working, please don't hesitate to ask in the community chat (see [[Main Page#Community and Support]])!<br />
<br />
=== Help and support ===<br />
<br />
For any questions regarding the phone please regard the contents of this wiki page, including linked articles further below. Still have any questions regarding software, shipping or ordering? Please don't hesitate to contact the community in the bridged community channels for detailed answers and to chat with friendly people, see [[Main Page#Community and Support]]. <br />
<br />
Mind that PINE64 is not like a regular company (see [https://www.pine64.org/philosophy/ PINE64 philosophy]) and that support resources are spare - the preferred way to get support quickly (issues are best solved in they're solved without delay!) is to ask in the community chat and to only contact PINE64 directly if questions couldn't be solved via the chat. The community is happy to help with any issue.<br />
<br />
== First time installation ==<br />
<br />
{{Hint|The Beta Edition comes with SSH enabled by default and a weak SSH password. It is highly recommend to disable SSH or to switch to key-based SSH authentication.}}<br />
<br />
When shipped the battery is isolated from the device using a protective plastic tab, which is required to be removed before using the phone. The battery '''will not''' charge until this is removed and the modem, WiFi and Bluetooth will not work until the battery is connected.<br />
<br />
The PinePhone's SIM slot only accepts a micro SIM, please do not insert a nano SIM without an adapter. An adapter from a nano to a micro SIM might be included under tape in the camera notch of the phone's packaging. The SIM card has to be placed in the lower slot, while the microSD has to be placed in the upper slot.<br />
<br />
To remove the sticker after unboxing the phone:<br />
<br />
# Carefully remove the back panel using the notch in the corner of the back cover without overbending it<br />
# Remove the battery (if the battery is stuck in the device please check [[PinePhone_FAQ#The_battery_is_stuck_inside_the_phone|this]] paragraph for a fix)<br />
# Peel off the clear plastic sticker below it, which isolates the charging contacts<br />
# Reinsert the battery<br />
<br />
<gallery mode="nolines" widths="400px" heights="400px"><br />
Image:Pinephone_warning.png|A protection foil isolates the battery for the shipping.<br />
Image:Pinephone_backside.png|The microSD belongs in the upper slot, the micro SIM in the lower slot.<br />
</gallery><br />
<br />
== Operating Systems ==<br />
<br />
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.<br />
<br />
=== Software releases ===<br />
<br />
The [[PinePhone Software Releases]] page has a complete list of currently supported phone-optimized Operating System images that work with the PinePhone as well as other related software information. As soon as more patches get mainlined and distributions ship with the updated kernel, they will also be able to run unmodified on the device. To update any installed operating system please see [[PinePhone Updating Instructions]].<br />
<br />
=== Installation instructions ===<br />
<br />
For instructions on how to install the operating systems to the eMMC or SD card see [[PinePhone Installation Instructions]].<br />
<br />
Relevant subsections of the article for installing OSes to the PinePhone are:<br />
<br />
* [[PinePhone Installation Instructions#Boot_priority|Boot priority]]<br />
* [[PinePhone Installation Instructions#Installation_to_the_microSD|Installation to the microSD]]<br />
* [[PinePhone Installation Instructions#Installation_to_the_eMMC|Installation to the eMMC]]<br />
* [[PinePhone Installation Instructions#Resize_partition_to_fit_disk_space|Resize partition to fit disk space]]<br />
* [[PinePhone Installation Instructions#Reuse_SD_card_for_data_storage_on_system_booting_from_eMMC|Reuse SD card for data storage on system booting from eMMC]]<br />
<br />
== Specifications ==<br />
<br />
* '''Dimensions:''' 160.5 x 76.6 x 9.2mm<br />
* '''Weight:''' Between 180 ~ 200 grams<br />
* '''SIM Card:''' Micro-SIM<br />
* '''Display:'''<br />
** '''Size:''' 5.95 inches (151mm) diagonal<br />
** '''Type:''' HD IPS capacitive touchscreen, 16M colors<br />
** '''Resolution:''' 1440x720, 18:9 ratio<br />
* '''System on Chip:''' [https://linux-sunxi.org/A64 Allwinner A64]<br />
* '''RAM:''' 2GB or 3GB LPDDR3 SDRAM<br />
* '''Internal Storage:''' 16GB or 32GB eMMC, extendable up to 2TB via microSD, supports SDHC and SDXC<br />
* '''Back [[#Camera|Camera]]:''' Single 5MP, 1/4", LED Flash<br />
* '''Front Camera:''' Single 2MP, f/2.8, 1/5"<br />
* '''Sound:''' Loudspeaker, 3.5mm jack & mic (jack doubles as hardware UART if killswitch 6 is deactivated)<br />
* '''Communication:'''<br />
** '''[[#Modem|Modem]]:''' [https://www.quectel.com/product/lte-eg25-g/ Quectel EG25-G]<br />
** '''LTE-FDD''': B1, B2, B3, B4, B5, B7, B8, B12, B13, B18, B19, B20, B25, B26, B28<br />
** '''LTE-TDD''': B38, B39, B40, B41<br />
** '''WCDMA''': B1, B2, B4, B5, B6, B8, B19<br />
** '''GSM''': B2, B3, B5, B8 (850, 900, 1800, 1900 MHz)<br />
** '''WLAN:''' Wi-Fi 802.11 b/g/n, single-band, hotspot<br />
** '''Bluetooth:''' 4.0, A2DP<br />
** '''GNSS:''' GPS/GLONASS/BeiDou/Galileo/QZSS, with A-GPS<br />
* '''Sensors:''' Accelerometer, gyroscope, proximity, ambient light, compass<br />
* '''Killswitches:''' Modem, WiFi & Bluetooth, Microphone, Cameras<br />
* '''[[#Battery|Battery]]:''' Lithium-ion, rated capacity 2800mAh (10.64Wh), typical capacity 3000mAh (11.40Wh) (nominally replaceable with any Samsung J7 form-factor battery)<br />
* '''I/O:''' USB Type-C, USB Host, DisplayPort Alternate Mode output, 15W 5V 3A Quick Charge, follows USB PD specification<br />
<br />
== Components ==<br />
<br />
{| class="wikitable"<br />
! Component<br />
! Model<br />
|-<br />
| Touchscreen<br />
| Goodix GT917S<br />
|-<br />
| Rear camera<br />
| OmniVision OV5640<br />
|-<br />
| Camera flash<br />
| SGMICRO SGM3140<br />
|-<br />
| Front camera<br />
| GalaxyCore GC2145<br />
|-<br />
| LCD<br />
| Xingbangda XBD599<br />
|-<br />
| WiFi<br />
| Realtek RTL8723CS<br />
|-<br />
| Bluetooth<br />
| Realtek RTL8723CS<br />
|-<br />
| Modem<br />
| [http://static.abstore.pl/design/accounts/soyter/img/dokumentacje/quectel_eg25-g.pdf Quectel EG25-G]<br />
|-<br />
| GNSS/GPS<br />
| [http://static.abstore.pl/design/accounts/soyter/img/dokumentacje/quectel_eg25-g.pdf Quectel EG25-G]<br />
|-<br />
| Magnetometer<br />
| ST LIS3MDL<br />
|-<br />
| Ambient light / Proximity<br />
| SensorTek STK3335<br />
|-<br />
| Accelerometer / Gyroscope<br />
| InvenSense MPU-6050<br />
|-<br />
| Vibration motor<br />
| Unknown model<br />
|-<br />
| Notification LED<br />
| LED0603RGB<br />
|-<br />
| Volume buttons<br />
| Buttons connected to the KEYADC<br />
|-<br />
| Power button<br />
| X-Powers AXP803<br />
|-<br />
| Battery fuel gauge<br />
| X-Powers AXP803<br />
|}<br />
<br />
See the [[PinePhone_component_list|PinePhone Component List]].<br />
<br />
== Hardware revisions ==<br />
<br />
The following are all hardware revisions of the PinePhone that have existed, ordered by the time of their releases:<br />
<br />
* [[Project Anakin]]<br />
* [[Project Don't be evil|"Project Don't Be Evil"]] &ndash; development kit (devkit)<br />
* [[PinePhone v1.0 - Dev|PinePhone v1.0]] &ndash; developer batch<br />
* [[PinePhone v1.1 - Braveheart|PinePhone v1.1]] &ndash; Braveheart<br />
* [[PinePhone v1.2]] &ndash; Ubports Community Edition<br />
* [[PinePhone v1.2a]] &ndash; postmarketOS Community Edition<br />
* [[PinePhone v1.2b]] &ndash; Manjaro Community Edition, KDE Community Edition, Mobian Community Edition, and Beta Edition<br />
<br />
== Hardware accessory ==<br />
<br />
=== PinePhone hardware accessory compatibility ===<br />
See [[PinePhone Hardware Accessory Compatibility]] for a list of devices working with the PinePhone (depending on their OS support).<br />
<br />
=== USB-C connector ===<br />
<br />
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.<br />
<br />
=== Pogo pins ===<br />
<br />
[[File:Pinephone pogo.png|400px|thumb|right|The pogo pins, as visible under the back cover.]]<br />
<br />
The PinePhone has six pogo pins on the back allowing for custom hardware extensions such as wireless charging, an IR blaster, a keyboard extension or extended battery case. The pogo pins provide access to an interrupt line, power inputs/outputs and an I2C interface.<br />
<br />
{| class="wikitable"<br />
| Interrupt<br />
| SDA<br />
| SCL<br />
|-<br />
| DCIN<br />
| USB-5V<br />
| GND<br />
|}<br />
<br />
DCIN and USB-5V are the names used in the schematics. The actual behavior of these pogo pins is not obvious based on their names. DCIN is connected both to the VBUS line of the USB Type-C connector, and to the ACIN/VBUS inputs on the PMIC. This means that, depending on a number of factors, DCIN may be at 0&nbsp;V or 5&nbsp;V. USB-5V is connected at the output of an LP6226 DC/DC boost converter (5&nbsp;V), which in turn is fed by the PS output of the PMIC. The boost converter is enabled or disabled by a GPIO output from the A64 SoC, controlled by software (e.g. the Linux kernel). Depending on inputs and decision made by the PMIC, PS may be at the battery voltage (fed "directly" by the battery through a transistor controlled by the PMIC), or at the "USB" voltage (fed by the PMIC's ACIN/VBUS inputs). This means that depending on a number of factors, USB-5V may be at battery voltage (between 3.0&nbsp;V and 4.3&nbsp;V), or at 5&nbsp;V.<br />
<br />
Because the PinePhone may act as a USB host (providing 5&nbsp;V at the USB Type-C connector's VBUS to a connected device) or as a USB device (drawing from a 5&nbsp;V source on the USB Type-C connector's VBUS), DCIN is actually not strictly an input nor an output. Some community analysis of the PinePhone schematic (and some testing) indicates that you can connect a 5&nbsp;V power supply to DCIN in order to power the phone at the PMIC's ACIN/VBUS inputs (and, as a side effect, charge the battery). This may not be safe to do in all conditions, e.g., when the phone is acting as a USB host to a connected USB device. It should also be safe to use DCIN as a power output from the PinePhone, e.g., when a USB Type-C charger is connected, you can draw current directly from the USB Type-C port's VBUS, which is provided by the charger. Please note that, when using DCIN as an output from the PinePhone, DCIN isn't "always on"; it may be 0&nbsp;V. It is currently not documented on how much current can be safely drawn.<br />
<br />
USB-5V should be safe to use as an "always on" power output from the PinePhone. Depending on a number of factors, voltage may be from 3&nbsp;V to 5&nbsp;V; thus, if you are using USB-5V to power your pogo-pins expansion board, you will probably need to use DC/DC converters/regulators as appropriate. USB-5V is on even while the A64 SoC is powered down.<br />
<br />
The I2C and interrupt lines have pull-ups on the phone side. The I2C lines are pulled up to 3v3 by the phone.<br />
<br />
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/ <i>"Making a backcover extension for the PinePhone"</i>].<br />
<br />
Pine64 store currently sells the [https://pine64.com/product/pinephone-flex-break-out-board/?v=0446c16e2e66 PinePhone Flex Breakout Board]. With the pitch being 2.54 mm, this Flex Breakout Board may have leads soldered directly to the contacts for use in a solderless board. A non-soldered solution would be to use a [https://www.digikey.com/en/products/detail/te-connectivity-amp-connectors/5-520315-6/2258879 TE AMP Connector] that will accept a Flat Flexible Cable 2.54 mm pitch.<br />
<br />
=== Back cover ===<br />
A step file for the back cover for creating custom cases is freely available [https://files.pine64.org/doc/PinePhone/PinePhone%20Back%20Cover%20ver%200.5.stp here].<br />
<br />
=== Community-built accessories ===<br />
* [https://www.thingiverse.com/thing:4654013 PinePhone Development Stand at Thingverse]<br />
* [https://www.thingiverse.com/thing:4658870 PinePhone Hard Case by _The3DmaN_ at Thingverse]<br />
* [https://www.thingiverse.com/thing:4651177 PinePhone Hard Case by blitzaxt at Thingverse]<br />
<br />
=== Serial console ===<br />
<br />
[[File:PinePhone_Serial_Cable.png|400px|thumb|right|Pinout of the serial adapter.]]<br />
<br />
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.<br />
<br />
The UART is 115200n8.<br />
<br />
The pinout for the serial connector is:<br />
<br />
* Tip: RX<br />
* Ring: TX<br />
* Sleeve: GND<br />
<br />
You can buy a serial debug cable from the [https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/ Pine64 Store]. The store cable uses a 4 ring plug, as seen in the [https://files.pine64.org/doc/pinebook/guide/Pinebook_Earphone_Serial_Console_Developer_Guide.pdf here], but a 3 ring plug works just as well. The cable uses a CH340 chipset based serial to USB converter, but any 3.3v serial connection can be used. Because it is a "host"/DTE it means that you need a ''cross modem cable'' ([https://en.wikipedia.org/wiki/Null_modem Null Modem]) with TX on Tip to be connected to RX. A cable like e.g. [https://www.ftdichip.com/Products/Cables/USBTTLSerial.htm FTDI TTL-232R-3V3-AJ] which has TX on Tip and RX on Ring fits perfectly.<br />
<br />
== Killswitch configuration ==<br />
<br />
[[File:PinePhone Kill Interruptors de Maquinari del PinePhone 4529.jpg|320px|thumb|right|Detail of DIP switch]]<br />
<br />
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.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Number<br />
! Name<br />
! Explanation<br />
! Description<br />
|-<br />
| 1<br />
| Modem<br />
| Pulls Q1501 gate up (FET killing modem power)<br />
| "On" enables 2G/3G/4G communication and GNSS hardware, "off" disables it.<br />
|-<br />
| 2<br />
| WiFi / Bluetooth<br />
| Pulls up CHIP_EN<br />
| "On" enables WiFi and Bluetooth communication hardware, "off" disables it.<br />
|-<br />
| 3<br />
| Microphone<br />
| Breaks microphone bias voltage from the SoC<br />
| "On" enables audio input from on-board microphones (not 3.5 mm jack), "off" disables it.<br />
|-<br />
| 4<br />
| Rear camera<br />
| Pulls up PWDN on OV5640 <br />
| "On" enables the rear camera, "off" disables it.<br />
|-<br />
| 5<br />
| Front camera<br />
| Pulls up PWDN on GC2145<br />
| "On" enables the front camera, "off" disables it.<br />
|-<br />
| 6<br />
| Headphone<br />
| Pulls up IN2 on analog switch BCT4717ETB<br />
| "On" enables audio input and output via the 3.5 mm audio jack, "off" switches the jack to hardware UART mode.<br />
|}<br />
<br />
== Camera ==<br />
<br />
The PinePhone has two cameras, OmniVision OV5640 with 5MP (up to 2592 x 1944 pixels) as rear camera and GalaxyCore GC2145 with 2MP (up to 1600 x 1200 pixels) as front camera.<br />
<br />
[[File:Rose.jpg|400px|thumb|none|Example picture taken on the PinePhone's rear camera by Martijn Braam using his app ''Megapixels''.]]<br />
<br />
Further details regarding the camera and the Megapixels camera app can be found on [https://blog.brixit.nl/tag/phones/ Martijn's blog].<br />
<br />
== Battery ==<br />
{{Hint|The EG25-G modem and the RTL8723CS WiFi and Bluetooth combo do not work without battery power, even when enough power is supplied to the PinePhone via the USB Type-C port.}}<br />
<br />
The phone ships with a protective plastic sticker between the battery and the phone to protect the device from turning on during shipping.. You need to gently open the back cover, then remove the battery and finally remove the sticker and check that the pins aren't bent. Note: If the battery is stuck inside the phone, the mid screw in the lower part of the midframe needs to be slightly loosened, see [[PinePhone_FAQ#The_battery_is_stuck_inside_the_phone|here]].<br />
<br />
The [https://files.pine64.org/doc/datasheet/pinephone/PinePhone%20QZ01%20Battery%20Specification.pdf supplied battery] is meant to be compatible with Samsung part number EB-BJ700BBC / BBE / CBE with dimensions 76.17 x 63.23 x 4.71 mm from the 2015 J7 phone. The extended life aftermarket BBU does fit, although it is a tight fit.<br />
<br />
The battery terminals, from the nearest to the battery edge to the nearest to the middle of battery, are as follows:<br />
<br />
{| class="wikitable" <br />
| style="min-width: 90px; text-align: center;" | +ve<br />
| style="min-width: 90px; text-align: center;" | thermistor<br />
| style="min-width: 90px; text-align: center;" | -ve<br />
| style="min-width: 90px; text-align: center;" | not connected<br />
|}<br />
<br />
The battery includes a protection circuit that isolates it in a number of fault conditions, including if it is discharged too far. The fully discharged battery can be recharged by connecting the phone to a charger with a sufficient output. Once it has charged sufficiently you will be able to boot the phone.<br />
<br />
== Modem ==<br />
The PinePhone uses Quectel EG25-G as modem. AT commands are used to communicate with the modem. The software <code>minicom</code> can be used to send the commands under Linux.<br />
<br />
To connect with the modem under Linux:<br />
<br />
<pre><br />
minicom -D /dev/ttyUSB2<br />
</pre><br />
<br />
=== AT commands ===<br />
<br />
A list of documented AT commands can be found in the [https://www.quectel.com/UploadImage/Downlad/Quectel_EC25&EC21_AT_Commands_Manual_V1.3.pdf EC25&EC21 AT Commands Manual] from Quectel. Further undocumented AT commands found by the developer megi, who reverse-engineered parts of the modem and its firmware, can be found on megi's website [http://xnux.eu/devices/feature/modem-pp-reveng.html#toc-un-der-documented-at-commands here].<br />
<br />
=== VoLTE ===<br />
<br />
The PinePhone's modem supports VoLTE and comes with a few VoLTE profiles preloaded. Most OSes try to set the correct profile automatically.<br />
<br />
To list the available VoLTE profiles:<br />
<br />
<pre><br />
AT+QMBNCFG="list"<br />
<br />
+QMBNCFG: "List",0,1,1,"ROW_Generic_3GPP",0x0501081F,201901141<br />
+QMBNCFG: "List",1,0,0,"VoLTE-ATT",0x0501033C,201909271<br />
+QMBNCFG: "List",2,0,0,"hVoLTE-Verizon",0x05010141,201911251<br />
+QMBNCFG: "List",3,0,0,"Sprint-VoLTE",0x05010205,201908141<br />
+QMBNCFG: "List",4,0,0,"Commercial-TMO_VoLTE",0x05010505,201811231<br />
+QMBNCFG: "List",5,0,0,"Telus-Commercial_VoLTE",0x05800C43,201912031<br />
+QMBNCFG: "List",6,0,0,"Commercial-SBM",0x05011C18,201904021<br />
+QMBNCFG: "List",7,0,0,"Commercial-DT",0x05011F1C,201905311<br />
+QMBNCFG: "List",8,0,0,"Reliance_OpnMkt",0x05011B38,201910161<br />
+QMBNCFG: "List",9,0,0,"TF_Germany_VoLTE",0x05010C1B,201909201<br />
+QMBNCFG: "List",10,0,0,"TF_Spain_VoLTE",0x05010CFA,201909261<br />
+QMBNCFG: "List",11,0,0,"Volte_OpenMkt-Commercial-CMCC",0x05012071,201904281<br />
+QMBNCFG: "List",12,0,0,"OpenMkt-Commercial-CT",0x05011322,201911081<br />
+QMBNCFG: "List",13,0,0,"OpenMkt-Commercial-CU",0x05011505,201807052<br />
</pre><br />
<br />
To select a profile manually, select the best fitting one or a generic one if none fits:<br />
<br />
<pre><br />
AT+QMBNCFG="select","ROW_Generic_3GPP"<br />
</pre><br />
<br />
Then enable Voice over LTE using:<br />
<br />
<pre><br />
AT+QCFG="ims",1<br />
</pre><br />
<br />
And reboot the modem to apply the settings:<br />
<br />
<pre><br />
AT+CFUN=1,1<br />
</pre><br />
<br />
To check the status of VoLTE during a call, the AT command <code>CLCC</code> can be used:<br />
<br />
<pre><br />
AT+CLCC<br />
<br />
+CLCC: 1,1,0,1,0,"",128<br />
+CLCC: 2,1,0,1,0,"",128<br />
</pre><br />
<br />
=== APN settings ===<br />
<br />
The APN setting is only required for a public Internet connection ("data") on the phone. For tested APN settings and how to apply them see [[PinePhone APN Settings]].<br />
<br />
=== Carrier support ===<br />
The page [[PinePhone Carrier Support]] contains information about the frequency support of different carriers and hints on setting up cellular network connectivity.<br />
<br />
=== Documents ===<br />
<br />
Detailed information about the modem can be found on the [https://xnux.eu/devices/feature/modem-pp.html#toc-modem-on-pinephone page of the developer megi], including reverse-engineered parts of the firmware and its functions. There is also a document about using the modem from January 18th 2020 by megi [https://megous.com/dl/tmp/modem.txt here]. A script at the end of the document showcases a way to poweroff the modem before powering off the phone, which is integrated into most of the available OSes.<br />
<br />
=== Firmware update ===<br />
<br />
{{Hint|The following instructions are directed towards professional users. It is highly recommend to make sure the update process is not interrupted to prevent the modem from bricking.}}<br />
<br />
The modem firmware can be updated to the latest version if it is outdated and ''dmesg'' returns the following message:<br />
<br />
<pre>modem-power serial1-0: Your modem has an outdated firmware. Latest know version is EG25GGBR07A08M2G_01.002.07. Consider updating.</pre><br />
<br />
'''Pre-update checklist:'''<br />
<br />
Please make sure all requirements of the checklist are fulfilled. If the update process is interrupted it will lead to a corrupted firmware of the modem, causing it to brick. Recovering a bricked modem is exponentially more complicated and requires the user to boot a special mode by physically bridging test points on the modem.<br />
<br />
* The battery needs to be charged sufficiently<br />
* The phone needs to be plugged into a charger<br />
* Deep sleep is recommended to be disabled as it can interrupt the update process<br />
* It is recommended to close all other running applications<br />
* Use common sense while doing the update, don't do the update while being impaired in any way<br />
<br />
To get the latest firmware, clone the repository of user Biktorgj on the phone:<br />
<br />
<pre>git clone https://github.com/Biktorgj/quectel_eg25_recovery</pre><br />
<br />
After cloning the directory, open it with cd:<br />
<br />
<pre>cd quectel_eg25_recovery</pre><br />
<br />
Then run qfirehose, which starts the flashing process:<br />
<br />
<pre>sudo ./qfirehose -f ./</pre><br />
<br />
The modem will automatically reboot after the update process is done. The boot process takes around 30 to 60 seconds. After that it is highly recommended to reboot the device.<br />
<br />
=== Firmware modifications ===<br />
<br />
See [[PineModems]] for more information regarding modem bootloader unlocking, building a custom modem firmware and modem recovery.<br />
<br />
=== GPS / GNSS ===<br />
The GPS engine in the modem supports mutli-GNSS reception from GPS, GLONASS, BeiDou, Galileo and QZSS independent of a cellular connection. The operation of the GNSS subsystem is controlled via a separate set of AT commands. The AGPS data upload uses the file management AT commands, which also have their own manual. These are linked in the [[PinePhone#Datasheets for components and peripherals|documentation section]] below.<br />
<br />
As with most smartphones, the PinePhone has a small antenna and has difficulty getting a first fix without assistance data, a cold start can take 15 minutes under good conditions. While the hardware supports AGPS data upload, it isn't yet implemented in current distributions. There is a [https://gist.github.com/alastair-dm/263209b54d01209be28828e555fa6628 proof of concept script] which can be made to work, but support needs to be added to ModemManager, oFono etc. before it will be easy to use.<br />
<br />
Basic testing of GNSS reception can be done by using the AT command interface (/dev/ttyUSB2) from a terminal progam like minicom and the data output interface (/dev/ttyUSB1) to feed NMEA data into gpsmon or some other progam that can parse standard NMEA sentences.<br />
<br />
[[File:Gpsmon eg25g.png|400px|thumb|none|gpsmon decoding GPS data from /dev/ttyUSB1]]<br />
<br />
To check if GNSS data output is enabled, you can<br />
<br />
cat /dev/ttyUSB1<br />
<br />
this should display a stream of NMEA sentences<br />
<br />
$GPVTG,,T,,M,,N,,K,N*2C<br />
$GPGSA,A,1,,,,,,,,,,,,,,,,*32<br />
$GPGGA,,,,,,0,,,,,,,,*66<br />
<br />
=== Voice mail ===<br />
<br />
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<br />
<br />
In America, AT&T also has support for accessing your voicemail via an external phone number: https://www.att.com/support/article/wireless/KM1009101/<br />
<br />
In Canada, Rogers voicemail can be called by dialing *98<br />
<br />
== Safety ==<br />
=== Thermal Safety ===<br />
<br />
With the Allwinner A64 being an older generation SoC with a large 40nm chip, the phone produces quite some heat with medium or higher use and especially also during charging or when using USB accessories, like a docking station. Measurements to prevent damage to the phone and to its surroundings need to be taken by the user. This includes especially a proper handling of the phone: do not charge the phone in a way where heat builds up around the phone without being able to escape. Especially don't charge your phone under a pillow, blankets, in pockets or bags. Charging the phone produces heat and charging the phone in a way, where the excessive heat can't dispose around the phone poses an immediate fire risk.<br />
<br />
The user might notice that the phone gets warm under usage, compared to phones with more up-to-date hardware. Under normal circumstances these temperatures don't pose a risk while being in the levels within the safe operating temperatures (which lay far beyond the point where components can be too hot to touch). Higher temperatures might especially be experienced on the top side of the screen and on the inside of the phone at the RF shield of the modem. The higher temperature of the RF shield of the modem is commonly caused by the SoC on the opposite side of the mainboard, the RF shield of the modem is used to disperse heat of the SoC. In newer mainboard revisions starting from 1.2a there are also thermal pads on the back cover and between the SoC's RF shield and the screen, dispersing heat on the screen and on the back cover. In the past there has been safety issues regarding thermal safety functions, causing temperature reads to not properly work over an extended period of time, which was causing heat damage in some cases (see the documentation of that issue by the developer Megous [http://xnux.eu/log/#018 here] and [http://xnux.eu/log/#017 here]). While the developers are working hard to prevent such issues, they can't be excluded under all circumstances (see [[PinePhone#State_of_the_software|state of the software]]). The users are expected to monitor their phones' thermal safety at every point at this state of the software.<br />
<br />
It is highly recommend to update the phone on a regular basis to always get the latest improvements. The default settings to throttle the performance and to shut down the phone when reaching critical temperatures might be set to a too high point depending on the specific usage and usage length. Under GNU/Linux the phone's thermal management behavior can be modified via the Thermal Sysfs driver to achieve lower temperatures and preventing the screen and other components to potentially take damage, see [[PinePhone Thermal Tweaks]] for the details.<br />
<br />
== Frequently asked questions ==<br />
<br />
For a list of frequently asked questions (including information regarding the shipping) see [[PinePhone FAQ]].<br />
<br />
== Modifications and repairs == <br />
<br />
=== Swapping in a new mainboard revision ===<br />
<br />
The mainboard can be replaced, for example for upgrading to a newer hardware revision or if it is faulty. The replacement board does not have an OS preinstalled, to test if everything is working after swapping the mainboard a flashed SD card is required. The mainboard also comes with a non-functional firmware on the ANX chip, a newer firmware version has to be flashed as explained below to get certain USB functionality to work.<br />
<br />
==== Replacing the mainboard ====<br />
<br />
{{Hint|Replacement boards come with an empty eMMC, which means that trying to boot from them looks like the board is faulty (no LEDs, no screen, no reaction of the phone). Please boot an OS from SD card.}}<br />
<br />
Prior to replacing your PinePhone’s mainboard please read the steps outlined in bullet points below and watch the attached video.<br />
<br />
# You’ll need a small Phillip’s screwdriver and a prying tool to swap out the PinePhone’s mainboard.<br />
# Remove the PinePhone’s back cover. See your quick start guide for details.<br />
# Remove the battery as well as any inserted SD and SIM cards.<br />
# Unscrew all 15 Phillip’s head screws around the midframe of the phone.<br />
# Gently pry up the midframe using a guitar pick or credit card corner. It is easiest to separate the midframe at one of the bottom edges. Work your way around all the sides of the phone until the midframe separates from the phone’s body.<br />
# Detach all ribbon cables and “Lego” connectors. List of things to detach: 1) two “Lego” connects at the bottom of the mainboard. 2) u.FL antenna connect and touchscreen digitizer on PCD left side. 3) LCD ribbon cable top of mainboard, next to audio/ UART jack.<br />
# Pry the mainboard up gently from the left-hand side.<br />
# Remove front and main cameras and reset them into the new mainboard.<br />
# Check that the rubber proximity sensor housing is in the chassis, not stuck to the removed mainboard.<br />
# Place the new mainboard in the chassis, hooking in on the plastic tabs on left side and pressing down firmly on opposite side, and follow the steps (7-2) in reverse. When reattaching the midframe take care that no cables are out of place or trapped, as they may be damaged when tightening screws.<br />
<br />
After swapping the mainboard the phone won't boot as there is no OS on the replacement board's eMMC preinstalled. To boot an OS insert a flashed SD card.<br />
<br />
A video tutorial by <i>Martijn Braam</i> can be found here (or alternatively a video tutorial by user <i>brigadan</i> with additional notes about the camera swap and proximity sensor isolator [https://www.youtube.com/watch?v=J3AJEF7akkw here]):<br />
[[File:Pinephone_martijn_pcb_replacement.png|thumb|none|600px|link=https://www.youtube.com/watch?v=5GbMoZ_zuZs|Watch Martijn Braam's video tutorial here: https://www.youtube.com/watch?v=5GbMoZ_zuZs.]]<br />
<br />
==== Flashing the ANX firmware ====<br />
<br />
===== Method 1 =====<br />
<br />
After swapping the mainboard the ANX7688 chip has to be flashed for full USB functionality.<br />
<br />
Download the latest ANX7688 firmware image on the phone:<br />
<br />
wget https://xff.cz/git/linux-firmware/plain/anx7688-fw.bin<br />
<br />
Execute as root ("sudo su") on the phone:<br />
<br />
cp anx7688-fw.bin /lib/firmware/<br />
echo 1 > /sys/class/typec/port0/device/flash_eeprom<br />
<br />
===== Method 2 =====<br />
<br />
Booting a factory test image will automatically flash the ANX7688 chip. See [[PinePhone Software Releases#Factory-loaded postmarketOS build]] for such an image.<br />
<br />
=== Replacing the screen ===<br />
<br />
Before attempting to replace the screen be sure to review the section on [[#Swapping in a new mainboard revision|replacing the mainboard]] since that will get you most of the way there. Be aware that the replacement screen is actually the entire front frame of the phone and there are components that will need to be swapped from your old screen.<br />
<br />
* Make sure you have a precision screwdriver set that has the correct size Philips tip. The screws are very small and the heads can easily be stripped if the screwdriver is not correct - if you feel your screwdriver slipping, stop what you are doing and try one that is a better fit. A magnetized screwdriver will help in not losing screws, as will a magnetic parts holder to keep them in while working.<br />
<br />
* There are a number of components and cables as well as the insulator sheet under the battery that are glued in place. A hair dryer will loosen the glue and make them much easier to remove. You may want to order extra cables along with the screen just in case.<br />
<br />
* The vibration motor, which is part of the USB-C board assembly and glued into place, will come apart easily and be damaged if you pry it up in the wrong place. Make sure you pry from underneath the complete part, not midway on its housing. The ribbon cable attaching this to the USB-C board is small, thin, and fragile so be careful with that as well.<br />
<br />
* The new screen comes with new side switches and insulator sheet but there are a number of parts that need to be transferred from the old screen, like the thin coax cable running up the side, the phone ear speaker, proximity sensor gasket, and a gold-colored mesh glued in place that needs to be transferred to a flexible circuit included on the new screen. If you don't swap over the proximity sensor rubber gasket the screen will immediately turn off after logging in. Be careful when routing the coax cable that it goes around the screw holes or you may drive a screw right through the cable.<br />
<br />
Take your time, use the right tools, be careful and you should be rewarded with success.<br />
<br />
=== Spare parts not available in the Pine64 store ===<br />
<br />
* Earpiece dimensions: 12x6x2 mm. Compatible with Xiaomi Mi2 / Mi3 / Mi4, Lenovo A536 and others, see [https://forum.pine64.org/showthread.php?tid=12046&pid=85698#pid85698 here]<br />
* Loudspeaker dimensions: 15x11x3 mm. Compatible with Nokia N91, Lenovo A536 and others, see [https://forum.pine64.org/showthread.php?tid=12046&pid=85698#pid85698 here]<br />
* Proximity sensor rubber isolator<br />
<br />
== Press ==<br />
<br />
For an overview about media of the PinePhone you can use for the news, blogs, or similar see [[PinePhone Press]].<br />
<br />
== PinePhone board information, schematics and certifications ==<br />
<br />
* PinePhone mainboard schematic:<br />
** [https://files.pine64.org/doc/PinePhone/PinePhone%20v1.2b%20Released%20Schematic.pdf PinePhone mainboard Released Schematic ver 1.2b]<br />
** [https://files.pine64.org/doc/PinePhone/PinePhone%20v1.2a%20Released%20Schematic.pdf PinePhone mainboard Released Schematic ver 1.2a]<br />
** [https://files.pine64.org/doc/PinePhone/PinePhone%20v1.2%20Released%20Schematic.pdf PinePhone mainboard Released Schematic ver 1.2]<br />
** [[PinePhone_v1.2|PinePhone schematic ver 1.2 change list]]<br />
** [https://files.pine64.org/doc/PinePhone/PinePhone%20Schematic%20v1.1%2020191031.pdf "Braveheart" PinePhone mainboard Schematic ver 1.1]<br />
** [https://files.pine64.org/doc/PinePhone/PinePhone%20mainboard%20top%20placement%20v1.1%2020191031.pdf "Braveheart" PinePhone mainboard component top placement drawing ver 1.1]<br />
** [https://files.pine64.org/doc/PinePhone/PinePhone%20mainboard%20bottom%20placement%20v1.1%2020191031.pdf "Braveheart" PinePhone mainboard component bottom placement drawing ver 1.1]<br />
** [[PinePhone component list]]<br />
* PinePhone USB-C small board schematic:<br />
** [https://files.pine64.org/doc/PinePhone/PinePhone%20USB-C%20small%20board%20schematic%20v1.0%2020190730.pdf PinePhone USB-C small board Schematic ver 1.0]<br />
** [https://files.pine64.org/doc/PinePhone/PinePhone%20USB-C%20small%20board%20top%20placement%20v1.0%2020190730.pdf PinePhone USB-C small board component top placement drawing ver 1.0]<br />
** [https://files.pine64.org/doc/PinePhone/PinePhone%20USB-C%20small%20board%20bottom%20placement%20v1.0%2020190730.pdf PinePhone USB-C small board component bottom placement drawing ver 1.0]<br />
* PinePhone certifications:<br />
** [https://files.pine64.org/doc/cert/PinePhone%20FCC%20SDOC%20Certificate-S19112602605001.pdf PinePhone FCC Certificate]<br />
** [https://fcc.report/FCC-ID/2AWAG-PINEPHONE RF Exposure SAR Information from FCC ID site]<br />
** [https://files.pine64.org/doc/cert/PinePhone%20CE%20RED%20Certificate-S19112602602.pdf PinePhone CE RED Certificate]<br />
** [https://files.pine64.org/doc/cert/PinePhone%20ROHS%20Report.pdf PinePhone ROHS Report]<br />
** Note: PinePhone's Type Allocation Code (TAC) is <i>86769804</i><br />
<br />
== Datasheets for components and peripherals ==<br />
<br />
* Allwinner A64 SoC information:<br />
** [https://files.pine64.org/doc/datasheet/pine64/A64%20brief%20v1.0%2020150323.pdf Allwinner A64 SoC brief introduction]<br />
** [https://files.pine64.org/doc/datasheet/pine64/A64_Datasheet_V1.1.pdf Allwinner A64 SoC Data Sheet V1.1 (Official Released Version)]<br />
** [https://files.pine64.org/doc/datasheet/pine64/Allwinner_A64_User_Manual_V1.0.pdf Allwinner A64 SoC User Manual V1.0 (Official Release Version)]<br />
<br />
* X-Powers AXP803 PMIC (Power Management IC) information:<br />
** [https://files.pine64.org/doc/datasheet/pine64/AXP803_Datasheet_V1.0.pdf AXP803 PMIC datasheet]<br />
<br />
* LPDDR3 (178 Balls) SDRAM:<br />
** [https://files.pine64.org/doc/datasheet/pinephone/ATL3A1632H12A_mobile_lpddr3_11x11.5_v1.0_1600.pdf Artmem LPDDR3 datasheet]<br />
<br />
* eMMC information:<br />
** [https://files.pine64.org/doc/datasheet/pinephone/Kimtigo_fbga153_16_32_64_eMMC_datasheet_v1.3.pdf Kimtigo eMMC datasheet]<br />
<br />
* CMOS camera module information:<br />
** [https://files.pine64.org/doc/datasheet/pinephone/QZ01-rear-2019-0717(HW)%20Model.pdf PinePhone 5M Pixel Real CMOS Image Sensor Module]<br />
** [https://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC for Rear Module datasheet]<br />
** [https://usermanual.wiki/Document/OV5640FirmwareUserGuideV10.952852672.pdf OV5640 Embedded Firmware User Guide&nbsp;&ndash; VCM AF Module]<br />
** [https://files.pine64.org/doc/datasheet/pinephone/QZ01-front-2019-0717(HW)%20Model.pdf PinePhone 2M Pixel Front CMOS Image Sensor Module]<br />
** [https://files.pine64.org/doc/datasheet/pinephone/GC2145%20CSP%20DataSheet%20release%20V1.0_20131201.pdf GC2145 2MP CMOS Image Sensor SoC for Front Module datasheet]<br />
<br />
* LCD touch screen panel information:<br />
** [https://files.pine64.org/doc/datasheet/pinephone/PinePhone%20LCD-QZ01.pdf 5.99" 1440x720 LCD IPS Panel specification]<br />
** [https://files.pine64.org/doc/datasheet/pinephone/ST7703_DS_v01_20160128.pdf ST7703 LCD Controller datasheet]<br />
** [https://files.pine64.org/doc/datasheet/pinephone/GT917S-Datasheet.pdf GOODiX GT917S Capacitive Touch Controller datasheet]<br />
<br />
* Lithium battery information:<br />
** [https://files.pine64.org/doc/datasheet/pinephone/PinePhone%20QZ01%20Battery%20Specification.pdf PinePhone Lithium Battery specification]<br />
** [https://files.pine64.org/doc/datasheet/pinephone/PinePhone%20QZ01%20Battery%20ZCV%20Curve%20Chart.xlsx PinePhone Lithium Battery ZCV curve chart]<br />
** [https://cad.onshape.com/documents/5194d6303f021e6f300b70a0/w/7b63ac4c32ed63dfd78c7840/e/5d43c0ce5b665bae10082a08 PinePhone Lithium Battery 3D onshape drawing]<br />
<br />
* WiFi/BT module information:<br />
** [https://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf RTL8723BS/RTL8723CS specification]<br />
<br />
* LTE module information:<br />
** [https://www.quectel.com/UploadFile/Product/Quectel_EG25-G_LTE_Standard_Specification_V1.2.pdf Quectel EG25-G LTE Module specification v1.2]<br />
** [[Media:Quectel EC25EC21 AT Commands Manual V1.2.pdf|EC25&EC21 AT Commands Manual]]<br />
** [https://www.quectel.com/UploadImage/Downlad/Quectel_EC2x&EG25-G&EG9x&EM05_FILE_AT_Commands_Manual_V1.0.pdf Quectel EC2x EG25-G EG9x EM05 FILE AT Commands Manual v1.0]<br />
** [https://sixfab.com/wp-content/uploads/2018/09/Quectel_EC25EC21_GNSS_AT_Commands_Manual_V1.1.pdf Quectel EC25 EC21 GNSS AT Commands Manual v1.1]<br />
<br />
* Sensors:<br />
** [https://www.st.com/en/mems-and-sensors/lis3mdl.html ST LIS3MDL 3-axis Magnetomater Datasheet]<br />
** [https://www.invensense.com/products/motion-tracking/6-axis/mpu-6050/ InvenSense MPU-6050 Six-Axis (Gyro + Accelerometer) MEMS datasheet]<br />
** [https://www.sensortek.com.tw/en/product/Proximity_Sensor_with_ALS.html SensorTek STK3335 Ambient Light Sensor and Proximity Sensor]<br />
<br />
* Digital video to USB-C bridge:<br />
** [https://www.analogix.com/en/system/files/AA-002281-PB-6-ANX7688_Product_Brief.pdf ANX7688 product brief]<br />
<br />
* Case information:<br />
** [https://files.pine64.org/doc/datasheet/pinephone/PinePhone%20Exploded%20Diagram%20ver%201.0.pdf PinePhone case exploded diagram]<br />
** [https://files.pine64.org/doc/datasheet/pinephone/PinePhone%20Back%20Cover.stp PinePhone back cover 3D file]<br />
<br />
* Other components:<br />
** See the [[PinePhone_component_list|Component List]]<br />
<br />
== Developer works ==<br />
<br />
The following resources have been made available by Megous, one of the developers:<br />
<br />
* [https://xnux.eu/howtos/pine64-pinephone-getting-started.html Getting started with PinePhone Hardware]<br />
* [https://xnux.eu/devices/pine64-pinephone.html State of development progress]<br />
* [https://xnux.eu/news.html PinePhone Technical News and Update, also applies to other Allwinner devices including PINE A64 SBC]<br />
* [https://xnux.eu/contribute.html Contributions to the kernel development]<br />
<br />
== External links == <br />
* [https://pine64.com/product-category/pinephone/ The PinePhone on the official Pine store]<br />
* [https://pine64.com/product-category/smartphone-spare-parts/ PinePhone spare parts on the official Pine store]<br />
* [https://pine64.com/product-category/smartphone-accessories/ PinePhone accessories on the official Pine store]<br />
<br />
[[Category:PinePhone]] [[Category:Allwinner A64]]</div>Tahayassenhttps://wiki.pine64.org/index.php?title=PinePhone_FAQ&diff=6379PinePhone FAQ2020-07-31T19:42:27Z<p>Tahayassen: More info on battery discharge issue during poweroff on braveheart edition</p>
<hr />
<div>A list of frequently asked question.<br />
<br />
== Hardware ==<br />
<br />
=== Revisions ===<br />
==== What are Community Editions? ====<br />
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].<br />
<br />
==== Is the Community Edition the latest revision? ====<br />
Yes, it is! The Community Edition is the latest version of the PinePhone, featuring the version number 1.2. 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]].<br />
<br />
==== Will there be other Community Editions? ====<br />
The UBports Community Edition is the first released Community Edition. Other Community Editions might follow, this however depends on multiple factors, including if the software is ready to be released on the consumer market.<br />
<br />
==== In simple terms, what are the differences between BraveHeart and the new Community Edition? ====<br />
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]].<br />
<br />
==== Will there be a newer revision after the Community Edition? ====<br />
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.<br />
<br />
The Community Edition (and parts for it) will be produced and sold for at least 5 years.<br />
<br />
There are plans for a newer revision with updated hardware, which is however multiple years away (3-5 years).<br />
<br />
==== Will there be hardware differences between the Community Editions? ====<br />
<br />
No, only the logo on the back panel will differ.<br />
<br />
=== Sound ===<br />
=== Modem ===<br />
<br />
==== The modem isn't working ====<br />
<br />
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.<br />
<br />
=== Battery ===<br />
<br />
==== The battery is stuck inside the phone ====<br />
<br />
The battery can be stuck in the phone if the screws of the frame are overtightened.<br />
<br />
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.<br />
<br />
==== The battery is discharging while the phone is powered off (BraveHeart Edition) ====<br />
<br />
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].<br />
<br />
=== Kill Switches ===<br />
==== What are the kill switches doing? ====<br />
<br />
{| class="wikitable"<br />
|-<br />
! Number<br />
! Name<br />
! Explanation<br />
! Description<br />
|-<br />
| 1<br />
| Modem<br />
| Pulls Q1501 gate up (FET killing modem power)<br />
| "On" enables 2G/3G/4G communication and GNSS hardware, "off" disables it.<br />
|-<br />
| 2<br />
| WiFi / Bluetooth<br />
| Pulls up CHIP_EN<br />
| "On" enables WiFi and Bluetooth communication hardware, "off" disables it.<br />
|-<br />
| 3<br />
| Microphone<br />
| Breaks microphone bias voltage from the SoC<br />
| "On" enables audio input from on-board microphones (not 3.5mm jack), "off" disables it.<br />
|-<br />
| 4<br />
| Rear camera<br />
| Pulls up PWDN on OV5640 <br />
| "On" enables the rear camera, "off" disables it.<br />
|-<br />
| 5<br />
| Front camera<br />
| Pulls up PWDN on GC2145<br />
| "On" enables the front camera, "off" disables it.<br />
|-<br />
| 6<br />
| Headphone<br />
| Pulls up IN2 on analog switch BCT4717ETB<br />
| "On" enables audio input and output via the 3.5mm audio jack, "off" switches the jack to hardware UART mode.<br />
|}<br />
<br />
<br />
=== Memory ===<br />
<br />
==== What's the speed difference between the eMMC and SD cards? ====<br />
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).<br />
<br />
== Software ==<br />
<br />
=== Installation ===<br />
<br />
==== How can I install an operating system on the SD card / eMMC? ====<br />
<br />
See [[PinePhone Installation Instructions]].<br />
<br />
=== Updating ===<br />
<br />
Read the [[PinePhone Updating Instructions]].<br />
<br />
=== Booting ===<br />
<br />
==== What's the boot order for SD cards and eMMC? ====<br />
<br />
The PinePhone will automatically boot from microSD if a bootable card is inserted. If no (bootable) microSD is found, it will boot from eMMC.<br />
<br />
==== How can I select different OSes at boot? ====<br />
<br />
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.<br />
<br />
=== Ubuntu Touch ===<br />
<br />
==== Can I install a different OS on the Ubports Community Edition? ====<br />
<br />
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.<br />
<br />
==== How can I enable SSH? ====<br />
<br />
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.<br />
<br />
==== What works, what doesn't? ====<br />
<br />
See https://gitlab.com/ubports/community-ports/pinephone#what-works-what-doesnt.<br />
<br />
==== I did not install an update and I'm stuck on the Pine64 logo after rebooting. ====<br />
<br />
# Use a USB A-C cable to plug your phone into your PC<br />
# Hold the PinePhone's power button for 4 seconds or more to power it off.<br />
# Wait 5 seconds<br />
# 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.<br />
# Your PC may automatically mount the PinePhone's partitions. If it does, Safely Remove or Eject all of them.<br />
# Open a terminal on your PC. Type <code>telnet 172.16.42.1</code><br />
# You should receive the text 'Welcome to Rescue SD Shell!'<br />
# In the new Rescue SD shell, type <code>umount /dev/mmcblk2p10; e2fsck -fy /dev/mmcblk2p10 && sync</code><br />
# Once this command pipeline finishes, type <code>sync && reboot -f</code><br />
<br />
Your PinePhone should reboot into Ubuntu Touch. Now head to Settings -> Updates and install the new update! <br />
<br />
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.<br />
<br />
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.<br />
<br />
==== I turned on my PinePhone. The red LED is lit and it will not boot. ====<br />
# Hold the power button until the light turns off<br />
# Hold the power button until the light turns on<br />
<br />
You may need to repeat these steps more than once.<br />
<br />
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.<br />
<br />
==== I can't connect to a 2.4Ghz Wi-Fi network. ====<br />
<br />
Reboot your device by holding the power button until the "Power" dialog appears, then pressing "Restart".<br />
<br />
If that does not fix the issue, note that all the following conditions must be met to use WiFi on the PinePhone:<br />
<br />
# The plastic tab between the battery and the device's battery contacts has been removed<br />
# The battery is installed<br />
# The WiFi killswitch, #2, on the rear of the device is switched "ON"<br />
<br />
Wi-Fi in the PinePhone only seems stable after a warm reboot like this.<br />
<br />
==== I can't update or install packages through apt ====<br />
<br />
<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><br />
<br />
Remount the root filesystem as read-write:<br />
<br />
<code> phablet@ubuntu-phablet:~$ sudo mount -o remount,rw / </code><br />
<br />
Now you should be able to run updates and install new packages<br />
<br />
=== Android ===<br />
<br />
==== What's the status of Android for the PinePhone? ====<br />
<br />
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.<br />
<br />
==== Why are my apps loading slower than on my Android phone? ====<br />
<br />
Android has multiple techniques in place to speed up launching applications after the first launch, such as the "Dalvik cache".<br />
<br />
== Shipping ==<br />
=== I did not receive an order confirmation ===<br />
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.<br />
<br />
=== When does the phone ship? ===<br />
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.<br />
<br />
=== It is shipping day but I did not receive a shipping notification ===<br />
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.<br />
<br />
=== When does my phone ship if I order now? ===<br />
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.<br />
<br />
=== What about import taxes? ===<br />
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.<br />
<br />
== Accessories ==<br />
<br />
=== Protection ===<br />
==== Which screen protector should i use? ====<br />
<br />
Protecting your screen is important, especially for devices like the PinePhone that doesn't have access to the newest glass technology.<br />
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].<br />
<br />
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.<br />
<br />
=== Batteries ===<br />
==== I'm outside the US and want a replacement battery, which one should I buy? ====<br />
<br />
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.<br />
<br />
=== External hardware ===<br />
<br />
==== Will Pine64 sell other addons made for the PinePhone? ====<br />
<br />
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. <br />
<br />
==== Which 3rd party hardware can connect to my PinePhone? ====<br />
<br />
See [[PinePhone Hardware Accessory Compatibility]].</div>Tahayassenhttps://wiki.pine64.org/index.php?title=PinePhone&diff=4701PinePhone2020-01-21T00:53:51Z<p>Tahayassen: Add link to PinePhone Software Release main article</p>
<hr />
<div>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 preinstalled OS and was 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.<br />
<br />
== Specifications ==<br />
<br />
'''Dimensions:''' 160.5 x 76.6 x 9.2mm <br><br />
'''Weight:''' Between 180-200 grams <br><br />
'''SIM Card:''' Micro-SIM <br><br />
'''Display:'''<br />
: '''Size:''' 5.95 inches (151mm) diagonal<br />
: '''Type:''' HD IPS capacitive touchscreen, 16M colors<br />
: '''Resolution:''' 1440x720, 18:9 ratio <br><br />
'''System on Chip:''' [https://linux-sunxi.org/A64 Allwinner A64] <br><br />
'''RAM:''' 2GB LPDDR3 SDRAM <br><br />
'''Internal Storage:''' 16GB eMMC, extendable up to 2TB via microSD, supports SDHC and SDXC <br><br />
'''Back Camera:''' Single 5MP, 1/4", LED Flash <br><br />
'''Selfie Camera:''' Single 2MP, f/2.8, 1/5" <br><br />
'''Sound:''' Loudspeaker, 3.5mm jack & mic (jack doubles as hardware UART if killswitch 6 is deactivated) <br><br />
'''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]'''<br />
: '''LTE:''' B1, B2, B3, B4, B5, B7, B8, B12, B13, B18, B19, B20, B25, B26, B28, B38, B39, B40, B41<br />
: '''WCDMA:''' B1, B2, B4, B5, B6, B8, B19<br />
: '''GSM:''' 850, 900, 1800, 1900 (MHz)<br />
: '''WLAN:''' Wi-Fi 802.11 b/g/n, single-band, hotspot<br />
: '''Bluetooth:''' 4.0, A2DP<br />
: '''GNSS:''' GPS/GLONASS/BeiDou/Galileo/QZSS, with A-GPS<br />
'''Sensors:''' Accelerometer, gyro, proximity, ambient light, compass <br><br />
'''[[#Killswitch configuration|Killswitches]]:''' Modem, Wifi & Bluetooth, Microphone, Cameras <br><br />
'''[[#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) <br><br />
'''I/O:''' USB Type-C (SlimPort), USB Host, DisplayPort Alternate Mode output, 15W 5V 3A Quick Charge, follows USB PD specification<br />
<br />
== Hardware Revisions ==<br />
<br />
# [[Project Don't be evil|"Project Don't Be Evil" devkit]]<br />
# [[PinePhone v1.0 - Dev|PinePhone v1.0 - Developer batch]]<br />
# [[PinePhone v1.1 - Braveheart]]<br />
<br />
== Hardware Addons ==<br />
<br />
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.<br />
<br />
'''A step/stl/stp (3D model) file for the back cover is [https://app.box.com/s/g1n9cvg60cg66utdhs7m5my1ftvd0jj8 freely available] for creating custom cases that interface with the pogo pins.'''<br />
<br />
== Killswitch configuration ==<br />
<br />
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.<br />
<br />
[[File:PinePhone-main-board.jpg|600px|thumb|centre|Photo of Developer mainboard courtesy of Martijn Braam, postmarketOS]]<br />
<br />
# Modem: On enables 2G/3G/4G communication and GNSS hardware, off disables.<br />
# WiFi/BT: On enables Wi-Fi and Bluetooth communication hardware, off disables.<br />
# Microphone: On enables audio input from on-board microphones (not 3.5mm jack), off disables.<br />
# Rear camera: On enables the rear camera, off disables.<br />
# Front camera: On enables the front camera, off disables.<br />
# Headphone: On enables audio input and output via the 3.5mm audio jack, off switches the jack to hardware UART mode.<br />
<br />
== Battery ==<br />
<br />
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.<br />
<br />
The battery terminals, in order from nearest the edge to nearest the middle, are:<br />
<br />
# +ve<br />
# thermistor<br />
# -ve<br />
# not connected<br />
<br />
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.<br />
<br />
'''When you first receive your Pinephone you will need to remove the plastic tab under the battery terminals to boot it! This is to protect it from turning on during shipping.'''<br />
<br />
== Modem and Carrier Support ==<br />
<br />
To check if the PinePhone is supported on your carrier: <br />
<br />
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).<br />
<br />
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.<br />
<br />
== Operating Systems ==<br />
See [[PinePhone Software Release]] for the main article. 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:<br />
* [[#postmarketOS|postmarketOS]]<br />
* [[#Ubuntu Touch|Ubuntu Touch]]<br />
* [[#Sailfish OS|Sailfish OS]]<br />
* [[#Maemo Leste|Maemo Leste]]<br />
* [[#LuneOS|LuneOS]]<br />
* [[#Manjaro|Manjaro]]<br />
<br />
=== postmarketOS ===<br />
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.<br />
<br />
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].<br />
<br />
=== Ubuntu Touch ===<br />
[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. <br />
<br />
=== Sailfish OS ===<br />
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].<br />
<br />
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!<br />
<br />
'''Instructions:'''<br />
# Download the flashing script<br />
# Insert a microSD card in your device<br />
# Make the script executable: <code>chmod +x flash-it.sh</code><br />
# Execute it: <code>./flash-it.sh</code><br />
# Follow the instructions. Some commands in the script require root permissions.<br />
<br />
=== Nemo Mobile ===<br />
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].<br />
<br />
=== Maemo Leste ===<br />
[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><br />
<br />
=== LuneOS ===<br />
[https://www.webos-ports.org/wiki/Main_Page LuneOS] downloads are available [http://build.webos-ports.org/luneos-testing/images/pinephone/ here].<br />
<br />
=== Manjaro ===<br />
[https://wiki.manjaro.org/index.php Manjaro] downloads are available [https://osdn.net/projects/manjaro-arm/storage/pinephone/ here].</div>Tahayassen