zhanghai / zhanghai/MaterialFiles
Notification bug
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 9k
- Forks
- 736
- PR merge metrics
- No merged PRs in 30d
Description
The bug in notification happens when I extract two files at the same time.
u0_a355@localhost
OS: Android REL 14 aarch64
Host: Xiaomi 11 Lite 5G NE (2)
Kernel: Linux 5.4.259-qgki-gbf
Uptime: 18 hours, 16 mins
Packages: 98 (dpkg)
Shell: bash 5.2.32
WM: Window Manager
Terminal: Termux 0.118.1
Terminal Font: monospace
CPU: SM7325 (8) @ 2.40 GHz
Memory: 5.44 GiB / 7.04 GiB
Swap: 3.68 GiB / 6.00 GiB (61%)
Disk (/): 705.48 MiB / 705.48 MiB
Disk (/storage/emulated): 72.x GiB
Local IP (rmnet_data3): 10.119.x.x
Local IP (wlan0): 192.168.100.x
Locale: en_US.UTF-8
https://github.com/user-attachments/assets/203d36cc-fcc6-4ed5-80b5-c6842cdd249f
Contributor guide
No contributing guide indexed for this repository
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 notification bug while extracting two files simultaneously on the reported Android environment, using the attached recording for comparison. Trace the extraction and notification entry points to determine the incorrect behavior; done means the notification behaves correctly during concurrent extraction and the reproduction no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100