Has anyone else had a problem with Google Now not detecting the hot word since the app got updated recently? I can uninstall the update and it works great, but as soon as I update, it stops working. Almost like it can't use the mic when you haven't actively pressed the mic button on the search bar. I can go into settings and try to re-train voice model, but when I try, it doesn't seem to pick up my voice. Not a huge issue, but annoying as crap.
For what its worth, I'm on straight un-rooted stock 5.0.
Related
Interesting one, and can't figure out why it's happening - so if anyone has any thoughts x)
Flashed L tonight, all went smoothly and generally everything is fine. The only weird thing is that Google Voice search has stopped working. I press the Voice search button, and it just doesn't pick up any sound. I trying saying "ok google", and it doesn't pick that up either. Also, along with that, Text to Speech refuses to work too, tried with different languages and different voice packs.
Any ideas?
I know I had to go into the Google Now settings and activate the "OK Google" from any screen, to get it to work.
I had the same problem when setting another language as the primary language, then switching back to English, but something seemed bugged.
Removing all the other languages and restoring English (US) only, and finally rebooting, resolved the issue. Hope this helps.
themcfly said:
I had the same problem when setting another language as the primary language, then switching back to English, but something seemed bugged.
Removing all the other languages and restoring English (US) only, and finally rebooting, resolved the issue. Hope this helps.
Click to expand...
Click to collapse
Hmm, just gave that a try, no dice Was it just the Voice language or the whole phone that you had to change?
The weird thing is, it's like it's not even connecting to the microphone, just sits there listening and not hearing anything x)
Yes, that was exactly the same behavior i had with mine. I also ended up trying to configure Ok Google from any screen, and the voice training feature didn't hear anything, remaining stuck on the 1st of 3 verifications.
Maybe you can try going to Settings > App > All > Google Search and deleting cache/data to restore it brand new.
themcfly said:
Yes, that was exactly the same behavior i had with mine. I also ended up trying to configure Ok Google from any screen, and the voice training feature didn't hear anything, remaining stuck on the 1st of 3 verifications.
Maybe you can try going to Settings > App > All > Google Search and deleting cache/data to restore it brand new.
Click to expand...
Click to collapse
Tried that, and reflashing it, factory reset etc. Turns out the problem is slightly wider than just that not working though - It's killed the Microphone completely, can't make voice calls, it's like it's just not picking up the mix exists for some reason :S
It takes time to activate, there is a backend update of google going on while you select your language, but eventually comes back on.
Try voice typing if your believe the mic is not doing any good for "ok google"
gamer.11 said:
It takes time to activate, there is a backend update of google going on while you select your language, but eventually comes back on.
Click to expand...
Click to collapse
Wouldn't really explain why my Microphone doesn't work at all, even in phone calls though
Reoryn said:
Wouldn't really explain why my Microphone doesn't work at all, even in phone calls though
Click to expand...
Click to collapse
just to try it out to rule out whether it's the telephony app or in effect a bug which affects 5.0 as a whole(which i highly doubt, because i have mine working like a charm) Hell mine even works on off-screen while charging.
gamer.11 said:
just to try it out to rule out whether it's the telephony app or in effect a bug which affects 5.0 as a whole(which i highly doubt, because i have mine working like a charm) Hell mine even works on off-screen while charging.
Click to expand...
Click to collapse
Ok, voice search nothing, voice typing nothing, Making Phone calls, nothing x) The only thing I haven't managed to try yet is downloading a 3rd party voice recorder app - but unfortunately I'm on GSM at work and for some reason, Lollipop is refusing to connect to the wifi as well. Good times
Might just flash it back to 4.4.4 and wait for the OTA upgrade to see if that does it better
Just as an additional - managed to download a voice recorder app.... Nothing either. So the whole OS isn't picking up the Microphone. Curiouser and curiouser
Oh hell.... I'm going to hang my head in shame now and hand in any tehcy credentials I may have once had.
I have a Pressy.... I forgot it was plugged in... I didn't install the app. Lollipop saw it as a headset and mic.
In conclusion: I'm an idiot. That is all x) Thank you for anyone who tried to help though.
I have the exact same problem but no pressy. Could it mean that there is a fault with the headphone jack?
Reoryn said:
Oh hell.... I'm going to hang my head in shame now and hand in any tehcy credentials I may have once had.
I have a Pressy.... I forgot it was plugged in... I didn't install the app. Lollipop saw it as a headset and mic.
In conclusion: I'm an idiot. That is all x) Thank you for anyone who tried to help though.
Click to expand...
Click to collapse
Lol
My mic is not working, i dont know what to do????? any help, just update to lollipop cuz receive the update message, but now i dont have mic. need help...
I have looked all over the internet and on XDA and haven't found an answer. Considering re-flashing the Rom.
I recently installed Cloudy 1.2 and flashed the D850 modem as well on my AT&T LGG3
Everything is working great, except when I press my bluetooth button on my headset nothing happens on the phone and I get the default sound from the headset saying that it can't do anything.
I can't figure out why this might be the case, all other functions of bluetooth work great. The only thing I have found that might possibly pertain to the issue is the lack of the Google Now launch option when using a bluetooth launch selector. Specifically [Google Search > com.google.android.googlequicksearchbox.VoiceSearchActivity] simply doesn't show up. I have been able to switch this setting and use google search on all of the roms I've used in the past cm12, cloudy 2.2 and the stock 4.4 from LG.
I am at a loss as to what may be the issue and would like to try something other than wiping the phone since that may not even fix the problem.
Edit** Jun 25, 2015
Started have a bunch of issues with the headphone jack being seen as a headset and triggering google search. I switched to Cloudy 2.3 since its different than 2.2. Hoping some of the bluetooth issues they've had in the past have been worked out but the button on my bluetooth headset triggers google search on my phone again. Thankfully.
Thanks for any suggestions/help
I have the same problem
falcon897 said:
I have looked all over the internet and on XDA and haven't found an answer. Considering re-flashing the Rom.
I recently installed Cloudy 1.2 and flashed the D850 modem as well on my AT&T LGG3
Everything is working great, except when I press my bluetooth button on my headset nothing happens on the phone and I get the default sound from the headset saying that it can't do anything.
I can't figure out why this might be the case, all other functions of bluetooth work great. The only thing I have found that might possibly pertain to the issue is the lack of the Google Now launch option when using a bluetooth launch selector. Specifically [Google Search > com.google.android.googlequicksearchbox.VoiceSearchActivity] simply doesn't show up. I have been able to switch this setting and use google search on all of the roms I've used in the past cm12, cloudy 2.2 and the stock 4.4 from LG.
I am at a loss as to what may be the issue and would like to try something other than wiping the phone since that may not even fix the problem.
Edit** Jun 25, 2015
Started have a bunch of issues with the headphone jack being seen as a headset and triggering google search. I switched to Cloudy 2.3 since its different than 2.2. Hoping some of the bluetooth issues they've had in the past have been worked out but the button on my bluetooth headset triggers google search on my phone again. Thankfully.
Thanks for any suggestions/help
Click to expand...
Click to collapse
So, you have been able to fix it? you flash "cloudy 2.3" and now when you long press your bluetooth button something is triggered on the phone? I own a lg g3 I think is a very good phone but I really miss that function
If my phone is on for more than 10 minutes, I lose calling functionality. When I try to call someone, it freezes and the Pixel becomes unresponsive, forcing me to hold down power for 10 seconds for a reboot. After this, it works just fine for another 10 or so minutes.
I have no idea when calling functionality begins to be lost because I can still send and receive texts, but I can't make or receive calls. I don't even get a wave of missed calls or anything when it works after a reboot.
Google Assistant has it's own issues when this happens too. It won't come up with "Hey, Google" at all. When I long press the home button, Google Assistant comes up, but I just get the floating dots. Fortunately, it doesn't freeze when I try this. Restart the phone and I'm good for about 10 minutes or so. I tried installing 3rd party calling apps, but the problem persists.
Hoping this is a Pie issue and waiting for the next security patch, will likely do a sideload flash-all. Any suggestions as to what the problem is from? Could my SIM card be the problem? Any apps I could try to help narrow down the issue? I had no issues with Oreo.
Thanks in advance.
Tried rebooting in safe mode. Slightly similar results: works fine for about 10 minutes but then it's just the mic not working. I can make and receive calls with out the phone freezing, but no mic.
mbstone said:
If my phone is on for more than 10 minutes, I lose calling functionality. When I try to call someone, it freezes and the Pixel becomes unresponsive, forcing me to hold down power for 10 seconds for a reboot. After this, it works just fine for another 10 or so minutes.
Click to expand...
Click to collapse
I have a similar issue with a used Pixel I purchased. I couldn't place or receive calls, with everything else working fine. Did the prerequisite online searches with results finding most everyone experiencing this issue chalking it up to hardware but I'm still thinking software. I tried a different phone app (drupe-enabled as default) with some success, then the problem returned (a few days later, rarely get/make calls). The default google phone app (version 23.0) fails every time. Currently looking into TWRP/Root and hoping to eliminate certain default apps to experiment further. Will be keeping an eye on this post! :cyclops:
--- Three weeks later ---
Could there be an issue within google play services with phone dialer app (any/or stock app)?
After continued issues I parked phone in drawer a bit then pulled out and tinkered with a few weeks later. Tried to isolate problem using logcat and on a hunch I flashed TWRP and a custom ROM but NOT any gapps package. Sticking sim in and using the built in phone app (Resurrection Remix -com.android.dialer) it works without issue. What? I flashed gapps (correct version/etc) and sure enough the problem returned. Went back to rom minus gapps, works fine. So, with straight up stock rom - stock phone dialer fails, custom rom - it works without a gapps package but not with.
Aimless Rambler said:
I have a similar issue with a used Pixel I purchased. I couldn't place or receive calls, everything else working fine. Did the prerequisite online searches with results finding most everyone experiencing this issue chalking it up to hardware but I'm still thinking software. I tried a different phone app (drupe-enabled as default) with some success, then the problem returned (about 5 days later). The default google phone app (version 23.0) fails every time. Currently looking into TWRP/Root and hoping to eliminate certain default apps to experiment further. Will be keeping an eye on this post! :cyclops:
Click to expand...
Click to collapse
Went back to Oreo before I had the problems and... problems persist. I'm sad. I had the privilege of speaking to someone from Google Support who was very knowledgeable. Unfortunately, my best option from the rep was to take it in to one of their authorized repair places.
Are you guys on Verizon? I'm having this problem with my dad's pixel on vzw.
brkshr said:
Are you guys on Verizon? I'm having this problem with my dad's pixel on vzw.
Click to expand...
Click to collapse
AT&T
---------- Post added at 07:47 AM ---------- Previous post was at 07:45 AM ----------
mbstone said:
Went back to Oreo before I had the problems and... problems persist. I'm sad. I had the privilege of speaking to someone from Google Support who was very knowledgeable. Unfortunately, my best option from the rep was to take it in to one of their authorized repair places.
Click to expand...
Click to collapse
--- Three weeks later ---
Could there be an issue within google play services with phone dialer app (any/or stock app)?
See my updated post (# 3) for what I've tried since..
Vzw ended up replacing my dad's phone through extended warranty. I talked to Google for awhile. Multiple factory resets, factory image installs, tried older phone apks. Nothing worked.
brkshr said:
Vzw ended up replacing my dad's phone through extended warranty. I talked to Google for awhile. Multiple factory resets, factory image installs, tried older phone apks. Nothing worked.
Click to expand...
Click to collapse
Older/newer phone dialer apps didn't work for me either ... custom rom and eliminating google play services did (no gapps). I'm still tinkering with the device ... installing frequently used apps using F-droid and Yalp, will test it. Not quite sure why but it works.
I ended up flashing Lineageos for Microg, presents it's own problems in the learning experience but it works.
Nothing ever worked in the end. No, not with Verizon. Bought through Canadian carrier called Fido.
Called Google tech and they weren't overly helpful. I started a chat with a Google Tech and they suggested I take it to UBreakIFix. They did a free diagnostic test and I referenced https://support.google.com/pixelphone/forum/AAAAb4-OgUsIW_gxTpXX3s/?hl=by that thread. Said they'd fix it for free even thought I was out of warranty. Got a new motherboard and my phone works like a charm.
Recently on my Note 10+ (SM-N975U1) running stock Pie and Dec 1 2019 update, I have been experience 2 issues.
Notifications for some apps are delayed
App updates hang on Google Play Store
For the app updates, they stall with "Download Pending" or the download stalls with <100% complete.
Resolution steps that have NOT worked
Clearing cache and data for Google Play Store
Rebooting phone
Rebooting into Safe Mode
Changing from Wifi to Cell Network Data and vice versa
Stop/starting app updates
Current Workaround
Closing/swiping the Google Play Store and opening it again. It will eventually complete downloading after multiple attempts and install/update an app - you will have to repeat this continuously for every app you want to install or update.
Is there anyway to debug this without doing a complete reset?
This is a problem I've had on many phones over the last few years. It took me a while to figure it out but it's bluetooth related. More specifically, I had the "Dynamic Lock" option enabled on my Windows 10 work laptop (which basically just locks my pc when my phone gets far enough away). I disabled this and now all my notifications come immediately and play store updates work as they should. I realize that you may not have that enabled and if that is the case then turn off your bluetooth for a while and see what happens. It worked for me and several others on the samsung community forum.
mtweisenbarger777 said:
This is a problem I've had on many phones over the last few years. It took me a while to figure it out but it's bluetooth related. More specifically, I had the "Dynamic Lock" option enabled on my Windows 10 work laptop (which basically just locks my pc when my phone gets far enough away). I disabled this and now all my notifications come immediately and play store updates work as they should. I realize that you may not have that enabled and if that is the case then turn off your bluetooth for a while and see what happens. It worked for me and several others on the samsung community forum.
Click to expand...
Click to collapse
Thank you! I turned off Bluetooth but nothing happened but after I rebooted with Bluetooth off everything started to work again. Is there a permanent fix for this? I am assuming turning back on Bluetooth will cause this to happen again? The strange thing this never happened to my Note 8.
selector said:
Thank you! I turned off Bluetooth but nothing happened but after I rebooted with Bluetooth off everything started to work again. Is there a permanent fix for this? I am assuming turning back on Bluetooth will cause this to happen again? The strange thing this never happened to my Note 8.
Click to expand...
Click to collapse
I have no idea why this happens. What I do know I have had this issue on LG phones, Pixels, and Motorola's. It isn't a Samsung thing. I think it's an Android Bluetooth issue.
This is an old thread - but in case someone else finds it, I came across someone's suspicions in another thread that their Plantronics headset was causing some kind of problem with their Bluetooth. I began unplugging my Savi headset when not in use and it seems to help... YMMV.
This has been going on since Pie; made me upgrade from my Note 8 to Note 10 and it came right back. Infuriating.
You may also want to try to rub a lucky stone and do some chanting as well, because it's about as effective as hoping for a fix after all this time.
I noticed recently that "Ok Google" voice activation of the Assistant was no longer working. It took me a long time to notice because I only use this feature when driving longer distances, something I haven't been doing much during the pandemic.
With the newer versions if I say "Ok Google" or "Hey Google" there is no response. If I manually launch the Assistant ie long press on Home button it comes up and I can press the microphone and it works. If I try to retrain the voice model it tells me it's having issues connecting, and I cannot get past this message. It's clearly not a connectivity issue because I can use other Google apps and surf the web just fine.
I was curious when this had stopped working so I did some testing:
10.97.8.21 original version that came with the OS update, working
11.19.12.21 working
11.19.17.21 working
11.21.9.21 not working
11.27.6.21 not working
11.30.12.21 not working
11.39.7.23 not working
11.43.8.23 not working
12.2.11.23 not working
12.6.8.23 not working
12.10.7.23 not working
Obviously I didn't test every single version available but it seems that it broke between 11.19.x.x and 11.21.x.x. I was not able to find a good 11.20.x.x to download and test, so I can't rule that version out.
For now I've reverted to 11.19.17.21 but I'm concerned about security running that old of a version.
Any idea what might have changed in between those two versions to make this stop working?
Anyone else have similar experiences?