0cb0e9346d4aa06f4a04261b6f99f5124c7c6cc8 |
|
19-Oct-2016 |
Jacky Cheung <jackyc@google.com> |
DO NOT MERGE ANYWHERE Add Wear-specific feature to override LE IO capability Force the first bond to use Just Works pairing when WEAR_LE_IO_CAP_OVERRIDE is set to TRUE. Bug: 32234733 Change-Id: I1732be86dd888586c603112fb6c3010974b54a13
/system/bt/btif/src/btif_storage.c
|
86453b65c60aec465f8e32cf515944f3f69db809 |
|
11-May-2016 |
Marie Janssen <jamuraa@google.com> |
btif: only save config when bonded devices change Bug: 27354612 Change-Id: I15f816c85d3ab1991abf076f7c1ae2914d773d54
/system/bt/btif/src/btif_storage.c
|
c7087d2466a291185853a6b2a16f789233e3420f |
|
18-Mar-2016 |
Ajay Panicker <apanicke@google.com> |
Add guest mode functionality (2/5) Add a flag to enable() to start Bluetooth in restricted mode. In restricted mode, all devices that are paired during restricted mode are deleted upon leaving restricted mode. Right now restricted mode is only entered while a guest user is active. Bug: 27410683 Change-Id: I8f23d28ef0aa3a8df13d469c73005c8e1b894d19
/system/bt/btif/src/btif_storage.c
|
95673843582fccf026d8af7592428f9b864f52fd |
|
11-Apr-2016 |
Andre Eisenbach <eisenbach@google.com> |
Move autopair blacklist to interop database Blacklist by partial name etc. was not working and had no effect; all BDAs in the config file start with 00:, which is implausible at best, so deleted... Added new mechanism to blacklist by BDA only initially and added Subaru car kit to blacklist. Bug: 27347017 Change-Id: Ie2941cb1ab663b5444b02c44f85032f13be4ab46
/system/bt/btif/src/btif_storage.c
|
20af7c3cc040e82124184ad869d840ad6fa1eacf |
|
28-Mar-2016 |
Ajay Panicker <apanicke@google.com> |
Revert "Add guest mode functionality (2/5)" This reverts commit 45ee419b233480060548f19b09de6726d28a06ea. Change-Id: I7d24acbe09305611c4e0bbfe7d40348d0fd1c365
/system/bt/btif/src/btif_storage.c
|
45ee419b233480060548f19b09de6726d28a06ea |
|
18-Mar-2016 |
Ajay Panicker <apanicke@google.com> |
Add guest mode functionality (2/5) Add a flag to enable() to start Bluetooth in restricted mode. In restricted mode, all devices that are paired during restricted mode are deleted upon leaving restricted mode. Right now restricted mode is only entered while a guest user is active. Bug: 27410683 Change-Id: I19ff91d1d7fb8c60230fee7a05d32574b5b2aeda
/system/bt/btif/src/btif_storage.c
|
1c4150bee59b5e3f76ddd54e1696f9e1e53dfede |
|
04-Mar-2016 |
Jacky Cheung <jackyc@google.com> |
Default missing DevType and DevClass in NVRAM. Missing DevType and DevClass in NVRAM were not properly set to a default values previously. Bug: 27852645 Change-Id: I79fbc333d7b6dda0fb795776b2dbe1e1e101352c
/system/bt/btif/src/btif_storage.c
|
5fe6f0cf6b223e3ed6be4912d55b3ed5b41ce0cd |
|
06-Feb-2016 |
Pavlin Radoslavov <pavlin@google.com> |
Removed checks for NULL returns after osi_calloc() / osi_malloc() Removed explicit checks for NULL pointer returns after calls to osi_calloc() and osi_malloc(), because those are not needed. If the memory allocation fails, osi_calloc() and osi_malloc() will trigger an assert. Bug: 27048759 Change-Id: I2791eb2f69c08f991f8fcdef10e101a41568cd95
/system/bt/btif/src/btif_storage.c
|
16856640e6179a73abf955e24dc7acf0699b66e4 |
|
30-Jan-2016 |
Andre Eisenbach <eisenbach@google.com> |
Fixed paired device config UUID parsing logic Also added unit tests to cover this bug. Bug: 26883553 Change-Id: Ice8641fad5c38ee43f1b080665dde70979f9d60f
/system/bt/btif/src/btif_storage.c
|
6b84f291c4edce7e4102efd8d4052a63bcb4b9dc |
|
05-May-2015 |
Anubhav Gupta <anubhavg@codeaurora.org> |
Support for A2DP Sink and Proper initialization of profiles - Register SDP and SEP (Stream End Point) for the profile whose init is called. We achieve this by making registration api aware of profile id being called. - Register A2DP Src + Avrcp Target + Avrcp Controller. We need to support Absolute Volume as well, so Avrcp Controller is required here. - Register A2DP Sink + Avrcp Controller. In this case we do not support absolute volume. Support would be added in AVRCP controller change - Adapter property is updated with profile ID for which init is called.This is required to make changes in btService for Profile initialization - Start listening for incoming AVRCP connection if we have only AVRCP Controller - Update default peer_features based on feature mask. In case of incoming AVRCP connection, SDP will be done later. In such a scenario default peer features sent to btif should be based on features-set selected during initialization. - Drop Control, Meta and Browse commands when TG is not up. - Not to call AVRCP app callbacks when mentioned service is down. - Close audio socket on suspend A2DP Sink: Support for AudioTrack - implemetation for audiotrack to take care of audio rendering - support for audio focus state in bluedroid Bluetooth: Support for Avrcp 1.3 Controller - support for SDP registration - support for sending vendor dependant commands - support for abs vol - support for receiving vendor dependant response - serialization of connection and rc_features callback Avrcp_Ctrl: handling of commands and events for AVRCP Controller - support of parsing cmd and event pdus - timeout handling Change-Id: I1e8d49b087eff6301373e1e90e8d868f15847c34
/system/bt/btif/src/btif_storage.c
|
258c2538e3b62a8cdb403f2730c45d721e5292b4 |
|
28-Sep-2015 |
Pavlin Radoslavov <pavlin@google.com> |
GKI cleanup - moved GKI buffer allocation wrappers to OSI * Moved the following GKI buffer allocation functions to OSI: - GKI_getbuf() -> osi_getbuf() - GKI_freebuf() -> osi_freebuf() - GKI_get_buf_size() -> osi_get_buf_size() For now we need the osi_getbuf() / osi_freebuf() allocation wrapper, because we need to be able to call osi_get_buf_size() on the allocated buffer. In the future those should be replaced with osi_malloc() / osi_free(). Currently, the osi_malloc() buffer size internal allocation tracker does not always track the size, hence we need the osi_getbuf() wrapper. * Replaced GKI_MAX_BUF_SIZE with BT_DEFAULT_BUFFER_SIZE * Added new file include/bt_common.h that can be usee to include few files that should be included alost everywhere (e.g. bt_target.h" NOTE: This file might be removed in the future and we should include everywhere the right set of header files. * Removed some of the GKI-related references * Removed file include/gki_target.h Change-Id: Ie87830e73143de200746d54235aa99f228a95024
/system/bt/btif/src/btif_storage.c
|
08393054f0867d0f86a7f9c2eb156e67a86382c7 |
|
07-Aug-2015 |
Marie Janssen <jamuraa@google.com> |
resolved conflicts for merge of 49a86709 to mnc-dev-plus-aosp Change-Id: Icd7ec2fd78ac4383da430708a88abaeba9009437
|
49a86709488e5cfd5e23759da18bf9613e15b04d |
|
08-Jul-2015 |
Marie Janssen <jamuraa@google.com> |
build: LOG_TAG consistency, include order, build fixes Fix the order of includes across a bunch of files, and declare LOG_TAG at the top of every file in which it is used. Consistently use bt_ as a LOG_TAG prefix. Fix issues with LOG macro usage. Remove unused includes and double-includes (when in related .h) Add includes as necessary to compile cleanly (problems surfaced by reordering includes) Change-Id: Ic55520c8302b06bbc1942c10c448b20844669da6
/system/bt/btif/src/btif_storage.c
|
e9d2d9bf736c83398be134d2b930fd2475a73145 |
|
24-Jul-2015 |
Arman Uguray <armansito@google.com> |
am f2d6434a: gn-build: Add bluetooth-service target * commit 'f2d6434a6b7ad98e20c7a601d2a0950237514837': gn-build: Add bluetooth-service target
|
f2d6434a6b7ad98e20c7a601d2a0950237514837 |
|
09-Jul-2015 |
Arman Uguray <armansito@google.com> |
gn-build: Add bluetooth-service target This patch makes the Bluetooth system service (service/) buildable using GN: 1. Added new BUILD.gn file for service/ 2. Added conditional compilation for global config paths, with TODOs for generalizing them later. 3. Added a shim for loading the Bluetooth library that calls hw_get_module on Android and explicitly calls dlopen on OS_GENERIC. 4. Fixed compile warnings and errors. 5. Did some minor clean up in gatt_server.cpp for better readability. Bug: 22124644 Change-Id: I3226537a3a5211a6762651a35707638df29956b0
/system/bt/btif/src/btif_storage.c
|
8ad14e310bf2e535c09e67c6a20e1caf989fb3a6 |
|
21-Jul-2015 |
Pavlin Radoslavov <pavlin@google.com> |
resolved conflicts for merge of 65f9c04a to mnc-dev-plus-aosp Change-Id: I4d7f657175347b2625f222b3cf6ab60fd37fb238
|
65f9c04aa36af5379ba3a28dba36a5de16686024 |
|
17-Jul-2015 |
Pavlin Radoslavov <pavlin@google.com> |
Fix the logic for removing bonded devices * Removed btif_storage_is_device_bonded(), because it is not needed, and it was giving the wrong answer in use cases like Smart Setup with BR/EDR connections. * Added a call to btif_storage_remove_ble_bonding_keys() within btif_storage_remove_bonded_device() so the bonded device state is properly removed. * Don't save the BLE bonding keys if it is temporary bonding Bug: 22233299 Change-Id: I33d9f76a124acc60173f0acaa517bc29ee6603e8
/system/bt/btif/src/btif_storage.c
|
9a78e8d25416325308fa700bb38459817eeb5c7a |
|
08-Jul-2015 |
Marie Janssen <jamuraa@google.com> |
am 49120dc8: build: Fix LOG_TAG define breakage, macro usage * commit '49120dc867c7818511b5afec461dfc97d17eef58': build: Fix LOG_TAG define breakage, macro usage
|
49120dc867c7818511b5afec461dfc97d17eef58 |
|
08-Jul-2015 |
Marie Janssen <jamuraa@google.com> |
build: Fix LOG_TAG define breakage, macro usage Fixes build breakages related to r.android.com/156982 Change-Id: Ib1143c41fe05a17c296226998afdb41a8cb6294a
/system/bt/btif/src/btif_storage.c
|
d33e39f14834ddfcfad27b9bef5ffb87919a8644 |
|
07-Jul-2015 |
Marie Janssen <jamuraa@google.com> |
am db554581: build: Update osi log functions, use consistently * commit 'db554581079863974af8e1289646f5deea6fc044': build: Update osi log functions, use consistently
|
e116777afad843f097c48755ef00fbb68969138a |
|
07-Jul-2015 |
Srinu Jella <sjella@codeaurora.org> |
am f1029c7a: Remove stored link key for temporarily paired devices * commit 'f1029c7afb9b4c9fcf95b3f98ce9c68b10d5a02c': Remove stored link key for temporarily paired devices
|
f1029c7afb9b4c9fcf95b3f98ce9c68b10d5a02c |
|
02-Sep-2014 |
Srinu Jella <sjella@codeaurora.org> |
Remove stored link key for temporarily paired devices Problem: Device shows up in paired list during just work pairing 1. Create a connection from DUT to remote. 2. Remove the link key in remote. 3. Send a file from remote to DUT. 4. Turn OFF BT. Turn ON. Failure: Device should not move to paired list after BT on/off as device removed from UI during just work pairing Root cause: remote device is not removed from btif but its removed from UI during justworks pairing Fix: remote device is removed from btif during justworks pairing to sync up UI and btif paired list Bug: 19417758 Change-Id: I73de0a94c4f7ada644d258790a9e3e4bf11fc4e5
/system/bt/btif/src/btif_storage.c
|
db554581079863974af8e1289646f5deea6fc044 |
|
26-Jun-2015 |
Marie Janssen <jamuraa@google.com> |
build: Update osi log functions, use consistently Update the LOG_* functions to take a tag argument which makes them more consistent with the Android Log.*(TAG, s) common syntax and removes some #define-dependency with osi/include/log.h. Also update to never use Android log functions directly. Also contains minor cleanup of some header includes. Bug: 21569831 Change-Id: If07385cafbea062232ecdbc7c673f908d5ef8921
/system/bt/btif/src/btif_storage.c
|
f4b0c9242b09316b228234219b67efcbffd7eaec |
|
13-Jun-2015 |
Arman Uguray <armansito@google.com> |
am cab5fc17: gn-build: Remove all -Wno-unused-* flags from build files * commit 'cab5fc179730ce6910989307680b275195876c4d': gn-build: Remove all -Wno-unused-* flags from build files
|
cab5fc179730ce6910989307680b275195876c4d |
|
02-Jun-2015 |
Arman Uguray <armansito@google.com> |
gn-build: Remove all -Wno-unused-* flags from build files This CL removes the -Wno-unused-variable, -Wno-unused-value, and -Wno-unused-function flags from all GN build and Android.mk files (except in test/ & tools/, which are not built using GN yet). Compile warnings, caused by the newly enabled flags, have been fixed throughout the code base. Bug: 21570302 Change-Id: I1c128b62256faa17668124798341005bcd0f7315
/system/bt/btif/src/btif_storage.c
|
ab813119d61a3ca8ac8ecb5239b73bf77e2c05bb |
|
11-Jun-2015 |
Andre Eisenbach <eisenbach@google.com> |
Fix more BLE_INCLUDED == FALSE build breakage Change-Id: I2da6dcdaced78d3a3bce6002fc3885c7480fba82
/system/bt/btif/src/btif_storage.c
|
eae61663a5c44f2a5757ae3df80cbc3b97fa6d60 |
|
02-Jun-2015 |
Pavlin Radoslavov <pavlin@google.com> |
Replace malloc/calloc/free with osi_malloc/osi_calloc/osi_free There were several leftover places that were still using malloc/calloc/free . Those are replaced to use osi_malloc/osi_calloc/osi_free like majority of the rest of the code. Note: There are few remaining places that are still using malloc/calloc/free: * Some of the unit tests * audio_a2dp_hw/audio_a2dp_hw.c It is used as part of the audio.a2dp.default.so library, and the bluetooth.default.so library Its usage of malloc/calloc/free should be refactored independently. Change-Id: Iafbed996e5f1ae8eb1343fb2acfadf32e515e419
/system/bt/btif/src/btif_storage.c
|
818d0f2afb10c75125b0df9ea2bce6108268a269 |
|
21-May-2015 |
Casper Bonde <c.bonde@samsung.com> |
SAP: Make it possible to enforce a 16-digit pin code (1/5) This change enable the posibility to enforce using a 16-digit pin or MITM for a RFCOMM or L2CAP connection. This is needed for the SIM access profile. Change-Id: I02886ce284f27295205def3c66fb76372f5dab4f Signed-off-by: Casper Bonde <c.bonde@samsung.com>
/system/bt/btif/src/btif_storage.c
|
033edab9780481ca743d1f14cc893dc533c3c3f2 |
|
07-May-2015 |
Satya Calloji <satyac@broadcom.com> |
Fix GATT connection failure after BT reset Handles the address type incorrect value storage issue and removes usage of DMT supported flag which was based on legacy code Bug: 20912064 Change-Id: I5bd20dc9cd0997ac3dbd4b346cc0513f1809f241
/system/bt/btif/src/btif_storage.c
|
56a3be0d6eaa1bc264736e399fb32d3094f0b513 |
|
02-Jun-2015 |
Pavlin Radoslavov <pavlin@google.com> |
Replace malloc/calloc/free with osi_malloc/osi_calloc/osi_free There were several leftover places that were still using malloc/calloc/free . Those are replaced to use osi_malloc/osi_calloc/osi_free like majority of the rest of the code. Note: There are few remaining places that are still using malloc/calloc/free: * Some of the unit tests * audio_a2dp_hw/audio_a2dp_hw.c It is used as part of the audio.a2dp.default.so library, and the bluetooth.default.so library Its usage of malloc/calloc/free should be refactored independently. Change-Id: Iafbed996e5f1ae8eb1343fb2acfadf32e515e419
/system/bt/btif/src/btif_storage.c
|
7cb76b4277d603e5abfe7f9222a45ebdf7a715e2 |
|
07-May-2015 |
Satya Calloji <satyac@broadcom.com> |
Fix GATT connection failure after BT reset Handles the address type incorrect value storage issue and removes usage of DMT supported flag which was based on legacy code Bug: 20912064 Change-Id: I5bd20dc9cd0997ac3dbd4b346cc0513f1809f241
/system/bt/btif/src/btif_storage.c
|
e87ef6dba42ebaa94c7f0200d9e5223d1259b9d9 |
|
01-May-2015 |
Andre Eisenbach <eisenbach@google.com> |
Use BTM structures for LE pairink keys and store LTK The long term key (LTK) was not assigned to the correct struct element before saving the key to NVRAM. Change-Id: Icfce82f5b70518e725875771756edde0b9caeb88
/system/bt/btif/src/btif_storage.c
|
97bcfbe83216e6a76c0ad0c27fb2cc33494acc61 |
|
29-Apr-2015 |
Andre Eisenbach <eisenbach@google.com> |
Add LE device to device database before adding LE keys A small bug in btif_read_le_key() would prevent a paired LE device from being added back into the internal device database after reboot, causing the security keys not being loaded. Also added a debug statement to trace keys being loaded. Bug: 20091926 Change-Id: Id2d6c69497857edc21e2d4c6a67ad9e8dadabcaa
/system/bt/btif/src/btif_storage.c
|
e28055315f96c0d06e73a66a9bb06df85247b5a7 |
|
22-Apr-2015 |
Chaojing Sun <cjsun@broadcom.com> |
Cross transport key mapping fixes Change-Id: I22d97303054eccc876c4a9c7c0a50e369ff4fa62
/system/bt/btif/src/btif_storage.c
|
2cd086a11a972f2e437dd521a121ed76ea79a15a |
|
15-Apr-2015 |
Vinit Deshpande <vinitd@google.com> |
am f29a2fb..e07ad10 from mirror-m-wireless-internal-release e07ad10 merge in m-wireless-internal-release history after reset to d232721ae5e5b6949a5249f0d116408b8a3c5f1d d232721 L2CAP socket - fix merge errors 899b771 BR/EDR secure connections support 7fb0da6 Support numeric comparison in SMP aa351f2 merge in m-wireless-internal-release history after reset to 399e89150b3df87172bdf92d54712b379324b149 399e891 Fix for AVRCP CTRL stops sending pass through command daddea9 Free Avrcp Controller callbacks on Cleanup 764babe Protect reset of out stream with mutex 444a8da LE Privacy 1.2 and LE secure connections 8372aa5 L2CAP and SDP Search API for BT profiles (2/2) fd422a7 Update Service Availability. 2a0652a merge in m-wireless-internal-release history after reset to 0b47e0a35c16f5b7d77c30ec1c095ed92ff4fd74 78d0f4c merge in m-wireless-internal-release history after reset to m-wireless-internal-dev 0b47e0a Avoid duplicate disconnection callbacks for fixed channel connections 5646973 Add a section on assertions to the style guide. d768767 Merge "Avoid null-pointer dereference in l2c_release_lcb()" into m-wireless-dev ef92b53 Avoid null-pointer dereference in l2c_release_lcb() 4bf68bf merge in m-wireless-internal-release history after reset to f538707fe64c62b1dbb8e4210e4a1bfa0bab2b56 de6ac86 Add a 'Bluedroid conventions' section to the style guide. 1b80439 Add a section to the style guide on variable declarations. 485f19e merge in m-wireless-internal-release history after reset to 4540f59bc447dc2b7b31a3e974b74a60b2417e7d bef8940 merge in m-wireless-internal-release history after reset to 841c9103cad1898ceca87b734acd4d4537f9f452 ab4c38c merge in m-wireless-internal-release history after reset to a7e698f5a9e062f62e21bc435643975c30bab846 2807a74 merge in m-wireless-internal-release history after reset to a7e698f5a9e062f62e21bc435643975c30bab846 99dbe9a merge in m-wireless-internal-release history after reset to 78c0b060f29b7b7014adddb2f98bf6ae9755c488 f7f8399 merge in m-wireless-internal-release history after reset to a5371c238b4e874d8313ac56a23451e7345ff541 3aa60d7 Make A2DP audio HAL a shared library again 3256a31 Move unused include file out of hci_audio.h b866b69 Add option for schedule_next_instance to force rescheduling 4ae5e3e Ensure alarms are called back when they expire in the past a7bd03e Rewrite alarms to use a single posix timer instance 88e7b15 Resolved hardware error observed during SCO Connection setup Change-Id: Ib9a0a2ffca1d4811a9a9e56674bf43275d8b2205
|
444a8da807abaf5f9e813ce70c56a79160495fb3 |
|
06-Mar-2015 |
Satya Calloji <satyac@broadcom.com> |
LE Privacy 1.2 and LE secure connections Bug: 19816438 Original author: Chaojing Sun <cjsun@broadcom.com> Change-Id: I5951f4d4e038f8348a62aa6d19b2111bae0b3ecc
/system/bt/btif/src/btif_storage.c
|
b246a1a750c5a337faaa6033b39e78c8bdd4c2fb |
|
10-Apr-2015 |
Prerepa Viswanadham <dham@google.com> |
Merge commit '4bf68bf020c7fd1aabcdc4b5d8f5fbb8bacdec9d' into merge_work Change-Id: Ibc6d6e691b7f97611d16f96220346dfd6ffbbf52
|
47d68ee6229ccec3deeaaf694fa86438d97333a4 |
|
03-Apr-2015 |
Scott James Remnant <keybuk@google.com> |
osi: add compat code for glibc glibc doesn't declare strlcpy(), strlcat() or gettid(). Add a header of compatibility routines that only get included when compiling on this. Change-Id: I889ac7f1d22cf7056757890fcff0403107488d62
/system/bt/btif/src/btif_storage.c
|
e1a9e52ff59d36bd1bb5b7b3a02fafba6394edfe |
|
31-Mar-2015 |
Etan Cohen <etancohen@google.com> |
Merge commit 'f7f839985b3931682363d2ef3b7c5cae55a842ee' into merge Change-Id: Iaaec1ea0bf3009b7e32a9a60f697631a3f56e889
|
f8027005333c88a2f097cfd70d15c3d54c7764ae |
|
12-Mar-2015 |
Chris Manton <cmanton@google.com> |
Demote, cleanup and extend observed logging
/system/bt/btif/src/btif_storage.c
|
95b74f252f534ec757aab1fc08e086e02b2cfe8d |
|
12-Mar-2015 |
Sharvil Nanavati <sharvil@google.com> |
Use fully qualified path for btcore includes.
/system/bt/btif/src/btif_storage.c
|
0f9b91e150e153229235c163861198e23600e636 |
|
12-Mar-2015 |
Sharvil Nanavati <sharvil@google.com> |
Use fully qualified path for OSI includes.
/system/bt/btif/src/btif_storage.c
|
8ff3fea05b0d01f7a011326542161f892e2b31d6 |
|
07-Jan-2015 |
Chris Manton <cmanton@google.com> |
Rename legacy uuid_copy to not conflict
/system/bt/btif/src/btif_storage.c
|
44802768c447ab480d4227b3a852a97d923b816d |
|
24-Dec-2014 |
Sharvil Nanavati <sharvil@google.com> |
Add platform-independent logging macros to OSI. These macros should replace ALOG* and the various trace macros used throughout bluedroid. This change eliminates all uses of the ALOG* macros in favor of the new ones.
/system/bt/btif/src/btif_storage.c
|
9609cee33087141eeb7b5adede488d7e13bfcebd |
|
16-Oct-2014 |
Sharvil Nanavati <sharvil@google.com> |
Use correct service ID for A2DP source to make way for A2DP sink.
/system/bt/btif/src/btif_storage.c
|
794f3b5f126fffc3dd1129a710187591348bbf23 |
|
01-Oct-2014 |
Chris Manton <cmanton@google.com> |
Removal of bd.[c|h] Consolidate legacy types into bt_types.h
/system/bt/btif/src/btif_storage.c
|
8a6a89faa942aed4f176b0c98402d01c8bdd6aa6 |
|
20-Aug-2014 |
Sharvil Nanavati <sharvil@google.com> |
Introduce btcore, a low-level library to manipulate Bluetooth data types. This change adds a single module to btcore: bdaddr. The bdaddr module is reponsible for manipulating and working with Bluetooth addresses.
/system/bt/btif/src/btif_storage.c
|
9d52f88bfc07556cb01ab3055f5b1242c9b467aa |
|
19-Aug-2014 |
Sharvil Nanavati <sharvil@google.com> |
Eliminate unused arguments to btif_config and clarify variable names
/system/bt/btif/src/btif_storage.c
|
b95c4ef4ac9e86953050a7ae6b3b4260df935713 |
|
16-Aug-2014 |
Sharvil Nanavati <sharvil@google.com> |
Switch over from an XML based file format to .INI-style conf files This change moves us to using a single file format for all configuration throughout bluedroid. I've provided a transcoder that converts the previous config file to the new format so settings will be preserved. In a future revision of bluedroid, we should remove the transcoder and drop our dependency on tinyxml2.
/system/bt/btif/src/btif_storage.c
|
11cf5ccd5cd6dd1568bf69e4b6cbc27c95f5026d |
|
11-Dec-2014 |
Chih-Hung Hsieh <chh@google.com> |
resolved conflicts for merge of ed0bdd42 to lmp-mr1-dev-plus-aosp Change-Id: Ife8b72d3688ed78a95ccb8d5e0b60f40e7fec9e9
|
104e3f238f500cacdb8afaccdc672dfc34eae7ee |
|
12-Nov-2014 |
Bernhard Rosenkränzer <Bernhard.Rosenkranzer@linaro.org> |
Cleanups needed to make clang happy This patch removes a slew of unused variables and some unused functions, fixes some incomplete initializations of structs and an sprintf parameter mismatching the format string. Change-Id: I35f22fdccc8350f885cd357d3685b869224fa433 Signed-off-by: Bernhard Rosenkränzer <Bernhard.Rosenkranzer@linaro.org>
/system/bt/btif/src/btif_storage.c
|
5e808468e0667a6a2a8a1e6de80efbc4f42fa0f0 |
|
21-Oct-2014 |
Andre Eisenbach <eisenbach@google.com> |
LE: Do not remove bond on encryption failure If the encryption fails during the re-connection process with a previously paired LE device, the pairing is removed. Thus, a single connection failure could lead to the device be unpaired. This patch prevents unpairing when encryption fails. Additionally, the IRK is restored from NV ram to fix reconnection to dual-mode devices. Bug: 18072300 Change-Id: I077a16d0715fdaa07b95b1c664c18bd839754896
/system/bt/btif/src/btif_storage.c
|
afa6e1abbedaad8fe854b0f43999b8aeb801af91 |
|
28-Jun-2014 |
Matthew Xie <mattx@google.com> |
resolved conflicts for merge of e8c3d75b to master Change-Id: I78ef69c4d54a36243620ae14296d3507e3339567
|
d5ebf6b695a5b40563b5fddca97c0591e39557f1 |
|
28-Jun-2014 |
Matthew Xie <mattx@google.com> |
handle link key check in non_ble case Change-Id: Ibbdf3c4fbff9e53f8e2a85db9d6de62cd2925c60
/system/bt/btif/src/btif_storage.c
|
e8c3d75b75493911ebf0f99c83676359657178f7 |
|
04-May-2014 |
Sharvil Nanavati <sharvil@google.com> |
Logging cleanup: BTIF and APPL. Change-Id: I5b1214642bbb4b9aecc0fd2c899a6ec2c9793286
/system/bt/btif/src/btif_storage.c
|
f281b43fbf6832b80651e0dbf300294ba9808f20 |
|
15-May-2014 |
Priti Aghera <paghera@broadcom.com> |
Reload Hid info only for bonded device Check if the device is bonded before loadind HID device information after BT reset. If the HID info exists in NVRAM for unbonded device, the device will not be able to repair. bug 14837902 Change-Id: I5e6d5e8c5344ca8ae18f102e40867745d3f460ab
/system/bt/btif/src/btif_storage.c
|
479a9a3750e243b40663ddbd1ac44d4fc1c3ec4e |
|
04-Jun-2014 |
Sharvil Nanavati <sharvil@google.com> |
Parse auto_pair_devlist.conf file with the generic config parser. Change-Id: Idfd1aca2417d74725a8f9ac67b1ca946a33bf14d
/system/bt/btif/src/btif_storage.c
|
ed999f5e92ef9e718f4e6a5d6e68caf1001961c8 |
|
05-Jun-2014 |
Matthew Xie <mattx@google.com> |
Save remote device name immediately bug 7381249 Change-Id: Ief1910c608116ebc28f5dc3e5804be65797ec53c
/system/bt/btif/src/btif_storage.c
|
1025687c6679608fe9df918f37011414ffc72b62 |
|
19-Aug-2013 |
Hemant Gupta <hemantg@codeaurora.org> |
[2/4] Bluetooth: Add support for HFP Client role. Implementation changes in BTA and BTIF layer to support HFP Client role. Change-Id: I9f939c18e8f989a50f298d0b313c5a0959c030a7
/system/bt/btif/src/btif_storage.c
|
740def526e757f5ea8f30d9d28d1e7a668dadc42 |
|
04-May-2014 |
Sharvil Nanavati <sharvil@google.com> |
Eliminate dead code (helped by compiler warnings). I've removed all functions that the compiler decided were unused. Change-Id: I0cbddf874ebd1586abe29b80e8d6390680679542
/system/bt/btif/src/btif_storage.c
|
fbf76881316471faf631dc543089efaeaf72df8d |
|
06-Jan-2014 |
Hemant Gupta <hemantg@codeaurora.org> |
GAP: Update local device name immediately Though the function btif_config_set_str requests to save device name immediately, sometimes it doesn't call save device name if the cached changes are more. So calling the "btif_config_save" explicitly to avoid failure cases. Change-Id: I9fb05caf284d6a6feb906f87a4db19896182d2c9
/system/bt/btif/src/btif_storage.c
|
8fe58875ce67c6e1099e7ba2339dcd2b979491b0 |
|
17-Apr-2014 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
Merge BT 4.1 features The features include: - LE Peripheral Mode - Link Layer topology (LE Central & Peripheral Concurrency) - Dual Mode Topology (Ability to choose LE transport when connecting with other Dual Mode devices) - Fast advertising Interval - Limited Discovery Time Changes - GAP Authentication and Lost Bond - Dual Mode Addressing - Common Profile and Service Error Code - 32 bit UUIDs Change-Id: Ic6701da4cf6aaa390ff2c8816b43157f36b7fb42
/system/bt/btif/src/btif_storage.c
|
a7ea809912e5a945d657957491753260826422f4 |
|
27-Nov-2013 |
Zhihai Xu <zhihaixu@google.com> |
Bluetooth: GAP: Remove bonded device info on Authentication fail Remove bonded device information from the BT-IF layer storage on authentication failure if already bonded with just works model. from QCOM Change-Id: Ia3c1635c446f39b1dbd4cdd0122c2f70cbbc8dd7
/system/bt/btif/src/btif_storage.c
|
6efaf223753108aa84f55332898340db0c9d5ebf |
|
27-Jan-2014 |
Zhihai Xu <zhihaixu@google.com> |
bluetooth: hid: store ssr_max_latency and ssr_min_tout in bonding db Store the ssr_max_latency and ssr_min_tout parameters in the bonding database. Previously these parameters were not stored for HID devices. This caused an inconsistency in sniff behavior between when the HID device was paired and following a reboot of the host. When the HID device is paired the SSR parameters are retrieved from the HID device and are stored in the HID Host's device list. If the host is rebooted then the HID Host's device list is constructed from the bonding database. If the SSR max latency is non-zero then the SSR parameters are sent to the firmware and SSR is used. In the event that the SSR max latency is 0, as it is if the parameters are not found, then SSR is disabled. Bug: 12764547 Change-Id: I63637575fdfcf4cb4ca0ce8dc2e4ccda9cccaf66 Signed-off-by: Adam Hampson <ahampson@google.com>
/system/bt/btif/src/btif_storage.c
|
7e6b379268f973752863e333b55e6068373e1664 |
|
24-Feb-2014 |
Matthew Xie <mattx@google.com> |
am 9d368b68: am 1292dd82: am 6bc62a36: Merge "Bluetooth: GAP: Update bonded device info immediately on NVRAM" * commit '9d368b68841dee6e6f581a3890433dcdc022fbb8': Bluetooth: GAP: Update bonded device info immediately on NVRAM
|
1292dd82812d76c54568796fbdafd1fdadc816eb |
|
24-Feb-2014 |
Matthew Xie <mattx@google.com> |
am 6bc62a36: Merge "Bluetooth: GAP: Update bonded device info immediately on NVRAM" * commit '6bc62a368da0a434a4e01f7bcb3273bd52a07568': Bluetooth: GAP: Update bonded device info immediately on NVRAM
|
377cb1407ee6ee1ff91b15bfa7052abed1023d18 |
|
20-Nov-2013 |
Sunny Kapdi <sunnyk@codeaurora.org> |
Bluetooth: Cleanup bt_config.xml during BLE Scan BLE Scan needs to clean up the bt_config.xml periodically so that new entries could be added to bt_config.xml. Also, there is no need to add BLE Random bd_addr to the bt_config.xml Change-Id: I00ba2e50dd39a021099052cb569786f6cb2cc8b9 b/12912008
/system/bt/btif/src/btif_storage.c
|
5e08d1ec92555e2cb3d80f1a9a3c746c76ed3e5d |
|
21-Nov-2013 |
Srinu Jella <sjella@codeaurora.org> |
Bluetooth: GAP: Update bonded device info immediately on NVRAM As the new bt-if config updation have delay in writing items to the NVRAM, some times there is a chance of not updating incase of battery removal happens before the actual write onto NVRAM. As the bonded device info is important data to store, it will update bonded info immediately onto NVRAM. Change-Id: I9699c8225a77d9272420334b4c76b3c1df87e459
/system/bt/btif/src/btif_storage.c
|
2a2701cdddac0859a95e58aec542742c450145b9 |
|
16-Sep-2013 |
Kim Schulz <k.schulz@samsung.com> |
Fixes for problems found with coverity analyzer - fixed UNINITIALIZED variable (hdl) in bta_hh_act.c :220 - fixed possible RESOURCE LEAK in btif_config_util.cpp in relation to open_file_map() if file is fd size=0 - fixed possible RESOURCE LEAK in create_socket_server() in uipc:196 (s not closed) - fixed possible OVERRUN in l2c_csm.c, (l2c_csm_config), array "l2cb.fixed_reg" of 4 20-byte elements at element index 60 (byte offset 1200) using index "p_ccb->local_cid - 3" (which evaluates to 60) - fixed possible OVERRUN in btm_pm.c, (btm_pm_reset) array "btm_cb.acl_db" of 7 288-byte elements at element index 7 (byte offset 2016) using index "btm_cb.pm_pend_link" (which evaluates to 7). - fixed possible OVERRUN in btif_storage.c, (btif_storage_add_device_to_autopair_blacklist) array "input_value" of 20 bytes by passing it to a function which accesses it at byte offset 20 using argument "20U". patch set 2: - fixed {} Patch set 3: - fixed review commment in stack/btm/btm_pm.c:379 bug: 10777562 Change-Id: I2a6d57f93acaaf9b25c49a6a29cb60d0e1e3c5d8
/system/bt/btif/src/btif_storage.c
|
b0a43da3b412f53557125bf352dd9dddfd1a9991 |
|
24-Sep-2013 |
Kim Schulz <k.schulz@samsung.com> |
memset arguments wrongfully swapped the arguments for one of the memset calls was wrong. Bug: 10907215 Change-Id: Ie00a3a6b829b99fd94659a764b6f0309684d9303
/system/bt/btif/src/btif_storage.c
|
7939ed0c9a50c769e9e648a2d7751e0894b485ed |
|
28-Sep-2013 |
zzy <zhenye@broadcom.com> |
added filter remove api to control the # of child node for bt_config.xml Bug 10949832 Change-Id: I10589b9d0a0b4b8d7cbf66122c66bb2e99be04a1
/system/bt/btif/src/btif_storage.c
|
76d041f915e4c14b3fb11bae3c12fcb59f77bef5 |
|
10-May-2013 |
Matthew Xie <mattx@google.com> |
am e1405531: am e915116a: Merge "Solve compilation problem when BLE/GATT/SMP features are false" into jb-mr2-dev * commit 'e1405531f637a3851371a2a2c624ff3db5e074fa': Solve compilation problem when BLE/GATT/SMP features are false
|
fc4b2f1953dbe60464d0f5ef7daaa10001fbc62f |
|
07-May-2013 |
Matthew Xie <mattx@google.com> |
Solve compilation problem when BLE/GATT/SMP features are false bug 8664724 Change-Id: I582846ccf4b8995f298d8db533488fceb7993ae3
/system/bt/btif/src/btif_storage.c
|
6ded3e4bc35c9878771a59cb8cc75b702c2097fd |
|
24-Apr-2013 |
Priti Aghera <paghera@broadcom.com> |
am f9020d0d: am f8f30c2c: HDP fix for Single SDP record * commit 'f9020d0de5c8ade5fab86b26979620aac4f67dc9': HDP fix for Single SDP record
|
f8f30c2cecf221b2c3983b72d5a849d799c39dd7 |
|
03-Apr-2013 |
Priti Aghera <paghera@broadcom.com> |
HDP fix for Single SDP record Modified stack code to support single SDP record for each register app call. bug 8656462 Change-Id: I92570243306d5c1ca8339042eba5733e43fdb72c
/system/bt/btif/src/btif_storage.c
|
7fe56f58c2a3cf0ac80177aaa890c143cd5fd950 |
|
29-Mar-2013 |
Priti Aghera <paghera@broadcom.com> |
Save the HID info into storage while adding device Previously HID device info was not saved immediately to NVRAM, thus when device was rebooted sometimes the hid information was missing from NVRAM, thus host does not identify the HID Device bug 8192743 Change-Id: I7ca8b607399e141fa851242e83c1c6d3854384f8
/system/bt/btif/src/btif_storage.c
|
ead3cde4bac0c3e32cd31f149093f004eef8ceeb |
|
06-Feb-2013 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
Initial version of BLE support for Bluedroid Change-Id: I9825a5cef9be2559c34c2a529b211b7d471147cf
/system/bt/btif/src/btif_storage.c
|
689d66b6559dcb3a0ad7f6cc33b6129e50910253 |
|
13-Dec-2012 |
The Android Open Source Project <initial-contribution@android.com> |
Snapshot 9fd57cbacd95e89602f430244c35bbc67f08b6d2 Change-Id: Ibc3a4bf4161d286c7cfab89a19c676eb5cc9224f
/system/bt/btif/src/btif_storage.c
|
5738f83aeb59361a0a2eda2460113f6dc9194271 |
|
13-Dec-2012 |
The Android Open Source Project <initial-contribution@android.com> |
Snapshot cdeccf6fdd8c2d494ea2867cb37a025bf8879baf Change-Id: Ia2de32ccb97a9641462c72363b0a8c4288f4f36d
/system/bt/btif/src/btif_storage.c
|