summaryrefslogtreecommitdiffstats
path: root/core/java/android
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'cm-13.0' of ↵HEADreplicant-6.0-0001replicant-6.0Wolfgang Wiedmeyer2017-05-023-0/+13
|\ | | | | | | https://github.com/LineageOS/android_frameworks_base into replicant-6.0
| * Prevent writing to FRP partition during factory reset.Charles He2017-03-221-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Avoid potential race condition between FRP wipe and write operations during factory reset by making the FRP partition unwritable after wipe. Bug: 30352311 Test: manual CVE-2017-0498 Change-Id: If3f024a1611366c0677a996705724458094fcfad (cherry picked from commit a629c772f4a7a5ddf7ff9f78fb19f7ab86c2a9c2) (cherry picked from commit a9437bd1caeeb38780d920a81bde8cc7ca280fe0) (cherry picked from commit 1c4d535d0806dbeb6d2fa5cea0373cbd9ab6d33b)
| * DO NOT MERGE. Retain DownloadManager Uri grants when clearing.Jeff Sharkey2017-03-131-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As part of fixing a recent security issue, DownloadManager now needs to issue Uri permission grants for all downloads. However, if an app that requested a download is upgraded or otherwise force-stopped, the required permission grants are removed. We could tell DownloadManager about the app being stopped, but that would be racy (due to background broadcast), and waking it up would degrade system health. Instead, as a special case we now only consider clearing DownloadManager permission grants when app data is being cleared. Bug: 32172542, 30537115 Test: builds, boots, app upgrade doesn't clear grants Change-Id: I7e3d4546fd12bfe5f81b9fb9857ece58d574a6b9 (cherry picked from commit 23ec811266fb728cf159a90ce4882b3c9bac1887) (cherry picked from commit 6eee8e37fd06bd47dd19b8503bc30cc8ccaf72a7) (cherry picked from commit 36772fc2263e06972add737660392afd246da15e)
| * DO NOT MERGE: Check provider access for content changes.Jeff Sharkey2017-03-131-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For an app to either send or receive content change notifications, require that they have some level of access to the underlying provider. Without these checks, a malicious app could sniff sensitive user data from the notifications of otherwise private providers. Test: builds, boots, PoC app now fails Bug: 32555637 Change-Id: If2dcd45cb0a9f1fb3b93e39fc7b8ae9c34c2fdef (cherry picked from commit c813f5dae231bd8f01864227c5dba10d43a89249) (cherry picked from commit db57376d6ccbd4d3e39fc35aa8cfb561bbca4bac) mh0rst: Backport from android-7.1.1_r21
* | Camera: Working barcode scanning with software renderingWolfgang Wiedmeyer2017-01-041-1/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Barcode scanner apps expect YUV as preview format. However, the software renderer cannot handle YUV. Thus, RGB 565 is used. Barcode scanner apps only need the first plane Y which is basically greyscale. The solution is a conversion from RGB to greyscale of preview frames that are requested by apps for processing. Apps request preview frames via onPreviewFrame(). The conversion is done using native code for optimal speed. The conversion algorithm is based on the implementations in the RGBLuminanceSource class of ZXing[1] and the RGB565LuminanceSource class of FastBarcodeScanner[2]. Signed-off-by: Wolfgang Wiedmeyer <wolfgit@wiedmeyer.de> [1] https://github.com/zxing/zxing/blob/cc16a72c85e4958ce406af9547764e5eee9adb6e/core/src/main/java/com/google/zxing/RGBLuminanceSource.java [2] https://github.com/tschaumburg/FastBarcodeScanner/blob/5a4c166a722730d0099d4c6a1c15d312b93547da/tracking-barcode-scanner/src/main/java/dk/schaumburgit/trackingbarcodescanner/RGB565LuminanceSource.java
* | support separate encryption/lockscreen passwordsDaniel Micay2016-12-161-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | This adds the necessary infrastructure for allowing users to opt-in to a distinct device encryption passphrase. The passwords are still tied together by default. This makes it possible to use a complex encryption passphrase without losing the convenience of a very simple lockscreen pin. This feature can be combined with a forced reboot after a chosen number of failed unlocking attempts to prevent brute-forcing by requiring the entry of the encryption password instead.
* | Merge branch 'cm-13.0' of ↵Wolfgang Wiedmeyer2016-12-1244-142/+538
|\ \ | |/ | | | | https://github.com/CyanogenMod/android_frameworks_base into replicant-6.0
| * Themes: Don't cache explicitly themed resourcesBharadwaj Narasimha2016-11-281-26/+1
| | | | | | | | | | | | | | | | | | When a nav bar should be unchanged in the process of customization(like changing icons,fonts) the nav bar changes due to explicitly caching themed resources. Change-Id: I3135fac9df82a0551879908f6bf24deba0da0339
| * Build: use UserHandle.isApp for M compatibilityZhao Wei Liew2016-11-271-1/+1
| | | | | | | | Change-Id: Ie4511c547d9afe2697e1ac3519f41a9b19784f18
| * Make Build.TYPE and Build.FINGERPRINT consistent for apps.Danny Baumann2016-11-251-0/+41
| | | | | | | | | | | | | | | | | | | | Some apps (namely Android Wear) like to do comparisons between TYPE and FINGERPRINT and throw errors on inconsistencies. As our fingerprints are almost always taken from stock ROMs, they don't really match our builds, causing said comparisons to fail. Avoid those failures by taking build type out of fingerprint for apps. Change-Id: I8e8db64de7ea224572ecb3695c85abea91e0e29f
| * frameworks/base: Addition of Changes for ZeroBalance featurePragnya Paramita2016-11-101-0/+99
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | --Addition of code to receive broadcast from ZeroBalanceHelper application for executing command to write block/unblock rule to Iptable. --Addition of ZeroBalanceHelper file to be accesible by other modules to notify ZeroBalanceHelper application about update on change of SIM balance. --Addition of rule to allow browser uid when rest all applications are in blocked state. --Addition of feature flag to control the zerobalance feature. CRs-Fixed: 927258 Change-Id: Ifdf4c46fd63ab78193047a9bc8b62bf41065a665
| * NotificationManager: Concentrate LED light capabilities at a single locationRicardo Cerqueira2016-11-102-0/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | We had(have) a bunch of individual boolean toggles for various LED behaviors and combinations, which end up getting used as a similarly sprawling bunch of getResource() calls across various locations. And they keep piling up... So... create a new overlayable array of LED capabilities (config_deviceLightCapabilities) where we can throw everything (and expand in the future). Also, create a helper to abstract usage of the old (multi-resource) and new (single resource array) formats to avoid breaking any deployed devices. Change-Id: I7d627914b058861048071fc15776031c4152157f
| * Merge tag 'android-6.0.1_r74' into HEADJessica Wagantall2016-11-092-5/+5
| |\ | | | | | | | | | | | | | | | CYNGNOS-3303 Android 6.0.1 release 74
| | * Merge commit '0a9d537f623b2c11dce707fb9b91fea016fd0e9f' into ↵Jeff Sharkey2016-09-271-3/+3
| | | | | | | | | | | | | | | | | | manual_merge_0a9d537 Change-Id: Ib1a0bbb34edb61666ac5739f0b0eaadbe4c5fe06
| | * Fix setPairingConfirmation permissions issue (2/2)Marie Janssen2016-09-271-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | setPairingConfirmation was set to only require BLUETOOTH_ADMIN permission which shouldn't be able to set the confirmation itself. This is restricted to BLUETOOTH_PRIVILEGED permission. Bug: 29043989 Change-Id: I887de32d156e672ec44aa0b286cd7ea7f9f8ad55 (cherry picked from commit 93326cfd9fb8a20081baa9b975275772798cfd80)
| | * Bind fingerprint when we start authentication - DO NOT MERGEJim Miller2016-08-252-7/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes a bug where it was possible to authenticate the wrong user. We now bind the userId when we start authentication and confirm it when authentication completes. Fixes bug 30744668 Change-Id: I346d92c301414ed81e11fa9c171584c7ae4341c2 (cherry picked from commit b6f4b48df273d210d13631b4c2426482feb40c97)
| | * Process: Fix communication with zygote.Narayan Kamath2016-08-251-6/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Don't write partial requests, and don't return (or throw) early after partially reading a response. bug: 30143607 (cherry-picked from commit 448be0a62209c977593d81617853a8a428d013df) Change-Id: I5881fdd5e81023cd21fb4d23a471a5031987a1f1 (cherry picked from commit e29c6493c07acf1a0b706917e9af0c8d761c8ae9)
| * | Support enforcing a minimum delay between notification sounds of an app.Danny Baumann2016-10-201-0/+3
| | | | | | | | | | | | | | | | | | Useful e.g. for messenger apps. Change-Id: If8e8cc9e2f02d70537c1f9dc14f22bbd0ec1e9a6
| * | (Optionally) allow vibration during priority zen mode.Danny Baumann2016-10-192-3/+3
| | | | | | | | | | | | Change-Id: I6fb81c5898fbfe9e89a4af3fdc042266c8a9be6c
| * | Merge tag 'android-6.0.1_r72' into HEADJessica Wagantall2016-10-063-13/+31
| |\ \ | | | | | | | | | | | | | | | | | | | | | | | | Android 6.0.1 Release 72 (M4B30X) # gpg: Signature made Tue 04 Oct 2016 09:47:40 AM PDT using DSA key ID 9AB10E78 # gpg: Can't check signature: public key not found
| | * | Bind fingerprint when we start authentication - DO NOT MERGEJim Miller2016-08-262-7/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes a bug where it was possible to authenticate the wrong user. We now bind the userId when we start authentication and confirm it when authentication completes. Fixes bug 30744668 Change-Id: I346d92c301414ed81e11fa9c171584c7ae4341c2 (cherry picked from commit b6f4b48df273d210d13631b4c2426482feb40c97)
| | * | Process: Fix communication with zygote.Narayan Kamath2016-08-261-6/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Don't write partial requests, and don't return (or throw) early after partially reading a response. bug: 30143607 (cherry-picked from commit 448be0a62209c977593d81617853a8a428d013df) Change-Id: I5881fdd5e81023cd21fb4d23a471a5031987a1f1 (cherry picked from commit e29c6493c07acf1a0b706917e9af0c8d761c8ae9)
| * | | [2/2] base: cm custom boot dexopt UIAlexander Martinz2016-08-103-10/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | * Pass app info and number of installed packages to boot message UI * Ui by Asher and Joey, based on Alexander's previous work Change-Id: I9ec9d0cb0e20a9bac73e126f6b6f3965400f05e7
| * | | IconPackHelper:Use un-tinted iconback when no defaultSwatchcolor is specifiedBharadwaj Narasimha2016-08-091-5/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | After applying the theme which supports paletteback feature and if there is no defaultSwatchColor specified then the background should go to the original color. Instead in a particular FootballDemo theme the theme would never get applied and just flood the logcat with null exceptions for each and every app. TICKET:CYNGNOS-2942 Change-Id: If2bd3d23ab5075dac1d8ff3f197cebc28c9c1f20
| * | | fw: enforce android.permission.PREVENT_SYSTEM_KEYS in system serverScott Mertz2016-08-051-7/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since privateFlags can be accessed and modified via reflection due to change 5d927c2d8e, the prevent system keys or prevent power keys flag can be set and deployed without ever calling setPrivateFlags directly. Move enforcing to system server to prevent app tampering. TICKET: CYAN-7921 (open source JIRA) Found by Maciej Krysztofiak Change-Id: I53c2804d0283692036f5cc95e6ad57821bc0655a
| * | | Merge tag 'android-6.0.1_r61' into HEADJessica Wagantall2016-08-023-6/+17
| |\ \ \ | | | |/ | | |/| | | | | | | | | | | | | Android 6.0.1 Release 61 (MOB30Z) Change-Id: Ib003ccb606e0d77209291b757ea36399d3b65814
| | * | DO NOT MERGE Fix intent filter prioritiesTodd Kennedy2016-06-241-1/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since this is a backport, there is only one rule that guards intent filter priorities: 1) Updates will NOT be granted a priority greater than the priority defined on the system image. Bug: 27450489 Change-Id: Ifcec4d7a59e684331399abc41eea1bd6876155a4
| | * | Don't trust callers to supply app info to bindBackupAgent()Christopher Tate2016-06-242-5/+7
| | |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Get the canonical identity and metadata about the package from the Package Manager at time of usage rather than rely on the caller to have gotten things right, even when the caller has the system uid. Bug 28795098 Change-Id: I215786bc894dedf7ca28e9c80cefabd0e40ca877 Merge conflict resolution for ag/1133474 (referencing ag/1148862) - directly to mnc-mr2-release
| * | Factory reset: Wipe media by defaultScott Mertz2016-07-251-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These hidden APIs are called from some public APIs (DevicePolicyManager), so we shouldn't change the default behavior. The intent API should also be considered public, so change that as well. FEIJ-1610 Change-Id: Ib9591c122dbe6168e7e237444c754b9608be0953
| * | PackageManager: make protected-broadcasts permission awareRoman Birg2016-07-212-4/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This extends the <protected-broadcast> mechanism to allow protecting actions based on a permission for system apps. For instance: <protected-broadcast android:name="ACTION_A" android:permission="PERMISSION_X" /> will restrict intents with action "ACTION_A" to be only sent with apps holding the "PERMISSION_X" permission. Note that system UIDs will bypass the permission check and always be allowed, just like the normal protected-broadcast mechanism. You must still be a system application to delcare a protected broadcast. Change-Id: Id25cffd233d400800dcb5249c5f487134e1b4152 Signed-off-by: Roman Birg <roman@cyngn.com>
| * | Merge remote-tracking branch 'remotes/android-6.0.1_r52' into HEADJessica Wagantall2016-07-071-0/+9
| |\ \ | | |/ | | | | | | | | | | | | Ticket: CYNGNOS-3020 Change-Id: Ia14b6d0120de0b458c7c249a11041ff121389cfa
| | * Don't pass URL path and username/password to PAC scriptsPaul Jensen2016-05-271-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | The URL path could contain credentials that apps don't want exposed to a potentially malicious PAC script. Bug: 27593919 Change-Id: I4bb0362fc91f70ad47c4c7453d77d6f9a1e8eeed
| * | BT: Set persiste Bluetooth State during enable timeout caseGurpreet Ghai2016-07-021-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Use case: When enable timeout occurs during S&S testing and Bluetooth state is moved from Turning On to Off. Steps: Changes related to enable timeout case, to test the changes, S&S testing can be done. Failure: Changes done to handle Bluetooth enable timeout case when Bluetooth state changes from Turning On to Off. Root cause: Setting Bluetooth Persist state to handle the enable timeout case so that Bluetooth doesnot self enable after enable timeout case is handled. Fix: Setting the Bluetooth Persist State to Off when enable timeout occurs. Change-Id: I17b3b05020eb7469666e6d8c88c86df7764b4024 CRs-Fixed: 1006444
| * | WindowAnimator : Check KEYGUARD_PANEL when deciding to show/hide windowDanesh M2016-06-291-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | By default, if blur is enabled we don't hide the window behind since we want the user to see it. This is not true for when a KEYGUARD_PANEL is active since we can't see anything behind it anyway. Only apply blur logic if KEYGUARD_PANEL is not added. CYNGNOS-2980 Change-Id: Icecae14455d6e68665bb688e3f6dc4ea9d74e88c
| * | Merge tag 'android-6.0.1_r46' into HEADJessica Wagantall2016-06-071-0/+15
| |\ \ | | |/ | | | | | | | | | | | | | | | Android 6.0.1 release 46 # gpg: Signature made Mon 06 Jun 2016 10:38:22 AM PDT using DSA key ID 9AB10E78 # gpg: Can't check signature: public key not found
| | * Add new, hidden MotionEvent flag for partially obscured windows.Michael Wright2016-04-211-0/+15
| | | | | | | | | | | | | | | Bug: 26677796 Change-Id: Ic4219b883bb760495e6172ef61e84e9725876ef6
| * | Frameworks: Add per app controls for LP keyguard notifications (1/2)Lars Greiss2016-06-013-0/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Nice done by google but the UX is a problem especially for ppl who are using a lot apps and just want to see from important apps the notifications on the lockscreen. This commit adds the ability to - enable/disable per app the keyguard notification at all - enable/disable per app ongoing notifications on the keyguard We handle this over the app policy conf file like the other per app notification options. CRACKLING-1127 Change-Id: Ib166db1b1673aeaea132c8eeb16c650d2f254a82
| * | fw: reintroduce PRIVATE_FLAG_PREVENT_POWER_KEYScott Mertz2016-05-312-2/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | Switching the PREVENT_SYSTEM_KEYS forces the application to handle every system key. Some apps may not want to handle every single key, so allow them to just handle the power key. CYNGNOS-2958 Change-Id: I43fd65e67b909e6d52548f110ff9997b829b3e15
| * | Core: Fix OOBMichael W2016-05-301-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | getExternal___Dir() relies on getExternal___Dirs to return an array of at least 1 element. Make sure there is at least one element returned. (Reference: BugDump 13-20160513-19 l#45 (FileManager) and L#104 (Gallery) BugDump 13-20160520-26 L#18 and more (26), just search for "getExternal" to find all cases of that OOB (>>100 users)) Change-Id: I56394db135c4c53c972e3bcc8f1df4ea1d4d39e7
| * | Only call uncrypt when we're encryptedPat Erley2016-05-231-15/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We were always generating a block map for encrypted update, even when the device was not encrypted. This leads to a spectacular failure. Fix this by only calling uncrypt when we're encrypted. Additionally, only pass block.map as the update file in the case that the device was encrypted and requires it. NIGHTLIES-3012 Change-Id: Ia34eb5115ac4365605fd57f76179854a6042c5e4
| * | fw: Repurpose PREVENT_POWER_KEY for preventing multiple system keys.Adnan Begovic2016-05-232-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Allows applications like camera, and various testing applications, to intercept certain system keys to verify behavior or leverage it in creative ways. Limited to signature/privileged. Change-Id: Iacd8735af2aabafbf1fc062d8c565b7102dc6865 TICKET: FEIJ-522
| * | frameworks/base: Support for third party NFC featuresPuneet Mishra2016-05-234-6/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Integration of below modifications are necessary to support third party NFC software: * a new interface in INfcAdapter.aidl allowing vendor specific extensions and features * a new size for MIFARE Classic tags * a modified constructor to distinguish MIFARE Classic tags from NfcA tags * allowing extensions to AidGroup and changing the protection of the instance variables to package protected Change-Id: Ic11dc68c4ea83262c705ec50b75b5808aa064f82 (integrated from commit 57a001b7851c97d41f042dda643f9a87aa6306e5)
| * | Themes: Fix theming of cmsdk assetsd34d2016-05-191-0/+2
| | | | | | | | | | | | | | | | | | | | | Missed the pkgid assignment bits in I4f64d53d82c9edafbe624c3b2eafcda7332587fb Change-Id: Ie442c8922f0d9eac3ed5bab70a99d3e065b719c4 TICKET: CYNGNOS-2723
| * | am: Handle unchecked activity starts for protected components.Adnan Begovic2016-05-193-5/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously if you received a notification from a protected app, since AM would state that the calling package was also the target package, the protected apps implementation would allow you to launch into the application. Mitigate this by hooking into the unchecked activity start stack (pending intent launches) globally. Change-Id: I0371593ade9e4af2554962873d89a0f82a639b57 TICKET: PAELLA-216 FEIJ-160 FEIJ-177
| * | Update volume slider only if ringer mode changedLuis Vidal2016-05-131-1/+2
| | | | | | | | | | | | | | | | | | | | | Prevents unnecesary updates to volume slider. Change-Id: Ie8c19c2061dc9f418972b16ca1618a80f10f1325 TICKET: CYNGNOS-958
| * | CmRes: Attach themed cmsdk resources to assetsd34d2016-05-101-0/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The cmsdk is beginning to contain some themable assets, like the quick settings tiles for LiveDisplay and Themes so we need to attach themed resources for the cmsdk in order for those themed resources to be picked up. Change-Id: I4f64d53d82c9edafbe624c3b2eafcda7332587fb TICKET: CYNGNOS-2723
| * | Settings: defer DEV_FORCE_SHOW_NAVBAR query to CMSettingsRoman Birg2016-05-021-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some apps were using Settings.System.DEV_FORCE_SHOW_NAVBAR to determine whether the device was forcing a nav bar. It was then moved to Settings.Secure, and then to CMSettings.Secure. So some apps check against Settings.System, and some may check against Settings.Secure. The real value lives in CMSettings.Secure right now. We could not intercept the setting because MOVED_TO_SECURE would return the already-cached value from Settings.Secure, not allowing us to intercept the call in CMSettings. With this removal, we can handle the logic for this key in CMSettingsProvider. Ticket: CYNGNOS-2480 Change-Id: I7485c0d0acf90df365e5ed5ebdb42596d148de62 Signed-off-by: Roman Birg <roman@cyngn.com>
| * | Merge tag 'android-6.0.1_r30' into HEADJessica Wagantall2016-04-201-0/+12
| |\ \ | | |/ | | | | | | | | | | | | | | | Ticket: RM-234 Android 6.0.1 release 30 Change-Id: I1bd7cf4081a12d28dc5da8b53b9124180afaa23d
| | * Redact Account info from getCurrentSyncsMatthew Williams2016-02-261-0/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | BUG:26094635 If the caller to ContentResolver#getCurrentSyncs does not hold the GET_ACCOUNTS permission, return a SyncInfo object that does not contain any Account information. Change-Id: I5628ebe1f56c8e3f784aaf1b3281e6b829d19314 (cherry picked from commit b63057e698a01dafcefc7ba09b397b0336bba43d)
| | * DO NOT MERGE Read Bluetooth interop database entries from settings (1/2)Andre Eisenbach2016-02-241-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Interop database entries are stored in the system settings entry "BluetoothInteropDatabase". The format is a list of entries separated by ";". An entry consists of a BDA fragment, followed by a comma and an integer representing a feature from interop.h. Example: To disable LE secure connections for devices starting with BDA 11:22:33, use "11:22:33,0". Bug: 26548845 Change-Id: I6a9fd34f6af4d3bdfcaa0e051eafebdfbf2a4949 (cherry picked from commit 3bc623be8dd8b83d0a22c5cc5b5a8955001f6fc7)
generated by cgit v1.1 at 2025-07-17 09:33:06 +0000