Ok, I've used upgraded the rom as described in that link. I didn't bother adding any new cab files to it... I just picked what I wanted and then hit go.


I believe the process worked as it was supposed to, however it has not really fixed my problem.


The issue is this... the FIRST sync with my headset is always perfect. It does exactly what it's supposed to.

BUT if I turn my headset off, lose connection for some reason, or turn off/reset my PPC the connection will not automatically resume.


The only means I know of conveniently reactivating the connection is to press the "play" button my headset. That does initiate a connection and begins streaming stereo sound into my headset. However, it's very choppy and drops out for long periods... it's a horrible horrible connection.


I can fix the situation by deleting the profile in the PPC and then making a new one being very careful on a few points in the process. For example, I must enter 0000 at the FIRST password prompt. This prompt "CAN" be skipped but this sometimes causes a connection that is just as horrible as the one started by pressing the play button... or sometimes it doesn't create a profile at all.


In any event, I need a way to establish the connection more easily then deleting and remaking the profile every time. The play button would be nice... but as I said, the resulting connection is horrendous.

Headset issue?
 

Perhaps since so many people are having good luck with the new A2DP stack in the kitchen this could be an issue with your headset? If not then I'd look in the bug posts and the comments posts for the kitchen. Several users have posted settings changes in the registry that they claim fixed skipping problems.

Good luck!

Unfortunately even though A2DP is vastly improved in this ROM, it's still not 100%. I have four A2DP devices--three of them work fine with these ROMs but one does not.

It does, however, work 100% with WM6, so MS is obviously still working on their A2DP implementation.

Aside from playing with the registry settings under HKLM\Software\Microsoft\Bluetooth\A2DP\Settings I'm not sure there's much else you can do.

The Widcomm stack has many problems on the Apache, which is why there hasn't been much talk about it. It does have pretty flawless A2DP though.

very well, what tweaks do you recommend for the registry with the MS stack?


Again, the problem that I'm having is that when I try to "re connect" the device it skips CONSTANTLY. The initial connection after creating the pairing profile is PERFECT. But if that connection is severed it's very hard... almost impossible from what little I've done with it to get a stable sound transmittion out of it. I don't know why there's a problem.


I do know that sometimes if I go into the blue tooth settings and tell the PPC that the head phones are to be used for stereo output it will "sometimes" create a stable connection. But that's rare. There are other variables that you have to watch out for. For example, all music has to be STOPPED or nothing changes.


It's very odd. I'm almost certain it has something to do with the headphones establishing the connection instead of the other way around.



Could it be that there are some variables that the headphones impose upon the connection by default if it initiates the connection... but that the PPC over rides if it initiates the connection? Because typically when it's the PPC that contacts the headphones first and not the other way around I get a better result.


Pressing the play button to get the headphones to sync up with the PPC almost always causes the problem. I'm talking 99 percent of the time.



I don't mind the PPC initiating contact so long there's an easy way to do it.... ie easier then deleting and remaking the profile.


Is there any way to have the PPC "look" for and connect to the headphones... and not the other way around?

If you do a google search (or search here at the forums) for words like:

bitpool
maxbitpool
usejointstereo

you should pull up several (many) links with info on what settings you can try to tweak. It takes a lot of trial and error, and still may not solve your problem. Like I said, some Headphones chipsets are just plain incompatible with the WM5 implementation of A2DP (I have three that work great, one that doesn't work at all no matter what I do).

You can install that widcomm stack, but you'd have to deal with all the other anomalies it causes.

what is the right way to install the widcomm stack?


I want to try everything. I've downloaded it and even installed it. But can't seem to get it to do A2DP... it doesn't even look like it's capable of it from what little I've seen.


Help me please.

I honestly don't know. I've never messed with it because I need the other functions of BT more than I need A2DP. Hopefully someone with some experience with it can come to your rescue.

Yeah, I dont know from there... My DC800 StereoMoto BT Device has no issues with the Stack on the new roms. It plays flawless, and if I recieve a call it pauses the music and rings through the bt stereo device... then when I answer it on my BT headset it transfers over with no problems. Then once the call has ended the music replays. If I restart my device, or turn off and then on my device, it still works... But, if I restart the device, ofcource WMP isn't running so I'll have to restart that. But if I just turn it off and then back on, the music continues with no problems.

You know what I would sugjest... if you can't seem to figure it out... I'm sorry to say but go out and buy a cheap a2dp device like a DC800 StereoMoto from Radio shack just to see if it works on that. I paid 25 bucks for my StereoMoto and I'm about to go find more and buy a few more for the other area's I want like all the rooms in the house n shyt!

What functions does it not have that you need?
==========================================
Well it might be that it has a problem when it's set as both phone and music?


You seem to have split them. The phone portion of the system is ALWAYS flawless. Even when the music is skipping horribly, if you start to make a phone call it immediately clears up and sounds perfect... in both ears.

Further if the music was fine before the call it comes back fine.


I'll try disabling hands free talking and see if that makes a difference. That would really be annoying but it's nice to narrow down what the issue is... then I just have to find the people that code this stuff and they can patch it...


Let me dream :)

I have a motorola S9 in addition to the sony headset. I'm going to return the motorola headset today as the Sony one is sooo much nicer. I haven't honestly played around with it though since the rom update...


Does anyone know if the S9 is supposed to behave? I ask because it's quiet a bit older then this sony model.

it's confirmed... anytime the headset opens the connection it's crap. I've found a few different ways to get the apache to do it and whenever it does the connection is great.


All of these means require opening the bluetooth configuration panel unfortunately.


Does anyone know of a "single click" option that would cause the APACHE to connect to the headset for music? The only fast means to connect them is by pressing the play button on the headset, but as I've said before that connection is crap.


I had some sound issues but I solved them by lowering my preamp settings. For whatever reason the PPC amplifes the bluetooth sound a little bit before it kicks it out to the head set... so by dropping the preamp a bit it cancels out...