Open Source • Background Tasks: Itoo 🚀

[Taifun]

which time picker value did you try?
what is the timer interval you got displayed in Label3?
for debugging use logcat

Capturing Device Logs using adb logcat

ADB is a command-line utility that that can be used to control your device over USB from a computer. It will allow you to install / uninstall and or view logs on your device. This could be very handy when there are issues with a specific app and you like to view the logs for information that may lead to identify the cause of error. In this post, we’ll discuss how to install and use ADB. Installation: ADB comes with Android SDK. However, you can download ONLY the ADB files from HERE . EDIT: …

EDIT: for an alarm example with itoo you also can try this

Alarm Manager with Itoo

The aia file aims to create an alarm system based on a background system created with Itoo. Reliability is maximum and it will always notify us exactly at the hour and minute marked as the alarm. The app would manage the service, auto-starting when there are pending alarms and closing when there are no pending alarms in the database. The application uses the following components [componentes] The aia consists of two parts: 1.- The Activity part 2.- The Service Part 1. In the activity par…

btw. usually you would use the alarmmanager feature of your Android device, which does not require to display a persistent notification... the Android system just will trigger your app at the given time "magically"... you coule use my paid alarmmanager extension for this...

[PAID] Alarm Manager Extension with Notification or Autostart

I tested the alarmmanager2.apk on some of my test devices. It works on: Pixel 2XL (Android 11) → works Galaxy Note8 (Android 9) → works Xiaomi Redmi Note 5 (Android 9) → works Nexus 5x (Android 8.1) → works Galaxy A3 (2017) (Android 8.0) → works Galaxy S6 (Android 7) → works Galaxy Note 3 (Android 5) → works Does not work on: Xiaomi Redmi Note 5 (Android 9) → doesn't work (also not in foreground) (EDIT: Notifications were disabled, no idea why) Galaxy S6 (Android 7) → doesn't work (also…

Taifun

[MOSAAB_BANI_MOSTAFA]

thanks for your help , but i need small notification not alarm , if you can i will send aia file to modify it ,
the timepicker i try is first one always but now it doesn't work

[Taifun]

@MOSAAB_BANI_MOSTAFA

but i need small notification not alarm

the purpose of an alarmmanager is to send a notification at a given time in the future without displaying a persistent notification

read again my previous answer and provide some answers...

@Taifun

which time picker value did you try?
what is the timer interval you got displayed in Label3?
for debugging use logcat

Taifun

[MOSAAB_BANI_MOSTAFA]

please try to open it and make what ever you want and send it to me
bgtasksClock (1).aia (153.6 KB)

[MOSAAB_BANI_MOSTAFA]

just for 1 time picker

[Taifun]

Unfortunately my free service ends here... I can fix your project and work with your aia file for a small fee... just send me a PM if you are interested in this...

How to send a PM (personal message)

Simply click on a user’s avatar and you will see some details about the user. [Unbenannt] Click on the message button to send a private message to that person. A private message is just like a post but can only be viewed by the recipient(s). You can include multiple people in a private message. Taifun Trying to push the limits! Snippets, Tutorials and Extensions from Pura Vida Apps by [image] Taifun.

Else check this example as already mentioned earlier

Taifun

[Randal_Andress]

@Kumaraswamy

It is just a Screen1 event issue

I am experiencing what seems like a similar event failure in the service process with the PhoneCall component's PhoneCallStarted and PhonecallEnded events.

To illustrate this, I modified the ItooMusic app to show that while the user interface receives these events, the Itoo service does not.

I am using Itoo 4.4.2 but have explicitly registered both events in the original manner. (I also tried it using the added implicit feature with a procedure properly named.)

The following screen shows starting the player. Then a call is made to the phone and rejected. Finally, the player is stopped.

The blocks:

The aia:
ItooMusic_orig_PhoneCall.aia (4.2 MB)

So far I have only tested this on Android 8. When the app starts for the first time (after being freshly installed) it asks for permission to make and manage phone calls , whereupon I select "Allow".

Have I misunderstood or misused something?

Kind regards,
Randal

[Kumaraswamy]

Will get back to this... Soon

[Randal_Andress]

Thank you very much for the reply. I realize you are "out of pocket" presently... I hope you are having an enjoyable or productive time (whichever you have intended.)

Look forward to hearing from you when you have time.

Kind regards,
Randal

[el_barto]

I'm getting this error after 40min - 1h with the app open:

08-08 13:12:10.294  8504  8504 E AndroidRuntime: java.lang.RuntimeException: Unable to resume activity {appinventor.ai_lipscellplay.imobmapa_motorista_nat_logs/appinventor.ai_lipscellplay.imobmapa_motorista_nat_logs.Screen1}: java.lang.IllegalStateException: Too many receivers, total of 1000, registered for pid: 8504, callerPackage: appinventor.ai_lipscellplay.imobmapa_motorista_nat_logs

It happens when I reopen the minimized app after several times, probably when onResume is called:

08-08 13:12:10.294  8504  8504 E AndroidRuntime: 	at xyz.kumaraswamy.itoo.Itoo.onResume(Itoo.java:164)

I was careful not to restart the process:

I'm using this latest update of the extension:
Extension Version: Itoo Sky 4.4.2
Date Built: 2025-06-20

any idea what it could be?

Logs:

08-08 13:12:10.294  8504  8504 E AndroidRuntime: FATAL EXCEPTION: main
08-08 13:12:10.294  8504  8504 E AndroidRuntime: Process: appinventor.ai_lipscellplay.imobmapa_motorista_nat_logs, PID: 8504
08-08 13:12:10.294  8504  8504 E AndroidRuntime: java.lang.RuntimeException: Unable to resume activity {appinventor.ai_lipscellplay.imobmapa_motorista_nat_logs/appinventor.ai_lipscellplay.imobmapa_motorista_nat_logs.Screen1}: java.lang.IllegalStateException: Too many receivers, total of 1000, registered for pid: 8504, callerPackage: appinventor.ai_lipscellplay.imobmapa_motorista_nat_logs
08-08 13:12:10.294  8504  8504 E AndroidRuntime: 	at android.app.ActivityThread.performResumeActivity(ActivityThread.java:4798)
08-08 13:12:10.294  8504  8504 E AndroidRuntime: 	at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:4831)
08-08 13:12:10.294  8504  8504 E AndroidRuntime: 	at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:54)
08-08 13:12:10.294  8504  8504 E AndroidRuntime: 	at android.app.servertransaction.ActivityTransactionItem.execute(ActivityTransactionItem.java:45)
08-08 13:12:10.294  8504  8504 E AndroidRuntime: 	at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:176)
08-08 13:12:10.294  8504  8504 E AndroidRuntime: 	at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
08-08 13:12:10.294  8504  8504 E AndroidRuntime: 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2247)
08-08 13:12:10.294  8504  8504 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:106)
08-08 13:12:10.294  8504  8504 E AndroidRuntime: 	at android.os.Looper.loopOnce(Looper.java:201)
08-08 13:12:10.294  8504  8504 E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:288)
08-08 13:12:10.294  8504  8504 E AndroidRuntime: 	at android.app.ActivityThread.main(ActivityThread.java:7881)
08-08 13:12:10.294  8504  8504 E AndroidRuntime: 	at java.lang.reflect.Method.invoke(Native Method)
08-08 13:12:10.294  8504  8504 E AndroidRuntime: 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:568)
08-08 13:12:10.294  8504  8504 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1045)
08-08 13:12:10.294  8504  8504 E AndroidRuntime: Caused by: java.lang.IllegalStateException: Too many receivers, total of 1000, registered for pid: 8504, callerPackage: appinventor.ai_lipscellplay.imobmapa_motorista_nat_logs
08-08 13:12:10.294  8504  8504 E AndroidRuntime: 	at android.os.Parcel.createExceptionOrNull(Parcel.java:2464)
08-08 13:12:10.294  8504  8504 E AndroidRuntime: 	at android.os.Parcel.createException(Parcel.java:2440)
08-08 13:12:10.294  8504  8504 E AndroidRuntime: 	at android.os.Parcel.readException(Parcel.java:2423)
08-08 13:12:10.294  8504  8504 E AndroidRuntime: 	at android.os.Parcel.readException(Parcel.java:2365)
08-08 13:12:10.294  8504  8504 E AndroidRuntime: 	at android.app.IActivityManager$Stub$Proxy.registerReceiverWithFeature(IActivityManager.java:5601)
08-08 13:12:10.294  8504  8504 E AndroidRuntime: 	at android.app.ContextImpl.registerReceiverInternal(ContextImpl.java:1770)
08-08 13:12:10.294  8504  8504 E AndroidRuntime: 	at android.app.ContextImpl.registerReceiver(ContextImpl.java:1731)
08-08 13:12:10.294  8504  8504 E AndroidRuntime: 	at android.app.ContextImpl.registerReceiver(ContextImpl.java:1718)
08-08 13:12:10.294  8504  8504 E AndroidRuntime: 	at android.content.ContextWrapper.registerReceiver(ContextWrapper.java:732)
08-08 13:12:10.294  8504  8504 E AndroidRuntime: 	at xyz.kumaraswamy.itoo.Itoo.onResume(Itoo.java:164)
08-08 13:12:10.294  8504  8504 E AndroidRuntime: 	at com.google.appinventor.components.runtime.Form.onResume(Form.java:732)
08-08 13:12:10.294  8504  8504 E AndroidRuntime: 	at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1476)
08-08 13:12:10.294  8504  8504 E AndroidRuntime: 	at android.app.Activity.performResume(Activity.java:8190)
08-08 13:12:10.294  8504  8504 E AndroidRuntime: 	at android.app.ActivityThread.performResumeActivity(ActivityThread.java:4787)
08-08 13:12:10.294  8504  8504 E AndroidRuntime: 	... 13 more

[Taifun]

@el_barto

java.lang.IllegalStateException: Too many receivers, total of 1000

Please provide a few more relevant blocks...
What exactly are you doing in the background?

Remember, this is the same issue you mentioned here [PAID] 📍 Location Service Extension - #166 by el_barto

Taifun

[el_barto]

The application essentially monitors the status of a web request in the background. The process is called every 10 seconds.
It also sends the location in the background using its extension.

Sending location:

[Taifun]

Some observations

• in your main procedure run you forgot an evaluate but ignore result Web2
• how does the event handler webgot look like?
• in the timer event handler the 2 evaluate but ignore result blocks are obsolete
• in your OnLocationChanged event handler the evaluate but ignore result block is obsolete
• It might help to add more Notifier.LogInfo blocks into your background event handlers
• it would be great to get an error log including more information what previously happened including itoo and Notifier debug statements

Taifun

[sidrobo]

Is it possible to detect an hot word using itoo. Ex
When I say ok google google gemini. automatically opens

[Kumaraswamy]

That would require continually using the microphone, I'm not sure how Google does this, a difficult one.

[Kumaraswamy]

@Randal_Andress

I am experiencing what seems like a similar event failure in the service process with the PhoneCall component's PhoneCallStarted and PhonecallEnded events.

The first problem is that the Phone Call component is not being fully initialized (like those Firebase and CloudDB components), therefore it isn't able to receive phone call events. I manually initialized it using odd methods, and there seems to be another problem. I will look into potential fixes for the next Itoo update.

Thank for you for the report!

[Gergo_Toth]

Hi I get this erro message have any clue why?

[Kumaraswamy]

Hey, from what screen are you calling Itoo? Adding Itoo to Screen1 should solve this error.

[Randal_Andress]

@Kumaraswamy

Thank for you for the report!

You are quite welcome!

Kind regards,
Randal

FYI, the problem I am needing to solve involves an Itoo process with a Player that is sourced to a live stream of an event (eg., a sports event). By manually (using UI buttons) pausing and restarting the Player it is adjusted to be synchronized with a live video stream of the same event.

But then if a phone call is started (eg., received), the Player is automatically paused ... and then resumed when the call ends, thus adding delay to the audio stream (the length of the call) and putting it out of sync with the video.

One way to solve this is to detect the call start and then on call end to restart the Player with the already-calculated delay...thus maintaining sync with the video.