TeamAmaze / TeamAmaze/AmazeFileManager
media files uploaded to mobile via FTP server are not in Android mediastore database
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
Triggering a full rescan of the database is possible, but time consuming ... like a reboot. That's annoying.
Who do others deal with this?
I'd expect that Amaze FTP server adds uploaded media files to MediaStore database ... somehow (like file transfers via Airdroid, etc.)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the FTP upload handling and its Android MediaStore integration, then verify that newly uploaded media appears in MediaStore without requiring a full database rescan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- databases, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100