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

alarm randomly fails with custom sound

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

I maintainer di solito rispondono entro 7 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
22/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Tranquilla
Stack tecnologico
android, kotlin
Ambito
mobile

Direzione di ricerca

The payload names no source file or test. The one searchable lead is the error text 'setDataSource failed' from the Java IOException in the screenshot, so search the repository for where the alarm sound URI is passed to a media player. The failure is intermittent and device-specific (Android 12, Moto G22), so reproducing it needs a device and several days of alarms. Done would mean a reliable fallback or a clear failure message, but the issue does not choose between the three expected behaviors it lists.

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

Descrizione

bug needs triage
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.6.0

Affected Android/Custom ROM version

Android 12

Affected device model

Moto G22

How did you install the app?

Google Play Store

Steps to reproduce the bug
  1. set a custom sound for the alarm
  2. use it normally for several months
Expected behavior
  • the alarm assuredly never fails to play the sound
  • or if failed, tell you why it failed when you wake up, instead of calling you a loser moron for sleeping too much
  • or know in advance the sound will not play, and tell you in advance it will fail before you set an alarm
Actual behavior

it randomly and silently fails

Screenshots/Screen recordings

yeah, I have a screenshot alright

Erro: java.io.IOException: setDataSource failed.: status=0x80000000

ignoreImageMinify

after the alarm failing for three days in a row, I selected the sound, it didn't play, and it showed this Java exception in the bottom. when I had same problem in Google Clock, it wouldn't even show an exception after the sound failed to play in the sound picker.

Additional information

pro tip: Google Clock has identical issue. I'm only using your app, because Google Clock had the same issue and I doubt they will ever fix it. so, even if your app is just as broken, I hope that you can fix it

my current workaround is to every night select the sound again and hear it, to double check that it will really play next morning. I've become fully paranoid of alarms not working. I've become so distrustful of clock apps in Android in general. and let me tell you. the alarm of my physical clock is also dysfunctional!!

Lingua principale
Kotlin
Stelle
706
Fork
73
Merge medio
5g 17h
PR unite (30g)
8

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/Clock

Tutte le issue di FossifyOrg/Clock

Issue simili

Altre issue su Kotlin

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.