- May 24, 2022
-
-
This is a squash of the following commits, forward-ported to Oreo and adapted to the Lineage SDK: Author: Danesh M <daneshm90@gmail.com> Date: Wed Jun 25 21:31:49 2014 -0700 ProximityWake : Add support for checking proximity when waking device Change-Id: Ia5ff446d88435773acccc7467e66009000dc20cb Author: Schubi <schubi@erlangen.ccc.de> Date: Tue Jul 29 02:10:16 2014 +0200 Be sure to shutdown the proximity sensor after display wake This fixes: http://review.cyanogenmod.org/#/c/66657/ Change-Id: I1768f13cb48c3e056d0e137642690fc3d650c4ab Author: Danesh M <daneshm90@gmail.com> Date: Mon Aug 4 20:18:18 2014 -0700 PowerManager : Make proximity check opt-in Change-Id: I7cf64a82530da2e655018e43683ba7a5584d54f8 Author: Danesh M <daneshm90@gmail.com> Date: Fri Jul 25 19:02:26 2014 -0700 Framework : Fix proximity wakeup reference Change-Id: Ia40ca6fbf6e37fbb3996f2384f725c30b88c2131 Author: dankoman <dankoman30@gmail.com> Date: Thu Feb 5 15:12:13 2015 +0100 [1/2] Frameworks: let InCallUI handle proximity sensor for incoming calls Fixes "while 'prevent accidental wake-up' is on, proximity sensor doesn't control screen state on incoming call. Must manually turn on screen to see who's calling." Change-Id: I738b3bbd328992c8a8010a0c8d9aa1e444cfa9f9 Author: Steve Kondik <steve@cyngn.com> Date: Thu May 21 13:10:54 2015 -0700 power: Fix locking for wakeup proximity check * Often I'm noticing high power consumption due to the proximity sensor never turning off. Add synchronization around this code to ensure ordering. Change-Id: I8ccf3152166cd896e0ce2551c01b8ac8f501d782 Author: Scott Mertz <scott@cyngn.com> Date: Fri Aug 21 13:47:51 2015 -0700 add config for proximity check on screen on default value Change-Id: I7e6ae08e23ee147a37986aa6aa9b3176b301a09e Author: Danesh M <daneshm90@gmail.com> Date: Mon Aug 4 18:09:06 2014 -0700 Services : Ensure proximity check is taken into consideration Only do the proximity check if explicitly being asked to do so. This is a patch that was never ported from cm-11.0 : 2293e60c7de011782e59486605c04b9f67a1e24f issue-id: CYNGNOS-1223 Change-Id: Id1be619e638de6a45252d8390eab6e38bd5de5a7 Author: Erica Chang <echang@cyngn.com> Date: Tue Jun 9 15:01:12 2015 -0700 services: button brightness should check proximity Change-Id: I10a72fa6d8b520e86cfef3d7ded489fd7fa936d2 Author: Steve Kondik <steve@cyngn.com> Date: Mon Oct 26 03:07:26 2015 -0700 powermanager: Initialize SensorManager in systemReady() * Service startup ordering is different on M and the sensor service is not ready during construction of the PowerManager. This was causing a hang on boot. Move it to systemReady instead. Change-Id: I9e0293484e1aaaf9f82f9c75680bec558607c54d Author: Adnan Begovic <adnan@cyngn.com> Date: Mon Nov 9 17:59:13 2015 -0800 fw: Move proximitycheck to CMSettings. Change-Id: Ie80166c990363d3846925b189a1f7001a7fd56f8 Author: Pat Erley <perley@cyngn.com> Date: Thu Dec 10 17:00:53 2015 -0800 PowerManagerService: Log when proximity blocks wake There is currently no indication when the proximity sensor is allowed to prevent the system from waking up. This can make it hard to debug weird failed wakes. Add a log to facilitate debugging wakup problems. Change-Id: I7df34e13b1268a4e7211fb06ccd88f2053c0af0a Author: Christopher R. Palmer <crpalmer@gmail.com> Date: Fri Feb 19 11:53:15 2016 -0500 base: Fix proximity check on power key To test, enable "Settings >> Display >> Prevent accidental wakeup", hold your hand over the proximity sensor and turn your phone on. Prior to this change, it will wake up the phone and after the change it will not. Change-Id: Ied300108cebb31dedf228e85510abebb3e8a4152 Author: vm03 <vasy@vasy.ru> Date: Sat Feb 27 17:16:02 2016 +0300 base: Fix proximity check on non power key To test, enable "Settings >> Display >> Prevent accidental wake-up" and "Settings >> Buttons >> Home button Wake up device", hold your hand over the proximity sensor and turn your phone on by home key. Prior to this change, it will wake up the phone and after the change it will not. Change-Id: Ifd14ff2ad9cd2cbc64209b9cf19e3c0ee0b6f40f Change-Id: Ia5ff446d88435773acccc7467e66009000dc20cb Signed-off-by:Jason Edson <jaysonedson@gmail.com>
-
Author: Roman Birg <roman@cyngn.com> Date: Thu Feb 4 16:28:00 2016 -0800 framework: move device key handler logic, fix gesture camera launch In order to make device camera gestures behave the same way as launching the camera by double tapping the power button, route DeviceKeyHandler logic through the GestureLauncherService. A callback is used in order to avoid publishing the GestureLauncherService into the System service registry, because the KeyHandler code cannot directly access services local to the system process. OPO-427 Change-Id: I2a8860b278f65ccf31bfee151513d8a23ab746c5 Signed-off-by:Roman Birg <roman@cyngn.com> Author: Roman Birg <roman@cyngn.com> Date: Sat Feb 13 09:08:21 2016 -0800 KeyHandler: don't break old interfaces Causing bootloops on devices, don't break old interfaces in the framework. OPO-427 Change-Id: I49473b057bc4ed4710e9092c76e41c6a8134d2de Signed-off-by:
-
Change-Id: Ibc3914370828e04c713ce1638bd4814fb893a3ee Signed-off-by:Mohammad Hasan Keramat J <ikeramat@protonmail.com>
-
Doing so allows us to keep track of user changes and restore preferences. This commit is squash of the following commits from CM 13.0: 7348be747940afe7c3ec6a2b133b5473bc18573a Move high touch sensitivity and hovering to InputService f9a9d50491dc583ea568a4f12e57a2f97b9baacb InputMethodManager : Move registration to systemReady Since lineage-17.1 services/core/java/com/android/server/InputMethodManagerService.java is moved to services/core/java/com/android/server/inputmethod/InputMethodManagerService.java Change-Id: I5a6af73129acefa6530ceb3f73cc4cd83a19a676 Ticket-Id: CYNGNOS-1166
-
@jhenrique09 edits: Adapt to AOSP Change-Id: I789814d780b06b146c1f9ab62293f4d6ca287208 Signed-off-by: -
Change-Id: Ifc346b7086bb8751d6440bf078ad2471eba217f2 Signed-off-by: -
All credits to LineageOS and related authors on: https://github.com/LineageOS/android_lineage-sdk Ported to AOSP from lineage-sdk by @SKULSHADY Change-Id: Iac8dba8b2d509fe1fa707efc4da9c661f1321d9d Signed-off-by:
-
All credits to LineageOS and related authors on: https://github.com/LineageOS/android_lineage-sdk Signed-off-by:
Henrique Silva <jhenrique09.mcz@hotmail.com> Change-Id: Ief90ce8c20115d6a1c17c84a9874af6246dc1dcd Signed-off-by:
-
This is a squash of the following commits: Author: beanstown106 <nbenis106@gmail.com> Date: Fri Oct 23 21:07:35 2015 -0400 SystemUI: Allow to enable Lockscreen Media Art Change-Id: Id93e115649df5d6dc680101a8c852644b217c28a Author: Ezio Lacandia Bijelkic <brabus84@gmail.com> Date: Fri Nov 20 00:41:04 2020 +0200 SystemUI: Hide lockscreen media art if media is not playing it's annoying to get the artwork even if the notification gets swiped out and media is paused, because the media session is still alive Change-Id: Ie65932127e47c463ef9a8b763298fc4dae20f8ae Change-Id: Idd3033b52b4aa1cf07eb694ea0c9c1c934248f7c -
Includes the fix from commit 31355d7. Change-Id: I0f70f13ae03dc1d15c58e9ccd7eebb50ba2de7cc
-
Author: Roman Birg <roman@cyngn.com> Date: Sun Nov 23 06:54:06 2014 -0800 SystemUI: double tap to sleep improvements * Make it more reliable * Add it to keyguard * Add a content observer to not always query Settings.System on every touch event Change-Id: I292c4d9d9f810843590b7a9ec6e15b99ac44009d Signed-off-by:Pranav Vashi <neobuddy89@gmail.com> Author: dianlujitao <dianlujitao@lineageos.org> Date: Thu Feb 27 12:57:07 2020 +0800 SystemUI: Don't sleep on double tap below status bar Change-Id: Ic64c29eae63e96f34dc37cda355401b7e2cd2d39 [Pig]: Forward port to R [bgcngm]: Forward port to S Change-Id: I0281d23cb3ad5f8f2b67d08ae431e8a962a60927
-
Logic is currently set to use 1/3 of right hand side of the statusbar to trigger a quick settings quick pull down, quickly. Change-Id: I3f536496f724f07d2419a5b2db5fa8f8261609e7 Signed-off-by:
-
Author: Thecrazyskull <anaskarbila@gmail.com> Date: Tue Jan 17 10:56:39 2017 -0600 SystemUI: Enable NFC tile Change-Id: Ib21f927d336fcb5e460552786828b79551b235fa Author: inthewaves <inthewaves@pm.me> Date: Sun Sep 20 14:59:10 2020 -0700 have NfcTile get an NfcAdapter directly This changes the NfcTile to not be dependent on an NfcManager giving the NfcTile an NfcAdapter. The problem with NfcTile is that the NfcService doesn't start until the device is unlocked after a reboot, but NfcTile can be created and have its state updated before the device is unlocked. The state of NfcTile depends on an NfcAdapter. The tile gets an NfcAdapter from a call to NfcAdapter#getDefaultAdapter, which gets an adapter from an NfcManager via Context#getSystemService, and NfcManager tries to get an adapter in its constructor via NfcAdapter#getNfcAdapter. If this is done before unlock, NfcService isn't started, so the constructor of NfcManager fails to get an adapter, opting to just store null. This means that the NfcManager that's _cached_ by the NfcTile's application context holds a null NfcAdapter, so subsequent calls in NfcTile to get the NfcAdapter will keep returning null. We can just have NfcTile get the NfcAdapter directly via NfcAdapter#getNfcAdapter instead of relying on an NfcManager to call the same method for us to get its default adapter. We just have to make sure we use the application context for NfcAdapter#getNfcAdapter, as per the doc comments for getNfcAdapter. This means that there's no longer an NfcManager associated with the NfcTile's application context. It doesn't look like NfcManager does anything special with the NfcAdapter anyway. It seems to just be some middle man for NfcAdapters: * The NfcAdapter field in NfcManager is final, and it doesn't do anything else with it besides have a getter method for returning it. The NfcManager seems to be a way to force third-party apps that want to get an NfcAdapter to use the application context. * NfcAdapter#getNfcAdapter manages the caching of NfcAdapters by application context in a static HashMap. NfcManager doesn't manage caching; it just calls NfcAdapter#getNfcAdapter. Change-Id: Ifafc666568a001a60baf7c8c16782dca1ee4d011 Author: Michael W <baddaemon87@gmail.com> Date: Fri Jan 15 00:03:02 2021 +0100 NfcTile: Don't create an error when editing tiles Repro: * Make sure no NfcTile is in your expanded QS (not tested what happens if it's there) * Hit the Edit-button: Error in handleSetListeningInternal java.lang.IllegalArgumentException: Receiver not registered: com.android.systemui.qs.tiles.NfcTile$1@7c00b87 at android.app.LoadedApk.forgetReceiverDispatcher(LoadedApk.java:1434) at android.app.ContextImpl.unregisterReceiver(ContextImpl.java:1543) at android.content.ContextWrapper.unregisterReceiver(ContextWrapper.java:664) at com.android.systemui.qs.tiles.NfcTile.handleSetListening(NfcTile.java:64) at com.android.systemui.qs.tileimpl.QSTileImpl.handleSetListeningInternal(QSTileImpl.java:371) at com.android.systemui.qs.tileimpl.QSTileImpl.access$700(QSTileImpl.java:80) at com.android.systemui.qs.tileimpl.QSTileImpl$H.handleMessage(QSTileImpl.java:496) at android.os.Handler.dispatchMessage(Handler.java:107) at android.os.Looper.loop(Looper.java:214) at android.os.HandlerThread.run(HandlerThread.java:67) * Only register or unregister the receiver if we actually need to change registered-state * Same code is in AirPlaneModeToggle.java, presumably was also added to prevent unnecessary registering/unregistering Change-Id: I6cd8f9bffccb68596b736cc0a3a38e9c12b9c489 Change-Id: Ia06b923ee15e91a9c84a806d4c69755478df2063 -
since google decided not to kill eyes of people with dark qs always but forgot to change the the color in drawable of Brightnessbar elements. it was white colored. before: https://imgur.com/OrW2p7d after: https://imgur.com/7DV844t if you are using gapps( with google overlays) then no need of this else needed Signed-off-by:
Harsh <harsh@project404.us> Change-Id: If789337a275f46de3615bd0d0158b172ac6dd8c9
-
Text in the QS status bar is medium in light mode and regular in dark mode. Fix the mismatch. Change-Id: Ic6e5dc547d4ded9d231f88f6cac3e1e9f8483d5e
-
This looks outdated, since most apps are edge-to-edge nowadays. Change-Id: I8c54e61e618a9b5bed1a59753ce76e8fbd69fae2
-
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
-
Handle the status that there is an existing p2p-group already formed when starting to connect to wifi display. There are two cases: - if the desired device is the same with the already connected device, start to listen to the remote display. - if the desired device is different, disconnect the old one and reconnect the new one. CRs-Fixed: 2293770 Change-Id: Icacc59d38fb81d6a6f812043c2798760f82bc606
-
1. wifidisplay: Use ExtendedRemoteDisplay to launch Wifi Display. - RemoteDisplay class is used to launch WiFi Display implementation in the Android framework with a discovered peer. There is a need to support proprietary implementation of wifi display instead of the framework implementation. - To enable this support, ExtendedRemoteDisplay is added, which launches the proprietary solution. ExtendedRemoteDisplay object is created if the class is available in the package. If the class is not available the default implementation will be used by creating RemoteDisplay. Change-Id: I2e2a5e552bc86888848c0402bafd873620b05c21 2. wifidisplay: Modify WifiDisplayController Spawn RTSP server before P2P connection --In order to be sanguine that the RTSP server has been spawned on source, invoke listen() before P2P connection. --Add a debug property to enable verbose logging in WifiDisplayController Block teardown to avoid severing P2P group --Since WFD dispose is asysnchronous, framework proceeds with teardown and dissolves P2P group before WFD stack is able to complete message exchange for teardown. --Prevent framework from doing so and allow it to proceed only once WFD stack indicates it's dependence on network is over. Add null check guards in WifiDisplayController --The WifiP2PGroup delivered in the onGroupInfoAvailable() callback is not guaranteed to be non-null and hence needs to be validated. --The same applies to the WFDDevice that is retrieved using info.getOwner() CRs-Fixed: 1041702 Change-Id: Ie0e23ba42c1afe42662943cd864ab3077a156e0a
-
Bug: 209297031 Test: Test: atest FrameworksCoreTests:BatteryUsageStatsTest FrameworksCoreTests:BatteryUsageStatsProviderTest Merged-In: I369d863b6f6fd488030aa031cc465bef6ce99ab8 Change-Id: Ifc70a49b731b5510e7bcd049e0c12d9ac7f68f44
-
BatteryUsageStats is created under a BatteryStatsImpl lock. One of the elements of BatteryUsageStats is the battery history buffer Parcel. Once the BatteryUsageStats object is created, the BatteryStatsImpl lock is released and the history buffer parcel continues to be appended by BatteryStatsImpl. The Parcel may even be reset altogether if the battery stats session is reset. The BatteryUsageStats object is parceled during the getBatteryUsageStats binder call. Any modification of the history buffer concurrent with parceling causes a crash. Bug: 194256984 Test: atest FrameworksCoreTests:BatteryUsageStatsTest FrameworksCoreTests:BatteryUsageStatsProviderTest Change-Id: I262c4608cd02943f926e8daaf3e782c6fe6eaee7 Merged-In: Ifb03a32275dfbea172cd28309a42349d6dd4bcd5
-
During disconnecting both a2dp output and input device, same device is passed to handler but with different profile, to avoid removing existing event in the handler, check the a2dp profile as well. CRs-Fixed: 2943846 Change-Id: I9d0eced33d57c46d6e49a74e958c488f3a07249c
-
Observed disconnect of A2DP is coming in and scheduled with delay of 500msecs as non supress intent and around same time connect is coming where it founds device is already connected and triggers device config change intent. And after timeout,scheduled disconnect event gets triggered and removes A2DP device causing music to route to speaker Fix is to remove scheduled events when recent event comes CRs-Fixed: 2974286 Change-Id: I625226269474a4f4b122275bcaa5dddc19cfeaad
-
CRs-Fixed: 3043842 Change-Id: I70f3c109140bf9634e2d0a293a323cae3c9cd476
-
- Add Profile entry for MCP Service CRs-Fixed: 3033146 Change-Id: I7f89b6ab2c84f8681d953c0f5c65750946962fc3
-
This change contains - API's to do filtered scan based on Group AD Type. - Extract Group identifier data from ScanRecord. CRs-Fixed: 2826578 Change-Id: I75982a1acf982c03234d9e1084aee287d3d3623d
-
Override the constructor to send addresstype as part of Scan results. These addresstype information will be sent only to previleged applications CRs-fixed: 2834981 Change-Id: I47acaf1fcc1cfdd35aa9fe2b913f588cfc51cc70
-
Define Headset state when SCO audio is disconnecting. CRs-Fixed: 2634664 Change-Id: Ie1200d4e9ce0b38ba71bd43c76e50720cb1ddc3f
-
- Add APIs to dynamically switch between BREDR and LE profiles for call and media Audio - These APIs are introduced as SDK APIs which can be called from external apps like Settings Change-Id: Iafb514fcf833ccd77ba300f60277ac30eae89943 CRs-Fixed: 3072404
-
- This adds attribution source as a parameter to Value added APIS, matching aidl changes also made in this topic. - This is now required to allow the app ops for the new bluetooth permissions (BLUETOOTH_CONNECT, BLUETOOTH_ADVERTISE, and BLUETOOTH_SCAN) to be noted. - Update Bluetooth API annotations. - Add missing permission checkes for binder APIS. Change-Id: I20cbc69fbfe86b510dfc6d6335de31072191b491 CRs-Fixed: 3046326
-
This change contains below implementations: - Bluetooth VCP profile proxy object implementation. - VcpProfile implementation in SettingsLib - VCP Refactor changes in framework and settingsLib CRs-fixed: 2857030 Change-Id: If7c607d51c92e4215a1bef58dab77a7479131a31
-
Add system APIS to support Group UI Add AUDIO MCOD related flags Add new icon for Group supported Adv Audio device CRs-Fixed: 2832643 Change-Id: Iab3b23115fb7b9917faed3cbb30f32538824e7db
-
CRs-fixed: 2856233 Change-Id: I04ecf35e9f6d8e778b3e8f90e8f1ab0cd34eeb9b
-
Add BC profile entry and override constructor for CachedBluetoothDevice CRs-fixed: 2853618 Change-Id: I750139a482280ce3409989582ffad50aed20e081
-
Add broadcast profile to BluetoothProfile CRs-fixed: 2856233 Change-Id: I17a4eb21ea9cc74a28349a8e0883ed2249838f3c
-
To avoid any future CTS failures, need to align our QC codec enumeration with AOSP. On top of that enumeraion extaned to QVA codecs. CRs-Fixed: 2708798 Change-Id: Idc8dbcdc6454586031ce7431f52a2c031cfd1871
-
This reverts commit 6e7b6cffb26610a7335e8e9c6b6451bd03468630. CRs-Fixed: 2914887 Change-Id: Ic1cf1a81bba8f0f54a5dc404cfe5fec0bcc850cd
-
CRs-fixed: 2814447 Change-Id: Ic77e8ddbe57e415f7fd9c11943da50e4d86230d2
-
This adds attribution source as a parameter to Value added APIS. Update Bluetooth API annotations. CRs-Fixed: 3044065 Change-Id: Icf9c0242f928ce2f26f66350ddb3937fda35220d
-
- In BLE on use case, quiet mode status is not updated to Adapter service which results in not initiating auto connection of hfp & a2dp though quiet mode is disabled for next turn On. - Added new API to update quiet mode status in Adapter service. CRs-Fixed: 2337538 Change-Id: I49a604b7996024fd9fd498fb7cc6aafc208517a5
-
