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.
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.
I've been having some issues with my Tilt and my car's hands free setup (see: http://forums.wireless.att.com/cng/board/message?board.id=cingular&message.id=105410). The problems seems to lie with the Microsoft bluetooth stack on WM 6.1. HTC is no help with this issue so I want to take matters into my own hands. Is there a way to replace the default Microsoft bluetooth stack with another, more reliable compatible stack from a reliable company (not Microsoft or HTC)? I don't want to get rid of my Tilt, but I need it to work right in my car. I'm thinking of staying away from purchasing WM 6.1 smartphones because of this.
frustrated...
Wow, no one has answered my post here, at ATT, at Kenwood, or on tiltsite. HTC answered only to tell me that compatibility doesn't necessarily mean that it would work (bs). This is very frustrating. I've read post all over xda developers and the rest of the internet about tilt bluetooth problems yet no one has an answer. I've completely giving up on trying to get bluetooth to work right with any of my devices (car, computer, etc). I can't imagine buying another HTC product. Good luck to everyone else out there struggling to get bluetooth to work on their tilt while the motorola, blackberry, lg, samsung, and other phone users watch with amazement and pity. Keep fighting the good fight. Hopefully one of you will win. I've completely lost!
That's a pretty strange story you've got there, because I have zero problems with my Tilt and bluetooth pairing to all manners of devices... on a regular basis, I connect my Tilt to my car's Pioneer stereo deck, to my laptop and desktop, and to my wireless headphones and I've had little to no difficulty. Actually, the easiest pairings so far have been between my Tilt and Pioneer Stereo Deck... At least for basic features - in order for the phone book entries to show on the deck's LCD display it required an upgrade from WinMo 6.0 to 6.1 and then in the deck itself I have to manually download the contact book. But that's the only troublesome thing I have to do, which is mostly an advanced feature any way that I could live (but prefer not to) without.
Sucks that you're having problems, all I can suggest is make sure you're doing everything properly... I've had no problems I couldn't overcome with my Tilt and bluetooth capable devices, especially since Windows Mobile 6.1 came out.
Hi,
I'm having the same problems, also when disconnecting from the BT carstereo after a phonecall, the device freezes up.
Anybody found a solution for this problem yet ?
Ny the way, my car stereo is a JVC KD-BT1
GRTZ,
Niels
@k4ever: Have you checked out this thread?
http://forum.xda-developers.com/showthread.php?t=285419
From what I can tell, they've ported the Widcomm BT stack to the Hermes and TyTN, so I imagine it's not far off from the Kaiser/TyTN-II, if it doesn't already work (my BT is working fine, so I'm not too likely to mes with my phone to find out-- but I hope this helps!)
-Weasel5i2
EDIT: Here's a CAB from the newer threads of the above post:
http://rs38.rapidshare.com/files/30721150/broadcomm_bt_stack.CAB
Thanks
Wow, thanks for the replies.
@ceosion
I got it working with a Pioneer deck in Best Buy. I was actually debating buying one, but I paid $500 for my Kenwood setup. All of my other phones work with it, to include other WM phone (not from HTC). I contacted Kenwood, but I have not recieved a reply.
@Weasel5i2
I tried the Widcomm stack when I used the stock ATT rom. It completely disabled bluetooth on the Tilt. I will try it with the PDA Corner rom I'm currently using (the best!) after the holiday weekend.
Thanks again for the replies!
k4ever said:
Wow, thanks for the replies.
@ceosion
I got it working with a Pioneer deck in Best Buy. I was actually debating buying one, but I paid $500 for my Kenwood setup. All of my other phones work with it, to include other WM phone (not from HTC). I contacted Kenwood, but I have not recieved a reply....
Click to expand...
Click to collapse
I am experiencing Bluetooth connection issues between the Tytn2 and a kenwood DNX8220BT As far as I've heard from kenwood the Tytn2 is only supported with the older version of Windows Mobile (6.0)
I've also tried the Kenwood with my wife's Touch Diamond (Also HTC but other CPU, don't know about the BT radio though) but that one is also experiencing trouble. I didn't get any indication when they would have a new firmware version ready.
You did indicate that you also tried another WM phone, which version of WM does that one operate on?
@Mautje
The other WM phone was a Samsung Blackjack II running WM 5. I downgraded my Tilt to the default WM 6 Rom from ATT, but I had the same problems. I'm running the PDA Corner WM 6.1 Rom now. Does matter which ROM I use, I get the same results on the Tilt.
widcomm stack a no-go
I tried the Widcomm stack. It did not work at all. Kept getting error that "there was not enough memory to run, please reset device" or something to that nature. Could not uninstall so I had to re-flash my ROM. Back to square one.
k4ever said:
The other WM phone was a Samsung Blackjack II running WM 5. I downgraded my Tilt to the default WM 6 Rom from ATT, but I had the same problems. I'm running the PDA Corner WM 6.1 Rom now. Does matter which ROM I use, I get the same results on the Tilt.
Click to expand...
Click to collapse
To bad. I was also looking into the other roms on this forum but it wil probably not work..
Kenwood is reporting that it should work with the rom version mentioned in the compatibility sheet.
In the sheet for version 1.43 firmware there is no mention at all of a rom version just the Tytn2.. I guess that's the WM 6.0 version
Your bluetooth disconect when you use your handsfree in your car????
Then try this software: JETware Hands-Free Extension 1.31.
I have four days without disconect.
(sorry for my english).
UPDATE 27-07-2009:
Versions of JETWARE:
1.11 (ShareWare)
1.20 (ShareWare)
1.31 (ShareWare)
1.31.178 (ShareWare)
1.40 (FreeWare??)
the good: The program solutions the disconnects of the bluetooth
the bad: BUT, in my handsfree (Saab 9-3 2008), i can make a call but i cant cut a call (i must to cut the call in the phone)
and if i uninstall i lose mi contacts in the car.
It is not perfect.
Hopefully this works mate.
Gonna try now & report back later
Cheers
Hopefully this works mate.
Gonna try now & report back later
Cheers
This Works so far. Gonna keep on trying & report back shortly. Will post another thread if it continues to be successful as this needs to be seen !
Just right.
This Works.
(sorry for my english again).
Great find hcorreo. This DOES work !
Been testing for a week now and i have had ZERO disconnections.
Thankyou so much mate
How exactly does this work?
Thats the work of 6 month looking for.
Thank you.
Screen won't stay off
I loaded the extension but now my backlight won't stay off. Is there a registry fix for this? Otherwise, it looks like a great BT extension.
Problem of the light:
I have the same problem with the version 1.31.178.1.
Try with the version 1.31.
Could this issue be fixed without having to buy a third party application?
Iam using my X1 with my builtin BT handfree in my Volvo and the problems just keeps coming.
The BT logo newer disappers like ive read about in other threads but the car and the phone seems to have massive communitcation trouble. Adressbook sync like it should but when i try to call from the car, it takes about 30sec until the phone reacts. Same goes for answering. When i press my answer button it takes about 30sec again for the phone to swallow that command. Sometimes it works, but then after 20sec the car reports that it lost its connection and if iam lucky, the connection is restored automaticly by the car.
The strange thing is that ive moved from my HTC Tytn to this phone, and the HTC never had any kind of trouble. I was running WM6 on the Tytn. Could it be WM6.1 that causes the trouble or is it the hardware in the phone?
Updated first post with info of versions and more info.
flashed to EnergyRom WM6.5 and disconnect is gone too
Used to disconnect randomly after 50-80second on my car's bluetooth
I have another problem, my bluetooth headset(SE HBH DS-205) disconnecting when i use WiFI
Jet Ware is good for the bluetooth desconexion.
Someone have a idea about how can i hang a call with the JetWare installed?
Thats the only thing to be perfect...