[SIII][V4.4.29] Connecting... but never connects :/

Discussions about running the rSAP app on the Samsung Galaxy S III
Post Reply
Scalabitan
Posts: 5
Joined: Thu Apr 03, 2014 12:05 am

[SIII][V4.4.29] Connecting... but never connects :/

Post by Scalabitan » Thu Apr 03, 2014 12:10 am

Hello,

I am trying to connect my Samsung Galaxy SIII phone to my VW Passat 2010 with rsap but I am having a problem.

The car ask for a confirmation code to connect and after I confirm the code (something like 000111222333) it changes to "Connecting" status and it stays a little bit until phone disconnects...and reconnects...once and once again.

Here a little piece of the log:

Code: Select all

----- start Logger main
04-02 22:23:07.860 I/RSAPPreferenceActivity(25883): APK version: 2.4.3 (trial)
04-02 22:23:07.860 I/RSAPPreferenceActivity(25883): RIL wrapper version: 8 Samsung Native - V2.4.1
04-02 22:23:07.860 I/RSAPPreferenceActivity(25883): Socket creator: Android API
04-02 22:23:07.860 I/RSAPPreferenceActivity(25883): Bluetooth state: STATE_LISTEN
04-02 22:23:07.860 I/RSAPPreferenceActivity(25883): SIM state: Idle
04-02 22:23:07.860 I/RSAPPreferenceActivity(25883): Model:   GT-I9300
04-02 22:23:07.860 I/RSAPPreferenceActivity(25883): Product: m0xx
04-02 22:23:07.860 I/RSAPPreferenceActivity(25883): Device:  m0
04-02 22:23:07.860 I/RSAPPreferenceActivity(25883): Version: 4.4.2
04-02 22:23:07.860 I/RSAPPreferenceActivity(25883): Build:   cm_i9300-userdebug 4.4.2 KVT49L 6c83857405 test-keys
04-02 22:23:09.295 I/ActivityManager(25883): Timeline: Activity_idle id: android.os.BinderProxy@421a99d8 time:20092656
04-02 22:24:29.385 I/ActivityManager(25883): Timeline: Activity_idle id: android.os.BinderProxy@421a99d8 time:20172745
04-02 22:24:33.680 I/ActivityManager(25883): Timeline: Activity_launch_request id:com.android_rsap.BluetoothRSAP time:20177043
04-02 22:24:34.010 I/ActivityManager(25883): Timeline: Activity_idle id: android.os.BinderProxy@425b7b70 time:20177372
04-02 22:24:35.635 I/ActivityManager(25883): Timeline: Activity_idle id: android.os.BinderProxy@421a99d8 time:20178999
04-02 22:24:54.615 D/BluetoothRSAPClient(25883): connected
04-02 22:24:54.620 D/BluetoothRSAPClient(25883): create ConnectedThread
04-02 22:24:54.625 I/BluetoothRSAPClient(25883): BEGIN mConnectedThread
04-02 22:24:54.635 D/BluetoothRSAPClient(25883): setState() STATE_LISTEN -> STATE_CONNECTED
04-02 22:24:54.635 I/BluetoothRSAPClient(25883): END mAcceptThread
04-02 22:24:54.695 I/RSAP    (25883): IN:  CONNECT_REQ(MaxMsgSize = 2048)
04-02 22:24:54.720 I/RSAP    (25883): OUT: CONNECT_RESP(ConnectionStatus = 0)
04-02 22:24:54.720 I/BluetoothRSAPPhone(25883): RIL state StateConnectingWaitPowerOff
04-02 22:24:54.720 I/BluetoothRSAPPhone(25883): BluetoothRSAPPhone.setState(Connecting)
04-02 22:24:56.060 I/BluetoothRSAPPhone(25883): RIL state StateConnected
04-02 22:24:56.060 I/BluetoothRSAPPhone(25883): BluetoothRSAPPhone.setState(Connected)
04-02 22:24:56.070 I/RSAP    (25883): OUT: STATUS_IND(StatusChange = 1)
04-02 22:24:56.105 I/RSAP    (25883): IN:  TRANSFER_ATR_REQ()
04-02 22:24:56.255 I/RSAP    (25883): OUT: TRANSFER_ATR_RESP(ResultCode = 0, ATR = {3B 9F 96 80 1F C7 80 31 E0 73 FE 21 13 67 93 18 01 02 02 01 02 51})
04-02 22:24:56.300 I/RSAP    (25883): IN:  TRANSFER_APDU_REQ(CommandAPDU7816 = {00 A4 08 0C 02 2F E2})
04-02 22:24:56.605 I/RSAP    (25883): OUT: TRANSFER_APDU_RESP(ResultCode = 0, ResponseAPDU = {90 00})
04-02 22:24:56.650 I/RSAP    (25883): IN:  TRANSFER_APDU_REQ(CommandAPDU7816 = {00 B0 00 00 0A})
04-02 22:24:56.665 I/RSAP    (25883): OUT: TRANSFER_APDU_RESP(ResultCode = 0, ResponseAPDU = {98 53 01 06 00 50 50 83 88 33 90 00})
04-02 22:24:56.705 I/RSAP    (25883): IN:  TRANSFER_APDU_REQ(CommandAPDU7816 = {00 A4 00 04 02 2F 05 00})
04-02 22:24:56.740 I/RSAP    (25883): OUT: TRANSFER_APDU_RESP(ResultCode = 0, ResponseAPDU = {62 22 82 02 41 21 83 02 2F 05 A5 09 C0 01 00 92 01 00 DE 01 00 8A 01 05 8B 03 2F 06 05 80 02 00 08 88 01 28 90 00})
04-02 22:24:56.785 I/RSAP    (25883): IN:  TRANSFER_APDU_REQ(CommandAPDU7816 = {00 B0 00 00 08})
04-02 22:24:56.790 I/RSAP    (25883): OUT: TRANSFER_APDU_RESP(ResultCode = 0, ResponseAPDU = {70 74 65 6E 66 72 64 65 90 00})
04-02 22:24:56.835 I/RSAP    (25883): IN:  TRANSFER_APDU_REQ(CommandAPDU7816 = {00 A4 00 04 02 2F 00 00})
04-02 22:24:56.865 I/RSAP    (25883): OUT: TRANSFER_APDU_RESP(ResultCode = 0, ResponseAPDU = {62 25 82 05 42 21 00 26 02 83 02 2F 00 A5 09 C0 01 00 92 01 00 DE 01 00 8A 01 05 8B 03 2F 06 03 80 02 00 4C 88 01 F0 90 00})
04-02 22:24:56.905 I/RSAP    (25883): IN:  TRANSFER_APDU_REQ(CommandAPDU7816 = {00 B2 01 04 26})
04-02 22:24:56.925 I/RSAP    (25883): OUT: TRANSFER_APDU_RESP(ResultCode = 0, ResponseAPDU = {61 21 4F 10 A0 00 00 00 87 10 02 FF FF FF FF 89 03 05 00 01 50 0D 55 53 49 4D 20 54 4D 4E 20 31 32 38 6B FF FF FF 90 00})
04-02 22:24:56.950 I/RSAP    (25883): IN:  TRANSFER_APDU_REQ(CommandAPDU7816 = {00 B2 02 04 26})
04-02 22:24:56.960 I/RSAP    (25883): OUT: TRANSFER_APDU_RESP(ResultCode = 0, ResponseAPDU = {FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 90 00})
04-02 22:24:57.050 I/RSAP    (25883): IN:  TRANSFER_APDU_REQ(CommandAPDU7816 = {00 A4 04 0C 10 A0 00 00 00 87 10 02 FF FF FF FF 89 03 05 00 01})
Can you please help me?

Thank you in advance,

admin
Site Admin
Posts: 4132
Joined: Wed Mar 23, 2011 4:12 pm

Re: [SIII][V4.4.29] Connecting... but never connects :/

Post by admin » Thu Apr 03, 2014 7:27 am

So far everything looks good. Can you please mail me a longer log (admin at ...)? Best would be an additional HCI log. Or does the log stop there?

You may also try if it is a phonebook problem by installing the trial version of my phonebook app. Sometimes problems with phonebook transfer abort the whole Bluetooth connection.

Scalabitan
Posts: 5
Joined: Thu Apr 03, 2014 12:05 am

Re: [SIII][V4.4.29] Connecting... but never connects :/

Post by Scalabitan » Sat Apr 05, 2014 6:16 pm

Hi again,

I've sent you an e-mail with the logs but did you reveived it?

I've tried to install a new ROM with android version 4.3 and 4.2 but I continue with this problem.

I will send you the complete logs (with HCI) and I appreciate any help that you could give me.

Thanks,

admin
Site Admin
Posts: 4132
Joined: Wed Mar 23, 2011 4:12 pm

Re: [SIII][V4.4.29] Connecting... but never connects :/

Post by admin » Sat Apr 05, 2014 8:10 pm

The connection always aborts when reading records from the same SIM files: 6F49 (Service Dialling Numbers) or 6F3C (SMS). I'd guess it is a "strange" SMS, maybe a binary SMS, which is causing the trouble. I'd try to delete all SMS from the SIM card.

Note that it is an SMS on the SIM card, not in the Android message store! I must confess that I don't know how to delete them with Android... Maybe you have an old phone which can handle SIM SMS?

Scalabitan
Posts: 5
Joined: Thu Apr 03, 2014 12:05 am

Re: [SIII][V4.4.29] Connecting... but never connects :/

Post by Scalabitan » Mon Apr 28, 2014 3:29 pm

Hi,

I am sorry for the late answer... Ok, I will try that!! Hope it is the problem!

As soon as I have news I'll let you know.

Best Regards,

Scalabitan
Posts: 5
Joined: Thu Apr 03, 2014 12:05 am

Re: [SIII][V4.4.29] Connecting... but never connects :/

Post by Scalabitan » Tue Apr 29, 2014 12:26 am

Hi again,

I've clean the SIM card (no contacts neither SMS) but the problem is yet the same.

I've send you once again the log hopping for any help.

Thank you very much once again.

Regards,
Luís Barreira

admin
Site Admin
Posts: 4132
Joined: Wed Mar 23, 2011 4:12 pm

Re: [SIII][V4.4.29] Connecting... but never connects :/

Post by admin » Tue Apr 29, 2014 8:11 pm

The communication still aborts while reading the SMS file - the last read entries are in fact empty. The car deliberately asks to end the connection, so there may be something wrong with the card. Did you already try a different SIM card?

Scalabitan
Posts: 5
Joined: Thu Apr 03, 2014 12:05 am

Re: [SIII][V4.4.29] Connecting... but never connects :/

Post by Scalabitan » Wed Apr 30, 2014 8:22 pm

Hi all,

Thank you for your answer admin!! Finally I have discovered the problem!

You are right, it is not a phone issue but a car issue. My car had already 2 profiles configured and my phone was the third one. Now, when I try with another phone and another SIM card the problem was exactly the same!

Although, when I create for the first time this new phone (nokia) profile, the fourth, I had to choose to delete onde other profile since the maximum profile number was reached... 3.

The problema was ... Not enough space!! After the last profile created, I try to connect the S3 again BUT this time I have deleted onde of the oldest profiles and... BINGO!!! It works perfectly!

Now, I have tried to delete the other profiles before this all history but it seems that there is no way to do it if you do not have a phone connected to the car!!

I hope that this post can help some other users and wish you the best admin, your help was great.

Best regards

Post Reply

Return to “Samsung Galaxy S III I9300”