PINE64 - User contributions [en]

PinePhone Carrier Support

2022-11-07T13:39:32Z

EJ5C98: china unicom works ootb with a firmware upgrade

{{under construction}}

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

= Check compatibility =
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 in the [[File:Quectel_EG25-G_LTE_Standard_Specification_V1.3.pdf]] modem specification sheet).

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.

= Tested and working carriers =

The following is a list of carriers which has been tested by users and confirmed to be working (excerpt):

== Asia ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
| Japan || [[wikipedia:SoftBank_Group#SoftBank_Mobile|SoftBank]] || Not tested || Unsupported by carrier || No || No || Mobian Phosh, December 2020
|-
| Japan || [[wikipedia:ja:楽天モバイル|Rakuten Mobile]] || Unsupported by carrier || Unsupported by carrier || Yes || Yes || Mobian Phosh, January 2021
|-
| Japan || [[wikipedia:ja:楽天モバイル|Rakuten Mobile]] || Unsupported by carrier || Unsupported by carrier || Yes || No || Manjaro Plasma Mobile February 2021
|-
| Japan || [[wikipedia:NTT Docomo|Docomo]] || Yes || Not tested || Yes || Yes || Mobian Phosh, February 2021
|-
| India || Vodafone / Vi India || Yes || Not tested || Yes || Yes || DanctNIX (Arch Linux ARM) with Phosh, March 2021
|-
| Malaysia || Celcom || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| Malaysia || Maxis || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| Malaysia || U-Mobile || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| Malaysia || Yes || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| South Korea || KT || Yes || Not tested || Yes || Yes || Manjaro Phosh, June 2021
|-
| China || [[wikipedia:China Mobile|China Mobile]] || Yes || Not tested || Yes || No || Mobile NixOS, December 2021
|-
| China || [[wikipedia:China Telecom|China Telecom]] || Yes (hack needed) || Not tested || Yes (hack needed) || No || AOSC OS Phosh, January 2022
|-
| Japan || [[wikipedia:ja:楽天モバイル|Rakuten Mobile]] || Yes || Not tested || Yes || Yes || Mobian Phosh, January 2022 (rivised from January 2021)
|-
| China || [[wikipedia:China Unicom|China Unicom]] || Yes || Not tested || Yes || Yes || [https://postmarketos.org/ pmOS] 22.06.3 Phosh, [[PineModems#Bootloader_unlocking | BLunlck'd]], [[PinePhone#Firmware_update|upd'd]] to [https://github.com/Biktorgj/quectel_eg25_recovery/tree/EG25GGBR07A08M2G_30.006.30.006 *8M2G_30.006*], November 2022
|}

== Africa ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129
|-
|}

== Europe ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Ukraine || KyivStar || Yes || Not tested || Yes || Yes || Mobian Phosh(11Nov21)
|-
|-
| Ukraine || Vodafone || Yes || Not tested || Yes || Yes || Manjaro ARM Phosh(29Jun22)
|-
| Sweden || Tele2 || Yes || Not tested || Yes || Not tested || Manjaro ARM Posh
|-
| Sweden || Telenor SE || Not tested || Not tested || Yes || Not tested || Manjaro Plasma Mobile beta2
|-
| UK || Three || Yes || Not tested || Yes || Yes || Manjaro Plasma Mobile beta2
|-
| UK || Vodafone || Yes || Not tested || Yes || Yes || ALARM & pmOS (Phosh?), modem FW latest - 26 Feb 21
|-
| UK || Sky Mobile (O2) || Yes || Not tested || Yes || Yes || ArchLinux Phosh (20210908 image, fully updated) - 3 October 2021
|-
| UK || Smarty Mobile (Three) || Yes || Yes || Yes || Yes || Arch Linux SXMO (Wayland) - 23 March 2022
|-
| France || Orange || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021
|-
| France || SFR || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021
|-
| France || Free || Yes || Not tested || Yes || Yes || pmOS SXMO (Wayland) - 27 March 2022
|-
| Czech Republic || O2 || Yes (only on 2G) || Not tested || Yes || Yes || Mobian Phosh (20210517 image up to date) - 2 June 2021
|-
| 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
|-
| Germany || E-Plus || Yes (sending only 2G) || Not tested || Yes || Yes || Manjaro Phosh and postmarketOS, 2021-10-15
|-
| Germany || Telekom || Yes || Not tested || Yes || Not tested || Mobian Phosh (5.10-sunxi64), 2021-07-28
|-
| Germany || O2 / Telefonica || Yes || Not tested || Yes || Not tested || KPlasma
|-
| Hungary || Telekom || Yes || Not tested || Yes || Yes (IPv4) || Manjaro Phosh Beta 12, 2021-07-30
|-
| Hungary || Telenor/Yettel || Yes || Not tested || Yes || Yes || Mobian-Phosh-20210517, 2021-09-24
|-
| Denmark || CBB || Yes || Not tested || Yes || Yes || Manjaro Plasma Mobile Beta 5, 2021-06-30
|-
| Belgium || Telenet || Yes || Not tested || Yes || Yes || postmarketOS v20.05, v21.03, v21.06 and edge, 2021-08-15
|-
| Belgium || CARREFOUR || Yes || Not tested || Yes || Yes || postmarketOS v20.05, v21.03, v21.06 and edge, 2021-08-15
|-
| Poland || Play || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta 18, 2021-11-14
|-
| Poland || Orange || Yes || No || Yes || Yes (IPv4 & IPv6) || Manjaro Phosh v21.10, 2021-12-23
|-
| Poland || Premium Mobile || Yes || No || Yes || Yes || Manjaro Phosh v22.01, 2022-01-13
|-
| Italy || WindTre Italy || Yes || Not tested || Yes || Yes || Archlinux ARM Plasma Mobile
|-
| Switzerland || Salt || Yes || Not tested || Yes || Yes || Phosh on Mobian + Arch
|}

== North America ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI || Modem Firmware
|-
|-
| USA || AT&T || Yes || Yes || Yes || Yes ||
* Mobian - Phosh
|-
| USA || T-Mobile || Yes || No || Yes || Yes ||
* Arch Linux Arm 2020/11/29
* Mobian - Phosh
* Manjaro - KDE Plasma Mobile
|-
| USA || T-Mobile || Yes || Yes || Yes || Yes ||
* Mobian Bookworm (Phosh) (2022-03-08)
|| EG25GGBR07A08M2G_01.003.01.003
|-
| USA || MetroPCS (T-Mobile) || Yes || No || Yes || Yes ||
*Arch Linux Arm (Phosh,SXMO) 2021/04/29
*Manjaro - Phosh 2021/04/29
*Mobian - Phosh 2021/3/20
|-
| USA || T-Mobile || Yes - buggy || No || Yes - buggy || Yes - buggy ||
*Manjaro - Plasma Dev 2020/11/21
*Ubuntu Touch - 2020/11/26
*KDE Neon 2020/11/02
|-
| USA || Mint Mobile (T-Mobile) || Yes || Yes || Yes || Yes ||
*Mobian - Phosh 2021/3/14
*postMarketOS - Phosh, Sxmo, Plasma Mobile 2021/5/26
*Ubuntu Touch 2021/5/24
*Manjaro - Phosh 2022/3/25
|-
| USA || Patriot Mobile (T-Mobile) || Yes || Yes chatty v0.6.1 mmsd-tng v1.8 || Yes || Yes ||
*Arch Linux Arm - Phosh 2022/01/12
|-
| USA || Tello (T-Mobile) || Yes || Yes || Yes || Yes ||
*DanctNIX (Arch Linux ARM) - Phosh 2022-07-09
|-
| USA || TracFone || No || No || No || No ||
*postMarketOS - Phosh 2022/06/28
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
*Mobian - Phosh 2021/3/1
|-
| USA || US Mobile || Yes || Not tested || Yes || Not Tested ||
*Mobian - Phosh 2022/01/09
|-
| USA || Verizon || No || No || No || No ||
*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)
|-
| USA || Verizon || Not tested || Not tested || Yes || Not via gui ||
*Manjaro - KDE Plasma Mobile 2021/5/10
|-
| USA || Verizon || Yes || Not tested || Yes || Not via gui ||
*Manjaro - Phosh 2021/5/31
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
*postmarketOS - Phosh 2021/5/31
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
*Arch - Phosh 2021/5/31
|-
| Canada || Freedom || Yes || Not tested || Yes || Yes ||
*Arch Pinephone - Phosh (APN: internet.windmobile.ca), 2021/4/25
|-
| Canada || SpeakOut || Yes || Not tested || Yes || Not tested ||
*Mobian - Phosh 2021/11/18
|-
| USA || Consumer Cellular (AT&T) || Yes || No || Yes || Yes ||
*Manjaro - Phosh 2021/06/26
|-
| USA || Google Fi (T-Mobile) || Yes || No || Yes || Yes ||
*Arch Linux Arm - Phosh 0.10.2 2021/05/29
|-
| Mexico || Telcel || Yes || Not tested || Yes || Yes ||
*Mobian - Phosh Weekly 2022/04/13
*PostmarketOS - SXMO De Sway v21.12 (stable) 2022/04/13
*PostmarketOS - Phosh v21.12 (stable) 2022/04/13
*PostmarketOS - Plasma Mobile v21.12 (stable) 2022/04/13
*PostmarketOS - sxmo edge 2021/09/09
|-
| USA || Ting || Yes || Yes - buggy || Yes || Yes ||
*Manjaro - Phosh 2021/12/10
|-
| USA || Simple Mobile || Yes || Yes || Yes || Yes ||
*Mobian - Phosh - Make sure APN is "Simple" in settings (note uppercase S)
|-
|}

== South America ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129
|-
|}

== Australia / Oceania ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129
|-
| Australia || Beyond (Telstra) || Yes || Yes || Yes || Yes || Manjaro Phosh Beta 20.
|-
| Australia || Belong (Telstra) || Yes || Yes || Yes || Yes || Arch (Danctnix), Feb 2022.
|-
| Australia || Optus || Yes || No. Ticket lodged with Chatty and mmsd re multiple APN issue || Yes || Yes || Manjaro Phosh Beta 20. Manjaro Plasma Mobile Beta 9 (Data working with this release). SXMO (Danctnix and PMOS edge December 2021).
|-
| Australia || Amaysim (Optus) || Yes || No. Ticket lodged with Chatty and mmsd re multiple APN issue || Yes || Yes || Manjaro Phosh
|-
| Australia || OPTUS (Dodo) || || ||Yes|| || Manjaro Plasma Mobile 5.23.4, 2021-12.27 (deepsleep disrupts settings)
|-
| Australia || Vodafone || Yes || Yes || Yes (No VoLTE) || Yes || pmOS Edge 5.15.3 kernel, 2022-02-10 with Phosh
|}

== Middle East ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || USSD working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Israel|| Cellcom prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Cellcom Talkman|| receive+notify|| YES || YES (when manually selecting the MMS APN) || ring(VoLTE not working) || YES || on mobian Feb 04, 2022, Earthquake early warning system did not show a notification on Feb 07, 2022
|-
|-
| Israel|| Cellcom Talkman|| NO || NO || NO || ring+ notify (VoLTE not working)|| YES || on Plasma Mobile Feb 04, 2022
|-
|-
| Israel|| Golan TC || receive+notify|| YES || NA || ring+ notify (VoLTE not working) || Yes || on mobian/phosh March 13 2022
|-
|-
| Israel|| Partner prepay || receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Pelephone prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Hot prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| 019 prepay|| No || NA || NA ||Bars only || NA || on PmOS Sxmo May 14 2021.
|-

|}

= Special carrier notes =

{{Warning|This section contains providers which do not work or require special settings or actions to work.}}

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:

== USA ==
=== AT&T ===
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. Phone and SMS with PinePhone work out-of-the-box with AT&T. If you transfer a SIM card from another phone you were using with AT&T, you may need to activate the PinePhone through [https://www.att.com/buy/wireless/byod/byod AT&T's website]. Calls and SMS messages work. 4G and MMS work if [https://www.att.com/support/article/wireless/KM1062162/ these settings] are used for APN, MMSC, and Proxy.

AT&T may 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.

=== Consumer Cellular ===

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.

=== Cricket Wireless ===
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).

=== Faith Wireless ===
Faith Wireless is a MVNO that uses AT&T's network. VoLTE was fully supported, but the PinePhone comes up as a Mobile Broadband Device. Faith Wireless does not service Mobile Broadband Devices. (As of February 2022)

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

=== Sprint ===
Sprint is currently not supported due to unknown reasons. Any input regarding this issue is highly appreciated.

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

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

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

=== Verizon ===
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page],
Verizon's primary frequency band for the United States is 13 (700 MHz). Verizon's bands and protocols are summarized on
[https://www.frequencycheck.com/carriers/verizon-wireless-united-states this page]. According to the same page, Verizon might restrict their network to only approved devices.

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.

=== TracFone ===
Following TracFone's [https://www.verizon.com/about/news/verizon-completes-tracfone-wireless-inc-acquisition acquisition by Verizon], support for the AT&T and T-Mobile bands has been deprecated as of early June 2022. TracFone has the same issues with connecting as Verizon, as they now exclusively use Verizon's frequency band.

=== Google Fi ===
Only T-Mobile service works currently, not US Cellular or Sprint.
The APN is h2g2.
Information from [https://forum.pine64.org/showthread.php?tid=11675&page=7 the forum].

Bear in mind that initial activation of the SIM card is not possible without an Android phone running Google Apps.

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.

== Europe ==
=== Telekom Germany ===
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.

=== Orange Poland ===
Setting up dual stack IPv4 and IPv6 may require [https://etherpad.gnome.org/p/dx7pbkPMCytMLMRl1eyo extra work], because the carrier provides IPv4 connectivity on internetipv6 APN via a protocol called CLAT/NAT64.

== Asia ==
=== China Telecom ===
The baseband itself ships with bad (for CDMA, which isn't supported by EG25-G) MBN file for CT, so a force change of MBN file to the generic one is needed to get VoLTE (thus SMS+Call) work.

Run the following AT commands to force ROW_Generic_3GPP which can support VoLTE on CT:
<pre>
AT+QMBNCFG="autosel",0
AT+QMBNCFG="select","ROW_Generic_3GPP"
AT+QCFG="ims",1
</pre>

=== SoftBank ===
SoftBank USIM cards are IMEI-locked, and on top of that will only work on either Android or iOS. 
A free SIM is available, but that one is data only. 
The same problem might exist with MVNO's who make use of the SoftBank network, and therefore it's advised to pick either NTT docomo or au as the MNO.

ソフトバンク社のUSIMカードはIMEIロックで御座います。 
なお、Android又はiOS限定です。 
フリーSIMもありますが、これはデータのみSIMです。 
ソフトバンク社を使っているMVNOで同じ問題があるかもしれませんので、出来ればMNOはNTTドコモ又はauをご選択下さい。

= Known issues =
Known issues:
* The [https://www.frequencycheck.com/models FrequencyCheck model page] does not list either Pine64 or the PinePhone.
* 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.
* 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.
* Some providers may allow only certain known devices identified by their [https://en.wikipedia.org/wiki/Type_Allocation_Code Type Allocation Code].

= MMS workarounds =
These scripts allow partial MMS support on a [[PinePhone]] in distributions without working MMS support:

* JMMS: [https://git.sr.ht/~amindfv/jmms]
* silvermms: [https://gitlab.com/5ilver/silvermms]
* MMS via Matrix with mmmpuppet: [[PinePhone MMS with Matrix]]

There is a Haskel MMS client. MMS can also be manually composed with mmsd on the command line.

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

[[Category:PinePhone]]

PinePhone Carrier Support

2022-11-07T03:30:42Z

EJ5C98: /* Asia */ fix chronological order

{{under construction}}

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

= Check compatibility =
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 in the [[File:Quectel_EG25-G_LTE_Standard_Specification_V1.3.pdf]] modem specification sheet).

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.

= Tested and working carriers =

The following is a list of carriers which has been tested by users and confirmed to be working (excerpt):

== Asia ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
| Japan || [[wikipedia:SoftBank_Group#SoftBank_Mobile|SoftBank]] || Not tested || Unsupported by carrier || No || No || Mobian Phosh, December 2020
|-
| Japan || [[wikipedia:ja:楽天モバイル|Rakuten Mobile]] || Unsupported by carrier || Unsupported by carrier || Yes || Yes || Mobian Phosh, January 2021
|-
| Japan || [[wikipedia:ja:楽天モバイル|Rakuten Mobile]] || Unsupported by carrier || Unsupported by carrier || Yes || No || Manjaro Plasma Mobile February 2021
|-
| Japan || [[wikipedia:NTT Docomo|Docomo]] || Yes || Not tested || Yes || Yes || Mobian Phosh, February 2021
|-
| India || Vodafone / Vi India || Yes || Not tested || Yes || Yes || DanctNIX (Arch Linux ARM) with Phosh, March 2021
|-
| Malaysia || Celcom || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| Malaysia || Maxis || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| Malaysia || U-Mobile || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| Malaysia || Yes || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| South Korea || KT || Yes || Not tested || Yes || Yes || Manjaro Phosh, June 2021
|-
| China || [[wikipedia:China Mobile|China Mobile]] || Yes || Not tested || Yes || No || Mobile NixOS, December 2021
|-
| China || [[wikipedia:China Telecom|China Telecom]] || Yes (hack needed) || Not tested || Yes (hack needed) || No || AOSC OS Phosh, January 2022
|-
| Japan || [[wikipedia:ja:楽天モバイル|Rakuten Mobile]] || Yes || Not tested || Yes || Yes || Mobian Phosh, January 2022 (rivised from January 2021)
|-
| China || [[wikipedia:China Unicom|China Unicom]] || Yes || Not tested || Yes (hack needed) || Yes || postmarketOS 22.06.3 Phosh, November 2022
|}

== Africa ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129
|-
|}

== Europe ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Ukraine || KyivStar || Yes || Not tested || Yes || Yes || Mobian Phosh(11Nov21)
|-
|-
| Ukraine || Vodafone || Yes || Not tested || Yes || Yes || Manjaro ARM Phosh(29Jun22)
|-
| Sweden || Tele2 || Yes || Not tested || Yes || Not tested || Manjaro ARM Posh
|-
| Sweden || Telenor SE || Not tested || Not tested || Yes || Not tested || Manjaro Plasma Mobile beta2
|-
| UK || Three || Yes || Not tested || Yes || Yes || Manjaro Plasma Mobile beta2
|-
| UK || Vodafone || Yes || Not tested || Yes || Yes || ALARM & pmOS (Phosh?), modem FW latest - 26 Feb 21
|-
| UK || Sky Mobile (O2) || Yes || Not tested || Yes || Yes || ArchLinux Phosh (20210908 image, fully updated) - 3 October 2021
|-
| UK || Smarty Mobile (Three) || Yes || Yes || Yes || Yes || Arch Linux SXMO (Wayland) - 23 March 2022
|-
| France || Orange || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021
|-
| France || SFR || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021
|-
| France || Free || Yes || Not tested || Yes || Yes || pmOS SXMO (Wayland) - 27 March 2022
|-
| Czech Republic || O2 || Yes (only on 2G) || Not tested || Yes || Yes || Mobian Phosh (20210517 image up to date) - 2 June 2021
|-
| 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
|-
| Germany || E-Plus || Yes (sending only 2G) || Not tested || Yes || Yes || Manjaro Phosh and postmarketOS, 2021-10-15
|-
| Germany || Telekom || Yes || Not tested || Yes || Not tested || Mobian Phosh (5.10-sunxi64), 2021-07-28
|-
| Germany || O2 / Telefonica || Yes || Not tested || Yes || Not tested || KPlasma
|-
| Hungary || Telekom || Yes || Not tested || Yes || Yes (IPv4) || Manjaro Phosh Beta 12, 2021-07-30
|-
| Hungary || Telenor/Yettel || Yes || Not tested || Yes || Yes || Mobian-Phosh-20210517, 2021-09-24
|-
| Denmark || CBB || Yes || Not tested || Yes || Yes || Manjaro Plasma Mobile Beta 5, 2021-06-30
|-
| Belgium || Telenet || Yes || Not tested || Yes || Yes || postmarketOS v20.05, v21.03, v21.06 and edge, 2021-08-15
|-
| Belgium || CARREFOUR || Yes || Not tested || Yes || Yes || postmarketOS v20.05, v21.03, v21.06 and edge, 2021-08-15
|-
| Poland || Play || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta 18, 2021-11-14
|-
| Poland || Orange || Yes || No || Yes || Yes (IPv4 & IPv6) || Manjaro Phosh v21.10, 2021-12-23
|-
| Poland || Premium Mobile || Yes || No || Yes || Yes || Manjaro Phosh v22.01, 2022-01-13
|-
| Italy || WindTre Italy || Yes || Not tested || Yes || Yes || Archlinux ARM Plasma Mobile
|-
| Switzerland || Salt || Yes || Not tested || Yes || Yes || Phosh on Mobian + Arch
|}

== North America ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI || Modem Firmware
|-
|-
| USA || AT&T || Yes || Yes || Yes || Yes ||
* Mobian - Phosh
|-
| USA || T-Mobile || Yes || No || Yes || Yes ||
* Arch Linux Arm 2020/11/29
* Mobian - Phosh
* Manjaro - KDE Plasma Mobile
|-
| USA || T-Mobile || Yes || Yes || Yes || Yes ||
* Mobian Bookworm (Phosh) (2022-03-08)
|| EG25GGBR07A08M2G_01.003.01.003
|-
| USA || MetroPCS (T-Mobile) || Yes || No || Yes || Yes ||
*Arch Linux Arm (Phosh,SXMO) 2021/04/29
*Manjaro - Phosh 2021/04/29
*Mobian - Phosh 2021/3/20
|-
| USA || T-Mobile || Yes - buggy || No || Yes - buggy || Yes - buggy ||
*Manjaro - Plasma Dev 2020/11/21
*Ubuntu Touch - 2020/11/26
*KDE Neon 2020/11/02
|-
| USA || Mint Mobile (T-Mobile) || Yes || Yes || Yes || Yes ||
*Mobian - Phosh 2021/3/14
*postMarketOS - Phosh, Sxmo, Plasma Mobile 2021/5/26
*Ubuntu Touch 2021/5/24
*Manjaro - Phosh 2022/3/25
|-
| USA || Patriot Mobile (T-Mobile) || Yes || Yes chatty v0.6.1 mmsd-tng v1.8 || Yes || Yes ||
*Arch Linux Arm - Phosh 2022/01/12
|-
| USA || Tello (T-Mobile) || Yes || Yes || Yes || Yes ||
*DanctNIX (Arch Linux ARM) - Phosh 2022-07-09
|-
| USA || TracFone || No || No || No || No ||
*postMarketOS - Phosh 2022/06/28
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
*Mobian - Phosh 2021/3/1
|-
| USA || US Mobile || Yes || Not tested || Yes || Not Tested ||
*Mobian - Phosh 2022/01/09
|-
| USA || Verizon || No || No || No || No ||
*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)
|-
| USA || Verizon || Not tested || Not tested || Yes || Not via gui ||
*Manjaro - KDE Plasma Mobile 2021/5/10
|-
| USA || Verizon || Yes || Not tested || Yes || Not via gui ||
*Manjaro - Phosh 2021/5/31
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
*postmarketOS - Phosh 2021/5/31
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
*Arch - Phosh 2021/5/31
|-
| Canada || Freedom || Yes || Not tested || Yes || Yes ||
*Arch Pinephone - Phosh (APN: internet.windmobile.ca), 2021/4/25
|-
| Canada || SpeakOut || Yes || Not tested || Yes || Not tested ||
*Mobian - Phosh 2021/11/18
|-
| USA || Consumer Cellular (AT&T) || Yes || No || Yes || Yes ||
*Manjaro - Phosh 2021/06/26
|-
| USA || Google Fi (T-Mobile) || Yes || No || Yes || Yes ||
*Arch Linux Arm - Phosh 0.10.2 2021/05/29
|-
| Mexico || Telcel || Yes || Not tested || Yes || Yes ||
*Mobian - Phosh Weekly 2022/04/13
*PostmarketOS - SXMO De Sway v21.12 (stable) 2022/04/13
*PostmarketOS - Phosh v21.12 (stable) 2022/04/13
*PostmarketOS - Plasma Mobile v21.12 (stable) 2022/04/13
*PostmarketOS - sxmo edge 2021/09/09
|-
| USA || Ting || Yes || Yes - buggy || Yes || Yes ||
*Manjaro - Phosh 2021/12/10
|-
| USA || Simple Mobile || Yes || Yes || Yes || Yes ||
*Mobian - Phosh - Make sure APN is "Simple" in settings (note uppercase S)
|-
|}

== South America ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129
|-
|}

== Australia / Oceania ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129
|-
| Australia || Beyond (Telstra) || Yes || Yes || Yes || Yes || Manjaro Phosh Beta 20.
|-
| Australia || Belong (Telstra) || Yes || Yes || Yes || Yes || Arch (Danctnix), Feb 2022.
|-
| Australia || Optus || Yes || No. Ticket lodged with Chatty and mmsd re multiple APN issue || Yes || Yes || Manjaro Phosh Beta 20. Manjaro Plasma Mobile Beta 9 (Data working with this release). SXMO (Danctnix and PMOS edge December 2021).
|-
| Australia || Amaysim (Optus) || Yes || No. Ticket lodged with Chatty and mmsd re multiple APN issue || Yes || Yes || Manjaro Phosh
|-
| Australia || OPTUS (Dodo) || || ||Yes|| || Manjaro Plasma Mobile 5.23.4, 2021-12.27 (deepsleep disrupts settings)
|-
| Australia || Vodafone || Yes || Yes || Yes (No VoLTE) || Yes || pmOS Edge 5.15.3 kernel, 2022-02-10 with Phosh
|}

== Middle East ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || USSD working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Israel|| Cellcom prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Cellcom Talkman|| receive+notify|| YES || YES (when manually selecting the MMS APN) || ring(VoLTE not working) || YES || on mobian Feb 04, 2022, Earthquake early warning system did not show a notification on Feb 07, 2022
|-
|-
| Israel|| Cellcom Talkman|| NO || NO || NO || ring+ notify (VoLTE not working)|| YES || on Plasma Mobile Feb 04, 2022
|-
|-
| Israel|| Golan TC || receive+notify|| YES || NA || ring+ notify (VoLTE not working) || Yes || on mobian/phosh March 13 2022
|-
|-
| Israel|| Partner prepay || receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Pelephone prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Hot prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| 019 prepay|| No || NA || NA ||Bars only || NA || on PmOS Sxmo May 14 2021.
|-

|}

= Special carrier notes =

{{Warning|This section contains providers which do not work or require special settings or actions to work.}}

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:

== USA ==
=== AT&T ===
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. Phone and SMS with PinePhone work out-of-the-box with AT&T. If you transfer a SIM card from another phone you were using with AT&T, you may need to activate the PinePhone through [https://www.att.com/buy/wireless/byod/byod AT&T's website]. Calls and SMS messages work. 4G and MMS work if [https://www.att.com/support/article/wireless/KM1062162/ these settings] are used for APN, MMSC, and Proxy.

AT&T may 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.

=== Consumer Cellular ===

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.

=== Cricket Wireless ===
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).

=== Faith Wireless ===
Faith Wireless is a MVNO that uses AT&T's network. VoLTE was fully supported, but the PinePhone comes up as a Mobile Broadband Device. Faith Wireless does not service Mobile Broadband Devices. (As of February 2022)

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

=== Sprint ===
Sprint is currently not supported due to unknown reasons. Any input regarding this issue is highly appreciated.

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

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

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

=== Verizon ===
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page],
Verizon's primary frequency band for the United States is 13 (700 MHz). Verizon's bands and protocols are summarized on
[https://www.frequencycheck.com/carriers/verizon-wireless-united-states this page]. According to the same page, Verizon might restrict their network to only approved devices.

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.

=== TracFone ===
Following TracFone's [https://www.verizon.com/about/news/verizon-completes-tracfone-wireless-inc-acquisition acquisition by Verizon], support for the AT&T and T-Mobile bands has been deprecated as of early June 2022. TracFone has the same issues with connecting as Verizon, as they now exclusively use Verizon's frequency band.

=== Google Fi ===
Only T-Mobile service works currently, not US Cellular or Sprint.
The APN is h2g2.
Information from [https://forum.pine64.org/showthread.php?tid=11675&page=7 the forum].

Bear in mind that initial activation of the SIM card is not possible without an Android phone running Google Apps.

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.

== Europe ==
=== Telekom Germany ===
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.

=== Orange Poland ===
Setting up dual stack IPv4 and IPv6 may require [https://etherpad.gnome.org/p/dx7pbkPMCytMLMRl1eyo extra work], because the carrier provides IPv4 connectivity on internetipv6 APN via a protocol called CLAT/NAT64.

== Asia ==
=== China Telecom ===
The baseband itself ships with bad (for CDMA, which isn't supported by EG25-G) MBN file for CT, so a force change of MBN file to the generic one is needed to get VoLTE (thus SMS+Call) work.

Run the following AT commands to force ROW_Generic_3GPP which can support VoLTE on CT:
<pre>
AT+QMBNCFG="autosel",0
AT+QMBNCFG="select","ROW_Generic_3GPP"
AT+QCFG="ims",1
</pre>

=== China Unicom ===
SMS/Data works OOTB. 
For calls, apply the [[#China_Telecom]] hack above. 

=== SoftBank ===
SoftBank USIM cards are IMEI-locked, and on top of that will only work on either Android or iOS. 
A free SIM is available, but that one is data only. 
The same problem might exist with MVNO's who make use of the SoftBank network, and therefore it's advised to pick either NTT docomo or au as the MNO.

ソフトバンク社のUSIMカードはIMEIロックで御座います。 
なお、Android又はiOS限定です。 
フリーSIMもありますが、これはデータのみSIMです。 
ソフトバンク社を使っているMVNOで同じ問題があるかもしれませんので、出来ればMNOはNTTドコモ又はauをご選択下さい。

= Known issues =
Known issues:
* The [https://www.frequencycheck.com/models FrequencyCheck model page] does not list either Pine64 or the PinePhone.
* 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.
* 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.
* Some providers may allow only certain known devices identified by their [https://en.wikipedia.org/wiki/Type_Allocation_Code Type Allocation Code].

= MMS workarounds =
These scripts allow partial MMS support on a [[PinePhone]] in distributions without working MMS support:

* JMMS: [https://git.sr.ht/~amindfv/jmms]
* silvermms: [https://gitlab.com/5ilver/silvermms]
* MMS via Matrix with mmmpuppet: [[PinePhone MMS with Matrix]]

There is a Haskel MMS client. MMS can also be manually composed with mmsd on the command line.

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

[[Category:PinePhone]]

PinePhone Carrier Support

2022-11-07T03:28:33Z

EJ5C98: /* Asia */ add interwiki links to jp/cn carriers

{{under construction}}

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

= Check compatibility =
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 in the [[File:Quectel_EG25-G_LTE_Standard_Specification_V1.3.pdf]] modem specification sheet).

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.

= Tested and working carriers =

The following is a list of carriers which has been tested by users and confirmed to be working (excerpt):

== Asia ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
| Japan || [[wikipedia:SoftBank_Group#SoftBank_Mobile|SoftBank]] || Not tested || Unsupported by carrier || No || No || Mobian Phosh, December 2020
|-
| Japan || [[wikipedia:ja:楽天モバイル|Rakuten Mobile]] || Unsupported by carrier || Unsupported by carrier || Yes || Yes || Mobian Phosh, January 2021
|-
| Japan || [[wikipedia:ja:楽天モバイル|Rakuten Mobile]] || Unsupported by carrier || Unsupported by carrier || Yes || No || Manjaro Plasma Mobile February 2021
|-
| Japan || [[wikipedia:NTT Docomo|Docomo]] || Yes || Not tested || Yes || Yes || Mobian Phosh, February 2021
|-
| India || Vodafone / Vi India || Yes || Not tested || Yes || Yes || DanctNIX (Arch Linux ARM) with Phosh, March 2021
|-
| Malaysia || Celcom || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| Malaysia || Maxis || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| Malaysia || U-Mobile || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| Malaysia || Yes || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| South Korea || KT || Yes || Not tested || Yes || Yes || Manjaro Phosh, June 2021
|-
| China || [[wikipedia:China Mobile|China Mobile]] || Yes || Not tested || Yes || No || Mobile NixOS, December 2021
|-
| China || [[wikipedia:China Telecom|China Telecom]] || Yes (hack needed) || Not tested || Yes (hack needed) || No || AOSC OS Phosh, January 2022
|-
| China || [[wikipedia:China Unicom|China Unicom]] || Yes || Not tested || Yes (hack needed) || Yes || postmarketOS v22.06.3 November 2022
|-
| Japan || [[wikipedia:ja:楽天モバイル|Rakuten Mobile]] || Yes || Not tested || Yes || Yes || Mobian Phosh, January 2022 (rivised from January 2021)
|}

== Africa ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129
|-
|}

== Europe ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Ukraine || KyivStar || Yes || Not tested || Yes || Yes || Mobian Phosh(11Nov21)
|-
|-
| Ukraine || Vodafone || Yes || Not tested || Yes || Yes || Manjaro ARM Phosh(29Jun22)
|-
| Sweden || Tele2 || Yes || Not tested || Yes || Not tested || Manjaro ARM Posh
|-
| Sweden || Telenor SE || Not tested || Not tested || Yes || Not tested || Manjaro Plasma Mobile beta2
|-
| UK || Three || Yes || Not tested || Yes || Yes || Manjaro Plasma Mobile beta2
|-
| UK || Vodafone || Yes || Not tested || Yes || Yes || ALARM & pmOS (Phosh?), modem FW latest - 26 Feb 21
|-
| UK || Sky Mobile (O2) || Yes || Not tested || Yes || Yes || ArchLinux Phosh (20210908 image, fully updated) - 3 October 2021
|-
| UK || Smarty Mobile (Three) || Yes || Yes || Yes || Yes || Arch Linux SXMO (Wayland) - 23 March 2022
|-
| France || Orange || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021
|-
| France || SFR || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021
|-
| France || Free || Yes || Not tested || Yes || Yes || pmOS SXMO (Wayland) - 27 March 2022
|-
| Czech Republic || O2 || Yes (only on 2G) || Not tested || Yes || Yes || Mobian Phosh (20210517 image up to date) - 2 June 2021
|-
| 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
|-
| Germany || E-Plus || Yes (sending only 2G) || Not tested || Yes || Yes || Manjaro Phosh and postmarketOS, 2021-10-15
|-
| Germany || Telekom || Yes || Not tested || Yes || Not tested || Mobian Phosh (5.10-sunxi64), 2021-07-28
|-
| Germany || O2 / Telefonica || Yes || Not tested || Yes || Not tested || KPlasma
|-
| Hungary || Telekom || Yes || Not tested || Yes || Yes (IPv4) || Manjaro Phosh Beta 12, 2021-07-30
|-
| Hungary || Telenor/Yettel || Yes || Not tested || Yes || Yes || Mobian-Phosh-20210517, 2021-09-24
|-
| Denmark || CBB || Yes || Not tested || Yes || Yes || Manjaro Plasma Mobile Beta 5, 2021-06-30
|-
| Belgium || Telenet || Yes || Not tested || Yes || Yes || postmarketOS v20.05, v21.03, v21.06 and edge, 2021-08-15
|-
| Belgium || CARREFOUR || Yes || Not tested || Yes || Yes || postmarketOS v20.05, v21.03, v21.06 and edge, 2021-08-15
|-
| Poland || Play || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta 18, 2021-11-14
|-
| Poland || Orange || Yes || No || Yes || Yes (IPv4 & IPv6) || Manjaro Phosh v21.10, 2021-12-23
|-
| Poland || Premium Mobile || Yes || No || Yes || Yes || Manjaro Phosh v22.01, 2022-01-13
|-
| Italy || WindTre Italy || Yes || Not tested || Yes || Yes || Archlinux ARM Plasma Mobile
|-
| Switzerland || Salt || Yes || Not tested || Yes || Yes || Phosh on Mobian + Arch
|}

== North America ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI || Modem Firmware
|-
|-
| USA || AT&T || Yes || Yes || Yes || Yes ||
* Mobian - Phosh
|-
| USA || T-Mobile || Yes || No || Yes || Yes ||
* Arch Linux Arm 2020/11/29
* Mobian - Phosh
* Manjaro - KDE Plasma Mobile
|-
| USA || T-Mobile || Yes || Yes || Yes || Yes ||
* Mobian Bookworm (Phosh) (2022-03-08)
|| EG25GGBR07A08M2G_01.003.01.003
|-
| USA || MetroPCS (T-Mobile) || Yes || No || Yes || Yes ||
*Arch Linux Arm (Phosh,SXMO) 2021/04/29
*Manjaro - Phosh 2021/04/29
*Mobian - Phosh 2021/3/20
|-
| USA || T-Mobile || Yes - buggy || No || Yes - buggy || Yes - buggy ||
*Manjaro - Plasma Dev 2020/11/21
*Ubuntu Touch - 2020/11/26
*KDE Neon 2020/11/02
|-
| USA || Mint Mobile (T-Mobile) || Yes || Yes || Yes || Yes ||
*Mobian - Phosh 2021/3/14
*postMarketOS - Phosh, Sxmo, Plasma Mobile 2021/5/26
*Ubuntu Touch 2021/5/24
*Manjaro - Phosh 2022/3/25
|-
| USA || Patriot Mobile (T-Mobile) || Yes || Yes chatty v0.6.1 mmsd-tng v1.8 || Yes || Yes ||
*Arch Linux Arm - Phosh 2022/01/12
|-
| USA || Tello (T-Mobile) || Yes || Yes || Yes || Yes ||
*DanctNIX (Arch Linux ARM) - Phosh 2022-07-09
|-
| USA || TracFone || No || No || No || No ||
*postMarketOS - Phosh 2022/06/28
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
*Mobian - Phosh 2021/3/1
|-
| USA || US Mobile || Yes || Not tested || Yes || Not Tested ||
*Mobian - Phosh 2022/01/09
|-
| USA || Verizon || No || No || No || No ||
*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)
|-
| USA || Verizon || Not tested || Not tested || Yes || Not via gui ||
*Manjaro - KDE Plasma Mobile 2021/5/10
|-
| USA || Verizon || Yes || Not tested || Yes || Not via gui ||
*Manjaro - Phosh 2021/5/31
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
*postmarketOS - Phosh 2021/5/31
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
*Arch - Phosh 2021/5/31
|-
| Canada || Freedom || Yes || Not tested || Yes || Yes ||
*Arch Pinephone - Phosh (APN: internet.windmobile.ca), 2021/4/25
|-
| Canada || SpeakOut || Yes || Not tested || Yes || Not tested ||
*Mobian - Phosh 2021/11/18
|-
| USA || Consumer Cellular (AT&T) || Yes || No || Yes || Yes ||
*Manjaro - Phosh 2021/06/26
|-
| USA || Google Fi (T-Mobile) || Yes || No || Yes || Yes ||
*Arch Linux Arm - Phosh 0.10.2 2021/05/29
|-
| Mexico || Telcel || Yes || Not tested || Yes || Yes ||
*Mobian - Phosh Weekly 2022/04/13
*PostmarketOS - SXMO De Sway v21.12 (stable) 2022/04/13
*PostmarketOS - Phosh v21.12 (stable) 2022/04/13
*PostmarketOS - Plasma Mobile v21.12 (stable) 2022/04/13
*PostmarketOS - sxmo edge 2021/09/09
|-
| USA || Ting || Yes || Yes - buggy || Yes || Yes ||
*Manjaro - Phosh 2021/12/10
|-
| USA || Simple Mobile || Yes || Yes || Yes || Yes ||
*Mobian - Phosh - Make sure APN is "Simple" in settings (note uppercase S)
|-
|}

== South America ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129
|-
|}

== Australia / Oceania ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129
|-
| Australia || Beyond (Telstra) || Yes || Yes || Yes || Yes || Manjaro Phosh Beta 20.
|-
| Australia || Belong (Telstra) || Yes || Yes || Yes || Yes || Arch (Danctnix), Feb 2022.
|-
| Australia || Optus || Yes || No. Ticket lodged with Chatty and mmsd re multiple APN issue || Yes || Yes || Manjaro Phosh Beta 20. Manjaro Plasma Mobile Beta 9 (Data working with this release). SXMO (Danctnix and PMOS edge December 2021).
|-
| Australia || Amaysim (Optus) || Yes || No. Ticket lodged with Chatty and mmsd re multiple APN issue || Yes || Yes || Manjaro Phosh
|-
| Australia || OPTUS (Dodo) || || ||Yes|| || Manjaro Plasma Mobile 5.23.4, 2021-12.27 (deepsleep disrupts settings)
|-
| Australia || Vodafone || Yes || Yes || Yes (No VoLTE) || Yes || pmOS Edge 5.15.3 kernel, 2022-02-10 with Phosh
|}

== Middle East ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || USSD working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Israel|| Cellcom prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Cellcom Talkman|| receive+notify|| YES || YES (when manually selecting the MMS APN) || ring(VoLTE not working) || YES || on mobian Feb 04, 2022, Earthquake early warning system did not show a notification on Feb 07, 2022
|-
|-
| Israel|| Cellcom Talkman|| NO || NO || NO || ring+ notify (VoLTE not working)|| YES || on Plasma Mobile Feb 04, 2022
|-
|-
| Israel|| Golan TC || receive+notify|| YES || NA || ring+ notify (VoLTE not working) || Yes || on mobian/phosh March 13 2022
|-
|-
| Israel|| Partner prepay || receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Pelephone prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Hot prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| 019 prepay|| No || NA || NA ||Bars only || NA || on PmOS Sxmo May 14 2021.
|-

|}

= Special carrier notes =

{{Warning|This section contains providers which do not work or require special settings or actions to work.}}

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:

== USA ==
=== AT&T ===
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. Phone and SMS with PinePhone work out-of-the-box with AT&T. If you transfer a SIM card from another phone you were using with AT&T, you may need to activate the PinePhone through [https://www.att.com/buy/wireless/byod/byod AT&T's website]. Calls and SMS messages work. 4G and MMS work if [https://www.att.com/support/article/wireless/KM1062162/ these settings] are used for APN, MMSC, and Proxy.

AT&T may 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.

=== Consumer Cellular ===

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.

=== Cricket Wireless ===
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).

=== Faith Wireless ===
Faith Wireless is a MVNO that uses AT&T's network. VoLTE was fully supported, but the PinePhone comes up as a Mobile Broadband Device. Faith Wireless does not service Mobile Broadband Devices. (As of February 2022)

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

=== Sprint ===
Sprint is currently not supported due to unknown reasons. Any input regarding this issue is highly appreciated.

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

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

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

=== Verizon ===
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page],
Verizon's primary frequency band for the United States is 13 (700 MHz). Verizon's bands and protocols are summarized on
[https://www.frequencycheck.com/carriers/verizon-wireless-united-states this page]. According to the same page, Verizon might restrict their network to only approved devices.

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.

=== TracFone ===
Following TracFone's [https://www.verizon.com/about/news/verizon-completes-tracfone-wireless-inc-acquisition acquisition by Verizon], support for the AT&T and T-Mobile bands has been deprecated as of early June 2022. TracFone has the same issues with connecting as Verizon, as they now exclusively use Verizon's frequency band.

=== Google Fi ===
Only T-Mobile service works currently, not US Cellular or Sprint.
The APN is h2g2.
Information from [https://forum.pine64.org/showthread.php?tid=11675&page=7 the forum].

Bear in mind that initial activation of the SIM card is not possible without an Android phone running Google Apps.

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.

== Europe ==
=== Telekom Germany ===
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.

=== Orange Poland ===
Setting up dual stack IPv4 and IPv6 may require [https://etherpad.gnome.org/p/dx7pbkPMCytMLMRl1eyo extra work], because the carrier provides IPv4 connectivity on internetipv6 APN via a protocol called CLAT/NAT64.

== Asia ==
=== China Telecom ===
The baseband itself ships with bad (for CDMA, which isn't supported by EG25-G) MBN file for CT, so a force change of MBN file to the generic one is needed to get VoLTE (thus SMS+Call) work.

Run the following AT commands to force ROW_Generic_3GPP which can support VoLTE on CT:
<pre>
AT+QMBNCFG="autosel",0
AT+QMBNCFG="select","ROW_Generic_3GPP"
AT+QCFG="ims",1
</pre>

=== China Unicom ===
SMS/Data works OOTB. 
For calls, apply the [[#China_Telecom]] hack above. 

=== SoftBank ===
SoftBank USIM cards are IMEI-locked, and on top of that will only work on either Android or iOS. 
A free SIM is available, but that one is data only. 
The same problem might exist with MVNO's who make use of the SoftBank network, and therefore it's advised to pick either NTT docomo or au as the MNO.

ソフトバンク社のUSIMカードはIMEIロックで御座います。 
なお、Android又はiOS限定です。 
フリーSIMもありますが、これはデータのみSIMです。 
ソフトバンク社を使っているMVNOで同じ問題があるかもしれませんので、出来ればMNOはNTTドコモ又はauをご選択下さい。

= Known issues =
Known issues:
* The [https://www.frequencycheck.com/models FrequencyCheck model page] does not list either Pine64 or the PinePhone.
* 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.
* 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.
* Some providers may allow only certain known devices identified by their [https://en.wikipedia.org/wiki/Type_Allocation_Code Type Allocation Code].

= MMS workarounds =
These scripts allow partial MMS support on a [[PinePhone]] in distributions without working MMS support:

* JMMS: [https://git.sr.ht/~amindfv/jmms]
* silvermms: [https://gitlab.com/5ilver/silvermms]
* MMS via Matrix with mmmpuppet: [[PinePhone MMS with Matrix]]

There is a Haskel MMS client. MMS can also be manually composed with mmsd on the command line.

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

[[Category:PinePhone]]

PinePhone Carrier Support

2022-11-07T03:14:40Z

EJ5C98: /* Asia */ +UNICOM

{{under construction}}

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

= Check compatibility =
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 in the [[File:Quectel_EG25-G_LTE_Standard_Specification_V1.3.pdf]] modem specification sheet).

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.

= Tested and working carriers =

The following is a list of carriers which has been tested by users and confirmed to be working (excerpt):

== Asia ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
| Japan || SoftBank || Not tested || Unsupported by carrier || No || No || Mobian Phosh, December 2020
|-
| Japan || Rakuten Mobile || Unsupported by carrier || Unsupported by carrier || Yes || Yes || Mobian Phosh, January 2021
|-
| Japan || Rakuten Mobile || Unsupported by carrier || Unsupported by carrier || Yes || No || Manjaro Plasma Mobile February 2021
|-
| Japan || Docomo || Yes || Not tested || Yes || Yes || Mobian Phosh, February 2021
|-
| India || Vodafone / Vi India || Yes || Not tested || Yes || Yes || DanctNIX (Arch Linux ARM) with Phosh, March 2021
|-
| Malaysia || Celcom || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| Malaysia || Maxis || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| Malaysia || U-Mobile || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| Malaysia || Yes || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| South Korea || KT || Yes || Not tested || Yes || Yes || Manjaro Phosh, June 2021
|-
| China || China Mobile || Yes || Not tested || Yes || No || Mobile NixOS, December 2021
|-
| China || China Telecom || Yes (hack needed) || Not tested || Yes (hack needed) || No || AOSC OS Phosh, January 2022
|-
| China || China Unicom || Yes || Not tested || Yes (hack needed) || Yes || postmarketOS v22.06.3 November 2022
|-
| Japan || Rakuten Mobile || Yes || Not tested || Yes || Yes || Mobian Phosh, January 2022 (rivised from January 2021)
|}

== Africa ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129
|-
|}

== Europe ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Ukraine || KyivStar || Yes || Not tested || Yes || Yes || Mobian Phosh(11Nov21)
|-
|-
| Ukraine || Vodafone || Yes || Not tested || Yes || Yes || Manjaro ARM Phosh(29Jun22)
|-
| Sweden || Tele2 || Yes || Not tested || Yes || Not tested || Manjaro ARM Posh
|-
| Sweden || Telenor SE || Not tested || Not tested || Yes || Not tested || Manjaro Plasma Mobile beta2
|-
| UK || Three || Yes || Not tested || Yes || Yes || Manjaro Plasma Mobile beta2
|-
| UK || Vodafone || Yes || Not tested || Yes || Yes || ALARM & pmOS (Phosh?), modem FW latest - 26 Feb 21
|-
| UK || Sky Mobile (O2) || Yes || Not tested || Yes || Yes || ArchLinux Phosh (20210908 image, fully updated) - 3 October 2021
|-
| UK || Smarty Mobile (Three) || Yes || Yes || Yes || Yes || Arch Linux SXMO (Wayland) - 23 March 2022
|-
| France || Orange || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021
|-
| France || SFR || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021
|-
| France || Free || Yes || Not tested || Yes || Yes || pmOS SXMO (Wayland) - 27 March 2022
|-
| Czech Republic || O2 || Yes (only on 2G) || Not tested || Yes || Yes || Mobian Phosh (20210517 image up to date) - 2 June 2021
|-
| 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
|-
| Germany || E-Plus || Yes (sending only 2G) || Not tested || Yes || Yes || Manjaro Phosh and postmarketOS, 2021-10-15
|-
| Germany || Telekom || Yes || Not tested || Yes || Not tested || Mobian Phosh (5.10-sunxi64), 2021-07-28
|-
| Germany || O2 / Telefonica || Yes || Not tested || Yes || Not tested || KPlasma
|-
| Hungary || Telekom || Yes || Not tested || Yes || Yes (IPv4) || Manjaro Phosh Beta 12, 2021-07-30
|-
| Hungary || Telenor/Yettel || Yes || Not tested || Yes || Yes || Mobian-Phosh-20210517, 2021-09-24
|-
| Denmark || CBB || Yes || Not tested || Yes || Yes || Manjaro Plasma Mobile Beta 5, 2021-06-30
|-
| Belgium || Telenet || Yes || Not tested || Yes || Yes || postmarketOS v20.05, v21.03, v21.06 and edge, 2021-08-15
|-
| Belgium || CARREFOUR || Yes || Not tested || Yes || Yes || postmarketOS v20.05, v21.03, v21.06 and edge, 2021-08-15
|-
| Poland || Play || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta 18, 2021-11-14
|-
| Poland || Orange || Yes || No || Yes || Yes (IPv4 & IPv6) || Manjaro Phosh v21.10, 2021-12-23
|-
| Poland || Premium Mobile || Yes || No || Yes || Yes || Manjaro Phosh v22.01, 2022-01-13
|-
| Italy || WindTre Italy || Yes || Not tested || Yes || Yes || Archlinux ARM Plasma Mobile
|-
| Switzerland || Salt || Yes || Not tested || Yes || Yes || Phosh on Mobian + Arch
|}

== North America ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI || Modem Firmware
|-
|-
| USA || AT&T || Yes || Yes || Yes || Yes ||
* Mobian - Phosh
|-
| USA || T-Mobile || Yes || No || Yes || Yes ||
* Arch Linux Arm 2020/11/29
* Mobian - Phosh
* Manjaro - KDE Plasma Mobile
|-
| USA || T-Mobile || Yes || Yes || Yes || Yes ||
* Mobian Bookworm (Phosh) (2022-03-08)
|| EG25GGBR07A08M2G_01.003.01.003
|-
| USA || MetroPCS (T-Mobile) || Yes || No || Yes || Yes ||
*Arch Linux Arm (Phosh,SXMO) 2021/04/29
*Manjaro - Phosh 2021/04/29
*Mobian - Phosh 2021/3/20
|-
| USA || T-Mobile || Yes - buggy || No || Yes - buggy || Yes - buggy ||
*Manjaro - Plasma Dev 2020/11/21
*Ubuntu Touch - 2020/11/26
*KDE Neon 2020/11/02
|-
| USA || Mint Mobile (T-Mobile) || Yes || Yes || Yes || Yes ||
*Mobian - Phosh 2021/3/14
*postMarketOS - Phosh, Sxmo, Plasma Mobile 2021/5/26
*Ubuntu Touch 2021/5/24
*Manjaro - Phosh 2022/3/25
|-
| USA || Patriot Mobile (T-Mobile) || Yes || Yes chatty v0.6.1 mmsd-tng v1.8 || Yes || Yes ||
*Arch Linux Arm - Phosh 2022/01/12
|-
| USA || Tello (T-Mobile) || Yes || Yes || Yes || Yes ||
*DanctNIX (Arch Linux ARM) - Phosh 2022-07-09
|-
| USA || TracFone || No || No || No || No ||
*postMarketOS - Phosh 2022/06/28
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
*Mobian - Phosh 2021/3/1
|-
| USA || US Mobile || Yes || Not tested || Yes || Not Tested ||
*Mobian - Phosh 2022/01/09
|-
| USA || Verizon || No || No || No || No ||
*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)
|-
| USA || Verizon || Not tested || Not tested || Yes || Not via gui ||
*Manjaro - KDE Plasma Mobile 2021/5/10
|-
| USA || Verizon || Yes || Not tested || Yes || Not via gui ||
*Manjaro - Phosh 2021/5/31
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
*postmarketOS - Phosh 2021/5/31
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
*Arch - Phosh 2021/5/31
|-
| Canada || Freedom || Yes || Not tested || Yes || Yes ||
*Arch Pinephone - Phosh (APN: internet.windmobile.ca), 2021/4/25
|-
| Canada || SpeakOut || Yes || Not tested || Yes || Not tested ||
*Mobian - Phosh 2021/11/18
|-
| USA || Consumer Cellular (AT&T) || Yes || No || Yes || Yes ||
*Manjaro - Phosh 2021/06/26
|-
| USA || Google Fi (T-Mobile) || Yes || No || Yes || Yes ||
*Arch Linux Arm - Phosh 0.10.2 2021/05/29
|-
| Mexico || Telcel || Yes || Not tested || Yes || Yes ||
*Mobian - Phosh Weekly 2022/04/13
*PostmarketOS - SXMO De Sway v21.12 (stable) 2022/04/13
*PostmarketOS - Phosh v21.12 (stable) 2022/04/13
*PostmarketOS - Plasma Mobile v21.12 (stable) 2022/04/13
*PostmarketOS - sxmo edge 2021/09/09
|-
| USA || Ting || Yes || Yes - buggy || Yes || Yes ||
*Manjaro - Phosh 2021/12/10
|-
| USA || Simple Mobile || Yes || Yes || Yes || Yes ||
*Mobian - Phosh - Make sure APN is "Simple" in settings (note uppercase S)
|-
|}

== South America ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129
|-
|}

== Australia / Oceania ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129
|-
| Australia || Beyond (Telstra) || Yes || Yes || Yes || Yes || Manjaro Phosh Beta 20.
|-
| Australia || Belong (Telstra) || Yes || Yes || Yes || Yes || Arch (Danctnix), Feb 2022.
|-
| Australia || Optus || Yes || No. Ticket lodged with Chatty and mmsd re multiple APN issue || Yes || Yes || Manjaro Phosh Beta 20. Manjaro Plasma Mobile Beta 9 (Data working with this release). SXMO (Danctnix and PMOS edge December 2021).
|-
| Australia || Amaysim (Optus) || Yes || No. Ticket lodged with Chatty and mmsd re multiple APN issue || Yes || Yes || Manjaro Phosh
|-
| Australia || OPTUS (Dodo) || || ||Yes|| || Manjaro Plasma Mobile 5.23.4, 2021-12.27 (deepsleep disrupts settings)
|-
| Australia || Vodafone || Yes || Yes || Yes (No VoLTE) || Yes || pmOS Edge 5.15.3 kernel, 2022-02-10 with Phosh
|}

== Middle East ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || USSD working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Israel|| Cellcom prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Cellcom Talkman|| receive+notify|| YES || YES (when manually selecting the MMS APN) || ring(VoLTE not working) || YES || on mobian Feb 04, 2022, Earthquake early warning system did not show a notification on Feb 07, 2022
|-
|-
| Israel|| Cellcom Talkman|| NO || NO || NO || ring+ notify (VoLTE not working)|| YES || on Plasma Mobile Feb 04, 2022
|-
|-
| Israel|| Golan TC || receive+notify|| YES || NA || ring+ notify (VoLTE not working) || Yes || on mobian/phosh March 13 2022
|-
|-
| Israel|| Partner prepay || receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Pelephone prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Hot prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| 019 prepay|| No || NA || NA ||Bars only || NA || on PmOS Sxmo May 14 2021.
|-

|}

= Special carrier notes =

{{Warning|This section contains providers which do not work or require special settings or actions to work.}}

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:

== USA ==
=== AT&T ===
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. Phone and SMS with PinePhone work out-of-the-box with AT&T. If you transfer a SIM card from another phone you were using with AT&T, you may need to activate the PinePhone through [https://www.att.com/buy/wireless/byod/byod AT&T's website]. Calls and SMS messages work. 4G and MMS work if [https://www.att.com/support/article/wireless/KM1062162/ these settings] are used for APN, MMSC, and Proxy.

AT&T may 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.

=== Consumer Cellular ===

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.

=== Cricket Wireless ===
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).

=== Faith Wireless ===
Faith Wireless is a MVNO that uses AT&T's network. VoLTE was fully supported, but the PinePhone comes up as a Mobile Broadband Device. Faith Wireless does not service Mobile Broadband Devices. (As of February 2022)

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

=== Sprint ===
Sprint is currently not supported due to unknown reasons. Any input regarding this issue is highly appreciated.

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

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

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

=== Verizon ===
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page],
Verizon's primary frequency band for the United States is 13 (700 MHz). Verizon's bands and protocols are summarized on
[https://www.frequencycheck.com/carriers/verizon-wireless-united-states this page]. According to the same page, Verizon might restrict their network to only approved devices.

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.

=== TracFone ===
Following TracFone's [https://www.verizon.com/about/news/verizon-completes-tracfone-wireless-inc-acquisition acquisition by Verizon], support for the AT&T and T-Mobile bands has been deprecated as of early June 2022. TracFone has the same issues with connecting as Verizon, as they now exclusively use Verizon's frequency band.

=== Google Fi ===
Only T-Mobile service works currently, not US Cellular or Sprint.
The APN is h2g2.
Information from [https://forum.pine64.org/showthread.php?tid=11675&page=7 the forum].

Bear in mind that initial activation of the SIM card is not possible without an Android phone running Google Apps.

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.

== Europe ==
=== Telekom Germany ===
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.

=== Orange Poland ===
Setting up dual stack IPv4 and IPv6 may require [https://etherpad.gnome.org/p/dx7pbkPMCytMLMRl1eyo extra work], because the carrier provides IPv4 connectivity on internetipv6 APN via a protocol called CLAT/NAT64.

== Asia ==
=== China Telecom ===
The baseband itself ships with bad (for CDMA, which isn't supported by EG25-G) MBN file for CT, so a force change of MBN file to the generic one is needed to get VoLTE (thus SMS+Call) work.

Run the following AT commands to force ROW_Generic_3GPP which can support VoLTE on CT:
<pre>
AT+QMBNCFG="autosel",0
AT+QMBNCFG="select","ROW_Generic_3GPP"
AT+QCFG="ims",1
</pre>

=== China Unicom ===
SMS/Data works OOTB. 
For calls, apply the [[#China_Telecom]] hack above. 

=== SoftBank ===
SoftBank USIM cards are IMEI-locked, and on top of that will only work on either Android or iOS. 
A free SIM is available, but that one is data only. 
The same problem might exist with MVNO's who make use of the SoftBank network, and therefore it's advised to pick either NTT docomo or au as the MNO.

ソフトバンク社のUSIMカードはIMEIロックで御座います。 
なお、Android又はiOS限定です。 
フリーSIMもありますが、これはデータのみSIMです。 
ソフトバンク社を使っているMVNOで同じ問題があるかもしれませんので、出来ればMNOはNTTドコモ又はauをご選択下さい。

= Known issues =
Known issues:
* The [https://www.frequencycheck.com/models FrequencyCheck model page] does not list either Pine64 or the PinePhone.
* 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.
* 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.
* Some providers may allow only certain known devices identified by their [https://en.wikipedia.org/wiki/Type_Allocation_Code Type Allocation Code].

= MMS workarounds =
These scripts allow partial MMS support on a [[PinePhone]] in distributions without working MMS support:

* JMMS: [https://git.sr.ht/~amindfv/jmms]
* silvermms: [https://gitlab.com/5ilver/silvermms]
* MMS via Matrix with mmmpuppet: [[PinePhone MMS with Matrix]]

There is a Haskel MMS client. MMS can also be manually composed with mmsd on the command line.

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

[[Category:PinePhone]]

PinePhone Carrier Support

2022-11-07T03:10:02Z

EJ5C98: /* Asia */ +UNICOM

{{under construction}}

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

= Check compatibility =
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 in the [[File:Quectel_EG25-G_LTE_Standard_Specification_V1.3.pdf]] modem specification sheet).

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.

= Tested and working carriers =

The following is a list of carriers which has been tested by users and confirmed to be working (excerpt):

== Asia ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
| Japan || SoftBank || Not tested || Unsupported by carrier || No || No || Mobian Phosh, December 2020
|-
| Japan || Rakuten Mobile || Unsupported by carrier || Unsupported by carrier || Yes || Yes || Mobian Phosh, January 2021
|-
| Japan || Rakuten Mobile || Unsupported by carrier || Unsupported by carrier || Yes || No || Manjaro Plasma Mobile February 2021
|-
| Japan || Docomo || Yes || Not tested || Yes || Yes || Mobian Phosh, February 2021
|-
| India || Vodafone / Vi India || Yes || Not tested || Yes || Yes || DanctNIX (Arch Linux ARM) with Phosh, March 2021
|-
| Malaysia || Celcom || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| Malaysia || Maxis || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| Malaysia || U-Mobile || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| Malaysia || Yes || Yes || Not tested || Yes || Yes || Gentoo, SXMO
|-
| South Korea || KT || Yes || Not tested || Yes || Yes || Manjaro Phosh, June 2021
|-
| China || China Mobile || Yes || Not tested || Yes || No || Mobile NixOS, December 2021
|-
| China || China Telecom || Yes (hack needed) || Not tested || Yes (hack needed) || No || AOSC OS Phosh, January 2022
|-
| China || China Unicom || Yes || Not tested || Yes (hack needed) || Yes || postmarketOS v22.06.3 November 2022
|-
| Japan || Rakuten Mobile || Yes || Not tested || Yes || Yes || Mobian Phosh, January 2022 (rivised from January 2021)
|}

== Africa ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129
|-
|}

== Europe ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Ukraine || KyivStar || Yes || Not tested || Yes || Yes || Mobian Phosh(11Nov21)
|-
|-
| Ukraine || Vodafone || Yes || Not tested || Yes || Yes || Manjaro ARM Phosh(29Jun22)
|-
| Sweden || Tele2 || Yes || Not tested || Yes || Not tested || Manjaro ARM Posh
|-
| Sweden || Telenor SE || Not tested || Not tested || Yes || Not tested || Manjaro Plasma Mobile beta2
|-
| UK || Three || Yes || Not tested || Yes || Yes || Manjaro Plasma Mobile beta2
|-
| UK || Vodafone || Yes || Not tested || Yes || Yes || ALARM & pmOS (Phosh?), modem FW latest - 26 Feb 21
|-
| UK || Sky Mobile (O2) || Yes || Not tested || Yes || Yes || ArchLinux Phosh (20210908 image, fully updated) - 3 October 2021
|-
| UK || Smarty Mobile (Three) || Yes || Yes || Yes || Yes || Arch Linux SXMO (Wayland) - 23 March 2022
|-
| France || Orange || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021
|-
| France || SFR || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta6 and later - 9 march 2021
|-
| France || Free || Yes || Not tested || Yes || Yes || pmOS SXMO (Wayland) - 27 March 2022
|-
| Czech Republic || O2 || Yes (only on 2G) || Not tested || Yes || Yes || Mobian Phosh (20210517 image up to date) - 2 June 2021
|-
| 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
|-
| Germany || E-Plus || Yes (sending only 2G) || Not tested || Yes || Yes || Manjaro Phosh and postmarketOS, 2021-10-15
|-
| Germany || Telekom || Yes || Not tested || Yes || Not tested || Mobian Phosh (5.10-sunxi64), 2021-07-28
|-
| Germany || O2 / Telefonica || Yes || Not tested || Yes || Not tested || KPlasma
|-
| Hungary || Telekom || Yes || Not tested || Yes || Yes (IPv4) || Manjaro Phosh Beta 12, 2021-07-30
|-
| Hungary || Telenor/Yettel || Yes || Not tested || Yes || Yes || Mobian-Phosh-20210517, 2021-09-24
|-
| Denmark || CBB || Yes || Not tested || Yes || Yes || Manjaro Plasma Mobile Beta 5, 2021-06-30
|-
| Belgium || Telenet || Yes || Not tested || Yes || Yes || postmarketOS v20.05, v21.03, v21.06 and edge, 2021-08-15
|-
| Belgium || CARREFOUR || Yes || Not tested || Yes || Yes || postmarketOS v20.05, v21.03, v21.06 and edge, 2021-08-15
|-
| Poland || Play || Yes || Not tested || Yes || Yes || Manjaro Phosh Beta 18, 2021-11-14
|-
| Poland || Orange || Yes || No || Yes || Yes (IPv4 & IPv6) || Manjaro Phosh v21.10, 2021-12-23
|-
| Poland || Premium Mobile || Yes || No || Yes || Yes || Manjaro Phosh v22.01, 2022-01-13
|-
| Italy || WindTre Italy || Yes || Not tested || Yes || Yes || Archlinux ARM Plasma Mobile
|-
| Switzerland || Salt || Yes || Not tested || Yes || Yes || Phosh on Mobian + Arch
|}

== North America ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI || Modem Firmware
|-
|-
| USA || AT&T || Yes || Yes || Yes || Yes ||
* Mobian - Phosh
|-
| USA || T-Mobile || Yes || No || Yes || Yes ||
* Arch Linux Arm 2020/11/29
* Mobian - Phosh
* Manjaro - KDE Plasma Mobile
|-
| USA || T-Mobile || Yes || Yes || Yes || Yes ||
* Mobian Bookworm (Phosh) (2022-03-08)
|| EG25GGBR07A08M2G_01.003.01.003
|-
| USA || MetroPCS (T-Mobile) || Yes || No || Yes || Yes ||
*Arch Linux Arm (Phosh,SXMO) 2021/04/29
*Manjaro - Phosh 2021/04/29
*Mobian - Phosh 2021/3/20
|-
| USA || T-Mobile || Yes - buggy || No || Yes - buggy || Yes - buggy ||
*Manjaro - Plasma Dev 2020/11/21
*Ubuntu Touch - 2020/11/26
*KDE Neon 2020/11/02
|-
| USA || Mint Mobile (T-Mobile) || Yes || Yes || Yes || Yes ||
*Mobian - Phosh 2021/3/14
*postMarketOS - Phosh, Sxmo, Plasma Mobile 2021/5/26
*Ubuntu Touch 2021/5/24
*Manjaro - Phosh 2022/3/25
|-
| USA || Patriot Mobile (T-Mobile) || Yes || Yes chatty v0.6.1 mmsd-tng v1.8 || Yes || Yes ||
*Arch Linux Arm - Phosh 2022/01/12
|-
| USA || Tello (T-Mobile) || Yes || Yes || Yes || Yes ||
*DanctNIX (Arch Linux ARM) - Phosh 2022-07-09
|-
| USA || TracFone || No || No || No || No ||
*postMarketOS - Phosh 2022/06/28
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
*Mobian - Phosh 2021/3/1
|-
| USA || US Mobile || Yes || Not tested || Yes || Not Tested ||
*Mobian - Phosh 2022/01/09
|-
| USA || Verizon || No || No || No || No ||
*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)
|-
| USA || Verizon || Not tested || Not tested || Yes || Not via gui ||
*Manjaro - KDE Plasma Mobile 2021/5/10
|-
| USA || Verizon || Yes || Not tested || Yes || Not via gui ||
*Manjaro - Phosh 2021/5/31
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
*postmarketOS - Phosh 2021/5/31
|-
| USA || Verizon || Yes || Not tested || Yes || Yes ||
*Arch - Phosh 2021/5/31
|-
| Canada || Freedom || Yes || Not tested || Yes || Yes ||
*Arch Pinephone - Phosh (APN: internet.windmobile.ca), 2021/4/25
|-
| Canada || SpeakOut || Yes || Not tested || Yes || Not tested ||
*Mobian - Phosh 2021/11/18
|-
| USA || Consumer Cellular (AT&T) || Yes || No || Yes || Yes ||
*Manjaro - Phosh 2021/06/26
|-
| USA || Google Fi (T-Mobile) || Yes || No || Yes || Yes ||
*Arch Linux Arm - Phosh 0.10.2 2021/05/29
|-
| Mexico || Telcel || Yes || Not tested || Yes || Yes ||
*Mobian - Phosh Weekly 2022/04/13
*PostmarketOS - SXMO De Sway v21.12 (stable) 2022/04/13
*PostmarketOS - Phosh v21.12 (stable) 2022/04/13
*PostmarketOS - Plasma Mobile v21.12 (stable) 2022/04/13
*PostmarketOS - sxmo edge 2021/09/09
|-
| USA || Ting || Yes || Yes - buggy || Yes || Yes ||
*Manjaro - Phosh 2021/12/10
|-
| USA || Simple Mobile || Yes || Yes || Yes || Yes ||
*Mobian - Phosh - Make sure APN is "Simple" in settings (note uppercase S)
|-
|}

== South America ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129
|-
|}

== Australia / Oceania ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Test || Test || Yes || Yes || Yes || Yes || TestOS with Phosh, 20201129
|-
| Australia || Beyond (Telstra) || Yes || Yes || Yes || Yes || Manjaro Phosh Beta 20.
|-
| Australia || Belong (Telstra) || Yes || Yes || Yes || Yes || Arch (Danctnix), Feb 2022.
|-
| Australia || Optus || Yes || No. Ticket lodged with Chatty and mmsd re multiple APN issue || Yes || Yes || Manjaro Phosh Beta 20. Manjaro Plasma Mobile Beta 9 (Data working with this release). SXMO (Danctnix and PMOS edge December 2021).
|-
| Australia || Amaysim (Optus) || Yes || No. Ticket lodged with Chatty and mmsd re multiple APN issue || Yes || Yes || Manjaro Phosh
|-
| Australia || OPTUS (Dodo) || || ||Yes|| || Manjaro Plasma Mobile 5.23.4, 2021-12.27 (deepsleep disrupts settings)
|-
| Australia || Vodafone || Yes || Yes || Yes (No VoLTE) || Yes || pmOS Edge 5.15.3 kernel, 2022-02-10 with Phosh
|}

== Middle East ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || USSD working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Israel|| Cellcom prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Cellcom Talkman|| receive+notify|| YES || YES (when manually selecting the MMS APN) || ring(VoLTE not working) || YES || on mobian Feb 04, 2022, Earthquake early warning system did not show a notification on Feb 07, 2022
|-
|-
| Israel|| Cellcom Talkman|| NO || NO || NO || ring+ notify (VoLTE not working)|| YES || on Plasma Mobile Feb 04, 2022
|-
|-
| Israel|| Golan TC || receive+notify|| YES || NA || ring+ notify (VoLTE not working) || Yes || on mobian/phosh March 13 2022
|-
|-
| Israel|| Partner prepay || receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Pelephone prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Hot prepay|| receive+notify|| NA || NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| 019 prepay|| No || NA || NA ||Bars only || NA || on PmOS Sxmo May 14 2021.
|-

|}

= Special carrier notes =

{{Warning|This section contains providers which do not work or require special settings or actions to work.}}

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:

== USA ==
=== AT&T ===
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. Phone and SMS with PinePhone work out-of-the-box with AT&T. If you transfer a SIM card from another phone you were using with AT&T, you may need to activate the PinePhone through [https://www.att.com/buy/wireless/byod/byod AT&T's website]. Calls and SMS messages work. 4G and MMS work if [https://www.att.com/support/article/wireless/KM1062162/ these settings] are used for APN, MMSC, and Proxy.

AT&T may 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.

=== Consumer Cellular ===

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.

=== Cricket Wireless ===
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).

=== Faith Wireless ===
Faith Wireless is a MVNO that uses AT&T's network. VoLTE was fully supported, but the PinePhone comes up as a Mobile Broadband Device. Faith Wireless does not service Mobile Broadband Devices. (As of February 2022)

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

=== Sprint ===
Sprint is currently not supported due to unknown reasons. Any input regarding this issue is highly appreciated.

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

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

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

=== Verizon ===
According to [https://ltefix.com/wp-content/uploads/USA-Major-Carriers-Bands-Frequencies-CA.pdf this page],
Verizon's primary frequency band for the United States is 13 (700 MHz). Verizon's bands and protocols are summarized on
[https://www.frequencycheck.com/carriers/verizon-wireless-united-states this page]. According to the same page, Verizon might restrict their network to only approved devices.

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.

=== TracFone ===
Following TracFone's [https://www.verizon.com/about/news/verizon-completes-tracfone-wireless-inc-acquisition acquisition by Verizon], support for the AT&T and T-Mobile bands has been deprecated as of early June 2022. TracFone has the same issues with connecting as Verizon, as they now exclusively use Verizon's frequency band.

=== Google Fi ===
Only T-Mobile service works currently, not US Cellular or Sprint.
The APN is h2g2.
Information from [https://forum.pine64.org/showthread.php?tid=11675&page=7 the forum].

Bear in mind that initial activation of the SIM card is not possible without an Android phone running Google Apps.

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.

== Europe ==
=== Telekom Germany ===
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.

=== Orange Poland ===
Setting up dual stack IPv4 and IPv6 may require [https://etherpad.gnome.org/p/dx7pbkPMCytMLMRl1eyo extra work], because the carrier provides IPv4 connectivity on internetipv6 APN via a protocol called CLAT/NAT64.

== Asia ==
=== China Telecom ===
The baseband itself ships with bad (for CDMA, which isn't supported by EG25-G) MBN file for CT, so a force change of MBN file to the generic one is needed to get VoLTE (thus SMS+Call) work.

Run the following AT commands to force ROW_Generic_3GPP which can support VoLTE on CT:
<pre>
AT+QMBNCFG="autosel",0
AT+QMBNCFG="select","ROW_Generic_3GPP"
AT+QCFG="ims",1
</pre>

=== SoftBank ===
SoftBank USIM cards are IMEI-locked, and on top of that will only work on either Android or iOS. 
A free SIM is available, but that one is data only. 
The same problem might exist with MVNO's who make use of the SoftBank network, and therefore it's advised to pick either NTT docomo or au as the MNO.

ソフトバンク社のUSIMカードはIMEIロックで御座います。 
なお、Android又はiOS限定です。 
フリーSIMもありますが、これはデータのみSIMです。 
ソフトバンク社を使っているMVNOで同じ問題があるかもしれませんので、出来ればMNOはNTTドコモ又はauをご選択下さい。

= Known issues =
Known issues:
* The [https://www.frequencycheck.com/models FrequencyCheck model page] does not list either Pine64 or the PinePhone.
* 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.
* 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.
* Some providers may allow only certain known devices identified by their [https://en.wikipedia.org/wiki/Type_Allocation_Code Type Allocation Code].

= MMS workarounds =
These scripts allow partial MMS support on a [[PinePhone]] in distributions without working MMS support:

* JMMS: [https://git.sr.ht/~amindfv/jmms]
* silvermms: [https://gitlab.com/5ilver/silvermms]
* MMS via Matrix with mmmpuppet: [[PinePhone MMS with Matrix]]

There is a Haskel MMS client. MMS can also be manually composed with mmsd on the command line.

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

[[Category:PinePhone]]

Pinebook Pro SPI

2022-11-02T07:38:52Z

EJ5C98: /* Zeroing out the SPI */ an->a

The Pinebook Pro comes equipped with two non-volatile storage components, the eMMC and the SPI. The capacity of the SPI is 128Mbit (16MiB) and it may be used in the boot process.

Boot data can be written to the SPI via two methods: either from within PBP or from a second machine connected to the PBP by USB.

= Writing to SPI from within PBP =

[https://forum.pine64.org/member.php?action=profile&uid=15527 Forum user pcm720] showed an example of writing to the SPI from within PBP in [https://github.com/pcm720/u-boot-build-scripts/releases their self-published version of U-Boot] that offers boot functionality for NVMe drives. It involves use of <code>flash_erase</code> command (available in the mtd-utils package on Arch/Manjaro) and the <code>dd</code> command.

= Writing to SPI from a second machine =

Writing to the SPI from a second machine is more complicated than the other method, but it is the only option when troubleshooting an SPI flash gone wrong. This method works by bringing the PBP into <code>maskrom mode</code> and issuing commands on the second machine that download the flash image onto the PBP.

Upon entering <code>maskrom mode</code>, the power LED on your PBP won't light up and neither will the display. Instead, your second machine, the one connected to your PBP via USB, will indicate <code>maskrom mode</code> by logging to <code>journalctl</code>.

There are two ways to reach <code>maskrom mode</code>, but the first tends to be less reliable.

== Maskrom mode (unreliable method) ==

According to Rockchip documentation, these steps should work; unfortunately, many users have reported them to be unsuccessful. You may need to repeat these steps several times for them to work.

# Press and hold recovery button.
# Short press reset.
# Release recovery button after about 3 seconds.

Why this procedure is unreliable is not clear, but there are two suspicions:

* The button is not working correctly or is just prone to failures.
* The problem occurs only when the SPI was previously flashed.

The button works by shorting two pins in the SPI device. But in some cases it just does nothing. Fortunately, the two pins can shorted by hand, as described in the next method.

== Maskrom mode (reliable method) ==

# Build and install <code>rkdeveloptool</code> (see [https://github.com/rockchip-linux/rkdeveloptool project repository] for instructions)
# Verify successful installation. Running <code>rkdeveloptool --version</code> should output: <code>rkdeveloptool ver 1.3</code>
# Run <code>journalctl -f</code> and keep it running. Once the Pinebook Pro is connected and maskrom mode is reached it will produce additional output.
# Power off the Pinebook Pro.
# Unscrew the bottom cover.
# Remove the metal shield surrounding the main CPU. The shield is held in place by a tape and micro clamps on the board. The clamps can be released with a pry tool and some force. [https://forum.pine64.org/showthread.php?tid=11073&pid=75096#pid75096 This forum post with photos] shows how it can be done.
# Disconnect all (!!!) boot devices (emmc, sdcard, usb).
# Locate SPI flash (component number 29 on [https://wiki.pine64.org/images/4/45/PBPL_S.jpg this photo of the Pinebook Pro internals]).
# Connect your PBP with USB-C - USB-A cable to second machine (PBP on USB-C side)
# Short pins CLK and VSS (see chip diagram to the right for the names of pins). This can be done with a pair of tweezers when short on tools. [[File:Spi.png|right]]
# Power on the Pinebook Pro.
# Press the reset button (component number 28).
# Check if there is new output from <code>journalctl</code> program.
# Check if the PBP connected by running <code>rkdeveloptool ld</code>. If successful, the output should be like: <code>DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=1401 Maskrom</code>

== After entering maskrom mode ==

Now that the PBP is in <code>maskrom mode</code>, you can use <code>rkdeveloptool</code> to write data to the SPI. To do so you'll need the binary file you'll be writing to SPI, which will be referred to as <code>SPI_new.bin</code>, and a helper file named [https://dl.radxa.com/rockpi4/images/loader/spi/rk3399_loader_spinor_v1.15.114.bin rk3399_loader_spinor_v1.15.114.bin].

# Flash the flash helper db file: <code>rkdeveloptool db rk3399_loader_spinor_v1.15.114.bin</code>. If successful, the output should read <code>Downloading bootloader succeeded</code>.
# Flash the new SPI binary: <code>rkdeveloptool wl 0 SPI_new.bin</code>. If successful, the output should read: <code>Write LBA from file (100%)</code>.
# Test the installation: <code>rkdeveloptool td</code>. If successful, output should read <code>Reset Device OK</code>.
# Run <code>rkdeveloptool rd</code> to reboot your Pinebook Pro.

== Zeroing out the SPI ==

In case, you wrote something bad to your SPI, it's helpful to wipe away that data with zeros. To do that, you follow the same steps above to enter <code>maskrom mode</code> and then write a binary file that consists of all zeros.

# Create the binary file <code>dd if=/dev/zero of=zero.bin bs=1M count=16</code>
# Flash the flash helper db file: <code>rkdeveloptool db rk3399_loader_spinor_v1.15.114.bin</code>. If successful, the output should read <code>Downloading bootloader succeeded</code>.
# Flash the new SPI binary: <code>rkdeveloptool wl 0 zero.bin</code>. If successful, the output should read: <code>Write LBA from file (100%)</code>.
# Test the installation: <code>rkdeveloptool td</code>. If successful, output should read <code>Reset Device OK</code>.
# Run <code>rkdeveloptool rd</code> to reboot your Pinebook Pro.

[[Category:PineBook Pro]]

PinePhone FAQ

2022-10-10T13:49:46Z

EJ5C98: /* How powerful is the PinePhone's hardware? */ fix external link to xnux's gstreamer experiment

A list of frequently asked question.

== Hardware ==

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

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

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

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

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

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

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

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

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

=== General ===

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

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

=== Sound ===

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

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

=== Modem ===

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

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

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

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

=== Battery ===

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

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

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

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

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

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

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

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

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

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

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

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

=== Memory ===

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

=== GPS ===

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

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

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

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

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

== Software ==

=== Installation ===

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

See [[PinePhone Installation Instructions]].

=== Updating ===

Read the [[PinePhone Updating Instructions]].

=== Booting ===

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

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

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

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

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

This can be the result of at least one situation:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

=== Other ===

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

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

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

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

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

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

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

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

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

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

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

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

Currently, there isn't any major push to get Android running well on the PinePhone. The developer Icenowy did get a partially working Android image, but it was slow and buggy, lacking some major functions. As of now, use Anbox as an alternative for your android apps, which is currently not included in Ubuntu Touch. In other distributions your millage may vary on what applications will run and how well.

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

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

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

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

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

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

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

The PinePhone uses [https://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf Realtek RTL8723CS] for its Wi-Fi and Bluetooth connectivity. Unfortunately, just like the other Realtek wireless chipsets ''([https://en.wikipedia.org/wiki/Comparison_of_open-source_wireless_drivers see more info])'' - the RTL8723CS chipset requires proprietary firmware for Wi-Fi and Bluetooth functionality. For those who want to create replacement free software firmware, resources like [https://libreplanet.org/wiki/Group:Hardware/research/e-readers/Kobo/Aura_H2O_Edition_2#Firmwares this] and [https://8051enthusiast.github.io/2021/07/05/002-wifi_fun.html this] (different chipsets, but still Realtek) could be a great starting point for further research.

=== SMS ===

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

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

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

You can access the ModemManager using the mmcli command.

'''Mobian:'''

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

'''Manjaro:'''

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

For Mobian, delete all the messages like this:

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

For Manjaro, delete all the messages like this:

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

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

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

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

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

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

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

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

== Accessories ==

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

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

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

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

Replacement batteries for US customers are available in the store.

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

=== External hardware ===

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

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

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

See [[PinePhone Hardware Accessory Compatibility]].

[[Category:PinePhone]]

PinePhone FAQ

2022-10-10T13:41:52Z

EJ5C98: /* What's the status of Android for the PinePhone? */ rearrange words

A list of frequently asked question.

== Hardware ==

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

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

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

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

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

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

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

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

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

=== General ===

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

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

=== Sound ===

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

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

=== Modem ===

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

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

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

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

=== Battery ===

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

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

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

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

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

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

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

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

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

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

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

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

=== Memory ===

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

=== GPS ===

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

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

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

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

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

== Software ==

=== Installation ===

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

See [[PinePhone Installation Instructions]].

=== Updating ===

Read the [[PinePhone Updating Instructions]].

=== Booting ===

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

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

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

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

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

This can be the result of at least one situation:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

=== Other ===

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

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

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

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

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

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

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

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

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

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

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

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

Currently, there isn't any major push to get Android running well on the PinePhone. The developer Icenowy did get a partially working Android image, but it was slow and buggy, lacking some major functions. As of now, use Anbox as an alternative for your android apps, which is currently not included in Ubuntu Touch. In other distributions your millage may vary on what applications will run and how well.

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

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

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

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

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

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

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

The PinePhone uses [https://files.pine64.org/doc/datasheet/pine64/RTL8723BS.pdf Realtek RTL8723CS] for its Wi-Fi and Bluetooth connectivity. Unfortunately, just like the other Realtek wireless chipsets ''([https://en.wikipedia.org/wiki/Comparison_of_open-source_wireless_drivers see more info])'' - the RTL8723CS chipset requires proprietary firmware for Wi-Fi and Bluetooth functionality. For those who want to create replacement free software firmware, resources like [https://libreplanet.org/wiki/Group:Hardware/research/e-readers/Kobo/Aura_H2O_Edition_2#Firmwares this] and [https://8051enthusiast.github.io/2021/07/05/002-wifi_fun.html this] (different chipsets, but still Realtek) could be a great starting point for further research.

=== SMS ===

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

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

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

You can access the ModemManager using the mmcli command.

'''Mobian:'''

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

'''Manjaro:'''

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

For Mobian, delete all the messages like this:

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

For Manjaro, delete all the messages like this:

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

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

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

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

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

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

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

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

== Accessories ==

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

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

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

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

Replacement batteries for US customers are available in the store.

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

=== External hardware ===

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

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

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

See [[PinePhone Hardware Accessory Compatibility]].

[[Category:PinePhone]]