Set Alarm

[xtofke]

Hi,
I recently switched to a Samasung Galaxy S5 (unrooted, Lollipop)

On my previous phone (running Slimkat 4) I had a workflow that would set alams based on calendar events. I copied the workflow to my new device and the workflow is working fine.

The only thing that bothers me that now instead of reactivating an existing (past) alarm, a new one is being created. This results in a huge number of inactive alarms after a while.
On my Nexus 7 (also Lollipop) the workflow also reuses existing alarms.

--> I suppose this behaviour is linked to the used alarm-app.

I already tried timely but behaviour is the same.

Is there an alamr app know to re-use existing alarms instead of creating new ones?

[Martin]

Hi,

The behavior depends on alarm app since it was not well defined in the past how an alarm app should behave.
The stock clock app distributed by Google on Android 5.1 reuses an existing alarm when all options are the same (same time and same label).
There are some ports of the official clock app available on Google Play that might implement the proper behavior (untested and often contain ads of some sort).

Regards,
Martin