Just installed the Vicious 4.1 JB ROM a few days ago. Everything seems to be working fine except the voice commands. They simply don't work. In the Search Box, the mic animates as if its hearing me, then it reverts to "Tap mic to begin speaking" message. In Navigation, Translator, or any other app--I get no animation as if its hearing me. On top of that: I can't hear people on a call unless I'm on speakerphone. Any ideas what the heck is going on?
P.S. - I apologize if this is the wrong forum (I couldn't post in the JB thread because I'm a noob to the forums.)
The thread of the rom you installed is probably where you would want to post a question like this. You might want to look through that thread and see if anyone has had similar problems. I have been running a clean JB 4.1 rom for the last week of so and haven't had any problems with the voice commands or with hearing a caller. Personally, I would think you would want to do a fresh install of the rom. Good luck.
bcrawford said:
The thread of the rom you installed is probably where you would want to post a question like this. You might want to look through that thread and see if anyone has had similar problems. I have been running a clean JB 4.1 rom for the last week of so and haven't had any problems with the voice commands or with hearing a caller. Personally, I would think you would want to do a fresh install of the rom. Good luck.
Click to expand...
Click to collapse
I've looked through the thread and done various thread searches with no similar results. I can't post to the thread because I'm new to the forum and I've re installed the ROM once already. I appreciate the feedback though
Welcome. It will all be golden very soon!!!!!!
Sent from my Galaxy Nexus using Tapatalk 2
You need to set the voice language to English us. Any other type of English and the voice commands go and you are only left with Google search. If you do switch to English us, it struggles to understand you with a London accent!
still nothin'
Ok, at this point, I've unrooted, gone back to 4.0.2, Superwiped, and flashed to 4.1.1. I still have no voice commands from the search bar, in Navigation, and nobody can hear me in calls except if I'm on bluetooth or speakerphone. I'm perplexed. In addition, My GPS takes about 10 minutes to lock-on using Navigation or Runkeeper Pro. Any suggestions?
Related
ive tried searching around and a few have reported the problem but ive seen no fix yet. i just loaded cm7 .. awesome ...my only problem is no voice input? is there a patch?
Wow! A whole year and not a single reply as well as no change with this issue in all that time. Is there some fear of voice input with the CM guys? I have CM7.2 loaded and just noticed this and was wondering .......?
What do you mean by no voice input?
I ran CM7.1 not long ago, and don't remember any problems with voice inputs. I wouldn't use a ROM if I couldn't use Voice Dialer. I use Voice Dialer, all the time. I also used voice input for Navigation, Search, etc. on occasions. I also used the app vlingo, for a while. Are you talking about some other kind of voice input?
I had to give up on CM for other reasons, though. I currently use Inc-Deck 1.3 gingerbread, which is based on CM7 (and extremely similar) and all my voice functions work fine on it, too.
Hmm. Vioce dialer is the only thing that is working then. The first thing I came across was the navigation wouldn't allow voice input. something about it not being present or some such thing.
Download voice search in the market. It won't work without that
-My life is a shooting range, people never change-
^^
what he said... I forgot that wasn't included with CM ROMs
then it'll all be working for ya
What do you know? That fixed it. Thanks! Surprised GAPPS didn't take care of that.
is there a download or fix for the bluetooth voice command....my bluetooth works but when i push the button on the bluetooth it says give command and then there is an error followed by, it disconnects. any advice on what to do or where togo to get the fix for this problem?
I've not been following the latest news on Epic, but if Sprint has released 2.2 I think you need to manually update your phone. Though from what I've read in the previous days was that Sprint did send out an update to some Epic users but the update was buggy. Therefore not everyone had their phone updated. Though assuming you're new to this forum ? And perhaps your Epic ? If your phone has 2.1 then there's no way you're going to be able to use your headset as 2.1 isn't capable of dialing out only accepting calls and manually making calls. I'm using midNIGHT custom rom and by using midNIGHT my headset does dial out. So join in on the forums and read up. I know there was a recent post http://forum.xda-developers.com/showthread.php?t=967014 That should be of great assistance to making your phone a lot better. Though most importantly I'm new here too and perhaps someone can give you better advice. But I do know that your phone out of the box won't allow you to voice dial using a headset until you're updated to Froyo and that I recommend midNIGHT rom but there are many roms to choose from as well as a lot of reading and learning which can be fun.
Before I get n00b bashed, I did "Search this thread" for the answer... (and other forums) Maybe I am just too n00b? Anyway, here goes.
Given kudos on this ROM already (Syndicate Rom: Frozen...anything is better than stock Froyo, but this is just AMAZING). But I was having some troubles with receiving incoming calls. Caller always got "All circuits busy" Or "cannot complete call as dialed".
Soooo, I wiped and reflashed. Tried to make a call (before restoring titanium backups) it worked, but my girl was still having troubles calling me...
So I restored most of my titanium backup (stuff that mattered?) and when trying to call out, I get "com.android.phone stopped working" and had to forcibly close it. So, I specifically restored phone 1.0 and contacts and all that from my titanium Backup, and still got the same issue. I am currently backing up stuff to my computer off the phone, going to format the card and do a fresh flash and see if that helps.
Thing to note, my account IS linked with Google Voice. Could that be an issue? And if not, is anyone else having this issue? Seriously the ONLY problem I am having with this rom. Thanks, guys!
Edit. Wipe and reflash did not help, however the phone is running MUCH better! Still not getting phone calls, though. Data works, MMS, etc, spotty 3G acceptance, though. Starting to get a bit aggravating. ANY help would be GRAND.
*sigh* think I got it. Flashed a different modem (EC03?) and it did not work, then flashed BACK to EC05 (AFTER the fresh flash) and it seems to have rectified the issue. HUGE thanks to QBKING77 (if that is his name on here) for the AWESOME video tuts and great linking to the site. I will update if call status changes. But I would still be interested in knowing if anyone else was having the same issues?
Sorry no one ever got to you for help. The Q&A section doesn't exactly have dedicatedhelpers. =/
I'll be trying to help this section more. So please do update if it comes again.
Sent from my Epix 4G using XDA
Shoulon said:
Sorry no one ever got to you for help. The Q&A section doesn't exactly have dedicatedhelpers. =/
I'll be trying to help this section more. So please do update if it comes again.
Sent from my Epix 4G using XDA
Click to expand...
Click to collapse
No worries. My girl and I gave it another go this morning, and all went well. Also received all my calld last night with no issue. Definitely made my girl a happy camper. Lol. Now I just have to calibrate my battery when I get to work, and all will be golden!
Sent from my SPH-D700 using XDA Premium App
the only thing I could think of is did you "freeze" any apps in titanium LOL yes I froze the wrong thing once and got the same error's I think it was the voice mail stuff seeing i went to gvoice didn't think I needed it but I did.
Nope. All apps were left unfrozen, just because I am too n00b for that chit, lol.
However, I flashed the EC05, and all incoming calls (90%) seem to be coming to me. Odd part is, it SHOULD be going to my voicemail if it cannot be dialed. I am thinkin Sprint is to blame, and I need to have it out with them.
*sigh*
Oh well, everything else is tits... Just waiting EAGERLY for 1.2... Chompin at the bit and all that!
Might get bored tonight and flash back to stock... see if I have the same problem.
Question. Let's say I want to "image" my phone the way it is right now (kinda like Norton Ghost used to do?) Flash back to stock, yadda yadda... Is there a way to RESTORE my phone as is (every byte) back with clockwork? Or is that what Nandroid does? Because if I flash back to Stock, play for a bit (see if it is sprint's fault) and want to flash back, I will have to reconvert back to EXT4... using clockwork 3.0, should I just use the .zip (.img?) that nandroid creates instead of the base ROM?
If any of that makes sense, kudos will be given for a clear answer, lol
just loaded Emerald Envy 2.0....
Absolutely love the ROM, but I can no longer receive calls. I've tried the wipe (x3), re-downloaded the ROM, no joy. no combination that I can think of. Have tried all the latest modems (EC05/EF02), no joy.
I did notice that the phone log does log that a call was received, but it never rings or brings up the phone application.
I also tried flashing the Genocide 1.1 kernal. no joy.
I'm about to go back to my Midnight ROM that I Nandroid'd earlier today before I started down this road. Really hope I don't have to, i'm hooked on this ROM!
Any help would be greatly appreciated!
-Todd
Sully1965 said:
Absolutely love the ROM, but I can no longer receive calls. I've tried the wipe (x3), re-downloaded the ROM, no joy. no combination that I can think of. Have tried all the latest modems (EC05/EF02), no joy.
I did notice that the phone log does log that a call was received, but it never rings or brings up the phone application.
I also tried flashing the Genocide 1.1 kernal. no joy.
I'm about to go back to my Midnight ROM that I Nandroid'd earlier today before I started down this road. Really hope I don't have to, i'm hooked on this ROM!
Any help would be greatly appreciated!
-Todd
Click to expand...
Click to collapse
My errors seem to be different than yours. Mine would not show up in my call log at all, nor would the calls go to voicemail. Are your callers able to leave messages?
Mine turned out to be a sprint/phone issue. Their networks have been all kinds of crappy in my area since january. Sucks, but all I could do was call, complain, and get credits.
My new epic seems to be working fine, and sprint seems to have fixed their issues in my area. I was running 1.2 up until last night with no issues callin/receiving. I only updated to the latest GB leak because it is hella stable and netflix works. Just seems to have some 3d issues. But I do not game much on here.
Keep troubleshooting, and give 1.2 a whirl. While your problem is not ROM related, I am very confident your experience (and battery) will be much better.
Oh. And call Sprint. Complain and whine. You will get credit on your bill. Lol.
Sent from my Epic. Which is better than yours.
New user, first post, if I am missing info then I apologize.
I have the tmobile galaxy s 3 SGH-t999.
Started looking around at different roms, etc, ended up with trying the cyanogenmod 10 first.
Did the required steps, used oden to load the clockworkmod recovery.
Wiped/factory reset, then loaded up the rom. Seemed to work pretty well other than some issues with the cam crashing (seperate issue which I researched and believe I have the answer to). But overall the problem was that intermittently the inbound audio on calls sounded robotic, and reverberating. Also dealt with 4 hour battery life. Tons of info to address later when this issue is corrected however.
Have been digging around on forums, and see this issue, but no articles yet (that i have found) addressed for the SGH-t999.
Ended up re-wiping the phone and put on the liquid smooth rc9 (d2tmo).
So far it appears i am having basically the same exact issues that occurred in cyanogenmod. If I reboot the phone, it will continue. Then for whatever reason the next few calls or so later that are sent or received it sounds fine. Then back to robotic.
End user can hear me fine. The audio issue is just for inbound voice.
Tried to factory reset again, still the same issue.
I have installed the google pack to be able to use play store, etc. Perhaps this is causing the issue?
I did try to get the log cat, but could not replicate the issue while running it, so I am not sure if it would be of any use or not.
Also, this issue does not make a difference whether bluetooth is enabled or not. Am not doing wifi calling, have not tested that yet.
Again very sorry if this article is incomplete.
Thanks in advance for the help!
Resolved
tsm233 said:
New user, first post, if I am missing info then I apologize.
I have the tmobile galaxy s 3 SGH-t999.
Started looking around at different roms, etc, ended up with trying the cyanogenmod 10 first.
Did the required steps, used oden to load the clockworkmod recovery.
Wiped/factory reset, then loaded up the rom. Seemed to work pretty well other than some issues with the cam crashing (seperate issue which I researched and believe I have the answer to). But overall the problem was that intermittently the inbound audio on calls sounded robotic, and reverberating. Also dealt with 4 hour battery life. Tons of info to address later when this issue is corrected however.
Have been digging around on forums, and see this issue, but no articles yet (that i have found) addressed for the SGH-t999.
Ended up re-wiping the phone and put on the liquid smooth rc9 (d2tmo).
So far it appears i am having basically the same exact issues that occurred in cyanogenmod. If I reboot the phone, it will continue. Then for whatever reason the next few calls or so later that are sent or received it sounds fine. Then back to robotic.
End user can hear me fine. The audio issue is just for inbound voice.
Tried to factory reset again, still the same issue.
I have installed the google pack to be able to use play store, etc. Perhaps this is causing the issue?
I did try to get the log cat, but could not replicate the issue while running it, so I am not sure if it would be of any use or not.
Also, this issue does not make a difference whether bluetooth is enabled or not. Am not doing wifi calling, have not tested that yet.
Again very sorry if this article is incomplete.
Thanks in advance for the help!
Click to expand...
Click to collapse
Ok, after 4 different roms, and lots of testing, I finally figure it out.
Using Voxer caused the issue. As soon as a voice message is sent using voxer, the problem starts immediately, and is correct by a reboot. Issue immediately returns once Voxer is used.
Any idea of how to work around this, besides the obvious? =)
Okay so I know that Google Now does not want to work with Bluetooth microphones, headphones, or anything of the sorts.
However I have heard that in the newer versions of Android (at least 4.2.2 and up) Google Now has had its code rewritten and it now works with Bluetooth.
My whole issue is that S-Voice is a slow piece of s**t and doesn't manage to do anything that I want it to do, particularly interface with Play Music. I have installed a pretty awesome stereo in my car, but I feel that S-Voice with all of its prompts and on screen pop ups is unsafe for driving, whereas Now would suit my needs much better.
Essentially what I'm asking is that if I were to put an Android 4.2.2 ROM on my device (recommendations highly appreciated, preferably with WiFi calling enabled), if it would interface with my head unit when I need to use handsfree (activated by a little telephone call button on my JVC head unit that currently enables the annoyingly slow S-Voice app).
Any ideas? I tried a workaround using 'Bluetooth Launch' and disabling S-Voice already, as advised on a few other forums... no such luck... just gave me an error code on the head unit. Kinda a strange thing, I know. Let me know if you have any ideas.
Thanks a bunch for your help and input, it's much appreciated.
PS. I'm really sorry, I hope there isn't another thread similar to this, I'm totes a noob
Not sure if bt will work like you want on a 4.2 2 rom. But you cannot have wifi calling unless its a T-Mobile Touchwiz based rom. We only have up to 4.1.2 on those.
Make a nandroid backup and try out a couple of roms. If you like the functionality enough, keep it, if not restore the nandroid.
Sent from my SGH-T999 using xda premium