Page 3 of 21
Re: Bluetooth Audio Support
Posted: Sun Aug 30, 2015 10:27 pm
by sectroyer
sakku wrote:dmesg | grep bt
usbcore: registered new interface driver btusb
btusb mod ld
btusb 2-1.3:1.0: usb_probe_interface
btusb 2-1.3:1.0: usb_probe_interface - got id
btusb 2-1.3:1.0: looking for a minor, starting at 194
BTHID bthid_init: ++
BTHID bthid_init: --
bthid mod ld
lsmod
bthid 2520 0 - Live 0xbf324000
hid_microsoft 2032 0 - Live 0xbf31e000
mousedev 7248 0 - Live 0xbf317000
evdev 5576 0 - Live 0xbf310000
usbhid 12872 0 - Live 0xbf307000
hid 31240 3 bthid,hid_microsoft,usbhid, Live 0xbf2fa000
rtnet5572sta 31484 2 - Live 0xbf2ed000
rt5572sta 1298772 1 rtnet5572sta, Live 0xbf1ad000 (P)
rtutil5572sta 30864 2 rtnet5572sta,rt5572sta, Live 0xbf1a3000
btusb 31020 1 - Live 0xbf196000
usb_storage 30272 0 - Live 0xbf189000
ehci_hcd 47852 0 - Live 0xbf178000
usbcore 108904 8 usbhid,rtnet5572sta,rtutil5572sta,btusb,usb_storage,ehci_hcd, L
ive 0xbf158000
tntfs 363728 0 - Live 0xbf0fa000 (P)
mdrv_emac 12576 0 - Live 0xbf0f1000 (P)
samsung_mstar 494248 0 - Live 0xbf066000
samsung_mali 83928 5 samsung_mstar, Live 0xbf04c000
rfs_fat 202648 7 - Live 0xbf015000 (P)
rfs_glue 61548 1 rfs_fat, Live 0xbf000000 (P)
seems btusb.ko need to be patched to work for any bluetooth headphones..
anyone has skill to do it ?
Patching is NOT the problem. But do you know WHAT to patch ?
It seems it works okay
Re: Bluetooth Audio Support
Posted: Sun Oct 25, 2015 10:57 am
by Meriox
This topic again died?
I thought someone manages to solve the mystery of soundshare :-/
Re: Bluetooth Audio Support
Posted: Sun Oct 25, 2015 6:11 pm
by miazza
It will remain a dream ... and a silly limitation on samsung TV.... all others can use any BT headset....
Re: Bluetooth Audio Support
Posted: Wed Dec 30, 2015 7:42 pm
by ZILZAL
SO still no solution ?
have you guys found a way ?
Re: Bluetooth Audio Support
Posted: Thu Dec 31, 2015 12:27 pm
by sectroyer
ZILZAL wrote:SO still no solution ?
NO
ZILZAL wrote:have you guys found a way ?
YES
I connected my iPhone DIRECTLY
Works as a charm
Re: Bluetooth Audio Support
Posted: Thu Dec 31, 2015 12:47 pm
by miazza
sectroyer wrote:ZILZAL wrote:SO still no solution ?
NO
ZILZAL wrote:have you guys found a way ?
YES
I connected my iPhone DIRECTLY
Works as a charm
How did you connect iPhone ?
My S5 is not connecting via BT.
Re: Bluetooth Audio Support
Posted: Thu Dec 31, 2015 2:10 pm
by zoelechat
I think sectroyer is talking about such stuff
Re: Bluetooth Audio Support
Posted: Thu Dec 31, 2015 3:53 pm
by miazza
HAHAHA ... in ths way there are also other stuff that does the job like BT Transmmitter.
Re: Bluetooth Audio Support
Posted: Thu Dec 31, 2015 4:39 pm
by ZILZAL
Re: Bluetooth Audio Support
Posted: Sun Mar 06, 2016 1:10 am
by hudd0
If you enter a "ps -ef" in your telnet session, you should see a line like this:
Code: Select all
ttyS1 00:00:00 /mtd_cmmlib/BT_LIB/bsa_server -all=0 -diag=0 -hci=0 -l2c=0 -app=0 -btm=0 -sdp=0 -rfc=0 -gap=0 -a2d=0 -avdt=0 -avrc=0 -mca=0 -u /mtd_rwarea/
There is the bsa_server process running with several options...
So if you enter "/mtd_cmmlib/BT_LIB/bsa_server -help", you find out that there are several debugging options and the ability to create a .snoop file which you can open in wireshark...
Code: Select all
root@tv:/mtd_rwcommon # /mtd_cmmlib/BT_LIB/bsa_server -help
BSA_trace 1@23h:59m:35s:347ms: Starting Bluetooth Daemon
BSA_trace 2@23h:59m:35s:348ms: BSA version:BSA_MI_01.00.05.00.29-eng3
BSA_trace 3@23h:59m:35s:348ms: BSA server version info:Eng2 + security update
DESCRIPTION:
bsa_server supports:
- if UART HCI is used, forcing the UART device to use
- if tracing is enabled, configuring tracing levels for the various
protocols and profiles of the Bluetooth stack and application.
The use of the option on the command line without any number will
result in the maximum trace level of 5 (DEBUG) for the layer.
Otherwise, the tracing level is set to the number specified.
The possible levels are the following:
NONE 0 No trace messages to be generated
ERROR 1 Error condition trace messages
WARNING 2 Warning condition trace messages
API 3 API traces
EVENT 4 Debug messages for events
DEBUG 5 Full debug messages
USAGE: bsa_server [OPTION]...
-help get option help information
-b file specify the BT Snoop file to save serial packets
-d device set the hci device interface (e.g. /dev/ttyHS0)
-u path prefix all the socket names with a path
-p patchfile force the patchfile to use
-all=# set trace level to # for all layers
-diag=# set DIAG trace level to #
-hci=# set HCI trace level to #
-l2c=# set L2CAP trace level to #
-app=# set APPL trace level to #
-btm=# set BTM trace level to #
-sdp=# set SDP trace level to #
-rfc=# set RFCOMM trace level to #
-gap=# set GAP trace level to #
-a2d=# set A2DP trace level to #
-avdt=# set AVDT trace level to #
-avct=# set AVCT trace level to #
-avrc=# set AVRC trace level to #
-mca=# set MCA trace level to #
EXAMPLES:
Example: bsa_server -d /dev/com10
This command would force the HCI to use /dev/com10
Example: bsa_server -d /dev/com10 -hci -l2c -app -a2d
This command would establish the following trace setting:
HCI layer = 5 (DEBUG)
L2CAP layer = 5 (DEBUG)
APPL layer = 5 (DEBUG)
A2DP layer = 5 (DEBUG)
Example: bsa_server -hci=0 -l2c=4 -app -a2d=3
This command would establish the following trace setting:
HCI layer = 0 (NONE)
L2CAP layer = 4 (EVENT)
APPL layer = 5 (DEBUG)
A2DP layer = 3 (API)
Found out, you should first kill the current active bsa_server process and immediatly fire up your own with enabled debugging options and logging of all bluetooth traffic into a btlog.snoop file, which can be opendend in wireshark afterwards.
First do a "ps -a" to get the current pid of the bsa_server process:
Afterwards fireup the following to see everything about blouetooth in your terminal an to log into a snoop file. Substitute my pid (11454) with your own!!!
Code: Select all
kill -9 11454 && /mtd_cmmlib/BT_LIB/bsa_server -all=5 -diag=5 -hci=5 -l2c=5 -app=5 -btm=5 -sdp=5 -rfc=5 -gap=5 -a2d=5 -avdt=5 -avrc=5 -mca=5 -u /mtd_rwarea/ -b /mtd_rwcommon/bt_test/btlog.snoop
Voila!! A new instance of the bsa_server process is running and logging all the detailed contents...
But i do not have neither a official Samsung A2DP Device, nor a A2DP Headphone or something like that....
