It seemed your method solved my BT disconect problem for me so far,(5 hrs now,no disconnects)thanks a lot for the find.

Bluetooth now staying connected!
 

Made your reg change and so far so good. I had to restart Bluetooth 3 times in 15 minutes earlier today. Mogul was able to stay connected coming out of sleep mode and incoming text messages since the reg edit. Had to soft reset after the reg edit to see its effects. Thanks Big D5!!!!! I'll let you know if it continues to work. Bluetooth = Motorola H700

EDIT: Had to reestablish connection after BT device went into power saving mode but at least the Bluetooth did not shut itself off on Mogul. Reset the Scan Mode to 0 and made the change from Donatom3 in post above (HKLM/software/microsoft/bluetooth/sys/DisableAutoSuspend to 0 from 1) and Bluetooth has been connected for 2 hours with no problems! Thanks for the info.

2kmy477, what were your values for the two reg keys before and after your edits?

HKLM/software/microsoft/bluetooth/sys

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.

htc and sprint should hire some people off of these boards, cause not only are they frickin smart as heck, they actually give a shit about making things work right for the end user.

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

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

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

-Sonny

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.

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

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.

Strangely Familiar?
 

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

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.

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

I did all the previous edits (except the one above) and was having better luck with bluetooth. The first day the bluetooth worked perfect and didn't drop once. My moto h700 stayed connected all night, my jawbone stayed connected most of the last two days. It did disconnect twice each day but it does seem a little better. Maybe it doesn't like the jawbone, I can't use my moto basically ever because no one can hear me. I will go back and see if anything has reset , prob. should have done that before the post but I need help with the following.

Now my phone will not sleep unless I hit the power button. If I get a notification it will dim but never sleep unless I hit the button. Anyone else having this problem since they did these edits or does anyone know how to fix it? Also it won't wake up sometimes when I get a call or message...I have to soft reset.

Thanks

Thanks, that actually fixed the issue with the d pad.

One thing that i have noticed dont know if any others have, when ever you go to BT through settings it seems like it disconnscts it. like ill see if bt is working throug settings, once i hit the mode tab under BT, my phone will hang for a bit (i think its disconnecting) and then goes to the page with no check in the turn on bt box.

but thabks so far for the fix.

j.w. how do you guys get all these value to try, or all these strings, lol do you guys just pull them from your a$$ or something. i would like to learn just to help out in certain things

I tried to change the registry settings but my setting were already the values to be changed TO. I don't understand. I have all the issues, and the values are the good ones...Hopefully something gets done about this crap.

i thought i was loosing my mind or maybe double personalities
mine will run a bit longer then turns itself off

p.s. i was thinking, i should just use this as an advantage to get a free replacement since my phone was all beat up from one fall. Replacements coming in next week :) lol

Okay guys...this is something new and I don't know if you can duplicate it and I don't even know if it makes any sense......BUT when I install Resco, bluetooth starts acting up. As soon as I uninstalled Resco Explorer, bluetooth started working fine. And I know this because I've tried all the apps one by one and Resco Explorer seems to be the one on my phone causing the trouble.

I don't have resco, but I do have PHM...maybe I'll give it a shot since my bt has been acting terrible today.

I couldn't take it any more I would rather have choppy sound than all this trouble with the connection so I flashed back to the 2.09 rom today, until I have time to perfect my a custom.

All edits gathered
 

Can you guys post all the BT edits that work in one posting?

changing the sys value to 0 kept bt connected perfectly, however, my screen would also never shut off all the way. the backlight goes off as instructed, but the screen only shuts off with press of power button.

i just changed the sys value to 2 and my screen does go completely dark like it should. i am going to test bt connectivity now. so far the first and second test pressing my bt button woke up the phone and launched voice command.

dude this is great. i know it has not been long but no matter what with the sys value to 1 my BT would stay connected but my screen would stay on after the backlight went off (and suck my battery dry!)

with the sys value on 2 my bt has been waking up my phone where EVERY OTHER TIME it would not, plus my screen goes black just like it should!

cant wait to test this all day tomorrow!

update: BT has been working fine all morning, phone going to sleep, no disconnect and the headset button wakes up the phone and launches voice command as expected.

anybody else testing the sys value 2?

fyi ihave the new rom and radio 1.40

I'm game to test this. I have the same ROM and radio. I never seemed to have a problem making a call with BT if the phone was asleep. Pressing the connect button would wake up the phone. The problem was receiving calls when phone was asleep. BT headset would never take the call. I'll post my results

Do you know what changing sys to 2 does?

Did you change HKLM/software/microsoft/bluetooth/sys/DisableAutoSuspend to 2 or HKLM\System\CurrentControlSet\Control\Power\State\ Suspended?

HKLM/software/microsoft/bluetooth/sys/DisableAutoSuspend to 2

Thanks for the clarify, it's hard to keep track sometimes. I changed HKLM/software/microsoft/bluetooth/sys/DisableAutoSuspend to 2 a little while ago and restored the other settings suggested in the thread back to defaults. So far so good. BT wakes up phone and Voice command kicks in just like it is supposed to. No disconnects yet. I'll report my results again in a day or so, sooner if I see issues.

hey np.

just an update, i am getting some disconnects with the sys value at 2, but BT stays connected longer and it wakes up the phone and VC does kick in whereas before BT would disconnect more often and would pretty much never wake the phone up. at least now i can rely on it a bit more, but still i want a fix.

with the sys value at 1 my phone would never goto sleep and the battery would just melt away quickly but BT did not disconnect once in 2 days.

with the sys value at 0 BT pretty much barely worked at all. it would sometimes freeze up my phone as well. that does not happen with sys value at 2 so far in one day whereas it would have already with the other values.

I have been running this for about 18 hours and I have had one BT disconnect. By now I would have had 18 disconnects (at least once an hour) running stock. So this does definetly helps make it tolerable until a fix is available.