alarm randomly fails with custom sound

Offen
  • Stimmt etwas nicht?
#447 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
22/100
Issue-Typ
Bug
Klarheit
Muss geklärt werden
Aktivitätsstatus
Ruhig
Tech-Stack
android, kotlin
Bereich
mobile

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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!!

Vorherrschende Sprache
Kotlin
Sterne
706
Forks
73
Ø Merge
16 Std. 52 Min.
Gemergte PRs (30 T.)
11

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus FossifyOrg/Clock

Alle Issues in FossifyOrg/Clock

Ähnliche Issues

Weitere Issues zu Kotlin

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.