Open Source • Background Tasks: Itoo 🚀

[Randal_Andress]

@Kumaraswamy

The problem is that you are trying to pass a component to a procedure starting with ui_xxx

Ahhh... Now I understand! It is the second argument/parameter to ui_DumpItooProperties that is the problem!

In my case then, since there is no need for the argument - there is only one itoo component - I only need to eliminate the parameter and simply "hard code" ItooPlayerService into the ui_DumpItooProperties procedure, correct?

-Randal

[Randal_Andress]

@Randal_Andress

Ahhh... Now I understand! It is the second argument/parameter to ui_DumpItooProperties that is the problem!

Well... that was only part of the problem. I was also attempting to pass a label component, which (of course) failed for the same reason. Once I got that corrected it works just fine. Thanks for the help!

BTW, I did not find a way to remove an argument from a procedure without causing all its calls to have arguments removed throughout the app. Since there were several argments and several call sites, I just renamed the arguments and ignored them.

Any advice as to how to easily remove arguments from a procedure so as to cause minimum disruption at the call sites?

-Randal

[Randal_Andress]

I asked this question on the general discussion forum:

Removal of Procedure Parameter's Effect on Call Site Arguments

Is there a way to remove a parameter from a procedure so as to cause minimal disruption to the actual argument list of existing calls to the procedure? Before removal of parameter "z": [procedureParameters] After removal of parameter "z": [procedurParameters2] It seems that the actual arguments are moved down/over, beginning with the one removed, so that all those following the one removed are miss-assigned and the last one is unassigned. Is there a way to avoid this so as to require less …

Evidently there is not presently a better way...

@ewpatton

If you feel comfortable with it, you can create an feature request on our GitHub repository

I went ahead and submitted a feature request

-Randal

[Madhan_Y]

@Kumaraswamy @Taifun
I am integrating itoo extension blocks with SMS reader extension.
My project is to fetch the SMS messages from the phone and read the last received message in background when the proximity sensor is triggered (My gesture as waving over the phone).

I have cross verified that the proximity sensor is triggered perfectly in background with itoo extension.
But when I integrate the SMS reader extension with the itoo blocks, there is no response.
Kindly help me with this.
UPI.aia (115.5 KB)

[Taifun]

Did you ask for permission to read sns?
EDIT: yes, during Screen Initialize

Use logcat for debugging

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: …

Taifun

[Kumaraswamy]

Hi, we cannot provide you support for an external untested extension, it's best if @The_K_Studio is able to look into it.

[The_K_Studio]

I am not familiar with using Itoo.

[Kumaraswamy]

We cannot help you with that extension... Maybe you could use this one from @Taifun App Inventor Extensions: Texting | Pura Vida Apps. I still make no guarantees.

[Taifun]

As a start, just use logcat as suggested earlier to find out, what's going on

Btw there is also the sms receiver extension available, see here App Inventor Extensions: SMS Receiver | Pura Vida Apps, which could be helpful for receiving sms in the background... it is available for 15 USD...

Taifun

[Madhan_Y]

The default Texting component available which indicates when a message is received by using blocks such as
When message.received

Is also not working (no response) with the itoo extension.
Am i missing something during coding (blocks) or it is not supposed to work?

Help me with that

[Taifun]

Read the documentation of the texting component about the functionality it provides in the background.

http://ai2.appinventor.mit.edu/reference/components/social.html#Texting

Obviously I would not waste any time in writing a sms receiver extension if it just worked without it.

Taifun

[Kumaraswamy]

The Texting component's nature does not make it compatible with Itoo... Look at Taifun's advice.

[Madhan_Y]

This set of blocks with texting component works fine without itoo extension.
But when i want to run it in background with itoo it has no response.
According to @Taifun , if the blocks works without itoo extension, obviously it should also work with itoo, but according to @Kumaraswamy the texting component is not compatible with itoo.
If this is supposed to work, what am i missing?
Or am i limited to puravida texting extension (free) for background processes.

my app objective is to read the incomming sms, either at the instant of receiving or with a trigger to read the last sms from the phone sms history (all by free)

[Kumaraswamy]

@Madhan_Y

Or am i limited to puravida texting extension (free) for background processes.

Yes. Let us know your findings.

[renato]

As a first attempt to use the Itoo extension I wanted to send a message 'ok5' after 5 seconds followed after another 1 second by the message 'ok1'. And again in cycle ok5 and ok1. I attach the blocks that do not work. Any suggention?

[Taifun]

@Madhan_Y

According to @Taifun , if the blocks works without itoo extension, obviously it should also work with itoo

I never said this
Use an extension which was made to run in the background, which is App Inventor Extensions: SMS Receiver | Pura Vida Apps
You also can try App Inventor Extensions: Texting | Pura Vida Apps to read all received messages and extract the latest one

Taifun

[Taifun]

@renato

Any suggention?

Instead of the CreateTask method try the CreateProcess method to create a foreground process

Taifun

[Madhan_Y]

@Taifun

I would not waste any time in writing a sms receiver extension if it just worked without it.

Look at the screenshot (previous post), i am using the built in texting component and not the puravida texting component.
I was only speaking about the built in texting component (blocks) in my previous post.

Is this supposed to work (previous post)?
If yes please help me troubleshooting it.
If no then i can shift to pura vida texting extension (which is not confirmed to work in background)

[Taifun]

@Madhan_Y

I was only speaking about the built in texting component (blocks) in my previous post.

Is this supposed to work (previous post)?

No
See again the already given answers

@Taifun

Read the documentation of the texting component about the functionality it provides in the background.

http://ai2.appinventor.mit.edu/reference/components/social.html#Texting

@Kumaraswamy

The Texting component's nature does not make it compatible with Itoo

Taifun