Samukelosfiso
Active Level 1
Options
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thursday in
Galaxy A
The Secure folder does not auto-lock when you leave the app on the UI 8.O. Which is a serious security concern.
7 Comments
CyberForge
Active Level 2
Options
- Mark as New
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thursday in
Galaxy A
I just lock my phone (screen turn off) and then unlock it to lock the secure folder after I am finished with it. More secure, actually. You can try installing an app lock inside the secure folder.😅
Samukelosfiso
Active Level 1
Options
- Mark as New
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thursday in
Galaxy A
Thanks, but having to use third party apps on your most secret stuff defeats the purpose.
Tumelo159
Active Level 7
Options
- Mark as New
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thursday in
Galaxy A
Samsung disabled that feature in One UI 8.
Samukelosfiso
Active Level 1
Options
- Mark as New
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thursday in
Galaxy A
Without that feature we are doomed.
Tumelo159
Active Level 7
Options
- Mark as New
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thursday in
Galaxy A
There is more information and a reason for the change.
I went through samsung news and they explained the change. In One UI 7, a security flaw allowed system components, and even third-party media pickers, to reveal the presence of apps and photos stored in the Secure Folder, even while encrypted.
So to make it more secure, there had to be changes.
Look at it like this:
In One UI 7, the way it was featured was what you preferred right, BUT it was not secure enough.
In One UI 8, it is not what you prefer, but it is secure now.✅️
I went through samsung news and they explained the change. In One UI 7, a security flaw allowed system components, and even third-party media pickers, to reveal the presence of apps and photos stored in the Secure Folder, even while encrypted.
So to make it more secure, there had to be changes.
Look at it like this:
In One UI 7, the way it was featured was what you preferred right, BUT it was not secure enough.
In One UI 8, it is not what you prefer, but it is secure now.✅️
Kendrick_Katong o
Active Level 9
Options
- Mark as New
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thursday in
Galaxy A
You are doomed we are not 🔥🔥
SherlockB221
Active Level 4
Options
- Mark as New
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thursday in
Galaxy A
Hi
You're absolutely right, and that’s a valid concern. 👇
On One UI 8.0 (Android 16), some users have noticed that Secure Folder doesn’t auto-lock immediately after leaving or minimizing the app — which it should do by default or according to the user’s set lock timer.
Here’s a breakdown of what’s likely happening and what you can do:
---
🔍 Possible Causes
1. New Behavior / Bug in One UI 8.0:
The update might have changed background app management or activity handling — Secure Folder may not register the “exit” event correctly, leaving it temporarily unlocked.
2. Lock Automatically Setting Reset:
After an update, Secure Folder sometimes resets “Auto-lock when app is closed” to a longer delay (like 10 minutes) or disables it entirely.
3. System Optimization Interference:
Device care or battery optimization might interfere with Secure Folder’s background locking mechanism.
---
✅ Fix / Workaround
Try the following steps:
1. Go to:
Settings → Biometrics and security → Secure Folder → Lock type
2. Tap “Auto lock Secure Folder”
3. Choose “Each time Secure Folder is closed”
4. Restart your phone to ensure the setting applies.
Also check:
Settings → Battery and device care → Battery → Background usage limits
→ Remove Secure Folder from “Sleeping apps.”
---
🚨 If It Still Doesn’t Lock
If you already set it to auto-lock on close and it stays open after exiting:
It’s most likely a bug introduced with One UI 8.0.
You can report it directly via Samsung Members → Get help → Error reports → Security → Secure Folder.
Include a screenshot or screen recording showing the issue.
Samsung takes Secure Folder bugs very seriously, so such reports usually trigger a quick patch in the next maintenance or hotfix update.
You're absolutely right, and that’s a valid concern. 👇
On One UI 8.0 (Android 16), some users have noticed that Secure Folder doesn’t auto-lock immediately after leaving or minimizing the app — which it should do by default or according to the user’s set lock timer.
Here’s a breakdown of what’s likely happening and what you can do:
---
🔍 Possible Causes
1. New Behavior / Bug in One UI 8.0:
The update might have changed background app management or activity handling — Secure Folder may not register the “exit” event correctly, leaving it temporarily unlocked.
2. Lock Automatically Setting Reset:
After an update, Secure Folder sometimes resets “Auto-lock when app is closed” to a longer delay (like 10 minutes) or disables it entirely.
3. System Optimization Interference:
Device care or battery optimization might interfere with Secure Folder’s background locking mechanism.
---
✅ Fix / Workaround
Try the following steps:
1. Go to:
Settings → Biometrics and security → Secure Folder → Lock type
2. Tap “Auto lock Secure Folder”
3. Choose “Each time Secure Folder is closed”
4. Restart your phone to ensure the setting applies.
Also check:
Settings → Battery and device care → Battery → Background usage limits
→ Remove Secure Folder from “Sleeping apps.”
---
🚨 If It Still Doesn’t Lock
If you already set it to auto-lock on close and it stays open after exiting:
It’s most likely a bug introduced with One UI 8.0.
You can report it directly via Samsung Members → Get help → Error reports → Security → Secure Folder.
Include a screenshot or screen recording showing the issue.
Samsung takes Secure Folder bugs very seriously, so such reports usually trigger a quick patch in the next maintenance or hotfix update.
