Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Sometimes Alarms will not work on set time (started in version 1.20)

Abierto
  • ¿Algo no está bien?
#176 6 comentarios 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 7 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
18/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
android, kotlin
Área
mobile

Línea de trabajo

The payload names no source files or tests, so the entry point is the app's alarm scheduling code, which the reporter says changed between versions 1.1.0 and 1.2.0; compare those releases to find what changed. Reproducing needs a Transsion (Tecno/Infinix) device or an emulator with aggressive battery restrictions. Done means alarms fire at the set time after a day of use, verified on that vendor's phone.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug device/software specific needs reproduction
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.2.1

Affected Android/Custom ROM version

Android 13

Affected device model

Tecno Camon 19 Pro 4G

How did you install the app?

GitHub releases

Steps to reproduce the bug
  1. I set some alarms for testing
  2. Wait for one day
  3. On other day the started to alarm in a wrong time: 10 minutes later, even two hour later from set time
Expected behavior

Alarms should work in a set time

Actual behavior

After ~1 day use alarms start to ring in a wrong time - 10 minutes later or even 2 hours later

Screenshots/Screen recordings

No response

Additional information

Versions 1.0 and 1.1 work perfectly for a long time. Then I updated to 1.2.0 from the Google store - and it started behave as above. Tested it for a long time. I reverted to 1.1 - works perfect.
Then 1.2.1 came out - I download it from github - the same behaviour as 1.2.0 :(

I think it is the issue with my Vendor - Transsion (Tecno, Infinix etc phones)
I have similar problems with other alarms, and I tried everything, I think (I have that phone for 1.5 years). No battery savings etc.
And I found your app that works fine. but after 1.2.0 update it started to behave as many other alarms :(
I know it is ridiculous to change app just for one vendor, but maybe those changes have other ways... so my phone could work fine with it?)
Or maybe you know what you have changed from 1.1.0 version to 1.2.0, so I will know where to dig :(

Lenguaje dominante
Kotlin
Estrellas
706
Forks
73
Merge medio
5 d 17 h
PR fusionados (30 d)
8

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de FossifyOrg/Clock

Todos los issues de FossifyOrg/Clock

Issues similares

Más issues de Kotlin

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.