Master Total Launcher: Native Sequences for Advanced Android Customization

Total Launcher is a highly capable platform for advanced Android customization, enabling seamless automation of any custom setup and homescreen layout without external plugins. Utilizing native sequences provides a significant structural benefit by streamlining routine device operations, optimizing layout design, and drastically reducing manual screen interactions. By linking distinct actions with precise millisecond waits, these advanced features transform static digital displays into deeply dynamic, context-aware interfaces. To configure these automated workflows, first open the primary editor menu to create a new macro, starting with the listening mode setup outlined in the first section below.

This page lists Total Launcher sequences that use only native Launcher Actions (no Tasker or external intents). Each example includes a sequence name, purpose, exact step list with suggested waits (ms), a recommended trigger, and short notes about limitations and fallbacks.

• Name: Play_Music
• Purpose: Enable Bluetooth, open music player, set media volume, and provide an in‑launcher confirmation using only native Launcher.

1. Action: Toggle Bluetooth → ON
2. Wait: 300
3. Action: Launch App → Music player
4. Wait: 300
5. Action: Set Media Volume → 60%
6. Wait: 150
7. Action: Change Wallpaper → (temporary “listening” wallpaper)
8. Wait: 100
9. Action: Go To Home Page (optional, if you want the home screen returned)
10. Wait: 100

• Trigger: Assign to a home icon tap or a gesture (tap / long‑press).

• Name: Drive_Prep
• Purpose: Minimize interruptions and open navigation quickly.

1. Action: Do Not Disturb → ON
2. Wait: 150 ms
3. Action: Auto Rotate → ON
4. Wait: 150 ms
5. Action: Show Status Bar → ON (or Show Navigation Bar → ON)
6. Wait: 200 ms
7. Action: Launch App → Maps/navigation OR Open URL → navigation intent

• Trigger: Swipe gesture or dedicated home icon.

• Name: Bedtime_Reader
• Purpose: Reduce brightness and audio, then open a reading app.

1. Action: Set Brightness to x%
   • This is a pre-set level
2. Wait:150 ms
3. Action: Auto Brightness → OFF (if available)
4. Wait: 150 ms
5. Action: Set Media Volume to 0
6. Wait: 200 ms
7. Action: Launch App → E‑reader
8. Wait: 300 ms
9. Action: Lock Screen (optional)

• Trigger: Tap icon or bedtime swipe.

• Name: Home_Clean
• Purpose: Restore a tidy home layout and minimal UI chrome, such as before handing the device to someone else.

1. Action: Close all windows and folders
2. Wait: 150 ms
3. Action: Go To Home Page
4. Wait: 150 ms
5. Action: Change Wallpaper to a minimal image (optional)
6. Wait: 200 ms
7. Action: Show Status Bar → ON; Show Navigation Bar → ON

• Trigger: Long-press on an empty area or a single reset icon.

• Name: Work_Open_Suite
• Purpose: Open a set of work apps and a specific window layout.

1. Action: Open Window → Work Folder
2. Wait: 250 ms
3. Action: Launch Email
4. Wait: 300 ms
5. Action: Launch Calendar
6. Wait: 300 ms
7. Action: Open [L/R/T/B] Drawer → access quick links

• Trigger: Two‑finger swipe or dock icon.

1. Waits: Start with 200–300 ms for UI steps; use 500–1000 ms for app launches.
2. Naming: Use a context prefix: `Drive_`, `Bedtime_`, `Work_`.
3. Modularity: Build small sequences (e.g., `Bluetooth_On`, `Music-Launch`, `Cleanup`) for easy reuse.
4. Keep sequences short: If a flow becomes long or fragile, split it into modular sequences and chain them.

• Capabilities beyond native TL sequences:
  • Reliable Bluetooth device connect/disconnect and event‑based cleanup.
• Car detection and CarPlay/Android Auto handoff triggers.
• Timers with completion actions (play sound, vibrate, run TL sequence).
• Smart‑home API calls and assistant routines via webhooks or plugins.
• Conditional logic and error handling (if/else, retries, variable checks).
• Background monitoring (trigger TL sequences on system events like headphone connect).

• How to combine:

1. Use Total Launcher sequences for UI/layout changes and quick app launches.
2. Invoke Tasker/MacroDroid tasks from TL sequences via intents or plugin calls when system‑level control is needed.
3. Keep TL sequences modular so Tasker can trigger or be triggered by them.

If you have native Total Launcher sequences you rely on, please share them here for inclusion. Provide:

1. Sequence name
2. Step list with waits (ms)
3. Trigger

uiTLM wiki will format shared sequences into copy‑ready TL editor entries and assemble a community examples appendix.