Until recently I was using a Galaxy S3 which paired fine with my 2008 XKR, but the car wouldn't download/display the phonebook properly (names are just shown as garbage characters), so making outgoing calls was not really an option.

A few years ago I tried my S3 with a 2009 XKR at the dealership and it worked fine, phonebook and all, but the dealer told me that the 2009 bluetooth module was not compatible with my car because it even had different connectors.

I recently got a new phone (Marshall London running android lollipop 5.0.2 ), and it wont even stay paired to the car for more than about 1 second. That was the last straw so I got the bit between my teeth and have done some research. It turns out the connectors on the bluetooth modules are in fact identical all the way up to the most recent bluetooth unit, so at least you can plug them in. Whether a newer module actually works in an older car is now the question.

I collated information from several sources and determined the following mapping for XK-series VIN numbers to bluetooth module (both Jag and OEM) part numbers:

To B07046: C2P11342
B07047 to B15111: C2P12058
B15112 to B27986: C2P14821 (6w83-10D893-AG) (MY CAR)
B27987 to B32752: C2P17620 (9W83-10D893-AA)
from B32753 until some time in 2012/2013: C2P20239 (9W83-10D893-AB)
At least B34872 to B36862 has 9W83-10D893-AB
B49386 (2013 xk) has 9W83-10F845-AA)
latest?: 9W83-10F845-AA

My car came with the C2P14821 module. I just found a reasonably affordable C2P17620 module (2009+ cars, next newest unit to mine) on ebay which I have now ordered, and will let you guys know what happens after I try it in my car.

I believe that when you turn it on, the car does an audit of every module against its internal list that only the dealer can set. Apparently the car can even refuse to start if it sees a module it doesn't recognize. I'm hoping that it only checks modules on the CAN (main vehicle) bus, since the bluetooth module only connects to the MOST bus (which is only for multimedia so not going to affect safety).

I still have my old S3 in a drawer so if the new module works at all, I can also test if maybe this is at least finally a solution to the corrupted phonebook issue that many people have already experienced and asked about here.

I still think it sucks badly that we have to even try stuff like this since Jaguar are choosing to continue to ignore all our bluetooth problems.

 

OK so I think I've solved whats causing the car to keep dropping the bluetooth connection to my Marshall London phone (android lollipop 5.0.2) as soon as it connects: I think its because the phone is trying to direct audio streaming (A2DP) to the car too, and the car is basically saying "I can't do that".

I found that out because I already have the optional Jaguar Audio Connectivity Module installed, and have one of these plugged into it for streaming audio over bluetooth to the car stereo:

As long as I have the Miccus paired before I try and connect to the car, the phone sends only phone stuff to the car and only music stuff to the Miccus, and the car then keeps the phone connected just fine. Of course the car phone book is all screwed up still, just as it was with my Galaxy S3, but at least it connects now and hopefully the new jaguar bluetooth module will fix the phonebook issue.

 

Great work so far, thanks. I'm having the same issue (dropping connection) with my Android 6.0 Nexus 5X. Please let me know how you get on with the 2009+ bluetooth module.

 

Try not allowing acess to contacts. Corrected issue with my new turbo 2. Thanks doug

 

I tried that with my Nexus 5X, no joy unfortunately but thanks from me for the suggestion.

 

Everything I've found suggests at least my problem is NOT the contacts. it the A2DP (Media Audio) streaming.
The later versions of Android apparently no longer first check that the car can also support A2DP, they just presume it can, so the phone tries establishing an A2DP connection as part of the paring, and when that part fails it takes down the whole connection.
You need to stop your phone trying to send A2DP to the car. If you're lucky enough that your phone makes a "Media Audio" option checkbox visible in the car entry in the bluetooth paired devices list, you can try just unchecking that.
My phone didn't show me that option, so I had to send just A2DP ("Media audio") to another device paired first (e.g. a spare bluetooth headset), so that the phone would then only try to send "Phone Audio" (i.e. not also "Media Audio" because it is already going somewhere else) when you now pair to the car. Try this and you should find that it stays connected.

 

I found an app on the Play Store called Bluetooth Auto Connect, which appears to let you enable or disable Bluetooth profiles for each paired device (assuming I understand the functionality correctly). I used it to change the default profile to Call Audio (HSP) and also changed the list of profiles for the paired device for my car as such too, so it appears that it won't attempt to use A2DP. This didn't work for me.

Would you mind installing the app (it's free) and trying this on your car? Just curious to see if it has the same result for you.

I don't really have any A2DP devices I can use to distract the phone from trying to use it with the car but I do have a little speaker I can test it with.

Did you receive and try the new bluetooth module for the car yet?

 

Tbe bluetooth module is still winging its way from England (it just happened that the cheapest one I could find was there). I will fit it as soon as I get it, and will report back ASAP. I will also try the phone app you suggested today.

 

Tried several including that with no sucess.

 

The Nexus support forum thread (https://productforums.google.com/for...te|spell:false) has some suggestions that the imminent security update for Marshmallow has resolved Bluetooth connectivity issues for some users. That should arrive OTA soon, or factory images are available for anyone wanting to install manually (this will erase any data on your device).

I'll wait for the OTA update myself. Hopefully your 2009 bluetooth module arrives soon, I'd be interested to hear if this works and if any other improvements are seen, particularly the names in the phone book issue...

 

Update: My phone received the OTA November security update last night, no improvement with bluetooth with my car though

 

OK so I just received and test-fitted the new 2009 bluetooth module after I got back from work this evening.

With the 2009 module, My android 5 phone phone stays connected and does not drop immediately on pairing like it does with the "proper" 2008 module.

There is now a different problem though, it may actually just be some setting in my phone, but the new module is not downloading the phonebook when the phone pairs ( and because it wont stay paired long enough with to old module to even get that far, I don't know if that problem is unique to the new module or not).
The new module does display the "previous 10 calls" with the names correctly displayed, so it appears that the new module also fixes the garbled names issue.
To try and isolate the cause of the phonebook problem, I will next try pairing my old S3 phone with the new module, since with the old module it also had the garbled names issue but stayed connected and the phone book did download.

Bottom line: even though my local dealer said it would be incompatible, the new module works much better than the "proper" one and solves the "dropped connection immediately after pairing" issue with my android 5 phone. Even if I can't ever get it to download the phonebook, it is now possible to make an outgoing call if that number happens to be in the last 10 list, since that at least is displaying names correctly now.

I might try working with the local dealer next to see if my new phone pairs/works with different years of whatever used XKs they havefor sale. Partly to identify if an even newer module might work even better in my car, and also if a 2009 car (i.e. the correct car for the new module I just bought) does properly download the phonebook from my new phone. If it does, then that would strongly suggest that there actually is justification for the dealers compatibility claim.

From this experience my confidence that even the latest bluetooth module would be very likely to be compatible with my 2008 car is now pretty high, contrary to my local dealers claims.

8Bit: I also tried the Bluetooth Auto Connect app as you requested, and it didn't seem to do anything tangible. In fact since my earlier solution involving the Miccus module stopped working about the same time I installed/tried/uninstalled that app, I'm concerned that it may actually have possibly screwed my phone up in some way to a point that it now needs a factory reset.

 

Thanks for the update, that's very encouraging. I had a look on eBay just now and found a very reasonably priced listing for the latest version of those, based on your part numbers, which apparently came out of a 2012 XK so I've ordered that. If it doesn't work out I should be able to sell it on, hopefully.

It'll be next week before I get a chance to fit it but I'll post back here when I do.

 

OK Ive definately got the bit between my teeth now.
I just saw the very latest module (9W83-10F845-AA) going cheap in Germany so ordered it on the spur of the moment. When it turns up I will try it and report back.

Update: dammit they just contacted me and said they got the part number wrong, its actually the same as the module I just bought so I cancelled this order and there are no others on ebay right now.

 

Well mine (latest part, number 9W83-10F845-AA) arrived today, a day earlier than advised. I've just been out to the garage and fitted it and can confirm it works.

As a little extra bonus I wasn't expecting, I now get phone battery and signal indicators on the touch screen:



Didn't get those before, so that's nice. Also I now see names against the numbers in the recent calls list. I haven't been able to get the phone book yet but I think that may take a while to transfer and I didn't test it for long tonight so will see if that appears in due course.

TL;DR - You can fit the latest revision Bluetooth modules to an earlier X150 XK/XKR.

 

Thanks for the update, it seems that you got exactly the same result as I got with the 2009 unit. Its a shame that the (lack of) phonebook download still apparently happens with the latest module, but thanks to you it saves me from buying a newer one and then finding that out.

If we can now just figure out a solution for the (lack of) phonebook download then it seems everything will be golden.

 

8Bit Since your unit seems to work exactly like my 2009 unit which is several versions older, I wonder what the actual difference is between the module versions?
Just a thought, but does anyone know for sure if the very last XK series cars also supported bluetooth audio streaming or not?

 

My 12 vert supports Android phonebook download very well. It also supports music from my Ipod or from as "thumbdrive". I have never tried streaming music via bluetooth; my guess is that it does not.

 

As far as I know, no XK/XKR supports audio streaming over Bluetooth. If I had to guess, I'd say the module is basically just an interface between the car infotainment system and a pretty much off-the-shelf bluetooth radio adapter so the different versions will just contain more up-to-date bluetooth radio adapters as they progressed.

I managed to make a call successfully this morning using my new one, but it did drop connection to the phone as I parked up at work. It did reconnect fine however. Once I'm more comfortable that this module is going to work OK going forward I may open up the old one just to satisfy curiosity. Bit of me hopes we'll get lucky and discover that we'll find the bluetooth module is removable (say USB or PCI interface) and could be swapped out but I won't hold my breath.

Ralph, can you remember - when you get a new phone or got your car (whichever came last), did it take very long for the phone book to transfer to the car?

 

8bit - On 10 and later xks the phone book reloads each time the phone connects to the car. I don't remember what it was like in my 08. Perhaps another member can tell you if the phone book connection functions the same way as it does in the 2010 and later xks.