PPCGeeks

PPCGeeks (http://forum.ppcgeeks.com/index.php)
-   HTC Touch Pro 2 (http://forum.ppcgeeks.com/forumdisplay.php?f=97)
-   -   Request for Chefs: Do NOT use Widcomm bluetooth stack from shipped ROMs (http://forum.ppcgeeks.com/showthread.php?t=85568)

Boo Boo 11-04-2009 03:57 AM

Re: Request for Chefs: Do NOT use Widcomm bluetooth stack from shipped ROMs
 
i wish the bt stack would play ringtones and hangup calls when you hit the end button on the headset. at least the tp worked.

disapointed withthe inability to get a work around taken care of

sammy12oz 11-04-2009 08:33 AM

Re: Request for Chefs: Do NOT use Widcomm bluetooth stack from shipped ROMs
 
I have the Jawbone 2 and this is an issue for me as well. I cannot use the buttons on the headset to activate MSVC, end a call or redial.
This headset worked flawlessly with my touch pro.
It's extremely dissapointing to not have these features as I use them all day at work, or I did. Also I am in CT and even though I don't see it enforced it is ilegal to use a cell phone without a hands free device.
I really hope that this is addressed by HTC, the carriers or someone in the community.

dodgeboy 11-05-2009 02:10 PM

Re: Request for Chefs: Do NOT use Widcomm bluetooth stack from shipped ROMs
 
Quote:

Originally Posted by raidzero (Post 1294872)
I have been working on removing the widcomm stack and am cooking again without it. I am no master at this by any means and my methods are pretty much brute force. I removed everything from oemdrivers that had a bt in the front (file name) except for the few modules, they stayed as they were in the TP oemdrivers. I then removed the widcomm registry entries from the rgu in oemdrivers. I very much doubt this will work. I am only doing it so toggleBTh.exe will work as it does not with the new stack. I have not tested with my car yet as I just got bluetooth working at all today. It did work fine with my cheapo earpiece. It is cooking now and I will report how it goes... it seems to me that what I did should work in theory, as all that is needed for MS BT to work are those SYS packages, which are included in this build. right? wrong?

edit: no luck.. no more widcomm in registry and no widcomm files = no bluetooth lol

Is the MS BT Stack available anywhere to try to install in its place? I really appreciate your work on this! I would definitely be willing to donate to whomever cooks a clean rom with the MS BT Stack.

helix139 11-05-2009 03:02 PM

Re: Request for Chefs: Do NOT use Widcomm bluetooth stack from shipped ROMs
 
Quote:

Originally Posted by raidzero (Post 1294872)
I have been working on removing the widcomm stack and am cooking again without it. I am no master at this by any means and my methods are pretty much brute force. I removed everything from oemdrivers that had a bt in the front (file name) except for the few modules, they stayed as they were in the TP oemdrivers. I then removed the widcomm registry entries from the rgu in oemdrivers. I very much doubt this will work. I am only doing it so toggleBTh.exe will work as it does not with the new stack. I have not tested with my car yet as I just got bluetooth working at all today. It did work fine with my cheapo earpiece. It is cooking now and I will report how it goes... it seems to me that what I did should work in theory, as all that is needed for MS BT to work are those SYS packages, which are included in this build. right? wrong?

edit: no luck.. no more widcomm in registry and no widcomm files = no bluetooth lol

Try asking Juicy or MightyMike or Scrosler or one of the other chefs. Juicy said in another thread that the MS stack files just aren't present in our ROMs, but I believe he knows what they are and probably where you can get them. My guess is the MS stack can be pulled from one of the TP1 ROMs. Getting rid of the Widcomm stack is half the battle though. Outstanding work!

the3rd 11-05-2009 05:01 PM

Re: Request for Chefs: Do NOT use Widcomm bluetooth stack from shipped ROMs
 
more than happy to donate to the chef who gets the ms stack as well.

ftc_osiris 11-05-2009 10:43 PM

Re: Request for Chefs: Do NOT use Widcomm bluetooth stack from shipped ROMs
 
I will as well

amw1972 11-05-2009 11:26 PM

Re: Request for Chefs: Do NOT use Widcomm bluetooth stack from shipped ROMs
 
reading thru all the posts...its clear to anyone that pays attention that MOST of the notable cooks are not going to go back to the MS Stack anytime soon. Even members of the elite team represented early in the thread.

I think this is going to be fixed if we voice own complaints to HTC. Some of us paid top dollar for our bluetooth device...NOT to mention vehicles...and for all to play nice...seems the Widcomm stack is it...but MS needs to playball and allow the Widcomm stack play well with its software (MSVC to be exact.)

HTC needs to come up with a fix so we can hang up calls from out headsets...or else why bother with a headset!


so if I was using the headset...VC doesn't work...and I reach down to dial...get a ticket...can I sue HTC/M$ for the fine that i paid...would that be a class action suit if enough of us are affected??

mikee4fun 11-05-2009 11:30 PM

Re: Request for Chefs: Do NOT use Widcomm bluetooth stack from shipped ROMs
 
Only issue I have seen with the new widcomm stack is it has issues hanging up when the phone is off. I am sure we will find a way to fix this issue. On a positive spin the new bluetooth stack turns off the bluetooth audio gateway when you disconnect your headset so you battery life is much better. You can with the Microsoft stack with a registry change but it has issues reconnecting.

Yes the widcomm stack is the best ever, that I have used. This is going all the back to the xda II

grv 11-09-2009 11:55 AM

Re: Request for Chefs: Do NOT use Widcomm bluetooth stack from shipped ROMs
 
I'd donate to someone who can cook up a clean stable ROM with the MS stack too. No way to get AVRCP to work with anything but HTC Medai Player, WMP or Pocket Player on the TP2 with the Widcomm stack, which just about has me on the point of sending the TP2 back.

If anybody ever figures it out, it would be awesome. I really like the TP2 otherwise, but BT is a dealbreaker for me.

helix139 11-09-2009 02:18 PM

Re: Request for Chefs: Do NOT use Widcomm bluetooth stack from shipped ROMs
 
It appears the hanging up issue is related to the data connection. When the connection is on or dormant, the BT headset will not hang up. When it is completely disconnected, the headset hangs up no problem. Perhaps someone can figure out a fix?

Boo Boo 11-09-2009 02:51 PM

Re: Request for Chefs: Do NOT use Widcomm bluetooth stack from shipped ROMs
 
easiest fix is to class action htc for violating the fair use act of the software MS provides. since the ms stack works and the htc doersn't but they monopolized it so its unusable. HTC just needs to stick with hardware and let MS design the software

mlcastro 11-09-2009 03:16 PM

Re: Request for Chefs: Do NOT use Widcomm bluetooth stack from shipped ROMs
 
Quote:

Originally Posted by helix139 (Post 1190265)
Question for everyone:

How many of you can actually get your headset to end a call when you hit the end call button, and what type of headset are you using?

Nothing like driving in your car with your phone put away in your center console and leaving someone a voicemail only to realize your phone didn't hang up and having to fumble around while driving for your phone so you can end the call, all while trying not to swear up a storm due to your frustration into your buddy's voicemail.

Yeah, exactly. Using Ford Sync, I can't hang up my phone at all. The TP2 is the first phone to cause this type of problem. I know many that are experiencing the same.

krohnjw 11-09-2009 03:43 PM

Re: Request for Chefs: Do NOT use Widcomm bluetooth stack from shipped ROMs
 
Quote:

Originally Posted by helix139 (Post 1190265)
Question for everyone:

How many of you can actually get your headset to end a call when you hit the end call button, and what type of headset are you using?

Nothing like driving in your car with your phone put away in your center console and leaving someone a voicemail only to realize your phone didn't hang up and having to fumble around while driving for your phone so you can end the call, all while trying not to swear up a storm due to your frustration into your buddy's voicemail.

Nokia BH-600 works fine as well as my Clarion CZ-509 head unit - no issues with answering calls, hanging up or slow downs when BT is in use.

davahad 11-09-2009 04:02 PM

Re: Request for Chefs: Do NOT use Widcomm bluetooth stack from shipped ROMs
 
I have a 2009 BMW X5 and I cannot hang up phone calls with Verizon TP2. Bluetooth worked perfectly with AT&T Tilt.

ftc_osiris 11-14-2009 07:34 PM

Re: Request for Chefs: Do NOT use Widcomm bluetooth stack from shipped ROMs
 
I can confirm, it does seem that having the data auto disconnect during phone call solves the issue!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

I will report back when tested more and will edit the above if it quits working

CovKid66 11-14-2009 07:58 PM

Re: Request for Chefs: Do NOT use Widcomm bluetooth stack from shipped ROMs
 
Quote:

Originally Posted by ftc_osiris (Post 1329413)
I can confirm, it does seem that having the data auto disconnect during phone call solves the issue!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

I will report back when tested more and will edit the above if it quits working

But as has been posted in other threads, that means those with Push E-mail are up the creek if they go that route unless you can find a way to auto-reconnect data after the call???

Boo Boo 11-15-2009 01:00 AM

Re: Request for Chefs: Do NOT use Widcomm bluetooth stack from shipped ROMs
 
davahad , maybe you should post the registry settings and we can go from there. check between both devices an see whats differnet

Boo Boo 11-15-2009 01:05 AM

Re: Request for Chefs: Do NOT use Widcomm bluetooth stack from shipped ROMs
 
ps, I doubt htc will fix this on the tp2, they would rather just screw the end user, since they got their money allready and still have yet to fix the stock tp rom which is faulty out of the box

BacardiGuy 11-15-2009 11:14 AM

Re: Request for Chefs: Do NOT use Widcomm bluetooth stack from shipped ROMs
 
Quote:

Originally Posted by helix139 (Post 1183360)
I've never had any problems with the MS stack whatsoever on either the 6700, 6800, or TP1. I've had 2 devices with Widcomm stacks (XV6600 and TP2) and both have been subpar. The Widcomm stack lacks the PAN profile, has major issues with voice command, won't hang up, ignore, or redial when you hit the appropriate buttons on your headset, and does not work at all with visual voicemail. It will connect and function fine during calls, but that is about it. I know that these problems have been well documented in the main forum.

At least if the chefs don't want to replace it, perhaps they can give us the option to do so ourselves, like many have done with the sys files on the TP1 ROMs. I'd be willing to donate to have that ability. I'd make a ROM myself but I have neither the time to do it, the knowledge to do it, or the time to learn how.

Same issues here

dodgeboy 12-02-2009 11:35 AM

Re: Request for Chefs: Do NOT use Widcomm bluetooth stack from shipped ROMs
 
FYI - Some of the new roms are using a new BT driver/stack that fixes most of these issues. I'm running MightyROM 11/25, and I can hang up the phone now. I'm sweeping through the list of BT Issue threads that I subscribed to and posting this for those that haven't heard about it.

Dave

HellsChicken 01-03-2010 01:25 AM

Re: Request for Chefs: Do NOT use Widcomm bluetooth stack from shipped ROMs
 
I'll throw in my weight as well..

I've got an '07 Altima with the nav system, and my Raphel can connect, but the person on the other end can't hear me, and what I hear is extremely distorted. Sadly, the workaround of transferring to the phone then back to the car never worked for me.

I'm running the EnergyRom now, but seems like it doesn't solve the problem (probably not using updated drivers).

I've heard the TP2 works fine with this system. Before it came out, I had a thread going with HTC about the issue, and they assured me it couldn't be fixed. Tried to tell me I'd need to replace the nav system. When the TP2 came out, I tried contacting them a couple of times asking if they would backport that driver to the TP, and never once heard back from them again =/

Anyway, if anyone does come up with a solution, I'd love one....


All times are GMT -4. The time now is 02:51 AM.

Powered by vBulletin® ©2000 - 2025, Jelsoft Enterprises Ltd.
©2012 - PPCGeeks.com


Content Relevant URLs by vBSEO 3.6.0