Samsung Secure Folder vs Private Spaces

General
26

According to the article:

Samsung has no control over the behavior of the photo picker and Permission Controller and subsequently can’t hide Secure Folder apps from them.

Basically, the flaw is streamed from how Android implemented work profile, not because Samsung’s own shitty implementation.

Maybe, you could reduce your dose of Samsung’s bias and just get your facts straight :joy:

This issue is confirmed to present in the latest One UI 7 (Android 15), meaning by that Samsung haven’t moved to the new Android’s Private Space yet.

It’s worth noting that this flaw doesn’t exist with Google’s version of Secure Folder, i.e. Android 15’s Private Space. This is because Google created an entirely new user type for Private Space, android.os.usertype.profile.PRIVATE , which is treated differently by the photo picker and Permission Controller apps.

27

My point was still that samsung secure folder IS a samsung weird reimplementation of work profile, the article has proven me right

Because it’s work profile, as I said again and again and again

And no, It’s NOT a work profile flaw. If you don’t want your work profile data to be seen, you lock the work profile. It’s samsung that set an incorrect expectation and implemented a layer over the work profile in a weird non-standard way. Internal image picker being able to see work profile images is an android feature, if you don’t like it then lock your work profile (oh wait, samsung didn’t do that, typical samsung fuckups)

Determining what apps are installed in the Secure Folder

Work Profile are meant for work apps, not a way to hide apps. Samsung applied it for the wrong purpose, it having the wrong result is within expectation