It is currently Fri Sep 21, 2018 12:04 pm

rSAP for Android Forum

Support forum for Android rSAP App

LG G2 and rsap

Discussions about running the rSAP app on the LG G2/G3
 
Posts: 26
Joined: Sun Jun 05, 2011 9:58 pm

Re: LG G2 and rsap

Post by sea68 » Thu Jun 05, 2014 2:12 pm

the customer of LG replied me that the profiles bt LG g2 are: A2DP, AVRCP, FTP, GAP, HFP, HID, HSP, OPP, PAN, PBAP, PBA. There isn't rsap !! ??? is there a solution? tks

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

Re: LG G2 and rsap

Post by admin » Fri Jun 06, 2014 9:58 pm

It looks like LG added rSAP "accidently". I guess they bought the baseband and phone software from Qualcomm and simply left rSAP enabled. So maybe LG wrecked something with the update, although others report that 4.4 works fine (in German: viewtopic.php?f=64&t=1272)

 
Posts: 26
Joined: Sun Jun 05, 2011 9:58 pm

Re: LG G2 and rsap

Post by sea68 » Sat Jun 07, 2014 3:08 pm

Excuse me , why your app should not be? It should work, how do I see in the software if there is rSAP, and what is missing?

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

Re: LG G2 and rsap

Post by admin » Sat Jun 07, 2014 5:51 pm

Maybe there is a misunderstanding: rSAP works with a G2 without my app. This seems to be an undocumented feature, because LG doesn't list rSAP as a supported Bluetooth profile, as you learned from LG support. Nevertheless It's there!

If it does no longer work for you, it is most probably a problem limited to you and maybe other users, since it works for some. That's why I thought my phonebook app can fix it. If not you may still try a different SIM card.

My app most probably does not work because LG uses a different interface for the radio software. My software assumes the "standard" interface and crashes. This is all guessing from your description, I didn't have the opportunity to check a G2 myself.

You can do one more thing to find out what goes wrong: please try to create a "HCI snoop log" or a HCI log with my logger app and mail it to admin at ... The only thing is, we may learn what goes wrong, but you will most probably be unable to fix it :(

 
Posts: 10
Joined: Wed Jan 29, 2014 9:02 pm

Re: LG G2 and rsap

Post by ccatorze » Sun Jun 08, 2014 3:18 am

I'm confused ...
Can anyone confirm if the RSAP actually continues working with KitKat 4.4.2 ??

I was to buy a LG G2... but...

thanks

 
Posts: 26
Joined: Sun Jun 05, 2011 9:58 pm

Re: LG G2 and rsap

Post by sea68 » Mon Jun 09, 2014 10:39 am

I hope to have made ​​a successful log, I used logcat, I ask you to tell me if you need some more logs. thanks06-09 10:10:24.692 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:24.792 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:24.882 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:24.992 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:25.062 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:25.142 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:25.212 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:25.312 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:25.442 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:50.892 D/BluetoothSAPServiceJni(1377): connection_state_callback(L102): state:0
06-09 10:10:50.902 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 0
06-09 10:10:50.942 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 2
06-09 10:10:52.201 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 5
06-09 10:10:52.251 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:52.391 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:52.491 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:52.561 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:52.632 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:52.711 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:52.862 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:53.032 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:53.092 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:53.182 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:53.242 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:53.292 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:53.352 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:53.412 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:53.511 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:53.581 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:53.652 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:53.731 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:53.812 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:53.911 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:54.012 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:54.112 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:54.232 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:54.372 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:54.442 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:54.522 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:54.612 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:54.752 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:54.832 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:54.922 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:55.022 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:55.121 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:55.181 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:55.241 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:55.291 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:55.341 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:55.441 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:55.581 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:55.641 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:55.701 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:55.751 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:55.811 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:55.881 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:56.111 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:56.181 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:56.311 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:56.441 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:57.141 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:10:57.601 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:11:01.161 D/BluetoothSAPServiceJni(1377): client_request_callback(L127): client_request_callback: Req type 6
06-09 10:11:08.731 I/BluetoothSAPServiceJni(8829): classInitNative(L170): succeeds
06-09 10:11:08.731 D/BluetoothSAPServiceJni(8829): initializeNative(L175): sap

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

Re: LG G2 and rsap

Post by admin » Mon Jun 09, 2014 11:00 am

This is a log of the built-in LG rSAP, it doesn't help, but it shows that LG rSAP is still there. You should try to create a "HCI" log, either from inside the Android developer settings (tap 7 times on build number to enable them) or with my logger app from Play Store. Be sure to start logging before you switch on the car, and end before you send the log. And don't run my rSAP app while making tests! Please mail the log to admin at ... instead of posting them here for all to read.

 
Posts: 26
Joined: Sun Jun 05, 2011 9:58 pm

Re: LG G2 and rsap

Post by sea68 » Mon Jun 09, 2014 11:27 am

Options on a developer I flagged the file creation HCL before connection and then I took off after dil flag, you do it this way? Where can I find the file hcl created? What is the location to the SD? I'm sorry but I'm not very good at it!

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

Re: LG G2 and rsap

Post by admin » Mon Jun 09, 2014 12:52 pm

I can't remember the exact filename, but it's something with "hci" and "snoop" and it's stored on the USB/SD memory.

 
Posts: 26
Joined: Sun Jun 05, 2011 9:58 pm

Re: LG G2 and rsap

Post by sea68 » Mon Jun 09, 2014 10:23 pm

Could be solved by installing a new radio? or a custom rom (CM11)? What do you think?

PreviousNext

Return to LG G2/G3

Who is online

Users browsing this forum: No registered users and 1 guest