[C2] RTC Alarm triggers bootup but sits on encryption screen and does not actually play the alarm

Bug Reports
#1

REPRODUCIBILITY: 100%
OSVERSION: 5.0.0.29
HARDWARE: Reeder S19 Max Pro S - s19mps - s19mps - 1.0.0.22 - aarch64
UI LANGUAGE: English (UK) (user: en_GB, os: en_GB.utf8)
REGRESSION: no idea

DESCRIPTION:

Setting an Alarm and shut down of phone should boot up the phone on alarm time using RTC. Then play the alarm at correct time once booted up

PRECONDITIONS:

Sounds are working generally. (Checked through Settings->Sounds)

STEPS TO REPRODUCE:

  1. Open Clock app
  2. Set a Timer, save it, shut down the phone
  3. let time elapse

EXPECTED RESULTS:

Start to boot up of device prior to alarm (works)
Audible alert from alarm app after boot up at the time set in alarm app (does not work)

ACTUAL RESULTS:

Device starts to boot up approximately 1 minute before the timer elapses. Which tells me the RTC is triggered. But once booted up to the encryption pin entry, it sits on that screen screen and keeps the screen on for minutes (indefinitely?). The alarm app does not play the alarm sound at the set time however.

MODIFICATIONS:

  • Patchmanager: no
  • OpenRepos: yes
  • Chum: yes
  • Other: none specified

ADDITIONAL INFORMATION:

Device Owner User: defaultuser

2 Likes
#2

Thanks for reporting. I noticed the same issue, but forgot about it already.

2 Likes
#3

How can it boot up without asking for decryption-pin?

#4

Thanks for pointing out @fingus . What i meant to say was “starts to boot up” and “once booted to the encryption pin entry”. I mixed up the encryption pin entry with the login pin. But one could argue that it is booted up to some extend at the point the encryption pin is request. Since it clearly is a user interface.

#5

Now reading the forum more, i question if this is related to a general alarm (sound) issue reported here:

#6

Or eventually starting up and have a minimal alarm able to ring even if the encryption is still enabled ?

1 Like