Slow upload speed - Google Pixel XL Questions & Answers

Has anyone noticed the ridiculously slow upload speeds of the pixel phones? I'm getting paltry upload numbers on two separate pixels. Any other Android OR iOS device is killing the upload numbers 3 to 1.
Is this a bug or hardware?

You'll have to give us a little more info here buddy.
Are you referring to Wifi? LTE? What Carrier? Are the phones on the same LTE bands?
I can tell you that on Verizon, I get fantastic Upload speeds on-par with my old Note 7. Normally 30-40Mb/s.
I can also tell you that if you are in an area running VZW's LTE Band 2, Upload sucks on that band. I suspect it's running a different slot assignment in the TDMA structure to prioritize download. Whenever I land on it, My upload speed is ~7Mb/s, But the download is blazing (100+Mb/s) depending on if you're in an area running Carrier Aggregation.

This was specifically about wifi. The wifi was tested in several different places on different networks.

sillyphillie said:
This was specifically about wifi. The wifi was tested in several different places on different networks.
Click to expand...
Click to collapse
Are you on the L build or P? P build is supposed to fix some wifi issues. Im having problems with 5ghz connections. I think it might be software?

sillyphillie said:
This was specifically about wifi. The wifi was tested in several different places on different networks.
Click to expand...
Click to collapse
I'm able to get >400Mb/s on upload tests here at our office (Engineer for an ISP). Seems to be inline with my old note 7.
I will agree however, The update they released (Got it ten minutes after I booted the phone up for the first time) supposedly fixed wifi issues.

I'm on an N build?

Yeah I'm not getting updates. Wondering if it's because I put a T-Mobile sim as soon as I received the device.

sillyphillie said:
Yeah I'm not getting updates. Wondering if it's because I put a T-Mobile sim as soon as I received the device.
Click to expand...
Click to collapse
My VZW Pixel XL is on NDE63P (Build number at the bottom of phone status).
Do you have the VZW variant, Or the Direct from google Variant?
If it's the VZW variant, See if you can borrow a SIM from someone to get the update. Even if the sim it came with is unprovisioned, It might get you on the network enough to grab the update via wifi.

Yeah I do. I'm wondering if it will continue to get updates of I don't have a version SIM. That's a whole other problem now I guess. I'm going to do that and at least see if the problem of speed corrects itself. Anyone know what the build of the Google version is?

So.. Funny thing happened. I put the Verizon SIM in and I received the update instantaneously. Interesting. Looks like you do not get updates with another carrier's SIM in the Verizon model. I'm thinking that it's not really unlocked then. Super Shady Verizon with that commercial stating "Only on Verizon" and now this.
Anyway.. I'm off to testing the upload now with the update.

sillyphillie said:
Has anyone noticed the ridiculously slow upload speeds of the pixel phones? I'm getting paltry upload numbers on two separate pixels. Any other Android OR iOS device is killing the upload numbers 3 to 1.
Is this a bug or hardware?
Click to expand...
Click to collapse
I suggest you call your carrier, let them know you have the newest latest Pixel and would like them to reprovision your line, explain to them it's slow.
I would retest speeds in different areas at different times of day, there have been recent ddos attacks messing with thr internet as a whole..

clockcycle said:
I suggest you call your carrier, let them know you have the newest latest Pixel and would like them to reprovision your line, explain to them it's slow.
I would retest speeds in different areas at different times of day, there have been recent ddos attacks messing with thr internet as a whole..
Click to expand...
Click to collapse
The issue is on wifi. The carrier shouldn't matter.

sillyphillie said:
The issue is on wifi. The carrier shouldn't matter.
Click to expand...
Click to collapse
I guess I missed the part about wifi in your post.
Id go to a local VZW store and test it out on their wifi while having their people witness to get a replacement if their displays arent showing the same issue.

Related

LTE on T-Mobile not working AT&T working

So I got my pixel xl from Google today. It works but I am on T-Mobile and it will not connect to LTE band 4 or 12 which are in my area. I have an ATT SIM for my work which I popped in and it works fine. That said without driving around Atlanta to try to find B2 I cannot tell if it is T-Mobile or the phone. Is anyone else on T-Mobile getting LTE connection at all?
So news today I can connect to LTE. Yesterday when I got the SIM in using *#*#4636#*#* I would get zero reception forcing LTE only. The phone would only connect to UMTS/HSPAP. Today after several restarts and calling T-Mobile and Google support it is now working. Here is what I did.
First Google is saying the update is supposed to affect LTE connecting issues.
Second make sure your SIM is properly registered with your provider. They should elevate the issue to higher tech support to have them look into it. This takes up to 24 hours.
Third go to your dialer do the *#*4636#*#*, go to phone info and change the preferred network type to LTE/UMTS or LTE/WCDMA (I haven't seen a difference between them). (This info is in other threads) Then restart your phone.
The problem seems to be how the phone determines what bands the network provider uses. It defaults to CDMA as the voice connection. For me this meant the phone was always connecting to UMTS only. It seems the firmware has some kind of default setting when it senses an error out the gate. The APN settings and preferred network settings needed to be updated and the phone restarted for it all to work. I now connect to band 4 LTE in my area. I hope this helps others.
I am also getting slow data speeds on my pixel XL connected to t mobile
My XL seems to get pretty consistent LTE service and good speed on T-Mobile.
LTE in Chicago working well.
Sent from my Pixel XL using Tapatalk
LTE in minnesota working fine.
Sent from my Pixel XL using Tapatalk
Google "Pixel LTE band 4 issue"
Weird. I'm getting pretty awesome Band 4 coverage in So. Cal. I also get Band 12 here, but Band 4 is what my phone tends to be connected to, which is fine since it tends to be significantly faster.
I'm in Oklahoma on t mobile getting slow connection compared to my friends. They each have a galaxy s6 edge and get between 70-80 MBs down sitting right next to me. I'm getting 14 MBs down. I just left sprint today for slow connection. Hoping to find a way to get this resolved ASAP.
mnguyen127 said:
Weird. I'm getting pretty awesome Band 4 coverage in So. Cal. I also get Band 12 here, but Band 4 is what my phone tends to be connected to, which is fine since it tends to be significantly faster.
Click to expand...
Click to collapse
I only experience the issue in downtown Toronto area and I contacted my carrier, Telus, in Canada. They confirmed that network signal in such area is mainly LTE band 4...
Just an FYI for those with the same issue. Google has asked for my shipping address after contacting them about the issue.
micah_675 said:
Just an FYI for those with the same issue. Google has asked for my shipping address after contacting them about the issue.
Click to expand...
Click to collapse
Which means replacement is on its way?
Not yet I'll update the thread when I get word.
I hope that result you issue, theres a lot of people with problems with LTE band 4 around the world
https://productforums.google.com/forum/#!msg/phone-by-google/OxkJ1Sn6i5c/E_2n5dFTBgAJ
micah_675 said:
Not yet I'll update the thread when I get word.
Click to expand...
Click to collapse
Have you tried swapping SIM cards?
I pulled the sim out of another working TMO iPhone6s and my PIXEL got LTE right away.
Have an update and updated the main post.
micah_675 said:
Have an update and updated the main post.
Click to expand...
Click to collapse
Thanks. I changed mine to LTE/WCDMA. Will know how it goes next week.
All seems to be working on my end.
I was having delays in mms being sent. I was using the default APN. About a week ago I changed the APN to the one recommended by T-Mobile. Mms sends instantly now just about. I don't think it's effected much on LTE but I didn't have problems before. Make sure your on the proper APN
I sure hope there isnt a recall..My XL hasnt even shipped yet and im on Tmo
I spoke with a t-mobile rep yesterday who helped me get my issue resolved. My main apn was set up incorrectly. Now I am connected to LTE and not just hspa+. I get generally good speeds most everywhere and I have tower right by my house that must go fairly unused.

AT&T problem

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.

After October Update - No LTE

Hey guys, just did the October update this morning and now I can't get LTE. Icon just shows 4G. I've tried several restarts and cycling airplane mode and mobile data to no avail. Anyone else experiencing this?
October release? What's the build number? I don't see an October update anywhere.
Are you mistaking the hot fix for the October update? The October update won't be until next week.. it's always the first Monday of every month.
A10Loogie said:
Hey guys, just did the October update this morning and now I can't get LTE. Icon just shows 4G. I've tried several restarts and cycling airplane mode and mobile data to no avail. Anyone else experiencing this?
Click to expand...
Click to collapse
Are you on AT&T?
I am on AT&T. Version # is QP1A.190711.020.C3. It probably was the Hotfix.
A10Loogie said:
I am on AT&T. Version # is QP1A.190711.020.C3. It probably was the Hotfix.
Click to expand...
Click to collapse
There are quite a few people talking about it. I just don't know if there's a fix or not. I'm on T-mobile
Golf c said:
There are quite a few people talking about it. I just don't know if there's a fix or not. I'm on T-mobile
Click to expand...
Click to collapse
There is. My Gf received the OTA yesterday.. I did as well. We are with T-Mobile. However, my bootloader is unlocked and I'm rooted so I ignored it. The security update will be next week, so I figured I'll wait to apply any updates.
4G and LTE are the same thing. Do a speedtest to check if you find the same speeds, but it's very likely just some regional assets not correctly fetched by the OS. The only reason why some builds show LTE in some countries is because of some very bad advertising from some providers (in the US for example some of them did that) where they called "4G" what should have been known as 3G+ (even though it was the same base protocol as 3G).
I'm seeing the same issue. Ran speed test and it's only hitting 10-12 Mbps. I'm also on AT&T. This happened after I updated today.
Flashed over with .020 and still having issues. No luck on the LTE.
I downgraded to .019 and was able to get LTE back. It automatically updated to .020 and I lost LTE again.
I had to downgrade back to .019 to get LTE back again. I turned off automatic updates in developer mode for now until the issue is gone.
xomikronx said:
Okay I figured out the issue. Hopefully this helps everyone here.
There are two updates from September, .019 & .020.
.019 is for all other Pixels.
.020 is for Verizon Pixels.
When the update for .020 was automatically applied to our phones, this is what broke LTE.
I didn't try updating from .3C to .019 to see if this would fix it. Maybe someone can try and report back.
What I did was just clean flash the .019 on my phone. Once Pixel applied the additional small update for Oct. I still have LTE.
Basically, we all on AT&T flashed the wrong firmware.
Good luck!
Click to expand...
Click to collapse
I have a Pixel 3 on AT&T. After the last hot fix I noticed that my LTE notification changed to 4G. I prefer the LTE icon as it is more informative that "4G" which has little meaning anymore. I ran a network signal info app and I am on actual AT&T LTE and my speedtest is 118 Mbps up, 6.7 down with 19ms ping. So am pretty confident that I am actually on LTE just that the icon changed. Based on your post I looked at my build number and it lists QP1A.190711.020.C3. So I guess I have the .020 that you reference.
Are you sure you did not have LTE and it was not just an icon issue? I don't really feel like flashing different firmware so might just live with the 4G thing unless the "wrong firmware" will cause some actual performance issues...
JujuYuki said:
4G and LTE are the same thing. Do a speedtest to check if you find the same speeds, but it's very likely just some regional assets not correctly fetched by the OS. The only reason why some builds show LTE in some countries is because of some very bad advertising from some providers (in the US for example some of them did that) where they called "4G" what should have been known as 3G+ (even though it was the same base protocol as 3G).
Click to expand...
Click to collapse
Same here. I have good speeds, just trying to figure out why the icon changed after the flash. Since the firmware was pushed to my phone does that mean Google is pushing the wrong firmware? I know this is not a regional issue because I flew around the whole US over the last two days with no change. I also reset my network settings with no change.
4G = LTE on AT&T.
If you are ever in doubt, do: *#*#4636#*#* from the dialer and select phone information.
uicnren said:
4G = LTE on AT&T.
If you are ever in doubt, do: *#*#4636#*#* from the dialer and select phone information.
Click to expand...
Click to collapse
I agree but I have always been on AT&T and through every Nexus and Pixel my notification bar always read LTE not 4G. My wife's P3 is on Google Fi with the latest update and it still reads LTE. I will check what hot fix build she got tonight. So why would my phone (and others here) read/indicate 4G now?
As I said, probably just an asset being fetched inconsistently. I know for a fact in other parts of the world it never says LTE but just 4G (because less bad communication around it here), so the system pulling one or the other is just up to how it associates the connected network to a region that says LTE or one that says 4G. My best guess would be that AT&T was misplaced in the last update for some reason that I can't imagine. ¯\_(ツ)_/¯
I lost my LTE this morning.
Had to "disable" the Google eSIM.
Then re-enabled it and LTE came back.
Lost it again after a reboot.
Repeated the above steps and it's been solid since.
orb_526 said:
I have a Pixel 3 on AT&T. After the last hot fix I noticed that my LTE notification changed to 4G. I prefer the LTE icon as it is more informative that "4G" which has little meaning anymore. I ran a network signal info app and I am on actual AT&T LTE and my speedtest is 118 Mbps up, 6.7 down with 19ms ping. So am pretty confident that I am actually on LTE just that the icon changed. Based on your post I looked at my build number and it lists QP1A.190711.020.C3. So I guess I have the .020 that you reference.
Are you sure you did not have LTE and it was not just an icon issue? I don't really feel like flashing different firmware so might just live with the 4G thing unless the "wrong firmware" will cause some actual performance issues...
Click to expand...
Click to collapse
I had full bars with 4G on .020.3C and was only getting 10-15Mbps. It wasn't just an icon change then. It could also be the spot that I was in.
Anyone else having normal LTE speeds, but only have the 4G icon?
orb_526 said:
I agree but I have always been on AT&T and through every Nexus and Pixel my notification bar always read LTE not 4G. My wife's P3 is on Google Fi with the latest update and it still reads LTE. I will check what hot fix build she got tonight. So why would my phone (and others here) read/indicate 4G now?
Click to expand...
Click to collapse
Thats for AT&T and/or Google to answer.
The bottom line is, regardless of what the indicator shows, use the dialer code and you will find out exactly what data network type you are on.
I have a Pixel 3XL and had the same issue. I did a factory reset yesterday and my LTE was good again

AT&T tech support said my OP7T not LTE Compatible

It's HD1907 T-MOBILE. What I need is HD1905. He sent me the wrong one.
I only realized a few hours ago I had no mobile data. I had got calls and texts to work this morning.
After spending 45 minutes on the phone with AT&T they concluded my phone is not recognized as LTE compatible. WTF? It's not even connecting to 3g.lb
I've been buying unlocked phones for years. My last phone was OP5T. I've never experienced anything like this.
I'll probably take it to the corporate store tomorrow but doubt it'll help. Has anyone had problems with AT&T and this phone?
I'm just putting it out there, hoping somebody has an idea...
AT&T worked for me, excellent data speeds, and great signal. But at times it would go from 4 bars to absolutely no signal or data, and lots of dropped calls. After that I went to Verizon, not as good of signal, slower data, but no dropped phone calls or mysterious total loss of signal in an area where it should have been 4 bars.
Droid_Nut said:
AT&T worked for me, excellent data speeds, and great signal. But at times it would go from 4 bars to absolutely no signal or data, and lots of dropped calls. After that I went to Verizon, not as good of signal, slower data, but no dropped phone calls or mysterious total loss of signal in an area where it should have been 4 bars.
Click to expand...
Click to collapse
I'll bet if you look in the settings your model is HD1905 or the global model, not sure the number.
Actually if you could take a look for me and post back here that'd be good. It most likely won't make a difference but I'm curious.
KLit75 said:
I'll bet if you look in the settings your model is HD1905 or the global model, not sure the number.
Actually if you could take a look for me and post back here that'd be good. It most likely won't make a difference but I'm curious.
Click to expand...
Click to collapse
Yes I have the HD1905, but you can totally forget about vowifi with any provider except for T-Mobile. I tried them all, I even had a tech from VZW work diligently to try and get vowifi working. I told him to try and add my IMEI to the approved list, and that did not work either. As far as AT&T, they did not give me the time of day, they just told me I needed and AT&T device, period.
Droid_Nut said:
Yes I have the HD1905, but you can totally forget about vowifi with any provider except for T-Mobile. I tried them all, I even had a tech from VZW work diligently to try and get vowifi working. I told him to try and add my IMEI to the approved list, and that did not work either. As far as AT&T, they did not give me the time of day, they just told me I needed and AT&T device, period.
Click to expand...
Click to collapse
You mean Verizon when you say VZW?
I'm just confused as to how he would be able to add it to the list of approved devices.
Anyway it's BS. If the carrier supports the phone, and the phone is capable of VOLT!/WIFI CALLING, it should work.
KLit75 said:
You mean Verizon when you say VZW?
I'm just confused as to how he would be able to add it to the list of approved devices.
Anyway it's BS. If the carrier supports the phone, and the phone is capable of VOLT!/WIFI CALLING, it should work.
Click to expand...
Click to collapse
Yes Verizon. I have heard hear many times on this site, that phones are blocked from wifi calling by the IMEI, I or they could be wrong.
Vowifi works on the unlocked Pixel, but are they going to butt heads with Google? Volte works fine, I got a network extender, and I can use google voice to make calls over wifi if I really need to.
If vowifi is a must, get an approved phone, that is all you can do.
Droid_Nut said:
AT&T worked for me, excellent data speeds, and great signal. But at times it would go from 4 bars to absolutely no signal or data, and lots of dropped calls. After that I went to Verizon, not as good of signal, slower data, but no dropped phone calls or mysterious total loss of signal in an area where it should have been 4 bars.
Click to expand...
Click to collapse
I worked at AT&T until a few months ago. I can tell you confidently that their tech support is a bunch of dummies. Employees have their own tech support line to call and that one is just as bad. They would routinely tell customers they needed to go to a store to have something done. Then they'd get to the store to find out we literally cannot do that at the store. Stuff like that was super common. One of them even bet me $1,000 that iPhones DON'T reboot when they update, which we all know is all the way wrong.
I halfway think support tells people that stuff on purpose to try to get them to buy something from AT&T. God, I could rant about that place for hours lol
redemptionx11 said:
I worked at AT&T until a few months ago. I can tell you confidently that their tech support is a bunch of dummies. Employees have their own tech support line to call and that one is just as bad. They would routinely tell customers they needed to go to a store to have something done. Then they'd get to the store to find out we literally cannot do that at the store. Stuff like that was super common. One of them even bet me $1,000 that iPhones DON'T reboot when they update, which we all know is all the way wrong.
I halfway think support tells people that stuff on purpose to try to get them to buy something from AT&T. God, I could rant about that place for hours lol
Click to expand...
Click to collapse
Maybe you can answer this for me. Just because a T-MOBILE locked phone is able to make calls and texts on AT&T, does that automatically mean it should be able to connect to mobile data?
I was able to get it to make calls after a refresh signal was sent out, but it could not connect to mobile data . My sim is fine. I even popped it my son's Pixel 3a and LTE started immediately.
The seller is saying the fact that it was able to make calls means it is able to connect to mobile data. And I should take it to AT&T before returning it. I don't think he's scamming. He says he has the same phone on AT&T. And he's sold Hundreds of them. That kinda checks out based on reviews and some of those people do report it works with AT&T.
These phones are hd1907 T-Mobile but supposedly OnePlus unlocks them before sending them out to some sellers. I sort of believe the guy but is it true? If it were locked to T-Mobile could I get it to make phone calls?
Obviously I'm not talking about a hack. Because I thought locked was locked. Is it possible for a locked T-Mobile phone to make calls on the AT&T network?
Also I got AT&T to make it work but once I removed the sim/reinsert it, the thing displays weird behavior. Wifi goes in and out. It forgets the apn settings that were set prior.
redemptionx11 said:
I worked at AT&T until a few months ago. I can tell you confidently that their tech support is a bunch of dummies. Employees have their own tech support line to call and that one is just as bad. They would routinely tell customers they needed to go to a store to have something done. Then they'd get to the store to find out we literally cannot do that at the store. Stuff like that was super common. One of them even bet me $1,000 that iPhones DON'T reboot when they update, which we all know is all the way wrong.
I halfway think support tells people that stuff on purpose to try to get them to buy something from AT&T. God, I could rant about that place for hours lol
Click to expand...
Click to collapse
I agree, ATT was the most horrible experience I ever had. Tracfone may have even had a better customer support.
Verizon CDMA service may be antiquated, but their customer service and tech support is 2nd to none.
KLit75 said:
Maybe you can answer this for me. Just because a T-MOBILE locked phone is able to make calls and texts on AT&T, does that automatically mean it should be able to connect to mobile data?
I was able to get it to make calls after a refresh signal was sent out, but it could not connect to mobile data . My sim is fine. I even popped it my son's Pixel 3a and LTE started immediately.
The seller is saying the fact that it was able to make calls means it is able to connect to mobile data. And I should take it to AT&T before returning it. I don't think he's scamming. He says he has the same phone on AT&T. And he's sold Hundreds of them. That kinda checks out based on reviews and some of those people do report it works with AT&T.
These phones are hd1907 T-Mobile but supposedly OnePlus unlocks them before sending them out to some sellers. I sort of believe the guy but is it true? If it were locked to T-Mobile could I get it to make phone calls?
Obviously I'm not talking about a hack. Because I thought locked was locked. Is it possible for a locked T-Mobile phone to make calls on the AT&T network?
Also I got AT&T to make it work but once I removed the sim/reinsert it, the thing displays weird behavior. Wifi goes in and out. It forgets the apn settings that were set prior.
Click to expand...
Click to collapse
It should have no trouble using data BUT you'll have to change the phone's APN settings to match your carrier before you can. You can google it and find them. It's not hard at all to change. Somewhere under the "network" settings.
Someone correct me if I'm wrong, but as I've understood it the phone will keep trying to access the previous carrier's data network, which is why you didn't have data. But as said above the APN settings should fix that.
redemptionx11 said:
It should have no trouble using data BUT you'll have to change the phone's APN settings to match your carrier before you can. You can google it and find them. It's not hard at all to change. Somewhere under the "network" settings.
Someone correct me if I'm wrong, but as I've understood it the phone will keep trying to access the previous carrier's data network, which is why you didn't have data. But as said above the APN settings should fix that.
Click to expand...
Click to collapse
If I told you the whole story, which started on Friday morning and in the end involved 7 AT&T employees, 6 on the phone and 1 in the store, it'd probably be removed because it's spam. Too long of a story.
But in the end it didn't get to connect to mobile data..at least not consistently. I took it to the store. The guy removed the Sim reset it, turned it off and boom! - LTE, calls and texts. His theory was it takes a little while for it to unlock and get set so when I tried it the other night it wasn't working.
I was happy because it literally took 5 minutes. I ran some errands and was out for like another 2 hours. Everything was working. Some point between the store and my driveway, the signal was gone. I never got it back. Of course I tried reset, remove Sim, reboot, change apn settings.
I called AT&T... the first woman didn't even know what CDMA and GSM was. I politely got her to transfer me to the guy who 'knows his stuff'. He got it to make calls again, but in the end concluded this device can't work on this network. I didn't wanna argue anymore. He had a BS answer for everything including 'If it doesn't work, why DID it work just a half hour ago?'
He said I could try getting a new sim. They have no idea. My son's sim won't work on this phone but pop it in my old phone and it works. And my sim works in his phone. It's not the sim. I know it.
KLit75 said:
It's HD1907 T-MOBILE. What I need is HD1905. He sent me the wrong one.
I only realized a few hours ago I had no mobile data. I had got calls and texts to work this morning.
After spending 45 minutes on the phone with AT&T they concluded my phone is not recognized as LTE compatible. WTF? It's not even connecting to 3g.lb
I've been buying unlocked phones for years. My last phone was OP5T. I've never experienced anything like this.
I'll probably take it to the corporate store tomorrow but doubt it'll help. Has anyone had problems with AT&T and this phone?
I'm just putting it out there, hoping somebody has an idea...
Click to expand...
Click to collapse
That's strange as they both litterly have the same bands besides 71 that 1907 has
This is att bands and oneplus bands
If u haven't tryed I would recommend using the failed to go to your settings and toggle around there all bit make sure it's set for north america
rob420p said:
That's strange as they both litterly have the same bands besides 71 that 1907 has
Click to expand...
Click to collapse
I took it back to AT&T yesterday. There was someone in front of me so I sat down, removed the sim from my working phone, popped it in the op7t... instant lte, calls & texts. The same thing happened the day before I went to at&t. It worked perfectly well there in the store and even 2 towns away but not m my neighborhood which DOES connect to LTE, has for years on every phone we've had.
The tech (if you can really call him that) updated the sim. That got it done. I've had a working phone for 24 hours. BUT no LTE. It only connects to H+.
I haven't had time to call or go back to the store, but I'm hoping it's an easy fix. This has been the weirdest week I've ever had dealing with a phone. I've learned that AT&T doesn't know what they're doing. I still can't believe I needed to explain what GSM and CDMA was to one of the people on the call.
I'm gonna try a few things tonight after work.
KLit75 said:
I took it back to AT&T yesterday. There was someone in front of me so I sat down, removed the sim from my working phone, popped it in the op7t... instant lte, calls & texts. The same thing happened the day before I went to at&t. It worked perfectly well there in the store and even 2 towns away but not m my neighborhood which DOES connect to LTE, has for years on every phone we've had.
The tech (if you can really call him that) updated the sim. That got it done. I've had a working phone for 24 hours. BUT no LTE. It only connects to H+.
I haven't had time to call or go back to the store, but I'm hoping it's an easy fix. This has been the weirdest week I've ever had dealing with a phone. I've learned that AT&T doesn't know what they're doing. I still can't believe I needed to explain what GSM and CDMA was to one of the people on the call.
I'm gonna try a few things tonight after work.
Click to expand...
Click to collapse
That is strange and pethetic the att peaple.dont know what they are doing.if I have time later I'll try to research she if anything comes out
rob420p said:
This is att bands and oneplus bands
Click to expand...
Click to collapse
Thanks for sharing, but I've never really needed to mess around with the settings as far as mobile data goes. It either works out of the box, or at most I'll need to put the apn in manually on some custom roms, but even that's rare.
How does the info you provided apply to my problem. I know the phone can connect to lte. It was connecting briefly on Monday afternoon and while I was at At&T yesterday, it connected before they updated the sim.
Is there something I can do with this? It's a sincere question. I'm not sure if I can apply it somehow. Thanks
KLit75 said:
Thanks for sharing, but I've never really needed to mess around with the settings as far as mobile data goes. It either works out of the box, or at most I'll need to put the apn in manually on some custom roms, but even that's rare.
How does the info you provided apply to my problem. I know the phone can connect to lte. It was connecting briefly on Monday afternoon and while I was at At&T yesterday, it connected before they updated the sim.
Is there something I can do with this? It's a sincere question. I'm not sure if I can apply it somehow. Thanks
Click to expand...
Click to collapse
I think his point was to show that the OP7T does in fact work on all AT&T bands. Normally you don't need to do anything with this if the SIM is provisioned correctly.
What are the chances that you are on the edge of the local AT&T LTE signal so it drops to H+ because that's a stronger connection? At the AT&T store the LTE signal is stronger so the phone is favoring that one. Some phones are more sensitive to signals than others (or more aggressive at switching to a stronger band).
Try using a program like "LTE Discovery" and see what bands you actually are connecting to. It can also let you know what is going on in your area with tower location.
Lost Dog said:
I think his point was to show that the OP7T does in fact work on all AT&T bands. Normally you don't need to do anything with this if the SIM is provisioned correctly.
What are the chances that you are on the edge of the local AT&T LTE signal so it drops to H+ because that's a stronger connection? At the AT&T store the LTE signal is stronger so the phone is favoring that one. Some phones are more sensitive to signals than others (or more aggressive at switching to a stronger band).
Try using a program like "LTE Discovery" and see what bands you actually are connecting to. It can also let you know what is going on in your area with tower location.
Click to expand...
Click to collapse
I'll try that. Thanks.
That's what I said but the guy at the store said it's really not a stronger signal at the store. Plus I know I can get LTE at my house and in the store because all our other phones connect, even this one, briefly at the at&t store.
The seller have me a code to input into the dialer but I'm waiting for tomorrow to put it in. It's my day off. If something goes wrong it won't be a huge deal. I will look into what you sent at some point though.
Droid_Nut said:
Yes I have the HD1905, but you can totally forget about vowifi with any provider except for T-Mobile. I tried them all, I even had a tech from VZW work diligently to try and get vowifi working. I told him to try and add my IMEI to the approved list, and that did not work either. As far as AT&T, they did not give me the time of day, they just told me I needed and AT&T device, period.
Click to expand...
Click to collapse
Your posts are bouncing between VoLTE & VoWiFi.
LTE bands and VoLTE work fine on Verizon's network.
Verizon allows VoWiFi on the OP 8's that they sell. They will not activate VoWiFi on the OP 7 series, the claim is that the phone did not go through their security testing. IIRC VZW doesn't allow VoWiFi on any outside phone.

Cricket canceling 7T on their network?!! As of Feb 2022

I made a call and got a message that my phone would no longer work on their network since they are upgrading things. This phone isn't that old. I wonder if their system doesn't recognize it. The lady said their system was showing it was a 2g phone so I told her it handles 4g. She said on Cricket it's only able to use 3g. Does anyone know if this is true. I don't trust some operator in another country reading off a script. It sounded like they want everyone to buy phones from their website. I can't imagine a relatively new phone not having the right band. Maybe there is a setting I need to tweak or flash onto my phone if I'm only using 3g on Cricket. I'm sure I've seen my antenna say LTE. Or maybe Cricket is screening out non Cricket phones.
Check it's specs.
If it supports the needed 4G bands it may need to be reconfigured. I haven't a clue how to do that.
Maybe Access point names but it may go deeper than that.
I'm going to google and see exactly what specs Cricket will require. I think you're right and maybe something to reconfigure. I can't imagine Cricket shutting off tons of new ish phones just because they aren't bought from Cricket. Ran a speed test now and got 2.77mbps download and 8.49mbps upload. I am showing LTE now which means I'm not on 3g as she was saying now. I bet it's a sales gimmick to scare less savy folks. What mean loose phone signal in Feb hehehe.
Edit: I was on wifi when I got the message so maybe when I phone is on wifi and not using their LTE network it doesn't detect anything which is why they told me I have a 2g phone. When I shut off wifi LTE popped right up so it's probably a glitch in their way of informing us.
Edit2: Spoke to a tech at Cricket and he said my phone currently isn't compatible with them aaahahahhaha dumb. I told him I'm currently using it on LTE just fine no issues. He didn't have anything to say when I asked him since I'm not using 3g then it shouldn't affect me. He just said he wants me to have great service so buy another phone from Cricket. BS
Only HD1905 works
bhaliyo said:
Only HD1905 works
Click to expand...
Click to collapse
I have HD1907 and it's currently working on LTE. Are you referring to not working in the future or currently working?
jeffrimerman said:
I have HD1907 and it's currently working on LTE. Are you referring to not working in the future or currently working?
Click to expand...
Click to collapse
Not working in the future. Here is the list of devices can work after Feb 2022.
bhaliyo said:
Not working in the future. Here is the list of devices can work after Feb 2022.
Click to expand...
Click to collapse
That link keeps rerouting to an ATT samsung S21 advertisment. I'll try to google the list
jeffrimerman said:
That link keeps rerouting to an ATT samsung S21 advertisment. I'll try to google the list
Click to expand...
Click to collapse
See the attachment above
Yes I
bhaliyo said:
See the attachment above
Click to expand...
Click to collapse
Yes I was able to download that list when I googled. Judging by what it said these are phones that are tested and will work, not so much that other phones won't work. My phone was originally branded for Tmobile so I'm sure they wouldn't have tested it but it would have only had a different OS with Tmobile bloatware which I took off. The cricket people said their LTE isn't changing so I shouldn't have an issue but it will be interesting to find out. They must have just been looking at this list which is why they said my phone currently isn't compatible.
Funny this was asked but no answer given from ATT. I'll keep googling
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
I read a discussion here from 2019 someone else asked and the different variants are by region as they usually are for the different LTE frequencies. 1905 is North American, 1907 is Tmobile in North America so I would imagine my LTE frequency is still going to be fine. Those that bought Chinese phones etc probably not.
This is weird. The current ad for it on Amazon says it's currently not compatible with ATT and Cricket. I wonder if me flashing another OS for North America or USA I forget is why it works fine? Maybe I'm screwed hehe
*** NOTE: Due to changes with AT&T and Cricket, this phone currently cannot be used on AT&T/Cricket. Compatible with T-Mobile and all GSM Networks along with their compatible MVNO networks such as Red Pocket GSM, Ultra Mobile, Mint Mobile, Ting GSM, Google FI and many others. This phone is NOT compatible with Verizon, Cricket or AT&T. Please verify with your network to ensure complete compatibility.
Spoke to a tech at Cricket and he said my phone currently isn't compatible with them
Click to expand...
Click to collapse
I work at a prepaid carrier store (not Cricket) and am having to tell customers the same thing. It's not just about if your phone has the radios necessary, they have to have the IMEI approved in their system and if it's not then you can possibly escalate to someone who can help get it approved but you probably won't get very far. I can't activate my own OnePlus device with my company either, even though it's currently running on our parent network. I have spoken with internal support folks about it multiple times and have gotten nowhere so I gave up.
jeffrimerman said:
I can't imagine Cricket shutting off tons of new ish phones just because they aren't bought from Cricket.
Click to expand...
Click to collapse
Believe it. It sucks and it sounds insane but it's really happening. For me? I have to tell everyone with a Samsung Galaxy S5-S10 that they have to buy a new phone to be compatible with our new network changes. And I can tell you here that it's (probably) not the sales rep lying to you to make a commission sale, our tools are indeed forcing us to do that.
jtaylor991 said:
I work at a prepaid carrier store (not Cricket) and am having to tell customers the same thing. It's not just about if your phone has the radios necessary, they have to have the IMEI approved in their system and if it's not then you can possibly escalate to someone who can help get it approved but you probably won't get very far. I can't activate my own OnePlus device with my company either, even though it's currently running on our parent network. I have spoken with internal support folks about it multiple times and have gotten nowhere so I gave up.
Believe it. It sucks and it sounds insane but it's really happening. For me? I have to tell everyone with a Samsung Galaxy S5-S10 that they have to buy a new phone to be compatible with our new network changes. And I can tell you here that it's (probably) not the sales rep lying to you to make a commission sale, our tools are indeed forcing us to do that.
Click to expand...
Click to collapse
I'm just wondering why they are saying my phone currently isn't compatible when it obviously is. It works great. Even streams HD in an instant on Crickets network. Corporations aren't super efficient at checking all things under the sun. They are just checking phones they approve. They told me the same thing that my imei currently doesn't work but it does. Unless they are trying to be like Verizon and only allow specific phones in the future I'm still thinking once they shut off 3g then when someone wants to switch from Tmobile to Cricket with their unlocked working fine non 3g phone they still can or are they saying no they are going to be like Verizon and it has to be a Cricket branded phone. I don't think it's the later. I think they are just saying what will work, but not saying what won't work. Let's find out =( hehe
Read a discussion from 8 months ago. Seems like most are fine, one guy with a 1905 had issues on ATT. One guy did what I did so maybe that's why mine is fine for now. I haven't had issues like dropped calls etc but maybe the real issue I will have if Cricket adds wifi calling and VoLTE is if they use a specific frequency and the 1907 is missing it then I won't be able to use those. If Cricket only uses VoLTE then yes I am screwed in February =/
https://www.reddit.com/r/oneplus/comments/kf0hfo
"I am currently using a 7t that was advertised as factory unlocked on ebay, when it showed up and I turned it on the big bright pink Tmobile boot logo came by. I did some research and found the convert to international/global thread on xda, I got rid of the crap hydrogen OS that came with the "unlocked" Tmobile phone. Using ADB I was able to flash the international firmware Oxygen OS and haven't had any problems with at&t now."
If it's an IMEI issue, flashing with the hd1905 fw probably won't help matters. I have a hd1905 on cricket since 2019, everything but wifi calling works. The same cricket sim in a samdung s9+ yields working wifi calling.
So while the hd1905 and 1907 are essentially the same hardware devices, the serial #/imei may determine what happens come 2022.
gpz1100 said:
If it's an IMEI issue, flashing with the hd1905 fw probably won't help matters. I have a hd1905 on cricket since 2019, everything but wifi calling works. The same cricket sim in a samdung s9+ yields working wifi calling.
So while the hd1905 and 1907 are essentially the same hardware devices, the serial #/imei may determine what happens come 2022.
Click to expand...
Click to collapse
Yup, I'm wondering if the hardware or the IMEI will determine things. I didn't even know Cricket had wifi calling. Did Cricket even let you download the wifi calling app but it didn't work or did they not allow you to download it?
Edit: I looked it up. Looks like wifi calling will work on phones that have it built in to their OS settings. I probably won't use it if I end up buying another OnePlus phone. I wonder if there are any phones where wifi calling is working on Cricket that isn't on the list but is in the OS settings.
Wifi calling app? The s9+ was hybrid flashed. Everything but the main OS came from the U firmware (carrier), while the rom came from U1 fw. Result was working carrier features (volte/wifi calling) without the bloat.
gpz1100 said:
Wifi calling app? The s9+ was hybrid flashed. Everything but the main OS came from the U firmware (carrier), while the rom came from U1 fw. Result was working carrier features (volte/wifi calling) without the bloat.
Click to expand...
Click to collapse
The s9+ is probably the same as the s9 as far as the wifi calling since "+" isn't mentioned on their list.
Huh? It's right under the s9.

Categories

Resources