Mobile Carriers in the United States

[RTP]

New Pinephone owner/daily driver user here

Wanted to share my current working info for those looking:

Service: AT&T (monthly plan, started pinephone with working SIM card removed from my Android phone)

Cellular Access point info used:
Name: ATT Phone
APN: NXTGENPHONE

Ubuntu Touch: calls working one way, but not the other, incoming outgoing sms both txts work, cellular data working

Manjaro:
incoming/outgoing calls and sms texts work, cellular data working

Mobian:
incoming/outgoing calls both work well (no drops, can hear both ends), sms texting works both ways, cellular data works as well

[Lt. Dillinger]

You don't need to reset. Since it sees your sim, can you make a phone call? If so, you don't have data enabled, 2g/3g/4g set, or the apn info correctly input. What are your apn settings supposed to be according to mint mobile CS? If you can't make a phone call, did you ensure you did all system updates? An earlier build could not make phone calls well.

I can't make any calls because it's not finding their cell towers (no connection at all)  Yes, it sees the SIM card, and when I click on it, there is a check mark, but then that's it.  I have the data enabled, but it will not let me put in all of the APN info that the tech at Mint Mobile gave me.  Basically, it won't save anything except for the WiFi info.  I've disabled WiFi and Bluetooth when I tried to set up the SIM card and still no luck.  I'll keep trying different things as I have 7 days to get a refund back from Mint if I can't get it working.  Immure as more updates come out things will get sorted out.  I'm not upset as I knew these types of things were going to happen going into this.  I still have very high hopes for this phone.

When you say "not finding their cell towers at all" do you mean you have no bars? If you have no bars, then obviously you won't be able to connect. Maybe you should pop another OS onto a sim card and boot from it just to make sure your hardware is ok. There is for instance the factory test image in the postmarket demo builds. It only tests hardware. July 20 something is the date on it.

No bars because it won't connect to any cell towers.  My wife works fine, bluetooth too, but it's hit and miss on finding the SIM card too.  Sometimes I reboot and it finds the SOM card, other times not.  I've got a buddy close to me who's a cell phone guru and I'm gonna let him have a look.  We've been talking about this phone, so he's a bit interested in it too.

The issue could be the OS, I have tried the factory image of the Postmarket os image and it shows the modem is working but when using UBports it does not work with my T-mobile sim. Another thing is I've heard about the firmware for the modem being corrupted in some cases. Have you tried another os such as Mobian to see if it will work with your SIM card?

No I haven't as I really want to stick with Ubuntu Touch OS.  I'm hoping that with updates many of these issues will be worked out.  What I find interesting is the tech at Mint Mobile said she was able to help some users get their phones working.  So I guess it is a hit and miss, phone by phone situation which I find intriguing.  It's kind of like the squeak you hear in your car, it's there daily but the day you take it to the dealership, it's gone.  

[daniel]

It's possible that different accounts have different RF band permission.  For instance, an AT&T unlimited plan might work different than a "pay as you go" plan or various plans with AT&T network MVNOs.

So you pretty much have to try out each plan on each service to know if it's going to work.

I don't have a PinePhone, but I've done the "bring your own device" thing on discount MVNOs about a dozen times over the years.  So I've run into these "gotchas" a lot.  Sometimes it's possible to find the actual technical restrictions of a given plan, sometimes it is not.

These appear to be the bands the PinePhone will work on:

Code:

LTE: B1, B2, B3, B4, B5, B7, B8, B12, B13, B18, B19, B20, B25, B26, B28, B38, B39, B40, B41
WCDMA: B1, B2, B4, B5, B6, B8, B19
GSM: 850, 900, 1800, 1900 (MHz)

Are there current software restrictions on this?
At least you can mostly eliminate some plans just knowing this.

I am not sure I fully understand what you are saying.
In your example, AT&T has different plans, but they should all use the same network, or not?
I thought the phone networks were dependent on the carrier (Verizon, AT&T, etc).
Are you saying that knowing the carrier is not enough to know if it is going to work or not?
Same question but from another angle. Can AT&T (or any other carrier) change network type depending on the plan?

Can you please clarify on this?

[rocket2nfinity]

It's possible that different accounts have different RF band permission.  For instance, an AT&T unlimited plan might work different than a "pay as you go" plan or various plans with AT&T network MVNOs.

So you pretty much have to try out each plan on each service to know if it's going to work.

I don't have a PinePhone, but I've done the "bring your own device" thing on discount MVNOs about a dozen times over the years.  So I've run into these "gotchas" a lot.  Sometimes it's possible to find the actual technical restrictions of a given plan, sometimes it is not.

These appear to be the bands the PinePhone will work on:

Code:

LTE: B1, B2, B3, B4, B5, B7, B8, B12, B13, B18, B19, B20, B25, B26, B28, B38, B39, B40, B41
WCDMA: B1, B2, B4, B5, B6, B8, B19
GSM: 850, 900, 1800, 1900 (MHz)

Are there current software restrictions on this?
At least you can mostly eliminate some plans just knowing this.

I am not sure I fully understand what you are saying.
In your example, AT&T has different plans, but they should all use the same network, or not?
I thought the phone networks were dependent on the carrier (Verizon, AT&T, etc).
Are you saying that knowing the carrier is not enough to know if it is going to work or not?
Same question but from another angle. Can AT&T (or any other carrier) change network type depending on the plan?

Can you please clarify on this?

What he's trying to say is that some devices are limited to which bands they can access. It is not based on plan, but on device. For instance, when t-mobile took over sprint they bricked band 41 for all but new 5g devices because spectrum sharing has not worked out yet.

What they can do is prioritize traffic based on plan (by apn) which can slow your speeds. But if your modem is capable, you will get access to the band unless they have a specific whitelist of block device imei's that are allowed or not - which verizon and AT&T do. In those cases, network access is blocked by device imei, not by plan. Usually this is done because a device does not meet the carriers access requirements, such as all the devices that are about to get kicked off because of no VoLTE support. The pinephone does have support for VoLTE, but whitelisting may still be an issue. T-mobile does not use whitelists.

---

I can't make any calls because it's not finding their cell towers (no connection at all)  Yes, it sees the SIM card, and when I click on it, there is a check mark, but then that's it.  I have the data enabled, but it will not let me put in all of the APN info that the tech at Mint Mobile gave me.  Basically, it won't save anything except for the WiFi info.  I've disabled WiFi and Bluetooth when I tried to set up the SIM card and still no luck.  I'll keep trying different things as I have 7 days to get a refund back from Mint if I can't get it working.  Immure as more updates come out things will get sorted out.  I'm not upset as I knew these types of things were going to happen going into this.  I still have very high hopes for this phone.

When you say "not finding their cell towers at all" do you mean you have no bars? If you have no bars, then obviously you won't be able to connect. Maybe you should pop another OS onto a sim card and boot from it just to make sure your hardware is ok. There is for instance the factory test image in the postmarket demo builds. It only tests hardware. July 20 something is the date on it.

No bars because it won't connect to any cell towers.  My wife works fine, bluetooth too, but it's hit and miss on finding the SIM card too.  Sometimes I reboot and it finds the SOM card, other times not.  I've got a buddy close to me who's a cell phone guru and I'm gonna let him have a look.  We've been talking about this phone, so he's a bit interested in it too.

The issue could be the OS, I have tried the factory image of the Postmarket os image and it shows the modem is working but when using UBports it does not work with my T-mobile sim. Another thing is I've heard about the firmware for the modem being corrupted in some cases. Have you tried another os such as Mobian to see if it will work with your SIM card?

No I haven't as I really want to stick with Ubuntu Touch OS.  I'm hoping that with updates many of these issues will be worked out.  What I find interesting is the tech at Mint Mobile said she was able to help some users get their phones working.  So I guess it is a hit and miss, phone by phone situation which I find intriguing.  It's kind of like the squeak you hear in your car, it's there daily but the day you take it to the dealership, it's gone.  

This might sound silly but have you tried taking the phone somewhere else and seeing if it can access Mint? In your other post, your phone clearly sees a band 13 tower which is verizon based. You simply may not have a t-mobile tower close enough for the pinephone to access.

[klick]

Hello All,
I just recently received my Ubuntu CE and hoped to use it on T-Mobile. Currently updated to OS Build Number 2020-07-27/2, version 116. I used my T-Mobile SIM from my iPhone and the PinePhone indicates that it is connected to the T-Mobile network but incoming and outgoing calls do not work. I was able to successfully send texts with the PinePhone to another iPhone but the replies were not routed to the PinePhone. The routing issue was probably due to still being linked to my iPhone and Apple's iMessage servers and I was not expecting for text to work properly without completing disconnecting my number from Apple's servers.

When making outgoing calls after rebooting, the dial pad has audible beeps and the PinePhone attempts to make the call. Shortly thereafter, the phone states that the call "Failed". After that first call attempt, the dial pad no longer has the audible beeps when being pressed. When an incoming call to the PinePhone was tried, the PinePhone did not ring but the call was instead routed back through Apple's servers (I assume, as I was able to answer the call on my Apple watch).

I have in the past been able to use the same SIM and switch back and forth between an iPhone and Android phone and still be able to make and receive calls without issue but something is not working or set properly on the PinePhone. The PinePhone appears to automatically detect the T-Mobile APN settings but call routing is not working for me.

I have read that others have been able to use T-Mobile but I am not sure what is different about my situation.

[tophneal]

Hello All,
I just recently received my Ubuntu CE and hoped to use it on T-Mobile. Currently updated to OS Build Number 2020-07-27/2, version 116. I used my T-Mobile SIM from my iPhone and the PinePhone indicates that it is connected to the T-Mobile network but incoming and outgoing calls do not work. I was able to successfully send texts with the PinePhone to another iPhone but the replies were not routed to the PinePhone. The routing issue was probably due to still being linked to my iPhone and Apple's iMessage servers and I was not expecting for text to work properly without completing disconnecting my number from Apple's servers.

When making outgoing calls after rebooting, the dial pad has audible beeps and the PinePhone attempts to make the call. Shortly thereafter, the phone states that the call "Failed". After that first call attempt, the dial pad no longer has the audible beeps when being pressed. When an incoming call to the PinePhone was tried, the PinePhone did not ring but the call was instead routed back through Apple's servers (I assume, as I was able to answer the call on my Apple watch).

I have in the past been able to use the same SIM and switch back and forth between an iPhone and Android phone and still be able to make and receive calls without issue but something is not working or set properly on the PinePhone. The PinePhone appears to automatically detect the T-Mobile APN settings but call routing is not working for me.

I have read that others have been able to use T-Mobile but I am not sure what is different about my situation.

Have you already verified the APN info in UBports is correct for T-Mobile?

[Lt. Dillinger]

It's possible that different accounts have different RF band permission.  For instance, an AT&T unlimited plan might work different than a "pay as you go" plan or various plans with AT&T network MVNOs.

So you pretty much have to try out each plan on each service to know if it's going to work.

I don't have a PinePhone, but I've done the "bring your own device" thing on discount MVNOs about a dozen times over the years.  So I've run into these "gotchas" a lot.  Sometimes it's possible to find the actual technical restrictions of a given plan, sometimes it is not.

These appear to be the bands the PinePhone will work on:

Code:

LTE: B1, B2, B3, B4, B5, B7, B8, B12, B13, B18, B19, B20, B25, B26, B28, B38, B39, B40, B41
WCDMA: B1, B2, B4, B5, B6, B8, B19
GSM: 850, 900, 1800, 1900 (MHz)

Are there current software restrictions on this?
At least you can mostly eliminate some plans just knowing this.

I am not sure I fully understand what you are saying.
In your example, AT&T has different plans, but they should all use the same network, or not?
I thought the phone networks were dependent on the carrier (Verizon, AT&T, etc).
Are you saying that knowing the carrier is not enough to know if it is going to work or not?
Same question but from another angle. Can AT&T (or any other carrier) change network type depending on the plan?

Can you please clarify on this?

What he's trying to say is that some devices are limited to which bands they can access. It is not based on plan, but on device. For instance, when t-mobile took over sprint they bricked band 41 for all but new 5g devices because spectrum sharing has not worked out yet.

What they can do is prioritize traffic based on plan (by apn) which can slow your speeds. But if your modem is capable, you will get access to the band unless they have a specific whitelist of block device imei's that are allowed or not - which verizon and AT&T do. In those cases, network access is blocked by device imei, not by plan. Usually this is done because a device does not meet the carriers access requirements, such as all the devices that are about to get kicked off because of no VoLTE support. The pinephone does have support for VoLTE, but whitelisting may still be an issue. T-mobile does not use whitelists.

---

When you say "not finding their cell towers at all" do you mean you have no bars? If you have no bars, then obviously you won't be able to connect. Maybe you should pop another OS onto a sim card and boot from it just to make sure your hardware is ok. There is for instance the factory test image in the postmarket demo builds. It only tests hardware. July 20 something is the date on it.

No bars because it won't connect to any cell towers.  My wife works fine, bluetooth too, but it's hit and miss on finding the SIM card too.  Sometimes I reboot and it finds the SOM card, other times not.  I've got a buddy close to me who's a cell phone guru and I'm gonna let him have a look.  We've been talking about this phone, so he's a bit interested in it too.

The issue could be the OS, I have tried the factory image of the Postmarket os image and it shows the modem is working but when using UBports it does not work with my T-mobile sim. Another thing is I've heard about the firmware for the modem being corrupted in some cases. Have you tried another os such as Mobian to see if it will work with your SIM card?

No I haven't as I really want to stick with Ubuntu Touch OS.  I'm hoping that with updates many of these issues will be worked out.  What I find interesting is the tech at Mint Mobile said she was able to help some users get their phones working.  So I guess it is a hit and miss, phone by phone situation which I find intriguing.  It's kind of like the squeak you hear in your car, it's there daily but the day you take it to the dealership, it's gone.  

This might sound silly but have you tried taking the phone somewhere else and seeing if it can access Mint? In your other post, your phone clearly sees a band 13 tower which is verizon based. You simply may not have a t-mobile tower close enough for the pinephone to access.

Yes, I was in two different areas today and still no connection.  Also, according to the Mint Mobile website, where I live the map shows very good coverage.  I've got to take my wife's iPhone in for a screen repair and I'm going to ask the folks there for some suggestion.  Maybe that can help, maybe no.

[natasha]

It's possible that different accounts have different RF band permission.  For instance, an AT&T unlimited plan might work different than a "pay as you go" plan or various plans with AT&T network MVNOs.

So you pretty much have to try out each plan on each service to know if it's going to work.

I don't have a PinePhone, but I've done the "bring your own device" thing on discount MVNOs about a dozen times over the years.  So I've run into these "gotchas" a lot.  Sometimes it's possible to find the actual technical restrictions of a given plan, sometimes it is not.

These appear to be the bands the PinePhone will work on:

Code:

LTE: B1, B2, B3, B4, B5, B7, B8, B12, B13, B18, B19, B20, B25, B26, B28, B38, B39, B40, B41
WCDMA: B1, B2, B4, B5, B6, B8, B19
GSM: 850, 900, 1800, 1900 (MHz)

Are there current software restrictions on this?
At least you can mostly eliminate some plans just knowing this.

I am not sure I fully understand what you are saying.
In your example, AT&T has different plans, but they should all use the same network, or not?
I thought the phone networks were dependent on the carrier (Verizon, AT&T, etc).
Are you saying that knowing the carrier is not enough to know if it is going to work or not?
Same question but from another angle. Can AT&T (or any other carrier) change network type depending on the plan?

Can you please clarify on this?

What he's trying to say is that some devices are limited to which bands they can access. It is not based on plan, but on device. For instance, when t-mobile took over sprint they bricked band 41 for all but new 5g devices because spectrum sharing has not worked out yet.

What they can do is prioritize traffic based on plan (by apn) which can slow your speeds. But if your modem is capable, you will get access to the band unless they have a specific whitelist of block device imei's that are allowed or not - which verizon and AT&T do. In those cases, network access is blocked by device imei, not by plan. Usually this is done because a device does not meet the carriers access requirements, such as all the devices that are about to get kicked off because of no VoLTE support. The pinephone does have support for VoLTE, but whitelisting may still be an issue. T-mobile does not use whitelists.

---

Since it looks the limiting factor is the hardware, not sure is the OS would make any difference. Meaning, if a carrier works for UB ports have to work also for the rest of OS distributions... (and vice versa).

[klick]

Hello All,
I just recently received my Ubuntu CE and hoped to use it on T-Mobile. Currently updated to OS Build Number 2020-07-27/2, version 116. I used my T-Mobile SIM from my iPhone and the PinePhone indicates that it is connected to the T-Mobile network but incoming and outgoing calls do not work. I was able to successfully send texts with the PinePhone to another iPhone but the replies were not routed to the PinePhone. The routing issue was probably due to still being linked to my iPhone and Apple's iMessage servers and I was not expecting for text to work properly without completing disconnecting my number from Apple's servers.

When making outgoing calls after rebooting, the dial pad has audible beeps and the PinePhone attempts to make the call. Shortly thereafter, the phone states that the call "Failed". After that first call attempt, the dial pad no longer has the audible beeps when being pressed. When an incoming call to the PinePhone was tried, the PinePhone did not ring but the call was instead routed back through Apple's servers (I assume, as I was able to answer the call on my Apple watch).

I have in the past been able to use the same SIM and switch back and forth between an iPhone and Android phone and still be able to make and receive calls without issue but something is not working or set properly on the PinePhone. The PinePhone appears to automatically detect the T-Mobile APN settings but call routing is not working for me.

I have read that others have been able to use T-Mobile but I am not sure what is different about my situation.

Have you already verified the APN info in UBports is correct for T-Mobile?

[tophneal]

For some reason your reply appears as empty. Hopefully, it's just on my end.