Remember folder permission when exporting APKs and configs

[WANGxHenry]

Just extract apks in the file,now need to allowed every time.

Screen_Recording_20250402_143603_SD.Maid.SE.mp4

It's not happened on sdmaid1,sdmaid 1 only one time authorized than extract app without ask,just extract apps in the file I set.

[d4rken]

I think it is easier and more flexible the way it now is in SD Maid 2.
Just dumping all exported APK data into a specific folder, all the time, makes it difficult to find and organize the files. While SD Maid 1's behavior may be easier for your specific use case, I think most users find the current way easier.

Closing this as I will not change the implementation at this time.
If a significant amount of users think differently about this feature, feel free to discuss it and we can revisit changing it in the future.

[WANGxHenry]

I think it is easier and more flexible the way it now is in SD Maid 2. Just dumping all exported APK data into a specific folder, all the time, makes it difficult to find and organize the files. While SD Maid 1's behavior may be easier for your specific use case, I think most users find the current way easier.

Closing this as I will not change the implementation at this time. If a significant amount of users think differently about this feature, feel free to discuss it and we can revisit changing it in the future.

Well,I'm means that permission in 8 sec .
I don't mind choose or creat new folder to extract apks,it's fine for me.
I means the difference between SDMaid 1 and 2,is the permission everytime.

After allowed all permission of SDmaid 1 in the beginning,the apk just extract into download folder,sdmaid1 didn't ask for the permission .

But sdmaid2 ask everytime even I allowed all permission in the begining setting.

So that's the issue I'm talking,haha.

Just confuse why I need to allowed system every time on SDMAID2?

[d4rken]

Reviewing this again after a discussion on discord.

While the system file picker will stay, SD Maid could theoretically remember the SAF permission given when selecting a previous folder for exports. So the "grant access dialog" no longer would have to show.

Caveats:

• There is a soft limit on the number of SAF permissions an app can hold ~128?
• We'd need logic to maintain this 128 permission count
• Pay attention to definitely keep the SAF permission that are part of setup
• Maybe a soft and basic SAF permission browser as part of the setup screen menu (like data areas)
• Side question, does having large numbers of URI permissions slow down deletion or search because SAF path mapping gets more complicated?

@WANGxHenry If this was your original idea, sorry. Might have been a language barrier issue.