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?
Can anyone help on a resolution to keep the new XDA IIs units gprs radio allways on? I tried GB Tweak, SPB GPRS Monitor, but when the unit goes off so does the gprs. When you turn the XDAIIs back on then gprs reconnects. The bluetooth issue was fixed by going off by the newest i-mate™ PDA2k patch. This seems to be another issue with the gprs radio going off when the unit turns off. If anyone can help in this issue it would be greatly appreaciated. By the way do not install GB tweak on XDA IIs because it jacks up the audio and you have to restore or hardboot to fix that issue.
Thanks,
Mike
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!!
Hello,
I am using my Blue Angel with a Nokia BH-700 Bluetooth headset.
During random time intervals (once a day, or every hour) although the Qtek bluetooth indicator flashes the connection with the headset is lost.
I had the same problem with an old Erickson headset also.
It is very annoying because when an incoming call is coming your head set is sometimes disconnected and you have to reconnect it and answer the call.
Is anyone else having the same problem?
Thank you.
My Qtek 9090 Specs:
Windows Mobile 2003 Second Edition
Version 4.21.1088 (Build 15045.2.6.0)
ROM version: 1.40.00 WWE
ROM date: 03/10/05
Radio version: 1.15.00
Protocol version: 1337.45
ExtROM version: 1.40.148 WWE
Bluetooth for Windows CE
BT-PPC/PE Version 1.0.0 Build 3900
Guys I have a problem with my bluetooth and my dopod. It connects then disconnects.
I have also noticed that the systems unchecks the "turn on bluetooth" check box and the "make this device discoverable to other devices"
Does anyone have any ideas? I am using Windows Mobile 5 and a Parrot 3100
Guys I just read this at another forum.
"The Dopod 838 pro and WM5 have chronic problems with the bluetooth stack, which is why everyone is waiting for the new ROM to appear, which will hopefully be WM6. HTC (manufacturers of Dopod 838 pro) announced that the new ROM will fix all of the known problems"
This I learn after having a car accident (minor) in my car playing with the bluetooth and trying to get it to work. Hutchison 3g should only be selling these with a warning.
I assume there is also a problem with the JasJam as they are the same phon
Originally, my qtek 2020 had the WM2003 and I was using a SBS BF400 bluetooth hand-free headset and everything was ok.
This headset uses the 1.2 bluetooth protocol.
When I made the upgrade to WM2005, when using the headset, this was constantly connected (and not in standby) draining down the battery in less than 2 hours.
I downgraded the ROM to WM2003 SE (WindowsMobile2003SE_XDA2_2.06 from buzzdev) and this headset works perfectly.
I am wondering if this ca be a problem of bluetooth protocol: which bluetooth version WM2005 uses? Could it be V2.0 o V2.1? Theorically, it should be compatible with V1.2....
Coulf you enligthened me???
Thanks
software cant change bluetooth versions to support bluetooth 2 the hardware needs to support it
So you are telling me that this should not be a protocol problem as it is working with WM2003 and WM2003SE.
Could it be with the bluetooth stack (widcomm or microsoft)?
could be a thing about the implemetation of the stack yes