+2
−1
Loading
Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more
In the new implementation of the KeyguardBottomAreaView, when the user locks their device, moving directly from the unlocked state into AOD/doze, we erroneously show the home controls quick affordance button for a moment/frame before hiding it. This was caused by our reliance on isDozing and dozeAmount where, what we should really look at is isDozing and isKeyguardShowing - like the CL is doing. The approach taken here is actually refactored out of the wallet quick affordance config implementation and applied generically to all quick affordance config implementation at the use-case layer. The reason I thought this could work is because I was only seeing the home controls button exhibit this bug while the wallet one was not. I didn't test the QR Code scanner one, but I bet it would have worked just like the home controls one. Bug: 240969525 Fix: 240969525 Test: locking from the unlocked home-screen proves that the fix works because it no longer flickers the quick affordance view over the AOD screen. Also, unit tests were added/modified to capture this. Change-Id: Id2917989991802825d1024d5a0d9161d4452265f