Accessibility Skip to content
Article ID: 000035661
Last Modified Date: 12/10/2021
Access Level: Public

Miracast works intermittently with Trio 8800

Customer is reporting that Trio 8800s do not always pair with Windows machines everytime for Miracast. After reviewing the Trio logs, these events stood out: 1016112552|wdisp|1|00|[void RTCSDK::ContentSharingAssistant::stopWirelessDisplayContent()] 414 stopWirelessDisplayContent++ 1016112552|lc   |2|00|MsgPpsSessionDrop reason 22 1016112552|lc   |3|00|Session stopped of type 2 video 1016112552|lc   |1|00|Session type 2 is already stopped (video)  
Reason code Meaning
22 Invalid RSN information element capabilities
 
In Linux Wifi Networking, reason 22 during beacon transmission/negotiation+authentication/802.11-setup”   means that the negotiation of security parameters for the wifi connect failed. Keep in mind that Miracast is simply a "Direct Wifi" connectoion from your Windows machine to the Trio, no different than the connection between you windows machine and your access point wifi router.  
Since RSN parameter negotiation was failing between windows laptop & Trio during Wifi-Direct connection set up, fine tunning the Trio's Wireless 802.11 adapter for United States use resolved the customer issues. After configuring the below parameters, the Trio no longer had Miracast connection issues.     content.wirelessDisplay.sink.enabled="1"
  content.wirelessDisplay.sink.name="PGS Voice Test"
  content.wirelessDisplay.sink.authorizationType="Button"
  content.wirelessDisplay.sink.bitrate="30"
  content.wirelessDisplay.sink.fps="30"
  content.wirelessDisplay.sink.height="1080"
  content.wirelessDisplay.sink.width="1920"
  device.set="1"
  device.wifi.country.set="1"
  device.wifi.country="US"
  device.wifi.radio.band2_4GHz.enable.set="1"
  device.wifi.radio.band2_4GHz.enable="1"
  device.wifi.radio.band5GHz.enable.set="1"
  device.wifi.radio.band5GHz.enable="1"
  device.wifi.enabled.set="1"
  device.wifi.enabled="0"
  device.net.enabled.set="1"
  device.net.enabled="1"