I have fixed the issue after numerous calls to LG and Verizon wireless. I am so disappointed with both companies. The vocoder software is faulty. from dialpad press ##PROGRAM980 and SEND to place call, the service code is 000000 then you goto Voice SO select each tab and change from Wild Card to 13 QCELP. Restart phone and its fixed
kmatone85 said:
I have fixed the issue after numerous calls to LG and Verizon wireless. I am so disappointed with both companies. The vocoder software is faulty. from dialpad press ##PROGRAM980 and SEND to place call, the service code is 000000 then you goto Voice SO select each tab and change from Wild Card to 13 QCELP. Restart phone and its fixed
Click to expand...
Click to collapse
Just did this and work perfectly now! It was the only thing bothering me about this phone. Thank you!
Cool. What exactly does this fix? I haven't noticed call issues. I changed it anyway. Does this improve call quality or what?
What is voice so?
Sent from LG G2 @sdny8
player911 said:
Cool. What exactly does this fix? I haven't noticed call issues. I changed it anyway. Does this improve call quality or what?
Click to expand...
Click to collapse
according to my gf i sound as thou i'm sick. others have told me too. apperantly my gnex had way better sound quality cus i never that before switching to the G2.
Just tried this. Anxious to see if this makes a difference.
tstretch said:
Just tried this. Anxious to see if this makes a difference.
Click to expand...
Click to collapse
Same here
Sent from my VS980 4G using Tapatalk
Wildcard lets it switch between voice codecs. QCELP 13 is the old 13Kbs voice codec replaced with EVRC which was replaced with SMV inn turn replaced with CDMA2000 for 4G networks(4GV successor of 3GGP2 type[Qcelp-SMV] codecs). 4GV is dynamically prioritized per network. EVRC-B is half and quartet speed. We do not have any later options, just QCELP and EVRC. QCELP is uncompressed 13Kbs, EVRC 8 is compressed with but with higher quality codec at 8Kbs. Default is EVRC8 home and roaming, page is wildcard to auto select best for the particular network. The only thing it may fix is using a tower that is overloaded with bad compression. Note that forcing the specification can cause more overload to the 3G signal, in turn, just making things worse for everyone. If I'm not mistaken, the way towers and plans are set up, a 4GV codec would cause using voice com to eat into data plan. I do not think most carriers are set up to sniff the data type to determine if it is indeed voice data, hence we don't have awesome voice quality that we are more than capable of having. Hope this helps.
I dont have Voice So in my menu.
It says Verizon Hidden menu
Field Tests
Device Security
W2bi testing
CMAS test message
Am I looking somewhere wrong?
casiouser said:
I dont have Voice So in my menu.
It says Verizon Hidden menu
Field Tests
Device Security
W2bi testing
CMAS test message
Am I looking somewhere wrong?
Click to expand...
Click to collapse
Select Field Tests....Voice SO is under there.
Does it still work when on 3g connection?
Sent from my Nexus 7 using xda app-developers app
It will. We have no 4G codecs. Unless you have problem with the default codec on your towers, this will not help, only hinder quality. I have no issues with default codec or quality at and around my location. Baltimore to D.C..
When I tried this the settings didn't survive a reboot.
Sent from my VS980 4G using Tapatalk
Mine stuck even after a reboot
I tried this on mine (Malladus) and wife's (stock), both (..phones) are fine after reboots and all.
Just can't yet confirm any differences.
QCELP-13 worked perfectly
EVRC 8k gave me some of the digital clipping type noise
EVRC-B works good and has minimal clipping
So the QCELP seemed to worked best over all.
Also, no issues with the settings surviving a reboot.
I'm test-driving this, too. Somebody at Android Central forum reported a possible impact on battery life. Anybody seeing anything like that?
this worked for me. The call quality still isn't the best but I am not getting that annoying noise anymore.
rfarrah said:
I'm test-driving this, too. Somebody at Android Central forum reported a possible impact on battery life. Anybody seeing anything like that?
Click to expand...
Click to collapse
I definitely have seen a sizable increase in nlpWakelock since I made this change but I didn't think it could be related... Could it be?
Just tried this on my Verizon device, sound is much improved.
Sent from my VS980 4G using xda premium
Related
I bought a dash 3g!!!
but.... it had an issue with a clicking sound every so often on the other end of the call, several people reported hearing the same sort of sound. i called my phone and could hear it as well, its like a switching channels kinda sound.
I tried everything i could think of, turning off 3g, turning off bluetooth, trying with or without the headset, new sim card, moving to many different locations, but still it kept happening so i exchanged it and twice viola! same thing on 3 different phones...... am i alone on this guys???
Have you tried turning off voice privacy in the settings? It's possible that for whatever reason that is toggling on and off and could explain the click. By the way, next time try having a more descriptive topic name and using fewer question marks and exclamation points.
djh816 said:
Have you tried turning off voice privacy in the settings? It's possible that for whatever reason that is toggling on and off and could explain the click. By the way, next time try having a more descriptive topic name and using fewer question marks and exclamation points.
Click to expand...
Click to collapse
ok i dont see any options for that over there.... any other ideas
to get to ur voice privacy settings :
settings > phone > more... > "voice privacy" - disable it, and see how that works out.
If this is any help, I'm in Europe with an original HTC Snap.
No voice issues like you described. Sound is loud and clear.
SoCalSpecialist said:
to get to ur voice privacy settings :
settings > phone > more... > "voice privacy" - disable it, and see how that works out.
Click to expand...
Click to collapse
voice privacy is a old feature is only on cdma network technology phones... still having problems here guys
not sure if it's just your area or not but i'm using a 3G dash in southern california w/ no audio issues (3G or GSM)
T-mobile is currently investigating 3g network issues in my area (Detroit metro area) because i have the problem with all tmobiles 3g phones, the old dash worked fine
I've had this issue occur several times. It's not 100% repeatable, but occasionally I lose 3G, 1X and all data connectivity after receiving a phone call.
I do NOT have WIFI enabled when this happens. I've seen posts referring that issue.
When this happens the only cure is a full power down reboot. Toggling Airplane mode doesn't work, infact it just hangs trying to toggle the mode. Toggling Mobile Network in settings doesn't work either.
I've seen this problem since the very first 2.2 leak on 7/27. I've also seen this running Virtuous 2.0 rom. I don't think this is ROM related, rather a generic 2.2 or radio issue (I've seen this happen on the 2.05 and 2.15 radio)
This problem seems to happen in low signal conditions.
Any ideas?
That's how it is with Verizon CDMA, no simultaneous voice and data. There is a network upgrade they can apply to correct it and give them more efficient use of bandwith as well but I guess they are not interested. I hear they are going GSM in the next few years anyway.
marcmarshall said:
That's how it is with Verizon CDMA, no simultaneous voice and data. There is a network upgrade they can apply to correct it and give them more efficient use of bandwith as well but I guess they are not interested. I hear they are going GSM in the next few years anyway.
Click to expand...
Click to collapse
I didn't mean to imply that they work at the same time. I meant no data connectivity after I hang up.
Sent from my ADR6300 using XDA App
Oooh. Well I've had 3 of these phones now and I have had that problem also. Verizon told me to update the network by calling *228 and choosing option 2. Seemed to help.
marcmarshall said:
Oooh. Well I've had 3 of these phones now and I have had that problem also. Verizon told me to update the network by calling *228 and choosing option 2. Seemed to help.
Click to expand...
Click to collapse
I wonder what that has to do with it. I thought that had to do with roaming which I wasn't.
Sent from my ADR6300 using XDA App
I think that's mostly what they say first for any network problem.
It sounds like you have an app that is fouling your data connection. Do you have any third-party phonebook/contact list apps? I'd look there first.
As for the *228 Option 2 (or the PRL path for your carrier), that is standard telco procedure for "get off my phone, I want to go back to having my thumb up my backside." All it does is update your Preferred Roaming List.
You could try Option 1 or 3, which are programming related, but if your rep tells you Option 2, do not lie & tell them you just did it. VZW's system tells the rep the last time you did - including the date of your activity. However, you can snicker, knowing you got a loser rep.
Warning - listen carefully when using O1 or O3. Let it repeat the instructions if you're not 100% sure, else you will be calling tech support & possibly getting one of the losers. Or, you could get a gem. BTW - O3 is hidden - you have to trust it is there.
DesertWildman said:
It sounds like you have an app that is fouling your data connection. Do you have any third-party phonebook/contact list apps? I'd look there first.
As for the *228 Option 2 (or the PRL path for your carrier), that is standard telco procedure for "get off my phone, I want to go back to having my thumb up my backside." All it does is update your Preferred Roaming List.
You could try Option 1 or 3, which are programming related, but if your rep tells you Option 2, do not lie & tell them you just did it. VZW's system tells the rep the last time you did - including the date of your activity. However, you can snicker, knowing you got a loser rep.
Warning - listen carefully when using O1 or O3. Let it repeat the instructions if you're not 100% sure, else you will be calling tech support & possibly getting one of the losers. Or, you could get a gem. BTW - O3 is hidden - you have to trust it is there.
Click to expand...
Click to collapse
No third party apps like that. I have tried option 1 and 2 but I didn't know about option 3. I'll give that a try. Thanks.
Sent from my ADR6300 using XDA App
I've noticed that the Nexus 4 is unusable for VoIP calls due to no echo cancellation, and no background noise filtering (using the second microphone). This issue occurs for all VoIP calls, no matter the client. Some clients attempt to fix this with software filtering, etc, but none do a very good job.
Please star the following issue on the Android bug tracker to bring this to Google's attention. https://code.google.com/p/android/issues/detail?id=41626 The following comment provides more details on the issue:
SIP is unusable on the Nexus 4 because the device doesn't provide an AcousticEchoCanceler[1], AutomaticGainControl[2] or NoiseSuppressor[3]. Additionally, the VOICE_COMMUNICATION[4] audio source designed for VoIP applications returns the same audio as if the application asked for raw microphone data, which is completely unusable for VoIP calls.
The reason cell calls sound good is because the cellular phone takes advantage of the second microphone on the device to perform background noise cancellation and presumably has a hardware chip for echo cancellation. Why these necessary items are not exposed via the APIs listed below on Google's flagship phone is a mystery to me.
Also, the reason SIP is still pretty good on the Galaxy Nexus is because it provides implementations for the AcousticEchoCanceler, AutomaticGainControl and NoiseSuppressor. So even though it doesn't have a second microphone, it does some processing on the audio (via hardware or software) to make it usable for a call. The Nexus 4 provides none of this.
[1] http://developer.android.com/reference/android/media/audiofx/AcousticEchoCanceler.html
[2] http://developer.android.com/reference/android/media/audiofx/AutomaticGainControl.html
[3] http://developer.android.com/reference/android/media/audiofx/NoiseSuppressor.html
[4] http://developer.android.com/refere...Recorder.AudioSource.html#VOICE_COMMUNICATION
Click to expand...
Click to collapse
Have other people noticed this issue. I've noticed it with the stock SIP client, sipdroid, csipsimple, and Talkatone.
I have only used GrooVe IP, and it works fine with stock settings.
I use sipdroid and it works well. No complaints.
Sent from my Nexus 4 using xda app-developers app
Try talkatone. Works well most of the time for me.
Sent from my Nexus 4 using xda premium
While indeed it is an issue, I'm seeing good enough results with sipdroid using gsm codec. Did run into major issues recently because newer cm nightlies changed mcast filtering / ARP. Manually revert that and its fine again. At the least, I've struggled with sip calls with many phones in the past and this is the smoothest experience yet (never had the gnex).
Note I used to use speex for its obvious benefits over gsm but gsm seems to work fine for me and I figure it may be less CPU intensive
Sent from my Nexus 4 using xda app-developers app
Try making a call outside, or with background noise. When I make a call while walking down the street, or in a windy location, the background noise is quite loud for the other person. I've tried several different clients and configurations, and all of them have this issue. The problem is that the phone is not filtering out background noise using the second microphone, and software can only attempt to make this better.
Slightly old thread here, sorry, but I'm wondering if anyone has tried using the built-in VOIP functionality. I currently have a T989 but am considering Mako, and I always had better results using CM10's built-in VOIP than with GrooveIP (i.e. people would complain a whole lot about static and echo when I used GrooveIP). Can anyone comment on this?
I agree. Tried all voip apps from market: groove, talkatone, spare phone, vonage, Skype. Terrible results. I did find one that is working great though (knock on wood): EverVoice. Tried it over the last few days and haven't had any problems on wifi and T-Mobile 4g.
Sent from my Nexus 7 using xda app-developers app
sec6 said:
I agree. Tried all voip apps from market: groove, talkatone, spare phone, vonage, Skype. Terrible results. I did find one that is working great though (knock on wood): EverVoice. Tried it over the last few days and haven't had any problems on wifi and T-Mobile 4g.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Edit: Spoke too soon. EverVoice is unreliable also. Decided to just ditch google voice and add prepaid minutes to tmobile 30 dollar prepaid unlimited plan.
Pandemic187 said:
Slightly old thread here, sorry, but I'm wondering if anyone has tried using the built-in VOIP functionality. I currently have a T989 but am considering Mako, and I always had better results using CM10's built-in VOIP than with GrooveIP (i.e. people would complain a whole lot about static and echo when I used GrooveIP). Can anyone comment on this?
Click to expand...
Click to collapse
Built in voip also echos for me on the Nexus 4. I wondering if regular voice calls go through a different chip or something that does echo cancellation. Is it possible that this chip isn't available for voip?
I am using the built in SIP client with Callcentric. I was using SipSorcery, but I had "no audio" issues on HSPA. Callcentric is NYC based (as am I) so the latency is much better, and echo is reduced as well. My only suggestion is find a SIP server with the lowest ping / least hops.
Skype was excellent on my Nexus S, but has a lot of issues on my N4, so I scrapped it.
For those of you who want the best quality out of your $30 smartphone plan, I made a 12-part video tutorial showing how to do it.
http://www.youtube.com/watch?v=u9DzN1Pu6-Q&list=PLE_de-PBwrTSUMm-Y48aiOOHt_YyT69t0
It's much better than GrooveIP, Vonage, Talkatone, Pbxes.org, and everything else, especially those with the "one big green button" solution.
This method gives you HD Voice (G.722 codec), bettery battery life, and much better options for logging/blocking/recording. You can even set up hold music. Yup, I said hold music.
It used to be difficult to set up until I made it as clear as the nose on your face in the video tutorial (with actual commentary instead of techno music).
Spread the word if you do it and it works out for you. I believe everyone deserves high quality and limitless VoIP WiFi/4g calling.
HowDoIVoIP said:
For those of you who want the best quality out of your $30 smartphone plan, I made a 12-part video tutorial showing how to do it.
http://www.youtube.com/watch?v=u9DzN1Pu6-Q&list=PLE_de-PBwrTSUMm-Y48aiOOHt_YyT69t0
It's much better than GrooveIP, Vonage, Talkatone, Pbxes.org, and everything else, especially those with the "one big green button" solution.
This method gives you HD Voice (G.722 codec), bettery battery life, and much better options for logging/blocking/recording. You can even set up hold music. Yup, I said hold music.
It used to be difficult to set up until I made it as clear as the nose on your face in the video tutorial (with actual commentary instead of techno music).
Spread the word if you do it and it works out for you. I believe everyone deserves high quality and limitless VoIP WiFi/4g calling.
Click to expand...
Click to collapse
I did this method....works very good except for an echo....
I fixed the echo(over 3g) on the nEXUS 4 doing this:
Csimple has an option to enable software control or volume instead of the android OS/hardware.....enable it...I suspect that fixed it combined with the following:
Echo cancellation(never worked until ti checked the above....works great now) in Csimple.
Faux kernel or something compatible with his software for fixing audio gain.
Faux sounds and Faux speakers app. I chose the quality preset plus my own sleight modifications and also the voice setting for speakers.
Echo was annihilated.....I also tried voice audio detection but I didn't like it...
I posted this in the PIAF thread since I used that method but this will help you guys as well.
Nexus 4 SIP echo fix - It's pretty bad for many users but this solved it 100% for me
It worked for me and I tested numerous different setting and configurations along with measuring my latency to ensure it works. YMMV but it's easy to try. At first I thought it was a Latency issue since echo didn't occur over wifi but with ping times lower than 60ms I still got echo over 3g without this method.
I'm using the silk codec(Silk 24 wifi/Silk 12 or 16 over 3g/4g); YMMV with other codecs.
*Before starting*
Root your phone, flash radio .27 or .33 if your on T-mobile or in Canada: We want to enable Nexus 4g! 3g is usually fine but 4g tends to have significantly lower latency(3G: 50-70ms versus 4g: 20-40ms). Sometimes my 3g speed was fine but latency sucks(100-250+ms)....3g has enough speed for VoIP but any latency issues/spikes/jumps will ruin a call.
This is a good guide to follow: Hippowise"s guide
For the first few steps plus a audio fix some users encountered with the radio downgrade; there are 2 scripts you can run via any terminal emulator app scripter(I used this $Scripter). The actual Script to be run can be found on XDA in the nexus 4 LTE thread(download or save them as txt files). The XML file I suggest editing your self(I just replaced all instances of epc.t-mobile with fast.t-mobile for T-mo users).
If said "scripting...wut?" just follow Hippowise's guide to the tee. Scripting is just faster/easier.
It took a few days for my 4g/LTE to kick in so be patient; It's worth the trouble!
**Now to the guide**
First, get the Faux kernel for Nexus 4 or use another kernel that has applied his patch.
2nd, get his apps from the Play store(they cost money but worth it): Faux Speakers and Faux Sound: Configure them for "voice" and "quality" respectively(you can adjust on your own from there, I upped the gain a bit).
3rd, Use Csipsimple and enable "Software volume control" instead of the default android/os/hardware based volume/gain control. I wonder if this bypasses Faux and puts volume control solely in the hands of Csipsimple. I would do 1-3 steps anyway because it fixes the SQ issues in general with the nexus 4.
4th. Enable Echo cancellation; until I did the previous steps, echo cancelation didn't work at all: YMMV.
I choose Echo mode Webrtc becuase Speex echo cancellation didn't work for me. If your codecs are different the other choices or auto might work better. Experiement.
5th: *Optional*
Noise Cancelation: Worked so-so....didn't need so I turned off
Voice Detection: I didn't like it but experiement.
Compact SIP packets: I use it, optional
STUN: I turned it on, I don't think it will hurt.
Audio troubleshooting in the Csip menu has tons of options to mess with. If all else fails, read some guides and experiment. I didn't need to chance anything here but some of it looks promising and has some fixes for specific models like the galaxy.
7th: Latency
Get Speedtest app from the play store and test your speed. In some areas over 3g I would get decent down/up speeds but godawful latency (300ms+ ). If your 3g latency consistently sucks, do the 4g fix for the nexus; Much better latency and I always get 4g in most places on T-mobile.....rural areas might be screwed on getting 4g although I noticed my 3g speeds increased overall after the fix.
8th
Finished; report back in the thread and tell me if it helped!! And if anybody knows a good I.T. position open for a VoIP office/callcenter; let me know cause I'm quitting mine.
Sorry for my ignorance. But all those SIP methods fix all VoIP calls? (Viber, Facebook Messenger, etc).
I just want to fix the terrible echo I am exporting to others Viber users.
Sent from my Nexus 4 using Tapatalk 4 Beta
thesebastian said:
Sorry for my ignorance. But all those SIP methods fix all VoIP calls? (Viber, Facebook Messenger, etc).
I just want to fix the terrible echo I am exporting to others Viber users.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
bump
detdett said:
bump
Click to expand...
Click to collapse
Seems fixed, at least, from the N4's end.
https://code.google.com/p/android/issues/detail?id=42978#c16
raz123 said:
Seems fixed, at least, from the N4's end.
https://code.google.com/p/android/issues/detail?id=42978#c16
Click to expand...
Click to collapse
Nope. Tried to use it on fongo but it didn't work.
Update. Fongo released a new beta today and it seems like the echo problem is gone...
Sent from my Nexus 4 using Tapatalk 4
I tried different voip apps including built-in voip client with CM 10.2. Best sound quality and no echos I've got with CSipSimple with echo reduction enabled.
swimma said:
I tried different voip apps including built-in voip client with CM 10.2. Best sound quality and no echos I've got with CSipSimple with echo reduction enabled.
Click to expand...
Click to collapse
Which cm 10.2 build are you on
Hello, I bought my wife and daughter the S8 Active for Christmas, upgrading them from the Galaxy S6 . Since using the new phones the call quality is horrible. Constant dropping calls, sound quality cutting in and out with voices sounding robotic. Never had these issues with the S6. This all happens in areas that should have no issues with service. Tried all the basics, updating PRL and profile, tried different carrier options. Tried a factory reset just to mark that off the list. I've been going back an forth with Sprint tech support with no progress. I've been searching around online and these forums (great info here) but I haven't found anything to help. Anyone heard or had issues like this?
The phone(s) are both stock, no root or unlocks.
I should note that the only time the phone does not have an issue with call quality is when it is connected to WiFi using WiFi calling.
Thank you
Did you try toggling HD Voice off and on to see if it made any difference?
Sent from my SAMSUNG-SM-G890A using Tapatalk
If that is the same as the LTE enhanced voice then yes. If it's different I haven't seen it but will check.
TyGeR_STD said:
If that is the same as the LTE enhanced voice then yes. If it's different I haven't seen it but will check.
Click to expand...
Click to collapse
I'm on AT&T, but I'm pretty sure thats what Sprint calls it. On both my S6 Active and S8 I had to disable it and the dropped calls ceased and the call quality improved. It seems you've checked everything else (factory reset, clearing cache partition, etc.) so if this doesn't work, I would exchange, maybe for a different phone that would work better in your area. I don't use WiFi calling because it has an echo effect and can also result in dropped calls (at least in my area on AT&T). Good luck and let us know how you make out.
Sent from my SM-G950U using Tapatalk
Using the phones on Sprint.
Since three weeks or so, while on LTE, the incoming voice calls are going directly to voice mail.
Sprint looked at it and changed the Network to 3G and now getting a ring for the incoming calls.
Basically, I am forced to run the phones on 3G service.
Need to go to a service center (which is very far for me) to have the phone looked at.
Anyone facing similar issue?
PS: 2 of the 3 PH-1 phones I have, are having the issue.
Tom23824 said:
Using the phones on Sprint.
Since three weeks or so, while on LTE, the incoming voice calls are going directly to voice mail.
Sprint looked at it and changed the Network to 3G and now getting a ring for the incoming calls.
Basically, I am forced to run the phones on 3G service.
Need to go to a service center (which is very far for me) to have the phone looked at.
Anyone facing similar issue?
PS: 2 of the 3 PH-1 phones I have, are having the issue.
Click to expand...
Click to collapse
Google have updated the dialer recently several times, could it be a bug that shows on Sprint, or do you have spam settings on, which I know has caught other people out. Check/play with spam settings in her dialer app.
(other areas I might check (if not dialer or network). I assume all phones were working before correctly, right? Are they different sims or the same sim in different phones? New sims, ie not old one you have cut down hat are old spec. Do lte settings match on different phones?)
Tom23824 said:
Using the phones on Sprint.
Since three weeks or so, while on LTE, the incoming voice calls are going directly to voice mail.
Sprint looked at it and changed the Network to 3G and now getting a ring for the incoming calls.
Basically, I am forced to run the phones on 3G service.
Need to go to a service center (which is very far for me) to have the phone looked at.
Anyone facing similar issue?
PS: 2 of the 3 PH-1 phones I have, are having the issue.
Click to expand...
Click to collapse
Same issue. Did you get it fixed?
I also have this problem on Sprint.
Sometimes restarting the phone fixes the issue, sometimes it doesn't.
Between this and no longer being able to use Google Voice without using a separate number, I think it's time for me to bail on Sprint.
My wife had this issue a bit back. Only happened when the phone was using VoLTE (verified by a debug menu, *#*#4636#*#*, showing both voice/text and data marked as LTE).
Fix was to disable the Enhanced 4G LTE communications option, which forced the phone too fallback to nonVoLTE while still using LTE for data. Again confirmed using the phone information menu which showed voice as 1xRTT and data as LTE.
Hope this help and that we can get a better fix soon.
serenesilence said:
My wife had this issue a bit back. Only happened when the phone was using VoLTE (verified by a debug menu, *#*#4636#*#*, showing both voice/text and data marked as LTE).
Fix was to disable the Enhanced 4G LTE communications option, which forced the phone too fallback to nonVoLTE while still using LTE for data. Again confirmed using the phone information menu which showed voice as 1xRTT and data as LTE.
Hope this help and that we can get a better fix soon.
Click to expand...
Click to collapse
Has this fix worked for anyone?
jhill110 said:
Has this fix worked for anyone?
Click to expand...
Click to collapse
Dude... His post says this fix worked for him... And it has worked for others...
Sent from my PH-1 using Tapatalk
rignfool said:
Dude... His post says this fix worked for him... And it has worked for others...
Click to expand...
Click to collapse
Didn't work for me.
I turned off the advanced and re provisioned everything is good.
You are the type that likes to belittle people.... Thanks for your non help post.
jhill110 said:
Didn't work for me.
I turned off the advanced and re provisioned everything is good.
You are the type that likes to belittle people.... Thanks for your non help post.
Click to expand...
Click to collapse
Any time...
I love sharing my time with ungrateful idiots that can't bother to read or need the red carpet rolled out for them...
Good luck with your device... Hope you drop it in the river
Sent from my PH-1 using Tapatalk
rignfool said:
Any time...
I love sharing my time with ungrateful idiots that can't bother to read or need the red carpet rolled out for them...
Good luck with your device... Hope you drop it in the river
Click to expand...
Click to collapse
Frustrating isn't it.
autosurgeon said:
Frustrating isn't it.
Click to expand...
Click to collapse
Nah...
I just wish him ill and send him on his way...
Maybe he will learn to read... And realize his device is no more valuable than anyone else's...
But probably not...
Google Voice Essential Phone NO Ring Ring Fix
jhill110 said:
Didn't work for me.
I turned off the advanced and re provisioned everything is good.
Click to expand...
Click to collapse
Didn't work for me either but I figured it out... what I had to do is change a setting under Google Voice in Settings under the tab CALLS change to "Use carrier only" and I did have to turn VoLTE off. I left the Preferred network type as LTE. Phone is working well now, with T-mobile and Google Voice I have been testing it all morning.
:highfive: