Hello,
I wonder if somebody can help me get to the bottom of this.
Basically, I have a TyTN II (branded as a T-Mobile MDA Vario III). I also have a Parrot 3200+ LS Colour car hands free kit.
Initially, I had a TyTN (branded as a T-Mobile MDA Vario II) and this worked fine with the Parrot. Problems began when I upgraded it to Windows Mobile 6 after an update was released by T-Mobile. What would happen is as I started the engine and the Parrot connected to the phone, it would say I was in a call even though I wasn't. It could only be resolved by rebooting the phone.
When I got the TyTN II, the problem became more frequent to the point where it was just annoying to use.
Now, this is where it gets interesting. Parrot are blaming Microsoft for this problem and aparently the problem *may* or *may not* get fixed in 6.1 which is some time off yet. It is a Bluetooth Stack issue aparently but I am not sure I believe them on this nor their attitude to if it will actually get fixed.
I am wondering if anybody knows anything more about this or any fix for it.
Best Regards,
Craig Brass
craigbrass said:
I am wondering if anybody knows anything more about this or any fix for it.
Click to expand...
Click to collapse
Install one of the 6.1 ROMs here and see if it helps?
I have this with my TyTn II and parrot 3300. It also used to happen with my Orbit.
I noticed that it only does it when a data connection is active. If I press the red button on the Parrot it clears and all is good.
Not sure if yours is the same issue.
I have a Parrot 3100, and have loads of problems! It randomly crashes, it randomly decides to want to call random people, it randomly decides to route the call through the Tytn II rather than the Parrot, and it randomly works without a problem. I emailed Parrot and got this response:
--------------------------------------------------------------------------
The HTC TyTn II is still undergoing compatibility tests with our products, thus is not listed as being compatible at present. We are currently also working closely with HTC to improve compatibility and functionality with new PDA devices running Windows Mobile 6.
I would recommend dialing out from the Parrot as opposed to using your handset as from experience this works best.
I would also recommend updating the software on your Parrot, the latest version is 4.16. To update you will need a Bluetooth enabled PC (preferably a laptop) and our Parrot update tool software. http://www.parrot.com/usa/support/downloads
--------------------------------------------------------------------------
Just noticed tonight that a new version is available for download, (4.17) so I have upgraded the Parrot and will give it a try tomorrow.
Cheers
so, was the upgrade succesfull? did it solve ur issue?
I'm also having issues using my tytn ii with the parrot ck3100. (standard firmware in it)
No, it hasn't completely. It has solved most of the problems, but it now decides to (randomly) mute incoming calls, and route the audio through the handset instead. It also decided to route the TomTom audio via the parrot! I didn't think that was possible???
I'm having some of the same sorts of problems w/ the Parrot CK3100 and my Tilt. Of course, I just go it installed last nite, so I haven't had a ton of time to play with it. I DID, however, do a long road trip today and here's what I've found.
When initiating a call from the phone, there's about a 50/50 chance that it will go thru the handset or Parrot.
One time, the Parrot locked up to a point that I had to get off at an exit and restart the engine to reset it.
I had to re-pair the phone and Parrot once, because the lost one another.
I'm running the latest AT&T ROM on my phone and latest firmware on the CK3100. I never had ANY of these problems w/ my Nokia CK-7W, but it had a REALLY annoying echo on the other end when used w/ anything but a Nokia phone.
Dan
Today, things got even stranger. As of this morning, the kit would try to initiate a phantom call every time the car was started and it connected w/ the phone.
Then, it was muting the radio for 1-2 seconds every 3 to 5 minutes - very annoying when listening to an audiobook.
As of this afternoon, both problems magically stopped. I have e-mailed Parrot tech support, but I'm not hopeful that I'll get a useful reply.
I have had so many problems with the 3200 that ,due to anger, I have broken the bracket and front screen. It mutes the radio even after the call has finished. Crashes too often. I have no audio at least half of the calls I make.
I must add that it also did this with my Trinity running WM6 but worked flawlessly with my SP5 smartphone.
I read "HTC and Parrot Announce Strategic Alliance" on the Reuters website.
How I chuckle.
Related
Hi Guys,
Recent got an XDA IIi after being with the older XDA II for over 16 Months.
But I have recently run into problems with my BT Car kit :
Motorola Bluetooth Car Kit HFW-8000.
Basically the problem is that it does not always connect to the Car Kit and when it does it will only from time to time connect and let me have a handfree conversation.
I have also used the Broadcom Bluetooth Cab file here in order to extend what Bluetooth Profiles that can be used but seems not to have any great bearing to stablize the issue.
So I went down the Hard Reset Road but again still intermittent issues, I then upgraded the ROM to the New one on the O2 Website the v 1.11.169 ROM.
I also had similar issues with the XDA II but it was resolved by using the Pocket Bluetooth tools, which was great and never once after installing it did I have any issues with the Car Kit.
http://www.bluetooth.jazztel.es/
One of my questions is, is there a similar programme to to above Pocket Bluetooth tools for the XDA IIi as I have tried it with the XDA IIi but does not work.
Or does anyone know how you would revert to have the XDA II radio or is there a work around for it.
Thanks Guys
Woody
Hi Woody_XDA,
I have had my XDA2i for a couple of months now and recently got a O2 blue headset for it, I had simular problems with the headset disconnecting and having to manually connect every time I switched it on. After browsing this wonderfull forum I decided to do a corperate install and get rid of the O2 active interface, since then no problems at all. I now use Pugs modified ROM version 162 with radio 1.04 and have no stability problems at all with no twice weekly reset. Hope this helps you and many thanks to Pug for his ROM.
Mace
Ditto, I also use the custom firmware with 1.04 radio and bluetooth works a charm. It still eats battery like nothing else, but it works with no problems. Also like the fact that the XDA can cope with my GPS receiver and my handsfree kit simultaneously, that's handy for in the car.
Cheers Guys for the information, took it on board and works great, did a great deal of stress testing in order to confirm it and works excellent..Thanks to PUG again and guys thanks for the info much appreciated and this is by far a great forum
Mace - you mention some bluetooth issues being resolved since you applied the custom ROM... I posted in the Alpine Applications forum here the other day a list of issues with bluetooth that I was wondering had been addressed - so far no reply - are these the symptoms that were cured for you??
Hi Bewlay Brother sorry, I missed your other post on Bluetooth issues, my original problem was that every time I switched on my BT headset , which is a O2 Blue, I had to open the BT manager and make the connection, the phone would then occasionally lose the connection and sometimes whilst still showing a connection refuse to transfer the call. This was using the official 162 ROM with the O2 active UI. I have since installed Pugs 162 ROM with radio1.04 and done a corporate install and BT seems to work perfectly, switch on the headset, it connects, never loses pairing and transfers calls.
Hope this helps you, and thanks again to Pug,
Mace.
Mace - what you describe sounds similar - my problems were essentially the loss of pairing with my Motorola headset a lot of the times when the XDAIIi switched off its display and went into stand-by mode, also if I closed the boom bike on the headset (to temporarily turn off the headset) it would fail to re-pair when I next opened the boom mike... the other issue was that I had to make sure the phone keyboard was displayed on the XDA once I had paired up otherwise the last number redial function on the headset would not work - if I pressed the dial button on headset and the phone display was not on the screen it would simply open the phone display function but fail to then dial the number - really crap. Also reception was poor to headset even over relatively short distances from the XDA. IF these areas in particular could be cured by the upgrade then I am eager to do it - I must admit I have read that this upgrade has not been without problems for some people here so it is going to be a tough call.
Just a thought, but have you done a personal or corporate install as I think the main fix with Pugs ROM was the upgrade to radio 1.04, which I don’t think affects the BT, so a corporate install with your existing ROM may make a difference.
Did a corporate install when it was new out of the box...
whats the difference between the corporate and personal install?
Corporate doesn't install ANY of the branded O2 interface - so no gubbins, nothing to slow down the phone, you just get a bog standard Windows Mobile 2003 SE installation, aside from the O2 GPRS and SMS settings. Bosh.
hi
i've been reading the posts and i have the same problem where can i get hold of pug's ROM if it's possible cos this seems to get rid of the problem
And then today, headset will not automatically connect, needing Bluetooth manager to be opened to make the connection. AARRRGH!
BT car kit problems
I have the 1.04 Radio, but it still won't sync with my 2003 BMW 325xi bluetooh or with my 2005 Acura MDX bluetooth.
Help!
Unstable Bluetooth Signal Strength - Samsung WEP200 Bluetooth Headset
Hi, I just got a Samsung WEP200 Bluetooth Headset. It would pair with my O2 XDAIIi but I cannot hear any voice in both incoming and outgoing calls. When I check the BT Manager, it shows a totally unstable BT strength that varies from very strong to very weak. The same headset worked well with other BT phones. My ROM version is 1.11.00 WWE, Radio version 1.04.00.
Any help would be greatly appreciated.
Hi guys,
I am at the end of my tether... I just bought a JVC head unit with on board bluetooth, so I can use it as a car kit. But I can't get my Treo 750 to pair with it! It just locks up after I enter the passkey... and the car kit just says "error" after a certain amount of time. I'm running a vanilla (extended ROM removed) version of the 3 Australia ROM.
So, I rolled back to Windows Mobile 5... same problem... UNTIL I went into the Bluetooth settings and setup an incoming COM port. Then it paired up perfectly and all was well.
So I've reinstalled WM6, but it doesn't have the option to create an incoming COM port. That's really annoying. I've googled a heap, and searched these forums a fair bit too, but haven't been able to find any sort of workaround. Is there a registry hack, third party program, or some other way I can tell it to allow an incoming connection from the car kit?
Thanks in advance!
Has anyone had any ideas on this? I have a real issue now, as I rolled back to a WM5 ROM which I found on these forums but I'm having awful problems with it - it drops calls all the time and sometimes they just go silent..... the call stays connected but I can't hear the person on the other end.
I really need to get either the original Telstra WM5 ROM, or a way of getting WM6 to work with my car kit! Any ideas... anyone??
Okay... now I really feel like I'm talking to myself but anyway.... thought I'd give an update.
After heaps of trial and error, I managed to install the Universal version of the Broadcomm bluetooth stack onto my device. And it pairs - hooray!
However... when I make a call, no sound comes through the speakers
No other version of the Broadcomm stack will run on my Treo, I just get the memory error that lots of other people have mentioned.
Chalk another person down who's royally annoyed with Palm for putting such a dodgy implementation of Bluetooth into these devices. It's my one and only bugbear to date.
I have exactly the same problem when pairing my WM6 Treo 750 to a Parrot MK6100 carkit. After entering the passcode on the Treo, the device just hangs. The carkit says it has connected succesfully, but nothing happens. After restarting it does not recognize the carkit at all.
Did you find a solution yet? I am also looking for a different Bluetooth stack that is guaranteed to work with the Treo.
Good to see I'm not the only one. No, I haven't found a solution yet unfortunately
The closest I've come is that hacked Broadcomm Bluetooth stack. My only hope is that some nice developer will help us develop something that works!
Hi Ben,
I solved my problem yesterday. I tried two suggestions.
1) Leave the passcode field blank (do not enter '0000') and press next
2) Install http://www.jetwaremobile.nl (fully functional 30-day trial)
After that pairing succeeded in a couple of seconds and all is working well. Let me know how it works out.
Thanks very much MattMax!
I had tried the Jetware software previously, and it didn't help. But I hadn't tried leaving the passkey field blank. Did that this morning... it popped up with a connection dialog asking if I wanted to allow the connection... went back to the passkey screen, I entered 0000 and away the sucker went. How simple was that!!
I just upgraded to the latest ROW2.23 WM6 ROM the other day, so I'm not sure if that made any difference either. But it's now paired and (seems to be) working well, just need to make and receive a few calls to make sure.
Thanks very much for your suggestion!
Good to hear that it worked out!
I had exactly the same experience, leaving the field blank, after that entering '0000' and it worked. I had just installed Jetware Mobile, but apparently that is not necessary for the solution.
Hello,
Just upgraded to WM6 using the official Palm upgrade (TREO750-2.23-RWE).
The Treo is unbranded and came with WM5, also an RWE ROM.
The most important issue I currently have is terrible bluetooth interaction with my car-kit. Pairing is OK, I can start or receive a call, but there is no sound. Before, with WM5 I had no issues.
Setup:
- Treo 750
- WM6 (TREO750-2.23-RWE)
- Pegeuot RD4 radio with integrated bluetooth
Any solution? Or should I downgrade to WM5? If so, how should I downgrade?
Your help is most welcome!
David
Odd... With both the Treo 750 running WM5, I had the same problem. Basically, the first 30-60 seconds of a call wouldn't sound on either the handset, or the speakers over the bluetooth connection. This was always for the first call after getting in the car. To get around it, I would get in, start up the car, and call my voicemail. Once I could hear the call on the speakers, usually 30 seconds later, I would hang up. I could then make and receive calls normally.
After upgrading to WM6, incoming calls would occasionally be very low volume. I would have to hang up and call the person back. This also happens with WM6 on my AT&T Tilt.
No fix for that one....
daupers said:
Hello,
Just upgraded to WM6 using the official Palm upgrade (TREO750-2.23-RWE).
The Treo is unbranded and came with WM5, also an RWE ROM.
The most important issue I currently have is terrible bluetooth interaction with my car-kit. Pairing is OK, I can start or receive a call, but there is no sound. Before, with WM5 I had no issues.
Setup:
- Treo 750
- WM6 (TREO750-2.23-RWE)
- Pegeuot RD4 radio with integrated bluetooth
Any solution? Or should I downgrade to WM5? If so, how should I downgrade?
Your help is most welcome!
David
Click to expand...
Click to collapse
daupers,
Just curious that this might be related. Can you post what radio version you ended up with after the upgrade to WM6?
Dropped the issue at Palm
Yesterday I sent an email to drop the issue at Palm, since I used the official upgrade on an official pristine Treo. I still have to receive an answer.
I'm wondering if I ever will receive an answer that will resolve my issue.
Did anybody else on this forum ever get help from Palm?
David
Im heaving simmilar problems with Treo 750 WM5 and Toyota original BT-HF. Repatedly the connection is established, but then lost (without warning) - and then you get no sound (or an odd "interferrence " sound). I switch the BT off, then on, connect it again and it (usually) works fine. I assume it has smthng to do with the BT firmware. No other solution so far.
Where can I find a download for the original RWE WM5 ROM?
Can anybody provide me with a link to an WM5 RWE ROM for the Treo 750 (Cheetah)?
Thanks
I did some searching and so far I discovered the following.
WM 5 supports bluetooth 1.2.
WM 6 supports bluetooth 2.0, which should be backwards compatible with 1.2.
The carkit supports 1.2, but I'm not sure if it supports 2.0.
It looks like a compatibility issue, caused by the upgrade.
Could this be the source of the problem?
D
The hardware in the 750 supports 1.2 only, WM6 is backwards compatible with 1.2. Any device that supports 2.0 will be backwards compatible with 1.2. I just upgraded to the AT&T official WM6 build and am still having the same problems as always with my Moto HF850, no voice command, only get one working connection before the bond fails and I get no audio. *sigh*
I have the same problems Treo 750V 2.18-VFE with WM6.
Car: Citroen C4 with integrated bluetooth radio.
My car connects fine to the Treo, however when I make a call or answer a call 9 out of 10 times I have no sound. Currently I have to use the wired headset.... While I have no sound the connection is intact and I cannot use the Treo itself without cancel bluotooth from the menu.
I can read the indexes of the phone, make calls by using car functionality but no sound. Also when I have sound most of the time it's after ten seconds.
Since yesterday I also have no ringer sound anymore. Palm Support gave me an update but it's not for my ROM version.
I'm affraid I have to ask Palm to swap the phone again. Currently this is number 3:-( within a few months
BT working after WM6 upgrade
Hi everybody, surprisingly, after upgrade to WM6, my BT connection with toyota original handsfree started to work, I haven´t had a single "lost connection" since. Why is that I don´t know... Just to let U know - More lucky than the others...
I Received my fourth Treo last week. I now have ringer sound again (for now).
However I still have the sound problems with using my carkit.
My car connects fine to the Treo, however when I make a call or answer a call 9 out of 10 times I have no sound.
I get the same problem with an Orange SPV M3100 (HTC TYTN) and by factory fitted bluetooth kit in my Citroen C4... It's fine using the latest Orange WM5 ROM, but upgrading to WM6 stops the car kit from working, (connects, but no sound). I asked my Citroen dealer and they advised it was a known issue with 'high end phones like Nokia running Symbian, etc'. They had no idea about when a fix might be available.
Delayed or Missing Sound
Install the sound fix. That's what is there for.
What sound fix? Can you post a link, or let me know where it is?
Support also advised me to install the sound fix.
However it only work for lower rom versions.
When you install WM6 You will have a higher rom version.
The sound fix should allready be in WM6.
I think I'll try to contact Citroen about this...
Just before my S730 died I tried to connect it with a Parrot MK 6100. It didn't work. The S730 stalled right after the connect. After 2 minutes it disconnected. Does anyone know if the S730 is compatible with this carkit? I might need to buy a new one, but I don't buy it if it isn't compatible.
can't find result for HTC S730 and MK6100:
http://www.parrot.com/usa/support/o...ompatibility/?idproduct=24&idbrand=41&etape=2
But I Have a HTC TyTN II and MK6000 and it's not really working 100%.
If I'm using navigation SW and streaming mp3 at the same time as I have to take an incoming call it'll lock up.
The Parrot do some strange after ending a call before it releases the mute function of my radio etc.
http://www.parrot.com/usa/support/o.../?idproduct=20&idbrand=41&idmodel=672&etape=3
HTC S730 works (almost good)
I bought the HTC S730 and it works fairly good. I experience the following problems:
Phone connects automatically, but A2DP needs to be connected manual. No big issue, because I seldom use the A2DP profile.
You need to pick up the phone using the Parrot's green button. Pressing the phone's button doesn't route the sound/mic through the Parrot, but leaves it on the phone (this might be done intentionally to allow private calls).
Sometimes the phone disconnects when calls are made quickly after eachother.
It's not perfect, but it works rather good. I only had very bad experiences with Windows Mobile and BT carkits, so I am already quite happy. I hope that Parrot fixes the last few flaws, but I suspect a lot of problems are in WM (or HTC).
update
You will have to flash you're parrot with latest firmware 1.3
We also did it here and now the htc S730 works although the tytn II (kaisers) don't work that fine.
Flashed my kaiser with dutty rom and now it syncs fine and i have no problems, but my collegue's with standard kaiserrom still do have problems.
This afternoon i will have a look into the other kaisers
anonymouz said:
You will have to flash you're parrot with latest firmware 1.3
Click to expand...
Click to collapse
I have firmware MK-6100 v1.03, but it isn't good. I always thought that my HTC S730 was causing the problems. However, I connected it to a built-in Audi carkit and the HTC S730 works great. I suspect it's not only the S730 that is causing the problem.
The main problem is that the S730 disconnects after finishing a phonecall.
Been reading it for a couple of months now and learned a great deal. I have a problem and was hoping some experts could point me in the right direction.
I have an '05 Acura TL. The phone will not initiate a call over the hands free if I dial from the phone. I have to dial the number, wait for the person to pick up, press the HF button on my steering wheel and say "Transfer". Then I can talk over the Bluetooth connection. There is no problem with incoming calls, only outgoing. I previously had a Samsung phone and this problem did not occur with that phone.
I am currently on WM 6.1 (the new AT&T Rom released yesterday) and had the same problem with WM 6.0. I was hoping 6.1 would solve the problem but no luck.
Any ideas on how to fix this?
Thanks in advance.
You're not the only with this same problem. I was searching right now in this forum to solve that.
When y try to call from my Parrot, is the voice recorder that inizialize in my Kaiser waiting for a voice command.
Any one have a suggestion?
Different radio?
Where would I start debugging?
I am currently using the Parrot M6100 and the Tilt with one of Dutty's ROMs. My setup will work for a while, however, due to the way my stereo is wired in my car, the Parrot does not turn off, even with the ignition off. Every so often, I have to remove the fuse to disconnect power and then it works fine for about a week. I have tried different radios, but the same result. I tried Jetware and it did not make a difference. From the testing that I have done, it points to the Parrot as being the issue. I am planning to update the firmware to see if that helps. Maybe Accura has a firmware update that could help.
If you go here: http://www.htc.com/europe/SupportDownload.aspx?p_id=13&cat=0&dl_id=60 and download the driver there, it seemed to fix the problem that I was having. I would be in the middle of the call and all the sudden it would just drop. I tried it today after installing patch and haven't had any problems.