View Single Post
  #23 (permalink)  
Old 11-03-2009, 04:22 PM
raidzero's Avatar
raidzero
N00b
Offline
Location: PPCG
 
Join Date: Dec 2008
Posts: 2,193
Reputation: 5220
raidzero is a trusted member of the communityraidzero is a trusted member of the communityraidzero is a trusted member of the communityraidzero is a trusted member of the communityraidzero is a trusted member of the communityraidzero is a trusted member of the communityraidzero is a trusted member of the communityraidzero is a trusted member of the communityraidzero is a trusted member of the communityraidzero is a trusted member of the communityraidzero is a trusted member of the community
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Send a message via MSN to raidzero
Re: Request for Chefs: Do NOT use Widcomm bluetooth stack from shipped ROMs

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
__________________

Last edited by raidzero; 11-03-2009 at 04:54 PM.
Reply With Quote