Wireless Display Adapters (Miracast)

Search This thread

narcopolypse

Senior Member
Jan 7, 2009
88
61
West Jordan, UT
With all of the confusion regarding Miracast adapters (especially the Netgear PTV3000) I thought I'd try to point people in the right direction.
First thing's first, the Netgear PTV3000 does NOT work. It is not certified and has absolutely no connectivity out of the box. It can be flashed
with an experimental firmware to gain crappy functionality but will not work properly until an official update is released.


Edit: The Netgear PTV3000 IS now certified and works great! It's also cheaper than most and is the only stand alone Miracast adapter that can be purchased at Best Buy (or any other offline store for that matter).

So rather than waste your money on a Netgear adapter (like I did) you could buy yourself an Actiontec ScreenBeam which I have confirmed
not only works with the N4 but works great! And if you're not a big fan of Actiontec devices, here is a direct link to the Wi-Fi Alliances list of

Official Miracast Certified Recievers

which are certified (imagine that) to work with the Nexus 4.
Happy screen beaming :laugh:
 
Last edited:

irishtexmex

Senior Member
Sep 27, 2010
399
56
Austin, TX
Not that I don't believe you, but who/how did you confirm the ActionTec works?

I'm looking for some anecdotal reviews and opinions of it. Thanks.
 

plasticdarlow

Senior Member
Aug 31, 2010
400
65
With all of the confusion regarding Miracast adapters (especially the Netgear PTV3000) I thought I'd try to point people in the right direction.
First thing's first, the Netgear PTV3000 does NOT work. It is not certified and has absolutely no connectivity out of the box. It can be flashed
with an experimental firmware to gain crappy functionality but will not work properly until an official update is released.
So rather than waste your money on a Netgear adapter (like I did) you could buy yourself an Actiontec ScreenBeam which I have confirmed
not only works with the N4 but works great! And if you're not a big fan of Actiontec devices, here is a direct link to the Wi-Fi Alliances list of

Official Miracast Certified Recievers

which are certified (imagine that) to work with the Nexus 4.
Happy screen beaming :laugh:

Where did you buy it?

Sent from my Galaxy Nexus using Tapatalk 2
 

ericshmerick

Senior Member
Apr 7, 2006
1,496
273

rican408

Senior Member
Jun 25, 2010
399
39
Please post a YouTube video!

---------- Post added at 04:32 AM ---------- Previous post was at 04:30 AM ----------

Never mind I found one and it looks like the same adapter from far away....
https://www.youtube.com/watch?v=qjtSzfNVq5E&feature=youtube_gdata_player

---------- Post added at 04:52 AM ---------- Previous post was at 04:32 AM ----------

Aaaand furthermore if you can wait they are sitting in best buy stores according to their website...
http://m.bestbuy.com/m/e/product/detail.jsp?skuId=3179075&pid=1218382979736
 

narcopolypse

Senior Member
Jan 7, 2009
88
61
West Jordan, UT
First link on Google:

http://www.amazon.com/ACTIONTEC-SBWD100KIT01-ScreenBeam-Universal-Wireless/dp/B009Z8T3K6

Looks like it's not out yet. So the OP is either 1. speculating based on the certification (from just 9 days ago). Or 2. Has some sort of inside connection to get one before they have even gone up for sale.

Guessing it's 1.
Or 3, they have been up for sale on Amazon for a week now but are currently sold out. (seems par for the course with anything related to the N4) Fortunately a friend of mine got one before they sold out. Tested and confirmed working with his Nexus 4.
And FYI this also comes with a little USB dongle that you can plug into any computer to make it Miracast enabled. We tried it with an AMD computer running a Nvidia GPU and it works great!

Where did you buy it?

Sent from my Galaxy Nexus using Tapatalk 2

Amazon
 

sempersi

Member
Jun 30, 2012
14
5
Nothing in the UK though :(

Sent from my Nexus 4 using xda app-developers app
 
Last edited:

clubtech

Senior Member
Jun 26, 2007
1,908
353
USA
I received my Actiontec adapter yesterday (bought through Amazon) and it does NOT work with both my nexus 4 devices.
It will try to pair and will fail after 20sec.
One N4 is unlocked and rooted running stock. The other N4 is not rooted and not unlocked fully stock with nothing installed on it.
Both will NOT connect with this adapter.

If anyone was able to get this to work please specify how you did it.
Both my N4's can connect to the Netgear PTV3000 with the beta firmware that was floating around.

Also, the Actiontec comes with a USB dongle that you can use on any PC to mirror its screen. Even that will only connect to the adapter two times in 20 tries...the rest will simply time out.
 

narcopolypse

Senior Member
Jan 7, 2009
88
61
West Jordan, UT
2 things (doubt you can help with the 2nd, but who knows).

1. when you use the USB dongle on the PC, does it mirror the laptop display, or can you configure it as a second screen?
2. Have you tested it with a Galaxy S3 (miracast certified)?

1. Didn't try but it did show up as an additional video card in device manager so I assume you could use it as a second screen.
Also, the Miracast standard (and pre release demos) say it should.
2. I couldn't get it to work but that doesn't surprise me.

I received my Actiontec adapter yesterday (bought through Amazon) and it does NOT work with both my nexus 4 devices.
It will try to pair and will fail after 20sec.
One N4 is unlocked and rooted running stock. The other N4 is not rooted and not unlocked fully stock with nothing installed on it.
Both will NOT connect with this adapter.

If anyone was able to get this to work please specify how you did it.
Both my N4's can connect to the Netgear PTV3000 with the beta firmware that was floating around.

Also, the Actiontec comes with a USB dongle that you can use on any PC to mirror its screen. Even that will only connect to the adapter two times in 20 tries...the rest will simply time out.

It will not work on the Nexus 4 if it is rooted. As for not working with on your unrooted one, I don't know what to tell you. We got it to work. (after we figured out it has to be unrooted)
 
  • Like
Reactions: c4v3man

philipswich

Member
Sep 6, 2010
21
8
screenbeam

Or 3, they have been up for sale on Amazon for a week now but are currently sold out. (seems par for the course with anything related to the N4) Fortunately a friend of mine got one before they sold out. Tested and confirmed working with his Nexus 4.
And FYI this also comes with a little USB dongle that you can plug into any computer to make it Miracast enabled. We tried it with an AMD computer running a Nvidia GPU and it works great!



Amazon

Could you do a video for me please? I'm really interested as to how miracast is implemented with the Nexus 4... does it just mirror everything on your screen no matter what app youre using, does it continue working when you turn the screen on the phone off, whats the latency like?

Really interested,

Thanks
 

clubtech

Senior Member
Jun 26, 2007
1,908
353
USA
1. Didn't try but it did show up as an additional video card in device manager so I assume you could use it as a second screen.
Also, the Miracast standard (and pre release demos) say it should.
2. I couldn't get it to work but that doesn't surprise me.



It will not work on the Nexus 4 if it is rooted. As for not working with on your unrooted one, I don't know what to tell you. We got it to work. (after we figured out it has to be unrooted)

That is not accurate. I don't think it has anyhting to do with being rooted or not.
I contacted Actiontec and they responded saying that the shipping firmware will not work with the N4 and that they are working on a beta firmware that will fix the problem.
Since you got it to work, what firmware version is your adapter running?
 

texasice

Retired Recognized Developer
Oct 27, 2009
603
3,434
Austin
I got mine today (Actiontec ScreenBeem SBWD100A v1.0.21). It does not work out of the box. (for me anyway)

Logcat is saying something about hdcp failing. apparently qseecom is looking in the wrong directory so i copied the discretix files from /vendor/firmware/discretix to /system/etc/firmware/ but it still wouldnt connect. Interestingly i can connect to it as a wifi-direct device it then disconnects saying the app wasnt found (on the tv). so after that i tried reconnecting the wfd, it connects but looks like hdcp still has issues and actually locks up the device every time. Anyway thats my story.

log snipped
Code:
I/ActivityManager(  544): Displayed com.android.settings/.Settings$WifiDisplaySettingsActivity: +527ms
W/System.err( 1987): Removed 2131231194
W/System.err( 1987): Removed 2131231203
D/overlay (  163): FROM_STATE = OV_BYPASS_3_LAYER TO_STATE = OV_CLOSED
I/wpa_supplicant(  699): p2p0: P2P-DEVICE-FOUND 10:9f:a9:dc:a1:62 p2p_dev_addr=10:9f:a9:dc:a1:62 pri_dev_type=8-0050F204-5 name='SBWD-DCA162' config_methods=0x88 dev_capab=0x25 group_capab=0xa wfd_dev_info=0x0000060051022a012c
D/overlay (  163): FROM_STATE = OV_CLOSED TO_STATE = OV_BYPASS_3_LAYER
I/wpa_supplicant(  699): p2p0: P2P-FIND-STOPPED 
I/WifiDisplayController(  544): Connecting to Wifi display: SBWD-DCA162
I/wpa_supplicant(  699): p2p0: P2P-INVITATION-RESULT status=0 
I/WifiDisplayController(  544): Initiated connection to Wifi display: SBWD-DCA162
E/wpa_supplicant(  699): Using interface p2p0 with hwaddr ea:92:a4:93:6a:82 and ssid "DIRECT-Am-Android_5132"
W/wpa_supplicant(  699): Device is trying to offload WPS Probe Response while not supporting this
W/wpa_supplicant(  699): Device is trying to offload P2P Probe Response while not supporting this
I/wpa_supplicant(  699): p2p0: CTRL-EVENT-CONNECTED - Connection to ea:92:a4:93:6a:82 completed (auth) [id=1 id_str=]
I/wpa_supplicant(  699): p2p0: P2P-GROUP-STARTED p2p0 GO ssid="DIRECT-Am-Android_5132" freq=2462 passphrase="GM1GC0rd" go_dev_addr=ea:92:a4:93:6a:82 [PERSISTENT]
D/CommandListener(  160): Setting iface cfg
D/CommandListener(  160): Trying to bring up p2p0
D/TetherController(  160): Starting tethering services
D/TetherController(  160): Tethering services running
D/WifiP2pService(  544): Started Dhcp server on p2p0
I/dnsmasq ( 2012): started, version 2.51 cachesize 150
I/dnsmasq ( 2012): compile time options: no-IPv6 GNU-getopt no-DBus no-I18N DHCP no-scripts no-TFTP
W/dnsmasq ( 2012): warning: no upstream servers configured
I/dnsmasq ( 2012): DHCP, IP range 192.168.49.2 -- 192.168.49.254, lease time 1h
I/dnsmasq ( 2012): read /etc/hosts - 1 addresses
D/overlay (  163): FROM_STATE = OV_BYPASS_3_LAYER TO_STATE = OV_CLOSED
W/ThrottleService(  544): unable to find stats for iface rmnet_usb0
D/alsa_ucm(  166): snd_use_case_set(): uc_mgr 0x40bf82a0 identifier _verb value Inactive
D/alsa_ucm(  166): Set mixer controls for HiFi Lowlatency enable 0
D/alsa_ucm(  166): snd_use_case_set(): uc_mgr 0x40bf82a0 identifier _disdev value Speaker
D/alsa_ucm(  166): Set mixer controls for Speaker enable 0
W/wpa_supplicant(  699): Device is trying to offload WPS Probe Response while not supporting this
W/wpa_supplicant(  699): Device is trying to offload P2P Probe Response while not supporting this
I/wpa_supplicant(  699): p2p0: AP-STA-CONNECTED 10:9f:a9:dc:a1:62 p2p_dev_addr=10:9f:a9:dc:a1:62
I/wpa_supplicant(  698): Could not set station 10:9f:a9:dc:a1:62 flags for kernel driver (errno=11).
I/WifiDisplayController(  544): Connected to Wifi display: SBWD-DCA162
E/MonoPipe(  166): Failed to fetch local time frequency when constructing a MonoPipe (res = -32).  getNextWriteTimestamp calls will be non-functional
I/AudioFlinger(  166): HAL output buffer size 1024 frames, normal mix buffer size 1024 frames
I/AudioMixer(  166): found effect "Multichannel Downmix To Stereo" from The Android Open Source Project
I/AudioFlinger(  166): HAL output buffer size 1024 frames, normal mix buffer size 1024 frames
I/AudioMixer(  166): found effect "Multichannel Downmix To Stereo" from The Android Open Source Project
I/WifiDisplayController(  544): Listening for RTSP connection on 192.168.49.1:7236 from Wifi display: SBWD-DCA162
D/ALSAStreamOps(  166): setParameters(): keyRouting with device 0x0
D/ALSAStreamOps(  166): setParameters(): keyRouting with device 0x0
I/AudioFlinger(  166): AudioFlinger's thread 0x40daf008 ready to run
I/AudioFlinger(  166): AudioFlinger's thread 0x41125008 ready to run
I/r_submix(  166): out_standby()
D/ALSAStreamOps(  166): setParameters(): keyRouting with device 0x0
I/dnsmasq ( 2012): DHCPDISCOVER(p2p0) 10:9f:a9:dc:a1:62 
I/dnsmasq ( 2012): DHCPOFFER(p2p0) 192.168.49.75 10:9f:a9:dc:a1:62 
I/dnsmasq ( 2012): DHCPREQUEST(p2p0) 192.168.49.75 10:9f:a9:dc:a1:62 
I/dnsmasq ( 2012): DHCPACK(p2p0) 192.168.49.75 10:9f:a9:dc:a1:62 
I/NetworkSession(  166): incoming connection from 192.168.49.75:44435 (socket 35)
I/NetworkSession(  166): added clientSession 2
I/WifiDisplaySource(  166): We now have a client (2) connected.
I/WifiDisplaySource(  166): Using AAC audio.
I/WifiDisplaySource(  166): Initiating HDCP negotiation w/ host 192.168.49.75:25030
D/QSEECOMAPI: (  166): QSEECom_start_app sb_length = 0x480
D/QSEECOMAPI: (  166): App is not loaded in QSEE
W/WifiDisplaySource(  166): Response handler for session 2, cseq 3 returned err -1010 (Unknown error 1010)
I/WifiDisplayController(  544): Lost RTSP connection with Wifi display due to error 1: SBWD-DCA162
I/WifiDisplayController(  544): Wifi display connection failed!
D/QSEECOMAPI: (  166): Loaded image: APP id = 1
D/DxHDCP  (  166): AKE_SEND_CERT received
D/DxHDCP  (  166): AKE_RECEIVER_INFO received
D/DxHDCP  (  166): AKE_SEND_RRX received
D/DxHDCP  (  166): AKE_SEND_H_PRIME received
D/DxHDCP  (  166): AKE_PAIRING_INFO received
D/DxHDCP  (  166): LC_L_PRIME received
D/DxHDCP  (  166): REPEATERAUTH_SEND_RECEIVERID_LIST received
I/DxHDCPModule(  166): Got callback from DX: 7, 0x43b24874, 0x0
I/DxHDCPModule(  166): Got callback from DX: 9, 0x43b24ea8, 0x0
I/WifiDisplaySource(  166): Saw HDCP notification code 8, ext1 1135759016, ext2 0
E/WifiDisplaySource(  166): HDCP failure, shutting down.
I/WifiDisplayController(  544): Lost RTSP connection with Wifi display due to error 1: SBWD-DCA162
I/WifiDisplayController(  544): Wifi display connection failed!
D/overlay (  163): FROM_STATE = OV_CLOSED TO_STATE = OV_BYPASS_3_LAYER
I/WifiDisplaySource(  166): Initiating HDCP shutdown.
I/WifiDisplayController(  544): Retrying Wifi display connection.  Retries left: 2
I/WifiDisplayController(  544): Stopped listening for RTSP connection on 192.168.49.1:7236 from Wifi display: SBWD-DCA162
D/overlay (  163): FROM_STATE = OV_BYPASS_3_LAYER TO_STATE = OV_CLOSED
I/wpa_supplicant(  699): p2p0: AP-STA-DISCONNECTED 10:9f:a9:dc:a1:62 p2p_dev_addr=10:9f:a9:dc:a1:62
W/wpa_supplicant(  699): Device is trying to offload WPS Probe Response while not supporting this
W/wpa_supplicant(  699): Device is trying to offload P2P Probe Response while not supporting this
I/wpa_supplicant(  699): p2p0: P2P-GROUP-REMOVED p2p0 GO reason=REQUESTED
D/WifiP2pService(  544): Client list empty, remove non-persistent p2p group
D/TetherController(  160): Stopping tethering services
I/dnsmasq ( 2012): exiting on receipt of SIGTERM
D/TetherController(  160): Tethering services stopped
D/WifiP2pService(  544): Stopped Dhcp server
D/CommandListener(  160): Clearing all IP addresses on p2p0
D/NetUtils(  544): android_net_utils_resetConnections in env=0x72438730 clazz=0x33d00001 iface=p2p0 mask=0x3
I/wpa_supplicant(  699): wpa_s->ifname p2p0 cmd SET p2p_group_idle 0
I/wpa_supplicant(  699): p2p0: P2P-DEVICE-LOST p2p_dev_addr=10:9f:a9:dc:a1:62
D/overlay (  163): FROM_STATE = OV_CLOSED TO_STATE = OV_BYPASS_3_LAYER
D/overlay (  163): FROM_STATE = OV_BYPASS_3_LAYER TO_STATE = OV_CLOSED
D/overlay (  163): FROM_STATE = OV_CLOSED TO_STATE = OV_BYPASS_3_LAYER
D/overlay (  163): FROM_STATE = OV_BYPASS_3_LAYER TO_STATE = OV_CLOSED
D/overlay (  163): FROM_STATE = OV_CLOSED TO_STATE = OV_BYPASS_3_LAYER
I/EventLogService(  984): Aggregate from 1355272073669 (log), 1355271525913 (data)
D/dalvikvm(  984): GC_CONCURRENT freed 232K, 3% free 9401K/9660K, paused 3ms+3ms, total 22ms
I/ServiceDumpSys(  984): dumping service [account]
D/overlay (  163): FROM_STATE = OV_BYPASS_3_LAYER TO_STATE = OV_CLOSED
D/overlay (  163): FROM_STATE = OV_CLOSED TO_STATE = OV_BYPASS_3_LAYER
D/overlay (  163): FROM_STATE = OV_BYPASS_3_LAYER TO_STATE = OV_CLOSED
D/overlay (  163): FROM_STATE = OV_CLOSED TO_STATE = OV_BYPASS_3_LAYER
D/dalvikvm( 1987): GC_CONCURRENT freed 131K, 2% free 9378K/9536K, paused 3ms+3ms, total 20ms
D/overlay (  163): FROM_STATE = OV_BYPASS_3_LAYER TO_STATE = OV_CLOSED
W/AudioTrack(  544): obtainBuffer timed out (is the CPU pegged?) 0x731d2b48 name=0x2user=00002000, server=00000000
D/overlay (  163): FROM_STATE = OV_CLOSED TO_STATE = OV_BYPASS_3_LAYER
W/AudioTrack(  544): obtainBuffer timed out (is the CPU pegged?) 0x731d2b48 name=0x2user=00002000, server=00000000
D/overlay (  163): FROM_STATE = OV_BYPASS_3_LAYER TO_STATE = OV_CLOSED
W/AudioTrack(  544): obtainBuffer timed out (is the CPU pegged?) 0x731d2b48 name=0x2user=00002000, server=00000000

EDIT:
so after reflashing the factory image and relocking the bootloader it is still failing on hdcp
Code:
I/WifiDisplaySource(  164): Initiating HDCP negotiation w/ host 192.168.49.75:25030
W/WifiDisplaySource(  164): Response handler for session 2, cseq 3 returned err -1010 (Unknown error 1010)
I/WifiDisplayController(  595): Lost RTSP connection with Wifi display due to error 1: SBWD-DCA162
D/QSEECOMAPI: (  164): QSEECom_start_app sb_length = 0x480
D/QSEECOMAPI: (  164): App is not loaded in QSEE
E/QSEECOMAPI: (  164): Error::Cannot open the file /system/etc/firmware/dxhdcp2.mdt
E/QSEECOMAPI: (  164): Error::Loading image failed with ret = -1
D/QSEECOMAPI: (  164): QSEECom_start_app sb_length = 0x480
I/WifiDisplayController(  595): Wifi display connection failed!
D/QSEECOMAPI: (  164): App is not loaded in QSEE
D/QSEECOMAPI: (  164): Loaded image: APP id = 1
D/DxHDCP  (  164): AKE_SEND_CERT received
D/DxHDCP  (  164): AKE_RECEIVER_INFO received
D/DxHDCP  (  164): AKE_SEND_RRX received
D/DxHDCP  (  164): AKE_SEND_H_PRIME received
D/DxHDCP  (  164): AKE_PAIRING_INFO received
D/DxHDCP  (  164): LC_L_PRIME received
D/DxHDCP  (  164): REPEATERAUTH_SEND_RECEIVERID_LIST received
I/DxHDCPModule(  164): Got callback from DX: 7, 0x43316874, 0x0
I/DxHDCPModule(  164): Got callback from DX: 9, 0x43316ea8, 0x0
I/WifiDisplaySource(  164): Saw HDCP notification code 8, ext1 1127313064, ext2 0
E/WifiDisplaySource(  164): HDCP failure, shutting down.
I/WifiDisplayController(  595): Lost RTSP connection with Wifi display due to error 1: SBWD-DCA162
I/WifiDisplayController(  595): Wifi display connection failed!
 
Last edited:

clubtech

Senior Member
Jun 26, 2007
1,908
353
USA
@texasice, it is interesting to see that you are running V1.0.24 while mine is running 1.0.21. Did you get yours from Amazon?
 

Top Liked Posts