Okay people, here's the deal. I have tried running multiple versions of multiple ROM's, everything from 4.4.2 bases up to 5.0.2 (CM11-12-nightlies, SkyDragon v20-v40.1, Renovate 5.0- r341- r349, LeeDroid, Broken, MaximusHD, etc). When I flash a ROM I download the ROM and gapps if applicable, perform a Nandroid backup, move Zip files to the phone's memory, always preform a full wipe, sometimes twice just to be sure, and follow the Aroma or TWRP installer promts, and finally, if given the option after finishing, wipe the dalvik/cache. On 99% of these ROM's everything works fine, with the exception of being able to add/edit VPN's and the ability to receive incoming calls. After flash I can receive calls for a few days 50% of the time, then nothing. Some of the ROMs, ie. CM12, won't even show a cellular connection. My cell signal is fine, it's showing 4G LTE, but calls just go straight to voicemail, UNLESS I happen to be talking on the phone when a call comes in. In that instance it allows me to transfer to the incoming call without issue. Last night I got so frustrated that I relocked the device and ran the stock AT&T 4.4.4 RUU. Of course everything is working fine now but I really hate this stock ROM. Here's my current set-up:
Unlocked, rooted with SU 2.46, TWRP recovery 2.8.50, 4.4.4 Firmware, S-on (I CAN NOT S-OFF, I'M POOR ), H-boot 3.19.0.0000, OS/Software 3.42.502.1, Radio/Baseband [email protected] Does anyone have a fix for this or know of a ROM that mimics the Lollipop OS look/feel that works with essentially a stock AT&T M8?? I think I've been as detailed as possible but the device is Gold, if that matters HELP?!?!
bford152 said:
Okay people, here's the deal. I have tried running multiple versions of multiple ROM's, everything from 4.4.2 bases up to 5.0.2 (CM11-12-nightlies, SkyDragon v20-v40.1, Renovate 5.0- r341- r349, LeeDroid, Broken, MaximusHD, etc). When I flash a ROM I download the ROM and gapps if applicable, perform a Nandroid backup, move Zip files to the phone's memory, always preform a full wipe, sometimes twice just to be sure, and follow the Aroma or TWRP installer promts, and finally, if given the option after finishing, wipe the dalvik/cache. On 99% of these ROM's everything works fine, with the exception of being able to add/edit VPN's and the ability to receive incoming calls. After flash I can receive calls for a few days 50% of the time, then nothing. Some of the ROMs, ie. CM12, won't even show a cellular connection. My cell signal is fine, it's showing 4G LTE, but calls just go straight to voicemail, UNLESS I happen to be talking on the phone when a call comes in. In that instance it allows me to transfer to the incoming call without issue. Last night I got so frustrated that I relocked the device and ran the stock AT&T 4.4.4 RUU. Of course everything is working fine now but I really hate this stock ROM. Here's my current set-up:
Unlocked, rooted with SU 2.46, TWRP recovery 2.8.50, 4.4.4 Firmware, S-on (I CAN NOT S-OFF, I'M POOR ), H-boot 3.19.0.0000, OS/Software 3.42.502.1, Radio/Baseband [email protected] Does anyone have a fix for this or know of a ROM that mimics the Lollipop OS look/feel that works with essentially a stock AT&T M8?? I think I've been as detailed as possible but the device is Gold, if that matters HELP?!?!
Click to expand...
Click to collapse
LOL Nothing?!?!
bford152 said:
LOL Nothing?!?!
Click to expand...
Click to collapse
Well, I read your thread yesterday, but I don't really know an answer (which is why I hesitate to respond). I can only guess here.
What I can say, although I'm not a user of CM12, but I believe the hboot you have and radio should be fine with CM12.
However, I have seen some folks using Euro based ROMs having some issues (primarily on LTE it seems) and not getting voice calls, like you.
So as you somewhat guessed, AT&T's network is probably to blame (at least that is my guess) in that some feature of the Euro based ROMs (possibly build.prop?) doesn't play well with AT&T's LTE network. It wouldn't be the first time something like this has cropped up. It seems that AT&T likes to do some (frustratingly) unique things in build.prop from just about every other carrier in the world, that causes headaches on custom ROMs. So if your are hell bent on using CM12, you might try to edit build.prop at least to start, if you are comfortable doing so.
---------- Post added at 10:04 AM ---------- Previous post was at 10:02 AM ----------
bford152 said:
Does anyone have a fix for this or know of a ROM that mimics the Lollipop OS look/feel that works with essentially a stock AT&T M8??
Click to expand...
Click to collapse
You might try a GPE ROM that supports 4.4.4 firmware, and see if the result is any better.
redpoint73 said:
Well, I read your thread yesterday, but I don't really know an answer (which is why I hesitate to respond). I can only guess here.
What I can say, although I'm not a user of CM12, but I believe the hboot you have and radio should be fine with CM12.
However, I have seen some folks using Euro based ROMs having some issues (primarily on LTE it seems) and not getting voice calls, like you.
So as you somewhat guessed, AT&T's network is probably to blame (at least that is my guess) in that some feature of the Euro based ROMs (possibly build.prop?) doesn't play well with AT&T's LTE network. It wouldn't be the first time something like this has cropped up. It seems that AT&T likes to do some (frustratingly) unique things in build.prop from just about every other carrier in the world, that causes headaches on custom ROMs. So if your are hell bent on using CM12, you might try to edit build.prop at least to start, if you are comfortable doing so.
---------- Post added at 10:04 AM ---------- Previous post was at 10:02 AM ----------
You might try a GPE ROM that supports 4.4.4 firmware, and see if the result is any better.
Click to expand...
Click to collapse
I tried with a few SD builds and same result. I wouldn't even know where to begin to edit build.props. Thanks though
bford152 said:
I wouldn't even know where to begin to edit build.props. Thanks though
Click to expand...
Click to collapse
Yeah, and build.prop might not even fix it. I think AT&T also messes with the signal icons, which screws up some stuff as well (believe it or not).
But you can't possibly be the only one on AT&T trying to use CM12? I have to think this is a known problem.
redpoint73 said:
Yeah, and build.prop might not even fix it. I think AT&T also messes with the signal icons, which screws up some stuff as well (believe it or not).
But you can't possibly be the only one on AT&T trying to use CM12? I have to think this is a known problem.
Click to expand...
Click to collapse
Whats really insane to me is I was running CM12 perfectly fine on my AT&T branded M7 months ago with the same exact setup. Obviously the 4.4.2 updated to 4.4.4 as well did TWRP and SuperUser but those are the only changes other than the device. Oddly enough, Renovate's nightly releases based on Lollipop work fine. No issues at all, and I'm getting better signal than on the official 4.4.4
bford152 said:
Whats really insane to me is I was running CM12 perfectly fine on my AT&T branded M7 months ago with the same exact setup.
Click to expand...
Click to collapse
Maybe AT&T made some specific changes to the radio for Voice Over LTE (VoLTE) in the latest M8 OTA, that isn't playing well with CM12? I know VoLTE was implemented in the OTA, so this is certainly a possibility, now that I think about it.
Unfortunately, if that is the case, downgrading the radio isn't allowed with s-on.
bford152 said:
Oddly enough, Renovate's nightly releases based on Lollipop work fine. No issues at all, and I'm getting better signal than on the official 4.4.4
Click to expand...
Click to collapse
Better signal based on what, dBm?
redpoint73 said:
Maybe AT&T made some specific changes to the radio for Voice Over LTE (VoLTE) in the latest M8 OTA, that isn't playing well with CM12? I know VoLTE was implemented in the OTA, so this is certainly a possibility, now that I think about it.
Unfortunately, if that is the case, downgrading the radio isn't allowed with s-on.
Better signal based on what, dBm?
Click to expand...
Click to collapse
dBm and dB. Yeah the VoLTE thing is the only thing that I can think of. I mean they were lethargic in getting 4.4.4 pushed out bc of it not wanting to play nice, and I'm assuming that's the issue with 5.0.1 siiiiiiiiiince we're the only carrier without it. Still.
bford152 said:
dBm and dB.
Click to expand...
Click to collapse
That is odd, I would not think the same radio with a different ROM would yield better signal in dBm.
I went through the same thing yesterday,. The difference was that I was running ViperOneM8 ROM (and really liked it). I contacted the Venom support folks and they indicated that they are aware and that it's the new AT&T HD voice (VoLTE) causing problems and there is no solution at present. Weirdest thing, I was able to receive calls... but only when I was not on the LTE network. The ROM would not let me select my network. I got some error when I tried that.
I relocked bootloader, ran RUU... then tried installing "HTC_One_M8_Lollipop_5.0.1LRX22C" which I ran in the past with no issues. I was unable to receive calls with this ROM as well. However this ROM does allow me to select between 2G, 3G and 4G (LTE) cellular networks and as long as I selected 2G or 3G, I receive calls just fine. Selecting the LTE option forces all calls directly to voice mail.
Until this gets resolved, looks like I am stuck.
GA_Android said:
I went through the same thing yesterday,. The difference was that I was running ViperOneM8 ROM (and really liked it). I contacted the Venom support folks and they indicated that they are aware and that it's the new AT&T HD voice (VoLTE) causing problems and there is no solution at present. Weirdest thing, I was able to receive calls... but only when I was not on the LTE network. The ROM would not let me select my network. I got some error when I tried that.
I relocked bootloader, ran RUU... then tried installing "HTC_One_M8_Lollipop_5.0.1LRX22C" which I ran in the past with no issues. I was unable to receive calls with this ROM as well. However this ROM does allow me to select between 2G, 3G and 4G (LTE) cellular networks and as long as I selected 2G or 3G, I receive calls just fine. Selecting the LTE option forces all calls directly to voice mail.
Until this gets resolved, looks like I am stuck.
Click to expand...
Click to collapse
This ROM works perfectly with your/mine current setup. I'm on ROM v7.0.1. The only issue? No AT&T visual voicemail.
http://forum.xda-developers.com/htc-one-m8/development/rom-leedroid-one-m8-l-v1-0-5-t3019102
bford152 said:
This ROM works perfectly with your/mine current setup. I'm on ROM v7.0.1. The only issue? No AT&T visual voicemail.
http://forum.xda-developers.com/htc-one-m8/development/rom-leedroid-one-m8-l-v1-0-5-t3019102
Click to expand...
Click to collapse
What is your setup?
Double_a2013 said:
What is your setup?
Click to expand...
Click to collapse
See the original post... it was by me and lists everything but basically it's stock AT&T 4.4.4 S-on.
bford152 said:
See the original post... it was by me and lists everything but basically it's stock AT&T 4.4.4 S-on.
Click to expand...
Click to collapse
I'm in the same boat (S-off thought), and having the same VoLTE issues. Did that ROM work for you?
Double_a2013 said:
I'm in the same boat (S-off thought), and having the same VoLTE issues. Did that ROM work for you?
Click to expand...
Click to collapse
Yuppers, this is the only ROM that has allowed me to receive calls and working WiFi. Been running it for two weeks now. Yet again, no visual voicemail but that's an AT&T issue since they haven't updated to a Lollipop build.
bford152 said:
Yuppers, this is the only ROM that has allowed me to receive calls and working WiFi. Been running it for two weeks now. Yet again, no visual voicemail but that's an AT&T issue since they haven't updated to a Lollipop build.
Click to expand...
Click to collapse
My issue has been I can either receive calls and stuck on HSPA+ or calls go straight to voice-mail and I get an LTE signal. Are you getting a LTE signal?
Double_a2013 said:
My issue has been I can either receive calls and stuck on HSPA+ or calls go straight to voice-mail and I get an LTE signal. Are you getting a LTE signal?
Click to expand...
Click to collapse
A very strong 4G LTE signal AND this is one of the fastest ROM's I've EVER tried. Btw, the battery life is AMAZING. I can easily get a full day and a half of regular use out of one full charge
It may work for your setup, but it did not work for me. The Venom support team would not even waste time troubleshooting (understandable) since it was a known issue/limitation.
GA_Android said:
It may work for your setup, but it did not work for me. The Venom support team would not even waste time troubleshooting (understandable) since it was a known issue/limitation.
Click to expand...
Click to collapse
Dude, I'm not talking about a Venom ROM. I'm using the ROM found here http://forum.xda-developers.com/htc-one-m8/development/rom-leedroid-one-m8-l-v1-0-5-t3019102 LeeDroid has it working fine but ViperOne, SD, Android Revolution, CM12, etc all had the issues you're complaining about. Try it and then thank me. Make a nandroid backup. Worst case scenario? You waste a few minutes and can say "I told you so"
To make this as plain as possible, if your device is on the current AT&T issued 4.4.4 release, LeeDroid's Lollipop/Sense 7 ROM WILL WORK FOR YOU!!
Related
Alright so ill start this of by saying, Picked up my note today and loving it so far. Got it rooted thanks to Da G and getting ready to get into roms.
Anyway im making this thread to see if anyone else has tried anything out on the non-AT&T notes(i.e I717M and what not). So far from what i have read people are developing mostly for the AT&T model and saying its not for bell rogers or telus. Now I have been in the samsung world for a while and when it comes to my galaxy there was always ways around this.
For instance most of my ROMs were made for the international version not my bell version. But as long as I kept a copy of the bell modem on my phone i could just flash that and the ROM worked great. So does anyone have a copy of the bell telus or rogers modem for the note? or know if there all the same?
Another example in the galaxy s world was the captivate(Same soft keys as our phones). A person with a captivate could flash an international ROM as long they made a soft key fix when they developed the ROM.
One of the main reasons I ask all of this is because i see so many N7000 ROMs up and running and am wondering what will and wont work.
Look forward to hearing from you all
adamtrace said:
For instance most of my ROMs were made for the international version not my bell version. But as long as I kept a copy of the bell modem on my phone i could just flash that and the ROM worked great. So does anyone have a copy of the bell telus or rogers modem for the note? or know if there all the same?
Click to expand...
Click to collapse
you can get all the carrier radio/modem, and even the kernel from carrier here:
http://forum.xda-developers.com/showthread.php?t=1506212
---------- Post added at 02:08 AM ---------- Previous post was at 02:05 AM ----------
and here: http://forum.xda-developers.com/showthread.php?t=1630843
---------- Post added at 02:10 AM ---------- Previous post was at 02:08 AM ----------
sorry, I also forgot this kernel: http://forum.xda-developers.com/showthread.php?t=1589389
Bell note here. Been. The at & t roms with no problem.
The only issue that I have is the Yellow Pages crap that appears in my contact list as well as at& t bloat depending on the rom. Easy enough to deal with though.
Aside from that, it's been perfect.
Currently on Team Perfection 4.0.4.
Sent from my SAMSUNG-SGH-I717 using xda premium
I forgot to add that I haven't had any issues with data speeds at all.
Also, Don't venture into the N7000 roms because they will not work.
Sent from my SAMSUNG-SGH-I717 using xda premium
The N7000 ROMs can hard brick your phone since the hardware if the two models are completely different. AS Far as ROMs go, most are based off the AT&T software simply because that's the only ICS leak we have available. But you can use any ROM for the i717 on your Bell Note. I have a Bell Note and flashed almost every ROM and never ran into any problems. Also, Ruth the help ofa lot of people on this sure, I've made stock images of the Bell, Telus, and Rogers Notes so we can always go back. Best if luck and don't hesitate to ask anything.
Thanks for the info, I get mine today and was wondering the same thing.
Yesterday I flashed my Rogers Branded Galaxy i717 with Bell Rom and Kernel and have not 1 issue. I chose to flash the rogers i717 with Bell because I use bell mobiletv and this was the only way to get this particular app to work. Again not 1 issue with data or anything else.
No Rooted device either. Just flashed using ODIN.
I'm currently running the UCLE2 Rom on my Rogers i717. I've noticed that I am not getting LTE where I should be. And GPS connectivity is shoddy at best.
I have a second i717 which is stock that is with me to compare (family member).
I am going to flash the Rogers modem to hopefully correct atleast the LTE issue. Anyone know if this would improve my GPS connectivity as well?
For a number of years I have been buying Canadian phones to use on ATT. Canadain ROMs have less restrictions than ATT. For instance tethering and NFC are not locked. Also after rooting my Roger's Note it took under a minute to remove the Rogers branding. (all except splash screen) I was left with a fully optioned unbranded ROM.
I did want to try the stock UCLE2 ROM out of curiosity but I thought it would not install because my phone was not an ATT I717. How did you install it eugenekim618? Personally I would rather wait for the Rogers ICS version. Keep checking everyday to see if it is available.
I have tried quite of a few of the ROMS on here with my Bell i717M, no problems at all so far, other than the "android.phone has stopped working" at startup, I don't know the cause but it only happens at boot.
DO NOT use N7000 roms! But all of the AT&T stuff has worked great for me.
Agoattamer said:
For a number of years I have been buying Canadian phones to use on ATT. Canadain ROMs have less restrictions than ATT. For instance tethering and NFC are not locked. Also after rooting my Roger's Note it took under a minute to remove the Rogers branding. (all except splash screen) I was left with a fully optioned unbranded ROM.
I did want to try the stock UCLE2 ROM out of curiosity but I thought it would not install because my phone was not an ATT I717. How did you install it eugenekim618? Personally I would rather wait for the Rogers ICS version. Keep checking everyday to see if it is available.
Click to expand...
Click to collapse
I followed the posts in the Dev section to Root the phone.
Then installed CWM.
The picked a ROM I thought was good and followed the instructions in it's respective post to install.
I've done a lot of ROM installs for the Dell Streak I used to have and for a Sony Xperia X10.
So I am not totally unfamiliar with the process. Just a matter of getting used to the delivery method for each manufacturer. And then, dealing with the quirks of a ROM that is not 100% for your carrier. Goes with the territory, right?
I tried to read all the posts in a given thread as much as I can.
So you are saying you didn't install the one click odin stock UCLE2 ROM?
Agoattamer said:
So you are saying you didn't install the one click odin stock UCLE2 ROM?
Click to expand...
Click to collapse
No, that doesn't work for non AT&T phones I believe. I tried it, and ODIN recognized the COM, but failed to install. From my readings, can't do the one click install on Rogers since it's not a Rogers ROM.
all custom roms should work no problem, ive flashed tons on my unlocked bell note.
its the stock odin files when you want to make sure you get the proper device.
Hey guys Ive flashed pretty much all the roms I can and some I cant lol. So far my experiances have encountered a few setbacks but nothing substantial and allot if not most of the bugs and glitchs occurring in the first & second gen of roms have been fixed or patched.
As far as roms go as was already mentioned as long as you stay away from n7000 model roms and stick to i727 youll be ok. With at&t roms I always seem to have signal and gps issues. Generally tho I find my signal problem will clear itself up on its own and I believe is actually just just caused by the fresh software 'settling in', even though my signal appears low or fluctuating speed testing always shows Im getting peak d/l & u/l speeds. If the signal doesnt seem to improve flashing the Bell stock modem via cwm always does the trick. Gps usually works great, very fast & accurate, when Im having location issues I use the 'faster fix' app from the market, I dont know about anyone elses experiance but allot of the times theres a problem the gps server isnt set to the normal 'north america pool' but servers Ive never seen before or set to an 'international pool'.
All in all besides signal headaches the only other recurring problems are the inherent and unpredictable random force closing of system apps. It can be pretty random but I find a few constant trouble makers to be at&t software update, android phone. At&t update can be disabled easily under applications in the main settings or I was able to actually remove it using 'rom toolbox's app manager but strangely not with root toolboxs remove system apps. For pretty much all other f/c problems the remedy is a running of 'fix permissions', there are a bunch of ways/apps to do it and Ive found using 'rom manager' works the best meanwhile rebooting into recovery and fixing permissions from there will actually cause more problems.
Ok so those are the most recurring and annoying issues Ive had to name a few but the list is too big to write merely because Ive tried just about every rom right from the sketchiest unstable first releases and everything in between lol so feel free to drop me line if your stuck on a problem cause I might be able to help.
But before I end this novel here lol I just flashed the new 'OnlyOne Beta2' rom from the development section and it runs great. The rom is super stable, very fast and features both fully functional S Voice app and fully functional S Notes app. If you havnt tried S Notes yet its awesome the new functions and abilities totally blew me away so I highly recommend you give this rom a try!
eugenekim618 said:
I'm currently running the UCLE2 Rom on my Rogers i717. I've noticed that I am not getting LTE where I should be. And GPS connectivity is shoddy at best.
I have a second i717 which is stock that is with me to compare (family member).
I am going to flash the Rogers modem to hopefully correct atleast the LTE issue. Anyone know if this would improve my GPS connectivity as well?
Click to expand...
Click to collapse
If you had LTE before and lost it through flashing a custom ROM or whatever then try changing your APN to your Carrier LTE network. If you never had LTE when you bought your phone, probably the seller gave you a wrong sim. tell her to give you a 403 LTE capable sim, the 401 is only 4G.
andronikal659 said:
If you had LTE before and lost it through flashing a custom ROM or whatever then try changing your APN to your Carrier LTE network. If you never had LTE when you bought your phone, probably the seller gave you a wrong sim. tell her to give you a 403 LTE capable sim, the 401 is only 4G.
Click to expand...
Click to collapse
Thanks for the tip. But I got everything running again. I did have LTE to start, and have a LTE sim card. The *#2263* certainly helped. And Flapjaxxx's GPS tools in his ROM helped me get the GPS back up to par.
eugenekim618 said:
Thanks for the tip. But I got everything running again. I did have LTE to start, and have a LTE sim card. The *#2263* certainly helped. And Flapjaxxx's GPS tools in his ROM helped me get the GPS back up to par.
Click to expand...
Click to collapse
ok now I just lost my LTE after flashing new ROM from Seraphim Stratosphere. How did you get it back. I factory wipe everything and flash Rogers modem and it doesn't work. How did you manage to get LTE back? btw I have a Canadian Note with Rogers. the Saurom ROM was canadian and I had LTE too.
andronikal659 said:
ok now I just lost my LTE after flashing new ROM from Seraphim Stratosphere. How did you get it back. I factory wipe everything and flash Rogers modem and it doesn't work. How did you manage to get LTE back? btw I have a Canadian Note with Rogers. the Saurom ROM was canadian and I had LTE too.
Click to expand...
Click to collapse
Try *#2263#
Then force select LTE, and select ALL. That should force the LTE connection. So watch the connection bars. You should see a loss of connection, then reconnect on LTE. Once that is established, do the code again, and just select automatic.
eugenekim618 said:
Try *#2263#
Then force select LTE, and select ALL. That should force the LTE connection. So watch the connection bars. You should see a loss of connection, then reconnect on LTE. Once that is established, do the code again, and just select automatic.
Click to expand...
Click to collapse
When I try dialing it, it says error can't find USSP or something like that... What does this mean?
Just to be clear that im doing the right thing. I go to the dialer and punch the code *#2263#. How do I "force select LTE"? will something popup for me to select it or should I go to settings/ wireless and networks... I don't have those options in "wireless settings", I only have APN settings...
I currently have my rezound unlocked and s-off with a straight talk att sim card, running liquid rom (most current). I have used CDMA workshop to edit nv values that would supposedly get 3g working (no-go). At no point since I have had the rezound on straight talk (even before nv edits) have I been able to send or receive sms, or receive phone calls. I can make outgoing calls and have edge data. I've tried fifty different ROMs and as many or more different "3g fix" hacks, to no avail. I have used probably over 100 different APN settings as well. I am (slowly) downloading all the files I need for a complete downgrade and update (my rez is my only source of internet right now), in hopes that doing that may have some influence in getting things working properly.
Edit: Forgot the most important part, if anyone has any thing that they think may work, please share. I'm willing to try anything at least once.
Bump
I think the bands are the problem so no software can fix hardware problems
I don't think you read my entire post. In not really concerned with data speed, what I want is SMS, MMS, and to recurrence phone calls. Which it should be able to do without any modification.
Anseri said:
I don't think you read my entire post. In not really concerned with data speed, what I want is SMS, MMS, and to recurrence phone calls. Which it should be able to do without any modification.
Click to expand...
Click to collapse
Just flash this
internauta37(dot)altervista(dot)org/how-and-patch-fully-enable-gsm-verizon-cdma-phones-android
If on "stock ROM" it should work without if on other ROM flash this if it doesnt connect automaticly let it sit for a while if it still doesn't reflash
Are you on AT&T or T-Mobile StraightTalk? Have you tried the SIM in another device? The reason I ask is because if you can make an outbound call and get Edge data, that is all you really you need to receive a call and send/receive SMS. MMS is a little more complicated but until you can get the voice and SMS working, I wouldn't even worry about MMS. But I am going to be honest, this sounds more like a SIM or Straight Talk setup issue than a phone issue.
@REV3NT3CH is kind of the expert in using domestic GSM on the Rezound... maybe he can chime in a little bit on this.
Sorry I copied and paste that from another thread
Aly3n said:
Just flash this
internauta37(dot)altervista(dot)org/how-and-patch-fully-enable-gsm-verizon-cdma-phones-android
If on "stock ROM" it should work without if on other ROM flash this if it doesnt connect automaticly let it sit for a while if it still doesn't reflash
Click to expand...
Click to collapse
I'll try this when I get home.
acejavelin said:
Are you on AT&T or T-Mobile StraightTalk? Have you tried the SIM in another device? The reason I ask is because if you can make an outbound call and get Edge data, that is all you really you need to receive a call and send/receive SMS. MMS is a little more complicated but until you can get the voice and SMS working, I wouldn't even worry about MMS. But I am going to be honest, this sounds more like a SIM or Straight Talk setup issue than a phone issue.
@REV3NT3CH is kind of the expert in using domestic GSM on the Rezound... maybe he can chime in a little bit on this.
Click to expand...
Click to collapse
At&t sim
Aly3n said:
Just flash this
internauta37(dot)altervista(dot)org/how-and-patch-fully-enable-gsm-verizon-cdma-phones-android
If on "stock ROM" it should work without if on other ROM flash this if it doesnt connect automaticly let it sit for a while if it still doesn't reflash
Click to expand...
Click to collapse
I'll flash this when I get home. Thanks.
acejavelin said:
Are you on AT&T or T-Mobile StraightTalk? Have you tried the SIM in another device? The reason I ask is because if you can make an outbound call and get Edge data, that is all you really you need to receive a call and send/receive SMS. MMS is a little more complicated but until you can get the voice and SMS working, I wouldn't even worry about MMS. But I am going to be honest, this sounds more like a SIM or Straight Talk setup issue than a phone issue.
@REV3NT3CH is kind of the expert in using domestic GSM on the Rezound... maybe he can chime in a little bit on this.
Click to expand...
Click to collapse
At&t sim.
Aly3n said:
Just flash this
internauta37(dot)altervista(dot)org/how-and-patch-fully-enable-gsm-verizon-cdma-phones-android
If on "stock ROM" it should work without if on other ROM flash this if it doesnt connect automaticly let it sit for a while if it still doesn't reflash
Click to expand...
Click to collapse
I'll flash this when I get home. Thanks.
acejavelin said:
Are you on AT&T or T-Mobile StraightTalk? Have you tried the SIM in another device? The reason I ask is because if you can make an outbound call and get Edge data, that is all you really you need to receive a call and send/receive SMS. MMS is a little more complicated but until you can get the voice and SMS working, I wouldn't even worry about MMS. But I am going to be honest, this sounds more like a SIM or Straight Talk setup issue than a phone issue.
@REV3NT3CH is kind of the expert in using domestic GSM on the Rezound... maybe he can chime in a little bit on this.
Click to expand...
Click to collapse
At&t sim.
Aly3n said:
Just flash this
internauta37(dot)altervista(dot)org/how-and-patch-fully-enable-gsm-verizon-cdma-phones-android
If on "stock ROM" it should work without if on other ROM flash this if it doesnt connect automaticly let it sit for a while if it still doesn't reflash
Click to expand...
Click to collapse
I'll try this when I get home. Thanks
Anseri said:
I'll try this when I get home. Thanks
Click to expand...
Click to collapse
Luck?
I am not sure I understand why all this is necessary... there are two simple prop.build tweaks that need to be done to get GSM to work reliably with most JB/KK ROMs, if you look in the first or second post of ROMs like Vanir and Evervolv you will see a GSM.zip that you can flash to make these changes for you, some newer ROMs make these changes for you on the fly (or so it appears, I do not have a Rezound any longer). This is typically all that is required to make it work, although some NV edits might be needed to tune the radios for better reception, it should have basic functionality with minimal changes.
Make sure you on the latest Hboot and radios, wipe thoroughly, and flash per dev's instructions and look through your ROM thread for any GSM specific settings or changes that need to be made (if you can't find any, ask in the ROM thread to be sure).
I have to go back to wondering if you tested this in a AT&T phone to make sure it works, because this sure sounds like a SIM or activation issue with Straight Talk to me.
It may very well be an issue with straight talk. I used the att sim from their byop kit and don't have an att phone to test it on. I'm still trying to get all of the files downloaded to do a full factory restore to make sure it's not something in my device that's the issue.
Aly3n said:
Luck?
Click to expand...
Click to collapse
I have downloaded the file, but still haven't gotten a chance to flash. I'll update here as son as I get a chance.
So I tried about three different gsm fix zips, including the one Aly3n posted. None of them worked. I have only two options left. Full factory downgrade and restore, and calling straight talk to see what they have to say.
Anseri said:
So I tried about three different gsm fix zips, including the one Aly3n posted. None of them worked. I have only two options left. Full factory downgrade and restore, and calling straight talk to see what they have to say.
Click to expand...
Click to collapse
Did you dirty flash your ROM between each GSM patch flash? If not you didn't have a good starting point for each attempt because your system partition had been modified with each flash...
Clean flash every time.
Anseri said:
Clean flash every time.
Click to expand...
Click to collapse
I would try to find an AT&T phone to test your SIM... I am betting this is a ST issue
Anseri said:
So I tried about three different gsm fix zips, including the one Aly3n posted. None of them worked. I have only two options left. Full factory downgrade and restore, and calling straight talk to see what they have to say.
Click to expand...
Click to collapse
Have let it sit for a while
I have been recently having an issue where no matter what rom i go to i get no data connection above shotty 3g. I can facebook and it will error no connection same in browser and snapchat. when i send mms it flashes 3g and fails to send mms unless im usuing liquid build 11/10 on wi fi. Pac everytime i install fc at startup. Slim i can barely get 3g. Validus is about the same as slim. And of course all the 5.0 builds (minus pa, because i havent tried it yet) i get no solid data. I tried flashing the 11c modem and changing apns. Any suggestions?
fftetf said:
I have been recently having an issue where no matter what rom i go to i get no data connection above shotty 3g. I can facebook and it will error no connection same in browser and snapchat. when i send mms it flashes 3g and fails to send mms unless im usuing liquid build 11/10 on wi fi. Pac everytime i install fc at startup. Slim i can barely get 3g. Validus is about the same as slim. And of course all the 5.0 builds (minus pa, because i havent tried it yet) i get no solid data. I tried flashing the 11c modem and changing apns. Any suggestions?
Click to expand...
Click to collapse
bad sim maybe?
bweN diorD said:
bad sim maybe?
Click to expand...
Click to collapse
How would i test that?
Are you flashing these Roms with your Sim removed? Also what is the signal strength in your area??
There are radio diag tests that can be done to assess your problem as well I believe in the Service menu
fftetf said:
How would i test that?
Click to expand...
Click to collapse
Not sure you can. Carriers usually don't charge for a new one. I would just get a new one from them and asses things after that.
Sent from my G3, Unlocked by Team Codefire
bweN diorD said:
Not sure you can. Carriers usually don't charge for a new one. I would just get a new one from them and asses things after that.
Sent from my G3, Unlocked by Team Codefire
Click to expand...
Click to collapse
I just don't want to take my modified device in and lose my warrenty. Idk if they can tell if i were to call.
pitbull8265 said:
Are you flashing these Roms with your Sim removed? Also what is the signal strength in your area??
There are radio diag tests that can be done to assess your problem as well I believe in the Service menu
Click to expand...
Click to collapse
I flash with my sim in. And if you could point me in the right direction i would appreciate it. I dont mind trying to test. But im a little lost. Currently im running pa 4.4.4 beta and i can get mms to work and what not. I still just get 3g. And it will blink. Ik its more cosmetic but i dont understand the numbers instead
fftetf said:
I flash with my sim in. And if you could point me in the right direction i would appreciate it. I dont mind trying to test. But im a little lost. Currently im running pa 4.4.4 beta and i can get mms to work and what not. I still just get 3g. And it will blink. Ik its more cosmetic but i dont understand the numbers instead
Click to expand...
Click to collapse
The only way I'm aware of to test the sim would be to flash back to 100% stock and see off the radios work properly there.
You could call them for a new sim. They will likely have you do a bunch of useless stuff like FDR. Just lie about anything that would reveal root or modifications. When nothing they try fixes the issue, they should mail you a new sim, when you say its not convenient to stop by the store, that's why you called. Worked for me before anyways.
Sent from my G3, Unlocked by Team Codefire
fftetf said:
I flash with my sim in. And if you could point me in the right direction i would appreciate it. I dont mind trying to test. But im a little lost. Currently im running pa 4.4.4 beta and i can get mms to work and what not. I still just get 3g. And it will blink. Ik its more cosmetic but i dont understand the numbers instead
Click to expand...
Click to collapse
there is also some good advice being posted in this thread http://forum.xda-developers.com/showpost.php?p=57358109&postcount=4
bweN diorD said:
there is also some good advice being posted in this thread http://forum.xda-developers.com/showpost.php?p=57358109&postcount=4
Click to expand...
Click to collapse
Thanks! Good to know
Getting a new SIM isn't too hard. I usually flash my phone back to stock though before I take in. Yeah, it's a pain, but easier than arguing with them in the store.
The last issue I had was my SIM wasn't reporting my device ID correctly. On my Verizon account page, it said that I was using a non-VZW device! This was on my Droid RAZR HD. Apparently, the SIM card got corrupted somehow. Not sure if flashing CM12 on my RAZR HD was the culprit, but the tech support guy on the phone said that the SIM card was sending back a garbled device ID and that's why it happened. He said just go into a store and get a new SIM card if I wanted or he could mail me a new one.
I just went and got a new one. Then, I upgraded to the LG G3 and got an entirely new SIM card. Too funny.
I've got a rooted unlocked s-off AT&T M8. I took the 4.4.4 update, then promptly moved to ARHD 34.0. Didn't realize it at first, but I am no longer able to receive calls while on LTE. (works fine for data, and outgoing calls)
If I force it down to 3g, I'm fine. I also noticed that outgoing calls automatically kick it down to 3g- then learned that LTE calls are not an option yet for AT&T. What I'm trying to figure out is, how was I able to have my stock rom on AT&T in LTE mode and still receive a call?
I've checked all the APN settings and it all is set to recommended parameters on AT&T's website. Is this an Android Revolution HD issue? SIM issue? AT&T issue?
I'm going to have to back out of ARHD if there is no solution here, and that would suck.
thanks.
ARHD 34.0 is Android 5.0 based (software 4.16); not 4.4.4 (software 3.x). You might be experiencing this issue due to firmware mismatch. My advice would be to flash the US Dev Edition RUU or firmware zip to get on the 4.x based firmware, and see if that helps. You can try the Euro 4.16.401 firmware, but my experience the US Dev Edition (4.16.1540) plays better on AT&T (as its designed to work on AT&T's network).
Even with the proper firmware, some folks have also had some random network issues running an "international" based ROM on AT&T's network. Most notably losing Google services while on LTE (possibly due to build.prop differences). So its possible your LTE issue may be related. Not to knock the ROM developers, but devs from Europe and other regions often aren't that familiar with the nuances of AT&T's network.
So if being on the proper firmware still does not resolve the issue, it might be the ROM itself doesn't play well with AT&T in your location.
Thanks Redpoint-
I hadn't considered that and am also shy to using the Dev RUU due to brick risk but will reassess that. (I have to convert my device to GPE to put that on don't I?) I recall some warnings about bricking if I change the ID of my phone and apply the wrong RUU or something- but I'll have to refresh myself on those caveats. Would have been so much simpler if AT&T had just released Lollipop but who knows how long I'd be waiting for that.
Thanks again.
jeremyenos said:
Didn't realize it at first, but I am no longer able to receive calls while on LTE. (works fine for data, and outgoing calls)
If I force it down to 3g, I'm fine. I also noticed that outgoing calls automatically kick it down to 3g- then learned that LTE calls are not an option yet for AT&T. .
Click to expand...
Click to collapse
Voice over LTE (VoLTE) not being available yet should not be the cause. VoLTE is not currently available on most carrier worldwide. Its a very new technology, and deployment is still ongoing in most regions. Only a few Asian countries currently have VoLTE.
That being the case, voice calls should be kicking down to 3G. The lack of VoLTE should not prevent you from receiving calls. As mentioned, I believe the issue is either a firmware mismatch, or ROM not playing well on AT&T's network.
---------- Post added at 10:50 AM ---------- Previous post was at 10:46 AM ----------
jeremyenos said:
Thanks Redpoint-
I hadn't considered that and am also shy to using the Dev RUU due to brick risk but will reassess that. (I have to convert my device to GPE to put that on don't I?) I recall some warnings about bricking if I change the ID of my phone and apply the wrong RUU or something- but I'll have to refresh myself on those caveats. Would have been so much simpler if AT&T had just released Lollipop but who knows how long I'd be waiting for that.
Click to expand...
Click to collapse
No, you don't need to convert to GPE to run Dev Edition RUU. Dev Ed not the same as GPE. Dev Ed is Sense, just without the AT&T branding. The US Dev Edition Lollipop ROM is actually pretty sweet (what I am currently on via RUU).
You won't likely brick the device with RUU unless you run an RUU for the wrong device.
Changing CID is safe as long as you type the command properly.
There is always some tiny risk of a brick if you mess with things s-off, and flashing hboot and radio. But I wouldn't say the risk is any more than installing the OTA (which also replaces hboot and radio) as long as you follow instructions carefully, and do the proper research, and take the proper care while performing the steps.
So thanks redpoint for the advice-
Dev edition RUU installed just fine, and updated my radio and hboot as I had hoped. I go to restore ARHD, and it fails though... even fresh install of ARHD fails with some symlink error. I think after reading up on it that this is due to partition resizing that Dev edition does. So now I can't seem to find a way to get ARHD back on the device. I have no idea what to do to the partitions to restore them to something ARHD can use again if that's the problem, and I can't find anything about it on XDA or elsewhere.
Kind of surprised by this if I'm on the only one hitting the issue... all of the issues. To my knowledge, without a radio update, no AT&T m8 in America with ARHD 34 is going to be receiving incoming calls with LTE enabled. The only way to get a radio update is to use an RUU- of which dev edition is the only one. AT&T/HTC only releasing the 4.4.4 RUU for right now it seems, without the radio and hboot update.
Maybe I've got this all wrong somehow... I can't be the only ARHD m8 AT&T LTE USA user that wants to have incoming calls right? How has anyone else accomplished this?
Stuck with Cyanogenmod for now... slower, less stable than ARHD.
jeremyenos said:
Dev edition RUU installed just fine, and updated my radio and hboot as I had hoped. I go to restore ARHD, and it fails though... even fresh install of ARHD fails with some symlink error. I think after reading up on it that this is due to partition resizing that Dev edition does. So now I can't seem to find a way to get ARHD back on the device. I have no idea what to do to the partitions to restore them to something ARHD can use again if that's the problem, and I can't find anything about it on XDA or elsewhere.
Click to expand...
Click to collapse
You're still misunderstanding about Dev Edition (DE) versus GPE. Only GPE has different partitioning from Sense. DE is still Sense, and has the same partitioning scheme as the stock AT&T (and other carrier) Sense setup.
Don't know why you are having the issues restoring ARHD nandroid and even flashing ARHD. Wipe cache and try to re-install TWRP or try a different version. Then try a "clean install" (factory reset in TWRP) of ARHD.
Or you might have a case where the DE firmware does not play well with ARHD. You can try the 401 firmware, for which ARHD is based. But this might cause as many issues as it solves, as the US DE firmware usually plays better with AT&T's network than the international firmware. But it might be worth a try.
---------- Post added at 11:31 AM ---------- Previous post was at 11:27 AM ----------
jeremyenos said:
The only way to get a radio update is to use an RUU- of which dev edition is the only one. AT&T/HTC only releasing the 4.4.4 RUU for right now it seems, without the radio and hboot update.
Click to expand...
Click to collapse
Since you are s-off, you can flash any carrier's M8 firmware, or flash the radio independently. Although a side note that you should stay away from flashing anything for CDMA (Sprint & VErizon) M8's or dual SIM M8.
If you mean there is no updated LP radio intended for AT&T, aside from the DE RUU that you are currently on; than yes that is correct.
Has this been solved? Im experiencing the same thing. I updated my m8 to the latest at&t lollipop ota. And installed xenon rom. Now i just noticed im not getting any calls. Wife is pissed lol
redpoint had my problem pegged. Just had the wrong rom w/o the radio update I think. I needed to get the developer edition from here. After applying it, I could put ARHD back on and all was good. It's been awhile, but that's how I roughly remember it.
simpl3lang said:
Has this been solved? Im experiencing the same thing. I updated my m8 to the latest at&t lollipop ota. And installed xenon rom. Now i just noticed im not getting any calls. Wife is pissed lol
Click to expand...
Click to collapse
There is no true fix for this, that I know of. Only workaround: turn off LTE in phone settings, or contact AT&T to have HD Voice (what AT&T is calling Voice Over LTE) turned off for your account. The latter is probably the best workaround if you want to continue using non-ATT ROMs; since it allows you to still utilize LTE speeds for data, and HD Voice only works if both parties have devices that support the feature (and many folks don't at this time).
redpoint73 said:
There is no true fix for this, that I know of. Only workaround: turn off LTE in phone settings, or contact AT&T to have HD Voice (what AT&T is calling Voice Over LTE) turned off for your account. The latter is probably the best workaround if you want to continue using non-ATT ROMs; since it allows you to still utilize LTE speeds for data, and HD Voice only works if both parties have devices that support the feature (and many folks don't at this time).
Click to expand...
Click to collapse
thank you for the quick reply. i will call at&t right now. and i will throw in an update.
redpoint73 said:
There is no true fix for this, that I know of. Only workaround: turn off LTE in phone settings, or contact AT&T to have HD Voice (what AT&T is calling Voice Over LTE) turned off for your account. The latter is probably the best workaround if you want to continue using non-ATT ROMs; since it allows you to still utilize LTE speeds for data, and HD Voice only works if both parties have devices that support the feature (and many folks don't at this time).
Click to expand...
Click to collapse
Update: i called, and the nice customer service lady couldnt turn off the feature. She said its part of billing something something. Damn what to do now besides turning off lte.
Should i input some apn or something? Revert radio image to an older one? Go back to kitkat?
simpl3lang said:
Update: i called, and the nice customer service lady couldnt turn off the feature. She said its part of billing something something. Damn what to do now besides turning off lte.
Click to expand...
Click to collapse
Just call again, the CS rep probably just didn't know what they were talking about. I think another user mentioned you need to talk to tech support, not the front line CS reps. Turning off HD Voice with AT&T was confirmed by at least 2 other XDA members to work.
simpl3lang said:
Should i input some apn or something? Revert radio image to an older one? Go back to kitkat?
Click to expand...
Click to collapse
Swapping radios or APNs probably won't help. Not sure about reverting to Kitkat.
redpoint73 said:
Just call again, the CS rep probably just didn't know what they were talking about. I think another user mentioned you need to talk to tech support, not the front line CS reps. Turning off HD Voice with AT&T was confirmed by at least 2 other XDA members to work.
.
Click to expand...
Click to collapse
+1000000000000000000
i guess third time calling is the charm. the first 2 calls i made, they said they couldnt turn it off, saying it was restricted. but the third person i spoke to made me turn my phone off and when it restarted it worked. i can receive calls now.. he said he turned the hd lte off in his side by putting me back to the settings i had before hd voice was added.
thanks again.
edit:
i was actually looking at this prior to making my third call to at&t. maybe it could help others. worth a try? do it at your own risk...
If for some reason the HD Voice Calling option is disabled or inaccessible on your phone after updating to Android 5.1, then you can try the following steps to fix the issue.
Navigate to Settings > More > Cellular Networks and enable the toggle switch for Enhanced 4G LTE Mode. However, if the toggle is missing then follow the steps provided below:
1.Launch the Dialer app on your phone, and dial *#*#4636#*#*.
2.Choose Phone information.
3.Enable or select VoLTE Provisioned Flag.
4.Restart the phone.
5.Go to Settings " More " Cellular networks and toggle the switch for Enhanced 4G LTE Mode, and the HD Voice calling feature should now be activated on your device running Android 5.1.
i got as far as rebooting my phone but the toggle was still missing.
Was working on Insert Coin 4.4.4, flash to OTA 4.16 5.0.2 works fine then I flashed to latest Insert Coin 7.1.9 5.0.2 I tried the following step suggested on post #13 don't see option #3 after click Choose Phone Info.
By calling AT&T turn off HD Voice you'll sacrifice anything?
First call attempt, att technical rep had me turn off phone, 1min later turn it back on and it's working now! Yay!!!
Sent from my HTC One_M8 using Tapatalk
@simpl3lang @redpoint73 Soo glad I found this thread, this was driving me nuts on my m9 running ARHD. When I called ATT they were able to take care of it and turn it off. I cannot find the setting under the *#4636#*, nor under phone settings in ARHD, Is this a setting that developers forget to include in their ROMS?
tc3sean said:
@simpl3lang @redpoint73 Soo glad I found this thread, this was driving me nuts on my m9 running ARHD. When I called ATT they were able to take care of it and turn it off. I cannot find the setting under the *#4636#*, nor under phone settings in ARHD, Is this a setting that developers forget to include in their ROMS?
Click to expand...
Click to collapse
The reason you won't find it in settings, is that "HD Voice" (or I forget what the actual toggle is called) is not a feature on non-ATT ROMs. Its an ATT-specific branding of what is more broadly being calling "Voice over LTE" or VoLTE. Further, most (or at least many) carriers worldwide have not started deploying VoLTE yet (or just starting to do so), so that is another reason why you won't see such a toggle in settings on most ROMs.
Even if such a toggle was present, I'm skeptical whether it would resolve the problem being discussed. It seems there is something unique in the way that ATT is deploying VoLTE, that is screwing with "international" based ROMs. So my hunch is that unless the ATT-specific tweaks are applied, you would still have the voice/SMS issue on LTE.
redpoint73 said:
The reason you won't find it in settings, is that "HD Voice" (or I forget what the actual toggle is called) is not a feature on non-ATT ROMs. Its an ATT-specific branding of what is more broadly being calling "Voice over LTE" or VoLTE. Further, most (or at least many) carriers worldwide have not started deploying VoLTE yet (or just starting to do so), so that is another reason why you won't see such a toggle in settings on most ROMs.
Even if such a toggle was present, I'm skeptical whether it would resolve the problem being discussed. It seems there is something unique in the way that ATT is deploying VoLTE, that is screwing with "international" based ROMs. So my hunch is that unless the ATT-specific tweaks are applied, you would still have the voice/SMS issue on LTE.
Click to expand...
Click to collapse
I can confirm that getting AT&T to turn off HD Voice fixed the issue with me. I installed SkyDragon v10. I had to call twice and go through a lot of crap to get them to do it. The last guy told me he was going to put the "opt-out" code on my number, but that wasn't technically supposed to do it. He said he was putting in that I had "requested" to opt-out (I was taking the line that it just stopped working, as I didn't want to have to deal with any fallout about having rooted and flashed my phone, perhaps that wasn't necessary, idk). So, I think you might take the short cut by saying that you want to opt out of HD voice, and that your "Brother-in-law" just did it, so you know it works. If you stick to your guns, and ask for a technical person and don't let them say no to that, you can definitely get it done.
Thanks to all of the participants on this thread I am out of a tight spot and would like to offer up a few more observations that may be helpful to the next person.
I had an LG G3 running CM13 20160504 that became unstable and I had to replace with my wife's old HTC One m8 also running CM13 20160504 (also tried 20160510 and 20160511) which, like the other phones discussed in this thread, did not get incoming calls, in fact calls did not even roll over to my Google Voice number.
Thanks to this thread I tried forcing the phone to 3g, found that I got calls and then got AT&T to turn of VoLTE (aka HD Voice) and now I can get calls while running with LTE data.
Rather than a fire-hose of details I'll just say that it seems that the G3 would get incoming calls on LTE, and I would not get the first ring then it would ring on what the caller perceived as the second ring. Whenever I was on a call I would note that I was running in 3G, after the call it went back to LTE. I assumed that it was a bandwidth issue but now I think in that lag between the callers first ring and my first ring the phone was negotiating down to a 3G connection like an old school high speed modem negotiating a call with a slower modem (anyone remember those days?). It looks like my HTC does not have the ability to negotiate down or that it was been somehow hardwired not to as there is a flag in the test menu (*#*#4636#*#*) marked "TURN OFF VOLTE PROVISIONED FLAG" which has no effect, i.e. I can press it and the is a visible deflection indicating that the phone knows that the button was pressed but the button text does not change to indicate that a toggle has been effected, calls continue to not ring and even rebooting after pressing does not make any difference.
In summary, having AT&T turn off HD Voice has me working fine with the HTC On m8 on CM13 and I am grateful to all of you for the conversation that got me out of that corner.
Every time I flash a custom ROM based on 4.16.X firmware I either lose LTE (though HSPA+ still works perfectly) or the ability to receive calls. I've tried ARHD, SD, the Stock WWE, and the US DEV edition, and all of them have exactly one of those issues (it's never both). I'm currently back on ATT stock 4.4.4 ROM (3.42.502.1 firmware), rooted, S-Off.
I thought flashing the WWE RUU before flashing a ROM like ARHD would be enough to upgrade the firmware, but maybe I'm missing something.
Double_a2013 said:
Every time I flash a custom ROM based on 4.16.X firmware I either lose LTE (though HSPA+ still works perfectly) or the ability to receive calls. I've tried ARHD, SD, the Stock WWE, and the US DEV edition, and all of them have exactly one of those issues (it's never both). I'm currently back on ATT stock 4.4.4 ROM (3.42.502.1 firmware), rooted, S-Off.
I thought flashing the WWE RUU before flashing a ROM like ARHD would be enough to upgrade the firmware, but maybe I'm missing something.
Click to expand...
Click to collapse
WWE RUU indeed updates the firmware, however to the WWE radio and other firmware.
I think a couple things are going on here (assuming your are on AT&T's network):
1) A number of folks have reported call issues while on AT&T's LTE network and running WWE based custom ROMs. The suspicion is that the changes being made by AT&T in advance of HD Voice (Voice over LTE) deployment is not playing well with Euro based ROMs. AFAIK, there doesn't seem to be a fix for this, although I think some devs like Team Viper are looking into it.
2) US Dev Edition is intended to be used on AT&T's network. However, its not clear from your description, but it seems you are using the WWE firmware (radio probably most importantly) with the Dev Ed ROM. If you haven't already, try the Dev Edition firmware with the Dev Ed ROM; either by RUU or flashing the firmware separately. That is the configuration I was running until just last week (giving Sense 7 a try) and seemed to have no issues on AT&T, including travel to a couple different locations around the country.
redpoint73 said:
WWE RUU indeed updates the firmware, however to the WWE radio and other firmware.
I think a couple things are going on here (assuming your are on AT&T's network):
1) A number of folks have reported call issues while on AT&T's LTE network and running WWE based custom ROMs. The suspicion is that the changes being made by AT&T in advance of HD Voice (Voice over LTE) deployment is not playing well with Euro based ROMs. AFAIK, there doesn't seem to be a fix for this, although I think some devs like Team Viper are looking into it.
2) US Dev Edition is intended to be used on AT&T's network. However, its not clear from your description, but it seems you are using the WWE firmware (radio probably most importantly) with the Dev Ed ROM. If you haven't already, try the Dev Edition firmware with the Dev Ed ROM; either by RUU or flashing the firmware separately. That is the configuration I was running until just last week (giving Sense 7 a try) and seemed to have no issues on AT&T, including travel to a couple different locations around the country.
Click to expand...
Click to collapse
Yeah, I'm on AT&T's network. So I should just download the dev edition ROM from HTC's website and RUU it?
Double_a2013 said:
Yeah, I'm on AT&T's network. So I should just download the dev edition ROM from HTC's website and RUU it?
Click to expand...
Click to collapse
If you don't mind wiping the phone (backup any personal data that you want to keep before RUU, obviously), then yes that is probably the easiest way to do it.
redpoint73 said:
If you don't mind wiping the phone (backup any personal data that you want to keep before RUU, obviously), then yes that is probably the easiest way to do it.
Click to expand...
Click to collapse
I just did; LTE is working, but I can't receive calls. When someone calls me, it goes directly to voice mail without ringing
EDIT:
So I actually got a call to come through. When it did, LTE went away and wouldn't comeback, so it definitely seems like an issue of VoLTE compatibility, even on the Dev Edition ROM for me.
Double_a2013 said:
I just did; LTE is working, but I can't receive calls. When someone calls me, it goes directly to voice mail without ringing
EDIT:
So I actually got a call to come through. When it did, LTE went away and wouldn't comeback, so it definitely seems like an issue of VoLTE compatibility, even on the Dev Edition ROM for me.
Click to expand...
Click to collapse
Weird. I wouldn't think that you would have the issue on Dev Edition ROM, running Dev Edition firmware.
Can you confirm the RUU properly installed the Dev Ed radio, by stating your radio number?
Forgot to mention that turning off LTE is a workaround. But obviously less than ideal.
redpoint73 said:
Weird. I wouldn't think that you would have the issue on Dev Edition ROM, running Dev Edition firmware.
Can you confirm the RUU properly installed the Dev Ed radio, by stating your radio number?
Forgot to mention that turning off LTE is a workaround. But obviously less than ideal.
Click to expand...
Click to collapse
The radio that was installed was 1.24.21331147A1.09G_20.68.4196.01_F
Double_a2013 said:
The radio that was installed was 1.24.21331147A1.09G_20.68.4196.01_F
Click to expand...
Click to collapse
I confirm that is the correct US Dev Edition radio baseband.
Weird, I've used mine (as mentioned) not only in my home area of Boston (and surrounding areas) but also while travelling to North Texas, and Washington State, and didn't see any issues. But that is by no means exhaustive. We really have little way of knowing what changes AT&T is making to their LTE network and where (in preparation for HD Voice).
You might fall back to the AT&T 4.4.4 ROM (and even the corresponding radio) to see what will happen. But that's of course kind of disappointing to fall back to KitKat from Lollipop.
You can even try the WWE firmware (4.16.401) zip. But I'd be very surprised if you get a better result on the WWE radio versus the Dev Edition.