Related
Having played around with WM2003se I still find that the MS Bluetooth stack is quite silly. I have seen some posts of people claming to have the widcomm stack working with SE, but I have not yet been able to find instructions.
The important things to me are in this order:
1. Hands free (headset and car kit)
2. GPS (Falcom NAVI-1)
3. BT Activesync
Would be nice to know whether this is possible.
Respect to dcs, mamaich, sin and everyone else assiting withe the wm2003se project for Himalaya.
yes, it is working with Win2k3SE
but not really sure working with other BT device
e.g Handfree, no sound and etc
Where to find the widcomm stack
I've actually been able to get my Xda II to run the following since ROM 1.60 to my current 2.06:
1. Bluetooth Headset (Sony Ericsson / EPoX)
2. ActiveSync via Bluetooth
3. File sending and receiving from other bluetooth devices
I have no GPS, so I haven't tested this yet.
what about the hands free is it working guys?
HI!
See my new thread "BT carkits woes come to an end with 2003 SE"
regarding BT handsfree carkits.
Regards
:wink:
Hi, I have a XDA II TSM 500 (Telefonica) in Spanish versions:
rom 1.72.03 ESN
03/*15/04
1.10.00
1337.18
ext rom 1.72.102
And I have a parrot ck3100 but it doens´t work, I cant uase the parrot I have install the bt tools but nothing, bttools v10.12 and 11.00 but nothing, and the widcomm program but nothing, can someone help me?, must I upgrade the room? what rom?. Thanks
The parrot carkit is one of the few that support the BT headset profile. This profile is the only (speech) one the standard Himalaya roms support.
So . . .It should work. Afaik, you do have to configure the parrot in order to make it support the headset (instead of handsfree) profile.
I think this should be in the manual.
As from 1.72 roms there is NO NEED to use the Pocket Bluetooth Tools for these matters. Uninstall those!
The widsomm stack wont help either, because that one supports a lot of protocols, but it does not support the headset . . .
RE
Thanks but when I syncronice my XDA with parrot in the screen of parrot appear HEAD SET!! but dont appear coberture, battery, agenda, and I cant speek throught the parrot my radio versiono is 1.00, whan I configure the XDA II bluetooth I put the com4 and com5 enable is this right?, thanks.
RE
I tested It again, it puts HEADSET in the screen of parrot, whan I call from XDA II puts bluetooth headset is on but I it dosn´t work in parrot or in XDA II listen nothing, and the sincronice fails after 30 seconds, I downloaded 2 roms from here "windowsmobile2003se.exe", "RUU172601WWE.exe" must I put one of this?, thanks.
I bought a parrot driveblue, it didn't work . I called parrots office and they said me my version Rom 1.66.00 radio 1.10.00 wasn't high enough to work with driveblue, and I see that you still have the same radio 1.10.00. Isn't it that, your problem ?
Look edsub has a OS 1.72.00 and a radio 1.17.00.
If you change with your ESN by a WWE , be carefull with the country error code !
May be I'm wrong and this have nothing to see with your problem.
hi
TOMY00
PLEASE
use himegetdeviceinfo.exe on your device
and give me the informations you found on file devicedata
on windows directory on your pda
please
my device is dead
and i need the operator code from telefonica movistar
thanks
I have one of the first Parrot CK3000 which works fine with a Sony T610 mobile. I have expended hours of effort trying to get to work with an XDAI, an XDAII and a PDA2K (borrowed).
I tried Windows Mobile 2003, 2003se and various BT tools. None worked.
I upgraded my XDAII to Magneto (WM5) and BINGO! works fine now!
Petermcc said:
I have one of the first Parrot CK3000 which works fine with a Sony T610 mobile. I have expended hours of effort trying to get to work with an XDAI, an XDAII and a PDA2K (borrowed).
I tried Windows Mobile 2003, 2003se and various BT tools. None worked.
I upgraded my XDAII to Magneto (WM5) and BINGO! works fine now!
Click to expand...
Click to collapse
ck3000 here worked almost fine with MDA1, MDA2 (original) and MDA2 with wm2005. BUT no chance to change the volume of the loudspeakers. are you able to do this?
Does the WM 2005 bluetooth work properly with handsfree profile or is it like 2003 and only work with head set profile :?:
Thanks
Jon
Works perfectly with my MR Handsfree headset. Until now I could not get it working in handsfree mode. With WM2005 it is working.
Own an AUDI with the factory installed Bluetooth handsfree kit and I have never been able to pair the XDAii with it so that it works properly - incredibly unstable and never could get to work completely... been lurking this forum and others and tried lots of solutions... upgraded the OS to WM5 today and first time paired and works perfectly - even displays caller ID on the Audi instrumentation!!! Most pleased - now if only I can get the o2 GPRS connection to work
Did notice the following problems with the Bluetooth
- Com ports not recognised - seemed to have something to do with the pairing... simple reset after pairing with Audi would then allow com port assigned to BT GPS (not fully tested yet)
- Multiple pairing - device seems to want to pair more than once not sure about this one but who cares it works now
916senna said:
Does the WM 2005 bluetooth work properly with handsfree profile or is it like 2003 and only work with head set profile :?:
Click to expand...
Click to collapse
I have Ericsson's HBH-65 and WM2005 uses it as Headset only. It doesn't even call-back when I press headset button :-(((((((
Motorola HS-850...
I have a Motorola HS-850 and it works perfectly with WM2005 in Handsfree mode.
Now if I can just get it to voicedial via bluetooth...
Jabra BT250 here and Handsfree works great!!!
WM2005 is the only OS that I have had where my Jabra does what i want it to do.
Craig.
The crux is can you activate your phone through your BT headset to call any number?
No good in a BMW
I loaded 2005 and tried to pair it with my BMW, although the pairing went well and the hands free profile was selected, its no better than Sins 2003 rom.
The microphone in the car doesnt work, the speakers do. The microphone on the phone is the active one. It wont connect a call unless you try twice and you have to answer call twice before they connect.
Bugger
Jon
In the devices list, tap and hold the car kit, and select handsfree, see if this helps.
Voice dialling
The thing I find most surprising with WM2005 (and the previous versions for PPC) is the lack of hands free/car kit voice dialling. That is one thing the P910 has over WM2005 phones that emphasises that full convergence has not happened in the mind of developers... the PPC is a PDA with phone connectivity, whereas the Symbian system has taken the approach that its a phone first and foremost. With the simple addition of hands free voice dialling, WM2005 could be the first really convergent OS.
(I'm kinda hoping someone will say they have a perfect voice-dialling system in place for the XDAII with WM2005, in which case I'll gladly eat my words)
I am still very grateful for ALL those here who have helped deliver three OS upgrades to my XDA in the space of 18 months!!!
Some people are using Microsoft Voice command with Magneto and they reported it to work well.
Cheers
Pat
List of working WM2005 programs:
http://forum.xda-developers.com/viewtopic.php?t=20727
scooter said:
Own an AUDI with the factory installed Bluetooth handsfree kit and I have never been able to pair the XDAii with it so that it works properly - incredibly unstable and never could get to work completely... been lurking this forum and others and tried lots of solutions... upgraded the OS to WM5 today and first time paired and works perfectly - even displays caller ID on the Audi instrumentation!!! Most pleased - now if only I can get the o2 GPRS connection to work
Did notice the following problems with the Bluetooth
- Com ports not recognised - seemed to have something to do with the pairing... simple reset after pairing with Audi would then allow com port assigned to BT GPS (not fully tested yet)
- Multiple pairing - device seems to want to pair more than once not sure about this one but who cares it works now
Click to expand...
Click to collapse
ditto with Merc 2003 E class.
same old problem with handsfree
i also have the Motorolla HS850 and though it did work for a while it seems to be back to mic and speaker working on the device and only speaker on the headset!
so though you can hear the call on the headset the mic dosn't work but the mic on the device is active as is the speaker
has anyone else had this with 2005?
have hard reset and re loaded 2005 but without success
hmm its working again.....
this is wierd!
headset battery was low yesterday so it may be to do with that. will keep checking and see if i can spot a pattern
I'm using the latest rom on my XDA2 (WMK5_2.01a32WWE) and TT Navigator 5.21 but I just can't get my Polstar PGM-111 wired receiver working at all, I've tried all sorts of input/output port settings even disabling GPS in control panel and yet I can't get connected. Don't really want to go back to 2003 as it works no probs but I just can't get this resolved in WM5, please any help would be wonderful before I lose any more hair!!
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.