I have a new Asus 551ML, which worked well until recently. My GF has a late-model Samsung. I'm on T-Mob, she's Verizon, and as of this week an identical error has cropped up in both, leading me to believe it is driven by a non-vendor specific error, likely derived from an Android or Google Voice Input update.
The error is is when you are in an application allowing Google Voice Input, if you leave the input active and let the phone go into standby or locked screen, when the phone is unlocked the GVI screen is still apparent, but is not active. It eats half the screen real-estate, and cannot be gotten rid of without restarting the phone.
The error is is when you are in an application allowing Google Voice Input, if you leave the input active and let the phone go into standby or locked screen, when the phone is unlocked the GVI screen is still apparent, but is not active. It eats half the screen real-estate, and cannot be gotten rid of without restarting the phone.
