[3.4.0.22] Voicecall-ui uses CPU on the background

Bug Reports
, ,
6

There used to be a problem with dismissed notifications eating CPU. Reason there was a QML Animation that kept running in the background or some such [1].

Now, /usr/share/voicecall-ui-jolla/calling/IncomingCallViewBase.qml has something like this:

 38
 39     enabled: active || !readyForStateChange
 40     swipeEnabled: active && readyForStateChange
 41     opacity: (incomingCallView.active || incomingCallControlFadeoutTimer.running) ? 1.0 : 0.0
 42     Behavior on opacity { FadeAnimator { duration: 200 } }
 43

which is a very similar “Design Pattern”, and Use Case, to the one from the mentioned problem.

I wonder if commenting out line 42, and maybe even binding a visible property to active can solve the OP issue?

Oh, and should someone look into this, there’s a couple more to look at, and possibly some opportunities to go from a FadeAnimation to a FadeAnimator as recommended in [2]

rpm -ql voicecall-ui-jolla | grep qml  | xargs grep Behavi -C 1

[1] Screenshot leads to lipstick high CPU and battery drain
[2] Silica Reference Documentation - Sailfish OS

5 Likes