Skip to content
Snippets Groups Projects
  1. May 13, 2024
    • Nick's avatar
      Revert "Controls in QS" · 9f13b931
      Nick authored and Dhina17's avatar Dhina17 committed
      This partially reverts commit ffb1601d.
      
      This revert does keep Controls in QS 100% intact, but it allows the
      power menu to have controls as well. You can even have both, if you
      want.
      
      2022/11/05 - nift4: port to T
      2023/01/20 - nift4: QPR rebase
      		    trick for future rebases: for i in packages/SystemUI/res/values-*/strings.xml; do git show de1606e3:$i | grep quick_controls_subtitle && sed -i "s#</resources>#$(git show de1606e3:$i | grep quick_controls_subtitle)\n</resources>#g" $i; done
      2024/04/30 - ikeramat: port to u-qpr2
      
      Change-Id: I384b9fe5ed0422a5ec2abcedaf624252f72e19fd
      9f13b931
    • Nick's avatar
      Revert "Remove "Device Controls" from Settings" · 0383dbd6
      Nick authored and Dhina17's avatar Dhina17 committed
      This reverts commit 73702413.
      
      Change-Id: Idc55a0515983652fff1f68cd6503f46c607591cd
      0383dbd6
    • Michael W's avatar
      EasterEgg: Fix some warnings · dd910f72
      Michael W authored and Dhina17's avatar Dhina17 committed
      
      * Replace deprecated methods with the ones the android doc recommends
        as a replacement
      
      Change-Id: I1be5ba74da6f9a8e68bed4a0478675f90c9c28c6
      Signed-off-by: default avatarJoey Huab <joey@evolution-x.org>
      dd910f72
    • PainKiller3's avatar
      neko/Cat: Mark FLAG_IMMUTABLE PendingIntent with FLAG_MUTABLE · 88e552c4
      PainKiller3 authored and Dhina17's avatar Dhina17 committed
      
      * Fixes device control crash when interacting with cat control
      
      stacktrace: java.lang.RuntimeException: java.lang.IllegalArgumentException: 0|com.android.egg|1|com.android.egg.neko:allcats|10100 Not posted. PendingIntents attached to bubbles must be mutable
      	at android.app.job.JobServiceEngine$JobHandler.handleMessage(JobServiceEngine.java:109)
      	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.app.ActivityThread.main(ActivityThread.java:7837)
      	at java.lang.reflect.Method.invoke(Native Method)
      	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
      	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1003)
      
      Change-Id: I1e755ce8a38cfefb1474bbfefd307767a436e9d0
      Signed-off-by: default avatarPainKiller3 <ninadpatil100@gmail.com>
      88e552c4
    • Nick's avatar
      EasterEgg: allow using toy without unlocking · d87813a7
      Nick authored and Dhina17's avatar Dhina17 committed
      * useful to test proper operation of home controls modifications
      * easier than buying an smart home :)
      
      Change-Id: I7fb23089611be6d50f252e2d8f6c1d1bba202cb6
      d87813a7
  2. May 09, 2024
  3. Apr 27, 2024
  4. Apr 23, 2024
    • danielml's avatar
      VolumeDialogImpl: Handle cases where media controller is not available · 61c0115f
      danielml authored and Dhina17's avatar Dhina17 committed
      
      As of QPR2, we can't crate a media output dialog with empty package
      name unless the use_media_router2_for_info_media_manager flag is
      enabled.
      
      When the flag is enabled, we can always show the dialog by passing
      the actual package name, or null if the media controller is not
      available.
      
      If the flag is disabled, we can only show the dialog if the media
      controller is available.
      
      Change-Id: Ic8d08905bf55be91b547708b316ef7c96c81c492
      Signed-off-by: default avatardanielml <daniel@danielml.dev>
      61c0115f
  5. Apr 20, 2024
    • Nick's avatar
      SystemUI: Enable fading squiggle animation of qs media player · cec5b727
      Nick authored and Dhina17's avatar Dhina17 committed
      - fixes the line having different curves between played and unplayed section
      - before https://imgur.com/a/vn4smvb
      - after https://imgur.com/a/7rL4jV6
      
      Change-Id: I2d2522c66341662eff74eb7d3686be7aa6e7ac5c
      cec5b727
    • Dhina17's avatar
      SystemUI: Add settings for pulse light face down [2/3] · 344ab6fd
      Dhina17 authored and Dhina17's avatar Dhina17 committed
      Change-Id: I185d828abe000bcf9d4ce3a0b79b35c7726f9d69
      344ab6fd
    • Nick's avatar
      wm: hacky fix for system_server crash · 8c0b6863
      Nick authored and Mohammad Hasan Keramat J's avatar Mohammad Hasan Keramat J committed
      When opening pre-Nougat app that did not specify resizable attribute
      (pre Nougat era) and also is forced to portrait orientation in
      freeform and then resizing its window, system_server will crash due to
      invalid resize. To avoid whole device going down, we just catch the
      crash - app will stop working (window will be empty), BUT this is a much
      better thing to have than whole device crashing. This fix is even more
      needed because since Android 13, Google saves freeform bounds, which
      means when you reopen the unresizable app, it will instantly crash
      system_server again and you cannot ever again use this app in freeform
      without factory reset.
      
      The proper fix is to enable force resizable in developer settings, or
      asking the app devs to fix it (by making the app resizable). Further
      Framework-side fixes for this should be done by AOSP.
      
      Change-Id: I40d48c0caa9c376160f427d27260bd6bd5f66978
      8c0b6863
    • Dhina17's avatar
      WindowDecor: Pass correct displayId for back key event · 494a2250
      Dhina17 authored and Mohammad Hasan Keramat J's avatar Mohammad Hasan Keramat J committed
      TaskOperations object is being created with default display context
      so it will provide the default display id only.
      It causes that back button is not working on external displays.
      
      Change-Id: Ia4772e898dda20fb16ae85f2b2652a17924e9a7c
      494a2250
    • Dhina17's avatar
      WindowDecor: Always show caption bar in external displays · a301b810
      Dhina17 authored and Mohammad Hasan Keramat J's avatar Mohammad Hasan Keramat J committed
      In desktop mode, status bar won't be shown there.
      so we don't have to bother about caption bar visibility
      based on status bar (immersive mode) there.
      
      Change-Id: I418c44cec81a7f939a617adfc22044c3aa6cf4b2
      a301b810
    • Nick's avatar
      wm: do not show keyguard windows when mirroring due to dream · becfe1bd
      Nick authored and Mohammad Hasan Keramat J's avatar Mohammad Hasan Keramat J committed
      Also process default display first, because it needs to be first for
      logic to work. Fixes multi display dreaming.
      
      Change-Id: Ic2f9f48f21099de43d1067100c84f1f266175e8a
      becfe1bd
    • Nick's avatar
      SystemUI: fix transparent navigation bar keys in secondary display · 4d528635
      Nick authored and Mohammad Hasan Keramat J's avatar Mohammad Hasan Keramat J committed
      Huge thanks to luka177 for investigation
      
      What happens here is simple: mContext has Theme.SystemUI set, for
      secondary displays, it uses createDisplayContext() which unsets Theme
      because it's not a UI context. If we manually set theme again, resources
      start resolving again and navigation bar keys are no longer transparent.
      
      Dhina17: Ported to 14 QPR2
      
      Change-Id: Ib8c9212ac0facda8e0f4eeac2d4f839748178cc9
      4d528635
    • Nick's avatar
      Allow disabling pointer acceleration · 1c4d3be8
      Nick authored and Mohammad Hasan Keramat J's avatar Mohammad Hasan Keramat J committed
      Dhina17: Ported to 14
      
      Change-Id: I8e78ad6fa8b5361104af533e70a9c7e55a609611
      1c4d3be8
    • Nick's avatar
      WindowManager: finally proper desktop mode handling · 57a49676
      Nick authored and Mohammad Hasan Keramat J's avatar Mohammad Hasan Keramat J committed
      * The previous approach turned out to break Miracast screen mirroring,
        because of the windowing mode.
      * Instead of hardcoding desktop, use FLAG_SHOULD_SHOW_SYSTEM_DECORATIONS
        to detect our custom display, as it's impossible for that flag to be
        set on a non-default display on AOSP.
      * Make InputManagerCallback check desktop mode per-display, to match
        new behaviour.
      
      Change-Id: I4a701a2cb219e49d3f89aac35720a3ea5e37ec52
      57a49676
  6. Apr 18, 2024
  7. Apr 10, 2024
  8. Apr 09, 2024
Loading