Does the AT&T M8 have the same radio bands/frequencies as the developer edition?
As far as the specs listed, and as far as I know, yes.
Although some folks have found that the versions sometimes contain band support for bands not listed in a particular versions specs. So the longer answer, is that there may be some small hidden differences (additional support bands on one versus the other).
It might be more useful for you to describe your intent, what you are trying to accomplish etc.
For instance, if you have the necessary bands for your carrier on the Dev Edition, changing to AT&T won't change that.
But the band support is either identical or at the most, minor differences.
I have a gold AT&T M8... It's unlocked s-off, etc... (bought it off Swappa loaded with Dev edition, s-off/unlocked, etc)
My carrier is T-Mobile... currently I have it flashed with the Dev edition of Marshmallow... I THINK my radio's the MM edition... (H-boot shows the radio is listed as 1.29.214500021.24_2G/OS as 6.12.1540.4)
Just trying to make sure I'm running something that won't leave me hanging on radio's... I've dabbled with GPE and T-Mo roms... but wasn't sure if the Dev radio would try and support bands that the hardware won't actually support...
Is there a real way to verify the bands the hardware will support?
scifan said:
I have a gold AT&T M8... It's unlocked s-off, etc... (bought it off Swappa loaded with Dev edition, s-off/unlocked, etc)
My carrier is T-Mobile... currently I have it flashed with the Dev edition of Marshmallow... I THINK my radio's the MM edition... (H-boot shows the radio is listed as 1.29.214500021.24_2G/OS as 6.12.1540.4)
Just trying to make sure I'm running something that won't leave me hanging on radio's... I've dabbled with GPE and T-Mo roms... but wasn't sure if the Dev radio would try and support bands that the hardware won't actually support...
Is there a real way to verify the bands the hardware will support?
Click to expand...
Click to collapse
The hardware is identical between the T-Mob, AT&T, Dev Ed and most other M8 versions. Band support is determined by the radio baseband firmware.
That being said, you do indeed have the MM radio, and most likely the Dev Ed radio (can't seem to find that radio number, at the moment), which is designed to work on AT&T's network. That means on T-Mob, you will have 2G (voice and EDGE data), 3G 1900 MHz (Band 2) and LTE (AWS); but you will not have 3G (HSPA) where T-Mob is using the HSPA AWS band (3G Band 4). This may or may not be an issue depending on your location. From what I'm reading, T-Mob is in the process of shutting down 3G service on the AWS band anyway, and migrating all 3G service to 1900 MHz (HSPA Band 2), one market region at a time. So you may not need the 3G AWS band, anyway.
However, if you find you need 3G AWS band at your location, you may want to go the the MM T-Mob radio once that update rolls out. Another option (if you really need the 3G AWS band now) might be to roll back to T-Mob Lollipop firmware, but that may cause its own complications.
redpoint73 said:
The hardware is identical between the T-Mob, AT&T, Dev Ed and most other M8 versions. Band support is determined by the radio baseband firmware.
That being said, you do indeed have the MM radio, and most likely the Dev Ed radio (can't seem to find that radio number, at the moment), which is designed to work on AT&T's network. That means on T-Mob, you will have 2G (voice and EDGE data), 3G 1900 MHz (Band 2) and LTE (AWS); but you will not have 3G (HSPA) where T-Mob is using the HSPA AWS band (3G Band 4). This may or may not be an issue depending on your location. From what I'm reading, T-Mob is in the process of shutting down 3G service on the AWS band anyway, and migrating all 3G service to 1900 MHz (HSPA Band 2), one market region at a time. So you may not need the 3G AWS band, anyway.
However, if you find you need 3G AWS band at your location, you may want to go the the MM T-Mob radio once that update rolls out. Another option (if you really need the 3G AWS band now) might be to roll back to T-Mob Lollipop firmware, but that may cause its own complications.
Click to expand...
Click to collapse
The last time I ran a T-Mo radio on my M8 HSPA wouldn't work at all because even though they'd refarmed my area, it would try and run on frequencies my phone didn't have... (it was LTE or no data)
And I either was able to get a stable Bluetooth connection, or a stable cellular data connection... but I couldn't get both to be happy at the same time... (I found switching from WiFi to Cellular was problematic under some of the 4.x stock OS's... and then bluetooth was spotty under most of the stock 5.x rom's... and cellular switching wasn't consistent under ASOP...)
I don't know... I think at this point, I'm going to see what happens after the rest of the Sense MM releases come out... if I can't get something consistent, I'll probably work on selling this one and move to a new phone... it's nearly time anyway.
scifan said:
The last time I ran a T-Mo radio on my M8 HSPA wouldn't work at all because even though they'd refarmed my area, it would try and run on frequencies my phone didn't have... (it was LTE or no data)
Click to expand...
Click to collapse
I don't know what you mean that "it would try and run on frequencies my phone didn't have" as that really doesn't make sense (or I'm not properly understanding what you mean).
T-Mob radio is designed to run on their network, so 3G should work whether its refarmed (1900 Band 2) or not (AWS Band 4).
scifan said:
And I either was able to get a stable Bluetooth connection, or a stable cellular data connection... but I couldn't get both to be happy at the same time... (I found switching from WiFi to Cellular was problematic under some of the 4.x stock OS's... and then bluetooth was spotty under most of the stock 5.x rom's... and cellular switching wasn't consistent under ASOP...)
Click to expand...
Click to collapse
Hard to speculate what the issue there was, as I don't know the specifics of what ROM(s) you were on (version, stock, custom) as well as what firmware number. But what I normally would have recommended, is to baseline to full stock T-Mob using RUU, and go from there; to eliminate mismatches between ROM, firmware, etc.
But it sounds like you are past that point, and not necessarily looking for fixes for things that happened in the past.
redpoint73 said:
I don't know what you mean that "it would try and run on frequencies my phone didn't have" as that really doesn't make sense (or I'm not properly understanding what you mean).
T-Mob radio is designed to run on their network, so 3G should work whether its refarmed (1900 Band 2) or not (AWS Band 4).
Click to expand...
Click to collapse
I've read elsewhere that if your baseband/radio includes frequencies your phone actually doesn't have hardware to support, that you can get stuck where your device will try and utilize that frequency and not realize that it's failing to communicate... I don't know if this was the situation, but it was significantly impacting my cellular data experience...
redpoint73 said:
Hard to speculate what the issue there was, as I don't know the specifics of what ROM(s) you were on (version, stock, custom) as well as what firmware number. But what I normally would have recommended, is to baseline to full stock T-Mob using RUU, and go from there; to eliminate mismatches between ROM, firmware, etc.
But it sounds like you are past that point, and not necessarily looking for fixes for things that happened in the past.
Click to expand...
Click to collapse
When I originally moved to 4.4.x on T-Mobile, I RUU'd the phone... I want to say that I've had to do this once or twice when I soft bricked my phone in the past as well... I've made too many changes to speculate on one baseband/rom or another... I've flopped back and forth between being fully GPE and a combo of Sense Firmware and GPE rom...
At this point, I'm running the MM Dev firmware and rooted Dev Rom from This thread.
Btw, normally, the bluetooth issues I've experienced are pauses in music playback... with my current configuration sometimes I'll see bluetooth disconnect once after it initially connects.... Pandora controls work well. and everything else works as expected.
scifan said:
I've read elsewhere that if your baseband/radio includes frequencies your phone actually doesn't have hardware to support, that you can get stuck where your device will try and utilize that frequency and not realize that it's failing to communicate... I don't know if this was the situation, but it was significantly impacting my cellular data experience...
Click to expand...
Click to collapse
The only such instance I am aware of on the M8 that is similar to what you describe, is if you try to flash a "GSM" radio (basically any non-CDMA version) to one of the CDMA variants (Sprint, Verizon) which results in a radio brick. Meaning the phone doesn't work, but it breaks the radio. But this is an issue unique to Sprint, Verizon M8.
All other M8 versions (with the odd exceptions of the dual SIM, and M8 Eye - which are really different devices) are identical in hardware and the radios are interchangeable.
Even with the CDMA M8, from what I understand, the hardware is the same as the GSM versions. Its just the partitioning that is different that causes the radio brick.
redpoint73 said:
The only such instance I am aware of on the M8 that is similar to what you describe, is if you try to flash a "GSM" radio (basically any non-CDMA version) to one of the CDMA variants (Sprint, Verizon) which results in a radio brick. Meaning the phone doesn't work, but it breaks the radio. But this is an issue unique to Sprint, Verizon M8.
All other M8 versions (with the odd exceptions of the dual SIM, and M8 Eye - which are really different devices) are identical in hardware and the radios are interchangeable.
Even with the CDMA M8, from what I understand, the hardware is the same as the GSM versions. Its just the partitioning that is different that causes the radio brick.
Click to expand...
Click to collapse
I know I've flashed back and forth between T-Mobile, AT&T, GPE and Dev radio's without breaking things... it just seemed that some radio frequencies didn't work...
Actually the reason I got a att m8 off swappa was because of the increased amount of bands over the tmobile version
Holds all lte and hspa bands along with additional lte ones
Related
So I purchased a UK unlocked Touch Pro and had it shipped to the US. While I hope there will be an ATT radio rom flash in the future, I have a quick question for the veterans out there:
On the Touch Pro, under the Phone Band settings, you can select "GSM(1900+850)+UMTS(1900+850)"
When I do this all I receive is Edge on ATT, but aren't the UMTS bands correct already for ATT under this setting?
ajk1116 said:
So I purchased a UK unlocked Touch Pro and had it shipped to the US. While I hope there will be an ATT radio rom flash in the future, I have a quick question for the veterans out there:
On the Touch Pro, under the Phone Band settings, you can select "GSM(1900+850)+UMTS(1900+850)"
When I do this all I receive is Edge on ATT, but aren't the UMTS bands correct already for ATT under this setting?
Click to expand...
Click to collapse
There are several threads on this topic already...Here's one:
http://forum.xda-developers.com/showthread.php?t=410945
Thanks, I appreciate the reply, but I had read through that thread. I understand that the device is likely in need of a reprogrammed ROM to activate the hardware because at the end of the day it is not working. My question is specifically if the phone setting is allowing me to select the two ATT UMTS bands already why wouldn't I get 3G speed?
ajk1116 said:
Thanks, I appreciate the reply, but I had read through that thread. I understand that the device is likely in need of a reprogrammed ROM to activate the hardware because at the end of the day it is not working. My question is specifically if the phone setting is allowing me to select the two ATT UMTS bands already why wouldn't I get 3G speed?
Click to expand...
Click to collapse
I have the UK version of the phone as well and I have the same issue. I have selected the right bands for both UMTS and GSM but all I get is EDGE. The reason for this is either a hardware limitation (no radio antenna to support 850/1900 UMTS bands (let's hope not) or the factory installed radio firmware does not include those bands or all those da#@ iPhone 3G users are hogging all the UMTS bandwidth . Hopefully all we need is to flash a new radio or ROM to unlock these bands. Just because you can select this band in phone settings does not mean the radio or hardware support it.
I guess I am crossing my fingers along with you . Thanks!
See my thread
http://forum.xda-developers.com/showthread.php?t=418000
Even though this is for T-Mobile im sure if tmo gets unlocked att will to. Watch that and post there if someone cracks it they will post on that thread.
I have a question for the guys only getting EDGE when they have the correct bands set.......do you have a 3G enabled SIM card? (aka a USIM, some networks require you use one for the 3G to be utilised correctly).
Hi, in answer to your question, yes I have a 3G compatible SIM. I literally plucked it out of my TyTN 2/ TILT and put it in to the Touch Pro. The Touch Pro automatically found the ATT network, and when I went in to check bands I realized that there was an option for the US UMTS bands. I am guessing that others have been right when they have stated that just because there is a menu option it doesn't mean the radios are properly enabled.
ajk1116 said:
Hi, in answer to your question, yes I have a 3G compatible SIM. I literally plucked it out of my TyTN 2/ TILT and put it in to the Touch Pro. The Touch Pro automatically found the ATT network, and when I went in to check bands I realized that there was an option for the US UMTS bands. I am guessing that others have been right when they have stated that just because there is a menu option it doesn't mean the radios are properly enabled.
Click to expand...
Click to collapse
So currently you are using a HTC branded Raphael? Could you post your ROM/Radio details? (device info in settings/system) Also your ROM build (settings/system->about)?
mrvanx said:
So currently you are using a HTC branded Raphael? Could you post your ROM/Radio details? (device info in settings/system) Also your ROM build (settings/system->about)?
Click to expand...
Click to collapse
I have a 3G enabled SIM, been using it with the Kaiser for the past year with good 3G reception. I now have the HTC branded Raph (UK version) with no 3G reception, only EDGE. Here's the info on my ROM/Radio:
ROM: 1.90.405.1 WWE (8/1/08)
Build: 19965.1.2.3
Radio: 1.02.25.19
OK so it seems the only radios actually in these Raphaels at the moment are all 1.02.25.19, once we have a decent way to flash a different radio stack to it we can see if it makes any difference both in the bands available and some of the reception issues we are seeing so far.
I'm not an expert in this area at all, far from it, but but was reading Black's post about his AT&T model and he has 1.01.25.16. Is this what you're going to flash it to once the HardSPL is completed given that you know his radio supports AT&T 3G?
I'm trying to keep up...
Has anybody heard an ETA for Hardspl? I know they where testing it. But any rumors on a timeframe?
My new UK Touch Pro (radio ver 1.02.25.19) is exhibiting this same behavior on AT&T... I have tried all combinations of those dropdowns under phone options without any luck. It does seem very strange that HTC put the US 3G bands in the band dropdown, but included radio software that doesn't support it...
... Why would HTC bother removing hardware supported bands in the software?
shaunco said:
My new UK Touch Pro (radio ver 1.02.25.19) is exhibiting this same behavior on AT&T... I have tried all combinations of those dropdowns under phone options without any luck. It does seem very strange that HTC put the US 3G bands in the band dropdown, but included radio software that doesn't support it...
... Why would HTC bother removing hardware supported bands in the software?
Click to expand...
Click to collapse
Because they couldn't get it working well enough in time for the release date, I guess. Similar to what appears to have been the case with the Diamond. The US isn't their main concern at the moment, so delaying a US-compatible version for now in or der to get it to the rest of the world on time.
Either that or it's deliberate act to slow down the grey imports until they do a proper US release in hand with the local carriers.
If AT&T doesn't want to subsidize the Pro/Diamond, HTC doesn't really have to worry about putting in 1900 support. And honestly, AT&T is too busy with the iPhone 3G to care about HTC.
On the other hand, I'm sure HTC is very interested in getting in on T-mo 3G (1700/2100). By downplaying 1900 (which is being eaten up by the iPhone, anyway), HTC can gear up for the fresh 1700/2100 band. Paired with Android, HTC could potentially gain a big chunk of US 3G networks.
I'm a touch pro user in Canada on the Rogers network. I too hope that HTC releases a radio that allows 3g network access. I don't think its a hardware limitation because it wouldn't really make sense to make two versions of the same phone just to disable parts of the radio.
I disagree with the statement that AT&T is too busy with the iPhone 3G to care about the Touch Pro. The fact is that the target audience for the two phones are entirely different and that a considerable amount of AT&T corporate customers still require their employees to use PPC based phones (even if the iPhone 3G supports email push).
Corporate standards don't usually move as quickly as they should, so of course AT&T is interested in extracting more money from customers that purchased a Tilt over the past 8 months and want to upgrade, but are not allowed to use an iPhone.
If HTC removed support because they were unable to get the software functioning properly, I can live with that. EDGE for a few months while HTC readies a new radio software package is fine... EDGE while HTC readies new hardware is not.
fhsieh said:
If AT&T doesn't want to subsidize the Pro/Diamond, HTC doesn't really have to worry about putting in 1900 support. And honestly, AT&T is too busy with the iPhone 3G to care about HTC.
Click to expand...
Click to collapse
If AT&T weren't interesting in pushing the Touch Pro, HTC wouldn't have went to the trouble and expense of making a specific hardware revision (PTT button) for them. That's not something HTC are gonna do just for the hell of it on a quiet Sunday afternoon.
Maybe I didn't read the thread well enough but did you try and flash the AT&T ROM that was posted? Maybe that might work!
Has anyone tried using one of the white unlocked Lumia 920 from Clove (I guess the ones from Expansys are the same) on an LTE network?
Specifically, do you have the "4G" option in the "highest connection speed" settings?
In my case, although I am using an LTE SIM with an LTE network on a supported band, I only have "2G" and "3G" options in the Highest Connection Speed settings. So normally it is only connecting over HSPA. Through playing around a lot with scanning LTE bands with the Field Test tool (##3282#), I can sometimes get the device to connect to LTE, after which it works perfectly on LTE until reboot. But it's not really a long-term solution.
The default firmware on my device is country variant "CV GB SW Variant ID 276 v03" which (apart from the version number) seems to be the same firmware as that sold by Orange / T-Mobile in the UK (i.e. for 3G networks).
I was thinking about trying to flash the EE firmware, but concerned this could create other issues (such as end up locking the phone to EE, or to certain LTE bands, or something...). Any thoughts appreciated.
You don't mention where you are, but that might help respondents.
As you may know, the LTE bands are different between the NA and Europe. The LTE Bands listed on the international version are 800/900/1800/2100/2600 while the NA(Rogers & AT&T) version has 700/850/1700/1900/2100.
Are you sure you are connecting to the LTE bands? Do you have an LTE SIM installed?
tomdjp said:
Has anyone tried using one of the white unlocked Lumia 920 from Clove (I guess the ones from Expansys are the same) on an LTE network?
Specifically, do you have the "4G" option in the "highest connection speed" settings?
In my case, although I am using an LTE SIM with an LTE network on a supported band, I only have "2G" and "3G" options in the Highest Connection Speed settings. So normally it is only connecting over HSPA. Through playing around a lot with scanning LTE bands with the Field Test tool (##3282#), I can sometimes get the device to connect to LTE, after which it works perfectly on LTE until reboot. But it's not really a long-term solution.
The default firmware on my device is country variant "CV GB SW Variant ID 276 v03" which (apart from the version number) seems to be the same firmware as that sold by Orange / T-Mobile in the UK (i.e. for 3G networks).
I was thinking about trying to flash the EE firmware, but concerned this could create other issues (such as end up locking the phone to EE, or to certain LTE bands, or something...). Any thoughts appreciated.
Click to expand...
Click to collapse
Have a look at this offivial Blog post from Nokia.
http://goo.gl/L2eiy
They basically saying that even-thought the new Lumias are LTE ready they will required a software update to turn LTE ON.
The information on that is very limited as Nokia didn't specify ANY details on how they will push this OTA.
What happens if you have an unlock device and use it in a different country of its origins? How they will push the update under what criteria?
Is the update is driven by the SIM ID? They will update the OS and turn ON LTE depending the SIM region or the device IMEI region?? Nobody knows...
Even worst there is a rumor that the latest Snapdragon S4 is supporting all 9 LTE bands at ONCE and the software just enable the appropriate ones, its programmable from the firmware. If this is true, then Nokia is committing a suicide here, they can simply program WP8 to recognize the SIM ID and turn ON/OFF LTE Bands depending the Network. Going with OTAs across different devices and regions will be a mess.
nMIK-3 said:
Have a look at this offivial Blog post from Nokia.
http://goo.gl/L2eiy
They basically saying that even-thought the new Lumias are LTE ready they will required a software update to turn LTE ON.
The information on that is very limited as Nokia didn't specify ANY details on how they will push this OTA.
What happens if you have an unlock device and use it in a different country of its origins? How they will push the update under what criteria?
Is the update is driven by the SIM ID? They will update the OS and turn ON LTE depending the SIM region or the device IMEI region?? Nobody knows...
Even worst there is a rumor that the latest Snapdragon S4 is supporting all 9 LTE bands at ONCE and the software just enable the appropriate ones, its programmable from the firmware. If this is true, then Nokia is committing a suicide here, they can simply program WP8 to recognize the SIM ID and turn ON/OFF LTE Bands depending the Network. Going with OTAs across different devices and regions will be a mess.
Click to expand...
Click to collapse
There are international versions that HAVE ALL 9 LTE bands enabled and also petaband 3G.
For example in Germany:
http://www.nokia.com/de-de/produkte/smartphones-und-handys/lumia920/technische-daten/ (expand where it says "Basisdaten")
or in Singapore:
http://www.nokia.com/sg-en/products/phone/lumia920/specifications/ (expand where it says "Hardware")
or also in Switzerland:
http://www.nokia.com/ch-de/produkte/smartphones-und-handys/lumia920/technische-daten/ (expand where it says "Basisdaten")
I think there might be a good chance that you can unlock those extra bands on international versions (RM-821) that have them disabled by flashing a different firmware version. However this is just me thinking out loud so please don't blame me if it doesn't work or if it breaks your phone!
However I would strong discourage you from flashing an RM-821 firmware to an RM-820 (North American version) as I know that sb around here almost broke his phone by doing so.
Hi all
Thanks for your replies so far.
Right now I am using the phone in Japan, where there are three carriers with Band 1 (2100 MHz) LTE networks. I only tried one carrier so far, and yes it is an LTE SIM. As mentioned, I can actually connect to LTE and have used it for several hours, it's just necessary to use an unreliable trick (with ##3282#) to get the phone to see the LTE network. This seems related to the fact there is no 4G option in my highest connection settings.
Thanks for the heads-up on the OTA updates, agreed it's not clear how this will work at all...
Regarding the LTE band support, personally (although it's just my intuition) I think the lists of 9 LTE supported bands on those regional Nokia websites are probably in error (it wouldn't be the first time). Normally the most reliable source in Nokia's website is Nokia Developers, which clearly shows five bands for global RM-821 (1, 3, 7, 8, 20) and four bands for AT&T RM-820 (2, 4, 5, 17).
While the Snapdragon baseband may be able to support all 9 bands, the most difficult part of the design is the RF - filters, amplifiers, etc. So I imagine different RF chains are used in the two variants to support these specific bands.
Again, if anyone has the unlocked RM-821 and tried with an LTE SIM, if you could confirm if the 4G setting is available in highest connection settings, it would be much appreciated.
karlmueller said:
There are international versions that HAVE ALL 9 LTE bands enabled and also petaband 3G.
For example in Germany:
http://www.nokia.com/de-de/produkte/smartphones-und-handys/lumia920/technische-daten/ (expand where it says "Basisdaten")
or in Singapore:
http://www.nokia.com/sg-en/products/phone/lumia920/specifications/ (expand where it says "Hardware")
or also in Switzerland:
http://www.nokia.com/ch-de/produkte/smartphones-und-handys/lumia920/technische-daten/ (expand where it says "Basisdaten")
I think there might be a good chance that you can unlock those extra bands on international versions (RM-821) that have them disabled by flashing a different firmware version. However this is just me thinking out loud so please don't blame me if it doesn't work or if it breaks your phone!
However I would strong discourage you from flashing an RM-821 firmware to an RM-820 (North American version) as I know that sb around here almost broke his phone by doing so.
Click to expand...
Click to collapse
I thought the same thing on PentaBand 3G and 9 Bands LTE, however in another discussion we verified (at least for the German model) that even thought the Nokia German website states PentaBand 3G and 9 Bands LTE, in the retail Box it only mentions QuadBand 3G (AWS missing) and PentaBand LTE.
With the Canadian model being PentaBand and Snapdragon's S4 Specs claiming that is fully supporting it, along with the programmable LTE, we really have no clue of whats really going on until Nokia, or anyone else clarify it...
I have a very bad feeling that the all 920s are PentaBand 3G and support all bands of LTE with programmable software but Nokia for some reason is locking specific bands on specific models/regions.
Hopefully in time we will clarify everything and hopefully its sooner rather than later..
nMIK-3 said:
I thought the same thing on PentaBand 3G and 9 Bands LTE, however in another discussion we verified (at least for the German model) that even thought the Nokia German website states PentaBand 3G and 9 Bands LTE, in the retail Box it only mentions QuadBand 3G (AWS missing) and PentaBand LTE.
With the Canadian model being PentaBand and Snapdragon's S4 Specs claiming that is fully supporting it, along with the programmable LTE, we really have no clue of whats really going on until Nokia, or anyone else clarify it...
I have a very bad feeling that the all 920s are PentaBand 3G and support all bands of LTE with programmable software but Nokia for some reason is locking specific bands on specific models/regions.
Hopefully in time we will clarify everything and hopefully its sooner rather than later..
Click to expand...
Click to collapse
Different frequency bands require different antenna design. It is probably very difficult to design an antenna that can satisfy all LTE bands even though the chipset can support it. So, instead, Nokia is probably going to selectively make different hardware with different antenna design to fit a specific region. Apple iPhone 5 uses the similar Qualcomm chipset and it only supports very limited LTE bands for international version.
foxbat121 said:
Different frequency bands require different antenna design. It is probably very difficult to design an antenna that can satisfy all LTE bands even though the chipset can support it. So, instead, Nokia is probably going to selectively make different hardware with different antenna design to fit a specific region. Apple iPhone 5 uses the similar Qualcomm chipset and it only supports very limited LTE bands for international version.
Click to expand...
Click to collapse
For 3G PentaBand is now standard in almost all chips and since the Canadian variant comes with PentaBand on board and the fact that is standard on the S4 I really see no reason of why Nokia will order a custom version of the S4 to just physically take off the AWS. It doesn't make any sense, so if its missing, most likely is turn off in firmware.
For the LTE. Qualcomm introduced a revolutionary technology called Software Defined Radio or simply SDR and the Snapdragon S4 Plus MSM8960 chip which is inside the Lumia 920, supports that technology. With SDR the chipset support all LTE bands from a low to high frequency, it can work in everything between, of course not at the same time, the software programs what frequency the antenna should be set.
If the Lumia 920 and its S4 really have SDR technology, they it will make sense for Nokia to have the firmware deride what LTE to make available to the user, by reading the SIM region and not providing individual updated per region, or based on device product number.
This finally solves a major issue for the manufactures because they do not have to build customs chips for specific countries, the software simply programs it. If you Google it you can find a lot of info regarding SDR. Of course we are not in the engineering team of the Lumia 920 line and its obvious whatever we say here is based on theory and specs that are available to us.
nMIK-3 said:
For 3G PentaBand is now standard in almost all chips and since the Canadian variant comes with PentaBand on board and the fact that is standard on the S4 I really see no reason of why Nokia will order a custom version of the S4 to just physically take off the AWS. It doesn't make any sense, so if its missing, most likely is turn off in firmware.
For the LTE. Qualcomm introduced a revolutionary technology called Software Defined Radio or simply SDR and the Snapdragon S4 Plus MSM8960 chip which is inside the Lumia 920, supports that technology. With SDR the chipset support all LTE bands from a low to high frequency, it can work in everything between, of course not at the same time, the software programs what frequency the antenna should be set.
If the Lumia 920 and its S4 really have SDR technology, they it will make sense for Nokia to have the firmware deride what LTE to make available to the user, by reading the SIM region and not providing individual updated per region, or based on device product number.
This finally solves a major issue for the manufactures because they do not have to build customs chips for specific countries, the software simply programs it. If you Google it you can find a lot of info regarding SDR. Of course we are not in the engineering team of the Lumia 920 line and its obvious whatever we say here is based on theory and specs that are available to us.
Click to expand...
Click to collapse
If you understand radio technology at all, you should know the most important part that make all things work is the radio antenna, not the chipset. The chipset itself can't receive or transmit radio signal without a proper antenna. Try to disconnect your car radio antenna and see how many stations you can receive
foxbat121 said:
If you understand radio technology at all, you should know the most important part that make all things work is the radio antenna, not the chipset. The chipset itself can't receive or transmit radio signal without a proper antenna. Try to disconnect your car radio antenna and see how many stations you can receive
Click to expand...
Click to collapse
We're going a bit off-topic from the thread here, but you're right - SDR defines the baseband, not the RF components.
If you look at Nokia's FCC filing for the RM-821, you can see it has two cellular antennas ("main" and "MIMO") for each of two bands ("HB" high-band and "LB" low-band). Presumably LB is used for bands below 1 GHz or so, while HB is used for bands above. So you can see it's not necessary to have different antennas for every band - bands 1 to 4 (including AWS) could also use the same antennas, for example.
However, each band needs its own RF filters to prevent interference from neighbouring channels, and also needs amplifiers that have flat gain over those bands. These RF components are usually band specific, relatively bulky and expensive, and there are some challenges to use several RF chains in parallel. To my understanding these are the limiting factors that explain why a given device tends to support maximum 4 or 5 LTE channels.
tomdjp said:
We're going a bit off-topic from the thread here, but you're right - SDR defines the baseband, not the RF components.
If you look at Nokia's FCC filing for the RM-821, you can see it has two cellular antennas ("main" and "MIMO") for each of two bands ("HB" high-band and "LB" low-band). Presumably LB is used for bands below 1 GHz or so, while HB is used for bands above. So you can see it's not necessary to have different antennas for every band - bands 1 to 4 (including AWS) could also use the same antennas, for example.
However, each band needs its own RF filters to prevent interference from neighbouring channels, and also needs amplifiers that have flat gain over those bands. These RF components are usually band specific, relatively bulky and expensive, and there are some challenges to use several RF chains in parallel. To my understanding these are the limiting factors that explain why a given device tends to support maximum 4 or 5 LTE channels.
Click to expand...
Click to collapse
You nail it.
foxbat121 said:
If you understand radio technology at all, you should know the most important part that make all things work is the radio antenna, not the chipset. The chipset itself can't receive or transmit radio signal without a proper antenna. Try to disconnect your car radio antenna and see how many stations you can receive
Click to expand...
Click to collapse
Is that a joke?? I am spending my time explaining what SDR is and I am getting that respond??
I am assuming that I am talking with a person that knows at least a modern chipset like the S4 package contains all the antennas for GSM/WCDMA/LTE a separate antenna for Bluetooth and Wifi, GPS (S4 also includes GLONASS), the CPU and the Adreno GPU.
All the above come in the same tinny chip that in the size of your nail. And all this is called the "chipset". Qualcomm does not use a separate antenna anymore its integrated to the chipset.
nMIK-3 said:
Is that a joke?? I am spending my time explaining what SDR is and I am getting that respond??
I am assuming that I am talking with a person that knows at least a modern chipset like the S4 package contains all the antennas for GSM/WCDMA/LTE a separate antenna for Bluetooth and Wifi, GPS (S4 also includes GLONASS), the CPU and the Adreno GPU.
All the above come in the same tinny chip that in the size of your nail. And all this is called the "chipset". Qualcomm does not use a separate antenna anymore its integrated to the chipset.
Click to expand...
Click to collapse
With respect, that's not right - the antennas and RF components are external to the chipset.
Go and get the SAR compliance test report for Nokia 920 from the FCC's website, and you can see diagrams showing the external antennas for cellular, WLAN/BT and GPS which are positioned in various places inside the phone's chassis (btw, the LB MIMO antenna is about 7 cm long!)
Or go and check out the iFixit teardown for iPhone 5 and you can see the same kind of thing...
tomdjp said:
With respect, that's not right - the antennas and RF components are external to the chipset.
Go and get the SAR compliance test report for Nokia 920 from the FCC's website, and you can see diagrams showing the external antennas for cellular, WLAN/BT and GPS which are positioned in various places inside the phone's chassis (btw, the LB MIMO antenna is about 7 cm long!)
Or go and check out the iFixit teardown for iPhone 5 and you can see the same kind of thing...
Click to expand...
Click to collapse
That is correct. Many manufactures are placing antenna extensions and putting additional GPS censor in more practical areas.
The actual GSM/WCDMA/LTE modem WiFi, Bluetooth and GPS for Qualacom solutions are placed inside the chipset.
Please see http://www.qualcomm.com/chipsets/snapdragon for more information.
4g / LTE
tomdjp said:
Has anyone tried using one of the white unlocked Lumia 920 from Clove (I guess the ones from Expansys are the same) on an LTE network?
Specifically, do you have the "4G" option in the "highest connection speed" settings?
In my case, although I am using an LTE SIM with an LTE network on a supported band, I only have "2G" and "3G" options in the Highest Connection Speed settings. So normally it is only connecting over HSPA. Through playing around a lot with scanning LTE bands with the Field Test tool (##3282#), I can sometimes get the device to connect to LTE, after which it works perfectly on LTE until reboot. But it's not really a long-term solution.
The default firmware on my device is country variant "CV GB SW Variant ID 276 v03" which (apart from the version number) seems to be the same firmware as that sold by Orange / T-Mobile in the UK (i.e. for 3G networks).
I was thinking about trying to flash the EE firmware, but concerned this could create other issues (such as end up locking the phone to EE, or to certain LTE bands, or something...). Any thoughts appreciated.
Click to expand...
Click to collapse
I go into into field test mode and it says 4g then asks what LTE Band. My phone shows 4G not LTE in top left... is it LTE or 3G+?
Does anyone know what the different bands stand for? (band 5 etc) under the field service menu?
zok-star said:
Does anyone know what the different bands stand for? (band 5 etc) under the field service menu?
Click to expand...
Click to collapse
Likely they are LTE bands (e.g. band 5 = 850 MHz), but as you probably noticed they don't completely match with the LTE band support of the device. Keep in mind this field test program was probably thrown together by Nokia's R&D guys for internal testing only (not for consumers), so could be a legacy of earlier testing, another device variant, or some other reason...
Anyway, it seems fine to keep this setting on Automatic.
dougwallace said:
I go into into field test mode and it says 4g then asks what LTE Band. My phone shows 4G not LTE in top left... is it LTE or 3G+?
Click to expand...
Click to collapse
Hi Doug, could you share what version of the Lumia 920 you have, and which firmware?
As mentioned in my mail above, there seems no problem to leave the 4G band on automatic, and the bands available to be selected don't seem relevant. (My device picks up Band 1 LTE networks even though band 1 is not in the list).
Regarding 4G vs LTE, my device (unlocked UK CV) shows 4G in the top left when it is connected to LTE. I assume this can be changed by Nokia depending on the operator's requirement (esp in the US where 4G means HSPA...). You can be sure you're on LTE by going back to the field test menu, selecting GSM option, then looking at "Radio Access Technology". If you're on LTE, it should say LTE there.
tomdjp said:
Likely they are LTE bands (e.g. band 5 = 850 MHz), but as you probably noticed they don't completely match with the LTE band support of the device. Keep in mind this field test program was probably thrown together by Nokia's R&D guys for internal testing only (not for consumers), so could be a legacy of earlier testing, another device variant, or some other reason...
Anyway, it seems fine to keep this setting on Automatic.
Click to expand...
Click to collapse
I've kept mine on all automatic and i have noticed it switch to 4G at times, but then when i go to use it, it'll flick back to 3G... I'll need to test this in CBD sometime this week.
I got my device from clove, but im in Australia on Telstra 4G network. They use 1800mhz.
zok-star said:
I've kept mine on all automatic and i have noticed it switch to 4G at times, but then when i go to use it, it'll flick back to 3G... I'll need to test this in CBD sometime this week.
I got my device from clove, but im in Australia on Telstra 4G network. They use 1800mhz.
Click to expand...
Click to collapse
Hi, yes better to test in CBD where there's strong LTE signal.
In your Settings => Mobile Network, do you have a "4G" option under "Highest connection speed", or is it 2G and 3G only?
I have the unlocked version sitting on my desk right now.
The only difference seems to be that the radios are not the same?
But I've been reading that the radio might be flashable so it can accept Tmobile frequencies.
One question though, can ROMs from the unlocked version be used on the Tmobile version? Thanks
teatime0315 said:
I have the unlocked version sitting on my desk right now.
The only difference seems to be that the radios are not the same?
But I've been reading that the radio might be flashable so it can accept Tmobile frequencies.
One question though, can ROMs from the unlocked version be used on the Tmobile version? Thanks
Click to expand...
Click to collapse
From what I have read, the T-Mobile H1 can flash any ROM.
The radio flashing is an open question. So far attempts to get the AWS working on the dev / unlocked models have not worked. HTC says they have different radio hardware, but at this point it is anyone's guess if we will ever get AWS working on dev.
If you use the unlocked / dev on TMO, you will get 21 Mb on the 1900 refarmed band, and eventually LTE if you live in an area that has it. Right now there are maybe three areas with LTE.
If you got the 32 Gb unlocked, in my opinion it has no advantage over the T-Mobile model. The Dev edition has 64 gb of storage.
stevedebi said:
From what I have read, the T-Mobile H1 can flash any ROM.
The radio flashing is an open question. So far attempts to get the AWS working on the dev / unlocked models have not worked. HTC says they have different radio hardware, but at this point it is anyone's guess if we will ever get AWS working on dev.
If you use the unlocked / dev on TMO, you will get 21 Mb on the 1900 refarmed band, and eventually LTE if you live in an area that has it. Right now there are maybe three areas with LTE.
If you got the 32 Gb unlocked, in my opinion it has no advantage over the T-Mobile model. The Dev edition has 64 gb of storage.
Click to expand...
Click to collapse
The tmobile version flashed to the unlocked ROM should retain AWS on HSPA+, correct? That's the route I will probably be taking. The additional LTE bands are inconsequential for me - mainly south america and Philippines.
zaos said:
The tmobile version flashed to the unlocked ROM should retain AWS on HSPA+, correct? That's the route I will probably be taking. The additional LTE bands are inconsequential for me - mainly south america and Philippines.
Click to expand...
Click to collapse
I don't think anyone has tried that yet. I suspect AWS wouldn't work without some modification because the ROM would not support AWS. But I don't think it would hurt anything either.
zaos said:
The tmobile version flashed to the unlocked ROM should retain AWS on HSPA+, correct? That's the route I will probably be taking. The additional LTE bands are inconsequential for me - mainly south america and Philippines.
Click to expand...
Click to collapse
Yes, flashing ROMs doesn't affect frequency compatibility. All GSM One variants have the same hardware and ROMs/kernels are cross-compatible (international HSPA-only, and EMEA/AT&T/T-moblie LTE). ROMs don't include radio software, and so far at least, radio software hasn't affected available frequency bands.
teiglin said:
Yes, flashing ROMs doesn't affect frequency compatibility. All GSM One variants have the same hardware and ROMs/kernels are cross-compatible (international HSPA-only, and EMEA/AT&T/T-moblie LTE). ROMs don't include radio software, and so far at least, radio software hasn't affected available frequency bands.
Click to expand...
Click to collapse
If flashing ROMs (not radios) to/from intl, US, EMEA models don't affect supported bands, I don't see why it would affect tmobile -> unlocked. Advantages would be no tmobile bloat, no hacks to please the tmobile overloads, etc.
zaos said:
If flashing ROMs (not radios) to/from intl, US, EMEA models don't affect supported bands, I don't see why it would affect tmobile -> unlocked. Advantages would be no tmobile bloat, no hacks to please the tmobile overloads, etc.
Click to expand...
Click to collapse
It sounds like you're disagreeing with me or something, but yes, flashing an international ROM on tmo One is great because it gets rid of bloat, can edit APNs to enable tethering, and always based on latest firmware rather than waiting for tmo to push an update. Only downside I know of is no wifi calling. I'm running TrickDroid on mine and it works great.
teiglin said:
It sounds like you're disagreeing with me or something, but yes, flashing an international ROM on tmo One is great because it gets rid of bloat, can edit APNs to enable tethering, and always based on latest firmware rather than waiting for tmo to push an update. Only downside I know of is no wifi calling. I'm running TrickDroid on mine and it works great.
Click to expand...
Click to collapse
Sorry, that was more directed at stevedebi's comment. Wifi calling can be replaced with SIP calling so that should be fine.
Warranty problems?
One potential issue with getting the T-Mobile version could have to do with the warranty. U.S. carriers seem squeamish about people modding their phones and threaten to void the warranty for unlocking bootloaders, rooting, etc. That said, I don't have specific info at hand that HTC unlocked phones are much more lenient but seems worth looking into.
zaos said:
Sorry, that was more directed at stevedebi's comment. Wifi calling can be replaced with SIP calling so that should be fine.
Click to expand...
Click to collapse
Well, most of the new T-Mobile plans come with unlimited hotspot and WiFi calling. I'm not planning to unlock mine. My One is performing fine on the stock ROM, and TMO will update the software (eventually).
As noted above, I'm not sure that T-Mobile looks kindly on having TAMPERED show up on a phone. They might well deny a warranty claim.
For me get the T-Mobile HTC one I had the 64gb edition got tired of the stupid refarm 1900mhz frequency my icon was switching from H to 3G. Now with my original T-Mobile HTC one I get steady 4g icon and good speeds
Sent from my HTC One using xda app-developers app
stevedebi said:
Well, most of the new T-Mobile plans come with unlimited hotspot and WiFi calling. I'm not planning to unlock mine. My One is performing fine on the stock ROM, and TMO will update the software (eventually).
As noted above, I'm not sure that T-Mobile looks kindly on having TAMPERED show up on a phone. They might well deny a warranty claim.
Click to expand...
Click to collapse
Same here mine is stock Rom with no root or unlocked bootloader only have about 5 T-Mobile apps that don't worry me.
Sent from my HTC One using xda app-developers app
ahernandez4110 said:
For me get the T-Mobile HTC one I had the 64gb edition got tired of the stupid refarm 1900mhz frequency my icon was switching from H to 3G. Now with my original T-Mobile HTC one I get steady 4g icon and good speeds
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Switching from H to 3G is just what the radio does; it's how the interface is supposed to work. The T-Mobile version works exactly the same way--and you can see this if you flash an international ROM on your tmo One--but tmo assumes Americans are idiots who a. don't know what HSPA+ is, and b. get confused if the radio idles at "3G" when they expect to have "4G" coverage. So stock tmo ROM just shows 4G all the time, but it is just themed connection icons really. Seems like they're right to do this, which is a bit sad.
Of course, that doesn't mean that you would be getting the same speeds with the dev edition, since even in refarmed areas, you could well get better UMTS coverage over AWS than PCS.
teiglin said:
Switching from H to 3G is just what the radio does; it's how the interface is supposed to work. The T-Mobile version works exactly the same way--and you can see this if you flash an international ROM on your tmo One--but tmo assumes Americans are idiots who a. don't know what HSPA+ is, and b. get confused if the radio idles at "3G" when they expect to have "4G" coverage. So stock tmo ROM just shows 4G all the time, but it is just themed connection icons really. Seems like they're right to do this, which is a bit sad.
Of course, that doesn't mean that you would be getting the same speeds with the dev edition, since even in refarmed areas, you could well get better UMTS coverage over AWS than PCS.
Click to expand...
Click to collapse
Not to mention that in many cases you get EDGE on 1900 even in refarmed markets.
yeah I was thinking of getting the DE because its 64gb but then I realize that with wifi everywhere, I can just upload pictures or videos to you box account, then delete them to make room, and keep installing apps I want and delete those you dont.
After dealing with 16gb in a Gnexus, you learn how to manage to space
teiglin said:
Switching from H to 3G is just what the radio does; it's how the interface is supposed to work. The T-Mobile version works exactly the same way--and you can see this if you flash an international ROM on your tmo One--but tmo assumes Americans are idiots who a. don't know what HSPA+ is, and b. get confused if the radio idles at "3G" when they expect to have "4G" coverage. So stock tmo ROM just shows 4G all the time, but it is just themed connection icons really. Seems like they're right to do this, which is a bit sad.
Of course, that doesn't mean that you would be getting the same speeds with the dev edition, since even in refarmed areas, you could well get better UMTS coverage over AWS than PCS.
Click to expand...
Click to collapse
You are right if you go to phone settings-about- network you could see UMTS and HSPS+ it swicthes between UMTS 3g and 4g HSPS+ and my 4g icon stays the same, this also happen to my old HTC one 64gb developer edition but it never showed the 4g icon like T-Mobile HTC one all it showed was 3g and H icons this happens in a 1900mhz refarm area. Look at T-Mobile HTC One as example thank god it has 1700mhz built-in that's why I got ridoff my developer Edition
Sent from my HTC One using xda app-developers app
zaos said:
The tmobile version flashed to the unlocked ROM should retain AWS on HSPA+, correct? That's the route I will probably be taking. The additional LTE bands are inconsequential for me - mainly south america and Philippines.
Click to expand...
Click to collapse
yes flashing the TMO version on an unlocked rom will allow you to retain the AWS bands tmobile uses for 3g/HSDPA/HSPAP(HSDPA+)
i bought the TMO HTC one and am now using ordroid 4.2.0 on se7en kernel and i have AWS signal. and not just refarmed signal also umts signal as well.
I need some assistance from the Pros on this one.
Problem: phone only connects to 4G HSPA, will not connect to 4G LTE no matter what I've tried. AT&T tier 3 technical support said by all means the phone should be connecting to 4G LTE. Unless the phone was falsely advertised as having support for 4G LTE.
This is the phone I bought for my wife: http://www.newegg.com/Product/Product.aspx?Item=9SIA2NR2977129
It advertises 4G LTE Support 700/900/1800/2100/2600 MHz
Also supports: GSM/GPRS/EDGE: 850/900/1800/1900 MHz and UMTS/HSPA: 850/900/1900/2100 MHz with HSPA+ up to 42 Mbps
The IMEI number shows in the IMEI database as supporting 4G LTE and all associated bands.
Phone Info:
HTC One M8 (International Version)
Model: M8_UL (the AT&T version is M8_UL_CA)
Stock MID: 0P6B11000 (I changed this to the AT&T MID of 0P6B12000 since I'm using it on AT&T network)
S-OFF
Unlocked
SuperCID: 11111111
HBOOT: 3.19.0.0000
Current Firmware: 4.16.401.10
Tried This Firmware: 4.16.1540.8
Current Radio: 1.25.214500021.06G
Tried This Radio: 1.24.21331147A1.09G
Running ARHD ROM 34.6 Lollipop 5.0.1
default.xml modified to SKU: 7 and Region 1 (for AT&T support)
What else can I try to enable 4G LTE? I already took the SIM out of my phone and put it in my wife's phone. Still her phone will not connect to LTE.
Are you checking the status in settings>about>network or going by the icons in the status bar? I'm using a "multi-carrier" ROM and the status bar icons show 4G for LTE and H for HSPA. I believe the ROMs built on ATT base will show 4GLTE and 4G, respectively.
Dial *#*#4636#*#* and Confirm Network Type
BYOBret said:
Are you checking the status in settings>about>network or going by the icons in the status bar? I'm using a "multi-carrier" ROM and the status bar icons show 4G for LTE and H for HSPA. I believe the ROMs built on ATT base will show 4GLTE and 4G, respectively.
Click to expand...
Click to collapse
You can't really rely on the icon, it's best to check the connected band by using this method:
Tap Phone
Dial *#*#4636#*#*
Tap Phone Information
You can change your radio frequency to USA or International
Select the Bands you want your phone to support
View Network Type: LTE, HSPA etc (it should always read LTE if you have an LTE plan and your near an LTE capable tower. My phone reads LTE always, my wife's reads HSPA)
Run Diagnostics etc.
TrickMasterPC said:
You can't really rely on the icon
Click to expand...
Click to collapse
Right. That was my point. Just making sure you weren't being duped by the status bar icons, as they are different for ATT and other carriers.
You might want to try running a full RUU for ATT to see if it will connect to LTE. That way you will be sure that all firmware, radio, system match for ATT.
BYOBret said:
Right. That was my point. Just making sure you weren't being duped by the status bar icons, as they are different for ATT and other carriers.
You might want to try running a full RUU for ATT to see if it will connect to LTE. That way you will be sure that all firmware, radio, system match for ATT.
Click to expand...
Click to collapse
You're on the right track! That was the first thing I did, I installed this ROM 4.28.502.1 from here: http://dl3.htc.com/application/RUU_...40.45.C33065.00_F_release_426617_signed_2.exe
Latest official AT&T, still no LTE, HSPA only. Sad Face.
TrickMasterPC said:
You're on the right track! That was the first thing I did, I installed this ROM 4.28.502.1 from here: http://dl3.htc.com/application/RUU_...40.45.C33065.00_F_release_426617_signed_2.exe
Latest official AT&T, still no LTE, HSPA only. Sad Face.
Click to expand...
Click to collapse
Ah bummer. What phone are you using? Does her sim card connect to lte on yours? I have read some posts where a new sim card from ATT store fixed this issue, but I know you tried yours already. Maybe hardware problem with the phone itself? I'm out of ideas, sorry.
BYOBret said:
Ah bummer. What phone are you using? Does her sim card connect to lte on yours? I have read some posts where a new sim card from ATT store fixed this issue, but I know you tried yours already. Maybe hardware problem with the phone itself? I'm out of ideas, sorry.
Click to expand...
Click to collapse
I put my SIM in her phone and visa versa, and both SIMs get LTE on my phone, but not on her phone. Here's what I think. The seller on Newegg changed the IMEI and falsely represented the phone as supporting LTE. That's really the only think I can conclude. The IMEI number it shipped with states LTE support in the IMEI look-up database. OR the IMEI information in the database is inaccurate for the phone.
The hardware is identical to the AT&T version, as are all "GSM" M8 versions (meaning Verizon and Sprint are excluded). So there shouldn't be any reason why LTE shouldn't work, as long as you are on the correct radio.
Its not a hardware issue, and something else is going on. It seems from your OP and subsequent posts, that you've tried a variety of things. You radio and ROM are kind of a mish-mosh right now. I'd suggest RUU back to stock Dev Edition or stock AT&T (latter probably being the best bet) and let us proceed from there to make things less confusing.
redpoint73 said:
The hardware is identical to the AT&T version, as are all "GSM" M8 versions (meaning Verizon and Sprint are excluded). So there shouldn't be any reason why LTE shouldn't work, as long as you are on the correct radio.
Its not a hardware issue, and something else is going on. It seems from your OP and subsequent posts, that you've tried a variety of things. You radio and ROM are kind of a mish-mosh right now. I'd suggest RUU back to stock Dev Edition or stock AT&T (latter probably being the best bet) and let us proceed from there to make things less confusing.
Click to expand...
Click to collapse
I flashed the latest official AT&T ROM, but this made no difference what-so-ever. I'm currently using the exact same ROM and firmware on my HTC One M8. I get LTE all-day-long no problem, my wife's phone does not. I already changed the MID to match my AT&T MID and also the CID, but that made no difference. The only thing I haven't tried is changing the model name. My model name is M8_UL_CA and hers is M8_UL. I can't figure out how to change this value, but I'm not sure it makes any difference.
AT&T LTE bands
Band2 1900MHz
Band4 1700MHz
Band5 850MHz
Band17 700MHz
Band 17 is AT&T's primary LTE band.
Phone is advertised as supporting the following LTE Bands
LTE: 700/900/1800/2100/2600 MHz
TrickMasterPC said:
I flashed the latest official AT&T ROM, but this made no difference what-so-ever.
Click to expand...
Click to collapse
Just the ROM, or the whole RUU? There is a huge difference. There are something like 36 partitions, and ROM (/system) is just one of them. The RUU flashes every partition.
I know you mentioned you previously flashed the AT&T RUU. But its also clear that you did a bunch of other things since then. The reason (as already stated) I want you to RUU now, is to put you on a stock AT&T software to give us a clean "blank slate" to work forward from here. As opposed to having too many other variables that can cause problems. For instance, its a known issue that Euro ROMs (such as ARHD) have some issues on AT&T's LTE network. So being on that ROM just compounds another layer of issues on top of issues. Going to a stock AT&T software configuration is a much cleaner state to troubleshoot your from.
TrickMasterPC said:
The only thing I haven't tried is changing the model name. My model name is M8_UL_CA and hers is M8_UL. I can't figure out how to change this value, but I'm not sure it makes any difference.
Click to expand...
Click to collapse
Model name does not make any difference, that I have seen. I've seen plenty of folks "convert" from one carrier version to another, and the steps of s-off, change CID and MID, flash RUU is all it takes (changing model name not required).
And that is probably also the reason that I've never seen a mod for changing model name (it doesn't actually affect anything as far as device checks).
I'd say, don't worry about it and don't waste your time trying.
TrickMasterPC said:
AT&T LTE bands
Band2 1900MHz
Band4 1700MHz
Band5 850MHz
Band17 700MHz
Band 17 is AT&T's primary LTE band.
Phone is advertised as supporting the following LTE Bands
LTE: 700/900/1800/2100/2600 MHz
Click to expand...
Click to collapse
By "primary" band, I assume you mean the one most commonly used by AT&T. Your phone needs to support the band that AT&T is using in your area. So unless you know for fact that 700 Mhz is what they are using in your area, it can be any of the four bands.
I mentioned that that this is not a hardware issue. But I should clarify, its not a matter of a difference in hardware between GSM versions (since they are actually all the same). But it occurs to me that it is fully possible that there may simply be a hardware defect that means your LTE simply broken, and the seller should replace the device.
If we can successfully confirm that you are on full stock AT&T software by RUU (confirm proper radio, main version, etc.) and LTE is still not working (and we know the SIM is good); then I pretty much have to conclude the phone is simply defective/broken.
redpoint73 said:
Just the ROM, or the whole RUU? There is a huge difference. There are something like 36 partitions, and ROM (/system) is just one of them. The RUU flashes every partition.
I know you mentioned you previously flashed the AT&T RUU. But its also clear that you did a bunch of other things since then. The reason (as already stated) I want you to RUU now, is to put you on a stock AT&T software to give us a clean "blank slate" to work forward from here. As opposed to having too many other variables that can cause problems. For instance, its a known issue that Euro ROMs (such as ARHD) have some issues on AT&T's LTE network. So being on that ROM just compounds another layer of issues on top of issues. Going to a stock AT&T software configuration is a much cleaner state to troubleshoot your from.
Model name does not make any difference, that I have seen. I've seen plenty of folks "convert" from one carrier version to another, and the steps of s-off, change CID and MID, flash RUU is all it takes (changing model name not required).
And that is probably also the reason that I've never seen a mod for changing model name (it doesn't actually affect anything as far as device checks).
I'd say, don't worry about it and don't waste your time trying.
By "primary" band, I assume you mean the one most commonly used by AT&T. Your phone needs to support the band that AT&T is using in your area. So unless you know for fact that 700 Mhz is what they are using in your area, it can be any of the four bands.
I mentioned that that this is not a hardware issue. But I should clarify, its not a matter of a difference in hardware between GSM versions (since they are actually all the same). But it occurs to me that it is fully possible that there may simply be a hardware defect that means your LTE simply broken, and the seller should replace the device.
If we can successfully confirm that you are on full stock AT&T software by RUU (confirm proper radio, main version, etc.) and LTE is still not working (and we know the SIM is good); then I pretty much have to conclude the phone is simply defective/broken.
Click to expand...
Click to collapse
I installed the HTC One M8 AT&T full RUU from this webpage: http://www.htc.com/us/support/rom-downloads.html (made no difference) and I tried it twice just to be sure so... it must be that AT&T in my area is using an unsupported LTE band, OR like you said something's wrong with the radio. Doesn't the radio hardware have specific frequency crystals to send/receive only on certain frequencies? Or is this is a fully digital self-tuning radio that receives/transmits on any frequency as programmed.
TrickMasterPC said:
I installed the HTC One M8 AT&T full RUU from this webpage: http://www.htc.com/us/support/rom-downloads.html (made no difference) and I tried it twice just to be sure so... it must be that AT&T in my area is using an unsupported LTE band, OR like you said something's wrong with the radio. .
Click to expand...
Click to collapse
I've never heard of AT&T using a band not supported by this phone. Their LTE network is fairly mature at this point, at least to the degree that they aren't adding bands not previously used, and not supported by relatively current (AT&T branded) devices.
If you confirmed that the proper AT&T radio was properly installed by the RUU, and checked the APN is good; have to conclude there is a hardware defect.
Normally, I'd suggest in that case that you contact the seller for an exchange or refund. But this is a tricky situatin, in that you've modified the phone, and trying to get it to work on LTE bands not specified for the device as it was manufactured.
TrickMasterPC said:
Doesn't the radio hardware have specific frequency crystals to send/receive only on certain frequencies?
Click to expand...
Click to collapse
Nope. Not sure about "crystals". But while you are correct that in older phones the band compatibility was set in hardware; the Snapdragon 801 was one of the first smartphone chipsets (if not the first) where band compatibility is determined solely by software (within reasonable limits - CDMA bands require different hardware). When I said the GSM variants are identical in hardware, I meant it.
Im sure someone has had you check this already but goto phone press *#*#4636*#*# scroll down there will be a drop down menu. See if you can select it.
Also att has been throttling back their users. So if you use to much net I think limit is 5gig they cut your speeds down and you want be able to connect any higher.
-Epix- said:
Also att has been throttling back their users. So if you use to much net I think limit is 5gig they cut your speeds down and you want be able to connect any higher.
Click to expand...
Click to collapse
It should be noted that this is only for those on grandfathered unlimited data plans. Those on tiered data plans will not be throttled, but be charged an overage once your allotment is used up.
Compare nv item 6828 and 6829 between yours and your wife phone using QXDM and QPST. You will get the answer why cannot receive LTE.
did you manage to solve the issue? I am having a similar problem with my htc one m8, it locks only to edge and cannot get it to work with LTE or 3G. I have super CID and MID is 0P6B10000, however the model is M8_UL_CA which is on ATT as far as I know, I am in EU. my SIM card works on my M7 with LTE and 3G but in my M8 I got only EDGE
waseem86 said:
did you manage to solve the issue? I am having a similar problem with my htc one m8, it locks only to edge and cannot get it to work with LTE or 3G. I have super CID and MID is 0P6B10000, however the model is M8_UL_CA which is on ATT as far as I know, I am in EU. my SIM card works on my M7 with LTE and 3G but in my M8 I got only EDGE
Click to expand...
Click to collapse
Post your full details and I can try to troubleshoot. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
I have an old M8 lying around that I fired up and had remembered I had rooted it and the bootloader is unlocked.. Is there a way to 'trick' this phone into thinking it's an AT&T branded phone? hboot, etc. and that will allow me to RUU something official from AT&T? I know this sounds really strange and probably stupid but.. I just can't sleep and need something to fill the time.. Can I do it?
Don't think so, radio hardware is different, not to mention the partition layout.
Sent from my HTC6525LVW using Tapatalk
jbarcus81 said:
Is there a way to 'trick' this phone into thinking it's an AT&T branded phone? hboot, etc. and that will allow me to RUU something official from AT&T? ?
Click to expand...
Click to collapse
Absolutely not. At least not any way that is known; and your chance of failure is high (with a brick being the possible or even probable result).
As mentioned in the previous comment, the partitioning on the phones is different. If you try to run the RUU, you at best it will fail, at worst it will brick the device.
Most other M8 versions (that don't support CDMA) can be "converted" from one version to another (other exceptions being dual SIM and M8 Eye). But Verizon and Sprint are the oddballs here. Some experienced devs have been messing around with these variants from the start (to try to convert them) with no success.
Perfect! All I needed to hear! Ah well.. it was worth a shot! Just trying to get my account provisioned for LTE so I can get LTE on my unlocked devices.. I've been told, and read, that if I can get an AT&T branded LTE capable phone to just swap my SIM in it.. and let my account provision, then I'll have LTE on any device AT&T or not... Just trying to avoid a contract..
jbarcus81 said:
I've been told, and read, that if I can get an AT&T branded LTE capable phone to just swap my SIM in it.. and let my account provision, then I'll have LTE on any device AT&T or not... Just trying to avoid a contract..
Click to expand...
Click to collapse
As long as the phone is SIM unlocked (Verizon version is) then you should just be able to put an AT&T SIM in, and enter the proper AT&T APN for service, as long as the phone supports the proper bands. Its irrelevant whether the phone is AT&T branded or not.
Now the underlined bit in the paragraph above is the main issue. The Verizon M8 only supports one of the four bands (Bands 2, 5, 4, and 17) used by AT&T for LTE (Verizon M8 supports Bands 3, 4, 7, and 13). So depending on what band is used in your area, you may or may not get LTE.
But GSM (2G) and HSPA (3G) should work just fine on AT&T.
redpoint73 said:
As long as the phone is SIM unlocked (Verizon version is) then you should just be able to put an AT&T SIM in, and enter the proper AT&T APN for service, as long as the phone supports the proper bands. Its irrelevant whether the phone is AT&T branded or not.
Now the underlined bit in the paragraph above is the main issue. The Verizon M8 only supports one of the four bands (Bands 2, 5, 4, and 17) used by AT&T for LTE (Verizon M8 supports Bands 3, 4, 7, and 13). So depending on what band is used in your area, you may or may not get LTE.
But GSM (2G) and HSPA (3G) should work just fine on AT&T.
Click to expand...
Click to collapse
That's the odd part.. My main phone is the S6 Edge from Verizon.. it's on the AT&T network and I assume my APN is correct.. But it's not picking up LTE and I am almost certain the S6 Edge from Verizon will pick up the correct band for AT&T LTE .. But it's only using the H+ speed.. What's even more strange?? When I throw my SIM into the M8? I get LTE on AT&T and verify with 30+mpbs speeds.. I have no idea what's going on...
jbarcus81 said:
That's the odd part.. My main phone is the S6 Edge from Verizon.. it's on the AT&T network and I assume my APN is correct.. But it's not picking up LTE and I am almost certain the S6 Edge from Verizon will pick up the correct band for AT&T LTE .. But it's only using the H+ speed.. What's even more strange?? When I throw my SIM into the M8? I get LTE on AT&T and verify with 30+mpbs speeds.. I have no idea what's going on...
Click to expand...
Click to collapse
Yeah, that is strange. According to the specs for the S6 Edge here, the Verizon version supports the same LTE bands as the VZN M8, and actually some additional bands (2 and 5) that also happen to be bands used by AT&T.
One thing I can think of, is that the VZN M8 in actuality supports some bands that are not advertised/explicit in the specs. It wouldn't be unheard of, as members here have reported some versions of the non-CDMA M8 as supporting some bands not indicated in the specs. And that band happens to be what AT&T is using in your market region. In this case, that band would seem to be Band 17 (the only band that AT&T is known to use, that isn't listed on the S6 Edge specs).
Or the other possibility, is there is just some issue with the S6 that is preventing connection to LTE (but on the same supported band that the M8 has).
redpoint73 said:
Yeah, that is strange. According to the specs for the S6 Edge here, the Verizon version supports the same LTE bands as the VZN M8, and actually some additional bands (2 and 5) that also happen to be bands used by AT&T.
One thing I can think of, is that the VZN M8 in actuality supports some bands that are not advertised/explicit in the specs. It wouldn't be unheard of, as members here have reported some versions of the non-CDMA M8 as supporting some bands not indicated in the specs. And that band happens to be what AT&T is using in your market region. In this case, that band would seem to be Band 17 (the only band that AT&T is known to use, that isn't listed on the S6 Edge specs).
Or the other possibility, is there is just some issue with the S6 that is preventing connection to LTE (but on the same supported band that the M8 has).
Click to expand...
Click to collapse
Yeah.. I'm not worried about it.. I've been told that all I need is an AT&T branded LTE capable device hooked up to the account and that my account hasn't been provisioned for LTE .. I've seen this in a few places so it's worth a shot.. I ordered a junk LTE phone branded AT&T to test it out.. ordered a OnePlus 2 and will likely unload the S6 Edge (if it never picks up the LTE from AT&T)
jbarcus81 said:
I've been told that all I need is an AT&T branded LTE capable device hooked up to the account and that my account hasn't been provisioned for LTE ..)
Click to expand...
Click to collapse
As I've already mentioned, its not really necessary to have an AT&T branded device. I suspect the reason you've seen people say this, is that AT&T branding means by definition the phone has all the bands used by AT&T for LTE; since obviously the phone is intended for use on AT&T's network. Since AT&T uses a number of bands (4) and LTE bands being used worldwide has become very un-standardized, its somewhat difficult to find a non-AT&T phone that has all the bands. But they do exist, such as the US unlocked M8, Dev Edition M8, and Nexus devices. Also, I've seen folks used other non-ATT branded phones, which may not have all 4 LTE bands used by AT&T, but the one(s) needed in the particular user's region. Not ideal, but sufficient for some folks.
Another reason why some may say the phone needs to be AT&T branded, is that AT&T tech support won't provide you any support if you have a non-ATT phone. But honestly, I've used non-branded devices (and plenty of folks here have), and this is very rarely an issue. The folks here on XDA will usually provide you better support, anyway!
Of course, your ATT account needs to be provisioned for LTE in order to have that service. Its a simple matter, and doesn't cost anything (just need a smartphone data plan).
redpoint73 said:
As I've already mentioned, its not really necessary to have an AT&T branded device. I suspect the reason you've seen people say this, is that AT&T branding means by definition the phone has all the bands used by AT&T for LTE; since obviously the phone is intended for use on AT&T's network. Since AT&T uses a number of bands (4) and LTE bands being used worldwide has become very un-standardized, its somewhat difficult to find a non-AT&T phone that has all the bands. But they do exist, such as the US unlocked M8, Dev Edition M8, and Nexus devices. Also, I've seen folks used other non-ATT branded phones, which may not have all 4 LTE bands used by AT&T, but the one(s) needed in the particular user's region. Not ideal, but sufficient for some folks.
Another reason why some may say the phone needs to be AT&T branded, is that AT&T tech support won't provide you any support if you have a non-ATT phone. But honestly, I've used non-branded devices (and plenty of folks here have), and this is very rarely an issue. The folks here on XDA will usually provide you better support, anyway!
Of course, your ATT account needs to be provisioned for LTE in order to have that service. Its a simple matter, and doesn't cost anything (just need a smartphone data plan).
Click to expand...
Click to collapse
I've dug deeper and have to not only have an AT&T branded phone, I have to register the IEMI on my account, then swap the SIM card back into the other phone. I've got the phone but can't find a way to do this online so I'll have to call tomorrow...
Sent from my ONE A2005 using Tapatalk
I have a m8 whl sprint abd does not use CDMA only gsm network. I can I change the mid and convert the phone to get latest ota for dev edition version? I thanks
long.nguyen said:
I have a m8 whl sprint abd does not use CDMA only gsm network. I can I change the mid and convert the phone to get latest ota for dev edition version? I thanks
Click to expand...
Click to collapse
Absolutely NO.
What I mentioned above (Post #3) for the Verizon variant, also applies to Sprint (both versions support CDMA - the fact you don't use it is irrelevant). If you try to convert to another version won't work, and will probably result in a brick.
Also, even if you didn't have a CDMA version M8, you typically can't convert using an OTA, it has to be an RUU.
redpoint73 said:
Absolutely NO.
What I mentioned above (Post #3) for the Verizon variant, also applies to Sprint (both versions support CDMA - the fact you don't use it is irrelevant). If you try to convert to another version won't work, and will probably result in a brick.
Also, even if you didn't have a CDMA version M8, you typically can't convert using an OTA, it has to be an RUU.
Click to expand...
Click to collapse
@redpoint ; don't we have any chance to install different provider radios to Verizon Htc devices..?
because verizon devices you know that support 3, 4, 7, and 13 bands,but i want to enable band 20 for europe LTE..
pls help us to enable other bands =( because only u can do that as a genius =)
thanx a lot
cincon said:
@redpoint ; don't we have any chance to install different provider radios to Verizon Htc devices..?
Click to expand...
Click to collapse
Absolutely NOT. As already thoroughly discussed on this thread, if you attempt to install another version's radio on the Verizon version, it won't work, and you may radio brick the phone (permanent damage possible).
Different radios, different partition layout.
Don't even try it. Experienced devs have tried to "convert" by various methods and mods, and failed.
But there may be other ways (besides flashing another version's radio) to enable the band(s) you want, read on:
cincon said:
[MENTION=434105]
because verizon devices you know that support 3, 4, 7, and 13 bands,but i want to enable band 20 for europe LTE..
Click to expand...
Click to collapse
You can take a look at the following method, as it claims to enable Band 20: http://forum.xda-developers.com/verizon-htc-one-m8/general/lte-band-7-2600mhz-finally-guide-t2992523
Read the thread, and proceed at your own discretion. I'm not knowledgeable with changing NV values (it doesn't work on "GSM" M8 variants, so does not apply to me). I simply know this thread exists.
cincon said:
[MENTION=434105]
pls help us to enable other bands =( because only u can do that as a genius =)
Click to expand...
Click to collapse
Far from a genius, and I don't create any of these mods. I just contribute by passing on knowledge I've gained here. Really, that is part of what XDA is all about.