Open Source • Background Tasks: Itoo 🚀

i cant use my clipboard to copy link somehow, its the thread number 397


this one by jerej.

yes i did that and changed the bleconnected one



i realised i needed to use the apk version of the app and not the ai companion connect one, so i found that the createprocess is working kinda okay {as the connectwithaddress block was working fine}till a certain point. the registerevents under monitorconnection are definitely NOT working still because wehn the device is connected, the bleconnect procedure that should work, doesnt? and bytes are still not being received, dont think the clock1.timer is working either. for debugging, i did try the logcat thingy, but in the powershell, the data kept on coming without a single millisecond of delay, and that confused me even more, so i dont know anymore, help
UPDATES: the doit procedure, the bleconnected AND blereceived are working now.

blocks (27)
blocks (26)
i saw the last example in the mainthread of firing an alarm whenever device is shaking and realised i had to do these too.
thank you for your help so far taifun

rather another question related to this, does the function of calling someone from the background like this not work?
Screenshot 2025-07-04 234820
and if not, then what are the alternatives of doing so? the phonecall blocks dont work, and when i try to run via activity starter, the whole app restarts completely. help
@Taifun

No
To call someone the app must be in the foreground
My alarmmanager extension among other things is able to bring the app to the foreground

Taifun

Okay thank you very much. But doesn't the createprocess of itoo bring everything to foreground too? Is it itoos limitations to do things or?

From the terminology section of the first post in rhis thread

  • We say the app is in "foreground" – meaning the app is open, being active.
  • The second meaning, we refer to "foreground" as in "foreground service" feature offered by the extension.

A foreground process does not bring the app to the foreground

Taifun

1 Like

I try to send notification using itoo,melonnotification extensions , but?

its just a time picker to set a time and when the time is gone send notification to main android screen , we have to store time picker set time to DB, to work on background forever ;
anyone can help me please



Show your relevant blocks !

You forgot the argument x in procedure BGalarm

  • For the main background procedure, you need to include an argument "x".

Also there is a spelling error...
Timer - Timier

Taifun

i change it but it still not working , i can send you aia file to make change and resend it to me
new_push_notification_modification.aia (1.5 MB)

Sorry, I'm on mobile

It would really help if you provided a screenshot of your updated relevant blocks, so we can see what you are trying to do, and where the problem may be.

To get an image of your blocks, right click in the Blocks Editor and select "Download Blocks as Image". You might want to use an image editor to crop etc. if required. Then post it here in the community.

Taifun


Trying to push the limits! Snippets, Tutorials and Extensions from Pura Vida Apps by icon24 Taifun.


i was reading and try solution for 3 day , now i miss the variable names
i thanks your help.

Your main procedure is called BGalarm

Your Timer procedure is your Clock1.Timer event handler. That procedure needs the same arguments as the Clock1.Timer event, which is none...

Aldo why are you calling your main procedure in a button click event? This does not make much sense

Taifun

And why are you asking for post notification permission in the Permission Denied event? Does this make sense? Ask it during Screen Initialize and after you got the permission create the process

Taifun

And the sequence is wrong

  • A component does not get created until you touch any of its block.

Taifun

its created when screan1 loaded



this is enhancement version.
2 time picker after time select time show in label , when press ok it send notification on time you select

It looks like you are getting creative... you now not only have an argument x in your main procedure, but also an argument y... this will cause an error as soon as itoo calls your main procedure during creating the process...

instead of y you just could use your global variable time_interval1 directly...

Also as far as I can see the second timer will overwrite the first... so you could just use one time picker...

And you are still ignoring to use the correct sequence

Taifun


its send notification in each second >>> not working well :slightly_frowning_face:

because 1 second is the default timer interval of Clock_master
you might want to set the timer interval to a large value

and why are you still not following the correct sequence? protip: Just do it correctly

  • A component does not get created until you touch any of its block.

btw. you set your global variable timer_interval1 but you never use it
usually procedure Notification is not meant to be called by someone except of itoo while creating the process...

I think it could work as you are doing it, however each new alarm will overwrite the previous one... with just one time picker it should work...

Taifun


i dont know the correct sequence , but the time master is set to disable in design , what can i do to make it work

i set time interval to procedure