meta data for this page
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.
Overview
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.
Listen — Quick
- Name: Play_Music
- Purpose: Enable Bluetooth, open music player, set media volume, and provide an in‑launcher confirmation using only native Launcher.
- Action:
Toggle Bluetooth→ ON - Wait:
300 - Action:
Launch App→ Music player - Wait: 300
- Action:
Set Media Volume→60% - Wait: 150
- Action:
Change Wallpaper→ (temporary “listening” wallpaper) - Wait: 100
- Action:
Go To Home Page(optional, if you want the home screen returned) - Wait:
100
- Trigger: Assign to a home icon tap or a gesture (tap / long‑press).
Total Launcher cannot natively guarantee connection to a specific Bluetooth device; this sequence enables Bluetooth and opens the player. For automatic device connect/disconnect handling, use Tasker/MacroDroid.
Drive Prep
- Name: Drive_Prep
- Purpose: Minimize interruptions and open navigation quickly.
- Action:
Do Not Disturb→ ON - Wait:
150 ms - Action:
Auto Rotate→ ON - Wait:
150 ms - Action:
Show Status Bar→ ON (orShow Navigation Bar→ ON) - Wait: 200 ms
- Action:
Launch App→ Maps/navigation OROpen URL→ navigation intent
- Trigger: Swipe gesture or dedicated home icon.
For automatic car detection and Bluetooth handoff, use Tasker; this sequence prepares the UI.
Bedtime Reader
- Name: Bedtime_Reader
- Purpose: Reduce brightness and audio, then open a reading app.
- Action:
Set Brightnessto x%- This is a pre-set level
- Wait:
150 ms - Action:
Auto Brightness→ OFF (if available) - Wait:
150 ms - Action:
Set Media Volumeto0 - Wait:
200 ms - Action:
Launch App→ E‑reader - Wait:
300 ms - Action:
Lock Screen(optional)
- Trigger: Tap icon or bedtime swipe.
A longer wait (e.g., 1000 ms) may be needed before Lock Screen to allow the reader to open fully first.
Home Cleanup
- Name: Home_Clean
- Purpose: Restore a tidy home layout and minimal UI chrome, such as before handing the device to someone else.
- Action:
Close all windows and folders - Wait:
150 ms - Action:
Go To Home Page - Wait:
150 ms - Action:
Change Wallpaperto a minimal image (optional) - Wait:
200 ms - Action:
Show Status Bar→ ON;Show Navigation Bar→ ON
- Trigger: Long-press on an empty area or a single reset icon.
Work Suite Launcher
- Name: Work_Open_Suite
- Purpose: Open a set of work apps and a specific window layout.
- Action:
Open Window→ Work Folder - Wait:
250 ms - Action:
Launch Email - Wait:
300 ms - Action:
Launch Calendar - Wait:
300 ms - Action:
Open [L/R/T/B] Drawer→ access quick links
- Trigger: Two‑finger swipe or dock icon.
To attempt parallel launches, launch apps consecutively with no wait and test. Some devices still serialize heavy app starts and balk at this.
Testing, Naming, and Best Practices
- Waits: Start with 200–300 ms for UI steps; use 500–1000 ms for app launches.
- Naming: Use a context prefix: `Drive_`, `Bedtime_`, `Work_`.
- Modularity: Build small sequences (e.g., `Bluetooth_On`, `Music-Launch`, `Cleanup`) for easy reuse.
- Keep sequences short: If a flow becomes long or fragile, split it into modular sequences and chain them.
What Using Tasker or MacroDroid Can Add
- 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:
- Use Total Launcher sequences for UI/layout changes and quick app launches.
- Invoke Tasker/MacroDroid tasks from TL sequences via intents or plugin calls when system‑level control is needed.
- Keep TL sequences modular so Tasker can trigger or be triggered by them.
Community contribution invitation
If you have native Total Launcher sequences you rely on, please share them here for inclusion. Provide:
- Sequence name
- Step list with waits (ms)
- Trigger
uiTLM wiki will format shared sequences into copy‑ready TL editor entries and assemble a community examples appendix.
Comments & Feedback
Toby Lancer is ready to help! Look for the Quick Help form:
► Desktop: left sidebar located near the bottom for Private to Admin
► Mobile: 3-bar menu at page top.
► Use the Discussion section below to share any experiences and communications with other Total Launcher users.
► Any Registered User can directly update this and any wiki page if desired.
Moderation: To keep the manual clean, all comments are held for appropriateness review. Preview any comment before submitting it. It will not be displayed after submission until it is reviewed. So, please, do not resubmit.
Formatting: If using any code snippets, place them inside code tags (e.g., 'code') using double single quotes (') before and after to keep them readable.
Be Kind: This is a community effort. Please keep feedback constructive and on topic.
~~DISCUSSION~~