Loading recordings is slow
Maintainers usually reply within 1 day
@naveensingh is already working on this.
Since Mar 11, 2025.
Assessment
This issue has not been assessed yet.
Description
Checklist
- I can reproduce the bug with the latest version given here.
- I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
- I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
- I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
- This issue contains only one bug.
- I have read and understood the contribution guidelines.
Affected app version
1.1.0
Affected Android/Custom ROM version
All Android versions
Affected device model
All Android devices
How did you install the app?
GitHub releases
Steps to reproduce the bug
- Select a folder with a lot (100s) of recordings (or audio files)
- Reopen the app
- Record another recording
Expected behavior
- Recordings load immediately or at least after a few seconds.
- New recordings should show up immediately.
Actual behavior
- On an average device, loading takes around 10 seconds for just 300 files.
- New recordings show up after the app is done loading all recordings. One has to wait for minutes if there are a lot of recordings.
Screenshots/Screen recordings
No response
Additional information
The slowness is a result of Android's inefficient DocumentFile implementation which is what the app uses now. Querying the document Uri directly using DocumentsContract should significantly speed up the process.
Even then, for a lot of recordings, some kind of pagination would be the ideal solution.
- Dominant language
- Kotlin
- Stars
- 1k
- Forks
- 98
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 14
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from FossifyOrg/Voice-Recorder
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
FossifyOrg/Voice-Recorder#419 ·
Maintainers usually reply within 1 day
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
FossifyOrg/Voice-Recorder#411 ·
Maintainers usually reply within 1 day
-
feature request needs triage
Difficulty 4/5 3-5 days Newbie friendliness 55/100
FossifyOrg/Voice-Recorder#441 ·
Maintainers usually reply within 1 day
-
toggle recording via bluetooth remote controlMay be free again A pull request for this issue was closed without being merged. Openfeature request needs triage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
FossifyOrg/Voice-Recorder#436 ·
Maintainers usually reply within 1 day
-
Audio LayeringOpenfeature request needs triage
Difficulty 5/5 Over a week Newbie friendliness 18/100
FossifyOrg/Voice-Recorder#432 ·
Maintainers usually reply within 1 day
All issues in FossifyOrg/Voice-Recorder
Similar issues
-
[Submission] AI服务引擎Opensubmit-adaption submit-adaption-pre
Difficulty 1/5 Under an hour Newbie friendliness 76/100
BetterAndroid/android-notification-icon-project#783 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
coding size:s skill:kotlin-core sub-issue
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
SKaiNET-developers/SKaiNET#1421 ·
Maintainers usually reply within 1 day
-
Show Full DetailsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
leonlatsch/Photok#809 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day