• Start URL – die Home-URL, die mit http://, https:// oder file:// beginnt.
  • Sie können Variablen wie $mac, $deviceID, $locale, $hostname, $hostname6, $deviceName, $ip4, $ip6, $sn, $bssid oder $ssid in der URL verwenden.
  • Wenn Sie mehrere URLs angeben (eine URL pro Zeile), Fully Kiosk öffnet die URLs auf mehreren Registerkarten .

  • Die Anmeldeinformationen (für die grundlegende HTTP-Authentifizierung!) können in die Start-URL (z. B. http://user:pass@server:8084/fhem/ftui/ ) aufgenommen oder in den Webinhaltseinstellungen unter Benutzername und Passwort eingegeben werden . Fully Kiosk Browser beinhaltet keine Passwortverwaltung für die webformularbasierte Authentifizierung. Bitte richten Sie die Web-Automatisierung in Fully Kiosk wenn Sie irgendeine Art von automatischer Web-Anmeldung benötigen.

  • Local files can be used for all URLs like this: file: ///path/to/test.html (note triple slash!) Note that any links to local files or embedding local files in HTTP/HTTPS documents are disabled by Android Webview for security reasons. Use Localhost File Access option for workaround. Check this FAQ for details about local files paths and access rules.

• Username (optional) – user name for Basic HTTP Authentication (only applied to hosts included in Start URL when 401 auth request received)
• Password (optional) – password for Basic HTTP Authentication (only applied to hosts included in Start URL when 401 auth request received)
• Enable Fullscreen Videos – videos can be switched to full screen
• Autoplay Videos – autoplay embedded HTML5 videos (this works only with websites having a static <video> tag, not with Youtube for now)
• Autoplay Audio – autoplay embedded HTML5 audio (this works only with websites having a static <audio> tag for now)
• Enable File Upload ( PLUS ) – allow users to upload files to web forms
• Enable Camera Capture Upload ( PLUS ) – allow users to make camera photos and upload them to web forms
• Enable Video Capture Upload ( PLUS ) – allow users to record a video and upload it to web forms
• Enable Audio Record Upload ( PLUS ) – allow user to record and upload audio
• Enable JavaScript Alerts – allow JavaScript alert, prompt and confirm boxed
• Enable Popups ( PLUS ) – support popups (also those which open without user interaction) and open links in new frame
• Enable Webcam Access ( PLUS ) – allow accessing webcam by HTML5 (Android 5+). Only possible from secure origin websites (loaded by HTTPS).
• Enable Microphone Access ( PLUS ) – allow accessing microphone by HTML5 (Android 5+). Only possible from secure origin websites (loaded by HTTPS).
• Enable Geolocation Access ( PLUS ) – allow accessing geolocation by HTML5. Only possible from secure origin websites (loaded by HTTPS).
• View local PDF Files ( PLUS ) – open local PDF files using different methods:
  • Disabled – ignore PDF files
  • Use PDF.js – the best rendering directly in the webview incl. clickable URLs, works even in iFrames for most PDF files, may be slow with large files on slow devices, uses PDF.js hosted at Unpkg, other hosting or app integration on request. Unfortunately with PDF.js you can’t generate the print output on Android properly.
  • Use Built-in PDF viewer (Android 5+) – fullscreen view only
  • Launch Standard App for PDF – open PDF file in another app
• View remote PDF Files ( PLUS ) – open remote PDF files using different methods:
  • Disabled – ignore PDF files
  • Use PDF.js – the best rendering directly in the webview incl. clickable URLs, works even in iFrames for most PDF files, may be slow with large files on slow devices, uses PDF.js hosted at Unpkg, other hosting or app integration on request. Unfortunately with PDF.js you can’t generate the print output on Android properly.
  • Use Built-in PDF viewer (Android 5+) – fullscreen view only
  • Use Google Docs – this doesn’t work for Intranet files
  • Download PDF and Pass File to Standard App – download and open PDF file in the standard PDF app
  • Download PDF and Pass Content to Standard App – download PDF file and pass content URL to the standard PDF app. This option resolves issues with the previous options and some PDF apps. (ver. 1.38+)
  • Just download the file – the file is saved to the app-specific storage if scoped storage mode is active (ver. 1.39+)
• Play videos in Fully ( PLUS ) – play Android supported videos (incl. RTSP) in Fully built-in player
• View/Open Other Files – Wählen Sie eine Möglichkeit zum Öffnen anderer verknüpfter Dateien. Wie bei PDFs können Sie diese deaktivieren, eine URL an eine andere App weitergeben, eine Datei/einen Inhalt herunterladen und an eine externe App weitergeben oder die Datei einfach herunterladen (die Datei wird im app-spezifischen Speicher gespeichert, wenn der Scoped-Storage- Modus aktiv ist).
• Links to Open in Other Apps – Liste der http/https-URLs, die in anderen Apps geöffnet werden sollen, eine URL pro Zeile, Platzhalter * möglich. Alle http/https-URLs, die nicht in dieser Liste enthalten sind, werden in der Webview von Fully Kiosk . Geben Sie beispielsweise https://hangouts.google.com/call/* in diese Option ein, wenn Sie diese Links in der Hangout-App (Version 1.40+) öffnen möchten.
• Open Other URL Schemes – Erlaubt das Öffnen von URLs wie tel:, mailto  : oder intent: in anderen Apps
• URL Whitelist – Geben Sie eine vollständige URL (einschließlich https:// usw.) pro Zeile ein, verwenden Sie * als Platzhalter, alle sind zulässig, wenn leer ( Beispiele finden Sie in dieser FAQ ). Die URLs auf der Universal Launcher werden automatisch auf die Whitelist gesetzt
• URL Blacklist – Geben Sie eine vollständige URL pro Zeile ein (einschließlich http:// usw.), verwenden Sie * als Platzhalter, überschreibt die Whitelist
• Redirect Blocked to Start URL – Leiten Sie die durch die Whitelist oder Blacklist blockierte URL zur Start-URL um
• Web-Overlay ( PLUS ) – eine nicht interaktive Website in einer transparenten Überlagerung über dem Hauptinhalt anzeigen (Ver. 1.52+)
  • Web Overlay URL – Geben Sie die URL ein oder lassen Sie das Feld leer, wenn Sie kein Overlay wünschen. Hier sind einige Beispiele für einfache Overlay-Seiten: Uhrzeit , IP-Adresse .
  • Web Overlay Vertical Alignment – oben oder unten auswählen
• Custom Error URL – Seite, die im Fehlerfall geladen werden soll. Überprüfen Sie die Abfrageparameter error und URL für weitere Informationen zum Fehler. Unter Android 5+ werden nur DNS-/Verbindungsfehler abgefangen, unter Android 6+ auch HTTP-Fehler 40x/50x. Bei Verbindungsfehlern empfiehlt es sich, lokale Dateien für die Fehler-URL zu verwenden, wie in diesen FAQ beschrieben . Ab Version 1.45+ können Sie fully://errorpage als einfachen Fehlerseitenhandler verwenden.
• Load Error URL on Disconnection – Benutzerdefinierte Fehler-URL auch bei Internet-Unterbrechung nach einigen Sekunden laden, 0 für deaktiviert. Internet-Unterbrechung wird durch Pingen der IP-Adresse 8.8.8.8 erkannt. Sie können die IP-Adresse über eine versteckte Option in Fully Kiosk : Holen Sie sich diese JSON-Einstellungsdatei , bearbeiten Sie sie und importieren Sie sie in Fully Kiosk .

• Enable Pull to refresh – Ermöglicht das Neuladen der aktuellen Seite durch Ziehen nach unten. Formulardaten werden erneut übermittelt, wenn dies in den erweiterten Webeinstellungen aktiviert ist. Die Verwendung dieser Option kann zu Fehlfunktionen auf einigen Websites führen, auf denen Ziehen erforderlich ist.
• Enable Back Button – Gehen Sie eine Seite des Verlaufs zurück, indem Sie auf die Schaltfläche „Zurück“ in der Navigationsleiste tippen.
• Load Start URL on Home Button – Tippen Sie auf die Home-Schaltfläche, um die Start-URL zu laden (erfordert Kiosk-Modus)
• Enable Tap Sound – Klickgeräusch beim Eintippen abspielen Webview
• Zum Navigieren wischen ( PLUS ) – Wischen Sie nach links/rechts, um im Verlauf vorwärts/rückwärts zu gehen
• Seitenübergänge animieren ( PLUS ) – Erzeugen Sie das App-Gefühl, indem Sie beim Navigieren Frames ein- und ausblenden und Frames während des Ladens ausblenden. Erfordert ein schnelles Gerät und eine schnell ladende Website.
• Wischen Sie, um die Registerkarten zu ändern ( PLUS ) – Wischen Sie nach links und rechts, um in geöffneten Browser-Tabs zu wechseln
• Wait for Network Connection – Versuchen Sie niemals, eine Webseite zu laden, wenn keine Verbindung verfügbar ist
• Search Provider URL – Verwenden Sie diese URL als Suchanbieter. Dazu ist die Adressleiste aktiviert. In die Adressleiste eingegebene Schlüsselwörter werden mit dieser URL verknüpft. Standard-Google-Such-URL:  https://www.google.com/search?q=
• NFC-Tags lesen ( PLUS ) – Öffnen Sie URLs von NDEF-formatierten NFC-Tags. Das Lesen von NFC muss in den Android-Einstellungen aktiviert sein und Fully Kiosk App muss im Vordergrund sein. Beachten Sie, dass Android-Geräte keine NFC-Tags lesen, während der Bildschirm gesperrt ist (auch wenn Fully Kiosk wird über der Bildschirmsperre angezeigt (mit der Option „Bildschirm entsperren“) oder wenn die Kamera verwendet wird.

• Enable Zoom – Zoomen zulassen (wenn die Website dies unterstützt)
• Load in Overview Mode – Website auf Gerätebreite herunterskaliert laden (nützlich für ältere Websites)
• Use Wide Viewport – achten Sie auf den Viewport-Meta-Tag der Webseite
• Initial Scale – Anfangsskalierung in % festlegen, nützlich für ältere Websites. Nur aktiv, wenn „Breitenbereich verwenden“ deaktiviert ist, andernfalls wird der Meta-Tag des Ansichtsbereichs überschrieben. Diese Option funktioniert möglicherweise bei einigen Websites, während sie bei anderen ignoriert wird oder seltsame/vorübergehende Effekte hat. Die korrekte Skalierung und das Layout der Website erfolgen über HTML in der Website, nicht über diese Option.
• Set Font Size – Schriftskalierung in % einstellen (Standard: 100%)
• View in Desktop Mode – Versuchen Sie, Websites in der Desktop-Ansicht statt in der mobilen Ansicht darzustellen

• Auto Reload on Idle – automatisches Neuladen (Start-URL oder aktuelle Seite) nach x Sekunden Inaktivität des Benutzers
• Auto Reload after Page Error – automatisches Neuladen nach x Sekunden bei einem Seitenladefehler; unter Android 5+ werden nur DNS-/Verbindungsfehler abgefangen, unter Android 6+ auch HTTP-Fehler 40x/50x.
• Auto Reload on Screen On – automatisches Neuladen beim Einschalten des Bildschirms
• Auto Reload on Screensaver Stop – automatisches Neuladen, wenn der Bildschirmschoner stoppt
• Auto Reload on Network Reconnect – automatisches Neuladen bei erneuter Verbindung von WLAN/LAN/LTE
• Auto Reload on Internet Reconnect (experimental) – Start-URL neu laden, sobald eine echte Internetverbindung wiederhergestellt ist. Die Verbindungsprüfung erfolgt durch einen Ping-Anruf an den Google DNS-Server unter 8.8.8.8 alle 10 Sekunden. Sie können die zu pingende IP-Adresse über eine versteckte Option in ändern. Fully Kiosk : Holen Sie sich diese JSON-Einstellungsdatei , bearbeiten Sie sie und importieren Sie sie in Fully Kiosk .
• Delete Cache on Auto Reload – Cache vor dem Neuladen leeren
• Delele Webstorage on Auto Reload – Webspeicher vor dem Neuladen leeren
• Delete History on Auto Reload – Verlauf und Formulardaten vor dem Neuladen löschen
• Delete Cookies on Auto Reload – Cookies vor dem erneuten Laden löschen
• Load Current Page on Auto Reload – Beim automatischen Neuladen wird immer die aktuelle Seite anstelle der Start-URL neu geladen. Wenn viele Tabs geöffnet sind, werden alle Tabs aktualisiert. Die benutzerdefinierte Fehler-URL wird auf die letzte „gute“ URL zurückgesetzt.
• Skip Auto Reload if Showing the Start URL – Kein automatisches Neuladen, wenn die Start-URL noch angezeigt wird. Diese Option funktioniert nicht, wenn Sie mehrere Start-URLs festgelegt haben.

• Basic Web Automation – Füllen Sie automatisch Text in Webformularen aus, aktivieren Sie Kontrollkästchen und klicken Sie auf Links und Schaltflächen. Konfigurieren Sie eine flexible Liste von Aktionen, die auf jeder geladenen Seite ausgeführt werden sollen. Sie können die Zielseite nach URL filtern (mit * als Platzhalter) und das Zielfeld, die Schaltfläche oder den Link nach Index oder verschiedenen IDs auswählen ( PLUS , Ver. 1.41+). Mit dieser Funktion können Sie Ihr Web-/Anmeldeformular so einrichten, dass es automatisch ausgefüllt und abgeschickt wird. Sie können auch die Automatisierung so einrichten, dass alle Cookies, Webstorage, Cache und der Verlauf vor dem Laden einer URL gelöscht werden. Dies sollte ausreichen, um die Website-Anmeldungen zu löschen.
• Aktivieren Sie die JavaScript-Schnittstelle ( PLUS ) – Erlauben Sie die Nutzung der Website Fully ’s JavaScript Interface to access app and device information and features. Enable this option only if you trust all websites loaded. This option is potentially insecure as any website can read ALL your local files etc. – see docs below
  • Detect iBeacons ( PLUS ) – scan for iBeacons and trigger event on JavaScript interface when detected. Note the beacons are only detected reliably when our Fully Kiosk app is in foreground and the screen is on.
  • Enable QR Code Scanner ( PLUS ) – enable the integrated barcode scanner from JavaScript interface (ver. 1.30+)
• Inject JavaScript ( PLUS ) – run this JavaScript code after loading each page. Using this option you can modify websites which code you can’t change. You will need a web developer to develop a JavaScript according to your requirements.
• Enable Text Input – Enable text input in editable web form fields
• Always Hide Keyboard – Make the soft keyboard always invisible. Experimental option, the behavior can be different depending on the device and keyboard app. May need an app restart each time after using the keyboard (e.g. in Settings) to have effect.
• Enable Form Autocomplete – save and prefill form data. This option is not available with Android 8+, please use the Autofill option below.
• Enable Form Autofill – allow Android Autofill Manager to auto-fill the forms in the Webview , please check the Autofill options in Android system settings (look for Language and Input) (ver. 1.54+)
• Enable User Interaction – Allow any user interactions in the Webview
• Enable Long Tap – Enable long tap actions like text selection and context menus (ver. 1.52+)
• Enable Dragging – Allow dragging objects by touch in the Webview , disabling will also disable scrolling in the webview (ver. 1.40+)
• Enable Scrolling – Allow page scrolling in the Webview (1.40+)
• Enable Overscroll – Enable overscroll animation (1.50+)
• Enable Third Party Cookies – allow accepting those cookies (Android 5+, always allowed for Android 4)
• Recreate Tabs on Reload – close web tabs and open new tabs on each Start URL load (ver. 1.27+)
• Web Popup Options – Specs for all popup windows (like width=500,height=500,top=200,background=#C00000FF) to show popups in the box, show popups fullscreen otherwise ( PLUS , 1.55.1+)
• 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. Enable this option only if you trust all websites loaded. This option is potentially insecure as any website can read ALL your local files. (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+)
• Add DNT Header – apply Do Not Track header to HTTP GET requests. This option is ignored by the most servers (ver. 1.55.3+)
• Remove X-Frame, CSP and CORS protection ( PLUS ) – Specify a list of URLs to remove the X-Frame-Options, Content-Security-Policy options and add Access-Control-Allow-Origin on the sever response, one URL per line, can use * wildcard. With this option you can try to void these protection mechanisms. Use with care and note that this option can affect web caching and HTTP POST requests are not processed (ver. 1.53+).
• Enable Web Filter ( PLUS ) – load a host list from fully-blackhosts.txt  and block them. You have to put this file in the root folder of the app-specific or shared storage (if accessible). 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 – can be used with self-signed certificates, this makes TLS/SSL absolutely unsafe of course
• Pause Webview while in Background (experimental, ver. 1.39.3+) – pause Webview when Fully Kiosk in background or screen is off
• Enable DRM protected content (experimental, ver. 1.41+) – enable protected content in the Webview
• Mixed Content Mode (ver. 1.43+) – allow secure origin documents to load a resource from an insecure origin. If you change this option, you should know what you do. Note that Webview 111+  blocks some mixed content regardless to this option due to  a known Chromium bug.
• Client Certificate File ( PLUS ) – Client certificate URL (or file URL) for client CA authentication, P12 or PFX files allowed. Note that AES256-SHA256 encryption is not supported by Android on some devices,  certificate in TrippleDES-SHA1 seems to work ok. Watch Logcat for CA issues.
• Client Certificate Password – Client certificate private key password
• Restart on Unresponsiveness – restart app after some seconds of Webview unresponsiveness, keep 0 for disabled ( PLUS , EXPERIMENTAL, ver. 1.52+)
• Cache Mode – select Caching Mode for the Webview
• Clear Cache After Each Page – purge cache after each page loaded
• Resume Playback when Getting to Foreground – try to resume embedded video and audio when Fully Kiosk is getting to foreground
• Keep Screen On while in Fullscreen Mode – disable screensaver and screen off timer while the Webview is in fullscreen mode
• Enable Webview Contents Debugging – enable remote debugging using Chrome Developer Tools
• Fake User Agent String – use the agent string of another web browser
• Custom User Agent String ( PLUS ) – set an arbitrary UA string (ver. 1.29+)
• Default Webview Background Color – select background color for the Webview , defaults to white. This option only takes effect if the website doesn’t specify any background color.
• Graphics Acceleration Mode – you can choose among hardware, software or no acceleration, try it if you have rendering issues in Webview ; videos will play only with Hardware mode
• Select Webview Implementation – On Android 7+ opens the developer options where you can select the Webview provider ( Webview , Chrome or Chrome beta, if installed)

• Select Items to Show – select apps from the list of installed apps or add URLs for web bookmarks to show on the launcher (more info)
• Show Launcher on Start – always show the launcher page (fully:// launcher ) instead of the Start URL
• Launcher Background Color – select background color for the launcher page
• Launcher Text Color – select app/bookmark label color for the launcher page (ver. 1.31+)
• Launcher Background Image URL – load launcher background image from this URL or file (ver. 1.38+)
• Launcher Page Scaling – set page scaling for launcher page in %, default: 100%
• Inject HTML Code in Launcher – design your custom launcher layout by injecting CSS/JS code in <head> of the launcher Seite wie diese
• Application to Run on Start in Foreground – Wählen Sie die App aus, die im Vordergrund ausgeführt werden soll Fully Start ( PLUS , experimentell, Version 1.45+). Wenn Sie nur eine App verwenden, verwenden Sie besser den Einzel-App-Modus in den Kioskmodus-Einstellungen.
• Applications to Run on Start in Background – Wählen Sie Apps aus, die im Hintergrund ausgeführt werden sollen Fully Kiosk Start, ein Paketname pro Zeile ( PLUS , experimentell, Version 1.43.4+). Technisch gesehen werden die angegebenen Apps beim Gerätestart von ihren launcher Absichten und dann Fully Kiosk sich selbst wieder in den Vordergrund drängen.

Diese Optionen haben nur dann eine Wirkung, wenn Fully Kiosk ist im Vordergrund. Da andere Apps unter Android normalerweise im Vollbildmodus laufen, ist es nicht möglich, dies zu ändern. Für Vollbildoptionen klicken Sie hier .

• Show Navigation Bar – Systemnavigationsleiste (untere Leiste) dauerhaft anzeigen, für den Vollbildmodus deaktiviert lassen, diese Einstellung hat keine Auswirkung auf Geräte mit Hardware-Home-/Zurück-Tasten
• Navigation Bar Color – Wählen Sie die Hintergrundfarbe für die Navigationsleiste. Alpha-Transparenz ist zulässig. Sie können den Hex-ARGB-Farbcode angeben. Auf neueren Android-Geräten hat diese Option nur dann Auswirkungen, wenn die Navigationsleiste dauerhaft angezeigt wird. Keine Auswirkungen auf Android 15+
• Show Status Bar – Systemstatusleiste (obere Leiste) dauerhaft anzeigen, für den Vollbildmodus deaktiviert lassen
• Status Bar Color – Wählen Sie die Hintergrundfarbe für die Statusleiste. Auf neueren Android-Geräten hat dies nur dann Auswirkungen, wenn die Statusleiste dauerhaft angezeigt wird. Keine Auswirkungen auf Android 15+
• Show Action Bar – Aktionsleiste mit Schaltflächen anzeigen
• Action Bar Title – Geben Sie den Text ein, der in der Aktionsleiste angezeigt werden soll. Sie können Variablen wie $mac, $deviceID, $locale, $hostname, $hostname6, $deviceName, $ip4, $ip6, $sn, $bssid oder $ssid verwenden.
• Action Bar Background color – Hintergrundfarbe für die Aktionsleiste auswählen
• Action Bar Text Color – Text-/Symbolfarbe für die Aktionsleiste auswählen
• Custom Icon URL – Laden Sie das Aktionsleistensymbol (links im Text) von dieser URL. Sie können lokale Dateien verwenden
• Custom Background Image URL – Laden Sie das Hintergrundbild der Aktionsleiste von dieser URL
• Show Back Button – Zurück-Schaltfläche in der Aktionsleiste anzeigen
• Show Forward Button – Vorwärts-Schaltfläche in der Aktionsleiste anzeigen
• Show Refresh Button – Schaltfläche „Aktualisieren“ in der Aktionsleiste anzeigen
• Show Home Button – Home-Button in der Aktionsleiste anzeigen
• Show Print Button – Drucktaste in der Aktionsleiste anzeigen
• Show Share Button – show share button on action bar – Version 1.28+
• Show Barcode Scan Button – QR-Scan-Schaltfläche anzeigen, in „Andere Einstellungen“ nach der Konfiguration des Barcode-Scanners suchen, diese FAQ lesen (Ver. 1.40+)
• Custom Button Action – URL zum Laden beim Drücken einer benutzerdefinierten Schaltfläche. Sie können vollständig:// verwenden. launcher für Universal Launcher , leer lassen, wenn keine benutzerdefinierte Schaltfläche gewünscht wird
• Größe der Aktionsleiste ( PLUS , experimental) – Skalierung der Aktionsleiste in Prozent einstellen (Standard 100 %, Version 1.43.5+)
• Show Action Bar in Settings – auch die Aktionsleiste in den Einstellungen anzeigen
• Show Tabs – Tab-Flaps für Browser-Frames anzeigen, Sie können mehrere Seiten laden, indem Sie mehrere Start-URLs definieren (eine URL pro Zeile)
• Show Close Buttons on Tabs – Benutzern das Schließen von Web-Tabs ermöglichen
• Show New Tab Button – Benutzern das Öffnen eines neuen Web-Tabs ermöglichen, die Adressleiste wird zur Eingabe der URL benötigt
• New Tab URL – Öffnen Sie diese URL auf den neuen Registerkarten, die von Benutzern geöffnet werden (Ver. 1.54+).
• Active Tab Color – Hintergrundfarbe für aktive Registerkarte definieren
• Inactive Tab Color – Hintergrundfarbe für inaktive Tabs definieren
• Tab Text Color – Farbe für Tab-Text und Schaltflächen definieren
• Show Address Bar – Adressleiste mit aktueller URL anzeigen, Fully wird die Adressleiste beim Scrollen automatisch ausblenden
• Address Bar Color – Hintergrundfarbe für die Adressleiste auswählen
• Show Progress Bar – Fortschrittsbalken beim Laden oben anzeigen
• Progress Bar Color – Farbe für den Fortschrittsbalken auswählen

• Screensaver Timer – Nach wie vielen Sekunden wird der Bildschirmschoner gestartet. Der Bildschirmschoner stoppt bei jeder Benutzerinteraktion oder wenn Bewegung erkannt wird. Bitte beachten Sie, dass vor Version 1.39 die Fully Kiosk Der Bildschirmschoner konnte nicht gestartet werden, während eine andere App im Vordergrund war. Aus diesem Grund waren die Bildschirmschoner-Einstellungen im Fully Single App Kiosk App vor Version 1.6. In diesen FAQ finden Sie eine mögliche Problemumgehung mit dem Android-Bildschirmschoner (Daydream) für ältere Versionen.
• Screensaver Playlist – Wählen Sie Mediendateien, Ordner, YouTube-Videos/Wiedergabelisten oder einfach nur Webseiten für den Bildschirmschoner aus. Sie können diese Liste leer lassen, wenn Sie den Bildschirm nur dimmen möchten.
• Screensaver Wallpaper URL – Diese Website als Bildschirmschoner-Hintergrund anzeigen. Für einen transparenten Hintergrund leer lassen. Für eine einfarbige Seite können Sie eine URL wie fully://color#000000 verwenden.
• Screensaver Brightness – Bildschirmhelligkeit für Bildschirmschoner einstellen (0-255), Bildschirm dimmen, wenn der Bildschirmschoner abgespielt wird, leer für Standard
• Fade In/Out Duration – Dauer der Bildüberblendung in Millisekunden einstellen, Standard 200 ms
• Ignore Motion Detection when Screensaver goes on/off – Ignorieren Sie Änderungen des Umgebungslichts und erkennen Sie keine Bewegungen, während der Bildschirmschoner startet oder stoppt. Wenn die Bewegungserkennung beim Ausschalten des Bildschirms ausgelöst wird, aktivieren Sie diese Option und stellen Sie den Bildschirmschoner-Timer etwas kürzer ein als den Bildschirm-Aus-Timer.
• Cache Images – Aktivieren Sie das Zwischenspeichern von Netzwerkbildern in der Wiedergabeliste
• Use Android Screen Saver – Starten Sie den Android-Bildschirmschoner (vor Android 7 Daydream genannt) anstelle von Fully Bildschirmschoner von . Der Start des Android-Bildschirmschoners funktioniert nicht zuverlässig, wenn das Gerät gesperrt ist und die Option „Bildschirm entsperren“ verwendet wird oder andere Apps im Vordergrund laufen. Diese Option ist in Android 13+ nicht verfügbar.
• Android Screen Saver Settings – Öffnen Sie die Einstellungen des Android-Bildschirmschoners (Daydream)
• Use Another App – Starten Sie eine App mit dem Bildschirmschoner-Timer statt Fully 's Playlist. Diese App muss die Möglichkeit bieten, den Bildschirmschoner durch Antippen zu beenden, wenn Sie ihn durch Antippen beenden möchten.
• Select Screensaver App – Wählen Sie eine App aus oder geben Sie eine auszuführende Intent-URL an. Diese App muss sich automatisch schließen, wenn eine Berührung oder eine andere Exit-Intent erkannt wird.

• Keep Screen On – Der Bildschirm bleibt immer eingeschaltet. Das Gerät wird durch die Android-Anzeigeeinstellungen am Ruhezustand gehindert. Das Ausschalten des Bildschirms und der Ruhezustand bleiben jedoch möglich durch Fully Kiosk Optionen wie Bildschirm-Aus-Timer und Geplantes Aufwachen/Ruhezustand . Im Kiosk-Modus kann das Verhalten des Power-Buttons in den Kiosk-Modus-Einstellungen festgelegt werden. Wenn Sie die Option Bildschirm eingeschaltet lassen deaktivieren, aktivieren Sie bitte die Option Ruhezustand bei ausgeschaltetem Bildschirm verhindern in Fully Energieeinstellungen, da Ihr Gerät sonst in den Ruhezustand fallen kann. Dies kann die Funktionen beeinträchtigen, wenn Sie Bewegungserkennung oder Remote-Admin verwenden.
• Keep Screen On (Advanced) – verwenden Sie dies, wenn die vorherige Option nicht hilft, Bildschirmausfälle bei der Verwendung anderer Apps zu vermeiden (Android 10+, Ver. 1.44+)
• Screen Brightness – Bildschirmhelligkeit auf 0…255 einstellen, für Systemstandard leer lassen
• Force Screen Orientation – Bildschirmausrichtung einstellen (nur für Fully Kiosk , erzwingt keine anderen Apps). Auf vielen Android TV-Geräten hat diese Option leider keine Wirkung.
• Force Screen Orientation Globally – Versuch, die gewählte Bildschirmausrichtung für das Android-Betriebssystem und alle Apps zu erzwingen (experimentell). Auf vielen Android-TV-Geräten hat diese Option leider keine Wirkung.
• Unlock Screen - zeigen Fully Kiosk “above” the lock screen. This works only for Fully Kiosk app, the user interaction may lead to a lock screen when other apps are started – as they are still “behind” the lock screen (file or camera capture uploads, open in other apps, open Wifi or other Android settings, permission dialogs etc.). Note that some features like NFC scan or hardware barcode scan can be unavailable is this option is enabled until you manually unlock the device. Check this FAQ and also look for Fire OS limitations
• Unlock Swipe Screen Lock (experimental) – try to unlock swipe screen lock automatically (Android 8+). This option can help to prevent the bug in some devices when the keyboard is not showing up. This unlock can take 3-4 seconds on some devices for unknown reasons unfortunately.
• Screen Off Timer ( PLUS ) – Seconds of user inactivity for the screen to be switched off. Screen goes on again on power button press, on wake up timer, when motion/movement detected (if enabled, look in Motion/Movement Detection) or when an API screenOn command is issued. Note that some devices will suspend the device completely or even kill the Fully Kiosk app when the screen is off and Motion/Movement Detection or Remote Admin can’t run. Look for Fire OS limitations. Please check related settings in Advanced Web Settings and in Other Settings to set the behavior of this option when fullscreen content is played or other apps are in foreground. Check this FAQ if you want the screen to wake up on tap.
• Turn Screen Off on Proximity ( PLUS ) – turn screen off while proximity sensor detects objets nearby (ver. 1.43+)
• Launch on Boot – run Fully Kiosk at device startup. You don’t have to turn on this option if you enable the Kiosk Mode with Home Button disabled, Fully Kiosk will run on start anyway.
• Redirect Audio to Phone Earpiece ( PLUS ) – redirect audio output to phone earpiece. This can have side effects for changing volume when redirected. In Android 12+ this option only has stable effect for audio output of Fully Kiosk app, not from other apps (ver. 1.43+)
• Set Volume Levels ( PLUS ) – set initial volume levels when the kiosk app starts, comma separated stream:percent list, empty for no change. Stream codes: 0 – Voice Call, 1 – System, 2 –   Ring, 3 – Music, 4 – Alarm, 5 – Notification, 6 – Bluetooth, 8 – DTMF, 9  – TTS, 10 – Accessibility. For example, the string value 2:80,3:50 will set the ring stream volume at 80% and the music stream volume at 50%.
• Force Immersive Fullscreen (experimental) – try making the system bars immersive for other apps – ATTENTION: This is not required for Fully to make the fullscreen for web browser and launcher , use settings in Toolbars and Appearance section. When this mode is activated all key input including keyboard and back key is out of order. We can’t change this unfortunately, this mode is a big hack.
• Remove Navigation Bar (experimental) – completely remove navigation bar for all apps (!), this works on Android 10 and older only and requires special permissions, read FAQ
• Remove Status Bar (experimental) – completely remove  status bar for all apps (!), this works on Android 10 and older only and requires special permissions, read FAQ
• Set Device Name – Gerätenamen (Bluetooth-Name) festlegen. Platzhalter wie in der Start-URL können verwendet werden, leer für „Behalten“ (experimentell). Diese Option funktioniert nicht mit allen Geräten. Samsung-Geräte erhalten beispielsweise den Gerätenamen von einer Quelle, die wir nicht ändern können (Version 1.46+).
• Bluetooth Mode – Erzwingen Sie die Aktivierung oder Deaktivierung von Bluetooth beim App-Start (Ver. 1.33+)
• Wifi Mode – Erzwingen Sie die Aktivierung oder Deaktivierung von WLAN beim App-Start (Version 1.33+). Mit Android 10+ ist diese Funktion nur auf bereitgestellten Geräten verfügbar .
• Hotspot Mode – Erzwingen Sie die Aktivierung oder Deaktivierung des Hotspots beim App-Start (experimentell, Version 1.54+)
• Reset Wifi on Internet Disconnection – Schalten Sie das WLAN aus und wieder ein (mit 5 Sekunden Verzögerung), wenn die Internetverbindung verloren geht ( PLUS ). Die Internetverbindung wird durch Pingen der IP-Adresse 8.8.8.8 überprüft. Sie können die IP-Adresse in Ping ändern, indem Sie eine versteckte Option in Fully Kiosk : Holen Sie sich diese JSON-Einstellungsdatei , bearbeiten Sie sie und importieren Sie sie in Fully Kiosk . Mit Android 10+ ist diese Funktion nur auf  bereitgestellten Geräten verfügbar .
• Erzwungene WLAN-SSID ( PLUS ) – Gerät für ein WLAN-Netzwerk vorkonfigurieren, wenn die angegebene SSID verfügbar ist Fully erzwingt die Verbindung zu diesem WLAN. Die WLAN-SSID kann nicht manuell in den Android-WLAN-Einstellungen hinzugefügt werden. Fully füge es hinzu, sonst Fully kann keine Verbindung herstellen. Mit Android 10+ funktioniert diese Funktion nur auf bereitgestellten Geräten geräuschlos und zuverlässig .
• Erzwungene WLAN-Schlüsselphrase ( PLUS ) – WPA-Schlüsselphrase für die obige SSID
• Erzwungene WLAN-Einstellungen ( PLUS )
  • Wifi Type – WPA PSK (Standard), WPA EAP, Offen (kein Passwort)
  • Enterprise WLAN-Identität (nur für WPA EAP)
  • Enterprise WLAN-Passwort (nur für WPA EAP)
• WiFi Settings – Öffnen Sie die WLAN-Einstellungen von Android direkt
• Inhalt aus ZIP-Datei laden ( PLUS ) – Laden Sie die ZIP-Datei von dieser URL und entpacken Sie sie automatisch in den gemeinsamen Speicher /storage/emulated/0 oder den anwendungsspezifischen Speicher. Prüfen Sie stündlich auf Updates (gemäß dem Last-Modified-Server-Antwortheader). Der anwendungsspezifische Speicher wird verwendet, wenn sich Ihr Gerät im Scoped-Storage-Modus befindet . Seien Sie vorsichtig, da vorhandene Dateien ohne Benachrichtigung überschrieben werden. Dateien mit der Größe Null werden beim Entpacken vom Gerät entfernt. Vermeiden Sie nicht-lateinische Buchstaben in den gepackten Datei-/Ordnernamen oder stellen Sie sicher, dass der Packer die UTF-8-Kodierung verwendet. Weitere Informationen finden Sie in diesen FAQ !

• Aufwachen und Schlafen planen ( PLUS ) – Legen Sie Einschlaf- und Weckzeiten für jeden Wochentag, die ganze Woche oder nur für das Wochenende fest. Bitte verwenden Sie für die Einstellungen das 24-Stunden-Format HH:MM. Beachten Sie, dass nicht alle Geräte planmäßig geweckt werden können. Zur geplanten Einschlafzeit sind die Bewegungserkennung und die Bewegungserkennung deaktiviert. Durch Drücken der Einschalttaste oder einen Neustart des Geräts werden sie jedoch wieder aktiviert. Beachten Sie, dass andere Apps oder Systemereignisse wie Ein-/Ausschalten oder bestimmte Benachrichtigungen das Gerät aus dem Ruhezustand wecken können. Pausierte Dienste werden selbstverständlich zur Weckzeit reaktiviert. Beachten Sie, dass manche Geräte nicht geweckt werden können oder die Weckzeit ungenau ist.
• Keep Sleeping if Not Plugged – nicht planmäßig aufwachen, wenn das Gerät nicht angeschlossen ist
• Turn Screen On on Power Connect (experimental, ver. 1.42+) – Wecken Sie ein Gerät im Ruhezustand auf, wenn das Netzkabel eingesteckt wird. Die meisten Geräte werden auch ohne diese Option geweckt.
• Sleep on Power Connect – Gerät in den Ruhezustand versetzen, wenn das Netzkabel eingesteckt ist, kann zum nächtlichen Aufladen verwendet werden
• Sleep on Power Disconnect – Gerät in den Ruhezustand versetzen, wenn das Netzkabel abgezogen wird, kann für den nächtlichen Schlaf verwendet werden
• Force Screen Off If Not Powered – Bildschirm nicht einschalten, wenn das Gerät nicht angeschlossen ist. Vorsicht! Wenn Sie diese Option aktivieren, ist Ihr Gerät erst betriebsbereit, wenn Sie das Netzkabel einstecken!
• Batteriewarnung anzeigen ( PLUS ) – Warnung auf dem Display anzeigen, wenn die Batterie unter diesem Wert liegt, 0 zum Deaktivieren einstellen
• Prevent from Sleep while Screen Off – Versuchen Sie, das Gerät auch bei ausgeschaltetem Bildschirm aktiv zu halten (Android 6+). Andernfalls fallen viele Geräte in den Ruhezustand, sobald der Bildschirm ausgeschaltet wird. Diese Option funktioniert bei einigen Geräteherstellern und Android-Versionen nicht 100%ig. Beachten Sie, dass einige Hersteller wie Huawei unsere Kiosk-App nach einer gewissen Zeit ohne Bildschirm deaktivieren können. Lesen Sie hier für mögliche Lösungen. Beachten Sie, dass trotz aktivierter Option die Android Webview pausiert das Skripting, wenn der Bildschirm ausgeschaltet ist. Daher können Sie Ihre Website wahrscheinlich nicht „am Leben“ erhalten, wenn der Bildschirm ausgeschaltet ist. Verwenden Sie den Bildschirmschoner in Fully Kiosk Stattdessen können Sie als Workaround den Bildschirm ausschalten.
• Set CPU Wakelock – CPU zwingen, immer mitzuhalten (normalerweise nicht erforderlich, hat bei neueren Geräten keine Auswirkungen)
• Set Wifi Wakelock – WLAN zwingen, immer mitzuhalten (normalerweise nicht nötig, hat bei neueren Geräten keine Wirkung)

• Enable Kiosk Mode – Sperrgerät mit Ausstiegsgeste und PIN. Wenn aktiviert Fully Kiosk wird auch immer beim Gerätestart gestartet. Android 12+ hat einige Einschränkungen, die einen zuverlässigen Kiosk-Modus-Schutz ohne device provisioning oder auf andere Weise. Lesen Sie diese FAQ. – Erfahren Sie mehr über den Kiosk-Modus
• Kiosk Exit Gesture – Wählen Sie eine Geste aus, um den PIN-Dialog anzuzeigen. Diese Option ist nicht verfügbar, wenn der Einzel-App-Kioskmodus aktiv ist.
  • Von links wischen (auch langes Drücken der Zurück-Taste, Standard, funktioniert nur, wenn Fully Kiosk App ist im Vordergrund). Wenn Sie die Gestennavigation aktiviert haben (in Android 10+), müssen Sie kurz am linken Rand gedrückt halten, bevor Sie das Menü herauswischen.
  • Schnelle 5 Taps überall (einfach zu verwenden, funktioniert nur, wenn Fully Kiosk App ist im Vordergrund)
  • Fast 7 Taps anywhere in any app (also works if another app is in foreground) – Lesen Sie diese FAQ für den Fall, dass 7 schnelle Taps versehentlich ausgelöst werden können
  • Doppeltippen Sie auf die obere linke Ecke und doppelt auf die untere rechte Ecke (alles muss innerhalb von 3 Sekunden erfolgen, schwer zu erraten, funktioniert nur, wenn Fully Kiosk App ist im Vordergrund)
• Kiosk Mode PIN – Passwort zum Verlassen des Android Kiosk-Modus, PIN-Dialog wird übersprungen, wenn Sie es leer lassen
• Wifi/Settings PIN – eine weitere PIN, um nur auf das Android-WLAN zuzugreifen, auf andere Einstellungen zuzugreifen oder andere Apps zu starten. Achtung: Auf manchen Geräten wie Samsung-Tablets ermöglicht der Zugriff auf WLAN oder andere Einstellungen den Zugriff auf alle Android-Einstellungen, wodurch der Kiosk-Modus deaktiviert werden kann. Versuchen Sie es mit diesem Workaround oder verwenden Sie stattdessen die Option „WLAN-Netzwerk auswählen“.
• Wifi/Settings PIN action – Wählen Sie die Aktion beim Eingeben der WLAN-/Einstellungs-PIN wie folgt aus (Ver. 1.33+):
  • Öffnen Sie die Android-WLAN-Einstellungen (Standard).
  • Öffnen Sie die Android-Bluetooth-Einstellungen
  • Öffnen Sie die Android-Mobilfunknetzwerkeinstellungen
  • Open Android Connection Settings
  • Open Android OTA Update Settings
  • Select Wifi Network (experimental, with Android 10+ only working on provisioned devices)
  • Custom Action Intent
• Wifi/Settings PIN Custom Intent – Specify the Intent URL for the custom action (ver. 1.33+)
• Disable Status Bar – lock status bar and system settings access – your kiosk won’t be safe if you disable this setting. On some devices if you switch off this option you still can’t expand the status bar if Disable Power Button is enabled. In Android 8+ you can pull down the status bar however it shouldn’t be usable. In Android 12+ the status bar and notification area can be used even with this option. Read this FAQ for solutions.
• Disable Volume Buttons – restrict volume buttons in Kiosk Mode, also try to block any sound volume changes  (look for Device Owner Settings for solution with provisioned devices)
• Limit the Volume Level – if volume buttons not disabled limit the volume on all channels to this maximum in percent, empty for disable (ver. 1.42+)
• Disable Power Button – make the power button almost useless in Kiosk Mode. Short button press will switch off the screen for a second however before Fully Kiosk turn it back on. Longer press can show the power off buttons for a very short moment. In Android 9+ with Samsung devices this option can’t block the power dialog (Power Off / Restart /Emergency) reliably.  With Android 12+ this is valid for all devices. Read this FAQ for solutions. Very long press will usually power off the device, this is a hardware feature that no app can block (except by using the KNOX Settings). Note: This option will also prevent the device from switching off the screen by display timer set in Android settings, by sensors or by other apps. If you want the screen to switch off after some time of inactivity please enable the Keep Screen On and use the Screen Off Timer option in Fully Kiosk Device Management settings instead.
• Disable Home Button – lock the home button, if enabled Fully Kiosk will ask to set itself as your Home App and also start automatically on device start up
• Disable Context Menus – disable system context menus like Copy/Share/Select all for Fully Kiosk app (not for other apps, ver. 1.52+)
• Disable Other Apps – block all other apps except apps intentionally started by/from Fully Kiosk , also makes Recent Task Button unusable
• Advanced Kiosk Protection – enable advanced protection against starting other apps. Recent tasks and power button will be useless even when other apps are in foreground. Advanced protection is always enabled automatically when using the Universal Launcher and the Single App Mode. This protection will show toast message when blocking other apps. You can add the good apps to the App Whitelist if Fully Kiosk is killing to much.
• Disable Multiple Apps – disable opening other apps in popup-view. Users will be required to press home button or make home gesture when multiple open apps detected (experimental, ver. 1.59+)
• App Whitelist – allow selected apps or activities to go to foreground, one package name (for apps) or component name (for activities) per line, may use * as wildcard. E.g. set com.skype*  to allow using Skype (including all activities of that app). All apps started directly by Fully Kiosk are automatically whitelisted and don’t need to be put on this list. Starting ver. 1.38  single activities can be whitelisted by providing a component name like com.android.settings/.Settings You can find out the activity name (component name) by watching the foreground activity info in Remote Admin.
• App Blacklist – always block selected apps or activities, one package name (for apps) or component name (for activities) per line, may use * wildcard (ver. 1.38+). App blacklist has a higher priority than app whitelist. Please look on Remote Admin in the Device Info for the Current Foreground Activity in order to find the component name to blacklist.
• Single App Mode – auto-run one selected app with full kiosk protection. So you can lockdown the device to one single app. Please start your app on the device prior to setting it as your single mode app in Fully for getting the required runtime permissions (or use device provisioning for setting the most permissions automatically). Tap 7 times very fast anywhere on the screen to see the PIN dialog. The Kiosk Exit Gesture option has no effect. If 7 fast taps can occur frequently by the normal usage of your app please check this FAQ for alternative solutions.
  • Single App Mode – enable single app mode
  • Select Single App – select the app to run in single app mode from the list of installed apps or specify an Intent URL
  • 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+)
  • Wait for Boot Completed – Wait for device boot completed before starting the single app
  • Pause for Updates – Keep the single app paused for 15 minutes after scheduled wakeup for possible updates (EXPERIMENTAL, ver. 1.51+). Otherwise single app has no chance to be updated by Google Play if staying in foreground all time. Scheduled Wakeup/Sleep must be used in Power Settings in order this option to take effect.
• Disable Notifications – block all status bar notifications from other apps (ver. 1.40+)
• Disable Incoming Calls – block all incoming calls (ver. 1.42+)
• Disable Outgoing Calls – block all outgoing calls (except emergency calls) (ver. 1.42+)
• Disable Screenshots – Disallow taking screenshots and screen recording in Fully Kiosk (doesn’t affect other apps). This option will also cause remote control tools like Anydesk or Teamviewer to show black screen. Restart the app after changing this option to apply! (ver. 1.43+)
• Lock Safe Mode – Sperren Sie den abgesicherten Modus von Android. Der Sperrbildschirm des Geräts wird zu diesem Zweck mit Ihrer Kiosk-PIN aktiviert. Dies kann beim Starten anderer Apps problematisch sein. Beachten Sie, dass diese Option in Android nicht rückgängig gemacht werden kann, auch wenn sie deaktiviert ist. Fully Kiosk . Sie können die Bildschirmsperre in den Android-Einstellungen manuell wieder deaktivieren, nachdem Sie die Administratorberechtigung von Fully Kiosk .
• Disable Camera – Kamera für alle Apps deaktivieren (einschließlich Fully Kiosk , daher wird die visuelle Bewegungserkennung deaktiviert)

• Enable Visual Motion Detection – use from camera for motion detection – siehe  unten
  • Detector Sensitivity – Erkennungsempfindlichkeit 0-100, höherer Wert bedeutet höhere Empfindlichkeit, funktioniert meist am besten bei 90-95
  • Detector Frame Rate – Detektorrate pro Sekunde (1-25), ein höherer Wert macht die Erkennung zuverlässiger, verursacht jedoch eine höhere CPU-Auslastung
  • Darkness Level – Dunkelheitsschwellenwert (0-100). Ein niedrigerer Wert löst Dunkelheit bei niedrigerem Umgebungslicht aus. Wenn Sie ihn auf 100 einstellen, wird Dunkelheit auch bei hellen Bedingungen ausgelöst. Nur relevant, wenn „Bildschirm bei Dunkelheit ausschalten“ aktiviert ist.
  • Select Camera – Wählen Sie die Kamera für die Bewegungserkennung aus. Beachten Sie, dass viele externe Kameras noch nicht von den Camera Legacy- und CameraX-APIs unterstützt werden.
  • Show Cam Preview – zeigt ein kleines Kameravorschaubild in der rechten unteren Ecke. Wenn die Gesichtserkennung aktiviert ist, werden Ihnen auch Smileys angezeigt, wenn Gesichter erkannt werden.
  • Camera API – Wählen Sie die Kamera-API für die Bewegungserkennung. Zur Anwendung ist ein Neustart der App erforderlich (EXPERIMENTELL, Version 1.54+). Sie können zwischen der Android Camera (Legacy, Standard) oder der Android CameraX API wählen. Die CameraX API bietet auf neueren Geräten möglicherweise eine bessere Kameraunterstützung, kann jedoch auf älteren Geräten fehlerhaft sein. Standardmäßig wird CameraX unter Android 15+ (Version 1.59+) verwendet.
  • Detect Faces – Aktivieren Sie die Gesichtserkennung im Kamerabild (experimentell, Version 1.48+). Sie können die neue JS-API vollständig nutzen. getFaceNumber() und Ereignisse abrufen, die von MQTT und JS-API erkannt wurden .
  • Face Detection Confidence – Erforderliche Konfidenzschwelle für die Gesichtserkennung, Standard 30 % (Ver. 1.55+)
  • Trigger Motion only when Faces Detected – Bewegungserkennung wird (nur!) ausgelöst, wenn Gesichter im Kamerabild erkannt werden. Solange keine Gesichter auf der Kamera zu sehen sind, wird die Bewegung nicht ausgelöst. (Ver. 1.48+)
  • Pause, wenn Fully in Background – Bewegungserkennung pausieren, während eine andere App im Vordergrund ist
• Enable  Acoustic Motion Detection – Verwenden Sie das Gerätemikrofon zur Bewegungserkennung. Diese Funktion scheint unter Android 11+ auf einigen Geräten nicht zu funktionieren.
  • Acoustic Detector Sensitivity – Mikrofonempfindlichkeit 0-100, funktioniert meist am besten bei 90-100
• Enable Proximity Motion Detection – Verwenden Sie den Näherungssensor des Geräts zur Bewegungserkennung. Beachten Sie, dass dieser Sensor normalerweise nur Objekte erkennt, die sich sehr nahe am Gerät befinden (Version 1.59+).
• Turn Screen On on Motion – Bildschirm einschalten, wenn Bewegung erkannt wird. Suchen Sie im Abschnitt „Geräteverwaltung“ nach dem Bildschirm-Aus-Timer
• Exit Screensaver on Motion – Bildschirmschoner bei Bewegungserkennung stoppen, Bildschirmschonereinstellungen im Abschnitt „Bildschirmschoner“ suchen
• Stop Web Reload on Motion – Neuladetimer zurücksetzen, wenn Bewegung erkannt wird. In den Web-Auto-Neuladeeinstellungen nachsehen, ob der automatische Neuladetimer bei Leerlauf aktiv ist (Ver. 1.43+).
• Turn Screen Off in Darkness – Bildschirm ausschalten, wenn Dunkelheit erkannt wird

• Enable Movement Detection – Verwenden Sie Beschleunigungs- und Kompasssensoren zur Bewegungserkennung des Geräts (kann zum Diebstahlschutz mit Warnungen von verwendet werden Fully Cloud )
  • Accelerometer Sensitivity – Beschleunigungssensorempfindlichkeit (0-100) zum Auslösen der Bewegungserkennung
  • Compass Sensitivity – Kompassempfindlichkeit (0-100) zum Auslösen der Bewegungserkennung
  • Turn Screen On on Movement – Bildschirm einschalten, wenn eine Bewegung des Geräts erkannt wird. Suchen Sie oben in der Geräteverwaltung nach den Einstellungen zum Ausschalten des Bildschirms
  • Exit Screensaver on Movement – Bildschirmschoner stoppen, wenn eine Gerätebewegung erkannt wird. Die Bildschirmschonereinstellungen finden Sie im Abschnitt „Bildschirmschoner“ oben .
  • Play Alarm Sound on Movement – Bei Erkennung einer Gerätebewegung einen kurzen Alarmton abspielen (Diebstahlschutz)
  • Alarm Sound File URL – Bei Alarm Datei von dieser URL abspielen, für Standardton leer lassen, für lokale Dateien kann die URL file:// verwendet werden
  • Play Alarm Sound until PIN entered – Sobald der Alarm ausgelöst wurde, wird im Kioskmodus der Alarmton so lange abgespielt, bis die richtige PIN eingegeben wird
  • Ignore Motion Detection when Moving Device – keine Bewegung erkennen, während die Gerätesensoren Bewegungen erkennen
  • Trigger Movement when Device Unplugged – Bewegung erkennen, wenn das Gerät von der Stromquelle getrennt wird (Ver. 1.33+)
  • Anti-Theft Beacon IDs – Liste der iBeacons als UUID/Major/Minor (ohne führende Nullen), ein Beacon pro Zeile, Platzhalter * möglich. Wird ein Beacon aus dieser Liste innerhalb der angegebenen Entfernung erkannt, wird eine Bewegung ausgelöst. Bitte verwenden Sie eine Scanner-App wie diese, um die Beacon-Erkennung zu testen und die IDs anzuzeigen. Beachten Sie, dass Beacons nur dann zuverlässig erkannt werden, wenn unsere Fully Kiosk App ist im Vordergrund und der Bildschirm ist eingeschaltet.
  • Anti-Theft Beacon Distance – Entfernungsschwelle zum iBeacon, wo eine Bewegung erkannt werden soll (in Metern, sehr ungefähr!)

• Enable Remote Administration – Infos anzeigen, konfigurieren und steuern Fully remotely in any web browser – siehe unten
  • Remote Admin Password – Passwort festlegen, erforderlich für die Remote-Admin-Site, für die REST-Schnittstelle und für Fully Cloud EMM -Zugriff auf das Gerät
  • Remote Admin from Local Network – Aktivieren Sie die Remote-Administration und die REST-Schnittstelle im lokalen Netzwerk oder über VPN unter  http://IP-Adresse:2323. Sie können eine HTTPS-Verbindung zur Remote-Administration herstellen, wenn Sie ein gültiges SSL-Zertifikat auf dem Gerät installieren ( weitere Informationen ). Wenn Sie diese Option deaktivieren, wird die Verbindung zur Remote-Administration nur von diesem Gerät (localhost) akzeptiert.
  • Enable File Management on Remote Admin – Auflisten und Herunterladen lokaler Dateien über die Remote Admin-Weboberfläche zulassen (1.32.2+)
  • Enable Screenshot on Remote Admin – Erlauben Sie das Erstellen eines Screenshots auf Remote Admin. Diese Option kann auf Remote Admin nicht geändert werden.
  • Enable Camshot on Remote Admin – Erlaubt das Aufnehmen eines Camshots auf Remote Admin (erfordert Bewegungserkennung), diese Option kann auf Remote Admin nicht geändert werden
  • Remote-Admin von Fully Cloud – Aktivieren Sie auch die weltweite Fernverwaltung mit Fully Cloud EMM-Dienst unter fully-kiosk.com/cloud Wenn diese Option aktiviert ist, sendet die App regelmäßig Heartbeats an Fully Cloud . Dies kann zu Datenverkehrskosten führen. Welche Daten übertragen werden, erfahren Sie in der Datenschutzerklärung .
  • Gerätestandort übermitteln an Fully Cloud – Schalten Sie es aus, wenn der Gerätestandort in Ihrem Anwendungsfall sensible/geschützte Daten sind (Ver. 1.55.3+)
  • Gerät hinzufügen zu Fully Cloud – Geben Sie Konto und Passwort an, um dieses Gerät hinzuzufügen Fully Cloud EMM. Sie können die Cloud-Anmeldeinformationen (verschlüsselt) speichern, um sie auf andere Geräte zu kopieren, indem Sie deployment verarbeiten  und andere Geräte automatisch hinzufügen Fully Cloud .

• Enable Root Features – Holen Sie sich Root-Rechte für die App und erlauben Sie Root-Funktionen, verwenden Sie es mit Vorsicht
• Daily System Restart – Geplante Zeit (HH:MM) im 24h-Format für den automatischen Geräteneustart, leer lassen für deaktiviert
• Shutdown on Power Disconnect – Schaltet das Gerät nach einer definierten Anzahl von Sekunden nach dem Trennen des Netzsteckers aus. Behalten Sie 0 für deaktiviert bei.
• Klar Launcher Apps – alles zurücksetzen launcher Apps nach Fully Kiosk ist für eine definierte Anzahl von Sekunden im Vordergrund, behalten Sie 0 für deaktiviert bei
• Clear Single App after Idle Time – Setzen Sie die einzelne App nach einer definierten Anzahl von Sekunden Inaktivität des Benutzers zurück, setzen Sie 0 für deaktiviert
• Kill Apps Before Starting Them – Beenden Sie ausgewählte Apps immer, bevor Sie sie starten. Geben Sie pro Zeile einen Paketnamen ein.

• Lock Task Mode  – Besserer Schutz im Kioskmodus, Deaktivieren der Home- und der letzten Aufgabenschaltfläche, Deaktivieren der Statusleiste (nur im Kioskmodus).
  • Aktivieren des Task-Sperrmodus
  • App Lock Task Whitelist – Ermöglicht ausgewählten Apps den Wechsel in den Sperrmodus, ein Paketname pro Zeile. Ab Version 1.43 werden Apps gestartet von Fully Kiosk wird automatisch auf die Whitelist gesetzt.
  • Enable Home Button – Erzwingen der Anzeige der Home-Taste im Task-Sperrmodus (Ver. 1.43+, Android 9+)
  • Enable Recent Task Button – Erzwingen der Anzeige der Schaltfläche „Letzte Aufgabe“ im Aufgabensperrmodus (Ver. 1.43+, Android 9+)
  • Enable Notifications – Statusleiste und Benachrichtigungen im Sperraufgabenmodus aktivieren (Ver. 1.43+, Android 9+)
  • Enable System Info – Aktivieren Sie die Systeminformationen in der Taskleiste im Task-Sperrmodus (Ver. 1.43+, Android 9+)
  • Enable Showing Global Actions – Aktivieren Sie die Anzeige globaler Aktionen beim langen Drücken der Einschalttaste im Task-Sperrmodus (Ver. 1.43+, Android 9+).
• Disable Status Bar – Statusleiste besser deaktivieren (nur im Kioskmodus)
• Disable Keyguard – Das Aktivieren dieser Option hat die gleiche Wirkung wie die Auswahl von „Keine“ für den Bildschirmsperrtyp. Diese Option hat jedoch keine Wirkung, wenn aktuell ein Passwort, eine PIN oder ein Muster festgelegt ist. Sie müssen diese Option aktivieren, wenn Sie die Bildschirmsperre auf bereitgestellten Geräten deaktivieren möchten. Das automatische Deaktivieren der Wisch-Bildschirmsperre funktioniert jedoch auf einigen Geräten nicht. Suchen Sie nach einer Alternative zur experimentellen Option „Wisch-Bildschirmsperre entsperren“ in den Geräteverwaltungseinstellungen oder stellen Sie die Bildschirmsperre manuell auf „Keine“.
• Ton stummschalten und Lautstärketasten deaktivieren
• Bildschirmaufnahme deaktivieren
• USB-Speicher deaktivieren
• ADB deaktivieren
• Disable Boot in Safe Mode – das funktioniert nicht bei allen Geräten 100%ig
• Location Mode – Aktivieren oder Deaktivieren des Standortdienstes beim App-Start erzwingen (Ver. 1.59+)
• System Update Policy – Richtlinie für Over-the-Air-Systemupdates auswählen: so schnell wie möglich, 30 Tage verschieben oder nur im Zeitfenster 22:00-02:00 Uhr
• Passwortqualität
• Minimale Kennwortlänge
• App Runtime Permission Policy – Standard-Laufzeitberechtigungsrichtlinie: Auffordern, Erteilen oder Verweigern
• Additional User Restrictions – Wenden Sie andere Benutzerbeschränkungen per Richtlinie an, eine Beschränkung pro Zeile, überprüfen Sie die Android-Dokumente auf IDs (verwenden Sie Werte wie no_add_user , no_add_wifi_config , no_adjust_volume usw.)
• Disable Apps From Unknown Sources – App-Installation aus APK-Datei deaktivieren
• APK Files to Install – geben Sie eine URL pro Zeile ein. Die stille Installation kann mit Android 6+ durchgeführt werden. Dazu muss „Apps aus unbekannten Quellen deaktivieren“ deaktiviert sein.
• APK File Update Interval – Alle X Minuten, mindestens 15 Minuten, auf APK-Updates gemäß Last-Modified-Server-Antwortheader prüfen, 0 für deaktiviert setzen
• APK File Update Time – Täglich um diese Uhrzeit HH:MM nach APK-Updates gemäß der zuletzt geänderten Serverantwort suchen, leer: deaktiviert (Ver. 1.56+)
• System Apps to Enable – Aktiviere ausgewählte System-Apps, ein Paketname pro Zeile. Standardmäßig sind die meisten vorinstallierten Apps deaktiviert durch device provisioning . Beim Erstellen provisioning Mit der QR-Methode können Sie auswählen, ob die Apps im provisioning Konfiguration festlegen
• Apps to Disable – Zugriff auf ausgewählte Apps deaktivieren, ein Paketname pro Zeile
• APN Config – fügen Sie eine benutzerdefinierte APN-Konfiguration hinzu, eine pro Zeile, wie folgt: 

entryName=APN1;apnName=mbb.mobi-data.com;operatorNumeric=26006;protocol=2;roamingProtocol=2
entryName=APN2;apnName=mbb2.mobi-data.com;operatorNumeric=26006;protocol=2;roamingProtocol=2

Unterstützt auch optionale Felder apnTypeBitmask und carrierEnabled .

• Global Proxy Config – Geben Sie die globale Proxy-Adresse als Host:Port an oder geben Sie eine vollständige PAC-URL an
• Daily System Restart – Geplante Zeit (HH:MM im 24-Stunden-Format) für den automatischen Systemneustart, leer lassen für deaktiviert (Ver. 1.49+)
• Remove Device Owner (EXPERIMENTAL) – Abmelden unserer App als Gerätebesitzer, kann verwendet werden, um die Kiosk-App vom bereitgestellten Gerät zu deinstallieren

• • Enable KNOX Features – Aktivieren Sie Samsung KNOX-Funktionen. Für die Aktivierung der KNOX-Lizenz ist Internet erforderlich. KNOX-Funktionen sind nur für B2B-Kunden verfügbar. Verwenden Sie diese Funktionen mit Vorsicht, da das Gerät möglicherweise unbrauchbar wird. Nach der Aktivierung müssen Sie die KNOX-Lizenzvereinbarung auf dem Gerät lesen und bestätigen. Dies ist nicht remote möglich. Testen Sie sorgfältig, da einige Geräte nach einem Neustart die KNOX-Lizenz verlieren oder erneut nach einer KNOX-Lizenzbestätigung fragen.
  • Use only when Kiosk Locked – Aktivieren Sie KNOX-Funktionen nur, wenn der Kiosk gesperrt ist, sonst werden die KNOX-Einstellungen wirksam, auch wenn Fully Kiosk wird gestoppt (Ver. 1.41+)
  • Disable Camera – Kamera für alle Apps deaktivieren
  • Disable Screen Capture – Screenshots deaktivieren
  • Disable Status Bar – besser das Herunterziehen der Statusleiste deaktivieren
  • Hide Status Bar – Inhalt der Statusleiste entfernen (Ver. 1.32+)
  • Hide Navigation Bar – Inhalt der Navigationsleiste entfernen (Ver. 1.32+)
  • Disable Hardware Home Button – Home-Button deaktivieren (Ver. 1.32+)
  • Disable Hardware Back Button – Zurück-Schaltfläche deaktivieren (Ver. 1.32+)
  • Disable Hardware Power Button – Einschaltknopf deaktivieren (Ver. 1.32+)
  • Disable Hardware Recent Task Button – Schaltfläche „Letzte Aufgabe“ deaktivieren (Ver. 1.32+)
  • Disable Hardware Volume Keys – Lautstärketasten deaktivieren (Ver. 1.32+)
  • Disable USB Host Storage – Deaktivieren Sie den USB-Zugriff auf externe Speicher und Geräte
  • Disable Media Transfer Protocol – Deaktivieren Sie den USB-Zugriff auf den Gerätespeicher über MTP
  • Disable Safe Mode – abgesicherten Modus deaktivieren
  • Disable OTA Upgrades – (Ver. 1.42+)
  • Disable Airplane Mode – (Ver. 1.42+)
  • Disable Android Beam – (Ver. 1.42+)
  • Disable Audio Record – (Ver. 1.42+)
  • Disable Bluetooth – (Ver. 1.42+)
  • Disable Clipboard Share – (Ver. 1.42+)
  • Disable Developer Mode – (Ver. 1.42+)
  • Disable Google Account Sync – (Ver. 1.42+)
  • Disable Google Crash Report – (Ver. 1.42+)
  • Disable Power Off – (Ver. 1.42+)
  • Disable Power Saving Mode – (Ver. 1.42+)
  • Disable SD Card Write – (Ver. 1.42+)
  • Disable Settings Changes – (Ver. 1.42+)
  • Disable Video Records – (Ver. 1.42+)
  • Disable VPN – (Ver. 1.42+)
  • Disable Wifi – (Ver. 1.42+)
  • Disable Wifi Direct – (Ver. 1.42+)
  • Disable non-Google-Play Apps – (Ver. 1.42+)
  • Disable Google Backup – (Ver. 1.42+)
  • Disable Mobile Data – (Ver. 1.42+)
  • Disable Data Roaming – (Ver. 1.55+)
  • Disable Clipboard – (Ver. 1.42+)
  • Disable Headphones – (Ver. 1.42+)
  • Disable Microphone – (Ver. 1.42+)
  • Disable USB Debugging – (Ver. 1.42+)
  • Disable Bluetooth Tethering – (Ver. 1.42+)
  • Disable USB Tethering – (Ver. 1.42+)
  • Disable Wifi Tethering – (Ver. 1.42+)
  • Disable Multiple Users – Deaktivieren Sie die Unterstützung mehrerer Benutzer. Benutzer können keine neuen Benutzer erstellen oder sich als Gast anmelden.
  • 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+)
  • Force Auto Start – Erzwingen Sie den Gerätestart beim Einschalten (NUR für Qualcomm- und LSI-Chipsätze, Version 1.48+)
  • APN Config – Fügen Sie benutzerdefinierte APN-Konfigurationen hinzu, eine pro Zeile (Ver. 1.48+), im Format wie folgt:

name=APN1;apn=mbb.mobi-data.com;mcc=260;mnc=06;protocol=IPV4V6;roamingProtocol=IPV4V6
name=APN2;apn=mbb2.mobi-data.com;mcc=260;mnc=06;protocol=IPV4V6;roamingProtocol=IPV4V6;preferred=true

• Tägliche Nutzungsstatistiken ( PLUS ) – Sammeln Sie täglich lokale Nutzungsstatistiken auf diesem Gerät, die nur Ihnen in der Remote-Admin-Oberfläche zur Verfügung stehen. Diese Funktion ist bei einigen Geräten nicht verfügbar, da wir die Bildschirmberührungen nicht zuverlässig zählen können.
• Umgebungssensoren aktivieren ( PLUS , ver. 1.40+) – ermöglicht das Lesen der verfügbaren Umgebungssensoren des Geräts. Die Sensorkonfigurationen und -werte können mithilfe der JS-API oder der REST-API abgerufen werden .
• Barcode-Scanner-Integration ( PLUS , ver. 1.40+) – select barcode scanner app, listen for input, open URL, trigger JS API, insert code into website etc. – lesen Sie diese FAQ
  • Barcode Scan App – Wählen Sie die App aus oder geben Sie die URL zur Scanner-App an. Lassen Sie das Feld leer, um den eingebetteten QR-Scanner (mithilfe der Rückkamera) zu verwenden.
  • Listen for Keyboard Input – wartet auf Tastenanschläge des Hardware-Barcode-Scanners (bis zur Eingabetaste). Verwenden Sie diese Option, wenn Ihr Scanner beim Scannen von QR-Codes Tastatureingaben simuliert. Diese Option funktioniert bei einigen Scanner-Apps nicht zuverlässig.
  • Barcode Scan Broadcast Intent Action – broadcast intent action from scanner app to listen for, empty for none. Use this and the next option when your scanner is sending a broadcast intent when a QR code is read. 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
  • Barcode Scan Target URL – URL to load on QR scan read, use $code placeholder, keep empty to not open any URL. If your QR code contains the URL you may want to put $code into this option in order to open that URL.
  • Insert Barcode Into Website – Try to insert the received barcode into the first input field on the current page (identified by input[type=”text”] selector).
  • Submit Form after Inserting the Barcode – try to submit the web form of the first input field.
• MQTT Integration ( PLUS ) – send device info and events to MQTT broker, look here for docs. Starting FKB 1.50 MQTT support is only available with Android 7+ devices.
  • Enable MQTT
  • MQTT Broker URL – specify your MQTT broker URL like  ssl://xxx.s1.eu.hivemq.cloud:8883
  • MQTT Broker Username
  • MQTT Broker Password
  • MQTT Client ID – client ID for MQTT broker connection (optional), a random one will be used if empty, can use variables like $deviceId
  • MQTT Device Info Topic – customize device info topic name, can use placeholders like $deviceId or $mac, default: $appId/deviceInfo/$deviceId (ver. 1.41+)
  • MQTT Event Topic – customize event topic name, can use placeholders like $event, $deviceId or $mac, default: $appId/event/$event/$deviceId (ver. 1.41+)
• Restart Fully After Crash ( PLUS ) – try to restart the Fully Kiosk app after any crash, check this FAQ
• Restart Fully After Update ( PLUS ) – try to restart the Fully Kiosk app after update of Fully or Android System Webview or Google Chrome, requires Kiosk Mode to be enabled
• Run as Priority App – Try prevent Android System from killing Fully even when resources are low and try to restart when killed. This option is always enabled in Android 8+
• Consider Device in Use while Keyboard Visible – don’t run features like screensaver, screen off, reload on idle when keyboard is open. With this option you can avoid starting on idle features while the soft keyboard is open.
• Consider Device is Use while Audio Playing – don’t run features like screensaver, screen off, reload on idle when music/video is playing (ver. 1.43+)
• Consider Device in Use while Using Another App – don’t run features like screensaver, screen off, reload on idle when another app is in foreground or screen is off. For using screensaver with other apps 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 or virtual keyboard is in foreground
• Regain Focus Timer ( PLUS ) – Bring Fully to foreground after some idle time with no interactions, set 0 for disabled
• Go To Background Timer ( PLUS )  – bring Fully Kiosk to the background after some idle time (set it in seconds), set 0 for disabled
• Custom Text Variable – sein Wert kann als $customVariable in allen URLs bei der Konfiguration verwendet werden (Ver. 1.53+)
• Benutzerdefiniertes Gebietsschema ( PLUS ) – Sprachkennzeichen ( IETF BCP 47 ) wie en-US oder de-CH, um eine andere Lokalisierung zu erzwingen Fully App, Systemstandard, wenn leer. Betrifft nur die Gebietsschemas/Sprachen in der Webview und einige für den Endbenutzer sichtbare Dialoge, das App-Menü/die App-Einstellungen sind nur auf Englisch verfügbar. Sie müssen die Registerkarten erneut öffnen, um sie anzuwenden Webview (Ver. 1.53+)
• Enable Version Info – Update-Zusammenfassungen beim Start anzeigen
• Show Menu Hint on Start – Demo und Hinweise zeigen, wenn Fully startet. Durch das Deaktivieren dieser Option werden auch veraltete Webview Warnungen.
• Dark Mode – Wählen Sie die Art der Dunkelmodus-Behandlung in der App. Diese Option ist nur wirksam, wenn sie vom Android-Betriebssystem unterstützt wird. Ein Neustart der App ist erforderlich, um die Änderung dieser Option zu übernehmen.
• Video Player Engine – Wählen Sie die Engine für die Wiedergabe von Vollbildvideos. Zur Anwendung ist ein Neustart der App erforderlich (EXPERIMENTELL). Sie können zwischen Android Media Player (Standard) und Media3 Exoplayer wählen. Lesen Sie diese FAQ (Version 1.52+).
• Render in Cutout Area – Anzeige von Inhalten im Notch-Bereich aktivieren (Ver. 1.43+)
• Confirm Exit – Bestätigungsfeld beim Beenden anzeigen
• Export Settings – alle Einstellungen in fully-settings.json schreiben
• Import Settings – Wählen Sie eine JSON-Einstellungsdatei aus und lesen Sie alle Einstellungen daraus
• Reset Settings – Alle Einstellungen auf Standardwerte zurücksetzen (Ver. 1.43+)
• Enable Settings Auto-Import – auto-import settings from fully-auto-settings.json and fully-once-settings.json at app start – für schnelle deployment
• Get All Runtime Permissions – Fordern Sie alle fehlenden Laufzeitberechtigungen an, unabhängig vom aktuellen Bedarf
• Device ID – Geräte-ID anzeigen, tippen, um in die Zwischenablage und in die Datei /sdcard/Download/fully-deviceID*.txt für die Offline-Lizenzierung zu kopieren
• Volume License Key – Für eine einfache Volumenlizenzierung geben Sie hier Ihren Volumenlizenzschlüssel ein. Sie erhalten ihn, wenn Sie für 10+ Geräte bestellen. Für Einzellizenzen verwenden Sie bitte Get a PLUS Lizenz   im App-Menü. Wenn Sie diesen Schlüssel entfernen, wird Ihr Gerät von der Volumenlizenz abgemeldet. Für die Volumenlizenzierung ist beim An- und Abmeldevorgang des Geräts eine Internetverbindung erforderlich. Eine Offline-Lizenzierung ist ebenfalls möglich .
• Version Info – Jetzt die letzten Update-Informationen anzeigen
• Device Info – Zusammenfassung der Geräteinformationen anzeigen. Bitte senden Sie uns eine Kopie, wenn Sie einen Fehler melden

Sie benötigen OpenSSL 3.x und einige Linux-Kenntnisse, um ein SSL-Zertifikat für das Gerät zu erstellen. Erstellen Sie zunächst ein Stammzertifikat (zum Signieren anderer Zertifizierungsstellen) mit einem Skript wie diesem:

openssl version
# OpenSSL 3.x.xx

mkdir CA
# Generate root CA, specify some good password for the private key
openssl genrsa -aes256 -out CA/rootCA.key 4096
openssl req -x509 -new -nodes -key CA/rootCA.key -sha256 -days 3650 -out CA/rootCA.crt

Importieren Sie rootCA.crt als vertrauenswürdige Stammzertifizierungsstelle in Ihren Webbrowser.

Erstellen Sie nun für jedes Gerät ein Domänenzertifikat „  fully-remote-admin-ca.p12 “ mit dem Kennwort „fully“. Geräte müssen in Ihrem lokalen Netzwerk über einen Hostnamen wie host.domain.tld und nicht über die IP-Adresse angesprochen werden.

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

# Pack domain certificate to PKCS12 file
openssl pkcs12 -legacy -export \
-out CA/fully-remote-admin-ca.p12 \
-inkey CA/domain.key \
-in CA/domain.crt \
-passout pass:fully

Wenn Sie ein Host-Zertifikat mit einer CA-Behörde wie Letsencrypt generiert haben , können Sie es wie folgt in die PKCS12-Datei packen:

openssl pkcs12 -legacy -export \
-out fully-remote-admin-ca.p12 \
-inkey /path/to/letsencrypt/live/host.domain.tld/privkey.pem \
-in /path/to/letsencrypt/live/host.domain.tld/cert.pem \
-certfile /path/to/letsencrypt/live/host.domain.tld/chain.pem \
-passout pass:fully

Jetzt müssen Sie die Datei fully-remote-admin-ca.p12 in den Stammordner des app-spezifischen oder freigegebenen Speichers (sofern zugänglich) auf dem Gerät legen und neu starten Fully Kiosk . Remote Admin ist jetzt am Standort https://host.domain.tld:2323 verfügbar

Dieses Setup funktioniert zumindest mit dem aktuellen Google Chrome unter Windows 11 ohne Warnungen. Bei der Verwendung anderer Clients ist möglicherweise ein etwas anderes SSL-Setup erforderlich.

// Get Device Info JSON
/?cmd=getDeviceInfo&password=[pass]
// Get  Fully  Log
/?cmd=showLog&password=[pass]
// Get Logcat
/?cmd=logcat&password=[pass]

// Load URL
/?cmd=loadStartUrl&password=[pass]
/?cmd=loadUrl&url=[url]&password=[pass]
/?cmd=loadUrl&url=[url]&tab=[0..n]&focus=[true|false]&password=[pass]
/?cmd=loadUrl&url=[url]&newtab=[true|false]&focus=[true|false]&password=[pass]

// Manage Tabs
/?cmd=focusTab&tab=[index]&password=[pass]
/?cmd=closeTab&tab=[index]&password=[pass]
/?cmd=refreshTab&password=[pass] (ver. 1.45+)

// Remove Web Items
/?cmd=clearCache&password=[pass]
/?cmd=clearWebstorage&password=[pass]
/?cmd=clearCookies&password=[pass] (ver. 1.28+)
/?cmd=reset Webview &password=[pass] (ver. 1.55.3+)

// Screen on/off
/?cmd=screenOn&password=[pass]
/?cmd=screenOff&password=[pass]
/?cmd=forceSleep&password=[pass]

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

//  Fully  Screensaver and Android Screen Saver (Daydream)
/?cmd=startScreensaver&password=[pass]
/?cmd=stopScreensaver&password=[pass]
/?cmd=startDaydream&password=[pass]
/?cmd=stopDaydream&password=[pass]

// Unlock/lock kiosk mode
/?cmd=lockKiosk&password=[pass]
/?cmd=unlockKiosk&password=[pass]

// Start other apps
/?cmd=startApplication&package=[pkg]&password=[pass]
/?cmd=startIntent&url=[intenturl]&password=[pass]

// Bring  Fully  app to foreground/background
/?cmd=toForeground&password=[pass]
/?cmd=toBackground&password=[pass]

// Restart and exit  Fully Kiosk 
/?cmd=restartApp&password=[pass]
/?cmd=exitApp&password=[pass]
/?cmd=killMyProcess&password=[pass]  // Kill my app hard (ver. 1.55+) 

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

// Download and launch APK file, user input can be required for install
// If app already installed in this version, APK install will be started only if forceInstall=true
// These features are not available if you installed  Fully Kiosk  from Google Play
/?cmd=loadApkFile&url=[url]&forceInstall=[true|false]&password=[pass]
/?cmd=uninstallApp&package=[package]&password=[pass]

// Get current APK installation status (JSON)
/?cmd=getInstallApkState&password=[pass]

// Kill background processes for package (Android 13 and older)
/?cmd=killBackgroundProcesses&package=[package]&password=[pass]

// Clear app data (Android 9+, provisioned devices only)
/?cmd=clearAppData&package=[package]&password=[pass]

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

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

// Rooted devices only
/?cmd=shutdownDevice&password=[pass]
/?cmd=runRootCommand&command=[command]&password=[pass]
/?cmd=runSuCommand&command=[command]&password=[pass]
// Rooted and provisioned devices only
/?cmd=rebootDevice&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]
/?cmd=textToSpeech&text=[text]&locale=[locale]&engine=[engine]&password=[pass]&queue=[0|1] // ver. 1.38+
/?cmd=stopTextToSpeech // ver. 1.38+ 

// Play sounds/video and change audio volume
// Audio Streams: 0 – Voice Call, 1 – System, 2 –  Ring, 3 – Music, 4 – Alarm, 5 – Notification, 6 – Bluetooth, 8 – DTMF, 9  – TTS, 10 – Accessibility
/?cmd=setAudioVolume&level=[0-100]&stream=[0-10]&password=[pass]
/?cmd=playSound&url=[url]&loop=[true|false]&password=[pass]&stream=[0-10]
/?cmd=stopSound&password=[pass]
/?cmd=playVideo&password=[pass]&url=[url]&loop=[0|1]&showControls=[0|1]&exitOnTouch=[0|1]&exitOnCompletion=[0|1]
/?cmd=stopVideo&password=[pass] // ver. 1.42+

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

// Get current setting values
/?cmd=listSettings&type=json&password=[pass]

// Import JSON settings file from URL or file
/?cmd=importSettingsFile&url=[url]&password=[pass]

// Download and upzip file from URL to directory
// If dir is not specified use shared storage root (if Android 9 or older, or All Files Access granted), otherwise use app specific storage root
/?cmd=loadZipFile&url=[url]&dir=[dir]&password=[pass]

// Download/delete local files
/?cmd=deleteFile&filename=[filename]&password=[pass]
/?cmd=downloadFile&filename=[filename]&password=[pass]
/?cmd=deleteFolder&foldername=[foldername]&password=[pass] // ver. 1.42+

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()
String fully.getWifiSignalLevel()
String fully.getSerialNumber()
String fully.getSerialNumberDeviceOwner()
String fully.getAndroidId()
String fully.getDeviceId()
String fully.getDeviceName()
String fully.getImei()
String fully.getSimSerialNumber()
float fully.getBatteryLevel()
float fully.getScreenBrightness()
int fully.getScreenOrientation()
int fully.getDisplayWidth()
int fully.getDisplayHeight()
long fully.getIdleTime()
long fully.getLastUserInteractionTime()
boolean fully.getScreenOn()
boolean fully.isPlugged()
boolean fully.isKeyboardVisible()
boolean fully.isWifiEnabled()
boolean fully.isWifiConnected()
boolean fully.isNetworkConnected()
boolean fully.isBluetoothEnabled()
boolean fully.isScreenRotationLocked()
String fully.get Fully Version()
int fully.get Fully VersionCode()
String fully.get Webview Version()
String fully.getAndroidVersion()
int fully.getAndroidSdk()
String fully.getDeviceModel()
String fully.getLocation() // Returns a JSON String

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

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

// Get data usage (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)
void fully.log(int type, String tag, String message)

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

// Run root command (rooted devices only)
void fully.runCommand(String command)
void fully.runSuCommand(String command)

void fully.reboot() // Provisioned and rooted devices only
void fully.shutdown() // Rooted devices only

// Note that write access to external SD card is not supported by many devices
void fully.deleteFile(String path)   
void fully.deleteFolder(String path) // recursive!
void fully.emptyFolder(String path)  // recursive!
void fully.createFolder(String path)
String fully.getFileList(String folder)  // get JSON array
boolean fully.writeFile(String path, String content)
String fully.readFile(String path) // ver. 1.55+
void fully.downloadFile(String url, String dirName)
void fully.downloadFile(String url, String dirName, boolean showToastMessages)
void fully.unzipFile(String fileName)
void fully.downloadAndUnzipFile(String url, String dirName)

// Get storage paths (ver. 1.59+)
String fully.getInternalSharedStoragePath()
String fully.getInternalAppSpecificStoragePath()
String fully.getInternalAppPrivateStoragePath()
String fully.getExternalSharedStoragePath()
String fully.getExternalAppSpecificStoragePath()

// 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()
void fully.initTts() // ver. 1.55, listen for ttsInitSuccess event for $info, containing available engines, voices and locales

void fully.playVideo(String url, boolean loop, boolean showControls, boolean exitOnTouch, boolean exitOnCompletion)
void fully.stopVideo()

// 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) // level: 0..100
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()
boolean fully.isMusicActive()

// Manage web browsing
String fully.getStartUrl()
void fully.setStartUrl(String url)
void fully.loadStartUrl()
void fully.addToHomeScreen()
void fully.shareUrl()
void fully.print()  // window.print() doesn't work
void fully.print2Pdf(String filename)  // Print A4 paper w/o prompt
String fully.getScreenshotPngBase64()
String fully.loadStatsCSV()

// Purge web items
void fully.clearCache()
void fully.clearFormData()
void fully.clearHistory()
void fully.clearCookies()
void fully.clearCookiesForUrl(String url)
void fully.clearWebstorage()
void fully.reset Webview  // ver. 1.55.3+

// Manage web tabs
void fully.focusThisTab()
void fully.focusNextTab()  
void fully.focusPrevTab()
void fully.focusTabByIndex(int index)
int fully.getCurrentTabIndex()
int fully.getThisTabIndex()
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)

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

// 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)

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

// Respond to QR events
void fully.bind('onQrScanSuccess','todo(\'$code\');')
void fully.bind('onQrScanCancelled','todo();')

// Get a list of known devices incl. connection state and battery level
String fully.btGetDeviceListJson()

// Open a serial (SPP) bluetooth connection (GATT is not supported!)
// These functions are async, listen to events below to get results
void fully.btOpenByMac(String mac)
void fully.btOpenByUuid(String uuid)
void fully.btOpenByName(String name)

// Get info about connected device 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");'); // Data is buffered until LF symbol found

// Note that NFC scan usually doesn't work if the screen is locked or the camera is in use
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();')
void fully.bind('onDaydreamStop','todo();')
void fully.bind('onBatteryLevelChanged','todo("$level");')
void fully.bind('volumeUp','todo();')
void fully.bind('volumeDown','todo();')
void fully.bind('headphonesPlugged','todo();')
void fully.bind('headphonesUnplugged','todo();')
void fully.bind('onMotion','todo();') // Max. one per second
void fully.bind('facesDetected','todo($number);') // 1.48+
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");');
void fully.bind('onQrScanSuccess','todo("$code","$extras");');
void fully.bind('ttsInitSuccess','todo("$info");'); // ver. 1.55+

// Manage fully kiosk screensaver
void fully.startScreensaver()
void fully.stopScreensaver()
void fully.startDaydream()
void fully.stopDaydream()

// Manage fully kiosk app
boolean fully.isInForeground()
void fully.bringToForeground()
void fully.bringToForeground(long millis)   // Delay in ms
void fully.bringToBackground()
void fully.restartApp()
void fully.exit()

// Manage kiosk mode and maintenance mode
void fully.enableMaintenanceMode()
void fully.disableMaintenanceMode()
void fully.setMessageOverlay(String text)
void fully.lockKiosk()
void fully.unlockKiosk()
void fully.checkKioskPin()
boolean fully.isKioskLocked()

// Manage other apps and broadcasts
void fully.startApplication(String packageName)
void fully.startApplication(String packageName, String action, String url)  // Can put null to omit the parameter
void fully.startIntent(String url)
void fully.broadcastIntent(String url)
void fully.registerBroadcastReceiver(String action)
void fully.unregisterBroadcastReceiver(String action)
void fully.killBackgroundProcesses(String package) // Android 13 and older
void fully.installApkFile(String url)       // Not in Google Play Edition

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

// Look in Remote Admin settings for the settings keys
// Or export a JSON settings file and look there
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)

<!-- 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 -->
<button type="button" onclick="fully.scanQrCode('Prompt text','javascript:alert(\'$code\');');">Scan QR Code</button>

<!-- 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>

• Select Items to Show – Manage playlist: Select media URL, files, folders, web sites or YouTube videos/playlists to show. You can specify to loop each playlist item, skip item on user interaction, play next after x seconds. For folders you can also specify the file play order. Folders will be played recursively including all subfolders.
• Wallpaper URL – Website to show as wallpaper. You can use an URL like fully://color#000000 for a solid color page.
• Fade In/Out Duration – set image/video fade in/out duration in milliseconds (default: 100 ms).
• Image Scaling Type – how to resize the smaller/bigger pictures to the screen size (ver. 1.7+)
• Loop Playlist – start playing from beginning when end of playlist reached
• Show Throbber – show throbber while preparing image/video to play (can’t remove throbber for YouTube videos)
• Show Play Controls – show auto-hiding play controls when playing videos (no controls for YouTube videos)
• Show URL/Filename – show URL or filename when starting playing
• Show Errors – show error on media play failure
• Cache Images – enable caching of network images
• Video Player Engine – select MediaPlayer lib or Exoplayer lib to play videos, requires app restart (EXPERIMENTAL, 1.14+).

• Auto Restart on Idle – restart playlist after some seconds of user inactivity
• Auto Restart on Screen On – restart playlist when the screen goes on
• Auto Restart on Screensaver Stop – restart playlist when screensaver stops
• Auto Restart on Network Reconnect – restart when Wifi/LAN/LTE reconnects
• Auto Restart on Internet Reconnect – restart playlist when real internet connection reappears

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 web engine) 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 Webview s 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 some websites 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 quick settings and 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 , clicking on three dots in the right upper corner and selecting Allow restricted settings. This method isn’t reliable, on some Xiaomi, Redmi and Huawei devices, slow pulling the status bar will still open the quick settings and notification area.

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 not supported by the Webview . Check this FAQ for alternatives.

On modern Android devices usually you have following storage locations:

You can use the file picker in URL dialog boxes to pick the file from one of the available storage locations. The path to external SD card /storage/<storageId> will be saved in settings as /sd_ext and replaced by the real path on each device dynamically.

When accessing the device storage by ADB you will see the full paths as in the table above. When accessing by USB (like by Windows File Explorer) the Internal storage will be usually mapped to the /storage/emulated/0 folder and SDCARD will be mapped to /storage/<storageId>

Note that app-private and app-specific storage will be deleted if you uninstall the app. The shared storage however has serious restrictions. We recommend using app-specific storage for storing all local files needed for Fully Kiosk .

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:///path/to/file.html Note the triple slash!

Note that linking to or embedding local files from HTTP/HTTPS documents is disabled by Android Webview for security reasons. But you can use the Localhost File Access option in Advanced Web Settings in order to access local files using https://localhost/… address. The full URL for a local file should then look like https://localhost/path/to/file.mp4. So you will be able to embed 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. With Fully Kiosk Browser 1.57+ check this FAQ!

You can use the Load ZIP File button in Remote Admin and Fully Cloud to download and unpack a ZIP file to local device storage. By default the app-specific storage will be used to unpack files if the device is in scoped storage mode. Otherwise shared storage will be used. When using File Manager in Remote Admin you can unpack to any storage (with respect of access permissions).

In order to use this feature 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. For ZIP files up to 100 MB you can use the File Storage in Fully Cloud . If you need a bigger storage please use your own web 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

This is the way to make a light local content management. You can create subfolders within the ZIP file that will be used during extraction. Use with care as all existing files will be overwritten when unpacking the same file paths 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).

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. You can also 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 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.

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 11 Google/Android enforces a privacy concept called scoped storage. In short: Normal apps can’t access most of files on the device shared 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. Up to Fully Kiosk Browser 1.57, Fully Single App Kiosk 1.17 and Fully Video Kiosk 1.17 you could avoid these restrictions by installing our apps from APK files. After that you can only avoid restrictions by granting the App Files Access permission (not available if you installed from Google Play).  Check this FAQ for transition!

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, however not other files like HTML or PDF. Access to media files is also kind of unsafe if you install our app from Google Play. We recommend using app-specific storage for all files.
• The app also can’t change/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. 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 internal shared storage. 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.

Starting Fully Kiosk Browser 1.58, Fully Single App Kiosk 1.18 and Fully Video Kiosk 1.18 our kiosk apps will comply with the latest File Access Permissions Policy (2024). Our kiosk apps won’t have any access to the most files on the shared storage with Android 11+ devices. Check this FAQ to understand different storage types in Android. If you don’t use any local files  or your devices are running Android 10 and older you can directly upgrade to the versions above.

However, if you use local files we recommend installing Fully Kiosk Browser 1.57, Fully Single App Kiosk 1.17 or Fully Video Kiosk 1.17 that will examine the app settings. If there are any settings referring to the local files on the shared storage the app will show a Local Files Alert and give you different options.

Option 1. You can grant All Files Access (Manage All Files) permission to Fully Kiosk app. This can only be done on the device. (Remote Admin can however trigger the permission dialog shown on the device.) This option is only available if you installed our apps from APK file or device provisioning (not when installed from Google Play).

Option 2. Our app can migrate the affected files by copying them to the app-specific storage (/storage/emulated/0/Android/data/<appid>/files) and adjust the app settings accordingly.  You can check the affected files and start this migration from the app or by Remote Admin. You will find the detailed results logged in Remote Admin >> Fully Log.  Note that the app-specific storage can only be accessed by our app and will be removed if you uninstall our app. If you need file access by other apps (like when using a file sync app) then please use the Option 1.

Of course, our app can only find the files to migrate that are linked from some setting. If you want to add other folders to migration you can import a settings file like this.  You can also force the file migration without any user interaction (after testing it!) by importing this settings file.

After file migration please check all settings files and configurations in use and avoid re-importing (or better delete!) those using local files on shared storage.

The file migration has to be done prior to the next app upgrade to Fully Kiosk Browser 1.58, Fully Single App Kiosk 1.18 or Fully Video Kiosk 1.18!

Option 3. Never upgrade the app higher than Fully Kiosk Browser 1.56, Fully Single App Kiosk 1.16 and Fully Video Kiosk 1.15.

Option 4. Permanently ignore the local files alert by importing this settings file. But you should know what you are doing.

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 Brower 1.59 our apps can use motion detection when in background even if installed from Google Play. Please check you have the latest version installed.

Otherwise you have to install the APK files from our website in order the motion detection to work stable even if another app is in foreground or the screen is off.

Also check that the camera isn’t used by other apps or websites. Disable Face Unlock feature in your Android settings.

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 orders conducted by Paddle.com you will get an invoice automatically by email from Paddle.com. You can also find it in your Paddle customer portal.

For all completed PayPal payments 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.

EU companies can pay the Fully PLUS Volume License by bank transfer. Please get an invoice from here. After getting a quote please type your company name/address and click the link Get an Offer/Invoice for Bank Transfer Payment.

EU companies can pay Fully Cloud Subscription (20+ devices) by the bank transfer. Please ask us for invoice.

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, granted All Files Access permission 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. If you have ADB access to the device you can just uninstall the Fully Kiosk app by ADB.

adb dpm remove-active-admin [package]/de.ozerov.fully.DeviceOwnerReceiver
adb uninstall [package]

Please use for Fully Kiosk Browser de.ozerov.fully, for Fully Single App Kiosk com.fullykiosk.singleapp, for Fully Video Kiosk com.fullykiosk.videokiosk, for Fully Kiosk Browser EMM edition com.fullykiosk.emm as [package] in this command.

5. Otherwise the Factory Reset is the only way to reuse the device. Ask your device vendor how to perform a factory reset by pressing the hardware buttons of your 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). There are also ANR (application not responding) issues possible. Usually these issues are related to specific website and Android hardware combination.

1. The Android Webview can crash after some time or cause ANRs due to 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
• https://remoting2.fully-kiosk.com

For Fully PLUS license 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 EMM 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 https://youtube/video/[videoId] or https://youtube/playlist/[playlistId] (ver. 1.57+). Some YouTube videos however are restricted by the video owner and can’t play in other apps.
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 or when device is booting. For this reason, when starting other apps or rebooting a locked device the lock screen may be displayed. Unfortunately this is something impossible to change by our app.

In many cases we recommend to set Lock Screen in Android Settings to None as workaround to disable the screen lock completely. Unfortunately we can’t do it automatically from the Fully Kiosk app. On provisioned devices you can 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.

Hiding the Soft Keyboard

If your website has a focused field for barcode input the Webview will always show the virtual (soft) keyboard by default.

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. Or you can use an app like Null Keyboard to switch off the soft keyboard system wide.

You can disable keyboard for selected pages only 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 keyboard emulation mode (keystroke mode) and the Listen to Keyboard Input option not working with many scanner apps. We recommend using the broadcast mode to transmit the scan result as described above.

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 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 EMM 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/. Launcher Replacement
adb shell pm disable-user --user 0 com.google.android.tv launcher 

adb shell pm enable --user 0 com.google.android.tv launcher 
adb shell pm set-home-activity com.google.android.tv launcher /.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 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/. Launcher Replacement
adb shell pm disable-user --user 0 com.amazon.fire launcher 

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

2a. 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.

2b. At least some versions of Fire OS always killing the Webview which kills our app when the screen goes off. We have no fix for this. Use the Screensaver instead of Screen Off.

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. Users reported that you can deny internet access for your Fire OS device by the router as a better workaround.

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.