Flow Opening Time

[digitalstone]

With some flows i experience a high waitingtime for it to open.
In most cases, the screen turns black (except the statusbar and 3 system buttons at the bottom) for a whole minute before it opens up.
After that, i can do everything with the flow and it runs smooth.
But i will need to go through this "waiting-process" each time i open it. Even if i 'just' came out of it.

No doubt it's a performance bug.
Is this a known issue?
And if yes: Is it being solved?

[Martin]

Hi,

I have not experienced such a huge delay when opening flows. Please try to reboot the device once to see if this helps.
Does this happen on every flow or just for some flows?

Regards,
Martin

[digitalstone]

With only some flows.
And those flows will keep that behavior for most of the time.
Sometimes it opens instantaneously.

But it definately doesn't switch around to other flows.

[Desmanto]

I never have this problem. It seem the phone goes through "soft-restart" process.

Try to disable all of the flows and open the problematic flow again. Logs are needed to check it in detail, but I don't know if the logs also include the flow opening.
If you have access to PC, you try to use adb logcat and try to open the flow which cause the problem until you get the slow opening. Then check the log.

[digitalstone]

So i had this bug again:

1 bug i come across sometimes is when i have been continuously working on a flow.
Then whenever i go back inside that flow, the screen then first turns completely black (with statusbar and 3 soft-buttons at the bottom still visible).
The screen also just hangs sometimes before the flow loads up.
The duration is usually 5 seconds, maybe 10... and in extreme cases a whole minute.

photo_2018-03-28 -halfres.jpg (8 KiB) Viewed 18682 times

It happened this time after fiddling around with a big flow (as usual when this happens).
I tried to de-activate the hardware acceleration. And wow, it got SO slow.
It was like my CPU workload capacity went down to 1% of it's original amount.
Every action and interaction inside Automagic had heavy delay on reacting. Even the back-button on Android-level) had trouble being redrawn on touch.
I think it took me near 2 minutes to close Automagic, and then to go back in order to turn on hardware acceleration.

@Desmanto I have no android studio here. Should i install that entire IDE just to do a logcat analysis?
Can't find any stand alone CMD tool.

[Desmanto]

You can try xda tutorial here : https://www.xda-developers.com/guide-se ... orite-app/
No need to install the entire SDK. If you have root, logcat extreme is one of the best choice.
It seems not the hardware acceleration problem.

How big is the flow? Does it have 100+ elements inside? I usually separate it when it reach 50+ elements.
And what is the devices that has from this problem? How long have you been using it? Some eMMC slow down can throtle the I/O speed and slowdown opening. How big is your flows.xml in /sdcard/Automagic/ ? Mine is above 1 MB already, consist of 47 active flows out of 115 flows.

[digitalstone]

The flow it happened with *this* time has around 50 elements as i was trying to improve to compress it down to 30.
Now it still happens.
But only after editing more and more on it (i think i said that earlier somewhere).

XML file is 205kB divided by 28 flows of which 14 active (lots of things yet to improve so that's why there are so many inactive).
Yet i think that tells not nearly enough since there are small and big flows, and there are reused elements (as much as possible).

I'll try to get the logcat to work.
I'm actually curious about this issue because i don't believe it's Automagic since i'm apparently the only one.
Why just why?

[Desmanto]

You need logcat to catch the problem. But the log will have so many data that really makes us tired looking at it. You might want to search for keyword "error", "exception" or "crash".

Mine is bigger and never have such problem. There is problem such as when executing update Media database, it takes so long until 5 minutes (not hang, only that action). But that is android problem, since it happened already when I am still using tasker. I am still troubleshooting it, since I only scan for one folder only /sdcard/Download/, only 10-20 files, but it always takes several minutes to complete.

I just afraid it is your phone, especially the eMMC. Do you have some similar problem with other app? You know, LG is known for its eMMC/motherboad problem, causing unrecovered bootloop. The problem is so widespread, causing a class action to them.