PINE64 - User contributions [en]

PinePhone Carrier Support

2021-05-29T19:52:27Z

QC8086: /* North America */

{{under construction}}

{{hint|MMS currently doesn't work in any distribution on the PinePhone without a [[PinePhone_Carrier_Support#MMS_workarounds|script]]! This means images and group chats will not work in text messages.}}

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

= 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 [https://www.quectel.com/UploadFile/Product/Quectel_EG25-G_LTE_Specification_V1.1.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 2020
|-
| 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
|}

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

== North America ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| USA || T-Mobile || Yes || No || Yes || Yes || Arch Linux Arm 2020/11/29, Mobian Phosh, Manjaro KDE Plasma Mobile
|-
| USA || MetroPCS (T-Mobile) || Yes || No || Yes || Yes || Arch Linux Arm (Phosh,SXMO) 2021/04/29, Manjaro Arm 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 || Not tested || Yes || Yes || Mobian Phosh, 2021/3/14
|-
| USA || Verizon || Yes || Not tested || Yes || Yes || Mobian Phosh, 2021/3/1
|-
| USA || Verizon || Not tested || Not tested || Yes || Not via gui || Manjaro KDE Plasma Mobile 2021/5/10
|-
| Canada || Freedom || Yes || Not tested || Yes || Yes || Arch Pinephone Phosh (APN: internet.windmobile.ca), 2021/4/25
|-
| USA || FaithWireless (AT&T) || Yes || No || Yes || Yes || Arch Linux Arm 2021/04/29 with Phosh 0.10.1-1, see the [[PinePhone_Carrier_Support#AT.26T|AT&T issues]] below.
|-
| USA || Google Fi (T-Mobile) || Yes || No || Yes || Yes || Arch Linux Arm 2021/05/29 with Phosh 0.10.2.
|}

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

== Middle East ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Israel|| Cellcom prepay|| receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-

|-
| Israel|| Golan TC || receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Partner prepay || receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Pelephone prepay|| receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Hot prepay|| receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| 019 prepay|| No || 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. The PinePhone seems to work out-of-the-box with AT&T. If you transfer a SIM card from another phone you were using with AT&T, you need to activate the PinePhone through [https://www.att.com/buy/wireless/byod/byod AT&T's website]. Calls and SMS messages work. VoLTE is as yet untested.

However, it is likely AT&T will drop support with their network upgrade in the near future like their child company Cricket Wireless already has. [https://www.att.com/ecms/dam/att/consumer/help/pdf/Devices-Working-on-ATT-Network.pdf This page] lists their supported devices for their new network.

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

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

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

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

* 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

2021-05-29T16:39:42Z

QC8086: /* Google Fi */

{{under construction}}

{{hint|MMS currently doesn't work in any distribution on the PinePhone without a [[PinePhone_Carrier_Support#MMS_workarounds|script]]! This means images and group chats will not work in text messages.}}

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

= 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 [https://www.quectel.com/UploadFile/Product/Quectel_EG25-G_LTE_Specification_V1.1.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 2020
|-
| 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
|}

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

== North America ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| USA || T-Mobile || Yes || No || Yes || Yes || Arch Linux Arm 2020/11/29, Mobian Phosh, Manjaro KDE Plasma Mobile
|-
| USA || MetroPCS (T-Mobile) || Yes || No || Yes || Yes || Arch Linux Arm (Phosh,SXMO) 2021/04/29, Manjaro Arm 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 || Not tested || Yes || Yes || Mobian Phosh, 2021/3/14
|-
| USA || Verizon || Yes || Not tested || Yes || Yes || Mobian Phosh, 2021/3/1
|-
| USA || Verizon || Not tested || Not tested || Yes || Not via gui || Manjaro KDE Plasma Mobile 2021/5/10
|-
| Canada || Freedom || Yes || Not tested || Yes || Yes || Arch Pinephone Phosh (APN: internet.windmobile.ca), 2021/4/25
|-
| USA || FaithWireless (AT&T) || Yes || No || Yes || Yes || Arch Linux Arm 2021/04/29 with Phosh 0.10.1-1, see the [[PinePhone_Carrier_Support#AT.26T|AT&T issues]] below.
|-
|}

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

== Middle East ==
{| class="wikitable sortable"
!Country || Carrier name || SMS working || MMS working || Calls working || Data working || Tested OS (with version) and UI
|-
|-
| Israel|| Cellcom prepay|| receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-

|-
| Israel|| Golan TC || receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Partner prepay || receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Pelephone prepay|| receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| Hot prepay|| receive+notify|| NA || ring+ notify || NA || on PmOS Sxmo May 14 2021.
|-
|-
| Israel|| 019 prepay|| No || 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. The PinePhone seems to work out-of-the-box with AT&T. If you transfer a SIM card from another phone you were using with AT&T, you need to activate the PinePhone through [https://www.att.com/buy/wireless/byod/byod AT&T's website]. Calls and SMS messages work. VoLTE is as yet untested.

However, it is likely AT&T will drop support with their network upgrade in the near future like their child company Cricket Wireless already has. [https://www.att.com/ecms/dam/att/consumer/help/pdf/Devices-Working-on-ATT-Network.pdf This page] lists their supported devices for their new network.

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

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

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

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

* 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 APN Settings

2020-11-04T01:47:33Z

QC8086: Add Google Fi APN settings

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

= Setting the APN =

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

== Distributions with Phosh ==

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



= List of tested carriers =

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

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

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

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

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

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

== Free (France) ==

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

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

== Google Fi ==

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

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

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

== Mineo (Japan) ==

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

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

APNs are provided by Mineo

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

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

== Mint Mobile (USA) ==

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

Use the following APN settings:

Name: Ultra
APN: Wholesale

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

== Mobile Vikings (Belgium) ==

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

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

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

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

== Penny Mobil (Germany) ==

APN settings:

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

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

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

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

== Red Pocket (USA) ==

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

APN settings:

name: Red Pocket
APN: RESELLER

== Simyo (Spain) ==

APN settings:
APN: orangeworld

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

== Telekom (Germany) ==

APN settings:

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

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

== Telstra (Australia) ==
APN settings:

Name: Telstra Internet/WAP
APN: telstra.iph

== Tracfone (USA) ==

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

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

Use the following APN settings:

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

To use Verizon's network:

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

== Verizon Contract (USA) ==

There are several APN names which can be used, but the following has worked fairly reliably for calls, SMS and data on Verizon under arch:

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

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

vzwapp
vzwims

== Virgin Mobile (Canada) ==

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

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

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

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

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

= Carriers that do not work =

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

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

== Sprint (USA) ==

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

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

== Other ==

Other VoLTE services.

= External links =

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

[[Category:PinePhone]]

User:Oogwaymaki/Kernel Installation

2020-09-29T02:55:10Z

QC8086: Rewrite intro for clarity and grammar

{{hint|This page could use some improvement, and is slightly outdated. You're welcome to contribute.}}

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

There are many reasons you may want to install a custom kernel. Perhaps there's a kernel that isn't yet packaged for your distribution with bug fixes or new features. There are also features that may be desirable to some, but aren't included in the default kernel since they might cause problems for other users.

You also might just want to help kernel developers by testing for bugs in the latest mainline kernel release.

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

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

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

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

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

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

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

Prerequisites:

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

<pre>
depmod -a

</pre>

Install dependencies:

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

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

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

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

Extract the kernel:

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

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

A default Mobian Installation looks like this:

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

Notice the small size on the /boot partition.

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

Easiest thing to do:

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

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

How to get and update initrd image:

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

</pre>

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

<pre>

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

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

Change the old boot.cmd to the new settings:

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

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

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

led 1 on

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

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

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

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

led 2 on

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

</pre>

Remove the old boot.cmd

<pre>

# rm boot.cmd

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

<pre>

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

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

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

led 1 on

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

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

led 2 on

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

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

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

== References ==

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

[[Category:PinePhone]]