Tasker boot delay problem

[Djefko Isov]

Hi,
Can someone tell me why Tasker start with near 20 sec delay after booting. I cant find information for that in google. Anybody talk about that if i have too many apps or if my memory is low and similar thinks. But i havent many apps on phone. Tasker is alloved to start after boot and it start but with delay. I install it on my tablet and result is same. I want tasks to start immediately after boot. There is no app to slow down device or somethink similar. I think that this is may be somethink on settings that i dont set.
I read many comments that in someones devices tasker start immediately. To test it i create task to beep after boot.Anythink on phone start and work fine without any lagging but tasker start after 20 secs and on notification says that tasker is active and than i hear beep

[Pent]

Android shows you the launcher and you think 'booting has finished', but
in the background it is still very busy starting up background
services etc. Only near the end, or maybe as last thing, does it send
signals to apps to tell them that the device has booted.

However, if you have e.g. a huge configuration file then it might take
Tasker a little longer to startup (not not 20 seconds).

Pent

[Pent]

Something else slowing things down at boot is if you have loads of media
installed that Android likes to scan at startup.

Pent

[Djefko Isov]

yes but anythink works fine after booting before starting of tasker. i can run another app or to play song or do many other thinks.
How i can make tasks to start for example when launcher start?

[Djefko Isov]

same is the situation with apps exported from tasker with app factory

[Pent]

yes but anythink works fine after booting before starting of tasker.t d

I expect the Tasker UI will launch also OK. But until it receives the signal
from Android, it doesn't know that the device has booted.

Android prioritises foreground things (play music etc) so that the user
doesn't have to wait for those things.

Pent

[Djefko Isov]

than itseems the problem is that android dont send boot signal to tasker with high priority and send it after all other  startup apps. Than maybe i have to find way do force android to send boot signal with high priority

[Djefko Isov]

o no
i try another automation app to play alert after boot
the result = they play alerts together
than the problem is on signal for boot on android

[Djefko Isov]

together after 20 secs

[Graphic]

If you don't install many apps, most phones come with pre-installed ones and run at boot wich can delay things also.

Pent, can't you specify a higher priority when booting?

Tasker loads with priority 0.

https://developer.android.com/guide/topics/manifest/intent-filter-element.html

"The value must be an integer, such as "100". Higher numbers have a higher priority. The default value is 0. The value must be greater than -1000 and less than 1000."

[Pent]

>Pent, can't you specify a higher priority when booting?

Will try, but I don't expect it to make much difference.

Pent

[Hippo Man]

I agree that it probably won't make much of a difference. I believe Android still has work to do during the boot phase, after the UI starts and before it even begins invoking apps. Therefore, even if Tasker's start-up priority is higher than that of all the other apps, there's still likely to be a delay upon boot-up before any of those apps get invoked.

But I'll be happy to be wrong about this.

.

[Graphic]

With 4.9u3, Tasker boot time improved alot so it does make a diference the priority 999 Pent set.

I have a flashlight widget and when phone boots it just shows a black rectangle, it takes awhile until it gets the text and the lamp drawing and Tasker would run exactly at this same time as the flashlight widget getting the text.

Now as soon as i enter the PIN, Tasker runs.

[Graphic]

With Autostarts in the "After Startup" apps list, Tasker was the last one on the list on my phone, so that explains why it would take so long.

Now is the 2nd.

BusyBox is 1st with a huge priority number but i guess Android will consider it as 1000 since it max allowed.

[JD]

Boot time is greatly improved. Now tasker completes my bootup scripts long before my screen even goes dim or turns off (prior to this, my screen would have turned off from idle timer before tasker did it's thing).

[Graphic]

Small correction: I wrote max priority is 1000 but in the link says "less than 1000", so it's 999.
Wich is the priority Pent set Tasker now.

[Pent]

Maybe the people seeing the improvement have something else installed with higher
priority that was taking a while previously.

In any case, as long as people are happy :-)

Pent