- Jan 25, 2024
-
-
* 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
-
-
-
-
-
[ghostrider-reborn] updated to android 12, 13 Co-authored-by:Adithya R <gh0strider.2k18.reborn@gmail.com> Change-Id: Ia55ac91c2db2f44062674a699f8df63c96e1de5c
-
When the selected WFD route is not available, the cast tile in quick settings and the cast slot in the status bar are both shown as a connected icon, it is not reasonable. This CL checks whether the selected route is available when getting the cast devices. Bug: 247925238 Test: Mannual Change-Id: Ifdbf4c61e95504ae7fc24933695e6fd348d75750
-
Read the current user's setting for showing silent notifications on the lockscreen whenever user switching occurs. Otherwise, when switching to another user, the former user's setting will be in effect for the new user, which may cause silent notifications to be unexpectedly hidden or visible on the lockscreen. Change-Id: I65b10f82307cf8eecaafcd1a76ddb5f98bd7c326
-
-
-
On msm-4.14 devices, when the proximity sensor is in use, the smp2p-sleepstate IRQ is fired multiple times a second, with each one holding a 200ms wakelock. This is probably a bug in the DSP firmware. To fix this, avoid using the proximity sensor in doze mode, because sleep is preferred to turning off the screen. Change-Id: I57750afd77267abdc49780f70636626d20e666ad
-
Correct mistake in keyboard_layout_hungarian.kcm: Shift + 1 -> ' and add two missing combinations: AltGr + M -> < AltGr + . -> > Change-Id: I238cec3e23df36e054f35fb9a3847389fd844e6b -
Toggled (or 'sticky') modifier keys that lock when pressed twice cause unexpected behavior that confuses users. Shift is especially problematic, as there are three distinct Caps Lock states in Android: The Caps Lock key, Alt + Meta, and Shift pressed twice. Only the first illuminates the Caps Lock LED, and each can only be disabled by pressing the right key/combination again. This forces users to 'hunt' to find the right one, and pressing Alt twice will lock that modifier leading to yet more unexpected behavior... Get rid of locking for toggled modifier keys to improve this mess. Change-Id: I94de5d8d051b2d518457a1a44c9ee939508b9abb
-
-
-
Change-Id: I71d9379f9bfdce9efaec1e431a58daeb705d142b Signed-off-by:Aayush Gupta <aayushgupta219@gmail.com>
-
Store normal callback references in PrivacyConfig, rather than WeakReference. This prevents the callbacks from becoming phantom reachable (finalized) shortly after SystemUI starts. Prior to this change, devices with an overlay config to enable location indicators may not properly utilize the indicator until the device is rebooted at least once after first install, if the garbage collector wins the race and finalizes the necessary PrivacyConfig callback. Test: Manual: Boot and unlock a device and wait about a minute for it to settle. Run `adb shell "dumpsys activity service \ com.android.systemui | grep locationAvailable"`. It will return two results with matching values. Then, run `adb shell cmd device_config \ put privacy location_indicators_enabled false` (or `true`; whichever does not match the value seen earlier) to change the values. Finally, run the first adb command again to verify that both of the values for locationAvailable match and reflect the newly-specified value. Issue: calyxos#1648 Change-Id: I4ee1d5054a8bb294cea267034169c6615490a735
-
Apps like Messaging may be allowlisted to be unaffected by doze mode using the allow-in-power-save permission, but prior to this change, their jobs are still restricted from running when the device is idle, leading to delayed processing. On the other hand, jobs scheduled by packages that are user-exempted via the "Unrestricted" app battery usage option do not experience such delays. This change causes system- exempted packages to be treated the same as user-exempted packages. Issue: calyxos#1525 Bug: 223643513 Test: CtsJobSchedulerTestCases Change-Id: I6d95b3940e536e93aae4b2b48706069e964bdb99
-
Change-Id: I9570db3ecb4e160eb759d48ae1c4aa70436b624f
-
Change-Id: I8c279d5c9ccb2298e84a0af18758c3604a70d9d7
-
-
-
We all have dreams, thank you. Change-Id: I392b833f8a8617165aae8a8e96a5d552a0b249e6
-
Change-Id: I15d0f9fee13647062c651219b527e01a539b6909
-
