Truly, your obsession with this isn't helping you get it solved. I'd recommend switching to a different ROM if this is that important, and coming back to try this with subsequent releases. Task has made it pretty clear that your continual "input" on the subject is just making him not want to work on it. Patience and silence will get you better results...
Tasks problem with me was that I was posting a lot in the dev thread asking questions about this issue without providing the correct information(a logcat for example) and I wouldn't let up. I realize I screwed up and was just obsessing about it because I use it often, and love the feature of google voice search on JB and google now. I have run tasks ROM's on my phone and galaxy tab 10.1 for about the past year now and another ROM is not an option for me because even without the voice to text working it's still the best ROM for this phone. I am really upset for pissing task off and it wasn't my intent but I have OCD and if it isn't working right but it's working right for everyone else I have to figure it out otherwise it's all I think about and I obsess over it. I pissed my girlfriend off too because I have been neglecting her for the past 3 days trying to fix my phone. Not only was my voice-to-text not working, my pc wasn't even recognizing my phone. Which is why I wasn't able to post a logcat when I was originally pissing task off and posting questions(in the dev thread none the less). So I had to fix that, then once I fixed that ADB wouldn't recognize my phone, now I fixed that. So I have been working while off work non-stop trying to figure out this problem. The problem is I'm not a developer and cannot read or understand logcats or kmesg's I hardly know how to use ADB as long as I have instructions and cmds to follow I can installed a kernel after rooting without triggering the flash counter and I now know off the top of my head how to creat a log-cat. So my knowledge is limited.
Like I said I apologized to task, I realize my mistakes and was disrespectful. I'm a huge supporter of his work, I just want some help and have the tools to get the necessary information to get help(as in am able to get logcats now and use ADB). I hope task accepts my apology and takes a minute to look into my problem.
I tried flashing ktoonez's newest kernel he released today and that didn't fix it. I just uninstalled Google Search from tibu and copied the quicksearchbox.apk or whatever from system/app to my sdcard root before doing that as well as made a backup, then I replaced the quicksearchbox.apk into my system/app folder, rebooted into recovery, wiped cache, dalvik, and fixed permissions(not to mentioned I fixed permissions manually when I copied the .apk back to system/app to rw/r/r/
Maybe a newer release of GAPPS will help? I've been using 7/26/12 since, but what Im' doing right now is I redownloaded 8/13 to see if it works then because I remember it used to work.fine and on 8/13 so far it has worked fine I'm gonna not restore anything and all I have done is sign into google at first boot. I will gladly install each release from 8/13 to 8/23 to see which release the problem starts at to narrow down what is causing it and I can't imagine it would take much after I figure out which release caused the problem. And I fell flashed 8/13, tested voice-to-text, it continued to listen to me no problems...fell asleep, restored my apps, still worked fine. Now I'm trying 8/17..
