[PAID] ⏰ Alarm Manager Extension with Notification or Autostart

[Taifun]

earlier you confirmed

@Emissary95

and gets the data for the current date from a text file (20000) characters in half a second.

@Emissary95

When you click LoadPrayerTimesData, the data in these blocks is immediately updated.

No
What about revealing the source code of your AI written extension?

Taifun

[Emissary95]

You're just nitpicking my words right now)) I'll send you the code in a private message, but as I said, that's not the point of my question.

[Taifun]

@Emissary95

You're just nitpicking my words right now

only those who understand the difference between "immediately" and "a tiny bit of time" can understand it

@Emissary95

I'll send you the code in a private message

I now checked your source code and I will comment only on what is required to answer your question

your code offers an event called OnDataLoaded. Remember what I mentioned earlier

@Taifun

if you or AI did it correctly then there should be an event, which provides the result, as this takes a tiny bit of time

In that event handler then the 5 new alarms should be set

Register that event using itoo and use the corresponding event handler to set the 5 alarm times

    @SimpleEvent(description = "Событие после загрузки данных.")
    public void OnDataLoaded(int recordsCount) {
        EventDispatcher.dispatchEvent(this, "OnDataLoaded", recordsCount);
    }

Taifun

[Emissary95]

@Taifun

OnDataLoaded

I honestly don't understand how this will help, since the notifications are coming and it's not the problem with them, but with the OnReceive call at 00:10 startnow. The notification that I set for testing doesn't come, which means that the procedure isn't being called for some reason.

[Taifun]

@Emissary95

but with the OnReceive call at 00:10 startnow

How did you set the alarm for 00:10? Remember to do it in an event, for example a button click event

Also use the alarmmanager extension only once, do not drag it twice to the working area

I see you updated your screenshot... the blocks to register the event look better now. Take your time to test. However as GetFarjMinute does not exist before the data has been loaded, you should call it in the event handler after the data has been loaded

Taifun

[Taifun]

Usually you would use the same argument name, which is recordsCount

Taifun

[Emissary95]

@Taifun

How did you set the alarm for 00:10?

[Taifun]

If you’re unsure whether the alarm was set correctly, use the Started event to verify it. You can then close the application when the user presses a button.

Again

@Taifun

use the alarmmanager extension only once, do not drag it twice to the working area

Taifun

[Emissary95]

The startnow notification block triggered with a delay of 7 minutes at 00:17, which is strange... in principle, it doesn't matter to me, the main thing is that it worked, albeit with a delay.

[Taifun]

You just found out the difference between inexact and exact alarms

Note : Google recommends to use exact alarms wisely to reduce battery consumption. See also Use cases that might not require exact alarms. If you decide to use exact alarms, then the user needs to grant the SCHEDULE_EXACT_ALARM permission, see method AskForScheduleExactAlarmPermission

Taifun

[Emissary95]

The extension works like a Swiss watch. It's a shame there's no choice of notification tones.

[Taifun]

@Emissary95

choice of notification tones

You can set a custom notification sound, see also the documentation at App Inventor Extensions: Alarm Manager | Pura Vida Apps

Taifun

[RafVuc]

Hey! I recently bought @Taifun's Alarmmanager extension to send SMS every 15 minutes even while the devices screen is off. But I can't quite get it to work properly. Anyone of you guys got an idea why?

My Code:

Thank you in advance,
RafVuc

[Taifun]

the texting component has not been designed to send sms in the background...
therefore you will have to start your app at the given time to be able to use the texting component to send the sms

alternatively without using the texting component you could use additionally my sms receiver extension, which is also able to send sms in the background, see App Inventor Extensions: SMS Receiver | Pura Vida Apps

I was wrong about the texting component not being able to send sms in the background, see my latest test example below

btw. you did not really understand how background processing is working... the AfterAlarm event does not fire in the background, you have to use the OnReceive event handler

see again the documentation at App Inventor Extensions: Alarm Manager | Pura Vida Apps and the examples in the Itoo integration section of the documentation

AfterAlarm
Event indicating that an alarm occurred. Event will fire only if the app is up and running, else depending on the startMode a notification will be displayed or the app will open screen LockScreen.

Taifun

[Taifun]

I did some more tests and was now able to send a sms in the background using the texting component (tested on Samsung Galaxy A54 running Android 16)

you can find the example project in the download folder of the alarmmanager extension

this example uses the

• itoo extension by @Kumaraswamy
• alarmmanager extension by @Taifun
• tools extension by @Taifun to check if SEND_SMS permission has been granted

Note: This solution is not permitted on Google Play, because it is using the SEND_SMS permission.

Taifun

[Irawan99]

Hello Pura Vida Team,

I have tested the Alarm Manager extension using the official lockscreen demo app (.aia) provided by Pura Vida.

However, I encountered the following issues:

1. The alarm only works when scheduled for a short time ahead (around 1–3 hours).
2. When I schedule alarms for longer periods (for example 16–20 hours later), the alarm does not ring at all.
3. When I set 3 different alarms for different times about 20 hours ahead, none of them work.
4. Each alarm uses a different ID.
5. I have already tried using “Start Always” mode as shown in the demo.

Could you please clarify:

• Is there a maximum time limit for how far an alarm can be scheduled?
• Or is there a specific configuration required to make long-term alarms work properly?

For your information, I am using a Vivo smartphone with Android 11, and all required app permissions have been enabled according to the demo .aia configuration.

This issue is very important because long-term alarms are currently not working at all.

Thank you for your support.

Best regards,
Ade Irawan

[Taifun]

@Irawan99

When I schedule alarms for longer periods (for example 16–20 hours later), the alarm does not ring at all.

Try to disable battery optimization. You can do this manually or use my extension

App Inventor Extensions: Ignore Battery Optimization | Pura Vida Apps

See also Vivo | Don’t kill my app! for Vivo restrictions

You also can try another device to find out, if the issue is device specific...

@Irawan99

Is there a maximum time limit for how far an alarm can be scheduled?

No, you can define an alarm also years in advance, for example as birthday reminder

@Irawan99

Or is there a specific configuration required to make long-term alarms work properly?

For some devices battery optimization has to be disabled

Taifun

[Irawan99]

but i have disabled battery optimization as per lockscreen.aia demo but it still doesn't work

[Taifun]

Read again this

@Taifun

Vivo | Don’t kill my app!

for your specific device
Try another device to see it working correctly

Taifun

[Taifun]

@Irawan99

I am using a Vivo smartphone with Android 11

I now asked Gemini for you. See the recommendations below

Taifun

---

It sounds like your user is running into the classic "Android Background Execution" wall. Even with battery optimization disabled, Vivo devices (along with Oppo, Xiaomi, and Huawei) are notorious for having aggressive secondary power management layers that the standard Android settings don't always touch.

​Since the alarms work in the short term but fail over longer periods, it's highly likely the system is "killing" the app's process or ignoring the AlarmManager to save juice.

​Here is a breakdown of what is likely going wrong and how to fix it:

1. Lock the app in the App Switcher: Open the app, go to the "Recent Apps" screen, and swipe down on the app card to "Lock" it (a small padlock icon will appear).

2. ​Check "High Background Power Consumption":

Vivo phones use Funtouch OS, which has its own proprietary battery manager. Disabling "Battery Optimization" in the standard Android settings often isn't enough.

• ​The Fix: The user needs to go to Settings > Battery > High Background Power Consumption and ensure your app is toggled ON. This tells Vivo’s custom skin not to freeze the app when it’s idle for a long time.

3. ​Enable Autostart: Essential for any alarm-based app on Chinese OEMs.

On Android 11, Vivo devices require explicit permission for an app to "start" itself (which is what happens when an alarm triggers while the app isn't in the foreground).

• ​The Fix: Ask the user to check Settings > App Manager > Autostart (or search "Autostart" in settings) and grant permission to your app.