Ha, I did not set the property through the blocks. I keep forgetting that even a foreground process cannot access the UI.
But, it still does not work. As an app, using the timer, works. As a process, the timer procedure, I don't think executes.
Ha, I did not set the property through the blocks. I keep forgetting that even a foreground process cannot access the UI.
But, it still does not work. As an app, using the timer, works. As a process, the timer procedure, I don't think executes.
What happens if you remove the if condition and send a notification regularly to report the battery status? Does that work?
Taifun
I disabled the if condition, and have a notification. With the x variable in the timer procedure, it does not seem to work at all.
If I remove the x variable in the timer procedure as well as the if condition, the notification shows every second, even though timer interval is set to 30000.
There's one more constraint, avoid using Global variables all together, you are limited to only what happens in the procedure.
Move the property block "TimerInterval" with the value "30000" over to the procedure "timer" before the if-else condition check.
Itoo 3
This Itoo update includes a wide range of internal, and functional enhancements that improves the overall foreground and background processing
Behavior changes
Optimisation of internal Itoo framework to work efficiently
Functional stability to work seamlessly
StopProcess
and StopService
blocks are unified into a single block StopProcess
Functional changes
Added POST_NOTIFICATIONS
permission
Added a way for one way communication b/w the foreground/background services
There are a lot more changes internally :-)
but simply not relevant to know
xyz.kumaraswamy.itoo.aix (62.8 KB)
Music Player This guide showcases the use of #Itoo for creating a foreground music player application Blocks Summary [Blocks] Above is the summary of the project, the blocks inside the border are of the foreground service, i.e. they run independently (closing/reopening app would not have any affect on them) Explanation [Component 2(1)] We can categorize services into two types: background (invisible to the user) and foreground (user-visible). We've chosen to use a foreground servicβ¦
1- The "Clock test" notification can't be removed from my phone, unless I remove app.
How to make it removable ?
2- And Simple notifications created by Itoo NOT opening the app when clicked.
1- The "Clock test" notification can't be removed from my phone, unless I remove app.
That's the whole point of having a foreground notification, you would need to ask the user to supress or hide the particular channel.
2- And Simple notifications created by Itoo NOT opening the app when clicked.
You would need to use the Modified Notification Style Extension to be able to change the functionality of the notification by updating the notification.
I'm already using the Modified Notification Style Extension :
Modified version of Notification Style Extension By @Jarlissonlira2, adds support for Android >= 12 Refer to the original topic for documentation: Fork of the extension: github.com/XomaDev/NotificationStyleAIX License (MIT) and modified sources (rush): rush-compatible/notification-style [component_event(5)] [component_method(17)] [component_method(16)] New permission blocks for Android Tiramisu (for >= 33). android.permission.POST_NOTIFICATIONS Make sure to ask the permission if thβ¦
How to to change the functionality of the notification by updating the notification ?
Use the simple notification block with the id set to
123321
if you want to update Itoo's foreground notification.
What is not working?
What is not working?
Simple notifications created by Itoo NOT opening the app when clicked.
I'll check and let you know about that
I have gotta say, I am also running into the same issue I am wondering if there is a bug/regression with the last release of ltoo?
I am trying to replicate the notification example as well, and here are my observations:
Hi, thats because you cannot interact with the Visible component from Itoo.
I see what you are saying. I went ahead and added the notification extension, and using the simpleNotification now in an attempt to see some life out of the background process, but still no luck. Is there anything obviously wrong with the blocks?
Post your project .aia here, so that I can look into it.