Hello!
I have one question regarding BT when connected to my carkit. Here is the situation.
I owe a Citroen C5 III with factory supplied carkit. I had an HTC touch HD, which was working excellent. Then I have swiched to HTC TP2 and here is where the problems started. The TP2 connects to my carkit with no problems, but when I make a call the phone starts to work really slowly. It take about 30seconds to hang up the call I just had. If I want to make another call the phone still works very slowly, making the call takes about 1 minute. Phone strats to work fast again as soon as I disconnect the phone from carkit.
I have tried to change the roms (a lot of them with and without manila), I have taken my car to dealershop to updtae the BT on my carkit.
I there any solution for this problem?
Is there any way I can update or. downgrade the bluetooth drivers on TP2 so there would be the old interface just like the HD had?
Thanks a lot for all your help!
leonveliki said:
Hello!
I have one question regarding BT when connected to my carkit. Here is the situation.
I owe a Citroen C5 III with factory supplied carkit. I had an HTC touch HD, which was working excellent. Then I have swiched to HTC TP2 and here is where the problems started. The TP2 connects to my carkit with no problems, but when I make a call the phone starts to work really slowly. It take about 30seconds to hang up the call I just had. If I want to make another call the phone still works very slowly, making the call takes about 1 minute. Phone strats to work fast again as soon as I disconnect the phone from carkit.
I have tried to change the roms (a lot of them with and without manila), I have taken my car to dealershop to updtae the BT on my carkit.
I there any solution for this problem?
Is there any way I can update or. downgrade the bluetooth drivers on TP2 so there would be the old interface just like the HD had?
Thanks a lot for all your help!
Click to expand...
Click to collapse
Check out this thread: http://forum.xda-developers.com/showthread.php?t=591322
On page two there is a list of the registry edits to apply to fix issues between the Widcomm bluetooth stack and bluetooth car kits.
Dwboston, thanks for your reply. It helped a lot. I did the changes as described on second page on the link you have provided. I did not find the last entry I was supposed to change.
I went on a short test drive and looks like the carkit is now working perfectly. Tomorow I will go on a trip for two days. after that I will tell if the tweak worked.
Again, thanks a lot for the help. You have no idea how you made my day.
leonveliki said:
Dwboston, thanks for your reply. It helped a lot. I did the changes as described on second page on the link you have provided. I did not find the last entry I was supposed to change.
I went on a short test drive and looks like the carkit is now working perfectly. Tomorow I will go on a trip for two days. after that I will tell if the tweak worked.
Again, thanks a lot for the help. You have no idea how you made my day.
Click to expand...
Click to collapse
I didn't have the last entry either on my Tilt 2. So far the phone is working fine with the bluetooth system in my Acura. Hopefully it keeps working.
I did some testing. Although it works fast, the address book is now not synching with the carkit. Any idea about that?
leonveliki said:
I did some testing. Although it works fast, the address book is now not synching with the carkit. Any idea about that?
Click to expand...
Click to collapse
Sorry - not sure about that one. My bluetooth system doesn't support phonebook synching.
I figured it out. When I have changed the Change SupportedFeatures to 45, I have changed decimal value. Now I have set hex value to 45 it has started to work. dwboston thanks a lot for all you help. If you ever come to Slovenia, I will buy you a cup coffe.)
Related
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.
Hello xda community!
I have a huge problem with my Hermes using Shaps Roms (latest), besides I tried all of the roms till now, and bluetooth devices!
I tried 3 devices till now:
Parrot 3200
Audi UHV
and a Sennheiser VMX 100 ear- handsfree
so first I had problems with the Audi to get a stable BT transmission without disconnect which is solved due to a rom change!
Now the problem is with picking up, or dialing.
For example BT -> Audi UHV connected!
Using phonebook to dial a number -> dialing ... it displays in the Audi -> Dialing.. and when the connection is established its shoud says connected like in phone but sometimes just shows "Hanging up.." -> while the Hermes display says connected!
And I am definitly connected to the person but I cant hear anything not on the phone or the BT Kit!
This is extremly anoying -> and not only withe the Audi, even the simple Sennheiser earphone there is exactly the same problem! or the Parrot!
The phone is not able to send correct "commands" Pick UP -> Connected -> Disconnected. I mean THIS IS A HORROR!
Its not a permanent error but it it shows quite often (6 tomes out of 10 calls) up it does it again and again till sofot reset!
Please someone help me !!!!!
PS i also tried Jetware Mobile same problem no difference ....
Greets,
fire
Out of interest, try my ROM and see if this works. I use bluetooth dialing on a car kit and it works fine for me...
CRCinAU said:
Out of interest, try my ROM and see if this works. I use bluetooth dialing on a car kit and it works fine for me...
Click to expand...
Click to collapse
ok, i will give ot a try - first without jhetware mobile and with it!
Is this problem typical or known or just affects me?
Not to sure - although I install a certain version of the BT kit that may affect your issue. I don't know if it will fix it, however I would be interested to see your results.
firefoxy said:
ok, i will give ot a try - first without jhetware mobile and with it!
Is this problem typical or known or just affects me?
Click to expand...
Click to collapse
I have used a number of Schaps ROMS and others, and I have never had a problem making or receiving calls through my car kit (a Ford).
Having said that, I have had probelms getting the car kit to access my contacts on most of them, but Schaps latest ROM worked 'straight out of the box' in every respect.
Hissing Syd said:
I have used a number of Schaps ROMS and others, and I have never had a problem making or receiving calls through my car kit (a Ford).
Having said that, I have had probelms getting the car kit to access my contacts on most of them, but Schaps latest ROM worked 'straight out of the box' in every respect.
Click to expand...
Click to collapse
interesting.. so if you dial a number the tytn sends to your ford the correct status of the calling process ?
start - call - stop ?
never had such issue:
Ford: start - stop
Hermes: start - call ...
silence on both ?
CRCinAU said:
Not to sure - although I install a certain version of the BT kit that may affect your issue. I don't know if it will fix it, however I would be interested to see your results.
Click to expand...
Click to collapse
First results:
15 minutes it works like a charm - no phonebook entries just the plain rom.
now I ll snyc with outlook and start another test!
* Stange thing is that the Audi UHV found my phonebook entries although i dind´t snyced them. Sim is empy ...
can there be something in extended rom ?
Sounds like it uses BT SAP to access the contacts on the phone. I haven't built the ROM with that in it - as I haven't until now come up with a device that actually uses SAP!
Maybe try doing a search to see if you can find a cab for BT SAP and see if that helps?
CRCinAU said:
Sounds like it uses BT SAP to access the contacts on the phone. I haven't built the ROM with that in it - as I haven't until now come up with a device that actually uses SAP!
Maybe try doing a search to see if you can find a cab for BT SAP and see if that helps?
Click to expand...
Click to collapse
First of all thanks for all the replies!!
The Audi UHV is capable to use rSAP, but I have no idea what it does and what it´s good for.
What is the difference between SAP and HFP ? I have nothing on the sim card.
Now you're getting a bit beyond my knowledge as I don't have any of these systems to test or experiment with
+1
I have had the same problems with multiple ROMs.
Trying to link a Garmin GPS, and other Hands Free devices.
Seems like a Hermes thing rather than the ROMs.
Try deleting the BT device from the Hermes, but not the device. Re-sync from the device.
Not sure if that will help, but I had weird BT problems with the 4.30 rom and that fixed it. No problems at all with the 4.31 though.
I will start some testing today and report back tonight!
Maybe it was the rsap being enabled in Shaps roms .... we will see!
The question is, should I install Jetware Mobile or not ?
It seems to be faster in syncing if I have it installed.
So far I tested it yesterday for half an hour and it worked!
Hey guys,
i was wondering if anyone was facing this problem... i have the Alpine 103BT in my car which has an inbuilt parrot bluetooth system. I have noticed that when someone calls me it shows up on the lcd on the headunit then immediately drops the call! it shows up as a missed call on my tp2... but when i call using this bluetooth system then it works like a charm!
Any idea what i can do to change this? Is there a setting i have inadvertently changed?
I would really appreciate this because this call dropping really defeats the point of hands free!
Elfangor
I've got the same problem.
Just look a few posts down the list and you'll notice my 'cry for help'.
So far though, nobody's come to the rescue.
I've been reading that our phones have a unique BT-implementation, so it could be down to a bug in that area. If more people show up having similar issue, we might know.
Until then: fingers crossed and hope for sombody to post a solution.
Great! its not just me then! I hope it gets sorted! it gets on your nerves after awhile!
That's putting it mildly.
This sucks big-time: when on a business-call you definitely don't want your headset to die in you. During any conversation, really, but blasting along the motorway it's the last thing you need.
I also have an alpine 103 bt and an htc touch(elf) with onyx rom on it.
my problem is that when i make a call either from the head unit or the phone on the head unit it stops the music, displays CALLING and then after 3 seconds it displays ------------- , resumes the music, but the phone doesnt hang up. It continues the call, shows that is stil connected but you cant hear anything.
this is really frastrating as it does this sort of thing randomly and not always.
any thoughts?
Your symptoms sound a bit different from ours so it could be a totally different problem.
We might need to be paitient until one of the experts has a simiral experience and dived into the software.
Until then, I'm baffled.
eidikos said:
I also have an alpine 103 bt and an htc touch(elf) with onyx rom on it.
my problem is that when i make a call either from the head unit or the phone on the head unit it stops the music, displays CALLING and then after 3 seconds it displays ------------- , resumes the music, but the phone doesnt hang up. It continues the call, shows that is stil connected but you cant hear anything.
this is really frastrating as it does this sort of thing randomly and not always.
any thoughts?
Click to expand...
Click to collapse
Come to think of it... i have a similar problem.. when i get an incoming call it stops the music and registers a call and just a few second later..i get the --------------, and then the music comes back...by the time i fish my phone out of the pocket ive got a missed call! havnt noticed any problems when im calling though.
i tried repairing the phone to the unit but same thing! not sure what else i could do
Similar problem (I think)
Cant get a working setup in my car kit. I have a Jaguar XF SC with bluetooth handsfree...The TP2 (TMO US) pairs and docks fine, but doesnt work well. Incoming calls dont seem to be recognized, and outbound calls will dial and communicate, but wont hangup. When I hang up from the TP2, the car kit still thinks its connected and mutes the radio until i forcebly disconnect from TP2...
arg...
I've got exactly the same problem as the original poster. Mine's a vodafone TP2 with the standard vodafone rom. I've got the Alpine 104BTi. I can make outgoing calls ok but as has been described any incoming call will show the caller ID for about 1 ring and then it hangs up the call.
I've got a Jabra BT500 which works perfectly. I am wondering whether it may be the actual firmware in the Alpine device. If you look at the phone compatibility list on the Alpine website the TP2 is not listed. It worked fine with my Kaiser and this is listed as compatible.
I emailed their tech support and they said they are waiting for their customized version of the firmware from Parrot to be updated, possibly around September. I've noticed that for the Parrot standalone devices these all list the TouchPro2 as compatible, so maybe this will be fixed.
They did mention that the firmware update may only be available through the dealers. I'll keep an eye on their website. My current firmware version is 320.
I've read some other threads somewhere that people with the vodafone rom describe having problems with bluetooth that are fixed after flashing with a different rom so may turn out to be that.
Infuriating though.
It seems to be the poor implementation of the new BT stack
I have had similar problems to those described above, my Peugeot van has inbuilt BT (uses Parrot in implementation) which just misbehaves unbelievably including hanging up the current call if a new one comes in on call waiting, phonebook access is rediculously slow and buggy.
My Jabra BT8010 disconnects at random
My Jawbone disconnects very occasionally
The stack is full of bugs and HTC must know it - I reported it on their support system and firstly fobbed off, then they said they would look into it, then the log was auto closed - very convenient way to show they are meeting targets in resolving issues.
It is poor, poor and more poor. The new WIDCOMM stack looks great but doesnt really work.
Very poor for a flagship handset and they should sort something out
I went to an Alpine delearship who suggested what ukdoc was trying to do.. basically firmware update! Are you using a different Alpine website? Because the one i go to says coming soon on the page where software updates are supposed to be. I culdnt find any connection with parrot and alpine on the parrot website!
Basically what im asking is how are you going to be getting the firmware update and could you direct me towards it!
Many thanks Mate
Elfangor
rlsxda said:
Cant get a working setup in my car kit. I have a Jaguar XF SC with bluetooth handsfree...The TP2 (TMO US) pairs and docks fine, but doesnt work well. Incoming calls dont seem to be recognized, and outbound calls will dial and communicate, but wont hangup. When I hang up from the TP2, the car kit still thinks its connected and mutes the radio until i forcebly disconnect from TP2...
arg...
Click to expand...
Click to collapse
FYI, I just upgraded the radio to "4.46.25.24 - HTC" (see http://forum.xda-developers.com/showthread.php?t=549939) and the handsfree seems better...not sure it's perfect, but it does answer and hangup now...
Upgrade Alpine CDE-104BTi firmware from 320 to 360
I have just updated the firmware in my CDE-104BTi radio to version 360
http://www.alpine-electronics.co.uk/support/bluetooth-update-software.html
This has fixed the problem of not being able to recieve incomming calls on my HTC Touch Pro 2.
dsalter said:
I have just updated the firmware in my CDE-104BTi radio to version 360
http://www.alpine-electronics.co.uk/support/bluetooth-update-software.html
This has fixed the problem of not being able to recieve incomming calls on my HTC Touch Pro 2.
Click to expand...
Click to collapse
I've just done likewise, and can also receive incoming calls at last!
Hi
I just tried updating the BT in my Alpine 104bti. The laptop connects to the headunit but the update tool don't find the connection, I've tried disabling the antivirus etc. But it don't see the connection but the connection is displayed on the laptop.
Any Ideas whats wrong ?
Cheers Gomez...
SOLVED
Tried again using a laptop with Xp on worked first time, Seems Windows 7 was causing issues.
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.
All,
I have this small issue with my HTC Desire and the Parrot CK3000 Evolution. Until now, everything works perfectly (calling, sending contacts, voice dialing, ending calls,...)
However I have one small issue. When I enter my car, and my phone is locked, the Desire will not pair with the Parrot. From the moment I activate the screen, pairing is done within a few seconds. I already tried to leave it there for half an hour, no pairing, touched the screen, pairing within a few seconds.
It looks to me like the bluetooth is not active / alive when the phone is locked (or in sleep). From the moment the pairing is done, everything works fine, also when the phone is back in lock / sleep.
Anybody has anything similar or has a solution for this? I searched the market for some kind of Bluetooth-keep-alive application, but could not really find it...
Thanks in advance,
Best regards,
Speedygerre
Small bump, nobody any idea for a solution or somekind of workaround / app?
-------------------------------------
Sent via the XDA Tapatalk App
I have a similar situation with my Audi A5 (factory BT kit).
It will connect when the phone is locked (screen off etc) but it can take anything from 1 to 10 minutes before it does connect.
Like yourself, my Desire connects immediately if the phone is not locked.
Strangely, it appears to work OK in my Mazda MX-5 which has a Kenwood DNX8220BT system (Bluetooth, SatNav, Ipod, coffee maker etc) - and the Bluetooth is a Parrot system. Having said that, I haven't used the MX-5 much since I got my Desire so it might not be a representative sample.
There is definitely something amiss though.
I have a Parrot CK 3100, and whilst I am happy to report that I do not have the same problem as you, I did have a problem syncing my contacts.
Check out this site, and download the software to udate to the latest firmware. You will need a laptop with either built in bluetooth, or a seperate bluetooth dongle.
http://www.parrot.com/uk/support/onlinehelpguides
I updated the firmware on mine, and now my contacts sync properly.
There is a good chance that updating could fix your connection problem as well.
Sorry forgot to add, that updating the kit really is a doddle, but their software is Windows 32bit ONLY and definitely no MAC!
Thans pergolesi, I hope your suggestion workshop, I will try it when I have some time one of the next days.
However I still think it has something to do with the Desire, since syncing workshop perfectly when Desire is not locked...
-------------------------------------
Sent via the XDA Tapatalk App
I don't know about the Bluetooth but I know my wifi deactivates after about 5 minutes when it's locked even though I have it set to never turn off. Maybe the Bluetooth is doing the same.
Perhaps not much help, but I sometimes play music from my Desire on my car headunit using Bluetooth streaming, and that continues to work fine when the screen goes off and the phone is locked. It also still responds to commands from the headunit (skip, pause, etc).
Once it's connected, everything works OK for me as well, it just is the connecting moment which apparently does not always work
REB1 said:
I have a similar situation with my Audi A5 (factory BT kit).
It will connect when the phone is locked (screen off etc) but it can take anything from 1 to 10 minutes before it does connect.
Like yourself, my Desire connects immediately if the phone is not locked.
Click to expand...
Click to collapse
Can I ask what year your A5 is? I've got a 2010 A3 and BT doesn't work properly with my Desire I can get it to pair, but then it will disconnect a few minutes later and the only way to reconnect seems to be to unpair/repair or switch the car off/on. When it IS working it can make calls, etc. fine - but I just can't get it to stay connected I tried my Audi dealer but they just said it's not on the Audi list and there's no update to support it, so interested to hear you got it working on your A5.
alanjrobertson said:
Can I ask what year your A5 is? I've got a 2010 A3 and BT doesn't work properly with my Desire I can get it to pair, but then it will disconnect a few minutes later and the only way to reconnect seems to be to unpair/repair or switch the car off/on. When it IS working it can make calls, etc. fine - but I just can't get it to stay connected I tried my Audi dealer but they just said it's not on the Audi list and there's no update to support it, so interested to hear you got it working on your A5.
Click to expand...
Click to collapse
My A5 is a 2008 model with SatNav and therefore MMI High. The Desire paired straight away with no problems and both the car and the phone remember each other - it just takes awhile sometimes for one or the other to realise it and connect.
I'm pretty certain that it is the phone that has the problem as I had no such problems with several Sony Ericsson phones previously.
REB1 said:
My A5 is a 2008 model with SatNav and therefore MMI High. The Desire paired straight away with no problems and both the car and the phone remember each other - it just takes awhile sometimes for one or the other to realise it and connect.
I'm pretty certain that it is the phone that has the problem as I had no such problems with several Sony Ericsson phones previously.
Click to expand...
Click to collapse
Thanks - interesting. I wonder how many different BT stacks Audi run - I was hoping they'd share some common code and therefore be updated quickly but it sounds like this isn't the case given that it's working fine on your A5. Thanks for the info though!