New [SENSATION XE]Bluetooth Car Kit Call List access


Torello

Members
Oct 2, 2012
24
11
Hi everybody,

did anybody encountered any problem with bluetooth car kit accessing call lists? My setup is as follow:

-Sensation XE with 3.33.401.x firmware
-miuiandroid 2.9.29 with installed miuiandroid lang pack
-installed ROM after full wipe (format all partition and full wipe)

I've tried many different ROMs and with sense based ROMs the call list syncing was functional. Is this a bug or is it as it is expected to work?

Unfortunately I cannot show you screenshot of my car and my phone is not showing anything strange. Is bluetooth stack generating any log that I can send you?

Ciao
Roberto.
 
Attached is portion of the logcat:


Code:
10-03 20:45:30.741 D/BTAPP_PBS(  735): #### btapp_pbs_on_rx_ctrl op_code = 1 access = 1 file name  /telecom/och.vcf ####[/SIZE]
 
[SIZE=2]10-03 20:45:30.741 I/PBS_CO  (  735): pbs_sql_co_open: p_path = [ /telecom/och.vcf], operation = [BTA_PBS_OPER_PULL_PB][/SIZE]
 
[SIZE=2]10-03 20:45:30.741 I/PBS_CO  (  735): pbs_sql_co_open: Open Android database [/data/data/com.android.providers.contacts/databases/contacts2.db][/SIZE]
 
[SIZE=2]10-03 20:45:30.811 I/PBS_CO  (  735): pbs_sql_co_open: PBS main table parsed size = 49[/SIZE]
 
[SIZE=2]10-03 20:45:30.811 E/        (  735): sqlite3_exec select number, name, type, date, duration, numbertype, raw_contact_id from calls where _id=145 with err 1: no such column: raw_contact_id[/SIZE]
 
[SIZE=2]10-03 20:45:30.811 E/        (  735): bta_pbs_app_parse_call_entry: Error in select statement no such column: raw_contact_id[/SIZE]
 
[SIZE=2]10-03 20:45:30.811 E/PBS_CO  (  735): pbs_sql_co_open: bta_pbs_app_parse_call_entry failed[/SIZE]
 
[SIZE=2]10-03 20:45:30.811 E/        (  735):  bps open done called. Status = 1[/SIZE]
 
[SIZE=2]10-03 20:45:30.931 D/BTAPP_PBS(  735): #### PBS Access  /telecom/mch.vcf 00:1E:A4:9E:5C:BE Ford Audio 1 ####[/SIZE]
 
[SIZE=2]10-03 20:45:30.931 I/        (  735): send_ctrl_msg: [BTL_IFS CTRL] send BTLIF_PBS_ACCESS_EVT (PBS) 526 pbytes (hdl 26)[/SIZE]
 
[SIZE=2]10-03 20:45:30.931 D/BTL-IFC (  213): btl_ifc_ctrl_rx: [BTL_IFC CTRL] received msg id 4646 - BTLIF_PBS_ACCESS_EVT (PBS); 528 pbytes (hdl 305)[/SIZE]
 
[SIZE=2]10-03 20:45:30.931 D/com_broadcom_bt_service_pbap_PBAPService.cpp(  213): #### handlePbapEvent 0x4026bcf6 ####[/SIZE]
 
[SIZE=2]10-03 20:45:30.931 D/BTL-IFC (  213): send_ctrl_msg: [BTL_IFC CTRL] send msg id 4421 - BTLIF_PBS_ACCESS_RSP (PBS) 526 pbytes (hdl 305)[/SIZE]
 
[SIZE=2]10-03 20:45:30.931 D/BTAPP_PBS(  735): #### btapp_pbs_on_rx_ctrl op_code = 1 access = 1 file name  /telecom/mch.vcf ####[/SIZE]
 
[SIZE=2]10-03 20:45:30.931 I/PBS_CO  (  735): pbs_sql_co_open: p_path = [ /telecom/mch.vcf], operation = [BTA_PBS_OPER_PULL_PB][/SIZE]
 
[SIZE=2]10-03 20:45:30.931 I/PBS_CO  (  735): pbs_sql_co_open: Open Android database [/data/data/com.android.providers.contacts/databases/contacts2.db][/SIZE]
 
[SIZE=2]10-03 20:45:30.941 I/        (  735): send_ctrl_msg: [BTL_IFS CTRL] send BTLIF_DTUN_SIGNAL_EVT (CTRL) 44 pbytes (hdl 22)[/SIZE]
 
[SIZE=2]10-03 20:45:30.941 I/DTUN_HCID4(  777): pending[/SIZE]
 
[SIZE=2]10-03 20:45:30.941 I/DTUN_HCID4(  777): orig_msg = 1233828[/SIZE]
 
[SIZE=2]10-03 20:45:30.941 D/DTUN_HCID4(  777): Answering Pending Req[/SIZE]
 
[SIZE=2]10-03 20:45:30.941 D/DTUN_HCID4(  777): Stream successfully created[/SIZE]
 
[SIZE=2]10-03 20:45:30.941 D/BluetoothA2dpService(  213): A2DP: onSinkPropertyChanged newState is: 2mPlayingA2dpDevice: null[/SIZE]
 
[SIZE=2]10-03 20:45:30.941 D/BluetoothA2dpService(  213): setPriority = Auto Connect[/SIZE]
 
[SIZE=2]10-03 20:45:30.961 I/PBS_CO  (  735): pbs_sql_co_open: PBS main table parsed size = 11[/SIZE]
 
[SIZE=2]10-03 20:45:30.961 E/        (  735): sqlite3_exec select number, name, type, date, duration, numbertype, raw_contact_id from calls where _id=59 with err 1: no such column: raw_contact_id[/SIZE]
 
[SIZE=2]10-03 20:45:30.961 E/        (  735): bta_pbs_app_parse_call_entry: Error in select statement no such column: raw_contact_id[/SIZE]
 
[SIZE=2]10-03 20:45:30.961 E/PBS_CO  (  735): pbs_sql_co_open: bta_pbs_app_parse_call_entry failed[/SIZE]
 
[SIZE=2]10-03 20:45:30.961 E/        (  735):  bps open done called. Status = 1[/SIZE]
 
[SIZE=2]10-03 20:45:30.991 D/BluetoothA2dpService(  213): A2DP state : device: 00:1E:A4:9E:5C:BE State:1->2[/SIZE]
 
[SIZE=2]10-03 20:45:30.991 I/BluetoothA2dpService(  213): [embedded] A2DP state : address: 00:1E:A4:9E:5C:BE name: Ford Audio State:1->2[/SIZE]
 
[SIZE=2]10-03 20:45:31.001 I/BluetoothProfileState(  213): Message:Entering Stable State

I see some errors in the sqlite3 select number command. I've never coded for Android, and I've never debugged bluetooth, if you have any idea on where the problem could be let me now.
 
I've also tried to look at the file in the framework dir. It seems that all the apks from miuiandroid and ht revolution hd (on which BT call list synching is working fine) that regards BT have same size and same date. Even after decompiling dex class package the content seems to be the same.

Are the missed calls and the last calls logs differing from the same log db on straight sense based roms?

Grazie
Rob.
 
I definitely found out the problem is related to accessing contact by ID.

Code:
10-03 20:45:30.931 D/BTAPP_PBS(  735): #### PBS Access  /telecom/mch.vcf 00:1E:A4:9E:5C:BE Ford Audio 1 ####
10-03 20:45:30.931 I/        (  735): send_ctrl_msg: [BTL_IFS CTRL] send BTLIF_PBS_ACCESS_EVT (PBS) 526 pbytes (hdl 26)
10-03 20:45:30.931 D/BTL-IFC (  213): btl_ifc_ctrl_rx: [BTL_IFC CTRL] received msg id 4646 - BTLIF_PBS_ACCESS_EVT (PBS); 528 pbytes (hdl 305)
10-03 20:45:30.931 D/com_broadcom_bt_service_pbap_PBAPService.cpp(  213): #### handlePbapEvent 0x4026bcf6 ####
10-03 20:45:30.931 D/BTL-IFC (  213): send_ctrl_msg: [BTL_IFC CTRL] send msg id 4421 - BTLIF_PBS_ACCESS_RSP (PBS) 526 pbytes (hdl 305)
10-03 20:45:30.931 D/BTAPP_PBS(  735): #### btapp_pbs_on_rx_ctrl op_code = 1 access = 1 file name  /telecom/mch.vcf ####
10-03 20:45:30.931 I/PBS_CO  (  735): pbs_sql_co_open: p_path = [ /telecom/mch.vcf], operation = [BTA_PBS_OPER_PULL_PB]
10-03 20:45:30.931 I/PBS_CO  (  735): pbs_sql_co_open: Open Android database [/data/data/com.android.providers.contacts/databases/contacts2.db]
10-03 20:45:30.941 I/        (  735): send_ctrl_msg: [BTL_IFS CTRL] send BTLIF_DTUN_SIGNAL_EVT (CTRL) 44 pbytes (hdl 22)
10-03 20:45:30.941 I/DTUN_HCID4(  777): pending
10-03 20:45:30.941 I/DTUN_HCID4(  777): orig_msg = 1233828
10-03 20:45:30.941 D/DTUN_HCID4(  777): Answering Pending Req
10-03 20:45:30.941 D/DTUN_HCID4(  777): Stream successfully created
10-03 20:45:30.941 D/BluetoothA2dpService(  213): A2DP: onSinkPropertyChanged newState is: 2mPlayingA2dpDevice: null
10-03 20:45:30.941 D/BluetoothA2dpService(  213): setPriority = Auto Connect
10-03 20:45:30.961 I/PBS_CO  (  735): pbs_sql_co_open: PBS main table parsed size = 11
10-03 20:45:30.961 E/        (  735): sqlite3_exec select number, name, type, date, duration, numbertype, raw_contact_id from calls where _id=59 with err 1: no such column: raw_contact_id
10-03 20:45:30.961 E/        (  735): bta_pbs_app_parse_call_entry: Error in select statement no such column: raw_contact_id
10-03 20:45:30.961 E/PBS_CO  (  735): pbs_sql_co_open: bta_pbs_app_parse_call_entry failed
10-03 20:45:30.961 E/        (  735):  bps open done called. Status = 1

It does it in 3 steps:
1) access missed call history file mhs.vcf
2) access contact list file contacts2.db
3) try to get caller name from the sql database

Apparently it fails at the third step, I am not familiar with sql android database, if you can help me I will be very glad and will make this ROM for sensation almost perfect.
 
I've tried the new ROM. 2.10.26

Call list access is still present? Do you think it can be related to setting right permission to BT framework? Should I try to disable the control access?

Ciao
Rob
 
Hi cream, do you have exact same problem? Are encountering issues in getting call list in the car kit? Which car do you have? Mine a Ford Focus with Sony Radio... just to check which model is giving the issue.

Could you try to collect a logcat? You can use aLogcat it is free and can be found on the market... I've unpacked the MIUI rom and the ARHD 6.8.0 and the ARHD 6.7.2 and de-assembled all the package in the framework, but I haven't found any major difference. I tried then to push the ARHD6.8.0 BT framework related files into MIUI but nothing changed... it is weird!

Ciao
Rob
 
Hi cream, do you have exact same problem? Are encountering issues in getting call list in the car kit? Which car do you have? Mine a Ford Focus with Sony Radio... just to check which model is giving the issue.

Could you try to collect a logcat? You can use aLogcat it is free and can be found on the market... I've unpacked the MIUI rom and the ARHD 6.8.0 and the ARHD 6.7.2 and de-assembled all the package in the framework, but I haven't found any major difference. I tried then to push the ARHD6.8.0 BT framework related files into MIUI but nothing changed... it is weird!

Ciao
Rob
my problem relates to sending files through bluetooth in general. i dont have a car kit because i drive an old car:).
i tried the bt_patch_by.xiaolie.zip and flashed through recovery to no avail. i even switched to a different kernel
just to see if it fixes the problem but the bluetooth is still not working. these are the devices i tried to send files with:
galaxy nexus (stock)
sensation (miui rom)
motorola defy (miui gb)
it pairs with these devices but i cant send files to them.
do you have a solution for this, rob? thanks.
 
I have not tried yet... last week I tried the JBMIUI4.1.2.

In that ROM BT is sending contact to my car, but I need to reboot the phone everytime I get into my car! :) Tomorrow I will install miuiandroid and tell you about file transfer with my phone.

Ciao
 
I know CM10 (OpenSensatio 2 in the last builds) has some issue with BT compatibility. But even miuiandroid with stock base has some issue. File transfer does not work and the call logs lists are not passed to my car kit.

Ciao
 
I know CM10 (OpenSensatio 2 in the last builds) has some issue with BT compatibility. But even miuiandroid with stock base has some issue. File transfer does not work and the call logs lists are not passed to my car kit.

Ciao
thanks for the info torello. im still stuck on 2.10.26. im waiting for miui china to sort things out.
 
I've also tried to ROM from miui.com directly. Unfortunately they have the same issue, probably because they are on the same base. I would like to find the responsible for the pyramid build and I will be more than glad working with him/her solving this annoying BT problems.
 
Attached is the logcat I have when I try to transfer a file... after few seconds it stops working and the progress bar never gets updated.

D/BluetoothSocket( 2565): socket already in closing state:android.bluetooth.BluetoothSocket@41231fb0
D/BLZ20_WRAPPER( 2565): tput_mon: s:38, rx:0, tx:1888 (kbps)
D/BLZ20_WRAPPER( 2565): tput_mon: s:38, rx:0, tx:686 (kbps)
D/dalvikvm( 2565): GC_FOR_ALLOC freed 1636K, 44% free 5335K/9439K, paused 27ms
D/BLZ20_WRAPPER( 2565): tput_mon: s:38, rx:0, tx:1878 (kbps)
W/ ( 1835): tput rx:0, tx:149 (kB/s) (tot : rx 25, tx 386729 bytes)
D/BLZ20_WRAPPER( 2565): tput_mon: s:38, rx:0, tx:743 (kbps)
D/dalvikvm( 2565): GC_FOR_ALLOC freed 1540K, 44% free 5337K/9439K, paused 18ms
D/BLZ20_WRAPPER( 2565): tput_mon: s:38, rx:0, tx:1310 (kbps)
D/BLZ20_WRAPPER( 2565): tput_mon: s:38, rx:0, tx:2017 (kbps)
W/ ( 1835): tput rx:0, tx:157 (kB/s) (tot : rx 40, tx 708939 bytes)
D/dalvikvm( 2565): GC_FOR_ALLOC freed 1544K, 44% free 5340K/9439K, paused 26ms
D/BLZ20_WRAPPER( 2565): tput_mon: s:38, rx:0, tx:700 (kbps)
D/BLZ20_WRAPPER( 2565): tput_mon: s:38, rx:0, tx:1260 (kbps)
D/dalvikvm( 2565): GC_FOR_ALLOC freed 1607K, 43% free 5399K/9439K, paused 17ms
D/BLZ20_WRAPPER( 2565): tput_mon: s:38, rx:0, tx:864 (kbps)
I/USERIAL_LINUX( 1835): ##### USERIAL_Ioctl: BT_Sleep, USERIAL_IO_BT_WAKE_DEASSERT ####
Maybe this is somehow related to the call list transfer as well!
By the way I am now on 2.11.30... it seems to be the same exact base! :(
 
To be honest, concerning Sensation XE, I haven't found any big news from october. I'm continuing updating hoping for BT fix to appear, but no big improvements so far... to be honest now it is even a little worse, at least with october version BT always automatically paired with my car kit, now once out of two it does not connect and I have to reboot the phone... strange!