Skip to content
Snippets Groups Projects
Select Git revision
  • test
  • fifteen-qpr0-new
  • fifteen default
3 results
Search by author
  • Any Author
  • Farzin Kazemzadeh Farzin Kazemzadeh itisFarzin
1 author
  1. Apr 09, 2024
  3. Apr 07, 2024
    • Dhina17's avatar
      Merge tag 'android-14.0.0_r31' into fourteen · 5eb040fc
      Dhina17 authored 
      Android 14.0.0 Release 31 (AP1A.240405.002.A1)

* tag 'android-14.0.0_r31' of https://android.googlesource.com/platform/frameworks/base:
  Gate SideFpsOverlayViewBinder and DeviceEntrySideFpsOverlayInteractor on device having SFPS
  Return correct result
  Fix security vulnerability that creates user with no restrictions when accountOptions are too long.
  isUserInLockDown can be true when there are other strong auth requirements
  Added limitations for attributions to handle invalid cases
  Stop marking apps as privileged if they are not signed properly.
  Don't store invalid pkgs when migrating filters

Change-Id: I3faf5c2a0cff4fb2ac5693d7658d63b885e4d6ab
      5eb040fc
  5. Apr 05, 2024
  7. Apr 03, 2024
    • Adithya R's avatar
      SystemUI: Add app rows to volume dialog · 3def99de
      Adithya R authored and Dhina17's avatar Dhina17 committed 
      Expand app rows instead of opening a settings panel.
Uses the per-app volume API.

Partially inspired by the patch from Android 11
"SystemUI: Add app volume row to volume dialog"
by cjybyjk <cjybyjk@zjnu.edu.cn>

Change-Id: I3728dfc4f39a06b96abfd571abb8858426e70f45
      3def99de
    • Arian's avatar
      SystemUI: VolumeDialog: Change bg tint for inactive rows · df6d9ea2
      Arian authored and Dhina17's avatar Dhina17 committed 
      The secondary accent in light mode does not have a good contrast
to the previously white icon.

Previously: https://imgur.com/a/XHpDHDJ
Now: https://imgur.com/a/QCk3QwC



Change-Id: Ib61ad4803e0e3c6cc9163408137c7a16742922b6
Signed-off-by: default avatarMohammad Hasan Keramat J <ikeramat@protonmail.com>
      df6d9ea2
    • Dhina17's avatar
      services: Workaround for our face unlock initialization [1/2] · 3dc0f968
      Dhina17 authored 
      AuthService registers the authenticators only once and
then onAllAuthenticatorsRegistered() callbacks are invoked.
The callbacks are removed as soon as it invoked.

Our LMO face unlock authenticator isn't being registered via AuthService.
When we register it, the onAllAuthenticatorsRegistered() callbacks aren't available
at that time so our face unlock isn't being initialized properly
and end up with bugs like "Face unlock isn't working after reboot".

As a workaround, we don't invoke callbacks if it's first time (from AuthService).
Instead we register our face unlock here on first time to make sure
callbacks are being called only after our face unlock authenticator registration.

If properties aren't empty, it's from hardware face sensor.
so allow to invoke callbacks regardless of the first time.

Change-Id: I26238a35f09d9cb398355d9467d44cd24b0e2525
      3dc0f968
  9. Apr 02, 2024
    • Tim Schumacher's avatar
      SystemUI: Enable NFC tile · 0249353d
      Tim Schumacher authored and Mohammad Hasan Keramat J's avatar Mohammad Hasan Keramat J committed 
      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
      0249353d
  11. Mar 31, 2024
  13. Mar 30, 2024