Hacktoberfest 2026:メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

オープン
#176 コメント 6 件 リアクション 1 件 担当者 0 名 GitHub で見る

メンテナーはふだん 7 日以内に返信

まだ誰も着手していません。

評価

この issue はまだ評価されていません。

説明

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 :(

主要言語
Kotlin
スター
706
フォーク
73
平均マージ
5日 17時間
マージ済み PR(30日)
8

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

FossifyOrg/Clock のほかの issue

FossifyOrg/Clock の issue をすべて見る

似ている issue

Kotlin の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。