Eingeschränkter Support in der Zeit vom 22.Dez bis 05. Jan 2014
In der Zeit vom 21.12.15 bis 03.01.16 arbeitet unser Büro in Münster mit einer Minimalbesetzung. Bitte haben Sie Verständnis dafür, wenn Bestellungen und die Beantwortung von Supportanfragen in dieser Zeit länger dauern, als Sie es von uns gewohnt sind. In vielen Fällen hilft auch unser Support-Center weiter....
Wir wünschen Ihnen und Ihren Familien ein frohes Weihnachtsfest, sowie einen guten Rutsch ins neue Jahr.


Support Anfrage: Dimming of screen on inactivity



We have an Android app (real time video chat for the health market) which currently runs in kiosk mode (we wrote the app for kiosk mode with a separate kiosk mode loader app and load the main app as an apk during device configuration) but we are moving to a browser based experience.

One feature that we have on our kiosk is that the screen goes down to 1% brightness after some number of minutes of inactivity. For our target demographic, we don't want the device to fully shut down as we want the user to know that they can just touch the screen and it comes back to full brightness and they click to call.

So, my question is whether it is possible to set the brightness through your software when running on Android in Chrome.

Related to this is that i do not want the screen to go back to the sitekiosk page (i.e., it needs to stay on the browser open page) - and maybe this happens when i upgrade to the paid version? Also, it is not clear based on some initial testing that the local storage of the browser is maintained across sessions (i.e., each time that i go from the sitekiosk page to the browser page which it is locked down to, it seems that the local storage is reset), if someone could confirm this is the case, it would be greatly appreciated. Also, are there any restrictions on sitekiosk that would impact the usage of webrtc? I assume push notifications to the browser are supported - any limitations on this beyond the limitations of Android?

I am sure that i will have further questions as we evaluate whether we should rework our current kioskmode app to adapt to the browser or leverage your product if it can do what we need.


Mobile: 856-313-4049

Antwort: (1)

Re: Dimming of screen on inactivity 06.07.2020 16:07

Thank you for your inquiry. Regarding the dimming of the screen, currently there is no SiteKiosk setting that dims the screen after a few minutes of inactivity. But that feature is planned for the next SiteKiosk Android version 3.There is no release date for that version but it is planned for the latter part of 2020.

Your alternative to this based on the descriptions you gave, can be found in "-->Screensaver-->Define actions", uncheck "Start application" and check "Restart main application".

In general, SiteKiosk is designed as a kiosk browser and is used to delete all browser content from a previous session. By default SiteKiosk deletes the browser data when you press the Logout button in the SiteKiosk browser (only visible if you have selected the "Browser" under "-->Application") and when the screen saver activates.

Which data are deleted is configured at “-->Security-->Logout”.

At “-->Screensaver-->Time to activation”, you can set the idle time.

At “-->Screensaver-->Define actions”, you can configure what happens when the idle time has been reached.

For example, if you use the Browser/Fullscreen Browser to display a certain URL and enable “Logout” and “Restart main application” but just leave “Start application” deactivated, the SiteKiosk Browser deletes all browser data and returns to the start page URL after the idle time has been reached.

With the unlicensed version, you can already test all features included in SiteKiosk Android.

WebRTC works in general, see for example this WebRTC test page on Github:
At “-->Security-->Media resources access”, you can configure what happens when a web page tries to access the camera and/or microphone (default setting is “Ask”).

Push notifications are not supported in SiteKiosk Android because the notification area of Android is blocked (to block the access to the Android system). But you may use an overlay or other web techniques instead.

General notes:
By default the Site Kiosk Browser on Android does use the so-called WebView Framework http://developer.android.com/guide/webapps/webview.html that is based on the pre-installed browser of Android. Your test results with the “Standard Browser” in SiteKiosk depends on the Android version with the integrated system browser.

These are the browser engine versions used by WebView on Android:
- pre Android 4.4 -->uses the WebKit Engine (Updates with operating system)
- Android 4.4 --> Chromium Engine 30/33 (Updates with operating system)
- Android 5+ --> Chromium Engine 36+ (Updates via Play Store - Android System Webview)
- Android 7+ --> Chromium Engine 51+ (Updates via Play Store - Chrome)

Best regards,