Android Enterprise enrollment asks for credentials and Remote View shows black screenSolved

For Android Enterprise enrollment using the 6-tap/7-tap method, the authentication prompt depends on the user authentication setting configured in the enrollment profile.

If the enrollment profile is set to Global Authentication, Hexnode applies the authentication configuration from Admin > Enrollment Settings. In that case, the device may prompt for credentials based on the global enrollment authentication settings.

For test enrollments, switching the enrollment profile to No Authentication can allow the device to enroll without entering a username and password. This matches the behavior you observed.

For the Remote View black screen, this is expected Android behavior. Android uses a security flag called FLAG_SECURE to prevent sensitive screens from being captured, recorded, or streamed. Screens such as password fields, PIN entry pages, Wi-Fi credential prompts, and certain protected app screens may appear black in Remote View. This is enforced by the Android operating system and is not specific to Hexnode.

So if it’s black only while typing passwords or changing Wi-Fi, that doesn’t mean Remote View is broken? I noticed it comes back after leaving that screen.

Correct. Remote View is functioning normally in that case. When the device is on a secure screen protected by FLAG_SECURE, Android blocks screen capture and the remote stream appears black. Once the user exits the protected field or moves away from the secure settings page, the Remote View session should resume automatically. This behavior is designed to protect passwords, Wi-Fi keys, and other sensitive information from being viewed remotely.

Can Hexnode disable FLAG_SECURE for managed Android Enterprise devices? We were hoping to use Remote View while entering credentials during setup.

No. FLAG_SECURE cannot be bypassed through Hexnode or any other MDM solution. It is an Android OS-level privacy restriction. MDM platforms do not have permission to override it, even when the device is fully managed through Android Enterprise. The practical workaround is to complete sensitive credential entry directly on the device. Remote View will continue normally after the secure input screen is closed.