XDA Universal (aka - Xda Exec, MDA Pro, JASJAR, Qtek 9000)

[carterc9]

I purchased a Targus (Model# AMB04US) Bluetooth Mouse it works great with my XDA, flawless, but when I use a Sony Ericsson HBH-DS980 to listen to music each time I even nudge the mouse the music goes silent and the mouse instantly works, but the headset then needs the mouse to fall still for a second or two before the music then plays again via the headset. HELP!!!!!!!!!!!!!!!!!!!!!!!! PLEASE PLEASE OH PLEASE PLEASE!!!!!!!!!!!!!! THANKS! Basically I can't use Bluemouse (Mouse) with a Headset. I am using WM6 and I am a tech myself and have run through all the possibles and so have resorted to a post for help. Thks.

[admin]

We're using the HTC Universal quite often here, probably because of the great hardware keyboard.

You've mentioned yours is using the wm6, so it's an unofficial release isn't it?

Is there any chance you could try to reproduce this issue on a different firmware/RUU?

[carterc9]

Yeah long time fan and user, no I haven't, I didn't wanna since I have so many third party apps, regis changes, regular stuff, but guess I'll have to redo all. Maybe there is a bluetooth.cab? which would install a new 'stack' is it... or would that have to be made/created by the cooked ROM creator or can a stand alone cab be installed - thanks!

[Jaeger]

I have had similar issues. I think it has something to do with bandwidth available to bluetooth, and nothing to do with the software.

If I am piping music through my WEP500 headset (with a BT hack), the mouse will not operate. If I am using the mouse and THEN pipe music to the headset, the mouse lags like CRAZY and eventually will not respond.
This is while piping sound to a plain mono headset (8khz), not even A2DP.

Even before I got BlueInput, if I tried to use my BT keyboard (built-in drivers) while piping A2DP to bluetooth speakers, the sound would start breaking up and eventually go silent until I stopped typing. I'm guessing nothing can be done without more bandwidth.

BTW - I recently upgraded to WM6.1 also, but the problem was the same with WM5.

[Teksoft]

Indeed it sounds like a limitation of the OS.

We'll test this further when we get the chance.