Repository navigation
[FEAT] Individual tagging/ naming #64
Description
Activity
Hi @HarriBuh, thanks for opening an issue. 1.5.4 will preserve the original filename, but custom naming won't as that's beyond the scope of my app and I don't want to overly clutter the UI.
That would perfectly fine. Thanks.
That new feature doesn't seem to work at all. At least, it's not enabled by default after updating to the latest version.
Every edited file will be be named to random digits and the "_compressed" tag.
I couldn't find any new options to change that either.That new feature doesn't seem to work at all. At least, it's not enabled by default after updating to the latest version. Every edited file will be be named to random digits and the "_compressed" tag. I couldn't find any new options to change that either.
uhh oops, I fucked up, 1.5.5 will be coming sooner than expected, so sorry about that, I should've tested first I only tested that it compressed a video and didn't even think to check the file name
Reacted by HarriBuhactually, no, google has decided privacy is "so important" so apps just get random numbers instead of file names, can we kill google with hammers
sharing videos to apps should still work?
yeah there's actually nothing I can do about this on Android 11+ sorry
Well that's a real shame. And weird. I mean, there are tons of FOSS apps that can rename edited files to their liking.. why not this one?
Well that's a real shame. And weird. I mean, there are tons of FOSS apps that can rename edited files to their liking.. why not this one?
They all request storage permissions, my app does not. The Android 11+ photo picker hides real file names.
Alright, and I guess you don't want to use this permission, ever?
Is this a thing about principles?Opened #65 with a fix: swap the picker for SAF (OpenDocument). It exposes the real DISPLAY_NAME and doesn't need any extra permissions, so the no-invasive-permissions promise stays intact.
SAF is a huge downgrade in terms of UX and also doesn't work properly on OneUI, which is not something I am willing to compromise on given that 8/10 of the top devices in my Play Store userbase is using OneUI and I personally use OneUI on my main phone.
Random-digit filenames as a permanent end state really isn't a good outcome. They look like an attempt at preserving names, but they're just the picker's synthetic IDs, no more meaningful than the
Compressed_<timestamp>names before 1.5.4. From a user's perspective the "preserve original file name" feature appears broken rather than absent.The "nothing I can do on Android 11+" framing isn't quite accurate. There are options:
-
Optional
READ_MEDIA_VIDEOpermission (READ_EXTERNAL_STORAGEpre-API-33), gated behind a "Preserve original file names" toggle in settings. The permission is only requested when the user opts in. With the grant, you resolve the picker's synthetic ID to the underlying MediaStore entry and read its realDISPLAY_NAME. Anyone who leaves the toggle off never sees a prompt: "no invasive permissions" stays true for them. This is what most FOSS apps do, and it's the path Android itself provides for this scenario. -
OS branching. The synthetic-ID behavior only kicks in on API 33+, on older versions the existing picker backport still returns real names. Routing through SAF only on API 33+ keeps the modern Photo Picker on every OS that doesn't break it anyway.
Regarding "100% AI-generated": fair to flag, and the footer was there for exactly that reason. The PR was written with Claude Code, but I read every line of the diff and tested end-to-end on my Pixel before opening it. The change was ~50 lines including the bonus hardening, not something I'd push without reviewing. Happy to redo it manually in a smaller diff if that's the real blocker.
Totally your call whether to act on any of this. I just wanted to push back on the "no options exist" framing, since the options do exist.
-
Random-digit filenames as a permanent end state really isn't a good outcome. They look like an attempt at preserving names, but they're just the picker's synthetic IDs, no more meaningful than the
Compressed_<timestamp>names before 1.5.4. From a user's perspective the "preserve original file name" feature appears broken rather than absent.The "nothing I can do on Android 11+" framing isn't quite accurate. There are options:
- Optional
READ_MEDIA_VIDEOpermission (READ_EXTERNAL_STORAGEpre-API-33), gated behind a "Preserve original file names" toggle in settings. The permission is only requested when the user opts in. With the grant, you resolve the picker's synthetic ID to the underlying MediaStore entry and read its realDISPLAY_NAME. Anyone who leaves the toggle off never sees a prompt: "no invasive permissions" stays true for them. This is what most FOSS apps do, and it's the path Android itself provides for this scenario. - OS branching. The synthetic-ID behavior only kicks in on API 33+, on older versions the existing picker backport still returns real names. Routing through SAF only on API 33+ keeps the modern Photo Picker on every OS that doesn't break it anyway.
Regarding "100% AI-generated": fair to flag, and the footer was there for exactly that reason. The PR was written with Claude Code, but I read every line of the diff and tested end-to-end on my Pixel before opening it. The change was ~50 lines including the bonus hardening, not something I'd push without reviewing. Happy to redo it manually in a smaller diff if that's the real blocker.
Totally your call whether to act on any of this. I just wanted to push back on the "no options exist" framing, since the options do exist.
- I'll think about it
- No
The SAF UI still sucks and is still broken on Samsung phones. Again, this is my app, my choices are mine because it's my app, I don't gain or lose anything because it's my app and it's free. You are free to have and maintain your own fork using SAF instead of the objectively significantly better Android media picker, but I am not going to merge SAF and that's final.
- Optional
Also there's no such thing as optional permissions, permissions are either there or they're not. As soon as I add that permission, now Google Play will start manually reviewing all my releases, and IzzyOnDroid starts saying my app has storage permissions.
I do not appreciate your 100% AI generated comments, you could at least fight this argument in your own words, so I am locking both this issue and your pull request. Please do not open a new issue or pull request, please do not email me, please do not message me on my socials. Goodbye.
- Repository owner locked as resolved and limited conversation to collaborators
on May 12, 2026
Metadata
Metadata
Assignees
Labels
Projects
- Status
Feature Request
I would like to be able to give a specific name to my compressed video, as I find the current naming very irritating/ not helpful. And because it will be saved in the apps own folder anyway, it could even keep its original name. Like "VID_xyx124", alternatively with that "-compressed" addition.
Device Info