{"push_id":909339532,"size":1,"distinct_size":1,"ref":"refs/heads/pac-5.1","head":"08ad3c254dd0aa1f7787bd0c0569f55b069e13d1","before":"a64b34ce6d455a8e7d7b26572aae9c35b309b0c1","commits":[{"sha":"08ad3c254dd0aa1f7787bd0c0569f55b069e13d1","author":{"email":"238a1843d81dd7fbe80b5c1b99515c4ba8c94d0d@cyngn.com","name":"Roman Birg"},"message":"SystemUI: fix \"directly show bouncer\" conflicting with smart unlock\n\nIf the user had \"directly show pattern view\" selected with a pattern\nunlock for instance, then the assumption is that the lock screen always\nopens to the pattern view, or the bouncer.\n\nIf smart lock is currently enabled and putting the keyguard in a\n'trusted' environment, e.g. not requiring security, then we shouldn't\ntry to show the bouncer, because there is none. Currently when smart\nlock is putting the keyguard in an insecure mode, it will basically\ndisable the lock screen if this option is selected. This is not the\ndesired result and we should still have a lock screen.\n\nOSS Ref: BACON-4449\nSigned-off-by: Roman Birg <roman@cyngn.com>\n\nChange-Id: Ie7a2326bf06e64c171e16fec5dde1179fe975450","distinct":true,"url":"https://api.github.com/repos/PAC-ROM/android_frameworks_base/commits/08ad3c254dd0aa1f7787bd0c0569f55b069e13d1"}]}