FAQ * よくある質問
デスクトップ版、オンライン版どっちですか?
いいえ、Automate は Androidアプリです。現在はそれ以外のプラットフォームでは利用できません。Windows または MacOS でフローを編集するには、BlueStacks などの Androidエミュレーター を使用します。
作成したフローが原因でデバイスが応答しません!
safe mode (device recovery) をご覧ください。
プレミアムが機能していません!
Google Play ストアアプリとの通信に問題がある場合、プレミアム所有権の情報確認に失敗する可能性があります。デバイスを再起動してみてください。詳細については、プレミアムページを参照してください。
バッテリー消耗が激しい!
フローが適切に構成されていれば、バックグラウンドでフローを実行している間、Automateはバッテリーをほとんど使用しないはずです。バッテリーの過度の使用を引き起こす可能性のある一般的なフロー構成の誤りは次のようなものがあります:
- Repeatedly checking (“polling”) state at a timed interval, e.g. checking Wi-Fi connectivity every 5 minutes, as this may prevent the device from going into a low-power “sleep” state. The solution is to set the Proceed option to When changed (or alike) so the flow will pause, allowing the device to “sleep” until the state has actually changed.
- D.I.Y. geofencing by repeatedly executing a Location get and/or Wi-Fi network scan block, as this may also prevent the device from “sleeping”. The solution is
to use the Location at block and let the system handle the geofencing without the need to have Automate constantly working.
- A looping flow without any blocks using a “When changed” Proceed option, as this will cause the flow to run continuously. The solution is to ensure a flow has a block where it will pause, awaiting an event.
フローチャートエディターはグラフィックを必要とするため、フローを編集するとバッテリーの消費量が増える場合があります。
フローが停止します!
フローは、何らかの障害が発生した場合にのみ停止し、またはそれは明示的に停止されます。フローは接続されていないドットに到達するまで実行されるため、すべてのドットを実行し続けるには、別のブロックに接続する必要があります。フローが無期限に実行されることを意図している場合、これは無限ループを意味します。
障害が原因でフローは停止しますが、それが望ましくない場合は、Failure catchブロックを使用することで失敗を処理できるため、場合に応じて、フローを再度実行し続けることができます。。
Automate が開いているときにフローが実行されていても、一時停止しているように見える場合は、Automate が実行されていないを参照してください。
Automate not running!
If flows, or a particular feature used therein, are running without issue but pause when the screen is turned off or when Automate is no longer in the foreground, it’s likely caused by
an installed “task killer” app like Greenify, or some kind of system “power save” feature:
Android 6—8.1
Android 9+
Huawei
- System Settings →
Advanced settings →
Battery manager →
Power plan → choose Performance.
- System Settings →
Advanced settings →
Battery manager →
Protected apps →
Automate → choose Protected.
- System Settings →
Apps →
Automate →
Battery → enable Power-intensive and Keep running after screen off.
- Huawei P9 Plus: System Settings →
Apps →
Settings →
Special access →
Ignore battery optimisation →
Automate → choose Allow.
- Huawei P20: System Settings →
Battery →
App launch →
Automate → choose Manage manually, and enable everything else.
Meizu
- System Settings →
Advanced settings →
Battery manager →
Power plan → choose Performance.
- System Settings →
Advanced settings →
Battery manager →
Protected apps →
Automate → choose Protected.
- System Settings →
Apps →
Automate →
Battery → enable Power-intensive and Keep running after screen off.
Nokia
OnePlus
- System Settings →
Battery →
Battery optimization (menu) →
Enhanced/Advanced optimization → switch Off.
- System Settings →
Apps →
Gear/Cog icon (menu) →
Advanced →
App auto-launch →
Automate → switch off.
Samsung
- System Settings →
Device maintenance →
Battery →
Save power →
Sleeping apps →
Unmonitored apps → add (menu) Automate to the list, or disable the App power monitor feature altogether.
- System Settings →
Apps →
Special access (menu) →
Optimize Battery usage →
Automate → disable.
Sony
- System Settings →
Power management →
Stamina mode → turn off.
Xiaomi
- System Settings →
Advanced settings →
Battery manager →
Power plan → choose Performance.
- System Settings →
Advanced settings →
Battery manager →
Protected apps →
Automate → choose Protected.
- System Settings →
Apps →
Automate →
Battery → enable Power-intensive and Keep running after screen off.
- System Settings →
Additional settings →
Battery & Performance →
Manage apps’ battery usage →
Saving power in the background →
Choose apps →
Automate →
Background settings → choose No restrictions.
- System Security app →
Permissions →
Auto-start →
Automate → turn on.
- Long-press Recent apps button → Long-press Automate → enable Lock.
Visit dontkillmyapp.com for additional information on “power save” features.
Even with every “power save” feature disabled the device will go hibernate/sleep, use the Device keep awake block around critical sections of the flows to prevent that.
Also, by default flows don’t resume running after a system reboot, enable the Run on system startup option in Automate settings to let them do so automatically.
I can’t uninstall Automate!
Apps that are enabled as Device administrator can’t be uninstalled until disabled as such. Revoke the “lock device and monitor failed unlock attempts” privilege in Privileges settings or in system Device administrator settings.
I can’t install permissions
Automate will install permission add-ons contained within its own package (apk) if Unknown source option is enabled in system Security settings. If the Install button in the “package installer” doesn’t respond, try disabling all screen overlay/filter apps, e.g. used to lower the brightness, as they may interfere with the button.
If the issue persist, disable the Unknown source option in system Security settings to install the add-ons directly from the
Google Play Store.
I can’t restore backup!
- If you can’t restore an Automate backup stored on the SD card. Remember that Automate, by default, can’t access the SD card. Grant access to “photos, media and files on your device” in
Privileges settings, before restoring the backup.
- If you open a backup file from within another app like Google Drive, that app may send the wrong file type. Automate will then fail with an “Corrupt flow” error as it tries to import the file as a flow. Always use the Restore backup option in settings.
- If the backup file is disabled/gray in the Google Drive app, it usually means there’s a MIME type issue. Long-tap the file and choose Download,
then restore the downloaded backup file instead, it’s located in the “Downloads” directory on the SD card/Internal storage. On the (Android 5+) system “file chooser” screen if the backup file is still disabled/gray, choose to “open from”
(see left drawer) the SD card with an Automate icon.
Corrupt flow!
If a flow stops working with an “Failed to read parcel” error after you’ve upgraded to a newer Android version, you’ll have to reconfigure all the App start shortcut and Plug-in blocks. This happens when Android has changed its internal data format.
A general “Failed to read flow” error message can appear when importing a flow and Automate is unable to access/read the data. This can be caused by a lack of privilege, or an issue with the app providing the data stream.
A “Corrupt flow” error message can appear when restoring a backup, see I can’t restore backup.
Crash when starting flow!
If Automate crashed when starting a flow, try increasing the stack size in
settings.
The “running” notification?
A permanent notification is an Android requirement to keep a background service running, without it Automate would become very unreliable.
However the notification can be hidden by turning off the
Running
notification channel in system App notification settings on Android 8 or later, or by enabling the Hide “running” notification option in settings, on prior Android versions.
Disabling all notifications for Automate, in system Apps settings, is not advised as it will hinder the “pick” blocks from working correctly, prevent the Notification show block from showing any notification,
and it may also prevent the Toast show block from displaying “toast” messages.
Why the extensions (add-ons)?
See security.
Reset the age information?
The age information, as specified on the age verification screen, can be reset by clicking
Clear defaults option in settings.