New Update Coming Soon! Here's the Change for 4.4.2 164.55.2

Question

This new update has allot of things in it and it seems it will be coming out pretty Soon)  if this update is Good and has solved some things might we see it shortly after Moto X  all we can do is Hope..
Here is the the Update Via the Good people at Droid Life..
http://www.droid-life.com/2014/02/21/android-4-4-2-update-approved-for-verizon-moto-x-as-164-55-2-here-is-the-changelog/

Answer 1

Got the update this morning and ever since the Google Now voice integration basically doesn't work anymore. Here's what's happening:
I first thought that it was freezing and then rebooting the phone, which it definitely seemed to do a couple of times, but the main pattern is this.
I'll say the "OK Google Now" phrase and get the prompt for "Yes?" and say something as simple as "What time is it?" and it will pop the result up on the screen, but will not give the voice response as it used to do. Then basically as soon as the phone's screen turns off either via timeout, or manually turning the screen off with the power button. The phone stops responding to the on/off button, no active display, or anything. I noticed though by doing the "camera wrist twist" function, that I feel the vibration for the camera app being opened. Nothing ever appears on the screen though. I can press the part of the screen where the "onscreen" back button would normally be showing and exit out of the camera app, and do the wrist twist again and lauch the app again, and repeat this process over and over again, but still with no screen display until I hold down the power button and reset the phone. I also had one instance where the phone froze when trying to answer a call as well.
Has anyone seen anything like this before?
It mainly just seems to be related to the Google Now integration. I took it to one of the local Verizon franchises and was told if a soft reset didn't fix it, that I would have to try to factory reset it, which I'll do if I have to, but it just doesn't seem like that should be the case. I was using a 3rd party laucher "Nova Laucher" and I disabled it, and that didn't resolve the problem. I've also removed the phone from the case I have it in to insure it wasn't something with the case, and again, that didn't help the problem either.
Thanks,
Garrett