|
||||
Quote:
|
|
||||
Quote:
Changed from 1 to 0.I really solved my BT diconnect problem,I'm very happy now. The "Scan Mode" change did not work for me at all. |
|
||||
Looks like ScanMode is set by the CommManger to set the mode of the radio.. If you go and turn off the BlueTooth and refresh the registry value it changes to 0. If you go and turn bluetooth back on, it sets back to 5.
Looks like DisableAutoSuspend is the trick. I am using nueRom version and it has the DisableAutoSuspend = 1 already in it. -Sonny |
|
||||
Here is an excerpt from MSDN:
DisableAutoSuspend - Determines whether or not suspend mode is enabled on the device. 1: AutoSuspend is disabled. If the Bluetooth device is currently connected the stack calls SystemIdleTimerReset periodically to ensure the device does not go to sleep. 0: AutoSuspend is not be disabled by the stack. |
|
||||
Curious how many of you are using default comm manager? I just removed mine to see if the scanmode changes when I turn Bluetooth on or off.
-Sonny |
|
||||
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 the key scanmode does not help try this one:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\l2 cap] "ScanModeControl"=dword:00000000 It worked on a E-TEN M600 which had the exact same problem. Let me know -Sonny |
|
|
|