- May 24, 2022
-
-
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 -
Change-Id: Idfb12a7bae6d921d207b5becd69b1005ce3d2b92
-
Change-Id: I7662b593f5ba52cafe3d7ba7cf2099b29b8d308b
-
Change-Id: I5ebe1ad88950ba56ce1445b77b7f8cdf030463da
-
Author: LuK1337 <priv.luk@gmail.com> Date: Mon Jun 4 10:05:37 2018 +0200 PhoneWindowManager: Improve home button wake haptic feedback handling * This fixes an issue where haptic feedback is used when screen is off and home button wake is disabled. Change-Id: I7ac4c00598cedf7f174dc99629f55dc7b74b0d2a Author: Gabriele M <moto.falcon.git@gmail.com> Date: Mon Sep 26 00:43:08 2016 +0200 Fix volume keys wakeup status handling The same status flag is used for the three different volume keys, however nothing prevents users from pressing multiple keys at the same time. This allows to set the status flag with one volume key and clear it with the other volume key. Use one flag per key so that we never end up in an inconsistent state. This fixes the seldom power button issues that happen when the "volume wake" feature is enabled. Change-Id: I08f5f9ff696bef3dd840cff97d570e44ebe03e4e Author: Martin Brabham <optedoblivion@cyngn.com> Date: Wed Dec 3 11:48:28 2014 -0800 Android Policy: handle volume key event as wake key when preference is set Change-Id: If9a61cd65553bf00f0efda1a75b1ab75b9129090 Author: willl03 <wgangers@gmail.com> Date: Mon Dec 8 11:13:28 2014 -0500 Only go HOME if screen is fully awake Avoid going home when hardware home button is used to wake the device on an insecure keyguard Change-Id: I5d5d8c4fff76967c29e70251f7b165205005ba11 Author: Matt Garnes <matt@cyngn.com> Date: Tue Mar 31 14:39:38 2015 -0700 If a wake key is disabled by the user, do not wake from doze. Currently, any wake key will wake the device from a doze, even if that key has not been enabled as a wake key in Settings. If the device is 'dreaming' in the Doze state, check if the user has explicitly disabled the wake key (or never enabled the setting in the first place) before waking the device. Change-Id: I7397087c143161e8e1ddb84d0e23f6027fea0aac Author: Michael Bestas <mikeioannina@gmail.com> Date: Thu Dec 18 04:26:38 2014 +0200 Cleanup button wake settings (2/2) Change-Id: Ie37136cbd57c4c334321abbfa4543727e940bc43 Keep quiet when volume keys are used to wake up device - Userspace will make a 'beep' with it receives a key up, so consume that event as well. - Removed wake key check in music control code as it will already be disabled here. Change-Id: I93839acd39aec8a2ee40291f833a31f6b048c9f8 Wake Keys: enforce the wake keys overlay * Keys disabled as wake keys by the overlay were still being allowed to wake the device. This change enforces the hardwareWakeKeys settings. Change-Id: Ifde0491b2de64a7f61a101cf22f5589cb5e841e2 Allow disabling Search/Recents button wake (2/2) Change-Id: I6a2ac064efc4fe85413bf0b935c28aa7bde5d672 Author: Danny Baumann <dannybaumann@web.de> Date: Sun Nov 30 23:04:37 2014 -0600 fw/base: allow home button to wake device [1/2] Change-Id: I2b79561dcfa7e569b2e24bbabfffb11517d4d313 Change-Id: Ic294515c7200c1260ac514db23ef3778d374d727 -
Fixups for ten @sam3000 This is a squash of the following commits: Author: Phil Tunstall <ptunstall@gmail.com> Date: Fri Nov 14 09:44:49 2014 -0800 Hardware key custom rebinding (1/2) Framework changes to allow rebinding of the actions performed on the following key press events: Home long-press, home double-tap, menu press, menu long-press, search press, search long-press, app-switch press and app-switch long-press. The available actions are: Nothing, open/close menu, recent apps switcher, search assistant, voice search, in-app search, device sleep, and launch camera. Change-Id: I72c0d220a09d79230bfa299e0521ed693e5c25f1 Author: Steve Kondik <steve@cyngn.com> Date: Tue Oct 18 23:38:28 2016 -0700 wm: Add support for split screen button behavior * And make it the default for long-press recents like the navbar. Change-Id: I432c80a2c9b29b9a02d64e29d484f92623b0648a Author: Bruno Martins <bgcngm@gmail.com> Date: Mon Dec 25 22:10:28 2017 +0000 Forward-port hardware keys custom rebinding to O * Adapted to Lineage SDK as well as to the moved hardware keys configs and constants. * Converted variables that track user-customisable behavior for certain key events from int to Action in order to use the newly introduced SDK function helpers. Change-Id: I2e2234e3d01d943e0cadd23898288f8a88936a47 Setting a custom menu key action will do both the custom action and the default action at the same time. Comparing code with 14.1 we're missing the return here. Change-Id: I2f188ec78fae5068ffa1a5c80a8afa5ee2f167b5 -
Change-Id: I43f3d339b73a3ff3cc19a881975f018b56b9d472
-
Fixups for twelve (@neobuddy89) Fixups for ten (@sam3000) Squash of: Author: beanstown106 <nbenis106@gmail.com> Date: Sun Jan 17 09:14:19 2016 -0500 policy: Long-press power while display is off for torch Long-press the power button while the display is off to turn the torchlight on and off. Credits: - Lion0738: The main hooks here: https://github.com/lion0738/android_frameworks_base/commit/9af2b7844a4d973c8b6c542d7937f56a24a7e5f1 - Atlantis: The logic on where to hook into this for power button only - Alex Cruz: Helping and giving me some pointers along the way Change-Id: I14365389990eb06daaa127f5db66df45abf6c064 Author: Sam Mortimer <sam@mortimer.me.uk> Date: Sat Dec 24 13:22:53 2016 -0800 [1/3] Torch long press power: add auto-off function Change-Id: Icdf50082324f8292859f0df8b271e730b02c84e7 Author: Pranav Vashi <neobuddy89@gmail.com> Date: Fri Dec 3 08:53:59 2021 +0530 Fix long-press power for torch on Android S * We must define FLAG_IMMUTABLE when creating PendingIntent on Android S Signed-off-by:Pranav Vashi <neobuddy89@gmail.com> Change-Id: I49222892c8fbc8a63af580c763e8987b225b11d2 Signed-off-by:
LibXZR <i@xzr.moe>
-
Change-Id: I56306e3a2bc9633c29a01196452c8e158d0d7fa7
-
For Spotify and other players that allow music controls for remote devices (PC, PS4) through the media notification Change-Id: I38887f8b1cff1a0c1e3adadbfe37d5af59b5cdcc
-
We can't use a generic DeviceKeyHandler here, because we don't want to override some of the AOSP logic (silencing incoming calls, screenshots) and we need to know if the device is interactive or not (for screen-off music controls) Change-Id: I485c2f6006c5bbd358ba0cbd32917689826c5c6d
-
Change-Id: Icf333f13bccfed9ba4ec030716d2bcf83841ef55
-
* Local HBM does not shows pressed icon * Global hbm shows pressed icon Change-Id: Ic9f51a33c1781527f0c7fc41e8bfe320bf2653d2
-
* TYPE_KEYGUARD_DIALOG was below volume and navbar and would have caused cause issues when HBM was enabled * BiometricPrompt uses different layer which again is below navbar and causes bright volume and navbar Change-Id: Ia37930ffd7a28fc8785f26ada3b69a02df0d4891
-
This should let us choose between multiple UdfpsHbmProvider implementations. Change-Id: I9b93e32644feaf1398cdac69e9696d8ec195f246
-
* set a solid color by configuring config_udfpsColor * set a custom image by setting udfps_icon_pressed and making config_udfpsColor #00ffffff (transparent) Change-Id: I2460f6196d32fe46eb97f9a5c767bde5c9976681
-
Update the screenshot share intent to align it with the data that is present in the screenshot edit intent. Bug: 220161786 Test: Take screenshot. Tap share. Tap Edit, which opens screenshot in Photos. See buganizer for more info. Change-Id: I7a1254e579cea38fd70fc13da81e1dae98f5f968 -
* 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)
-
Only Primary storage and adoptable storage can get visible flag. so, Unless Device support adoptable stoarge, it cannot have visible path for sdcard. In refrernce, Adoptable storage cannot support FBE. If device cannot get visible path for sdcard, 3rd app and MTP cannot read sdcard even though they have READ_EXTERNAL_STORAGE permission. this fixing is releasing visible condition for all sdcard. Test: Check MountFlags is VISIBLE on Log. Change-Id: I7afe5078650fe646e79fced7456f90d4af8a449a Signed-off-by:Sangho Yoon <sangho.yoon@lge.com>
-
* Fixes a2dp offload on devices not using QTI BT stack. Change-Id: I5044d02f8be74bbf050b16083e753bd392dac0a6
-
