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...
Related
I have a Galaxy S5 Active and have recently started having a problem. Occasionally when I dial a number, no sound will be output even though the phone is making the call, and the timer at the top corner counts as if the call is working. I'd say it does this about 1 out of 5 calls, I have to hang up and call back and it will work fine. I am not positive, but I think this may have started with the recent 4.4.4 update. I really dont want to restore my phone if not necessary.. anybody heard of this issue?
cohokiller673 said:
I have a Galaxy S5 Active and have recently started having a problem. Occasionally when I dial a number, no sound will be output even though the phone is making the call, and the timer at the top corner counts as if the call is working. I'd say it does this about 1 out of 5 calls, I have to hang up and call back and it will work fine. I am not positive, but I think this may have started with the recent 4.4.4 update. I really dont want to restore my phone if not necessary.. anybody heard of this issue?
Click to expand...
Click to collapse
Maybe it's the front ear speaker issue or network connectivity problem.
Next time you get this problem, see if the loudspeaker option helps to find if the front ear speaker is damaged
GokulNC said:
Maybe it's the front ear speaker issue or network connectivity problem.
Next time you get this problem, see if the loudspeaker option helps to find if the front ear speaker is damaged
Click to expand...
Click to collapse
I have tried this and there is still no sound even in loud speaker mode. I have also verified that other caller cannot hear me also
I think this issue is with Google play services... Try to search on xda or Google about it. I had read somewhere about it
Tried clearing cache of google play services like suggested in another thread.. but it didnt help
I should also mention that the problem only occurs when I am the one making the call, never when I receive a call
bump
bump
cohokiller673 said:
Tried clearing cache of google play services like suggested in another thread.. but it didnt help
Click to expand...
Click to collapse
If you have root then try to disable google play services and other Google apps. And check if problem occurs in 2-3 days.
Hope someone may be able to help. Recently on my S6E, whenever I make or answer a phone call the speaker phone is always turned on. Any idea how to remedy this? Its quite annoying.
Thanks
BassTeQ said:
Hope someone may be able to help. Recently on my S6E, whenever I make or answer a phone call the speaker phone is always turned on. Any idea how to remedy this? Its quite annoying.
Thanks
Click to expand...
Click to collapse
Dear @BassTeQ
See if this helps go to [S voice settings] and uncheck auto-start speaker
Regards
bluff master said:
Dear @BassTeQ
See if this helps go to [S voice settings] and uncheck auto-start speaker
Regards
Click to expand...
Click to collapse
Hi @bluff master,
Thanks for your reply, I have tried that, the option was already disabled.
BassTeQ said:
Hi @bluff master,
Thanks for your reply, I have tried that, the option was already disabled.
Click to expand...
Click to collapse
Anyone ??
BassTeQ said:
Anyone ??
Click to expand...
Click to collapse
I had the same horrible issue, i tried some fixes online but it didn't work, i had to restore.
hosmsdos said:
I had the same horrible issue, i tried some fixes online but it didn't work, i had to restore.
Click to expand...
Click to collapse
Ohh dear, not the answer I wanted to hear. Glad to see I'm not the only one with the issue. So you did a factory reset to resolve it?
Same here. After so many bugs I am about to sell that damn thing. It really is a shame! Common, but those are core basic things that should never NEVER ever have issues like this!
I have the same issue since a day... I tested many workaround ut nothing works and I will not do a factory reset for that!
Hope we will find a solution.
I read a lot of posts speaking about a USB connector issue.
The connector needs to be cleaned or changed.
Any one have more info ?
For those who are interested, I really think it is a software bug because when I connect my phone into my car in bluetooth, the speakerphone shut off.
So it's so annoying to manually cut the speakerphone that I decided to reset my phone today.
I'm currently doing a backup with Helium (because I'm not yet rooted) and then I will do a factory reset.
I will keep you informed.
Problem still persists. Please keep us informed.
Finally...
After resetting my phone the problem is solved !!!
I reinstalled all my applications and it is still ok.
Now the question is for how long...
You know what you have to do.
Enjoy !
I for sure won't do that! I'll better be selling this bug loaded piece. Memory leakage issue is driving me nuts. Can't handle 3 apps without having to reload them every time. Veeeery disappointed. And I mean common.. the basic calling feature is not able to work properly.. WTF
Seems like not many are facing this issue? It came out of nowhere on mine and I really dont want to reset my phone for this. I'd like to keep this thread active.
Just reset your phone and that's it!
Sent from my SM-G920F using XDA Free mobile app
Same problem here and same case. When on Bluetooth in my car, the speaker will not auto enable, but whe I turn off BT, the problem persists. I tried the Svoice, The Partition Cache cleaning, the reset, etc. Up to now, no positive results.
I admitted defeat and reset my phone, problem gone
I've solved my speaker phone problem
Hi,
I use note 4 and had similar problem. After long testing, I've found out mine was related to Gear VR. If I turn on "do not disturb" inside the Gear VR setup Menu and unplug the phone. My phone will always go into speakerphone. Very annoying. If I go back into the Gear VR and enable the "do not disturb" and then disable it again (so "do not disturb" is off). My speaker phone problem goes away.
Do you use Gear VR on your phone? If you do, then your speaker phone issue is probably related to the problem I had.
I hope this post will help some of you.
i got here by doing google.
my phone is doing that too. everytime i answer the phone, the speaker is on, i have to turn it off everytime !
cant find any setting to disable it, i think i going to reset my phone too.
@netnerd, Never found a fix, quite easy to do a backup and restore using Helium app after resetting the phone.
Anyone having issues with voice (system, US English)? In that it only works once or twice, then constantly fails with the error "voice input fail".
I can change language (to German for instance) it will work a few times, then stop... back to US English (works a few times...then, yep, stops....).....
Anyone else see this?
Thanks!
Edit/Update - - Try UK ?? English!
..
I have the same issue. Don't know what's wrong.
Seems to work now....
mcaspe1 said:
I have the same issue. Don't know what's wrong.
Click to expand...
Click to collapse
Yours working yet? I factory reset the watch after backing it up and did the whole set-up dance....no difference. Then, later in the day, it started working....haven't thoroughly tested it....but it seems be better....
..
I have an S2, but the underlying implementation is the same.
S-Voice uses a remote server for decoding and interpreting voice input. Occasionally Samsung's servers are unresponsive or failing in some other way. I've experienced this a few times over the last year I've had my S2.
So this may be what was going on, particularly since it started working again later. I didn't use S-voice yesterday, so I can't comment on any outages.
Finally, I will add that since the rollout of the recent update adding a bunch of S3 features to the S2 (reminders, etc.) and updating the entire Tizen OS, S-voice is working much better than it used to. Still doesn't hold a candle to Google's "okay google", but has crossed the threshold to being a useful, value-add feature now rather than a cruel tease. In my opinion, of course.
I had this problem with my S3. You might have hit a setting that you did not realize you hit. When you were able to enter speech and hit send, you had a choice to choose send as text or send as voice. Just below these two choices there is a small circle, if you accidentally touch that, it turns off the speech input and only uses the text. The only way I have found to get out of this mode is to open the main settings, scroll down to messages, select messages, you should see "send as audio". Click it so it is "on".
This should take you back to where it will let you dictate messages. Just be careful when selecting the send as text or audio option as that little circle will be below them and it is easy to touch accidentally.
I hope this helps
I have the same problem and it has not been corrected by resetting or the message sound option.
Same issue here
Well it seems to be at it again.
Interesting part is that using U.S. English, it does not work. If I switch it to U. K. English it does work. (I'm in the US..)
... C'mon Samsung, how about getting your current software working correctly before introducing any new buggy stuff.
Skeeter123,, I am having the same exact problem since I installed the new software update , very frustrating hopefully they will fix this issue soon ?
Yup.
Fix the old buggy software before you give us a new buggy stuff.
Ridiculous Update
I have had my watch for one week and it worked great and then the voice input just stopped. I called Samsung and they offered NO help other than for me to mail it back to them, REALLY! So, back to Best buy for an exchange. Well, same issue will another brand new $450 watch. Is the Gear S3 going to another Note 7 debacle? It is a Samsung product. Get your crap together Samsung! If anyone finds a fix, Pease post.
I'm having this problem
Indeed setting the language to English(Great Britain) actually works! Hats off the person who posted this earlier in the thread
tamerelnaggar said:
Indeed setting the language to English(Great Britain) actually works! Hats off the person who posted this earlier in the thread
Click to expand...
Click to collapse
You're welcome!
But now you have to speak that funny English that they speak over there.:silly:
While I never tried it till this morning, it did work. US.
Still not working for me. And UK English is not working very well either.
Are you in the US?
For all of my tests I am attempting to dictate a message.
I just switched mine over to the English (UK) and it appears to be working right now. I am in the good ole US of A, and have a pretty thick southern accent and it works, but we should not have to change it this way, but at least it works again.
Yup. I hear ya! Too bad Sammy doesn't. I'm going to check out some of the Android Wear 2.0 watches soon.....If I like one, then it's bye-bye Sammy. For good....sigh...
That's too bad that they will lose customers over their inability to get it right the first time. Crazy thing with voice input, I have to have it set to UK English to respond to text messages, or to send a text, but it has to be in US English to speak a reminder in?. Do you think Samsung even monitors this forum?
Chief19 said:
That's too bad that they will lose customers over their inability to get it right the first time. Crazy thing with voice input, I have to have it set to UK English to respond to text messages, or to send a text, but it has to be in US English to speak a reminder in
Click to expand...
Click to collapse
Guys, this issue has been pestering for a month now and I seem to have not found a fix for this yet. I first started to notice the problem with my phone when I was unable to attend the calls, the screen will usually get stuck or i will not be able to swipe up the green button during the call. Even if sometimes I manage to i will be able to hear the other person speak but I wont be able to speak to them. So sometimes once I restart the phone it will seem to work fine for an indefinite period of time and again it starts.
Then things started getting very bad, sometimes during normal device usage, the screen just turns to a monochrome black and white screen ( just as you see when there was no signal on older television sets). And when I switch to the bootloader screen, when I power the device on, I get a very thin green line for an instant on the screen and then the booting sequence starts.
I have made a lot of factory resets and stock image flashing, and by far I noticed one considerably situation, the times when the sound functions fine, the booting sequence where the 4 google dots animation appears and when there is no sound, the booting sequence gets stuck on Google and made by Google screen.
Other observations are during abnormal device behavior, no function related to sound will properly. To elaborate it, Google assistant wont work, videos cannot be played and even the system sounds wont be heard. I am open to suggestions here. Please let me know what can be done to test the phone out. FYI I know there is a problem with the Pixel microphone, but I am not convinced that its the exact problem. Please correct me if I am wrong. Thank you.
Sounds like a hardware defect. RMA if possible.
Sent from my Pixel using XDA Labs
It is a hardware issue indeed, I am facing the same issue, I contacted google , they told that replacement is possible tho I'm out of Canada at the moment so I'm just dealing with it through my Bluetooth earphones, everybody works fine with Bluetooth.
That's the only way I suppose!...did you get the phone directly from the Google store?...are they accepting phones bought from a retailer?...since I am in Singapore now...Google support is next to nothing here...try contacting them but it's of no use...only when I get to India I will be able to go forward with the replacement!.....but the thing is .... yesterday...I updated the phone to Oreo and the audio stopped working completely....and after repeated switching between safe and normal mode....the speakers are working now...but the microphone is still busted.
This happened to me, I was given a replacement phone from EE UK
Current update guys...as per the pixel support centre person's suggestion ...I rebooted the device to safe mode to check if the phone is operating normally ...which it did not....but surprisingly ...after restarting to normal mode ...it started working normally again...my query is how is this zeroed down to an hardware issue if in case it's perfectly working for a while and at some point goes bonkers...can you guys please enlighten me on this...coz I don't have much knowledge on the hardware field.
MK1207 said:
Current update guys...as per the pixel support centre person's suggestion ...I rebooted the device to safe mode to check if the phone is operating normally ...which it did not....but surprisingly ...after restarting to normal mode ...it started working normally again...my query is how is this zeroed down to an hardware issue if in case it's perfectly working for a while and at some point goes bonkers...can you guys please enlighten me on this...coz I don't have much knowledge on the hardware field.
Click to expand...
Click to collapse
hello, i am facing the same things as you do since updating to oreo, my question is how do i test everything in safe mode, to see if everything is alright as you did
ndiri said:
hello, i am facing the same things as you do since updating to oreo, my question is how do i test everything in safe mode, to see if everything is alright as you did
Click to expand...
Click to collapse
Tough luck mate! Sorry to hear that....you can check it out by pressing down the power button until you get the power off and restart menu. Keeping pressing down on the power off menu...it will reboot to safe mode without your prompt. In safe mode for me it was the same....maybe you will have a better luck...try it out!
MK1207 said:
Tough luck mate! Sorry to hear that....you can check it out by pressing down the power button until you get the power off and restart menu. Keeping pressing down on the power off menu...it will reboot to safe mode without your prompt. In safe mode for me it was the same....maybe you will have a better luck...try it out!
Click to expand...
Click to collapse
well, its been almost an hour the phone wont turn sound back on.
Keep switching it to and out of safe mode...at some point ideally at least the speakers must start lest the microphone. Tried contacting Google about it and no response at all...mine started acting weird only for the past month...I suppose from the Aug months patch update....tried reverting it back to previous stock versions...but I suppose the damage is permanently done
When I contacted google, they told me to send it back to Canada and let someone there give it to google.. which won't happen in my case , my phone also started acting like this after Oreo beta . Now I will restart the phone whenever it happens to get it back working :/
The only reason I am still sticking to this phone is coz of it's camera. Planning to get back to India around December to get this fixed. Support for pixel in Singapore now is next to nothing since it wasn't launched here. I had no problem at all with the Nexus line up but this is kind of a disappointment.
Alaadragonfire said:
It is a hardware issue indeed, I am facing the same issue, I contacted google , they told that replacement is possible tho I'm out of Canada at the moment so I'm just dealing with it through my Bluetooth earphones, everybody works fine with Bluetooth.
Click to expand...
Click to collapse
You've mentioned it as through Bluetooth it works fine....care to elaborate on this?...are you able to input voice commands to Google assistant and speak over calls using it ?...since I am planning to buy one in case its a perfect workaround
MK1207 said:
You've mentioned it as through Bluetooth it works fine....care to elaborate on this?...are you able to input voice commands to Google assistant and speak over calls using it ?...since I am planning to buy one in case its a perfect workaround
Click to expand...
Click to collapse
Yea, Bluetooth works fine for calls, as for google assistant voice command you can enable that from google app settings. Of course other media will be working with Bluetooth as music, YouTube, etc..
Alaadragonfire said:
Yea, Bluetooth works fine for calls, as for google assistant voice command you can enable that from google app settings. Of course other media will be working with Bluetooth as music, YouTube, etc..
Click to expand...
Click to collapse
Excellent!...thanks for the input....let me check and get myself one and I will have to manage with it till December....and are you able to connect to a laptop thru Bluetooth...coz I am unable to do so...it just says paired...but the bt symbol in the phone doesn't change to connected..did you try that out ?
MK1207 said:
Excellent!...thanks for the input....let me check and get myself one and I will have to manage with it till December....and are you able to connect to a laptop thru Bluetooth...coz I am unable to do so...it just says paired...but the bt symbol in the phone doesn't change to connected..did you try that out ?
Click to expand...
Click to collapse
Hmmm I don't remember connecting to a laptop via Bluetooth.. you mean for file transfer ? Anyway Bluetooth has nothing to do with the sound issue we are facing, it might be your laptop Bluetooth driver needs to be updated
Alaadragonfire said:
Hmmm I don't remember connecting to a laptop via Bluetooth.. you mean for file transfer ? Anyway Bluetooth has nothing to do with the sound issue we are facing, it might be your laptop Bluetooth driver needs to be updated
Click to expand...
Click to collapse
Just bought a Bluetooth headset....works fine for the most part...but sometimes during calls...the phone just hangs and it automatically restarts....sigh! pixel just can't be trusted to be my daily driver?
MK1207 said:
Just bought a Bluetooth headset....works fine for the most part...but sometimes during calls...the phone just hangs and it automatically restarts....sigh! pixel just can't be trusted to be my daily driver?
Click to expand...
Click to collapse
Sorry to hear so, I actually installed ElementalX kernel and it is less to happen. Try to flash the kernel.
Alaadragonfire said:
Sorry to hear so, I actually installed ElementalX kernel and it is less to happen. Try to flash the kernel.
Click to expand...
Click to collapse
Planning to do just that....I may have better luck with a custom kernel...will post an update once I have flashed it.
I had been on the 8.0 beta for a while. Then got 8.0.
Though just 2 days ago, my mic was starting to have issues. Then yesterday, only my speaker phone would work.
Now I can't get any audio/mic except though Bluetooth (I've got a portable speaker with a mic, and Bluetooth on my car.
Contacted Google support. Will be getting a replacement on their warranty.
They didn't tell me this, but I did some searching, and apparently many of the pixels (mostly from the first 3 months of production) had an issue with the soldering of the audio codec. though usage, little bumps here and there, that soldering can get loose. Which explains why my audio and mic were spotty, and within an hour yesterday morning, all aspects of it stopped working.
So, it's a hardware issue.
So.. I have this problem where (wait for it...) "Hey Google" doesn't respond, BUT (before you stop reading) it only stops responding after I've been on a voice call. Weird, eh?
Here are some fun facts:
1. To get it to respond again, all I have to do is manually open and close Google Assistant by tapping on the screen, then "Hey Google" will generally behave itself and respond until I get another voice call. Sounds easy (I even have a Tasker routine to automate the process), but it's still a chore and it's always a bit hit and miss.
2. I've tried every generic solution I can find on the internet, including retraining the voice model, deleting the cache and data, factory reset etc etc...
3. This issue is 100% specific to the OnePlus 8T running Android 13 (F.13, F.15 & F.62). I used MSM tool to go back to Android 11 and "Hey Google" worked like a charm. I took the OTA updates to Android 12, still working fine. As soon as I took the OTA update to Android 13 (guess what?) yep, the problem came back! No other apps were installed, only the apps built in to the stock ROM.
4. I've tried a number of custom ROMs. All Android 13 ROMs I've tried have this same problem. (Android 12 based ROMs not affected.) I've also tried EU, Global and Indian Firmware.
I sent feedback to OnePlus already, so hopefully we'll get a fix. In the meantime, please, if anyone has a workaround please let me know.
If you don't have a solution but want to complain about the problem here, I'll give you a listening ear.
706mix said:
So.. I have this problem where (wait for it...) "Hey Google" doesn't respond, BUT (before you stop reading) it only stops responding after I've been on a voice call. Weird, eh?
Here are some fun facts:
1. To get it to respond again, all I have to do is manually open and close Google Assistant by tapping on the screen, then "Hey Google" will generally behave itself and respond until I get another voice call. Sounds easy (I even have a Tasker routine to automate the process), but it's still a chore and it's always a bit hit and miss.
If you don't have a solution but want to complain about the problem here, I'll give you a listening ear.
Click to expand...
Click to collapse
Maybe the process of Google Assistant is killed in background by stock memory cleaner or some app?
Try whitelisting it (disable memory optimization and so on).
Rootk1t said:
Maybe the process of Google Assistant is killed in background by stock memory cleaner or some app?
Try whitelisting it (disable memory optimization and so on).
Click to expand...
Click to collapse
Thanks for the suggestion. The Google app is already set to 'Unrestricted' - are there any other processes/apps that should also be set to 'Unrestricted'?
I'm wondering if the Qualcomm Voice Assist Aqstic Audio Codec is not being implemented properly in Android 13.
So, I finally received a reply from OnePlus Support. They have asked me to send a screen recording of me saying "Hey Google" and the phone not responding. Sounds fair. I'll have to go back to stock OOS13 so they can see that the issue is not just with custom ROMs.
Oh well, guess I'll get round to that when I have a spare day...
(At least we can do a nandroid backup with TWRP these days. )
Please, if anyone is running an Android 13 ROM (stock or custom) on their 8T, please can you check if "Hey Google" is working properly on your device after making or receiving a call?
Please post on this thread whether it worked or not, and what ROM you are using. Thank you.
Here's a little update in case anyone's interested...
I sent OnePlus Support a screen recording of the malfunction. Today I received this reply:
I contact you due to the malfuntion of Google Assistant.
There is a need to solve this issue in the next update of Android. The version Android 13.1 will be pushed in June and please inform us if the issue still persists.
Best regards,
Klaudia
OnePlus customer service
Click to expand...
Click to collapse