Confirm source of Bluetooth problem?

**TurboFool** · #1 (**permalink**) 04-05-2008, 09:26 PM

I got a new Bluetooth headset (Samsung WEP200) a couple of days ago, and I'm having a major issue. The headset itself seems to work well overall. Audio quality's pretty good, size is great, comfort is... well, I'm getting used to it. Anyway, the first day I received a phone call, had a nice long conversation, and everything was good. Next call I received, within about 5 seconds of answering the audio suddenly went completely dead. I couldn't hear the other person, and they apparently couldn't hear me. Hung up, called back, still no sound. Turned off hands-free while in the call, and no sound on the handset, either, even through another attempted call. Finally had to soft-reset the phone, and then everything (including the headset) worked perfectly. A few hours later, same thing happened.

I then built a new ROM and tried again. Today everything worked great for several hours and several phone calls, and then as I answered another call, boom, silence. Same pattern, including the lack of sound even with the headset turned off and using the handset's own speaker.

I'm hoping someone can confirm for me whether the problem I'm having is caused by WM6.1, no2chem's ROMs (or the specific build), the kitchen, or something else I may not be thinking of.

I started with a ROM cooked from the 5060 basekit, then when I rebuilt I worked from the official 5060 kitchen with no improvement. I've heard there are Bluetooth issues in WM6.1, but I haven't gotten a clear picture of WHAT specific problems people are having. So far I've been quite successful in connecting via Activesync with Bluetooth and syncing to my Vista machine and browsing my phone from it, so that's working for me. But this sudden losing all phone audio thing is major. If it's just WM6.1 I guess I'll have to consider cooking something based on 3.35 and foregoing the things I've gotten used to in the new OS. If it's the kitchen, then I can always go back to uncooked no2chem ROMs and manually installing my applications. I just want to see if someone has a solid answer before I waste more time.

digitalonellc · #2 (**permalink**) 04-06-2008, 03:12 AM

I am having the same problem, with the same headset, I have tried all the roms and the only one that works decent is the newest sprint rom.

everything else disconnects, its not just your headset either, there are lots more, search for disconnect.

**TurboFool** · #3 (**permalink**) 04-06-2008, 12:00 PM

So that's the same problem? I'd read about disconnects, but wasn't sure they involved the losing audio altogether. So this is a WM6.1 issue, then?

digitalonellc · #4 (**permalink**) 04-06-2008, 12:13 PM

6.0 / 6.1 same headset had 0 issues with my 6700, even with 6.0, it must be the bluetooth stack causing issues. chipset drivers?

**Lsme420** · #5 (**permalink**) 04-06-2008, 12:20 PM

I'm not to sure its a bluetooth problem at all. I have 2 different bluetooths and I just had to hard reset my phone because of no sound. It started about a week ago when my phone started make a strange beep when I would make a call. After a few days all sound would just disappear until I would do a soft reset. I'd make a call and the other party couldn't hear me and I couldn't hear them. Went back to the stock Sprint rom from a dcd rom but changed the page pool size and removed some of the bloat ware and all seams well as of now.

digitalonellc · #6 (**permalink**) 04-06-2008, 12:25 PM

Crazy, I had that exact deep tone happen to me when making calls.

digitalonellc · #7 (**permalink**) 04-06-2008, 12:26 PM

Quote:

Originally Posted by Lsme420

I'm not to sure it a bluetooth problem at all. I have 2 different bluetooths and I just had to hard reset my phone because of no sound. It started about a week ago when my phone started make a strange beep when I would make a call. After a few days all sound would just disappear until I would do a soft reset. I'd make a call and the other party couldn't hear me and I couldn't hear them. Went back to the stock Sprint rom from a dcd rom but changed the page pool size and removed some of the bloat ware and all seams well as of now.

whats a good page pool size?

dallas contractor · #8 (**permalink**) 04-06-2008, 12:31 PM

I have heard around you may need to try your our settings. 2,4,6,8,10
Did you remove one version of BT? or did you mean you had two versions of Microsoft Voice Command?

**Lsme420** · #9 (**permalink**) 04-06-2008, 12:37 PM

Quote:

Originally Posted by digitalonellc

Crazy, I had that exact deep tone happen to me when making calls.

Ya it was nutz. It happened all on its own to. I didn't install anything just one morning it started to do the beep. I thought at first it was WinMobile Torrent but Have since decided it wasn't. I read a post here on the geeks that said I need to do a registry change to stop the beep but Im not going for it. Something changed on its own so just changing the registry wouldn't fix my problem.My page pool I set at 5 or 6. I have gone to 4 but it was sh*tty.

Quote:

Originally Posted by dallas contractor

I have heard around you may need to try your our settings. 2,4,6,8,10
Did you remove one version of BT? or did you mean you had two versions of Microsoft Voice Command?

I dont use voice commander so whats this 2,4,6,8 setting you speak of?

**TurboFool** · #10 (**permalink**) 04-06-2008, 12:40 PM

Well, I've just downgraded to a 3.35-based cooked ROM with hopes that this clears up the problem. If it happens again I'll go back to 6.1, since it's obviously a different issue. I'm halfway hopefully hopeful that this fixes it, though, and that Sprint's official 6.1 update comes sooner than later.