Soundshare, once again. Bluetooth audio knowledge

Ideas and dreaming will go this forum

rg2013
Posts: 17
Joined: Sun Nov 24, 2013 9:06 pm

Soundshare, once again. Bluetooth audio knowledge

Post by rg2013 » Mon Dec 02, 2013 3:16 pm

Does anybody have an information on soundshare?
I have several questions.
1. Does the bluetooth audio device transmit a special name?
(from a Samsung video on youtube it seemed to me that soundshare transmits a string named "[Samsung] AirTrack".
Can anybody confirm that? Are there any other known strings?
2. Is it possible to search for a Samsung soundbar with any bluetooth enabled notebook. Perhaps by using linux bluetooth utilities?
3. Does anybody have images of pcb of soundshare capable audio device. Looking for chipset.
4. What about pairing? Does the user enter a key like "0000" or any other. May there be a preprogrammed key? Do you have to press a button for pairing?
5. Does every soundshare device have NFC? Is NFC mandatory for soundshare?
6. What known soundshare devices are there. Headsets, soundbars, speakers, any others?
7. Are there any known non Samsung working devices? Like philips, LG, Sony, creative, logitek,...

I dont think that Samsung has invented their own special protocol. (The market is to small). In e-series brainstorm forum someone mentioned the apt-x protocol. To my opinion that could be a promising way to go. If this is right, it schould be possible to attach to a samsung soundbar with a bluetooth pc with special software. I would prefer to manipulate my sound device to connect to tv rather then manipulate the TV software.
Using a module like this on aliexpress from cambridge silicon radio: CSR8645-ROM-Module-Bluetooth-4-0-Support-APT-X-Decoding-Smaller-SMT-Package-RoHS-Compliance-DIY could be a way.
Last edited by rg2013 on Fri Dec 13, 2013 12:24 pm, edited 1 time in total.
Samsung TV UE32F5570 Firmware: T-MST12DEUC-1113.0 / T-MST12DEUS-1009

rg2013
Posts: 17
Joined: Sun Nov 24, 2013 9:06 pm

Re: Soundshare, once again. Blutooth audio knowledge

Post by rg2013 » Fri Dec 06, 2013 4:17 pm

Found some proof that samsung uses apt-x.
Hope its ok to post this link:
http://www.csr.com/technology-solutions ... nd/Samsung
(several soundbars and headset DA61.
Im now looking for an inexpensive csr module.
Samsung TV UE32F5570 Firmware: T-MST12DEUC-1113.0 / T-MST12DEUS-1009

rg2013
Posts: 17
Joined: Sun Nov 24, 2013 9:06 pm

Re: Soundshare, once again. Blutooth audio knowledge

Post by rg2013 » Sat Dec 07, 2013 8:38 pm

Seems nobody cares about this topic. So i have to keep on talking to myself. :-)

Anyway, according to some posts on csr apt-x propriatary codec there seems to be a libbt-aptx-*.so software module necessary.
You can find it on Samsung android phones.

Is there such a module in the library path on Samsung tv?
Is the codec implemented in this module?
Is the codec in the bluetooth hardware of the tv-set?
Is it possible to exchange the library file by a dummy library
and bypass apt-x to do simple A2DP bluetooth profile?

Does any body have photos of Samsung Bluetooth hardware in Bluetooth enabled Samsung TVsets?
Samsung TV UE32F5570 Firmware: T-MST12DEUC-1113.0 / T-MST12DEUS-1009

rg2013
Posts: 17
Joined: Sun Nov 24, 2013 9:06 pm

Re: Soundshare, once again. Bluetooth audio knowledge

Post by rg2013 » Fri Dec 13, 2013 12:40 pm

Still nothing. ;-)
Reanmed my bluetooth string on my linux ubuntu:
sudo hciconfig hci0 name '[Samsung] AirTrack' (dont know if nessesary.)
started sniffing
sudo hcidump -a hci0
started bluetooth search for bt keyboard on my samsung tv.
got two Bluetooth profiles from TV,
bt-address= 00:02:72:14:33:4E:
AVRCP (Target) and A2DP (sink)

Code: Select all

HCI sniffer - Bluetooth packet analyzer ver 2.2
device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
< HCI Command: Inquiry (0x01|0x0001) plen 5
    lap 0x9e8b33 len 8 num 0
> HCI Event: Command Status (0x0f) plen 4
    Inquiry (0x01|0x0001) status 0x00 ncmd 1
> HCI Event: Inquiry Result with RSSI (0x22) plen 15
    bdaddr 00:02:72:14:33:4E mode 0 clkoffset 0x6706 class 0x08043c rssi -58
> HCI Event: Inquiry Result with RSSI (0x22) plen 15
    bdaddr 00:02:72:14:33:4E mode 0 clkoffset 0x6706 class 0x08043c rssi -58
> HCI Event: Inquiry Result with RSSI (0x22) plen 15
    bdaddr 00:02:72:14:33:4E mode 0 clkoffset 0x6706 class 0x08043c rssi -57
> HCI Event: Inquiry Result with RSSI (0x22) plen 15
    bdaddr 00:02:72:14:33:4E mode 0 clkoffset 0x6706 class 0x08043c rssi -56
> HCI Event: Inquiry Result with RSSI (0x22) plen 15
    bdaddr 00:02:72:14:33:4E mode 0 clkoffset 0x6706 class 0x08043c rssi -57
> HCI Event: Inquiry Result with RSSI (0x22) plen 15
    bdaddr 00:02:72:14:33:4E mode 0 clkoffset 0x6706 class 0x08043c rssi -59
> HCI Event: Inquiry Result with RSSI (0x22) plen 15
    bdaddr 00:02:72:14:33:4E mode 0 clkoffset 0x6706 class 0x08043c rssi -58
> HCI Event: Inquiry Result with RSSI (0x22) plen 15
    bdaddr 00:02:72:14:33:4E mode 0 clkoffset 0x6706 class 0x08043c rssi -57
> HCI Event: Inquiry Result with RSSI (0x22) plen 15
    bdaddr 00:02:72:14:33:4E mode 0 clkoffset 0x6706 class 0x08043c rssi -56
> HCI Event: Inquiry Result with RSSI (0x22) plen 15
    bdaddr 00:02:72:14:33:4E mode 0 clkoffset 0x6706 class 0x08043c rssi -58
> HCI Event: Inquiry Result with RSSI (0x22) plen 15
    bdaddr 00:02:72:14:33:4E mode 0 clkoffset 0x6706 class 0x08043c rssi -58
> HCI Event: Inquiry Result with RSSI (0x22) plen 15
    bdaddr 00:02:72:14:33:4E mode 0 clkoffset 0x6706 class 0x08043c rssi -57
> HCI Event: Inquiry Result with RSSI (0x22) plen 15
    bdaddr 00:02:72:14:33:4E mode 0 clkoffset 0x6706 class 0x08043c rssi -57
> HCI Event: Inquiry Result with RSSI (0x22) plen 15
    bdaddr 00:02:72:14:33:4E mode 0 clkoffset 0x6706 class 0x08043c rssi -70
> HCI Event: Inquiry Result with RSSI (0x22) plen 15
    bdaddr 00:02:72:14:33:4E mode 0 clkoffset 0x6706 class 0x08043c rssi -58
> HCI Event: Inquiry Result with RSSI (0x22) plen 15
    bdaddr 00:02:72:14:33:4E mode 0 clkoffset 0x6706 class 0x08043c rssi -56
> HCI Event: Inquiry Result with RSSI (0x22) plen 15
    bdaddr 00:02:72:14:33:4E mode 0 clkoffset 0x6706 class 0x08043c rssi -57
< HCI Command: Inquiry Cancel (0x01|0x0002) plen 0
> HCI Event: Command Complete (0x0e) plen 4
    Inquiry Cancel (0x01|0x0002) ncmd 1
    status 0x00
< HCI Command: Create Connection (0x01|0x0005) plen 13
    bdaddr 00:02:72:14:33:4E ptype 0xcc18 rswitch 0x01 clkoffset 0x0000
    Packet type: DM1 DM3 DM5 DH1 DH3 DH5 
> HCI Event: Command Status (0x0f) plen 4
    Create Connection (0x01|0x0005) status 0x00 ncmd 1
> HCI Event: Role Change (0x12) plen 8
    status 0x00 bdaddr 00:02:72:14:33:4E role 0x01
    Role: Slave
> HCI Event: Connect Complete (0x03) plen 11
    status 0x00 handle 42 bdaddr 00:02:72:14:33:4E type ACL encrypt 0x00
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
    handle 42
> HCI Event: Page Scan Repetition Mode Change (0x20) plen 7
    bdaddr 00:02:72:14:33:4E mode 0
> HCI Event: Max Slots Change (0x1b) plen 3
    handle 42 slots 5
> HCI Event: Command Status (0x0f) plen 4
    Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 0
> HCI Event: Command Status (0x0f) plen 4
    Unknown (0x00|0x0000) status 0x00 ncmd 1
> HCI Event: Read Remote Supported Features (0x0b) plen 11
    status 0x00 handle 42
    Features: 0xff 0xff 0x8d 0xfe 0x9b 0xf9 0x00 0x80
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
    bdaddr 00:02:72:14:33:4E mode 2 clkoffset 0x0000
> HCI Event: Command Status (0x0f) plen 4
    Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
> HCI Event: Remote Name Req Complete (0x07) plen 255
    status 0x00 bdaddr 00:02:72:14:33:4E name '[TV]Samsung LED32'
< HCI Command: Authentication Requested (0x01|0x0011) plen 2
    handle 42
> HCI Event: Command Status (0x0f) plen 4
    Authentication Requested (0x01|0x0011) status 0x00 ncmd 1
> HCI Event: Link Key Request (0x17) plen 6
    bdaddr 00:02:72:14:33:4E
< HCI Command: Link Key Request Negative Reply (0x01|0x000c) plen 6
    bdaddr 00:02:72:14:33:4E
> HCI Event: Command Complete (0x0e) plen 10
    Link Key Request Negative Reply (0x01|0x000c) ncmd 1
    status 0x00 bdaddr 00:02:72:14:33:4E
> HCI Event: PIN Code Request (0x16) plen 6
    bdaddr 00:02:72:14:33:4E
< HCI Command: PIN Code Request Reply (0x01|0x000d) plen 23
    bdaddr 00:02:72:14:33:4E len 4 pin '0000'
> HCI Event: Command Complete (0x0e) plen 10
    PIN Code Request Reply (0x01|0x000d) ncmd 1
    status 0x00 bdaddr 00:02:72:14:33:4E
> HCI Event: Link Key Notification (0x18) plen 23
    bdaddr 00:02:72:14:33:4E key E06423C545C84442C1641E95836D87FB type 0
    Type: Combination Key
> HCI Event: Auth Complete (0x06) plen 3
    status 0x00 handle 42
< HCI Command: Authentication Requested (0x01|0x0011) plen 2
    handle 42
< ACL data: handle 42 flags 0x02 dlen 10
    L2CAP(s): Info req: type 2
> ACL data: handle 42 flags 0x02 dlen 16
    L2CAP(s): Info rsp: type 2 result 0
      Extended feature mask 0x02b8
        Enhanced Retransmission mode
        Streaming mode
        FCS Option
        Fixed Channels
        Unicast Connectless Data Reception
< ACL data: handle 42 flags 0x02 dlen 10
    L2CAP(s): Info req: type 3
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 42 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 42 packets 1
> ACL data: handle 42 flags 0x02 dlen 20
    L2CAP(s): Info rsp: type 3 result 0
      Fixed channel list 0x00000006
        L2CAP Signalling Channel
        L2CAP Connless
< ACL data: handle 42 flags 0x02 dlen 12
    L2CAP(s): Connect req: psm 1 scid 0x0040
> HCI Event: Command Status (0x0f) plen 4
    Authentication Requested (0x01|0x0011) status 0x00 ncmd 1
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 42 packets 1
> ACL data: handle 42 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0043 scid 0x0040 result 1 status 0
      Connection pending - No futher information available
> HCI Event: Auth Complete (0x06) plen 3
    status 0x00 handle 42
> ACL data: handle 42 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0043 scid 0x0040 result 0 status 0
      Connection successful
< ACL data: handle 42 flags 0x02 dlen 23
    L2CAP(s): Config req: dcid 0x0043 flags 0x00 clen 11
      RFC 0x00 (Basic) 
> ACL data: handle 42 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
      MTU 510 
< ACL data: handle 42 flags 0x02 dlen 18
    L2CAP(s): Config rsp: scid 0x0043 flags 0x00 result 0 clen 4
      MTU 510 
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 42 packets 1
> ACL data: handle 42 flags 0x02 dlen 14
    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
      Success
< ACL data: handle 42 flags 0x02 dlen 24
    L2CAP(d): cid 0x0043 len 20 [psm 1]
        SDP SSA Req: tid 0x0 len 0xf
          pat uuid-16 0x0100 (L2CAP)
          max 65535
          aid(s) 0x0000 - 0xffff
          cont 00
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 42 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 42 packets 1
> ACL data: handle 42 flags 0x02 dlen 200
    L2CAP(d): cid 0x0040 len 196 [psm 1]
        SDP SSA Rsp: tid 0x0 len 0xbf
          count 188
          record #0
              aid 0x0000 (SrvRecHndl)
                 uint 0x10001
              aid 0x0001 (SrvClassIDList)
                 < uuid-16 0x110c (AVRemTarget) >
              aid 0x0004 (ProtocolDescList)
                 < < uuid-16 0x0100 (L2CAP) uint 0x17 > <
                 uuid-16 0x0017 (AVCTP) uint 0x103 > >
              aid 0x0005 (BrwGrpList)
                 < uuid-16 0x1002 (PubBrwsGrp) >
              aid 0x0009 (BTProfileDescList)
                 < < uuid-16 0x110e (AVRemote) uint 0x104 > >
              aid 0x000d (AdditionalProtocolDescLists)
                 < < < uuid-16 0x0100 (L2CAP) uint 0x1b > < uuid-16 0x0017 (AVCTP) uint 0x103 > > >
              aid 0x0311 (SuppFeatures)
                 uint 0xf1
          record #1
              aid 0x0000 (SrvRecHndl)
                 uint 0x10002
              aid 0x0001 (SrvClassIDList)
                 < uuid-16 0x110a (AudioSource) >
              aid 0x0004 (ProtocolDescList)
                 < < uuid-16 0x0100 (L2CAP) uint 0x19 > <
                 uuid-16 0x0019 (AVDTP) uint 0x102 > >
              aid 0x0005 (BrwGrpList)
                 < uuid-16 0x1002 (PubBrwsGrp) >
              aid 0x0009 (BTProfileDescList)
                 < < uuid-16 0x110d (AdvAudio) uint 0x102 > >
              aid 0x0100 (SrvName)
                 str "default av service name"
              aid 0x0311 (SuppFeatures)
                 uint 0x1
          cont 00
< ACL data: handle 42 flags 0x02 dlen 24
    L2CAP(d): cid 0x0043 len 20 [psm 1]
        SDP SSA Req: tid 0x1 len 0xf
          pat uuid-16 0x1200 (PNPInfo)
          max 65535
          aid(s) 0x0000 - 0xffff
          cont 00
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 42 packets 1
> ACL data: handle 42 flags 0x02 dlen 82
    L2CAP(d): cid 0x0040 len 78 [psm 1]
        SDP SSA Rsp: tid 0x1 len 0x49
          count 70
          record #0
              aid 0x0000 (SrvRecHndl)
                 uint 0x10000
              aid 0x0001 (SrvClassIDList)
                 < uuid-16 0x1200 (PNPInfo) >
              aid 0x0005 (BrwGrpList)
                 < uuid-16 0x1002 (PubBrwsGrp) >
              aid 0x0200 (VersionNumList)
                 uint 0x103
              aid 0x0201 (SrvDBState)
                 uint 0xf
              aid 0x0202 (unknown)
                 uint 0x0
              aid 0x0203 (unknown)
                 uint 0x0
              aid 0x0204 (unknown)
                 bool 0x1
              aid 0x0205 (unknown)
                 uint 0x1
              aid 0x8001 (unknown)
                 uint 0x1
          cont 00
< ACL data: handle 42 flags 0x02 dlen 12
    L2CAP(s): Disconn req: dcid 0x0043 scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 42 packets 1
> ACL data: handle 42 flags 0x02 dlen 12
    L2CAP(s): Disconn rsp: dcid 0x0043 scid 0x0040
< HCI Command: Disconnect (0x01|0x0006) plen 3
    handle 42 reason 0x13
    Reason: Remote User Terminated Connection
> HCI Event: Command Status (0x0f) plen 4
    Disconnect (0x01|0x0006) status 0x00 ncmd 1
> HCI Event: Disconn Complete (0x05) plen 4
    status 0x00 handle 42 reason 0x16
    Reason: Connection Terminated by Local Host

thats all for now.
Samsung TV UE32F5570 Firmware: T-MST12DEUC-1113.0 / T-MST12DEUS-1009

Slav
Posts: 17
Joined: Sun Jan 26, 2014 9:23 pm

Re: Soundshare, once again. Bluetooth audio knowledge

Post by Slav » Wed Jan 29, 2014 12:47 am

Hi!
bsa_server, drivers, and scripts from my TV. All contents of /mtd_exe/BT_LIB
Maybe it will help you to understand problem.
See attachment.
You do not have the required permissions to view the files attached to this post.

rg2013
Posts: 17
Joined: Sun Nov 24, 2013 9:06 pm

Re: Soundshare, once again. Bluetooth audio knowledge

Post by rg2013 » Wed Jan 29, 2014 4:00 pm

Thanks for that post.
if you google for:
Broadcom Set-Top Applications and Wireless Solutions pdf
(I dont know if deep linking urls is allowed!)
you can find a pdf white paper explaining Broadcom wireless framework including bluetooth.
To my opinion Broacom doesnt support aptx in hardware, so there should be some softwarecodec on the tv set.
Maybe theres another library path on the tv, where the former mentioned libbt-aptx.. file resides?

Meanwhile i had a hex look at bsa_server binary file.
Seems there are some log strings included that tell what kind of codec is used when a a2dp audio connection is
established. Additionally there are some strings with APTX, so my strategy would be:
1. Enable the logging on tv bsa_server.
2. Established connection on some borrowed samsung soundshare device.
3. Detect in the logfile what codec is used.
4. Satisfy the TVset whith some cheaper hacked non samsung bluetooth device.
Lack of my strategy is number 2.
Samsung TV UE32F5570 Firmware: T-MST12DEUC-1113.0 / T-MST12DEUS-1009

User avatar
nobody
Posts: 182
Joined: Sat Nov 12, 2011 1:45 am

Re: Soundshare, once again. Bluetooth audio knowledge

Post by nobody » Mon Feb 24, 2014 2:31 pm

You are not talking to yourself, I am trying to achieve the same thing.
What I wish to do is this:
Since I have a PC with bluetooth, I wish to connect headphones to my pc and listen to tv audio.
I installed blueman and bluez on my debian vm. I can't make it work with my tv nor with my galaxy s4 phone.
I also don'u understand why they don't do simply this:
Use the phone as "bluetooth speakers" for tv, so I can connect the headphones to my phone and listen to tv.

Condoman98109
Posts: 1
Joined: Mon Jun 23, 2014 7:40 pm

Re: Soundshare, once again. Bluetooth audio knowledge

Post by Condoman98109 » Mon Jun 23, 2014 7:45 pm

I stumbled across this thread while looking for ways to stream audio to my Bernafon Soundgate 2.0 which is the remote control I use with my hearing aids. With it I can stream audio from my iPhone. I would like to be able to connect my Samsung UN46F6400 to the hearing aids because the audio level I need is much higher than others who watch TV with me. Any clues on this?

Meriox
Posts: 4
Joined: Sun Aug 30, 2015 11:09 am

Re: Soundshare, once again. Bluetooth audio knowledge

Post by Meriox » Sun Aug 30, 2015 11:29 am

Has anyone tried another bluetooth speaker with support apt-X csr?

Are you enabled in the service menu > "Option" > "Engineer Option" > "BT_AUDIO_ON_OFF" to "ON"?

Faqeer1
Posts: 1
Joined: Fri Apr 08, 2016 12:14 pm

Re: Soundshare, once again. Bluetooth audio knowledge

Post by Faqeer1 » Fri Apr 08, 2016 12:24 pm

To my opinion Broacom doesnt support aptx in hardware, so there should be some softwarecodec on the tv set.Maybe theres another library path on the tv, where the former mentioned libbt-aptx.. file resides?????

Post Reply

Return to “[F] Brainstorm”