Skip to content

Navigation buttons stop working when "Disable lock screen" becomes active due to a system profile #118

@bo-hmpl

Description

@bo-hmpl

When you have a system profile with the lock screen mode set to Disable lock screen (like 'at home') AND this profile becomes active (manually or by a trigger) the "home" and "recent" buttons don't work anymore until another profile becomes active (or this Disable lock screen is manually disabled).

I found descriptions of this behaviour for earlier LOS versions like 19.1 (https://www.reddit.com/r/LineageOS/comments/11wh6d4/navigation_buttons_dont_work_when_screen_lock_is/) and even on a seven year old post (https://www.reddit.com/r/LineageOS/comments/7svouf/problem_with_system_profils_buttons_menu_and_task/). I also remember having this problem with LOS 17 on the same device.

The latter post shows up a fix for cm-14.1 which fixes sth called "Keyguard". Apart from the fact that this bug is still around (or again)... can this fix still be implemented?
Also, is this an inherent lineage problem or something that affects only this build or device?

I found the same file that would be patched in the frameworks base of LOS 21 (https://github.com/LineageOS/android_frameworks_base/blob/lineage-21.0/packages/SystemUI/src/com/android/systemui/keyguard/KeyguardViewMediator.java) but no way to apply this exact patch there.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions