PTV3000 Firmware Version 2.4.19

Supported Intel Wireless Display platforms:

• Windows 7, Intel Wireless Display V3.1.29.0, Wifi driver V15.1.1
• Windows 7, Intel Wireless Display V3.5.41.0,  Wif driver V15.3.1
• Windows 8 (systems upgraded form Windows 7), Intel Wireless Display V3.5.41.0,  Wifi driver V15.3.50
• Windows 8 (with Win8 preinstalled),  Intel Wireless display, V3.5.41.0,  Wifi driver V15.5.7
• Windows 8 (with Win8 preinstalled),  Intel Wireless display, V4.0.18.0,  Wifi driver V15.6.1

Supported Miracast platforms:

• Samsung Galaxy S3 (Android 4.1.1 or above)
• Samsung Galaxy S4
• Samsung Galaxy Note II
• Samsung Galaxy Note 10.1
• LG Optimus G (Android 4.0.4 or above)
• Google Nexus 4 (Android 4.2.1)
• Sony Xperia (various models with Android 4.0.4 or above) 

Enhancements & Bug Fixes:

• Fixed EU power-save mode that device does not wake up after entering power-save mode.
• Updated the RTSP User Agent to ME29 so new Samsung phones will project at 1080p.
• Blurry text when projecting for Sony Mobile phones.
• AP mode does not turn on properly when in FW update mode.
• Prevent pushbutton from initiating p2p pairing if coming out of low power mode. It just wakes up now.
• [MS Windows Blue] UI gets stuck if PC left idle for too long – Only added watchdog to reboot the system if key any key applications die unexpectedly.
• [MS Windows Blue] PTV3000 is not responsive which leads to be disconnect.
• [Widi Gen4] Blank/black screen with mouse only.
• [Widi Gen3] Black screen during HDMI hot plug after WiDi connection is established.
• (Heavy WiFi Traffic) Lenovo x220, WiDi 3.0.13, 4.0.17 and v2.4.1(r14548) cannot connect.
• Added Miracast failed cases (not tested yet):
  • 6.1.2(P-SnUT operating as a Group Owner accepts a WFD Session with a Reference Source)
  • 6.1.3(P-SnUT starts a WFD Session with a Source that is operating as an Autonomous GO)."
• Keep the credential(s) even after changing any of the settings on web UI.
• [#481 r14862 & V2.4.14] PTV locks up when disconnecting Windows.blue session from laptop.
• NON-HDCP FW shows black screen when WiDi mirroring starts. This FW is for engineering verificaiton purposes only.
• Enable Miracast certificaiton, test case 6.1.17a.
• [Microsoft Windows.blue] Dongle is dead after prolonged use.
• Integrate QCA 3.2.1.127
  • SF 1157749: ar9374 Block Ack flood during Nexus 4 4.2.2 streaming
  • SF 1176921: ar9374 Inconsistency between probe response (20Mhz) and capability beaconed (20Mhz & 40Mhz)
  • SF 1190765: ar9374 fails to send invitation response.
  • MSFT IOT fixes (no single channel scan).
  • Other P2P mobile phone IOT fixes.B29".
• [#234, #335, #435, #436 Excessive frame repeats and skips, Excessive latency, and A/V sync.] Tested at Intel KPI lab and passed all Playback Quality, Latency, and A/V Sync tests for Speed and Quality modes.
• [Widi gen4] Connection drop within 4 hours. Deauth sent from NB. WiDi log and sniffer trace sent to Intel.
• [HTC new one] TV displays "WiFi connection closed" screen instead of mirroring. Changes for this have been in r14767.
• [Sony Xperia Z] Sony Odin 10.3.A.0.423 crashes supplicant on reconnect.
• Set L2SD off as default for all future releases.
• Fixed issue of Connecting icon animation stays on screen after WiDi connection.
• Fixed issue of PTV3000 outputs low resolution to Sharp LC-19DV24U.
• Fixed HMDI hot plug issue.
• Fixed no HDMI signal if no HDMI cable is plugged in upon power up.
• [Windows.blue] "Display correct error connect/disconnect messaging on PTV.
  To access additional debug capabilities, the following actions need to be taken:
  • For connection issues, add extra handling to rtspfailedgui.sh and disconnectedgui.sh
  • For HDCP, add the uboot variable DISPLAY_HDCP_STATUS=1. The scripts displayHdcpStatus.sh, connectinggui.sh and rtspfailedgui.sh
    also are modified.
  • For displaying packet drops, add the uboot variable DISPLAY_PKTDROP_SEQERRROR=1. The script displayPktDropSeqErrStatus.sh
    displays the UI."
• [Widi gen3] After entering wrong PIN, TV screen shows new PIN but WiDi app still displays "connecting" message.
• [Widi gen4] Failing to connect with BCM4352 (2 cases)… Note: Discovery issue is still open. Now tracked by #448.
• [AV quality] Excessive frame repeats and skips (possibly, needs KPI testing). Improved datapath such that it takes about 55ms less time to decode large WiDi I-frames in Quality mode.
• Blank or Black Screen.
• Cleaned up pushbutton disconnect so that it works properly for Legacy Widi laptop connections, as well as cleanly sends an RTSP TEARDOWN for Miracast devices.
• All settings are kept with FW update (except the device profile).
• All settings are erased when doing reset-to-factory default.
• Incorporate final string translations.
• New UI animation images without line below text.
• When pushing reset button in Settings mode, successfully reset to factory default settings.
• Connection time is too long.
• No Audio when switched to Low Delay Mode.
• No Video while 1366x768 streaming (Calpella Laptop).
• Fixed issue with incorrect UserAgent parsing for Samsung Galaxy S3. This enables all movie mode features properly for that phone.
• HDCP Authenication drops after connection.
• Black screen during HDMI hot plug after WiDi connection is established.
• Ensured UI goes to EDID resolution upon disconnect.
• Fixed issue with incorrect aspect ratio correction being applied after connection.
• UI animation enabled by default and without the respective user setting in web UI.
• The "Browse" button in web UI customized for all languages.
• Do not reset language to factory default language after user updates FW.

Firmware Update Procedure:

Step 1: Press and hold the button on the side of the Push2TV adapter for 7 seconds, to put your device into firmware update mode.

Step 2:Using the Download Link below, download and extract the new firmware to a convenient place such as your desktop.

Download Link: http://www.downloads.netgear.com/files/GDC/PTV3000/PTV3000_V2.4.19.zip

Step 3: Using the wireless network manager utility on your device, search for Push2TV wireless network name (SSID) and connect.

Step 4: Open a web browser on your device, and type http://192.168.3.1 into the URL bar of the browser.

Step 5: Follow the steps on the web page to upload the firmware ".sbin" file and complete the update.