I only use the simple voice recorder and playback. I've tried unsuccessfully to load up the Chrome Browser to try out the voice recognition, but gave up after reading about all the problems you all are having.
The simple voice recorder issues are a delay in the start of the record function causing the intitial sounds to be cut off, which can be solved by counting to three before starting to speak after clicking on the record button.
The second is that the "auto-end" detector is so sensitive to background noise, that it continues recording long past the time I stop speaking. So I rarely use it, as when I do my daily first hour of listening to past, present, and future sentences I like to move super fast, and this delay slows me down by a factor of 3 ot 4. It its handy when the study goal is to learn or refine correct pronunciation, at a slower pace.
About a month ago I suggested adding a "Finished Recording" button which would override or even replace the auto finish detector.
BTW there has apparently been a change in the selection order of Flashcards and test rating so the program focuses on the non-easy cards first which is good.
My original suggestion about this was to add a button to allow us to do them either way, not give up the ability to review all cards as a complete set.
I like to start my morning by quickly going through all the flashcards for the Modules I am in and sometime previous and upcoming modules - not just the hards ones which slow me down.
"Blitzing" through several hundred in a few minutes is the way I like to warm up.
So I am hoping on the wish list the Rocket Team will add a toggle switch that empowers us to do them all in a set or focus just on the "non-easy" ones, or even just one column of "hardest."
When I used paper flashcards 1000 box sets I used to play all sorts of games with order, like sorting them by gender, or having the twelve hardest ones that I would do over and over 20 times to get them to sink in.
One principle for software learning systems I espoused in my companies is that they should always be at least as functional as the paper based systems they intend to replace or surpass. This goal is not always possible but should always be an aspiration for the programming and design teams.