23-01-2026
This commit is contained in:
parent
07959c0ba2
commit
854ce02bf6
166 changed files with 32909 additions and 1262 deletions
480
public/_cabinet/KIOSK_MODE_SETUP.md
Normal file
480
public/_cabinet/KIOSK_MODE_SETUP.md
Normal file
|
|
@ -0,0 +1,480 @@
|
|||
# Chrome Kiosk-Mode Setup für Android Digital Signage
|
||||
|
||||
## 🎯 Problem
|
||||
|
||||
Bei einem Page-Reload (z.B. nach 6h automatisch) wird der Vollbildmodus beendet - das ist eine Browser-Sicherheitsmaßnahme. Der Vollbildmodus kann nicht automatisch per Script reaktiviert werden.
|
||||
|
||||
## ✅ Die Lösung: Chrome Kiosk-Mode
|
||||
|
||||
Der **Kiosk-Mode** ist die professionelle Lösung für Digital Signage. Chrome läuft dabei permanent im Vollbild ohne Browser-UI.
|
||||
|
||||
---
|
||||
|
||||
## 📱 Option 1: Chrome Kiosk-Mode (Empfohlen für Android)
|
||||
|
||||
### Voraussetzungen:
|
||||
- Android-Gerät (Tablet/Display)
|
||||
- Chrome Browser installiert
|
||||
- ADB (Android Debug Bridge) für Setup
|
||||
|
||||
### Setup-Schritte:
|
||||
|
||||
#### 1. **Developer-Optionen aktivieren**
|
||||
|
||||
1. Gehe zu **Einstellungen** → **Über das Telefon/Tablet**
|
||||
2. Tippe **7x auf "Build-Nummer"**
|
||||
3. Developer-Optionen sind jetzt aktiv
|
||||
|
||||
#### 2. **USB-Debugging aktivieren**
|
||||
|
||||
1. Gehe zu **Einstellungen** → **Entwickleroptionen**
|
||||
2. Aktiviere **"USB-Debugging"**
|
||||
3. Verbinde Gerät per USB mit Computer
|
||||
|
||||
#### 3. **ADB installieren (auf Computer)**
|
||||
|
||||
**Windows:**
|
||||
```bash
|
||||
# Download Android Platform Tools
|
||||
https://developer.android.com/studio/releases/platform-tools
|
||||
|
||||
# Entpacken und zu PATH hinzufügen
|
||||
```
|
||||
|
||||
**macOS:**
|
||||
```bash
|
||||
brew install android-platform-tools
|
||||
```
|
||||
|
||||
**Linux:**
|
||||
```bash
|
||||
sudo apt install android-tools-adb
|
||||
```
|
||||
|
||||
#### 4. **Chrome im Kiosk-Mode starten**
|
||||
|
||||
```bash
|
||||
# Verbindung testen
|
||||
adb devices
|
||||
|
||||
# Chrome beenden
|
||||
adb shell am force-stop com.android.chrome
|
||||
|
||||
# Chrome im Kiosk-Mode starten
|
||||
adb shell am start \
|
||||
-n com.android.chrome/com.google.android.apps.chrome.Main \
|
||||
-a android.intent.action.VIEW \
|
||||
-d "https://cabinet.b2in.eu" \
|
||||
--ez create_new_tab true \
|
||||
--activity-clear-task \
|
||||
--activity-clear-top \
|
||||
--activity-single-top
|
||||
|
||||
# Optional: Vollbild erzwingen
|
||||
adb shell settings put global policy_control immersive.full=*
|
||||
```
|
||||
|
||||
#### 5. **Auto-Start beim Boot (Optional)**
|
||||
|
||||
Erstelle eine Boot-App oder nutze Automate-Apps:
|
||||
|
||||
**Mit MacroDroid (kostenlose App):**
|
||||
1. Installiere MacroDroid aus Play Store
|
||||
2. Erstelle Macro:
|
||||
- **Trigger:** "Device Boot"
|
||||
- **Action:** "Launch Application" → Chrome
|
||||
- **Action:** "Load Webpage" → https://cabinet.b2in.eu
|
||||
3. Speichern und aktivieren
|
||||
|
||||
---
|
||||
|
||||
## 📱 Option 2: Dedicated Kiosk-Browser Apps
|
||||
|
||||
### Empfohlene Apps für Android Digital Signage:
|
||||
|
||||
### **1. Fully Kiosk Browser** (⭐ Empfohlen)
|
||||
|
||||
**Features:**
|
||||
- ✅ Echter Kiosk-Modus (keine UI, kein Zurück-Button)
|
||||
- ✅ Auto-Start beim Boot
|
||||
- ✅ Remote-Management
|
||||
- ✅ Screensaver-Funktion
|
||||
- ✅ Keep Screen On
|
||||
- ✅ Remote-Config via Web-Interface
|
||||
|
||||
**Installation:**
|
||||
```
|
||||
1. Download: https://www.fully-kiosk.com
|
||||
2. Installiere APK auf Android
|
||||
3. Öffne App
|
||||
4. Settings:
|
||||
- Start URL: https://cabinet.b2in.eu
|
||||
- Kiosk Mode: ON
|
||||
- Launch on Boot: ON
|
||||
- Hide System UI: ON
|
||||
- Keep Screen On: ON
|
||||
- Reload on Network Restore: ON
|
||||
5. Lock App (Admin Pin setzen)
|
||||
```
|
||||
|
||||
**Kosten:**
|
||||
- Kostenlos für Single-Device
|
||||
- Plus Version: ~€20 (einmalig) für erweiterte Features
|
||||
|
||||
### **2. Kiosk Browser Lockdown**
|
||||
|
||||
**Features:**
|
||||
- ✅ Einfaches Setup
|
||||
- ✅ Kiosk-Mode
|
||||
- ✅ Auto-Start
|
||||
- ✅ Kostenlos
|
||||
|
||||
**Installation:**
|
||||
```
|
||||
1. Play Store: "Kiosk Browser Lockdown"
|
||||
2. URL setzen: https://cabinet.b2in.eu
|
||||
3. Kiosk Mode aktivieren
|
||||
4. PIN setzen
|
||||
```
|
||||
|
||||
### **3. Chrome mit Custom Launcher**
|
||||
|
||||
**Features:**
|
||||
- ✅ Nutzt Chrome Engine
|
||||
- ✅ Custom Launcher ersetzt Home-Screen
|
||||
- ✅ Kostenlos
|
||||
|
||||
**Apps:**
|
||||
- "Screen On" (Play Store)
|
||||
- "Stay Alive!" (Play Store)
|
||||
- "Screen Alive" (Play Store)
|
||||
|
||||
---
|
||||
|
||||
## 💻 Option 3: Chrome Flags (Desktop/Android)
|
||||
|
||||
### Für Desktop-Testing:
|
||||
|
||||
**Chrome starten mit Flags:**
|
||||
|
||||
**Windows:**
|
||||
```powershell
|
||||
"C:\Program Files\Google\Chrome\Application\chrome.exe" ^
|
||||
--kiosk "https://cabinet.b2in.eu" ^
|
||||
--disable-session-crashed-bubble ^
|
||||
--disable-infobars ^
|
||||
--noerrdialogs ^
|
||||
--disable-translate ^
|
||||
--no-first-run ^
|
||||
--fast-start ^
|
||||
--disable-features=TranslateUI ^
|
||||
--disk-cache-dir=NUL ^
|
||||
--overscroll-history-navigation=0
|
||||
```
|
||||
|
||||
**macOS:**
|
||||
```bash
|
||||
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome \
|
||||
--kiosk "https://cabinet.b2in.eu" \
|
||||
--disable-session-crashed-bubble \
|
||||
--disable-infobars \
|
||||
--noerrdialogs
|
||||
```
|
||||
|
||||
**Linux:**
|
||||
```bash
|
||||
google-chrome \
|
||||
--kiosk "https://cabinet.b2in.eu" \
|
||||
--disable-session-crashed-bubble \
|
||||
--disable-infobars \
|
||||
--noerrdialogs \
|
||||
--disable-translate \
|
||||
--no-first-run
|
||||
```
|
||||
|
||||
### Flags Erklärung:
|
||||
- `--kiosk` - Vollbild-Modus ohne UI
|
||||
- `--disable-session-crashed-bubble` - Keine "Chrome wurde nicht korrekt beendet" Meldung
|
||||
- `--disable-infobars` - Keine Info-Leisten
|
||||
- `--noerrdialogs` - Keine Error-Dialoge
|
||||
- `--disable-translate` - Keine Übersetzungs-Popups
|
||||
- `--no-first-run` - Kein First-Run-Dialog
|
||||
|
||||
---
|
||||
|
||||
## 🔧 Option 4: Unsere Fallback-Lösung (bereits implementiert)
|
||||
|
||||
### Was haben wir implementiert:
|
||||
|
||||
#### 1. **LocalStorage-Tracking**
|
||||
```javascript
|
||||
// Beim Aktivieren merken
|
||||
localStorage.setItem('cabinet_fullscreen_was_active', 'true');
|
||||
|
||||
// Nach Reload prüfen
|
||||
if (wasFullscreen) {
|
||||
// Auffälliger Reminder anzeigen
|
||||
}
|
||||
```
|
||||
|
||||
#### 2. **Visueller Reminder**
|
||||
- **Orange pulsierender Button** nach Reload
|
||||
- Text: "⚠️ Vollbild aktivieren!"
|
||||
- Automatisch sichtbar wenn Fullscreen vorher aktiv war
|
||||
|
||||
#### 3. **Auto-Retry (30s Delay)**
|
||||
```javascript
|
||||
// Nach 30s automatisch versuchen (falls Kiosk-Mode aktiv)
|
||||
setTimeout(() => {
|
||||
enterFullscreen(); // Wird ignoriert wenn keine User-Geste
|
||||
}, 30000);
|
||||
```
|
||||
|
||||
#### 4. **Logging**
|
||||
```javascript
|
||||
✅ "Fullscreen aktiviert"
|
||||
⚠️ "Fullscreen-Reminder angezeigt"
|
||||
ℹ️ "Fullscreen verlassen"
|
||||
```
|
||||
|
||||
### Vorteile:
|
||||
- ✅ Funktioniert ohne zusätzliche Apps
|
||||
- ✅ Visueller Hinweis dass Fullscreen reaktiviert werden muss
|
||||
- ✅ Nutzer wird "erinnert" nach Reload
|
||||
- ✅ Logging für Monitoring
|
||||
|
||||
### Nachteile:
|
||||
- ❌ Erfordert manuellen Klick nach Reload
|
||||
- ❌ Nicht vollautomatisch
|
||||
|
||||
---
|
||||
|
||||
## 🎯 Empfohlenes Setup für Production
|
||||
|
||||
### Für Android Digital Signage Displays:
|
||||
|
||||
#### **Best Practice:**
|
||||
|
||||
```
|
||||
1. Hardware: Android Tablet/Display
|
||||
└─ Empfohlen: Android 9+ mit min 2GB RAM
|
||||
|
||||
2. Software: Fully Kiosk Browser (Plus)
|
||||
├─ Start URL: https://cabinet.b2in.eu
|
||||
├─ Kiosk Mode: ON
|
||||
├─ Launch on Boot: ON
|
||||
├─ Hide System UI: ON
|
||||
├─ Keep Screen On: ON
|
||||
├─ Reload on Network Restore: ON
|
||||
└─ Remote Management: ON
|
||||
|
||||
3. Network: Kabelgebunden (LAN)
|
||||
└─ Fallback: 5GHz WiFi mit statischer IP
|
||||
|
||||
4. Power: USV/Surge Protection
|
||||
└─ Auto Power-On nach Stromausfall
|
||||
|
||||
5. Monitoring:
|
||||
├─ Fully Kiosk Remote Admin
|
||||
└─ Unsere Logs: view-logs.php
|
||||
```
|
||||
|
||||
### Setup-Checklist:
|
||||
|
||||
- [ ] Android-Gerät vorbereitet
|
||||
- [ ] Fully Kiosk Browser installiert
|
||||
- [ ] Kiosk-Mode konfiguriert
|
||||
- [ ] Auto-Start aktiviert
|
||||
- [ ] System-UI versteckt
|
||||
- [ ] Keep-Screen-On aktiviert
|
||||
- [ ] Remote-Management aktiviert (Optional)
|
||||
- [ ] PIN-Schutz gesetzt
|
||||
- [ ] Display-Helligkeit eingestellt
|
||||
- [ ] Netzwerk getestet (LAN bevorzugt)
|
||||
- [ ] Power-Management konfiguriert
|
||||
- [ ] Test-Lauf 24h durchgeführt
|
||||
- [ ] Monitoring aktiv (Logs checken)
|
||||
|
||||
---
|
||||
|
||||
## 🔍 Troubleshooting
|
||||
|
||||
### Problem: Kiosk-Mode wird nicht aktiviert
|
||||
|
||||
**Lösung 1: Developer-Optionen**
|
||||
```
|
||||
Settings → Developer Options → "Stay Awake" ON
|
||||
```
|
||||
|
||||
**Lösung 2: App-Berechtigungen**
|
||||
```
|
||||
Settings → Apps → Fully Kiosk → Permissions
|
||||
- Display over other apps: ALLOW
|
||||
- Auto-start: ALLOW
|
||||
```
|
||||
|
||||
**Lösung 3: Device Admin**
|
||||
```
|
||||
Settings → Security → Device Administrators
|
||||
- Fully Kiosk Browser: ENABLE
|
||||
```
|
||||
|
||||
### Problem: Display schaltet sich ab
|
||||
|
||||
**Lösung:**
|
||||
```
|
||||
1. Fully Kiosk Settings:
|
||||
- Keep Screen On: ON
|
||||
- Screen Saver: OFF
|
||||
- Prevent Sleep: ON
|
||||
|
||||
2. Android Settings:
|
||||
- Display → Sleep: NEVER
|
||||
- Display → Adaptive Brightness: OFF
|
||||
```
|
||||
|
||||
### Problem: Chrome Exit nach Reload
|
||||
|
||||
**Lösung:**
|
||||
```
|
||||
Nutze Fully Kiosk Browser statt Chrome!
|
||||
- Fully ist speziell für Kiosk designed
|
||||
- Kein ungewolltes Exit möglich
|
||||
- Automatischer Neustart bei Crash
|
||||
```
|
||||
|
||||
### Problem: Zurück-Button verlässt App
|
||||
|
||||
**Lösung:**
|
||||
```
|
||||
Fully Kiosk Settings:
|
||||
- Disable Back Button: ON
|
||||
- Disable Home Button: ON (Device Admin nötig)
|
||||
- Kiosk Mode: Advanced
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 📊 Vergleich der Optionen
|
||||
|
||||
| Option | Kosten | Komplexität | Zuverlässigkeit | Empfehlung |
|
||||
|--------|--------|-------------|-----------------|------------|
|
||||
| **Fully Kiosk** | €20 | ⭐⭐ | ⭐⭐⭐⭐⭐ | 🥇 **BEST** |
|
||||
| **Chrome Kiosk (ADB)** | Kostenlos | ⭐⭐⭐⭐ | ⭐⭐⭐ | OK für Tech-Versierte |
|
||||
| **Kiosk Browser Free** | Kostenlos | ⭐⭐ | ⭐⭐⭐ | OK für Testing |
|
||||
| **Unsere Fallback-Lösung** | Kostenlos | ⭐ | ⭐⭐ | Fallback |
|
||||
| **Chrome + Custom Launcher** | Kostenlos | ⭐⭐⭐ | ⭐⭐⭐ | Mittel |
|
||||
|
||||
---
|
||||
|
||||
## 🎬 Quick Start: Fully Kiosk (Empfohlen)
|
||||
|
||||
### 5-Minuten-Setup:
|
||||
|
||||
```bash
|
||||
1. Download: https://www.fully-kiosk.com
|
||||
└─ APK auf Android-Gerät installieren
|
||||
|
||||
2. App öffnen → Settings:
|
||||
Start URL: https://cabinet.b2in.eu
|
||||
|
||||
3. Advanced Settings:
|
||||
[x] Kiosk Mode
|
||||
[x] Launch on Boot
|
||||
[x] Hide System UI
|
||||
[x] Keep Screen On
|
||||
[x] Prevent Sleep
|
||||
|
||||
4. Lock Settings (+ Button):
|
||||
└─ PIN setzen (z.B. 1234)
|
||||
|
||||
5. ✅ Fertig! Display läuft 24/7 im Kiosk-Mode
|
||||
```
|
||||
|
||||
### Remote-Management aktivieren:
|
||||
|
||||
```
|
||||
1. Settings → Remote Administration:
|
||||
[x] Enable Remote Administration
|
||||
[x] Remote Admin from Local Network
|
||||
|
||||
2. Notiere IP-Adresse:
|
||||
z.B. http://192.168.1.100:2323
|
||||
|
||||
3. Öffne vom PC:
|
||||
http://192.168.1.100:2323
|
||||
└─ Password: (Dein PIN)
|
||||
|
||||
4. ✅ Remote-Control aktiv!
|
||||
- Screenshots
|
||||
- Reload
|
||||
- Settings ändern
|
||||
- Screen On/Off
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 💡 Pro-Tipps
|
||||
|
||||
### 1. **Netzwerk-Stabilität**
|
||||
```
|
||||
- LAN bevorzugen (kein WiFi)
|
||||
- Statische IP vergeben
|
||||
- Router/Switch mit QoS
|
||||
- Fully Kiosk: "Reload on Network Restore" ON
|
||||
```
|
||||
|
||||
### 2. **Power-Management**
|
||||
```
|
||||
- USV verwenden
|
||||
- BIOS: "AC Power Recovery" → ON
|
||||
- Android: "Auto Power On" → ON
|
||||
- Fully Kiosk: "Restart on Crash" → ON
|
||||
```
|
||||
|
||||
### 3. **Display-Pflege**
|
||||
```
|
||||
- Bildschirmschoner nach 22:00 Uhr
|
||||
- Helligkeit reduzieren nachts
|
||||
- Pixel-Shift aktivieren (gegen Burn-In)
|
||||
- Display-Timeout: NEVER
|
||||
```
|
||||
|
||||
### 4. **Monitoring**
|
||||
```
|
||||
- Fully Kiosk Remote Admin
|
||||
- Unsere Logs: view-logs.php
|
||||
- Ping-Monitoring (Nagios/Zabbix)
|
||||
- Wöchentliche Checks
|
||||
```
|
||||
|
||||
### 5. **Security**
|
||||
```
|
||||
- Fully Kiosk mit PIN schützen
|
||||
- Device Administrator aktivieren
|
||||
- USB-Debugging OFF (nach Setup)
|
||||
- Unknown Sources OFF
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 📞 Support
|
||||
|
||||
### Fully Kiosk Support:
|
||||
- Website: https://www.fully-kiosk.com
|
||||
- Forum: https://www.fully-kiosk.com/forum
|
||||
- Email: support@fully-kiosk.com
|
||||
|
||||
### Unsere Logs:
|
||||
- URL: https://cabinet.b2in.eu/view-logs.php
|
||||
- Check: Fullscreen-Events
|
||||
- Monitor: Memory & Errors
|
||||
|
||||
---
|
||||
|
||||
**Empfehlung:** Investiere die €20 für **Fully Kiosk Browser Plus** - es spart viele Stunden Troubleshooting und ist die stabilste Lösung für Digital Signage! 🎯
|
||||
|
||||
---
|
||||
|
||||
**Last Update:** 2026-01-19
|
||||
**Version:** 1.3
|
||||
Loading…
Add table
Add a link
Reference in a new issue