Dell Venue 8 Pro 5830 WiDi Miracast not working after BIOS A05 upgrade
Does anyone know how to roll back to previous BIOS? I upgraded to latest A05 BIOS on my Venue 8 Pro and WiDi/Miracast stop working. My Netgear WiDi Adapter is picked up and connected but the second monitor just gives a black blank screen. I tried Extended desktop, Duplicate and Second monitor only mode. No picture is showing up on the monitor/TV but sound is connected. I tried it on several HDMI monitors, TV and projectors. I borrowed my friends Venue 8 Pro with older A02 BIOS and it works fine.
Same issue here, Blekin miracast fails to connect after a05. It finds the miracast, and begins the connection then fails after a few seconds of "negotiation/handshake"
(on a04 it would connect, show the screen for maybe three seconds then disconnect.)
my Lattitude e7440 connect fine and works as expected.
Hi Jacksodj, I managed to resolve this myself and may be worth a try for you. The issue is with Intel TXEI drivers. I simply uninstalled it and WiDi works fine now. Also I realized my TV doesn't support lower res than 1080 so it only support extended mode (1080 on tv and 780 on V8P) but I set the TV as primary display and use a mouse. Duplication mode works fine on my 24 inch monitor where it can dump down res to 780. go to Dell support website and download the TXEI driver installer to give you option to uninstall. http://www.dell.com/support/home/us/en/04/Drivers/DriversDetails?driverId=76XFC&fileId=3298804060&osCode=WB32A&productCode=dell-venue-8-pro&languageCode=EN&categoryId=DD
and pull down the latest firmware version update. As of the posting of this message, that version is 2.4.49 and is 26 MB in size.
Once the download is complete, goto your PTV device and hold in the black button on the side for at least seven seconds. There will be a delay in any reaction on the TV screen. Don't push it twice or it will leave the firmware update mode.
Once the screen shows that it is in firmware update mode, go back to your Venue. Taking your index finger, slide in from the right side of the screen to bring up the Start menu. Click on the Settings button. In the bottom right corner of the screen, click on the wireless network icon (second row from bottom, upper left icon).
If you have successfully put the Netgear PTV device in firmware update mode, you will see its name listed as one of the networks available. Click on it. By default, as you connect, your default Internet browser will start and will connect to the webpage for the PTV. If not, open your browser and type in the address 192.168.3.1.
There will be an option on the left side of the screen to update the firmware. Click on it. Then click on the browse button to select the firmware upgrade file that you downloaded from the Netgear website. If you cannot find it, goto your browser's setting panel and find out where (in what drive and directory/folder) it puts the downloaded files, by default. Go back to the PTV tab that is asking for the downloaded file and point it to that directory. Then select the file and it will download it to the PTV device and begin the firmware update.
Once the firmware update is completed, the PTV device will reboot itself. The TV screen will show you when it is done booting.
You will now need to redefine the connection from the Venue to the PTV. On the Venue, slide your index finger in from the right side of the screen to bring up the Start menu. Click on Devices. Click on Project. If you see the Push2TV device, click on it. If not, click on the "Add a wireless display" link, colored in purple. If a search is done, the PTV will be listed. Select it and the connection will be reestablished.
So again, do not remove the A05 BIOS update for you Venue Pro. It works just fine. Instead, update the firmware on your PTV.
I'm currently typing these instructions to you, using my Venue Pro and the PTV device is connected to my 55" Samsung TV. It's all very easy to read and write this stuff on a big screen. However, the next screen is going to be 4K and a lot bigger. But that is for a different discussion.
jacksodj
1 Message
1238
0
Posted May 20th, 2014 08:00
Same issue here, Blekin miracast fails to connect after a05. It finds the miracast, and begins the connection then fails after a few seconds of "negotiation/handshake"
(on a04 it would connect, show the screen for maybe three seconds then disconnect.)
my Lattitude e7440 connect fine and works as expected.