I've been going back and forth with Sprint for the past two weeks (since I got the phone) to get Google Voice integration to work. I'll skip all the steps and issues we had and just tell you that the way to do it is to turn off WiFi calling and deactivate the service entirely before dialing *28XXXXXXXXXX to forward your calls to the GV voicemail. It's also a good idea to wait at least a minute after you do that and reboot your phone before you make the call. For some reason, even after this device comes back on after a reboot, it continues to reset various settings and services in the phone.
Thank you so much. It worked!
Related
I'm integrated with google voice (using my existing sprint number).
1-2 calls a day (I only get 5-10 calls a day) will ring and ring and finally go to voicemail from the caller's perspective. With my phone sitting on the couch next to me all I'll get is the alert for the voicemail through the google voice app (no ringing, no missed call notification through sprint or google voice, ONLY a voicemail notification)
Anyone else having issues?
Yes, this happens to as well. Very annoying. To test it I had gmail open and my phone next to me and had someone call me. My phone started ring 15 seconds after my gmail alerted me there was a call incmming. This time varies, sometimes its immediate, and sometimes the phone doesn't ring before vm picks up. Gmail almost always was nearly instant.
I'm not integrated though I do forward to GV. While testing my call filtering scripts, about half the calls would simply not even ring or forward on my Epic, with and without the scripts enabled.
The only thing done to this phone is the revolutionary root method to get the tether app. While making an outgoing phone call to 2-3 different phone numbers, the phone would buzz to show it did connect. Then about a second later the screen goes back to the dialer screen. Any idea's??? Thanks.
Does the phone number you're calling have a +1 or other international code in front of the number? The dialer really doesn't like that. There should be a setting in the calls settings for plus code dialing where you should be able to adjust it. But I haven't been on a stock ROM for a while, so I can only assume it's there.
You can call sprint and have them reprovision (re-activate) your phone, that may help. The fact that you are rooted shouldn't have anything to do with problems making calls, thats usually a network issue.
I've had the same issue. Make a phone call and before it even dials it goes straight to lock screen. Or sometimes it does dial then stops the call and goes back to lock screen. I'm on CM7 so I just figured it was a poor signal causing mine. Sense roms do not seem to do this for me.
I've the S4 for a little over a week, but it's been a rather busy week so I haven't given it my full attention as yet. I really like it so far, I haven't gotten all the bells and whistles to work and I'm testing battery life with them disabled vs enabled etc. But I'm not really doing much else with it yet.
The only actual issue I'm having is receiving phone calls. When someone calls me, it takes a couple rings on their end before my phone starts ringing (I've encountered this with Sprint before though) but then when I try to answer the call, I don't get the person on the other end. I get a recorded message telling me I've got an incoming call from (name of caller in my contacts list) and if I want to accept to press 1 now. The message takes so long to get to that point that by the time it tells me to press 1 to accept the call, the call goes into voicemail.
I don't receive a lot of phone calls, but I would like to be able to actually answer them when I do. As of now when someone does call me I have to call them back.
This message plays AFTER I've 'accepted' the call on the screen and it plays through the handset not the speakers. I have Google voice set up for my voicemail.
Any assistance would be greatly appreciated.
Sounds like you have google voice setup or you used to. You will have to go to the site on your pc to disable it.
Sent from my icrap 2 using Tapatalk HD
cruise350 said:
Sounds like you have google voice setup or you used to. You will have to go to the site on your pc to disable it.
Sent from my icrap 2 using Tapatalk HD
Click to expand...
Click to collapse
I thought Google Voice had something to do with it but I didn't think of checking the settings via PC.
For anyone else with the same issue: Google.com/voice>settings>calls> call screening off.
As the title says, when somebody calls me on one of my sip numbers and I'm on wifi I need to put the phone on speaker a number of times before I can start hearing anything from the call. After that it works but it might lose audio again at some later point and cycling the speaker setting brings it back.
I haven't noticed this before 4.4.2 and I can't reproduce it while on 3G. Any ideas?
Actually phone also directly drops the call or even reboots from time to time while doing this. Cool software, bro.
As a late update - I followed Samsung support's advice and reset the phone to factory defaults (from recovery) - then only installed a minimal set of programs and modified a minimal set of options. Receiving sip calls is still buggy or causing the phone to reboot.
I have a stock, non-rooted Verizon GN3, which behaved pretty much flawlessly in general, and with Bluetooth Headsets in particular, prior to the KitKat update.
This behavior occurs with both my BlueAnt S4 Visor device, and a Bose Series 2 Headset. When I turn either on, it quickly connects. With the phone locked, screen off, if I initiate the connection from either device, the Voice Dialer comes up, and I can initiate a call. The call connects, and I can hear and speak through the Bluetooth device. Everything works as expected.
But if I then try to make another call, it takes at least 2 additional tries to get the Voice Dialer to come up. The first time, the screen comes on briefly, then turns off, sometimes with the grey screen preceding the Voice Dialer briefly appearing. After a couple of more tries, the Voice Dialer comes up.
But after I have it place a call, the audio send/receive stays in the phone, and doesn't transfer to the Bluetooth device. This pretty much defeats the purpose of having it in the first place!
If I turn off either Device, turn it on and reconnect, the same cycle starts up again. It works properly the first time, but messes up after that.
With the BlueAnt S4, I removed the pairing from my GN3, effectively deleting the device, and then turned off the phone. I then did a complete reset on the S4. Turned the phone back on, re-paired, but this didn't fix it.
This is extremely annoying, to say the least.
I have examined all my settings, and they seem correct. I went to Google Search settings, Voice settings, and tried it with the Bluetooth headset ('records audio through Bluetooth headset if available') both checked and not checked, and observe the same behavior.
I welcome suggestions on how to fix this, and getting it to work consistently and correctly, as it did before KitKat.
I would consider a factory reset on the GN3, if I were convinced this would fix the problem. But I'd hate to go through that hassle, and encounter the same problem again.
I have noticed several anomalies with the kitkat update. I was hoping there was a way to roll back the update
Sent from my SM-900V, unrooted
Well, I've made some progress, and I think the problem originates in a recent update to "Google Search." I found many reports of Bluetooth related problems that were remedied when the update was rolled back.
So, I went ahead and rolled back the Google Search Update, and in fact, went ahead and Turned if Off completely.
I tried out my Bluetooth Headset (the Bose earpiece, haven't tested on the BlueAnt yet), and it works perfectly, as before. And better yet, when I touch the BT button, S-Voice comes up, rather than the plain Voice Dialer, so I can not only place calls, but initiate navigation, send a text, or whatever I would like to do. And it seems to respond each and every time.
We'll see what happens over time, and if there are any unanticipated consequences to turning Google Search off, but so far so good.
If this turns out to be the answer, it will be a Google Search issue (which would hopefully be fixed over time), rather than a KitKat issue as such.