Contextual voice menu in an activity can blank it when it resumed after a different one is closed

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Using the new contextual voice mentioned here:
https://developers.google.com/glass/develop/gdk/voice
to launch new activities directly, using Intent.

2. After closing those "called" activities (using "swipe down" or calling 
"finish()" from the code), I can see that the current activity that has the 
voice menu sometimes displays a blank screen.

What is the expected output? What do you see instead?
I expect to see the original activity. instead, I have a blank screen.
Using the touch pad reveals that the app is still running, only that specific 
activity was blanked and reopening that activity will bring it to life

What version of the product are you using? On what operating system?
XE 18.11

Original issue reported on code.google.com by moshe.sc...@gmail.com on 25 Jun 2014 at 3:11

[GoogleCodeExporter]

I am also facing the same issue. It doesnt happen always but can be reproduced 
easily 

Original comment by dileepmo...@gmail.com on 25 Jun 2014 at 8:46

[GoogleCodeExporter]

I am also facing same issue in my app

Original comment by muneer...@gmail.com on 26 Jun 2014 at 7:03

[GoogleCodeExporter]

All in all it seems that using the voice menus will take its toll in 
performance.
My app becomes very slow and I hardly written any code for it.

Original comment by moshe.sc...@gmail.com on 30 Jun 2014 at 6:16

[GoogleCodeExporter]

Well... I updated to 18.3.
It seems that the original bug is fixed.

Now I have a different one - related one.
When I close an activity which was called from a voice menu, the voice menu 
stops responding to voice.
the "ok glass" is there, but it won't respond to "ok glass".
closing and opening the app will fix it until the next time...

I would love a feedback from the Glass team, or anyone else for that matter.

Thanks,

Moshe

Original comment by moshe.sc...@gmail.com on 1 Jul 2014 at 1:26

[GoogleCodeExporter]

I'm getting the same issue as as #4 in XE19.1.

This seems to happen when one voice triggered activity starts another voice 
triggered activity. Once the second activity is finished, the first activity 
will say *ok glass* but it won't respond. 

If I have the touch menu enabled in the first activity, that continues to work 
and once I trigger the touch menu, the voice menu (i.e. *ok glass*) will start 
working. However this is no longer a hands-free experience since I need to tap 
on the device to re-enable the voice menu. 

Original comment by rkch...@gmail.com on 31 Jul 2014 at 6:30