Which band is missing on the N920T from the N920A? - T-Mobile Samsung Galaxy Note5

I'm having a hard time finding a definitive answer about which LTE band I'll lose using the tmobile variant on att.

I don't think any, I think both are identical. I am using the N920T with AT&t. I would suggest you consider using DarthStalkers ROM, he was able to pull the AT&T carrier files.
The N920T & A are the same. If you had bought the N920I you might lose bands.

Does anyone know where I can get a band 12 coverage map? I can only find the LTE coverage map which doesn't specify if band 12 is used there

wdkingery said:
I'm having a hard time finding a definitive answer about which LTE band I'll lose using the tmobile variant on att.
Click to expand...
Click to collapse
17 and 30 (I don't think the 920t's band 12 will work with AT&T's B17 - even though 12 is a subset of 17 (or do I have that backwards?) Possibly 29 (downlink only for AT&T) - but there's very little documentation on B29, so I'm not sure if the N920A supports it or not.

garyd9 said:
17 and 30 (I don't think the 920t's band 12 will work with AT&T's B17 - even though 12 is a subset of 17 (or do I have that backwards?) Possibly 29 (downlink only for AT&T) - but there's very little documentation on B29, so I'm not sure if the N920A supports it or not.
Click to expand...
Click to collapse
Could you be so kind as to translate what that will mean to me? I have a t-mobile note 4 here on att and it seems to do fine.. Do you think I'll be so lucky with the note 5?

wdkingery said:
Could you be so kind as to translate what that will mean to me? I have a t-mobile note 4 here on att and it seems to do fine.. Do you think I'll be so lucky with the note 5?
Click to expand...
Click to collapse
Band 29 is rarely used by AT&T (only as a downlink in heavily congested areas.) This shouldn't be a problem.
Band 30 (WCS band) is something AT&T _just_ started deploying, but I've never seen it in actual use. In fact, until very recently, none of AT&T's own phones supported it. B30 is really of limited value for general use due to it's propagation (or lack thereof.) Like 29, its probably only used as a supplement to other bands. I wouldn't worry about B30.
B17, however, is a Big Deal for AT&T. That's AT&T's primary "lower frequency" LTE band. Because of the low frequency, it has excellent propagation (meaning it moves farther and through trees, buildings, etc.) They use this band to cover large geographical areas with minimal towers. If you will be using your phone in a non-urban area, B17 is almost essential for AT&T. (My phone spends the majority of the time at my home on B17.)
I haven't heard of anyone with a TMO Note 5 device (without explicit B17 support) attaching to AT&T's B17, but that doesn't mean it won't work. However, Unless someone confirms B17 functionality on the n290T from actual use (and not just what they think), I'd suggest assuming that it won't work.

garyd9 said:
Band 29 is rarely used by AT&T (only as a downlink in heavily congested areas.) This shouldn't be a problem.
Band 30 (WCS band) is something AT&T _just_ started deploying, but I've never seen it in actual use. In fact, until very recently, none of AT&T's own phones supported it. B30 is really of limited value for general use due to it's propagation (or lack thereof.) Like 29, its probably only used as a supplement to other bands. I wouldn't worry about B30.
B17, however, is a Big Deal for AT&T. That's AT&T's primary "lower frequency" LTE band. Because of the low frequency, it has excellent propagation (meaning it moves farther and through trees, buildings, etc.) They use this band to cover large geographical areas with minimal towers. If you will be using your phone in a non-urban area, B17 is almost essential for AT&T. (My phone spends the majority of the time at my home on B17.)
I haven't heard of anyone with a TMO Note 5 device (without explicit B17 support) attaching to AT&T's B17, but that doesn't mean it won't work. However, Unless someone confirms B17 functionality on the n290T from actual use (and not just what they think), I'd suggest assuming that it won't work.
Click to expand...
Click to collapse
An informative post if ever there was one indeed.
What app do you use to determine which hand your phone is connected thru? I have found this app "LTE discovery", and it seems my att note 3 stays connected to 5 mostly, or 4 for lte. But then for GSM is doesn't list a band, but appears connected. On her t-mobile note 4 connected to att, she stays on 5, but the GSM doesn't appear to be connected to anything..
We will be almost exclusively in the middle of a city, but as with anything that could change or in the event of a road trip..
Is there a place I can sit and study this information? Perhaps a website with all of this data? Or do you happen to work in the field?
In a sea of noobs, an informed person is a real diamond in the rough - I appreciate your time.

wdkingery said:
What app do you use to determine which hand your phone is connected thru? I have found this app "LTE discovery", and it seems my att note 3 stays connected to 5 mostly, or 4 for lte.
Click to expand...
Click to collapse
That's a good app to use. I also use my phone's diagnostic menu's, but I doubt AT&T left those enabled on the 'a' variant.[/QUOTE]
wdkingery said:
But then for GSM is doesn't list a band, but appears connected. On her t-mobile note 4 connected to att, she stays on 5, but the GSM doesn't appear to be connected to anything..
Click to expand...
Click to collapse
Is that with "lte discovery" that she doesn't appear to have any GSM side connection? She most likely does, as that's where voice calls will take place...
wdkingery said:
Is there a place I can sit and study this information? Perhaps a website with all of this data?
Click to expand...
Click to collapse
Google. Then google some more. If you run out of pages from google, use another search engine. All the information is readily available - it just takes time to find it all.

garyd9 said:
That's a good app to use. I also use my phone's diagnostic menu's, but I doubt AT&T left those enabled on the 'a' variant.
Click to expand...
Click to collapse
Is that with "lte discovery" that she doesn't appear to have any GSM side connection? She most likely does, as that's where voice calls will take place...
Google. Then google some more. If you run out of pages from google, use another search engine. All the information is readily available - it just takes time to find it all.[/QUOTE]
so i got through all the hoops.. don't have LTE ;-(
it connects to band 4 or 5 when i first come out of airplane mode, but it jumps right back off. stuck on 4g. called at&t for an hour, they said initially it wasn't provisioned on my sim card, but then afterwards they determined it was a problem on my end, walked my thru APN settings and then ended the call.. still no LTE.
do you have an opinion of what i could do?

wdkingery said:
do you have an opinion of what i could do?
Click to expand...
Click to collapse
Quoting me in a thread was enough... didn't have to also PM me...
@TEKHD has a firmware that might work for you. Check it out over here: http://forum.xda-developers.com/tmo...h6-tekxodus-n5-urv1-00-00-lollipop-5-t3201869
He has apparently provided a mechanism that is working for other AT&T users... (probably via loading the AT&T RIL libs.)
I haven't tried this (and I don't even have a 't' variant myself.) On the other hand, a quick search of that thread seems to show that other people are having successes with AT&T sim's on 't' variant devices.
Good luck!
Gary

sorry about the double.
after a precursory examination, idon't see exactly what you are talking about in his thread..
is it a download?

garyd9 said:
Quoting me in a thread was enough... didn't have to also PM me...
He has apparently provided a mechanism that is working for other AT&T users... (probably via loading the AT&T RIL libs.)
Good luck!
Gary
Click to expand...
Click to collapse
the search feature doesn't appear to work for me; shows 0 results on att or at&t.. i'm having to sift thru all 114 pages by hand.

garyd9 said:
He has apparently provided a mechanism that is working for other AT&T users... (probably via loading the AT&T RIL libs.)
Gary
Click to expand...
Click to collapse
i searched all 114 pages and didn't find reference to any of that.. now i know why search provided no results; there weren't any!
so i need to find the att ril libraries. how will i ever find that.

wdkingery said:
i searched all 114 pages and didn't find reference to any of that.. now i know why search provided no results; there weren't any!
so i need to find the att ril libraries. how will i ever find that.
Click to expand...
Click to collapse
Maybe that was the wrong firmware... it's something in the TMO dev section. Please search.

garyd9 said:
Maybe that was the wrong firmware... it's something in the TMO dev section. Please search.
Click to expand...
Click to collapse
i've searched the entire tmo dev section for term "at&t" and there are sparse hits; there is some conversation about CSC for a guy in canada getting his VoLTE working, but nothing on att.

wdkingery said:
i've searched the entire tmo dev section for term "at&t" and there are sparse hits; there is some conversation about CSC for a guy in canada getting his VoLTE working, but nothing on att.
Click to expand...
Click to collapse
Apparently, you already found it: http://forum.xda-developers.com/tmo...on-1-aroma-t3212091/post63516726#post63516726
This has AT&T RIL's in the update.zip, and from a quick look at the first post in that thread, they are installed based on an aroma installer. Others in that thread claim it works for them. You're using a TMO device on ATT, so you have to expect some level of incompatibility. There are AT&T LTE bands that the TMO device simply doesn't support. It doesn't matter what happens with your Note 4. Different device and different modem.
So, if you want to use a TMO device on ATT, you'll have to make some sacrifices. Most people will find the sacrifices are less drastic using an international version of the phone. For some reason, US carriers go out of their way to ensure their devices are incompatible with each other.

garyd9 said:
Apparently, you already found it: http://forum.xda-developers.com/tmo...on-1-aroma-t3212091/post63516726#post63516726
This has AT&T RIL's in the update.zip, and from a quick look at the first post in that thread, they are installed based on an aroma installer. Others in that thread claim it works for them. .
Click to expand...
Click to collapse
ok this is where i started, by flashing the ATT option for this rom. but that doesn't solve the problem. i'm in the process of clean flashing the tmobile choice like he suggested.
thanks for all your help.
i'm afraid this isn't going to work either. i realize the wife's note 4 may have different hardware, and isn't a good reference.
i can see the thing connect to band 5, then band 4, lte .. but it's in "emergency calls only" mode, then it gives up on that, connects to HSUPA or HSPA+ and that's the last of an LTE connection.
i feel like it would connect if it could, and that i'm having a software issue.

problem solved guys sorry for the large headache..
Solution:
AT&T did not recognize my IMEI as being LTE capable. Because of that, they decline to allow my phone to connect to LTE. My phone would connect to an LTE tower (as in the screen shots a few pages back), but wouldn't receive anything back from AT&T, so it would say "emergency calls only" and then give up after about 10 seconds, and then never go back. Crap data all around at this time.
What you'll need to do is walk into an AT&T store, take a picture of the IMEI off an LTE phone, and then call in and change your IMEI to the phone you found. This will cause the system to recognize your phone as LTE capable, and like magic, you'll have LTE.

I can confirm that I have a tmobile branded unit that attaches to band 17. It isn't as frequently as on my note 4, I'm generally on band 2. With that said I've had virtually no trouble with service. I was initially worried about the b17 issue, but it hasn't seemed to make any difference.

intifadamericana said:
I can confirm that I have a tmobile branded unit that attaches to band 17. It isn't as frequently as on my note 4, I'm generally on band 2. With that said I've had virtually no trouble with service. I was initially worried about the b17 issue, but it hasn't seemed to make any difference.
Click to expand...
Click to collapse
Does it attach to band 17 on AT&T or t-mobile?

Related

T-mobile 4g Radio

OKAY so I decided to update this thread:
There are two versions of the One X. One with aws bands and one without. I have a device without AWS (I am about 80 % sure). There are reports of people getting 4g on AWS with the Rogers Version as of now, and more testers need to check it out as it could still be possible on ATT.
This flash here theoretically could enable the One X radio to lach onto AWS (The radios here are for the One S Ville.)
http://ville.giev.de/?page_id=42
I have flashed all three, and although I did not get 4g, I got faster ping and a near immediate connection onto T-mobile. To all the people saying this will "brick" the phone, it does not and you have nothing to worry. But as always make sure to do a backup. The radio hacks for the Skyrocket/Note were also based on flashing the Galaxy S2 radio directly on top. This should work the same.
I'm interested in this as well. What does is involved and the risk? I don't have warranty on my phone, so I'm a little bit leery in being first.
ver2go said:
I'm interested in this as well. What does is involved and the risk? I don't have warranty on my phone, so I'm a little bit leery in being first.
Click to expand...
Click to collapse
if your rooted ull should be fine just make a back up of ur current set up. this is just a clockwork flash, it may not even flash, but if it does then there's a high chance of 4g.
i've done radio hacks before for the droid 3/skyrocket/note all from a similar concept. ex. flashing the t-mobile galaxy s2 radio on the note, to enable 4g.
if anyone could provide me with a better solution for an unlock i am sure i can get this to work. seems that the htc unlocker server is down right now
it's the same thing as flashing different radios via clockwork posted in the One X android dev forum
I'll give it a try, hopefully it won't mess anything up. So I just flash the radio in recovery. If no good, I just flash the correct radio again?
There is a one click no HTC Dev bootloader unlock in the Dev forum.
http://forum.xda-developers.com/showthread.php?t=1734558
---------- Post added at 07:57 PM ---------- Previous post was at 07:25 PM ----------
I flashed:
Radio from RUU_Ville_U_HTC_Europe_1.78.401.2 [Recommended] (update by rhcp)
0.16.31501S.17_2_10.23.31501S.10L
From your link. It flashed correctly. The phone on data and voice still works. I confirmed the version in Settings is not my original:
0.17.32.09.12_10.86.32.08L
I'm still on Edge, but I'm in a crappy cell area, so still not certain if radio or my area. I might give the:
Radio from Stock T-Mobile US (update by rhcp)
0.16.31501S.02_10.18.31501S.08L
Radio a try too.
good to hear no negative results got my phone unlocked so i will be testing tonight. also do u guys have the newer sims or older ones?
I have an older sim I believe. It is one that came from an activation kit I bought off ebay. I tried the T-Mobile radio and same results, still on Edge, but still could be my location.
What in gods name are you guys doing! ? Are you trying to brick your phones? It's already been confirmed that the hardware on this phone does not support the proper bands for T-Mobile 3g!
seh6183 said:
What in gods name are you guys doing! ? Are you trying to brick your phones? It's already been confirmed that the hardware on this phone does not support the proper bands for T-Mobile 3g!
Click to expand...
Click to collapse
Prove it. Why would the phone soc be any different than the one s one.
Sent from my HTC One X using xda premium
ECEXCURSION said:
Prove it. Why would the phone soc be any different than the one s one.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
It's not just the SOC that determines hardware compatibility. There are various radio amplifiers and filters which are tuned to the specific frequencies that the phone is likely to encounter. If a phone is going to be sold in multiple markets, sometimes the hardware filters are set up for all frequencies and some are disabled via software, but often times this is not the case.
It's not impossible that a radio reflash can make it work, though highly improbable.
sassafras
Interested in this. There might be better luck flashing the tmo radio since I don't think any European operators use AWS bands, correct me if I'm wrong.
Can anyone explain why flashing this radio from a different device won't brick our phones?
tspx23 said:
good to hear no negative results got my phone unlocked so i will be testing tonight. also do u guys have the newer sims or older ones?
Click to expand...
Click to collapse
I have a tmobile one s, but i also have the one from att and i am so interested on using this phone over tmobile 4g let me know if i can of help. I am using my micro sim that came with the one s and i am getting edge (asume its the latest from tmobbile 4g mucro sim. I am on 1.85 rooted but i did not unlock. though i am sure we can flash through CWM. any ways i am sure there is a way out to get 3g or 4g on the one x on tmobile did not find the way yet.
flashed both of the t-mobile modems no luck for me either, although my ping is significantly higher and connects to t-mobile a LOT quicker.
does anyone know how to edit the LTE settings. it is odd but for most ATT LTE phones they have the 1700mhz frequency i think it would be a matter of just defaulting that....
the radios also show up in my baseband so i have successful flashes
EDIT: one more thing, before i was not able to use data at all considering i had the newer t-mobile sims but now data works but on edge speed.
danada said:
Interested in this. There might be better luck flashing the tmo radio since I don't think any European operators use AWS bands, correct me if I'm wrong.
Can anyone explain why flashing this radio from a different device won't brick our phones?
Click to expand...
Click to collapse
it's just a file in your system. it could potentially brick your phone but you can always get into recovery and restore. which is why i stated you should create a back up of your device before trying it out.
however, i was fairly certain it wouldn't do that because the internals of the One S/One X are nearly identical, they both share the same processor and most likely similar (if not same, radios).
either way, the the radios work, getting me higher ping, and working data without having to switch out my sim for an older one, hope there is a way to activate the 1700 band !
http://www.gsmarena.com/htc_one_x_at&t-4614.php
EDIT 2: apparently there are two models of the ATT One X/XL one with the 1700 band and one without
tspx23 said:
flashed both of the t-mobile modems no luck for me either, although my ping is significantly higher and connects to t-mobile a LOT quicker.
does anyone know how to edit the LTE settings. it is odd but for most ATT LTE phones they have the 1700mhz frequency i think it would be a matter of just defaulting that....
the radios also show up in my baseband so i have successful flashes
EDIT: one more thing, before i was not able to use data at all considering i had the newer t-mobile sims but now data works but on edge speed.
Click to expand...
Click to collapse
Likely the software has been changed to support T-Mobile, but the hardware (filters, amplifiers, etc) are non-existent, so you'll never get actual 1700 MHz AWS support.
Of course, this is just a 50,000 foot view perspective without actually trying it myself.
sassafras
sassafras_ said:
Likely the software has been changed to support T-Mobile, but the hardware (filters, amplifiers, etc) are non-existent, so you'll never get actual 1700 MHz AWS support.
Of course, this is just a 50,000 foot view perspective without actually trying it myself.
sassafras
Click to expand...
Click to collapse
you might be right about this one but there are certain One X/XL's that do have the 1700 band found out through some searching and trying to figure out the reason behind it.
If that's correct.... the people with the 1700 band would have 4g when they flash this radio! also use *#*#4636#*#* to change network type to lte/gsm
--- for other phones though like the Skyrocket/Note they were directly compatible with T-mobile radios.
Okay, I flashed the Tmo One S radio and did not receive a brick. What I did receive is a not-so-good connection that will switch between HSPA+ and 3G quite often.
I don't have a WIND sim to test with, but I tried running AT commands on my phone and they don't seem to be working. I tried doing a network scan with AT+COPS=? waited forever and had nothing displayed.
Strange...
--edit--
Rebooted and ran the commands again. Still don't see any AWS carriers.
uid=0 [email protected]:/ # +COPS: (1,"CAN Rogers Wireless Inc.","ROGERS","302720",7
),(2,"ROGERS","","302720",2),(1,"CAN Rogers Wireless Inc.","ROGERS","302720",0),
(1,"","","302220",2),(1,"","","302610",2),(1,"","","302610",7),(1,"","","302220"
,7),,(0,1,2,3,4),(0,1,2)
Click to expand...
Click to collapse
danada said:
Okay, I flashed the Tmo One S radio and did not receive a brick. What I did receive is a not-so-good connection that will switch between HSPA+ and 3G quite often.
I don't have a WIND sim to test with, but I tried running AT commands on my phone and they don't seem to be working. I tried doing a network scan with AT+COPS=? waited forever and had nothing displayed.
Strange...
--edit--
Rebooted and ran the commands again. Still don't see any AWS carriers.
Click to expand...
Click to collapse
Don't you need a wind sim to connect im pretty sure the Canadian version will work on aws
Confirmed on my end that even with the T-Mobile radio, I'm not getting HSPA+. Even when I drove by the Moscone center where 1900Mhz was refarmed during Apple's WWDC (maybe it was just that day?). I was hoping this would be like the Note and Rocket where I can flash different radios.
Any other new phone capable of this? The S III? If not, I may have to either wait for 1900MHz refarm or switch to Straight Talk.
ver2go said:
Confirmed on my end that even with the T-Mobile radio, I'm not getting HSPA+. Even when I drove by the Moscone center where 1900Mhz was refarmed during Apple's WWDC (maybe it was just that day?). I was hoping this would be like the Note and Rocket where I can flash different radios.
Any other new phone capable of this? The S III? If not, I may have to either wait for 1900MHz refarm or switch to Straight Talk.
Click to expand...
Click to collapse
Picking up an att s3 today to test it out. Most likely there's two versions of one x one with aws and one without. I know mine doesn't though.
tspx23 said:
Don't you need a wind sim to connect im pretty sure the Canadian version will work on aws
Click to expand...
Click to collapse
I'm not exactly sure of this one.
If someone is willing to let me cut up their WIND sim (or lend me their WIND microsim), I'll re-flash the tmo radio and meet you somewhere to test it (Toronto, please).
~dan
-----edit-----
Just popped in an old WIND sim that I used to test AWS connectivity at first. Saw WIND Away with the standard radio, and after flashing the Tmo radio I see WIND Away and AT&T (AT+COPS=? shows Rogers, ATT, Telus, Bell).
I live by the lake, that would explain why ATT shows up.
-----edit again-----
Check this out http://imgur.com/Nb984,rUvM6. Not using the One S radio...

[Completed] Noob in need of radio/modem flashing information

Hello,
I recently purchased a note 5 duos SM-N9208 from Taiwan. I was led to believe that the device was unlocked GSM, but had EV-DO capabilities. My understanding was that this would work on Verizon's network, because it had both radio chips inside. I was told by Verizon that "there is no approved way" for them to get me up and running on their network. The tech made a point of saying there is a difference between approved, and no way. This leads me to believe that something can be done. I'm wondering if someone would be kind enough to help me out. Phone is running original Rom, unrooted, and is basically useless to me right now, as I'm desperately clinging on to my unlimited data with Verizon. Is it possible to root the device, and flash the modem with Verizon note 5 baseband info? Any help anyone can offer would be very much appreciated.
XDA Visitor said:
Hello,
I recently purchased a note 5 duos SM-N9208 from Taiwan. I was led to believe that the device was unlocked GSM, but had EV-DO capabilities. My understanding was that this would work on Verizon's network, because it had both radio chips inside. I was told by Verizon that "there is no approved way" for them to get me up and running on their network. The tech made a point of saying there is a difference between approved, and no way. This leads me to believe that something can be done. I'm wondering if someone would be kind enough to help me out. Phone is running original Rom, unrooted, and is basically useless to me right now, as I'm desperately clinging on to my unlimited data with Verizon. Is it possible to root the device, and flash the modem with Verizon note 5 baseband info? Any help anyone can offer would be very much appreciated.
Click to expand...
Click to collapse
Hi, and welcome to XDA!
When I looked up the specs on the Note 5 Duos, unfortunately it says nothing about CDMA. Having both "radio chips inside" can be taken two ways, in this case, this phone has the capability to handle two GSM carriers (and in this case, like most dual-sim phones, only the first SIM can do 3G/4G/LTE speeds).
Network Technology GSM / HSPA / LTE
2G bands GSM 850 / 900 / 1800 / 1900 - SIM 1 & SIM 2
3G bands HSDPA 850 / 1900 / 2100
4G bands LTE
Speed HSPA 42.2/5.76 Mbps, LTE
GPRS Yes
EDGE Yes
Click to expand...
Click to collapse
It seems the only option (if you want to use this phone), is to join a GSM carrier like AT&T, T-Mobile, or one of their MVNO's (like MetroPCS).
Hope this helps.
joel.maxuel said:
Hi, and welcome to XDA!
It seems the only option (if you want to use this phone), is to join a GSM carrier like AT&T, T-Mobile, or one of their MVNO's (like MetroPCS).
Hope this helps.
Click to expand...
Click to collapse
Thank you, Joel! I'm excited to learn as much as possible from tgis forum. I actually changed over to T-Mobile, and have been good for the most part. The problem i'm having now is related to finding a way to flash the radio to all of their Rf's. I rooted, and attempted to flash the modem and bootloader from N920T, but it failed. I am still having a hard timr understanding why the identical hardware will not accept firmware from different model numbers. Again, very inexperienced, so it may be something very obvious i dont know about. If could offer any assistance, or provide and thread links that may be useful, i wpuld very grateful. Ive been searching nonstop, reading, and still cant seem to find a way.
Rockstah said:
Thank you, Joel! I'm excited to learn as much as possible from tgis forum. I actually changed over to T-Mobile, and have been good for the most part. The problem i'm having now is related to finding a way to flash the radio to all of their Rf's. I rooted, and attempted to flash the modem and bootloader from N920T, but it failed. I am still having a hard timr understanding why the identical hardware will not accept firmware from different model numbers. Again, very inexperienced, so it may be something very obvious i dont know about. If could offer any assistance, or provide and thread links that may be useful, i wpuld very grateful. Ive been searching nonstop, reading, and still cant seem to find a way.
Click to expand...
Click to collapse
Well, the hardware (particularly the modem) is not compatible, hance the failed install. You are lucky it cancelled out as you could have had worse problems on your hands.
The way i see it, you will have to wait for other regions for the Note 5 Duos to open up before you get flashing options. I would even question the need for that, if you get a decent range of bands with T-Mo (I am assuming you can get 4G).
If you want to explore further anyway, please check out this thread:
> Samsung Galaxy Note5 > Galaxy Note5 Q&A, Help & Troubleshooting > [Help Thread][Galaxy Note5] Ask Any Question, Noob Friendly
Hope this helps.
joel.maxuel said:
Hope this helps.
Click to expand...
Click to collapse
It did, thank you! I get decent service (including LTE) almost everywhere. Problem is, once I get to my.house, I go completely out of service. No call.I no text. It wouldn't be a big deal, but the Taiwanese phone doesn't have a way to turn WiFi calling.
Rockstah said:
It did, thank you! I get decent service (including LTE) almost everywhere. Problem is, once I get to my.house, I go completely out of service. No call.I no text. It wouldn't be a big deal, but the Taiwanese phone doesn't have a way to turn WiFi calling.
Click to expand...
Click to collapse
Aha. That and no sign of the 700mHz band (which may not be part of your phone anyway, not just hidden by the current firmware).
Since the firmware would need deep support of Wifi Calling (or VoLTE), as in more than just an App, I am afraid you will have to wait until the Duos releases into an area with that support in their firmware (and hope that, that area's firmware doesn't disable a frequency you use).
Makes scraping all the lead paint[*] off the house the more manageable task, doesn't it?
[*] I really don't know if your house does indeed have lead paint. I am assuming it's coated in something metal, or concrete, which avoids typically high frequency radio waves from entering. I never had that problem with my house (which may be strange, since it was built in the 40's), but maybe creating ways to boost the existing signal may be in order instead.

? How to get LTE speed on US LTE tablet running ROW LTE Image?

Hi folks,
I've got the US LTE original Shield tablet, which is the replacement that NVidia sent me for my original "pyro edition" tablet. Since ATT haven't released the Nougat (Android 7, software package 5.0 or 5.1) builds for this tablet, but the ROW tablets are able to get this update, I flashed my tablet using adb/fastboot with the full ROW 5.0 package downloaded from the NVidia site. I then connected to WIFI, and let it pull down the 5.1 update. Factory reset, flash TWRP, rooted with SuperSU. Easy peasy. Then I set up the tablet with my accounts and such.
Based on good info from user @Son-j I made two build.prop edits, changing ro.build.flavor to wx_na_do-user (was wx_un_do-user) and ro.product.name to wx_na_do (was wx_un_do). This changed the reported signal type from H+ to 4G. Unfortunately I'm having trouble finding the thread where he suggested doing this. I think it was on the geforce web forum.
The only problem I've found so far is that I'm not getting LTE speeds. I was in Chicago for a couple days, in an area with strong LTE signal, and my other devices were reporting LTE and getting ~20Mbps down / 10+ Mbps up. My Shield was pulling maybe 8 Mbps down at best , and 1-2 Mbps up. At home in my suburban location, the difference is negligible (most devices here do 5 Mbps down / 1 Mbps up, LTE or 4G).
Still, I'd like to fix this if possible. Are there further edits or flashings that will let my US device running the ROW build get LTE? I have gone in and verified that my APN settings are the recommended ones from ATT. These showed up automatically, and matched the ATT recommendations.
Thanks in advance!
Hi I'm not sure but I there was a thread here in XDA that says it's still difficult to change the LTE (RoW to US, and vice versa) bands because developers couldn't find yet which part of the code to modify... It's not also confirmed if it is indeed possible to change the LTE bands to support.
So basically, flashing RoW LTE on US LTE device will still result in US-LTE supported bands. That's what I understood.
But what you did is quite a revelation. Can anyone else confirm that modifying the build prop will work? Boy I'm excited!
Son-j said:
Hi I'm not sure but I there was a thread here in XDA that says it's still difficult to change the LTE (RoW to US, and vice versa) bands because developers couldn't find yet which part of the code to modify... It's not also confirmed if it is indeed possible to change the LTE bands to support.
So basically, flashing RoW LTE on US LTE device will still result in US-LTE supported bands. That's what I understood.
But what you did is quite a revelation. Can anyone else confirm that modifying the build prop will work? Boy I'm excited!
Click to expand...
Click to collapse
Hi @Son-j -
Thanks! Do you happen to remember which thread had those two buildprop edits? I found them after seeing a post from you a few days ago, but now I can't find it at all. My google mojo has fled me.
I'd like to have a link there so others can see the original source.
It would be nice to get LTE speed, if someone knows how, but most places where I use the tablet don't have super fast LTE, so the difference for me isn't enough to make me downgrade to the marshmallow US LTE build. I'll stick with nougat for now, and hope eventually to get full speed. Who knows, maybe ATT will eventually release the 5.1 US LTE build...
For clarity here is the set of APN settings I'm using. I'm going with the column in the center at the bottom for Tablets:
https://www.att.com/esupport/article.html#!/wireless/KM1062162
All of this was correctly entered by default except I did need to edit two keys:
APN was listed as broadband instead of Broadband (yes, I'm picky, but wanted to match case)
APN type was listed as just default. I edited it to match the listed setting of: default,mms,supl,hipri,fota
Also I'm set to LTE for "Preferred network type"
Ok I think there's a misunderstanding. Uhm, I'm trying to look for the related posts here at the Nvidia threads but it seems to have disappeared.
Just to set something straight, LTE speed is influenced by:
1. LTE device with specific supported LTE bands
2. LTE sim
3. Location with LTE signals
I take it that for your specific device - US LTE Shield Tablet (just like mine) - you satisfy all 3.
For the record, flashing RoW LTE on our US device won't change the supported LTE bands (check baseband code in About Tablet section of settings). So if you used to have AT&T LTE speeds/signals using US LTE ROMs, it shouldn't change if you flashed RoW LTE ROM on the same device.
We are speculating though that there might be a way, software/firmware speaking. We are hoping it's not hardware-baked.
Son-j said:
Ok I think there's a misunderstanding. Uhm, I'm trying to look for the related posts here at the Nvidia threads but it seems to have disappeared.
Just to set something straight, LTE speed is influenced by:
1. LTE device with specific supported LTE bands
2. LTE sim
3. Location with LTE signals
I take it that for your specific device - US LTE Shield Tablet (just like mine) - you satisfy all 3.
For the record, flashing RoW LTE on our US device won't change the supported LTE bands (check baseband code in About Tablet section of settings). So if you used to have AT&T LTE speeds/signals using US LTE ROMs, it shouldn't change if you flashed RoW LTE ROM on the same device.
We are speculating though that there might be a way, software/firmware speaking. We are hoping it's not hardware-baked.
Click to expand...
Click to collapse
Thanks Son-j. It kind of freaks me out that just a week ago I found the thread that recommended those two changes in buildprop, but now I can't find it, and apparently neither can you! So maybe I'm not crazy, since it's more than just me having problems finding it.
Anyway, yes, I used to get the LTE indicator on the tablet, when in an area that has decent reception of those bands. At my workplace, which is a building built like a Faraday cage, we can get only ATT service, via repeaters spread throughout the building (I switched from Verizon in part due to this). Phones almost always report ~3 bars of LTE in places I usually find myself within the building. However, speeds tend to be <10 Mbps (tested using Speedtest.net from either my phone or tablet). So, despite getting "LTE service" there (prior to my software update), the speeds were nothing so great. For this reason, I'm not TOO worked up that my US tablet running ROW software isn't reporting LTE... most places where I use the tablet don't have blazing fast LTE, and the difference between the 4G service it actually gets and the LTE it "used to get" is not that great.
I would like to fix the problem if possible, but it's not a critical thing, and I may just put it on the back burner until the US LTE 5.1 image comes out, then flash back to that. I've got lots of other fish to fry these days.
Always interesting discussion. Thanks Son-j!
Marc
If it's just a speed issue, that will be the provider's end. If it's a signal issue, that's device problem.
It's possible to get an LTE signal but with HSPA speed in some areas.
There is an app called LTE Discovery. It will tell you which band it is currently connected to. I've got it on my tablet on T-Mobile. I am having problems with it connecting to anything other than 3G. But I have read others with the Shield tablet having similar problems with T-Mobile.
Sent from the Delta Quadrant using Tapatalk
caseyatbt said:
There is an app called LTE Discovery. It will tell you which band it is currently connected to. I've got it on my tablet on T-Mobile. I am having problems with it connecting to anything other than 3G. But I have read others with the Shield tablet having similar problems with T-Mobile.
Sent from the Delta Quadrant using Tapatalk
Click to expand...
Click to collapse
Thanks @caseyatbt,
I was unaware of that app. I downloaded it on my phone (which gets LTE just fine at my house, most of the time) and it reports all kinds of fun stuff about the LTE signal it's connected to. On the US Shield tablet running ROW stock, this is what I get, which frankly makes me think the tablet is connecting via CDMA of all things, despite having chosen all the correct options in the Settings / Mobile section:
The fact that my radio seems to be connecting to WCDMA instead of GSM is kinda freaking me out, folks.
I'm tempted to try flashing the US LTE device Marshmallow recovery image, and see if that fixes it. I understand the flashes don't change the baseband, but since I flashed 5.0 and the the device did an OTA update to 5.1, that might have changed the baseband, eh?
So, if me flashing the marshmallow files doesn't fix it, I might reflash an earlier edition and let it OTA to latest edition, which presumably would install correct "latest" baseband for the model.
We'll see ... I'm still not committed to one direction or another.
Marc
OK, I just flashed the 4.4.0 version of Marshmallow. (full flash of all Nvidia recovery image files). After letting it reboot the first time, it checked for update and found none, as expected.
NO LTE. Downloded the LTE Discovery app, and it still only sees WCDMA signals. Uggh.
Now I'm going to install the 4.3, and let it OTA to 4.4, and hope that refreshes the modem/radio. If anybody is following this, wish me luck!
EDIT: OK, I'm in idiot mode. I downloaded what I thought was the 4.3 US LTE image and it was actually the 4.3 ROW image. I didn't notice this until after flashing, and seeing the H+ icon, and noticing lack of ATT usage tracking app. Oops.
I don't see the 4.3 US LTE image on the site; I'm now downloading the 4.1 image, and will do OTA updates from there, checking as I go how which signal my radio is getting.
No Joy.
I flashed US LTE 4.1 image. AFter the flash, LTE Discovery still reports just HSPA+ signal from WCDMA towers. I then let it take the OTA for 4.4... the latest available for the US LTE tablet, and after it ran through its update process, I'm still on WCDMA.
Uggh. I doubt there's any WCDMA signal where I work so I may have killed my tablet, at least as far as using it at work is concerned.
I'm sure there IS a path back, I just can't imagine what it might be, at the moment. I'll start a new thread to be more specific to this current problem.
Sigh.
Frankenscript said:
Thanks Son-j. It kind of freaks me out that just a week ago I found the thread that recommended those two changes in buildprop, but now I can't find it, and apparently neither can you! So maybe I'm not crazy, since it's more than just me having problems finding it.
Click to expand...
Click to collapse
Eventually found that thread with the buildprop changes, see here if interested or if you ever need to find it.
I just checked my Shield on T-Mobile. In the same area on LTE Discovery that yours says W-CDMA mine says the same thing (under Neighbor Cells). When you scroll to the bottom, what does it say for carrier?
Carrier: AT&T (310410)
caseyatbt said:
I just checked my Shield on T-Mobile. In the same area on LTE Discovery that yours says W-CDMA mine says the same thing (under Neighbor Cells). When you scroll to the bottom, what does it say for carrier?
Click to expand...
Click to collapse
Here are screen shots of my sim status (personal details redacted) and the LTE discovery window:
I am thinking that it is possible that W-CDMA doesn't mean what we think it means. It shows you connected to AT&T so you are not on someone elses network.
caseyatbt said:
I am thinking that it is possible that W-CDMA doesn't mean what we think it means. It shows you connected to AT&T so you are not on someone elses network.
Click to expand...
Click to collapse
I talked to ATT. It's sort of their backup network, not available everywhere. My other devices definitely show LTE. Will post a screen so from my phone a bit later which shows that.
Sent from my LG-D851 using Tapatalk
caseyatbt said:
I am thinking that it is possible that W-CDMA doesn't mean what we think it means. It shows you connected to AT&T so you are not on someone elses network.
Click to expand...
Click to collapse
Here are some pictures taken from my phone, which is working properly. In settings, you can see the LTE network type and in the LTE Discovery app screen capture, all the LTE towers.
ATT maintains a "vestigial" WCDMA to allow some level of connectivity by devices that don't have GSM/LTE, but it's not everywhere and it's pretty slow.
The Shield used to show LTE in the Settings Cellular network type, as well as giving the LTE icon, when appropriate. Now it's just HSPA. Sigh.
Frankenscript said:
Here are some pictures taken from my phone, which is working properly. In settings, you can see the LTE network type and in the LTE Discovery app screen capture, all the LTE towers.
ATT maintains a "vestigial" WCDMA to allow some level of connectivity by devices that don't have GSM/LTE, but it's not everywhere and it's pretty slow.
The Shield used to show LTE in the Settings Cellular network type, as well as giving the LTE icon, when appropriate. Now it's just HSPA. Sigh.
Click to expand...
Click to collapse
My T-Mobile phone shows similar to your phone with LTE. T-Mobile must have a similar vestigial WCDMA that is showing up on my tablet. I still haven't found anyone that was able to get T-Mobile LTE working after it was only giving them 3G and HSPA. I have heard it either worked or it didn't.

LTE Band 12, VoLTE, and T-Mobile

I am starting this thread, since there seems to be a lot of confusion around "newer" LTE bands, like Band 12 on T-Mobile, which apparently require a fully functioning and "approved" VoLTE phone to get reception.
There are various threads in device-specific forums, but they are not getting a lot of attention, and this is a significant enough problem that it should be more visible.
T-Mobile at this point has pretty fantastic coverage via the 700MHz Band 12 LTE network.
The only problem is that Band 12 requires the phone to be VoLTE "certified". The rumor was that phones could still connect to this band/LTE-network and send/receive data, but that they would fall back to alternative bands, even 3G or 2G, for phone calls. For a lot of people that would be "good enough" if not ideal.
Based on some recent testing, this is NOT CORRECT:
While phones may "sometimes" connect to Band 12 for data, the much more common scenario is apparently that the phone will disconnect from Band 12 almost immediately, or will refuse to connect to Band 12, and will instead default to an alternative LTE, 4G, 3G, or 2G connection.
In other words: even if you have perfect LTE Band 12 coverage (5/5 bars, or 100%), your "Band 12 capable" phone may instead try to connect to a really ****ty GPRS or EDGE tower that has barely any reception for the phone.
I recently encountered this with my Xperia X Compact while travelling: My phone would barely be able to connect to a T-Mobile tower with a GPRS data connection, while my wife's Moto G4 would get 5/5 or 100% LTE reception. Swapping SIM cards had the same result, so we know the problem rests with the phone.
Searching for "Available Mobile Networks" on my "band 12 capable" phone would show various T-Mobile 4G networks, but the phone would be unable to connect to them.
Talking to other Xperia X Compact owners, they have the same problem: the phone will sporadically connect to Band 12, but it is not a reliable connection (if the phone even connects) and it will (more likely) prefer other networks/bands/frequencies.
Based on the phone having the proper frequencies, I would assume that T-Mobile has some mechanism on some (or the majority of) towers where they disconnect non-VoLTE certified devices.
Anecdotally, I also had a similar issue with my previous phone - a Nexus 5x. The phone is even VoLTE certified, but when using Cyanogenmod/LineageOS, it would have really terrible reception, despite the location having almost perfect Band 12 coverage - LineageOS/CM does not (or had no) VoLTE support.
I have also tried "hacking" the X Compact to enable VoLTE support by adding the relevant lines to the build.prop and enabling the option under Settings and (*#*#4636#*#*) but this does not appear to make any difference.
A list of T-Mobile "VoLTE certified" phones can be found here:
http://www.spectrumgateway.com/compatible-phones
Would be great if anyone has any suggestions how to resolve this, or force the phone to prioritize Band 12, but it would otherwise appear that the only solution is to get the phone certified by T-Mobile (so much for net neutrality and open access).
I'm using an Xperia X Compact and my home market only has band 12 lte and I can't connect to it. Which means I'm always in 3g or roaming and rarely have data in buildings. It's maddening because I will only buy Sony. I think they are the only manufacturer making attractive handsets and the build quality is light years beyond well marketed, poorly constructed brands like Samsung and LG. But regardless of anyone's choice of manufacturer, a device with a functioning 700 mhz lte radio should function just fine on the corresponding network regardless of where it was purchased.
Would certifying this device and enabling VOLTE be particularly costly to Sony? Correct me if I'm wrong but based on internal components this device should be capable of this ja?
I think it wouldn't hurt to send petitions to both the manufacturer and T-mobile USA. This certainly doesn't help Sony in a market they are seriously struggling in. It also isn't very uncarrier to favor certain devices over others.
The only reason I switched from Verizon was the ability to choose my device. That and the things John Legere was doing to change the industry. I believed in what he was saying. But right now it isn't working for me and likely many others. He should know. I can say firsthand that the guy answers his emails. I think we need to show both parties that this is worth their attention.
---------- Post added at 01:09 AM ---------- Previous post was at 12:14 AM ----------
I should mention that after multiple calls to T-mobile tech support I received a cryptic call very late at night from someone high up in tech support.
Long story short he at least admitted that even though it wasn't a t mobile device and even though it didn't support VoLTE, it should still connect to band 12 just fine. He also said that they were having problems with this sort of thing in my area and that it should be resolved in a month. He also said my IMEI was logged and I would be given priority in the matter. Whatever that means.
I should also mention that was a month ago and he didn't have an email to give me. He did however give me a phone number (probably just the department) that I need to dig up.
Could just be a bunch of fluff because they are afraid to lose customers. Then again he was from tech support not customer retention. And as I said t mobile does listen to its customers.
POMF2K said:
I'm using an Xperia X Compact and my home market only has band 12 lte and I can't connect to it. Which means I'm always in 3g or roaming and rarely have data in buildings. It's maddening because I will only buy Sony. I think they are the only manufacturer making attractive handsets and the build quality is light years beyond well marketed, poorly constructed brands like Samsung and LG. But regardless of anyone's choice of manufacturer, a device with a functioning 700 mhz lte radio should function just fine on the corresponding network regardless of where it was purchased.
Would certifying this device and enabling VOLTE be particularly costly to Sony? Correct me if I'm wrong but based on internal components this device should be capable of this ja?
I think it wouldn't hurt to send petitions to both the manufacturer and T-mobile USA. This certainly doesn't help Sony in a market they are seriously struggling in. It also isn't very uncarrier to favor certain devices over others.
The only reason I switched from Verizon was the ability to choose my device. That and the things John Legere was doing to change the industry. I believed in what he was saying. But right now it isn't working for me and likely many others. He should know. I can say firsthand that the guy answers his emails. I think we need to show both parties that this is worth their attention.
---------- Post added at 01:09 AM ---------- Previous post was at 12:14 AM ----------
I should mention that after multiple calls to T-mobile tech support I received a cryptic call very late at night from someone high up in tech support.
Long story short he at least admitted that even though it wasn't a t mobile device and even though it didn't support VoLTE, it should still connect to band 12 just fine. He also said that they were having problems with this sort of thing in my area and that it should be resolved in a month. He also said my IMEI was logged and I would be given priority in the matter. Whatever that means.
I should also mention that was a month ago and he didn't have an email to give me. He did however give me a phone number (probably just the department) that I need to dig up.
Could just be a bunch of fluff because they are afraid to lose customers. Then again he was from tech support not customer retention. And as I said t mobile does listen to its customers.
Click to expand...
Click to collapse
Since I did encounter this also on my Nexus 5x with LineageOS, I doubt that what T-Mobile told you is true. They must be actively blocking these non-certified handsets, since the phone should just attempt connecting.
So who do we need to appeal to? T mobile or Sony.?
POMF2K said:
So who do we need to appeal to? T mobile or Sony.?
Click to expand...
Click to collapse
Both. Maybe also complain to the FCC - I thought that carriers needed to provide open access to their network. Verizon got into hot water for not doing so ...
Does your compact ever connect to lte for a few seconds after a reboot?
I might try to force LTE and restart and see if that has any effect.
I just flashed the UK. T mobile networks work just fine. Well except lte/4g but that was expected.
POMF2K said:
Does your compact ever connect to lte for a few seconds after a reboot?
I might try to force LTE and restart and see if that has any effect.
I just flashed the UK. T mobile networks work just fine. Well except lte/4g but that was expected.
Click to expand...
Click to collapse
It does connect sometimes but it then usually kicks down to Band 4 or a GSM band (HSDPA, UMTS, EDGE, or even GPRS).
I cannot find any info how to prioritize LTE bands, so I assume this is T-Mobile's band 12 cell tower's kicking the phone off when they notice that it is not VoLTE approved.
Interesting discussion on Howard forums....
http://www.howardforums.com/showthr...rtphones-with-band-12-LTE-w-o-VoLTE-now/page2
POMF2K said:
Interesting discussion on Howard forums....
http://www.howardforums.com/showthr...rtphones-with-band-12-LTE-w-o-VoLTE-now/page2
Click to expand...
Click to collapse
Interesting discussion though nothing new.
Yes, we know that Band 12 phones should be able to get a data connection, yet T-Mobile apparently actively disconnects them (or bars them from connecting), especially in areas where Band 12 would give you great coverage but there is no other coverage.
F Sony and F T-Mobile for this!
BTW: here is an article about the follow up model: https://arstechnica.com/gadgets/2017/08/sony-xperia-xz1-compact/
Please leave comments about Sony not getting their phones approved for VoLTE with T-Mobile and the phone therefore NOT REALLY WORKING with the carrier.
It would seem to me that the only solution to this problem would be either T-Mobile accepting a standard spec for VoLTE, they open source their code for VoLTE, or someone figures out how to implement VoLTE and trick T-Mobile to think it is an approved "whitelisted" phone.
Given that the T-Mobile network is getting worse and worse every day without Band 12 coverage, I find it really surprising that most people just don't seem to care. Does nobody use their phone outside of WiFi?
andTab said:
It would seem to me that the only solution to this problem would be either T-Mobile accepting a standard spec for VoLTE, they open source their code for VoLTE, or someone figures out how to implement VoLTE and trick T-Mobile to think it is an approved "whitelisted" phone.
Given that the T-Mobile network is getting worse and worse every day without Band 12 coverage, I find it really surprising that most people just don't seem to care. Does nobody use their phone outside of WiFi?
Click to expand...
Click to collapse
There is a standard spec, the problem is the certification. It requires a certificate from T-mobile to be used by the phone, which is gained through certification. And if SONY is detecting T-mobile at the modem level then there isn't anything a ROM can do with or without a ROM. I had a Z5, but this drove me crazy so I switched to a Pixel.
I wouldn't expect this to change based on SONY de-prioritizing the US phone market, so either upgrade to a new supported sony phone or move on (shrug)
sovanyio said:
There is a standard spec, the problem is the certification. It requires a certificate from T-mobile to be used by the phone, which is gained through certification. And if SONY is detecting T-mobile at the modem level then there isn't anything a ROM can do with or without a ROM. I had a Z5, but this drove me crazy so I switched to a Pixel.
I wouldn't expect this to change based on SONY de-prioritizing the US phone market, so either upgrade to a new supported sony phone or move on (shrug)
Click to expand...
Click to collapse
That can't be true.
I accept that T-Mobile may issue a certificate but that must be processed on the rom/OS/phone.apk level. Otherwise, every custom ROM on any certified phone would work. We all know that is not the case.
If it's the rom/OS/phone.apk though, why can't we hack a phone to work with TMUS / VoLTE?
I have an x compact and while it is the best device I have ever owned it is essentially unusable on T-Mobile or att.
andTab said:
That can't be true.
I accept that T-Mobile may issue a certificate but that must be processed on the rom/OS/phone.apk level. Otherwise, every custom ROM on any certified phone would work. We all know that is not the case.
If it's the rom/OS/phone.apk though, why can't we hack a phone to work with TMUS / VoLTE?
I have an x compact and while it is the best device I have ever owned it is essentially unusable on T-Mobile or att.
Click to expand...
Click to collapse
Because the SONY modem firmware doesn't even attempt to negotiate VoLTE, which does *not* happen in user space. It is likely possible to hack the qualcomm modem with QPST to enable this, but without documentation and correct values one will not get very far.
sovanyio said:
Because the SONY modem firmware doesn't even attempt to negotiate VoLTE, which does *not* happen in user space. It is likely possible to hack the qualcomm modem with QPST to enable this, but without documentation and correct values one will not get very far.
Click to expand...
Click to collapse
If it was the modem, then flashing a new system (eg custom ROM) should not make any difference.
I also have a Nexus 5x. With stock it is fantastic and uses VoLTE on T-Mobile. With LineageOS, it is useless on Band 12. SAME MODEM!
Experience therefore shows that it is the OS/System that somehow prevents this from working.
andTab said:
If it was the modem, then flashing a new system (eg custom ROM) should not make any difference.
I also have a Nexus 5x. With stock it is fantastic and uses VoLTE on T-Mobile. With LineageOS, it is useless on Band 12. SAME MODEM!
Experience therefore shows that it is the OS/System that somehow prevents this from working.
Click to expand...
Click to collapse
The Nexus 5x is a different phone made by a different manufacturer with a different firmware scheme. You cannot compare them directly.
I noticed that the XZ1 Compact says right on the website compatible with t mobile band 12 and wifi calling... this is infuriating. It should be easy for them to patch the Xperia x compact.
I would have never purchased this if I had known. Especially since they apparently flashed an update to my old t mobile z3 that allows voice over lte and band 12.
Sony X Compact
sovanyio said:
There is a standard spec, the problem is the certification. It requires a certificate from T-mobile to be used by the phone, which is gained through certification. And if SONY is detecting T-mobile at the modem level then there isn't anything a ROM can do with or without a ROM. I had a Z5, but this drove me crazy so I switched to a Pixel.
I wouldn't expect this to change based on SONY de-prioritizing the US phone market, so either upgrade to a new supported sony phone or move on (shrug)
Click to expand...
Click to collapse
It has to be on Sony, use the t-mobile BYOD app to check, I have a Huawei mate 9 that I just purchased, connects perfectly on band 12, VoLTE works just like it's supposed to. On a side note I went through three Sony phones before I bought this Huawei, had to return all three due to quality control issues, one had worst touches that made the phone unusable, one wouldn't pick up the SIM card, and the third wouldn't power on at all, thank good Amazon refunded my money on all three. They may have the Sony name on the phone, but they are still build by the lowest bidder in China and makes with Sony's name.
revjamescarver said:
It has to be on Sony, use the t-mobile BYOD app to check, I have a Huawei mate 9 that I just purchased, connects perfectly on band 12, VoLTE works just like it's supposed to. On a side note I went through three Sony phones before I bought this Huawei, had to return all three due to quality control issues, one had worst touches that made the phone unusable, one wouldn't pick up the SIM card, and the third wouldn't power on at all, thank good Amazon refunded my money on all three. They may have the Sony name on the phone, but they are still build by the lowest bidder in China and makes with Sony's name.
Click to expand...
Click to collapse
See this: http://www.androidpolice.com/2015/0...cked-smartphones-and-yep-its-still-confusing/ It is up to an OEM to decide to go through this process per-phone. Since no US carrier carried the phone they didn't not bother spending the money or time to certify it. I loved the SONY design, but since they weren't supporting the market I had to abandon them for other phones.

Install T-Mobile software instead of international

Hi everyone. I purchased a OnePlus 8 5G directly from OnePlus, running on the T-Mobile network. After trying to figure out why I didn't receive the T-Mobile 5G SA update (10.5.17.IN55CB), I realized my phone is running the international version of the software. I guess this is because it's factory unlocked but I didn't realize this would limit my access to T-Mobile 5G updates! I never travel internationally and don't really care about an unlocked bootloader, etc. as long as the SIM is unlocked.
Can I manually download and install the T-Mobile software so I will get the 5G SA update (and future T-Mobile OTA updates)?
i was also wondering if that would make a difference. maybe someone could provide the modem.img from that update, if it changed. flashing the euro modem on the international rom definitely made a difference for me. not really with speed but overall coverage and stability.
nickdearing88 said:
Hi everyone. I purchased a OnePlus 8 5G directly from OnePlus, running on the T-Mobile network. After trying to figure out why I didn't receive the T-Mobile 5G SA update (10.5.17.IN55CB), I realized my phone is running the international version of the software. I guess this is because it's factory unlocked but I didn't realize this would limit my access to T-Mobile 5G updates! I never travel internationally and don't really care about an unlocked bootloader, etc. as long as the SIM is unlocked.
Can I manually download and install the T-Mobile software so I will get the 5G SA update (and future T-Mobile OTA updates)?
Click to expand...
Click to collapse
Right now you dont want it. It breaks incoming and outgoing phone calls.
Seems they pulled the update as well
Guys I'm on TMO but switched over to global voluntarily. Honestly check out TMO 5G info and you'll find it's not as great as you think. It's the beginning of a software change. Veteran modders know the beginning of updates have a lot of bugs.
If you really want it then get the MSM Tool, downgrade to 10.5.7 and let it upgrade you manually to 10.5.17. then you can get back to global if you'd like with the modem. Happy modding!
Thanks, it sounds like it was premature. I live in a rural area and my main concerns are 1) better (not reliant on LTE) 600Mhz coverage and 2) lower latency.
Do you think the global software line will get an SA update down the road? Are there any other difference between the global and T-Mobile line of software that would affect my coverage performance with LTE or 5G?
nickdearing88 said:
Thanks, it sounds like it was premature. I live in a rural area and my main concerns are 1) better (not reliant on LTE) 600Mhz coverage and 2) lower latency.
Do you think the global software line will get an SA update down the road? Are there any other difference between the global and T-Mobile line of software that would affect my coverage performance with LTE or 5G?
Click to expand...
Click to collapse
Great question, This is my first OnePlus phone so I can't tell you if and when gonna will get the update. What I have heard of that TMO is rolling out 5G in several layers. This first one is pretty low key but it had some books already. Second and third would be better. I guess check around here to see more about it. If you are absolutely sure you want this update then you can use MSM took to downgrade then just let the TMO servers do the work for you. Happy modding!
nickdearing88 said:
Thanks, it sounds like it was premature. I live in a rural area and my main concerns are 1) better (not reliant on LTE) 600Mhz coverage and 2) lower latency.
Do you think the global software line will get an SA update down the road? Are there any other difference between the global and T-Mobile line of software that would affect my coverage performance with LTE or 5G?
Click to expand...
Click to collapse
I would be surprised if the global version got an update for SA 5g. That's TMO specific and OnePlus would have zero care about a specific carrier of all the world's carriers .
There are differences in modems according to TMobile. I can't remember specifics but I think it was carrier aggregation on band 66 ( I don't remember much so I may be way off)
Josh McGrath said:
I would be surprised if the global version got an update for SA 5g. That's TMO specific and OnePlus would have zero care about a specific carrier of all the world's carriers .
There are differences in modems according to TMobile. I can't remember specifics but I think it was carrier aggregation on band 66 ( I don't remember much so I may be way off)
Click to expand...
Click to collapse
Yeah, I figured that was unlikely with the global version, although I'm sure carriers across the world will begin deploying SA 5G at some point.
I was going to start a new thread but after you notes about the modem differences, this might relate to another issue I've noticed: When connected to Band 2 (1900 Mhz) with LTE or 5G, I was getting really good speeds (~30Mbps Down/5Mbps Up). Now, when I test using 5G or LTE (by turning off 5G) my speed tests are horrible: ~1Mbps Down/0.7Mbps Up. I have tested with "Smart 5G" on and off, and also removed and reinstalled the SIM card. If I pop the SIM card out and put it back into my Pixel 2, I get 30Mpbs Down/5Mpbs Up with LTE on Band 2. My Pixel 2 was purchased directly from Google and is factory unlocked/direct Google updates.
Do you think this is because of the carrier agg issue you mentioned? In my area Band 4/Band 66 is only used for T-Mobile 2G/3G, to my knowledge. LTE is offered on Bands 2, 12, and 71. 5G NR seems to only be on Band 71 here at present.
Josh McGrath said:
I would be surprised if the global version got an update for SA 5g. That's TMO specific and OnePlus would have zero care about a specific carrier of all the world's carriers .
There are differences in modems according to TMobile. I can't remember specifics but I think it was carrier aggregation on band 66 ( I don't remember much so I may be way off)
Click to expand...
Click to collapse
Josh, not often this happens, but I disagree with what you say here. Normally I agree with everything you post. However, this time I have to disagree.
5G SA is not at all T-Mo specific and is a standardized implementation for carriers should they choose to go that route.
However, OnePlus caring about it is up in the air, lulz!
See here: https://ibasis.com/what-is-5g-sa-nsa/
5G SA means stand alone. This means that the device will only ride on 5G and not aggregate with 4G.
If I am wrong please correct me. Thanks!
Nathan.7118391 said:
If you are absolutely sure you want this update then you can use MSM took to downgrade then just let the TMO servers do the work for you.
Click to expand...
Click to collapse
I and many others posted that they cannot get the update. Those that did said they had connectivity issues. I suspect that T-Mo pulled the update. I don't know this for fact, however I cannot get the update. T-Mo site says check back after 8/31. That's crazy weird. Others also complain. I think the update is borked hence the lack of wide roll out. . Again, dont know this for fact but just speculating...
Scott said:
Josh, not often this happens, but I disagree with what you say here. Normally I agree with everything you post. However, this time I have to disagree.
5G SA is not at all T-Mo specific and is a standardized implementation for carriers should they choose to go that route.
However, OnePlus caring about it is up in the air, lulz!
See here: https://ibasis.com/what-is-5g-sa-nsa/
5G SA means stand alone. This means that the device will only ride on 5G and not aggregate with 4G.
If I am wrong please correct me. Thanks!
...
Click to expand...
Click to collapse
For sure. I do stand corrected here on SA. I was referring to the specific bands that TMobile uses for SA 5g vs world bands SA 5g but who knows if that's impossible but I, like you, think that OP will not care about it or would screw it up.
As for the modem differences, I was referring to an older post from TMobile on their forums during the 6t launch days so I can't really remember exactly what it was. I think if you searched my posts from way you could find it
Speaking of, I am incredibly disappointed in tmos 5g. I'm lucky to get 20 dl. Are you having any better luck
Scott said:
Josh, not often this happens, but I disagree with what you say here. Normally I agree with everything you post. However, this time I have to disagree.
5G SA is not at all T-Mo specific and is a standardized implementation for carriers should they choose to go that route.
However, OnePlus caring about it is up in the air, lulz!
See here: https://ibasis.com/what-is-5g-sa-nsa/
5G SA means stand alone. This means that the device will only ride on 5G and not aggregate with 4G.
If I am wrong please correct me. Thanks!
I and many others posted that they cannot get the update. Those that did said they had connectivity issues. I suspect that T-Mo pulled the update. I don't know this for fact, however I cannot get the update. T-Mo site says check back after 8/31. That's crazy weird. Others also complain. I think the update is borked hence the lack of wide roll out. . Again, dont know this for fact but just speculating...
Click to expand...
Click to collapse
Yeah I think you are right. As soon as it was available it became unavailable. They will roll it out when those bugs are fixed. This is one of the reasons I don't like TMO stock. They are buggy and slow to update. Not to mention all the bloatware.
Josh McGrath said:
Speaking of, I am incredibly disappointed in tmos 5g. I'm lucky to get 20 dl. Are you having any better luck
Click to expand...
Click to collapse
I am EXTREMLEY disappointed
History of my observations...
When I first switched to T-Mobile with the 6T the speeds were great. Well, decent. But around the time the S20 series came out I noticed extreme sluggishness with the 6T. Compared it to the people in the store and there's wer the same. A massive down turn in speed. I suspect it had something to do with the implementation of 5G in the area. It was my guess... Anways, moved back to T-Mobile two months ago and got this phone. The speeds are even worse. So this phone on 5G is just as bad as LTE. I disabled 5G and tested. Same results.
Long story short, T-mobile did something and slowed my connection down.
Your lucky. Very luck. I routinely get 2 to 5 mbs when I am home. In town I dont think I got over 25Mbs. AT&T has the best network in Fargo. 200MBS down on S20U all day!

Categories

Resources