Garlic Launcher Settings

Garlic-Launcher Settings
Garlic-Launcher Settings Activity

Custom Back Button

This option appears only on rooted Android devices. It sets a Back-Button in the left down corner of the screen.

Why do we need this?

Some manufacturers build rooted Android images (AOSP) on customer request, which have additional options in their settings. Among other things, often there is an opportunity to disable the navigation bar totally in these, Unfortunately every manufacturer provides his API for that.

So, instead of supporting dozens of different manufacturers' APIs for hide/show, it is better to create a custom Back-Button which can be activated in the case it should be needed. For example, when starting a second app, a browser, do some maintenance etc…

It is recommended to use regularly supported features like the so-called “immersive mode”, but there are customers which do not want a visible navigation bar in their kiosk systems under any circumstances. Due to these reasons, there is a back button overlay possible.

Service Password

This activates the “strict mode” with a password.

What is the Strict Kiosk Mode?

The “Normal Kiosk Mode” means that garlic-launcher is pinned. So, it is not possible to exit into Android-UI. However, you can still install/uninstall apps or configure your device manually or remotely from a CMS. That is the common use case for the most requirements.

In some high-security environments, this is a no-go. To cover this, you can activate a more strict “Kiosk Mode”. This deactivates the config buttons in garlic-launcher and prevent the installing/uninstalling of apps, the modifying of accounts and some more things. So even on an application crash it is not possible to manipulate apps or user. If a maintenance technician needs physical access to the device, there is a password secured “Service Mode”-Button. This temporary deactivates the restrictions.

The password for activating the “Service-Mode” must be set personally and is not recoverable. For security reasons, the launcher stores the password hashed with an individual salt that is new created each time. So if you choose the password wisely, it cannot be attacked via brute-force or with rainbow tables.

Do not forget the password; otherwise you had to execute a factory reset.


Here, you can set the path where the player should look for a SMIL-file. This can be a web-path to a CMS like or direct to a SMIL-Index like https://domain.tld/index.smil or to a local directory like /home/user/index.smil.

No Player start delay after booting

Normally, the digital signage player starts delayed (look below). This is for maintenance reasons. Activating this option makes the player starts immediately. But only the first time after a boot sequence.

When you close the player with Ctrl-Q or touching/clicking 10 times on screen, you will enter the launcher. Now the normal delay counts down.

Start Delay for Player in s:

This value set the delay until the player starts. Standard is 15s, but you can decrease it to 5s.

5s is minimum; otherwise you had a good chance to lock yourself out.

Daily Reboot

Set a daily reboot. Default is 3:00 a.m.