A nice piece of technology, but

A nice piece of engineering, except for a few problems.
The device, so connecting to the Android smartphone (we have a Sony Xperia L, Android 4.2.3 and a Sony Xperia Z1 with Android 4.4.2) is simple to make and is not actually wrong with the spoken instructions of this unit.

Sony Xperia L with Android 4.2.3
it was absolutely impossible to move the Google Voice Control to work together in spite of all the Met settings, ie speech, language files (incl. Offline packages) in German, has not understood us the Sony Xperia L. It was probably still tuned for English language instructions. However, this is explicitly not the problem of Jabra.
But what a problem the Jabra is:
There are Android an event when the Bluetooth button (that would be the Jabra tour of "Talk Button" with the head icon) pressed longer, you can let it react a few apps. So we have the Cyberon Voice Commander tried to start it, but when you press the button a bit longer said, nothing comes on the Android device, it is called the Jabra Tour mode instead of the Jabra internal voice commands. Unfortunately it was not possible under Android 4.2.3 the short press the talk button with Cyberon link.
Conclusion: Google voice input could be called up, but responded incorrectly to the voice commands. Cyberon could not start with Jabra.

Well, we still have a second device, the Sony Xperia Z1 with the latest Android 4.4.2
Here worked the voice control via Google, hooray, I called, na finally.
Until the phone lock screen indicated. Everything then happened on the phone when you press the Talk button:
You will see a gray screen with "Initialize", then does nothing more.
The whole way, we have tried also with a HTC phone, the same effect.
EXPRESS is a bug in Android, which is described here [...]
Well, I thought, under Android 4.4.2 I can the Bluetooth Button Press Event with Cyberon Voive Command link, which unlike Android 4.2.3 works fine. Only take this app on this device, no voice commands to, probably a bug in the app Cyberon.
OK, further research led me to Voice Command patch which solves the problem that the gray screen with "Initialize" in the blocked phone no longer appear and you can actually access the Google voice input.
No sooner said than done, but now radioed another problem with the Jabra tour in between:
You press the Talk button (when the screen is locked) then the following will happen:
1. On the phone launches the Google voice input
2. The Jabra roars loud audible "Please wait"
3. The Jabra roars loud audible "Not Supported!"
4. Wait for 2 3 seconds
5. Now one could speak
OK, I thought, no problem, a challenge, simply stellste from the speech of Jabra.
Said and done, only one can no longer hear who is calling you. The Jabra reads namely NORMALLY the caller's name, which we find quite useful, finally one has the phone in your pocket while driving.
Buy OK, another app installed which reads the name of the caller on my smartphone.
But again, Jabra has a trick: When a call comes in does not exist Jabra sound on the phone again, but it has its own ring tone, so you hear only the faint blare of Jabra, but not the sound output of the smartphone which desperately the name of screams calling into Datennirwana because it is ignored by Jabra.

So we abandoned it as Jabra Voice Control for Android to use, it is simply not possible to make an outgoing call without the smartphone while driving to take into their own hands. Who has still managed, may indeed like to comment. I hope to update from Android / Cyberon and will probably try again in a few months.

If you can live with the fact that you can not fully use the voice Android devices, receives a solid little device with crystal-clear sound, long-running, high ease of use and a really good micro. We have to keep it because of these properties. My girlfriend now knows this limitation and after some initial grumbling she uses it now very happy.