Hi everybody,
I am trying, and failing, to use an LG TV as a wireless display.
The TV is an LG xxLF652V. Per LG documentation and TV user interface it does support WiDi and Miracast. I could verify (on www.wi-fi.org) it is listed as Miracast certified; don't know about any WiDi certification. I can use that same TV as a wireless display for an Android smartphone without any problem.
The computer is a desktop using an Intel Dual Band AC 7260 + Bluetooth (via a PCIe+USB to miniPCIe adapter card; adapter + 7260 = ‘GIGABYTE GC-WB867D-I REV. 2.0 867Mbps’).
- Operating system: Windows 7 with Service Pack 1 (64-bit). I previously tried with Windows 10 and the perceived behaviour is the same. I installed Win7 back in order to use 100% Intel tools and to avoid extra possible problems (for example it was a huge pain to get the latest graphics driver instaled).
- CPU: i5-4590S
- Graphics: integrated Intel HD Graphics 4600. No other grapich card present. Driver version: 10.18.14.4414.
- Wireless: Intel Dual Band Wireless-AC 7260. Bluetooth enabled/disabled does not change the behaviour. Driver version: 18.33.3.2.
- Intel Pro WiDi version 6.0.66.0
- The WiDi Compatibility Checker (1.0.4.10) concludes everything is ok and up to date.
When I start the Intel WiDi application it does see the TV. I click on the TV name and it tries to connect. At first it asked for the PIN displayed on the TV, now it doesn’t anymore (guess it remembered it). Then it tries to connect but nothing happens; the TV also shows the information that <COMPUTERNAME> is trying to connect (but no more PIN; it did display a PIN in the past). After quite some time it gives up (the TV gives up a bit earlier) with an error message ‘There was a problem connecting to the wireless display [LG] webOS TV LF652V’; no details as to why.
I attach a logfile generated when trying to connect.
Maybe this is a red herring, but what I noticed looking inthere is the following:
...
07:42:11:163,[t:0x1040] : Handle_WIFI_EVENT_PAN_CLIENT_JOINED - WIFI_EVENT_PAN_CLIENT_JOINED EA-F2-E2-02-9A-1E [L=5][M=WFDDNS][F=WFDDnS.cpp: 958]
07:42:11:163,[t:0x1040] : Handle_WIFI_EVENT_PAN_CLIENT_JOINED - Not the address we are connected to: EA-F2-E2-02-1A-1E [L=7][M=WFDDNS][F=WFDDnS.cpp: 967]
...
07:42:15:323,[t:0x1040] : Handle_INTEL_WIFI_AUTH_SUCCESS - MACAddress: EA-F2-E2-02-9A-1E [L=7][M=WFDDNS][F=WFDDnS.cpp: 700]
07:42:15:323,[t:0x1040] : Handle_INTEL_WIFI_AUTH_SUCCESS - g_cur_peer_mac: EA-F2-E2-02-1A-1E [L=7][M=WFDDNS][F=WFDDnS.cpp: 701]
...
07:44:05:030,[t:0x1040] : Handle_INTEL_WIFI_EVENT_CONNECTION_COMPLETE - INTEL_WIFI_EVENT_CONNECTION_COMPLETE received [L=5][M=WFDDNS][F=WFDDnS.cpp: 1186]
07:44:05:030,[t:0x1040] : Handle_INTEL_WIFI_EVENT_CONNECTION_COMPLETE - btSelectedDeviceMACAddress: EA-F2-E2-02-1A-1E [L=7][M=WFDDNS][F=WFDDnS.cpp: 1201]
07:44:05:030,[t:0x1040] : Handle_INTEL_WIFI_EVENT_CONNECTION_COMPLETE - g_cur_peer_mac: EA-F2-E2-02-1A-1E [L=7][M=WFDDNS][F=WFDDnS.cpp: 1202]
07:44:05:030,[t:0x1040] : Handle_INTEL_WIFI_EVENT_CONNECTION_COMPLETE - g_cur_peer_mac: EA-F2-E2-02-1A-1E [L=7][M=WFDDNS][F=WFDDnS.cpp: 1244]
07:44:05:030,[t:0x1040] : Handle_INTEL_WIFI_EVENT_CONNECTION_COMPLETE - Connection complete event received, result=0, g_bReconnectAfterInvite=0 [L=5][M=WFDDNS][F=WFDDnS.cpp: 1246]
07:44:05:030,[t:0x1040] : Handle_INTEL_WIFI_EVENT_CONNECTION_COMPLETE - Connection failed, reason code=4, see below key [L=3][M=WFDDNS][F=WFDDnS.cpp: 1271]
07:44:05:030,[t:0x1040] : ... eConnectionTimeout(4) ...
...
Notice the next-to-last byte of the MAC address differs. My thinking is that if the Intel WiDi application considers those response packets comes from a different device then it ignores them; if nothing else remains then it considers there's no response and the connection times-out. Is this normal?
Is there anything I can do to get this working (or give up and return the wifi card)?