- Jan 28, 2024
-
-
Properties are limited and don't allow us to list as many apps as we wish. Change-Id: I4432f627f1fa120b6ea41c252cd512beb129848c
-
* Replace vendor.camera.aux.packageblacklist with vendor.camera.aux.packageexcludelist as recommended by coding guidelines https://developers.google.com/style/word-list#blacklist. Original change: Author: Sauhard Pande <sauhardp@codeaurora.org> Date: Thu Jul 21 18:23:21 2016 -0700 Camera: Expose Aux camera to apps present in the whitelist Issue: 3rd party apk cannot handle additional aux camera and may cause crash, Mono camera doesnt support all capabilities of HAL3 causing CTS issue. Fix: 1. Expose aux camera to apps present in the whitelist 2. ignore the availabe/unavailable status update for aux camera 3. returning exception for open request for bad cameraid Change-Id: I15910154c6df205e6d4e00bfad30a00c9e3d5bee CRs-Fixed: 1086937 --------------------------------------------------------------------------- Forward-ported to R and squashed with the following changes: Author: Rashed Abdel-Tawab <rashed@linux.com> Date: Sat Mar 24 13:20:52 2018 -0400 camera: Check if aux camera whitelist is set before restricting cameras Some devices have a fully featured 3rd camera and adding 20+ camera apps to the whitelist is impossible due to the string length limit on systemprops. Add a check to see if the prop is even set, and if not, check if the blacklist property is set and mark those apps to hide the 3rd camera from. If a package is not part of the blacklist, just restore the original behaviour and expose all the cameras to the app. Change-Id: I6c3b33c077e8710c73b5d0fa28e1b017d6c43a58 Author: Paul Keith <javelinanddart@gmail.com> Date: Fri Feb 8 08:42:33 2019 -0600 Camera: Simplify code for Aux/Mono white and black lists Change-Id: I20c5454385d4d830a9a4d61926807a7eb1407c95 Change-Id: I7eb9f78c37f06a4e713fe6bcbf1793052aad3583 Change-Id: I15910154c6df205e6d4e00bfad30a00c9e3d5bee
-
Change-Id: Ib001ce767067e3789ea5957ac9b23ed416341d18
-
Some audio hals do not implement get/set audio_port, even though the device hal version should have it. Function not implemented gets mapped to invalid operation, so just ignore invalid operation failures. Change-Id: I1ceaa7aa4467d48f8e492ea6c7de87ed0a9570fa (cherry picked from commit cc082e030b5eac6f53fa83d2943fc49b09c513a1)
-
Fixes custom pattern size in auth prompts from apps. Change-Id: I8238de614f7acd0e2b286b06775961820b6c10fb
-
- Jan 26, 2024
-
-
This reverts commit 8bb51489. We've intentionally enabled and fixed the Wi-Fi and cellular data tiles to work with the provider model, so revert this to fix the dedicated network tiles. Signed-off-by:
Danny Lin <danny@kdrag0n.dev> Change-Id: I1c74e0426a2660c07cd8cc59ff22eb45bcdc4dda Signed-off-by:
Mohammad Hasan Keramat J <ikeramat@protonmail.com> (cherry picked from commit 4fd6f7569b5986b2b10b671c943c0333ec63e928)
-
Allows quickly connecting/disconnecting to/from VPNs. Change-Id: Iaa9413bf1071805be8764d92bc5e2dd3131fdaed Signed-off-by:
Omkar Chandorkar <gotenksIN@aospa.co>
-
- Jan 25, 2024
-
-
* HACK: This settings initialization should have been done since LMO 12, however, we missed it. To fix the issue on 12->13 flash, we initialize it in a version upgrade not present in 12. Note that this code block also is required for clean flash Change-Id: Ibfcb5b76ea9a446a7d7a750aed17fe7b8ca1a99b
-
-
Change-Id: I7c6bc9921d301709eac6172b88ff8473dfdd5dd4
-
It's only for an clean install Change-Id: Ia8eb9df2e151bf7cfdf94cde79824782e9fe7ce0 Signed-off-by: -
Add below changes for Multi SIM device phone ringtone. 1. Add api setActualDefaultRingtoneUriForPhoneAccountHandle to set ringtone for specific PhoneAccountHandle. 2. Add api getActualDefaultRingtoneUriForPhoneAccountHandle to get ringtone for specific PhoneAccountHandle. 3. Support saving ringtone cache for specific PhoneAccountHandle. Bug: 118735436 Test: Manual, CTS Test Change-Id: I26c20ef52753256e1148ee9b01492034f55a3bd4
-
* Add a global cleartext penalty setting and a system property. When set, apps cannot send/receive cleartext traffic and cannot allowlist themselves * Change default policy from ACCEPT to INVALID. INVALID takes ACCEPT's functionality and ACCEPT is used to allowlist apps from cleartext restrictions * Listen to changes to the setting, to package removals and to validated private DNS servers and set/remove cleartext rules accordingly * Set global cleartext restrictions on boot * Use an invalid UID, -1, to apply cleartext restrictions globally Change-Id: Id9e5dc71b998de8fe124772dde6b82c7c1d4c1b6 Change-Id: Ie1a631dc574cc6f9039967e990d51ea5011f36fc (cherry picked from commit bb52bb4de9d9de5eb08ea4f0344d63db13f065eb)
-
* Modify existing VPN user range functions to conditionally have traffic from all users pass through the global VPN. These functions are called when: 1. Starting a VPN 2. Adding a user 3. Removing a user * Disallow starting VPNs in secondary users when a global VPN is set Also includes: Author: Oliver Scott <olivercscott@gmail.com> Date: 2021-08-27 16:30:22 -0400 Show Global VPN icon on all users Change-Id: I496c0abbdf92b8f823bc57b297473aa14bd968c8 Change-Id: I42616cc1f4e39e1dad739d81f6d5c55e218be995 Signed-off-by: -
By exploiting the already existing implementation used in Keyguard to "lock" the device after a specific timeout has been reached we add our own custom action that starts right when the display is in the "locked" state and stops when we enter the "exit" phase of keyguard ( aka unlocked ) Also cancel reboot timeout when unlocking without a secure lock screen. Add a debugging statement to make this easier to troubleshoot (needs `adb shell setprop persist.log.tag.Keyguard DEBUG`). Issue: calyxos#1683 Co-authored-by:Tommy Webb <tommy@calyxinstitute.org> Change-Id: I23170e5ec3ae296a4aa1d9c1793d61c8399c4d54
-
Do not handle tile clicks if keyguard is locked and setting is blocking Change-Id: I8194e9b7b64c0a23a42aeb3ffca90602f0882ec4 Signed-off-by: -
This adds initial support for running multiple instances of the same app at the same time. Basically this is done by making use of multiuser. Further work is needed to make it perfect. Squashed: * base: Expose parallel space owner to api * base: Add support for managing files across parallel spaces * services: camera: Whitelist parallel space users * services: location: Whitelist parallel space users * SystemUI: Fix privacy indicator not showing for apps in parallel spaces * ParallelSpaceManagerService: Do not install setupwizard too * ActivityStarter: Resolve launcher intent to parallel owner user * pm: Restore the default behavior of `pm install` * fwb: Rename parallel space permission * StorageManager: Return pass through mount mode only when parallel users available * SystemUserInfoHelper: Fix crash when switching user * ParallelSpaceManager: Add method to get the default cloned apps list * services: Add internal api to handle parallel space service Dhina17: Adapted for Android 14 Change-Id: Ib385753df5778a25facd39166abd8b1e29ed7e91 Signed-off-by:
LibXZR <i@xzr.moe> Signed-off-by:
Adithya R <gh0strider.2k18.reborn@gmail.com> Co-authored-by:
electimon <electimon@gmail.com> Co-authored-by:
Dhina17 <dhinalogu@gmail.com>
-
Changes are imported from the original frameworks/base commit Ie35c6c7103b8bed644d510d8268d6c99cb71a1a2 and adapted for lmo framework. Change-Id: Ib3cae7e882e98c6668a68e148c0aaccbea60fb3b Co-authored-by: -
Author: cjybyjk <cjybyjk@zjnu.edu.cn> Date: Wed, 13 Apr 2022 09:29:41 +0000 udfps: Implement framework dimming support Author: bengris32 <bengris32@protonmail.ch> Date: Sun, 17 Sep 2023 11:31:02 +0530 udfps: Add delay for framework dimming support Co-authored-by:Pranav Vashi <neobuddy89@gmail.com> Author: Thomas DE SA <desathomas@gmail.com> Date: Sun, 22 Oct 2023 17:46:42 +0200 udfps: Apply dim layer in configureDisplay() callback Ensure that the timing of the dimming layer application is as close as possible to the timing of the illumination. Too early and you get the screen going dark for a few frames, too late and the screen gets bright for a few frames. Change-Id: Icf84cc61e2448840944e50d3b5c48c9f24a7f9f5
-
fc343495 replaced onUiReady with onUdfpsUiEvent which was only used by AIDL hals. onUdfpsUiEvent now is responisble for the previous functionality and requesting the enrollment icon + progress bar to be shown. The latter was missed for HIDL hals, thus it wasn't visible. Change-Id: I6cda3d3897fda350d506f777d3e85587ff04a0e3
-
During development the Wi-Fi service might not work, let's handle this case so the Setting app doesn't crash when opening the about phone page Logic borrowed from the Bluetooth controller Change-Id: Id8f6ba5d7cbac5780363612b50848ecfea10bc04
-
Change-Id: I3a50feec03e4f913a5c0fabe975cf1206f7f2d40
-
* The current WiFi network has a setting toggle and also opens the settings on single click where the mobile network only allows connecting but not opening settings * Add a long press listener that goes to the subId's network settings, allowing for example to disable roaming or change network Change-Id: Iacc1c64d318b0240da5397f2b4e4dfb59d4834dd
-
Author: Nico <nicorg2529@gmail.com> Date: Sun Mar 8 11:39:47 2020 +0000 Implement edge long swipe gesture [1/3] The gesture will activate if user executes edge swipe for a long horizontal motion. The triggered action is configurable in Button Settings. Reference: https://gerrit.dirtyunicorns.com/q/topic:%22back-longswipe-actions%22 Change-Id: Ie1bbe6645b6a00d346af60d6bb5e4d584997d6e9 Author: LuK1337 <priv.luk@gmail.com> Date: Thu Nov 25 17:39:29 2021 +0100 Use custom flag for edge long swipe gesture Previously we were using same flags that'd be used for regular back key long press thus being unable to determine whether the event was sent from EdgeBackGestureHandle or not. Fixes: https://gitlab.com/LineageOS/issues/android/-/issues/4194 Change-Id: I5c4fd455f581ac5c9c5e3a146095be33e82e8d6e Author: someone5678 <nemui3353@gmail.com> Date: Fri, 14 Jul 2023 17:26:19 +0900 Adapt and fix from original long swipe gesture impl Change-Id: I22c6442299df0cf15d046718fa40df6fb6aee07c Signed-off-by:someone5678 <nemui3353@gmail.com> Author: someone5678 <nemui3353@gmail.com> Date: Sun Jul 30 20:55:13 2023 +0900 Flip back gesture canvas if started from left * Better than constant right arrow direction Change-Id: I45108f185130d6f778660ba11f3beb758826ba99 Signed-off-by:
-
The current silent and vibrate volume icons in the status bar have slightly too much padding compared to all of the other status bar icons, which makes it look out-of-place. Remove the excess insets to make it more even. Note that the silent icon still has 0.5 dp of padding on its left and right sides to make its total size match that of the vibrate icon, which is 19 dp, while the silent icon is 18 dp. Change-Id: I7fb9a6e0113f6103eed308ac2d25c392fe8abb73
-
-
Expand/collapse animation with the 2 finger swipe/swipe down from right side to expand QS gesture [1] was pretty ugly with all the notifications being dragged along. Let's hide the notifications stack entirely when quickly expanding QS, for a nicer looking animation similar to the one in lockscreen. [1]: https://github.com/pa-gr/android_frameworks_base/commit/d3622399728c819c45c5435ddd0b1e359207f962 Change-Id: Id2dbc707f9da543d47d76ae5525e827b400a4e7b
-
* and provide an alternative if not [SamarV-121: Use HEAVY_CLICK effect on activation and deactivation] Change-Id: I9b6fafd731c49bf4d875b0ad581ee1b4666daf17
-
-
Change-Id: Ic85d351558dea5a5446c5ebe468b0db9e8c99285
-
This is a refactor of the following changes, so to make use of tuner API. Author: Timo Wendt <timo@tjwendt.de> Date: Thu Aug 30 12:18:41 2012 +0300 Runtime toggle of navbar This adds the framework support for enabling the Navigation bar on devices with hardware keys. It is toggled from Settings, and depends on device-specific support for the KeyDisabler hardware control Change-Id: I88fecb2ca1e8613591c327a93f53909b00239cd8 wm: Nullify hardkey function assignments if enabling the navbar This caused erroneous (and sometimes duplicate) events being generated due to the regular key function assignments. The navbar does its own action management, so don't try to derive from the actions usually present in hard keys. Change-Id: I82866e24547f8145cac4f07820ae90aacce09281 Update DEV_FORCE_SHOW_NAVBAR constant. Change-Id: Ie5b4317162c514d22276956f81007e064a3d0f32 Settings: Move DEV_FORCE_SHOW_NAVBAR load to loadSecureSettings. Change-Id: I6ac53b8c9f7fce6f9ca6b4ad7bf31a1c1e896863 Author: Paul Keith <javelinanddart@gmail.com> Date: Tue Jan 16 15:47:07 2018 +0100 PhoneWindowManager: Make sure KeyDisabler is always called on boot * Otherwise, some KeyDisabler classes are left in a weird state * Because we don't keep track of whether an initial state was ever set, we never call KeyDisabler on boot if the setting is set to 0 * To remedy this, keep track of whether an initial state was set Change-Id: Ib432ed3278dd8f4f4cba3ba488879b3c1cd9c8f4 Author: LuK1337 <priv.luk@gmail.com> Date: Sat Sep 29 20:42:04 2018 +0200 PhoneWindowManager: Fix issues introduced with runtime navbar * With system settings we need to pass UserHandle.USER_CURRENT to make sure we are getting proper value, otherwise we always end up getting '0'. Also we need to make sure to set valid mHasNavigationBar in setInitialDisplaySize(). Change-Id: I3efd614e735f9a602f13263a742ce858a9d14769 Author: jhenrique09 <jhenrique09.mcz@hotmail.com> Date: Tue Mar 24 22:04:47 2020 -0300 DisplayPolicy: Fix watchdog when adding new display * Fixes system crashing after connected to Android Auto or started screen record That was introduced on toggle navbar commit Only register content observer if default display Change-Id: Ia43a922251803be94de8618eb442dcf132e479e9 Author: LuK1337 <priv.luk@gmail.com> Date: Sat Oct 31 12:28:09 2020 +0100 Edit: Bring-up changes for A11 * Due to race condition we end up calling DisplayPolicy.hasNavigationBar() before the settings value is updated. * Switch over few more navigation bar checks that'd likely also fail. * Call WindowManagerService.onOverlayChanged() so that we don't end up with reserved space for 3-button style navbar when gestural navigation is enabled. Change-Id: I4a6d3f89bc171c3921875b24c077cb78c03517ad -
libmcf-jni.so library (which is proprietary blob required for MotCamera2) looks for methods with these exact signatures, but signatures of these methods was changed in Android 11. This change returns these methods that makes MotCamera2 fully-functional on Android 11. Change-Id: Ib9a701f6d8ebb783c52666e34e7539faba5cb99f Signed-off-by:Ihor Ivanov <toulmee@gmail.com>
-
* Many devices identifying as "Analog Docks" have not built in volume controls and rely on software volume (See: All Motorola Mods, older 3.5mm docks, etc.) Change-Id: Ie9b97c7b17b882a5d804db398d149bd777ccf5a4 (cherry picked from commit 24ce6c3ea58f339cc8a537205e30d2516d2b073b) (cherry picked from commit a6eff9c92353cd74ebae12cc82840d1356844980)
-
Squash of: Author: Vachounet <vachounet@live.fr> Date: Thu May 8 14:16:54 2019 +0200 BatteryService: Add support for battery Moto Mods * This relies on the prebuilt Moto Health service being included device side. Reference: I48803eeb72499fe8459805f6ef80ef5f868f431e Change-Id: I41a4d5fdeb5e1f2ad7838851ad0815cef7d72980 Author: LuK1337 <priv.luk@gmail.com> Date: Tue Mar 2 12:47:51 2021 +0100 BatteryManager: Mark battery moto mods constants as hidden Change-Id: I095a646d78c718df14cd8cd4fcde848ae3ba01df Author: Ali B <abittin@gmail.com> Date: Tues Mar 2 17:40:53 2021 +0300 BatteryService: Mod: Check against all conditions * Change logical operators from `||` to ~&&` to achieve this. * Additionally, change to using supplementalOrEmergencyModOnline() to avoid duplicating logic. * This fixes battery power saver mode on some devices that were effected by the initial Battery mod commit. Change-Id: I9b2bfa26ab0c204f7a42ba6010f1f569fa7b0fd8 Author: Michael Bestas <mkbestas@lineageos.org> AuthorDate: 2023-07-11 00:38:16 +0200 fixup! BatteryService: Add support for battery Moto Mods Change-Id: If1171bd9ec8972a489db0540889690ae4f9a5d3b Change-Id: Ic4017dd7946ffcf4ab874131240136c07f3f063b (cherry picked from commit 619042ec7eda1d8c8392246b91398b790c8b1b56) -
The Fingerprint HAL is not always reporting fingerprint removal success, so report success on fingerprint removal if no error has occurred. Change-Id: I28fe2767ecffc9a830a91f2a1f262fbeaac73a1a (cherry picked from commit 19642c74c69a33d0edd72356e46b7d7e85ac6af9)
-
-
* We have RRO's that should enable regardless of what the target property is set to (e.g. `ro.com.google.gmsversion`). Change-Id: I58e4b4d80f89990e9d6dc8c7d6786f807d98e271
-
The code in FrameworkParsingPackageUtils was added in efbb3196 and copied from ParsingPackageUtils in services.jar At that point in time there was already a duplicated implementation but in 2 different jars, but after that change they now both live in framework.jar Let's migrate to the FrameworkParsingPackageUtils implementation as that's already used elsewhere in framework.jar Test: m, refactoring Change-Id: Icd816d59fbe9d0070167c526e52c3b4e172f412b
-
"contextual", "menu_ime" and "right", we get three different variants for one and the same thing. Or well, that's how it was, until Google decided to break it. "contextual", which was used for 2-button nav due to a Google change, now contains the floating rotation button, but the code expects the in-navbar rotation button (and that makes more sense too). This was broken by a more or less recent Google commit moving the floating rotation button handler to Launcher3 for taskbar. Manually changing this to "menu_ime" in this overlay however gets 2-button nav back on track. Accessibility button, rotation suggestion button, IME switcher and menu button (with extra downstream commit that returns support for this) now work in 2-button again. Thanks to SirRGB for bringing this issue to my attention. Change-Id: I0a09ec0aa8b7dbfef02d1aaf0dedd2128156a6e7
-
-
