banner.jpg

Site Feed

Site feed

Market QR Codes

Bluetooth SIM Access Profile


Bluetooth SIM Access (Trial)


Bluetooth SIM Access Install


Bluetooth Phonebook

Start Compatibility
Compatibility

Please do also check the forum for more information and user experience!


General

There are two basic causes for problems to get rSAP running with your combination of phone and car:


SIM Card

The biggest problem is the access to the SIM card. There is no standard for it in the Android programmer interface, so this is basically what makes a phone compatible or not. Check the tables below for more information.

The rSAP installer app checks for basic compatibility, when it says that your phone is not compatible, there is nothing you can do.

SIM card problems always show after Bluetooth pairing. Some car phones show an error message after pairing, some simply timeout after a few seconds, sometimes after a much longer time. When you have a SIM PIN active and you are requested to enter it, you are most probably safe.

Sometimes it may happen that a phone is compatible, but the SIM card you use does not work with rSAP for whatever reason. Please test a different SIM card (best is from a different provider). Maybe you get a working card when you request a new card from your provider, but maybe a new card has the same problems. Be sure to test your card with the trial version of the app!

When the phone is compatible there are two basic flavors of SIM card compatibility with my app:

  • Full SIM Access

The car phone can access the SIM card with no restrictions. Especially it should be no problem to establish 3G data connections. The full SIM access may make a difference on the VW Premium phone, built-in recent Audi phones and the Nokia 610/616.

  • GSM-only SIM Access

The car phone can only use the GSM application of the SIM card. This may cause restrictions or problems with car phones that try to establish 3G data connections. Especially recent Audi phones (Audi connect) do not work with this mode! Many car phones only use GSM mode, like Porsche PCM, Mercedes SAP, Audi SAP module and Opel. It does not make a difference with these.

GSM-only mode is used by the Nexus 4 and some HTC phones, like HTC Sensation, HTC One S villec2, ... All other phones support the full SIM access.

 


Bluetooth Issues

Car phones query for the rSAP profiles in two different ways

  • Only by profile ID/first entry in service class id list

VW Premium, Audi SAP adapter, Nokia 610/616, Opel, Mercedes SAP V3

  • By full service id class list and/or profile descriptor list

Porsche PCM, Mercedes SAP V2, Audi built-in, VW Premium (Golf 7)

The Android Bluetooth programming interface is only able to set a single entry in the service class id list. This makes the phone invisible for all cars that need the additional information.

Additionally the Bluetooth implementations vary heavily between different phones, sometimes even between different firmware and/or Android versions on the same phone. For some Bluetooth implementations my app is able to specify the additional data.

There are 3 major Android Bluetooth implementations that support the additional information:

  • Old Broadcom Bluetooth stack

Samsung and HTC phones before Android 4.0, some HTC phones also with Android 4.x

  • Linux BlueZ stack

AOSP 2.3-4.1 (Nexus S, Galaxy Nexus), CyanogenMod 7-10, Most Samsung and HTC phones with Android 4.0/4.1, Sony Xperia with Android 4.0

  • New Broadcom Bluetooth Stack

AOSP 4.2/4.3 (Nexus 4, Galaxy Nexus), CyanogenMod 10.1/10.2

HTC One 4.3, Samsung Galaxy S3/S4 4.2

Remember: this only makes a difference for Porsche PCM, Mercedes SAP, built-in Audi phones and the new VW Premium in the Golf 7. If your car recognizes your phone and allows pairing and entering the Bluetooth PIN (16 or 6 digit) you are not affected by this Bluetooth problem!



Phones


Samsung Phones

Most Samsung Galaxy S and Note phones support rSAP without an additional app.

Support rSAP out of the box
(with Samsung ROM
- not with AOSP ROM!)
Galaxy S GT-I9000
Galaxy S+ GT-I9001
Galaxy S II GT-I9100 (except Android 4.0.3)
Galaxy Note GT-N7000 (except Android 4.0.3)
Galaxy W GT-I8150
Galaxy S III GT-I9300 (except builds XXA???)
Galaxy S4 GT-I9505
Galaxy S4 Mini GT-I9195
Compatible
(Confirmed)

Galaxy SL GT-I9003 (not sure if it supports out of the box!)
Nexus S GT-I9020/GT-I9023
Galaxy S II GT-I9100 (Android 4.0.3)
Galaxy Note GT-N7000 (Android 4.0.3)
Galaxy Nexus GT-I9250
Galaxy S III GT-I9300 (builds XXA???)
Galaxy S III Mini GT-I8190
Galaxy Xcover 2 GT-S7710
Galaxy S Advance GT-I9070 (Android 4.x)

Maybe compatible
(Not yet confirmed. Please tell me if you could successfully run the trial app!)

 

Not compatible

Galaxy Pocket GT-S5300
Galaxy Y GT-S5360
Galaxy Mini GT-S5570
Galaxy Gio GT-S5660
Galaxy Ace GT-S5830
Galaxy Y Duos GT-S6102
Galaxy Mini 2 GT-S6500
Galaxy S DUOS GT-S7562
Galaxy S II HD LTE SHV-E120L
Galaxy S II LTE GT-I9210
Galaxy Ace 2 GT-I8160
Galaxy S Advance GT-I9070 (Android 2.x)

Samsung phones either use the old Broadcom Bluetooth stack (all phones with Android 2.3), the BlueZ stack (all phones starting with Android 4 and all CyanogenMod or MIUI ROMs) or the new Broadcom Bluetooth stack (starting with 4.2).

Do not install the rSAP app on Samsung ROMs before Android 4, where native rSAP support is already existing! After Android 4.0 my app is able to disable the built-in rSAP.

My app should work on all AOSP based ROMs, like CyanogenMod. Be careful when flashing a custom ROM because similar named devices are in fact completely different phones (e.g. i9000, i9001, i9003).

The Samsung Android 4.0.3 ROMs for the Galaxy S II and the first 4.0.4 ROMs for the Galaxy S III did not support rSAP natively. My app runs on these ROMs.

The Galaxy S II and the Galaxy Note are the only phones that support installing the rSAP system files without rooting the phone.

 


HTC Phones

For HTC phones there exist 3 basically different rSAP system files. The "native" solution only works on older, usually single core phones. On later dual-core phones the "generic" solution may work. This only supports GSM SIM access. Some recent HTC phones feature a Qualcomm CPU that is compatible with the generic Qualcomm system files. Be sure to test compatibility with your phone with the free trial version!

HTC ROMs before Android 4.0 and the recent phones use the old Broadcom Bluetooth stack. Some phones with 4.0 and 4.1 use the BlueZ stack. Starting with 4.3 the new Broadcom stack is used.

Compatible Using "Native" System Files
(Confirmed)
Magic
Hero
Legend
Wildfire
Nexus One
Desire
Desire HD
Desire Z (G2)
Wildfire S
Desire S
ChaCha
Sensation XL
One V
HD2 (Leo)
- after flashing Android!
Compatible Using "Generic" System Files (GSM-only)
(Confirmed)
Sensation
One S (ville & villec2)
One X
Desire C
Compatible Using Generic Qualcomm System Files
(Confirmed)
One S (ville, not villec2)
One (M7)
One SV
Should be compatible
(Not yet confirmed. Please tell me if you could successfully run the trial app!)

Dream
Tattoo
EVO 4G
Gratia
Incredible S
Salsa
Sensation XE

Not compatible

Explorer A310e
EVO 3D

 


Sony Phones

Sony phones may be compatible if they use the Qualcomm RIL (/system/lib/libril-qc-qmi-1.so)

Compatible
(Confirmed)
Xperia S (LT26i)
Xperia T (LT30p)
Xperia V (LT25i)
Xperia Z (C66)
Xperia Z1
Maybe compatible
(Not yet confirmed. Please tell me if you could successfully run the trial app!)
Xperia Acro S (LT26w)
Xperia Ion (LT28h)
Xperia TX (LT29i)
Not compatible Xperia P
Xperia U
Xperia Sola
Xperia Go
Xperia SP

rSAP works only on stock Sony ROMs. All CyanogenMod versions seem to have difficulties with the SIM state changes and crash when starting and/or stopping an rSAP connection.

 


LG Phones

The Nexus 4 uses a solution similar to the "generic" HTC solution, therefore it does only support GSM mode.

Support rSAP out of the box G2 (D802)
Compatible
(Confirmed)
Nexus 5 (hammerhead)
Compatible
(GSM only)
(Confirmed)
Nexus 4 (mako)
Maybe compatible
(Not yet confirmed. Please tell me if you could successfully run the trial app!)

Not compatible

 


Phones using a Qualcomm SOC

Recent phones with a Qualcomm SOC may support rSAP. This is used for the HTC one (m7), HTC One S (ville) and the Sony phones listed above. In this table I list the phones from other manufacturers.

Support rSAP out of the box Xiaomi MI2/MI2S
Compatible
(Confirmed)
Motorola Razr HD
Motorola Photon Q (XT897)
Oppo Find 5
Huawei Ascend Y300
Maybe compatible
(Not yet confirmed. Please tell me if you could successfully run the trial app!)

Not compatible Motorola Moto G

 


Car Kits


 

Here I list some reported problems with car kits.

 


Volkswagen/Skoda Premium

See here.

Some users report crashes of the car unit when syncing phonebook. The cause may be contacts with (too large?) pictures.

I created a Bluetooth Phonebook app that replaces the Phone Book Access Protocol. This does not work on ROMs with the "old" Broadcom Bluetooth stack! See compatibility page.

Older VW Premium devices only support the IrMC phone book transfer. You can use my Bluetooth Phonebook app.

 


Mercedes Benz SAP Module

The SAP V3 has problems reading the phonebook via Phone Book Access Protocol. Try the replacement mentioned in the Volkswagen section.

 


Audi

Built-in car phones have huge problems with GSM-only rSAP implementations. Please be sure to test with the free trial version!