- Feb 10, 2024
-
-
[ghostrider-reborn] - Use app volume icon by amartya (@ yukiscape) Change-Id: I674cda1d7463b3603ccaac673178aeead4093619 Co-authored-by:
yukiscape <garikapatiamartya@gmail.com> Signed-off-by:
chrisw444 <wandersonrodriguesf1@gmail.com> Signed-off-by:
Mohammad Hasan Keramat J <ikeramat@protonmail.com> Signed-off-by:
cjybyjk <cjybyjk@zjnu.edu.cn> Signed-off-by:
Pranav Vashi <neobuddy89@gmail.com> Signed-off-by:
Adithya R <gh0strider.2k18.reborn@gmail.com>
-
Change-Id: Ic6644bd25854854e50ec03fed9ef853c39c4248f
-
-
Dhina17 authored
Enabling blur behind via style attr causes an unexpected behaviour that power menu always has the blur behind even when the device disables the systemui blur. [persist.sysui.disableBlur=1] GlobalActionsDialog is a part of SystemUI so it should follow BlurUtils#supportBlursOnWindows not only Settings.Global.DISABLE_WINDOW_BLURS. With style attr, it only followed Settings.Global.DISABLE_WINDOW_BLURS, that's why worked fine with blur toggle in targets which don't disable systemui blur. Change-Id: If6aa97ce3df7f12e181274d85a05531fcb575ec5
-
Unpatched HWUI blur required for CTS test Squashed: commit 3f3bd82e2e1cc9219cb52f62c722b7bb74d7149e Author: nift4 <nift4@protonmail.com> Date: Sat Jun 17 14:26:19 2023 +0200 Revert "base: Fix corny blur rendering bug" This reverts commit 5e75419441c8d459d7d2e9a7e609962f79944517. commit 1d40918a8943961c110f03cc34f29a85011ec1fa Author: nift4 <nift4@protonmail.com> Date: Sat Jun 17 14:27:15 2023 +0200 Revert "fixup! blur: Switch to glass blur effect" This reverts commit e551e7022744fa1171d4732b3ac42715d53feaa8. commit fc6c4c4b3aab9d0ee4994e02ad923eea814b649c Author: nift4 <nift4@protonmail.com> Date: Sat Jun 17 14:27:20 2023 +0200 Revert "blur: Switch to glass blur effect" This reverts commit e081220a381f282c6dac9ff0248ce1d09bacb8b1. Test: CtsUiRenderingTestCases android.uirendering.cts.testclasses.PaintTests Change-Id: I408c51663128cc9bb788f51161d3badba2b83141 Signed-off-by:Saalim Quadri <danascape@gmail.com>
-
Dhina17 authored
- To match with AOSP default style. Change-Id: I2b8bee6d33e841323d832ac6d24c913f64b72b23
-
Dhina17 authored
- Also bring back Scrim Alpha value. - Matches with AOSP style when blur is disabled. Change-Id: Icafaac08b8e14ed5aa8c9b99b4c22be6babbf860
-
Change-Id: Ic8819c9b9cf5d1469a47f3d16cd10918285f40f9 Signed-off-by:Mohammad Hasan Keramat J <ikeramat80@gmail.com>
-
Dhina17 authored
Squashed: * SystemUI: Fix HD calling icon for RTL layout * SystemUI: sb: Fix VoWifi icon size * SystemUI: sb: Hide wifi airplane spacer when vowifi is available * SignalDrawable: Add support for Cut + Roaming back Adithya R <gh0strider.2k18.reborn@gmail.com>: HD icon shows for VoLTE/VoNR, and wifi calling for VoWiFi. Based on CLO's volte/vowifi icon implementation, reworked manually. Drawables taken from Nothing OS and manually tweaked. Dhina17 <dhinalogu@gmail.com>: Rewrite it for new status bar impl in Android 14. Move VoWifi icon to Wifi space. New VoWifi icon with SIM identification. Signed-off-by:Weijie Wang <quic_weijiew@quicinc.com> Co-authored-by:
electimon <electimon@gmail.com> Co-authored-by:
nift4 <nift4@protonmail.com> Original-Change-Id: I0190394690e9b38e0575ffb099be8a5ed2ae9d90 Change-Id: Ib48b1295d060acf462b2f91e81cbb570fd8df42e
-
Dhina17: Ported to 14 Change-Id: I326e1d54019179f0505a558b7e57ab6a2479cdf2 Signed-off-by:
Dhina17 <dhinalogu@gmail.com>
-
cjh1249131356 * Port to QPR2 neobuddy89 * Update for LOS ikeramat * Port to A14 QPR1 with contentObserver Co-authored-by:
cjh1249131356 <cjh1249131356@gmail.com> Co-authored-by:
-
Dhina17 authored
Change-Id: I2b09b09170b3ec498e036b08f2e6de40c0e6e6c3
-
Dhina17 authored
HAL supposed to send all deleted ids when we call remove with id 0. 0 means remove all. Then fwk use the deleted ids to clear those ids in local biometrics data. (xml files in /data). but some HALs just return back 0 as deleted id instead of the correct ones. so local data become not in sync causes some issues like showing it has biometrics after removing secure lockscreen. It is supposed to be fixed in HAL but :) Change-Id: I95896a0db224e9d8c4abca858057c5c83a668921
-
Change-Id: Ibf6fdac4c7555b5a7f8cec654f3590e0151ac820 Signed-off-by: -
Based on AOSPA fw/base 0af31949c69f7c306b49ecf2c25579300973fdc9 - https://github.com/AOSPA/android_frameworks_base/commit/0af31949c69f7c306b49ecf2c25579300973fdc9 Allows to indicate whether a device is charged using a proprietary oem fast charge solution which writes status to sysfs. [nift4: Some devices turn off fast charging when display is on, which is why even though AOSP detects the fast charger, the user won't actually get to see it without this commit.] The oem fast charge detection tries to be as generic as possible and is configured via overlays. nift4: - port to 13 - support using custom value for path, don't hardcode 1 - big cleanup Change-Id: Ia91a9c3bb20967c5aac18c24ac7c2be10a0b8bf1 Signed-off-by:
Alexander Martinz <alex@amartinz.at>
-
System icon pack changes were previously managed by reconstructing some components which used them, such as KeyguardStatusBarView. This introduced a memory leak where KeyguardStatusBarViewController never unregistered a callback, thus it was not being garbage collected. Furthermore, some usages of the system icons were not updated on a pack change. Change that by recreating the icons on theme changes. This reverts commit db9671c8544cce1cb20dc5c439e8eea15df21ce0. Change-Id: Ic2b774d243546a88ac2e17f8441e073629caa1c8
-
Once the animation starts, AOSP just disables blur. This works because the QS panel is not transparent, so the user won't notice. Due to our transparent QS panel patches, it becomes obvious that blur just disappears once a user opens an app from QS (long press qs tile, use settings button, etc). To improve this situation, we use a small trick: Unlike how it looks in the animation, the shade is always on top of apps, hence, our newly-launched app is below the shade and below the blur. We disable blur in the very moment the app starts fading in to make it as un-noticeable as possible for the user, without accidentally blurring the app in the process. Change-Id: Iecd794ef67c92a76f93c500e8feec9723f0e0d41
-
Google uses com.android.internal.R resources in a blob, however, internal resources don't have stable IDs. Manually stabilize the IDs with patched aapt2 to fix malfunctioning blob crashing. Fixes: java.lang.IllegalArgumentException: missing configurations: expected config_displayWhiteBalanceBrightnessFilterIntercept [Dhina17: Updated IDs for Android 14] Change-Id: I63bbc171bdfdcceb839a5f3eb6f5d0880c6b27fd
-
-
Dhina17 authored
Change-Id: I8a424cd3bf2c35490dbde3f9a303174194fcf902
-
- We are running out of space in portrait after 23205: Screenshot: Add delete action chip intent | https://gerrit.aospa.co/c/AOSPA/android_frameworks_base/+/23205 Change-Id: I8967e1c5925701a84bca81d7f15b3d0457c2bb0f
-
-
-
java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 524 at android.util.SparseIntArray.keyAt(SparseIntArray.java:183) at com.android.server.net.NetworkPolicyManagerService.addSdkSandboxUidsIfNeeded(NetworkPolicyManagerService.java:5978) at com.android.server.net.NetworkPolicyManagerService.setUidFirewallRulesUL(NetworkPolicyManagerService.java:5998) at com.android.server.net.NetworkPolicyManagerService.updateRestrictedModeAllowlistUL(NetworkPolicyManagerService.java:4450) at com.android.server.net.NetworkPolicyManagerService$12.onAvailable(NetworkPolicyManagerService.java:1450) at android.net.ConnectivityManager$NetworkCallback.onAvailable(ConnectivityManager.java:3823) at android.net.ConnectivityManager$NetworkCallback.onAvailable(ConnectivityManager.java:3805) at android.net.ConnectivityManager$CallbackHandler.handleMessage(ConnectivityManager.java:4132) at android.os.Handler.dispatchMessage(Handler.java:106) at android.os.Looper.loopOnce(Looper.java:201) at android.os.Looper.loop(Looper.java:288) at android.os.HandlerThread.run(HandlerThread.java:67) at com.android.server.ServiceThread.run(ServiceThread.java:44) Change-Id: I500f4c7b3c4bc7609c494e4ab8763389a3f2bdbb -
* Show battery percent on 1 value and percent inside on 2 Signed-off-by: -
Signed-off-by: -
To reproduce: 1. Open pre-honeycomb app with options menu 2. adb shell input keyevent MENU 3. Observe menu opening 4. adb shell input keyevent MENU 5. Observe menu closing 6. adb shell input keyevent MENU 7. Menu not re-appearing! Root cause: If opening menu for the first time, decorView will be null and we call initializePanelContents to populate st.shownPanelView, therefore hasPanelItems succeeds as it should. However, when opening menu for a second time, decorView will exist, we will skip the code block and shownPanelView will never be initialized, which will cause false negative of hasPanelItems(), therefore menu will not be shown. Fixes: 3c2bfc88 ("CP: Don't create panel if content is empty") Test: Reproduce steps now successfully open menu every time. Change-Id: I2c49b7595bd0f13d9800ec7f0d493ff96236adf2
-
-
Inspired by nothing ;) Shrink down the dialog a bit to make way for it. Change-Id: I56b8c70011c90103e87ee298d83d9f93270d8bc5 Signed-off-by: -
-
-
-
When we changed our notif media style, we still rely on the old media notification color parsing. So we used halfway the color palette before using some nice color that might be on the whole cover art. Also, give the muted color an oportunity before going full monochromatic Change-Id: I7aae9c690e815a826a5271262c6e7d9aa31b4446
-
- Feb 08, 2024
-
-
* Stop turning on the audio hardware and playing silence. * Kind of annoying with certain types of Bluetooth headphones that don't actually play silence very well (hissssssssss). Not to mention power usage. Change-Id: I6985db8710f8b0f61619ac57e8efb9e4e01cc31a Signed-off-by:
Joe Maples <joe@frap129.org> Signed-off-by:
Joey Huab <joey@evolution-x.org>
-
-
* If selinux is permissive, Google decide to disable seccomp filter because debug tools like strace needs both them to be disabled to work. * This is fine for developers, but if one runs selinux permissive in production, it will be super easy for a macilious app to gain root access on Q+, with newly interoduced ZygotePreload API. * Technical details: https://github.com/dantmnf/BrokenSandbox https://github.com/vvb2060/Magica Change-Id: I1a1208a0a82d36aeb49820972429d106919d6bce (cherry picked from commit 32cf8c9cb1915ef67526c4e961ecb6a2181b6934)
-
Change-Id: I97620578ab8a34506b6bdf0cfe91c2f34000f58e
-
Informing the user that ADB is enabled does not necessitate an alert sound. It's especially annoying with the default AOSP notification sound, but even with a less distracting sound, this doesn't need to be so intrusive. Change-Id: Idee92b44cff2473a3686a2f2d95c6f5e4e91c2f8
-
If an app is old, users should already know that, and there's usually no point in warning them about it because they would already be using a newer version if one existed. Sometimes, using an old app is necessary for one reason or another, so remove this annoyance and let the user use their old app in peace. Change-Id: I1a3021f0f9bec1ab6ff7641776391e1bd4c3cc49
-
The previous commit solves the issue that users can not swipe an app away from recent apps if it was exited with the back button. (see f59b8135 Fix: Recent Apps not closing) However, it still has a similar problem in the case of users press the clear all button. Because the method removeAllVisibleTasks() will remove the task record from recent tasks in an earlier stage, so removeTaskByIdLocked() can not get the task record from either task stacks or recent tasks and notifyTaskStackChanged() will not be invoked. Solution: Call notifyTaskStackChanged as well for the non-existent task Test: 1. Clear all apps from recent apps first and make sure the list is emptied 2. Open an app and exit with back button 3. Go to recent apps and press the clear all button 4. Open recent apps again and the app should be removed from the list Bug: https://issuetracker.google.com/issues/137386250 Change-Id: I7ffd36fe7760b9f087e26c768219d7e7a5f12807 Signed-off-by:
Arghya Chanda <arghyac35@gmail.com> Signed-off-by:
SagarMakhar <sagarmakhar@gmail.com> Signed-off-by:
Dmitrii <bankersenator@gmail.com> Signed-off-by:
spezi77 <spezi7713@gmx.net>
-
