- Basics
- The Knox Ecosystem
- White Paper
- Samsung Knox Portal
- Knox Cloud Services
- General Knox Support
- Knox Licenses
- For IT admins
- Knox Admin Portal
- Knox Suite
- Knox Platform for Enterprise
- Introduction
- How-to videos
- Before you begin
- Get started with UEMs
- Introduction
- Blackberry UEM
- Citrix Endpoint Management
- FAMOC
- IBM MaaS360
- Microsoft Intune
- MobileIron Cloud
- MobileIron Core
- Samsung Knox Manage
- SOTI MobiControl
- VMware Workspace ONE UEM
- Knox Service Plugin
- Release notes
- Migrate to Android 11
- FAQs
- Troubleshoot
- KBAs
- Knox Mobile Enrollment
- Knox Configure
- Mobile
- Wearables
- Shared Device
- FAQ
- KBAs
- Knox Capture
- Introduction
- How it works
- How-to videos
- 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
- Release notes
- FAQ
- KBAs
- Troubleshoot
- 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
- 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
- Introduction
- How-to video
- Get started
- Using Knox Guard
- Dashboard
- Manage devices
- Device management
- Accept or reject devices
- Upload devices
- Delete devices
- Complete device management
- Send notifications
- Enable or disable SIM control
- Download devices as CSV
- View device log
- View device deletion log
- Start and stop blinking reminder
- Lock and unlock devices
- Update lock message
- Send relock timestamp
- Turn on/off relock reminder
- Manage policies
- Manage licenses
- Manage resellers
- Manage admins and roles
- Activity log
- Knox Deployment App
- Release notes
- FAQ
- KBAs
- Support
- Samsung Care+ for Business
- For Knox Partners
- Knox Deployment Program
- Knox MSP Program
Debug mode
We understand that successfully deploying your policies and settings correctly is important. To help you test and deploy your configurations, Knox Service Plugin (KSP) includes a setting called Debug mode.
Overview
By default, KSP runs in the background and does not have a UI. Debug mode enables you to easily see policy results and errors on a device, so you can verify that your configurations are correct. When turned on, it launches an app that displays the status of policies. This app should auto-launch when it receives any new polices.
Here's what debug mode looks like when opened manually on a device:
The app provides a list of the polices that you have pushed, along with details about the last configuration, including:
- Policy title — Name of the policy.
- Message — Description of the policy, along with the status of the policy application.
Activate Debug mode
Debug mode is activated inside your UEM console, in the Knox Service Plugin configuration area. The location and appearance of the Debug mode feature in your UEM console may vary depending upon your UEM UI. Here is an example of how it may look:
Once you activate debug mode within your UEM, the next time policy changes are pushed to a device, the KSP app opens on the device. For example, if you are trying to debug the Enable fingerprint authentication feature, follow these steps in your UEM:
- Turn on the Debug mode flag.
- Expand Device-wide policies, and set Enable device policy controls to True.
- Under Password Policy > Biometric authentication, configure the Enable fingerprint authentication policy.
- Push the policies to a device.
-
Check the KSP app for debug information. If, for any reason, the app does not launch:
- Confirm that the device is using the latest Google Play services and Play client application.
- Confirm that the UEM has pushed the appropriate policies to the device. Some UEMs have a delay between the time a policy is saved on the console and when it is received by the device. You may have to open the UEM agent on the device and perform a manual refresh to receive the policy. Refer to your UEM's instructions for more information.
Debug mode features
You can perform the following actions when Debug mode is activated:
-
To apply any updated policies, tap Apply Latest Policies.
NOTE — If the policy updates aren't applied when you tap Apply Latest Policies, try again in a few minutes. It can take a short time for updated policies to be pushed from your UEM to devices. -
When you first open the app, it only shows the most recent pushed configuration. Tap this configuration to display the list of configuration results.
-
You can tap Configuration results and then tap Policies received to see the policies in JSON format.
-
To get a log of the current configurations, tap
(Details) > Export results.
Contact Support and provide debug files
In some cases, you may want to contact Support for help with a KSP issue. If you do, you need to provide the following files for investigation:
- ConfigurationResults_<timestamp>.txt
- ReceivedPolicies_<timestamp>.txt
- dumpstate log file
To obtain these files for upload:
- After enabling debug mode as described in the previous sections, open the KSP app.
- Tap the latest configuration.
- Tap
(Details) > Export results.
- Tap Save to save the KSP configuration results file to your Internal storage > Download folder.
- Repeat steps 3 and 4, this time tapping Export policies received, to export and save the KSP received policies file.
-
See Dumpstate logs (phone) for instructions on saving your device's dumpstate log file. Skip steps 2–5 in that procedure.
NOTE — Save the dumpstate log file soon after your issue occurs. If too much time passes, the relevant activity might no longer be contained in the log file. - Upload these three files to your support ticket.