Enable 850MHz UMTS/HSDPA on X1i via ROM update?

Enable 850MHz UMTS/HSDPA on X1i via ROM update? - XPERIA X1 ROM Development

Hello friends.. I know this question has been hinted at in other threads, but on the off chance that this may lead to something, I wanted to get a definitive answer.
Like other US customers, I am saddened, insulted, and angered after receiving the final specifications of the X1a and X1i, having endured months of pushed-back release dates by SE, which basically state that I must choose between:
- crap video capture (X1a), or
- crap 3G support in my region (X1i)
Now, all emotions aside, we know that the video situation can't be remedied in the X1a, since this is a limitation of the inferior hardware.
The question is -- will it be POSSIBLE to remedy the 850MHz 3G situation in the X1i via ROM update? Or is this also a hardware limitation?
Any insight would be appreciated, thanks.

poorangus said:
Hello friends.. I know this question has been hinted at in other threads, but on the off chance that this may lead to something, I wanted to get a definitive answer.
Like other US customers, I am saddened, insulted, and angered after receiving the final specifications of the X1a and X1i, having endured months of pushed-back release dates by SE, which basically state that I must choose between:
- crap video capture (X1a), or
- crap 3G support in my region (X1i)
Now, all emotions aside, we know that the video situation can't be remedied in the X1a, since this is a limitation of the inferior hardware.
The question is -- will it be POSSIBLE to remedy the 850MHz 3G situation in the X1i via ROM update? Or is this also a hardware limitation?
Any insight would be appreciated, thanks.
Click to expand...
Click to collapse
And again: X1i has 850 MHz support, at least in Europe in the unbranded UK ROM it is definitely listed as GSM (1900+850) + UMTS (1900+850).

Thanks for the reply, Norti. To the best of my knowledge, it has been determined in numerous forums that what you are seeing is a generic Windows Mobile setting. You need it to switch between 1900/2100, but 850 is not actually supported by the X1i, even though it appears as part of the selection.
See: http://www.xperiax1.net/forum/xperia-x1/977-x1i-3g-umts-bands.html
Thanks.. anyone else?

poorangus said:
Thanks for the reply, Norti. To the best of my knowledge, it has been determined in numerous forums that what you are seeing is a generic Windows Mobile setting. You need it to switch between 1900/2100, but 850 is not actually supported by the X1i, even though it appears as part of the selection.
See: http://www.xperiax1.net/forum/xperia-x1/977-x1i-3g-umts-bands.html
Thanks.. anyone else?
Click to expand...
Click to collapse
OK sorry, I was not aware of this. Mobile operators tend to use two frequencies paired in Hungary (900+1800), maybe it's not so in other countries. But that still leaves the 850 MHz question in the X1i open.

Hey guys, I'm an X1i user in Canada faced by this same problem. I am also truly hoping for the possibility to unlock UMTS 850mhz on the X1i via a radio ROM flash from the X1a. I've heard that users of the Touch Diamond/Pro/HD are in a similar situation, but there has been no success yet.
Basically, the X1i DOES support 850mhz on the GSM band, however this will only get you EDGE or GPRS speeds. The X1i does NOT have support for the 3G (UMTS) band on 850mhz. Therefore, it only really half supports our networks over here.
Some users in the USA are lucky as they are in a 1900mhz UMTS zone, and since the X1i does support that 3G/HSDPA band, they are able to get 3G speeds. Problem is for me, 850mhz is predominant in my area, so my phone will always prefer to hop on that frequency, thereby eliminating my chances of connecting to 1900mhz and getting 3G.
Another possibility would be to force the phone to look for and use 1900mhz, even if the 850mhz towers were stronger. I think the possibility of this happening is less than flashing a new ROM to the X1i radio. The latter depends on whether or not the radio hardware can support different bands by a simple firmware change. I wouldn't hold my breath on this either, as I'm sure the two distinctions are made for a reason.
Anyways, I would LOVE to see it, so I can get 3G speeds up here, burn thru my data faster, and pay more money to the ONE GSM provider in Canada *bah*
Post any news in this thread if you hear of it!

The X1a
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well the x1a does support vga video recording, just thought you would like to know that... besides consider which you would be using more video, or internet?

Yes but the VGA video is only 10 fps.
Both options suck, which is why I hate that SE is putting us to this decision.
Hopefully there is a hack to overcome the 850 prob. My question is only whether such a hack is even possible.
Thanks.

Uhh that sucks
Ok yeah you are definitly correct it is only about 10fpm... is this because of broadcomm patents?

From what I gather, yes.

It has pretty much been answered here; however, I can tell you beyond the shadow of a doubt... The X1i will absolutely not support UMTS Band V (or UMTS850). This is a hardware limitation of that model.

Innoman -- I appreciate your response, and your level of certainty. I am aware that what you say seems to be the consensus.
Can you substantiate your statement in any way? Link to a schematic or paper showing that this is in fact a hardware limitation? Basically, can you please somehow back up what you are saying? Or is this an educated guess?
And assuming you are able to demonstrate this definitively, then next question arises: can the hardware in question be easily swapped?
My fear is that too many people will accept this important limitation without stopping to thoroughly question or understand it. So if you can prove your stance, please do -- and let this thread serve as the definitive answer to this question. (A question which I believe may have only been met with speculation thus far.) Don't forget, in terms of manufacturing, it is cheaper (and very common) to give sibling devices identical hardware, and control features in software. I have not been shown a document explicitly describing radio hardware differences between X1a and X1i -- I have only seen descriptions of differences in how the hardware functions, which could mean anything. (The video, of course, is a different issue). Maybe you can show me a document identifying the radio hardware in X1a and X1i, demonstrating that there is in fact a difference.
Thanks!

poorangus said:
Can you substantiate your statement in any way? Link to a schematic or paper showing that this is in fact a hardware limitation? Basically, can you please somehow back up what you are saying? Or is this an educated guess?
Thanks!
Click to expand...
Click to collapse
The only way to achieve the level of certainty you are after is a hardware blueprint from either SE or HTC. Since neither of these organisations will publish this, your best bet is to find the FCC report on the X1i - this may list the actual hardware frequencies.
The Qualcomm Court-ordered permanent injunction is a fact (Case SACV 05-467 JVS RNB 31-12-2007 United States District Court District of California) - you can easily download the Court decision in PDF format. You will also note from this that any Qualcomm "workaround" is also subject to on-going Court examination and determinations.
Since then, HTC have deliberately crippled all their devices to ensure that the 850Mhz UMTS frequency is not available. Both HTC and SE will not state whether this is a hardware or firmware issue. My educated guess is that it is a hardware action as the 850Mhz frequency is still present in the firmware (in the Registry) but does not work. You will also note that the X1a is released well after the X1i - again, my educated guess is that this sequence has been done to test the market popularity of the X1 as against the amount of royalties payable to Broadcomm if the X1a is released in the US.
The Court injunction is only on devices actually sold in the US, but since the US is the main market for 850Mhz devices, countries like South Africa, South America and Australia also miss out.
The release of the X1a in the US and elsewhere, which includes the 850Mhz working frequency, will require Qualcomm to pay royalties to Broadcomm on any devices actually sold in the US. I cannot say whether devices privately imported into the US from elsewhere (say the UK) will be subject to US Customs action - I don't know.
The video fps is also crippled for the same reasons.
If you have flashed the Hard SPL on your X1i, I suggest you try flashing one of Jack Leung's ROM's to test the 850Mhz frequency. This should tell you definitively if it a hardware or firmware issue. (You can then always reflash your existing ROM if you have a copy of it).
The core problem is down to Qualcomm, not SE or HTC. Both of these latter organisations have done whatever they believe they need to do to minimise the impact of Qualcomm's convicted theft. SE UK repeat the line that there is NO X1i, X1 a etc - only an X1 (yes, I have chased this question down to that level). Do I believe them ? NO. I'm in Aus, with an X1 on order from a UK retailer that I am assured has a working 850Mhz frequency ... but if it doesn't, it goes back for a refund.

What is it about Jack Leung's ROM that would make it possible to test for 850? It is "Based on UK official rom (WWE)," so wouldn't it be subject to the same restrictions? (he doesn't claim to have affected frequency availability).
That FCC Report is a bear.
Also, was the crippling of the video a direct action, or a natural consequence of using the different chip (or both)?

@poorangus
"What is it about Jack Leung's ROM that would make it possible to test for 850? It is "Based on UK official rom (WWE)," so wouldn't it be subject to the same restrictions? (he doesn't claim to have affected frequency availability)."
You don't seem to get it - the 850Mhz restriction is limited to sales in the US (do try and read the US Court decision). So the UMTS frequencies for the UK X1 are not limited by law (this frequency is not used in the UK, but not because of the Court decision, so the ROM doesn't turn it off). Therefore if you try Jack's ROM and you still can't access 850Mhz, it is a hardware restriction in your device, not a firmware restriction.
Which is what you want to know. If you demonstrate to your satisfaction that it is hardware, no firmware trick can help.
"That FCC Report is a bear." I'm afraid that's your problem. Qualcomm has removed all hardware specs for the MSMxxx series from their website about 11 months ago.
"Also, was the crippling of the video a direct action, or a natural consequence of using the different chip (or both)?" See the above answer. You will not find a definitive hardware answer to this because Qualcomm will NOT publish it, OK?
Last time, I repeat that Qualcomm is the problem here, not SE or HTC or this sub-forum.

The most interesting aspect of this post has been observing how confrontational everybody (except scar45) feels they need to be in their responses, whether they have anything of substance to add or not. I will not take issue with this fact, preferring instead to sit back and let you continue to look cool or knowledgeable in front of the other forum members, or whatever this nasty approach to conversation currently achieves. It's not amusing, but as I say, it is interesting, so carry on.
Of course, you're only winning the favor of the ignorant, as intellectuals can see right through that aggression to the insecurity and ignorance that drive it. When you unnecessarily phrase your responses as attacks, intellectuals see an ignorant person trying really hard to look smart, and you can imagine how pathetic this winds up appearing after 6 paragraphs. Remember, the record of this conversation will likely outlive you, and future generations will judge you based on it. Do you really want them to look back and see what a sad little man you were? No? Then be nice. Try different ways of explaining things. We are here to promote learning, not to detract people from it.
Getting back to the issue, the obvious flaw in your Jack Leung's ROM logic is that phones shipping with UK official ROM specifically claim to not support 850. So installing this ROM to find that 850 still doesn't work, gives us no new information (since we still don't know if it's being blocked at some software level). And since my X1i already shipped with the UK official ROM, this is sure to be the result.
Plus, your assertion that "this frequency is not used in the UK, but not because of the Court decision, so the ROM doesn't turn it off" is pure speculation and thus equally useless (mis)information.
Lastly, we get it, Qualcomm is the problem. That is very insightful of you to point out, and we all now understand that you are familiar with the court decision, and we are very proud of you. Unfortunately, this is unrelated to the question at hand.
If anyone has anything useful to contribute, please speak up.. maybe someone managed to grab Qualcomm's MSMxxx specs before they were removed? Or maybe someone is familiar with devices using the same chip as the X1a and could comment on the video capture capabilities of these devices, possibly helping us to better understand the implementation of the X1a's restrictions. In any event, we need a better understanding of the radio hardware in X1a and X1i, so let's start piecing it together.
The quest for certainty continues..

850 MHZ HSDPA in Panama
Ok, so I got my SE X1 a few days ago and it's been running on edge most of the time until about 2 days ago, after rebooting the phone it switched to the 3G network, the "E" became an "H" and i could notice the speed increase. Panama uses 850 Mhz band.

rpereira - thanks for the post. This means you have the X1a model (a = Americas). The other distinguishing characteristic of this phone is that it will only shoot VGA video at 10fps. We are trying to determine whether the X1i model (i = International) may be coerced into supporting 850MHz, like your device does.

Poorangus, you're absolutely right. After a second look to my box, it's clearly labled as X1a. Thanks for helping with the clarification .

i have an x1i running touch it xperience pb1 rom. Im in los angeles california and my data icon is H.
dont know if this helps, just thought i'd share.

Bruce bruce - this is also my situation. Fortunately, we are able to use 1900MHz. But I took my X1i for a drive up the coast yesterday, and it dropped to EDGE at least twice. No way of knowing whether 850MHz availability would have affected this.

Related

[Q] Possible to use HTC Dream with UMTS Band VI?

Hi all,
Brand new owner of a T-mobile G1 here, got a possibly low level question. I will be living in an area with only UMTS band VI coverage for the next 4-6 months. I see that band VI is a subset of the frequencies used in band V. I have seen a couple of posts around the web suggesting that some band V phones can be used on band VI. I assume it has something to do with code in the radio stack or somewhere in the OS? I am working on flashing Cyanomod 6.1.0-RC1-DS onto my Dream tonight/tomorrow (so I don't know yet if it will just work out of box haha). Anyone have any advice/thoughts? I apologize if this has been asked/answered before - I have done a lot of searching/reading and haven't been able to figure out the answer. Thanks in advance!
-David
Reference links <er, um, apparently i can't post outside links here yet as a new user so i'll replace them with instructions for making google give you the link as the first hit >
UMTS frequencies -- google "umts frequency bands"
video of 3G iPad supposedly working on band VI -- google "ipad foma 800Mhz"
discussion of iPhone4 and band VI -- google "iPhone 4 frequency changes"
(also posted at cyanogenmod's general HTC Magic forums under the title possible-to-use-htc-dream-with-umts-band-vi )

Could 4.3 code for the radio be causing physical hardware failure?

I just replied to a question in the development thread where an N4 user, running stock 4.3 suddenly lost connectivity to his 5ghz router band, nothing changed on his phone but suddenly he loses connectivity to 5ghz band?
Of course this is a well known issue, impacting hundreds of users globally since the 4.3 update, and it got me thinking that just maybe the actual code written for the Wi-Fi radio drivers in 4.3 was overly aggressive in terms of the capabilities of the radio hardware in the N4 and actually physically damaged the hardware? Code can break hardware, we all know of devices that have been permanently bricked and became coasters - all because of bad code or a flash that went wrong.
What if the radio code written in 4.3 was to maximize signal strength to remedy the complaints of poor/slow Wi-Fi on many 4.2 devices, but was too aggressive for the radio hardware in our N4's causing it to basically overload and physically die? I've read of people who had no issues with their 5ghz channel (like me) then after updating to 4.3 completely lost 5ghz connectivity, and even after downgrading to factory 4.2 stock firmware STILL had no 5ghz connectivity. In my case after downgrading to 4.2 i still had no connectivity to both of my dual band Netgear routers, nor any other 5ghz band router I tried, complete 5ghz failure - downgrading to the same 4.2 firmware that had worked flawlessly before updating to 4.3! If it was just software then downgrading to the previous 4.2 firmware should have instantly resolved the 5ghz connectivity, right? If it worked without issue before then it should work without issue again. Except for many it simply remained broken, so it stands to reason that something else changed - i.e. the physical hardware was damaged.
Maybe that's why Google quietly shot out 4 different versions of 4.3 in an attempt to hide the fact that the radio code was too aggressive for some phones hardware? They perhaps toned down the radio code's aggressive push of the hardware, which might explain why some people don't have the issue, but it was already too late for phones with lower hardware tolerances and the damage was permanent.
I'm getting a replacement device from Google tomorrow and if the 5ghz band works out of the box on the stock 4.3 firmware, I'm highly likely to immediately downgrade to 4.2 stock as I have a strong feeling that its just a matterof time before i once again lose 5ghz connectivity just like the person i mentioned at the beginning of this post.
I suspect Kit Kat to use the same drivers as 4.3 so I'm staying clear of new builds until V5.0.
Of course if people regain 5ghz connectivity on Kit Kat I will stand corrected, but I'm willing to bet they don't - if functionality that worked fine on 4.2 can't be recovered by downgrading from 4.3, it's almost certainly damaged radio hardware, and no new versions can fix that.

Scary but probably unlikely I'm sure google knows the hardware limits of the devices and tests before it releases it. I mean google is generally try to play it safe then sorry like how high they set the CPU voltages.
Sent from my Nexus 4 using xda app-developers app

THEBANDIT420 said:
Scary but probably unlikely I'm sure google knows the hardware limits of the devices and tests before it releases it. I mean google is generally try to play it safe then sorry like how high they set the CPU voltages.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Google releases their ROM's for numerous phone manufacturers, remember that ICS was the first android version that was cross compatible across all phones and tablets, the idea that it was easy to mass implement.
Consider the price of the N4 - $250 for 16gb model, about 40% of the price of a Samsung GS4! And the old saying that you get what you pay for. Junky screen compared to the SGS4 and other top price phones. Crap audio hardware compared to the fantastic sound chips Samsung uses. And most likely many other corners were cut to be able to release a 'flagship' device for less than half the price of the next major Android competitor (SGS4). It's straight forward economics, you get what you pay for. And I don't think Google realized that the tolerance levels of the N4's radio hardware were as low as I think they actually are, which is why they have been unable to resolve the issue in 4 quickly released 4.3 builds! I think they knew that the first release boosted signal strength in most other phones but didn't expect it to actually exceed the tolerances of lower end components that had to be used in the N4 which packs in all the top features of a high end phone at half the price!
I would never buy an LG flat screen TV, I'd always buy the Samsung simply because it's better quality in every way. I'm not sure why my brain didn't tell me this when I bought the N4. It was too good to be true at less than $250 for the latest Android phone? I think it was too good to be true!!
Let's watch Kit Kat roll out and watch these forums fill with p!seed people who still don't have reliable connectivity, and never will because their phone is physically broken.
Again, the acid test is to downgrade to say 4.1.2 and see if your 5ghz band works and your 2.4ghz speed flies, because it did when the phone was released back in December 2012 when it ran 4.1.1 or 4.1.2. I'm betting it won't work like it did and you still can't connect with the speed and reliability you once had. And if you can't get 5ghz connectivity on 4.3 you won't ever get it again because the hardware is cooked.

Globespy said:
Too long to quote.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Globespy said:
to long to quote
Click to expand...
Click to collapse
You don't buy lg TVs yet you bought a phone made by lg......
You bought the n4 but yet to YOU the s4 is WAY superior to it.....
Then I guess you know what you need to do then.....
Smh
Sent from my Nexus 4 using XDA Premium 4 mobile app

Highly doubtful that the radio firmware is causing hardware failure. As for your example usually a phone bricks because something went wrong with the flash or an incorrect file was flashed and the file system is no longer accessible hence a black screen with no boot... or worse.. the the hardware its self isn't actually damaged.
Sent from my Nexus 4 using xda app-developers app
---------- Post added at 02:53 PM ---------- Previous post was at 02:49 PM ----------
PJcastaldo said:
Highly doubtful that the radio firmware is causing hardware failure. As for your example usually a phone bricks because something went wrong with the flash or an incorrect file was flashed and the file system is no longer accessible hence a black screen with no boot... or worse.. the the hardware its self isn't actually damaged.
And I think and still think the N4 is a great device. Its fast looks nice. I personally think the screen looks nice.. and takes great pictures. So... maybe you should go buy a Samsung...
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Sent from my Nexus 4 using xda app-developers app

Globespy said:
[A lot of text]
Click to expand...
Click to collapse
A few things.
1. It seems you fail to grasp the purpose of the Nexus program.
2. I doubt Google would release software that damaged the hardware on the latest Nexus phone. That's kind of the point of the Nexus line; development. Not only for independent developers, but also internal Google ones. If this scenario were true, it definitely wouldn't be the Nexus phone that got broken, it would be a different one.
3. Assuming that the Nexus 4 is of lower quality than the GS4 since it is half the price, citing "simple economics" as a reason is just plain ignorant. There is a lot at play here, the two devices aren't in the same situation. Samsung is trying to make money off of the hardware so they mark it up. Google is just trying to showcase Android and offer an affordable top-end phone, so they don't mark up the price. Plus, they make their money off of their services.
4. Head over to this thread and start flashing different radios. I'll bet you 3,000 Internet Dollars that one of those radios fixes your WiFi issues.

Zenety said:
Click to expand...
Click to collapse
So childish. I bought the N4 for thethe same reason most others did - it was sold as a flagship product for what was literally a 'steal'. I haven't had this many issues with a phone since I ditched windows and moved to Android when eclair came out. But I suppose this makes me a Mac fanboy now? Lol.
I actually have never owned a Mac - PC guy.

Johmama said:
A few things.
1. It seems you fail to grasp the purpose of the Nexus program.
2. I doubt Google would release software that damaged the hardware on the latest Nexus phone. That's kind of the point of the Nexus line; development. Not only for independent developers, but also internal Google ones. If this scenario were true, it definitely wouldn't be thethe Nexus phone that got broken, it would be a different one.
3. Assuming that the Nexus 4 is of lower quality than the GS4 since it is half the price, citing "simple economics" as a reason is just plain ignorant. There is a lot at play here, the two devices aren't in the same situation. Samsung is trying to make money off of the hardware so they mark it up. Google is just trying to showcase Android and offer an affordable top-end phone, so they don't mark up the price. Plus, they make their money off of their services.
4. Head over to this thread and start flashing different radios. I'll bet you 3,000 Internet Dollars that one of those radios fixes your WiFi issues.
Click to expand...
Click to collapse
This thread was started because of an idea, based on a problem that I've struggled with as well as friends who ate all nexus guys.
It was not to bash LG or Google - I've been around on this forum a LONG time and have bought many nexus phones and tablets, and have enjoyed them!
The last Gnex was not priced at the level the N4 released at, yet at that time Android phones had been selling as much as iPhone, I believe around that time worldwide sales surpassed them for the first time. I understand that Google has a different business model focused on selling software (actually their main business is advertising) and want to market their products at a lower price point than hardware manufacturers like HTC, Samsung etc. But when you do this you still cut corners. I'm not alone here in saying that the screen and sound hardware used in the sgs4 is just better. There's no argument. I could have bought one but I'm a nexus guy and have been for a while. I bought a sgs4 for my Gf, she loves that TW nonsense. But maybe just maybe I have a point about hardware failure given that the majority can't resolve it even going back to software that worked before!
Anyway, your recommendation of flashing different kernels may work for a few, but from looking at the hundreds of posts on numerous different sites (most notably Google's N4 support forum), it's clear that the majority are still having issues, me included which is why I just ordered a replacement phone which success today.
You see, I actually like the device - with a few tweaks here and there it can be vastly improved. Screen gamma can be fixed, sound quality too with things like viper.
If a problem that didn't exist on a previous build still exists when going back to that exact build then you tell me why? Something else has changed.

Globespy said:
If a problem that didn't exist on a previous build still exists when going back to that exact build then you tell me why? Something else has changed.
Click to expand...
Click to collapse
When you say you go back to a previous version of Android, how do you do it? Do you have a flashable zip that you flash through recovery to return to the previous version, or do you grab the factory image from Google and run flash-all.bat?

Johmama said:
When you say you go back to a previous version of Android, how do you do it? Do you have a zip that you flash through recovery to return to the previous version, or do you grab the factory image from Google and run flash-all.bat?
Click to expand...
Click to collapse
I've tried EVERYTHING, but with regard to stock images I use ADB to flash the factory firmware, which as you should know basically nukes the phone and whatever used to be on it is gone forever and what you have left is a pure stock phone just as you would receive from Google if you bought a new one (like the new one I'll get from Google in a few hours, running JWR66Y), except my 5ghz radio doesn't work on any 5ghz router (both my wndr3700 & R6300, nor my neighbors dlink, Asus or Linksys routers) regardless of whether it's 4.1.1, 4.1.2, 4.2.x or 4.3.
In case you are serious about your bet earlier, I'd like to have a few more bills for fun money, so here is my money ($3K in 100's) - you can see my N4 with this actual thread showing (it's taken with a $5K camera so just zoom in) so you know I actually put my money where my mouth is.
And I know for 100% that in the case of my phone you are wrong because I've tried to fix this for over 3 months using every available option
So if you have time to sit on Skype today and you can walk me through the things you think will fix the 5ghz connectivity issues (kernels from faux, Franco, neo, semaphore, matrix and the list goes on), or maybe you think I haven't thought about build specific kernels like JSS, JWR or JLS?
I'm available all day my friend and as soon as you show me your cash then let's do it, but I can guarantee you will lose.
Heck, it's Friday so let's make it $5K (the extra bundle of $100 notes in the top of the pic) - I was thinking of new rims for my Porsche.
https://db.tt/dZz3Xpek
PS - I'm a 25 year veteran software developer for a prominent electronics firm - yeah I'm an old dude not a pot faced teen. I hope you have the chops to back up your words. And if you don't live in the US forget about it because I can't chase you down so easily when you don't pay up and vanish.

Globespy said:
I've tried EVERYTHING, but with regard to stock images I use ADB to flash the factory firmware, which as you should know basically nukes the phone and whatever used to be on it is gone forever and what you have left is a pure stock phone just as you would receive from Google if you bought a new one - except my 5ghz radio doesn't work on any 5ghz router (both my wndr3700 & R6300, nor my neighbors dlink, Asus or Linksys routers) regardless of whether it's 4.1.1, 4.1.2, 4.2.x or 4.3! The same one in getting in about 5 hours which I know will be JWR66Y.
In case you are serious about your bet earlier, I'd like to have a few more bills to for fun money, so here is my money ($3K in 100's) - you can see my N4 with this actual thread showing (it's taken with a $5K camera so just zoom in) so you know I actually put my money where my mouth is.
And I know for 100% that in the case of my phone you are wrong because I've tried to fix this for over 3 months using every available option
So if you have time to sit on Skype today and you can walk me through the things you think will fix the 5ghz connectivity issues (kernels from faux, Franco, neo, semaphore, matrix and the list goes on), or maybe you think I haven't thought about build specific kernels like JSS, JWR or JLS?
I'm available all day my friend and as soon as you show me your cash then let's do it, but I can guarantee you will lose.
Heck, it's Friday so let's make it $5K (the extra bundle of $100 notes in the top of the pic) - I was thinking of new rims for my Porsche.
https://db.tt/dZz3Xpek
PS - I'm a 25 year veteran software developer for a prominent electronics firm - yeah I'm an old dude not a pot faced teen. I hope you have the chops to back up your words. And if you don't live in the US forget about it because I can't chase you down so easily when you don't pay up and vanish.
Click to expand...
Click to collapse
Ok, you're starting to get a little antagonistic here. I'm just trying to help you. In my previous post I was trying to ascertain whether or not you're flashing a new radio. When you flash back to an older version of Android, if you don't flash a new radio, it won't help your situation. So unless you run either
Code:
fastboot flash radio radio.img
or a script that has that in it, such as the flash-all.bat that comes with the factory image, you aren't really doing anything to fix your WiFi issues.
Head on over to the thread I posted previously, here, try flashing a few different radios, starting with the most recent, and see if that helps. In the same thread, someone else also had issues with 5Ghz WiFi which got fixed by flashing one of the hybrid radios. Check this post for the problem, this post for a link to the originally-posted hybrid radio that fixed that guy's problem. You don't necessarily need to use that hybrid radio, but it helped that poster; scroll down the page to read his post after he reported back.

It's not a hardware issue. I've had the same problem with certain hybrid radios like 33/84 as mentioned by the poster above. I switched to 33/54 and it started working okay. It's some software issue. It was very annoying but fixable with the right radio.

lazer155 said:
It's not a hardware issue. I've had the same problem with certain hybrid radios like 33/84 as mentioned by the poster above. I switched to 33/54 and it started working okay. It's some software issue. It was very annoying but fixable with the right radio.
Click to expand...
Click to collapse
I get that these methods have worked for some but not all.
Let's get real basic.
If my phone had zero 5ghz issues on say 4.2.2 (with .54 radio), and then lost 5ghz connectivity on 4.3, then I flashed a completely clean version of that previous Google factory 4.2.2 firmware (which includes the .54 radio) and my phone now shows that indeed that old radio was installed, yet i still can't get 5ghz connectivity, then its not software only. Something changed that's not software, otherwise it should work. The phone has been returned to exactly the same way it was before the 4.3 update, every shred of the 4.3 build nuked as if it never existed. Yet part of it is not functional that used to be fine? There aren't too many things it could be - software or hardware. The software didn't change, I know that is factual as its the very same Google factory stock firmware. So......?????

Johmama said:
Ok, you're starting to get a little antagonistic here. I'm just trying to help you. In my previous post I was trying to ascertain whether or not you're flashing a new radio. When you flash back to an older version of Android, if you don't flash a new radio, it won't help your situation. So unless you run either
Code:
fastboot flash radio radio.img
or a script that has that in it, such as the flash-all.bat that comes with the factory image, you aren't really doing anything to fix your WiFi issues.
Head on over to the thread I posted previously, here, try flashing a few different radios, starting with the most recent, and see if that helps. In the same thread, someone else also had issues with 5Ghz WiFi which got fixed by flashing one of the hybrid radios. Check this post for the problem, this post for a link to the originally-posted hybrid radio that fixed that guy's problem. You don't necessarily need to use that hybrid radio, but it helped that poster; scroll down the page to read his post after he reported back.
Click to expand...
Click to collapse
PM sent. I'm just playing with you mate. I just got tired of people on the other end of an internet connection making bets they can't or won't follow through on. I am no novice and have been around long enough to know that my issue is not fixable. Trust me I've tried everything and then some. After trying all the potential fixes, I also bought a new router (the r6300), and tried 3-5 other routers and same problem every time. That's when I threw in the towel and sent for a replacement.
But thanks for your suggestions. I still think in my case it's hardware as I've ruled out software.

So I just had a knock on the front door and have a new N4!
However, it came pre-installed with JDQ39 (4.2.2), and it connected no problem with both my routers.
Now I have a dilemma. Firstly, if this is indeed a new phone (packaging all looks like it has never been opened), then why wouldn't it come with 4.3 installed? It's been out for over 3 months. So chances are whilst it's a new phone, it was manufactured before June of this year.
I'm terrified to update it to 4.3 in case the same thing happens again and my 5ghz connection vanishes. And it seems that most people think that Kit Kat will use the same drivers as JB 4.3, so even if I wait until Kit Kat (hopefully later this month) I could end up with the same borked 5ghz band.
Maybe 4.2.2 is as good as it gets for this phone.......what to do what to do....

Globespy said:
So I just had a knock on the front door and have a new N4!
However, it came pre-installed with JDQ39 (4.2.2), and it connected no problem with both my routers.
Now I have a dilemma. Firstly, if this is indeed a new phone (packaging all looks like it has never been opened), then why wouldn't it come with 4.3 installed? It's been out for over 3 months. So chances are whilst it's a new phone, it was manufactured before June of this year.
I'm terrified to update it to 4.3 in case the same thing happens again and my 5ghz connection vanishes. And it seems that most people think that Kit Kat will use the same drivers as JB 4.3, so even if I wait until Kit Kat (hopefully later this month) I could end up with the same borked 5ghz band.
Maybe 4.2.2 is as good as it gets for this phone.......what to do what to do....
Click to expand...
Click to collapse
That is weird that it came with 4.2.2, it's been quite some time since 4.3 came out.
Anyway, have you tried something like this? I know you said you tried a few different routers after upgrading to 4.3, but maybe you just needed to make your 5Ghz channel static. I don't know how true this is, but in that thread they said that the channel switching function isn't the greatest at detecting conflicts and switching over. Of course, even if that's true it could just be his router.
I'm sorry, I'm just having a tough time believing that it's a software issue that permanently removed 5Ghz WiFi capabilities on the hardware. I'm sure it's possible; I've seen stranger things. My gut just keeps telling me that it isn't the cause in this case. If you want to, maybe try manually flashing different radios through adb so you know nothing else is getting touched and see if one removes the 5Ghz capability; then flash back. Mainly the .84 that comes with 4.3. If not, I guess just stay on 4.2.2 until the issue is resolved. Maybe a new radio will come with KitKat that no-one will have an issue with.

Let's analyse;
first of all, I do not own the device. I have just sold my Note 2 and waiting for a good second hand Nexus 4 to show up in the local market. So I have no idea of this problem specifically. Just trying to help by looking into pieces.
- First, you should try to find anyone who used to lose 5GHz connection and than got it back. If there is a case then it is not related to hardware.
- Second you should be sure abour wiping every single code on your device. I don't know how thing are done in Nexus world but in Note 2, there is no certain ways of "deleting" every code. Maybe with a PIT file, not sure.
- I know that every chip or device or SoC manufacturer put their own non-software-controlled precautions to their "things". For example, you may choose to disable thermal throttiling of CPU by modifying a kernel but it will still cut the power once it reaches a pre-defined critical heat, regardless of the software. I am sure Wi-Fi antennas have this type of phsical/hardware protections.
- Besides; who would release a "voltage boosting software" without further testing it? (that could happen though, would not be the first time in the mobile devices' world)..
- What else, besides some un-down-gradeable driver or software, do you think, could possibly disable 5 GHz signal of antenna? Maybe it is about battery? I remember Nexus 4, first having USB OTG support but then removed both from advertisings and the sofware due to battery current limitin.. Maybe there is case like this?
- Any more investigable ideas?

Johmama said:
That is weird that it came with 4.2.2, it's been quite some time since 4.3 came out.
Anyway, have you tried something like this? I know you said you tried a few different routers after upgrading to 4.3, but maybe you just needed to make your 5Ghz channel static. I don't know how true this is, but in that thread they said that the channel switching function isn't the greatest at detecting conflicts and switching over. Of course, even if that's true it could just be his router.
I'm sorry, I'm just having a tough time believing that it's a software issue that permanently removed 5Ghz WiFi capabilities on the hardware. I'm sure it's possible; I've seen stranger things. My gut just keeps telling me that it isn't the cause in this case. If you want to, maybe try manually flashing different radios through adb so you know nothing else is getting touched and see if one removes the 5Ghz capability; then flash back. Mainly the .84 that comes with 4.3. If not, I guess just stay on 4.2.2 until the issue is resolved. Maybe a new radio will come with KitKat that no-one will have an issue with.
Click to expand...
Click to collapse
Thanks. Tried this with every channel on the 5ghz band, 2-digit and 3-digit channel.

_delice_doluca_ said:
Let's analyse;
first of all, I do not own the device. I have just sold my Note 2 and waiting for a good second hand Nexus 4 to show up in the local market. So I have no idea of this problem specifically. Just trying to help by looking into pieces.
- First, you should try to find anyone who used to lose 5GHz connection and than got it back. If there is a case then it is not related to hardware.
- Second you should be sure abour wiping every single code on your device. I don't know how thing are done in Nexus world but in Note 2, there is no certain ways of "deleting" every code. Maybe with a PIT file, not sure.
- I know that every chip or device or SoC manufacturer put their own non-software-controlled precautions to their "things". For example, you may choose to disable thermal throttiling of CPU by modifying a kernel but it will still cut the power once it reaches a pre-defined critical heat, regardless of the software. I am sure Wi-Fi antennas have this type of phsical/hardware protections.
- Besides; who would release a "voltage boosting software" without further testing it? (that could happen though, would not be the first time in the mobile devices' world)..
- What else, besides some un-down-gradeable driver or software, do you think, could possibly disable 5 GHz signal of antenna? Maybe it is about battery? I remember Nexus 4, first having USB OTG support but then removed both from advertisings and the sofware due to battery current limitin.. Maybe there is case like this?
- Any more investigable ideas?
Click to expand...
Click to collapse
Lots of great ideas. I've heard of only a few people who managed to get the 5ghz band back, although most still suffer from much slower speeds. If you run broad searches you will see that most people can't get it to work after they lose it, even downgrading the entire system to a build/radio that previously worked without issue - like me.
Using MrSkips toolkit it absolutely wipes any trace of the 4.3 ROM and any radio association, turning the phone back to how it was shipped (JDQ39). Yet still no luck. Not all hardware is created equally, just like certain CPU can overclock/undervolt the same amounts. Perhaps some radios have lower tolerances and die? It may sound strange, but not impossible.
I'm sticking with 4.2.2 until Kit Kat comes out and will wait a few weeks to see what happens. If people get 5ghz back then it's likely Google rewrote the radio code.

Regarding Z2 (standard), CustomROMs and frequencies

Hi,
since the sourcecode of the Z2 as well as the Pro-version have been released and Custom-ROMs are rolling in, what do you think are the chances of the standard-version getting attention by devs?
This forum seems to mostly focus on the Z2 Pro, not the standard.
The reason for me asking is that the Z2 Pro and Standard both have the Snapdragon 820 built in. Meaning both are capable of supporting the same range of frequencies. The Standard comes with a lot less frequencies (likely due to licensing).
As seen on this forum (http://forum.xda-developers.com/galaxy-s5/general/how-to-add-rf-lte-frequency-bands-to-t2886059), it should be possible to unlock the frequencies the Standard is "missing" when using CM, Remix etc. The result would be a phone with the best bang for the buck but also e.g. LTE/4G-Support for frequencies required in Europe (band 20 in Germany is pretty much mandatory...)
Cheers in advance for any answers

Iam interested too in unlocking band 20

Messing around with the actual radio of an Android phone is pretty tricky stuff, since the radio is a part of the phone that comes with it's own firmware. From what I understand this part is pretty much like an closed box with which the operating system communicates. So addings things that aren' t supposed to be there is both tricky and potentially dangerous.

BTW lover said:
Messing around with the actual radio of an Android phone is pretty tricky stuff, since the radio is a part of the phone that comes with it's own firmware. From what I understand this part is pretty much like an closed box with which the operating system communicates. So addings things that aren' t supposed to be there is both tricky and potentially dangerous.
Click to expand...
Click to collapse
Yeti, the CPU Supports a couple of frequencies that obviously were left out - most likely due to licensing. I can't realen think of anything that bad that could happen...

Enable Galileo use in the USA?

The best I've been able to surmise, is that every model of the X4 has Galileo disabled in the USA. It seems to be a geo-fence lockout, since people have reported that Galileo satellites become usable as they fly over the ocean to Europe. And the opposite occurs when returning to the USA. Motorola does not seem receptive my requests for enabling the feature, even though the FCC made a ruling in December 2018 that Galileo could now be utilized in the USA.
Anyone have any idea where the USA geo-fence for Galileo use is implemented? Would that be hard-wired on the Snapdragon chipset (I'm thinking unlikely), in the radio firmware, or in Android? If in radio or Android, I'm curious if any custom ROMs have this feature enabled?
Thanks for any help.

From another thread on another site, it seems like there is a blacklist setting per GNSS provider (GPS, Glonass, Galileo, Beidou, etc)
Example Link
data/data/com.android.providers.settings/databases/settings.db
It's not clear to me if this needs to be changed prior to ROM compile, or can be changed after the ROM is installed.
Curious if any ROM builders or rooted folks would be willing to test this to see if we can get Galileo enabled on the Moto X4 in the USA?

Can anyone confirm they can track Galileo satellites while in the USA with a rooted ROM? If so, which ROM?
You can use the gpstest app to confirm. Look for the dark blue EU flag.
You can read more in this article written by the app author.

ndoggac,
I have the exact same issue / questions you have. I'm in the US. 2020 model Moto G Power. "Supports" Galileo but none seen. So far my questions on Motorola forum have not been replied to.
Looks like we found the same blacklist/whitelist /geofencing info. It also looks like it might be as simple as a change in value in a system variable.
Hoping someone who routinely hacks on androids can offer how involved making a change like this might be.
Also wondering if anyone in the 48 states has any phone that's using Galileo and or Beidou?
I also found and installed "adb" which might be the right path to making the change, but I'm not wanting to brick my phone by screwing around too much!

General Variants of the 10 Pro, Clearing up some confusion.

There have been some confusing discussions all over the internet from this forum to OnePlus' forum on what ROM and hardware variant is used where. The simple answer is that Oneplus uses different hardware for different regions and the ROM is not necessarily tied to the hardware. OnePlus is using hardware variants that will work best outside of it's designed region and putting a generic ROM over it.
To clear things up I've made a cheat sheet with the main specifications between and across all the variants. I understand that it may not be complete, but it should help a lot of people understand what they are getting with each variant. I've also attached a PDF for easy copying and pasting.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

mine is a NE2210 , but it came preloaded with NE2211 , the hardware is same and it has Oxygen OS , which is good .. but so from now onwards i will be following guides meant for NE2211\?

Dr-Hack said:
mine is a NE2210 , but it came preloaded with NE2211 , the hardware is same and it has Oxygen OS , which is good .. but so from now onwards i will be following guides meant for NE2211\?
Click to expand...
Click to collapse
I'd treat it as such, really the biggest difference is the OS. Technically all the phones are the exact same hardware (except for Ram and storage sizes) and you should be able to cross flash if a full factory rom is released.

omega552003 said:
I'd treat it as such, really the biggest difference is the OS. Technically all the phones are the exact same hardware (except for Ram and storage sizes) and you should be able to cross flash if a full factory rom is released.
Click to expand...
Click to collapse
This is a fascinating and most helpful discussion - but I am CONFUSED. In your earlier post you wrote "The simple answer is that Oneplus uses different hardware for different regions and the ROM is not necessarily tied to the hardware." but now you say that all the phones are the exact same hardware? Which statement is correct?
Thanks for clearing up yet another confusion!

Does that mean that NE2210 has different physical hardware than NE2215, or is it just a software limitation? For e.g. if you flash NE2210 with NE2213 OOS rom the missing 4g/5g bands will not magically become enabled?

omega552003 said:
There have been some confusing discussions all over the internet from this forum to OnePlus' forum on what ROM and hardware variant is used where. The simple answer is that Oneplus uses different hardware for different regions and the ROM is not necessarily tied to the hardware. OnePlus is using hardware variants that will work best outside of it's designed region and putting a generic ROM over it.
To clear things up I've made a cheat sheet with the main specifications between and across all the variants. I understand that it may not be complete, but it should help a lot of people understand what they are getting with each variant. I've also attached a PDF for easy copying and pasting.
View attachment 5685035
Click to expand...
Click to collapse
This is such a useful document - thank you very much for this fine work! You must know these phones in great detail.
Can you please enlighten me... Is the OnePlus 10 Pro hardware the same for all versions, i.e. - if we flash an EU ROM onto the NE2210, will the phone have the same bands as an original NE2213 version? Will Android Auto work - even though it hasn't been preinstalled by the phone manufacturer? (This is the error message I get when I try to run Android Auto on the NE2210.)

ralphhayes said:
This is such a useful document - thank you very much for this fine work! You must know these phones in great detail.
Click to expand...
Click to collapse
I use a NE2215 daily, but other than that I just looked it up on the internet.
ralphhayes said:
Can you please enlighten me... Is the OnePlus 10 Pro hardware the same for all versions, i.e. - if we flash an EU ROM onto the NE2210, will the phone have the same bands as an original NE2213 version? Will Android Auto work - even though it hasn't been preinstalled by the phone manufacturer? (This is the error message I get when I try to run Android Auto on the NE2210.)
Click to expand...
Click to collapse
I think so due to the fact that people have said they have NE2213 ROM on an NE2210 phone. Also when I looked at the SIM slot of my NE2215 it has 2 sets of contacts even though it's sold as a single sim phone. Lastly I rooted my NE2215 phone by booting a rooted NE2213 boot.img.

Thank you for your comments. Fascinating comment, esp. about your discovery of the 2 sets of contacts!
I have never rooted or used Fastboot on a phone, but feel that I need to in this case. I got my NE2210 while in Europe (I upgraded from an 8T). Used it in various countries without real problems (except for phone and messaging apps - which I could not replace with the Google apps, and some Chinese bloatware, which I uninstalled or at least force-stopped). Next, I traveled to the U.S. That's when the problems began. The NE2210 would not connect to any Mobile Network (I am using Google Fi but also have an Asian SIM card - neither would connect.)
I love the camera and speed of the phone and even the Color O/S is fine.
I then realized that Android Auto does not work - "because it had not been pre-installed by the phone manufacturer."
Please let me ask you one more question: On the Internet, there are numerous instructions on how to flash the NE2113 ROM - have you seen step-by-step instructions that are complete and airtight (for a beginner)? I'll be happy to share my experiences once I have made them!
TY!

ralphhayes said:
Thank you for your comments. Fascinating comment, esp. about your discovery of the 2 sets of contacts!
I have never rooted or used Fastboot on a phone, but feel that I need to in this case. I got my NE2210 while in Europe (I upgraded from an 8T). Used it in various countries without real problems (except for phone and messaging apps - which I could not replace with the Google apps, and some Chinese bloatware, which I uninstalled or at least force-stopped). Next, I traveled to the U.S. That's when the problems began. The NE2210 would not connect to any Mobile Network (I am using Google Fi but also have an Asian SIM card - neither would connect.)
I love the camera and speed of the phone and even the Color O/S is fine.
I then realized that Android Auto does not work - "because it had not been pre-installed by the phone manufacturer."
Please let me ask you one more question: On the Internet, there are numerous instructions on how to flash the NE2113 ROM - have you seen step-by-step instructions that are complete and airtight (for a beginner)? I'll be happy to share my experiences once I have made them!
TY!
Click to expand...
Click to collapse
I have an NE2210 that I bought off Amazon and when it came in, it was flashed with Oxygen OS NE2215 ROM. I'm currently using it with Google Fi and seems to work great in my area so you should be able to get yours to work stateside. The only thing I'm not certain of yet is if 5g band 71 is activated since it's on a NE2215 ROM or if that band will not work at all due to hardware limitations. Earlier posts in this thread seem to allude to that it does work because the hardware is the same, however I've seen other threads that indicate the US version definitely has different hardware. I can tell you that my phone has indicated 5g before but that may only be the 41 band. I'm going to install signal spy to try and confirm if I'm ever on band 71.
Edit: Oh, and my Android auto does work. However, the seller indicated that the ne2215 ROM was flashed by OnePlus themselves. Not sure if that's true or not.

RS7JR said:
I have an NE2210 that I bought off Amazon and when it came in, it was flashed with Oxygen OS NE2215 ROM. I'm currently using it with Google Fi and seems to work great in my area so you should be able to get yours to work stateside. The only thing I'm not certain of yet is if 5g band 71 is activated since it's on a NE2215 ROM or if that band will not work at all due to hardware limitations. Earlier posts in this thread seem to allude to that it does work because the hardware is the same, however I've seen other threads that indicate the US version definitely has different hardware. I can tell you that my phone has indicated 5g before but that may only be the 41 band. I'm going to install signal spy to try and confirm if I'm ever on band 71.
Click to expand...
Click to collapse
Am actually wondering this myself. I've seen a few posts of NE2215 devices getting better signal when cross flashed with NE2213 because 2213 has a few more 5G Bands enabled.. I would definitely be interested in this if cross flashing could open up more bands... if the hardware truly is the same.

RS7JR said:
The only thing I'm not certain of yet is if 5g band 71 is activated since it's on a NE2215 ROM
Click to expand...
Click to collapse
It does, as T-Mobile uses B71 for NR 5G and the NE2215 is sold by them.

omega552003 said:
It does, as T-Mobile uses B71 for NR 5G and the NE2215 is sold by them.
Click to expand...
Click to collapse
But my variant is actually a NE2210 (Chinese) which has NE2215 ROM flashed to it (supposedly from factory). Are you saying that you have proof the hardware is the same between the two and by simply flashing the NE2215 ROM on a NE2210 device will activate the use of 5g band 71?

so NE2213 supports tmobile volte and wifi calling?

Prant said:
Am actually wondering this myself. I've seen a few posts of NE2215 devices getting better signal when cross flashed with NE2213 because 2213 has a few more 5G Bands enabled.. I would definitely be interested in this if cross flashing could open up more bands... if the hardware truly is the same.
Click to expand...
Click to collapse
So update: Over the weekend, I've noticed my phone on 5g three different times. All three times I was on band 41. Still no luck at catching it on 71. The theory of flashing ROMs to activate bands isn't looking good so far but I'm going to keep trying.

daviddem said:
so NE2213 supports tmobile volte and wifi calling?
Click to expand...
Click to collapse
I have both VoLTE and VoWiFi working on stock NE2215. I've heard NE2213 works just the same, but sometimes better due to having a couple extra 5G bands. But @RS7JR seems to be seeing something different with actual tests.

Prant said:
I have both VoLTE and VoWiFi working on stock NE2215. I've heard NE2213 works just the same, but sometimes better due to having a couple extra 5G bands. But @RS7JR seems to be seeing something different with actual tests.
Click to expand...
Click to collapse
I don't think my tests prove that VoLTE and VoWifi don't work. I don't have t-mobile but I do have Google Fi and my WiFi calling does work which I'm pretty sure is the same as t mobile VoWifi. Not sure about VoLTE though. The only thing my tests have proven so far is that flashing ROMs from other variants doesn't unlock the use of more frequency bands in the radio. And in my particular case, specifically 5g band 71. Keep in mind, I've only had 3 opportunities to test it so take my info with a grain of salt. I'll still be doing more testing for the next couple weeks.

I just got NE2213 in the US on Tmobile and volte, wifi calling and all bands are working

daviddem said:
I just got NE2213 in the US on Tmobile and volte, wifi calling and all bands are working
Click to expand...
Click to collapse
Is there any chance for you to try out any other carriers, Verizon or MVNOs like visible/us mobile?

jllll said:
Is there any chance for you to try out any other carriers, Verizon or MVNOs like visible/us mobile?
Click to expand...
Click to collapse
sorry i only have tmobile

From what I can tell, 5G is not working in Canada. I believe that, in order for 5G to work, the device has to be certified for use on Canadian carriers' 5G service, and that doesn't seem to be the case for the OnePlus 10 Pro. Otherwise, everything else seems to work perfectly. However, it's also my understanding that 5G connectivity did work on the OnePlus 9 (also the OnePlus8???), so not having it work on the OnePlus 10 Pro is very confusing. Personally, I don't care if I can't access 5G. It has no "REAL" benefit for me, so I can live with it. I'm just curious as to why the OP10P is blocked from 5G access.

Database Develop

welcome