Alarm icon on status bar set by an app "Macrodroid" won't go away
- Thread starter Ali121
- Start date
I will check that and come back to you thanks.
This macro opens up the clock application but there is no active alarm set. And I am pretty sure that this alarm has been set by macrodroid app
Endercraft
Moderator (& bug finder :D)
If MacroDroid has been uninstalled, how would it still have an alarm active ?
I think MacroDroid is not the culprit here.
I'll try to verify it. It's a bit troublesome to test on the main terminal, so I'd like to verify it and upload the results after setting up the environment on a sub terminal.
Dimlos thank you sooo much man. your trick worked thanks aloooooooot
You're right. I really thought that it was because of microdroid but I was wrong. it was some other app and Dimlos macro helped me findout. wow Dimlos
It seems that we have reached a conclusion, but since we verified it, we will upload the results.
1.If no alarm is set, the icon will not be displayed and the macro will be shown as empty.
2.Set the Clockapp alarm.
3.The app name becomes Clock and the time is displayed correctly.
4.In the Wait action, the app name should be MacroDroid.
5.Uninstall MacroDroid, the icon will disappear.
1.If no alarm is set, the icon will not be displayed and the macro will be shown as empty.
2.Set the Clockapp alarm.
3.The app name becomes Clock and the time is displayed correctly.
4.In the Wait action, the app name should be MacroDroid.
5.Uninstall MacroDroid, the icon will disappear.
Attachments
Last edited:
Just to clarify.....
It used to be possible to schedule device wakeups at specific times and have them honoured by the device actually waking up at the requested time. Now there are all sorts of restrictions, so if we request a wakeup at 10:00am for example, the device might wake up at 10:00am, it might wake up at 10:02am, 10:05am ...... or it might just say nope your app has had too many wakeups today and totally ignore it and it also varies based on the manufacturer and what battery optimization settings might be enabled.
In order for the device to wake up at an exact specified time an app has to use what is known in the SDK as an alarm clock. This will mandate that the icon is displayed in the notice bar whenever one is pending.
Of course most people who use the day/time trigger want it to actually work at the specified time so the "use alarm" option is enabled by default. The same goes for wait before next action etc.
It used to be possible to schedule device wakeups at specific times and have them honoured by the device actually waking up at the requested time. Now there are all sorts of restrictions, so if we request a wakeup at 10:00am for example, the device might wake up at 10:00am, it might wake up at 10:02am, 10:05am ...... or it might just say nope your app has had too many wakeups today and totally ignore it and it also varies based on the manufacturer and what battery optimization settings might be enabled.
In order for the device to wake up at an exact specified time an app has to use what is known in the SDK as an alarm clock. This will mandate that the icon is displayed in the notice bar whenever one is pending.
Of course most people who use the day/time trigger want it to actually work at the specified time so the "use alarm" option is enabled by default. The same goes for wait before next action etc.