Fix issue with disable flags being set for the wrong user
- The default status bar manager disable() calls use the binder's calling user (which is always the primary user), so when the bouncer is showing for a secondary user, the flags would be propagated to the non-running primary user. This CL switches to the specific user call to apply the flags to the current user. A separate token is Ok because we also don't want these particular disable calls to clobber disable calls from other parts of SysUI (they will be coalesced into one set of flags when sent so final state is the same) Bug: 264638487 Test: atest SystemUITests Test: Create secondary user, switch to 3 button and show the bouncer to verify the right buttons show then and after unlocking Change-Id: I26371352a2d7e327e499faf19535769ee72175e4
Loading
Please register or sign in to comment