I'm sorry to say we ended up activating Google speech-to-text manually on all 150 remaining devices. I haven't been able to find a way to automate this.

If I understand correctly, speech-to-text is part of the Google app, com.google.android.googlequicksearchbox. Specifically the com.google.android.googlequicksearchbox:interactor part. Yet if I enable this either through StageNow or through MobiControl, nothing changes in the Virtual Keyboard settings.

I tried enabling google.cloud.speech.v1, but that's basically the Google API for speech-to-text. So that didn't get me anywhere either.

Are you using lockdown menu or application-run-control profile payload on your devices?

We're using a lockdown menu, yes.

Anybody an idea?

Hi Theun,

With your lockdown menu enabled, have you add  Launch://com.google.android.googlequicksearchbox as the last item in your lockdown profile payload?  IF not,  add it and test if voice input is OK on your device.  Don't worry about having an extra item in the test, as there are simple tricks to handle the issue later.

Hi Raymond,

Thanks for replying. I did have Launch://com.google.android.googlequicksearchbox incorporated in the lockdown, but as the second-to-last entry. I switched it to the last spot. However, I'm not showing it as an icon in the lockdown though. Is that okay?

It's OK not to show the item as an icon (i.e. no <MCDispImg#> in the html, but  <MCLink#> should be there).  The more important thing is that you should be able to find the mic (i.e. voice) input icon added on the soft keyboard.  Is that so?

Yes, the icon's available. It just doesn't do anything at the moment. It starts working when Google speech-to-text is enabled, which I've enabled manually on a bunch of devices (for now).

The Google Speech-To-Text option in Settings of course needs to be enabled.   On Zebra devices, this may be automated with Zebra MX script.  You have to check the Zebra's documentation for details.  Maybe Matt (https://discussions.soti.net/profile/matt-dermody-1/) can give you a quick answer on this.

That was the original question, yes. Mind you, it's speech-to-text I'm after, not text-to-speech. Thanks for the help so far.

This customer's got about 145 devices left in the field with Google speech-to-text disabled, I've already been trying to get it to work through StageNow and mxconfig but without any progress I'm afraid.

Hello Theun,

Thank you for your post, is it possible for you to share screenshot of the device where it says disabled for Speech to Text?

Regards,

com.google.android.googlequicksearchbox is indeed needed for this to work. How was this disabled in the first place on the devices? Are you using an Application Blacklist or perhaps Zebra's GMS restricted mode? Are you using StageNow for enrollment or another method like DPC Identifier (afw#mobicontrol), NFC, or QR?

Thank you for your replies. Hereby a screenshot of the 'manage keyboards' screen. All devices were enrolled using StageNow and its barcodes and Google speech-to-text (or "Google spraakgestuurd typen" in Dutch) was disabled manually, before the devices were sent to the customer. It's not blacklisted.

Enabling com.google.android.googlequicksearchbox isn't enough to switch the above option back on. I'm hoping there's an intent or command I can send to the devices to sort this out, otherwise we'll have to try and manually enable speech-to-text on all affected devices through MobiControl's remote control. Also an option, it'll just take a while.

Hello Theun,

Following up on this thread, were you able to resolve the issue? If yes, I would like to know what were the steps taken to resolve the issue and I can mark that as a Solution.

Regards,