Related
Anyone else experiencing 4g issues after update? When I'm in areas where I used to have strong 4g, I'm getting weak 2g now. Also, sometimes WiFi signal strong but pages load slow and switching from WiFi to tmo network causes no data connectivity. Stupid updates grrr
Sent from my HTC_Amaze_4G using xda premium
Same here. Kind of wish I could go back to how I got it out of the box. After the update I get a lot of 2G signal where before I would get 4G nearly always. At least the latest update fixed the issue of not being able to turn the phone off. It did for me at least.
I have seen that as well and suspecting the new radio in that latest update. in many cases, my phone get stuck in 2G
Sent from my HTC_Amaze_4G using xda premium
I have not seen any difference. Do you have a 128kb sim card?
Which update is this? I haven't had an update for a while now.
I work at T-Mobile. Anytime I have seen an issue was because it was not a new 3G-G sim.
that is true my brother updated his phone and has been having service problems ever since sometimes even no service at all. He has baseband that ends in .08 and I have the one that ends in .07 so mine has been ok.
Hi all. I was having a problem that I just couldn't find any fix to after scouring the internet. It seems to be fixed (so far), so I thought I'd share briefly so someone else can find it.
I was on the Stable release of CM10 Jewel (HBOOT 1.19, S-ON) on the Evo 4g LTE. I live in an area with early LTE rollout, and I was getting LTE on my stock Rom. If I selected Network Mode: LTE/ CDMA/ EvDo, I would get a cell signal and reception but no data of any kind. If I switched the network mode to CDMA/ EvDo Auto, I would get reliable 3g (or 2.5g). As far as I can tell, this is a common issue that has something to do with the LTE handoff.
I was reluctant to start using the nighties, since the stable release is so recent. However, updating to the most recent nightly (at this point 12-10-2012), through the simple CM10 updater in the "about phone" menu, seems to have fixed the problem. Just FYI.
thewildgunman said:
Hi all. I was having a problem that I just couldn't find any fix to after scouring the internet. It seems to be fixed (so far), so I thought I'd share briefly so someone else can find it.
I was on the Stable release of CM10 Jewel (HBOOT 1.19, S-ON) on the Evo 4g LTE. I live in an area with early LTE rollout, and I was getting LTE on my stock Rom. If I selected Network Mode: LTE/ CDMA/ EvDo, I would get a cell signal and reception but no data of any kind. If I switched the network mode to CDMA/ EvDo Auto, I would get reliable 3g (or 2.5g). As far as I can tell, this is a common issue that has something to do with the LTE handoff.
I was reluctant to start using the nighties, since the stable release is so recent. However, updating to the most recent nightly (at this point 12-10-2012), through the simple CM10 updater in the "about phone" menu, seems to have fixed the problem. Just FYI.
Click to expand...
Click to collapse
I don't have LTE but everything works great for me on my CM10 build. I think its 12-4 that was posted on this forum.
I even turned S-OFF using DirtyRacun before hand, works like a charm (did it on my 64bit Win7 machine)
My problem now is when LTE connects, I get 4G icon and no data. When I get out of LTE coverage, data works again. So in LTE areas, I have to disable it. Kind of counter productive. I am downloading 12/10 nightly build and will test LTE later today.
Sent from my EVO using Tapatalk 2
I live in a Lte area and it works good for me. 12.4. Build
Sent from my EVO using Tapatalk 2
Meanee said:
My problem now is when LTE connects, I get 4G icon and no data. When I get out of LTE coverage, data works again. So in LTE areas, I have to disable it. Kind of counter productive. I am downloading 12/10 nightly build and will test LTE later today.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Yep, thats why I am on ViperRom until LTE is handing off to 3G for everyone. It works for some, but not for others. I need to consistently have my LTE.
Problem is, it was screwing up on a Sense ROM as well. I flashed latest CM10 nightly, and managed to squeeze 12kbps transfer on LTE in Miami airport and that was it. But hey, at least for once I saw a 4G icon!
Sent from my EVO using Tapatalk 2
Meanee said:
Problem is, it was screwing up on a Sense ROM as well. I flashed latest CM10 nightly, and managed to squeeze 12kbps transfer on LTE in Miami airport and that was it. But hey, at least for once I saw a 4G icon!
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
For me on sense LTE worked how its supposed to. Never worked right on aosp.
Sent from my EVO using xda premium
For the past couple of months I have been experiencing issues with 3G on both of my Rezounds which are on two separate accounts.
I installed the 4.03.605.2 Global RUU back in September and have been running Vigor360 without issue (except this 3G issue lately).
When I am in a non-4G area, the phones drop to 3G and only shows the UP data arrow, and I don't have any data at all. I have been able to swap the SIM cards between phones, and sometimes I can get 3G to come back temporarily on both Rezounds. I haven't figured out the magic combination though. This proves to me there isn't an issue with the accounts or the device hardware since it does work on occasion.
I have also tried different ROMs based on 4.03.605.2 and I still have the issue.
I have the following radio firmware on both phones:
2.22.10.0801r, 2.22.10.0803r
Does anyone know of other radios I can try, or have any ideas as to why I have so much trouble with 3G?
I have same experience 4G is stable if you have it but 3G not so much
Have you tried switching to only 3g auto prl to see if it helps keep a steady connection?
Sent from my ADR6425LVW using Xparent ICS Tapatalk 2
Strating a new topic to figure out which radio works better on T-Mobile for AT&T JB update.
Before JB update, like several other people on this forum, I have been using i717 on T-Mobile network . 4G has been working fine with GT-N7005-IMM76D-DXLJ2 Rom and UVLG3modemfori717_gt-n7005amss radio.
1. UVLG3 modem with GT7005 amss gives no signal.
2. UVLG3 modem with JB amss gives no signal.
3. Stock radio and amss in JB update only connects to Edge. (unless you are in area where T-Mobile has 3g on 1900?)
4. Blaze ICS modem connects to 4g but signal bars are not shown in status bar.
For the best modem so far, check the below post...
http://forum.xda-developers.com/showthread.php?p=41052527
If anybody else tried any other combinations, please post your experience in this thread.
Thanks.
same here plus i try it with Telus modems too not signal (signal comes and gone)
I made my own combo for WIND in Canada (confirmed to work on T-Mobile with much higher speeds). It's really slow (about 1 Mbps down and 50 kbps up) but at least it works (good voice/signal strength and somewhat usable data)
It's the SGH-T989D (Telus Galaxy S II X) latest modem (TLMC4) and AMSS from the old Blaze modem posted around this forum. Just flash it with CWM.
http://speedy.sh/uyHBp/SGH-T989D-TLMC4-amss-from-blaze.zip
Steps:
1. Flash in CWM
2. On reboot, do a network scan
3. Open dialer, dial *#2263# and select WCDMA Prefs -> WCDMA 1700
4. Do network scan again, WIND (or whatever your AWS provider is) should appear. Select it and it should register.
5. You can multi task back to the service mode and go back and select "[1] Automatic" to use all bands again.
No responsibility if it bricks your phone, it works on my SGH-i717R without issues
OT: I also tried SGH-T989D_TLMC4_radio.zip and it works on Bell/Telus/Rogers without any mods. However, trying any T989 combos never really worked (some did, but data kept dropping).
windroidHD said:
Strating a new topic to figure out which radio works better on T-Mobile for AT&T JB update.
Before JB update, like several other people on this forum, I have been using i717 on T-Mobile network . 4G has been working fine with GT-N7005-IMM76D-DXLJ2 Rom and UVLG3modemfori717_gt-n7005amss radio.
1. UVLG3 modem with GT7005 amss gives no signal.
2. UVLG3 modem with JB amss gives no signal.
3. Stock radio and amss in JB update only connects to Edge. (unless you are in area where T-Mobile has 4g on 1900?)
4. Blaze ICS mpdem connects to 4g but signal bars are not shown in status bar.
If anybody else tried any other combinations, please post your experience in this thread.
Thanks.
Sent from here.
Click to expand...
Click to collapse
This is an important thread for this forum. I'm in the same situation, utilizing the AT&T rom on an AT&T device, and trying to use it on T-Mobile.
My experience has been strange. I am using the stock firmware radio with the AT&T JB update, and I seem to connect to 4G randomly on T-Mobile, switching between UMTS:3 and HSPAP15. I am usually on Edge more often than "4G". I don't have LTE in my area, and "3G" on 1900 doesn't work on my Wife's Iphone.
I tried the UVLG3 Modem for i717, and got no signal at all.
I haven't tried the Blaze modem. What I want to know, is what is the experience with Blaze when you look at system status? UMTS:3? HSPAP?
I am on stock modem in JB rom right now, shows UMTS3 in status.
Nothing strange about that, it is in UMTS when data is idle, anything else is when data is active.
You only get 3G on T-Mobile if its a "re-farmed" 1900 MHz region, where they moved 3G from AWS to 1900 MHz. If you go outside your zone you will only have 2G.
zivan56 said:
Nothing strange about that, it is in UMTS when data is idle, anything else is when data is active.
You only get 3G on T-Mobile if its a "re-farmed" 1900 MHz region, where they moved 3G from AWS to 1900 MHz. If you go outside your zone you will only have 2G.
Click to expand...
Click to collapse
What is HSPAP:15 considered? HSPA 15Mbps? Is that at 1700MHz or 1900Mhz?
crazeco said:
What is HSPAP:15 considered? HSPA 15Mbps? Is that at 1700MHz or 1900Mhz?
Click to expand...
Click to collapse
You would have to go to field test mode to find out, Android does not have such details. Dial *#0011# and find at the very top "RRC: .. BandX," where X is a number. Is it 4 (AWS) or 2 (1900Mhz)?
There may be an item (radio dependant) called DC_HSPA to indicate whether its dual cell HSPA(+). Post a screenshot and I can check it for you.
zivan56 said:
I made my own combo for WIND in Canada. It's really slow (about 1 Mbps down and 50 kbps up) but at least it works (good voice/signal strength and somewhat usable data)
It's the Blaze 4G latest modem (T769-UVMB1) and AMSS from the old Blaze modem posted around this forum. Just flash it with CWM.
http://www.speedyshare.com/YTNEb/T769-UVMB1-amss-from-blaze.zip
Steps:
1. Flash in CWM
2. On reboot, do a network scan
3. Open dialer, dial *#2263# and select WCDMA Prefs -> WCDMA 1700
4. Do network scan again, WIND (or whatever your AWS provider is) should appear. Select it and it should register.
5. You can multi task back to the service mode and go back and select
No responsibility if it bricks your phone, it works on my SGH-i717R without issues
OT: I also tried SGH-T989D_TLMC4_radio.zip and it works on Bell/Telus/Rogers without any mods. However, trying any T989 combos never really worked (some did, but data kept dropping).
Click to expand...
Click to collapse
With the T989D_TLMC4_radio i got the most sickiest DL ever on CM 10.1 but cant make calls only data and text did you think can modify to work on TMO.
BTW right now o using Telus TELL4 modem and work amazing
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Mervingio said:
With the T989D_TLMC4_radio i got the most sickiest DL ever on CM 10.1 but cant make calls only data and text did you think can modify to work on TMO.
BTW right now o using Telus TELL4 modem and work amazing
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
Hmm, can you try this. I've tested it a bit on WIND and data/voice works...the data is slighly more stable/faster (still around 1.5 Mbps/50 Kbps for me)
http://speedy.sh/uyHBp/SGH-T989D-TLMC4-amss-from-blaze.zip
IT works for me on WIND, so it should work on T-Mobile. Same steps as in my previous post above to get it to see AWS carriers. If your T-Mobile service is 1900 MHz, it may just work without any of those steps.
Btw, for some reason it only sees WIND (the modem is non WIND specific) and no other AWS carriers (i.e Mobilicity) when set to WCDMA 1700. No idea why.
I
zivan56 said:
Hmm, can you try this. I've tested it a bit on WIND and data/voice works...the data is slighly more stable/faster (still around 1.5 Mbps/50 Kbps for me)
http://speedy.sh/uyHBp/SGH-T989D-TLMC4-amss-from-blaze.zip
IT works for me on WIND, so it should work on T-Mobile. Same steps as in my previous post above to get it to see AWS carriers. If your T-Mobile service is 1900 MHz, it may just work without any of those steps.
Btw, for some reason it only sees WIND (the modem is non WIND specific) and no other AWS carriers (i.e Mobilicity) when set to WCDMA 1700. No idea why.
Click to expand...
Click to collapse
Tried it, signal strength went from 2 bars with stock modem to 4 bars, status shows UMTS3 when idle and switches to HSPAP:15 briefly.
Speed test
outside the house 7000kbps/1000kbps
Inside the house 1650kbps/66kbps
*#0011# shows rrc band 4, previously it was band 2.
*#2263# doesn't shows any item with * infront, previously automatic had * infront of it.
Tried setting wcdma to 1700 and saw the same performance, rrc band4 and switching between umts3 and hspap:15.
Havn't tested call quality but this has been the best modem so far.
Thanks for sharing.
zivan56 said:
Hmm, can you try this. I've tested it a bit on WIND and data/voice works...the data is slighly more stable/faster (still around 1.5 Mbps/50 Kbps for me)
http://speedy.sh/uyHBp/SGH-T989D-TLMC4-amss-from-blaze.zip
IT works for me on WIND, so it should work on T-Mobile. Same steps as in my previous post above to get it to see AWS carriers. If your T-Mobile service is 1900 MHz, it may just work without any of those steps.
Btw, for some reason it only sees WIND (the modem is non WIND specific) and no other AWS carriers (i.e Mobilicity) when set to WCDMA 1700. No idea why.
Click to expand...
Click to collapse
not sure why but with this ROM (jelly bean) i can lock DC-HSPA8+ and damn it go fast!!!!
this pics are with your modem i will test later today when i go to the mall now works perfect!
Thanks for the help
zivan56 said:
You would have to go to field test mode to find out, Android does not have such details. Dial *#0011# and find at the very top "RRC: .. BandX," where X is a number. Is it 4 (AWS) or 2 (1900Mhz)?
There may be an item (radio dependant) called DC_HSPA to indicate whether its dual cell HSPA(+). Post a screenshot and I can check it for you.
Click to expand...
Click to collapse
I'm now using the Blaze radios posted by Zivan in the link above. I'm getting Band 4 CPCH and FCPH and DCH. Averaging around 3-6Mbps down and 300Kbps up.
crazeco said:
I'm now using the Blaze radios posted by Zivan in the link above. I'm getting Band 4 CPCH and FCPH and DCH. Averaging around 3-6Mbps down and 300Kbps up.
Click to expand...
Click to collapse
Great!!
Mervingio said:
Great!!
Click to expand...
Click to collapse
To be honest, I'm getting better T-Mobile 4g reception with that modified Blaze radio on JB than I did on ICS with UVLG3. Not going to complain!
Anybody managed to get LTE with a JB rom yet?
Question ?.........I picked wcdma 1700 and I'm getting crazy good speeds ....9down 2up..sometimes better What is safe cpu temps? Cause I think it may be heating up
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Wow, good to hear folks...I'm getting rather terrible speeds on WIND. But the phone works, I did a bunch of calling/texting/data usage and its been stable for over a day.
Well I had to reflash for some reason it was picking up excellent speeds then poof gone .. tried changing back to 1900... nothing .. so I reflashed and just picked automatic
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Sorry for the confusing thread title but couldn't figure out how to word it. The issue I'm having is this , I have a normal sense HTC one from T-Mobile that I converted to a official gpe using a ruu and guide found here. From what I've read only the official gpe HTC one on T-Mobile suffers from the lack of being able to receive hspa+ where LTE is lacking, the normal version does not suffer this problem. I know this to be true as prior to converting mine I was always on LTE with great data speeds. However after converting to gpe in certain areas my phone loses LTE and goes to hspa for a brief second and then to 3g or even edge. Now from what I've read the normal HTC one model has the proper radio which prevents this while the official gpe does not. However seeing as the guide I followed he gave me a official gpe with stock recovery and boot loader I'm inclined to believe that this is just a software issue or that since mine is running the official software yet has the right radio to receive hspa+ it can no longer utilize it. As u can probably tell I'm new to all this. If someone can clarify this it would be great and if there is a way to restore hspa+ functionality while keeping gpe stock software on my device that would be great. The gpe is just what I've been after but I hate to suffer data speed loss in certain areas. Any help would be great guys.
i havent updated my htc one to gpe because of this same reason, ive been trying to find out if theres a way around but im a little confused, because normaly this hapens whens the phone doesnt support that type of band, i had a note1 that i flashed a tmob modem and worked 4g, i hope something like that can be made so i ca use gpe with my one :fingers-crossed:
wakeup6621 said:
Sorry for the confusing thread title but couldn't figure out how to word it. The issue I'm having is this , I have a normal sense HTC one from T-Mobile that I converted to a official gpe using a ruu and guide found here. From what I've read only the official gpe HTC one on T-Mobile suffers from the lack of being able to receive hspa+ where LTE is lacking, the normal version does not suffer this problem. I know this to be true as prior to converting mine I was always on LTE with great data speeds. However after converting to gpe in certain areas my phone loses LTE and goes to hspa for a brief second and then to 3g or even edge. Now from what I've read the normal HTC one model has the proper radio which prevents this while the official gpe does not. However seeing as the guide I followed he gave me a official gpe with stock recovery and boot loader I'm inclined to believe that this is just a software issue or that since mine is running the official software yet has the right radio to receive hspa+ it can no longer utilize it. As u can probably tell I'm new to all this. If someone can clarify this it would be great and if there is a way to restore hspa+ functionality while keeping gpe stock software on my device that would be great. The gpe is just what I've been after but I hate to suffer data speed loss in certain areas. Any help would be great guys.
Click to expand...
Click to collapse
Just out of curiosity, the Google edition is not designed to support HSPA+; why do you expect it to do so? I would not expect the software to be designed to work with AWS, even though the radio and radio firmware support it. The GE was designed to work with ATT hardware, and that version of software is not expecting AWS hardware to be installed.
EDIT: You know, I personally think it is stupid for HTC to have two versions of hardware for US operations on GSM. They should have put the same AWS capabilities into both ATT and TMO versions (and GE as well).
stevedebi said:
Just out of curiosity, the Google edition is not designed to support HSPA+; why do you expect it to do so? I would not expect the software to be designed to work with AWS, even though the radio and radio firmware support it. The GE was designed to work with ATT hardware, and that version of software is not expecting AWS hardware to be installed.
EDIT: You know, I personally think it is stupid for HTC to have two versions of hardware for US operations on GSM. They should have put the same AWS capabilities into both ATT and TMO versions (and GE as well).
Click to expand...
Click to collapse
Thats the thing, I dont expect it to. i didnt know this until after i switched over but seeing as the hardware is there im assuming there has to be a way to flash a radio that will allow me to keep the google software and utilize the hardware i have. since im new to this i have no idea where to begin looking for radios.
EDIT: After reading a little more here on the forum I see there are people with Tmobile Htc Ones that have switched to GPE software and are saying they get HSPA+ all the time. Im still confused though because like i said when i was on stock sense software I ALWAYS had LTE. And ever since the switch im either on LTE or I drop to HSPA+ for like two seconds and then stay on 3g. Either my LTE reception is no longer as good as it was on stock sense, or the stock sense was never telling me when i went to a lesser connection. Considering flashing a radio but dont now where to start.
This thread has officially confused me. What exactly is the problem?
I have TMO HTC ONE on GE software and it seems to work on all bands as far as I know perfectly fine? What is the issue we are talking about here?
umrico said:
This thread has officially confused me. What exactly is the problem?
I have TMO HTC ONE on GE software and it seems to work on all bands as far as I know perfectly fine? What is the issue we are talking about here?
Click to expand...
Click to collapse
The issue is that apparantly the tmobile GPE One which you can buy doesnt support HSPA+. I had the stock tmobile one which i converted to GPE and before the swtich I always had lte. Ever since i put GPE on my phone im either on LTE or it drops right to 3g. This led me to believe that even though my htc one doesnt suffer the physical limitation that the bought GPE One has, that of not having acces to HSPA+ bands, that maybe the software of the GPE was limiting mine to HSPA+ as well.
However now im reading that people that have flashed their phones to GPE are accessing HSPA+.
Can i ask you this. When you put GPE on your One, what version did you put on? Did you got to 4.2.2 and update to 4.3? or did you go right to 4.3? and would that make any difference?
wakeup6621 said:
The issue is that apparantly the tmobile GPE One which you can buy doesnt support HSPA+. I had the stock tmobile one which i converted to GPE and before the swtich I always had lte. Ever since i put GPE on my phone im either on LTE or it drops right to 3g. This led me to believe that even though my htc one doesnt suffer the physical limitation that the bought GPE One has, that of not having acces to HSPA+ bands, that maybe the software of the GPE was limiting mine to HSPA+ as well.
However now im reading that people that have flashed their phones to GPE are accessing HSPA+.
Can i ask you this. When you put GPE on your One, what version did you put on? Did you got to 4.2.2 and update to 4.3? or did you go right to 4.3? and would that make any difference?
Click to expand...
Click to collapse
I update about every day for past 4 months. Never wiped clean.
Are you aware that if the device sees a weak, it drops down to 3G/HSPA+ mode. HSPA uses more power then 3G. So when the phone is idle and not pushing mass amounts of data, it sits on 3G. When you push data for a number of seconds, its switches up to HSPA+ then idles back at 3G to use less power...could this be what you are referring to?
On Stock Sense, you will not see this as they hide it in the back ground...where as on GE they tell you the truth
umrico said:
I update about every day for past 4 months. Never wiped clean.
Are you aware that if the device sees a weak, it drops down to 3G/HSPA+ mode. HSPA uses more power then 3G. So when the phone is idle and not pushing mass amounts of data, it sits on 3G. When you push data for a number of seconds, its switches up to HSPA+ then idles back at 3G to use less power...could this be what you are referring to?
On Stock Sense, you will not see this as they hide it in the back ground...where as on GE they tell you the truth
Click to expand...
Click to collapse
Yes maybe that is what was happening because i was never really trying to access the internet, I was just keeping an eye on my phone to see what network it was on.
And I had a feeling that the sense version was just hiding that from me..
Thanks for the help, you pretty much clarified what i needed to know. Now if I can just find out what I have to do in order to receive OTA updates I will be good to go..
Just to add my own 2 cents: I fully converted my TMob HTC One to GPe 4.2.2 last wording just to make sure I could OTA when 4.4 hit.
It updated to 4.3 via OTA just fine and has been on LTE all morning. HSPA+ also seems to work fine when I'm outside the LTE area.
Not sure if that helps at all, but you definitely should be getting LTE and hspa+ if you did a full conversion from a TMob handset.
Sent from my Nexus 10 using Tapatalk 4
PhoenixPath said:
Just to add my own 2 cents: I fully converted my TMob HTC One to GPe 4.2.2 last wording just to make sure I could OTA when 4.4 hit.
It updated to 4.3 via OTA just fine and has been on LTE all morning. HSPA+ also seems to work fine when I'm outside the LTE area.
Not sure if that helps at all, but you definitely should be getting LTE and hspa+ if you did a full conversion from a TMob handset.
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
I realized as previous poster said that it displays 3g when idle. However my signal seems weaker now since converting in areas I had three bars of LTE before switch I get one or two of HEPA+. Have u noticed any reception loss.
Also did u get out with stock mid as I only changed Cid to googlOOO
wakeup6621 said:
I realized as previous poster said that it displays 3g when idle. However my signal seems weaker now since converting in areas I had three bars of LTE before switch I get one or two of HEPA+. Have u noticed any reception loss.
Also did u get out with stock mid as I only changed Cid to googlOOO
Click to expand...
Click to collapse
I did the full conversion - swapped bootloaders, wrote cid/mod (CID to GOOGL000 and MID to PN0710000), and then flashed the GPe RUU for 4.2.2 in fastboot RUU mode.
(I've actually used similar methods for converting this device to dev and international editions as well in the past using only different CID/MID combinations in order to get OTAs).
All conversions have resulted in HSPA+ and LTE connectivity. I've never really been concerned about speeds as they've always been "good enough" for me, but the few speed-tests I've run have always been at least 15mbit or higher (38mbit being the highest I've seen to date).
At some point I'll post the process and CID/MID combinations that have gotten me success on my T-Mobile One. It requires a modified hboot that can be scary at points (no screen, have to hold the power button for *ages* to get it into RUU mode, etc), but gets the job done.
PhoenixPath said:
I did the full conversion - swapped bootloaders, wrote cid/mod (CID to GOOGL000 and MID to PN0710000), and then flashed the GPe RUU for 4.2.2 in fastboot RUU mode.
(I've actually used similar methods for converting this device to dev and international editions as well in the past using only different CID/MID combinations in order to get OTAs).
All conversions have resulted in HSPA+ and LTE connectivity. I've never really been concerned about speeds as they've always been "good enough" for me, but the few speed-tests I've run have always been at least 15mbit or higher (38mbit being the highest I've seen to date).
At some point I'll post the process and CID/MID combinations that have gotten me success on my T-Mobile One. It requires a modified hboot that can be scary at points (no screen, have to hold the power button for *ages* to get it into RUU mode, etc), but gets the job done.
Click to expand...
Click to collapse
I'm fully converted to 4.3 gpe like I said I've only changed Cid to that of gpe. I was worried about not receiving it's updates but have read posts which confirm u can get then without changing mid. I was just wondering I'd after u received ota if your data speeds were better. Its hard to tell because while on stock sense I always displayed LTE as it apparently doesn't let you know when u switch networks. Noe on gpe I'm only getting hspa+ or 3g in areas which according to T-Mobile coverage maps I should get LTE I'm wondering I'd thid was always the case and I just didn't know. My speeds are sufficient for web browsing and YouTube everywhere I'm just the type that wants to know what is happening andbifbi can make it better I will do so. I've reqd of people getting better LTE after converting and then receiving 4.3 ota. This just doesn't seem to be my experience but their so many variables that its hard to say. Thanks for input though
wakeup6621 said:
I'm only getting hspa+ or 3g in areas which according to T-Mobile coverage maps I should get LTE I'm wondering I'd thid was always the case and I just didn't know.
Click to expand...
Click to collapse
I'm pretty sure T-Mobile doesn't show LTE coverage on their maps (there's a lot of gaps so this is for PR reasons). "4G" is either HSPA+ or LTE coverage on T-Mobile's maps, but they do not distinguish. The stock ROM (sense) will display "4G" for HSPA+ coverage, while the GPE ROM doesn't. It's still the same coverage. I think this is what's happening to you.
To clear up some confusion, all HTC One versions support HSPA+. It's a question of which frequencies they support it on. The GPe and Dev edition do not support Band 4 HSPA+ (AKA 1700 Mhz, or AWS). T-Mobile uses AWS HSPA+ on a majority of their "4G" footprint. Only areas that are getting LTE have Band II (1900 Mhz) HSPA+. This is done in order to free up AWS spectrum for LTE. Even within reframed areas, such as southern CA, AWS HSPA+ coverage is better (as not all towers have been, or it seems will be upgraded to LTE and reframed Band II HSPA+). Therefore the GPe will have significantly worse data coverage.
It's possible that the GPe conversion will disable Band 4 HSPA+ coverage on the T-Mobile variant. This is what the discussion should be about. If you're connected to an LTE tower, nothing should change. The GPe edition supports band 4 LTE, which is what T-Mobile uses anyway It's likely that you didn't have LTE before in these locations, and all that's changed is the display icon. Hope this helps.
theslug said:
It's possible that the GPe conversion will disable Band 4 HSPA+ coverage on the T-Mobile variant. This is what the discussion should be about.
Click to expand...
Click to collapse
I'm a clueless n00b, but my suspicion given all I've read about AWS and the M7 is that a GPE RUU won't disable the band, but the GPE baseband may not be optimized or may otherwise be unable to take advantage of that extra band that's not present in PN07120. If that's the case, I would imagine that flashing a T-Mobile radio onto a PN07130 [T-Mobile] One converted into a GPE would solve the problem and give you coverage identical to a bone stock PN07130.
The main reason I think this is that no one has had any success enabling AWS on the ATT/GPE/Dev variants by flashing T-Mobile radios or RUUs. I doubt you can 'disable' the band at anything lower than a superficial level, and even then I'm betting it's not 'disabling' as much as it is the GPE baseband not being programmed with AWS HSPA in mind.
I'll be in a position to find this out soon, as I'm probably going to sell my AT&T One and get a T-Mobile variant. I have a pretty decent idea of what kind of [crappy] coverage you get on a device lacking AWS (and I'm in a refarmed area).