How hard is it to update the BT stack in our phones? Is it a function of the ROM or can one update it themselves? I am using Energy's 21889 WM6.5 Phoenix ROM on my unlocked ATT Fuze and the BT stack in it is no working for me....
Bottom-line is my VW, needs an RSAP compatible BT stack in order to sink my contacts with the NAV unit. Of the four phones I have tried running WM, none have worked and the VW forums indicate it is the Microsoft BT stack giving me issue. Now I have no clue what stack I need, but depending on what it takes t change them out I might be willing to try different ones.
Related
I need some help and I'm not technical... when using my XDAII with only a Jabra FreeSpeak BT250 I had no problems at all. Recently I had my car dealer install a bluetooth hands free system (Parrot CK3000 - www.bluedrive.com) in my car and when I pair with my XDAII the headset connection is lost with the Jabra becuase there is no handsfree option on the XDAII. As I understand it, I must have a headset profile for the Jabra and a handsfree profile for the CK3000. Is it possible to have two profiles on my XDAII for two types of connections? If so, how? If not, does anyone know how I could have two headset profiles that I could easilly switch between based on the pairing device I want to use? Please help...
Re: Headset option available but no Hands Free option on XDA
Charles said:
Is it possible to have two profiles on my XDAII for two types of connections? If so, how? If not, does anyone know how I could have two headset profiles that I could easilly switch between based on the pairing device I want to use? Please help...
Click to expand...
Click to collapse
Well, the XDA II comes with Microsoft's Bluetooth stack, and that stack just does not implement the Handsfree Profile. Some people have, with some degree of success, installed a Widcomm Bluetooth stack on an XDA II. However, as the Widcomm stack was never officially ported to the XDA II, it cannot completely replace the Microsoft stack, so that solution has a few quirks (having two stacks, and switching betrween them for different applications). If you want to try that, just search for "Widcomm". Be advised, however, that the Widcomm stack is not freeware, and is not sold separately. So, all version you find are pirated.
Then there are the Pocket Bluetooth Tools (http://bluetooth.i-networx.de). I think they would allow you to have more than one Bluetooth headset paired with your XAD II, but unfortunately at least the version 1.1.0 does not work with your Parrot. I know that for sure, because I have a Parrot CK-3000 myself (firmware 3.13), and no matter what I tried, it didn't work.
And this is where your options end... no luck, I am afraid.
Cheers
Daniel
Two BT Stacks...what are the potential problems
Thanks for the initial support...very helpful!
If I install the Widcomm Bluetooth software what functions will not be supported/available. I currently have he Jabra FreeSpeak BT250 and the Parrot CK-3000 I would like to pair but also have a BT Sony Vaio Laptop PCG-Z1WAMP3 that I will pair over the next few days and plans to purchase a BT GPS unit in a week that works on the XDAII and the Laptop. Will Widcomm software support all my needs or will it fall short.
PS - before reading your post I tried Pocket Bluetooth Tools (http://bluetooth.i-networx.de) version 1.1.0 and I could not pair the two either. I was initially happy and finally maddened! Should this be removed before adding Widcomm if I do elect to proceed?
Cances of getting anything to work with your sony vaio (other than other sony kit) are slim, sony use their own peculiar bluetooth stack and it doesn't support any but the most basic profiles on any other stack. If I try to search services on my sony c1-mhp from my xda 2 with either widcomm stack or microsoft stack all i get is a load of serial ports.
I did see a thread a while ago about using the widcomm stack on a vaio, but can't remember where.
Re: Two BT Stacks...what are the potential problems
Charles said:
Will Widcomm software support all my needs or will it fall short.
PS - before reading your post I tried Pocket Bluetooth Tools (http://bluetooth.i-networx.de) version 1.1.0 and I could not pair the two either. I was initially happy and finally maddened! Should this be removed before adding Widcomm if I do elect to proceed?
Click to expand...
Click to collapse
Well, it'll be hard enough to get two stacks together working on one hardware, so I don't think it'll be a good idea to add a third player (the Bluetooth Tools) to the game.
I had the Widcomm installed only very briefly. Some time after that, more elaborate instructions on how to install and set up the beast occured on this forum, so your best bet is to search the forum for "Widcomm" and read everything you find. Be warned - it still is a big hack that involves manually adjusting Registry entries and such things.
Cheers
Daniel
Did you guys realize all WM6 versions posted here have Bluetooth Problems ?
Does any1 of you try using a bluetooth GPS with tomtom and wm6 on prophet ?
Here is the problem. On preferences of bluetooth you can add connections then link them. after that you do virtual ports on wich the connection is selected.
Now here comes the buggy part. on wm5 it worked you could choose Incoming and Outgoing ports wich is needed to control and link to a external GPS device. Since crystal, shadow ... and all these roms its not possible to define a Incoming Port thats why TOMTOM in my case does not work anymore. if i downgrade to wm5 and set a incoming port everything runs fine.
Do you know something about this Problem ?
i am currently using tomtom6 with a holux gps bluetooth receiver and i have no problems. you just have to pair your devices and then setup an outgoing com port. even if bluetooth is off, tomtom manages to activate it and connect to my gps device - tested on crystalV5
same here with holux. just pair devices, make outgoing port, setup gps in tomtom, and no problemo. no need for an incoming port.
What problems?
I have been flashing the different WM6 roms and I have no problems whatsoever in using them with my BT GPS. Do the actions by the two previous posts before me and you should not have a problem. Cheers!
It looks like it is not a bug but a feature you describe! Keep in mind that newer software is developped to make things easier...
I use Totom with the original Tomtom BT receiver and I don't have to make any setting or pairing at all. All is taken care of by Tomtom and WM without any interaction by me. Convinient!
alphazero said:
Did you guys realize all WM6 versions posted here have Bluetooth Problems ?
Does any1 of you try using a bluetooth GPS with tomtom and wm6 on prophet ?
Here is the problem. On preferences of bluetooth you can add connections then link them. after that you do virtual ports on wich the connection is selected.
Now here comes the buggy part. on wm5 it worked you could choose Incoming and Outgoing ports wich is needed to control and link to a external GPS device. Since crystal, shadow ... and all these roms its not possible to define a Incoming Port thats why TOMTOM in my case does not work anymore. if i downgrade to wm5 and set a incoming port everything runs fine.
Do you know something about this Problem ?
Click to expand...
Click to collapse
I am having exactly the same problem as you. I have used different WM6.1 rom and the "New Incoming Port" option doesn't show up after i connect my Holux GPS receiver..
yes ihave the same problem with the shadows roms ( TE & CE & ... )
use the korand 3.1 rom thats good ( not have BT problem )
sorry of my english
I have SLIM BT GPS some problem with Google Maps - but I have overcome them by manually setting the GPS in Google Maps options. Woks cool..
From the other hand I have strange problems with sending files from other devices to my JAMin.
I am not sure but the solution is to remove JAMin from the list of paired devices on PC/NOKIA and then You can send files to JAMin. If JAMin is on the list of paired devices - sending do not work.
Best
Use or NDrive I have no problem at WM6
cannot create BT handsfree profile
I'm using Korand's WWE 3.1, WM6.1 ROM - it is excellent, thanks Korand for your work
The only issue I have is with the BT: I have linked up TomTom, and CompeLand via GPSGate fine, and everything works perfectly. However, I have not been able to completely pair my car handsfree.
It took a while to add the device, but I eventually managed it. In settings/Devices, if I press & hold on this device, I get just edit or delete, but set as Hands-free, set as Wireless Stereo are greyed out.
And in the Com ports tab, there should be an option for New Outgoing Port, but it's blank, so I can't tell WM how to connect this device.
Would any kind soul know how to resolve this (any cabs?)
tia
Paul
possible solution to BT ports issue
Posted this on Korand 3.1 WWE (WM6.1), posting it here so that the information is not missed:
in the Output tab of GPS gate, you can add all sorts of ports, including COM ports.
Once you decide to choose the Add COM port option, you can then choose which COM port you want to add. I added COM3 and COM6. I had all sort of problems after that, the device was maxing out on processor and memory. So I removed COM3, and the device runs OK again.
I suspect - and hope - that COM6 is the one for my car handsfree, since I had it running whilst both these ports were enabled. I need to research this a bit more, but it's promising so far
(there is also a virtual activesync port which runs very well for syncing).
These COM ports do not show up in the BT COM ports tab, nor is the "new outgoing port" option available, but this seems to be the way to go
People that have BT problems and they are using any WM6.1 in my opinion they must go back to WM6 and your problem is solved.
I've tried A LOT of WM6.1 and i had problems with BT. But any WM6 rom works fine to me.
I think we should wait for a WM7 (when it comes some day ) to see if the problem is solved. At the mid -time stick with WM6 imo.
I was wondering if anyone had found a way to update the crappy MS Bluetooth stack on the Mogul to the Broadcom one? I am having a lot of trouble with the bluetooth after updating to the 3.35 ROM. It keeps shutting off and it didn't on the 3.09 ROM I had before. I thought that maybe getting rid of the MS stack in favor of the Broadcom one might do the trick. Does anyone know if this is possible? I have tried several different .cab files, one for the Dell Axiom and one for the Hermes, but neither have worked right. I have also tried all of the bluetooth registry tweaks I could find and nothing helps. ANY help on this topic would be greatly appreciated!
Has there been a solution to this? The BT shutting off randomly is driving me nuts.
bump bump!
Do any of the custom rom's include the microsoft bluetooth stack instead of the widcomm htc version.
Thanks
That's exactly what I was searching for when I found this disappointingly empty thread. I'll keep searching...
It has NOT been done! And I'm almost sure that it woun't be!
I have TomTom Navigator 7.913(9189) on my Leo. It is a custom ROM using the latest shipping base & packages (3.14) and WM 6.5.3 (5.2.23152). I have a Bluetooth carkit (XCarLink) and the pairing is set up OK as far as I can see. The XCarLink has Hands-free and Stereo Audio. Playing music is fine, however the audio from TomTom is at maximum and whatever I change the volume to in TomTom it stays the same. It is so bad that there is clipping. I have changed the 'Link volume to car speed' to enabled and disabled and there is no difference.
I had the same version (same .CAB) on my Blackstone and the audio worked perfectly on this.
Any ideas?
Andy
Hi,
had a similar problem with the Mobile Navigator
I think it has something to do with HTC's own Bluetooth stack.
Strangely, it was not at all tested Costumrom's
One solution I have not found yet.
Hi!
This is just to let you know taht you are not alone. I got the very same problem on my HD2, Jabra connector and Navigator.
The problem apears just using blutooth, using the earphone jack it works flaweless.
I would appreciate any help.
Thanks
Gabriel
After a lot of searching I now understand that the BT stack on the HD2 is the Widcomm/Broadcom BT stack and this is the issue. On the Blackstone its the MS BT stack. Apparently the Broadcom stack doesn't support volume control - this is supposedly a function of the bluetooth audio device and the volume must be controlled by it. Its not part of the BT standard if I am to believe other posts? This is obviously different from how the MS stack worked as this worked perfectly on my Blackstone.
I did some research into maybe getting the MS stack transplanted back into the HD2 ROM but I never got very far with it - I assume its possible as the Windows Phone 7 ROMs for the HD2 have the MS BT Stack don't they? Plus all the HD2 Android ROMs using other drivers for the BT?
Andy