I'd like to request a security feature that would help users identify who is trying to unlock their phone.
Proposal:
When an incorrect unlock password/PIN/pattern is entered more than twice, the phone automatically takes a photo (front camera) of the person attempting to unlock the device and sends the image to the user’s registered email address (or a user-defined email). Optionally include a timestamp and the device name/model in the email.
Capture an image with the front camera (or both cameras if user enables back camera).
Save the photo locally and send it as an attachment to the user’s Samsung account email or a user-provided email.
Include metadata: date/time, failed-attempt count, and optionally approximate location (if user enabled).
3. All steps run in a secure, permissioned context so the camera and email send do not expose the device to third-party apps.
Why this helps:
Deters unauthorized access and helps identify the person trying to access the device.
Useful in theft or targeted harassment situations.
Builds on existing Routines capability so Samsung’s automation engine can securely handle the action.
Privacy & security considerations:
This must be opt-in (off by default) and require explicit permission to use the camera and to send email.
Images should never be uploaded to third-party servers without explicit consent; sending to the user’s registered Samsung account email or a user-configured email keeps control with the user.
Include an explanation in Settings about how images are used and retained; allow auto-delete after a user-defined period.
Prevent abuse by limiting how often images can be captured (e.g., cooldown period after capture).
Configurable options for users:
Enable/disable feature (opt-in only)
Failed-attempt threshold (2–10)
Send to Samsung account email OR custom email address
Include timestamp and location toggle
Front camera only / both cameras
Retention period for captured images
Request:
Please consider adding this as a Routine-capable security action or an integrated Security setting in a future One UI update. I believe many users would appreciate this extra layer of protection. Happy to provide more implementation ideas or testing feedback.
If other members like this idea, please upvote or contribute suggestions — for example, safe retention defaults or additional triggers (SIM change, unauthorized boot, etc.).
