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.
Related
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!!
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.
Hey all,
So my M8 is currently S-off w/ the super-CID set. It's running the ATT version of Viper 4.3, and I was looking to change roms. Do I need to do anything special (aside from the already done S-CID?)?
Is there any feedback on how reception/SMS/calling are if I switch to an international rom?
Just wanted to make sure everything was clear before making the jump.
Thanks.
You need to update to Lollipop firmware (hboot, radio, etc.) to run the latest ROMs.
Also, if you are using AT&T as your carrier, some folks have had issues with "international" ROMs where you can't receive calls or SMS while on LTE. This is due to some interference with AT&T's implementation of Voice over LTE (which they call "HD Voice) which doesn't play well with non-AT&T ROMs.
No true solution to this. The workaround is to call AT&T and have them turn off "HD Voice" for your account (probably need to talk to tech support, as first tier customer support probably won't know what you are talking about). This is not a bad workaround (at least for the time being), since to my understanding, both parties on a call need to have HD Voice compatible phones, and have it enabled on their accounts, for the feature to work; and not that many folks have compatible phones at this time.
Another workaround is to turn off LTE in settings. But obviously, this is less desirable than the previous workaround, as you miss out on LTE data speeds.
Other than this (AT&T caused fluke), there should be no significant reception difference when using an international ROM. In fact, the Viper ROM you are on supports AT&T, but its actually not (AFAIK) AT&T base. Its probably "international" base (software x.xx.401), but with AT&T build.prop and APN added.
I've been running "international" based ROMs (Skydragon Sense and LeeDroid) for some time now with no issues. Part of that, I'm guessing that AT&T never turned on "HD Voice" for my account.
redpoint73 said:
You need to update to Lollipop firmware (hboot, radio, etc.) to run the latest ROMs.
Also, if you are using AT&T as your carrier, some folks have had issues with "international" ROMs where you can't receive calls or SMS while on LTE. This is due to some interference with AT&T's implementation of Voice over LTE (which they call "HD Voice) which doesn't play well with non-AT&T ROMs.
No true solution to this. The workaround is to call AT&T and have them turn off "HD Voice" for your account (probably need to talk to tech support, as first tier customer support probably won't know what you are talking about). This is not a bad workaround (at least for the time being), since to my understanding, both parties on a call need to have HD Voice compatible phones, and have it enabled on their accounts, for the feature to work; and not that many folks have compatible phones at this time.
Another workaround is to turn off LTE in settings. But obviously, this is less desirable than the previous workaround, as you miss out on LTE data speeds.
Other than this (AT&T caused fluke), there should be no significant reception difference when using an international ROM. In fact, the Viper ROM you are on supports AT&T, but its actually not (AFAIK) AT&T base. Its probably "international" base (software x.xx.401), but with AT&T build.prop and APN added.
I've been running "international" based ROMs (Skydragon Sense and LeeDroid) for some time now with no issues. Part of that, I'm guessing that AT&T never turned on "HD Voice" for my account.
Click to expand...
Click to collapse
Awesome man, thank you for the feedback.
Yeah, I'l check and see if I have VoLTE enabled on my account or not, usually their calls don't take long at all so that's good.
I ran the ATT Skydragon before, and it was awesome. The only thing I miss is the 3-dot menu button on the nav-bar. I gotta figure out a way to add that to any rom. Viper has it enabled by default.
My question/problem. What/why do I have a good 4 bars (of 5 bars) of data signal normally, but, when I decide to dial and make a telephone call, the signal strength goes to barely one bar as soon as I hit the dial button on the phone? I have not moved myself or the phone's location. The call may dial, but goes in and out and, more often than not, drops the call. At the same time, if I receive a call from someone, it is normally a much better signal, and does not drop or go in and out.
I am on Verizon phone (vs996) Frankenstein to us998 30b (pie). I have recently tried android 10 roms (Havoc, POSP). I don't know if that has anything to do with it or not? Very frustrating when trying to call someone.
Any thoughts or explanations or, hopefully, fixes?
Thx
gimpy1 said:
My question/problem. What/why do I have a good 4 bars (of 5 bars) of data signal normally, but, when I decide to dial and make a telephone call, the signal strength goes to barely one bar as soon as I hit the dial button on the phone? I have not moved myself or the phone's location. The call may dial, but goes in and out and, more often than not, drops the call. At the same time, if I receive a call from someone, it is normally a much better signal, and does not drop or go in and out.
I am on Verizon phone (vs996) Frankenstein to us998 30b (pie). I have recently tried android 10 roms (Havoc, POSP). I don't know if that has anything to do with it or not? Very frustrating when trying to call someone.
Any thoughts or explanations or, hopefully, fixes?
Thx
Click to expand...
Click to collapse
If you are using Verizon on US998 firmware, then you don't have access to VoLTE (which is phone calls over LTE, Voice over LTE). LTE started out as a data-only service but for actual phone calls, carriers were still using 3G HSPA or CDMA (Verizon, Sprint). When making a phone call, phones temporarily bump down to 3G, and then jump back to LTE after the phone call is over.
With the VoLTE protocol, that finally allowed phone calls with LTE. It added VOICE capability to LTE.
However, different carriers treat VoLTE differently. T-mobile allows VoLTE and Wi-Fi calling for US998 phones, while AT&T and Verizon are more stingy. They reserve VoLTE mostly for their branded phones running their carrier firmware.
I'm an AT&T customer and I've never had VoLTE because I've never used a branded AT&T phone. For me, on AT&T, when I make a phone call I am bumped down temporarily to AT&T HSPA. Then, after the phone call, it jumps back to LTE.
If I were to flash the AT&T TWRP flashable zip, possibly I could enable that. But it's not just firmware, it's also a setting on the carrier side that has to be enabled.
Bottom line, what's happening is you are seeing you STRONG LTE signal. But when you make a phone call, you are being temporarily bumped down to Verizon CDMA. However, Verizon is in the process of dismantling all their CDMA towers. That's why your CDMA signal is so weak. Verizon plans to shutdown CDMA entirely by end of 2020. After that, you will need VoLTE to make phone calls on Verizon.
Since you have an actual VS996, you can flash the VS996 TWRP-flashable zip. Once on that firmware, see if VoLTE is enabled on your account (carrier side setting) and see if when you make phone calls you stay on LTE and are not bumped down to CDMA?
Thx, Chazz. So, it's a Verizon thing? Not necessarily something I caused by going back and forth trying out the different Android 10 roms. Good to know. I will try the 996 rom later today, since I don't need the Hotspot for a couple of days. As always, you've been very helpful, thx. :good:
gimpy1 said:
Thx, Chazz. So, it's a Verizon thing? Not necessarily something I caused by going back and forth trying out the different Android 10 roms. Good to know. I will try the 996 rom later today, since I don't need the Hotspot for a couple of days. As always, you've been very helpful, thx. :good:
Click to expand...
Click to collapse
Yes, especially if you see strong LTE signal before making the phone call. Control freak Verizon (mostly) only allows VoLTE on Verizon firmware with Verizon branded phones. There may be exceptions (maybe Pixel phones?) and I know the ZTE Axon 7 (not a branded Verizon phone) somehow got VoLTE not only on ZTE stock firmware but also on LOS ROM -- but I believe ZTE paid Verizon to allow that. It's the exception that proves the rule.
Here's a a more in depth article about Verizon CDMA being shut down end of this year.
https://grantcountyreview.com/content/verizon-wireless-postpones-its-shutdown-3g-cdma networks
when Verizon closes its 2G and 3G networks at the end of 2020, 3G phones will become obsolete and non-VoLTE LTE phones will not be able to make or receive calls.
Click to expand...
Click to collapse
You DO have a Verizon VoLTE capable phone -- a Verizon VS996 -- but for V30 only on Verizon firmware. If you were using T-mobile with US998 firmware, you would have no problems with VoLTE or Wi-Fi calling. T-mobile is more open than Verizon about such perks.
I don't get VoLTE with AT&T on US998 firmware, but AT&T has no plans to end 3G HSPA anytime soon.
Chazz, I thought I would give a quick update. Late Last night/early this morning, I switched to vs99630c. I have made two phone calls, one to Florida, one to Washington state. Both connected and sounded so much better than when with the us99830b Rom. Even though both dialers had a little HD in the upper left hand corner. This Rom kept the same 3 or 4 bar designation for the signal strength. Much happier with it. Even though I don't have a hotspot (may have to pay the $10(?)or so to set it up, if I decide to stay on here.
Also, I have just seen a 99630c debloated Rom someone has made, that I might try in the next day or so.
I so wanted to try the android 10 Roms, but I just had too many small issues (reboots, no hot spot, system ui crashes, etc.).
Thnx, again for your help and guidance.
gimpy1 said:
Chazz, I thought I would give a quick update. Late Last night/early this morning, I switched to vs99630c. I have made two phone calls, one to Florida, one to Washington state. Both connected and sounded so much better than when with the us99830b Rom. Even though both dialers had a little HD in the upper left hand corner. This Rom kept the same 3 or 4 bar designation for the signal strength.
Much happier with it. Even though I don't have a hotspot (may have to pay the $10(?)or so to set it up, if I decide to stay on here.
Also, I have just seen a 99630c debloated Rom someone has made, that I might try in the next day or so.
I so wanted to try the android 10 Roms, but I just had too many small issues (reboots, no hot spot, system ui crashes, etc.).
Thnx, again for your help and guidance.
Click to expand...
Click to collapse
Then you are now probably using Verizon VoLTE, which is using LTE signal -- not the increasingly degraded CDMA signal Verizon will completely shut off December 31, 2020.
Verizon is probably already deprecating those towers -- leaving just enough, like when you're on the highways.
ChazzMatt said:
Then you are now probably using Verizon VoLTE, which is using LTE signal not the increasingly degraded CDMA signal Verizon will completely shut off December 31, 2020.
Verizon is probably already deprecating those towers -- leaving just enough, like when you're on the highways.
Click to expand...
Click to collapse
I really want volte and vowifi for my unlocked us998. The only way to have that is to flash the vs rom, which is 30c? I'm on US99820h, what do I lose by going to the vs rom? Is there a vs 20h variant?
ldeveraux said:
I really want volte and vowifi for my unlocked us998. The only way to have that is to flash the vs rom, which is 30c? I'm on US99820h, what do I lose by going to the vs rom? Is there a vs 20h variant?
Click to expand...
Click to collapse
Yes, we have Oreo VS996 KDZ. It's actually "20k", because it took Verizon two attempts to fully release LG V30 Oreo. And they released a couple extra updates for Verizon related bugs. So, although it's equivalent to US998 20h, it's a higher letter.
https://forum.xda-developers.com/lg-v30/development/vs996-lg-v30-verizon-vs996-t3865398
You need to have VoLTE enabled in your Verizon account, besides flashing this firmware. It helps to have it already enabled from a Verizon branded phone. But sometimes a helpful store rep willing to bend the rules can do it for you.
ChazzMatt said:
Yes, we have Oreo VS996 KDZ. It's actually "20k", because it took Verizon two attempts to fully release LG V30 Oreo. And they released a couple extra updates for Verizon related bugs.
https://forum.xda-developers.com/lg-v30/development/vs996-lg-v30-verizon-vs996-t3865398
You need to have VoLTE enabled in your Verizon account, besides flashing this firmware. It helps to have it already enabled from a Verizon branded phone. But sometimes a helpful store rep willing to bend the rules can do it for you.
Click to expand...
Click to collapse
I thought the Pie variants were not great, lots of broken features? Or was that just the US998 versions? What were the tradeoffs to staying on Oreo?
ldeveraux said:
I thought the Pie variants were not great, lots of broken features? Or was that just the US998 versions? What were the tradeoffs to staying on Oreo?
Click to expand...
Click to collapse
You asked for Verizon Oreo equivalent to US998 20h and that's what I gave you.
I'm not recommending Pie for US998.
Verizon Pie may be a lot better. I don't know. Someone using Verizon Pie will have to answer.
ChazzMatt said:
You asked for Verizon Oreo equivalent to US998 20h and that's what I gave you.
I'm not recommending Pie for US998.
Verizon Pie may be a lot better. I don't know. Someone using Verizon Pie will have to answer.
Click to expand...
Click to collapse
I misread, somehow thought the ROM you linked was Pie. My bad. I know dirty flash is never recommended, but could I get away with it here? What do I lose by going with the VS ROM over the US998? Apparently the only things I have to gain are VOLTE and possibly VVM?
ldeveraux said:
I misread, somehow thought the ROM you linked was Pie. My bad. I know dirty flash is never recommended, but could I get away with it here? What do I lose by going with the VS ROM over the US998? Apparently the only things I have to gain are VOLTE and possibly VVM?
Click to expand...
Click to collapse
Do you have VoLTE already enabled in your Verizon account?
You'll lose the no bloatware experience, but you can fix that with Titanium Backup.
As for dirty flashing, you can try... If it doesn't work, then you have to factory reset and clean install. Don't forget to reflash Magisk.
ChazzMatt said:
Do you have VoLTE already enabled in your Verizon account?
You'll lose the no bloatware experience, but you can fix that with Titanium Backup.
As for dirty flashing, you can try... If it doesn't work, then you have to factory reset and clean install. Don't forget to reflash Magisk.
Click to expand...
Click to collapse
I logged into my VZW account and after 8745 menus, finally found the HD Voice section. It says it's "Active", so I should be good for the VS ROM yes?
ldeveraux said:
I logged into my VZW account and after 8745 menus, finally found the HD Voice section. It says it's "Active", so I should be good for the VS ROM yes?
Click to expand...
Click to collapse
Seems like, yes.
I had to do a few steps to manually activate HD/VOLTE on my VS996 phone when I was on VZ. I documented the steps somewhere here (using ShortcutMasterLite). I know at least one other member here used the same steps on his phone. I'm thinking you'll be fine once you're on VS996.
I have not switched to Pie... still running Oreo. I have heard too many issues with Pie, so I have no desire to bother. I can't imagine VZ's Pie release is any better than Pie US998. VZ is too lazy to do anything else right, so why would they bother fixing what's wrong on US998.
Just want to quickly update this thread. I dirty flashed the VS99620K.zip in TWRP, then immediately flashed the latest Magisk zip. Everything updated perfectly, installed about 10 VZ apps, and I now have VOWIFI (and can send/receive texts!), though haven't been able to check VOLTE as I'm currently in a dead zone.
I'd already had HD calling active on my account, but can't select the option to also enable Video Calling. It says I need to contact support. I chatted multiple times with VZ support who claim it's active, though every time I try to enable it, it gives me the same error. What is this option, and do I need it? I'm pretty sure I was able to use Duo, Skype, Zoom, etc before the ROM update, am I spinning my wheels here?
Also, independent of this upgrade, my motion GIFs in any text app don't move. I thought it might have something to do with the non-VZ specific kernel, but after flashing, still just shows a static picture.
ldeveraux said:
I'd already had HD calling active on my account, but can't select the option to also enable Video Calling. It says I need to contact support. I chatted multiple times with VZ support who claim it's active, though every time I try to enable it, it gives me the same error. What is this option, and do I need it? I'm pretty sure I was able to use Duo, Skype, Zoom, etc before the ROM update, am I spinning my wheels here?
Click to expand...
Click to collapse
Are you the account holder? Some people can't get to it as they are just user.
https://community.verizonwireless.c...video-calling-feature-is-disabled/td-p/853001
I'm not sure what Verizon video calling is. I'm guessing some Verizon-only video chat -- like Apple's FaceTime is only for iOS? If you are already using Duo, Skype, Zoom, it would seem you don't need it. But you do make sure you have voice over LTE (VoLTE, called "HD calling" Verzion) --before end of this year.
ChazzMatt said:
Are you the account holder? Some people can't get to it as they are just user.
https://community.verizonwireless.c...video-calling-feature-is-disabled/td-p/853001
I'm not sure what video calling is. I'm guessing some Verizon-only video chat -- like Apple's FaceTime is only for iOS? If you are already using Duo, Skype, Zoom, you don't need it. But you do need to get voice over LTE.
Click to expand...
Click to collapse
I am the only user on this account, so definitely the account holder. After more wasted chats with VZ, they said that since my phone is not VZ branded, it's not eligible for Video Calling, which apparently is exactly as you described; Facetime for non-iphone Verizon users. I don't need that, as you said all my other platforms work fine.
How do I determine if VOLTE works? Like I said, I'm in a dead zone now, but going out to a good cell region in a few hours and can check then somehow. I did confirm that I can make calls and text over WiFi, so that's half the battle. How to check VOLTE?
ldeveraux said:
How do I determine if VOLTE works? Like I said, I'm in a dead zone now, but going out to a good cell region in a few hours and can check then somehow. I did confirm that I can make calls and text over WiFi, so that's half the battle. How to check VOLTE?
Click to expand...
Click to collapse
I think if you have Vo-WiFi that means your VoLTE is also activated. They seem to be packaged together.
If you make a call in a good signal area, see if the "4GLTE" icon stays on when you make the call. It may even change to VoLTE icon? or HD calling icon? A Verizon user can probably tell you better. But the key is to see if there are any status bar icon changes and what they are. Also see if there is any information in the dialer GUI during the call, where you click on the dialer timer.
Yeah, don't talk to VZ. They're too stupid to help and downright liars. Your phone will work fine on their network even if it's not VZ branded (I've used US998 and H931 phones on VZ without issue).
On my phone, I did have to do some setting changes in SML (ShortcutMasterLite) to get VOLTE working. I don't think most people have to do that, but I did... and I agree, I think that got VOWIFI working as well. I'm guessing you have both, too... just need to try it. If not, you can force-activate it as I documented earlier (via SML).
I'm pretty new to both rooting and this website, so I apologize in advance for any newbie mistakes I'm gonna make.
Background:
I have a VS-996 which frankensteined and unlocked by following this post . After doing that I flashed pie and then flashed lineage os from here . That rom wasn't very stable and kept crashing, so I tried others. I wound up going with Havoc OS. I believe it was in 3.4 when I first flashed it. I've kept up with the updates up to 3.7.
The Problems:
Havoc OS works fine for me, very stable, except for some reason phone calls and messages(both sms and MMS) are spotty at best. Sometimes texts won't send at all, or they'll act like they sent but the text won't be recieved. Sometimes my phone will say I can make emergency calls only. Group messages and sending pictures don't seem to work at all, at any time. These issues seem most prevalent immediately after booting my phone up. Data works perfectly except sometimes when the phone doesn't like to register that the SIM is inserted for a little bit after booting up.
What I've tried:
I've tried reinstalling the rom.
I've tried installing different Android 10 roms.
I've tried going through the process again starting at the the Frankenstein method and going from there.
I've tried messing with the apn
If I flash back to a stock pie ROM everything goes back to working perfectly, and I'm using my sim in my old V20 while I try to sort this out, so I know the SIM is not to blame.
I've been unable to find anybody else with this particular problem, though that could just be because the problems cover so many different aspects that I'm not sure exactly how to search for answers.
Any help is appreciated, thanks.
olliethehobo said:
Havoc OS works fine for me, very stable, except for some reason phone calls and messages(both sms and MMS) are spotty at best. Sometimes texts won't send at all, or they'll act like they sent but the text won't be recieved. Sometimes my phone will say I can make emergency calls only. Group messages and sending pictures don't seem to work at all, at any time. These issues seem most prevalent immediately after booting my phone up. Data works perfectly except sometimes when the phone doesn't like to register that the SIM is inserted for a little bit after booting up.
Click to expand...
Click to collapse
Are you Verizon customer? You say you have VS996.
There's an LOS ROM bug for Verizon SIM card users where upon rebooting the phone you have to make a phone call first to then receive texts. This phone call "registers" the SIM card or whatever. Many people call their voicemail number to satisfy this requirement.
This bug affects all LOS-based ROMs.
Yes I am a verizon customer. I had noticed that making a phone call seemed to help things along when messages wouldn't send. I guess I managed to let my phone die or turn it off enough to hide the fact that it fixed me. Giving it a test just now it seems to be working correctly. I don't know if I'll be happy or mad if the solution turns out to be this simple.
olliethehobo said:
Yes I am a verizon customer. I had noticed that making a phone call seemed to help things along when messages wouldn't send. I guess I managed to let my phone die or turn it off enough to hide the fact that it fixed me. Giving it a test just now it seems to be working correctly. I don't know if I'll be happy or mad if the solution turns out to be this simple.
Click to expand...
Click to collapse
Was noted extensively on LOS-16 ROMs, but not discussed as much with LOS-17 (Android 10) ROMs. But earlier this month someone in the Havoc 3.7 (LOS-17 based) thread did bring it up...
July 9, 2020
https://forum.xda-developers.com/lg-v30/development/rom-havoc-os-3-3-t4062657/page39
XxD34THxX said:
Would anyone happen to know a fix for the having to make a call on verizon to receive incoming calls/text messages-
It's the main thing preventing me from running any android 10 rom. Have an unlocked (True) US998
Click to expand...
Click to collapse
gimpy1 said:
I don't know of a fix, but, I always called my voice mail to get it to work. I haven't been on a custom room for a little while. I assume that still works, though.
Click to expand...
Click to collapse
However, the larger problem is in six months you will not be able to use LOS-based custom ROMs with V30 on Verizon.
* As of December 31, 2020 Verizon is dropping 3G CDMA to repurpose bandwidth for 5G.
After that date, to make any phone calls on Verizon you will need VoLTE. No LOS-based custom ROMs have VoLTE. You will need stock Verizon firmware. It can be rooted stock firmware; you can use Magisk modules to add features -- but needs to be Verizon firmware for VoLTE.
* T-mobile users are in the same predicament.
In January 2021, T-mobile will be dropping 3G HSPA for same reasons. T-mobile users will need VoLTE, which only comes with V30 stock firmware. However, T-mobile is less stingy. They also allow US998 firmware to have VoLTE and Wi-Fi calling with T-mobile SIM. Whereas Verizon requires Verizon stock firmware, and it needs to have been activated on a phone with Verizon IMEI at some point.
* AT&T will also eventually drop 3G HSPA -- but not until February 2022 (18 months from now).
So, for U.S. V30 owners who wish to run custom ROMs a little longer, you should check out AT&T Prepaid. It's a lot cheaper than "regular" AT&T, but is only for people who own their phones.
18 months is a long time. Anything can happen in 18 months!
AT&T only gives VoLTE to AT&T IMEI phones, as well as iPhones and some other phones I would never own. I've never used an AT&T branded phone on AT&T. I'm an AT&T customer with three native US998 for myself, my wife, my mother -- so I'll cross that bridge when I come to it in February 2022. Will probably give my mother an AT&T V35. Maybe my wife, too. Also, LG may get their act together and produce a good phone fro the LG V70 or LG V80.
Any Verizon, T-mobile (and Sprint), and AT&T MVNOs (Straight Talk, Ting, etc.) will also be affected by these decisions.
I have a more extensive discussion of this issue here:
All U.S. V30/V3O+/V30S will need stock firmware, not LOS-based custom ROMs. When?
https://forum.xda-developers.com/lg-v30/how-to/s-v30-v3o-v30s-stock-firmware-los-based-t4138223