It is currently Fri Feb 23, 2018 8:47 am

rSAP for Android Forum

Support forum for Android rSAP App

S3 and Cyanogenmod 11 (kitkat 4.4.2)

Discussions about running the rSAP app on the Samsung Galaxy S III
 
Posts: 2
Joined: Fri Jan 24, 2014 12:22 pm

S3 and Cyanogenmod 11 (kitkat 4.4.2)

Post by PitarSap » Fri Jan 24, 2014 12:34 pm

Hi everybody!

I recently upgrade my SGSIII to a custom rom based on Cyanogenmod 11 (kitkat 4.4.2).

My car (AUDI A6 MMI) did stablish bluetooth connection with phone but no phonebook got to be synced.

I've installed rSap App (v.2.4.4) and updated system files. It recognizes as a GT-I9300, product "m0xx" and versiones 4.4.2

When I run the Bluetooth Phonebook (v1.1.6) I get "Ready" states both with PBAP and IrMC profiles but no matter how many times a unpair and re-pair my carkit no contacts are sent. In fact, phone never asks me to grant access to phonebook.

Am I doing something wrong? Is there something I could try?

Thanks in advance!

PD: here is the log file incase it helps:

01-24 14:52:34.690 I/ActivityManager( 5452): Timeline: Activity_idle id: android.os.BinderProxy@41bbdab8 time:6008497
01-24 14:52:47.100 I/BluetoothIrMCService( 5452): ---- SERVICE RESTARTED ----
01-24 14:52:47.105 W/BluetoothAdapter( 5452): getBluetoothService() called with no BluetoothManagerCallback
01-24 14:53:26.420 I/ActivityManager( 5452): Timeline: Activity_idle id: android.os.BinderProxy@41e3dcb8 time:6060228
01-24 14:53:33.320 I/BluetoothIrMCService( 5452): ---- SERVICE RESTARTED ----
01-24 14:53:33.320 W/BluetoothAdapter( 5452): getBluetoothService() called with no BluetoothManagerCallback
01-24 14:53:33.325 I/BluetoothPbapService( 5452): ---- SERVICE RESTARTED ----
01-24 14:53:33.330 I/BluetoothPbapService( 5452): socket_handler = PbapSocketHandlerAOSP42
01-24 14:53:33.335 W/BluetoothAdapter( 5452): getBluetoothService() called with no BluetoothManagerCallback
01-24 14:53:48.200 I/BluetoothRSAPService( 5452): ----- start Logger pb
01-24 14:53:48.215 I/MainActivity( 5452): APK version: 1.1.6
01-24 14:53:48.215 I/MainActivity( 5452): Model: GT-I9300
01-24 14:53:48.215 I/MainActivity( 5452): Product: m0xx
01-24 14:53:48.215 I/MainActivity( 5452): Version: 4.4.2
01-24 14:53:48.215 I/MainActivity( 5452): Build: cm_i9300-userdebug 4.4.2 KOT49H 028ff86477 test-keys
01-24 14:54:00.685 I/BluetoothIrMCService( 5452): ---- SERVICE RESTARTED ----
01-24 14:54:00.685 W/BluetoothAdapter( 5452): getBluetoothService() called with no BluetoothManagerCallback
01-24 14:54:00.695 I/BluetoothPbapService( 5452): ---- SERVICE RESTARTED ----
01-24 14:54:00.695 I/BluetoothPbapService( 5452): socket_handler = PbapSocketHandlerAOSP42
01-24 14:54:00.705 W/BluetoothAdapter( 5452): getBluetoothService() called with no BluetoothManagerCallback

 
Posts: 4055
Joined: Wed Mar 23, 2011 4:12 pm

Re: S3 and Cyanogenmod 11 (kitkat 4.4.2)

Post by admin » Sat Jan 25, 2014 8:38 pm

It looks like your Audi doesn't support PBAP or IrMC. When PBAP or IrMC were used you'd see a "last connected to" instead of "ready". Did it work with the stock ROM?

rSAP usually doesn't help with phonebook problems, and it looks like it also is not used by your Audi. For rSAP you'd need the carphone option, sometimes called "Bluetooth high" or in newer models "Audi connect".

 
Posts: 2
Joined: Fri Jan 24, 2014 12:22 pm

Re: S3 and Cyanogenmod 11 (kitkat 4.4.2)

Post by PitarSap » Sun Jan 26, 2014 1:21 pm

Thanks for your reply!

Actually I haven't had any problems connecting my SGS3 to my Audi carkit until I flashed a non-stock rom.

Now I doubt about whether if it used to synced my SIM contacts or the phonebook but It has always worked even without your app... just stock. Even it showed signal strenght on the car display... :(

I might go back to stock and try... :cry:

 
Posts: 4055
Joined: Wed Mar 23, 2011 4:12 pm

Re: S3 and Cyanogenmod 11 (kitkat 4.4.2)

Post by admin » Sun Jan 26, 2014 4:42 pm

Different phone makers use different Bluetooth implementations for their phones, that's why they differ. CyanogenMod is based on Android Open Source which has some well known issues, while Samsung made significant changes, sometimes for the better ;)

You may try to enter a bug at CyanogenMod. I guess you should add a HCI log with the bug report, which you can create in the developer options or with my HCI logger app. But of course it's easier to go back to the Samsung ROM if everything worked with it.


Return to Samsung Galaxy S III I9300

Who is online

Users browsing this forum: No registered users and 1 guest