Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Sep 28, 2012
  1. @cgarst @Whitehawkx

    Ported: Bluetooth Message Access Profile (MAP) from CM9

    cgarst authored Whitehawkx committed
    This was added to restore message exchange capabilities with automotive systems.
    
    Change-Id: I88af538273bdf9dd24c971c196500d713f54f6ab
Commits on Jul 13, 2011
  1. Merge "Add NOTICE and MODULE_LICENSE_GPL files."

    Jean-Baptiste Queru authored Android (Google) Code Review committed
Commits on May 25, 2011
  1. Add BT_POWER socket option.

    Jaikumar Ganesh authored
    BT_POWER socket option is used to control the power
    characteristics of the underlying ACL link. Currently, this is
    used to set the ACL link to active mode when the remote end has put
    the ACL link in sniff mode and we are sending data. By default,
    the ACL link will always be moved to active mode. However, this
    causes problems with HID devices. And hence, for HID devices the
    ACL link will not be moved to active mode when we are sending data.
    
    This socket option is implemented for both rfcomm and l2cap sockets.
    
    Change-Id: I0261a8daa2241d691670cc690cd27c39c67c1591
  2. Add missing NOTICE files.

    David Deephanphongs authored Jaikumar Ganesh committed
    Original commit: c3d03f1
    update by Jaikumar Ganesh for Bluez upmerge.
  3. Update userspace headers for SCO/eSCO packet selection in struct sock…

    Nick Pelly authored Jaikumar Ganesh committed
    …addr_sco.
    
    uint16_t sco_pkt_type is introduced to struct sockaddr_sco. It allows bitwise
    selection of SCO/eSCO packet types. Currently those bits are:
    
    0x0001 HV1 may be used.
    0x0002 HV2 may be used.
    0x0004 HV3 may be used.
    0x0008 EV3 may be used.
    0x0010 EV4 may be used.
    0x0020 EV5 may be used.
    0x0040 2-EV3 may be used.
    0x0080 3-EV3 may be used.
    0x0100 2-EV5 may be used.
    0x0200 3-EV5 may be used.
    
    This is similar to the Packet Type parameter in the HCI Setup Synchronous
    Connection Command, except that we are not reversing the logic on the EDR bits.
    This makes the use of sco_pkt_tpye forward portable for the use case of
    white-listing packet types, which we expect will be the primary use case.
    
    If sco_pkt_type is zero, or userspace uses the old struct sockaddr_sco,
    then the default behavior is to allow all packet types.
    
    Packet type selection is just a request made to the Bluetooth chipset, and
    it is up to the link manager on the chipset to negiotiate and decide on the
    actual packet types used. Furthermore, when a SCO/eSCO connection is eventually
    made there is no way for the host stack to determine which packet type was used
    (however it is possible to get the link type of SCO or eSCO).
    
    sco_pkt_type is ignored for incoming SCO connections. It is possible
    to add this in the future as a parameter to the Accept Synchronous Connection
    Command, however its a little trickier because the kernel does not
    currently preserve sockaddr_sco data between userspace calls to accept().
    
    The most common use for sco_pkt_type will be to white-list only SCO packets,
    which can be done with the hci.h constant SCO_ESCO_MASK.
    
    This patch is motivated by broken Bluetooth carkits such as the Motorola
    HF850 (it claims to support eSCO, but will actually reject eSCO connections
    after 5 seconds) and the 2007/2008 Infiniti G35/37 (fails to route audio
    if a 2-EV5 packet type is negiotiated). With this patch userspace can maintain
    a list of compatible packet types to workaround remote devices such as these.
    
    Change-Id: Ie6dc57a6a2d4ec4b42f919070d98d39f225eaf95
  4. Add ACL flow control state (MTU, packets available, packets total) fo…

    Nick Pelly authored Jaikumar Ganesh committed
    …r debug.
    
    Accessed with the debug tool 'hcitool con'
    
    Change-Id: I637d6ac9e2ca63c6e4fc1d24a149f73901704550
  5. Change SDP socket path to be compatible for Android.

    Jaikumar Ganesh authored
    Original Change by Nick Pelly <npelly@google.com>
    
    Change-Id: Id33de250ab501a4d81ee143e6a01fe26abe31d07
  6. Add Android makefiles to Bluez.

    Jaikumar Ganesh authored
    This includes the following commits from previous versions:
    
    a) bluez: Add Android.mk for pand (off by default)
       b163e2b by <san@google.com>
    
    b) Add missing libbluetooth in linker commands for executables using libbluetoothd.
       3e442fe by <dougkwan@google.com>
    
    c) Edit makefiles to get network to work. Changed libglib to be a shared library
       fddb10d62d21580c49101c3dc4ab43f6619234c0 by Danica Chang
    
    d) Update Bluetooth configuration path: 0b25504e93b95a809e32227a3832bf08a3c13296
       by Jaikumar Ganesh
    
    e) bluez : use another code for Intel's mmx. fe0762b2463df43b2765582c76a09356c753e16b
       by: Author: Jae-Hyung Ahn <jerry.ahn@windriver.com>,
       Signed-off-by: Bruce Beare <brucex.j.beare@intel.com>
  7. Fix links of header files.

    Jaikumar Ganesh authored
    The header files are maintained in the lib directory and moved to the include
    directory during install. Since Android doesn't have any installtion process,
    this change moves all the header files to the lib/bluetooth directory. We don't
    follow upstream but this is the closest we can get without using sym links.
Commits on May 18, 2011
  1. @sjanc @jhedberg

    Fix empty parameter list in functions declarations

    sjanc authored jhedberg committed
Commits on May 14, 2011
  1. @sjanc

    Remove not needed NULL check in sdp_gen_pdu

    sjanc authored Johan Hedberg committed
  2. @sjanc

    Fix dead increments and assignments in sdp code

    sjanc authored Johan Hedberg committed
  3. @sjanc

    Fix potential NULL pointer dereference in sdp_get_lang_attr

    sjanc authored Johan Hedberg committed
Commits on May 10, 2011
  1. @sjanc

    Fix C++ style comments

    sjanc authored
Commits on Apr 28, 2011
  1. Add secure param to mgmt_ev_pin_code_request

    Waldemar Rymarkiewicz authored Johan Hedberg committed
    Update mgmt interface with secure param in PIN code request event which
    is part of secure PIN requirement implementation.
  2. Add support for store_hint in mgmt_ev_new_key

    Johan Hedberg authored
  3. Remove unused old_key_type from mgmt_ev_new_key

    Johan Hedberg authored
Commits on Apr 27, 2011
  1. mgmtops: Add support for confirm_hint in mgmt_ev_user_confirm_request

    Johan Hedberg authored
    Since we don't yet have a proper Agent.ConfirmPairing D-Bus callback,
    and can't add one before 5.x just do an automatic reply for now.
  2. Use HCI_MAX_EIR_LENGTH instead of hard-coded value

    Bruna Moreira authored Johan Hedberg committed
Commits on Apr 6, 2011
  1. Add NOTICE and MODULE_LICENSE_GPL files.

    Jaikumar Ganesh authored
    Change-Id: Ibec15e1a8d9d23a0fe557ceb59ac2c80bbc5d6c3
Commits on Mar 31, 2011
  1. mgmt: Add support for discovering event

    Johan Hedberg authored
  2. mgmt: Add support for start_discovery & stop_discovery

    Johan Hedberg authored
Commits on Mar 30, 2011
  1. Add BT_POWER socket option.

    Jaikumar Ganesh authored
    BT_POWER socket option is used to control the power
    characteristics of the underlying ACL link. Currently, this is
    used to set the ACL link to active mode when the remote end has put
    the ACL link in sniff mode and we are sending data. By default,
    the ACL link will always be moved to active mode. However, this
    causes problems with HID devices. And hence, for HID devices the
    ACL link will not be moved to active mode when we are sending data.
    
    This socket option is implemented for both rfcomm and l2cap sockets.
    
    Change-Id: I0261a8daa2241d691670cc690cd27c39c67c1591
  2. Add missing NOTICE files.

    David Deephanphongs authored Jaikumar Ganesh committed
    Original commit: c3d03f1
    update by Jaikumar Ganesh for Bluez upmerge.
  3. Update userspace headers for SCO/eSCO packet selection in struct sock…

    Nick Pelly authored Jaikumar Ganesh committed
    …addr_sco.
    
    uint16_t sco_pkt_type is introduced to struct sockaddr_sco. It allows bitwise
    selection of SCO/eSCO packet types. Currently those bits are:
    
    0x0001 HV1 may be used.
    0x0002 HV2 may be used.
    0x0004 HV3 may be used.
    0x0008 EV3 may be used.
    0x0010 EV4 may be used.
    0x0020 EV5 may be used.
    0x0040 2-EV3 may be used.
    0x0080 3-EV3 may be used.
    0x0100 2-EV5 may be used.
    0x0200 3-EV5 may be used.
    
    This is similar to the Packet Type parameter in the HCI Setup Synchronous
    Connection Command, except that we are not reversing the logic on the EDR bits.
    This makes the use of sco_pkt_tpye forward portable for the use case of
    white-listing packet types, which we expect will be the primary use case.
    
    If sco_pkt_type is zero, or userspace uses the old struct sockaddr_sco,
    then the default behavior is to allow all packet types.
    
    Packet type selection is just a request made to the Bluetooth chipset, and
    it is up to the link manager on the chipset to negiotiate and decide on the
    actual packet types used. Furthermore, when a SCO/eSCO connection is eventually
    made there is no way for the host stack to determine which packet type was used
    (however it is possible to get the link type of SCO or eSCO).
    
    sco_pkt_type is ignored for incoming SCO connections. It is possible
    to add this in the future as a parameter to the Accept Synchronous Connection
    Command, however its a little trickier because the kernel does not
    currently preserve sockaddr_sco data between userspace calls to accept().
    
    The most common use for sco_pkt_type will be to white-list only SCO packets,
    which can be done with the hci.h constant SCO_ESCO_MASK.
    
    This patch is motivated by broken Bluetooth carkits such as the Motorola
    HF850 (it claims to support eSCO, but will actually reject eSCO connections
    after 5 seconds) and the 2007/2008 Infiniti G35/37 (fails to route audio
    if a 2-EV5 packet type is negiotiated). With this patch userspace can maintain
    a list of compatible packet types to workaround remote devices such as these.
    
    Change-Id: Ie6dc57a6a2d4ec4b42f919070d98d39f225eaf95
  4. Add ACL flow control state (MTU, packets available, packets total) fo…

    Nick Pelly authored Jaikumar Ganesh committed
    …r debug.
    
    Accessed with the debug tool 'hcitool con'
    
    Change-Id: I637d6ac9e2ca63c6e4fc1d24a149f73901704550
  5. mgmt: Add support for remote_name event

    Johan Hedberg authored
  6. Add MGMT_MAX_NAME_LENGTH define to mgmt.h

    Johan Hedberg authored
  7. Add HCI_MAX_NAME_LENGTH define to hci.h

    Johan Hedberg authored
  8. mgmt: Add support for device_found event

    Johan Hedberg authored
  9. Add HCI_MAX_EIR_LENGTH define

    Johan Hedberg authored
Commits on Mar 27, 2011
  1. @sjanc

    Add support for Out of Band (OOB) association model in mgmtops

    sjanc authored Johan Hedberg committed
Commits on Mar 21, 2011
  1. Change SDP socket path to be compatible for Android.

    Jaikumar Ganesh authored
    Original Change by Nick Pelly <npelly@google.com>
    
    Change-Id: Id33de250ab501a4d81ee143e6a01fe26abe31d07
  2. Add Android makefiles to Bluez.

    Jaikumar Ganesh authored
    This includes the following commits from previous versions:
    
    a) bluez: Add Android.mk for pand (off by default)
       b163e2b by <san@google.com>
    
    b) Add missing libbluetooth in linker commands for executables using libbluetoothd.
       3e442fe by <dougkwan@google.com>
    
    c) Edit makefiles to get network to work. Changed libglib to be a shared library
       fddb10d62d21580c49101c3dc4ab43f6619234c0 by Danica Chang
    
    d) Update Bluetooth configuration path: 0b25504e93b95a809e32227a3832bf08a3c13296
       by Jaikumar Ganesh
    
    Change-Id: I8e9e506cf5963b70456ecdb222b9cf2068b980da
Commits on Mar 15, 2011
  1. mgmt: Implement adapter name control

    Johan Hedberg authored
    This patch adds a new set_local_name command as well as a
    local_name_changed event to the management interface. Instead of 248
    bytes (like in the HCI spec) 249 bytes are always reserved for the name
    in the messages so that there's a guarantee of it being nul-terminated
    (this is not guaranteed on the HCI level).
Something went wrong with that request. Please try again.