A2DP problem

[tt]

When I use A2DP my trinity get extreamly slow.(worse than xda II) Even I set bitpool to 40 but I still get a lot of skipping. Anyone know how to slove this problem?

PS. My XDA II do much better jod than trinity on A2DP. I use WM6 2.0.1.1

[banerbocken]

try:

Current bitpool:48
Max bitpool:48
Capasaty: 37
Priority256:149

Then you pair the Trinity to the headset in the bluetooth menu on the Trinity.
Do not let the headset auto pair with the Trinity cause it causes problems.
I read in this forum som where someone that came to this conclution and it works for me.

Hope you understood what I was trying to explain..

[TROTAMAR]

I he the same problem, and I do not understand what you mean when you say "Then you pair the Trinity to the headset in the bluetooth menu on the Trinity.
Do not let the headset auto pair with the Trinity cause it causes problems."

Can you explain it?, please

[YYYYY]

I have the same problem, everytime I listen to music via Bluetooth the CPU Usage becomes 100%, it´s very annoying

[tsaurus]

Me too...

Could you clarify on how to apply that fix? Are those settings in the registry?

What happens with your trinity when you're listening to music and a call comes through? I thought it was supposed to switch automatically and resume playback..but the cpu being so slow it doesn't work.

[banerbocken]

Please let me try to clarify.
If the bluetooth on the Trinity is on when you turn the headset on, the headset will auto pair ( connect) with the Trinity.
I read here ( and it works for me ), that if you first turn on the headset, then turn on the bluetooth, there will be no connection between the Trinity and the headset. This is when you in the bluetooth settings of the Trinity choose to use the headset as a headset. This will connect the headset to the Trinity and walla.. no chopping. Now Im no guru in this forum, but as I understand, the problem is in the bluetooth stack in Windows Mobile.
The settings I spoke of are in the regestry. They can be configured in TweakUI on the A2DP tab or manually in " HKLM\Software\Microsoft\Bluetooth\A2DP\Settings " and " HKLM\Software\Microsoft\Bluetooth\AudioGateway "
Now this is not a perfect fix. As I wrote before, the problem is the stack.
The Trinity will become very slow but the chopping will go away.
Hope this works as well for you as it does for me..

[tedkyle]

The problem seems to be that A2DP on the Trinity takes up a lot of CPU resource and slows things down. I've learned that the choice of media player can make a difference.

With MortPlayer or WMP, my device became so slow, it effectively could do nothing but play music. With Core Player, it's slow, but useable for other functions. It's a shame, because MortPlayer is a fine player otherwise.

[tsaurus]

As a consequence to the high cpu usage, I've found that its impossible to watch divx movies on core player (its possible but chuggy). Is there a setting in which we can lower the cpu usage whilst using bluetooth audio?

And can I just confirm with someone that the problems previously described with the bluetooth is a software problem and not hardware? Is there a likelihood that the official WM6 rom will allow bluetooth audio without crippling there rest of the system?

[MontAlbert]

can someone explain the settings for A2DP in TweakUI for me please? I cant seem to find anywhere what each setting means....

thanks