Hi @mila_diaz. Welcome to the Hexnode Community.
For the location tracking notification, this is expected Android behavior. When a device is using background location services, Android requires a persistent system notification for privacy and transparency. If a Hexnode Location Tracking policy is active, Android may keep this notification visible while the background service is running.
There is no Hexnode portal setting to hide only this location tracking notification. Disabling Hexnode notifications from the device settings is not recommended because it can suppress all Hexnode-related notifications, including important prompts, alerts, and policy-related messages. Increasing the location update interval, such as changing it from every 1 hour to every 2 or 3 hours, can help reduce battery and data usage. However, it will not remove the persistent notification as long as background location tracking remains enabled.
For the Remote View black screen issue, the behavior you described is also expected on certain Android screens. Apps such as Microsoft Authenticator, banking apps, password screens, and some account setup flows often mark their windows as secure using Android’s FLAG_SECURE protection. When this flag is present, Android blocks screen capture, screen recording, and remote viewing tools from capturing that content.
On Android 15 and Android 16, this behavior is stricter and can also apply to lock screen PIN or password entry. You may be able to see the initial lock screen, but once the user swipes up and the PIN keypad appears, the remote session can turn black. This is enforced by Android at the operating system level. Hexnode Remote View, developer options, and screen sharing protection toggles cannot bypass FLAG_SECURE. The user must physically enter the PIN, password, or secure app credentials on the device.
Best Regards,
Isabel Lora
Hexnode UEM