Since late April, shortly after the Nexus S was released to the masses, a bug with Voice Search has haunted many users. Some have been so annoyed to the point where they’ve just ended up returning the phone. Others have looked to third party solutions such as flashing custom ROMs as well as downloading applications that keeps the issue from happening.
The bug causes Voice Search to initiate without the user expressly opening the application or holding the search button. It happens more often than others for some folks with reports of the application flickering on top of any application they’re using, making the phone useless until they find some way to get it to stop (usually by restarting the phone, but that only helps the problem for so long).
Google has supposedly been investigating since the problem was pointed out to them, but they have since let nearly 4 months’ worth of complaints pile up with nary a word on their progress. Early troubleshooting efforts wondered if different combinations of hardware versions and software versions caused the issue, but so many different people have reported the issue that those variables don’t seem to be the ultimate cause of the issue.
Even AT&T Nexus S owners, who are on the latest hardware version and on Android 2.3.4, are having the issue, meaning whatever the problem is Google likely hasn’t made an attempt to fix it. Users are urging others to try to get Samsung and the carriers they bought the phone from to offer support, but that doesn’t seem to be working. We’re not sure why they’ve been so pedestrian on getting to the bottom of this, but we’re hoping this spotlight will help get things rolling on a true fix. [Google Support Forums, Thanks Patrick!]