Just setting up my new t805 from AT&T (so officially it's a sm-t807a) and noticed it doesn't have a dialer app. No big deal. I use Google Hangouts for all my calls anyway.
Nope. Installed Hangouts app, installed dialer, can't dial out. It lets me dial and brings up the "in-call" screen (blacl screen with big face icon in the middle) but doesn't actually dial.
Anybody know how to fix that? I was hoping to not have to root this tablet but the ability to actually make phone calls is pretty essential.
Okay weirdest thing. Turns out I just can't call the first person in my contacts list. Sorry to waste anyone's time.
Related
So I just bought a new car, and while hooking my dinc up via Bluetooth I noticed that I cant call out from my phone because I have it set to ask every time I make a call if I want to use Google voice...it gets stuck on that screen and fails to make the call.
Is there a way to prevent the Google voice app from asking when calling out via Bluetooth?
Anyone? I could have sworn it worked Thursday when I picked the car up, that's the weird thing...
I'm not sure exactly where it is but there is an option in the settings somewhere that dictates how Google voice handles calls. It can be set to use Google voice, not use it, or ask.
k_nivesout said:
I'm not sure exactly where it is but there is an option in the settings somewhere that dictates how Google voice handles calls. It can be set to use Google voice, not use it, or ask.
Click to expand...
Click to collapse
I think that's for international calls. But, you phone might be dialing an international prefix before the number. That normally wouldn't matter, but Gvoice will take notice of it. I set mine to never ask because I never call internationally.
Ah yeah, I think loonatik is right. So if you do have 1+ before the number, GV will probably pick that up and that might be what's giving you troubles. Maybe?
No, I have it set to always ask...but I was hoping there was some way to override it if the call is made via Bluetooth. I could have sworn I had it working Thursday, but now it just fails because it gets stuck on the Google voice screen ...
Anyone know of any way to override the setting if making a call thru Bluetooth?
Or, an alternative would be for me to turn it off (or on) for all calls and have an easy way to bypass it...
Possible solutions...
Free, but a pain in the butt:
Drop the Google Voice Settings widget on one of your home screens. The third button (the one that looks like a handset inside of a settings button) toggles call modes for GV:
-Use for all calls
-Do not use
-Use for international
-Ask every time
Free, but I have never tried the app so I can't personally comment:
http://www.androidzoom.com/android_applications/communication/google-voice-callback-free_fpin.html
Looks like you could set this up to perhaps side-step the GV behavior of manually answering every time
I was about to write out how to do it with Tasker and the Locale Google Voice Settings plug-in. But I just realized that it doesn't have the all/none/ask choice as a plug-in setting: only the online stuff like forwarding phones, etc. Bummer - but maybe you could contact the dev about future integration
Google Voice always ask and bluetooth
Did you ever find a good work-around or solution for this?
I just got an S4 today, and I was hoping that the Google Voice app on the Android would be similar to the iPhone one. It's not.
I use google voice to call/text my friends (I ported my original # over to Google) and the main number for work. But when I tried making a call over bluetooth in the car, got the same problem as you, it got stuck on the "Always Ask" prompt. The problem with making it never ask, is there is no dialer to just go to like there is on an iPhone when you do want to make a call using Google Voice. So you have to keep switching the option on that widget before every call. So annoying.
Suggestions?
So I just got my GN, and it's pretty freakin awesome! One thing I noticed though is that if I swipe calls to the left to ignore, it sends them to my new voicemail on verizon as opposed to my GV. If I let it ring all the way through though, then it routes to GV. It's not a super big deal because I can just push the power button and ignore calls that way, but still...
Also, the messaging sends through regular texts, and not GV...this last part I had heard before, but in case anyone else didn't know that.
Here's hoping they update the GV app to take care of these things.
My voicemail routing works correctly, however you're right on the auto-reply texts. Even with Google Voice set as the default action for messaging, they still send via the stock app.
Lumenii said:
My voicemail routing works correctly, however you're right on the auto-reply texts. Even with Google Voice set as the default action for messaging, they still send via the stock app.
Click to expand...
Click to collapse
Are you on verizon?
I went through a hassle to get Google Voice setup correctly on this phone. Had to upgrade my Voice account to a full Google Voice number, instead of just a voicemail number. Doesn't really matter, since I'm only using the voicemail functionality of it, but still.
Go to the phone and call *71 and your number (so *718001112222 if your GV number was 800-111-2222) and it'll set the call forwarding up correctly. Just have to make sure it's a *FULL* Google Voice number (can be done on the website - voice.google.com)
fdm1 said:
Are you on verizon?
Click to expand...
Click to collapse
Yes, I am on Verizon. I use a full Google Voice account for calls, voicemails, and texts, and have call screening services turned off. I now use it on Galaxy Nexus and a Galaxy Tab 10.1; it's a wonderful setup.
On a side note, I did not have to call the routing number to set up my Voicemail forwarding. I simply selected "ok" both times during the Android setup process, ignoring the warnings about "incompatibility."
You should double-check your settings: https://www.google.com/voice#phones
fdm1 said:
So I just got my GN, and it's pretty freakin awesome! One thing I noticed though is that if I swipe calls to the left to ignore, it sends them to my new voicemail on verizon as opposed to my GV. If I let it ring all the way through though, then it routes to GV. It's not a super big deal because I can just push the power button and ignore calls that way, but still...
Also, the messaging sends through regular texts, and not GV...this last part I had heard before, but in case anyone else didn't know that.
Here's hoping they update the GV app to take care of these things.
Click to expand...
Click to collapse
My send to Google voicemail is working correctly when I dismiss a call, but the text messaging option still tries to use the built in messaging app even though I disabled it.
Anyone know a way to force it to use Google Voice for text messaging?
Thanks for suggestions everyone. Just did the *71 thing and will check to see if it worked when I get to work.
Not sure what you mean by full gv account... I use it for everything, so I'm assuming I am on full.
I also pushed OK and ignored the incompatible warning, but that didn't work last night... Maybe because of 4.0.2? Either way, hopefully im fixed now.
Sent from my Galaxy Nexus using Tapatalk
Edit: Just checked, the *71 plus the GV number did the trick. Thanks again everyone.
I'm looking for a new Text-To-Speech app that announces the name of who's calling and who's texting me. I just uninstalled Voice Alerts because it doesn't announce names without cutting out and worse, it doesn't stop announcing caller's names long after you've declined the call. I also used SMS Alerts and some others, but each one ends up failing.
Does anyone else use an app like this on their GN2?
Hmm... guess no one like to use TTS announcements instead of ringtones like I do. I did find and am trying out "Call Announcer". I had a minor problem at first so I contacted the Developer who replied fairly quickly. It's working so far.
I've used Full Screen Caller ID for quite a while: https://play.google.com/store/apps/details?id=com.androminigsm.fscifree&hl=en
Besides the bigger contact picture, it will announce calls and read text messages.
Turn on driving mode under touchwiz. (You will find it under the quick toggles in the pull down notification screen.)
I am not 100% it works the way you want it to, but it does announce who is calling and who sent you a text message. Play with it.
I was wondering how that was happening on my mom's note.
Whenever I miss a phone call, I get TWO notifications. One of them informing me that I've got a voicemail and telling me to dial 1-800-whatever, T-mobile's standard Voicemail #.
Then a second or two later, I get a second notification from the Visual Voicemail app informing me of the same message.
Is this standard behavior for T-mobile and their Visual Voicemail App? It seems like it shouldn't be, because its annoying.
If not, how do I fix the issue and eliminate the redundant notifications?
Phone is 4.1.1 completely stock.
ergonomicz said:
Whenever I miss a phone call, I get TWO notifications. One of them informing me that I've got a voicemail and telling me to dial 1-800-whatever, T-mobile's standard Voicemail #.
Then a second or two later, I get a second notification from the Visual Voicemail app informing me of the same message.
Is this standard behavior for T-mobile and their Visual Voicemail App? It seems like it shouldn't be, because its annoying.
If not, how do I fix the issue and eliminate the redundant notifications?
Phone is 4.1.1 completely stock.
Click to expand...
Click to collapse
It sounds like the app didn't configure your voicemail correctly when you switched. Try updating to the latest visual voicemail and then go to settings>applications. Find Visual Voicemail and clear data. After that open the app and set it up again. Hopefully it will fix the issue.
Can alternatively use Google Voice. Better in every way.
Aerowinder said:
Can alternatively use Google Voice. Better in every way.
Click to expand...
Click to collapse
I disagree. On by my S2 and S3 when I go to play a message with google voice it starts to play for a second, I hold it up to my ear and it stops. I have to hit play once or twice more to get it to play. The only benefit I've found to google voice is the speech to text engine which doesn't form readable sentences most of the time. The other issue with google voice is if you have your phone off or dead it will go to your original voicemail because your phone is what actually redirects the number to google voice when it is on.
I do not have any of these issues on my S3.
TTS (and reverse TTS) has never been good. All implementations, never found one that was even half-way decent.
The call forwarding settings on saved on the carrier side. Not the phone. This is evident when you attempt to change said settings, and why the settings are saved even after total wipes. It does not make any logical sense that the call would not appear in your GVoice inbox. After a quick test, I've learned that it works as I expected.
Not sure where you went wrong. Working on all fronts here.
I looked through the forums and could not find anything on this that is recent. If I missed something I apologize for the re-post.
What I am experiencing is rather annoying. I start most of my phone calls in one of 3 ways. 1) from the contact/missed/recent screens in the dialer app, 2) from the contact info screen, as access by Textra (my preferred texting app), or 3) voice command.
Regardless of how I start the call, more times than not I am greeted with the call about to start (in other words the dialer opens and the number is present along with the contact info) then the dialer will close. Then I try again by either swiping from the contact list, or sending the voice command again and the call dials.
I am not rooted, on the latest 5.0.1.
Any ideas?
Me too, same problem on 5.0.1. Annoying~
I have the Note 4 Dev and it is rooted with MOROM 6.5 installed, and I sometimes have this happen as well.
I have been experiencing the same issues. I'm also on 5.0.1 not rooted. Running Nova Launcher.
Sent from my BN NookHD+ using Tapatalk
ssb13 said:
I looked through the forums and could not find anything on this that is recent. If I missed something I apologize for the re-post.
What I am experiencing is rather annoying. I start most of my phone calls in one of 3 ways. 1) from the contact/missed/recent screens in the dialer app, 2) from the contact info screen, as access by Textra (my preferred texting app), or 3) voice command.
Regardless of how I start the call, more times than not I am greeted with the call about to start (in other words the dialer opens and the number is present along with the contact info) then the dialer will close. Then I try again by either swiping from the contact list, or sending the voice command again and the call dials.
I am not rooted, on the latest 5.0.1.
Any ideas?
Click to expand...
Click to collapse
I have noticed this issue on MoROM custom ROM and a person did mention it on that thread so it seems like this is a lollipop bug for some or all :/