TeamAmaze / TeamAmaze/AmazeFileManager
Numbers in "Propterties" load at different speed
Open
Nobody has claimed this yet.
Issue-Glitch
Not-reproducible
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
Describe the bug
Under "Properties", same number is found for the graph but not for the "Size" text field
To Reproduce
Steps to reproduce the behavior:
- Go to '/storage/emulated/0/Android/media/com.whatsapp/WhatsApp/Media'
- Select 'WhatsApp Images'
- Open its properties
- If large number of files are there in it, then the numbers in the graph will be loaded before the number in "Size"
Expected behavior
The number 265 MB should have come at both places together
Screenshots
Image with problem
Image after waiting for some time
Smartphone (please complete the following information):
- Device: Redmi 4x
- OS: Android 12
- Rooted: No
- Version: 3.8.2
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
Start by reproducing the issue in the Properties view using a large WhatsApp Images folder, then compare when the graph and Size value appear. The work is done when both show the same size at the same time without the Size value lagging behind.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100