-
Notifications
You must be signed in to change notification settings - Fork 58
Speech to Text stops working after 3 to 4 minutes in Android SDK Version 1.2.2 #69
Comments
I am getting the same problem as well, did u manage to find a workaround/fix for it ? |
after 10 minutes, using a subscription key with the client java sdk and in longdictation speech recognition mode, i get the following error: 03-21 13:25:25.490 14967-15013/com.microsoft.CognitiveServicesExample I/NLPLAT: Waiting for connection/send completion. |
@redphoenix2k no fixes found for this and no reply from Microsoft as well |
Same problem:
After 5-15 minutes (very often if the voice commands not use a long time) and with a paid key:
Workaround for me - did set Timer with tic at few minutes:
|
Hello,
We are facing issue using speech to text API, it works fine for around 4 minutes and suddenly it stops working. When checking in logcat(Android studio error logger) it shows errors as below. We are using it with subscription key
02-08 03:30:02.434 27572-4854/ I/NLPLAT: WebSocket closed unexpectedly, status: 0
02-08 03:30:02.844 27572-4865/ I/NLPLAT: Failed to 'hresult', HR=80004005, WebSocket connection failed
.....
.....
.....
02-08 03:30:11.552 27572-5155/ I/NLPLAT: Failed to 'hresult', HR=80004005, WebSocket connection failed
02-08 03:30:11.552 27572-5155/ I/NLPLAT: WebSocket closed unexpectedly, status: 0
02-08 03:29:38.057 27572-8428/ I/NLPLAT: WebSocket closed unexpectedly, status: 0
02-08 03:29:38.057 27572-8428/ I/NLPLAT: Initiating websocket connection. m_connection=0xbdf1d924 host=websockets.platform.bing.com port=443
02-08 03:29:38.060 27572-8430/ I/NLPLAT: WebSocket closed unexpectedly, status: 0
02-08 03:29:38.062 27572-8430/ I/NLPLAT: Initiating websocket connection. m_connection=0xbdf1d924 host=websockets.platform.bing.com port=443
02-08 03:29:38.065 27572-8432/ I/NLPLAT: WebSocket closed unexpectedly, status: 0
Any help would be highly appreciated.
The text was updated successfully, but these errors were encountered: