Database Info

[Q] Unable to get VoiceEngineWrapper (S-voice w/ gear on non samsung device)

I have a Nexus 4 and followed the tutorial on how to get things working on it in regards to the gear. Most of the stuff works now but i have an odd issue with s-voice:
When i open it on the gear, it will run, but the first time i run it after a restart, the phone shows an error: "Unable to get VoiceEngineWrapper"
On the gear, the voice sounds distorted and pitched with some weird echo. It also replies with "I didn't catch that" to whatever command i give it.
I tried to google the error i'm getting on the phone since i'm assuming it's connected, but nothing comes up. I was trying to get the google now voice engine to replace the s-voice tts since i've heard it can be done but i can't find any info on how to do it. Only thing i found was settings-tts-download us voice and set it as default.
If anyone smarter than me has some ideas on what in the world that error means or what else to try, I would appreciate it.
Thanks!

noctrin said:
I have a Nexus 4 and followed the tutorial on how to get things working on it in regards to the gear. Most of the stuff works now but i have an odd issue with s-voice:
When i open it on the gear, it will run, but the first time i run it after a restart, the phone shows an error: "Unable to get VoiceEngineWrapper"
On the gear, the voice sounds distorted and pitched with some weird echo. It also replies with "I didn't catch that" to whatever command i give it.
I tried to google the error i'm getting on the phone since i'm assuming it's connected, but nothing comes up. I was trying to get the google now voice engine to replace the s-voice tts since i've heard it can be done but i can't find any info on how to do it. Only thing i found was settings-tts-download us voice and set it as default.
If anyone smarter than me has some ideas on what in the world that error means or what else to try, I would appreciate it.
Thanks!
Click to expand...
Click to collapse
I have the very same problem on a Nexus 5 device.

noctrin said:
I have a Nexus 4 and followed the tutorial on how to get things working on it in regards to the gear. Most of the stuff works now but i have an odd issue with s-voice:
When i open it on the gear, it will run, but the first time i run it after a restart, the phone shows an error: "Unable to get VoiceEngineWrapper"
On the gear, the voice sounds distorted and pitched with some weird echo. It also replies with "I didn't catch that" to whatever command i give it.
I tried to google the error i'm getting on the phone since i'm assuming it's connected, but nothing comes up. I was trying to get the google now voice engine to replace the s-voice tts since i've heard it can be done but i can't find any info on how to do it. Only thing i found was settings-tts-download us voice and set it as default.
If anyone smarter than me has some ideas on what in the world that error means or what else to try, I would appreciate it.
Thanks!
Click to expand...
Click to collapse
Same issue here. I have searched everywhere and can't seem to find any solutions. I've seen videos of people using s voice on the gear 2 with a nexus 5, but not sure what firmware versions, etc. they are using. Are there any other threads or solutions out there?

Pixel dumps SMSC upon restart

So, this is bit of a new issue, one I've not had before. I wish Hangouts/Messenger still had the Service Center ID in the settings in order to fix this, but, in the long/short run...
I unboxed my pixel and put my SIM in, started the phone. LTE/UMTS work perfect, locked right on, good signal/speeds, can place/receive calls, all is right in the world? I noticed after an hour I hadn't received any texts, and after feeling very unimportant, I sent a SMS to a friend, and got an immediate error. Out of curiosity, I went into the INFO settings (*#*#3646#*#*) and went into the SMSC settings. pressed refresh, which, populated an error. I manually typed mine, hit update, went back to hangouts, and voila!
The next day, I restarted the phone ( I like to do this often. I am also this user who actually turns their phone off from time to time ) and noticed upon restart, the problem resurfaced, like as if I never updated it to begin with.
Is this occurring with anyone else? I've yet to see a phone completely dump it. I'd prefer not to download another SMS application really, but, it's just inconvenient those few times I do restart it that I lose that SMSC number...

I'm having the problem as well but still haven't been able to fix it with the same procedure you did. It's driving me nuts.
UPDATE EDIT: I just realized the Wifi is interfering with it. As soon as I turned off the wifi, the txt would go out.

I'm having this same issue. I've contacted support about it, but haven't gotten a response yet (they said I would have an update yesterday).
If I manually put the SMSC in, and then Update, I can send texts briefly, but eventually I start getting an error 38 instead. A reboot and then manually entering the SMSC again allows me to send texts again.

vagosto said:
I'm having the problem as well but still haven't been able to fix it with the same procedure you did. It's driving me nuts.
UPDATE EDIT: I just realized the Wifi is interfering with it. As soon as I turned off the wifi, the txt would go out.
Click to expand...
Click to collapse
I'm curious if setting your mobile data to always-on would be a functional workaround to help until they can get this fixed for real. Have you tried that?

S voice not working today

Hi guys
I got my gear s3 delivered yesterday and have been playing with it for the past couple of days. Yesterday the voice commands worked okay but tonight when I have tried to set an alarm I just get a message saying "I'm unable to process your request, please try again later"
Is s voice working for anyone else? I so wish this watch could use Google voice. That works great every time.
Cheers
Edit: I have the voice set to united kingdom, if I set it to USA it works. Could be the server is down possibly

Mine even set to English US also not works

I figured out the problem with mine. The S voice app got updated yesterday and I think something went wrong with the install. So I backed up my data through the Samsung gear app and did a factory reset on the watch. All my apps then transferred back automatically including the update for S voice which installed correctly this time.

It has stopped working again tonight saying "I could not find an answer to your question"
Hate S Voice

After working fine suddenly I get the same response when using s voice to make a call."An error has occurred. Try again later".

Tried backup, reset and restore
Following Rob77's lead I backed up to the Samsung Cloud, reset my S3 then restored my backup. Sadly none of my purchased apps got restored! But the good news is S Voice is functioning once again. Flakey Tizen

S Voice problem since 3.0

hey, i've been using the Gear S3 since half a year now, after being disappointed by AW 2.0 ruining my Moto 360 2nd gen
since the 3.0 update, i often get an error using s-voice with simple commands like "set timer for ten minutes"
sometimes it works, but often getting an error after a few seconds, show either "an error has occurred. i'm unable to answer your question. please try again later" or "an error has occured, try again later"
has anyone else encountered this problem and found a fix?
i did a factory reset twice now, didn't help, not changing the s voice language from automatic to us english
the other stuff i wanted from the update also didn't happen, but i guess that's a different discussion

I am having the same problem. I had purchased the S3 Frontier when it 1st came out. I returned it due to problems with svoice. I just purchased it again last week and svoice is still garbage. Was hoping for it to be better. Will be returning again.

i did not have this problem with 2.x, voice commands like this never showed the error, for me it started after the 3.0 update

Same problem here can't reply to a message with voice and errors when simple commands like the OP stated.
I get around the message problem by setting the language to English UK

I still get the error message after the latest update on the gear update. I need to re-flash the stock Tezin on it hoping it will fix it.

Same issue with S3 Classic
Same issue here with my S3 Classic. Occasionally it works but most of the time I get the error. Reported it to Samsung but they were unaware of the issue and were non-responsive.

View attachment 4365678my fix for this issue was to clear cache for s-voice. you can do it from s-voice menu
bottom button that looks like refresh

Same x 2
My S3 Tmobile LTE failed in 6 days. They exchanged it for a new one at the store yesterday and that one failed also. So I returned it since it's a defective product. I'll buy again when the issue is fixed.

S-Voice implementation on the watch is just total garbage. No way around it.
I like the notification system and the magnetic payments, but nothing is intuitive and nothing can be trusted to just work without having to re-try three times. Voice commands are an exercise in frustration.
Nine times out of ten, my watch says it can't understand me, can't find the contact I want or can't find any contacts at all even though I can open contacts on the watch and they're all there. I'm sitting here with a Galaxy s8+ and their flagship Gear S3 Classic watch and they don't complement each other at all.
Implement FREAKING GOOGLE ASSISTANT you lamebrains!

WaxysDargle said:
View attachment 4365678my fix for this issue was to clear cache for s-voice. you can do it from s-voice menu
bottom button that looks like refresh
Click to expand...
Click to collapse
how often to you have to clear out the s-voice ??

matthewinaz said:
how often to you have to clear out the s-voice ??
Click to expand...
Click to collapse
Every time you want it to work.

gboybama said:
S-Voice implementation on the watch is just total garbage. No way around it.
I like the notification system and the magnetic payments, but nothing is intuitive and nothing can be trusted to just work without having to re-try three times. Voice commands are an exercise in frustration.
Nine times out of ten, my watch says it can't understand me, can't find the contact I want or can't find any contacts at all even though I can open contacts on the watch and they're all there. I'm sitting here with a Galaxy s8+ and their flagship Gear S3 Classic watch and they don't complement each other at all.
Implement FREAKING GOOGLE ASSISTANT you lamebrains!
Click to expand...
Click to collapse
I have the exact same experience Gboybama! Some contacts i can call, some produce an error message, some let svoice "synchronice contacts", which is never finished, letting the problem persist even after clearing cache, stopping the app, restart etc... **** this.

matthewinaz said:
how often to you have to clear out the s-voice ??
Click to expand...
Click to collapse
i only had to do it once. it has been working "fine" ever since.
s-voice never quite works properly. never has. i doubt it ever will. seems like samsung just doesn't care.

I just got my s3 today to go with my new s8+ having tons of iss6 with s voice. Looks like I'm not alone. Probably going to be returning this and researching other options.

good and bad to hear it also happens in combination with Samsung phones.
the last response i got from them:
"@SamsungSupport: There will be slight compatibility trouble considering it is not paired to a Samsung device. ^Aaron"
i removed all apps from my phone, reset the watch, reinstalled the apps and set up the watch as new. worked for a couple of days then back to the same, 9 out of 10 (or even more) it would simply give me the "an error has occurred"
i don't understand the error doesn't include an error code, how are they even supposed to understand what's going wrong with just "an error has occurred"
I'd fire the developer, project manager or whoever thought this was ab good idea
but indeed, Samsung doesn't seem to care

good and bad to hear it also happens in combination with Samsung phones.
the last response i got from them:
"@SamsungSupport: There will be slight compatibility trouble considering it is not paired to a Samsung device. ^Aaron"
i removed all apps from my phone, reset the watch, reinstalled the apps and set up the watch as new. worked for a couple of days then back to the same, 9 out of 10 (or even more) it would simply give me the "an error has occurred"
i don't understand the error doesn't include an error code, how are they even supposed to understand what's going wrong with just "an error has occurred"
I'd fire the developer, project manager or whoever thought this was ab good idea
but indeed, Samsung doesn't seem to care

Op 7 pro tmo

First this is a rant, and I have seen multiple threads with some of the same problems.
1. Day one (right after unboxing) when I first powered on the device, I could not hear the other person on the phone. I tried calling multiple times, I even called on facebook messenger, they could hear me, but I could not hear them. The only way for me to get around this was to reboot my phone. This went away for a little bit, but has been happening again and again more frequently now.
2. BT will randomly switch from headset/stereo to phone speaker without any warning. Just a simple swap from talking to someone over BT and then thinking they hung up or disconnected, only finding out that it decided to swap from BT to phone. Incredibly annoying, and I have even lost some business calls from it.
3. Stock messaging app does not work. It wont send or receive messages. I have to use another 3rd party app to send and receive my text.
4. I am constantly getting notifications that there is a problem with getting my voicemails. Now I lose calls due to the BT failure, and now I do not get the voicemails when they try to all back.
5. Apps will not install. It will download them but it freezes at the install portion, I have tried clearing everything-cache and what not, and only way to get around this is to reboot the phone again. really annoying when I want to install an app, I have to reboot my phone. Although I have had the same problems with my Note 8, So it is most likely a google issue.
Any one have any ideas on these? I am going to try and talk with TMO but odds are they will tell me to do a system reset.
Thanks.

Have you tried reflashing stock and a factory reset?

I would also suggest the factory reset.
However, I have been having issues with the play store this evening installing apps just as you mentioned. Cleared the cache and rebooted, everything installed fine then.