• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

ics update, voice talk, and bluetooth issue

I don't know if I'm the only one with this issue, but since I updated to ics, voice talk wont work with my bluetooth. Let me explain, if I use my handsfree blueant s4 to initiate phone commands (voice talk), it wont work or turn on my phone because its on standby. I have to get my phone out of standby and press "tap & speak" or say "Hi Galaxy" and then it will work. This makes the handsfree bluetooth, well, useless. I don't have a lock on my phone, so that can't be an issue. Someone please help, every since getting my license I've been doing the whole not texting or talking while driving because Its dangerous. Now that I can't properly use my bluetooth,if I ever have to make a call, I have to pull over.

UPDATE: I was able to find two useful android apps that have been helping me. One of them is called "BtWIFIUnlocker" by Joel Stern. I use this to unlock my phone when it is connected to my Bluetooth or wifi. I can set it up in the way that would lock my phone once its not connected to that specific bluetooth/wifi and unlock it when it is.
"Keep Screen on" byOne Coder from the android market is another one that has been helping me. I use it before I get in the car to prevent my phone from going into standby.
These two apps help in the sense that while I use my Bluetooth the phone stays unlocked and NOT on standby, so when I do hands free calling voice talk opens up!
The down side is that "keep screen on" does, of course, drain the battery, which is why I only use it in the car while charging my phone or on full battery.
 
When I did the update on my phone, I had to un-sync the phone with my truck then sync them up again to get the hands free and Bluetooth audio to work again. That may be what you need to do.
 
I am having the same issue; even with the new FH13 update. Probably this is not a big issue for the majority of people that use this phone so I don't have my hopes up of someday Samsung getting this bug fixed!!!
 
I am having the same issue; even with the new FH13 update. Probably this is not a big issue for the majority of people that use this phone so I don't have my hopes up of someday Samsung getting this bug fixed!!!

I got the update as well, and it didn't fix it, it was meant to fix battery issues though which isn't relevant to this issue.
 
This worked for me as well, unpair and then pair. Well as far as i can tell as i just did it after reading a different thread. Based on my readings, this is a ics issue not sprint/verizon or any other carrier as we are all haveing issues.....
 
I am having the same issue with or without a BlueAnt Q2 headset with the Voice command / Voice talk not working after getting the ICS update and as of today the FH13 update. When I speak into the headset or at the phone, I can see where my voice command is being "heard" by the phone and it appears to be "processing" the request, but it comes back with a "network operation timed out. Please try again". Before the ICS update, the Voice Dial / Voice Command worked great (with or without headsets (Jawbone II, Jawbone Prime and Jabra Extreme). Being that I use my Sprint Samsung Galaxy S2 for work-Is there another Android app that works "better" for voice dialing contacts in the phone? The S2 is a great workhorse, but the voice dialing issue is killing it!
 
Back
Top Bottom