Related
Hi all,
Dunno about you guys but my new XDA2s is pretty paff when it comes to bluetooth. Scratchy sound, erratic volume, headset disconnecting randomly, poor range, etc etc.
I have used an old O2 G2 headset, a new O2 Bluetrek headset and most recently a Nextlink Bluespoon AX headset. All of them were nearly as bad as each other - except the volume on the AX is far less erattic. However, using them with my PC proved no problem so the XDA2s is at fault here!
I did find that forcing the headset to use headset mode rather than hands-free made a significant difference on the older models, however I cannot manage to force the AX to headset mode in any way (still waiting for tech support on that). The AX is let off though as its hands-free mode is as good as the headset mode on the older models, I just hope it will be even better when I force it to headset (if anyone knows how let me know!).
So - I have tried the following builds with my AX:
Radio 1.06.00 BT 3500 - BAD
Radio 1.06.00 BT 3900 - BAD
Radio 1.08.00 BT 3500 - Better volume and outgoing call, but bad for person on other end of the phone.
Radio 1.08.00 BT 3900 - Pretty much the same, small imporvement for me, no imporvement for other end of the line.
I am hoping we can keep a track of various radio and BT version in this post and try between us to figure out a good combination.
There is an extra audio dll
There is an extra audio dll for bluetooth that fixes some problems posted somewhere else in this forum.
This one fixed bluetooth headset enormous here.
I believe the dll you are talking about adds the high-quality bluetooth protocl, allowing stereo bluetooth heasets to be used for music etc. Does this make any difference to the normal bluetooth headsets though?
R
Hi,
Not sure how I got mine to work but I am using a Jabra 200 headset and it works great.
I am using a custom image of WM2003SE with the optional BT drivers and so far no problems - I found when I originally had similar issues I had to pair the headset again and then everything was okay (I noted the XDAII asked if I wanted to enable the headset support).
I get the odd problem where the headset icon disappears from the today screen but I found that its still there, just doesn't refresh so you have to tap the area and it comes to life.
The headset answers the calls after 3 rings (the headset creates beeps in time with the ringing) and when I dial the headset switches on after a second of making the call. The only thing I have noticed is that I cannot redial when pressing the button on the headset however it does hangup an existing call.
Cheers,
Godz
Hi finalzero - you say XDAII, do you mean IIs or are you using the II? My old XDAII worked fine - it is just this new XDAIIs that is giving me problems.
R
Bluetooth
Hi ,
same problem for me ,
Radio 1.08.00 BT 3900 - slightly better but not the best wit Jabra 250 V & Qtek 9090 ,
I installed BA_OEM_AudioGW CAB , downloadble somewhere around , but still problems .
When all of this will end ? Bluetooth is a nightmare !
I've had an XDA2 (several actually and got fed up of them being rubbish so insisted on an upgrade) now got XDAIIs. The bluetooth manager is aweful! Can't connect to my O2 headset, does't work well with TomTom3 and is generally crap!
Logged on to find out if anyone else is having trouble so please it's not just me, now all I need to do is find out how to fix it. I'm not a mega techie (but not too bad with the right support) and wondered if it's possible to use the bluetooth software from the XDA2?
Bluespoon AX
I have the same sort of combination Orange M2000 and Bluespoon AX and have the same nightmare sound quality - using Radio 1.04.00 and BT 3900. The AudioGW patch makes no difference (as posted above it's for headphone solutions).
Would be interested in the info you get back from Nextlink on the way to force the mode of the device if possible. Otherwise it's a complete waste of money as it crackles at both ends.
Nothing back from NextLink - have sent 2 emails. With radio 1.08 it sounds fine to me but the user on the other end reports it still quite bad. Gonna do 1.10 soon and see if that helps...
Rich
XDAIIs Bluetooth - upgrade to a Jabra 250
I had similar problems with my bluetooth Jabra 200 so I upgraded to a 250 (the black one) and I didn't have any further problems. The vibrating alert is really neat... 8)
bluespoon AX
while we're waiting for Nextlink's reply - can anyone advise me as to whether an upgrade to the Radio version (I'm only on 1.04) requires a hard reset (and full software re-build) or not? If not - are there instructions on another post that say how to do it??
Upgrading to radio ROM 1.08 or 1.10 may improve your BT performance significantly -- I updated my SX66 to 1.08 a couple weeks ago and my Bluetrek G2 headset now works much better.
Radio ROM upgrades do involve a hard reset & software re-install; this thread is devoted to the 1.10 upgrade -- there's another one in this forum for the 1.08.
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,
my Diamond works ok with my Parrot bluetooth car kit. The only thing that is really anoying me, it takes veeeery long until the Diamond has established the connection to the car kit. I have to drive for several minutes! until the Diamond connects. Before I had a Sony Ericcson phone where I did not have this problem.
Any ideas? Is this just because the Diamond is a WM phone?? Or is there a way to improve this?
Thanks
I use my diamond with a Parrot CK3300 - not sure if that is the same as yours. I only use it for handsfree since I use the Diamond's own GPS receiver. I don't have this problem - it picks up and pairs within seconds.
Have you flashed the Parrot with the latest software? I found that improved performance considerably - automatic update of contacts, user name on screen rather than phone name etc.
I use the Parrot CK3100 and the pick is almost instant; I've barely got in the car and started it up and the Parrot has picked up my Diamond. It was just as quick on my Hermes device too.
I also have a CK3100 and here's somewhat the same problem.
It connects in a few seconds, and it's usable.
But the synchronisation takes forever.....
That doesn't bother me, becouse I'm quite long in my car when driving to work...
But:
The phonebook in my CK3100 starts with the numbers wich are saved on the SIMcard.
All my friends are saved on the internal memory of the TD.
So if i want to call 'Anouk': I press 'A' on the CK3100.
It starts with the 'A' from the SIMcard.
Then I have to use the turning wheel, to scroll BACKwards to "anouk'!
So this takes a lot of time.... and is very, very unpracticle.
Someone a solution for this?
As I said before flashing the latest software onto my Parrot made it much better for syncing contacts. But I only need do it once - after that it only checks for changes. It should not be syncing each time because the Parrot should store the contacts itself.
Yep, just check the Parrot website to see what the latest update is for your particular BT device and try applying it. Saying that, I've not updated my one from factory.
Unfortunately I was not able to update my Parrot so far. I have only a CK3000 Evolution, Firmware version 5.08C. I guess I would need this special serial flash cable...
@ swissly
i have the same problems fw months ago. you have to delete the partnership's on your CK3000. press the red and the green button for more the 3 sec. (Erasing in progress) if this is done you can create a new partnership. hope that helps.
\\yoshi
swissly said:
Hi,
my Diamond works ok with my Parrot bluetooth car kit. The only thing that is really anoying me, it takes veeeery long until the Diamond has established the connection to the car kit. I have to drive for several minutes! until the Diamond connects. Before I had a Sony Ericcson phone where I did not have this problem.
Any ideas? Is this just because the Diamond is a WM phone?? Or is there a way to improve this?
Thanks
Click to expand...
Click to collapse
Hello
For all of you who have a Parrot Bluetooth car kit listen up:
When you use any phone with any Parrot Bluetooth car kits please go to the Parrot support website to flash your car kit - http://www.parrot.com/uk/support/onlinehelpguides
This will update the device with the latest firmware and as Parrot continuly add new phones to their list it is must. I did it as soon as my HTC Diamond arrived and finds it pairs/syncs within 1 - 3 seconds of switching the car on. FYI I have a Parrot MK6100 device, which supports A2DP Bluetooth audio and is mint. Previous to this I had an SPV M700 and a Parrot CK3100-something, but same thing - update it and you will find it solves the problem(s).
- PLEASE HOWEVER READ THE INSTRUCTIONS ON FLASHING - IT AIN'T HARD BUT READ IT ANYWAY!!! -
Please correct me if I'm wrong, but I still think I CANNOT UPDATE my Parrot CK3000 Evolution WITHOUT THE PARROT SERIAL CABLE!
swissly said:
Please correct me if I'm wrong, but I still think I CANNOT UPDATE my Parrot CK3000 Evolution WITHOUT THE PARROT SERIAL CABLE!
Click to expand...
Click to collapse
You are correct AFAIK. Most other Parrots can be updated easily using bluetooth, but not that one. Probably why it was cheaper than the others.
I have experienced few irritating problems with my Diamond when used in my Seat Leon 2008's stock head unit via bluetooth:
1. Phonebook is displayed always and I can call phones from there which is OK, however "Incoming Calls", "Outgoing Calls" and "Missed Calls" are not working always: sometimes I have those lists filled with the corresponding entries, sometimes all three lists are empty.
2. When I am running iGO8, the bluetooth connection gets connected and disconnected each 5 minutes or so.
3. The headset volume is really low. I didn't have that problem with my Sony Ericsson phones before.
Does anyone have any of those problems and know a solution for them?
Only thing i can say. Stock seat bluetooth is terrible. My brother has orderd a new seat and the dealer advised to choose for the pioneer mounted radio because of the known problems with the seat unit and the bluetooth functions of it.
try posting in the Accesories section, u might get more help.
marco899 said:
Only thing i can say. Stock seat bluetooth is terrible. My brother has orderd a new seat and the dealer advised to choose for the pioneer mounted radio because of the known problems with the seat unit and the bluetooth functions of it.
Click to expand...
Click to collapse
Pioneer isn't that good either, I had the Pioneer radio with Bluetooth and I couldn't get it running with my previous phone Trinity P3600 and with my Diamond it didn't work either.
Willem
I have used the stock head unit previously with simple mobile phones and it has always worked perfectly and I was very happy with the bluetooth implementation in Seat. So, I think the problem is not in the head unit (i.e. an accessory problem) but lies somewhere in the "phonebook through bluetooth" implementation in the Diamond.
Hello,
I have the same problem. I have a Skoda Octavia II (2007) with built-in bluetooth and a Diamond (ROM 2.03).
I use the iGO8, and it works fine, but the bluetooth connects and disconnects randomly in all ~5 minutes. When I shut down the iGO8 or when it runs on the background, the bluetooth works perfectly, when it runs in the foreground, the bluetooth disconnects again...
Who knows wat is this problem? Should I try a new ROM? A new radio version? A new iGO version?
CyberGene: Have you a solution for this problem? Or you use a different iGO8 or a different navi software?
Thanks,
DuckHead_
Unfortunately I didn't find any solution to the problem. To be honest, I am currently using a SonyEricsson phone and the Diamond is used by my girlfriend. We are still using iGo from within the Diamond but with no Bluetooth activated.
Thank you for the quick answer.
Why don't you just take your car into a car audio place and get them to check it out for you
I thought it so that the problem with Diamond. The BT does not work only if running the iGO...
Hi all,
Need help with my HTC Diamond. As my Pioneer car navigation, with which the diamond bluetooth functioned well, was stolen, I was advised to mount a JVC navigation system NX7000 with a detachable front in order to prevent theft. However, the HTC bluetooth dysfunctions. It connects and pairs without problems, but when the diamond goes into sleep or is switched off, it is impossible to establish a phonecall using the JVC car-unit, although it indicates that blueconnection is still valid. When I switch on the phone, even minutes later, it will eventually do the call. If I force the HTC to remain powered-on it will function normally. I am sure that this has something to do with a suspend-mode of the diamond bluetooth part and that this can be solved by the right registry tweak. I tried several tweaks that I found on the forum already but without succes. I upgraded the HTC to the latest firmware 2.03 but no improvement.
I called with HTC and they said that they know the correct registrysettings but they won't supply them because of "licence restrictions"...........
Anybody the same problem? Somebody who has the solution?
Thanks
I have exactly the same problem! Incoming calls work fine, but like you, I cannot initiate outgoing calls from the JVC unit unless the diamond is turned on fully. I there's not a fix for this, I may have to go out and buy an iphone again after selling mine to get a diamond!
there is a fix but HTC won't tell. they suggested to open a thread on this forum in order to get suggestions on the matter. and so I did. When I subsequently asked them if they would post this solution on this forum they said they would not :-(
Bluetooth problems across the board with JVC NX7000
drpellypo said:
I have exactly the same problem! Incoming calls work fine, but like you, I cannot initiate outgoing calls from the JVC unit unless the diamond is turned on fully. I there's not a fix for this, I may have to go out and buy an iphone again after selling mine to get a diamond!
Click to expand...
Click to collapse
You may not want to fall back on an iPhone with the JVC NX7000. Not to go too far off-topic here, but pairing an single iPhone works great (once I figured out the overly complicated menus). BUT...it won't let me pair a second phone (of any kind). Once the first phone is paired, all pairing menu options are greyed out ("Search" and "Open"), thereby preventing any further phones from being paired. I first need to unpair the first phone before I can pair the second one. JVC Support is comically unhelpful.
Has anyone had luck paring more than 1 phone (of any brand) with the JVC NX7000?
You are the lucky one! You can succesfully pair one phone but it works
I don't care if I can only pair one phone. I only have one phone! lol.
Hey guys!
kind of the same problem here but with the Volvo built-in bluetooth solution. Actually when the device sleeps and I initiate a call it will take some time, then the device will turn on and it will begin to dial but drops immediately. When the device is fully turned on there is no problem at all. Incoming calls work just fine. Even though it first rings on the phone and after a second or two it will ring in the car and the device will stop ringing. Which confirms that bluetooth sleeps somehow and only connects fully when the device is fully awake.
It really looks like bluetooth goes to sleep, so we need a solution which keeps bluetooth awake even if the device itself is in sleep mode.
Patrick
Exactly the problem I described. It's a sleep or suspend mode of the bluetooth that causes the dysfunction. I can pair nokias wih JVC without any functional problem, they work like a charm. It is really a HTC related problem, I tried a lot of registry tweaks suggested for similar problems in other HTC devices, but no luck so far.
Reply to Guitartng:
storing multiple bluetoothdevices in the JVC for subsequent use can be done by selecting "new device" and then go to "bluetooth setup".
Exact same issue with a Kenwood DNX 8120 double din unit.
If anyone finds out the solution, please post it here. I'll keep searching.
Good News Lads!
Well after blowing my head of trying different roms and radios got a solution.
The solution comes from JVC stereo and not from Htc diamond Phone!
You have to set special phones To Samsung E520 and then pair device with the htc diamond. It works like a charm, know I can make calls through my JVC stereo and NO MORE deep sleep of htc diamond.
Try with samsung, it work for me, if not try with other phones in special phones before pairing!
Cheers!
I just wanted to let you know that I also was able to fix my bluetooth issue by flashing stock firmware 2.03.405.3 WWE with Radio 1.09.25.23. I was previously using Dutty's V4 which is based on 2.03 afaik, but it look like Dutty tweaked something on the bluetooth stby behaviour.
Anyway, it works like a charm now and the whole calling and answering process is also much faster!