The standard StartReceiverAt is inexact, in order to allow the OS to make optimizations. Worth reading: https://developer.android.com/training/scheduling/alarms Exact scheduling: 1. AddPermission(android.permission.SCHEDULE_EXACT_ALARM) 2. Private ion As Object - class global 3. Private...
Learn how to use Android's AlarmManager to schedule time-based operations that can run even when your application is not active, distinguishing between inexact and exact alarms and their implications for system resources.
developer.android.com
From the article:
"Repeating alarms allow the system to notify your app on a recurring schedule.
A poorly-designed alarm can cause battery drain and put a significant load on servers. For this reason, on Android 4.4 (API level 19) and higher, all repeating alarms are inexact alarms.
A repeating alarm has the following characteristics:
A trigger time. If the trigger time you specify is in the past, the alarm triggers immediately.
The alarm's interval. For example, once a day, every hour, or every 5 minutes.
A pending intent that fires when the alarm is triggered. When you set a second alarm that uses the same pending intent, it replaces the original alarm."
How can I implement the whole thing in B4A with receivers, to start a receiver every day at 10 o clock?
This document outlines the changes to the SCHEDULE_EXACT_ALARM permission in Android 14, where it is no longer pre-granted to most newly installed apps, and discusses migration steps, best practices, and alternative APIs.
The standard StartReceiverAt is inexact, in order to allow the OS to make optimizations. Worth reading: https://developer.android.com/training/scheduling/alarms Exact scheduling: 1. AddPermission(android.permission.SCHEDULE_EXACT_ALARM) 2. Private ion As Object - class global 3. Private...