S Voice can't hear me and WiFI reconnects a lot?

ColdBrew

Well-known member
Jul 22, 2011
76
3
0
When I activate S Voice it can't hear me talk. Anyone else have this problem or know what could be wrong? Voice Actions can hear me, but it is just as useless as it was on my Bionic. It can't even call someone...

The WiFi seems to constantly be notifying me that it has connecting to my wifi. I never saw it act like that with my Bionic. Is there something wrong with the wifi in the phone?

Just to have something to say positive, it is quite a bit smoother (faster) than my Bionic...
 
Not sure about s voice but I hear it needs a lot of improvement. But not sure why it wouldn't be able to hear you at all. I saw in some other threads users talking about wifi connectivity problems. So I think we will have to see if it's a widespread problem and something an ota will fix or just a bug in some devices.
 
Not only can it not hear me, I can't hear it... I'm pretty sure I'm suppose to be able to hear what it is saying.
 
Okay, I feel dumb. Not sure why I didn't try this first. But a simple reboot fixed it. I'm actually pretty impress with S Voice.

I'm going to have to monitor WIFI longer to see how it's performance is. Maybe get a sample bigger than just my house.
 
FYI the S Voice stopped working again. It can't speak and it can't hear me. There seems to be some bugs in S Voice... Maybe it doesn't like one of my apps...
 
Even rebooting isn't fixing it now. It can't pick up sound for like a half a second and then it can't hear anything. This is after a fresh reboot.

I guess I'll contact Samsung and see if they can offer some help. I actually use voice commands a lot for calling people...
 
Any news on this? Mine is doing the same thing.

I just got the phone yesterday and it was working on the way home. After I got home and a bunch of updates hit it, and I put some apps on, it can't hear me.

Other things hear me - regular voice search, and even the lock screen - I can say "Hi Galaxy" and it fires right up and goes into S Voice. But once inside, whenever I speak, there's no "blue" in the microphone meaning it's hearing something. It comes back and says "I didn't catch that, but not audibly - just text.

I'm on Sprint, but since there was already a thread, I thought I'd check here first since the symptoms are identical.

(I'm not having a wifi problem, though)

Thanks,
Kevin
 
Yep I figured it out. And I feel really dumb but...

I just replaced my land line phone system at my home. It has the ability to connect to your phone using bluetooth. So when I was trying to use S Voice it was trying to listen to my commands through my land line phone handset. Once I disabled bluetooth or didn't have it connected to any headsets it works fine.

Personally I love S Voice. I think it works great. I never could get Google's voice software to dial any of my contacts, so it doesn't take much to impress me. But it can easily do that and more.

BTW, that is exactly how my S3 would behave.
 
Wow - that's exactly what I have - a Bluetooth home phone system.

Sure enough - I turned off BT and it works fine. that seems like an odd thing.

Thanks for helping me in the right direction, but did you find a workaround?

Kevin
 
When I'm at home and I want to use S Voice I have to disable the bluetooth first. It is just the way it is designed to work. I can't actually even talk to my phone through the handset. I can only dial out with it.
 
I had a Sprint phone fora week and it did the same thing, s voice didn't always work. Blue indicator didn't show sound. Sometimes a reboot fixed it. Now I have a Verizon version and the same thing happens.

I haven't found a likely explanation.
 
Thanks again for getting me sorted. I'm just glad I don't have a broken phone. I don't anticipate using it much at home anyway - I can set an alarm through Google's voice search.

Kevin
 

Forum statistics

Threads
955,372
Messages
6,964,603
Members
3,163,266
Latest member
realjordonjacob