EAP version 1.25.0-dev

[kintrupf]

* when possible automatically rename references to a flow when the flow is renamed
* new button in flow editor to open referenced flows from action Execute Flows and other actions and conditions

YES! Thank you

[lailoken]

You say you've added an alternate way to set Airplane modes, I've checked, and there is still only two ways?

Did you update one of them? Or perhaps both?

Could you give a quick explanation of either way?

PS: The English help text is partly still in german. (Used Google Translate)

[Martin]

There was only one method to change the airplane mode in version 1.24. There are two methods now. Method 1 is the classical one that changes the system setting and sends an event to the system so that the change is picked up by the system. Method 2 uses an internal system service to change the airplane mode. I expect that method 2 works better on most phones.

Documentation is fixed, thanks for mentioning.

[Martin]

Version 1.25 is considered feature complete. I will concentrate on testing and fixing issues in the next days.

Changes in this update:

• fixes trigger WiFi Connected/Disconnected on Android 5
• pass variables screen_x/screen_y to clickable action of a widget displayed as an overlay
• new action Init Variable WiFi Access Point List
• bug fixes and workarounds for Android 5

Changes made some weeks in the past, but missed to add to the release notes:

• new action Init Variables Bluetooth Device List
• new action Init Variable WiFi Access Point List

Download: Automagic.apk (updated 2014-11-14)

[mathieson]

Problem with trigger in 5.0.

Whe using the "balanced (experimental)" mode in the location trigger it seems as if it does not execute ever. Could you confirm this is true?

I am upgrading to the latest version of the EAP in order to test this.

Thanks!

[Martin]

Hi,

This seems to work for me. Are you using the trigger Periodic Location Update to acquire the location? What mode are you using in system settings -> Location?
Please try to restart the device once and test again. If it still fails, could you please post the exact settings you are using in the trigger or publish an example flow that fails. Please also enable Debug log in the preferences of Automagic to see if there's some kind of error shown.

Regards,
Martin

[gollyzila]

Hi Martin,

I'm new to Automagic so I hope I'm posting in the right section. The Clear PIN action correctly clears the pin but the pin input doesn't get disabled, so when I swipe to unlock I have to enter a pin (any pin works, even blank).

Nexus 5 Android 5.0 Lollipop
EAP 1.25.0-dev Build 20141114_180512_e1ee0d9

[mathieson]

Martin,

Thanks for the reply. I have updated to the release version of android 5.0 and it does indeed work as expected. Sorry about the report. Seems the problem was in android 5.0 pre-release.

[Martin]

@mathieson: no problem, I'm glad it's working now

@gollyzila: This is a known bug of the Lollipop ROMs. To my knowledge there's no workaround available yet. Add a star to this issue if you want to get notified about changes (please only add a star but don't add a comment since everyone get's a mail about new comments).

Maybe you could build a flow that's executed with a trigger UI Event: Component focused package com.android.systemui and then execute an action Control UI: click("Enter");. Ensure that this flow is only enabled when the screen turns off and the PIN is currently not set, otherwise Automagic always executes one wrong PIN entry when the screen comes up and a real PIN is required. Disable the flow immediately after the flow was executed, otherwise Automagic might press enter in some random screens of the system.

Regards,
Martin

[gollyzila]

@gollyzila: This is a known bug of the Lollipop ROMs. To my knowledge there's no workaround available yet. Add a star to this issue if you want to get notified about changes (please only add a star but don't add a comment since everyone get's a mail about new comments).

Maybe you could build a flow that's executed with a trigger UI Event: Component focused package com.android.systemui and then execute an action Control UI: click("Enter");. Ensure that this flow is only enabled when the screen turns off and the PIN is currently not set, otherwise Automagic always executes one wrong PIN entry when the screen comes up and a real PIN is required. Disable the flow immediately after the flow was executed, otherwise Automagic might press enter in some random screens of the system.

Regards,
Martin

It works! Besides creating a global variable to keep track when the PIN is set, here's how I implemented it.