OK so I have tried everything I can think of and just about exhausted my google-fu trying to figure this one out and I haven't solved it yet. Time to ask the experts! The mic in my gPad isn't working. I use it mostly for voice search and "OK Google" stuff, so I'm not exactly sure when it started as I don't use this feature every day. I just noticed about a week ago that it stopped responding to OK Google, so I checked the google settings first to make sure that they didn't get turned off, and they hadn't. Next I tried a restart and that didn't do anything. I then tried a voice recording app and that didnt work either. So at this point I figured it was a hardware issue and I took a needle and cleaned out the port, there was some fuzz but nothing major- tried everything again and none worked. Last thing I tried was to use hangouts dialer to make a call, and the really puzzling part is that this worked, the other person could hear me loud and clear. So I know its not a hardware issue now. Basically I have no idea what to do from here, not having the mic isn't a huge deal but since the hardware isn't broken I'd like to be able to make it work again. Thanks for any suggestions or help!
Related
Hi all,
I have a problem with my HTC TP2. All of a sudden, the microphone stopped working... There are a couple of strange things though!
- First of all, it came out of nothing. I didn't do anything special when the problem came...
- Headset works, so I first thought it was a hardware problem, but after some hardware resets, it started working again! Unfortunatly, it didn't last for long. 5 minutes later it was stuck again :s
So it is probably a SW bug...
- If I talk really loud, you can hear something, so probably the amp doesn't work correctly... But why does it work with the headset then...
I've seen others with the same problem, but haven't found a real solution, but to send it to HTC for repair... I would rather avoid this!!
Can anyone help me please?
I have the same problem. At first it started just happening every once and a while I would get or make a call and the person on the other end couldn't hear me, now it's probably 90% of the time they can't hear me. I've even tried booting into android and it still doesn't work which leads me to believe my issue is hardware unless someone else has a better idea
If it is not working properly after a hard reset without installing any applications, then it most likely hardware related. Send it in for repairs.
one of my touch pro 2s had this problem, i just took it sprint and they gave me another one.
During a phone call, my E4GT does not properly allow entry of my access code. I normally dial into a conference call in the morning and enter my access code (299542#) to participate. I connect to the conference call main line, but it doesn't recognize my access code properly. Almost never recognizes the "2"....other buttons too. I have tried to go back to GB, different versions of ICS, different mods...none of those have remedied anything. I have searched for answers on the forum but I feel I'm not asking the question clear enough, and others have posted similar problems but there have been no fixes posted. Very interested in a cure. I appreciate the work you guys do!
If it worked before and all of a sudden quit working maybe the issue is on their end. The only thing I can think of is to turn on keytones.
Worked on other Driod
someguyatx said:
If it worked before and all of a sudden quit working maybe the issue is on their end. The only thing I can think of is to turn on keytones.
Click to expand...
Click to collapse
It never worked on my E4GT, but it did work fine on my Xperia Play Gingerbread and blackberry and home phone lines for the last 2 years. I've messed with turning on and off keytones. Could the tones be messed up? Would there be a way to take the tones from another phone and install them?
I doubt it, probably just a tech issue on their end. I never had an issue entering digits in any automated phone system. The keytones thing was just a wild guess. Maybe skype or google voice would work.
Hello I have noticed that ok Google is not recognizable from any of my devices either my smartwatch 3 or my note 3 I have already tried to set up ok google but it can recognize my voice I have tried to teach to my phone the sound of my voice but nothing I can't even pass the first object of learning any idea how to fix this problem? Thanks
Sent from my SM-N9005 using XDA Free mobile app
o-ellinas said:
Hello I have noticed that ok Google is not recognizable from any of my devices either my smartwatch 3 or my note 3 I have already tried to set up ok google but it can recognize my voice I have tried to teach to my phone the sound of my voice but nothing I can't even pass the first object of learning any idea how to fix this problem? Thanks
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
Are you sure it's your devices and not you? I find "Okay Google" to be awkward to pronounce, especially several times in a row, due to the "k" and double "g" combo. Wish we could change the hotword. I just touch the watch...find this to be easier and more reliable. Once I do that, I find the boice recognition to be surprisingly accurate, even with names, foreign-sounding places, etc. Does your watch recognize voice if you activate it by touch? If not, you may have a microphone problem. Also, if you have an accent or something, or a stutter, I'd try having someone else say it to see if it's the device or it's you. And also, make sure the watch is lit up first and out of ambient mode. I don't think it works when the watch is in low power mode. As for not working on the phone, I had that issue on the Note3 as well when using Nova Launcher, worked fine in TouchWiz. But I'm pretty sure the watch keyword detection is not dependant on the phone, since I can activate mine even when it's disconnected from my phone.
I'm having issues with my OK Google too. It's like my watch microphone isn't working. I can't do any voice dictation into the watch. It just says "Sorry didn't catch that" when I talk to it. It worked at one point and seems to work sporadically. Now it doesn't work at all.
Not sure for how long but I think it's something like 1 week that voice commands don't work any more for me.
They are opened as web searches instead.
eg. I used to say "OK Google, set a timer for 5 minutes" and the timer would start. Now it opens web link suggestion...
Same with most other voice commands that used to be really useful.
Anyone having same problem?
Hi!
I bought one sony sw3 3 days ago, and have the same problem...I say the voice comands and it always do the search... anyone solved this? In my note 2 the comands are working fine, like call someone, send a text...
In the watch it always makes the search sugestions.
Thanks
Have AT&T Note 4 since launch. Stock, not rooted or anything like that. Not sure when this problem started because I don't regularly make calls, but I think within the last week or two, possibly after I got the update to COC6 (the update seemed to complete normally, though).
Every time I place or receive a phone call and attempt to use the phone normally (hold it to your head), the person on the other end cannot hear me at all. If I switch to speakerphone, they can hear me and it behaves normally, and if I connect to a Bluetooth device like my car, it also works fine, but if I try to use the phone normally, they cannot hear me. I can always hear them perfectly.
For what it's worth, Google won't pick up my "Ok Google" from the home screen anymore either. Also, I had previously had the option to wake the phone with "Ok Google" disabled, but when I try to enable it now, it hangs on listening to me say "OK Google" 3 times... as if it never hears me say it.
The microphone appears to be working completely normal for everything else I've tried, it's just acting like it's on mute when I'm in a call and not on speakerphone or Bluetooth, and the OK Google stuff isn't working either.
Any ideas? I'm trying not to factory reset... I've searched a lot and not found anything where anyone has solved the issue.
FWIW I had the same issue randomly with my rooted Note 2, and I believe I either fixed permissions or reinstalled the ROM to get it working (can't remember). I wish I could just reinstall the ROM or latest update (COC6) again so I don't have to factory reset. Is this an option at all?
Of course right after I post I solve it myself, but I'll share the fix for my case in the event that it helps anyone. The left hand bottom mic hole next to the USB port was plugged with some gunk (I could clearly see it plugged up completely). I used a safety pin to carefully clear it out and that fixed it. Works normally now. I had originally ruled out this kind of thing being a problem because everything was fine with speakerphone so I thought the mic was ok, but I guess maybe it only uses one mic or something? I suppose I was also swayed by the fact that my previous Note did have a software problem causing the same thing, so I figured this was probably software too. But nope, good to go after checking the mic hole!
pj_rage said:
Of course right after I post I solve it myself, but I'll share the fix for my case in the event that it helps anyone. The left hand bottom mic hole next to the USB port was plugged with some gunk (I could clearly see it plugged up completely). I used a safety pin to carefully clear it out and that fixed it. Works normally now. I had originally ruled out this kind of thing being a problem because everything was fine with speakerphone so I thought the mic was ok, but I guess maybe it only uses one mic or something? I suppose I was also swayed by the fact that my previous Note did have a software problem causing the same thing, so I figured this was probably software too. But nope, good to go after checking the mic hole!
Click to expand...
Click to collapse
Not gonna lie, I checked my mic hole as soon as I read this. XD
I tend to always put my pinky finger over that mic subconsciously. I don't mean to, but it's just how my hands want to hold the phone during a call. I constantly get people saying that they can't hear me though. Then I always notice that my stupid pinky is on the darn mic. Grrrrrr.
Sent from my SAMSUNG-SM-N910A using Tapatalk
This has been annoying since I got the phone 7 months ago.
It doesn't turn off the screen when I take/make a call. I'm constantly putting my caller on hold or even hanging up with my ear or cheek. I've Googled the crap out of this and I've found MANY different settings to check/change - NONE of which exist on this phone.
So does anyone know? Is this simply not a feature of this phone?
Thank you.
bcsteeve said:
This has been annoying since I got the phone 7 months ago.
It doesn't turn off the screen when I take/make a call. I'm constantly putting my caller on hold or even hanging up with my ear or cheek. I've Googled the crap out of this and I've found MANY different settings to check/change - NONE of which exist on this phone.
Click to expand...
Click to collapse
I thought it was just me! I haven't looked for a solution as yet, but if you find one please post back here and share.
Actually I did resolve it finally! I installed a different dialer app and it worked with it. I hated the app though, so I uninstalled it. Before I had a chance to find a different app, a call came in (using the default app again) and it worked as it should. I can't explain why, but for me... installing a different app and then removing it got the default dialer to behave correctly.
Now that it works "correctly", I have noticed a quirk with it. I have to wait for an outgoing call to actually be ringing (which can take some time with some calls) before I put it up to my ear or the screen won't shut off until I bring the phone down and then back up. Now, it is *possible* that this was always the issue and I just never figured it out. So maybe the whole app install/uninstall thing is unnecessary. Not sure.
bcsteeve said:
Actually I did resolve it finally! I installed a different dialer app and it worked with it. I hated the app though, so I uninstalled it. Before I had a chance to find a different app, a call came in (using the default app again) and it worked as it should. I can't explain why, but for me... installing a different app and then removing it got the default dialer to behave correctly.
Now that it works "correctly", I have noticed a quirk with it. I have to wait for an outgoing call to actually be ringing (which can take some time with some calls) before I put it up to my ear or the screen won't shut off until I bring the phone down and then back up. Now, it is *possible* that this was always the issue and I just never figured it out. So maybe the whole app install/uninstall thing is unnecessary. Not sure.
Click to expand...
Click to collapse
I had a same problem too, but did resolved after factory reset. But I don't know where is the problem located, maybe the proximity sensor is very sensitive even with dust.
Sorry, bad English.
Your English is fine
I think you might be right, because my problem now seems to come and go. The screen definitely shuts off, but there's some times when my face will put the call on mute or other strangeness. I've even accidentally sent an email to my Mom, all with my cheek while on the phone with someone else! I had to click the back button 6 or 7 times to get back to the phone screen.
This phone was good value, but I do regret the purchase.
The proximity sensor is very sensitive, even with a very small string. I just test this when I call my second phone. And moving around my finger, and boom! My screen is turned off, but did turned on again after I moving away my finger. This is surprising me when I call my mom, and I force to turn off my device, and it's rebooted. After my device is successfully booted, I tried to call my Dad, and surprisingly the screen is not turned off. So I'll try to find the problem, and I founded them:
The proximity sensor is very sensitive, so be sure to wipe the proximity sensor until it gets clean completely.
That's it, so no matter if you use a different dialer or default dialer for your device, just keep in mind that I mentioned there.
Thank you. As always, sorry for my bad English.?