I found that it occurs when using the "Messages" App with the tap to speek. I was also able to recreate problem this same way, by pushing the sleep button once the tap to speak screen is up. However, I switched over to the "Message +" App and trying to recreate it did not work. So maybe by using the Message + app it won't happen. So far so good........
For now, everyone here should consider going to the App Manager, selecting Google App, and Uninstall Updates. Then wait for word on when either Samsung or Google corrects this conflict.
Worked for me!! On my Samsung S6, I went to Settings, Applications, Applications Manager, Google App, Uninstall Updates, and confirmed actions. Basically it restores the app to factory settings. I'm not getting the Tap To Speak freeze-up anymore where the app won't close/won't respond and the Google App is still functional. If Google responds to all the grievances and complaints with a patch or an update that works corrected, please post and let us know.
It seems I was able to stop this from happening by uninstalling the updates, then going to the Play Store Andrey downloading the updates for Google app. Good luck y'all! That was really annoying
Same thing started on my Note 3 last week. Today, it happened every time I used voice-to-text. Had to reboot each time. I uninstalled the Google App update, and it hasn't happened since.
Mine freezes up and I can't use it of course and I can't type a text message either. It blocks my screen so I basically have to restart the phone to have it reset. I am also having crazy noises coming thru my phone as if it has been taken over by a scrambler if that makes sense.
Mine happens so often that I have been forced to type text messages or restart it 25 times a day and that seems to be wearing my battery down. I was getting 3 days on a charge now I am having to charge every day seems like the culprit, maybe not? I don't know.
Thought the google app update from yesterday was the fix, but nope. The problem is back today. Uninstalling all the updates and going back to the factory install version has fixed the problem for me as of now. Guess I'll wait a month or so and update the app. Hopefully the issue will be fixed by then.