11 docs tagged with "debugging"

Enabling native debug on Android-powered players and displays will allow you to access WebView console and capture logcat logs during development.

How to remotely debug Applets on devices using Weinre, enabled from the Box Troubleshooting tab to inspect DOM and console logs over websockets.

Overview of platform-specific Native Debug for Applets, activated via Box or REST API, with Chrome inspector steps for Tizen, webOS, Android, and more.

NOTE: Enabling native debug on Brightsign devices causes memory issues and may lead to out of memory errors, make sure that Native debug is turned off...

NOTE: Enabling native debug on ChromeOS devices causes memory issues and may lead to out of memory errors, make sure that Native debug is turned off...

Explains corner-pixel status indicators and Debug Mode icons that reveal device connection, authentication, verification, and Applet loading states on the display.

How to enable and use developer debug mode on LG webOS displays for signageOS troubleshooting.

How to debug a Linux signageOS device by enabling Native Debug in Box and connecting Chrome DevTools remotely via chrome://inspect on port 9992.

Native debug on RPi3 requires you to install Epiphany Browser (a.k.a. Gnome Web) on your PC.

Step-by-step guide for native debugging on Samsung Tizen 3.0+ (SSSP5 and above) displays using Developer mode.

How to debug Applets on Windows devices via Chrome inspector on port 9222, including legacy Kiosk-mode steps, password recovery, and troubleshooting tips.