N10 can't see Miracast display - Nexus 10 Q&A, Help & Troubleshooting

I've got a Miracast-enabled Android TV Box (JUSTOP Android 4.0 TV Box HD), but my N10 can't see the remote display (I've enabled wireless display and searched for displays but it doesn't show up). The Android/Miracast box seems to have Miracast running fine, and is displaying a Device ID on the Miracast page.
Has anyone managed to connect the N10 to one of these devices using Miracast?
The Android TV box is connected to my network via ethernet - could this be the problem?

I've managed to get the Miracast receiver to see the N10 as a peer device. I clicked on the N10 in the list and sent an invitation to the N10 to connect. The invitation popped up on the N10 and I accepted it, but then....nothing. The N10 continued to report that there were no nearby wireless displays.
???

Related

[Q] Miracast and Netgear PTV3000

So after upgrading my N7 to 4.2 this morning, I stopped over at Best Buy to pick up their last Netgear PTV3000.
Unfortunately, I'm not able to get it to work but it could also be that I just don't know how to use Miracast on N7. Should the device just show up as another SSID?
Anyone have a suggestion?
Thanks,
Joey
jb0352 said:
So after upgrading my N7 to 4.2 this morning, I stopped over at Best Buy to pick up their last Netgear PTV3000.
Unfortunately, I'm not able to get it to work but it could also be that I just don't know how to use Miracast on N7. Should the device just show up as another SSID?
Anyone have a suggestion?
Thanks,
Joey
Click to expand...
Click to collapse
Which app are you trying to "miracast" ?
The new Youtube has a "Pair with youtube TV" option. Perhaps you can try that ?
Swedish_Steel said:
Which app are you trying to "miracast" ?
The new Youtube has a "Pair with youtube TV" option. Perhaps you can try that ?
Click to expand...
Click to collapse
I actually found a few threads discussing how the miracast is still not there on the Nexus 7. Will just have to wait.
And it should be an exact mirror, not just certain apps
Now for the Bad News
Called Google support about Nexus 7, Miracast, PTV3000 problem. Level 1 didn't know about the feature. Level 2 couldn't figure out why the feature was not on my tablet. Level 3 said the feature is on the Nexus 4 - not quite ready for the Nexus 10 - and NEVER going to be on the Nexus 7. The main reason I bought this tab was for this feature ( I have poor eyesight ). Thanks for nothing Google! How about reimbursing me for the Tablet and Netgear adapter I bought because of your false advertising!
It doesn't seem to work on Nexus 4 either. N4 sees the adapter, but when I tap to connect, says "connecting" and never connects. Sigh Documentation of PTV3000 which is quite scarse says
*PTV3000 supports pre-standard compliant Miracastâ„¢ wireless enabled display devices.
Click to expand...
Click to collapse
which to me pretty much means 60 bucks spent for nothing..
leobg said:
It doesn't seem to work on Nexus 4 either. N4 sees the adapter, but when I tap to connect, says "connecting" and never connects. Sigh Documentation of PTV3000 which is quite scarse says
which to me pretty much means 60 bucks spent for nothing..
Click to expand...
Click to collapse
Only the Nexus 4 is Miracast certified. The PTV3000 is not.
The PTV3000 doesn't work either with the Xperia T or V, even though Sony's product blog recommends it as Miracast dongle
The download has finally been posted! Firmware 2.1.5. Here is the link: http://support.netgear.com/product/PTV300
It seems that this is the same 2.1.5 that had the Miracast HDCP Authentication issue before. WiDi doesn't work either. You also have to switch between Miracast and WiDi. FAIL. Really disappointed with this. They even gave a big presentation at CES about how they are coming out with an update very soon. Way to go Netgear.
NEXUS4 :
PTV3000 miracast now works with the NEXUS 4, you just have to upgrade the PTV3000 firmware to the latest 2.2.9. It's a little slow to initially connect (~2min) but once it does it runs perfectly.
The NEXUS 7 with PTV3000 2.2.9:
I''m getting the following using PTV3000 2.2.9 trying to connect to Nexus 7 4.2.1:
From N7 wifi --> "Wi-Fi Direct": Peer Devices "Push2TV xxxxxx" available, click on it and then it goes to invited and then quickly to connected.
Once my N7 shows connected (above) my TV screen goes from Ready for connection to Connecting to wireless display device.... but the TV screen never goes past the connecting message.
I opened a trouble ticket with NetGear regarding the PTV3000/Nexus7 issue above and this is what I'm dealing with:
Per NetGear tech:
"Regarding your concern, as off now PTV3000 doesn't support Miracast so, it will not work with Nexus 7. We apologize for the inconvenience."
I responded to him with:
1) According to your NetGear PTV3000 Installation Manual the PTV3000 does support Miracast:
"Miracast Wireless Display
Push2TV now supports Miracastâ„¢ Wireless Display. To switch between Intel WiDi
and Miracast modes, press the button on the side of the Push2TV for 2 seconds.
You can then launch the wireless display application on a Miracast-compatible
smartphone, tablet, or laptop, and connect."
2) I also have a Nexus 4 that supports Miracast and it connects to the PTV3000 (although slow connecting) once connect it runs without any issues.
I'll let you know what transpires with the NEXUS 7 and PTV3000.
Refluga any luck?
How did it turn out for you Regluga? I saw your thread on Netgear support forums too, but didn't see any update after your last response. Were you ever able to get it to work? I am loving my Nexus 7 and need ability to mirror the output to my TV (Netgear/Miracast or any other means). Looking forward to your reply.
Cheers Bro!
How do I change resolution to 1080p, on Nexus7?

LG LM640s TV and N4 WirelessDisplay

I recently bought the LG LM640s TV, which has a WiFi-Direct and Wireless Screenshare option. The N4 connects just fine, the TV shows a message saying "Android XYZ connected", but I can't get it to display my phones screen.
I'm on xylon #18, and besides the connection over wifi-direct, there's an option in "Settings -> Display ->" like this.
Tried checking "Skip HDCP negotiation", didn't work either. The TV received an update like a week ago, didn't help :/
As much as I love this phone, I sometimes get frustrated that the standards it's pushing aren't available or working as intended (wireless charging, wireless display), even with hardware from the same manufacturer.
Did anyone manage to get this working with a similar TV?
i got the 55LM670T and it doesnt work, but i checked it out and although on the tv it says wireless display, it does say miracast, which is what the N4 supports, so i dont think our tvs support the miracast standard
italia0101 said:
i got the 55LM670T and it doesnt work, but i checked it out and although on the tv it says wireless display, it does say miracast, which is what the N4 supports, so i dont think our tvs support the miracast standard
Click to expand...
Click to collapse
If it's not working with the N4 and/or miracast - what is it working with?

[ISSUE][LOLLIPOP][MIRACAST/CASTSCREEN] Fail to PIN pair with WiDi TV

Hi,
I experience problems with connecting to my Samsung T24B750 Smart TV via Intel WiDi (fully supported by Miracast so said...).
1. Nexus detects the device just fine.
2. Every attempt of connecting to device fails - TV generates PIN code, but no PIN popup shows on N4, just info that Nexus is connecting -> connected and using screen - which obviously isn't true.
2.1. Attempt of connecting using developer option WPS configuration - KEYPAD also fails - kaypad is shown, but PIN isn't being sent to TV (I guess).
TV gets the request of connection and generates PIN using any method chosen on phone.
I'm attaching my logcats - using default (PBC) WPS configuration method and 2nd using KEYPAD.
(I've tried with Jellybean and KitKat too with same results)
Maybe it's the TV? If anyone can read logcat with Cast screen data, then maybe you will know where the issue is.
Also you could help me out by providing me with a logcat of successful Miracast connection.

[Q] How to setup ADT-1 via OSD with no remote?

Hello,
I have ordered an ADT-1 from eBay and I have a question about initial setup. I have connected my ADT-1 to my TV via HDMI, the network connection via Ethernet, but I'm trying to figure out how to set up going through the on-screen menu.
On my TV screen, the first screen are language options - if it came with a remote, I would just press "OK" and I assume it would prompt me through everything. I have tried installing the "Android TV Remote Control", but it seems to install on my Galaxy Note 3, it detects the ADT-1 on the network, but then the app continuously crashes making the remote unusable.
I guess my question is how, or what do I need to go through the initial setup of the ADT-1 on my TV screen? Do I need to break out my Logitech remote from the basement and see if the ADT-1 is in its database? Or is there another way to set this up through the OSD?
Thanks in advance

Casting troubles

I got in on the $50 NP deals a little bit ago. It's been a neat little device aside from a couple issues. First, nothing can cast to it. Various phones, tablets try to connect then give up with a "Unable to connect to device" error. I have Chromecasts and they work flawlessly. I have done a factory reset or two without any improvement. Another oddity is that from my desktop computers, most of the time the device doesn't even get listed from the Chromecast icon (No cast devices found). One exception seems to be Youtube. There it shows the device, but still never sends anything to the Player.
The other issue I've had is that Netflix plays 1-5 seconds of a show before popping up it's aip-703. Netflix's web site gives a few suggestions, remove and readd account and the like, but that hasn't helped.
The only other thing I can think of is that the upgrade to Marshmallow might magically fix things, but I'm not holding out much hope. Any other suggestions?
I bet the casting problems you're getting are due to the NP's dodgy wi-fi connectivity. It's got compatibility issues with loads of different routers. I for example have a dual band router and since I moved the NP over to the router's 2.4GHz band, I have been able to cast without issues. And this sucks since I prefer it to connect to the 5GHz band for throughput and interference reasons. If you get any chance to try this with a different router you'll most likely see that those issues go away...
I was wondering that too, so I picked up an OTG cable and connected my Wii's ethernet adapter. Devices still aren't able to connect to the NP's casting receiver. So much for that...
In dealing with the Netflix thing, I decided to give their support a try. Surprisingly, they were very easy to deal with as far as tech support phone lines are. We tried a few things, but weren't able to settle on anything more than maybe it's the ISP's fault (Comcast). One interesting thing was they were able to pull up a demo movie that displays the current bitrate that you're getting. It was only pulling 1700kbps before getting the error. At other devices I get a similar rate, up to 3000kbps. I don't see how if Comcast were throttling Netflix connections, it should fail on any device rather than just this one (phones, tablets, computers, Chromecast, GoogleTV work just fine).
I've been able to cast on both NP I have without an issue. They were both running 5.1.1 and connected through 5Ghz wifi. I updated one to 6.0 and now I have the high brightness issue.
Both the casting and Netflix app got updated yesterday. Hopefully that will fix your problems
Casting no longer powers on TV via HDMI
Has anyone else experienced that casting no longer wakes up a powered-off TV?
Since I got my NP, starting to cast (with the TV off) would power on the TV and set it to the correct input (via HDMI commands sent from the Nexus Player). But, since yesterday (6.0 upgrade and new Cast Receiver - not sure which is to blame) this no longer happens. Is this now a configurable setting somewhere? I do observe that I can still use my TV remote's d-pad to control the Nexus Player, so believe HDMI-CEC is still active and configured correctly on the TV.
I loved this feature (prevented me from needing my TV remote!) and sad that it's now broken.

Categories

Resources