Go to file
Anthony Callegaro 4ddd274cc7 Attempt at autoplaying videos
- Upgrade XWalk to 22
 - Try to disable requirement for user gesture to play media on the
 Webview in different part of the code
2016-11-03 23:49:20 +01:00
certificates ssl: add a note about PKCS#12 password 2015-12-20 21:38:42 +01:00
gradle/wrapper build: use gradle wrapper 2015-01-23 22:16:50 +01:00
res prefs: add "2 minutes" and "5 minutes" as possible timeouts 2016-11-03 07:42:41 +01:00
src/com/deezer/android/dashkiosk Attempt at autoplaying videos 2016-11-03 23:49:20 +01:00
.gitignore android: replace build system with gradle 2015-01-23 21:03:21 +01:00
.travis.yml travis: don't specify components to use 2015-01-23 23:57:51 +01:00
AndroidManifest.xml Attempt at autoplaying videos 2016-11-03 23:49:20 +01:00
build.gradle Attempt at autoplaying videos 2016-11-03 23:49:20 +01:00
gradlew build: use gradle wrapper 2015-01-23 22:16:50 +01:00
gradlew.bat build: use gradle wrapper 2015-01-23 22:16:50 +01:00
README.md doc: explain how to download missing Android components 2015-12-21 09:40:25 +01:00

This repository contains the Android application to be used with Dashkiosk. Its documentation is on ReadTheDocs.


This project uses Gradle. To compile, just use:

./gradlew assemble

To just build a debug APK, use:

./gradlew assembleDebug

The above commands will download a SDK if one is not found. However, currently, they fail to download some dependencies. You can download them manually with:

android update sdk --no-ui --all \
                   --filter extra-android-support,extra-android-m2repository

The embedded certificates are just here as an exemple. Only the client certificate (along with the key) will be bundled in the application. Since the CA shouldn't be used anywhere, it shoudn't be a security risk. But you can remove the symbolic link in res/raw. Have a look at certificates/generate script to understand how those certificates were generated.

Currently, ensure that you store only one keypair in the keystore. The Android application will always use the first certificate.

About Dashkiosk

Dashkiosk is a solution to manage dashboards on multiple screens. It comes as four components:

  1. A receiver runs in a browser attached to each screen and will display the requested dashboards. The receiver is quite dumb, it contacts the server and wait for it to tell which URL to display.

  2. A server which will manage the screens by sending them what they should display. An administration interface allows the user to manage those screens individually or in a group.

  3. An Android app that will run the receiver. This is mainly a fullscreen webview built on top of Crosswalk to get access to an up-to-date browser engine.

  4. A Chromecast custom receiver which will run the regular receiver if you want to display dashboards using Google Chromecast devices.

Limitations and non-limitations

The Dashkiosk application for Android has a few perks, notably the support of WebGL and decent performance, thanks to the accelerated webview.

However, here are a few limitations:

  • inability to login through a web form
  • inability to preset a cookie (this could be a workaround for the limitation above and this should not be too complicated to do, open an issue if needed)
  • inability to use several client certificates, see XWALK-6025)