nein, die zeiten kommen alle korrekt rein.
Das problem ist wirklich aus Auslösen von Timed Events in Android. Es gibt da (min.) 2 verschiedene APIs: "high precision" und "low precision" - erstere macht entsprechend größeren akkuverbrauch und zweitere ist weniger genau.
Dazu kommen dann noch herstellerspezifische Implementierungen von Suspend/Standby/Sleep und Notifications:
Some Android OEMs have their own customised Android OS that can prevent applications from running in the background. Consequently, scheduled notifications may not work when the application is in the background on certain devices (e.g. by Xiaomi, Huawei). If you experience problems like this then this would be the reason why. As it's a restriction imposed by the OS, this is not something that can be resolved by the plugin. Some devices may have setting that lets users control which applications run in the background. The steps for these can vary but it is still up to the users of your application to do given it's a setting on the phone itself. The site https://dontkillmyapp.com provides details on how to do this for various devices.It has been reported that Samsung's implementation of Android has imposed a maximum of 500 alarms that can be scheduled via the Alarm Manager API and exceptions can occur when going over the limit.
