Repository navigation
[BUG] saved filename filled from wrong source #105
Copy link
Copy link
Closed as not planned
Labels
BugSomething isn't workingSomething isn't workingOEM issueThis issue is caused by your device manufacturer, not CompressorThis issue is caused by your device manufacturer, not CompressorUser InterfaceThis issue is related to the user interfaceThis issue is related to the user interfaceWon't FixThis will not be worked onThis will not be worked on
Description
Issue Description
The filenames that compressor saves to seem to be not the original video file name, but that of the thumbnail. This loses important information stored in the original filename (e.g. recorded date)
Expected Behaviour
Filename of actual original video file is used in the compressed file name when "original name" chip is part of the file name, as per >settings>general>filename builder
Device Info
Device Manufacturer* (e.g. Samsung):
- Device Model* (e.g. Galaxy S10): Black view Shark 8
- Android Version* (e.g. 12): 13
- Compressor Version* (e.g. 1.1.0): 1.6.2
- Where did you get Compressor from?* (GitHub Releases, IzzyOnDroid/F-Droid, Google Play Store): IzzyOnDroid
- Device Chipset (e.g. Exynos 9820):
- Device Model Number (e.g. SM-G973F):
Screenshots
No response
Logcat
No response
Prerequisites
- I have checked that there are no open issues that are the same or very similar to mine, and I understand that my issue will be closed if it is a duplicate
- I have filled in all required fields to the best of my ability, and I understand that my issue will be closed if they are not
- I have copied the device & app info to my clipboard and pasted it into the device info section where indicated, and I understand that my issue will be closed if it is not
- I have uploaded appropriate screenshots and log files, and I understand that my issue may be closed or remain unresolved if not
- My issue is written in English, and I understand that my issue will be closed if it is not
- My issue is not listed in [READ FIRST] Features/bugfixes that will NOT be implemented #3
- I have added a title to my issue
- I understand that my issue will be closed if all of these checkboxes are not checked
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
BugSomething isn't workingSomething isn't workingOEM issueThis issue is caused by your device manufacturer, not CompressorThis issue is caused by your device manufacturer, not CompressorUser InterfaceThis issue is related to the user interfaceThis issue is related to the user interfaceWon't FixThis will not be worked onThis will not be worked on
Projects
- StatusShow more project fieldsNot Implementing
Activity
JoshAtticus commentedon Aug 22, 2026
Hi @Antzus! Thanks for opening an issue. Unfortunately this is a limitation imposed by Google that can't be bypassed without adding invasive storage permissions. This will be fixed in Compressor Edge (see https://compressor.joshattic.us/edge).
Antzus commentedon Aug 22, 2026
Thanks for fast and straightforward response. I'd be open to a version of Compressor that requires file-access permission.
Google really is a double-edge sword of functionality + dis-functionality...