• Start URL – die URL beginnend mit http://, https:// oder file://. Sie können Variablen wie $mac, $deviceID, $locale, $hostname, $deviceName or $ssid in der URL nutzen. Sie können hier auch mehrere URLs angeben (eine pro Zeile), sie werden dann in mehreren Tabs geöffnet (ver. 1.25+).
• Username (optional) – Benutzername für Basic HTTP Authentication
• Password (optional) – Password für Basic HTTP Authentication
• Enable Fullscreen Videos – Videos können auf Vollbild geschaltet werden
• Autoplay Videos – autoplay eingebettete HTML5-Videos (funktioniert zur Zeit nur mit Webseiten, die einen statischen <video> Tag haben, daher nicht mit Youtube)
• Autoplay Audio – autoplay eingebettete HTML5-Audio (funktioniert zur Zeit nur mit Webseiten, die einen statischen <audio> Tag haben)
• Enable Form Autocomplete – Formulardaten speichern und vorbefüllen lassen
• Enable File Uploads (PLUS) – Datei-Uploads erlauben (funktioniert nicht in Android 4.4)
• Enable Camera Capture Upload (PLUS, Android 5+) – Upload von Kamera-Bildern bei Upload-Formularen erlauben
• Enable Javascript Alerts – alles Javascript alert, prompt und confirm Boxen erlauben
• Enable Popups (PLUS) – Untersützung für Popups (auch solche ohne Benutzerinteraktion) und Links im neuen Fenster öffnen
• Enable Webcam Access (PLUS) – Webcam-Zugriff durch eine HTML5-Webseite erlauben (Android 5+)
• Enable Microphone Access (PLUS) – Mikrophon-Zugriff durch eine HTML5-Webseite erlauben (Android 5+,  Fully ver. 1.8+)
• Enable Geolocation Access (PLUS) – Zugriff auf Geolocation durch HTML5 erlauben
• Open URL Schemes in Other Apps – Erlaubt anderen Apps, URLs mit anderen Schemes wie mailto: oder intent: zu öffnen
• View remote PDF Files in Fully (PLUS) – PDF-Dateien im Netz mit verschiedenen Methoden öffnen
  • Disabled – PDF-Dateien ignorieren
  • Use PDF.js (ver. 1.25+) – das beste Rendering direkt in der Webview inkl. klickbare URLs, funktioniert sogar in iFrames für die meisten URLs, kann bei größeren Dateien und schwachen Geräten jedoch langsam sein, nutzt  PDF.js hosted at Unpkg, anderes Hosting oder App-Integration auf Anfrage
  • Use Built-in PDF viewer (Android 5+) – Rendering durch Android, nur Vollbildanzeige
  • Use Google Docs – funktioniert nicht für Intranet-Dateien
  • Launch Standard App for PDF – PDF-Datei in einer anderen App öffnen
• View local PDF Files (PLUS) – lokale PDF-Dateien mit verschiedenen Methoden anzeigen
  • Disabled – PDF-Dateien ignorieren
  • Use PDF.js (ver. 1.25+) – das beste Rendering direkt in der Webview inkl. klickbare URLs, funktioniert sogar in iFrames für die meisten URLs, kann bei größeren Dateien und schwachen Geräten jedoch langsam sein, nutzt  PDF.js hosted at Unpkg, anderes Hosting oder App-Integration auf Anfrage
  • Use Built-in PDF viewer (Android 5+) – Rendering durch Android, nur Vollbildanzeige
  • Launch Standard App for PDF – PDF-Datei in einer anderen App öffnen
• Play videos in Fully (PLUS) – von Android unterstützte Videos (inkl. RTSP) in Fully in Vollbild abspielen
• View Other Remote Files – auswählen, wie andere Dateien geöffnet werden: abschalten, anderen Apps eine URL übergeben oder Datei herunterladen und anderen Apps übergeben (ver. 1.17+)
• Enable Open in Other Apps – Links zu Dateien in anderen Apps öffnen lassen
• URL Whitelist – eine volle URL (inkl. http:// etc.) per Zeile, * als Wildcard, alle erlaubt, wenn leer, Beispiel: *google.*
• URL Blacklist – eine volle URL (inkl. http:// etc.) per Zeile, * als Wildcard, überschreibt Whitelist, Beispiel: *google.*
• Custom Error URL – Seite, die im Fehlerfall geladen werden soll; prüfen Sie Query-String-Parameter error und url für mehr Info über den Fehler; auf Android 4.4+ werden nur DNS-/Verbindungsfehler erkannt; auf Android 6+ auch HTTP-Fehler 40x/50x.
• Load Error URL on Disconnection – Custom Error URL auch laden, wenn Internetverbindung abgebrochen nach dafinierter Anzahl der Sekunden, 0 für abgeschaltet (ver. 1.27+)

• Enable Pull to Refresh – erlauben das Runterziehen, um die aktuelle Seite neu zu laden
• Enable Back Button – erlaubt History-Back beim Klick auf Zurückbutton
• Load Start URL on Home Button – Tap auf Home-Button, um die Start-URL zu laden
• Enable Tap Sound – Click-Sound abspielen beim Tappen in der Webansicht
• Swipe to Navigate (PLUS) – swipe links/rechts, um in der Browser-History vorn-/zurückzunavigieren
• Animate Page Transitions (PLUS) – ein App-Feeling durch animierte Übergänge beim Navigieren schaffen, blendet Inhalte beim Laden aus, ein schnelles Gerät und eine schnell ladende Webseite ist erforderlich
• Wait for Internet Connection – versucht niemals eine Webseite zu öffnen, wenn keine Verbindung vorhanden
• Search Provider URL – diese URL als Such-Provider nutzer, Address Bar muss aktiviert sein, Keywords werden an diese URL angehängt, default Google-Suche URL: https://www.google.com/search?q= (ver. 1.12+)
• Read NFC Tags (PLUS) – URLs von NFC-Tags (NDEF-Format) öffnen, NFC muss in Android-Einstellungen erlaubt und Fully muss im Vordergrund sein (ver. 1.16+)

• Enable Zoom – zoomen können, wenn die Webseite das unterstützt
• Load in Overview Mode – lade die Seite runterskaliert auf Bildschirmbreite (hilfreich für ältere Webseiten)
• Use Wide Viewport – Viewport-Metatag der Webseite beachten
  
• Initial Scale – initiale Skalierung in % setzen (hilfreich für ältere Webseiten, funktioniert nur wenn Use Wide Viewport ausgeschaltet ist,  da anderenfalls Viewport-Metatag wichtiger ist)
• Scale Font Size – nur die Schrift skalieren in % (default: 100%)

• Auto Reload on Idle – automatischer Reload nach x Sekunden Inaktivität
• Auto Reload after Failure – automatischer Reload nach x Sekunden nach einem Ladefehler
• Auto Reload on Screen On – automatischer Reload beim Bildschirmeinschalten
• Auto Reload on Screensaver Stop – automatischer Reload beim Stoppen des Screensavers (ver. 1.10+)
• Auto Reload on Network Reconnect – automatischer Reload beim WLAN/LAN/LTE-Reconnect
• Auto Reload on Internet Reconnect (experimentell) – Start-URL neuladen, wenn reale Internet-Verbindung zustande kommt (geprüft durch einen Ping auf den Google-DNS-Server auf 8.8.8.8 alle 10 Sekunden) – funktioniert nicht mit jedem Gerät!
• Delete Cache on Auto Reload – Cache vor dem Neuladen löschen
• Delele Webstorage on Auto Reload – Webstorage vor dem Neuladen löschen
• Delete History on Auto Reload – Verlauf und Formulardaten vor dem Neuladen löschen
• Delete Cookies on Auto Reload – Cookies vor dem Neuladen löschen
• Load Current Page on Auto Reload – immer die jetzige Seite anstatt Start URL bei Auto-Reload neuladen; wenn mehrere Tabs offen, alle werden refreshed; Custom Error URL wird zur letzten “guten” URL zurückkehren (ver. 1.27+)
• Skip Auto Reload if Showing the Start URL – Do not auto reload if the start URL is still showing (ver. 1.31+)

• Enable JavaScript Interface (PLUS) – JavaScript Interface zur Interaktion der Website mit Device-Features einschalten siehe unten
  • Detect iBeacons (PLUS) – iBeacons erkennen und auf dem JavaScript-Interface Events triggern (ver. 1.19+)
  • Enable QR Code Scanner (PLUS) – enable the integrated barcode scanner from JavaScript interface (ver. 1.30+)
• Inject JavaScript (PLUS) – dieser Javascript-Code wird nach dem Laden jeder Webseite ausgeführt, erlaubt eigene beliebige Modifikationen der Webseiten (ver. 1.25+)
• Enable Keyboard – Texteingaben in Webformularen erlauben
• Enable Text Selection – Textauswahl mit langem Tap erlauben
• Enable Touch Interaction – Touch-Interaktionen in der Webview erlauben
• Enable Scrolling and Dragging – Scrolling und Dragging mit Touch in der Webview erlauben
• Enable Third Party Cookies – Third Party Cookies erlauben (vor Android 5 immer erlaubt)
• Recreate Tabs on Reload – Webtabs schließen und neu öffnen bei Auto-Reload (ver. 1.27+)
• Resubmit Form Data on Reload – Resend form data (POST) on each page reload (ver. 1.33+)
• Localhost File Access (PLUS) – access local files in Webview using https://localhost/… or http://localhost/… URL. So you can embed local files (images or videos) in your website. Check this FAQ. (ver. 1.33+)
• Add Referer Header – apply Referer Header to HTTP GET requests (ver. 1.33+)
• Add XFF Header – apply X-Forwarded-For header to HTTP GET requests (ver. 1.33+)
• Enable Web Filter (PLUS) – load a host list from /sdcard/fully-blackhosts.txt  and block them. So you can make a basic ad blocker. You can get a list of known Ad hosts in text format here (ver. 1.33+)
• Enable Safe Browsing (experimental) – Block websites Google has classified as a known threat (requires Android 8.1+)
• Ignore SSL Errors – kann bei selbstsignierten Zertifikaten genutzt werden, macht SSL unsicher
• Client Certificate File (PLUS) – Client certificate file or URL for client CA authentication, P12 or PFX files allowed (ver. 1.32+)
• Client Certificate Password – Client certificate private key password (ver. 1.32+)
• Cache Mode – Caching Mode für dir Webview auswählen
• Clear Cache After Each Page – Cache nach jedem Seitenladen leeren
• Fake User Agent String – User Agent vom anderen Webbrowser vorgeben
• Resume Playback when Getting to Foreground – versucht Video und Audio weiterzuspielen, wenn Fully Kiosk in Vordergrund zurückkehrt
• Keep Screen On while in Fullscreen Mode – Screensaver und Screen Off Timer abschalten, solange Webview in Fullscreen-Modus befindet
• Enable Webview Contents Debugging – Remote-Debugging für die Webview mit DevTools erlauben
• Default WebView Background Color – Hintergrundfarbe für die WebView auswählen, weiß im Standard
• Graphics Acceleration Mode – versuchen Sie diese Einstellung bei Problemen mit dem Rendering in der Webview zu ändern

• Select Items to Show – Apps für den Launcher aus der Liste der installierten Apps auswählen (mehr Info)
• Show Launcher on Start –  die Launcher-Seite (launcher:) immer anstatt der Start-URL zeigen
• Launcher Text Color – select app/bookmark label color for the launcher page (ver. 1.31+)
• Launcher Background Color – Hintergrundfarbe für die Launcherseite
• Launcher Page Scaling – Seitenskalierung in % für die Launcherseite, default: 100%
• Inject HTML Code in Launcher – eigenes Design für die Launcher-Seite (Beispiel) durch Einfügen von diesem CSS/JS-Code in <head> hinzufügen

• Screensaver Timer – Nach wie vielen Sekunden Inaktivität soll Screensaver URL geladen werden, 0 für abgeschaltet
• Screensaver Playlist – Media-Dateien, Ordner, YouTube Videos/Playlists oder Webseiten auswählen, die im Screensaver gezeigt werden sollen
• Screensaver Wallpaper URL – Diese Website wird als Hintergrund des Screensavers angezeigt, leer für transparenten Hintergrund
• Play Fullscreen – Vollbildmodus ohne Systembars einschalten, wenn Screensaver startet
• Screensaver Brightness (PLUS) – Bildschirm-Helligkeit für den Screensaver (0-255), leerlassen für System-Default
• Fade In/Out Duration – Bild-Übergangsdauer in Millisekunden, default 200ms
• Use Android Daydream – Android Daydream (ab Android 7 Screensaver genannt) anstatt Fully’s Screensaver starten
• Android Daydream Settings – Android-Einstellungen für Daydream öffnen

• Keep Screen On – Bildschirm bleibt an
• Screen Brightness – Bildschirm-Helligkeit von 0 bis 255 setzen, leerlassen für System-Default
• Force Screen Orientation – Bildschirmausrichtung festlegen
• Unlock Screen – Sperrbildschirm wird umgangen
• Screen Off Timer – Nach wie viel Sekunden Inaktivität soll der Bildschirm abgeschaltet werden, 0 für keine Abschaltung. Mit Motion Detection oder Movement Detection kann man den Bildschirm wieder einschalten lassen.
• Force Immersive Fullscreen (experimental) – versucht Systembalken immersive für andere Apps zu machen. WICHTIG: Diese Option ist nicht erforderlich für Fully, um die eigene Webview oder Launcher im Vollbild zu machen, nutzen Sie dafür die Einstellungen in Toolbars and Appearance Settings. Wenn diese Einstellung aktiviert, sind alle Tastatureingaben und Zurücktaste blockiert und funktionieren nicht. Das ist etwas, was wir nicht ändern können, dieser Modus ist ein großer Hack.
• Launch on Boot – die App beim Systemstart starten
• Bluetooth Mode – Force enable or disable Bluetooth on app start (ver. 1.33+)
• Wifi Mode – Force enable or disable Wifi on app start (ver. 1.33+)
• Force Wifi SSID (PLUS) – Das Gerät für ein bestimmtes WLAN-Netzwerk vorkonfigurieren, wenn angebebene SSID verfügbar, wird Fully die Verbindung zu diesem WLAN forcieren
• Force Wifi Keyphrase (PLUS) – WPA-Keyphrase für die obige WLAN-SSID
• WiFi Settings – Android’s WLAN-Einstellungen öffnen

• Schedule Wakeup and Sleep (PLUS) – Schlaf- und Aufwachzeiten für jeden Tag der Woche oder ganze Woche oder Wochenende einstellen, nutzen Sie bitte das 24-Zeitformat HH:MM. Beachten Sie, dass  nicht jedes Gerät zu eingestellten Zeiten automatisch aufwachen kann, siehe auch Known Issues (PLUS)
• Keep Sleeping if Not Plugged – das Gerät nicht auswecken, wenn kein Strom angeschlossen
• Sleep on Power Connect – das Gerät in Schlafmodus versetzen, wenn Stromkabel angeschlossen, kann für nächtliches Laden verwendet werden (ver. 1.18+)
• Sleep on Power Disconnect – das Gerät in Schlafmodus versetzen, wenn Stromkabel abgezogen
• Show Battery Warning (PLUS) – optische Warnung anzeigen, wenn Batterie-Level unter diesem Wert, fürs Abschalten auf 0 setzen
• Prevent from Sleep while Screen Off – Try to keep device awake even if the screen is turned off (Android 6+). Otherwise usually many devices will fall asleep as soon as the screen is turned off (ver. 1.32+)
• Set CPU Wakelock – die CPU immer wach halten (normalerweise nicht benötigt)
• Set Wifi Wakelock – das WLAN immer wach halten (normalerweise nicht benötigt)

• Enable Kiosk Mode – Gerät mit Exit-Geste und PIN blocken – siehe unten
• Kiosk Exit Gesture – Geste zum Anzeigen der PIN-Abfrage im Android-Kiosk-Modus auswählen
  • Swipe vom linken Rand (default)
  • Schnelle 5 Taps egal wo (easy)
  • Double Tap Oben Links plus Double Tap Unten Rechts (beide müssen innerhalb von 3 Sekunden erfolgen, schwer zu erraten)
• Kiosk Mode PIN – die PIN zum Verlassen des Kiosk-Modus, keine PIN-Abfrage wenn leergelassen, Standard-PIN: 1234
• Wifi/Settings PIN – eine separate PIN nur für den Zugang zu WLAN-Einstellungen. Achtung: Auf einigen Geräten wie z.B. bei Samsung Tablets wird durch WLAN-Einstellungen ein Zugang zu allen Android-Einstellungen möglich. Nutzen Sie Select Wifi Network in der nächsten Einstellung stattdessen.
• Wifi/Settings PIN action – Select the action on entering Wifi/Settings PIN of following (ver. 1.33+):
  • Open Android Wifi Settings (default)
  • Open Android Bluetooth Settings
  • Open Android Mobile Network Settings
  • Open Android Connection Settings
  • Open Android OTA Update Settings
  • Select Wifi Network (experimental)
  • Custom Action Intent
• Wifi/Settings PIN Custom Intent – Specify the Intent URL for the custom action (ver. 1.33+)
• Disable Status Bar – Zugang zu Status-Bar (oben) und Systemeinstellungen blocken – bitte nur nach einem eingehenden Test im Kiosk-Modus (inkl. Reboot und Abschalten des Kiosk-Modus) einschalten. Diese Option hat Einschränkungen auf Android 12.
• Disable Volume Buttons – Lautstärken-Tasten in Kiosk Mode blockieren
• Disable Power Button – die Power-Taste blockieren, sehr langer Druck wird das Gerät dennoch abschalten. Diese Option hat Einschränkungen auf Android 12.
• Disable Home Button – den Home-Button blockieren, wenn aktiviert, Fully Kiosk wird sich als Home App einrichten
• Disable Other Apps – alle anderen Apps blockieren außer solcher, die mit Absicht von/aus Fully gestartet wurden
• App Whitelist – erlaubt ausgewählten Apps, in den Vordergrund zu gehen, eine Package Name pro Zeile, kann * als Wildcard nutzen, z.B. com.skype*  um Skype-Nutzung zu erlauben. Die Apps, die von Fully direkt gestartet werden, sind automatisch gewhitelisted und müssen hier nicht hinzugefügt werden.
• Advanced Kiosk Protection – einen verbesserten Schutz gegen das Starten von anderen Apps aktivieren, Recent Task Button und Power-Button werden nutzlos sein, sogar wenn andere Apps im Vordergrund. Advanced Protection is immer automatisch aktiv, wenn Universal Launcher genutzt wird.
• Single App Mode – eine App automatisch mit vollem Kiosk-Schutz starten. Damit können Sie das Gerät außer einer einzigen App komplett sperren. Bitte starten Sie app auf dem Gerät vorher einmal, um die erforderlichen Berechtigungen zu erteilen (oder nutzen Sie das Provisioning, um die Berechtigungen automatisch zu erteilen).
  • Wichtig: Mit Fully Kiosk 1.27 und älter müssen Sie 5x kurz und schnell von oben wischen und anschließend sofort den Home-Button drücken, um zu Fully Kiosk zurückzukehren. Danach nutzen Sie die eingestellte Fully Exit Gesture, um die PIN-Eingabe zu sehen. Schalten Sie diese Option nicht ein, wenn Ihr Gerät kein Touchscreen oder keinen Home-Button (onscreen/hardware) besitzt. Sie werden die App nicht verlassen können.
  • Wichtig: Mit Fully Kiosk 1.28+ können Sie Single App Mode auch mit Android 8+ Geräten nutzen. Tappen Sie 7x sehr schnell irgendwo auf dem Bildschirm, um die PIN-Eingabe zu sehen.

• Select Single App – die App für Single App Mode auswählen oder Intent-URL eingeben.
• Single App Exit by Remote Admin only – Disable single app mode exit by 7 fast taps. You will only be able to exit from single app mode by the Remote Admin Unlock Kiosk button. Remote Admin must be activated in order this option to have effect. (ver. 1.32+)
• Lock Safe Mode – Blockiert Android Safe Mode, dafür wird ein Sperrbildschirm mit Ihrer Kiosk PIN aktiviert. Das kann beim Starten anderer Apps problematisch sein.
• Disable Camera – Kamera für alle Apps abschalten (incl. Fully Kiosk, also wird das die  Visual Motion Detection killen)

• Enable Visual Motion Detection – Bewegungserkennung mit der Camera siehe unten
  • Pause when Fully in Background (experimental) – wenn andere App im Vordergrund, wird die Motion Detection angehalten, so kann die Camera von der anderen App genutzt werden
  • Detector Sensitivity – Erkennungsempfindlichkeit, 90-95 funktioniert meist am besten
  • Detector Frame Rate – Abtastfrequenz pro Sekunde (1-25), je höher desto sicherer die Erkennung, jedoch auch eine etwas höhere CPU-Last
  • Darkness Level – darkness threshold level (0-100), lower value triggers darkness at lower ambient light level
  • Camera Id – use the specified camera Id, keep empty to use the default front cam
  • Show Cam Preview – kleines Preview-Bild der Cam zeigen
• Enable  Acoustic Motion Detection (experimental) – Geräte-Mikrophon für Bewegungserkennung nutzen
  • Acoustic Detector Sensitivity – Mikrophon-Empfindlichkeit 0-100, funktioniert meist gut mit 90-100
• Turn Screen On on Motion – Bildschirm einschalten, wenn Bewegung erkannt, schau in Device management für Einstellungen, um den Bildschirm zeitgesteuert auszuschalten
• Exit Screensaver on Motion – stop Screensaver, wenn Bewegung erkannt, schau in Screensaver-Abschnitt für Screensaver-Einstellungen
• Turn Screen Off in Darkness – turn screen off when darkness detected, keep screen off as long as darkness persists

• Enable Remote Administration – Fully- und Geräte-Info anzeigen und Einstellungen von Fully aus jedem Webbrowser verwalten – siehe unten
  
  • Remote Admin Password – Passwort für Remote Admin, für REST-Interface und für Zugriff aus Fully Cloud setzen (ohne Passwort geht nicht)
    
  • Remote Admin from Local Network – Remote Admin und REST-Interface aus dem lokalen Netzwerk (oder über VPN) unter http://ip-address:2323 erlauben
  • Enable File Management on Remote Admin – Allow listing and downloading local files using Remote Admin web interface (1.32.2+)
  • Enable Screenshot on Remote Admin – allow getting a screenshot on Remote Admin, this option can’t be changed on Remote Admin
  • Enable Camshot on Remote Admin – allow getting a camshot on Remote Admin (requires Motion Detection), this option can’t be changed on Remote Admin
  • Remote Admin from Fully Cloud – Also enable remote admin worldwide using Fully Cloud service at fully-kiosk.com/cloud
  • Add Device To Fully Cloud – specify account and password to add this device  to Fully Cloud. You can save the cloud credentials (encrypted) in order to copy them to other devices by the deployment process and add other devices automatically to Fully Cloud.

• Enable Root Features – Get root privileges for the app and allow root features, use it with caution
• Daily System Restart – Scheduled time (HH:MM) in 24h format for automatic device restart, keep empty for disabled
• Shutdown on Power Disconnect – Shutdown the device after defined number of seconds after unplugging, keep 0 for disabled
• Clear Launcher Apps – reset all launcher apps after Fully Kiosk is in foreground for defined number of seconds, keep 0 for disabled
• Clear Single App after Idle Time – reset the single app after defined number of inactivity seconds, set 0 for disabled
• Kill Apps Before Starting Them – Always kill selected apps before starting them, enter one package name per line

• Lock Task Mode  – remove home and recent task button, disable status bar (in Kiosk mode only). Do not enable this mode if you are going to start other apps.
• Disable Status Bar – better disable status bar (in Kiosk mode only)
• Disable Keyguard
• Disable Volume Buttons
• Disable Screen Capture
• Disable USB Storage
• Disable ADB
• Disable Boot in Safe Mode – this doesn’t work 100% with all devices
• System Update Policy – select policy for over-the-air system updates: as soon as possible, postpone for 30 days or only in time window 10pm-2am
• Password Quality
• Minimum Password Length
• App Runtime Permission Policy – default runtime permission policy: prompt, grant or deny
• Disable Apps From Unknown Sources – disable app install from APK file
• APK Files to Install – enter one URL per line, silent install can be done with Android 6+, requires Disable Apps from Unknown Sources to be switched off
• App Lock Task Whitelist – allow selected apps to enter the lock task mode, one package name per line
• System Apps to Enable – enable selected system apps, by default only settings app is enabled, one package name per line
• Apps to Disable – disable access to selected apps, one package name per line

• Enable KNOX Features (experimental) – enable Samsung KNOX features, requires Internet for KNOX licensing. KNOX features are for B2B customers only. KNOX settings will take effect even if Fully Kiosk is stopped. Use with caution, there is a small chance to brick the device.
• Disable Camera – disable camera for all apps
• Disable Screen Capture – disable screen capture
• Disable Status Bar – better disable pulling down the status bar
• Hide Status Bar – remove status bar content (ver. 1.32+)
• Hide Navigation Bard – remove navigation bar content (ver. 1.32+)
• Disable Hardware Home Button – disable home button (ver. 1.32+)
• Disable Hardware Back Button – disable back button (ver. 1.32+)
• Disable Hardware Power Button – disable power button (ver. 1.32+)
• Disable Hardware Recent Task Button – disable recent task button (ver. 1.32+)
• Disable Hardware Volume Keys – disable volume keys (ver. 1.32+)
• Disable USB Host Storage – disable USB access to external storage and devices
• Disable Media Transfer Protocol – disable USB access to device storage via MTP
• Disable Safe Mode – disable safe mode
• Disable Multiple Users – Disable multiple user support, users can’t create new user or login as guest
• Disable Air Command Mode – (ver. 1.32+)
• Disable Air View Mode – (ver. 1.32+)
• Disable Edge Screen – (ver. 1.32+)
• Disable Multiple Window Mode – (ver. 1.32+)
• Disable Task Manager – (ver. 1.32+)

• Daily Usage Statistics (PLUS) – Tägliche Nutzungsstatistiken auf dem Gerät sammeln, sie sind  nur für Sie in Remote Admin Interface verfügbar
• MQTT Integration (PLUS) – send device info and events to MQTT broker, look here for docs
  • Enable MQTT
  • MQTT Broker URL – specify your MQTT broker URL like this tcp://farmer.cloudmqtt.com:18075
  • MQTT Broker Username
  • MQTT Broker Password
• Restart Fully After Crash (PLUS) – die App nach einem Absturz automatisch neustarten
• Restart Fully After Update (PLUS) – die App nach Update von Fully und von Android Webview automatisch neustarten
• Run as Priority App – Versucht Android daran zu hindern, die Fully App bei Ressourcenmangel zu killen
• Conside Device in Use while Keyboard Visible – don’t run features like screensaver, screen off, reload on idle when keyboard is open, Fully Kiosk however can’t determine if the device is in use when the keyboard or other apps are in foreground. With this option you can avoid starting on idle features while the soft keyboard is open (ver. 1.25+)
• Consider Device in Use while Using Another App – don’t run features like screen off, reload on idle when another app is in foreground or screen is off (ver. 1.31+). For screensaver with other app check this FAQ.
• Touching Other Apps Restarts Idle Timer – don’t run the idle features like screensaver, screen off time, reload on idle when user keeps touching the screen  even if another app is in foreground(ver. 1.29+)
• Go To Background Timer (PLUS)  – bring Fully Kiosk to the background after some idle time (set it in seconds)
• Enable Version Info – Update-Zusammenfassung bei Start zeigen
• Show Menu Hint on Start – Menü kurz beim Starten zeigen und den Hinweis einblenden
• Confirm Exit – beim App-Beenden bestätigen
• Export Settings – alle Einstellungen zu fully-settings.json exportieren
• Import Settings – JSON-Datei auswählen und Einstellungen importieren
• Enable Settings Auto-Import – Auto-Import der Einstellungen aus fully-auto-settings.json bei App-Start – genutzt für schnelles Deployment
• Device ID – zeigt Device ID, beim Tappen wird diese zu Zwischenablage und in die Datei  fully-deviceID*.txt für Offline-Lizenzierung kopiert
• Volume License Key – für einfache Massenlizenzierung den Volume License Key hier eingeben. Sie können einen solchen Schlüssel bekommen, wenn Sie eine Fully PLUS Volumenlizenz (ab 10 Geräten) ordern. Für Einzellizenzen bitte nutzen Sie Get a PLUS License im Menü. Das Lizenz wird abgemeldet, wenn Sie den Key hier rauslöschen.
• Version Info – letzte Update-Informationen anzeigen
• Device Info – Zusammenfassung der Geräte-Info anzeigen, bitte senden Sie uns eine Kopie, wenn Sie einen Bug berichten

You need Openssl and some Linux knowledge to create a SSL certificate for the device. First create a root certificate (for signing other CAs) using a script like this:

#!/bin/bash
mkdir CA
openssl genrsa -aes256 -out CA/rootCA.key 4096
openssl req -x509 -new -nodes -key CA/rootCA.key -sha256 -days 3650 -out CA/rootCA.crt

Import the rootCA.crt as Trusted Root Authority in your web browser.

Now create a domain certificate fully-remote-admin-ca.p12 with password “fully” for each device using a script like this. Each device must be addressed in your local network by a hostname like device4711.network.my, not by the IP address.

#!/bin/bash

if [ -z "$1" ]
then
echo "Please supply a domain to create a certificate for";
echo "Usage:"
echo "$0 device4711.network.my"
exit;
fi

openssl req -new -nodes -keyout domain.key -out domain.csr -days 3650 -subj "/C=DE/L=Some/O=Acme, Inc./CN=$1"
openssl x509 -req -days 3650 -sha256 -in domain.csr -CA CA/rootCA.crt -CAkey CA/rootCA.key -CAcreateserial -out domain.crt -extensions v3_ca -extfile <(
cat <<-EOF
[ v3_ca ]
subjectAltName = DNS:$1
EOF
)

openssl pkcs12 -export -out fully-remote-admin-ca.p12 -inkey domain.key -in domain.crt -passout pass:fully

echo Generated self signed CA for $1 in fully-remote-admin-ca.p12
openssl pkcs12 -in fully-remote-admin-ca.p12 -nodes -passin pass:"fully" | openssl x509 -noout -text

Now copy fully-remote-admin-ca.p12 file onto device into /sdcard folder and restart Fully Kiosk. Remote Admin will now be available at the location like https://device4711.network.my

This setup works at least with current Google Chrome on Windows 10 without any warnings. Using other clients may need a slightly different SSL setup.

// Device Info
/?cmd=deviceInfo&password=[pass]

// Basic features
/?cmd=loadStartURL&password=[pass]
/?cmd=loadURL&url=[url]&password=[pass]
/?cmd=clearCache&password=[pass]
/?cmd=clearWebstorage&password=[pass] 
/?cmd=clearCookies&password=[pass]  (ver. 1.28+)
/?cmd=restartApp&password=[pass] 
/?cmd=exitApp&password=[pass] 
/?cmd=screenOn&password=[pass]
/?cmd=screenOff&password=[pass]
/?cmd=forceSleep&password=[pass] 

// Simulate motion 
/?cmd=triggerMotion&password=[pass] 

// Screensaver and daydream
/?cmd=startScreensaver&password=[pass]
/?cmd=stopScreensaver&password=[pass]
/?cmd=startDaydream&password=[pass] (ver. 1.24.1+)
/?cmd=stopDaydream&password=[pass] (ver. 1.24.1+)

// Start other apps and bring Fully app to foreground
/?cmd=startApplication&package=[pkg]&password=[pass]
/?cmd=toForeground&password=[pass]

// Return to webview if any view (PDF, Video, Settings, Menu) is open
/?cmd=popFragment&password=[pass] 

// Download and launch APK file, user input can be required for install
/?cmd=loadApkFile&url=[url]&password=[pass]

// Lock/unlock device for maintenance
/?cmd=enableLockedMode&password=[pass]
/?cmd=disableLockedMode&password=[pass]


// Show message in an overlay (1.34+)
/?cmd=setOverlayMessage&text=[text]&password=[pass]

// Load full usage stats CSV file
/?cmd=loadStatsCSV&password=[pass]

// Get screenshot image (PNG)
/?cmd=getScreenshot&password=[pass]

// Get camshot image (requires Motion Detection)
/?cmd=getCamshot&password=[pass] 

// Text to speech
/?cmd=textToSpeech&text=[text]&password=[pass] 
/?cmd=textToSpeech&text=[text]&locale=[locale]&password=[pass] 
/?cmd=textToSpeech&text=[text]&locale=[locale]&engine=[engine]&password=[pass] 

// Sounds and volume
/?cmd=setAudioVolume&level=[0-100]&stream=[1-10]&password=[pass]
/?cmd=playSound&url=[url]&loop=[true|false]&password=[pass]
/?cmd=stopSound&password=[pass]
/?cmd=playVideo&password=[pass]&url=[url]&loop=[0|1]&showControls=[0|1]&exitOnTouch=[0|1]&exitOnCompletion=[0|1]

// Change any of 200+ Fully settings, look in Remote Admin for keys
// New setting will be applied immediately
/?cmd=setBooleanSetting&key=[key]&value=[true|false]&password=[pass] 
/?cmd=setStringSetting&key=[key]&value=[value]&password=[pass] 

// Import settings file (dat/json) from /sdcard
/?cmd=importSettingsFile&filename=[filename]&password=[pass]

// Download and upzip file to /sdcard
/?cmd=loadZipFile&url=[url]&password=[pass]

String fully.getCurrentLocale()
String fully.getIp4Address()
String fully.getIp6Address()
String fully.getHostname()
String fully.getHostname6()
String fully.getMacAddress()
String fully.getMacAddressForInterface(String interface)
String fully.getWifiSsid()
String fully.getWifiBssid()   // ver. 1.44+
String fully.getWifiSignalLevel()  // ver. 1.30+
String fully.getSerialNumber()
String fully.getAndroidId()
String fully.getDeviceId()
String fully.getDeviceName()
String fully.getImei()
String fully.getSimSerialNumber()
float fully.getBatteryLevel()
float fully.getScreenBrightness()
int fully.getScreenOrientation() // ver. 1.40.2+
int fully.getDisplayWidth()
int fully.getDisplayHeight()
boolean fully.getScreenOn()
boolean fully.isPlugged()
boolean fully.isKeyboardVisible()
boolean fully.isWifiEnabled()
boolean fully.isWifiConnected()   // ver. 1.44+
boolean fully.isNetworkConnected()  // ver. 1.44+
boolean fully.isBluetoothEnabled()
boolean fully.isScreenRotationLocked()  // ver. 1.40.2+
String fully.getFullyVersion()
int fully.getFullyVersionCode()
String fully.getWebviewVersion()
String fully.getAndroidVersion()
int fully.getAndroidSdk()
String fully.getDeviceModel()

// Get storage info (ver. 1.33+)
long fully.getInternalStorageTotalSpace()
long fully.getInternalStorageFreeSpace()
long fully.getExternalStorageTotalSpace()
long fully.getExternalStorageFreeSpace()

// Get environment sensor info (ver. 1.40+)
String fully.getSensorInfo()
float fully.getSensorValue(int type)
String fully.getSensorValues(int type)

// Get data usage (ver. 1.44+, Android 6+)
long fully.getAllRxBytesMobile()
long fully.getAllTxBytesMobile()
long fully.getAllRxBytesWifi()
long fully.getAllTxBytesWifi()

void fully.turnScreenOn()
void fully.turnScreenOff() 
void fully.turnScreenOff(boolean keepAlive) 
void fully.forceSleep()
void fully.showToast(String text) 
void fully.setScreenBrightness(float level)
void fully.enableWifi() // In Android 10+ only with provisioned devices
void fully.disableWifi() // In Android 10+ only with provisioned devices
void fully.enableBluetooth()
void fully.disableBluetooth()
void fully.showKeyboard()
void fully.hideKeyboard()
void fully.openWifiSettings()
void fully.openBluetoothSettings()
void fully.vibrate(int millis)
void fully.sendHexDataToTcpPort(String hexData, String host, int port)
void fully.showNotification(String title, String text, String url, boolean highPriority) // ver. 1.33+
void fully.log(int type, String tag, String message) // ver. 1.41+

// Access clipboard (ver. 1.40+)
// No access with Android 10+ if Fully is in background
void fully.copyTextToClipboard(String text)
String fully.getClipboardText()
String fully.getClipboardHtmlText()

// Note that write access to external SD card is not supported
void fully.deleteFile(String path)   
void fully.deleteFolder(String path) // recursive!
void fully.emptyFolder(String path)  // recursive, ver. 1.30+
void fully.createFolder(String path) // ver. 1.42+
String fully.getFileList(String folder)  // get JSON array, ver. 1.31+
void fully.downloadFile(String url, String dirName)
void fully.unzipFile(String fileName) // ver. 1.40.2+
void fully.downloadAndUnzipFile(String url, String dirName)

// ver. 1.36+ respond to download/unzip events
void fully.bind('onDownloadSuccess','todo("$url","$dir","$code","$fileLength","$lastModified","$mimetype");')
void fully.bind('onDownloadFailure','todo("$url","$dir","$code");')
void fully.bind('onUnzipSuccess','todo("$url","$dir");')
void fully.bind('onUnzipFailure','todo("$url","$dir","$message");')

void fully.textToSpeech(String text)
void fully.textToSpeech(String text, String locale)
void fully.textToSpeech(String text, String locale, String engine)
void fully.textToSpeech(String text, String locale, String engine, boolean queue)  // ver. 1.38+
void fully.stopTextToSpeech()  // ver. 1.38+

void fully.playVideo(String url, boolean loop, boolean showControls, boolean exitOnTouch, boolean exitOnCompletion)
void fully.stopVideo() // ver. 1.42+

// Audio Streams: 0 – Voice Call, 1 – System, 2 –  Ring, 3 – Music, 4 – Alarm, 5 – Notification, 6 – Bluetooth, 8 – DTMF, 9  – TTS, 10 – Accessibility
void fully.setAudioVolume(int level, int stream)
void fully.playSound(String url, boolean loop)
void fully.playSound(String url, boolean loop, int stream)
void fully.stopSound()
void fully.showPdf(String url)
int fully.getAudioVolume(int stream)
boolean fully.isWiredHeadsetOn()  // ver. 1.43+
boolean fully.isMusicActive()     // ver. 1.43+

void fully.loadStartUrl()
void fully.setActionBarTitle(String text)
void fully.startScreensaver()
void fully.stopScreensaver()
void fully.startDaydream()
void fully.stopDaydream()
void fully.addToHomeScreen()
void fully.print()  // window.print() doesn't work
void fully.exit()
void fully.restartApp()
String fully.getScreenshotPngBase64()
String fully.loadStatsCSV()
void fully.clearCache()
void fully.clearFormData()
void fully.clearHistory()
void fully.clearCookies()
void fully.clearCookiesForUrl(String url) // ver. 1.43.5+
void fully.clearWebstorage()
void fully.focusNextTab()  
void fully.focusPrevTab()
void fully.focusTabByIndex(int index)
int fully.getCurrentTabIndex()
void fully.shareUrl()

void fully.closeTabByIndex(int index)
void fully.closeThisTab()
String fully.getTabList() // returns a JSON array
void fully.loadUrlInTabByIndex(int index, String url)
void fully.loadUrlInNewTab(String url, boolean focus)
int fully.getThisTabIndex()
int fully.getCurrentTabIndex()
void fully.focusThisTab()
void fully.focusTabByIndex(int index)

// Use $code placeholder in the resultUrl, see example below
void fully.scanQrCode(String prompt, String resultUrl)

// Ver. 1.31+, enhanced interface
// Use -1 for cameraId and timeout (in seconds) for defaults 
void fully.scanQrCode(String prompt, String resultUrl, int cameraId, int timeout, boolean beepEnabled, boolean showCancelButton)

// Ver. 1.43.4+, activate flashlight if needed
void fully.scanQrCode(String prompt, String resultUrl, int cameraId, int timeout, boolean beepEnabled, boolean showCancelButton, boolean useFlashlight)

// Ver. 1.31+, respond to QR events
void fully.bind('onQrScanSuccess','todo(\'$code\');')
void fully.bind('onQrScanCancelled','todo();')

// Open BT connection
// These functions are async, use events below to get results
boolean fully.btOpenByMac(String mac)
boolean fully.btOpenByUuid(String uuid)
boolean fully.btOpenByName(String name)

// Get info and close connection
boolean fully.btIsConnected()
String fully.btGetDeviceInfoJson()
void fully.btClose()

// Send data
boolean fully.btSendStringData(String stringData)
boolean fully.btSendHexData(String hexData)
boolean fully.btSendByteData(byte[] data)

// Respond to events
void fully.bind('onBtConnectSuccess','todo("$device");');
void fully.bind('onBtConnectFailure','todo();');
void fully.bind('onBtDataRead','todo("$data");');

bool fully.nfcScanStart();
bool fully.nfcScanStart(int flags, int debounceMs);
bool fully.nfcScanStop();
void fully.bind('onNdefDiscovered','todo("$serial", "$message", "$data");');
void fully.bind('onNfcTagDiscovered','todo("$serial", "$type", "$message", "$data");');
void fully.bind('onNfcTagRemoved','todo("$serial");'); // Android 7+

// The second parameter is a String containing JavaScript code to perform
void fully.bind('screenOn','todo();')
void fully.bind('screenOff','todo();')
void fully.bind('showKeyboard','todo();')
void fully.bind('hideKeyboard','todo();')
void fully.bind('networkDisconnect','todo();')
void fully.bind('networkReconnect','todo();')
void fully.bind('internetDisconnect','todo();')
void fully.bind('internetReconnect','todo();')
void fully.bind('unplugged','todo();')
void fully.bind('pluggedAC','todo();')
void fully.bind('pluggedUSB','todo();')
void fully.bind('pluggedWireless','todo();')
void fully.bind('onScreensaverStart','todo();')
void fully.bind('onScreensaverStop','todo();')
void fully.bind('onDaydreamStart','todo();')  // ver. 1.39+
void fully.bind('onDaydreamStop','todo();')   // ver. 1.39+
void fully.bind('onBatteryLevelChanged','todo();')
void fully.bind('volumeUp','todo();')
void fully.bind('volumeDown','todo();')
void fully.bind('onMotion','todo();') // Max. one per second
void fully.bind('onDarkness','todo();') // Requires screen off on darkness
void fully.bind('onMovement','todo();') 
void fully.bind('onIBeacon','todo("$id1","$id2","$id3",$distance);')
void fully.bind('broadcastReceived','todo("$action","$extras");'); // 1.40.2+
void fully.bind('onQrScanSuccess','todo("$code","$extras");');

void fully.startApplication(String packageName)
void fully.startApplication(String packageName, String action, String url)  // Can put null to omit the parameter in ver. 1.33+
void fully.startIntent(String url)
void fully.broadcastIntent(String url)     // ver. 1.31+
boolean fully.isInForeground()
void fully.bringToForeground()
void fully.bringToForeground(long millis)   // Delay in ms
void fully.bringToBackground()              // ver. 1.31+
void fully.installApkFile(String url)       // ver. 1.36+
void fully.enableMaintenanceMode()          // ver. 1.39+
void fully.disableMaintenanceMode()         // ver. 1.39+
void fully.setMessageOverlay(String text)   // ver. 1.39+
void fully.registerBroadcastReceiver(String action)   // ver. 1.40.2+
void fully.unregisterBroadcastReceiver(String action) // ver. 1.40.2+

void fully.startMotionDetection()
void fully.stopMotionDetection()
boolean fully.isMotionDetectionRunning()
String fully.getCamshotJpgBase64()
void fully.triggerMotion()
void fully.bind('onMotion','todo();') // Triggered max. once per second

String fully.getStartUrl()
void fully.setStartUrl(String url)

// Look in Remote Admin settings for the settings keys
String fully.getBooleanSetting(String key)
String fully.getStringSetting(String key)

// Changes apply immediately
void fully.setBooleanSetting(String key, boolean value)
void fully.setStringSetting(String key, String value)
void fully.importSettingsFile(String url)   // ver. 1.36+

<!-- Make actions -->
<button type="button" onclick="fully.openWifiSettings();">Wifi</button>

<!-- Show device info -->
<button type="button" onclick="alert(fully.getMacAddress());">Mac address</button>

<!-- Play Text to Speech -->
<button type="button" onclick="fully.textToSpeech('How do you do?','en_GB');">Say hello</button>

<!-- Change Fully Kiosk settings -->
<button type="button" onclick="fully.setStringSetting('screenBrightness','255');">Full brightness</button>
<button type="button" onclick="fully.setBooleanSetting('motionDetection',true);">Enable MD</button>
<!-- Listen for events -->
<script>
function myMotion() { alert("Motion"); }
fully.bind('onMotion','myMotion();');
</script>

<!-- Listen for iBeacon -->
<script>
function onBeacon (id1,id2,id3,distance) {
  alert("iBeacon found: "+id1+"/"+id2+"/"+id3+" in "+distance+" meter");
}
fully.bind('onIBeacon','onBeacon("$id1","$id2","$id3",$distance);');
// You can also use $mac, $name, $type, $manufactorer as placeholders
</script>

<!-- Scan QR Code -->
<script>
<button type="button" onclick="fully.scanQrCode('Prompt text','javascript:alert(\'$code\');');">Scan QR Code</button>
</script>
<!-- Identify Fully Kiosk Browser -->
<script>
if (typeof FullyKiosk !== "undefined")
  document.writeln("<h1>Fully Kiosk working</h1>");
</script>

<!-- Print on Bluetooth Printer -->
<script>
fully.bind('onBtConnectSuccess','alert(\'BT connected: $device\');
fully.bind('onBtConnectFailure','alert(\'BT failed\');');
fully.btOpenByUuid('0000110a-0000-1000-8000-00805f9b34fb');
</script>
<button type="button" onclick="alert(fully.btSendHexData('68656c6c6f0a'));">btSendHexData()</button>
<button type="button" onclick="alert(fully.btSendStringData('Hello\n'));">btSendStringData()</button>
<button type="button" onclick="alert(fully.btSendByteData(new Uint8Array([104, 101, 108, 108, 111, 10])));">btSendByteData()</button>

With 300+ options Fully Kiosk apps can be configured for many different use cases. Don’t be afraid. Usually you have to change only very few options. Just to give you some ideas for the most common scenarios:

1. Let users only to browse a set of allowed websites
   Use Fully Kiosk Browser app. Set the Start URL, configure the URL Whitelist for the allowed websites, configure Web Auto Reload setting to return to the Start URL on some condition. Enable the Kiosk Mode and enjoy.
2. Play some images, videos or websites in a loop (without user interaction)
   Use Fully Video Kiosk app. Configure the Playlist, enable the Kiosk Mode and voila.
3. Allow using some set of apps
   Use Fully Kiosk Browser app. Configure the Universal Launcher with the allowed apps and enable the Kiosk Mode. You can also add websites or file bookmarks.
4. Lock device and auto-start one specific app
   Use Fully Single App Kiosk app. Very easy to configure: select the app, set the PIN and start the Kiosk Mode. Add other allowed apps to the App Whitelist option if needed.

Please also check the recommended settings for unattended devices for the best kiosk mode protection.

Fully Kiosk uses Android Webview (Chromium based) provided by Android on your device for any website loading, caching, rendering and scripting (incl. embedded videos etc.). Fully Kiosk can’t select another web engine or change a lot about how Android Webview is handling websites. If something is wrong with your website please follow these topics:

1. Check and update the available Android Webview on your device.

You can check the available Webview version and provider app in Fully Settings >> Other Settings >> Device Info. The websites could run into some issues if the installed Webview is not up to date.  In this case you should install/update the Webview provider app from Google Play or by appropriate APK from APKmirror.com.  Some devices can only update the Webview by system update, check this FAQ and this FAQ.

On Android 5+ the Webview is provided by one of these apps that can be installed and updated separately:

• Android System Webview (com.google.android.webview)
• Google Chrome (com.android.chrome) – only in Android 7, 8 and 9

On some devices you can choose the Webview provider app in Android Developer Settings (also available in Fully Settings >> Advanced Web Settings >> Select Webview Implementation). In some cases you have to uninstall/disable one provider app in order to use another one as Webview provider. There are however no differences known between Webviews provided by those two apps (if on the same version). Read this for more technical details.

Note that the current Android Webview is only available for Android 7+ devices. For Android 5 the latest available Webview version is 95. For Android 6 the latest available Webview is 106. If you experience any issues with outdated Webview upgrading the Android version or replacing the device is the only way to go.

Note that Webview can only use the trusted root TLS certificates installed in your Android device that can cause issues with some websites in Android older that 7.1.1. Check this FAQ.

2. Check your website is working properly in Google Chrome on the same device.

If your website isn’t working properly with Google Chrome on the same Android device Fully Kiosk probably won’t make it better, even if the latest Webview is installed. Please optimize your HTML/CSS/JS code for Chrome on Android. Do not compare to other browsers (Firefox, Dolphin, Opera etc.) or other platforms (Windows, Mac). Those web engines may work significantly different in some details. A few Google Chrome APIs are not available in Android Webview, check known issues.

3. Check your website with Remote Webview Debugging.

If your website is running ok in Google Chrome but not in Fully Kiosk Browser web developers can enable Webview Content Debugging in Advanced Web Settings and use the remote debugging with Chrome Developer Tools in order to see what happens behind the scenes and where the different behavior comes from.

If some colors are showing wrong switch OFF the Dark Mode in app settings.

Please also check the Web Content Settings in Fully Kiosk. If something (like popups, form data saving, geolocation, alert boxes etc.) isn’t working it can be caused by a restriction controlled by Fully. In very rare cases you can improve the rendering by selecting another Graphics Acceleration mode in Advanced Web Settings. Please also check the known issues.

Fully Kiosk Browser doesn’t select or force any screen resolution. Note that devicePixelRatio bigger than 1 can be set for your high resolution screen by the Android Webview. This affects the CSS pixel size reported by window.screen.width and window.screen.height. We are unable to change this by our app. Check you have the latest Android Webview available on your device and let your web developers learn in this training and this answer how to support high resolution screens (FullHD, 4K) properly.

Starting some point in 2024 your website can fail loading in Fully Kiosk on Android versions older than 7.1.1. This is because of the missing ISRG Root X1 root certificate used by many websites certificates signed by Let’s Encrypt. Android Webview can only use the trusted root certificates installed in your Android device. You can ask your website provider to use a certificate supported by the older Android versions. Or you can download and install ISRG Root X1 and Let’s Encrypt R3 certificates manually on your device in Android Settings > Security > Credential Storage > Install from SD Card (or similar). In Fully Kiosk Browser 1.55.3+ we allowed the ISRG Root X1 and ISRG Root X2 certificates to mitigate this issue.

If you’ve installed the latest Android Webview and Google Chrome but Fully Kiosk still shows an outdated Webview version in the Device Info box (in Other Settings) your Android device likely has an AOSP ROM where you can’t update the Webview. The integrated Webview has another app ID (com.android.webview) than one provided by Google Play (com.google.android.webview). Read this for more technical details. So the new Webview will be installed side by side but the old integrated Webview will still be used by Android system (and it’s app ID is hardcoded in Android OS). On rooted devices you can use this Magisk module to select another Webview. There has also been a discussion at Chromium with backgrounds why is it done like this. Sorry, this is something where Fully Kiosk can’t change anything. Please ask you device vendor for a Webview update.

Devices running Android 12+ will have some kiosk mode protection gaps if you don’t follow the recommendations in this FAQ. This is something we can’t completely solve by an app upgrade due to new restrictions built-in in Android 12+:

• The system status bar (on the top) can always be pulled down and the buttons on the notification area can be used. The user however still can’t open Android Settings or other apps if Advanced Kiosk Protection enabled.
• The Power Dialog can be opened by a long power button press. The user can power off or restart the device or make an emergency call.
• The Recent Task view can be opened and the buttons there (Screenshot etc.) can be used on some devices. The user still can’t change to another app.

In order to maintain the secure kiosk mode with Android 12+ you have three options:

1. Use the device provisioning, enable Disable Status Bar option in Device Owner Settings, enable and configure the Lock Task Mode in Device Owner settings.
2. On the most Samsung devices you can use the options Disable Status Bar, Hide Navigation Bar and Disable Power Button in KNOX Settings.
3. After installing the kiosk app from APK on our website (not from Google Play!) look in Android Settings for Accessibility and enable Fully Kiosk as accessibility service. This will enable the status bar and system dialog protection in Kiosk Mode again. In Android 13+ devices the Fully Kiosk option may be disabled and greyed out in Accessibility Settings ( shows “Restricted setting” box). You can enable it by opening the App Info for Fully Kiosk (hold the app icon), clicking on three dots in the right upper corner and selecting Allow restricted settings.

If your device is already on Android 11 please check this page and ask your device vendor if your device will be upgraded to Android 12 and if there is a way to prevent the update. On Samsung devices you can disable the OTA update using the KNOX settings. Check this article for other ways to disable the OTA updates. If there is a risk that your device will upgrade or auto-upgrade to Android 12 please follow the recommendations above.

Some users are reporting an issue (“Couldn’t sign you in. This browser or app may not be secure”) when trying to login to the Google Account in Fully Kiosk Browser.

For security means Google obviously decided to disallow using the Google Account also in Android Webview (that is used by Fully Kiosk and many other apps). For now the Android Webview however doesn’t seem to be blocked 100%. Depending on something (OS, version, network or location?) some users still can login in Google Account while other users experience this issue.

The official solution should allow less secure apps to login as described here. However users reported that it doesn’t have any effect for Android Webview.

The working workaround for now is to select Edge as Fake User Agent in Fully Kiosk Advanced Web Settings. However no idea how long this can work. If Google really decides to block all logins in Android Webview there will be no workaround anymore. This is unfortunately something out of our control.

If your webcam video requires Basic HTTP Authentication (it’s URL starts with http://user:auth@host…) and you embed this video in your page by using the <img> oder <video> tag it probably won’t work as the authentication for embedded contents is not allowed in Android Webview (as well as in Google Chrome on Android) for security reasons. For more information please read the discussion on this topic at Chromium Bugtracker. This is something Fully can’t change. The only known workaround is using the video proxy.

If your website is loaded as HTTPS document and your webcam URL is HTTP, so it might blocked as it’s not allowed to mix secure and non-secure contents. You can try changing the Mixed Content Mode option as workaround. However Android Webview 111+ has a known bug and often blocks all mixed content, so this option doesn’t work anymore.

If your camera stream is RTSP you can’t embed it into your website with <video> tag as this is currently not supported by the Webview. Check this FAQ for alternatives.

You can use a file URL to address local files each time an URL is required in Fully. The full file URL looks like file:///sdcard/path/to/file.html Note the triple slash and that /sdcard usually refers to internal shared storage. You can use the file picker in URL dialog boxes to pick the file from storage. You can also select a file on external SD card. The path to external SD card will be saved in settings as /sd_ext and replaced by the real path on each device dynamically. Note that Fully Kiosk doesn’t support any write access to external SD card due to restrictions in Android OS.

Note the any links to local files or embedding local files from HTTP/HTTPS documents are disabled by Android Webview for some security reasons. But you can use the Localhost File Access option in Advanced Web Settings in order to access local files using https://localhost/… or http://localhost/… address. The full URL for a local file should look like https://localhost/sdcard/path/to/file.mp4. So you can for example embed the local video/image files in your HTTPS website.

If your devices are using Android 11+ or Android 11 OTA upgrade is pending please urgently attend to the scoped storage restrictions.

You can use the Load ZIP File button in Remote Admin and Fully Cloud to download and unpack a ZIP file to /sdcard (or to the app-specific storage in Android 11+ scoped storage mode) on the device. Note that /sdcard usually refers to the internal shared storage (not to the external SD card!) on most devices. You have to put the ZIP file on some web server where it can be accessed by the device and provide the HTTP/HTTPS URL. This is the way to make a light local content management. Use with care as all existing files will be overwritten when unpacking the same file names from the ZIP file. Avoid non-latin letters in the packed file/folder names or make sure the packer is using UTF-8 encoding. When using this feature from Fully Cloud you can load ZIP file to many devices with only one click (mass admin). You can set the File Load Timeframe in Cloud Settings in order to randomize the file loading across devices within the specified timeframe (next x seconds).

Starting ver. 1.43 you can force unneeded files to be deleted when unpacking if you put files of zero size in the ZIP file. Zero size files will be not extracted but deleted from device. Starting version 1.44 you can put a file .delete into ZIP archive containing the list of files and folders to remove before unzipping. So you can update the whole folder content and don’t care about filenames. Sample ZIP file is here.

You can use the Load Content From ZIP File option in Device Management settings in order to download and unzip file from some URL to /sdcard (or to the app-specific storage in Android 11+ scoped storage mode) folder automatically. Fully Kiosk will check each hour for updates on this URLs (according to servers Last-Modified HTTP response header). On the first app start the ZIP file will be downloaded prior to loading the Start URL. Use Auto-Reload on Idle option to reload the Start URL when device is not in use in order the updated local files can take effect.

For hosting the ZIP files you can now use the File Storage in Fully Cloud. If you need a bigger storage, please note that ZIP file download currently can’t work properly with files on Google Drive as Google Drive doesn’t provide Last-Modified time. If you don’t have your own webserver we recommend using Dropbox for bigger ZIP file hosting. The download URL must then look like this: https://www.dropbox.com/s/k7xdrtk8ujvqyf0/archiv.zip?dl=1

You can see the results of long running download commands in Fully Log on the Remote Admin. We recommend enabling the maintenance mode during changing content files on the devices.

You can also use the JavaScript API to silently download/unpack files, list files, delete files or folders from your website.

Of course you can also use some other file sync app to sync local files with remote storage. However you likely can’t install/configure that app automatically like Fully Kiosk.

Starting Android 14 Google/Android enforces a privacy concept for restricting apps from using the camera and microphone when the app is not in use. Starting Fully Kiosk Browser ver. 1.56, Fully Single App Kiosk 1.16 and Fully Video Kiosk 1.15 our kiosk apps will comply with this enforcement. Good news: The restrictions only apply to Android 14+ and only if you update to the app versions listed above from Google Play. If you install APK files from our website the  restrictions will be not active and the motion detection should work stable even if another app is in foreground or the screen is off.

Starting Android 11 Google/Android enforces a privacy concept called scoped storage. In short: Normal apps can’t access most of files on the device public storage anymore. Starting Fully Kiosk Browser ver. 1.44, Fully Single App Kiosk 1.8 and Fully Video Kiosk 1.8 our kiosk apps will comply with this enforcement. Good news: The restrictions only apply to Android 11+ and only if you update to the app versions listed above from Google Play. Currently if you install APK files from our website the scoped storage restrictions will be not active.

Attention: Starting Fully Kiosk Browser 1.57, Fully Single App Kiosk 1.17 and Fully Video Kiosk 1.16 we will comply with the latest File Access Permissions Policy (2024). Our kiosk apps wont have any access to any files on the public shared storage (/sdcard). Please move all needed local files to the app-specific storage (/sdcard/Android/data/<appid>/files) using some file management app or ADB prior to updating the app. The Fully Kiosk apps installed from APK files will also run into this restriction however you will have an option to manually grant the Manage All Files permission in order to access all files on /sdcard.

If your kiosk app is running in scoped storage mode:

• You will see a hint Storage mode: scoped on the Device Info box in Other Settings.
• The kiosk app can only browse, pick and play media files from the public shared storage (not after the FKB 1.57 update!), however not other files like HTML or PDF. The app can’t write/delete any files on the public storage (also not by JS/REST API). You will see warnings in the File Picker and on the File Management page in Remote Admin.
• For other local files we recommend using the app-specific storage located at /sdcard/Android/data/<appid>/files. At this location all files are visible, readable and manageable by our kiosk app (and only that app). If you uninstall the Fully Kiosk app the app-specific storage however will be removed.
• The Load Zip File feature will unpack files into app-specific storage, not into the public /sdcard folder. All file download will be saved in the app-specific storage as well.
• If you use any local files at other locations move them to the app-specific storage prior to device upgrade to Android 11.

If you need only few bookmarks and you don’t use the Kiosk Mode please check the Add to Home Screen feature on the menu.  The current page link shortcut will be added to your Android’s Home Screen.

Otherwise you can add your favorite websites to the Universal Launcher and use it as your bookmark page. You can even seamlessly mix apps, websites and file shortcuts on the launcher.

You can specify multiple Start URLs (type one URL per line and press Enter to start new line). The URLs will be opened on separate tabs. You can enable visible tab flaps and set colors in Toolbars and Appearance settings. In Web Browsing Settings you can also enable Swipe to Change Tabs to be able to change between tabs by swiping left or right.

There are also some JavaScript and REST APIs available to manage tabs programmatically. You can still use the usual JavaScript methods window.open() and window.close() to open and close new tabs.

Configure the Screensaver Playlist in Screensaver settings. You can add media files, folders, URLs to media files or websites. Look in each item configuration for the Play next item after… option, otherwise it may be shown forever. You can also  change the Wallpaper URL if you don’t like the default black background and set the Screensaver Brightness for the display. Let Keep Screen On option in Fully Kiosk Device Management Settings enabled and do not use any Android Display Settings. Now set the Screensaver Timer in order to start the screensaver after some time of user inactivity. If you are going to use the Fully Screensaver with other apps please enable the Touching Other Apps Restarts Idle Timer in Fully’s Other Settings.

When the device screen is completely off you usually can’t wake up the device as the switched off display can’t recognize any taps. You can use display dimming instead of screen off by setting the Screensaver Timer to the delay in seconds and Screensaver Brightness to 0. Also keep the Screensaver Wallpaper URL at fully://color#000000 for the maximum darkness. The real dimming level is depending on the device. You can then wake up by tapping the screen.

If you need to use the Screen Off Timer feature consider using different Motion Detection, Device Movement Detection or REST Interface alternatives for waking up the device.

Many new devices can be woken up by tap or double tap. Check the Android Settings for this option.

You can have up to 6 keys when working with Fully:

• The Kiosk Mode PIN set in the Fully Kiosk app is needed to get out from the Kiosk Mode. Default PIN is 1234. If the PIN is empty the PIN dialog will be omitted. If you forget the Kiosk Mode PIN check this FAQ how to exit.
• The Wifi/Settings PIN set in the Fully app only allows to access Wifi or other Android Settings in Kiosk Mode. You can give this PIN to someone who is only allowed to manage Wifi or other connections/settings but may not change anything else on the device or in Fully Kiosk settings.
• The Remote Admin Password is set in the Fully Kiosk app settings on each device. You need this password to login to Remote Admin interface locally at http://ipaddress:2323/ or use the REST API. When adding device to your Fully Cloud Account you have to specify this password in order to allow Fully Cloud talking to the device. If this password is not set in the Fully app or you forget it you can’t connect locally to Remote Admin interface and you can’t add this device to the Fully Cloud.
• The Fully Cloud Account Password is used with your email to login to Fully Cloud. If you forget the Fully Cloud password you can make password recovery with your email address.
• The Fully Cloud API Access Token is needed for using Fully Cloud REST API. This token can be grabbed in Fully Cloud Settings.
• The Fully PLUS Volume License Key is a secret key sent to you when you order a volume license. You can activate a PLUS license for current device by entering this key in Fully’s Other Settings. You can also add all devices activated by the specified Volume Key to the Fully Cloud account at once.

You can change the Kiosk Mode PIN, the Wifi PIN, the Remote Admin Password and the Volume License Key via Remote Admin interface (locally or in Fully Cloud) in View/Edit Settings. For security reasons you cannot change the Remote Admin Password by importing a setting file via Remote Admin.

This topic can be confusing sometimes. The Fully PLUS License and Fully Cloud Subscription are two separate products which are working independent from each other.

• Fully PLUS License is for using all PLUS features in the Fully Kiosk App. It’s 7.90 EUR/device (plus VAT) one-time payment. (The price on Google Play can be slightly different.) Volume pricing is available. With a Fully PLUS License you can also use the Fully Cloud Basic Features for free. Find more information here.
• Fully Cloud Subscription is additionally required for using the Fully Cloud Advanced Features. It’s a recurring payment max. 1.18 EUR/device per month (plus VAT) incl. 15% discount on annual payment etc. Check here for the feature list and more information.

You can try all features of the Fully Kiosk app and cloud for one month for free. Just install the app from our website and register for the free Fully Cloud EMM account.

For all completed PayPal for Fully PLUS License we sent automatically an email from info@fully-kiosk.com to your PayPal email address. Also please check your SPAM folder. Please use an invoice link in that email to get your invoice.

For all completed credit card (Stripe) payments for Fully PLUS License we sent automatically an email from info@fully-kiosk.com to the email address you put on the order form. Also please check your SPAM folder. Please use an invoice link in that email to get your invoice.

For all Google Play orders you can find the receipts and request VAT invoices in your Google Account.

For completed Fully Cloud subscription payments please find your invoices in your Fully Cloud account in Menu >> Subscriptions >> Payments >> View >> Get Invoice.

You can now use our License & Invoice Finder to get all missing links to invoices for payments associated with your email address.

For data protection reason we absolutely can’t send invoices to other email address than one provided in your order or your PayPal email address.

If you like to pay your Fully PLUS Volume License by bank transfer please get an invoice from here. Type your company name/address and click the link Get an Offer/Invoice for Bank Transfer Payment.

If you like to pay your Fully Cloud Subscription (20+ devices) by the bank transfer you can get an offer in your Fully Cloud account (Menu >> Subscriptions).

You have to make the Kiosk Exit Gesture in order to see the Kiosk PIN dialog box. Depending on Fully settings the Exit Gesture can be one of following:

• Swipe from Left (default)
• Long press Back Button
• Fast 5 Taps anywhere (in Fully Kiosk only)
• Fast 7 Taps anywhere (in any app)
• Double Tap Top Left Corner plus Double Tap Bottom Right Corner (all must be done within 3 seconds)

The default Kiosk PIN is 1234

If you can’t exit the Kiosk Mode or can’t remember your Kiosk PIN there are following ways to escape:

1. If you have Remote Admin or Fully Cloud access to your devices, you can change the PIN or unlock the Kiosk Mode (ver 1.37+) via Remote Admin or Fully Cloud.

2. If you installed the app from APK file and not disabled the Settings Auto-Import in Other Settings, you can attach your device by USB cable and put the fully-once-settings.json file (rename in fully-video-once-settings.json for Fully Video Kiosk or fully-single-app-once-settings.json for Fully Single App Kiosk app) disabling the kiosk mode to the main folder of the internal shared storage (/sdcard). Then restart the device in order to auto-import the settings file.

3. If you have not enabled the Lock Safe Mode option in Fully Kiosk Mode settings, by Device Owner Settings or by KNOX Settings, you can boot into safe mode (ask your vendor for instructions with your device, usually you have to press some buttons during the boot) and uninstall Fully Kiosk. If you can’t uninstall Fully Kiosk in safe mode you can look in Android Settings for Home App and select the standard Android Home App.

4. Otherwise the Factory Reset is the only way to reuse the device.

There is no backdoor available in our apps for good reasons.

If you get the PIN dialog triggered accidentally when you are tapping fast 7 times or typing in another app you can choose one of these solutions. Try carefully!

1. Enable the Single App Exit by Remote Admin Only option in Kiosk Mode Single App Mode settings. This will disable the PIN dialog by 7 fast taps. You will only be able to exit from single app mode by the Remote Admin Unlock Kiosk button. Remote Admin must be activated in order this option to have effect. (ver. 1.32+)

2. Download, adjust the value in the JSON file  fully-tapsToPinDialogInSingleAppMode.json and import this settings file. This will alter the number of fast taps required to show the PIN dialog in Single App mode.

3. Detect fast taps only within first X ms after screen on. So you have to switch the screen off and on before tapping. Download, adjust and import the file fully-millisScreenOnToPinDialogInSingleAppMode.json

On the modern Android systems the normal apps don’t have access to permanent device identifiers like mac address or serial number for privacy reasons. We try to get the best Device ID based on the data available in your Android and your device. But if you reset the device or even reinstall the app the Device ID can change and we have no chance to recognize the device again. In this case you have to move a single Fully PLUS License to the new Device ID. For the Fully PLUS volume license you are required to unregister the device prior to device reset or app uninstall.

You can avoid changing Device ID if you use the device provisioning for device setup (recommended!) and don’t turn the Wifi on/off. On provisioned devices our kiosk app can access the permanent device identifiers.

If the Fully Kiosk app disappear randomly it may be crashing or being killed by Android OS. The 99% of such issues happen in the Android Webview that still has tons of known bugs (e.g. known memory leaks when using CSS animations).

1. The Android Webview can crash after some time due to high website complexity and resource usage what we unfortunately are unable to catch. You can try running a simple page like www.google.com. If the Fully Kiosk Browser doesn’t crash anymore then that’s 100% a Webview issue. Crashes like this usually start and stop due to some updates on the particular website or Android Webview updates. You can only prevent these crashes by upgrading/downgrading the Webview or simplifying your website.

2. If Fully Kiosk suddenly started crashing on each app start it could be introduced by a buggy Webview update like that in March 2021. We recommend disabling Webview/Chrome auto-updates once tested to avoid such risks. Please use device provisioning to be able to remote update the Webview manually when needed.

Enable these options in Other Settings in order to try the app auto-restart after all stops: Restart Fully After Crash, Restart Fully After Update, Run as Priority App. The Fully Kiosk restart mechanisms work best if Keep Screen On and Kiosk Mode options are enabled. Additional crash detection was added in Fully Kiosk Browser 1.54.  Note that we can’t guarantee a restart in some cases because our app is just a non-system app that can’t override the power of Android OS.

When Fully Kiosk is auto-restarting after crash there is a log entry, check the Fully Log in Remote Admin. If you want to know exactly what/how is crashing  you can get and analyze a bug report just after crash on your device. If you can’t make a bug report just after crash you can connect your device to the PC and record the Logcat permanently by ADB tools using a command like /path/to/adb logcat >logcat.txt and analyze the resulting file.

If your network is firewall protected for the Fully Cloud remote management you need to allow devices to access https://api.fully-kiosk.com and https://remoting2.fully-kiosk.com For Fully PLUS activation/deactivation devices also need access to https://licensing.fully-kiosk.com All communication to our servers is done by standard HTTPS.

If you use Enterprises please also check these network requirements.

1. If you only show websites in Fully Kiosk Browser or play media in Fully Video Kiosk the immersive fullscreen mode which is enabled by default is usually a sufficient solution. The system bars (status bar at the top and navigation bar at the bottom) are invisible but can be pulled up and disappear shortly.

In Kiosk Mode the system bars will be made useless. With Android 8+ the status bar can be pulled down in the Kiosk Mode but automatically collapse back so it’s still not usable on the majority of devices. You can use device provisioning or KNOX features for a better status bar protection.

In Android 12+ the status bar can be pulled down in kiosk mode. Check this FAQ for solutions.

2. If you start other apps it’s the responsibility of other apps to show the system bars or put them into immersive mode. We can only force other apps by our experimental Force Immersive Fullscreen option. Be aware of hard limitations of that option. All the keyboard input and back button will be out of order in other apps.

3. On provisioned devices you can use the lock task mode to securely lock/remove the status bar and reduce buttons on the navigation bar.

4. On Samsung devices you can use KNOX settings to disable the system bars or remove system bar contents.

5. With Android 10 and older you can use the status and navigation bar complete removal options which might work with majority of devices and all apps.  These options however require additional permissions that can only be granted using ADB.

• Download and install the Android Debug Bridge (ADB) tools for Windows, Mac or Linux
• Enable Developer Options and USB Debugging on the device (Howto)
• Connect your device to the PC via USB and confirm connection
• On the computer run this command in your ADB folder to grant permission

adb shell pm grant de.ozerov.fully android.permission.WRITE_SECURE_SETTINGS

For Fully Single App Kiosk use com.fullykiosk.singleapp, for Fully Video Kiosk use com.fullykiosk.videokiosk, for Fully Kiosk Browser Deployment edition use com.fullykiosk.emm instead of de.ozerov.fully in this command.

If something goes wrong while the system bars are removed you can easily un-remove them with following ADB command:

adb shell wm overscan 0,0,0,0

After granting permissions enable Remove Navigation Bar and Remove Status Bar options in Device Management Settings to remove the system bars.

In  Fully Kiosk Browser the Web Content Settings >> URL Whitelist setting can contain one or many URLs which are allowed to load. If you specify some whitelist URLs all other URLs will be blocked, you don’t have to put anything on the URL blacklist. The URLs added to the Universal Launcher will be auto-whitelisted automatically.

URL Whitelist is a multiline text field. Please type one URL per line and use the enter key on the keyboard to start a new line. You have to specify full URL including https:// and all query parameters. However you can use * as wildcard. For example, if you have to enable all Google and Youtube pages you can type these two lines into the whitelist setting:

*google.com*
*youtube.com*

So all URLs including “google.com” or “youtube.com” will be allowed, regardless http or https, with or without www subdomain. In most cases the list above will be a sufficient whitelist.

You can narrow the whitelist using a line like this which only allows Google Maps, regardeless http or https:

*://maps.google.com/*

Or be even more precise. This one must be https, http will be filtered out:

https://www.google.com/maps?hl=de&*

Anyway it’s a good idea to put a star wildcard at the end of the URL.

If the Wifi/ethernet connection of the device is not available immediately on device start you should keep the option Wait for Network Connection enabled. With this option Fully Kiosk Browser will not try to load any pages until a connection is established.

Put the Custom Error URL to detect website load errors and show a nice error page instead the default one. In Fully Kiosk Browser 1.45+ you can just use the nice embedded fully://errorpage URL for that. If something goes wrong when loading a web page the user will see the error page instead.

If you want the user to see the error page in case of Internet Disconnection immediately (without loading the next page – which can be frustrating) use the Load Error URL on Disconnection option. The real Internet connectivity is checked by pinging the IP address 8.8.8.8 every 10 seconds. You can change the IP address to ping by a hidden option in Fully Kiosk: get this JSON settings file, edit and import it into Fully Kiosk.

Enable the Auto reload on Internet Reconnect option in order to come back to the right website automatically once the Internet connection reappeared.

If you only want to play a video playlist please check out our Fully Video Kiosk app.

There are also several ways to play videos in Fully Kiosk Browser:

1. HTML5 videos – can be embedded in a webpage by <video> tag, controlled from HTML, support only few video formats (depending on Webview/Android version, usually no RTSP support). These videos can be autoplayed by Enable Autoplay option and may go fullscreen if Enable Fullscreen Videos setting is on. Please note that Android Webview does not cache video files. You can use the Localhost File Access option in order to embed local video files in you website in order to save traffic.
2. Fully’s built-in video player – fullscreen only, the player can be started by opening the video URL (requires Play videos in Fully), with JS interface powerful function fully.playVideo() (requires Enable JavaScript Interface) or by REST API. Also the Screensaver playlist and Fully Video Kiosk playlists use this player. The video player engine is one of these:
   1. Android Media Player. This supports all Android media formats incl. many RTSP streams (depends on the Android version, media format/codec). Some video formats upscale to fullscreen, sometimes even with broken aspect ratio. This seems to be an Android Media Player bug with some Android versions
      
   2. Media3 Exoplayer (available in Fully Kiosk Browser 1.52+ and Fully Video Kiosk 1.14+ as EXPERIMENTAL feature, Android 7+ required). Supported formats include many DASH, HLS and RTSP streams.
3. Play fullscreen YouTube videos/playlists in Fully Kiosk (no controls) by opening the URL fully://youtube/video/[videoId] or fully://youtube/playlist/[playlistId] (requires ver. 1.26+). Some YouTube videos however are restricted by the video owner and can’t play in other apps. October 2024: Playing Youtube Playlist is out of order right now due to the broken Youtube Iframe API.
4. External video player – depends on the external app, can support even more formats, see the FAQ for external app starting and restrictions

1. If you setup kiosk devices for another site and you know the Wifi Key/Password on that site you can specify these Wifi credentials in Force Wifi SSID and Force Wifi Keyphrase options on Fully’s Device Management settings. The device will then connect to that  Wifi network automatically when SSID detected. Note that with Android 10+ this feature is only available with provisioned devices.

2. If you don’t know the Wifi credentials you can setup a special Wifi/Settings PIN on Kiosk Mode settings and give this PIN to the administrator on site. When entering this Wifi PIN instead of the Kiosk PIN that person can open the Wifi settings and connect the device to the network without being able to exit the kiosk or change other settings. Be aware that this feature can break the kiosk with some devices (like many Samsung tablets) as they allow access from Wifi settings to all other Android settings. In this case please try to use the experimental Select Wifi Network option (for Android 10+ this option is working only with provisioned devices) or put the following Android Settings activities onto the App Blacklist.

com.android.settings/.Settings
com.android.settings/.homepage.SettingsHomepageActivity
com.android.settings/.Settings$ConnectionsSettingsActivity

If you want to lock down your device to a single app please check out our Fully Single App Kiosk app. You can setup a single app kiosk very fast using that app.

In Fully Kiosk Browser you can start other apps in many different ways:

1. By using the Universal Launcher. Add your apps to the launcher in Fully settings and show it by opening fully://launcher URL. The launcher is a special web page in Fully Kiosk which HTML code is looking like this. You can design the launcher appearance very flexible and easy by adding any HTML code to the <head> of the launcher page. When using the Universal Launcher, the Advanced Kiosk Protection will always be activated automatically.

2. By using the Single App Mode in Kiosk Mode settings (look in Kiosk Mode settings).

3. By opening a link to some file/content which is handled by external app – requires View Other Files option to be set to Pass URL/File/Content to External App

4. By opening an intent: scheme URL – requires enabled Open Other URL Schemes option. Samples for working Intent URLs are here:

intent:#Intent;component=com.skype.raider/.Main;end
intent:#Intent;component=com.android.mms/.ui.ConversationList;end

5. By calling JS Interface functions fully.startApplication() or fully.startIntent() – requires Enable JavaScript Interface is on

6. By using cmd=startApplication or cmd=loadURL with Intent URL on the REST interface

7. By using the experimental Application to Run On Start in Background/Foreground options. Technically the specified apps will be started on device startup by their launcher intent. Then Fully Kiosk push itself back to foreground if you use the start in background option.

You can allow other apps to go foreground in Kiosk mode by adding the app package name to Kiosk Mode >> App Whitelist. E.g. if you want to allow incoming Skype calls add com.skype.raider to the app whitelist.  If you are using the Task Lock Mode (on provisioned devices) you have to put the app also on the App Lock Task Whitelist if it must be allowed to start. Apps started directly by Fully Kiosk are whitelisted automatically und usually don’t need to be whitelisted.

If you need to find out the correct component name for some activity just add that app to the Universal Launcher and you will see the component name in the launcher item configuration. The part of the component name in front of the slash is the package name.

Restrictions when starting other apps:

• Unlike Fully Kiosk other apps usually don’t skip the lockscreen. So if your device is locked, the screen lock may be displayed when starting another app. This is unfortunately something Fully can’t change. Change Android settings in order to never lock the screen as workaround (unfortunately we can’t do it automatically). In Android 8+ you can try to unlock the Swipe screenlock by using the experimental Unlock Swipe Screen Lock option in Device Management settings. Read this FAQ for more details.
• Fully Kiosk can force many apps to run in fullscreen mode by the Force Immersive Fullscreen option. Be aware of hard limitations of this feature, no keyboard input or back button will be working. Check this FAQ for another option.
• For the correct working with Screensaver Timer or Screen Off Timer check Fully’s Other Settings for options controlling the idle features while another app is in foreground.
• While another app is in foreground, the recent task button and the power button are only restricted if Advanced Kiosk Protection is enabled. Advanced Kiosk Protection is always enabled automatically when using the Universal Launcher or the Single App Mode.
• Starting ver. 1.33 Fully Kiosk is trying to lock the Volume Keys even while another app is in foreground. You can get a better Volume Key lock by using the Device Owner Settings with provisioned devices or by using the KNOX features (on Samsung devices only)
• Another app can stay in foreground forever if the user doesn’t press back or home button. Consider using the Regain Focus After Idle Time option or JS interface functions fully.isInForeground() and fully.bringToForeground() to bring Fully Kiosk back in focus whenever.
• On some old devices with Android 5.x you have to enable the App Usage Stats Access permission for Fully Kiosk manually in Android Security Settings.

If you have the Screen Lock enabled in Android Settings your device will ask you for a swipe, PIN, Pattern or Password after booting the device, after locking the screen with the power button, after screen off and when starting other apps. This is normal Android behavior. Fully Kiosk can show itself “above” the screen lock if you enable Unlock Screen option in Device Management settings (enabled by default). But Fully Kiosk can’t skip or disable screen lock for other apps. For this reason, when starting other apps with locked device the lock screen may be displayed. Unfortunately this is something impossible to change without changing the target app.

In many cases it’s recommended to set Lock Screen in Android Settings to None as workaround to disable the screen lock at all. Unfortunately we can’t do it automatically from the Fully Kiosk app. On provisioned devices you also have to switch on the Disable Keyguard option in Device Owner Settings. If you have the swipe screen lock set you can also try using the experimental Unlock Swipe Screen Lock option in Fully Kiosk.

If the Screen Lock is disabled you won’t be able to use the Lock Safe Mode option in Kiosk Mode settings. Enabling the Lock Safe Mode option will setup the PIN screen lock automatically. Please use device provisioning to enable Device Owner Settings for a better safe mode lock. On the most Samsung devices you can reliably disable the Safe Mode using the KNOX Settings.

Note that Unlock Screen feature is not working with many Fire OS devices. Check this FAQ.

Using an External or Integrated Hardware Barcode Scanner

External or integrated QR code scanners usually have a control app like Datawedge. By default the scanner usually emulates the keyboard and can enter the scanned code into the web fields. However the web field must be enabled and focused for this. The code must be something textual, binary values will cause issues. In many cases however this could be a sufficient integration.

Fully Kiosk supports different ways for a better integration with external scanner apps or hardware QR scanners. Check Barcode Scanner Settings in Other Settings. You can let Fully Kiosk:

• Listen to the broadcast intent (RECOMMENDED) – many apps like Datawedge can send a broadcast intent when the barcode is scanned. It’s difficult to give exact steps for the configuration as the external scanner app can slightly change depending on its version. Look in your scanner app docs or look in the app settings for a Broadcast Action name and String Extra name and put those names into these options in Fully Kiosk Settings in order to listen to the broadcasts.
  • Barcode Scan Broadcast Intent Action – broadcast intent action from scanner app to listen for, empty for none. In devices using Datawedge app this can be something user defined or something  like com.datalogic.decodewedge.decode_action
  • Barcode Scan Broadcast String Extra – broadcast intent string extra from scanner to look for the scanned code in. In devices using Datawedge this can be something like com.symbol.datawedge.data_string or com.datalogic.decode.intentwedge.barcode_string

If you can specify the intent category in your scanner app then keep it empty.

• Listen to activity intent – some  barcode scanners can sent explicit activity intents when barcode is scanned. Just use de.ozerov.fully.action.barcode as action and put the barcode in the Intent String Extra code or specify the String Extra Name in the Fully’s String Extra option.
• Listen to keyboard input from scanner – useful with many hardware scanners that can emulate keystrokes when scanning a barcode (sometimes called keyboard mode or keystroke output). Look in your scanner app settings. This option should catch the input even without a focused web field however it isn’t working reliably with some scanner apps and isn’t recommended.

Note that the barcode readers may be unavailable if you use the Unlock Screen option in Fully Kiosk (enabled by default) until you unlock the screen manually.

Check below how to handle the resulting barcode.

Using Device Camera as Barcode Scanner

You can use the use the integrated camera of the device for QR Code scanning. You can start the QR Scanner by JavaScript interface scanQrCode() or the QR scan button on the action bar.

With JS API you can specify the prompt text and target URL, the camera ID, the timeout, enable/disable beep sound and show/hide the cancel button in the barcode reader UI using scanQrCode() function. Don’t forget to enable the Enable QR Code Scanner option in Advanced Web Settings. The HTML code sample for triggering barcode scanning:

<a href="javascript:fully.scanQrCode('Nice prompt text', 'https://domain.com/target/url/$code', -1, 60, true, true);">SCAN</a>

Handling Resulting Barcode

For handling the scanned barcode from barcode app or device camera you can use Barcode Scan Target URL, Insert Barcode Into Website and Submit Form after Inserting options. Look in the Configuration how to use these options. Also JS API and MQTT events will be sent.

If your website has a focused field for barcode input you can disable popping up the soft keyboard by switching off the Enable Text Input or switching on the Always Hide Keyboard option in Advanced Web Settings. This makes the keyboard unusable on all websites however. You can disable keyboard for selected barcode scan pages by using the Fully JavaScript Interface and Inject JavaScript option with a code like this:

if (location.href=="https://url_of_barcode_scan_page")
  fully.setBooleanSetting("softKeyboard", false);
else
  fully.setBooleanSetting("softKeyboard", true);

Note that disabling keyboard can make the Listen to Keyboard Input option not working with some scanner apps.

Using External App as Barcode Scanner

You can use a different barcode app like ZXing Barcode Scanner for scanning barcodes and getting codes back to web. The app must support zxing: URL scheme. Enable Open URL Schemes in Other Apps option in Fully’s Web Content Settings and use this HTML code to make a scan button:

<a href="zxing://scan/?ret=http://mydomain.com/path/to/page.html?item={CODE}">Scan Barcode</a>

After a barcode is scanned the scanner app will proceed to the specified return URL. Select Fully Kiosk Browser to be always the browser for handling this URL when asked. If another browser app is opened for the URL you have to clear defaults in the app settings for that browser app.

If you plan to run unattended devices check following topics in order to make your device locked and secure.

1. Reset Settings in Fully Kiosk (look in Other Settings) to get back to the recommended settings. Then double check every option you change. Enable the Kiosk Mode, set the Kiosk Exit Gesture and a good Kiosk Mode PIN. Enable the Remote Admin and set a fairly long Remote Admin Password. Enable Restart Fully options in Other Settings.

2. Use Device Provisioning to setup new devices. Switch ON the Disable Status Bar, Disable USB Storage, Disable ADB, Disable Boot in Safe Mode in Device Owner Settings.

3. On Samsung devices please also use the KNOX Settings for advanced protection.

4. On Android 11+ devices please attend to this FAQ for the secure kiosk mode.

5. Install the latest Android System Webview (for Android 5, 6 and 10+) or latest Google Chrome (for Android 7, 8 and 9) to avoid many Webview related issues.

6. Have a strategy for remote app installs/updates.

7. If you have enabled Google Play on the device please disable Fully Kiosk auto-updates. You can’t select the auto-update time and during auto-update your device will be not protected. Please also disable auto-updates for Android System Webview, for Google Chrome and Android System updates if possible.

8. If you have Google App installed please disable Google Screen Search, otherwise a long press on the Home Button can make strange things.

1. You can update Fully Kiosk and other apps remotely without user interaction by using the Managed Google Play Enterprise in Fully Cloud. Then your apps can be managed and updated through Fully Cloud in cooperation with Google Play for Work. An Internet connection to Google servers and device provisioning is required for this solution.

2. An app update/install from APK file button is available on Remote Admin and Fully Cloud for provisioned devices with Android 6+. The Disable Apps From Unknown Sources (Disable APK Installs) option must be switched off in Device Owner Settings. For automatic app install you can put the APK file URL into APK Files to Install option in Device Owner Settings. An APK file will be downloaded by Fully Kiosk from URL provided and installed silently. Note that this option is not available if you installed Fully Kiosk from Google Play. Google Play editions don’t allow installing APK files.

3. A silent app update/install is also available on devices with root access. If you have rooted devices please enable the Root Features in Fully Kiosk for silent remote update/install (ver. 1.37+).

4. In all other cases you only can tell Fully Kiosk app to download and start installing an APK file via Remote Admin. IMPORTANT: In these cases user input will be required ON THE DEVICE for confirming the installation.

With Fully Cloud EMM you can trigger the APK file install/upgrade for many devices at once. Now you can also host your APK files on the File Storage in Fully Cloud.

Note that you can’t downgrade the app without uninstalling it.

You can see the results of background app install commands in Fully Kiosk Log on the Remote Admin. Starting Fully Kiosk 1.50.3 installing and uninstalling APK files is not available if you installed Fully Kiosk from Google Play.

When updating the Fully Kiosk app itself it will be stopped. The kiosk protection will be lost for this moment. Fully Kiosk app will be restarted automatically after the update if you have Restart Fully After Update option enabled in Other Settings.

You can get a screenshot of the device screen in Remote Admin. Note that other apps and videos won’t be visible on that screenshot.

For remote screen sharing with an particular device you can use the Anydesk Remote Control app. For silent access you can configure the Anydesk app to  Never show incoming session requests and Enable unattended access with password. If you run Fully in Kiosk Mode you have to add the following activity to the App Whitelist otherwise Fully will kill the screen recording request.

com.android.systemui/com.android.systemui.media.MediaProjectionPermissionActivity

You can force the Android to bypass the screen recording dialog and resolve some other issues as described in this manual in order to have a silent integration. Also check the Disable Screenshots option is switched off in Kiosk Mode Settings and in KNOX Settings.

For configuring Fully Kiosk app and configuring devices we highly recommend you using Fully Cloud where you can do it for many devices with only few clicks.

Android 4.4 devices are just unsafe as there is no built-in support for TLS 1.2.  This makes all network communication of the device spoofable. Keeping support for these devices by our servers is potentially insecure. Thatswhy we stopped supporting Android 4.4 by the end of the year 2021.

The last app releases working with Android 4.4 are Fully Kiosk Browser 1.44.1, Fully Single App Kiosk 1.8 and Fully Video Kiosk 1.8. Newer releases don’t support Android 4.4 and can’t be installed at all. If your devices get updates by Google Play they will not get any Fully Kiosk updates anymore. You can keep using older versions, of course, with all PLUS features. However you can’t activate/deactivate a PLUS license or use Fully Cloud with those devices anymore.

Please be aware of the security and other issues in the old Android versions and the totally outdated Android Webview. We recommend an upgrade to some newer devices.

Nope. The devices change on the market every 3-4 weeks. We can’t test them all. And of course, we don’t test. There are also big quality differences even inside each brand or price segment. Please attend to the known issues and select a device according to your budget, quality and performance requirements. If you plan to show websites check that the Webview available on the device is up-to-date or can be updated by yourself. Please test the Fully Kiosk app with your devices and your contents thoroughly prior to deployment. Report any issues to info@fully-kiosk.com

Android Go devices with Android 10+ have some serious restrictions. Kiosk mode, visual motion detection and all features requiring the draw on top of other apps permission don’t work with Android Go Edition running Android 10+.

As a workaround you can grant this permission using ADB with following command:

adb shell pm grant de.ozerov.fully android.permission.SYSTEM_ALERT_WINDOW allow

For Fully Single App Kiosk use com.fullykiosk.singleapp, for Fully Video Kiosk use com.fullykiosk.videokiosk, for Fully Kiosk Browser Deployment edition use com.fullykiosk.emm instead of de.ozerov.fully in this command.

Users reported that this workaround has no effect on some devices with Android 12+.

Android TV is a feature reduced version of Android OS for large devices. The features are cut arbitrarily without a proper documentation and the resulting restrictions can change in an unpredictable way across different devices and Android TV versions.

Many Fully Kiosk features (like those requesting Device Admin or Overlay Permissions) are disabled in Android TV.

You can use the long press on the back button to open the menu instead on swiping.

Disabling the Home Button in Kiosk Mode is impossible out-of-the-box on the most Android TV devices. You can however run the kiosk mode “light” where the home button is not locked. If your device is not touchscreen and you hide the remote this might be a sufficient protection.

adb devices
adb shell pm set-home-activity com.fullykiosk.videokiosk/.LauncherReplacement
adb shell pm disable-user --user 0 com.google.android.tvlauncher

adb shell pm enable --user 0 com.google.android.tvlauncher
adb shell pm set-home-activity com.google.android.tvlauncher/.MainActivity

On some Android TV devices also the Launch on Boot option doesn’t work and other restrictions may apply. Try using the Grant All Permissions button or using the workaround for Android Go device in this case to grant the Draw on Top permission.

On some Android TV devices Fully Kiosk can't show fullscreen or in the correct orientation. This is something we can't fix currently.

Amazon's Fire OS is a very special Android derivative. We absolutely can't recommend using Fire OS devices in any production environment as Amazon seems to be hunting apps overriding the standard launcher. Showing you advertising whenever possible is one of the reasons why Fire OS devices are cheaper than usual. So even if Fully Kiosk is working fine for now make sure your device will never get an Fire OS update where anything will be broken. You've been warned.

Please install Fully Kiosk apps on Fire OS from APK files on our website. Fully Kiosk Browser, Fully Video Kiosk and Fully Single App Kiosk allow enabling the Kiosk Mode with Fire OS without any third party tools. It has been tested with some Fire OS 5, 6 and 7 devices. However even the minor Fire OS change can have effects.

Please uninstall apps like Launcher Hijack. If you have Google Play on your device please don't install Fully Kiosk apps from Google Play and disable auto-updates for the Fully Kiosk app.

When enabling Kiosk Mode in Fully Kiosk please read the dialog box text carefully and enable the Detect Home Button option in Fire OS Accessibility Settings. This is required to make the kiosk protection with Fire OS. Note: This accessibility option is sometimes reset by Fire OS - no idea why, you will get a warning toast when Starting Fully Kiosk in this case. If the Advanced Kiosk Protection is enabled, your device is probably still 98% protected in that case.

Due to changes in the accessibility service the Fire OS edition of Fully Kiosk Browser will always be an APK file to install. You can get it in the download box. It won't be accessible on Google Play as Google doesn't like apps tampering with accessibility service. Amazon store didn't like our apps for unknown reasons, so our app can't be made available there.

Major Issues with Fire OS reported by users:

1. Fire OS 5 (after update to 5.3.7.0 or 5.6.9.0), Fire OS 6 and Fire OS 7 takes some seconds (usually 5 seconds) to return to Fully Kiosk when the Home Button is pressed. If you plan to make an OS upgrade or obtain new Fire OS devices please check if this issue appears.

adb devices
adb shell pm set-home-activity de.ozerov.fully/.LauncherReplacement
adb shell pm disable-user --user 0 com.amazon.firelauncher

adb shell pm enable --user 0 com.amazon.firelauncher
adb shell pm set-home-activity com.amazon.firelauncher/.Launcher

2. After update to Fire OS 5.6.6.0 or 5.7.0.0 the Fully Kiosk app stops working if Visual Motion Detection is active and the screen goes off. It looks like this Fire OS is killing all apps that use the camera while screen is off. We have no fix for this. Use the Screensaver instead of Screen Off or use the Acoustic motion detection.

3.There is a bug in the newer Fire OS 7.3.1.5+ that the granted microphone access permission gets lost sometimes. You can deny this permission as workaround. The depending features in Fully Kiosk like Acoustic Motion Detection of course won't work.

4. The Kiosk Mode can have other serious issues with Fire OS. You've been warned.

5. The Lock Screen can't be disabled on many Fire OS devices. The Screen Off Timer, Sleep Schedule or the short Power Button press will always lead to the lock screen. All this is no issue with normal Android OS. Another ROM or rooted Fire OS can help you. Some users reported successful screen lock removal in Fire OS according to this manual (based on this approach). Other users reported that this approach reverts randomly unless you disable the access to any networks except required (e.g. by VLAN configuration). Other users reported successfull lock screen deactivation by using the screen pinning.

The Unlock Screen option is available for some Fire OS 6 and Fire OS 7 based devices. But it still doesn't work 100% as after device reboot sometimes you still have to swipe to unlock. Also the keyboard may not appear until you press the home button if the Unlock Screen is enabled.

6. The Android Webview can't be updated separately, but it seems to be updated with Fire OS and is slightly outdated with Fire OS we tested.

7. Some users reported to be impossible to use Alexa and the Show Mode when Kiosk Mode is activated.

8. Some users reported screen brightness issues where the brightness is not set/reset properly when using the brightness settings in Fully Kiosk. If you encounter this issue please check that Keep Screen On option is enabled in Fully Kiosk. Otherwise Android  screen off can mess up things. Avoid using Screensaver Brightness option if you still have brightness issues.

9. Add to Home feature isn't working with the standard Fire OS launcher.

10. It looks like there is no device provisioning method working with Fire OS and so there is no way to make a silent remote app installations (unless the device is rooted).

11. Some devices like Echo Show can't grant the requested app install permission and show the permission request repeatedly. You can deny this permission request permanently by downloading and importing this JSON settings file.

12. Some Echo Show devices display the limited touch functionality warning.

13. The Dark Mode doesn't work even if the device is on Android 9.

If you find some issues with the Fire OS please feel free to report to info@fully-kiosk.com and let's see what we can do.

Fire TV sticks seem to work with Fully Kiosk (with the restrictions above) however you can't get them into the kiosk mode and some different restrictions apply as for other Android TV devices. You can try to switch off the Disable Home Button option and run in the kiosk mode "light" where the home button is not locked. If your device is not touchscreen and you hide the remote this might be a sufficient protection. App icons for sideloaded apps are broken on some Fire TV devices.