So I have a Vodafone s8+ that I got just a month ago. I just downloaded an update that they sent out a night or 2 ago (Android 8.0.0, Samsung Experience 9.0, build # R16NW.G955FXXu1CRB7) and since then I have been having periodic problems with the microphone:
Google Assistant does not hear me (acts as if I am constantly talking loudly but no discernible words)
Samsung voice recorder records loud static with no actual input from the mic
Trying to use the voice keyboard fails, not recognizing any speech
phone calls (normal; I'm not talking about speakerphone) work without difficulty (making a phone call actually "resets" the microphone so other problems disappear for 60-90 seconds whereupon the former problems reassert themselves) (the phone call doesn't have to actually go through - I can make the call and immediately hang up before talking and the "reset" still happens)
using a wired headset works without any difficulty
Rebooting causes the mic to work normally for 60-90 seconds
Rebooting in safe mode causes the mic to work until I leave safe mode
Using a BT headset works fine and has the same "reset" effect where the phone mic continues to work after I disconnect BT for about 60-90 seconds before the same mic problems reassert themselves
I am not 100% certain that the update is the cause. I had a malfunctioning BT headset at about the same time - obviously I am no longer using the headset and it is not connected (it is *off* and out of range) when the problems are occurring
Related
I have an interesting issue while using a Kitchen with Tachi Dialer (HTC Touch Pro)
I use a bluetooth headset almost everytime I make a call (I hate the handset as an actual phone)
It happens when I realize the wrong number has been dialed or the like (which also happens on occasion that it redials instead of dialing a selected number)
When I hit the end call button or the hard end button, the phone will think it has ended the call BUT the bluetooth headset is still in the call and the person can still pickup and talk. The headset cannot end the call and the soft and hard buttons also do not work.
The only way to end the call is to actually reset the phone or wait after the other end hangs up.
This seems to happen most if I end the call between dialing and when the headset establishes an active connection. (from the passive state)
I have 3 headsets:
Plantronics Voyager Pro
Voyager 815
Motorola H700
Any ideas?
Thanks,
Osiris
Hey,
I am having trouble with my Pioneer CD-BTB200 Bluetooth Adapter, which is a common problem, according to the very few available threads on the internet.
This also didn't work with any other Smartphone before i.e. Samsung S3 or Blackberry Bold 9700.
Cliffnotes:
-pairing, media streaming (different source) and receiving and making calls works great! No issues there
-transfering the contact list results in a big mess, I have to dig in there if I can figure it out or if I just transfer one contact after another....
-now for the problem.......I installed Cyberon Voice Commander because it gives me the best behaviour and voice recognition since I am a native German speaker. Google, Dragon and AIVC don't work really well. But it doesn't matter which voice assist app I use, because it is the Bluetooth adapters fault. The Nexus 5 is rooted and runs stock Kernel with KitKat 4.4.2.
When I press the voice dial button on my Pioneer AVH-P5000DVD deck it activates the Cyberon Voice Commander app (or whichever is set as default). so far so good, that is what I want.
But! the dialog between me and the phone is almost impossible because the output volume over the car speakers is way to low. I have to literally pick up the phone and look at it's display to see what the voice commanding app is doing because you have to wait until it is finished asking what I want to do. (just holding a phone is illegal in Germany)
Assuming the app understood me right and starts dialing everything turns to be fine from that point because the volume of the actual call is perfect!
When the phone talks back to me I have to crank the volume all the way up to understand it a little bit and then turn it back down fast before the phone call starts or it'll blow the speakers out....since my car is quite loud when on temperature I don't think I will understand anything when I am driving.
I heard that the app TASKER could be programmed to raise the Bluetooth volume at a certain point and then lower it again. I checked but it only goes up to 15, which I already have set before with the stock volume slider. Additionally I have no idea how to configure Tasker to (maybe) get rid of the problem.
Has anyone ever heard of a similar problem and / or has an idea how to handle it?
Again, it's only the voice command prompts that are way to quiet when I start the voice dialing function via Bluetooth, everything else is fine.
Fixed the issue with SoundAbout!
https://play.google.com/store/apps/details?id=com.woodslink.android.wiredheadphoneroutingfix&hl=de
Now the voice prompts play loud and clear over the car speakers! Every other volume managing app failed miserably!
I used the latest Beta Version btw, going to buy the Pro Version soon.
http://soundabout.userboard.net/f8-download-beta-versions
I did very little changes to the settings, if anyone is interested I can hook you up with some screenshots
sutobe said:
Fixed the issue with SoundAbout!
https://play.google.com/store/apps/details?id=com.woodslink.android.wiredheadphoneroutingfix&hl=de
Now the voice prompts play loud and clear over the car speakers! Every other volume managing app failed miserably!
I used the latest Beta Version btw, going to buy the Pro Version soon.
http://soundabout.userboard.net/f8-download-beta-versions
I did very little changes to the settings, if anyone is interested I can hook you up with some screenshots
Click to expand...
Click to collapse
I have this issue as well. SO what did you have to do with this app?
I'm not sure when this issue started exactly but I've noticed that when using bluetooth both at home (I have a set of cordless phones with bluetooth link) and when linked to my two automobiles both receiving and initiating calls after a few seconds of conversation the phone suddenly switches to using the microphone and earphone instead of the bluetooth connection. This has occured with wifi on and off...in 3g and 2g areas....while tethering and not....etc....seems to be consistant with the device and I don't recall it doing it in the past so I'm wondering if the most recent 6045i update to ue40 might be part of the problem....in any case I'm looking for suggestions of apps or settings changes that might help with the bluetooth. I should mention I've also had music playing in the car drop at random intervals or at least I stop being able to hear it. This was playing local content so it wasn't a streaming issue.
I just flashed the OTA update for Android 6.0 last week on my Nexus 5 and I noticed that with the new update, phone calls no longer get routed through Bluetooth on my Mazda3. It is able to pair fine with the car and can stream music through Bluetooth, but calls do not go through.
Here is what happens:
When I place a call, the audio automatically gets routed back to the phone. If the other person picks up, calls will continue going through the phone speaker unless I manually select route through Bluetooth. Sometimes this works and sometimes it doesn't, but it does get frustrating trying this workaround especially while driving.
I tried unpairing and re-pairing bluetooth with the car, cleared the data and cache of the Bluetooth app on the phone, and even tried a factory reset, but the problem still persists. Anybody else run into the same issue and found any possible fixes?
For the record, when I did this with Lollipop 5.1.1, it worked without a hitch.
Thanks!
I am having a similar problem trying to connect my Nexus 5 running Android 6.0 to my JVC car stereo. It continually complains of an invalid key, albeit both phone and car head unit show the correct key.
I am unable to make a bluetooth connection at all with the stereo. I had no issue with my Nexus when it was running 5.1, and my iPhone 5 continues to pair with the stereo.
I had this issue on the last preview but haven't seen it yet on final 6.0. For either regular calls or Hangouts calls.
I just rolled back to 5.1.1 and Bluetooth calls work fine with the car now. So it appears that it is a problem that is resident in 6.0.
Same here, but a little different: It pairs and when I start a call from the menu it goes down but the call is still up on the phone. When the other person picks up the call is re-routed to the car speakers... very strange behaviour!
Same behavior as what you are seeing when paired to a '15 Accord but works fine on a '14 Camry.
im at 6.0.1 and has the same problem, streaming music through bluetooth is ok but no voice call...
Any news on this? My wife's nexus has same problem. Nexus 5 with Android 6.0.1. compiling version M4B30Z.
I read on a different site to disable wireless scanning in location. Just tied that and have been able to make and receive calls from the car. Will be interesting to see if it continues to work.
During the last few weeks, I am having an issue with bluetooth audio during calls. The issue is exactly the same as another user in https es (dot) verizonwireless (dot) com
/sdcommunity/t5/Android-General/Bluetooth-audio-drops-from-headset-during-call-while-headset-and/td-p/1150368), so much so, that I used the same subject.
During a call, where I can speak and listen with the bluetooth headset, suddenly the audio begins to be routed to the phone itself (without any warning). The dialer UI still shows, wrongly, that the audio is being routed to bluetooth (the icon on the dialer is green). The fastest way to restore it to the headset during the call is to press the bluetooth button on the phone dialer (green to white) and again (white to green). Not very hands-free...
I have made a few tests and this is what I came up to:
- When it happens, the volume keys on the headset doesn't work, but the end-call button (on the headset) does (the call ends if pressed), so the headset is still connected to the phone.
- repairing, disabling media and contacts access (just enabling call access) on the bluetooth headset made no difference to the issue. Also restarting the phone, btw.
- As far as I can tell, it only happens with normal calls, since that is not happening with WhatsApp, Telegram, Skype or Hangouts calls.
- It happens randomly. Sometimes in a hour call it never happens, sometimes it happens 2, 3 times.
I was wandering if this is a new issue with the March 1 patch in S7 or something with my config.
I have:
Android: 8.0.0
Baseband: G935FXXS8ETC2
Build: R16NW.G395FXXS8ETC3
Patch level: March 1, 2020
If anyone experiences the same, has an idea, or something before I connect the device to the PC in debug mode to try to sort it out.
Best regards,