I have an LG G3 Verizon VS985. I recently tried to update stock VS98547A using the LG UP method with VS98547A_01_0314_ARB01.kdz. Everything works great except trying to make or receive a call. Phone shows I have a good signal. But the call won't event connect. Just dialing for a minute then call would end. I do use a t-mobile sim, but voice calls did work when I was on Android 5.1.1 before upgrading to Marshmallow. Also noticed that only the 4Glte symbol only shows on the top of screen. It used to change from edge, hspa and 4g symbols I remember.
I tried going back to stock VS98510B by flashing the TOT file. But that still did not get the voice call to work. Maybe I should have set it to refurbished instead of upgrade when I tried flashing it. Any ideas on how to fix this?
I have same problem , plz help me too
Since I don't use T-Mobile I don't know for sure but maybe you have to add a T-Mobile APN.
roirraW "edor" ehT said:
Since I don't use T-Mobile I don't know for sure but maybe you have to add a T-Mobile APN.
Click to expand...
Click to collapse
I have added t-mobile apn settings, but the I still have not been able to get voice calls to connect. Receiving a phone call goes straight to my voice mail without even ringing on my end. I will try to put a different sim and check if it works. Thanks for the reply Rode Warrior.
You're welcome! Again, just guessing but there are certain radio bands that come disabled by default and can be enabled although I assume it might require root.
There are threads about it in the General and this section. I wouldn't know what you wouldn't have had to do that previously but would have to now, though.
Maybe find one of the T-Mobile threads in these Verizon sections and someone with actual experience using the phone on T-Mobile might be able to help better.
I cant receive and make calls , i cant call on 112 or 911 .
i can receive and sent sms , use wifi and other soft working correctly .
i try to flash tot file, kdz, but result 0
this is a video of problem
sorry for my bad English .
Ha, I have the opposite "problem". The phone makes and receives calls just find but it always says "no service". I change the band back and forth to global and cdma and the signal reappears but only temporarily.
APeter001 said:
Ha, I have the opposite "problem". The phone makes and receives calls just find but it always says "no service". I change the band back and forth to global and cdma and the signal reappears but only temporarily.
Click to expand...
Click to collapse
What sim card were you using? Mine says no service from time to time.
zest0093 said:
I cant receive and make calls , i cant call on 112 or 911 .
i can receive and sent sms , use wifi and other soft working correctly .
i try to flash tot file, kdz, but result 0
this is a video of problem
sorry for my bad English .
Click to expand...
Click to collapse
No problem, your english is just fine. Looks like we have the same problem. I wonder if flashing the tot or kdz file changed the band settings.
roirraW "edor" ehT said:
You're welcome! Again, just guessing but there are certain radio bands that come disabled by default and can be enabled although I assume it might require root.
There are threads about it in the General and this section. I wouldn't know what you wouldn't have had to do that previously but would have to now, though.
Maybe find one of the T-Mobile threads in these Verizon sections and someone with actual experience using the phone on T-Mobile might be able to help better.
Click to expand...
Click to collapse
I am wondering if flashing the tot file altered the radio bands of the phone somehow. It would be great if the VS985 had the hidden menu accessible to change the bands but that seems to be not available at this time.
rei2043 said:
I am wondering if flashing the tot file altered the radio bands of the phone somehow. It would be great if the VS985 had the hidden menu accessible to change the bands but that seems to be not available at this time.
Click to expand...
Click to collapse
I know there's *some* way of enabling the extra bands - people have done it according to the threads about it in these sections.
roirraW "edor" ehT;67969246 said:
I know there's *some* way of enabling the extra bands - people have done it according to the threads about it in these sections.
Click to expand...
Click to collapse
all LTE bands are opened or other bands you mean ?
zest0093 said:
all LTE bands are opened or other bands you mean ?
Click to expand...
Click to collapse
If you find the thread or threads I mentioned, they give all the details. I'm only going from memory since I haven't had a need to enable bands that are normally disabled and I read almost every single post in every Verizon G3 section.
From what I recall, this phone doesn't even contain the necessary hardware for every LTE band out there, but it does have what it takes for some bands (LTE and/or otherwise, again I don't know off the top of my head what ones were available to enable). Somewhere in those threads - I don't even remember if the information was in the OP of those threads - they detail what bands are available on the VS985 (including the ones enabled by default, and what's available to enable). I know I also saw mention of which particularly bands some carriers use.
I check in Verizon Hidden menu all LTE bands ,
and after watching , when Signal losts , i undarstand , signal lost when mobile in active using , mobile temperature are high and when GPS, LTE and other services are active .
I think problem in antenna (motherboard , or other)
Related
After happily using my 'old' S4 on T-Mobile with HSPA+ since having the Note 3 as my primary line, I was naturally excited to update the baseband and unlock Band 4 LTE. However I noticed some caveats which I've now solved which will undoubtedly confuse everyone at some point.
Assuming you've got the correct APN for T-Mo (fast.t-mobile.com) and naturally install the SIM, if your phone is on global you will happily see working LTE but not so fast (no pun intended). If you call or text, it fails. If you quick check your About -Status in settings and look under network it will say say Unknown and not T-Mobile. Why? Essentially you're in LTE data only mode because by default the baseband is looking to connect to CDMA for everything else in the CDMA/LTE marriage that is Verizon unique, which obviously won't work here. The assumption otherwise is that you will only need GSM if traveling internationally so it never looks for LTE with GSM.
The quick easy fix is to drop out of Global back to the GSM/UMTS setting, which will bring everything back, network restored to T-Mobile, but now it won't use LTE again, lame.
Luckily there is a fix. Use the PhoneInfo app or however you prefer to get to the Testing App. Under device information change the dropdown to LTE/GSM (auto PRL). Toggle airplane mode or restart. When it comes up you should be on LTE and quick check settings again you'll see T-Mobile, and everything will work. So far this seems to hold pretty well.
EDIT: Note: This works for TW Roms. I have not had success in CM10.2. In CM I've only gotten LTE data (wrongly labeled Verizon) and nothing else. Doesn't even pick up my phone number regardless of settings used.
Can you send me the link to the TW rom you are using for this? Thanks!
A walk through would be nice
Sent From The Future
majorlag said:
Can you send me the link to the TW rom you are using for this? Thanks!
Click to expand...
Click to collapse
Just stock actually. Nothing special.
killajoe said:
A walk through would be nice
Sent From The Future
Click to expand...
Click to collapse
Use this app, hit Device Information, and change the dropdown to LTE/GSM (auto PRL). Given the simplicity not sure you need much more of a walk through than that. A video would require a bunch of editing to blot out IMEI and phone #s.
zepfloyd said:
Use this app, hit Device Information, and change the dropdown to LTE/GSM (auto PRL). Given the simplicity not sure you need much more of a walk through than that. A video would require a bunch of editing to blot out IMEI and phone #s.
Click to expand...
Click to collapse
I am using this app and it is great. When it works, it would show T-Mobile as Net. Op instead of Unknown. Only issue I am seeing is that 4G LTE signal is not so great over where I am at and once in a while it would drop to H+ and then get back to LTE. During that cycle, the Net. Op would become Unknown again. Wish there was a way to fix this permanently like tricky the SMS app to send GSM or whatever it is causing Net Ops to be unknown.
majorlag said:
I am using this app and it is great. When it works, it would show T-Mobile as Net. Op instead of Unknown. Only issue I am seeing is that 4G LTE signal is not so great over where I am at and once in a while it would drop to H+ and then get back to LTE. During that cycle, the Net. Op would become Unknown again. Wish there was a way to fix this permanently like tricky the SMS app to send GSM or whatever it is causing Net Ops to be unknown.
Click to expand...
Click to collapse
Couple of things. Remember as I started with the baseband in i545 when on LTE really wants to use CDMA as the default so when it's searching it's not going to obtain GSM as instantaneous As it otherwise would. Don't see any specific way of that getting patched ever as we're going against the grain of how it's typically supposed to be used. If you are on a fringy area for it, you may be better off just leaving LTE off, H+ speeds are practically the same anyway. Tmo is only using 3-5mhz channels for band 4 as they use other channels too so for us it's not going to be superfast like Verizon on average anyway.
My phone is in Global mode, I have fast LTE internet and calls/texting works just fine. I am using a Verizon S4 with MJ7 and a T-Mobile simcard. No need to change anything except the APN and switch to Global.
elite-fusion said:
My phone is in Global mode, I have fast LTE internet and calls/texting works just fine. I am using a Verizon S4 with MJ7 and a T-Mobile simcard. No need to change anything except the APN and switch to Global.
Click to expand...
Click to collapse
Stock?
Sent From The Future
yep, cant really install anything on MJ7 since there is no official root even, so yeah, bone stock. Fastest I have gotten the internet to be was 25-26mbps download which isnt great, but for a cellphone is more than enough lol
So maybe the MK7 bootloader fixes this SMS issue...
How is this holding on for u ? I got it to work one time with hyperom and I restarted and it doesn't want to work. I did however get it working completely on a mj7 ROM and gummy kikat ROM. Weird.
Sent from my SCH-I545 using xda app-developers app
If you happen to have an MDK and want to run CM10.2 with GSM service run the ATT "I337" ROMS, fixes all the Verizon CDMA quirks
Black6spdZ said:
If you happen to have an MDK and want to run CM10.2 with GSM service run the ATT "I337" ROMS, fixes all the Verizon CDMA quirks
Click to expand...
Click to collapse
I did that and it kept failing.... TWRP recovery just would not get it to take.
So I flashed the MJ7 rom again and I got it working on it. I'm not sure why it didn't work on hyperom. Very weird. Tried the method and nothing. But I tried the method on mj7 ROM and it works perfectly. Weird weird weird.
Sent from my SCH-I545 using xda app-developers app
420haxr said:
How is this holding on for u ? I got it to work one time with hyperom and I restarted and it doesn't want to work. I did however get it working completely on a mj7 ROM and gummy kikat ROM. Weird.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
so using the 4.4 gummy rom you were able to connect to LTE / HSPA+ networks easily? And SMS / MMS worked just fine? Upon trying with the MJ7 update, non-rooted, I could only connect to Edge services under the GSM profile. Using global would barely warrant the HSPA band.
zepfloyd said:
After happily using my 'old' S4 on T-Mobile with HSPA+ since having the Note 3 as my primary line, I was naturally excited to update the baseband and unlock Band 4 LTE. However I noticed some caveats which I've now solved which will undoubtedly confuse everyone at some point.
Assuming you've got the correct APN for T-Mo (fast.t-mobile.com) and naturally install the SIM, if your phone is on global you will happily see working LTE but not so fast (no pun intended). If you call or text, it fails. If you quick check your About -Status in settings and look under network it will say say Unknown and not T-Mobile. Why? Essentially you're in LTE data only mode because by default the baseband is looking to connect to CDMA for everything else in the CDMA/LTE marriage that is Verizon unique, which obviously won't work here. The assumption otherwise is that you will only need GSM if traveling internationally so it never looks for LTE with GSM.
The quick easy fix is to drop out of Global back to the GSM/UMTS setting, which will bring everything back, network restored to T-Mobile, but now it won't use LTE again, lame.
Luckily there is a fix. Use the PhoneInfo app or however you prefer to get to the Testing App. Under device information change the dropdown to LTE/GSM (auto PRL). Toggle airplane mode or restart. When it comes up you should be on LTE and quick check settings again you'll see T-Mobile, and everything will work. So far this seems to hold pretty well.
EDIT: Note: This works for TW Roms. I have not had success in CM10.2. In CM I've only gotten LTE data (wrongly labeled Verizon) and nothing else. Doesn't even pick up my phone number regardless of settings used.
Click to expand...
Click to collapse
how did you update and unlock to baseband 4? What developer makes the PhoneInfo app? thanks
---------- Post added at 08:20 PM ---------- Previous post was at 08:16 PM ----------
elite-fusion said:
My phone is in Global mode, I have fast LTE internet and calls/texting works just fine. I am using a Verizon S4 with MJ7 and a T-Mobile simcard. No need to change anything except the APN and switch to Global.
Click to expand...
Click to collapse
Are you actually getting "LTE" or reframed 4G?
please school me how to change apn.
well let me give you a trick, flash an i9505 rom which you can find them here http://forum.xda-developers.com/galaxy-s4/i9505-develop
then flash any verizon kernel (because if you just flash an at&t or t-mob rom it wont reboot it will say triangle and not authorized verizon software)
dont forget to update your baseband to lastest then you can enjoy LTE (and fast) without any problems.
if you get and prop. issues while flashing international roms just change the "updater-script" first line to :
assert(getprop("ro.product.device") == "jfltevzw" || getprop("ro.build.product") == "jfltevzw"
then you can flash anything you want.
Here is how I did it
Here is how I did it, but needs some minor updates since then. Please let me know if anyone tries it and is happy with the result.
http://forum.xda-developers.com/showthread.php?t=2560128
zepfloyd said:
Use this app, hit Device Information, and change the dropdown to LTE/GSM (auto PRL). Given the simplicity not sure you need much more of a walk through than that. A video would require a bunch of editing to blot out IMEI and phone #s.
Click to expand...
Click to collapse
App wont open for me.
Running a rooted stock MK2.
any ideas?
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.
To be clear, I have absolutely no idea what I'm doing, and no experience whatsoever with any of this.
Over 12 hours of research I managed to unlock the bootloader, root, and flash my TextNow Moto E with a stock US Cellular ROM. Everything worked fine.
What are the next steps to take, if any? Is it possible to even use a GSM network on this phone? I have an active T-Mobile sim card that the phone simply will not accept. I get a "no sim found" notification.
I attempted this with no success.
To start, su command would not work.
This worked for me on the XT1529, but it might work on the XT1526 as well since they're both LTE/CDMA devices:
root, open /system/build.prop, add the following line to the end: ro.telephony.default_network=10
save, make sure the permissions are still 0644, reboot.
When you check *#*#4636#*#* it should be in LTE/GSM/CDMA mode, and in Settings > Mobile Network it should say "Global".
xtermmin said:
This worked for me on the XT1529, but it might work on the XT1526 as well since they're both LTE/CDMA devices:
root, open /system/build.prop, add the following line to the end: ro.telephony.default_network=10
save, make sure the permissions are still 0644, reboot.
When you check *#*#4636#*#* it should be in LTE/GSM/CDMA mode, and in Settings > Mobile Network it should say "Global".
Click to expand...
Click to collapse
This didn't work. I ended up experimenting more and softbricked my phone, got stuck in a boot loop. Through curiosity I ended up flashing the phone with a stock xt1527 rom. SIM now recognized as a non supported sim, so that's nice. Still doesn't work.
I cannot post links to screens as a new user, but if you happen to want to see them, message me and I'll link them from my dropbox.
I ended up ordering an unlocked xt1527 last night. However, I would still like to figure this out. Would I perhaps have to flash the modem?
akaholik said:
This didn't work. I ended up experimenting more and softbricked my phone, got stuck in a boot loop. Through curiosity I ended up flashing the phone with a stock xt1527 rom. SIM now recognized as a non supported sim, so that's nice. Still doesn't work.
I cannot post links to screens as a new user, but if you happen to want to see them, message me and I'll link them from my dropbox.
I ended up ordering an unlocked xt1527 last night. However, I would still like to figure this out. Would I perhaps have to flash the modem?
Click to expand...
Click to collapse
You could try the procedure posted in this thread if you haven't already, assuming your still on the xt1527 rom:
http://forum.xda-developers.com/moto-e-2015/general/how-to-verizon-moto-e-2015-gsm-network-t3098953
hydroman202 said:
You could try the procedure posted in this thread if you haven't already, assuming your still on the xt1527 rom:
http://forum.xda-developers.com/moto-e-2015/general/how-to-verizon-moto-e-2015-gsm-network-t3098953
Click to expand...
Click to collapse
Just tested this - not working. This is a really maddening scenario
I contacted sprint and gave them the IMEI - they tell me that this phone can indeed be unlocked (xt1526), but I would have to do it through TextNow. I've searched for ways to bring up the SIM unlock prompt, but it simply doesn't show up with any of the methods found. :s
akaholik said:
I contacted sprint and gave them the IMEI - they tell me that this phone can indeed be unlocked (xt1526), but I would have to do it through TextNow. I've searched for ways to bring up the SIM unlock prompt, but it simply doesn't show up with any of the methods found. :s
Click to expand...
Click to collapse
I am also having problems finding this menu. I wish there was an easy way to access it, but unfortunately, sprint has made it rather difficult.
hydroman202 said:
I am also having problems finding this menu. I wish there was an easy way to access it, but unfortunately, sprint has made it rather difficult.
Click to expand...
Click to collapse
I still have my sprint model as well, and have the MSL code. But I have also never found a way to enter it for unlock. I've tried using active ATT and VZW SIMs, and also tried flashing the USC modem on it - still works on sprint / ringplus, but also still won't acknowledge ATT or VZW SIMs.
Sent from my XT1526 using Tapatalk
dandrumheller said:
I still have my sprint model as well, and have the MSL code. But I have also never found a way to enter it for unlock. I've tried using active ATT and VZW SIMs, and also tried flashing the USC modem on it - still works on sprint / ringplus, but also still won't acknowledge ATT or VZW SIMs.
Sent from my XT1526 using Tapatalk
Click to expand...
Click to collapse
I don't know for sure, but i did read in another place on here somewhere about an "embedded card" that sprint put in another phone. I wonder if that is the case with this one? If not, all i can really think of is that there is something in place that motorola made specifically for the sprint model. We know its not modem related, so it must be somewhere else, in the NAM, or something like that. One thing i did accomplish was to get another bar, (it had no signal and looked like an outline, but it was there), show up by editing the build prop with a specific line and then rebooting. Odd thing is, its the same thing that showed up when i attemped to flash another stock firmware. The firmware i flashed was for the xt1526, retail us. Which leads me to think it might be a band issue, as someone else mentioned in another thread on here somewhere. I mean, it would make sense with the no signal and everything. Sorry for the long post, just thinking out loud i guess.
hydroman202 said:
I don't know for sure, but i did read in another place on here somewhere about an "embedded card" that sprint put in another phone. I wonder if that is the case with this one? If not, all i can really think of is that there is something in place that motorola made specifically for the sprint model. We know its not modem related, so it must be somewhere else, in the NAM, or something like that. One thing i did accomplish was to get another bar, (it had no signal and looked like an outline, but it was there), show up by editing the build prop with a specific line and then rebooting. Odd thing is, its the same thing that showed up when i attemped to flash another stock firmware. The firmware i flashed was for the xt1526, retail us. Which leads me to think it might be a band issue, as someone else mentioned in another thread on here somewhere. I mean, it would make sense with the no signal and everything. Sorry for the long post, just thinking out loud i guess.
Click to expand...
Click to collapse
Yes, I'm hoping there is a fix somehow. I'm ok to use the phone on WiFi, but it is otherwise useless to me. I'd like to have a backup phone in case my first Moto E dies, they are really rugged. I have experimented all day without success. Experimenting with build.prop does nothing. I export the build.prop text and post it just for reference, if anyone cares to play with it.
hydroman202 said:
I don't know for sure, but i did read in another place on here somewhere about an "embedded card" that sprint put in another phone. I wonder if that is the case with this one? If not, all i can really think of is that there is something in place that motorola made specifically for the sprint model. We know its not modem related, so it must be somewhere else, in the NAM, or something like that. One thing i did accomplish was to get another bar, (it had no signal and looked like an outline, but it was there), show up by editing the build prop with a specific line and then rebooting. Odd thing is, its the same thing that showed up when i attemped to flash another stock firmware. The firmware i flashed was for the xt1526, retail us. Which leads me to think it might be a band issue, as someone else mentioned in another thread on here somewhere. I mean, it would make sense with the no signal and everything. Sorry for the long post, just thinking out loud i guess.
Click to expand...
Click to collapse
its not an embedded card in the textnow wireless version as ive taken the sim card out of mine. The S3 was an imbedded card, but not this device. Im also searching for a method to sim unlock this little bugger. Ill let you know what i find out
youdoofus said:
its not an embedded card in the textnow wireless version as ive taken the sim card out of mine. The S3 was an imbedded card, but not this device. Im also searching for a method to sim unlock this little bugger. Ill let you know what i find out
Click to expand...
Click to collapse
I talked to Sprint - they told me TextNow has to SIM unlock the device. I talked to TextNow - They told me the device IS SIM unlocked. So, there's that if anybody is wondering. I've almost abandoned this experiment, but it's still in the back of my mind. In other news - the new Moto E 2015 I received has a yellowed display. 2/3 brand new Motorola devices I received had display issues. Excellent phones, poor quality control it seems.
akaholik said:
I talked to Sprint - they told me TextNow has to SIM unlock the device. I talked to TextNow - They told me the device IS SIM unlocked. So, there's that if anybody is wondering. I've almost abandoned this experiment, but it's still in the back of my mind. In other news - the new Moto E 2015 I received has a yellowed display. 2/3 brand new Motorola devices I received had display issues. Excellent phones, poor quality control it seems.
Click to expand...
Click to collapse
i got my E2015 from textnow for $10 as a refurb and its solid as a rock so far. I stumbled upon this thread and it looks promising, but im at work and we use citrix clients and not actual computers so i cant run it here, but ill give it a whirl when i get home. I do also believe that its GSM unlocked
Trying to make my XT1526 (Boost stock ROM) work with GSM, and got stuck on something weird. Inserted a SIM card from China Mobile, changed the network mode to "Global" and turned on roaming, after a while it got successfully registered on T-Mobile network, both voice and data. Yet, when I inserted a T-Mobile SIM card, the phone gave an "Invalid SIM card" error, and simply refused to connect. Thought it might be an issue with APN setting, but I couldn't manually add the T-Mo APN to the phone (in fact it wouldn't take any APN).
I think the phone's hardware is capable of LTE/CDMA/GSM. It's a just matter of figuring out the right configuration.
ck9068 said:
Trying to make my XT1526 (Boost stock ROM) work with GSM, and got stuck on something weird. Inserted a SIM card from China Mobile, changed the network mode to "Global" and turned on roaming, after a while it got successfully registered on T-Mobile network, both voice and data. Yet, when I inserted a T-Mobile SIM card, the phone gave an "Invalid SIM card" error, and simply refused to connect. Thought it might be an issue with APN setting, but I couldn't manually add the T-Mo APN to the phone (in fact it wouldn't take any APN).
I think the phone's hardware is capable of LTE/CDMA/GSM. It's a just matter of figuring out the right configuration.
Click to expand...
Click to collapse
thats a DSU issue. Domestic sim unlock can be tricky
youdoofus said:
thats a DSU issue. Domestic sim unlock can be tricky
Click to expand...
Click to collapse
Why so tricky? Why? I am truly of no help, I just started the thread. Learning as I go...funny thing. Upon flashing again with the xt1527, and flashing the modem with a different modem software, the phone still shows to be a sprint modem software.
I wonder if the "fastboot oem config carrier" option would do any good?
DSU is tricky because it involved modifying the NV values thats buried in the radio software and it has a similar access issue to SU. I have (among many others) a Sprint S5 (G900P) and achieving DSU on it was the work of some SERIOUS developers. The config carrier might be of some help, but i havent delved into it yet, and im not sure if id fully understand what it means anyways. Additionally, Moto devices are tricky period. I had 2 Razrs (one xt 912 and one xt910), one of them was GSM unlockable and the other wasnt. Motorola mobile phone division has also changed hands recently, so its direction has also changed. Basically, whats needed here is either a ton of forum scouring or a developer to actually pay attention to this device, or a bit of both
Wifi calling is enabled for Verizon (go to phone settings to enable). I am sure there
are other changes. Update G965U1UEU3ARH7.
fb
Hi, just posted the same update for GS9 Unlocked using AT&T. 495.78 MB.
Thanks for sharing... View attachment 4598513
Sent from my SM-G960U1 using Tapatalk
fbroce said:
Wifi calling is enabled for Verizon (go to phone settings to enable). I am sure there
are other changes. Update G965U1UEU3ARH7.
fb
Click to expand...
Click to collapse
Yes, and Secure Wi-Fi has now been added. I think it previously existed only on the European firmwares. Now we get it, too.
Any way to see if AT&T Wifi Calling will work as I do not see the option in Settings? I have US Unlocked GS9 on AT&T
If I flash this U1 for my ATT phone (running full Tmobile firmware now),
will I have Wifi calling with Tmobile? Or Wifi calling only works with Verizon with U1
sweetboy02125 said:
If I flash this U1 for my ATT phone (running full Tmobile firmware now),
will I have Wifi calling with Tmobile? Or Wifi calling only works with Verizon with U1
Click to expand...
Click to collapse
Despite what the websites like to post, there really isn't a VZW U1 and an ATT U1. There's just XAA U1. You'll get Wi-Fi Calling on every carrier with it now, except for ATT.
maddie01 said:
Any way to see if AT&T Wifi Calling will work as I do not see the option in Settings? I have US Unlocked GS9 on AT&T
Click to expand...
Click to collapse
Reading up on it (short summary) this is because AT&T uses a database of IMEI numbers to provision WiFi calling and VoLTE. Since our IMEI numbers from our phones are not in that database we won't be able to use WiFi calling or VoLTE.
Makes sense but is ridiculous for AT&T to restrict it. Has anyone ever called to ask to have thier Unlocked IMEI added to this "list" so that these features will work? Seems like it is a disadvantage for AT&T if it works for TMo and now Verizon but not AT&T...?
Just curious...
Sent from my SM-G960U1 using Tapatalk
maddie01 said:
Makes sense but is ridiculous for AT&T to restrict it. Has anyone ever called to ask to have thier Unlocked IMEI added to this "list" so that these features will work? Seems like it is a disadvantage for AT&T if it works for TMo and now Verizon but not AT&T...?
Just curious...
Sent from my SM-G960U1 using Tapatalk
Click to expand...
Click to collapse
It's odd for sure. Verizon has always had VoLTE on unlocked too. At least since the S7. Probably before that. ATT has never felt the need to change the policy.
maddie01 said:
Makes sense but is ridiculous for AT&T to restrict it. Has anyone ever called to ask to have thier Unlocked IMEI added to this "list" so that these features will work? Seems like it is a disadvantage for AT&T if it works for TMo and now Verizon but not AT&T...?
Just curious...
Sent from my SM-G960U1 using Tapatalk
Click to expand...
Click to collapse
Who can say if it's disadvantageous or not, for all we know it might be the technology differences between the networks. Also it does make sense... having specific IMEI numbers known to connect to carrier specific services like wifi calling and VoLTE ensures that everything works. It doesn't make it convenient for us and I will admit it would be nice to have the features.. but for calling via wifi there are options.
Personally I use pbx in a flash and bria softphone. With the right VoIP provider it's a good setup and doesn't break the bank at all. I haven't even spent more then 5 bucks maybe in a month. For me this is better then wifi calling and I don't have any problems.
As for adding our IMEI to that database I tried inquiring about it, but I do recall reading where some people may have had luck in doing this. I suspect it may require a bit of luck and/or perserveriance after my last discussion with AT&T customer service.
I explained the situation and what needed to be done while being placed on hold a few times. As the call continued I tried to be patient with the person I spoke too, but I admit it is not easy when he is saying that just because I see H data speed that it's actually VoLTE. When I mentioned the speed test and how it was H data speed (and that H data speeds are not VoLTE) he was saying that H data speeds were like blazing fast compared to LTE..
I had to politely finish the call before I either started to laugh or feel sorry for that rep.
scottusa2008 said:
I tried inquiring about it, but I do recall reading where some people may have had luck in doing this. I suspect it may require a bit of luck and/or perserveriance.
In my case I tried to be patient with the person I spoke too. After waiting on hold a few times the representative tried to say everything was normal.. and then proceeded but to say that just because I see H+ speed that it's actually VoLTE. When I mentioned the speed test and how it was H data speed (and that H data speeds are not VoLTE) he was saying that H data speeds were like blazing fast compared to LTE..
I had to politely finish the call before I either started to laugh or feel sorry for that rep.
Click to expand...
Click to collapse
Hahaa, i have had a similar situations in the store where i had to correct a worker that was completely explaining 3G/HSPA wrong. Incredible how incompetent they are unless you just want an iPhone...thanks
Sent from my iPad using Tapatalk
maddie01 said:
Makes sense but is ridiculous for AT&T to restrict it. Has anyone ever called to ask to have thier Unlocked IMEI added to this "list" so that these features will work? Seems like it is a disadvantage for AT&T if it works for TMo and now Verizon but not AT&T...?
Just curious...
Click to expand...
Click to collapse
The only thing I've seen some people do successfully to get VoLTE working on an unbranded unlocked device is to have AT&T provision a SIM card to an IMEI of a phone that is AT&T branded and capable of VoLTE. Then use that SIM card on the unbranded unlocked device.
guyd said:
The only thing I've seen some people do successfully to get VoLTE working on an unbranded unlocked device is to have AT&T provision a SIM card to an IMEI of a phone that is AT&T branded and capable of VoLTE. Then use that SIM card on the unbranded unlocked device.
Click to expand...
Click to collapse
Do you recall seeing if they said this work for prepaid and/or postpaid?
If it's that simple i'm gonna have to find a phone capable of VoLTE and see if this works
scottusa2008 said:
Do you recall seeing if they said this work for prepaid and/or postpaid?
If it's that simple i'm gonna have to find a phone capable of VoLTE and see if this works
Click to expand...
Click to collapse
Honestly don't recall, or if it was even mentioned.
So this new version includes wifi calling. You find this in the menu system somewhere? Does HD Voice also work and indicated like Verizon SM-G965U?
houston-tx said:
So this new version includes wifi calling. You find this in the menu system somewhere? Does HD Voice also work and indicated like Verizon SM-G965U?
Click to expand...
Click to collapse
Hd voice always worked on unlocked for Verizon. Wifi calling is found in the phone app's settings.
I flashed G965U1UES3ARI1 for XAA to SM-G965U1 and I can't find settings for Wifi calling. Are they visible or just built in and assumed to be there?
houston-tx said:
I flashed G965U1UES3ARI1 for XAA to SM-G965U1 and I can't find settings for Wifi calling. Are they visible or just built in and assumed to be there?
Click to expand...
Click to collapse
What carrier are you on? It's supported for SPR, TMB, and now VZW. Look in the settings of the actual phone app, not the device settings.
Verizon. Found it. Thought it was in Settings. Thank you!
houston-tx said:
Verizon. Found it. Thought it was in Settings. Thank you!
Click to expand...
Click to collapse
No problem. You're not the first person to look for it in the wrong place. U1 builds always place the setting there. So they stayed consistent doing it this way.
My phone is a T-Mobile branded DE2118; I have noticed this app in those secret launchers(I use Activity Launcher); I don't know Chinese at all and also when I set something I lose my signal for 5-10 minutes.
Regardless, this phone has the SD480 in it and apparently with the x51 modem it should have support for mmWave.
Is there any way to change/modify the bands at all within this app/program? Has anyone actually been successful with it at all?
I have had success using com.oneplus.engmode for LTE band selection, making sure I set the signal to lte_only in the *#*#4636#*#* phone menu
Well, there's an issue; *#*#4636#*#* doesn't work for me......
I wonder if it was caused from when I bricked my phone a month ago?
I don't know, but here is a video of the process on mine
blowtorchhonor said:
I don't know, but here is a video of the process on mine
Click to expand...
Click to collapse
Thanks! I'll work on this tomorrow!
I checked it out, but it only shows LTE bands and not NR/mmWave