Re: Planned features, to-do list

[Sergio Bossa]

I would add:

*  Duplicating a flow from the main entry screen.

* Easier deletion of blocks (current drag&drop mechanism is imho quite unfriendly).

On Monday, October 13, 2014 3:14:23 AM UTC+1, Automate developer wrote:

Core features

• Flowchart zoom. (Almost ready for Alpha testing)
  
• Inter-fiber communication; global variables or some other form.
• Group list of flows.
• Warn when fiber has stopped by an error.
• Copy & paste flowchart blocks with multi-selection.

Building blocks

• Cell tower scan block.
• Calendar event query block or Calendar next event block.
• Component pick block; let user pick an app Activity, Service or Receiver.
• Component resolve; find app Activity, Service or Receiver that handles an Intent.
• Alarm next; await new/next alarm.
• Dropbox; list, download, upload, delete
  
• any upcoming requests...

Expression functions

• Value clone function
• any upcoming requests...

Alterations

• Make file picker return relative paths, instead of absolute SD card paths.
  
• Flowchart serialization without recursion, to handle large flows.

If i forgot anything that i said was coming, let me know.

[Automate developer]

• You can duplicate a flow by just import it from "Share Automate flow".
• Deletion will become easier when multi-select is implemented.
  Then you will be able to long-press and select multiple block to delete, copy or more.

[Sergio Bossa]

On Mon, Oct 13, 2014 at 12:13 PM, Automate developer
<henrik.l...@gmail.com> wrote:

> You can duplicate a flow by just import it from "Share Automate flow".

Well, exporting and importing back is rather cumbersome: I understand
this is not a priority, but an easier way to duplicate flows would be
nice to have at some point.

> Deletion will become easier when multi-select is implemented.
> Then you will be able to long-press and select multiple block to delete,
> copy or more.

Cool, thanks.

>
>
> On Monday, October 13, 2014 11:19:01 AM UTC+2, Sergio Bossa wrote:
>>
>> I would add:
>> * Duplicating a flow from the main entry screen.
>> * Easier deletion of blocks (current drag&drop mechanism is imho quite
>> unfriendly).
>

> --
> You received this message because you are subscribed to the Google Groups
> "Automate" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to automate-use...@googlegroups.com.
> To post to this group, send email to automa...@googlegroups.com.
> Visit this group at http://groups.google.com/group/automate-user.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/automate-user/bd3ce944-7307-4545-8122-b9106edb35cb%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.



--
Sergio Bossa
http://www.linkedin.com/in/sergiob

[Mark Newton]

You forgot to add building an MMS/WPA stack and corresponding MMS blocks.

[David Steele]

How about wifi nearby, so something could trigger even if you are not connected to a hotspot?

On Sunday, October 12, 2014 10:14:23 PM UTC-4, Automate developer wrote:

Core/UI features

• Flowchart zoom. (Alpha testing now)
  

• Inter-fiber communication; global variables or some other form.
• Group list of flows.
• Warn when fiber has stopped by an error.
• Copy & paste flowchart blocks with multi-selection.

Building blocks

• Cell tower scan block.
• Calendar event query block or Calendar next event block.

• Notification added
  

• Component pick block; let user pick an app Activity, Service or Receiver.
• Component resolve; find app Activity, Service or Receiver that handles an Intent.
• Alarm next; await new/next alarm.
• Dropbox; list, download, upload, delete

• MMS: incoming, send
  
• any upcoming requests...

Expression functions

• Value clone function (Alpha testing now)
  
• any upcoming requests...

Alterations

• Make file picker return relative paths, instead of absolute SD card paths. (Alpha testing now)
  

• Flowchart serialization without recursion, to handle large flows.

[Automate developer]

Use the "Wi-Fi scan" block.

[Mark Newton]

Need to add the bugfix for dateParts using 0-11 rather than 1-12 for months. I think it was mentioned before by someone. I just noticed it myself though.

[Automate developer]

I'll clearify it in the doc. But i don't want to change it since months are 0-11 in all other languages.

[Mark Newton]

Okie dokie. Good enough!

[Sergio Bossa]

Another nice feature would be to "highlight" (i.e. by flashing) the
"selected" block in a flow: that would make it easier to debug and
edit complex flows with several crossing lines, what do you think?

> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Automate" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/automate-user/8ijnwHSdkRA/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to

> automate-use...@googlegroups.com.
> To post to this group, send email to automa...@googlegroups.com.
> Visit this group at http://groups.google.com/group/automate-user.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/automate-user/fd2c3e6c-4e25-4bc4-84ad-060c21e19f6a%40googlegroups.com.

[thera...@gmail.com]

I don't see "Contact Picker" on this "to do" list.  When I create an action to allow a phone number to ring even when silenced, I get a generic box to type in the phone number, which is cool if I want a number that's not currently in the phone.  I would also expect to see a picker to link the number to a contact, so that if I update that person in Contacts, that would be reflected in the block condition.  Even if it just statically copied the number from a contact that would be nice, since I don't know the number.  That's what contacts are for!  (wink)

Perhaps I'm doing it wrong.  I did when call state is ring, yes goes to when ringing in call and I'm putting a number there.

- Rags

On Sunday, October 12, 2014 10:14:23 PM UTC-4, Automate developer wrote:

Core/UI features

• Log the reason for stopped fiber; by user, unconnected dot, failure, etc. (Ready for next release)
• End Beta and enable in-app “premium” purchase.
  
• Inter-fiber communication/persistent storage; global variables or some other form.
• Warning notification when fiber was stopped by an error.
• Group list of flows.

• Copy & paste flowchart blocks with multi-selection.

• Flowchart annotations, "Post it" notes.
• Rework flowchart serialization without recursion, to handle large flows.

Building blocks

• Mobile network; check, set
• Fiber running check
• Notification posted
• Mobile operator block, or retool the Roaming block.

• Component pick block; let user pick an app Activity, Service or Receiver.
• Component resolve; find app Activity, Service or Receiver that handles an Intent.
• Alarm next; await new/next alarm.

• All audio stream volumes;  get, set
  

• Dropbox; list, download, upload, delete

• MMS: incoming, send
  
• any upcoming requests...

Expression functions

• Sentence case
  
• any upcoming requests...

Bugs

• Minimum/Maximum labels are swapped in the layout of "Calendar event query" block. (Fixed for next release)
• Calendar event add crash. (Fixed for next release)
• Wi-Fi connected block with proceed “When changed” and without SSID and BSSID doesn't report new connections.

[Mark Newton]

Look under the content category of blocks. There's already a contact pick and contact query block.

[thera...@gmail.com]

That appears to be a manual entry block, ie, it's not a way for the flow to have a number to use from contacts, but a way for the flow to stop until I interact with it.  That's not what I mean.  Thanks though!

[Mark Newton]

The query block doesn't work that way. Only the contact pick block does.

[thera...@gmail.com]

So I set the incoming call to a variable, but I have no clue what that data is.  I assume it's a phone number, so I fed that variable into a contact query by phone number, but I get no true/false output.  Do I add yet *another* block to say see if the phone number is ""?  Or is there a simpler way?

[Mark Newton]

I'll answer in the other thread you made.

[Automate developer]

What do you mean with "selected" block?

On Tuesday, October 28, 2014 9:02:04 AM UTC+1, Sergio Bossa wrote:

Another nice feature would be to "highlight" (i.e. by flashing) the
"selected" block in a flow: that would make it easier to debug and
edit complex flows with several crossing lines, what do you think?

[Sergio Bossa]

I mean any block you touch/drag.

--
You received this message because you are subscribed to the Google Groups "Automate" group.
To unsubscribe from this group and stop receiving emails from it, send an email to automate-use...@googlegroups.com.

To post to this group, send email to automa...@googlegroups.com.
Visit this group at http://groups.google.com/group/automate-user.

To view this discussion on the web visit https://groups.google.com/d/msgid/automate-user/1bd7d9ef-45d3-4a44-b558-8104c8daf24a%40googlegroups.com.

[Automate developer]

If you tap the block for a bit longer time before you start dragging, it will become "pressed".
I'll make the block look "pressed" when it's dragged.

On Tuesday, October 28, 2014 8:48:55 PM UTC+1, Sergio Bossa wrote:

I mean any block you touch/drag.

[Sergio Bossa]

What do you mean by "look pressed"?

--

You received this message because you are subscribed to the Google Groups "Automate" group.
To unsubscribe from this group and stop receiving emails from it, send an email to automate-use...@googlegroups.com.
To post to this group, send email to automa...@googlegroups.com.
Visit this group at http://groups.google.com/group/automate-user.

To view this discussion on the web visit https://groups.google.com/d/msgid/automate-user/85c88020-f06e-49ab-86a3-8a034a4a6653%40googlegroups.com.

[Automate developer]

The block turn blue when you press it.

On Wednesday, October 29, 2014 12:14:59 AM UTC+1, Sergio Bossa wrote:

What do you mean by "look pressed"?

[Mark Newton]

I just remembered. You were going to add an image manipulation block at some point. And, if not related, it would also be nice to have an option to set the wallpaper as centered in the wallpaper set block if possible.

[keith.yo...@gmail.com]

Ability to delete an alarm set by the "add alarm" block, or if this is not possible, delete all alarms set for a specified time of day.

I was trying to create a flow that adds an alarm at 7:30am every time a calender event is found for the next day. Without the ability to delete alarms, soon there will be loads of 7:30am alarms piled up in my Clock app.

Thanks!

[Automate developer]

Android only allows alarms and timers to be set, not removed:
https://developer.android.com/reference/android/provider/AlarmClock.html#ACTION_SET_ALARM

Any work around for this will be near impossible, since the Clock app varies with Android version, phone manufacturer, etc.

Create your own alarm clock using the "Time await" and "Sound play" blocks.

[keith.yo...@gmail.com]

Hi Developer,

I read your link where it says if an identical alarm exists, the action will only activate the existing alarm, not create a new one. This is exactly what I wanted -> problem solved!

Thanks for developing Automate. Flexible, not hard to use, and good-looking interface!

[w.kind...@googlemail.com]

Any idea, when this feature will be realized?

• Cross-device messaging, send & receive using GCM
  

[Automate developer]

I will not add any more features, with potential bugs, until i've released version 1.0.
Once version 1.0 has been released i'll continue to work off the to-do list.

My plan is to release version 1.0 before december. So the messaging may be ready in early to mid december.

[Automate developer]

Forgot. Use PushBullet until then, it can be used as a plug-in.

[pete....@gmail.com]

Hi,

Only thing I would like to request is that the tasker/locale plugin blocks are moved to their own separate section.

That would make them easier to find.

Pete

On Monday, 13 October 2014 03:14:23 UTC+1, Automate developer wrote:

Core/UI features

• End Beta and enable in-app “premium” purchase.
  

• Inter-fiber communication/persistent storage; global variables or some other form.

• Copy & paste flowchart blocks with multi-selection.

• Warning notification when fiber stops by error.
• Rework flowchart serialization without recursion, to handle large flows.
• Group list of flows.
• Improve flowchart connection drawing; separate parallel lines, "jumps" over crossing lines, rounded corners

• Flowchart annotations, "Post it" notes.

• Custom widget and activity layout editor, and related event blocks.
  

Building blocks

• Add offset period to Calendar event query

• Mobile operator block, or retool the Roaming block.

• Database; insert, delete, query
• CPU control, for over/under clocking
• Network traffic get
  

• Cross-device messaging, send & receive using GCM

• Alarm next; await new/next alarm.

• Image manipulation block; rotate, scale, crop, effect etc,.

• All audio stream volumes;  get, set
  

• Dropbox; list, download, upload, delete

• MMS: incoming, send
• Vibrate settings; get, set for notification and ringer — the API is deprecated, and does nothing, i’ve tested.
  
• Set mobile network (2g/3g) — impossible without signing an add-on app with system signature, requiring special installation method.
  
• any upcoming requests...

Expression functions

• Sentence case
  
• any upcoming requests...

Bugs

• no bugs?
  

[Mark Newton]

I bought your app! I had to support your work after all this time and especially considering how great an application Automate is. I have a strange question though, is the update an alpha build or the full build? I tried to re-update my review on google play and it wouldn't let me. Said something about using a test version or not being able to post reviews with test versions of apps.

[Automate developer]

It's the full build, but i've currently only published version 1.0 to the alpha users, to see that the premium purchase/check are working correctly.
I'll start a staggered release, of the same version, to the rest of the users tomorrow,

[abin mn]

Please add a most downloaded section to the community tab as many people doesn't rate the flows on the community. If the most downloaded is added people may find new flows easier.

[Automate developer]

I could rename the "top rated" tab to just "top flows" and include the number of downloads into the ranking algorithm for the "top flow" list.

The problem with download count is that, currently i don't store who downloaded a flow, it's just a counter that's incremented when the flow is downloaded.
I would also have to register every download, so the ranking couldn't be so easily cheated.

But since users don't rate flow it will probably have to be done.
I'll do it when i finish the web version, it still needs a category list, search and list flows.

[Mark Newton]

Personally, Id rather see Most Downloaded over Top Rated. Specifically because people seem to have found out they can abuse it by rating their own flows with 5. You can find new flows by going to Top New. Still, the top rated thing isn't really a big deal.

Edit: lol. I seem to have a knack for responding right after the developer. His idea is a great compromise and better than the current system. I think everyone would be happier with that setup. Particularly because of what I mentioned above.

[Automate developer]

Try including a link to the community page in the description of your flows, to see if that gets users to rate your flows. Use the share button "Copy to clipboard" to get the link.
If that gets users rating, i could instead add a rate button directly on the "flow details" page, so users dont have to go to the community to find and rate it there.

On Tuesday, December 30, 2014 3:14:32 AM UTC+1, abin mn wrote:

[1yai...@gmail.com]

Can you add a Cell ID block?

http://developer.android.com/reference/android/telephony/gsm/GsmCellLocation.html

[Automate developer]

Use the "Cell tower near" block, or do you need some other cell id functionality?

[abin mn]

You told that you will be adding an accelerometer gesture when we communicated via email. And there is no sign about it.

[Automate developer]

Added. It will probably become a "Device motion gesture" block that will include shake, etc.

[Automate developer]

Added. It will probably become a "Device motion gesture" block that will include shake, etc.

On Sunday, January 18, 2015 at 6:57:35 AM UTC+1, abin mn wrote:

[Robert Duić]

I was happy user of Sip Switch Widget but with introduction of Android 5.0 Lollipop widget stops running because Google changed the API for SIP settings.

This widget has two buttons: the left one gives you a shortcut to the SIP settings. The second one allows you to select how calls should be routed primarily: you can select whether all calls should be made via SIP by default, only Internet calls via SIP, or if you want to be asked before each call.

Therefore I was thinking to re-create Sip Switch Widget functionality with Automate, but lack of SIP control block stops me.

Please consider to add SIP controls block. I hope it will not require root

P.S. I adore new Copy/Paste functionality introduced in 1.05v!

[Automate developer]

Looking at the source for the widget, you can probably do it without a dedicated block.

To route calls use the System settings block:
Category: Global
Name: sip_call_options
Value: SIP_ALWAYS, SIP_ADDRESS_ONLY or SIP_ASK_ME_EACH_TIME

To start the settings use the App start block:
Package: com.android.phone
Class (lollipop): com.android.phone.settings.PhoneAccountSettingsActivity
Class (pre lollipop): com.android.phone.sip.SipSettings

[Robert Duić]

Unfortunately, it seems, root is required to start com.android.phone.settings.PhoneAccountSettingsActivity

[Automate developer]

The Activity is part of the Phone app, and not the Android OS, so that's not surprising.

[Viggo Jorgen]

What about screenshot and screen record blocks?

[Automate developer]

Screenshots can easily be taken using the SU shell command "screencap", so it has low priority. But i'll add it to the "to do" list.
Screen recording may be difficult, i don't know if there's any built-in way of doing it, implementing encoding won't be easy.

[Viggo Jorgen]

Since KitKat screen recording is native system feature, just like screenshots, so I believe such things as encoding are already covered by Android itself

[Automate developer]

Okay, good to know, i'll investigate.

[Nnyan]

I've done some searching and was able to find some items that I had on my list so I took them off, but these I didn't find so excuse me if they are known.  I've been playing with a dozen or so automation apps and for the last day or two I've been playing with Automate.  I've been trying to do the same thing on all of them (basically enable Air Plane Mode when you have no connection or a bad one, see if there is available wifi or if you are in a known area and connect.  Otherwise disable radios when screen is off, scan for available connections (wifi then cellular) when screen is on, and connect and sync every 10 minutes when screen is off.  Ignore power saving when connected to power.

I've include a screen shot of one of my attempts at this (I've only maybe fixed 1/10th of the issues and I don't really have a grasp on how the forks work so that was just playing around.  This also launched 111 fibers, issues, etc...  but it was just in the initial stages I just put it in so you can see what I'm trying to do (and do it badly).  

I do have some suggestions (again I hope I'm not being redundant):

1. Not have connection lines merge but link together side by side.  It would make it so much easier to trace.

2. Function to renumber blocks based on pattern.

3. Lock connections (unlock by ex. long press).  It's too easy when doing this (at least on a phone) to accidentally delete or move things if you don't notice the undo.

4. Air Plane Mode radios.  Allow you to select which APM radios will be affected when you turn on/off APM.

5. Connection Wait.  For any connection based action let that action wait until connected before proceeding.

6. Connection Not Available.  Same as above but can determine if there is a known/any connection (cell, wifi, etc...) available.

7. Signal Strength.  Let you do actions based on bad connections (treat as no connections).

8. Block Inputs Multiple Actions.  Give the inputs of any blocks the flexibility to handle the first flow and any other additional flows that hit it different.  EX.  First time proceed immediately, 2nd+ wait for status change.

9. Monitor function.  For my flow allowing any block to wait for change doesn't seem to work (at least how i'm using it remember i'm a complete noob).  Would be nice to have the ability to monitor changes in Wifi, Celluar, etc... and based on how it changes (on/off/no connection/bad connection/etc...) trigger a flow.

10.  Partial Test Function.  Select "Test" Click on a flow path by clicking the blocks (in my example, 1,2,3,15,16,18,20,19) and test as if your phone was in that configuration. Or a function to test all paths.

Anyway just my thoughts after playing around with this all day yesterday.  Thank you.

[Automate developer]

If you using 111 fibers there's something wrong, a flow should only require one fiber for each "When ..." block (trigger), and maybe some extra to perform asynchronous operation, like network, file etc, without blocking a "parent" fiber.
A path coming out of a "forked" sub-flow should never loop back to a block before the Fork.

The suggestions:
1. It's on the "to do" list. Will take some time since it's not an easy task, the algorithm for it will be a pain to implement.
2. Sorry but the block id's are, and will remain immutable, since they are referenced from other blocks and saved in home screen shortcuts etc.
3. Use the "move" lock option show in the menu when the tool "drawer" is open.
4. You can use the System settings block with name "Air plane mode radios" to change the affected radios, but can add a dedicated block for it.
5. For now i've taken the decision not include such an option to every network related block since it would duplicate a lot of code, it would also make the blocks perform multiple "functions". And for which network should it wait, Wi-Fi, Mobile, any? or should all the blocks also include a network selection option? as said, a lot of duplicate code and additional block options.
6. The Network connected block should be usable for that.
7. For the mobile network use the Cell signal strength block, but i'll add a Wi-Fi signal strength block too.
8. I've also thought about a this problem, a way to reduce the number of blocks needed. I'am evaluating if storing the number of execution and adding an "proceed" option for "First immediately, then When changed" to every intermittent (decision) block. One problem is that the "input arguments" may have changed for the second execution.
9. You have to create the "trigger" yourself using a Fork and then the appropriate network block.
10. Just add an extra Flow beginning block, and drag a path the first block you want to test. When your done testing the partial flow, remove the beginning block again. It's impossible to add a "test" button to a block since the variables aren't correct until the full flow has run.

[gprs...@gmail.com]

We have the ability to start other flows with the Flow Start block. It would be handy to have the ability to stop another flow too.

[gprs...@gmail.com]

Having the ability to exit without saving would be nice

[Automate developer]

The can already be done adding a additional Flow beginning block to the flow that should be stopped and then starting that block from the stopping flow.

But can add a Flow URI field to the Flow stop block, so it can be used to stop other flows as well.

[Automate developer]

I've decided not to do it that way, since most apps always saves the content your currently working on, see the Gmail, Calendar app, etc.

And since Automate has "undo" it's not really needed either.

[man...@gmail.com]

As to UI, it would be handy to have searchable 'pick activity' list

[gprs...@gmail.com]

Yep, adding the Flow URI would be helpful. It would allow for more modular structures containing flows that loop or otherwise need to be programmatically stopped.

Thanks

[gprs...@gmail.com]

I can't disagree. This makes it manly like Linux where rm -f means rm -f :)

The level of kludge one can achieve, all the while blissfully unaware, is surprisingly high though :) Enter the three rules of computing; backup, backup,and backup again.

[Automate developer]

I'll add a search field to the Activity picker dialog.

[rocks...@gmail.com]

-Awesome, the Fiber Stop block will solve many of my problems.  Thanks for enlightening me to yet another well thought feature.

-I don't seem to have a Fiber Running block though I think you meant Fiber Stopped? block which has the same effect. Perfect.

-I still think there is merit in being able to control blocks that wait for state changes.  For instance When at location could be forced to proceed to either it's yes or no connector.  This would allow for override conditions in other fibers.

-I see what you mean about "live" blocks.  Perhaps a better way to describe it is active blocks.  Consider a flow with several fibers and many conditional blocks.  The logs will advance with the most active fiber leaving the fibers that are waiting for state change in the dust as far as the logs go.  I see that stopping the flow logs the active blocks that are stopped.  Just might be helpful in debugging if you can see it in action.

-have you considered the ability to roll flows into apk's?  This might be super cool or potentially problematic.

-How does one gain access to the alpha's?  I'd love to try the Variable Give/Take blocks as I just ran into variable problems.

Re: [Automate] Re: Global variables

-In addition to starting and stopping other flows from inside a different flow, it would be sensible to be able to check the state of other flows. 

-how about those "when" blocks? Perhaps we could check state, force stop, and force go? E.G. I created a fiber using Mark Newton's Speak Caller ± VCommands which uses a "when ringing in call" block.   I only want this fiber used when I'm not at the office but once the fiber is started and waiting for an incoming call, I have no way of stopping it. This might be resolved by breaking the fiber out to its own flow once we can control other flows but I suspect there is still value in controlling blocks waiting for state changes. 

-could the current live blocks be shown along with the active fiber count? In multi fiber flows it can be easy to lose track of which fibers are where. 

-maybe an option to search for blocks? I know I need to adjust block 132 based on the log but where was that block again? 

Thanks again for such an outstanding app. I was happy to make the purchase in support of the effort.

You can check the if another flow is running with the Fiber running block, but only if you're using it from the flow that started it, since it can get the Fiber URI of the started flow. Same goes for stopping it with the Fiber stop block.

I got plans on adding a Flow URI field to the Flow stop block, so it also can be used to stop all fiber of another flow.

Every block, directly or indirectly connected to the started Flow beginning block of a running flow should be considered "live".

Block search, by id, sounds great, i'll add it.

[Automate developer]

Yes the block called Fiber stopped, not Fiber running.

Do you want to force a block to proceed to YES/NO from another fiber/flow?
The problem with forcing a block to proceed is that it's impossible to assign the correct/expected values to the output variables, leaving the fiber in an unexpected/invalid state.

I know Tasker has the ability to package its automations into an APK. Are the created APKs self-contained, or do they still requires Tasker to be installed?
It wouldn't be that difficulty to implements, if the Automate app was still required, it could just read the flow from the APK.
But i don't really see such a feature adding much, flows are already easy to share, either from a personal webpage, as an email attachment, or using the in-app community.

You can join the alpha here: https://groups.google.com/forum/#!topic/automate-alpha/OW8VPRYQVsQ

[rocks...@gmail.com]

Hmmm....I see the difficulty with the output variables.  Too bad, this could have been useful.  I don't suppose it would be possible to set the variables within the override block (which leads back to the global variable thread) if the scope of the "global" variables is at the flow level.  I'm honestly not sure the implications of this sort of variable scope would be.

Perhaps users could post apk's of their flows with links back to Automate to allow for further customization.  I guess the only benefit here is that the flows could be made more widely available in the Play Store.  Maybe a mandatory link in the app somewhere or in the Play Store that lead back to Automate?  Dunno.

thanks,

Dean

[Automate developer]

The new Variables give and Variables take blocks are used to update variables in another fiber, but they must be in the same flow.

Seems like the Tasker App Factory does not require Tasker to be installed.
I may implement this in the future, when Automate becomes more feature complete, and stable. Since such user created apps couldn't be update by me when i fix bugs.

[w.kind...@googlemail.com]

Wake-on-Lan-Block

Is it a planned feature or difficult to programm to have a block that is waiting for the 'magic paket' on the interface.

[Automate developer]

It's not on the list, but i plan on adding it. But it will probably only work for sending Wake-on-LAN packages, and not to wake the phone/tablet.
I'll start working on it.

[w.kind...@googlemail.com]

It can not completely wake the phone, but if the WLAN is connected phones and tablet are always listening on that interface for push mail and so on. Sending a 'magic paket' from another device could trigger some events in the tablet.

[wowbu...@gmail.com]

Any chance you could add a "rename" option to blocks? For instance, on a start flow it only shows the URI once one is chosen, which can get confusing if you have multiple start/stop flow blocks in a flow. Or possibly, show the name of the chosen flow instead of the URI?

[Automate developer]

I've got the request to show the flow title instead of the flow URI in the block captions before. I'll begin working of it.

[nicki...@gmail.com]

An useful building block should be "Find Flow by Name". Because the Start Flow block requires the flow id.

Building blocks:

- Find Flow by name

[Automate developer]

Could you give me a use case for it?

There's a lot of problems in using the name to find a flow, the flow could have been renamed, duplicate flows with the same name, etc.
It could easily result in the wrong flow being unintentionally started.

[Nicola Inchingolo]

This is my use case:

I have two Flows:

Morning

Night

When disconnected to power source in the morning i want to start the first statement in the flow named Morning.

When connected to power source in the night i want to start the first statement in the flow named Night

If i have different installations the flows named Morning have different ids.

Bye

[Automate developer]

Yes, the same flow on different devices will likely have different Flow URIs ("id").

If you're going to share it, don't separate it into different flows. Instead include the Morning and Night into a single flow with different Flow beginning blocks.
The Flow start block accept relative Flow URIs (i.e "statements/1", without any flow "id") if you pick a Flow beginning block in the same flow.

On Thursday, May 14, 2015 at 2:57:29 PM UTC+2, Nicola Inchingolo wrote:

This is my use case:

I have two Flows:

Morning

Night

When disconnected to power source in the morning i want to start the first statement in the flow named Morning.

When connected to power source in the night i want to start the first statement in the flow named Night

If i have different installations the flows named Morning have different ids.

Bye

[Nicola Inchingolo]

Ok, you're right! Thanks.

[teiqu...@gmail.com]

At system startup, there could have a delay before starting Automate fibers;

but... this delay could optionally be only to new fibers, so would help on countering malicious ones (not that I have seen any, this is just an idea).

Also, we could alternatively have to click OK somewhere to allow Automate begin.

And more smartly, if two reboots happens subsequently (in less than 2 minutes), Automate could simply stop running and inform it up.

Interestingly enough I am almost sure we could code this on Automate, just disabling the default auto-start on boot up and coding a fiber to do that, and auto start that fiber from a shortcut.

On Sunday, October 12, 2014 at 11:14:23 PM UTC-3, Automate developer wrote:

Core/UI features

• Inter-fiber communication/persistent storage; global variables or some other form. (work in progress)
  
• Android Wear support for the Dialog confirm, Dialog choice and Speech recognition blocks (work in progress)
  
• Add last modified date to local flows database, and warn when uploading/updating a newer community flow.
  
• Warning notification when fiber stops by error.
• Rework flowchart serialization without recursion, to handle large flows.
• Group list of flows.
• Show flow title instead of URI in block caption.
  
• Improve flowchart connection drawing; separate parallel lines, "jumps" over crossing lines
  
• Flowchart annotations, "Post it" notes.
• Custom widget and activity layout editor, and related event blocks.
  

Building blocks

• Account generic add (in alpha)
• App pick (in alpha)
• Media playing with meta-data output variables (in alpha)
• Media tags read (in alpha)
• Wi-Fi signal strength (ready for alpha)
• Timer add (ready for alpha)
  
• Cross-device messaging, send & receive using GCM (work in progress)
• Image manipulation; rotate, scale, crop, effect etc,. (work in progress)
• Email/Gmail incoming (work in progress)
• Audio player control: add seek command
• Magnetic sensor
• File copy/move, Google Drive/FTP upload; argument whether to overwrite (older) files
• FTP: make dir, move, get/set file stats
• Google Drive; make dir, move, set/set file stats, change event
• Database; insert, delete, query
• Modify Network connected or add a custom function for device MAC address.
• Screen record
  
• Record video
  
• All audio stream volumes;  get, set
  
• Dropbox; list, download, upload, delete
• MMS: incoming, send
• VPN
• Philips Hue set light
• Support Xperia light bar: https://groups.google.com/d/msg/automate-user/mljnzXEi6JA/g2Uu0q1onicJ
• Samsung pen inserted
  
• Vibrate settings; get, set for notification and ringer — the API is deprecated, and does nothing, i’ve tested.
  
• any upcoming requests...

Expression functions

• Sentence case
  
• any upcoming requests...

Bugs

• Location at block never seems to work a 100%. Please report your issues.
  
• Bluetooth SCO block seems to be difficult to keep enabled. Need more information, please report your issues.
  

If i forgot anything that i said was coming, let me know.

[Automate developer]

Fiber can be used for a lot of things, and are often short lived so delaying them would make Automate very slow. They aren't a problem, even in a malicious flow.

If you don't want Automate to run on boot, just disable the "Run on system startup" option in settings, you should then have to start Automate manually with a tap on the launcher icon, that very much like an OK button

I may implement additional security checks if i find any cause for it, including a "not to often reboot" check.

[Mark Newton]

Can you make the flow properties editor show the okay and cancel buttons no matter how big the description is? As it stands now after the description gets so long the buttons seem to disappear under the description box.

[Mark Newton]

Also, maybe a timeout variable to the dialog choice blocks. That way a person can program a flow to stop if the timeout was reached. It could still flow through the no connection, but then an expression block could be used to check for a timeout if wanted.

[Automate developer]

It's a bug, i'll fix it.

[Automate developer]

I'll investigate if it's possible. It must work for all dialogs and pick blocks, since they all work the same way.

[Automate developer]

Obsolete locked thread, please see:
https://groups.google.com/d/topic/automate-user/ieFxvzSiWkA/discussion

Core/UI features

• Community
• List and search flows by user
• Reply to review
• Group list of flows, sort by running, start/stop group from list
• Binary data type for use with raw socket protocols
  
• Android Wear support;
  
  • Stage 1: Speech recognition block
  • Stage 2: All blocks? (will require major internal refactoring to facilitate remote block execution on a Wear device)
    
• Option to not restart a flow after reboot.
• Enumerate duplicate flow titles.
  
• Save title & description in flow export.
  
• Save screen position in flow.
• Export flow as image or PDF.
• Export/import flow as "source code"
• Move lock: persist as setting or in flow
  
• Move multiple selected blocks.
• Block selection mode
• remove connections (disconnect)
  
• Confirm back tap in block editor.
• Mark/sort/hide block by feature/root usage.
  

• Rework flowchart serialization without recursion, to handle large flows.

• Compile special edition as Chrome "ARC welder" plug-in to run on PC.
  
• Custom layout editor for use with widgets, notifications and possibly activities.
• Filter block list on availability; root, system feature
  
• Nested sub-flows inside a "folder" or container within the flowchart, like a Russian doll.
• Improve flowchart connection drawing; separate parallel lines, "jumps" over crossing lines.
  
• Flowchart annotations ("Post it" notes) and/or block coloring.
  
• Debugger, break points, stepping execution, variable values, etc.
  
• Add last modified date to local flows database, and warn when uploading/updating a older flow.

• Show flow title instead of URI in block caption.

• Rearrangeable connector dots?
• Material design
  
• Dark theme, with setting to choose.
  
• Create app APK from flow.
• Automatic flowchart block rearrange/layout.
  

Building blocks

• Date/Time pick: Use calendar/clock pickers (ready for Alpha)
  
• Multi-SIM support (currently partial, will be improved as the Android APIs evolve)
• Image manipulation; rotate, scale, crop, effect, etc. (work in progress)
• Email / Gmail incoming (work in progress)
• Pick block: add pre-populate value where possible (work in progress)
• Notification posted: notification id argument
  
• Wi-FI connected: capabilities output variable
• Screen brightness: add min and max input arguments for "adjustment"
• Number pick: SeekBar, RatingBar and NumberPicker styles.
  
• Data usage: Use public Marshmallow API: http://developer.android.com/reference/android/app/usage/NetworkStatsManager.html
• App usage: http://developer.android.com/reference/android/app/usage/UsageStatsManager.html
• Quick setting tile, unofficially supported in Marshmallow, official support in Android N and CyanogenMod: https://medium.com/@kcoppock/android-m-what-s-that-broadcast-tile-for-d1cd3a477a5f#.n22j1hi6k
• App network policy set: https://github.com/android/platform_frameworks_base/blob/master/core/java/android/net/INetworkPolicyManager.aidl#L33
  
• USB mass storage/MTP set state
  
• Notification show: add progress bar percentage
  
• E-mail/Gmail send/compose and MMS send: multiple attachments
• Add way to distinguish timeouts and cancel of dialog and pick blocks
• Chromecast/MediaRoute control: https://github.com/KevinDyer/Chromecast-PlaySpace/blob/master/DemoCastPlayer/src/com/google/android/gms/cast/samples/democastplayer/MrpCastPlayerActivity.java
  
• Raise/throw failure
  
• Vibrate: play/preview preset pattern
• Bluetooth device connected: major device class (input argument)
• Mobile operator set: https://github.com/android/platform_frameworks_base/blob/marshmallow-release/telephony/java/android/telephony/TelephonyManager.java#L3564
  
• Wired headset plugged: microphone input argument
• Notification show: proceed "When tapped"
• Speech recognition: mute audio during record
• Notification policy: http://developer.android.com/reference/android/app/NotificationManager.html#setNotificationPolicy%28android.app.NotificationManager.Policy%29
  
• Flow stopped/running: with fiber count output variable
• Screen gestures
• Lock screen welcome message set
  
• Variables give: add proceed "When enqueued", a slot has become empty instead of failing
  
• HTTP request: network interface input argument
  
• MMS incoming
• Roaming set state
• Location pick: satellite view
• Satellite info get
  
• Bluetooth message send/receive
  
• Interact raw (Input event send): with "event recorder" dialog, etc.
• Ping: throw exception on error
  
• Device locked: add lock type output variable: http://stackoverflow.com/questions/7768879/check-whether-lock-was-enabled-or-not
  
• File exists: calculate directory size
• System setting get/set: filter settings for category, or vice versa

• Audio player control: add seek command

• Media tags write
  
• Generic network events for Ethernet, etc.. possible?
  
• USB OTG: safe eject
• Google Tasks API
  
• Google Spreadsheet API
• Call state: investigate http://stackoverflow.com/a/29490832/445360
  
• Mobile radio? + Mobile radio state set
• Bluetooth file transfer
  
• FTP upload/download; "only copy newer files" option input argument
  
• FTP: support SFTP, move, get/set file stats
• SMB/CIFS: copy, move, delete, list
  
• Google Drive; read text, move, set/set file stats
  
• Database; insert, delete, query
• Log append: custom log levels and colors
• Screen record
• Service stop: any benefits beyond App kill background?
  
• Service running
• Toast clear
  
• Zip: encryption support
• Calendar event get: return attendees
  
• Calendar: edit, add reminder
• Contacts; query for multiple result, edit
  
• Dropbox, OneDrive, AmazonCloudDrive; list, download, upload, delete
• Tone to file: generate WAV file of waveform
• Telegram API
• Speech recognition: engine argument (likely useless since there's no alternative engines available?)
  
• Quiet: suppress sound/vibrate in subsequent blocks (should not longer be an issue since an Timeout no longer play sound/vibrate)
  
• Screen turn off: impossible with public API, find a root way

• Support Xperia light bar: https://groups.google.com/d/msg/automate-user/mljnzXEi6JA/g2Uu0q1onicJ
• Samsung pen inserted

• Now on Tap: https://android.googlesource.com/platform/frameworks/base/+/android-5.0.1_r1/tests/VoiceInteraction — signature permission required
  
• Motion gesture: add tolerance input argument (not possible with the current algorithm, other improvements done instead)
  
• Time set — would see little use, easily done with Shell command block
  
• Philips Hue/LIFX set light — no interest from manufacturers, can be done with HTTP request block
  
• Vibrate settings; get, set for notification and ringer — API is deprecated, does nothing
  
• any upcoming requests...

Expression functions

• Sentence case
  
• any upcoming requests...

Known/confirmed issues

• Reschedule alarms for Time await and Time window when time or timezone change
• Stop/Stop all has difficulty stopping infinite-looping/runaway flows.
  
• SMS send: no error but doesn't send messages, NullPointerException for PackageInfo.packageName on some devices
• SMS/MMS/Call rate limiters too strict when rebooting.
• App in foreground block doesn't work in immersive mode.
• Bluetooth SCO block seems difficult to keep enabled. Need more information, please report your issues.

Reported/uninspected issues

• Calendar event query: Begin/end timestamp of "all day" events always in UTC?
  
• Media button: override may fail at start of playback for some players on Lollipop?
• Screen orientation set: not working on CyenogenMod 5.1.1?
  
• Bluetooth device connected: BT disabled reported as disconnect even is no device is connected?
  
• Call incoming: missed not working?
• Wi-Fi connect: doesn't handle open networks which require web/form login, used by hotels etc.
  
• Investigate why NFC "any" tags aren't working?
• Investigate Bluetooth device connected not resulting in NO when Bluetooth is disabled?
• Screen lock set state: secure not working on 5.0.2?
• Wi-Fi connected: not working for static IP on Android 5.1?

[sumonesu...@gmail.com]

Don't know if this is currently available, but a block to toggle T-Mobile wifi calling would be great.

[Automate developer]

Can find the forum post, discussed before. But i recall it couldn't be done because it was handled within an third-party app (T-mobile?) and not by the Android system.

[k2...@null.net]

A quick way to make this easier to read/edit might just be to alter the color of connections for the last box selected, or alternatively the last block held on (when you start a multi-selection, if only one block is selected, highlight the in/out connections, until they get to what they connect to.

Wouldn't help with lines crossing, but would be the quickest 'fix' I could imagine to distinguish what connects where, if there is confusion.

On Sunday, October 12, 2014 at 9:14:23 PM UTC-5, Automate developer wrote:

Core/UI features

[Automate developer]

Yes I'll could make the connection colors more saturated or maybe animated, for the selected blocks in the selection "mode". I'll do some tests to see which makes them most visible.

[PC]

Can I request Microsoft OneDrive support, please (just like Google Drive/Dropbox, etc)?

Thanks in advance...

[lee.d...@gmail.com]

In general, a way to interact with current alarms would be nice.

[Automate developer]

Android provide no way for apps to access alarms, except adding new ones.
There's no standard, so "alarm clock" app are forced to manage alarm in their own way.

[ist...@gmail.com]

Is it possible make the block id more visible? Maybe by putting it in the caption when you edit it?

Many thanks for this great app.

[Automate developer]

Sure, i can make it more prominent. If you need to find a block use the Goto menu.

[miroslav...@gmail.com]

Hi, just an idea - what about touchscreen only input - e.g. wake up of the device by double tap on turned off screen (LG style)?

Regards,

Miro

p.s. Keep on excellent work!

[Automate developer]

Sadly, cool features like that requires manufacturer/hardware support.

[Viggo Jorgen]

Maybe UI lock with password? Since Automate can contain vulnerable data or can be used in malicious way this could be helpful. Sorry if it was discussed before, I haven't been here for a long time

[Automate developer]

Apps which use password to start/open only provide a false sense of security. If a person with malicious intent gets hold of your device they'll probably install or use other tools/apps with more damage potential.
Android 5 comes with screen pinning, which can be used to constrain a guest user (kids) to a single app.

[Usama Ejaz]

How about a server-side user(login) system, for just syncing settings/purchase etc ? :(

On Monday, October 13, 2014 at 7:14:23 AM UTC+5, Automate developer wrote:

Core/UI features

• Add link to community page in flow details (in alpha now)
  
• Android Wear support;
  
  • Stage 1: Dialog choice, Dialog input and Speech recognition blocks (work in progress)
  • stage 2: All blocks? (will require major internal refactoring to facilitate remote block execution on a Wear device)
    
• Add last modified date to local flows database, and warn when uploading/updating a newer community flow.
• Multi-SIM support: new "subscription" picker block, add "subscription" field to affected blocks
  
• Move multiple selected blocks
  
• Group list of flows, sort by running, start/stop directory from list.
  

• Rework flowchart serialization without recursion, to handle large flows.

• Improve flowchart connection drawing; separate parallel lines, "jumps" over crossing lines
  
• Flowchart annotations, "Post it" notes.

• Show flow title instead of URI in block caption.

• Custom widget and activity layout editor, and related event blocks.

• Rearrangeable connector dots?

• Create app APK from flow.
  

Building blocks

• Failure catch (in alpha now)
  
• Media store remove (in alpha now)
  
• File list: add recursive input argument (in alpha now)
• Cross-device messaging, send & receive using GCM (in alpha now)

• Image manipulation; rotate, scale, crop, effect etc,. (work in progress)
• Email/Gmail incoming (work in progress)

• Sub-routines: a way of calling a sub-flow that returns a result
  
• Weather: "use daily forecast" input variable
  
• SMS received: join split messages
  

• File exists: calculate directory size

• Notification show: add proceed "When tapped"?
  
• Notification posted: add an "additional texts" output variable with all big/inbox style texts.

• Mobile radio? + Mobile radio state set

• MMS incoming
• Add way to distinguish timeouts and cancel of dialog and pick blocks.
  

• Audio player control: add seek command

• File copy/move, Google Drive/FTP upload; argument whether to overwrite (older) file

• Documents: copy, move, delete (only way to write to secondary external storage, i.e. removable SD cards)
  
• FTP: move, get/set file stats
• Google Drive; move, set/set file stats
• Database; insert, delete, query
• Log append: custom log levels and colors.

• Modify Network connected or add a custom function for device MAC address.
• Screen record

• Screen turn off: impossible with public API, find a root way-
  
• Record video
• Service running
  

• Calendar: edit, add reminder
• Contacts; query for multiple result, edit
  

• Dropbox; list, download, upload, delete

• OneDrive; list, download, upload, delete
• Time set: little use, easy to do as a shell command
  

• All audio stream volumes;  get, set

• VPN
• Philips Hue/LIFX set light

• Support Xperia light bar: https://groups.google.com/d/msg/automate-user/mljnzXEi6JA/g2Uu0q1onicJ
• Samsung pen inserted
  

• Vibrate settings; get, set for notification and ringer — the API is deprecated, and does nothing, i’ve tested.
  

• any upcoming requests...

Expression functions

• Sentence case
  
• any upcoming requests...

Bugs

• Location at block never seems to work a 100%. Please report your issues.
  

• Bluetooth SCO block seems to be difficult to keep enabled. Need more information, please report your issues.
  

[Automate developer]

Settings are mostly device dependent. If we decide to sync/backup them, no server would be needed, it would be done using Google backup services.
Same goes for in-app purchases, it's handles by the Google Play store app.

[Usama Ejaz]

OK. Well, another thing i was thinking was. Is it possible to have multiple connection lines from one (OK) or output?

[Automate developer]

No, that's not how a flowcharts supposed to work.
You have the Fork block to "split" flow into multiple paths.

[mi.mo...@gmail.com]

What about global variables, or parameters to pass to flows.

E.g. passing filename and path to a flow that returns the file content.

[Automate developer]

Use the payload field in the Flow start block to pass parameters when starting flow.
You can share variable values with other fibers, of the same flow, using the Atomic and Variables give/take blocks.

There's no "global variables", see post:
https://groups.google.com/d/msg/automate-user/mBEvt6UgUXg/xxXL4D8K17kJ

[mi.mo...@gmail.com]

Ok. Though it's not possible to access/return variables from the flow started via "start flow"?

The give/take blocks only allow sending and receiving within the current flow.
So I can pass the filename to my flow, but can't receive the text content. It'd be nice to have an "end flow" block to return values.

Allowing flows to return values also allows passing values back and forth across flows.
It gives you the option to structure your flows and thus making management easier.
Thread safety is also guaranteed if flows returning a value are started synchronously, which could be user controllable or automatic.