Quote:
Originally Posted by landale
It does seem to make sense that change to DisableAutoSuspend would solve the bluetooth drop out issues. While it certainly doesn't get to the root of the problem which is related to what goes on with the Mogul when it goes into D3 suspend (sleep) with bluetooth enabled. Essentially this registry change prevents the Mogul from going into D3 suspend when it is currently connected to a bluetooth device thus avoiding the problem. In these situations the dpad would also keep working since its only in D3 suspend that the problem occurs. However if you don't have an active bluetooth connection this change will not stop the device from going into D3 suspend thus causing the dpad to stop working on resume. If we could figure out a way to force the device to only go into D2 suspend (standby) then this should also resolve the dpad issue although it might cause battery life to drop a bit since standby isn't as battery efficient as sleep.
|
If you note the MSDN documentation it refers to the Bluetooth Device connected to the Stack. I take that to mean the Bluetooth Radio itself, not the headset. This is just a guess.
-Sonny