After many hours of reading and trouble shooting I'm ready to throw my note 3 out a window. I (like a dumb ass) purchased my note 3 from Craigslist. Three months to the day the device was blacklisted do to non payment. After arguing with the police and tmobile I decided to pay to have the imei remotely fixed. Now the phone works but will not automatically connect to 4g or lte. The guy that fixed the imei sweres up and down that his fix has never effected data in this way. If I force lte in the service mode it connects some of the time. Once it's connected if I get a phone call the data drops to G and will not go back to lte. I've checked apns, had metro pcs reset my account, tried different roms, kernels, and modems. If anyone has any advice I would be forever greatful.
I'm wondering if anyone else is or has been experiencing this issue. For the last couple weeks my black Pixel 2XL 128gig on Android 8.0 is having a problem switching from LTE to HSPA when trying to make a phone call. I've been on the phone with both Google and AT&T numerous times. ATT deactivated and reactivated my sim card. I ended up getting a new sim card and still didn't fix the problem. Google eventually sent me a brand new phone and I'm still having the same problem. Now Google wants to send me another new phone. I had the original pixel XL on ATT and did not have this issue at all. Anyone else having a similar issue?
Uh... Yes, that's normal, you don't have VoLTE enabled. There's a whole thread about enabling it with AT&T here on the boards. TLR of that thread, download the Oreo 8.1 beta, enable VoLTE in the software, talk to AT&T to enable enhanced voice features.
Sent from my Pixel 2 XL using Tapatalk
You may need a new sim card, I had similar issues, visited an AT&T store and it was fixed within five minutes.
dratsablive said:
You may need a new sim card, I had similar issues, visited an AT&T store and it was fixed within five minutes.
Click to expand...
Click to collapse
I did get a new SIM card. Still was experiencing the same problem. I updated to 8.1 beta to and enabled enhanced LTE to see if that fixes the issue.
JaredC01 said:
Uh... Yes, that's normal, you don't have VoLTE enabled. There's a whole thread about enabling it with AT&T here on the boards. TLR of that thread, download the Oreo 8.1 beta, enable VoLTE in the software, talk to AT&T to enable enhanced voice features.
Click to expand...
Click to collapse
It definitely was not normal. I had a the first pixel XL before this and did not experience this issue.
dutchy716 said:
It definitely was not normal. I had a the first pixel XL before this and did not experience this issue.
Click to expand...
Click to collapse
Then somehow you had VoLTE on your first Pixel. Without VoLTE, the phone will 100% of the time kick back out to HSPA+ when you make a phone call. That's been the case with every phone I've owned prior to VoLTE and actually having a phone that had and made use of VoLTE.
Sent from my Pixel 2 XL using Tapatalk
JaredC01 said:
Then somehow you had VoLTE on your first Pixel. Without VoLTE, the phone will 100% of the time kick back out to HSPA+ when you make a phone call. That's been the case with every phone I've owned prior to VoLTE and actually having a phone that had and made use of VoLTE.
Click to expand...
Click to collapse
I know it's supposed to kick back to HSPA when making a phone call. The problem is that it doesn't. Instead of going to HSPA I lose signal completely. The phone will try to make the phone call and then the phone will manually hang up like I hit the end call button but it does it automatically. Then I either have to toggle airplane mode or reboot the phone to get LTE again.
dutchy716 said:
I know it's supposed to kick back to HSPA when making a phone call. The problem is that it doesn't. Instead of going to HSPA I lose signal completely. The phone will try to make the phone call and then the phone will manually hang up like I hit the end call button but it does it automatically. Then I either have to toggle airplane mode or reboot the phone to get LTE again.
Click to expand...
Click to collapse
Ah ha, your original post didn't make it sound like that. In that case, maybe try a new SIM card?
Edit: Re-read the first post and you already tried a new SIM. Have you tried a SIM from someone else, maybe on another Network to see if it's the phone or the network?
JaredC01 said:
Ah ha, your original post didn't make it sound like that. In that case, maybe try a new SIM card?
Click to expand...
Click to collapse
Ya I got a new SIM the other day. I talked to jcase about it and he believes it's a provisioning issue on AT&Ts end. I was just wondering if anyone else has experienced this and if they found a solution to it. I did end up upgrading to 8.1 beta and that obviously fixed it because of enhanced calling. It's just weird because I haven't found anybody else who has had this problem.
dutchy716 said:
I'm wondering if anyone else is or has been experiencing this issue. For the last couple weeks my black Pixel 2XL 128gig on Android 8.0 is having a problem switching from LTE to HSPA when trying to make a phone call. I've been on the phone with both Google and AT&T numerous times. ATT deactivated and reactivated my sim card. I ended up getting a new sim card and still didn't fix the problem. Google eventually sent me a brand new phone and I'm still having the same problem. Now Google wants to send me another new phone. I had the original pixel XL on ATT and did not have this issue at all. Anyone else having a similar issue?
Click to expand...
Click to collapse
One thing you should always try before going to the provider is a safe mode boot. I tried a new rom and could not get data. Most things worked but no data. I could call and WIFI but no cellular data. In safe mode I got data. That tells you some third party APP is responsible.
JaredC01 said:
Then somehow you had VoLTE on your first Pixel. Without VoLTE, the phone will 100% of the time kick back out to HSPA+ when you make a phone call. That's been the case with every phone I've owned prior to VoLTE and actually having a phone that had and made use of VoLTE.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
What does VoLTE have to do having LTE data while on a call? I don't see any reason why you couldn't have LTE available for data even when it doesn't support LTE for voice calls.
I've had LTE switch to H every time I've made a phone call on my Nexus 5, Nexus 5X and Pixel 2 XL. Since 8.1 I've had VoLTE. I know because when I make a call I see the "HD" which is VoLTE but the LTE still switches to H so it seems like the two are related.
jimv1983 said:
What does VoLTE have to do having LTE data while on a call?
Click to expand...
Click to collapse
Uhm, everything? VoLTE is Voice over LTE which implies that you have an LTE radio connection (as opposed to a UMTS/WCDMA/HS*PA radio connection).
jimv1983 said:
I don't see any reason why you couldn't have LTE available for data even when it doesn't support LTE for voice calls.
Click to expand...
Click to collapse
That's because you don't understand the fundamental way in which cellular networks work. Don't feel bad - you're not alone; it's a complicated topic.
The radio on your device can only support one type of radio connection at a time. There are a multitude of reasons for this: capacity on the chip, the need for multiple amplifiers to work simultaneously (because typically carriers use different parts of the radio spectrum for one Radio Access Type than another), antenna capacity etc. Keep in mind that are scenarios in which your device is already juggling quasi multiple radio connects, e.g. carrier aggregation.
Don't get me wrong, there have been devices that supported multiple simultaneous radio access technologies on a single device, but that's because they had multiple radios. These were older devices on IS-95 CDMA carriers such a Sprint when they were pushing WIMAX, and even I believe some Verizon devices which allowed them to do multi-RAB for simultaneous voice and calls before their CDMA infrastructure was upgraded to allow this (and prior to their VoLTE launch). These devices are few and far between.
One last point on this topic: the network handles handover between RATs (though it's possible for the device to only support one RAT). If you were allowed to have simultaneous connections to two radio access types, the network would be juggling twice the resources for your device (the transmit and receive portion of a data connection or call is not the only resource involved). This is yet another reason why in most circumstances you'll never see two simultaneous RATs for one device: it costs the network money. Unless you're trying to cover up for a deficiency is your network architecture (e.g. IS-95 CDMA networks lack of support for multi-RAB. Multi-RAB refers to radio access bearers, basically multiple virtual connections across a single radio link. You might think of this like VLANs on an ethernet network.) you don't put the network and engineering expenses to support multiple RATs..
jimv1983 said:
I've had LTE switch to H every time I've made a phone call on my Nexus 5, Nexus 5X and Pixel 2 XL. Since 8.1 I've had VoLTE. I know because when I make a call I see the "HD" which is VoLTE but the LTE still switches to H so it seems like the two are related.
Click to expand...
Click to collapse
Actually, no. "HD" stands for "HD Voice" which is a better codec. Depending on the carrier, you may get HD voice on a 3G RAT and VoLTE RAT or just on a VoLTE RAT. Keep in mind that HD Voice uses more radio resource than the standard GSM codecs, so there's a trade-off involved here. LTE is more spectral efficient, so offering the higher quality, higher bit rate voice codec on VoLTE has less of an impact on the network than offering it on VoLTE + 3G. So depending on your carrier, they may or may not allow the HD codec on non-VoLTE radio connections. Either way, HD does not in any way shape or form constitute having a VoLTE connection, since it's radio access type independent.
RomPlinker said:
Uhm, everything? VoLTE is Voice over LTE which implies that you have an LTE radio connection (as opposed to a UMTS/WCDMA/HS*PA radio connection).
That's because you don't understand the fundamental way in which cellular networks work. Don't feel bad - you're not alone; it's a complicated topic.
The radio on your device can only support one type of radio connection at a time. There are a multitude of reasons for this: capacity on the chip, the need for multiple amplifiers to work simultaneously (because typically carriers use different parts of the radio spectrum for one Radio Access Type than another), antenna capacity etc. Keep in mind that are scenarios in which your device is already juggling quasi multiple radio connects, e.g. carrier aggregation.
Don't get me wrong, there have been devices that supported multiple simultaneous radio access technologies on a single device, but that's because they had multiple radios. These were older devices on IS-95 CDMA carriers such a Sprint when they were pushing WIMAX, and even I believe some Verizon devices which allowed them to do multi-RAB for simultaneous voice and calls before their CDMA infrastructure was upgraded to allow this (and prior to their VoLTE launch). These devices are few and far between.
One last point on this topic: the network handles handover between RATs (though it's possible for the device to only support one RAT). If you were allowed to have simultaneous connections to two radio access types, the network would be juggling twice the resources for your device (the transmit and receive portion of a data connection or call is not the only resource involved). This is yet another reason why in most circumstances you'll never see two simultaneous RATs for one device: it costs the network money. Unless you're trying to cover up for a deficiency is your network architecture (e.g. IS-95 CDMA networks lack of support for multi-RAB. Multi-RAB refers to radio access bearers, basically multiple virtual connections across a single radio link. You might think of this like VLANs on an ethernet network.) you don't put the network and engineering expenses to support multiple RATs..
Actually, no. "HD" stands for "HD Voice" which is a better codec. Depending on the carrier, you may get HD voice on a 3G RAT and VoLTE RAT or just on a VoLTE RAT. Keep in mind that HD Voice uses more radio resource than the standard GSM codecs, so there's a trade-off involved here. LTE is more spectral efficient, so offering the higher quality, higher bit rate voice codec on VoLTE has less of an impact on the network than offering it on VoLTE + 3G. So depending on your carrier, they may or may not allow the HD codec on non-VoLTE radio connections. Either way, HD does not in any way shape or form constitute having a VoLTE connection, since it's radio access type independent.
Click to expand...
Click to collapse
My Pixel 2 XL does VoLTE on AT&T. "HD" might have different meanings in different cases but in this case the "HD" does mean VoLTE. Google specifically stated that in release notes for 8.1 on the Pixel 2 XL.
Also, back when I had a Galaxy S2 Skyrocket (AT&T's LTE variant of the Galaxy S2 and its first LTE phone) back in late 2011 it didn't do VoLTE but it did allow LTE data while a voice call was in progress.
So I upgraded from my damaged 6x to a new 7x I purchased on Amazon. I've had the phone for 1 day now and am having strange issues with my 4G LTE not working, essentially timing out. It happens almost a third of the time while using data. The rest of the time I have no issues and am getting fast speeds. My MVNO is Simple Mobile on the $50 Unlimited plan.
I've checked my APN, taken the SIM In/Out even called 611 to which they could not find a problem. Do I need to return the phone or does anyone have some advice. Also have tried different locations to see if it was just a tower to no avail.
So I came into possession of a Verizon Moto Z2 Play into which I put my AT&T sim. I was pleased to find that once it switched to Global Mode I could make and receive calls but even after manually inputting the old wap.cingular APN info that I've done a million times on many other phones I still cannot connect to mobile data (my sim only has a 3g package). Am I hitting a hardware limitation of the device or should I take the time to flash it to one of the firmwares here in the ROM section?
Okay I put my sim back into the device I took it out of and now mobile data is no longer working on it either so it looks like AT&T disabled something on their side. I'll go through and check all the other access point settings in this device (and there's a lot since it has a good rom from this site on it) but I think this is probably going to be the straw that breaks the camels back with AT&T and I'll be taking my number to a prepaid service on Verizon's network.
I talked to AT&T and they told me that their computer automatically disabled my data because the Z2 Play's IMEI was flagged as a 3G device. I told them that's simply not true and thanks for nothing but is the radio in it only capable of LTE on Verizon's network? That doesn't seem likely?
I live in an area with sometimes-spotty reception.
Is it at all possible that when running a non-TMO firmware (such as global or custom ROM) I can have a less reliable network connection even if I'm running a NON-HLOS modem pulled from T-Mobile firmware?
I have a 9Pro purchased from T-Mobile and am on the TMO cellular plan.
And I can swear that running custom ROM or global firmware can sometimes deliver worsened network behavior than when on TMO firmware.
Not sure if it's just in my head or if others have the same issue?
Please tell me about your experience?
CZ Eddie said:
I live in an area with sometimes-spotty reception.
Is it at all possible that when running a non-TMO firmware (such as global or custom ROM) I can have a less reliable network connection even if I'm running a NON-HLOS modem pulled from T-Mobile firmware?
I have a 9Pro purchased from T-Mobile and am on the TMO cellular plan.
And I can swear that running custom ROM or global firmware can sometimes deliver worsened network behavior than when on TMO firmware.
Not sure if it's just in my head or if others have the same issue?
Please tell me about your experience?
Click to expand...
Click to collapse
I think it's just you since I'm running global without issues. I'm not crazy about my network signal being a tad bit lower, as long as it works. I have nearly identical signal compared to stock firmware.
No issues here. T-Mobile user, Indian firmware. WiFi speeds top at 400mbps at home for reference. Running the same modem from when the phone was released (TMobile OG stock modem).
I actually noticed an improvement in reception going from OOS12 to crDroid on my 2127 tmo op9p. The transition was tricky though so DM me if you need guidance.
I thought my issues were related to switching to global/EU firmware from T-Mo, but when my wife and kids started having network problems with their stock T-Mo phones, it turned out to be then network was garbage (in our experience). Garbled calls, dropped calls, slow data, generally useless. Tried in multiple parts of the country (west, east, middle, north) and had issues. Even the unlocked ones we brought over had issues. So they either sold us a several garbage phones, or their network wasn't up to snuff.
Got all phones unlocked, and switched back to AT&T. They all work fine.
The network might just suck where you use it.