-
Notifications
You must be signed in to change notification settings - Fork 25
alexa-smart-screen-sdk error #8
Comments
Could you attach the log messages starting right when SampleApp has started? Thanks, |
Hi @bennyAv10 for INFO
|
Hi @bennyAv10 for DEBUG9
|
Hi @shubhamsbhosale96 , Can you try running with the AVS Device SDK SampleApp? You can check the instructions on how to run that SampleApp in the quick start guide |
avs device SDK sample app working fine. |
I have re-installed AVS Smart screen sdk with fresh raspbian stretch os on RPi. |
Could the problem be related to the remote desktop software (VNC)you are using? Can you try on the Raspberry Pi directly? |
thanks |
IMPORTANT: Before you create an issue, please take a look at our Issue Reporting Guide.
Briefly summarize your issue:
while testing alexa smart screen sample app by pressing and holding "A" button, It doesn't take voice input. Terminal displays=
E AudioInputProcessor:executeRecognizeFailed:reason=Barge-in is not permitted while busy
What is the expected behavior?
when press and hold the "A" button, alexa should take voice input and provide output with display template.
What behavior are you observing?
2019-11-30 11:26:33.391 [ 3] 3 GUILogBridge:GUILog:component=WSClient:message sent, type: holdToTalk
2019-11-30 11:26:33.391 [ 6] 9 WebSocket:AccessLog
2019-11-30 11:26:33.392 [ 6] 9 WebSocket:AccessLog
2019-11-30 11:26:33.393 [ 6] 9 WebSocket:AccessLog
2019-11-30 11:26:33.393 [ 6] 9 WebSocket:AccessLog
2019-11-30 11:26:33.393 [ 6] 9 GUIClient:onMessage:payload={"type":"holdToTalk"}
2019-11-30 11:26:33.394 [ 6] 9 GUIManager:handleHoldToTalk
2019-11-30 11:26:33.397 [ 6] 9 WebSocket:AccessLog
2019-11-30 11:26:33.397 [ 19] E AudioInputProcessor:executeRecognizeFailed:reason=Barge-in is not permitted while busy
2019-11-30 11:26:33.398 [ 6] 9 WebSocket:AccessLog
2019-11-30 11:26:33.398 [ 6] 9 WebSocket:AccessLog
2019-11-30 11:26:33.398 [ 6] 9 WebSocket:AccessLog
2019-11-30 11:26:33.399 [ 6] 9 GUIClient:onMessage:payload={"type":"logEvent","level":"info","component":"WSClient","message":"message sent, type: holdToTalk"}
2019-11-30 11:26:33.399 [ 6] 9 WebSocket:AccessLog
2019-11-30 11:26:33.399 [ 3] 3 GUILogBridge:GUILog:component=WSClient:message sent, type: holdToTalk
2019-11-30 11:26:33.400 [ 6] 9 WebSocket:AccessLog
2019-11-30 11:26:33.400 [ 6] 9 WebSocket:AccessLog
2019-11-30 11:26:33.400 [ 6] 9 WebSocket:AccessLog
2019-11-30 11:26:33.400 [ 6] 9 GUIClient:onMessage:payload={"type":"holdToTalk"}
2019-11-30 11:26:33.401 [ 6] 9 GUIManager:handleHoldToTalk
2019-11-30 11:26:33.401 [ 6] 9 WebSocket:AccessLog
2019-11-30 11:26:33.401 [ 19] E AudioInputProcessor:executeRecognizeFailed:reason=Barge-in is not permitted while busy
2019-11-30 11:26:33.402 [ 6] 9 WebSocket:AccessLog
2019-11-30 11:26:33.403 [ 6] 9 WebSocket:AccessLog
2019-11-30 11:26:33.403 [ 6] 9 WebSocket:AccessLog
2019-11-30 11:26:33.403 [ 6] 9 GUIClient:onMessage:payload={"type":"logEvent","level":"info","component":"WSClient","message":"message sent, type: holdToTalk"}
2019-11-30 11:39:44.117 [ 37] 9 HTTP2Transport:onActivity
2019-11-30 11:39:44.117 [ 37] 9 HTTP2MimeResponseDecoder:onResponseFinished:status=COMPLETE
2019-11-30 11:39:44.117 [ 37] 9 MimeResponseSink:onResponseFinished:status=COMPLETE
2019-11-30 11:39:44.117 [ 37] 7 MessageRequestHandler:onResponseFinished:status=COMPLETE,responseCode=204
2019-11-30 11:39:44.118 [ 37] 7 MessageRequestHandler:reportMessageRequestAcknowledged
2019-11-30 11:39:44.118 [ 37] 7 MessageRequestHandler:reportMessageRequestFinished
2019-11-30 11:39:44.118 [ 37] 7 HTTP2Transport:onMessageRequestFinished:countOfUnfinishedMessageHandlers=0
2019-11-30 11:39:44.118 [ 37] 0 AudioInputProcessor:onSendCompleted:status=SUCCESS_NO_CONTENT
2019-11-30 11:39:44.118 [ 37] 5 AudioInputProcessor:stopCapture:reason=streamClosed
2019-11-30 11:39:44.118 [ 37] 0 LibcurlHTTP2Connection:streamFinished:streamId=AVSEvent-31,result=No error,CURLcode=0
2019-11-30 11:39:44.118 [ 37] 9 LibcurlHTTP2Connection:releaseStream:streamId=AVSEvent-31
2019-11-30 11:39:44.118 [ 37] 7 MessageRequestHandler:reportMessageRequestAcknowledged
2019-11-30 11:39:44.118 [ 37] 7 MessageRequestHandler:reportMessageRequestFinished
2019-11-30 11:39:48.323 [ c] 0 DialogUXStateAggregator:transitionFromThinkingTimedOut
2019-11-30 11:39:48.323 [ c] 0 DialogUXStateAggregator:setState:from=THINKING,to=IDLE
2019-11-30 11:39:48.323 [ c] 5 TemplateRuntime:onDialogUXStateChanged:state=IDLE
2019-11-30 11:39:48.323 [ 19] 1 FocusManager:releaseChannel:channelName=Dialog
2019-11-30 11:39:48.323 [ 5] 9 WebSocketServer:writeMessageBegin
2019-11-30 11:39:48.323 [ c] 5 AlexaPresentation:onDialogUXStateChanged:state=IDLE
2019-11-30 11:39:48.324 [ 5] 9 WebSocket:AccessLog
2019-11-30 11:39:48.324 [ 19] 0 AudioInputProcessor:setState:from=BUSY,to=IDLE
2019-11-30 11:39:48.324 [ 5] 9 WebSocket:AccessLog
2019-11-30 11:39:48.324 [ 5] 9 WebSocketServer:writeMessageComplete
2019-11-30 11:39:48.324 [ 17] 9 AudioInputProcessor:onFocusChanged:newFocus=NONE
2019-11-30 11:39:48.324 [ 6] 9 WebSocket:AccessLog
2019-11-30 11:39:48.324 [ 6] 9 WebSocket:AccessLog
2019-11-30 11:39:48.324 [ 6] 9 WebSocket:AccessLog
#################################
ALEXA STATE: IDLE
#################################
Provide the steps to reproduce the issue, if applicable:
cd /home/pi/sdk_folder/ss-build
PA_ALSA_PLUGHW=1 ./modules/Alexa/SampleApp/src/SampleApp -C
/home/pi/sdk_folder/sdk-build/Integration/AlexaClientSDKConfig.json -C
/home/pi/sdk_folder/alexa-smart-screen-sdk/modules/GUI/config/SmartScreenSDKConfig.json -L DEBUG9
Tell us about your environment:
What version of the AVS Device SDK are you using?
Tell us what hardware you're using:
Tell us about your OS (Type & version):
The text was updated successfully, but these errors were encountered: