- Nov 28, 2013
- 7
- 0
- 0
I've had my Surface 2 since soon after launch. I had been pretty happy with it, especially with the standby battery life. However, around November 22nd, my battery life plummeted. Instead of charging every 5 days or so, I had to charge daily or every other day. I did some searching using cmd powercfg and I think the problem has been narrowed down. It looks like Microsoft's drivers for the Surface 2 are preventing the Surface 2 from entering the correct sleep state during connected standby, along with a Tegra driver that is also problematic. The worst thing is that the Microsoft driver issue (Microsoft UART V2 Driver) has been known since Window 8.1 Preview, and apparently the November updates unfixed it. The workaround for this is to turn on the bluetooth radio to reduce the battery consumption (counter-intuitive, right?). Unfortunately, when I went to turn on my Bluetooth, the menu option was missing (?!). Further investigation in the device manager revealed that the hardware was not recognizing the Bluetooth radio. So apparently the November updates that fixed some issues caused a lot of collateral damage. Evidence below:
Used cmd powercfg -battery report to check battery drain patterns. Connected standby battery life plummets after Nov. 22nd (also the first day when my sound drivers started acting up):

So I used cmd powercfg /sleepstudy to see what was going on during connected standby. Results show that during connected standby, the computer is being kept active, rather than using the proper sleep state:

Looking at the processes that were active, two drivers seem to be causing the issues: Microsoft UART V2 Driver and Tegra I2C Controller Driver:

Did some web searches for offending drivers. While not much info about the Tegra driver, the Microsoft driver had many discussions. Apparently, UART V2 is somehow connected to the Bluetooth ratio state. There is a known bug in the Windows RT 8.1 Preview that was causing high battery drain when the Bluetooth radio was off. Turning the Bluetooth radio on resolved the issue:

More info, with Microsoft acknowledging issue in Preview build:

It's a shame that an issue known in Preview wasn't fixed for general release, or was unfixed by the November update, but that seems to be the case. I decided to check my Bluetooth radio to see if turning it on would help. However, the PC and devices menu somehow lost the Bluetooth menu (should be between Display and Devices):

Web search reported that changes in desktop Bluetooth settings could remove menu option in modern settings... Going into the device manager to look for the Bluetooth settings, it turned out that Bluetooth was greyed out:

Checking the properties of the Bluetooth controller, is seems that my Surface 2 no longer has Bluetooth:

My next steps are to try refreshing my Surface 2 to see whether my Bluetooth will come back, and whether that will fix my connected standby power drains. Altogether, it is absolutely ridiculous that I'm having to go through this, just to have a product that functions as it is marketed. If Microsoft wants to sell products to general audiences, they cannot have software/hardware(?) issues that require so much poking around to fix. The apparent mantra of "Check for updates/refresh your Surface" by tech support really is not acceptable, when issues acknowledged more than four months ago are the underlying problems. Will post my observations after refreshing.
Used cmd powercfg -battery report to check battery drain patterns. Connected standby battery life plummets after Nov. 22nd (also the first day when my sound drivers started acting up):

So I used cmd powercfg /sleepstudy to see what was going on during connected standby. Results show that during connected standby, the computer is being kept active, rather than using the proper sleep state:

Looking at the processes that were active, two drivers seem to be causing the issues: Microsoft UART V2 Driver and Tegra I2C Controller Driver:

Did some web searches for offending drivers. While not much info about the Tegra driver, the Microsoft driver had many discussions. Apparently, UART V2 is somehow connected to the Bluetooth ratio state. There is a known bug in the Windows RT 8.1 Preview that was causing high battery drain when the Bluetooth radio was off. Turning the Bluetooth radio on resolved the issue:

More info, with Microsoft acknowledging issue in Preview build:

It's a shame that an issue known in Preview wasn't fixed for general release, or was unfixed by the November update, but that seems to be the case. I decided to check my Bluetooth radio to see if turning it on would help. However, the PC and devices menu somehow lost the Bluetooth menu (should be between Display and Devices):

Web search reported that changes in desktop Bluetooth settings could remove menu option in modern settings... Going into the device manager to look for the Bluetooth settings, it turned out that Bluetooth was greyed out:

Checking the properties of the Bluetooth controller, is seems that my Surface 2 no longer has Bluetooth:

My next steps are to try refreshing my Surface 2 to see whether my Bluetooth will come back, and whether that will fix my connected standby power drains. Altogether, it is absolutely ridiculous that I'm having to go through this, just to have a product that functions as it is marketed. If Microsoft wants to sell products to general audiences, they cannot have software/hardware(?) issues that require so much poking around to fix. The apparent mantra of "Check for updates/refresh your Surface" by tech support really is not acceptable, when issues acknowledged more than four months ago are the underlying problems. Will post my observations after refreshing.