[ad_1]
Google introduced a new Sleep API this week that will help developers build better sleep tracking apps. In response, the developer of Tasker wasted no time implementing the API in a new beta, allowing users to create custom sleep tracking on Android.
For those of you who don’t know, Tasker is a popular automation app available on Android. You can create profiles that initiate tasks that consist of actions. These profiles can be triggered based on user-defined states or events. Because Tasker is so extensible, there are limitless possibilities for automation. And now, with Tasker 5.12.3 beta, you can add sleep tracking automation to the mix. The latest beta uses Google’s new Sleep API to centralize the processing of sleep detection in a battery-efficient manner. The Sleep API uses a machine learning model on the device to infer the user’s sleep state based on input from your phone’s light and motion sensors.
João Dias, the developer of Tasker, said he didn’t get a chance to test the new sleep tracking features overnight, so your mileage may vary. Also, since the Sleep API is part of Google Play services and not Tasker, it cannot fix any issues with it if it breaks on Google’s side. That said, if you want to take control of your sleep data or create your own sleep tracker, watch the video above to see how you can use the new sleep status feature in the latest beta of Tasker.
The full changelog for Tasker 5.12.3 beta is below:
- Added Sleeping status: track your sleep with Tasker
- Assistant added in HTTP request Actions Headers field to easily define commonly used headers
- Added Wifi ADB wizard for easy configuration of authorization grant / revoke commands
- Make unencapsulated monospace text in some optional input fields (Preferences> UI)
- To fix Check event does not work reliably if the screen is turned off on some devices
- Try to fix the clipboard change detection on Android 11 on some specific devices
- If you are looking for something like Carry out when you add an action and you have tasks containing the word “perform”, do not use them to auto-populate the Perform the taskField Name of
- Do not display global variables structured with. on their behalf in the VARS tab
- Now, when reading a structured output, if there is no match and the variable has been marked as a structured variable, it will be correctly evaluated in the “If not defined” condition. If you use the variable with structure access, the literal value will be used.
- When reading the HTML structure with bracketed notation, use braces for attribute matching, for example. {attr = value} instead of [attr=value]
- Allow the use of an empty key when accessing a structured variable, for example. % json[]
- Check if a variable is of the specific type used in the action “Define the type of variable structure”
- Fixed crash when adding certain events / states
- Fixed use of setLocal () function in Scene WebView for project / profile / task variables
- Correction of the configuration of project / profile / task variables from the “Java function” action
- Fixed a bug where if you select the “Perform a task” action based on a search for a task name, the priority would be incorrectly initiated at 5 instead of% priority
- Try to fix external SD or USB OTG card on Android 11+. Not yet fully operational.
[ad_2]
Source link