Automagic Forum

What happened to a free version of automagic ?
i cant find it on google play.

Hi,

The very outdated Automagic for Gleeo has been discontinued some years ago and is not available on Google Play anymore.

I recommend to use the free evaluation version available on our site:
http://automagic4android.com/en/evaluation

Regards,
Martin

Despite Automagic being the most useful app on my phone, i would disagree in it never falling flat. It has it's bugs.

Then again, i'm not sure which bugs are being fixed.

Having that said: Why would anyone settle with the free version of Automagic? It's VERY well worth the price.

digitalstone wrote:Despite Automagic being the most useful app on my phone, i would disagree in it never falling flat. It has it's bugs.

Then again, i'm not sure which bugs are being fixed.

Having that said: Why would anyone settle with the free version of Automagic? It's VERY well worth the price.

agreed with you there! however, from what i can see, alot of the bugs are because of the android system

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.
Whenever i use Clean Master to clean up "junk" before i reboot my phone, it's alright again.

Another bug is when the flow just refuses to run at all.
And then when i manually execute it, a small "1" within a circle will be shown at the top-right of that flow's trigger, indicating there's 1 instance already running (yet is not running).
Also, when i go out of that flow, its color is red. Indicating it's running.
It's as if the flow does indeed run, but is being stuck at the very part before the trigger itself gets the signal of being colored red.

digitalstone wrote: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.
Whenever i use Clean Master to clean up "junk" before i reboot my phone, it's alright again.

Another bug is when the flow just refuses to run at all.
And then when i manually execute it, a small "1" within a circle will be shown at the top-right of that flow's trigger, indicating there's 1 instance already running (yet is not running).
Also, when i go out of that flow, its color is red. Indicating it's running.
It's as if the flow does indeed run, but is being stuck at the very part before the trigger itself gets the signal of being colored red.

Are you keeping it activated in the background? and it is not being battery optimised?

@Autumn : I found out from this forum, that it seems the devices which tend to have compatibility problem, comes from Huawei and HTC (their stock ROM). I wonder what bug do you have with your device.

@digitalstone : It can be caused by the hardware acceleration. Try to change to software rendering at settings - workarounds.
I never use any kind of cleaner in my phone. Those tends to make more harm than the benefit. For the red trigger, what is the trigger that you use? I remember there are some triggers those have timeout after triggered. Can't remember which ones, maybe Command output.

Autumn-Leigh wrote:Are you keeping it activated in the background? and it is not being battery optimised?

I opted out of the battery optimization. And it's always active in the background.
1 flow for example, is always on, being refreshed every minute in order to get my statusbar up-to-date on the current profile on other info. And that one always works, even when waking up after sleeping for years on end.

@Desmanto I haven't thought about hardware acceleration. That just could be it.
On the other hand, without that cleaner, that bug still would be present even after a reboot.
It's strange though, i never have problems with anything. I'm using a rooted Nexus 5X here running vanilla Android. Pure as can get.
And these 2 bugs (sometimes) just pop up.
I couldn't remember exactly which flow it happened to last time (that was 2 days ago, i'm using a sieve for memory).
I'll give a yell whenever it happens again and i'll try to make a screenshot.

Desmanto wrote:@Autumn : I found out from this forum, that it seems the devices which tend to have compatibility problem, comes from Huawei and HTC (their stock ROM). I wonder what bug do you have with your device.

@digitalstone : It can be caused by the hardware acceleration. Try to change to software rendering at settings - workarounds.
I never use any kind of cleaner in my phone. Those tends to make more harm than the benefit. For the red trigger, what is the trigger that you use? I remember there are some triggers those have timeout after triggered. Can't remember which ones, maybe Command output.

I have a kangVIP custom rom, i go into my recent tasks, pull down automagic and it locks it into there, also took it off battery optimise and set notifications as priority

@digitalstone : I leave the H/W accel on since 1.34.0 and never encounter any problem. So maybe some other app is interfering with Automagic. Try to trace back the last installed app to the date you started to experience this problem.

@Autumn : I also have excluded and Whitelist Automagic from any optimization. The most important thing at my phone is I may not touch the "nuke button" aka kill all, clean RAM, clear all or any similar name in other phone. One I press this, even though Automagic is whitelisted, the accessibility still got killed and some flows will start to be broken. I am avoiding Huawei devices for a while until I can confirm that they work properly with Automagic. So if you have any bug that is not general limitation from the android, let me know. If no major bug happen, I would started to put them back into my next phone upgrade choices.