Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 725143eb authored by Juan Sebastian Martinez's avatar Juan Sebastian Martinez
Browse files

Distinct event logs for clicks on the QSLongPressEffect 

The logs for when a tile is clicked are now different to indicate which
path led to the click: A click from a backwards long-press animation, or
a click from the View's onClickListener.

Test: presubmit
Flag: com.android.systemui.quick_settings_visual_haptics_longpress
Bug: 229856884
Change-Id: Ib545a1558eaaab1098004d2ea40ebb4c4f636d64
parent 066cfe96

packages/SystemUI/src/com/android/systemui/haptics/qs/QSLongPressEffect.kt

+6 −2
Original line number Diff line number Diff line
@@ -178,7 +178,11 @@ constructor( 
            State.RUNNING_BACKWARDS_FROM_UP -> {

                callback?.onEffectFinishedReversing()

                setState(getStateForClick())

                logEvent(qsTile?.tileSpec, state, "click action triggered")

                logEvent(

                    qsTile?.tileSpec,

                    state,

                    "click action triggered from handleAnimationComplete",

                )

                qsTile?.click(expandable)

            }

            State.RUNNING_BACKWARDS_FROM_CANCEL -> {
@@ -206,7 +210,7 @@ constructor( 
        if (keyguardStateController.isPrimaryBouncerShowing || !isStateClickable) return false



        setState(getStateForClick())

        logEvent(qsTile?.tileSpec, state, "click action triggered")

        logEvent(qsTile?.tileSpec, state, "click action triggered from onTileClick")

        qsTile?.click(expandable)

        return true

    }