Excessive mobile data consumption on kiosk-mode tablets: Chrome foreground traffic from web app identified as primary cause

Android

If your kiosk-mode tablets are consuming excessive cellular data, the issue is often caused by web applications running continuously in Google Chrome. This guide helps you identify the cause and implement solutions.

Before you begin

This issue typically occurs when:

Devices run in kiosk mode with a web application displayed full-screen in Chrome
Devices connect via cellular data (SIM) rather than Wi-Fi
Web applications load continuously and remain active throughout operating hours
Devices stay powered on for extended periods

Step 1: Check which app is consuming data

Open the Esper Console and navigate to Devices & Groups
Select the affected device and go to Device Details
Look for a Data Usage section to see which applications are consuming the most data
Note whether Chrome or the web application is listed as the top consumer

Step 2: Obtain detailed data usage statistics

If the Esper Console data usage view doesn't provide enough detail, request a bug report from the device:

If the device is online: Go to Devices & Groups → [Device Name] → Actions → Request Bug Report
If you have on-site access: Use ADB to pull a bug report directly:
```
adb bugreport bugreport_output.zip
```

Once you have the bug report, look for per-app data usage breakdown in the netstats or dumpsys netstats sections.

Step 3: Investigate the web application

If Chrome is the primary data consumer, the issue likely stems from the web application content itself. Work with your web app vendor or your IT team to:

Check whether the web app serves video or animated media
Review whether the app uses auto-refreshing dashboards or high-frequency API polling
Audit assets for data-heavy content, such as uncompressed video loops

Step 4: Compare devices with different consumption patterns

If multiple devices run the same web app URL but show different data usage, the difference may be due to content variations served by the web app:

Compare a high-consumption device against a low-consumption device in the same group
Check whether the web app delivers different content variations (A/B testing, dynamic ads, etc.) to specific devices

Step 5: Reduce data consumption

Once you've identified the cause, consider these mitigation options:

Optimize web app content: Work with your web app vendor to reduce file sizes, compress media, or lower API polling frequency
Switch to Wi-Fi: If available, connect high-usage devices to Wi-Fi instead of cellular
Restrict Chrome background data: Navigate to Blueprint → App Permissions / Network Policy to restrict or cap background data for Chrome (if supported by your Android version)
Schedule device downtime: Configure devices to power off or dim the screen during non-operational hours to reduce active foreground rendering

Step 6: Verify the fix

After implementing changes, monitor data usage over the next 7 to 14 days:

Go to Devices & Groups → [Device Name] → Data Usage
Compare the new usage against your baseline from before the changes
Confirm that consumption has decreased to expected levels

Still need help?

If the data consumer is not Chrome or the web app, or if you're unable to identify the root cause, contact Esper Support. include your bug report and any data usage statistics you've collected.