- Jan 25, 2024
-
-
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
-
The QS panel explains how to add/remove tiles, however after 'SystemUI: Allow user to add/remove QS with one click' the description is wrong. Update the string to suggest both ways. Change-Id: I2912e9254f9ed14436119addc913fe9907dc7f4e
-
Change-Id: Ied86dcfb6179d936786273867a50610900f1c5e5
-
Change-Id: I8f7f88d6451371458632b7949ef74bedbeccbaf8
-
Emergency location is handled through emergencyCallCallback that calls reloadGpsProperties() which in turn runs toggleXtraDaemon() before and after the emergency call Change-Id: I96dd4504f597ed71693c04d9d1806de1c1b73c38
-
It can be toggled using the existing Assisted GPS setting to avoid user confusion. Change-Id: Ic4c551d1726eac540e47faf214a963ec2adbf7f3
-
* This way the user can choose to turn it off, and it'll never have been enabled * If they just keep it as the default (toggle will be on in SuW), then it'll be enabled, which is the default we want Change-Id: I878200a0351d0b0018a975e432602de2badc4eef
-
* The location toggle itself is already ignored during emergency calls. * Also ignore the AGPS toggle during that to not change behavior around emergency calls, we never want to affect those, because life is everything. Issue: calyxos#1490 Change-Id: Iab13be99ccd65e0fdabcb67a25d73944ef24556a
-
Except in case of emergency, do not include sensitive subscriber information in SUPL requests (A-GPS). Issue: calyxos#618 Co-Authored-By:
MSe1969 <mse1969@posteo.de> Co-Authored-By:
Michael Bestas <mkbestas@gmail.com> Change-Id: I9f372cfcf02d3b768bd5cf1de220eea1fe8c1dbb
-
Occasionally, a remote display change is not processed within the timeout period. One prominent example is when a device is not able to complete its rotation from landscape back to portrait in time after the display is turned off. When this happens, and the callback is called after the timeout instead, DisplayContent.sendNewConfiguration abandons its effort when it sees there are pending display changes, but this callback itself might be the pending display change, and it does not expect itself to be included as part of this decision. Remove all callbacks before calling the last one to prevent this. Test: Manual: Build and run with REMOTE_DISPLAY_CHANGE_TIMEOUT_MS = 50, or some other low value. Enter landscape mode, e.g. by playing a video. Turn off the screen. Wait 3 seconds. Turn the screen back on. The lock screen will appear as normal. Previously, the screen would remain black until a restart or `adb shell wm` change interaction. Issue: calyxos#1392 Change-Id: I53659d5580cdd70b4c7138dcca770b11f5397194
-
