OK new to this forum, but please assist if possible - I have an XDAIIs which I have combined with a Bluetooth GPS unit and Bluetooth headset, I am runing the latest ROM from the O2 web site and the following occurs:
with TomTom vs3 the headset will pair but fails to connect, with TomTom vs5 the headset set will pair and connect, but when I terminate a call on the road using the TT vs5 the GPS disconnects at the same time. I have tried TomTom vs 3 with the GPS driver rolled back to vs2.06 which was the concerted opinion of pocketgps.co but that to did not work. I have tried setting the XDA up for a wired conection but that to fails to work - does anyone have a TomTom nav working reliably with this device when it is combined with a Bluetooth headset, any help much appreciated as I am now considering returing the unit as not fit for the purpose it was sold to me - in anticipation many thanks Mike
I have had the same problem with TTN3 and headsets not working. The GPS pairing was not the issue. Removing TTN3 restored the link, but for some reason headsets will no longerconnect automatically.
I have tried soft and hard resets, and updated the bluetooth drivers to build 3900, but still the headsets will not connect automatically, only manually..
I have exchanged a few e-mails with the guru's at TomTom who now thick this may be a bug, but no resolution yet...
OK try this for good measure, I loaded up TomTom vs5 again yesterday, and connected up a wired GPS unit through the serial port (remove cross from check box marked "receive incoming beams" in the Ir port settings tab - in order to use serial GPS) and it works the Bluetooth headset is fine and doesn’t mess up the GPS - However before you rush out and purchase TT5 please read on. Last night I undertook a trip from Blackpool to the centre of Liverpool, approx 55 miles and about one hour in duration. The XDA required soft resetting no less than 16 times on the way there - not easy when driving !! When I got there I needed to use it as a phone and got the no noise in headset problem - note I was not using the bluetooth at this point it was back to a "normal phone" (occurs on my unit at least three times per day) - another soft reset. One other observation with the XDAIIs was its inability to charge up properly when running in the car cradle I set off with 85% in the main battery, a hour later it was down to 35% even though it was showing charging, way too many bugs in this unit for me to consider putting up with it any longer, one month on from purchasing it is going back to the shop and I don't want it repaired, or swapped for another one - I am going to go back to a standard phone that will work, I am sure under the trading standards the unit would be viewed as unable to perform the function for which it was sold - its a shame I like the design of the unit, and the functionality without having to carry around a plethora of kit, chargers, holders etc. but I will return back to my trustworthy ipaq-4700, in twelve months I have never hard reset, the XDA has had over twelve hard resets in the one month of ownership - regards all - Mike
OK appologies for the rant and rave, yesterday I took the unit back to the O2 shop who really did not want to know anything about the problems - "you only have 14 days - take it up with customer support" - which I did, first lesson if you have any problem with a new O2 unit get it back in the 14 day period. Customer support were most helpful and aventually agreed to replace the handset with an identical machine at the local shop, which proved easy (shame about 40 min on the phone but at least I got somewhere) second lesson use the support system it really does work. thirdly the shop assistant manager informed me O2 are no longer selling the XDAIIs with the TomTom package due to neumerous problems - that says something in its self. Loaded the new unit up with TT5 and used it today for navigation (3 hours), no problems with charging, GPS or phone usage all day, if this remains the case I will be a happy customer, perhaps I had indeed been supplied a faulty handset, time will tell - Mike
sinclox, if you need more advice on this one please e-mail me on [email protected]
I am sure you can get it to work - I am most impressed with my unit once the bugs were ironed out - let me know _mike
Mike,
Thanks for the offer, currently I am waiting for TTN5 upgrade to arrive until them I am unable to register TTN3 due to the TT upgrade process and so can't use TTN on the XDA.
I have dumped the O2 active interface in favour of Wisbar 2 and the XDA hasn,t locked up since.
Have you any clues as to how to get the bluetooth connection working automatically again with headsets? :?
Send me an e-mail to address previously posted on this link - Mike
Related
OK here's a strange one. Orange SPV M2000 with Navman Smart ST V3 amd a Holux GPS cradle (which uses the com port on bottom of the phone so its hard wired).
Since installing I have been through a process of elimination to find out why the software reports NO GPS DATA occasionally, especially when it had to do anything that involves loading something, i.e. a speedcam warning or voice command approaching a roundabout. Tried the lot. Disabling ports/activesync etc.
Then one day it dawned on me that it wasn't happening on a long drive North from London. The only thing that was different was I didn't have the headset plugged in!
I've tested this over the last few weeks or so, and yes, headset plugged in means loss of data from the GPS intermittently.
I installed TOM TOM 5 from a friend and low and behold it seems to be doing the same. In TOM TOM you get the signal bars at the right and they go to zero every couple of minutes then spring back up. So its not software specific.
I would have thought the supplied headset was just a good old-fashioned 'feed to the speaker or feed to the earpiece' hard connection but it would appear not to be so.
So the question is, what is the Blue Angel doing when the headset is plugged in that it isn't doing when its not?!!!
....... tumbleweed rolls by........ signs creak...... saloon doors swing......
OK, ....I know, ...I know, ....if no one has posted it probably means no one knows the answer So I'll ask, does anyone use their Blue Angel with Navman SmartST V3 who could try this with the headphones to see if its a one off or a real issue?
As a test I installed TomTom Navigator and it does the same thing.
Any thoughts appreciated.
OK guys. I know I can't force a response so I'll post findings to date. For one reason or another, I have used Navman Smart ST V3 (now returned) a 'borrowed' version of Tom Tom navigator 5 and, in an effort to remain 'legit' a version of Destinator PN. All these exhibit the same problem so I can only presume that there is a hardware issue with the Blue Angel and my GPS port (port 1). Does anyone have a clue what the BA does when you plug in the headset that could cause such a problem or pehaps even a fix?
I have an XDA IIs with TomTom 5 and a wired GPS unit.
It doesn't exhibit this fault.
The headset (wired) works just fine. I have disabled BlueTooth to get reliable telephone performance, so I can't tell what that would work like.
HTH
Steve
I am have a Vauxhall fitted with a manufactuers Bluetooth car-kit - which was working fantastically with my old Nokia phone. Now I have a XDA Orbit, which pairs fine with the car, and is setup as a Hands-free device on the Orbit. However the car and the Oribit seem to disconnect randomly, during calls, or when idle. Most times I have to reconnect to the Orbit via the carkit.
Sometimes after I have connected, and reconnected a few times it seems to get the message and retains the connection - other times, I end up just plugging in a headset and have done with it.
Any ideas?
Works on my Wizard
I'm about to switch to an Artemis so was trawling through the board...
I had similar problems with my Wizard, until I insatlled Jetware www.jetwaremobile.com - I then needed the addressbook swap script to get it to fully work.
Becasue I've blasted my ROM fairly regularly, I've never gone past the 30 day free trial yet...
Hmm, tried that - however the car bluetooth and my Orbit connect fine for about 5 - 10 seconds and then dsconnect. Tried deleting the pairings on both sides - but has no effect. Is this an issue with the ROM or Bluetooth?
If I reconnect, then again it suddenly disconnects after 5 - 10 seconds.
I think you're stuffed. Had same probelms when I had a BMW with factory fit bluetooth, would work with a Nokia but only pair and drop-out on my XDA - solution..?? never found one, changed the car. I'm using a Siemens car kit now, works fine..
I actually managed to solve it (with a little help from another friend).
Basically if cleared down the call-history (recieved/made/missed calls) and then reconnected it worked.
I am not sure if it was the number of entries in the call history that was the problem or an erroneous entry - but after that everything has been fine.
Happy days.
TangerineTractor said:
I'm about to switch to an Artemis so was trawling through the board...
I had similar problems with my Wizard, until I insatlled Jetware www.jetwaremobile.com - I then needed the addressbook swap script to get it to fully work.
Becasue I've blasted my ROM fairly regularly, I've never gone past the 30 day free trial yet...
Click to expand...
Click to collapse
Just put this onto my Orbit - after getting only a transient phonebook transfer to the BMW (would only stay there for about 30 seconds and then it would disappear), this Jetware certainly seems to fix the problem and will even allow me to read my SMS's on the car's monitor.
Only issue is that NEW SMS's (ones that come in whilst the phone is paired to the BMW) aren't flagged or readable - need to unpair/re-pair and then the new msg Icon pops up and the messages can be read.
Still, its MUCH better than it was before.
SMS on BMW
Have you tried the advanced options in jetware to tell the bmw to handle the sms alerts?
Also, does the phonebook work? If not, use the phonebookswap script from the jetware site...
I've been struggling for several months now to get my MDAC III working with my built-in car Bluetooth hands-free. The full details are below, but in short, I'm told that the system seems to work OK with Wizard, and I'm wondering what about the Wizard could be different to the Artemis (Bluetooth stack perhaps?), and if there is a difference, is there anything I can do about it?
The full issue: The system I'm trying to connect with is in a Land Rover Freelander 2 (LR2 in the US) Initial pairing was a bit hit and miss, but now I've got the the phone paired with the PTI, that's not a problem and they automatically pair whenever I start the car.
I can succesfully initiate or answer a call from the car, but the call itself isn't routed through the car's speakers/mic, it just goes through the phone as normal. However, once in a call if I select the "privacy" option on the PTI (which would normally have the effect I've already got of passing the call to the phone), and then select the "hands free" option, it does what it should and routes the call through the car. Effectively, it's as if the system starts in "privacy" mode rather than "hands free". Once I've done this once, subsequent calls work fine, routing straight through the car, but only until the ignition's turned off. The next time I start the car up I'm still paired, but calls go through the phone again.
If anyone's got any suggestions, I'd really appreciate them.
Thanks!
Try this
Had similar in a BMW...
Try www.jetwaremobile.com
Thanks, did try that but didn't seem to help, it seemed to be more geared towards additional functions like phonebook syncing rather than just getting a working connection in the first place. Maybe I'll give it another go.
Same Probleme On 207
hi,
I have the same ....
I precise that work fine with the original m650 rom, i search many hours but i found nothing, i try bluetooth toggle with no effect...
please help us !
thank for dev for everything they do !
RE
I try many combinaison so:
if i want to use my bt car kit, i'm forced to validate hands free option at every phone call...
I think it's btaudiotoggle the cause of mly problem, he is included in the aje rom...
you think it's possible ?
TangerineTractor said:
Had similar in a BMW...
Try www.jetwaremobile.com
Click to expand...
Click to collapse
Thanks TangerineTractor!
I fixed the problem I have with car kit of OPEL ANTARA using the software you said. It works disable sending Phonebooks.
I am having a similar problem with Wizard Mobile 6 cooked ROM. Before with the official O2 ROM on my Xda Mini S, it worked fine. The car would automatically recognise the phone whenever in proximity, and all calls would go through the speaker.
Now, I have to press the car kit's button (Nokia Bluetooth) each time I get in the car, to tell it to search for devices - i.e. the phone doesn't automatically announce its presence.
So, is there a different Bluetooth Stack we can try?
My Orbit works fine with my Nokia CK-7W using a B&B ROM.
Thanks, and yep that's the same car kit I have.
When you get in the car, do you have to do anything, or does the car kit automatically detect the phone? Mine doesn't since getting the Wizard Mobile 6 cooked ROM.
Do you know what Bluetooth Stack you use, and if I can download it anywhere for the Wizard?
No, just switch on the ignition key and away it goes. Also if the car kit is set as the default hands free if the phone rings it should try to connect to the car kit.
The radio I am using is 2.95.90 I have no idea what bluetooth stack it is, Tom Codin cooked the ROM, he will know.
Okay thanks. Does anyone know if the BT Stack is part of the Radio ROM? If so I'll just try a different Radio ROM.
I currently have a Diamond and TP2 with stock ROM's.
Diamond worked perfect with carkit untill i performed major ROM upgrade from htc.com. now it will connect and not reconnect on either device or carkit restart.
My TP2 behaves EXACTLY the same - connects and drops after either restarting. when connected it works fine - voice/dialing etc etc.
My car kit is a JVC KS-BTA200 connected to my KW-AVX810 head unit.
i've read all comments on google/xda's etc - well almost all! to no avail.
the devices are all set to visible obviously and all paired. ive read that a registry edit possibly fixes the issue but my TP2 & Diamond dont have the required reg strings. (that i can find!!)
i have the remote registry tool installed on my Desktop - so im ready to make changes!
please, if anyone can help i will very grateful!!
radak23 said:
I currently have a Diamond and TP2 with stock ROM's.
Diamond worked perfect with carkit untill i performed major ROM upgrade from htc.com. now it will connect and not reconnect on either device or carkit restart.
My TP2 behaves EXACTLY the same - connects and drops after either restarting. when connected it works fine - voice/dialing etc etc.
My car kit is a JVC KS-BTA200 connected to my KW-AVX810 head unit.
i've read all comments on google/xda's etc - well almost all! to no avail.
the devices are all set to visible obviously and all paired. ive read that a registry edit possibly fixes the issue but my TP2 & Diamond dont have the required reg strings. (that i can find!!)
i have the remote registry tool installed on my Desktop - so im ready to make changes!
please, if anyone can help i will very grateful!!
Click to expand...
Click to collapse
Hi, I am using my Touch Pro 2 with the same HU and Bluetooth adaptor as you but no such problem so far.
It used to have this problem then I try to connect using Window CE as the phone setup and choose another Connection Key instead of default 0000 to pair the phone with the HU.
ok, well i just tried connecting via searching for the device from the HU. it finds my device - i tap enter (to connect on HU) then it just jumps to a blue flashing 'connecting' then goes to a yellow 'error' straight away. if i select 'open' on the HU then it connects (connecting with a different ID - a number '6') but only untill i restart the HU.
also as a test i just tried an Xperia (just had one laying around LOL) and it does the exact same as mine!! ARRRRGHHH!
so im glad to say i believe it is not an HTC issue!
ok so i have an update - the problem is my HU will not pair correctly and it will not store a pairing. great.
another quick one - have found others are having trouble with their HU/adapters. thanks anyway everyone!
TP2 Bluetooth and voice dialing working fine ???
Have you tried to reset your carkit? I had the same problem after the rom-update with my TP1 and I put my carkit (Bury CC9060) back to factory settings. So I did the same this morning after I updated my TP2 and now it works just like a charm. Of course I don't know if your carkit has this possibility. Good luck, greetz Ton
'iznogoooog' - yes it work perfectly until you restart either device - 'ton66' - unfortunatley a reset is pretty much all i can do!!! eeeeek!
hopefully a reset will fix it! - i did unplug my b/tooth adapter then switch the unit on - then off then plug it back in.. didnt change anything.. oh well! will do complete re-set 2day!
BTW:
thanks so much for everyones help!
Got a questions. I am using the AVX-826 with build in Bluetooh. I want to know if you guys get the Signal Strength show on your Head unit is correct. on my unit pair with TP2. The Signal Strength indicator doesn't move. it always show the strength with my phone is connected to the unit and it stay that way.
The Battery Strength indicator does work and show the correct battery level.
I have exactly the same prob!
Hi,
I have a AXV800 and a BTA200.
My first device was a Artemis with WM6.0. No problem so far!
Then I changend to a Diamond with WM 6.1 and had the same problem as mentioned before. Now I tried my new TP2 and still the same problem.
And I tried the old Artemis again with a new 6.1 ROM and the same problem as on the other two phones.
Now I think it depends on the WM build. 6.0 seems to work 6.1 not!!!!!!!!!!
I did a reset on my AVX800 two times without luck!
I think I'm going to use a normal phone without Windows mobile for the next test!
Schelbi.
My girlfriend and I both have HTC Desires (one unbranded and one Vodafone). We recently got a 2005 BMW 5 series with the I-Drive Pro Nav system in it.
When I try to use BT to connect to the car, I can manage to pair them, but when the phone goes to connect to the car, it only connects for a few seconds and then disconnects. It then connects again and the whole thing repeats. The disconnect is frequent enough (every few seconds) to render the whole thing unusable. It also means that it isn't connected long enough to transfer the phone book.
Both our Desire's have this problem (they have different firmwares). I thought that maybe it was the car, but I put my SIM into my old Xperia X1 and it worked flawlessly with the car.
Is there a setting on the phone that needs adjusting or is it a firmware problem? I hear other people with the same car having no problems with the Desire. I've also used my Desire in a Toyota Avensis and a Vauxhall Insignia with no problems.
Any advice would be gratefully received.
tifosi256 said:
My girlfriend and I both have HTC Desires (one unbranded and one Vodafone). We recently got a 2005 BMW 5 series with the I-Drive Pro Nav system in it.
When I try to use BT to connect to the car, I can manage to pair them, but when the phone goes to connect to the car, it only connects for a few seconds and then disconnects. It then connects again and the whole thing repeats. The disconnect is frequent enough (every few seconds) to render the whole thing unusable. It also means that it isn't connected long enough to transfer the phone book.
Both our Desire's have this problem (they have different firmwares). I thought that maybe it was the car, but I put my SIM into my old Xperia X1 and it worked flawlessly with the car.
Is there a setting on the phone that needs adjusting or is it a firmware problem? I hear other people with the same car having no problems with the Desire. I've also used my Desire in a Toyota Avensis and a Vauxhall Insignia with no problems.
Any advice would be gratefully received.
Click to expand...
Click to collapse
Hi,
I know there are some issues when it comes to Bluetooth and Android, and especially car kits.
Ref (sound quality): http://code.google.com/p/android/issues/detail?id=9888
Ref (disconnections): http://code.google.com/p/android/issues/detail?id=5452
This is supposed to be a fix (I did not get it to work properly): http://forum.xda-developers.com/showthread.php?t=731626
I know that Cyanogenmod has made some changes to their kernel in 6.1 that adresses audio quality (bitpool increased), and I also think that the disconnection is adressed. I'm actually testing it for the moment (6.1RC2).
Thanks very much for your reply - very useful. The link to disconnections that you gave shows someone else with the same car as us (slightly different model) with the same issue.
It's very strange as there are people reporting no problems at all with that car/phone combination.
Unfortunately, I can't try the suggested fix as I don't want to start mucking around with my ROM.
I have a problem with my Volvo and the Desire. No disconnections, but I can't get into the phonebook, using PBAP.
Flashing a MIUI Rom works charming for the bluetooth connectivity, however I'm missing my SenseUI.
Just hoping, praying, some def will include the AOSP bluetoothstack in a SenseUI-Rom
BMW Software update
Hi
I´d try contacting your local BMW workshop, to let them do a reading on your car to establish which software version your car have.
If it´s a rather old software version your car have, I´d suggest that you have it updated.
The software update might be the answer to your problems, and can also explain why other users with the same car don´t have this issue (they might have a newer software version than you).
Remember, this phone is way newer than the car, and also the software in it.
I´d give it a try
PS: Be advised. Updating from very old software to new software might cause "in car-hardware" compatibility issues, and demand new hardware in the car (computer modules ect.), so make sure you talk over which consequences the update could have for your specific car before the update is carried out
Cheers
-Buggi- (BMW workshop foreman in Denmark)
Thanks for that advice. I'll talk to the dealership and see about software upgrades. Fingers crossed!
I have a 2008 530i and my Desire (and my other halfs) work fine, so hopefully there is some newer firmware for yours. They facelifted the cars and slightly changed the iDrive in 2007 though so fingers crossed there is an update that fixes the pre-LCI models with a Desire.
Just for reference, this is sorted out now.
My I-Drive actually broke and I had a whole new unit put in (under warranty thankfully!). Since they were doing that, I begged them for the latest software, not just for the Bluetooth module, but for the system as a whole.
Since the software upgrade, the phone stays connected and everything works great.
The only fly in the ointment is that it seems that for some reason, not all numbers of contacts (or all contacts) make it into the car's phone book (most of them do).
Anyway, for anyone else having this issue, get BMW to upgrade your BT software (or the whole system if you're brave).
I have similar problem when i try to pair the phone with volkswagen tiguan 2010, it says "your phone in not supported"