BT keeps shutting off with new rom; anyone else?

[Sonny486]

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

[Sonny486]

Originally Posted by Sonny486

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

Has anyone had any luck with this setting? Mine stayed on all night with multiple power ups and downs.

-Sonny

[Big D5]

Update: Bluetooth never turned off but I did have some weird connection problems yesterday, I just got this bluetooth so I am not sure if it was the setup or operator error.

Looks like if I change the HKCU first all the other reg edits change as well, did another hard reset and set HKCU scan mode than checked the HKLM setting discussed above and HKLM /disable auto suspend was already set to 1. I flashed back and checked the HKLM l2 cap and it was set to 1 in the old AKU so I am trying that, but I think we are getting close here lets keep working on it.

[APOLAUF]

Originally Posted by Sonny486

If the key scanmode does not help try this one:

[HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\l2 cap]
"ScanModeControl"=dword:00000000

Every time I reboot, the value is reset to 1. Any way around this?

[ktwombley]

My mogul has both of these registry settings as default, so changing them might be a red herring. Not only that, but if I change either setting, it changes back on its own. The disableautosuspend changes back on soft reset, and the scanmode changes to 5 when the BT radio is on and 0 when it's off, all on its own.

[Big D5]

Originally Posted by ktwombley

My mogul has both of these registry settings as default, so changing them might be a red herring. Not only that, but if I change either setting, it changes back on its own. The disableautosuspend changes back on soft reset, and the scanmode changes to 5 when the BT radio is on and 0 when it's off, all on its own.

Agreed this is a red herring, I am still having the same or similar problems with these settings changed. I have been trying all day with no success, there has to be an answer but its not in the registry, at least not that I can find. I hope this gets solved soon because this is a deal breaker for me.

[myteematt]

Wasn't there also a terrible bluetooth stack on the PPC-6700 and XV6700 also? Same problems new phone... Sprint loves its customers. I also have tried both registry tweaks and they didnt work. I also agree its a driver issue or a radio issue. I read in another post that some people were using mixed roms and radios to improve this issue? Has anyone tried this succesfully?

[Sonny486]

Originally Posted by myteematt

Wasn't there also a terrible bluetooth stack on the PPC-6700 and XV6700 also? Same problems new phone... Sprint loves its customers. I also have tried both registry tweaks and they didnt work. I also agree its a driver issue or a radio issue. I read in another post that some people were using mixed roms and radios to improve this issue? Has anyone tried this succesfully?

I believe you are right, it must be a driver issue.

The HKCU\Software\Microsoft\Bluetooth\Settings\ScanMod e show up as follows:

5 Bluetooth on
0 Bluetooth off
7 Bluetooth in Discoverable mode.

I think this is a read key to show what the radio is doing.

I am going to try a different Radio Rom to see what happens.

-Sonny

[dtndvm]

Originally Posted by ktwombley

My mogul has both of these registry settings as default, so changing them might be a red herring. Not only that, but if I change either setting, it changes back on its own. The disableautosuspend changes back on soft reset, and the scanmode changes to 5 when the BT radio is on and 0 when it's off, all on its own.

I wonder if there may be some other setting controlling disableautosuspend. I have changed the disableautosuspend and it has not changed back through numerous soft resets. I am still able to stay connected for long periods of time. However, like Big D5, I have had some strange connection issues. The voice speed dial will sometimes not function after the connection has been idle for some time. Overall, the disableautosuspend change has made BT functional on my device until the real answer can be found.

Info on the Bluetooth drivers can be found here:

http://msdn2.microsoft.com/en-us/library/ms890583.aspx

When I look in windows, I don't see the BT drivers referenced but there are 3 BT_Init_Scripts that have the same date as the new ROM. I would be suspicious that this is HTC's tweaking of the BT. If anybody knows how to interpret these, it may shed some light on the issue. They look a lot like the coarse audio remap changes to improve sound output.

[Sonny486]

Just FYI to all: I am using no2chem Rom (alpha) and Radio 1.47. Made adjustment to l2cap ScanModeControl = 0, HKLM\System\CurrentControlSet\Control\Power\State\ Suspended - Default = 2.

Can someone do the same to check it out.

-Sonny