Venue 8 Pro Wifi Failure Log

If you want even more battery life under Windows 10 you need to deactivate Onedrive, because, oh wonder oh wonder, the app is buggey in Windows10. You can see this with powercfg batterylife reports, the onedrive app always waking up the tablet every few mintues without any reason. Also make sure you uncheck the calendar, I think it's calendar because you cant uncheck mail, under settings which apps are allowed to run in background/standby. You see under powercfg stats the communications app which includes calendar and mail, it's both in the same app, is also bugged and triggeres cpu power state confusions too. And of course cortana, which you cant deactivate 100%, the process still idles with 1-3% cpu usage even if you set cortana to off, like I said, Windows10 is really really bad for tablets or devices with batteries in general.

System, Power & Sleep, uncheck "On battery power, stay connected to Wi-Fi while asleep". DV8P sleeps, pings stop, resume from sleep, ping resume.  Seems to be working. As stated, the solution on this thread solves the crashed driver issues for WiFi and Bluetooth.  Using the Wi-Fi off approach will likely extend battery life further.  Testing would be needed in order to completely validate the results and additional comments on this post.

First thing, using hibernate as a replacement on a tablet for connected standby is of course a very bad idea, because it reduce your MMCs lifespan dramatically. Also you dont need to reactivate it, because under Windows10, 81 also but Windows10 pushed the reboot times a bit even more, shutdown is mostly identically to hibernate, except for saving the session state of course.

Just wanted to say that I have a Windows10 device here which still has no HKLM\System\CurrentControlSet athihvs.dll IHVExtensions entries at all. How is the correct supposed way to do this update of the drivers? Because I think it's important if you do an "upgrade" in the setup of the Qualcomm setup or do a re-install. I think if you chose upgrade, it wont add the IHVExtensions to the registry at all.

Also just noticed dell had released an updated wifi/bt driver a few hours ago:

http://www.dell.com/support/home/us/en/04/Drivers/DriversDetails?driverId=Y3DWJ&fileId=3531893968&osCode=wt32a&productCode=dell-venue-8-pro&languageCode=en&categoryId=NI

Official fixes:

- The system in European can't connect to the Miracast receiver as WiFi-direct group owner in Autonomous GO mode.
- In particular usage by 3rd party application, the driver can't indicate RSSI info in monitor mode.

Version:

3.7.2.63705

Anyone yet tested if those fix the issues of this thread too?

I'm going to stay with the LG drivers for at least 1 month to confirm reliability for my workflow (still perfect), but if anyone tries the new Dell drivers, it would be interesting to see if it resolves the failure log issue, resume lockups, etc.

Very interesting indeed.  The version number is higher so it might, assuming that it is the version number that was the fix vs. the packaging.  Note that Dell has repackaged the drivers, whereas LG released separate packages for BT vs wifi.

Drivers from LG are still looking very, very good.  I have Wifi set to turn off during sleep and no crashed whatsoever.  I have also disabled apps running in the background.  The past 6 hours resulted in 2% drain (0.33% per hour).  I'll report back later with additional test results.

Last Friday I have installed the latest driver released be Dell. the same wifi dropout has occurred. So this driver does not fix the issue, at least not for me.

Firmware Recovery #001

Firmware Version: 0x31C87576

Recovery Start: 2016-04-10 11:20:53.959

Recovery Reason: Control Endpoint TX Hang

Information:

Control Endpoint (1): Credit = 0, Queue Depth = 18

  Last Credit Consummed: 2016-04-10 11:20:48.954

  Last Credit Returned: 2016-04-10 11:06:01.137

Recovery Finish: 2016-04-10 11:20:59.769

Recovery Status: ERROR (0xFFFFFFFF)

It's obvious you also need to remove athihvui from registry if you're on WIndows10 and have those in your registry.

That failure is with the latest Dell driver, it seems, instead of the LG driver. Maybe the underlying issue is still present in the Dell driver.

Why is it obvious?  Nobody doesn't have them installed and myself does have them installed and the test results between the two configs appear to have been comparable.  Do you have additional info on those libraries that you can share here?

Sadly I have to report, the "LG driver" is still unstable under Windows 8.1. No bluescreens though, but random drops of wifi and/or bluetooth suddenly have no connection anymore and you have to restart the driver.

That's unfortunate, are you getting the log file, too? On Win10 with A14 bios, LG drivers are still perfect here.