Figure

HI 诗雨

根据当前的日志对比，在副屏调整音量后，中控未回复设置音量成功，导致了音量无法设置为静音。

正常日志：

05-12 15:59:55.775 1113 18232 D AudioIDCMicroNegotiator: idcm_volume:setIDCMicroVolume
05-12 15:59:55.776 1113 18232 D AudioIDCMicroNegotiator: idcm_common:requestResult method = setVolume parameters = {"functionInfo":{"IDCM_VolumeValue_Media":"0"}}
05-12 15:59:55.776 1113 18232 I MicroServiceManager: requestResult(setVolume) parameters is{"functionInfo":{"IDCM_VolumeValue_Media":"0"}}.
05-12 15:59:55.789 2153 23881 D MicroService: Send message to IDCM:SocketMessageBean{businessData='21930', srcService='FSEM_AudioService', destService='IDCM_CarAudioService', messageType='0', uuid='1683878395776530299', payloadData={"srcService":"FSEM_AudioService","dstService":"IDCM_CarAudioService","messageType":0,"uuid":1683878395776530299,"methodName":"setVolume","parameters":{"functionInfo":{"IDCM_VolumeValue_Media":"0"}}}}
05-12 15:59:55.842 2153 23882 I MicroService: Receive message: SocketMessageBean{businessData='21930', srcService='IDCM_CarAudioService', destService='FSEM_AudioService', messageType='1', uuid='1683878395776530299', payloadData={"srcService":"IDCM_CarAudioService","dstService":"FSEM_AudioService","methodName":"setVolume","messageType":1,"uuid":1683878395776530299,"parameters":{"functionInfo":{"IDCM_VolumeValue_Media":"0"}}}}
05-12 15:59:55.842 2153 23882 I MicroService: onResponse(setVolume): {"functionInfo":{"IDCM_VolumeValue_Media":"0"}} ★★★
05-12 15:59:55.843 1113 20922 D AudioIDCMicroNegotiator: idcm_common:response from IDCM method = setVolume parameters = {"functionInfo":{"IDCM_VolumeValue_Media":"0"}}
05-12 15:59:55.843 1113 20922 D AudioIDCMicroNegotiator: idcm_volume:onSetIDCMicroVolume mIsTimeout= false value = 0 isRequested=true
05-12 15:59:55.843 1113 18232 D AudioIDCMicroNegotiator: idcm_volume:setIDCMicroVolume return 0 ★★★

异常日志：
3-53 副屏.log:31950:11-11 03:53:05.412 D/AS.AudioService( 1135): idcm_volume:setIDCMicroVolume(stream=3, index=0, calling=com.thundercomm.remotecontrolservice)
3-53 副屏.log:31951:11-11 03:53:05.413 D/AudioIDCMicroNegotiator( 1135): idcm_volume:setIDCMicroVolume
3-53 副屏.log:31952:11-11 03:53:05.413 D/AudioIDCMicroNegotiator( 1135): idcm_common:requestResult method = setVolume parameters = {"functionInfo":{"IDCM_VolumeValue_Media":"0"}}
3-53 副屏.log:31953:11-11 03:53:05.413 I/MicroServiceManager( 1135): requestResult(setVolume) parameters is{"functionInfo":{"IDCM_VolumeValue_Media":"0"}}.
3-53 副屏.log:31954:11-11 03:53:05.427 D/MicroService( 2022): Send message to IDCM:SocketMessageBean{businessData='21930', srcService='FSEM_AudioService', destService='IDCM_CarAudioService', messageType='0', uuid='1668109985414484852', payloadData={"srcService":"FSEM_AudioService","dstService":"IDCM_CarAudioService","messageType":0,"uuid":1668109985414484852,"methodName":"setVolume","parameters":{"functionInfo":{"IDCM_VolumeValue_Media":"0"}}}}
3-53 副屏.log:31956:11-11 03:53:06.014 D/AudioIDCMicroNegotiator( 1135): idcm_volume:setIDCMicroVolume return null ★★★

下一步
该问题需要中控分析为什么收到设置音量的消息，没有返回设置成功的消息。

393415 05-10 18:22:38.152 I/HCOMHAL ( 596): {"srcService":"FSEM_AudioService","dstService":"IDCM_CarAudioService","messageType":0,"uuid":1668110021378319473,"methodName":"setVolume","parameters":{"functionInfo":

{"IDCM_VolumeValue_Media":"28"}
}}
393416 05-10 18:22:38.152 I/HCOMHAL ( 596): ---------------------------------
393417 05-10 18:22:38.152 I/HCOMHAL ( 596): HandShake is not completed, ignore msg!
395804 05-10 18:22:39.809 I/HCOMHAL ( 596): ---------------------------------
395805 05-10 18:22:39.809 I/HCOMHAL ( 596): {"srcService":"FSEM_AudioService","dstService":"IDCM_CarAudioService","messageType":0,"uuid":1668110023039399941,"methodName":"setVolume","parameters":{"functionInfo":

{"IDCM_VolumeValue_Media":"30"}
}}
395806 05-10 18:22:39.809 I/HCOMHAL ( 596): ---------------------------------
395807 05-10 18:22:39.809 I/HCOMHAL ( 596): HandShake is not completed, ignore msg!

Audio这边没有收到消息，看comhal的log好像是主副屏通信握手没有完成，帮忙分析一下

固定链接
YangWang7
Yang WANG 汪洋 添加了评论 - 2023/05/15 13:57
从EE云端日志分析，测试时间启动时间点是05-10 14:29左右。
从开机日志《Log_124_001_20230510143000_startup.log》分析，
启动后按正常流程握手成功：

01-01 08:00:16.912 596 633 I HCOMHAL : handShake check success!
6秒后因为没有收到副屏的心跳消息，判断心跳异常，判定握手失败，需要重新握手。
按照设计要求，之后所有消息都不进行处理。

11-11 00:00:27.665 596 632 W HCOMHAL : [heartbeatChecker]
11-11 00:00:27.666 596 632 D HCOMHAL : [onHeartbeatResult] Enter: isOK=0
11-11 00:00:27.666 596 632 D HCOMHAL : [onHeartbeatResult] End
需要副屏判断该特殊userdebug版本是否集成了程天颖的微服务心跳逻辑。
如果已经集成，为何这次启动握手成功后，6秒内没有收到心跳消息。

HI 天颖

心跳问题，麻烦分析一下，谢谢！

95版本的微服务使用的timer定时执行心跳任务，timer使用的系统时间定时执行任务，时间同步更改了系统时间可能会导致心跳断开连接，副屏于5月8日对该问题进行了处理，使用handler执行心跳任务，心跳问题已解决。此次修改将集成于00100版本，后续请使用00100版本进行测试