[Deepmeister]

Just got an Android based Samsung Galaxy S but before buying it, could not find much on compatibility of Andriod phones with Audi MMI interfaces. Took the plunge anyway, and thought I would share the findings in case it helps anyone else who may be looking:

1) For BT High, the phone interface does not allow a user to enable or disable RemoteSIM mode. If you pair from the MMI, it will "find" the phone and automatically pair with RemoteSIM enabled. If you want RemoteSIM disabled, delete the pairing and then start the pairing process from the handset and "search" for the car. In the MMI Phone settings, remember to set the Bluetooth to be Visible whilst pairing, it can be set back to Hidden afterwards.

2) With BT High and RemoteSIM enabled, any contacts that are stored in the SIM card will be visible in the MMI. However, call logs such as Missed calls, Received calls, Dialled calls, etc, will be blank on the MMI screen. The SMS text messages will appear on the MMI screen but this is inconvenient as they are stored in the MMI so you cannot read them later on the phone outside the car which is the way it is designed, it is not an Android issue. The external antennas provide better signal quality but only operate on the 2G frequencies, so you will better off in areas which have good 2G signal, but worse off in areas where 3G signals exist but no 2G signal. When RemoteSIM is enabled, the phone becomes "offline" so eMail and other features cease to operate on the handset.

3) With BT High and RemoteSIM disabled, or with BT Low, the situation is more encouraging. All contacts in the phone book become visible on the MMI screen. The call logs such as Missed calls, Received calls, Dialled calls, etc, will be visible on the MMI screen. You will not see SMS messages on the MMI screen, but the messages will be in the phone to read anytime/anywhere. The phone handset antenna will be used so whilst it may be slightly less capable than the external antenna in 2G areas, it will provide coverages in areas where 3G is also available. Other phone online features such as eMail continue to work.

Nothing to do with the A5, but whilst writing, I would say that all the 5 star reviews all over the web are absolutely right, it is an awesome piece of hardware!

 

[REB_A5]

I have the HTC Desire and Telephone Prep (Low) in my A5 and as with the Samsung, I get all the info I need on the MMI.

The HTC Desire doesn't support the RSAP profile so I imagine it won't make use of all the features of Telephone Prep (High).

 

[RDStar]

I have kinda the same problem.

I used to have a HTC daimond with windows mobile and I could perfectly pair the phone and use the contacts from my phone on the MMI screen.

I have bought a Samsung galaxy S i9000 with Android, I can pair the phone adn call handsfree, but I cannot use the phonebook, so I have to use the phone for dailing and I have to look on the phone screen if someone is calling to know who it is.

As I understood there are 2 kinda bluetooth solutions, one where you only use the SIM card via bluetooth and a built-in phone of the car, the other one is using the car's bluetooth for phonebook and 'headset'

I have the 'cheap' Bluetooth option in my A5 But since it worked fine with a 3 year old windows mobile phone I guess it should work at least as good with a brand new Android phone.

 

[HAWKiS5]

It seems rSap/rSIM once was a great idee when there were not so much smart phones around.....using the external antenna, in fact completely remote access the SIM data via Bluetooth from the MMI, as if the SIM was in the car...........a great solution when using an old Nokia 6310i.

The fact that you can NOT use your smartphone anymore (for twitter, foursquare, websites, chat, RSS feeds, e-reader, music playing, navigation, etc, etc, etc) however, makes the rSap/rSIM completely useless when using a modern smartphone like the iPhone, Android, Windows Mobile, Blackberry, Symbian, etc devices all out there.

In my case, I use the built-in SIM-card reader inside the MMI (in between the 2 SD card slots) and put there a duo-sim card, and then I have the external antenna use, and still can use the smartphone whenever I (or in fact only the passengers!) need to.

Just my $0.02

 

[RDStar]

It seems rSap/rSIM once was a great idee when there were not so much smart phones around.....using the external antenna, in fact completely remote access the SIM data via Bluetooth from the MMI, as if the SIM was in the car...........a great solution when using an old Nokia 6310i.

The fact that you can NOT use your smartphone anymore (for twitter, foursquare, websites, chat, RSS feeds, e-reader, music playing, navigation, etc, etc, etc) however, makes the rSap/rSIM completely useless when using a modern smartphone like the iPhone, Android, Windows Mobile, Blackberry, Symbian, etc devices all out there.

In my case, I use the built-in SIM-card reader inside the MMI (in between the 2 SD card slots) and put there a duo-sim card, and then I have the external antenna use, and still can use the smartphone whenever I (or in fact only the passengers!) need to.

Just my $0.02

Thank you for your reply, butr the fact is that me and my wifa are using the car on a regular bases and I don't have a sim reader in between the 2 SD slots.

But it woudn't solve my problems, since my Android phone syncronise my contacts with an exchange server, so in outlook, on my phone, adn on webmail my contacts are always in sync. (As a consultant so my contacts are changing a lot.)

That was the great thing with my old windows mobile phone, the MMI was loading the contacts every time the phone get connected.
And now I just woudl like to have the same features with my Samsung andriod phone.

So if anyone here got their carkit working with their Android phone, I would love te hear how they managed it.

 

[HAWKiS5]

If you don't have the SIM slot, you probable don't have rSAP en so you have a "regular" bluetooth connection. I use also the "regular" connection with my Windows Mobile device, and then all contacts/calls/etc are synced with the MMI. If you have many contacts, the first time can take very long (20 minutes or so) so connect, and drive on and see what happens.

I remember there was a tool for Windows Mobile to get it working even better, but don't know if this exists for Android too.

 

[RDStar]

Today I was with a friend who also uses the same windows mobile phine in his BMW car kit, and it was exactly the same problem.

Using windows mobile, the phonebook download works find, using the Android phone you can use the hands-free to place calls, but the phonebook isn't available via the carkit.

So I guess I need to go looking specificly to tweak the setting or something in the android phone and it has probably nothing to do with the A5 built in car kit.

 

[HAWKiS5]

Today I was with a friend who also uses the same windows mobile phine in his BMW car kit, and it was exactly the same problem.

Using windows mobile, the phonebook download works find, using the Android phone you can use the hands-free to place calls, but the phonebook isn't available via the carkit.

So I guess I need to go looking specificly to tweak the setting or something in the android phone and it has probably nothing to do with the A5 built in car kit.

Maybe you can find your answer here:

Audi Mobile Database

For Windows Mobile you can install additional software of Jetware, maybe there is something similar for Android?

 

[Deepmeister]

If you don't have the SIM slot, you probable don't have rSAP en so you have a "regular" bluetooth connection.

Not quite. MMI 3G has the extra SIM slot. MMI 2G does not have a dash based SIM slot. MMI 2G Bluetooth High has the external antenna and Remote SIM (rSAP) whilst MMI 2G Bluetooth Low has no Remote SIM and no external antenna.

 

[HAWKiS5]

Not quite. MMI 3G has the extra SIM slot. MMI 2G does not have a dash based SIM slot. MMI 2G Bluetooth High has the external antenna and Remote SIM (rSAP) whilst MMI 2G Bluetooth Low has no Remote SIM and no external antenna.

Oops, sorry, I ment only 3G MMI (there rSAP means extra sim slot).

 

[REB_A5]

... So I guess I need to go looking specificly to tweak the setting or something in the android phone and it has probably nothing to do with the A5 built in car kit.

As I said above, my Android powered HTC Desire works perfectly in my 2008 A5 with Bluetooth low fitted (and with firmware/software updated to 5570). I haven't had to make any Android setting changes or run anything else on the phone to make it do so - it just worked as soon as I paired it to the car.

On the other hand, if Audi have changed the Bluetooth spec/software for 3G (highly likely) and it doesn't work with my HTC Desire, I'm going to be one p!ssed off A5 Sportback owner come Dec/Jan! :no:

 

[REB_A5]

Not quite. MMI 3G has the extra SIM slot. MMI 2G does not have a dash based SIM slot. MMI 2G Bluetooth High has the external antenna and Remote SIM (rSAP) whilst MMI 2G Bluetooth Low has no Remote SIMand no external antenna.

Actually, it does have an external antenna but it can only be used via the (useless) cradle system under the armrest. :thumbsdown:

 

[gruffle]

HTC Desire and 2010 MMI3G work absolutely fine for me.
Phonebook/call lists - no problem.
No tweaking - just setup pairing intially then works.

(with Bluetooth option - high option and messing around with SIM cards seems waste of time to me)

maybe bluetooth bugs in some other phones?

Now on Froyo - still good.

 

[RDStar]

HTC Desire and 2010 MMI3G work absolutely fine for me.
Phonebook/call lists - no problem.
No tweaking - just setup pairing intially then works.

(with Bluetooth option - high option and messing around with SIM cards seems waste of time to me)

maybe bluetooth bugs in some other phones?

Now on Froyo - still good.

Mayeb I'll try to update to Froyo this week and see what the result is then.

I tried to re-pair teh phone, all goes smooth nuut still the same result.

I start to think that maybe it's a Samsung prob then a Android problem. Since it seems that with a HTC it's no problem.

About the version of the MMI software, It's a 2010 A5 Sportback. Is there somewhere I can check the version number?

 

[Deepmeister]

Mayeb I'll try to update to Froyo this week and see what the result is then.

I tried to re-pair teh phone, all goes smooth nuut still the same result.

I start to think that maybe it's a Samsung prob then a Android problem. Since it seems that with a HTC it's no problem.

About the version of the MMI software, It's a 2010 A5 Sportback. Is there somewhere I can check the version number?

When you have connected, is there an icon on the lower part of the MMI screen? It will look like a mobile phone or it will look like a SIM card, just next to the signal strength icon? If you see the SIM card icon, you have connected via rSAP which is not fully supported for Address Book, Call Logs, etc. In this case, assuming you prefer normal Bluetooth with Address Books and Call Logs, delete the pairing on both the car and the phone. Wait until the car shuts off completely (usually half an hour after engine off), then attempt to pair again but from the mobile phone initiating the pairing process rather than the car. That should pair it without rSAP and you may then find better compatibility.

 

[RDStar]

When you have connected, is there an icon on the lower part of the MMI screen? It will look like a mobile phone or it will look like a SIM card, just next to the signal strength icon? If you see the SIM card icon, you have connected via rSAP which is not fully supported for Address Book, Call Logs, etc. In this case, assuming you prefer normal Bluetooth with Address Books and Call Logs, delete the pairing on both the car and the phone. Wait until the car shuts off completely (usually half an hour after engine off), then attempt to pair again but from the mobile phone initiating the pairing process rather than the car. That should pair it without rSAP and you may then find better compatibility.

Tnx for the input, I'll check this tonight. :thumbsup:

 

[RDStar]

For those who are interested I found the problem (but no solution yet.)
My samsung Galaxy S synchronise the contacts/mail/calendar with our exchange server.

If I check my contacts there is little square next to the name, this means it's a 'linked' contact.

When I create a contact manually on the phone, it's not a 'linked' contact (no small square next to the name) and that contact is then available via MMI. But the contact does not sync with our exchange server.

For now I haven't managed to 'un-link' an existing contact, nor did I manage to create a contact on the phone that then synchronize with the exchange server.

So I can conclude that it's clearly a problem with the phone.

When I get it solved (The Samsung support is terrible! Giving a very vague answer via e-mail and you cannot reply, the only way to continue to contact is to call an expensive 0900 number where you are in wait very long time.)

 

[C99]

Actually, it does have an external antenna but it can only be used via the (useless) cradle system under the armrest. :thumbsdown:

That's not truth. You can buy rSAP adapter (cradle) for phone prep low, as I did. Not cheap, but excelent - no problem with my old Nokia 6300 and current E66, external antenna works.
There was the thread about it somewhere in the forum year or 2 years ago.

 

[HAWKiS5]

Desire Z not working flawlessly...

After reading this thread, at first I was not so worried to get my HTC Desire Z connected to my Audi MMI 3G+ with BT+.

However........it seems not so easy as it sounds.......at least.........when you have lot of phone numbers in your Android phone!

The connection can be made from the MMI (search for phone) or from the HTC (search for BT devices) . Both ways make it possible to connect (after giving a pin). The only choice you have, however, is connecting as Handsfree. The rSAP option is NOT shown (not when initiating the connection from the MMI, but also not when started from the HTC).

Since, for obvious reasons, I don't want to use rSAP for my HTC, I connect the MMI as "Handsfree device".

All looks ok (you can dial numbers from the MMI or the HTC, you can speak/listen, and you see a signal bar on the MMI screen). However.......after a few minutes the BT connection is suddenly lost, and it is NOT possible to reconnect again (not from MMI and not from HTC). The only way to re-connect is to put BT on the HTC off and on again, or put the MMI/ignition off and on again. But then the same thing repeats: first there is a connection, but it is lost after few minutes!

Not really a situation to use the phone in the car.........so I really wanted to solve this and digged deeper.

I noticed that when the HTC is connected, the MMI tries to sync the phone numbers of the HTC (missed, dialed, answered calls and contacts). You see a sync symbol in the top of the MMI screen. Then, on the HTC you get a message: "Audi MMI wants to access your contact lists, do you Allow or Deny?".........since you want to use the numbers in the MMI, of course I chose Allow. And there it went wrong!!!

The MMI can "only" store 2000 numbers per connected phone (and max 5000 numbers over a maximum of 4 "paired phones"). I have less than 2000 contacts, so this went ok when connecting my previous HTC (Touch Pro, WM6.1), where every contact was shown in the MMI with one or more numbers (and adresses, so you could navigate to your contacts too!).

With the HTC Desire Z (Android 2.2/Froyo) however, all numbers from 1 HTC contact, are stored as a separate contact in the MMI, so if somebody has a phone number for work, house and car, this means 3 contacts in the MMI with the same name. Not very convenient and because of this for example "only" 666 HTC contacts (with an average of 3 phone numbers per contact) can be stored in the MMI this way.

Assuming you don't care about this maximum, the problems are not over, because.........if you connect a phone to the MMI that has more (than 2000 phone numbers), it will connect, and even tries to sync these 2000 numbers, but when the maximum is reached, it disconnects (without any error) and you are left with a non-connected phone

Don't know how to really solve this, but there might be some workaround (e.g. by only syncing the most important contacts, but you can not select this in the MMI or the HTC, on WM 5/6 this was possible using the Jetware tool!).

Happily I found a way to be able to at least use the phone in the car, despite this "bug" and that is by selecting Deny (and NOT Allow) when the HTC is asking for your permission that the MMI will access its contact list. You have to Deny 5-6 times, but then, after few minutes, the sync symbol on the MMI screen disappears, and the HTC stays connected! And even more strange: then you have all missed/dialed/answered calls AND 2000 numbers accessible in the MMI (so much for Denying access........!?). How many (and which) numbers did NOT sync into the MMI is totally unclear, so it is not a real solution, but it works for me now.

Another way might be to use an SD card to import Outlook contacts (then 1 contact can have multiple numbers again, AND the naviation addresses will be included again, something that is apparantly NOT possible now with Android....).

So much for BT compatibility accross different platforms..... :ninja2:

 

[pparrett]

This is really strange. I'm using a Samsung Fascinate from Verizon and It will pair and start to connect but will drop immediately. I see the loading icon at the top of the MMI screen but it never asks for the permission to download contacts. I might try to update the phone software and see what happens.