meta data for this page
Total Launcher Multi-Screen Guide: Configuring Independent Multi-Screen Workspaces
Total Launcher provides robust, native support for multi-screen and foldable Android devices, offering configuration capabilities that exceed standard third-party alternatives. Rather than forcing a single layout to awkwardly stretch across expanding display panels, Total Launcher intelligently treats folded and unfolded hardware states as entirely separate workspaces. This architecture enables the deployment of distinct, customized layouts perfectly optimized for both exterior cover screens and interior expanded displays.
To implement this hardware-aware functionality, distinct layouts must be created for both portrait and landscape orientations.
Key Features
| Feature | Description |
|---|---|
| Independent Layouts | Allows for completely different setups on the cover screen (folded) vs. the inner screen (unfolded). |
| Orientation Awareness | Can trigger specific layout changes based on Portrait vs. Landscape orientation, which is essential for square-ish inner displays. |
| Z-Axis/Rotation | Unlike grid-based launchers, Total Launcher allows overlapping widgets and free placement, useful for spanning gaps on dual-screen devices like the Surface Duo. |
Device Compatibility & Behavior
Total Launcher does not rely on a whitelist of specific devices; instead, it uses Android's `DisplayManager` callbacks to detect when the screen configuration changes. Below are the verified device categories and their specific behaviors.
Native Foldables (Book-Style)
• Samsung Galaxy Z Fold (1-6)
• Google Pixel Fold
• OnePlus Open
• Honor Magic V
These devices are natively supported via the configuration settings.
- Behavior: The launcher detects the “Folded” vs “Unfolded” state as a hardware event.
- Setup: Two distinct layouts are created. The launcher automatically switches between them when the hinge sensor triggers.
- Known Quirks: On some devices (like the Pixel Fold), rotating the device immediately after unfolding may cause a brief redraw delay as the launcher recalculates the grid.
Dual-Screen Devices (Hinged)
• Microsoft Surface Duo 1 & 2
• LG V60/G8X (Dual Screen Case)
These devices are often treated by Android as two separate display panels masked as one large desktop.
- Behavior: Total Launcher treats the spanned dual-screens as one giant landscape canvas.
- Setup Strategy: The “hinge gap” must be manually calculated to place widgets accordingly.
- Advantage: Unlike stock launchers, Total Launcher allows placement of widgets under the hinge or creating pixel-perfect gaps to avoid it.
Flip-Style Foldables (Clamshell)
• Samsung Galaxy Z Flip
• Motorola Razr
- Behavior: Generally, Total Launcher is used for the inner main screen only.
- Cover Screen: Most flip phones run a limited OS on the cover screen that blocks third-party launchers by default.
Configuration Guide
To enable multi-screen support, a specific foldable-specific setting must be activated:
- Navigate to '' Advanced'' >
Behavior - Toggle ON:
Support foldable screen
Once enabled, the setup process works by physically changing the device state:
- Fold the device. Customize the cover screen.
- Unfold the device. See a blank screen or a stretched version of your cover.
- Customize the unfolded screen.
Note: Changes made to the inner screen will not affect the cover screen, and vice versa. They are treated as separate “Window” instances.
Advanced Tips
Persistent Taskbar
To simulate a desktop-style taskbar that only appears on the inner screen:
- Create a new Window object.
- Set it to
Show on top. - In the Window options, set visibility rules so it only appears when the screen width is greater than a certain pixel count (or manually toggle it for the inner layout).
Surface Duo Specifics
For Surface Duo users, place a widget explicitly on the “Left” or “Right” side of the coordinates to prevent it from being cut off by the hinge. Use the Margins setting to create a “safe zone” in the center to avoid the hinge entirely.
Pros and Cons
Pros
- Unmatched customization for different form factors.
- Lightweight on resources compared to stock launchers.
- “Window” feature allows for pop-up widgets, saving screen real estate.
Cons
- Steep learning curve (high complexity).
- Minor redraw lag on some devices when switching from cover to inner screen.
- Android gesture navigation animations may be less fluid than stock.
Contribute to this Manual
Expansion of this section with device-specific tutorials and screenshots is desired. Owners of specific foldable devices (Z Fold, Pixel Fold, Duo) are encouraged to contribute.
Methods of Contribution:
- Edit this page: Verified setups can be added as a “Tutorial” or “Downloads” subsection for specific device models.
- Discussion: Or leave your experience in the Discussion tab for this page, and the Admin can incorporate it into the page.
- Contact Admin: If preferred, notify the Admin (see Quick Help on the left sidebar) directly about an experience for consideration of inclusion as official content of this wiki.
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~~