Confirm source of Bluetooth problem? - Page 2

**Lsme420** · #11 (**permalink**) 04-06-2008, 12:41 PM

Quote:

Originally Posted by TurboFool;242215S

Sprint's official 6.1 update comes sooner than later.

Your not holding your breath I hope. I don't like 6.1. Uses more Ram than 6.0. I just use Codys threaded sms app and couldn't ask for better. Cant really tell a difference.

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

Quote:

Originally Posted by Lsme420

Your not holding your breath I hope. I don't like 6.1. Uses more Ram than 6.0. I just use Codys threaded sms app and couldn't ask for better. Cant really tell a difference.

Yes, but point is that I do like 6.1. I've been very happy with it, and prefer its integrated SMS to the codypcc application which gave me enough occasional problems that I was glad to move on from it. I also found that 6.1 managed its RAM drastically better than 6.0, making its use of slightly more RAM irrelevant. So I'm quite disappointed to be switching off of 6.1 right now because of this Bluetooth issue. So hopefully Sprint's announced 6.1 update for the Mogul comes very soon, as then we'll likely have Bluetooth drivers that are fully compatible with the OS and better cooked ROMs without these problems.

**Lsme420** · #13 (**permalink**) 04-06-2008, 12:50 PM

Quote:

Originally Posted by TurboFool

Yes, but point is that I do like 6.1. I've been very happy with it, and prefer its integrated SMS to the codypcc application which gave me enough occasional problems that I was glad to move on from it. I also found that 6.1 managed its RAM drastically better than 6.0, making its use of slightly more RAM irrelevant. So I'm quite disappointed to be switching off of 6.1 right now because of this Bluetooth issue. So hopefully Sprint's announced 6.1 update for the Mogul comes very soon, as then we'll likely have Bluetooth drivers that are fully compatible with the OS and better cooked ROMs without these problems.

Right-on.........

avaya · #14 (**permalink**) 04-06-2008, 04:12 PM

count me in as having the exact same problem. I am also using the WEP200. Wonder where the problem lies..

**puff** · #15 (**permalink**) 04-06-2008, 04:28 PM

i could swear i read somewhere that the bT stack used is different due to issues w/ the bT stack from prev builds (like wM6.0) - think it was in no2chem's thread

*edit* http://forum.ppcgeeks.com/showpost.p...&postcount=839

payback · #16 (**permalink**) 04-06-2008, 04:34 PM

Are you experiencing this problem while your phone is connected to a wall outlet ( charging )

**TurboFool** · #17 (**permalink**) 04-06-2008, 08:45 PM

Well, downgraded to a cooked 3.35 and experienced the problem again within about 15 minutes. Went straight back to 6.1 since there was clearly no benefit to the downgrade. What on earth is the story here? I'd suspect the headset, except there's no logical reason why it would cut off ALL audio to the phone through the handset, as well.

I also noticed today that when it IS working, I get random audio oddities. Sometimes the audio on my phone would play through the headset when not in a call (menu effects, error beeps, etc.), but usually not, and for a while I was hearing a constant flow of silent sound, including random crackles until I soft-reset. Very odd.

digitalonellc · #18 (**permalink**) 04-25-2008, 12:38 AM

You know I had the same things happen, the random crackles, whats crazy is I put 6.1 back on, and it was actually working great until today, and I didnt put anything new on it. Heres the deal: I press the headset button, and the microphone appears onscreen, and it WILL work if you say a command, I just dont get the DING sound, checked and in sounds the notifications are still on. Like lsme420 nothing changed, unless the government installs their monitoring software on my phone and its not fully compatible with the cooked roms ://

oh no! all your ppc are belong to us.

**mikee4fun** · #19 (**permalink**) 04-25-2008, 01:08 AM

Quote:

Originally Posted by Lsme420

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.

Hah had the same issue. Sounds from the phone. I thought Hal was trying to hack in. I cooked my own from the 5060 base and now all is good. =)

**TurboFool** · #20 (**permalink**) 04-25-2008, 11:41 AM

As an update to my issue, after my last post and the problem occurring one more time, it hasn't happened since (knock on wood). Very odd. I'm relieved, though, because all I can assume is if it does happen again it will be seldom enough that I'm not too displaced by it.