Skip to content

bug: [FEATURE PROPOSAL] Direct unlock into Private Space using alternate credential #860

@omsn1528

Description

@omsn1528

Issue type

User interface

Device

generic (feature proposal)

crDroid version

crDroid 11

Exact version / Build date

16.0

Bug description

This is not a bug report.

Feature proposal:

What if unlocking the phone could directly open a specific space?

Idea:
Allow users to unlock directly into Private Space by entering a different
credential at the lockscreen, instead of unlocking first and switching spaces manually.

Example:

  • PIN A → Main space
  • PIN B → Private Space

Important constraint:
To avoid ambiguity and security issues, both spaces must use the same lock type:

  • PIN → PIN
  • Pattern → Pattern
  • Password → Password

Benefits:

  • Faster access to Private Space
  • Cleaner privacy workflow (no visible space switching)
  • Improved daily usability

This feature would be optional and opt-in.
The intent is to discuss feasibility and security implications before any implementation.

Steps to reproduce

N/A – Feature proposal, no steps to reproduce.

Relevant log (logcat/build log)

N/A – Feature proposal, no logs applicable.

Screenshots or videos

No response

Solution

Potential framework-level enhancement to Keyguard and user/profile selection logic.
Details provided in description.

Additional context

This proposal is independent of device-specific behavior and intended for discussion
before any implementation.

Acknowledgements

  • I've checked device is officially supported and that no support is provided for unofficial devices (for device specific reports and not source related).
  • I'm running latest version available on crdroid.net for this device and that the device is still maintainer supported (not flagged unsupported on download page)
  • I have searched the existing issues and this is a new and no duplicate or related to another open issue.
  • I have written a short but informative title.
  • I filled out all of the requested information in this issue properly and understand that not doing so will automatically result in closing of ticket.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingneeds-triagelabled for new issues in order to confirm viewed and directed properly

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions