Next Alarm Time on Android Lock Screen

hendis

Member
Just got a new phone, moved from a Samsung Galaxy Note 5 to a T-Mobile REVVL V+ 5G, and Android 7 to Android 11. Running MD Pro. I'm still in the process of setup, but I have noticed a problem, and want to let the forum know about it.

On the lock screen of my new phone, the default clock app is supposed to show the next alarm time if an alarm is set. I have traced this problem to MacroDroid. When MacroDroid is uninstalled the problem goes away. I have an alarm set in my default clock app, but when MacroDroid is installed, the time shown on the lock screen for the next alarm will always be incorrect. If I uninstall MacroDroid, the time shown on the lock screen reverts to the correct value. I have not found a way to suppress the next alarm display or correct it, either in Macro Droid or in the phone settings.

Does anybody else think that this behavior sounds like a bug?
Is there any way that I can get the correct time on the lock screen and use Macro Droid as well?
 

Dm114

Well-known member
You probably have macros with Day/Time triggers and/or Wait actions and the Use alarm boxes ticked.

Just untick these boxes. Unfortunately the triggers will fire with less accuracy (generally from 0 to 2 minutes). I guess it's a specific behavior with Samsung device because I pointed this problem many years ago but @MacroDroidDev never could reproduce it...
 

hendis

Member
Yes, I have many macros. (Between 60 and 70) Many of them have Day/Time triggers, and many more have wait actions. Which boxes do you suggest that I untick? How can I replicate the actions that you suggest that I not use? I am more than willing to edit my current macros if needed.
 

hendis

Member
I'd like to report possible success - maybe.

I went through each of my macros and UNticked "use clock" in every place where possible. A cursory glance at the lock screen shows that the next alarm time is showing accurately. We will see what we will see.

Apparently, the trigger or other time in MD was feeding it's value to the lock screen IF the "use clock" tickbox was checked.

Like I said, we will see what we will see...
 

Dm114

Well-known member
See attached screenshots
 

Attachments

  • 20220622_065413.jpg
    20220622_065413.jpg
    321.4 KB · Views: 3
  • 20220622_065241.jpg
    20220622_065241.jpg
    264.5 KB · Views: 3

Dm114

Well-known member
I'd like to report possible success - maybe.

I went through each of my macros and UNticked "use clock" in every place where possible. A cursory glance at the lock screen shows that the next alarm time is showing accurately. We will see what we will see.

Apparently, the trigger or other time in MD was feeding it's value to the lock screen IF the "use clock" tickbox was checked.

Like I said, we will see what we will see...
Don't worry! You problem is now solved... unless you forgot to untick one only box. 😉🙂
 

hendis

Member
Dm114, thank you for your suggestion. I hope that it works - only time will tell.

BTW, this problem is not limited to Samsung devices. (IDK how the old Note 5 would have reacted to this, bc when I used it, I never used the clock or set a screensaver or set an alarm...) But everything is different now that I'm not using a Samsung phone any more.
 

Dm114

Well-known member
Dm114, thank you for your suggestion. I hope that it works - only time will tell.

BTW, this problem is not limited to Samsung devices. (IDK how the old Note 5 would have reacted to this, bc when I used it, I never used the clock or set a screensaver or set an alarm...) But everything is different now that I'm not using a Samsung phone any more.
Good question!

I spoke about Samsung because @MacroDroidDev told me, in the past, it could be an issue due to my Samsung device (old A40 under Android v9, I'm fighting every day to avoid upgrading...)

I misread your first post and understood you had a configuration similar to mine. In fact it's the exact opposite: you have a brand new device with new Android version. It could be interesting to report your problem in the troubleshooting section of the MD home page.
 

MacroDroidDev

Administrator
Staff member
Unfortunately the only way to ensure accurate time wakeups is to set the wakeup as an alarm which obviously interferes with displaying when the next "Alarm" is.
 
Top