Widcomm BT Stack (.03) Problems (A2DP) - 8525, TyTN, MDA Vario II, JasJam Software Upgradin

Since the main widcomm thread has become what I'd tend to call convoluted, I thought I might as well start a new thread in the hopes that somebody has experienced a similar problem and found a fix.
I installed the widcomm stack on an 8525, install went fine (yes, MS BT was disabled during install). Successfully paired my Pulsar 590A's and they seemed to work well. The audio fidelity was an incredible improvement.
The problem was the intermittent stops that occurred several times per song playing MP3's (generally encoded to 192) in Media Player. It was annoying enough that I hard reset, but my God I can't go back. The MS stack, even with the reg hack, is just is too horrible.
I'm running the plain ol 1.34.502.1 ROM with the 1.16 radio.
I should note that I installed HTweakC 2.0, and had run the bluetooth improve audio quality tweak prior to installing the widcomm stack. Don't know if that would make a difference or not.
Things I tried: I removed the HTweakC settings, soft reset. I shut down all the BT services except the high quality audio, soft reset. Deleted and repaired the headset, soft reset. Got fed up, hard reset lmao
So I'm going to take another stab at the widcomm stack, because as aforementioned, after experiencing the wid and then going back to MS, I can't abide the MS stack any longer.
Any suggestions, tips, whatever, would be awesome.

---

viatorx said:
Since the main widcomm thread has become what I'd tend to call convoluted, I thought I might as well start a new thread in the hopes that somebody has experienced a similar problem and found a fix.
I installed the widcomm stack on an 8525, install went fine (yes, MS BT was disabled during install). Successfully paired my Pulsar 590A's and they seemed to work well. The audio fidelity was an incredible improvement.
The problem was the intermittent stops that occurred several times per song playing MP3's (generally encoded to 192) in Media Player. It was annoying enough that I hard reset, but my God I can't go back. The MS stack, even with the reg hack, is just is too horrible.
I'm running the plain ol 1.34.502.1 ROM with the 1.16 radio.
I should note that I installed HTweakC 2.0, and had run the bluetooth improve audio quality tweak prior to installing the widcomm stack. Don't know if that would make a difference or not.
Things I tried: I removed the HTweakC settings, soft reset. I shut down all the BT services except the high quality audio, soft reset. Deleted and repaired the headset, soft reset. Got fed up, hard reset lmao
So I'm going to take another stab at the widcomm stack, because as aforementioned, after experiencing the wid and then going back to MS, I can't abide the MS stack any longer.
Any suggestions, tips, whatever, would be awesome.
Click to expand...
Click to collapse
i suggest you watch your program memory levels while playing the 192 bitrate file and while running the widcomm stack... you will find that your device runs out of program memory... as media player required a fair amount of memory to play high bitrate files that only gives you a minimal amount left for the widcomm stack which also requires a decent amount...
i suggest you try mortplayer or a different mp3 player and see if u have the same issues...

---

Yeah that definately makes sense. I was careful about closing out everything but the media player and the bluetooth manager, but I had wondered if the higher bitrate levels were what was causing some of the problem. I'll try mortplayer and see if I get a better result.

---

Using MortPlayer is a good idea, especially with your Plantronics headphones, since AVRCP (play/pause/next/back buttons) should work with it.

---

Excellent, I'll def try that. I've got Widcomm back up and paired. I tried TCPMP first and I definately get less skips, but they do persist. I'll try Mort and see how that does, had just chosen to try TCPMP because it appeared to be less of a CPU hog. I am also wondering if the A2DP fix that Sleuth posted will do anything.

---

FWIW, I started experiencing more probs last night. Active sync via USB wouldn't work, and the memory issue started popping up. Boy, really is a frustrating issue. The audio quality is like 10x better, it pairs easier with my computers, and I like the interface. But grr, I'm at the point where I think I'm going back to MS again. I'll just bide my time until some of the bugs can be worked out. I really appreciate all the help though guys, this place is a treasure of unspeakable magnitude.

---

for me the skipping disappeard when using Sleuths A2DP Fix.
and this is a known error, not only with widcomm but with ms stack too.
i do not have the AS error nor memory problems with the widcomm stack, using Xda-live 0.2 and Widocm 0.3.
using mortplayer for music and tcmpg for video , no problems what so ever (except that i must sometimes (quite often) softreset to get my headset to pair (using plantronics 260)

---

viatorx said:
FWIW, I started experiencing more probs last night. Active sync via USB wouldn't work...
Click to expand...
Click to collapse
I also have this problems. After install Widcomm stack (I have Windows Mobile VI - BLACK EDITION v1.2 but also happended with WM6 for Hermes LVSW Edition), I can't sync via USB. My computer don't detect the Hermes! Is if like I didn't connect to it.
Any solution for this?

---

viatorx said:
Excellent, I'll def try that. I've got Widcomm back up and paired. I tried TCPMP first and I definately get less skips, but they do persist. I'll try Mort and see how that does, had just chosen to try TCPMP because it appeared to be less of a CPU hog.
Click to expand...
Click to collapse
Yup, it IS less of a CPU hog unless you use the equalizer - with about 70-80% (see my article in the General forum on the generic CPU usage of all MM players). However, it doesn't support AVRCP - only the latest version(s) of the commercial CorePlayer do so (see my AVRCP-compatibility articles).
If you need both AVRCP and very low CPU usage, go for iPlay.

---

sesaru said:
I also have this problems. After install Widcomm stack (I have Windows Mobile VI - BLACK EDITION v1.2 but also happended with WM6 for Hermes LVSW Edition), I can't sync via USB. My computer don't detect the Hermes! Is if like I didn't connect to it.
Any solution for this?
Click to expand...
Click to collapse
As has been pointed out in several of my articles (do you follow them? They're all cross-posted to the General forum), if you install the Widcomm BT stack and don't apply the related COM Registry hacks, you can only use the "old" (pre-WM5) ActiveSync approach, NOT the newer. That is, in your case, you don't see your PDA because it'd require a different way of connection than before installing the Widcomm stack.
Try disabling your firewall / antivirus software to see whether they allow for the connection.

---

viatorx said:
I should note that I installed HTweakC 2.0, and had run the bluetooth improve audio quality tweak prior to installing the widcomm stack. Don't know if that would make a difference or not.
Click to expand...
Click to collapse
It does't - it only sets the MS BT stack quality parameters, NOT those of Widcomm.
Also see my Widcomm & MS BT stack quality-related article in the General forum, where I elaborated on all these parameters.

---

Menneisyys said:
As has been pointed out in several of my articles (do you follow them? They're all cross-posted to the General forum), if you install the Widcomm BT stack and don't apply the related COM Registry hacks, you can only use the "old" (pre-WM5) ActiveSync approach, NOT the newer. That is, in your case, you don't see your PDA because it'd require a different way of connection than before installing the Widcomm stack.
Try disabling your firewall / antivirus software to see whether they allow for the connection.
Click to expand...
Click to collapse
Umm, sometimes is hard to find the things in large posts, even if you look for them.
Here is the fix:
http://forum.xda-developers.com/showpost.php?p=1072534&postcount=59

---

sesaru said:
Umm, sometimes is hard to find the things in large posts, even if you look for them.
Here is the fix:
http://forum.xda-developers.com/showpost.php?p=1072534&postcount=59
Click to expand...
Click to collapse
Oh!! I just realised now I can't switch on the phone module of the comm manager (>_<) So It doesn't work; I give up.
Can you post where exactly is the fix for this? I'm reading a lot, but I can't find it ...

---

sesaru said:
Umm, sometimes is hard to find the things in large posts, even if you look for them.
Here is the fix:
http://forum.xda-developers.com/showpost.php?p=1072534&postcount=59
Click to expand...
Click to collapse
Please, anybody that make this work let me know how can I do it ... I can't find in the forum ...

---

I've been working with the Widcomm BT Stack for a week now in combination with a Logitech Mobile Headset HS200. So far this is what I experienced:
XDA Live v0.20
- Connected using MS Stack, no tweaks: Poor sound quality / severe skipping
- Connected using WC Stack, no tweaks: Average sound quality / servere skipping
- Connected using WC Stack, Sleuth255 A2DP fix: Average sound quality / average skipping
HTC AKU 3.3 with 16MB poolsize
- Connected using WC Stack, Sleuth255 A2DP fix, several tweaks: Good Sound quality / average skipping
- Connected using MS Stack, Sleuth255 AD2P fix / workaround: Poor sound quality / almost no skipping.
Here it got interesting. Apparently without the Widcomm BT Stack the skipping was zero to none with all the tweaks. But the MS Stack sucks bigtime, so how much you tweak it won't sound as good as the WC Stack.
Now running WC Stack with Sleuth255's workaround to avoid skipping making some minor changes in the registry. Skipping is brought down to a minimal when using Widcomm BT Stack now, but I'm still not satisfied.
I'm waiting for the XDA v0.30 release, so I can try a 16MB poolsize and A2DP on WM6.
Edit:
Wow HTweak 2.0 greatly improved the sound quality. Still have some minor skipping, but for the time being I can live with this.

---

Mesh said:
I've been working with the Widcomm BT Stack for a week now in combination with a Logitech Mobile Headset HS200. So far this is what I experienced:
XDA Live v0.20
- Connected using MS Stack, no tweaks: Poor sound quality / severe skipping
- Connected using WC Stack, no tweaks: Average sound quality / servere skipping
- Connected using WC Stack, Sleuth255 A2DP fix: Average sound quality / average skipping
HTC AKU 3.3 with 16MB poolsize
- Connected using WC Stack, Sleuth255 A2DP fix, several tweaks: Good Sound quality / average skipping
- Connected using MS Stack, Sleuth255 AD2P fix / workaround: Poor sound quality / almost no skipping.
Here it got interesting. Apparently without the Widcomm BT Stack the skipping was zero to none with all the tweaks. But the MS Stack sucks bigtime, so how much you tweak it won't sound as good as the WC Stack.
Now running WC Stack with Sleuth255's workaround to avoid skipping making some minor changes in the registry. Skipping is brought down to a minimal when using Widcomm BT Stack now, but I'm still not satisfied.
I'm waiting for the XDA v0.30 release, so I can try a 16MB poolsize and A2DP on WM6.
Edit:
Wow HTweak 2.0 greatly improved the sound quality. Still have some minor skipping, but for the time being I can live with this.
Click to expand...
Click to collapse
I have never had skipping but the sound quality with the WC stack is just way better.
I've edited the LVSW edition to a 10mb pagepool to try how this works as I find the WC stack with normal pagepool to slow.
I will upload this version here:
http://forum.xda-developers.com/showthread.php?p=1194525#post1194525

---

trion said:
I have never had skipping but the sound quality with the WC stack is just way better.
I've edited the LVSW edition to a 10mb pagepool to try how this works as I find the WC stack with normal pagepool to slow.
I will upload this version here:
http://forum.xda-developers.com/showthread.php?p=1194525#post1194525
Click to expand...
Click to collapse
Tnx might give it a try. Still waiting for XDA Live v0.30 release or perhaps the new Black v2.0 release everyone's talking about. Give a nice 16MB pagesize, and test the Widcomm BT Stack. I have this thing for new ROM's...

---

trion said:
I have never had skipping but the sound quality with the WC stack is just way better.
I've edited the LVSW edition to a 10mb pagepool to try how this works as I find the WC stack with normal pagepool to slow.
I will upload this version here:
http://forum.xda-developers.com/showthread.php?p=1194525#post1194525
Click to expand...
Click to collapse
Hello,
I installed this ROM in my X01HT and WC Stack. After That, I did this:
1. Close BT Manager and turn BT off.
2. Open registry (need Resco Registry plug-in) and make the following changes (no need of soft reset after them):
[HKLM\Software\Widcomm\BTConfig\Applications\0001]
Change ComPortNumber from 8 to 7
[HKLM\Software\Widcomm\BTConfig\Services\0001]
Change ComPortNumber from 9 to 6
Rename [HKLM\Drivers\BuiltIn\Serial8] to [HKLM\Drivers\BuiltIn\Serial6] and change these subkeys acordingly
"FriendlyName"="Bluetooth Serial Port COM6:"
"DeviceArrayIndex"=dword:00000006
"Index"=dword:00000006
When you have changed this, suspend (off) the PDA for a few seconds and turn it on again. Then goto Bluetooth Settings- Services-Serial Port-Advanced and verify that thet ports that Widcomm is using are 6 & 7​
But now I can't switch on the phone App. When I open the Comm App, and push the "Phone" button, it didn't start.
Please, somebody let me know what I'm doing bad.
Thanks
Cesar

---

Mesh said:
HTC AKU 3.3 with 16MB poolsize
- Connected using WC Stack, Sleuth255 A2DP fix, several tweaks: Good Sound quality / average skipping
- Connected using MS Stack, Sleuth255 AD2P fix / workaround: Poor sound quality / almost no skipping.
Click to expand...
Click to collapse
What ROMs have 16 Mg of PoolSize? What is that ROM? Is it for Hermes?

---

i am just wondering if anyone else has the same problem with the widcomm for hermes as I do, when running the memory footprint goes from around 25 down to 2 mb in a matter of hours.
Anyone else noticed? (I am using black v.2 wm6)
(tried wit for 2 days without widcomm, no memeory loss, with widcomm memory loss was unavoidable)
anyone with a solution?