Hello all. First I would like to thank the community here for having solved two problems so far with my recently purchased WD TV Media Player.
• Connecting to my Windows 10 Devices
• Audio in MKV files not playing
Now I have one other nagging problem I figured I would pick your brains with.
I have a Microsoft Lumia 950 XL. What’s more, it supports Miracast and also has Continuum. MS’s details of Continuum say that the Lumia 950 XL should connect to any display or system that supports Miracast and once connected, will activate Continuum onto the display.
(For those not familiar, Continuum makes it so your phone projects a Windows 10 Desktop Experience onto your TV or other Monitors and you can use a Keyboard/Mouse or the Phone as a touchscreen for working or playing on the TV/Monitor using Universal Apps. At the same time, you can still use your phone for other programs, making calls, receiving texts, etc.)
Now, I have attempted to connect my phone to the WD TV Media Player, it shows up, tries to connect, but then the connection fails due to a poor connection or something like that.
I have seen similar threads in here regarding the same issue with Miracast for such devices as tablets, Galaxy S5/6’s and other Android devices, but I have not yet seen a solid solution to the problem and some of the possible fixes seems constrained to Android.
For the record, my WD TV Media Player is not wired and is connected to the network using Wi-Fi.
I also attempted to update the firmware of the WDTVMP but it is apparently up to date (Last Firmware found was from 2014)
I have also attempted Auto Connect and Manual Connection with no luck.
Is there anybody in here who has attempted to connect either a Lumia 950 or Lumia 950 XL (Or perhaps another Lumia / Windows 10 Mobile Device) to the WDTVMP?
Is it even possible or are the devices simply too new… or is Continuum causing some sort of issue which the WDTVMP simply can’t handle?
I assume it is possible to fix, as I have heard some people with recent devices solving this problem, which is the same problem I am having, however they fixed it by adjusting whatever Android OS they were using (KitKat?) and something to do with sideloading or custom roms installed on their devices. (None of which applies to my situation)
Any help would be appreciated, thanks in advance.