summaryrefslogtreecommitdiffstats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'LA.BF64.1.2.2_rb4.7' of ↵Steve Kondik2015-11-161-7/+9
|\ | | | | | | git://codeaurora.org/platform/vendor/qcom-opensource/bluetooth into cm-13.0
| * Bluetooth: Create ftp sdp record in accept threadNitin Shivpure2015-10-301-7/+9
| | | | | | | | | | | | | | | | | | | | A case, where BT On/Off is running into loop, In failure case it was stuck while creating ftp record, which was processing in bt process main thread, which leads ANR. Hence creating ftp sdp record in accept thread to avoid ANR. CRs-fixed: 931421 Change-Id: Id6938a8c51e44b787c68ca6a5a551856bdff0f89
* | BluetoothExt: Cleanup CAF stringsMichael Bestas2015-11-078-19/+19
|/ | | | Change-Id: I00782b8e5656d8356a843dcc8b862275a04eba5a
* FTP: Get External mount points from StorageManager volume list.Ashwini Munigala2015-10-061-3/+19
| | | | | | | | | | Fetch external primary and secondary storage mount points from system StorageManger volumes list instead from obsolete Environment.getExternalStorageDirectory() API and System.getenv(ENV_SECONDARY_EXTERNAL_STORAGE) variable; Change-Id: I33c72e194b7a10662bffcf94d33231f0da0bf140 CRs-Fixed: 919025
* Bluetooth-Wipower: Wipower refactoring.Kiran Kelageri2015-08-042-1212/+0
| | | | | | | Wipower code move from aosp (packages and frameworks) to vendor on M. Change-Id: I632d456acc99f53c482c828a9b44b2bea8a7d7fb
* Fix compilation issues in FTP and DUN codeHemant Gupta2015-07-204-22/+127
| | | | | | | This patch fixes compilation issues in DUN and FTP code due to changes in SDP API's Change-Id: Ie59c30c5135df4a0a81e6a316c4e758f6a121495
* Bluetooth-Wipower: Fix for missing PAE.Kiran Kelageri2015-06-231-0/+3
| | | | | | | Power disable command is sent before sending enable command such that FW could reset OWI state. Change-Id: I505b3ca1281ebc2e9915f04ea7d623cdab5b6211
* Muliuser: Check for calling user before starting service.Hemant Gupta2015-05-223-0/+117
| | | | | | | Check for calling user before starting service Change-Id: Ibadfa84c5fbf3c1c2aec9579c83a3f324010c259 CRs-Fixed: 841500
* Bluetooth-Wipower: Fix for missing PAC and permission API.Kiran Kelageri2015-04-301-10/+12
| | | | | | | | | | | a> fix ofr Missing power apply command(long duration) during disconnection. b> Add change to enable charging based on charge output and permission parameter as per PTU. Change-Id: I3d47a9722970c195ecb183450b7272fd44363d48 CRs-fixed: 827874 CRs-fixed: 827864
* Bluetooth-Wipower: change in Optional Fields and Vrect_min_static val.Kiran Kelageri2015-04-281-5/+6
| | | | | | | | | | | a> Adjust Vrect_min_static from 7V to 7.1V. b> When Output is disabled, optional field Validity must be set to 1. In addition, Vrect_high must be set to 19.3V when output is disabled. c> Reset dynamic values to default on disconnect. d> Adjust Vrect_set_static from 7V to 7.1V. Change-Id: Ida51d7014999eee155487cb95cfddbd26ebe8ddb CRs-fixed: 823217
* Bluetooth-Wipower: Fixed the issues identified during A4WP PF#8Kiran Kelageri2015-04-221-35/+33
| | | | | | | | | | | | | | | | The changes ensures: 1> PRU doesn't start charging until PTU request to enable charge output is been sent. 2> PRU starts charging based on data events sent from stark and abiding to the voltage conditions as per spec. 3> Doesn't set charge port if it was disbaled on 2nd static PRU parameters read from PTU during connnection. Change-Id: Ife87d985697eda074e7f9d2e919d1fa44b768333 CRs-fixed: 820419 CRs-fixed: 820423 CRs-fixed: 820429
* Merge "Bluetooth-WiPower: Fixed the issues identified during A4WP PF#8"Linux Build Service Account2015-04-211-18/+31
|\
| * Bluetooth-WiPower: Fixed the issues identified during A4WP PF#8Umesh Vats2015-04-101-18/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1. PRU was not enabling data notifications from FW until the PTU enables PRU's charge output. This resulted in dynamic messages from PRU to PTU with stale/invalid values for Vrect and IRect. Now, PRU enables data notifcations from FW as soon as it receives the request for PRU static parameter read from PTU. 2. If PRU is quickly removed after placing it on the PTU, sometimes it doesn't disconnect. The issue happens when PRU hasn't started the data notifications monitoring timer before its removed from PTU. Now: a. PRU starts data notification monitoring timer as soon as it ' enables data notifications from the FW. (Wipower service change) b. PRU handles WBC event for PTU presence. If PTU is not present, then disconnection with PTU is initiated. (A4wp app change) Change-Id: I07eb8f64602a2a750731f67b0a407bf716ee08e8 CRs-Fixed: 818371 CRs-Fixed: 818364
* | SAP: Update the exit flags and flush streams properlySmriti Gupta2015-04-101-2/+11
|/ | | | | | | | | | | This patch is required to update the IntExit flag whenever there is some exception resulting in timing issues which prevented Sapservice from listening on Rfcomm socket. Also streams are now flushed whenever required for the proper communication with the sap daemon. Change-Id: I8e02e5b56d5fcc5d3a5e03abcc716a03f2ee6694 CRs-Fixed: 815103
* FTP: Fix ANR caused from re-trials to start serverSocket listener.Ashwini Munigala2015-04-071-0/+8
| | | | | | | | | | | Current implementation support re-try mechanism to start FTP server socket listener while it fails on first attempt till 10 subsequent attempts with a waiting timeperiod of 300msec for each trial. Check for mAdapter and BT STATE to fix ANR caused from re-trial attempts to start serverSocket listener while BT being Turning OFF. Change-Id: I97610e876cd4dfd0044bbd3f483e440958938187 CRs-Fixed: 804823
* Bluetooth-Wipower: Fix for crash during gatt read request.Kiran Kelageri2015-03-201-15/+46
| | | | | | | Read/Write support is been added for A4WP prucontrol characteristic. Change-Id: I0086b1abc8e97c8d12f834fe6bdbbe0a13c380b3
* Bluetooth-WiPower: Prevent duplicate power apply commands, send PRU alertUmesh Vats2015-03-161-8/+20
| | | | | | | | | | | | | | | | | | notifications only in connected state, don't release the wake lock when disable charge output is received 1. WBC driver can generate spurious/duplicate Wipower charge complete events. BT FW can get into bad state if host sends power apply command in the connected state. To prevent this, additional checkks are being added. 2. PRU alerts should be sent only if PRU is connected to PTU. Otherwise, crashes can result in race conditions. 3. Wake lock should not be released when "Disable Charge Port" command is received from PTU. Otherwise, PRU can get into deeper sleep state resulting in timeouts at PTU for dynamic parameter reads. This will in turn cause BLE connection to be terminated. CRs-Fixed: 807683 Change-Id: I01edd435f031e41a1544641ac232d09a0a44ac75
* BluetoothWiPower: PRU Alert notifications(Interface change)Umesh Vats2015-03-121-40/+9
| | | | | | | Changes in the interface for passing alerts to Wipower App Some log messages are also fixed. Change-Id: I160fee6f7d2ff0bd45149b8a7e51cff01a3addf7
* Bluetooth-WiPower: Support for PRU alert notificationsUmesh Vats2015-03-101-24/+103
| | | | | | | Support for PRU Alert notifications as per A4WP spec added Change-Id: I7c87292edbb8f718debedce49cafe9d65581488c CRs-Fixed: 797727
* Bluetooth-WiPower: DUT disconects 10 seconds after connection to iPadUmesh Vats2015-03-101-1/+25
| | | | | | | | | | | | | | | Two problems identified in the WiPower app: 1. Same UUID is being reused for PRU Alert characteristic and PRU Alert character Descriptor. 2. The PRU Alert description is being registered by the app, but onDescriptorReadRequest is not implemented The fix is: 1. The UUID value for the PRU alert descriptor has been modified to a different UUID. 2. onDescriptorReadRequest() is implemented. Change-Id: I933476d614aebc637a6ebcd6f0459a1ed5093a7b CRs-Fixed: 795938
* Wipower-Bluetooth: Host Changes for advertisment offloading.Kiran Kelageri2015-03-101-42/+15
| | | | | | | | Advertisment is offloaded to firmware to accomodate A4WP spec timelines. Change-Id: I22426133f991073cb0571a0b7fc8c6c36aa43bdd CRs-fixed: 797885
* Bluetooth-Wipower:Fix for re-connect and Vrect_max value change.Umesh Vats2015-03-101-1/+6
| | | | | | | | | | | 1> It was observed that in some cases, PRU was not sending advertisements after disconnection(enablePowerApply OFF). The code changes are done to take care of this issue. 2> Vrect_max values changed from 18V to 19.3V. Change-Id: I8b7017cf4b0e544f89668f421fa353dab1ce6df4 CRs-fixed: 769853, 791497
* Bluetooth-Wipower:PRU re-enables Charge port after disabling.Umesh Vats2015-02-231-11/+26
| | | | | | | | | PRU enables the charge port whenever the dynamic paramters are non zero and vrect > vmin. Now additional check is added. PRU will enable charge port only if PTU requests to do so. Change-Id: Ifb3d3d1beefc28750d711c7572949abe3a183e8f CRs-fixed: 788178
* Bluetooth-Wipower: Fix Vrect_set Vrect_min in dynamic parameterKiran Kelageri2015-02-121-17/+65
| | | | | | | | | | a> Changes been made for the Vrect_set and Vrect_set_min, Currently it is set to 13.6V for the MTP, this should be set to 7.2V while charging and 10.2V while not charging. b> Stop advertisement instance once the connection is through. Change-Id: I127cc67bcbf793a76eb3c807ce6cb2631cc2393d CRs-fixed: 768745
* Bluetooh-Wipower: Fix for delayed advertisments.Kiran Kelageri2015-02-101-1/+42
| | | | | | | | | | Creating a seperate handler to handle advertisment messages i.e. start or stop advertisements, this also minimizes the delays caused in advertising during single thread. Change-Id: I366758bb5a81f7f439234946dbddd83889c849bc CRs-fixed: 759654
* Merge "Bluetooth-Wipower: Fix for BLE GATT Server disconnection failure."Linux Build Service Account2015-02-101-5/+5
|\
| * Bluetooth-Wipower: Fix for BLE GATT Server disconnection failure.Kiran Kelageri2015-02-091-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Create dummy connection to hold the connection even after stop advertisments for wipower is restricted to wipower profile only, Earlier it was creating a dummy connection during for all the new gatt connections. Fix for low RSSI, Wipower needs the tx power level to be high so that there is not drop in RSSI level when on PTU, As part "set multiple advertising parameters" the paramters sent earlier was with low power which reduced 21DB in RSSI so now its been changed for default RSSI levels. Change-Id: Ib6015d2c9a23c56358ea69649dd475675377ef5b CRs-fixed: 781789 CRs-fixed: 781824
* | Bluetooth-Wipower: Recovery of CHG_OK line on reset.Kiran Kelageri2015-02-091-0/+27
|/ | | | | | | | start charging in case CHG_OK pin get resets in bad coupling scenarios Change-Id: Ida1c5540645648c866e042a1b118923228c27b10 CRs-fixed: 754892
* Merge "BT: Remove BluetoothExt process foreground handling."Linux Build Service Account2015-02-092-59/+2
|\
| * BT: Remove BluetoothExt process foreground handling.Ashwini Munigala2015-02-022-59/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | FTP Service startForeground was required during a active FTP Session because BluetoothExt process had less proirity than Bluetooth (com.android.bluetooth) process. This is not required anymore due to BluetoothExt process runs in Bluetooth (com.android.bluetooth) process context now. Removed the relevant code changes to mark the FTPService in foreground and back to normal priority while active FTP Session Connect and Disconnect. This actually reverts commit f32eef886d7429dcf07d4499ae970b1e71279b30. Change-Id: If3619f5d0a952ace9e4dcbef3a923fff678fe1a0 CRs-Fixed: 765862
* | Merge "Bluetooth-Wipower: Fix for disconnect during LE unpair."Linux Build Service Account2015-02-061-14/+10
|\ \
| * | Bluetooth-Wipower: Fix for disconnect during LE unpair.Kiran Kelageri2015-01-211-14/+10
| |/ | | | | | | | | | | | | | | | | | | | | | | | | Disconnect is generic GATT message, if any of the connected LE devices are disconnected or unpaired the connection for wipower was dropping since the same disocnnect message is been handled in wipower too, So as to overcome this a local copy of the device address is maintained such that the disocnnect is based on combination of GATT disconnect and wipower device address. Change-Id: If1252383afce57dd1b175203b08f484a40cc0d74 CRs-fixed: 768026
* / Bluetooth-Wipower: A4WP hold a wakelock upon connection.Kiran Kelageri2015-01-081-0/+39
|/ | | | | | | | | | | | | | This ensures the wake lock is held during wipower connection and released once the connection is dropped, in case of registeration timeouts the wake locks are not triggered. Note: This is back-up solution till the issue is root caused. by default the wake lock is enabled if the property persist.a4wp.skip_connection_wakelock is set then the wake lock will be skipped. Change-Id: I14ec009b6b1e19570b879e61c041d3e8f05d62d5 CRs-fixed: 757812
* Merge "FTP: Remove pending user timeout intent on ACL disconnected"Linux Build Service Account2014-11-251-60/+69
|\
| * FTP: Remove pending user timeout intent on ACL disconnectedHemant Gupta2014-11-241-60/+69
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch fixes the following issues in FTP Code: - MSG_INTERNAL_USER_TIMEOUT intent is removed on reception of ACL disconnected. Previously this message was not removed and new intent was sent to stop obex server resulting in rfcomm socket being listened 2 times from ftp service in case ACL is disconnected while waiting for authorization. - Rfcomm accept thread is closed properly and joined instead of making it null on stopObexServer. this might be leading to some synchronization issues, as thread variable was made zero before it was closed. - VERBOSE logging was not shown, so removed all the logs from the flag for BluetoothFtpService.java. Change-Id: Ie5c3ea45bd0a616f3513d63e8de9c332d768e3b2 CRs-Fixed: 761687
* | SAP: Flush RfcommOutputStreamSmriti Gupta2014-11-231-3/+8
|/ | | | | | | | | | Flush RfcommOuputStream after every write so that Sap packets could go seperately. It is done since It was leading to queing of packets at rfcomm earlier. CRs-fixed: 760728 Change-Id: I1cc6b5a60ce2c830f4a8bf7f06965e0573aa53b2
* Merge "FTP: Fix klockwork reported issues."Linux Build Service Account2014-11-193-6/+7
|\
| * FTP: Fix klockwork reported issues.Ashwini Munigala2014-11-193-6/+7
| | | | | | | | | | | | | | | | Fix NPE and RLK issues reported from klockwork. CRs-fixed: 758708 Change-Id: I017b1e8b954239cff377ca3e68d6737e32d53b2c
* | Merge "SAP: Klocwork issue"Linux Build Service Account2014-11-191-1/+2
|\ \
| * | SAP: Klocwork issueSmriti Gupta2014-11-181-1/+2
| |/ | | | | | | | | | | | | | | This change will fix the Klocwork issue coming with respect to RfcommInputStream in SAP. Change-Id: I29fc19e6b44b5eb35999111d45327b6cd4251ddb CRs-fixed: 758581
* | Merge "Bluetooth: Fix KW issues for DUN profile"Linux Build Service Account2014-11-191-3/+5
|\ \ | |/ |/|
| * Bluetooth: Fix KW issues for DUN profileNitin Shivpure2014-11-191-3/+5
| | | | | | | | | | | | | | This patch fixes P1 Klockwork issues in DunService. Change-Id: I11f724451858d51825ad1a1d8b9dc1fd5ef21c20 CRs-fixed: 759267
* | Merge "Bluetooth-Wipower: Avoid advertisement on USB connect."Linux Build Service Account2014-11-121-11/+17
|\ \
| * | Bluetooth-Wipower: Avoid advertisement on USB connect.Kiran Kelageri2014-11-111-11/+17
| |/ | | | | | | | | | | | | | | | | | | | | Following changes have been made: a> Advertisement seen after USB connection, Charge complete ensures power apply event is only triggered on 600ms long beacons. b> Limited mode advetisement interval is reduced to 5seconds. c> NULL validation been made to avoid unnecessary crashes. Change-Id: Ie9e31a905674b98a429dca5a25910d62a9f51150 CRs-fixed: 749930
* / FTP: Update isWaitingAuthorization as FALSE when user presses cancelHemant Gupta2014-11-091-1/+7
|/ | | | | | | | | | | This patch updtes the value of isWaitingAuthorization to FALSE when user presses cancel. Without this, authorization state was not correct in timeout, and cancel scenarios leading to authorization popup not being received at ftp layer which prevented new FTP connection until BT off and on was done CRs-Fixed: 753197 Change-Id: I685fdcc7aba54d3954c8a99a7fbe86e2da2e7773
* Merge "SAP: Fix Klocwork issues."Linux Build Service Account2014-10-281-3/+6
|\
| * SAP: Fix Klocwork issues.Smriti Gupta2014-10-161-3/+6
| | | | | | | | | | | | | | This change will fix the Klocwork issues in SapService. Change-Id: Iea5ff1b348431c581bcbb66b7b68478fc365a6a9 CRs-fixed: 740239
* | Bluetooth-Wipower: MTP continues advertising WPT UUID post connection.Kiran Kelageri2014-10-221-4/+13
|/ | | | | | | | | | | | | | | a> Stack conitnues to advertise post connection which would lead to cross connection with other PTU within vicinity, So as to avoid rest of PTU's scanning the DUT which continues to advertise, Advertiements are being stopped post connection. b> .setTimeout() with any value less than 180Sec as parameter ensures that it sets the limited mode advertising. since wipower spec demands the advertisement mode to be limited this partciular change is been made and the timeout value is been set to 30Secs which is far enough for PTU to initiate connection. Change-Id: Id63bcc19d714d087fcb6c78553572b649f106580 CRs-fixed: 734301
* Bluetooth : Fix PXP LPP app link loss reconnectionSatish kumar sugasi2014-10-032-28/+46
| | | | | | | | | When BLE link loss reconnection happens,the host is not able to send Vendor specific commands to the controller to start monitoring the RSSI values. CRs-Fixed: 733771 Change-Id: I8b6fd522b2040fd4529d9f1bbc87d4e8adb25474
* Merge "Merge tag 'AU_LINUX_ANDROID_KK.04.04.04.010.171' into HEAD"Linux Build Service Account2014-10-011-0/+258
|\
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-04 07:45:02 +0000