I'm looking for advice on compatible radios for Bell Canada. I'm running the latest CM10.1 build from epinter and my wifi/bt are basically dead. They only turn on sometimes, but most of the time they seem to be frozen.
I had this problem with the stock Bell radio, and it continues with the Telstra N_01.87.00R, which otherwise works great for data/calls/sms.
What I'd like to know is this: Has anybody used the .100 radio, or the .37/.38 radios from ATT, on Bell? Are they compatible with my network? Will I get HSPA+ speeds?
Thanks so much!
OK, I just did a quick Google search and it appears they use the same frequencies. That's good news, right?
So I guess the question is, do the ATT radios work, and work well, on Bell's network?
Quick answer - yes, the radios work, no they don't work well.
Stick with your Bell OTA or the Telstra radios.
I can't seem to find this in the forums at all. I recently bought the T-Mobile HTC One (Model PN07130) and changed it to a Google Play edition (S-Off, SuperCID, flashed 4.2.2 RUU.zip and OTA updated to 4.3)
My questions are that:
Is the 1700mhz band still enabled on my phone?
Will flashing the latest T-Mobile Radio enable it?
Is it HBOOT/ROM dependent?
Is there anyway to check the Bands used/enabled?
Will changing the radio block OTA updates? (I'm pretty sure this is a yes)
Best APN settings?
I would like people who have done this to respond, or those that have an idea of how this all works. I'm giving this phone as a gift and would like the recipient to have great coverage with uninterrupted updates.
Thanks
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
Does anyone know what differences there might be between the Unlocked version and the T-Mobile variant? I'm wondering if there are any features missing from the Unlocked version while on the T-Mobile network (like how on the VZW version Wifi calling is apparently not usable on the Unlocked version).
Any info would be great, thanks.
The unlocked one has the mobile data toogle while Tmobile dont have it. Wifi calling running fine on the unlocked ones with Tmobile services. Hope that could help you.
AS I understand there aren't many differences between them.