- Basics
- About Knox
- Knox licenses
- Knox white paper
- Sign up for Samsung Knox
- Latest release notes
- General Knox FAQ
- General Knox KBAs
- Submit a support ticket
- User Acceptance Testing
- For IT admins
- Knox Admin Portal
- Knox Suite
- Knox Platform for Enterprise
- Knox Mobile Enrollment
- Knox Configure
- Mobile
- Introduction
- Get started
- Features
- License management
- Release notes
- Troubleshoot
- Wearables
- Shared Device
- FAQ
- KBAs
- Mobile
- Knox Capture
- Welcome
- Overview
- How-to guides
- Manage licenses
- Scanning profiles
- Apps and activities
- Scan engine settings
- Keystroke output and data formatting
- Export configuration and deploy through EMM
- Set the camera scan trigger
- Connect a hardware scanner
- Configure the output path
- Check a configuration in test mode
- Use intent output
- Knox Capture AR
- Get started
- How-to videos
- Release notes
- FAQ
- KBAs
- Troubleshoot
- Knox Capture: Scandit Edition
- Introduction
- How it works
- IT admins: Get started
- Getting started with Knox Capture
- Step 1: Launch Knox Capture
- Step 2: Create a scanning profile
- Step 3: Select apps and activities
- Step 4: Configure the scanner
- Step 5: Set keystroke output rules
- Step 6: Test apps in your configuration
- Step 7: Share your configuration
- Step 8: Deploy Knox Capture in Managed mode
- End users: Get started
- Features
- Knox Asset Intelligence
- Knox Manage
- Introduction
- How-to videos
- Get started
- Video: Getting started with Knox Manage
- Integration with Managed Service Provider
- Access Knox Manage
- Configure basic environments
- Create user accounts
- Create groups
- Create organization
- Set up devices and profiles
- Create a new profile
- Assign profiles to groups and organizations
- Enroll devices
- Shared Android device quickstart
- Non-shared Android device enrollment quickstart
- Android Management API device enrollment quickstart
- Apple User Enrollment quickstart
- View device information
- Apply profiles to organizations
- Set up Knox Manage deployment with a Knox Suite license
- Manage Chromebooks
- Manage Android devices with the Android Management API
- Manage Shared iPads
- Configure
- Licenses
- Organization
- Users
- Sync user information
- Groups
- Devices
- Content
- Applications
- Profile
- Knox E-FOTA
- Certificates
- Advanced settings
- Monitor
- Kiosk devices
- Knox Remote Support
- Active Directory
- Microsoft Exchange
- Mobile Admin
- Appendix
- Release notes
- Features
- FAQ
- KBAs
- Knox E-FOTA
- Introduction
- How-to videos
- Get started
- Features
- EMM integration
- Appendix
- Release notes
- FAQ
- KBAs
- Troubleshoot
- Knox E-FOTA On-Premises
- Legacy Knox E-FOTA products
- Knox Guard
- Samsung Care+ for Business
- For Knox Partners
- Knox Deployment Program
- Knox MSP Program
How to prevent a plugged-in Android device's screen from turning off
Environment
- Knox Manage Kiosk mode
- Android Enterprise enrollment type
- Devices running Android 6.0 and above
Overview
For deployments where devices may be permanently plugged in and charging, you may want to force the device screen to stay on.
Previously only available in Knox Configure, this knowledge base article shows you how to configure the Always on Display and Screen on when Plugged in policies to keep device screens on with Knox Manage.
NOTE — The Screen on when Plugged in policy is only available for devices running Kiosk mode.
How to keep the device screen on when plugged in and charging
To configure a profile to keep the device screen on:
- In your Knox Manage console, click Profile.
- Create or modify a profile with Android Enterprise set as the enrollment type.
-
Set the following policies in the Android Enterprise policy drawer:
- System > Always on Display — Allow
- Kiosk > Screen on when Plugged in — Apply
- Kiosk > Screen on when Plugged in > Screen On when Plugged into Charger — Select the desired charging methods.
- Click Save & Assign to assign the profile to a group or organization.
After the policy is enabled and the device is connected to a charger, the screen stays on until it is disconnected.
