As of today, I noticed that when I say "OK Google" or touch the microphone, I don't get the audible "beep" that tells me it's ok to start speaking?
Has anyone else noticed this?
I uninstalled the latest version and tried it and the beep work, but when I updated again to the latest version, Sept 14th release, it doesn't beep for me.
[UPDATE] As posted in reply #6, my sons S6 no longer beeps either.
I haven't had any issues with Google Now. Got my phone Monday and installed B27 update as soon I turned it on.
gumbyx84 said:
I haven't had any issues with Google Now. Got my phone Monday and installed B27 update as soon I turned it on.
Click to expand...
Click to collapse
Mine works, just doesn't beep?
tele_jas said:
Mine works, just doesn't beep?
Click to expand...
Click to collapse
Works for me. Odd
Mine no longer beeps either. I don't use Google Now often, but I sure do miss the "beep"! Anyone know of a fix?
My son's S6 no longer beeps either, so it's not just an Axon 7 thing... Also, Google search found several people with this issue and the latest update. I even installed the latest "beta" and there is no beep, but uninstall it and roll back to the previous version, the beep is there.
It's a Google thing.....But it doesn't seem to affect every phone?
I got a google update today 9/23, it still beeps, I am using action launcher and the google pill widget....but still hooks to the google app.
Related
i wonder if someone can help me out....i've been having problem with google voice lately, each time i make a call, the other end cant hear my voice, i can hear them just time. can someone point me out how to fix.
Same.
Same here, buddy. Same here. But it's not even Google Voice, I don't think anyway, since I don't use it. I mean it's installed, but still. However, if the other person calls me back, everything will be fine. Sometimes I have to call them 3 or 4 times in a row in order for them to hear me.
Network congestion on your end or the other. If the person you are calling is on AT&T they have been having problems over the past month.
Sent from my PC36100 using XDA App
Mine works fine.
Did you do the latest update? Also it says to manually open up google voice before using it at all in the update directions.
rutter9 said:
Mine works fine.
Did you do the latest update? Also it says to manually open up google voice before using it at all in the update directions.
Click to expand...
Click to collapse
i have the latest update, and it was working fine last month, until lately, i am having problem. that problem does not apply to incoming call, only outgoing calls....sigh.
will probably revert back to older version.
Hey everyone
I got a nexus 5 and using a Galaxy gear live.
I think there was an update the other day to google services and I think since then the watch has been having issues.
I get notifications and everything fine
But when I try to say text my friend Justin
I go OK google. Text Justin mobile. Say my text. It transcript it fine but then says I didn't catch that. And does that every time. I will say hey what's up. It will show that fine in the screen but then all of a sudden it will say didn't catch that
Anyone else having that issue at all?
At least it's not just me then! Same thing started a couple of days ago for me too. Using the LG G Watch R, it now won't "show me my steps", "set a timer for 50 minutes" or acknowledge what I want to say in a message even though it's got it up on the screen. Must be a software bug as I've reset the watch and reinstalled Android Wear on my phone. Still gets my notifications through so it's just a matter of waiting for a patch I suppose.
Weirdly enough, I can't reply to texts (I use Hangouts) but I can dictate replies to Whatsapp messages so it must be a google thing.
I suspect it's a server-side issue as it suddenly happened to a lot of us (though seemingly not all) around the same time. It's similar to how voice dictation of location-based reminders stopped working for some people for a few days a couple of months ago. I do find it alarming, though, that the primary and intended method of interacting with the watch can simply go offline for days on end without a word for Google.
Sent from my Nexus 7 using Tapatalk
Ya. Seems to be working again fine without issues now. Was odd
c_86 said:
Ya. Seems to be working again fine without issues now. Was odd
Click to expand...
Click to collapse
Unfortunately it still doesn't work for me. Really frustrating
Yesterday's Android Wear app update has solved the "show me my steps" issue but texting is still out of action.
I have been using Kevo on my samsung phones going back a couple of models. I got the S7 Edge and it worked fine until yesterday. Door doesn't respond to the phone. The app said it needed to update, but timed out of updates whether on wifi or 4G. The app itself said it was for lollipop- it just stopped working. I uninstalled and then reinstalled, the update button is now gone, it works, and still shows for lollipop. Anyone have similar experience?
sefar said:
I have been using Kevo on my samsung phones going back a couple of models. I got the S7 Edge and it worked fine until yesterday. Door doesn't respond to the phone. The app said it needed to update, but timed out of updates whether on wifi or 4G. The app itself said it was for lollipop- it just stopped working. I uninstalled and then reinstalled, the update button is now gone, it works, and still shows for lollipop. Anyone have similar experience?
Click to expand...
Click to collapse
I just installed my Kevo on Easter. I didn't have any problems with it at all...until I tried to enable android wear. When I did that, I got an alert that it needed an update. That was an endless process of back and forth, enable and disable it on the app, but finally I got an update button that said keep phone w/in 20 feet while it processed the download. I just sat my phone on the floor and did some other stuff. Came back and I had an all update finished and "tap here to restart kevo app". I did that and tried the lock out with my phone, fab, and keys...all okay. When I tried my watch (moto 360), I got the "no keys" error followed by "unexpectedly stopped" message.
I shot an email off to Kevo/Kwikset about it and yesterday got a reply back. Their support stated they do not support the S7 or S7edge with no eta that they will in the future. I asked why, but haven't received an answer yet. Then I saw on reddit that someone said it was because Kevo only supports Android-L; however, now that more devices are getting updates to M, a lot more people are having trouble. They officially state that Kevo supports the S6...what's going to happen when an S6 updates to M? Wonder if they'll put out an update?
They have been notoriously slow, but my app is working again, despite the OS issue they mentioned. Weird, and it still doesn't work with the GearS2, contrary to all the publicity when the watch was released last year that it was working!
My wife and I both have a 6p. She is running the latest lineageos and I've got Resurection's latest rom. Both of our phones have the same problem. The notification tone will randomly go off continuously for 30+ seconds and when unlocking the phone and checking, there are no new notifications. I've had the problem on lineage, stock, resurrection and weta roms. I've spend days searching xda without any luck. Is anybody else having this issue or know of a cure?
jrkelley85 said:
My wife and I both have a 6p. She is running the latest lineageos and I've got Resurection's latest rom. Both of our phones have the same problem. The notification tone will randomly go off continuously for 30+ seconds and when unlocking the phone and checking, there are no new notifications. I've had the problem on lineage, stock, resurrection and weta roms. I've spend days searching xda without any luck. Is anybody else having this issue or know of a cure?
Click to expand...
Click to collapse
It's odd to be sure, especially since you say you can reproduce on both phones running the stock ROM. I've never heard of it. Emergency alerts maybe? Which carrier?
Try disabling NFC under Settings--> More.
v12xke said:
It's odd to be sure, especially since you say you can reproduce on both phones running the stock ROM. I've never heard of it. Emergency alerts maybe? Which carrier?
Click to expand...
Click to collapse
We use straight talk service with Verizon SIM. I thought along the same lines but they both do it at different times. I was in a meeting yesterday and it started going off and then later in the evening hers went off in the middle of a movie. I don't even know where to begin to start to figure out the cause of it. It's not deal breaker, just annoying.
jrkelley85 said:
We use straight talk service with Verizon SIM. I thought along the same lines but they both do it at different times. I was in a meeting yesterday and it started going off and then later in the evening hers went off in the middle of a movie. I don't even know where to begin to start to figure out the cause of it. It's not deal breaker, just annoying.
Click to expand...
Click to collapse
Turn off emergency alerts, and flash one back to stock? Never heard of a similar issue.
I'm having similar issues with notifications sounds too. I get one notification, check it, turn screen off, and not getting any sound for 30/60 secs, even if one or more notification arrives ( I can see it from the led notification).
Really wierd... I'm running s-aosp but I don't think the ROM is to blame. Maybe aggressive doze from greenify or maybe a Google play services bug, I noticed that removing some permission of play services caused delay in notifications, never noticed it till a week ago and then I started noticing it continuosly...
v12xke said:
Turn off emergency alerts, and flash one back to stock? Never heard of a similar issue.
Click to expand...
Click to collapse
I've been thinking of going back to stock anyways because of the rumor off fingerprint gestures in the new beta update so maybe I'll try it again and see what happens.
jrkelley85 said:
I've been thinking of going back to stock anyways because of the rumor off fingerprint gestures in the new beta update so maybe I'll try it again and see what happens.
Click to expand...
Click to collapse
Not only are the fingerprint gestures working, but Google finally released the full image on their beta page, which makes things really easy.
Anyone else find that every once in a while you'll call someone and won't be able to hear anything and they won't hear you until you call them back? Happens when I call out from time to time. Very frustrating.
Tried wiping dialer data. Also tried reinstalling app updates from the play store, no change.
xxBrun0xx said:
Anyone else find that every once in a while you'll call someone and won't be able to hear anything and they won't hear you until you call them back? Happens when I call out from time to time. Very frustrating.
Tried wiping dialer data. Also tried reinstalling app updates from the play store, no change.
Click to expand...
Click to collapse
If you're on sprint I've been having the same issues.
Sent from my Essential PH-1 using Tapatalk
AxxPyrtlexx20 said:
If you're on sprint I've been having the same issues.
Click to expand...
Click to collapse
I'm actually on ATT, which means it's probably not carrier related. Wonder if anyone knows of any alternate dialers that would work? Could see if it's app related or driver related.
I've done this but found my phone was on mute. Next time it happens check to see if that's the case. I think maybe it is easy to hit with your face?
I had the same issue but it would work with some numbers and not with others. I found a setting under the caller that was turned on for hearing aid support. Once I turned that off, it seems that my issues have gone away.
10 hours into the phone (got mine this AM) and I like the device but still not a fan of the camera, even with the Google camera port. Some things essentially (intentional) seem half baked or not thought completely through.
I just downloaded the MS Launcher and I have to say, I like it a lot. I'm considering keeping that the stock launcher.b
Same issue, my face it's the mute button all the time.
Happened twice in a day, I had to reset everything and still same if I restore all apps from back and/or if I connect my phone to car bluetooth --> safe unlock.