Database Users

[Q] Google Voice - Can't Press 1 to accept + Greeting is cut off

I just installed Google Voice on my Epic 4G and received my first phone call on it - and was unable to answer. Two problems - first, when I answered, the greeting telling me to press "1" to accept was cut off at the beginning (all I heard was '...all from [spoken voice]. Press 1 to accept".
I can get past that, but then when I pulled up the dial pad to press 1, I was unable to. I pounded on the "1," was sure it was showing up, but it would not answer the call. I tried enabling audible touch tones but that didn't work, and I don't think there's a setting on the epic to change between long/short touch tones.
Does anyone know what's going on with this?

pissinguoff247 said:
I just installed Google Voice on my Epic 4G and received my first phone call on it - and was unable to answer. Two problems - first, when I answered, the greeting telling me to press "1" to accept was cut off at the beginning (all I heard was '...all from [spoken voice]. Press 1 to accept".
I can get past that, but then when I pulled up the dial pad to press 1, I was unable to. I pounded on the "1," was sure it was showing up, but it would not answer the call. I tried enabling audible touch tones but that didn't work, and I don't think there's a setting on the epic to change between long/short touch tones.
Does anyone know what's going on with this?
Click to expand...
Click to collapse
I think the second problem is a bug. It's not related to google voice but the phone itself. The dialpad is not very responsive when you take the phone off your face and the screen is back on. Wait a few seconds, and it'll be back again.
It happened all the time when I called any customer service number and tried to use the dialpad to choose in the menu.

Bigger problem
fookxixi said:
I think the second problem is a bug. It's not related to google voice but the phone itself. The dialpad is not very responsive when you take the phone off your face and the screen is back on. Wait a few seconds, and it'll be back again.
It happened all the time when I called any customer service number and tried to use the dialpad to choose in the menu.
Click to expand...
Click to collapse
I never had the phone to my face when I did my test calls - this was always phone in my hand and calling from my office phone.
I think I just came across a bigger problem - the dialpad doesn't work on incoming calls. I just called my phone from my office on the regular (not G-voice) number and pushed a bunch of buttons, and couldn't hear the tones.

You can disable the initial greeting and go straight to the call when you pick up. It is under Voice Setting in your google voice account. I know this doesn't address your unresponsive screen issue, but it's a temporary work around until your dialpad gets fixed.

bojackson63044 said:
You can disable the initial greeting and go straight to the call when you pick up. It is under Voice Setting in your google voice account. I know this doesn't address your unresponsive screen issue, but it's a temporary work around until your dialpad gets fixed.
Click to expand...
Click to collapse
Is this actually a bug? I posted another thread here and am trying to have people verify whether or not this is a real issue - if it's not a bug then I definitely need to replace the phone, 'cuz it's been factory reset as of last night.

[Q] My Phone Keeps Beeping

I just recently bought my Note 4, and have to say it is the single best phone I have ever owned lol. I am still trying to learn about it. I mean it is Rooted and I do not even know what that means LOL
Anyways the reason I joined is because I need help. This has been happen off and on, my phone keeps beeping every time I shake my phone. I did not know you can shake the phone and even have it do anything (I need to really learn more about my phone haha). When I am out walking the beep drives me bonkers! It will even bleep during the start of a phone call. I recorded the sound and really hope that I can upload it.
Thank you in advance for any help you may be able to provide. I am sure it is just something simple, but I am not seeing it

Hi there,
A simple Google search brings me here:
http://forums.androidcentral.com/samsung-galaxy-s4/282858-2-tone-beep-sound-constantly-playing.html
Did you try turning off NFC to see if this causes the problem?
(This doesn't seem to happen on my handset when turned on btw.)
Else turn off Orientation Lock maybe?
(Seeing the fact you say it occurs more when you move or shake your handset.)
Question: Does the sound also play if the profile is on silent mode?
Kind regards, Stefan.

Thank you for taking the time to respond to my question
I came across that same thread when I was searching for answers before coming here. It did not find it relevant because my NFC is not on.
I was able to kind of see a screen before silly me accidentally hit the back button. I did not see the name of the app, but it was a white background with a picture of an orange mic and switch on the bottom in orange that says sonar. There was probably other things on the page but that is all I saw for the split second I saw the screen. Then it is after it started doing the beeping. When I look at my apps the only ones I have that have anything to do with my mic is S Voice, Voice Recorder and Voice Search, and not one of them are what I saw. The beeping I am hearing same kind of sound I would hear if I tap Voice Search, but that is not what is causing the beeps.

Hi again,
It does sound like the Voice Search beep, but it seems different.
You could try to disable double tap home for Svoice but I doubt if it would work:
Double tap the home button to*open S Voice.
Press the menu button in the top right of the app.
Tap “Settings.”Uncheck “Open via the home key.”
Did you check the screen orientation lock yet?
I assume you have rebooted your handset right?
Kind regards, Stefan.

We are becoming fast friends! LOL
Yes it does sound the voice search, and it does go away after I reboot my phone, I would just really like to know what this is though so I can try to prevent it from happening or turn it off when it does happen.
Again, thank you so much for caring enough to try and help me.

An other thing that ia worth mentioning is under:
Accessibility these is: direct acces.
When enabled it enables certain user set options by 3x pressing the home button.
But I could not find any option that enabled this beeping.
It could very well be a third party app causing it.
Anyways good luck, maybe anyone else has some input.
Kind regards, Stefan.

You might try safe mode to see if an app is causing it. It will temporarily disable all non-system apps. See if that fixes it. If so, it is an app you installed. m.androidcentral (I can't post links yet so change this to a '.') com/galaxy-note-4-safe-mode
Sent from my SM-N910T using XDA Free mobile app

OK Google from screen off requires PIN. How to turn that off?

I have set up "OK Google" to recognize my voice from screen off.
This works great, however, when I use it, it requires me to enter my PIN/fingerprint to show the results.
Is there any way to turn this off? I find it kind of silly that I have to do that every time.
And as far as security reasons, the phone won't respond to anyone else, so it's not like someone would be able to "OK Google" and unlock my phone, unless they sound exactly like me.

mgorman said:
I have set up "OK Google" to recognize my voice from screen off.
This works great, however, when I use it, it requires me to enter my PIN/fingerprint to show the results.
Is there any way to turn this off? I find it kind of silly that I have to do that every time.
And as far as security reasons, the phone won't respond to anyone else, so it's not like someone would be able to "OK Google" and unlock my phone, unless they sound exactly like me.
Click to expand...
Click to collapse
I've been having this issue as well, I've been meaning to start a thread about it. It seems that trusted voice isn't working correctly - this is meant to unlock the device when it responds to your voice. Well that's my understanding anyway.

Ah I see what is missing. You have to enabled "Trusted Voice" in the security settings for smart lock. Once I did this, it now unlocks with OK Google.

mgorman said:
Ah I see what is missing. You have to enabled "Trusted Voice" in the security settings for smart lock. Once I did this, it now unlocks with OK Google.
Click to expand...
Click to collapse
I've already got this enabled yet 90% of the time it still brings up the PIN screen.

I too was confused by this. I was like.. well google now from screen off is totally useless if I have to unlock the phone after making my request. lol
All is good now. Thanks for the tip.

Tung_meister said:
I've already got this enabled yet 90% of the time it still brings up the PIN screen.
Click to expand...
Click to collapse
Unfortunately, trusted voice matching is still hit and miss. It can depend on the environment when you talk to it, or even on you if you have a cold or something else that effects you. The best option is to try retraining the voice recognition in the ok google settings; I had to do that once when I had a particularly poor match up.

cbowens said:
Unfortunately, trusted voice matching is still hit and miss. It can depend on the environment when you talk to it, or even on you if you have a cold or something else that effects you. The best option is to try retraining the voice recognition in the ok google settings; I had to do that once when I had a particularly poor match up.
Click to expand...
Click to collapse
Surely though if the phone responds to my "OK Google" and wakes it up it has recognised it as me though so should work?

Tung_meister said:
Surely though if the phone responds to my "OK Google" and wakes it up it has recognised it as me though so should work?
Click to expand...
Click to collapse
While I don't have documentation to support my understanding, the best I've been able to put together is that "trusted voice" and "hotword detection" operate on different levels of accuracy. When you train it to recognize "Ok Google" in order to launch voice commands, it's attempting to better recognize you based on your enunciation and potential accent, where as the trusted voice is actually trying to match further, perhaps with things such as tone and pitch, in order to authenticate that its really you. For example, after training my phone, I can use "Ok google" to launch into voice commands when the phone is unlocked, or to bypass the unlock requirement when the phone is locked and execute a voice command. My wife, if she tries to immitate the way I say the phrase, can get my phone to launch into voice commands when the phone is unlocked, but if she tries while the phone is locked, it will require a PIN entry. It seems to be the same situation as what you're describing.

To me, this is exactly how it should work.

Tung_meister said:
I've already got this enabled yet 90% of the time it still brings up the PIN screen.
Click to expand...
Click to collapse
You should retrain your voice model then. Be sure to speak naturally and at a distance that you'd be speaking at the phone normally. I always practice a few times before hand to make sure I don't sound robotic like I am talking to an automated operator. "Speak to a representative..... Speak to a representative.... SPEAK TO A REPRESENTATIVE!"

You can use this app to pass that policy: https://play.google.com/store/apps/details?id=com.luutinhit.doubletapscreenoff

"Okay Google" Not Working Since Update?

Today I updated Google and noticed that saying "okay Google" from the home button screen (whatever it's called, the screen shown when you hold the home button for a bit) doesn't work anymore. It works from any other screen from the home screen to the lock screen.
I searched around but found no solution. Anyone have any ideas, or is experiencing the same thing? Could this be just an issue with the update and require another update to fix?
Edit: And now it's mysteriously working again, with absolutely nothing changed or done on my end.

Did you ever get this fixed? Ok google has been very buggy for me. I have a Google Home and wondered if it was messing it up.

So I noticed after the update I couldn't unlock the Axon 7 when it had its screen off and it was plugged in (the feature obviously doesn't work at all if the device isn't plugged in). The way I solved this was to go to the voice activity on Google and I paused (or deactivated) it. By doing this, you essentially reset all Google Voice settings (not the history). Then, just long press the home button which brings up the assistance which will ask you to give it permission to listen to you. It will then ask you to say "Ok Google" three times (as if it's the first time you're using it). When the trusted voice option is toggled (which is automatically will do it for you), the issue is fixed and the phone can be unlocked with you voice with its display off and while plugged in.

Alternative ways to answer incoming calls

I am having trouble answering income calls. The only option seems to be to swipe the circle. About half the time it fails resulting in me not being able to answer the phone and the caller going to voicemail.
The flip down to not answer and bring to ear to answer also seems to work about 50/50. Is there a setting I am missing to swipe and answer or hit a button and answer? The drag the circle answer just is not cutting it.
LG v20 - AT&T flavor

Nothing? Makes the phone questionable....

I agree that swiping to 'outside' the circle doesn't always work, but not to the tune of 50%.
On rare occasions, I sometimes see the circles replaced with a row of square (rectangle) boxes with the same functionality as the circles, yet they say "Touch" instead of "Swipe" for results. I don't know how to make that a permanent action though.
BTW ... the concept behind swiping to answer is so you can't inadvertently answer/cancel a call just by grabbing the phone in the wrong spot, so depending on where/how you use the phone ... be careful what you ask for as it may come with unintended results. If you're really having an issue with the Swiping aspect of answering a call, see if it's the same on the display in the store ... if not, you have a faulty phone and they'll give you another under warranty.
My two swipes worth.

In phone settings you can change it to touch and hold to answer. Works much better.

Androiddiego is right.
My phone is through Verizon and here's how it maps out: Settings ---> Accessability ---> Dexterity & Interaction ---> Touch & Hold for calls ---> slide button to "ON".
This is better than the swipe to answer!

That is really cool! On my T-mobile the sequence is:
Settings --> General --> Accessibility --> Motor and cognition --> Touch and hold for calls

fclifton said:
That is really cool! On my T-mobile the sequence is:
Settings --> General --> Accessibility --> Motor and cognition --> Touch and hold for calls
Click to expand...
Click to collapse
Yes.
This is great! You have no idea how frustrating this was. This is the same for AT&T as T-Mobile.