Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Update cover art when media is rescanned (or on explicit trigger)

Aperta
  • Qualcosa non va?
#516 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
53/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
android, kotlin
Ambito
backend, mobile

Direzione di ricerca

Start by locating the album art loading and cache invalidation entry points, then check how media rescans detect changed files. The issue names no files or tests, so first trace the existing scan flow and identify how cached artwork is stored. Done means replacing an album art file, then rescanning or using an explicit trigger, refreshes the displayed cover.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

feature request needs triage
Checklist
  • 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 request will be dismissed otherwise.
  • This issue contains only one feature request.
  • I have read and understood the contribution guidelines.
Feature description

It would be nice for the player to notice when I've updated (read: corrected) an album art file, and update the display rather than keeping the previous image cached.

Why do you want this feature?

I have at least once put the wrong cover art in the folder with my audio, and it annoys me every time I open it up in the player.

Additional information

I saw this behavior when replacing an image file with both a new one of the same name, and of a different name.

Workaround attempts that did not solve the problem for me:

  • Excluding then restoring the containing folder
  • Restarting my phone
  • Clearing the app cache
  • Clearing the app storage

The feature request is a low priority one since it's a rare issue and doesn't affect the core functionality/usability. That said, it seems crazy that clearing the app storage and cache still somehow left a reference to a file that no longer available in my file manager (and I previously would have assumed is no longer on my device at all). I haven't gone as far as uninstalling and reinstalling the app, or deleting and restoring the folder/files containing my audio.

Lingua principale
Kotlin
Stelle
933
Fork
104
Merge medio
21h 12m
PR unite (30g)
15

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di FossifyOrg/Music-Player

Tutte le issue di FossifyOrg/Music-Player

Issue simili

Altre issue su Kotlin

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.