- May 24, 2022
-
-
*allow setting vibration when call is connected *allow setting vibration when call is disconnected *allow setting vibration for call waiting *this works with google and aosp dialer :) Change-Id: I14a403189f37e45fa4b999ab015bde8f89ae3da4 Signed-off-by:Mohammad Hasan Keramat J <ikeramat@protonmail.com>
-
Change-Id: Ie21e09f923001cfbab5a611426516a2a4ec23ac1 Signed-off-by: -
* So that they can be used in apps like launcher and settings. Signed-off-by:Pranav Vashi <neobuddy89@gmail.com> Change-Id: Ib1cb0987b08d02982177a47f3ba7e742fd747535
-
Change-Id: Ia574b200377fabcdad5a81db5aff8549b2e81549 Signed-off-by: -
@neobuddy89: * Includes addtional customizations / fixes * Complete rewrite to work with code improvements * Updated APIs for Android 11 Signed-off-by:
-
This is a squash of the following commits: Author: Utkarsh Gupta <utkarsh.eminem@gmail.com> Date: Tue Aug 18 12:27:39 2015 +0530 SystemUI: use new visualizer from Eleven Change-Id: I4441440868cac71caa32c91a0875f00a630fe596 Signed-off-by:Utkarsh Gupta <utkarsh.eminem@gmail.com> Signed-off-by:
Roman Birg <roman@cyngn.com> Author: Mikalacki Sava <mikalackis@gmail.com> Date: Thu Sep 3 23:10:35 2015 +0200 SystemUI: fix NPE crash when Visualizer is not initialized Change-Id: Ic3774011acfae0312f1642d88c7f5bf2abc9f5a7 Author: Roman Birg <roman@cyngn.com> Date: Fri Sep 4 15:55:39 2015 -0700 SystemUI: hide visualizer when keyguard is occluded Change-Id: Ia943fd829f7a379fee0f657bb08c34b8c6f36caa Signed-off-by:
-
This is a squash of the following changes: Author: Danesh Mondegarian <daneshm90@gmail.com> Date: Sun Nov 10 23:30:56 2013 -0800 SystemUI : Port forward statusbar brightness control Brings back the status bar brightness control from cm-10.2/cm-11 Change-Id: Icc04e7da3286e9925f8b90528c1e022b33d33e9d Author: Roman Birg <roman@cyngn.com> Date: Mon Dec 1 16:08:21 2014 -0800 SystemUI: improve brightness slider behavior Mimic the brightness slider behavior in the statusbar. This adds logic to make the statusbar slider also work with automatic brightness mode enabled and it will instead adjust the temporary automatic brightness overrride. Change-Id: I78814a785decc83df94844fcc2f489c8cbec2b65 Signed-off-by: -
This change is a combination of following changes: 1) frameworks/base: Support for third party NFC features 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 Author: Puneet Mishra <puneetm@codeaurora.org> Change-Id: Ic11dc68c4ea83262c705ec50b75b5808aa064f82 (integrated from commit 57a001b7851c97d41f042dda643f9a87aa6306e5) 2) NFC: Allow extensions to ApduServiceInfo Mobile network operators expect additional features in ApduServiceInfo to support their payment solutions. To achieve this, the final keyword is removed from the class definition and its instance variables, thereby allowing extensions to the class. Author: Puneet Mishra <puneetm@codeaurora.org> Change-Id: I9058d08e729027b04ee94405c66ff9d99c0f963b Change-Id: I04bbe46bf9efd032e973bba7a16dc430fb6edd12 -
Author: Luca Stefani <luca.stefani.ge1@gmail.com> Date: 2019-11-30 13:41:05 +0100 SystemUI: Bring back good ol' circle battery style * This code is based on the old Java implementation and converted to Kotlin * Instead of creating different style within the same drawable create one on its own, this makes the code more readable and future proof Change-Id: I23798426e603b277408fb63f4898b385027e7eeb Author: Bruno Martins <bgcngm@gmail.com> Date: 2021-04-08 21:41:24 +0100 SystemUI: Fix status bar battery icon title The wrong string was being picked up which is not capitalized and not even localized. Use the already localized string from SystemUI package. Change-Id: I4be427c95a0fb98c77d450e0791bb8e3442ed3a1 Change-Id: I025811006cf6088d94b6a2e2e5520543dedd7f98 -
Adapted to Lineage SDK and squashed with the following changes: From: Adnan Begovic <adnan@cyngn.com> Date: Wed, 05 Aug 2015 10:40:41 -0700 Keyguard: Don't disable visibility when scrambling pin. Otherwise the first numbers text is flipped to invisible even though it shouldn't be. Change-Id: Ia2b80d594e7f11af7a60a85bdb4ea9909d0ac20b From: Adnan Begovic <adnan@cyngn.com> Date: Wed, 05 Aug 2015 16:21:27 -0700 Keyguard: Fix scramblepin logic. Change-Id: I71e6d26e853fa7bfaeea4b3256902881ac7f74fc From: LuK1337 <priv.luk@gmail.com> Date: Sat Apr 24 18:14:46 2021 +0200 Keyguard: Fix mapping mismatch between KeyEvent and NumPadKey Change-Id: Ida28a4f037c2f3fa843ac136779e026020d711db Original-Change-Id: Ibe8611eb0b8a5bd9275bc96682d2cbafaa37d8f5 Change-Id: I6716b1c76b69d51bd1457ce07de2274541fca1e8 -
Some devices don't support the High profile very well. Use Main profile, which is more compatible, so they can use screen recorder too. Change-Id: Iac23480e080edf4300e6f411c3394c0b41030daa
-
This implements and API for apps to interface with NvCPL and by extension the PowerHAL. Reverse engineered from the Shield Experience 8.2.0 update then cleaned up to match Android standards. Change-Id: I774ac62c8867151f21712cfeee25f96a591415ad
-
NvCPL works in conjunction with the PowerHAL in order to adjust various performance knobs based on the app or device specific profiles. Change-Id: I4953cbb96d729dbe0cee6d7071b5933586770330
-
This is not necessary because BiometricPrompt is not drawn above the navigation bar. Change-Id: I7a00a0d6f1b2b68d6c642be03e23849029f8faa1
-
1) Ensure the spacer measurement is clamped to 0. Negative values cause the layout to exhibit undefined behavior. 2) Instead of making the layout xml even more complicated, for low-area sensor devices, we just have onLayoutInternal() translate the icon and indicator to where it should be. Note that this can definitely cause overlap with the button bar, but at least this implementation allows the button bar to be shown (and thus pass curent CTS requirements). We can have additional refinement in the future. Bug: 201510778 Test: atest CtsBiometricsTestCases Change-Id: Ie9869f15fc3afddc3bd4392a2fd08efbf136cd6c
-
Reference: https://review.lineageos.org/c/324695 Signed-off-by:
Tư Mã Tần Quảng <baobaoxich@gmail.com> Change-Id: I07dd734faca6116356fc05af7dff262bec65b4cb
-
* The creates a CLI accessible version of per-app cellular data, VPN, and wifi restrictions. Reference: https://review.lineageos.org/c/259455 Signed-off-by:
tumatanquang <baobaoxich@yahoo.com> Change-Id: I005cacdd7be3e6311ef47465d3fca7fa847d3b7e
-
Change-Id: I62e46729278d57b8b21aa0c307f25d9ec053b216 Signed-off-by:SamarV-121 <samarvispute121@pm.me>
-
Based on the following changes: Author: Ricardo Cerqueira <cyanogenmod@cerqueira.org> Date: Mon Nov 4 03:37:40 2013 +0000 framework: Add advanced reboot options (2 of 2) This commit is an squash of the commits below and re-adds the reboot logic to CM. I took the liberty to rewrite some of the ShutdownThread code because it had some lingering issues present since I originally wrote this for CM7 (!!). Namely, the reboot reason was being changed when the items are pressed instead of when the user presses the positive button. This made some people add workarounds like handling back button presses and whatnot, these are gone now. commit 588464bea40b92b04c4aeee35c47f7becceeed56 Author: Roman Birg <roman@cyngn.com> Date: Thu Jul 10 14:20:42 2014 -0700 advanced reboot: add soft reboot option Adds a "Soft reboot" option which restarts zygote, as requested in JIRA CYAN-3998 Change-Id: Ia6e5ed9b053e1c5ebd1fc55e5692858b97f7e0fc Signed-off-by:Jorge Ruesga <jorge@ruesga.com> Author: Zhao Wei Liew <zhaoweiliew@gmail.com> Date: Sat Dec 10 18:07:51 2016 +0800 core: Adjust power menu icons for 7.1 Resize the icons to fit in with the new power off & restart icons. Also, use an icon without a home button for the screenshot icon, since home button-less phones are a growing trend. Change-Id: I5131346f65345010bba45dca04f3d767e6f9746a Author: Dave Kessler <activethrasher00@gmail.com> Date: Wed Feb 18 10:27:58 2015 +0200 GlobalActions: Always add power off option to power menu Change-Id: I3083cda3b8c665a65f1260984a5be41faa384510 Author: Zhao Wei Liew <zhaoweiliew@gmail.com> Date: Fri Dec 9 20:52:29 2016 +0800 GlobalActions: Inform user of screenshot long-press action Long-press actions are extremely obscure. Hiding the partial screenshot feature behind a long-press action is highly detrimental to its discoverability. Inform the user of the screenshot long-press action by displaying a short summary message. Change-Id: I949bd0ef80a654d6cdf852b7a3138e7379ad36d2 Author: Michael Bestas <mikeioannina@gmail.com> Date: Sat Nov 7 23:52:26 2015 +0200 Fix reboot dialog messages * Fix mismerge * Fix wrong messages being displayed when rebooting to recovery Change-Id: I09a04cc82d48539e8086fd55c30d6160c292bc08 Author: maxwen <max.weninger@gmail.com> Date: Fri Nov 15 00:16:26 2019 +0100 SystemUI: Add reboot fastboot to power menu Change-Id: I88f00a273f4a0be1355158c58a24db78cb8e684e Author: Bruno Martins <bgcngm@gmail.com> Date: Fri Feb 25 09:49:09 2022 +0000 GlobalActionsDialog: Hint that there's more behind restart button If advanced restart is enabled, show a slightly different text to hint that there might be something more behind it. The string exists, so make use of it. Change-Id: I607fb48c24ea7a8c004ccca33af19ced1847e170 Change-Id: Id561b0111e8cc7a80c345668d79a363ec0ec389c
-
Default to the old long press behaviour when the feature is enabled. Change-Id: I5fc37f818b06db2bd2d315cffee2041a740781ed Signed-off-by:Jesse Chan <jc@lineageos.org>
-
Passing control action to activityStarter.dismissKeyguardThenExecute() is enough to toggle it post device unlock. Test: Use a control action from locked device, notice that it's no longer toggled twice. Change-Id: I48cb9e0ad2425d35063fddefc738ab36c01690b8 -
Change-Id: Ice1bab5f3d1b3a15f20085cfb7f5578c7f70855a
-
* Causes much logspam, especially when using Clash/Shadowsocks because notification is updated every second. Test: m, no logspam anymore Change-Id: Ibe2db6afa18ebc68032730d81c29fb4cfaf8601f
-
* Since we are shipping userdebug builds by default it'd be nice to keep signature and version downgrade checks intact. * Fixes : https://gitlab.com/LineageOS/issues/android/-/issues/2192 Change-Id: Ib46ccb50ac091469caf99a73a5a08942cbc457f6
-
* App would be killed once limit reached, this is really bad for users. Change-Id: I226a7a34031c9e9d8bf6843c22d79e72203bf867
-
When empty the usap pool, the usap processes may be blocked by usapPoolSocket.accept(), which cause the usap process fail to kill immediately. So we can move the position of blockSigTerm after usapPoolsSocket.accept() and delele the old blockSigTerm in the while loop. Test: manual test. 1.setprop persist.device_config.runtime_native.usap_pool_enabled true. After 1 min, trigger fill usap pools. 2.setprop persist.device_config.runtime_native.usap_pool_enabled false. After 1 min, trigger empty usap pools. 3.repeat step 1. Signed-off-by:zhangjianqiu <zhangjianqiu@oppo.com> Change-Id: I657940b30f71cdc717c673be6d70738e61e2bb68
-
Picked remaining support from commit bbd00b7 and lid state handling from commit 68771fe. Change-Id: I310dfd026b2dc5e7bc47dd4a2c1ae029d58a1e8e
-
* Use keypress info to exclude pressing volume keys from illuminating HW buttons in config_buttonLightOnKeypressOnly mode. Change-Id: I6bfc7ddd075e12e1ad10c3663a63e80c8d7f983d Signed-off-by:Corinna Vinschen <xda@vinschen.de>
-
Author: Anas Karbila <anaskarbila@gmail.com> Date: Sat Jun 3 03:21:32 2017 +0200 PowerManagerService: Allow to light up buttons only when pressed * Right now capactive, lit hardware keys are being lit every time you either touch them or the screen. But some devices handle this differently on stock: Display touch => buttons not lit Buttons touch => buttons lit * Thus, add a setting in order to allow the user to choose the preferred behavior. Change-Id: I35ac71a8274568901f962c9692788d1c682a98dd Author: Corinna Vinschen <xda@vinschen.de> Date: Sun Aug 6 15:05:54 2017 +0200 PowerManagerService: fix HW button illumination timeout Change I35ac71a8274568901f962c9692788d1c682a98dd, introducing hardware button backlight on button keypress only, also introduced a bug: When touching a button and then performing display activity while the buttons are still on, the buttons would keep lightened up until the next user interaction, potentially only switched off at the next screen off timeout. Also, the buttons were not illuminated on device wakeup. This patch fixes it, together with another, long-standing problem: When touching a hardware button, nextTimeout was set to now + mButtonTimeout, even if mButtonTimeout is longer than the timeout determined by the screen off timeout. To wit, if screen timeout is set to 15 secs, but button timeout to values > 15 secs. Change-Id: I8a56f1d1e0138c38ed6fe294e4816a9f7f744f1e Signed-off-by: -
Squash of: Author: Ricardo Cerqueira <cyanogenmod@cerqueira.org> Date: Fri Nov 23 14:23:16 2012 +0000 Reintroduce button-backlight (and respective inactivity timeout) The power manager rewrite from Change I1d7a52e98f0449f76d70bf421f6a7f245957d1d7 completely removed support for control of the button backlights, which makes all capacitive buttons out there stay dark. The commit message in that change mentions it hasn't been implemented _yet_, so this fix should be temporary until upstream does their own implementation Change-Id: I6094c446e0b8c23f57d30652a3cbd35dee5e821a Author: Danny Baumann <dannybaumann@web.de> Date: Thu Aug 22 08:53:24 2013 +0200 Add PowerManager integration for button and keyboard backlight. Allows setting button and keyboard backlight brightness as well as button timeout. Change-Id: I550cccafc0a8f90d6347de9261adb26b75955cc4 Author: Steve Kondik <steve@cyngn.com> Date: Sat Jan 3 05:13:26 2015 -0800 power: Disable keyboard/button lights while dozing/dreaming * With hardkeys and doze mode enabled, entering suspend results in an epic battle over the lights. It's a bad situation. Disable them when we're sleepy. Change-Id: I7f1fc35a1573717d1ea101a07c4171d6f66d1553 Author: nadlabak <pavel@doshaska.net> Date: Sun Jun 7 02:01:05 2015 +0200 PowerManagerService: Fix updating of mUserActivitySummary I7f1fc35a1573717d1ea101a07c4171d6f66d1553 missed the fact that the primary purpose of the affected condition block was to update mUserActivitySummary and the button/keyboard light handling was just appended to it later. This fixes the waking from dream/screensaver by user activity. I30c5c8c9c09e3d57ace18cac72b783510b9b3bf3 is removed here as well as it was just a band aid. jira: NIGHTLIES-1285 Change-Id: I6b2f6c58e73110787d62e86d4d2ef538638cf491 Author: Bruno Martins <bgcngm@gmail.com> Date: Tue Dec 26 17:15:05 2017 +0000 Forward-port button brightness implementation to O * Reworked for the new handler interface, restoring also removed methods (partial revert of commit 86c39f9e). * Keyboard backlight brightness support left out for now. Change-Id: I53f031fa2da394e95a2b29a01eb3c6a8f8132507 Change-Id: I5176a2028c18408c17bac7f25e62b5612fd6c227 -
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 Change-Id: I4a6d3f89bc171c3921875b24c077cb78c03517ad -
Add support for camera button Based on commit http://review.cyanogenmod.org/#/c/51487/ This patch adds: - Use camera button as wake key - Use focus button as peek and wake key - Use camera button to launch (secure) camera Change-Id: Ia515c04cca098bf0d20b077ebffc079ee4008f21
-
[mikeioannina]: Adjust for 5.0 changes Change-Id: I1b45da63b815aa1b3ddf7cda2b7afb0872ab433f
-
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
-
Change-Id: If3ed27e8408cdf383653c7d18988112c13f8bcea
-
Some apps may react to back key long press and it doesn't make sense to allow them to do that if 'Back long press action' is set to anything other than 'No action'. Change-Id: Iacac909d6a288cacf964c89d9586d572d14d1871
-
Change-Id: I28762c88d4777f8dbc8f213a2522875c3428fdab
-
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
-
* When the torch is on, any subsequent long press power is almost certainly intended to turn the torch off (regardless of screen state). Therefore, always allow long press power to toggle torch if the torch is on. * Tested: long press power toggles torch on/off with screen off. long press power toggles torch off with screen on and torch on. long press power brings up global actions menu with screen on and torch off. Change-Id: I932caa9f3be06d14408aea2ecb3a6eca73e052e0 -
This allows long press power button for torch and long press volume buttons for track skip to work during ambient display. sam3000/razorloves: partial pick from: Author: ezio84 <brabus84@gmail.com> Date: Fri Feb 2 01:24:34 2018 -0500 base: Support binding the power button to flashlight Thanks to beanstown106 for the initial longpress action calls in PhoneWindowManager (improved by lineage guys) [cut] Allow torch action also on ambient display Change-Id: I12da044f86c7b625872607529cf8524615cf576b Author: ezio84 <brabus84@gmail.com> Date: Sun, 7 Jan 2018 21:24:53 +0100 Fix volume rocker skip track on Ambient Display and Lift to Wake we need to check if dream service is dozing before checking keyguard status Change-Id: Ic3a6c830496188bb6edf27043cd24eb2d553bb82 Change-Id: I2463579e056364652b549524bc9775da4fa35b1f
-
