Quickstart: Run the Speech Devices SDK sample app on Android
In this quickstart, you'll learn how to use the Speech Devices SDK for Android to build a speech-enabled product or use it as a Conversation Transcription device.
The source code for the sample application is included with the Speech Devices SDK. It's also available on GitHub.
Before you start using the Speech Devices SDK, you'll need to:
Follow the instructions provided with your development kit to power on the device.
Download the latest version of the Speech Devices SDK, and extract the .zip to your working directory.
The Android-Sample-Release.zip file includes the Android sample app and this quickstart assumes that the app is extracted to C:\SDSDK\Android-Sample-Release
If you plan to use the Conversation Transcription you must use a circular microphone device and this feature is currently only available for "en-US" and "zh-CN" in regions, “centralus” and “eastasia”. You must have a speech key in one of those regions to use Conversation Transcription.
If you plan to use the Speech service to identify intents (or actions) from user utterances, you'll need a Language Understanding Service (LUIS) subscription. To learn more about LUIS and intent recognition, see Recognize speech intents with LUIS, C#.
You can create a simple LUIS model or use the sample LUIS model, LUIS-example.json. The sample LUIS model is available from the Speech Devices SDK download site. To upload your model's JSON file to the LUIS portal, select Import new app, and then select the JSON file.
Set up the device
Start Vysor on your computer.
Your device should be listed under Choose a device. Select the View button next to the device.
Connect to your wireless network by selecting the folder icon, and then select Settings > WLAN.
If your company has policies about connecting devices to its Wi-Fi system, you need to obtain the MAC address and contact your IT department about how to connect it to your company's Wi-Fi.
To find the MAC address of the dev kit, select the file folder icon on the desktop of the dev kit.
Select Settings. Search for "mac address", and then select Mac address > Advanced WLAN. Write down the MAC address that appears near the bottom of the dialog box.
Some companies might have a time limit on how long a device can be connected to their Wi-Fi system. You might need to extend the dev kit's registration with your Wi-Fi system after a specific number of days.
Run the sample application
To validate your development kit setup, build and install the sample application:
Start Android Studio.
Select Open an existing Android Studio project.
Go to C:\SDSDK\Android-Sample-Release\example. Select OK to open the example project.
Add your speech subscription key to the source code. If you want to try intent recognition, also add your Language Understanding service subscription key and application ID.
For speech and LUIS, your information goes into MainActivity.java:
// Subscription private static String SpeechSubscriptionKey = "<enter your subscription info here>"; private static String SpeechRegion = "westus"; // You can change this if your speech region is different. private static String LuisSubscriptionKey = "<enter your subscription info here>"; private static String LuisRegion = "westus2"; // you can change this, if you want to test the intent, and your LUIS region is different. private static String LuisAppId = "<enter your LUIS AppId>";
If you are using conversation transcription, your speech key and region information are also needed in conversation.java:
private static final String CTSKey = "<Conversation Transcription Service Key>"; private static final String CTSRegion="<Conversation Transcription Service Region>";// Region may be "centralus" or "eastasia"
The default keyword is "Computer". You can also try one of the other provided keywords, like "Machine" or "Assistant". The resource files for these alternate keywords are in the Speech Devices SDK, in the keyword folder. For example, C:\SDSDK\Android-Sample-Release\keyword\Computer contains the files used for the keyword "Computer".
You can also create a custom keyword.
To use a new keyword, update the following two lines in
MainActivity.java, and copy the keyword package to your app. For example, to use the keyword 'Machine' from the keyword package kws-machine.zip:
Copy the keyword package into the folder “C:\SDSDK\Android-Sample-Release\example\app\src\main\assets\”.
MainActivity.javawith the keyword and the package name:
private static final String Keyword = "Machine"; private static final String KeywordModel = "kws-machine.zip" // set your own keyword package name.
Update the following lines, which contain the microphone array geometry settings:
private static final String DeviceGeometry = "Circular6+1"; private static final String SelectedGeometry = "Circular6+1";
This table lists supported values:
Variable Meaning Available values
Physical mic configuration For a circular dev kit:
For a linear dev kit:
Software mic configuration For a circular dev kit that uses all mics:
For a circular dev kit that uses four mics:
For a linear dev kit that uses all mics:
For a linear dev kit that uses two mics:
To build the application, on the Run menu, select Run 'app'. The Select Deployment Target dialog box appears.
Select your device, and then select OK to deploy the application to the device.
The Speech Devices SDK example application starts and displays the following options:
Try the new Conversation Transcription demo. Start transcribing with 'Start Session'. By default everyone is a guest. However, if you have participant’s voice signatures they can be put into a file
/video/participants.propertieson the device. To generate the voice signature, look at Transcribe conversations (SDK).
If you cannot connect to the Speech Device. Type the following command in a Command Prompt window. It will return a list of devices:
This command uses the Android Debug Bridge,
adb.exe, which is part of the Android Studio installation. This tool is located in C:\Users[user name]\AppData\Local\Android\Sdk\platform-tools. You can add this directory to your path to make it more convenient to invoke
adb. Otherwise, you must specify the full path to your installation of adb.exe in every command that invokes
If you see an error
no devices/emulators found then check your USB cable is connected and ensure a high quality cable is used.