Integrating external variables enables Total Launcher to display real-time, dynamic data streams directly on a custom Android homescreen setup. By utilizing automation bridges from third-party applications such as Tasker(Google Play Store) or MacroDroid (Google Play Store), text objects within the Launcher can automatically reflect battery metrics, sensor readings, system events, or custom notifications without manual user interaction. Understanding the syntax requirements, specifically the conversion between automation variable formats and Total Launcher angle brackets, ensures reliable data transmission across interfaces. The setup workflow requires establishing the output task within the automation platform before assigning the target variable key to a text object on the canvas.

• In Tasker (see Tasker's variable guidance at [https://tasker.joaoapps.com/userguide/en/variables.html] for a more detailed explanation), a task has two actions:
  • Variable Set
  • Send Variable
• From Tasker's Action category “Plugin”
  • Select “Total Launcher” from the alphabetical dialog
  • Enter the following information with the symbols and brackets included. Substitute the appropriate varName.
    • Tasker variable name
      • %varName
    • Total Launcher
      • <varName>
• In Total Launcher
  • Turn Edit Mode on
  • Navigate to the desired screen
  • Press Object Add (+} in the upper right screen area to open a dialog of element types
    • Select Graphic. The dialog will list the built-in element types:
      • Select Text
    • A dialog “Action on Tap” opens
      • Tap the back button
    • The text element will show on the screen
      • Tap and hold to move the text element to the desired location
  • Tap the Options icon (gear) to enter the object's Edit dialog.
    • Tap the label “Text” for a list of settings for this element
      • Scroll to the end of the listing and select
        • Advanced - Variable
    • Click on Variable
      • Enter the desired varName next to Text as <varName>
      • Any text entered prior to or after <> will be displayed as literal.
      • Tap OK
      • The varName value will now appear on the screen
        • Should the varName be displayed literally, the variable has no recognized value. Re-check your work and ensure Tasker has transmitted the data.