Related
I just flashed my phone to OMJ's custom Verizon, now I have lost all service. Any advise on what settings I am missing?
Or is this a call into Verizon to do something? If so what do I say?
Thanks,
Scott
well hopefully when you updated the radio with a different rom you didn't let the customizations run.
if you did everything correctly you may just need to activate a different phone on your plan, get all your services working on that phone, then reactivate your xv6900, do the *228, remove battery thing and hopefully that'll work for you
No did not let the customizations run. It all went smooth. I did find this message....
http://forum.xda-developers.com/showthread.php?t=416908&highlight=verizon
So I am calling Verizon....
Is there a way to not have to call Verizon? Will this happen with EVERY flashed ROM? Or is it only when you unlock with IMcoke's utility?
What a PITA!
Scott
Well, I hope this thread can help others...
I did have to call Verizon to reset. Now the gal who answered did sound cute, but it took 20 minutes of her reading her scripts until she escalated me to 2nd level support.
10 minutes there and they did the A-Key update....
So all is working..
But more importantly, what causes this? Will it happen with every ROM or just the first you flash?
Regards,
ST
I know I have to call in every time I Master Reset my stock XV6900 so I imagine it's the same issue with a new flash as well. Something about this phone makes them manually update it on their end I guess.
You should only need to do this if you update the Radio. But, I've flashed two radios to date, and only on the first did I need to call VZW. I've flashed quite a few ROMs and had to call maybe twice.
Scott_T said:
Well, I hope this thread can help others...
I did have to call Verizon to reset. Now the gal who answered did sound cute, but it took 20 minutes of her reading her scripts until she escalated me to 2nd level support.
10 minutes there and they did the A-Key update....
So all is working..
But more importantly, what causes this? Will it happen with every ROM or just the first you flash?
Regards,
ST
Click to expand...
Click to collapse
I helped a buddy upgrade his Verizon XV6900 radio to the sprint radio. We ran into all kinds of problems with his phone. No internet, phone searched for thirty minutes and when it got a signal would sometimes randomly shut off. We fixed everything by logging onto the Verizon website and activating one of his old phones. We took the battery out of the touch before hand because two signals equal no good. We activated his old phone for about ten minutes and then reactivated his touch. Everything worked fine afterward. He had a new akey and I believe his dmu keys were reset. Hope this helps, but activating an old phone on the verizon website is a bit of a pain.
Thanks for the info everyone...
Hope this helps someone else out.
Scott
woodicw said:
well hopefully when you updated the radio with a different rom you didn't let the customizations run.
if you did everything correctly you may just need to activate a different phone on your plan, get all your services working on that phone, then reactivate your xv6900, do the *228, remove battery thing and hopefully that'll work for you
Click to expand...
Click to collapse
um.... what if I did let the customization run? after I used the Sprint Radio Upgrade. Does the phone now think it's a Sprint phone? It won't even let me do the *228 anymore. Someone mentioned having success using a radiorefurbish.exe? does that make sense?
Thanks!
I'm no pro, but re-flash, and make sure to soft reset before the customizations. Not a big deal.
Scott
I have the same problem with internet. I too accidentally let the first flash run customization. I then re flashed the phone with a bunch of different roms and still cant get internet working, nor *228. I can still make phone calls just no internet. Can someone recommend with a link a good rom for verizons xv6900 that would solve this problem?
TheBigBentley said:
I have the same problem with internet. I too accidentally let the first flash run customization. I then re flashed the phone with a bunch of different roms and still cant get internet working, nor *228. I can still make phone calls just no internet. Can someone recommend with a link a good rom for verizons xv6900 that would solve this problem?
Click to expand...
Click to collapse
You left some important details like,
The ROM & what exactly the error is.
Well the first rom was the oem sprint rom. I did this mostly for the gps function. The error is when i try to use data it says its dialing #777 then after about a min or 2 its says it could not connect. Ive tried entering my username and pass as someone suggested, but i actually never had one there before so I didn't see how that was going to help. Needless to say it didnt. I also have a problem when i try to use *228 to update my phone. It says it failed. Im mostly concerned with internet atm. By the way i really appreciate your fast reply!
I also ran the verizon carrier cab as was recommended in some posts but no dice there either.
TheBigBentley said:
Well the first rom was the oem sprint rom. I did this mostly for the gps function. The error is when i try to use data it says its dialing #777 then after about a min or 2 its says it could not connect. Ive tried entering my username and pass as someone suggested, but i actually never had one there before so I didn't see how that was going to help. Needless to say it didnt. I also have a problem when i try to use *228 to update my phone. It says it failed. Im mostly concerned with internet atm. By the way i really appreciate your fast reply!
I also ran the verizon carrier cab as was recommended in some posts but no dice there either.
Click to expand...
Click to collapse
First, if you haven't done it yet, enter the username and password. After you flash a new ROM, the fields are blank, but the internet will work, but at some point, it will start to fail becuase of it being blank.
If that doesn't solve it, I suggest flashing a new Radio and ROM, I personally suggest using one from OMJ. I'm currently using his 3.09 Clean ROM, and it runs smooth. And after using the aGPS hack, something you can do after you resolve this, I get a faster GPS lock inside my home or office, than someone with an in-car model.
which radio do you suggest Ive tried 3.42.30 and 3.42.50 both give me same problame. Im flashing omj's 3.03.01 clean as I type this.
I'm using 3.42.50 right now, and so far it works great.
ok so then I have both radio and rom installed and still no data. any further suggestion? Is there anyway of restoring verizon data setting to original defaults? I think the sprint rom must have changed something specific to the data settings. Ive tried everything to revert them back with no luck
What's the link to the ROM that you originally flashed and run the cusomizations.
http://www.smartphonejunkie.com/showthread.php?t=169263
Filename
RUU_PPST_Vogue_SPRINT_WWE_3.03.651.4_2_Radio_3.42.30_AM_NV_2.04_Ship
Well, I just browsed through the thread at PPCGeeks, I saw you just asked there too, but this is the best thing I've found:
http://forum.ppcgeeks.com/showpost.php?p=265704&postcount=360
I'm having a VERY specific issue with my ATT M8 that I can't seem to figure out. First and foremost, I've tried wiping all partitions and starting over....with 3 different ROMS (Liquid, Candy5, Bliss Pop) and none of them allow me to RECEIVE calls. I've even done an RUU back COMPLETELY to stock everything using the ATT stock Lollipop RUU image. When I boot the stock RUU I can again receive calls. Below is the detailed info on the scenario....
Can't receive calls but I'm notified if someone leaves a voice mail.
Making calls from my phone works fine.
If I'm on the phone and someone calls me the phone notifies me like it normally would.
When someone tries to call me, they hear it ring the proper number of times and it does NOT go straight to voice mail.
That last bullet is VERY important. The fact the call doesn't go straight to voice mail is an indication the ATT network knows my phone is indeed powered on and available. Strangely though, it doesn't ring or do anything to otherwise show someone is trying to call.
At this point I'm really stumped. How on Earth is this even possible? Especially after doing the RUU and having the phone work as intended only to try and flash any other ROM later and have it not receive calls. I'm 100% stumped and really need y'alls help.!
**SOLUTION BELOW**
Apparently AT&T is rolling out HD Voice in many areas. It's basically voice over LTE and it's not compatible with many custom ROMS. This is why flashing the stock AT&T RUU made everything work just fine but when I tried ANY custom ROM it wouldn't work.
If this happens to you try the following....disable LTE by turning off mobile data or simply switching to 3G. Then try to call yourself or have someone call you. If the call comes through on your handset it's due to HD Voice having been activated on your account. I called AT&T and explained that I needed HD Voice turned off for my account. You'll likely have to talk to tech support. Ask them when it was activated on your account. Mine was activated last week which is the EXACT time I started having issues. The AT&T tech will ask that you power down the phone whilst they make the changes. Then turn your phone back on (with LTE active) and try a test call. It should work for you.
Big thanks to @redpoint73 for helping me figure this out!
I'm wondering if after doing the RUU my radio or something isn't at a proper level. Attached is a screenshot of my current bootloader. Anyone see something out of the ordinary that needs updating?
Yeah, I would go ahead and check with ATT if there are any bars on your account. Sounds like more of a network issue than a phone issue.
downbringer said:
Yeah, I would go ahead and check with ATT if there are any bars on your account. Sounds like more of a network issue than a phone issue.
Click to expand...
Click to collapse
Thanks for the reply! What would lead you to believe it's a network issue? I can make calls just fine and if I'm on the phone and someone calls me it works as if it normally would. Only issue is when someone calls me and I'm NOT on the phone.
Try turning off LTE, and see if you can get calls.
Some folks have been having issues with "international" based Sense ROMs not playing well with AT&T's LTE network upgrades (in preparation for Voice Over LTE). Not sure if this affects AOSP ROMs, but I have a feeling this is the problem.
redpoint73 said:
Try turning off LTE, and see if you can get calls.
Some folks have been having issues with "international" based Sense ROMs not playing well with AT&T's LTE network upgrades (in preparation for Voice Over LTE). Not sure if this affects AOSP ROMs, but I have a feeling this is the problem.
Click to expand...
Click to collapse
Wow......You, you're good you lol. @redpoint73
Sooooo yeah, changing my mobile data to 3G all of a sudden allows calls to come through. What exactly is at play here and how do I fix it?
italynstylion said:
What exactly is at play here and how do I fix it?
Click to expand...
Click to collapse
As I already described, AT&T is upgrading their LTE network for Voice Over LTE (they call it "HD Voice") and something in that upgrade doesn't seem to be playing well for some people on international based custom ROMs. In addition to voice call problems, you will probably also find SMS messages won't work on LTE.
Curiously, the problem seems to be very location specific. I've been running Skydragon Sense and LeeDroid for a few months, and on AT&T network. And everything has been working fine for me at my home location, as well as a few other locations around the country (I travel pretty occasionally for work). These are some of the ROM that others have had AT&T LTE issues with; and at one point even in the same city as another user that was suffering this issue (Chicago area). But for me, everything seemed to work fine.
The only real fix is to go back to stock AT&T based ROM. Folks have tried to flash various radios, and other things with no luck. Team Venom (Viper ROM) also said they would look into it a few months ago; but I don't think anything ever came of that.
An ingenious workaround posted by another user (if you want to stay on an international ROM): call AT&T and ask them to turn off HD Voice for your account. So you can still use LTE for data, but the call bug won't occur.
Of course, the downside for this is that you won't be able to utilize HD Voice. But that is probably the lesser of evils, if you want to stay on the current ROM.
redpoint73 said:
As I already described, AT&T is upgrading their LTE network for Voice Over LTE (they call it "HD Voice") and something in that upgrade doesn't seem to be playing well for some people on international based custom ROMs.
The only real fix is to go back to stock AT&T based ROM. Folks have tried to flash various radios, and other things with no luck.
An ingenious workaround posted by another user (if you want to stay on an international ROM): call AT&T and ask them to turn off HD Voice for your account. So you can still use LTE for data, but the call bug won't occur.
Of course, the downside for this is that you won't be able to utilize HD Voice. But that is probably the lesser of evils, if you want to stay on the current ROM.
Click to expand...
Click to collapse
This is brilliant. I'll give it a shot. Thanks for your help!
italynstylion said:
This is brilliant. I'll give it a shot. Thanks for your help!
Click to expand...
Click to collapse
I agree, its a good workaround. Especially since HD Voice requires users on both ends of the call to have a phone that supports the feature; and few phones for the time being have it. So having HD Voice turned off on your account (even if its deployed in your area) is probably mostly irrelevant.
You're quite welcome. And if you have a chance, please click the "Thanks" button for any posts you found helpful!
redpoint73 said:
I agree, its a good workaround. Especially since HD Voice requires users on both ends of the call to have a phone that supports the feature; and few phones for the time being have it. So having HD Voice turned off on your account (even if its deployed in your area) is probably mostly irrelevant.
You're quite welcome. And if you have a chance, please click the "Thanks" button for any posts you found helpful!
Click to expand...
Click to collapse
Just got off the phone with AT&T and everything is just peachy again. I updated the first post with the solution/fix. Thanks so much for your help!
italynstylion said:
Ask them when it was activated on your account. Mine was activated last week which is the EXACT time I started having issues.
Click to expand...
Click to collapse
Interesting. I wonder if HD Voice hasn't been activated on my account yet; and that is why I haven't had this issue while others have?
redpoint73 said:
Interesting. I wonder if HD Voice hasn't been activated on my account yet; and that is why I haven't had this issue while others have?
Click to expand...
Click to collapse
It's certainly possible. I live in Dallas which is a fairly large area. It wouldn't surprise me if we were one of the areas that got it first. Sucks being a guinea pig but I've left a trail of breadcrumbs for everyone else to follow.
italynstylion said:
It's certainly possible. I live in Dallas which is a fairly large area. It wouldn't surprise me if we were one of the areas that got it first. Sucks being a guinea pig but I've left a trail of breadcrumbs for everyone else to follow.
Click to expand...
Click to collapse
I'm in Boston area, and according to the AT&T maps, HD Voice is working here.
Although, I got the M8 long before it supported the feature (they added it with the 4.4.4 OTA). So I don't know how they decide when to activate it on your account; but if its device related, I can see how it might not be on mine yet.
italynstylion said:
I'm having a VERY specific issue with my ATT M8 that I can't seem to figure out. First and foremost, I've tried wiping all partitions and starting over....with 3 different ROMS (Liquid, Candy5, Bliss Pop) and none of them allow me to RECEIVE calls. I've even done an RUU back COMPLETELY to stock everything using the ATT stock Lollipop RUU image. When I boot the stock RUU I can again receive calls. Below is the detailed info on the scenario....
Can't receive calls but I'm notified if someone leaves a voice mail.
Making calls from my phone works fine.
If I'm on the phone and someone calls me the phone notifies me like it normally would.
When someone tries to call me, they hear it ring the proper number of times and it does NOT go straight to voice mail.
That last bullet is VERY important. The fact the call doesn't go straight to voice mail is an indication the ATT network knows my phone is indeed powered on and available. Strangely though, it doesn't ring or do anything to otherwise show someone is trying to call.
At this point I'm really stumped. How on Earth is this even possible? Especially after doing the RUU and having the phone work as intended only to try and flash any other ROM later and have it not receive calls. I'm 100% stumped and really need y'alls help.!
**SOLUTION BELOW**
Apparently AT&T is rolling out HD Voice in many areas. It's basically voice over LTE and it's not compatible with many custom ROMS. This is why flashing the stock AT&T RUU made everything work just fine but when I tried ANY custom ROM it wouldn't work.
If this happens to you try the following....disable LTE by turning off mobile data or simply switching to 3G. Then try to call yourself or have someone call you. If the call comes through on your handset it's due to HD Voice having been activated on your account. I called AT&T and explained that I needed HD Voice turned off for my account. You'll likely have to talk to tech support. Ask them when it was activated on your account. Mine was activated last week which is the EXACT time I started having issues. The AT&T tech will ask that you power down the phone whilst they make the changes. Then turn your phone back on (with LTE active) and try a test call. It should work for you.
Big thanks to @redpoint73 for helping me figure this out!
Click to expand...
Click to collapse
Thanks for the post this helped me with my issue!!!
Have any of you tried to disable enhanced 4G LTE Mode in network settings instead of slowing you down to 3g?
goo.gl/photos/BX9N2b37Z2Wb1UeQA
[/QUOTE]
italynstylion said:
I'm having a VERY specific issue with my ATT M8 that I can't seem to figure out. First and foremost, I've tried wiping all partitions and starting over....with 3 different ROMS (Liquid, Candy5, Bliss Pop) and none of them allow me to RECEIVE calls. I've even done an RUU back COMPLETELY to stock everything using the ATT stock Lollipop RUU image. When I boot the stock RUU I can again receive calls. Below is the detailed info on the scenario....
Can't receive calls but I'm notified if someone leaves a voice mail.
Making calls from my phone works fine.
If I'm on the phone and someone calls me the phone notifies me like it normally would.
When someone tries to call me, they hear it ring the proper number of times and it does NOT go straight to voice mail.
That last bullet is VERY important. The fact the call doesn't go straight to voice mail is an indication the ATT network knows my phone is indeed powered on and available. Strangely though, it doesn't ring or do anything to otherwise show someone is trying to call.
At this point I'm really stumped. How on Earth is this even possible? Especially after doing the RUU and having the phone work as intended only to try and flash any other ROM later and have it not receive calls. I'm 100% stumped and really need y'alls help.!
**SOLUTION BELOW**
Apparently AT&T is rolling out HD Voice in many areas. It's basically voice over LTE and it's not compatible with many custom ROMS. This is why flashing the stock AT&T RUU made everything work just fine but when I tried ANY custom ROM it wouldn't work.
If this happens to you try the following....disable LTE by turning off mobile data or simply switching to 3G. Then try to call yourself or have someone call you. If the call comes through on your handset it's due to HD Voice having been activated on your account. I called AT&T and explained that I needed HD Voice turned off for my account. You'll likely have to talk to tech support. Ask them when it was activated on your account. Mine was activated last week which is the EXACT time I started having issues. The AT&T tech will ask that you power down the phone whilst they make the changes. Then turn your phone back on (with LTE active) and try a test call. It should work for you.
Big thanks to @redpoint73 for helping me figure this out!
Click to expand...
Click to collapse
phgojiya said:
Have any of you tried to disable enhanced 4G LTE Mode in network settings instead of slowing you down to 3g?
goo.gl/photos/BX9N2b37Z2Wb1UeQA
Click to expand...
Click to collapse
[/QUOTE]
What ROM are you on? I dont have that option to turn off enhanced LTE on my network settings page
grafik2 said:
What ROM are you on? I dont have that option to turn off enhanced LTE on my network settings page
Click to expand...
Click to collapse
If you are on AT&T and suffering this problem, my advice would be to call AT&T and ask them to turn off HD Voice on your account. The enhanced LTE setting on the phone does nothing to help this problem.
redpoint73 said:
If you are on AT&T and suffering this problem, my advice would be to call AT&T and ask them to turn off HD Voice on your account. The enhanced LTE setting on the phone does nothing to help this problem.
Click to expand...
Click to collapse
Gotcha.
i had this happen to me once months ago maybe even a year ago and i called and they turned HD voice off and it worked. it started happening again last week I wonder if ATT reapplied the HD voice setting for some reason
italynstylion said:
I'm having a VERY specific issue with my ATT M8 that I can't seem to figure out. First and foremost, I've tried wiping all partitions and starting over....with 3 different ROMS (Liquid, Candy5, Bliss Pop) and none of them allow me to RECEIVE calls. I've even done an RUU back COMPLETELY to stock everything using the ATT stock Lollipop RUU image. When I boot the stock RUU I can again receive calls. Below is the detailed info on the scenario....
Can't receive calls but I'm notified if someone leaves a voice mail.
Making calls from my phone works fine.
If I'm on the phone and someone calls me the phone notifies me like it normally would.
When someone tries to call me, they hear it ring the proper number of times and it does NOT go straight to voice mail.
That last bullet is VERY important. The fact the call doesn't go straight to voice mail is an indication the ATT network knows my phone is indeed powered on and available. Strangely though, it doesn't ring or do anything to otherwise show someone is trying to call.
At this point I'm really stumped. How on Earth is this even possible? Especially after doing the RUU and having the phone work as intended only to try and flash any other ROM later and have it not receive calls. I'm 100% stumped and really need y'alls help.!
**SOLUTION BELOW**
Apparently AT&T is rolling out HD Voice in many areas. It's basically voice over LTE and it's not compatible with many custom ROMS. This is why flashing the stock AT&T RUU made everything work just fine but when I tried ANY custom ROM it wouldn't work.
If this happens to you try the following....disable LTE by turning off mobile data or simply switching to 3G. Then try to call yourself or have someone call you. If the call comes through on your handset it's due to HD Voice having been activated on your account. I called AT&T and explained that I needed HD Voice turned off for my account. You'll likely have to talk to tech support. Ask them when it was activated on your account. Mine was activated last week which is the EXACT time I started having issues. The AT&T tech will ask that you power down the phone whilst they make the changes. Then turn your phone back on (with LTE active) and try a test call. It should work for you.
Big thanks to @redpoint73 for helping me figure this out!
Click to expand...
Click to collapse
Thank you so much! I've been looking everywhere for a solution after I installed the Resurrection Remix Rom 5.7.4 on a replacement HTC M8 that I bought new. Love these now 3+ year old phones but not recieving phone calls was crazy. I thought I would be forced to go back to stock.
Hello, I would like to preface this post by saying I'm a complete noob to XDA Forums and custom ROMs as well. I've know about XDA Developers for years, just never been much of a tinkerer when it comes to Android, I just prefer stock.
Well recently, I bought a used LG G3 because the deal was just to good to pass up. It was my first time using a ROM other than stock and it was utterly disgusting in comparison. I hated it so much I installed my first ROM ever, and it was Candy5 for I heard CynogenMod stopped supporting the LG G3 is some capacity. Well, I've been using it for a while now and made it look as close as I could to stock, there's just one problem.
I recently enabled Wi-Fi calling on Ting. The device was a Verizon model, but I purchased it unlocked, and activated it on the MNVO Ting. Well, it wasn't working so I was wondering what's up. I read that you had to enable it within the devices settings, but all guides were not specific to the custom ROM I had installed, and even following along as closely as I could, the option for Wi-Fi calling wasn't there. I've read that if Wi-Fi calling doesn't appear, your device doesn't support it. But, everywhere I've read, has been consistent that Wi-Fi calling is supported on the LG G3.
So, I ask you long time tinkerers, do you know how to enable Wi-Fi calling within the Candy5 ROM? Does it just not support it? I even used the neat search feature within the settings app and couldn't find a switch for it. Please help!
NeatAndClean said:
Hello, I would like to preface this post by saying I'm a complete noob to XDA Forums and custom ROMs as well. I've know about XDA Developers for years, just never been much of a tinkerer when it comes to Android, I just prefer stock.
Well recently, I bought a used LG G3 because the deal was just to good to pass up. It was my first time using a ROM other than stock and it was utterly disgusting in comparison. I hated it so much I installed my first ROM ever, and it was Candy5 for I heard CynogenMod stopped supporting the LG G3 is some capacity. Well, I've been using it for a while now and made it look as close as I could to stock, there's just one problem.
I recently enabled Wi-Fi calling on Ting. The device was a Verizon model, but I purchased it unlocked, and activated it on the MNVO Ting. Well, it wasn't working so I was wondering what's up. I read that you had to enable it within the devices settings, but all guides were not specific to the custom ROM I had installed, and even following along as closely as I could, the option for Wi-Fi calling wasn't there. I've read that if Wi-Fi calling doesn't appear, your device doesn't support it. But, everywhere I've read, has been consistent that Wi-Fi calling is supported on the LG G3.
So, I ask you long time tinkerers, do you know how to enable Wi-Fi calling within the Candy5 ROM? Does it just not support it? I even used the neat search feature within the settings app and couldn't find a switch for it. Please help!
Click to expand...
Click to collapse
Yeah WiFi calling won't be an option on AOSP ROMs... Its cooked into the stock software (for at least t mobile) and only works on stock based ROMs. There was a developer that tried to use the code from I BELIEVE the nexus 6 and adopt it to our devices but it never got pushed through. If you want WiFi calling/VolTE, stick with stock ROMs.
yanowman said:
Yeah WiFi calling won't be an option on AOSP ROMs... Its cooked into the stock software (for at least t mobile) and only works on stock based ROMs. There was a developer that tried to use the code from I BELIEVE the nexus 6 and adopt it to our devices but it never got pushed through. If you want WiFi calling/VolTE, stick with stock ROMs.
Click to expand...
Click to collapse
Ah, I see. Hopefully some day it would be available on custom ROMs. Using the stock ROM is not even worth the gloriousness of Wi-Fi calling, and that's really saying something, because my room is a complete dead zone for reception. I have to walk out on my porch every time I want to place / receive phones calls or SMS texts.
NeatAndClean said:
Ah, I see. Hopefully some day it would be available on custom ROMs. Using the stock ROM is not even worth the gloriousness of Wi-Fi calling, and that's really saying something, because my room is a complete dead zone for reception. I have to walk out on my porch every time I want to place / receive phones calls or SMS texts.
Click to expand...
Click to collapse
Yeah I completely feel your problem. Over at my house (which is in the maybe 10 minutes from the main bay area) there is NO reception, only when you walk down the street is there reception. When I was on Verizon I got their WiFi booster thing... Now that I'm on T mob, I use WiFi calling bakdd info their ROMS
Hello, im on cm 12.1 and recently i have no call audio, calling works fine on facebook and the like, but not when im calling someone from my contacts , ive tried factory reset, flashing different rom , back to stock and nothing works ,can someone help me???
dpwguenther said:
Hello, im on cm 12.1 and recently i have no call audio, calling works fine on facebook and the like, but not when im calling someone from my contacts , ive tried factory reset, flashing different rom , back to stock and nothing works ,can someone help me???
Click to expand...
Click to collapse
Need more info....download samsung phone info and post a screenshot of the firmware tab. If your bootlader and baseband dont match, theres your problem. If they do, try reflashing stock (twice) then doing a tactory reset from the stock recovery right after. If after that the issue is still present....probably something else.....mabey hardware related. Good luckl
Do you use bluetooth? I had a very similar problem and figured out that the only time I had call audio was when I was using a bluetooth headset or the bluetooth in my car. I don't know what sets it off but I've done some searching on this problem and it appears to be common among GSM GS4 owners, and even doing stuff like a complete reset doesn't fix it.
The one fix that I did find, that helped some people, was to go into Google Now and disable "Okay Google" detection from any screen. Several people found that that worked. But I didn't have that feature enabled anyway so it didn't apply.
I don't know if the same problem occurs with CDMA GS4s; my wife has a Sprint GS4 and doesn't have the problem but that doesn't mean it doesn't exist. I think it was just AT&T and T-Mobile GS4 owners who reported this.
lordodin912 said:
Need more info....download samsung phone info and post a screenshot of the firmware tab. If your bootlader and baseband dont match, theres your problem. If they do, try reflashing stock (twice) then doing a tactory reset from the stock recovery right after. If after that the issue is still present....probably something else.....mabey hardware related. Good luckl
Click to expand...
Click to collapse
My bootloader is nb4 and baseband is foh3, but it's been that way for a while now, and this problem is only recently, also I've tried that and it didn't work
Sent from my SGH-M919 using XDA Free mobile app
Mama Luigi said:
Do you use bluetooth? I had a very similar problem and figured out that the only time I had call audio was when I was using a bluetooth headset or the bluetooth in my car. I don't know what sets it off but I've done some searching on this problem and it appears to be common among GSM GS4 owners, and even doing stuff like a complete reset doesn't fix it.
The one fix that I did find, that helped some people, was to go into Google Now and disable "Okay Google" detection from any screen. Several people found that that worked. But I didn't have that feature enabled anyway so it didn't apply.
I don't know if the same problem occurs with CDMA GS4s; my wife has a Sprint GS4 and doesn't have the problem but that doesn't mean it doesn't exist. I think it was just AT&T and T-Mobile GS4 owners who reported this.
Click to expand...
Click to collapse
I don't have Bluetooth, I've tried it with a wired headset and even that didn't work, but what's so puzzling about this is that my calling works fine with Facebook messenger calling feature, hangouts and things like that
Sent from my SGH-M919 using XDA Free mobile app
Edit:
Nevermind. It worked twice then I tried calling a different phone and it broke again. I will keep searching and update.
Original:
I have had this issue intermittently for the past year. It was fixed for about 6 months then two weeks ago started occurring again. Today I flashed a new Rom (PacMan) and the M919UVUFOK3_M919TMBFOK3_TMB firmware. That did not fix it. I was connecting to a 5Ghz WiFi so on a whim I forgot that network and made a call without WiFi enabled. Call worked!
So I connected to my 2.4Ghz WiFi and it is working again. I would try turning off WiFi and see if your calls go through if so it could be 5Ghz or the router...maybe a forget network / reconnect to network will fix it consistently.
Hope this helps you and if anything new comes up I will let you know.
So an update. I finally just gave up on it. My wife had an old phone I remembered (from 2 - 3 years ago) that was ran over and the digitizer broke. I just took her guts and put it in my phone and now it magically works. Hopefully it stays that way.
Should have done this years ago as my phone would no longer charge with the USB Cable nor was my SD Card accessible. Now it is all functioning right again.
dpwguenther said:
My bootloader is nb4 and baseband is foh3, but it's been that way for a while now, and this problem is only recently, also I've tried that and it didn't work
Sent from my SGH-M919 using XDA Free mobile app
Click to expand...
Click to collapse
So after flashing stock NB4 twice.....and factory resetting after from stock recovery, your still not getting call audio?.....doesnt make sense....try again and make sure the bootloader and baseband match.....and dont reboot into download from the OS.
For anyone having issues with no call audio through cell service but for some reason it works through data calls through whats app or facebook messenger, etc ,i have been having the same problem for awhile now. I believe i have traced it to be a hardware issue with the middle frame, when looking at the phone with the battery cover open on the top right over by where there are two markings R1 and L1. There is a module there labeled J-AT TMGA 7-3. When i was having issues i noticed that if i put slight pressure on that module my audio would fade back in on the call but if i put too much pressure it goes away again. If it is a hardware connectivity issue it would explain why slunked was able to get his phone working again by changing the guts in the unit. Im currently waiting for a middle frame and a blue cable for the antenna to confirm if this is indeed the issue.
Hello All,
After I fixed the frozen boot image, I finally got into the ROM itself... but I'm sill having a few issues.
I flashed this kernel: https://forum.xda-developers.com/tmo...chwiz-t3229557
I then flashed the Darthstalker ROM here: https://forum.xda-developers.com/tmo...aroma-t3217247
However... I'm fairly new to root/flashing... so I've encountered a few problems.
-When calling or receiving phone calls... the other party can not hear me. So my phone function doesn't work. They can only hear me on speaker phone and even on speakerphone I'm hard to hear.
-My data will only work well/fast when changed to "LTE only" under mobile data settings. If I choose LTE/3g/2g option, It goes down to 4g service.
-The unrestricted tethering mod is not working (This could be due to meeting my 5gb cap this month, so I may have to wait till next month to reset? Maybe? I'm not sure. Or can I call TMobile and add more hotspot data, then drop it next month when the hotspot hack works/resets?
Any clue what could be causing these issues? Maybe I have an old baseband/modem running? Not sure how I would find a fix, as I'm not sure which one I'll need. I'm running G928TUVS4DPH2 and kernel 3.10.61 stock modified kernel.
Thanks to all who respond!
Foye said:
Hello All,
After I fixed the frozen boot image, I finally got into the ROM itself... but I'm sill having a few issues.
I flashed this kernel: https://forum.xda-developers.com/tmo...chwiz-t3229557
I then flashed the Darthstalker ROM here: https://forum.xda-developers.com/tmo...aroma-t3217247
However... I'm fairly new to root/flashing... so I've encountered a few problems.
-When calling or receiving phone calls... the other party can not hear me. So my phone function doesn't work. They can only hear me on speaker phone and even on speakerphone I'm hard to hear.
-My data will only work well/fast when changed to "LTE only" under mobile data settings. If I choose LTE/3g/2g option, It goes down to 4g service.
-The unrestricted tethering mod is not working (This could be due to meeting my 5gb cap this month, so I may have to wait till next month to reset? Maybe? I'm not sure. Or can I call TMobile and add more hotspot data, then drop it next month when the hotspot hack works/resets?
Any clue what could be causing these issues? Maybe I have an old baseband/modem running? Not sure how I would find a fix, as I'm not sure which one I'll need. I'm running G928TUVS4DPH2 and kernel 3.10.61 stock modified kernel.
Thanks to all who respond!
Click to expand...
Click to collapse
G928, isnt that a s6+? I tried to follow the kernel link but 404. I would shoot to the s6+ forum and aquire a differnt kernel or hunt around for a call patch. It seems you may be in the wrong forum?