Miracast: Laptop Sees TV but Cannot Connect

I've successfully connected my previous Miracast laptop to TV.
New Win10 laptop (HP-17 AK000) sees my TV over WiFi and shows "connecting."
TV and laptop natively support Miracast.
There is no TV adapter involved.
Laptop times out with a "couldn't connect" message.

Any troubleshooting tips will be appreciated. I'll consider making a
recommended 3rd party hardware purchase in order to successfully
connect. Thanks.

M. L. wrote:

I've successfully connected my previous Miracast laptop to TV.
New Win10 laptop (HP-17 AK000) sees my TV over WiFi and shows "connecting."
TV and laptop natively support Miracast.
There is no TV adapter involved.
Laptop times out with a "couldn't connect" message.

Any troubleshooting tips will be appreciated. I'll consider making a
recommended 3rd party hardware purchase in order to successfully
connect. Thanks.

Does your machine have Bluetooth ?

Perhaps you could try "pairing" first.

Also, make sure the TV is in miracast mode,
so it is prepared to do its part.

Since your laptop "sees" the Wifi, that suggests
the TV is showing an SSID as if it's a router. (It's
an Access Point as far as I know.) That would also
suggest you've successfully put it in Miracast mode,
as otherwise it might have to do "something else"
to stream content from a router.

To check for Bluetooth, you could look in Device Manager
(right-click start and check the menu for Device Manager).

If I had a Miracast TV, I could make pictures, but my
TV resources are "vacuum tubes" :-) My real TV is a
TV tuner card and computer monitors.

Another thing of note - Windows 10 supports Miracast
"Source" and Miracast "Sink". If you had two laptops,
you might try firing up a "Sink" role first, then attempt
to connect to it from the laptop running as Miracast "Source".
I don't think anyone here has tested that. Again, I've
only one Wifi device (my laptop), which limits the possibilities
on that score.

You can try this in an admin Command Prompt window.

netsh wlan show drivers # checks for ingredients

Wireless Display Supported: Yes
Graphics Driver: Yes
Wi-Fi Driver: Yes

Your machine is AMD perhaps, so this issue could differ a bit.

https://forums.tomsguide.com/threads...racast.140136/

"it is not only the wifi card that could be the issue, it could
also be the graphics card. Nvidia cut support for miracast over
a year ago, so any new drivers will not make it work. I rolled
mine back to 350.12

(http://www.nvidia.com/download/drive...px/83819/en-us)

and after that, miracast worked flawlessly"

Some mid-range video cards can handle the screen compression
step, without breaking a sweat. Without such support, the
CPU is going to take a hammering. A GTX 1050 for example,
has NVEnc (one block) which can compress H.264 at 300FPS.
AMD has, perhaps, VCE, but I don't know the names of the
sub-agents to look for.

dxdiag

(then save the report to file and skim read for details)

------------------
System Information
------------------
Miracast: Available, with HDCP

---------------
Display Devices
---------------
Miracast: Not Supported


*******

There was a discussion thread on 2/5/2019 about Miracast.
The TV wasn't Miracast capable, so that ended that. But
we had fun anyway.



http://al.howardknight.net/msgid.cgi...a%404ax.com%3E

*******

Microsoft makes a dongle, that plugs into the TV.

Microsoft Wireless Display Adapter

https://www.microsoft.com/accessorie...kit-highlights

One end is USB (for power), the other end is "HDMI out" to the TV.

But that's not going to help, unless the laptop
is actually ready to do Miracast. That replaces the TV
response, with a dongle response. The TV can be in an
"ordinary" mode when using one of those.

Paul

On 2/26/2019 2:48 AM, Paul wrote:
M. L. wrote:

I've successfully connected my previous Miracast laptop to TV.
New Win10 laptop (HP-17 AK000) sees my TV over WiFi and shows
"connecting."
TV and laptop natively support Miracast.
There is no TV adapter involved.
Laptop times out with a "couldn't connect" message.

Any troubleshooting tips will be appreciated. I'll consider making a
recommended 3rd party hardware purchase in order to successfully
connect. Thanks.

Does your machine have Bluetooth ?

Perhaps you could try "pairing" first.

Also, make sure the TV is in miracast mode,
so it is prepared to do its part.

Since your laptop "sees" the Wifi, that suggests
the TV is showing an SSID as if it's a router. (It's
an Access Point as far as I know.) That would also
suggest you've successfully put it in Miracast mode,
as otherwise it might have to do "something else"
to stream content from a router.

To check for Bluetooth, you could look in Device Manager
(right-click start and check the menu for Device Manager).

If I had a Miracast TV, I could make pictures, but my
TV resources are "vacuum tubes" :-) My real TV is a
TV tuner card and computer monitors.

Another thing of note - Windows 10 supports Miracast
"Source" and Miracast "Sink". If you had two laptops,
you might try firing up a "Sink" role first, then attempt
to connect to it from the laptop running as Miracast "Source".
I don't think anyone here has tested that. Again, I've
only one Wifi device (my laptop), which limits the possibilities
on that score.

You can try this in an admin Command Prompt window.

Â*Â* netsh wlan show driversÂ*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* # checks for ingredients

Â*Â*Â*Â*Â* Wireless Display Supported: Yes
Â*Â*Â*Â*Â* Graphics Driver: Yes
Â*Â*Â*Â*Â* Wi-Fi Driver: Yes

Your machine is AMD perhaps, so this issue could differ a bit.

https://forums.tomsguide.com/threads...racast.140136/

Â*Â* "it is not only the wifi card that could be the issue, it could
Â*Â*Â* also be the graphics card. Nvidia cut support for miracast over
Â*Â*Â* a year ago, so any new drivers will not make it work. I rolled
Â*Â*Â* mine back to 350.12

Â*Â*Â* (http://www.nvidia.com/download/drive...px/83819/en-us)

Â*Â*Â* and after that, miracast worked flawlessly"

Some mid-range video cards can handle the screen compression
step, without breaking a sweat. Without such support, the
CPU is going to take a hammering. A GTX 1050 for example,
has NVEnc (one block) which can compress H.264 at 300FPS.
AMD has, perhaps, VCE, but I don't know the names of the
sub-agents to look for.

Â*Â* dxdiag

Â*Â* (then save the report to file and skim read for details)

Â*Â*Â*Â*Â* ------------------
Â*Â*Â*Â*Â* System Information
Â*Â*Â*Â*Â* ------------------
Â*Â*Â*Â*Â* Miracast: Available, with HDCP

Â*Â*Â*Â*Â* ---------------
Â*Â*Â*Â*Â* Display Devices
Â*Â*Â*Â*Â* ---------------
Â*Â*Â*Â*Â* Miracast: Not Supported


*******

There was a discussion thread on 2/5/2019 about Miracast.
The TV wasn't Miracast capable, so that ended that. But
we had fun anyway.



http://al.howardknight.net/msgid.cgi...a%404ax.com%3E


*******

Microsoft makes a dongle, that plugs into the TV.

Microsoft Wireless Display Adapter

https://www.microsoft.com/accessorie...kit-highlights


One end is USB (for power), the other end is "HDMI out" to the TV.

But that's not going to help, unless the laptop
is actually ready to do Miracast. That replaces the TV
response, with a dongle response. The TV can be in an
"ordinary" mode when using one of those.

Â*Â* Paul
I have a Samsung Smart TV and an HP HP 15-ay068nr that is about 3 years old.

As I understand it there are three ways to connect to the TV, one
through the your LAN, one by Bluetooth, and the other a direct
projection to the TV

Like you I have had some problems connecting to the TV, but to
accomplish the task, I deleted the TV connection from Windows 10,
Settings-Devices-Bluetooth and other devices.

I rebooted the computer and every thing worked. I don't remember if I
deleted them from the TV, so you may wish to try as part of the resolution.

While I have routinely used the Connect to the TV and projected the
screen to the TV, I don't believe the TV can be used as a second monitor
through the LAN (at least I have not found it)

Connect: Message Center Square Icon on right end of Tool bar. If it is
not there go to Settings-Notifications&Actions and select the things
you want to see in the Message Center





--
2018: The year we learn to play the great game of Euchre