Browse: Home / How to allow clock, Network and Battery status on Secure Launcher – Workspace One UEM (AirWatch)

Menu

Skip to content
  • Privacy Policy
  • Advertise with us
  • About Me
  • Home

WSO UEMLogo

VMware EUC Destination

Menu

Skip to content
  • Home
  • Digital Workspace/EUC
  • VMware Social Media Advocacy
  • Business Continuity with VMware Workspace ONE
  • Watch 44 Technical Breakout Sessions At Your Convenience
  • HCI as Virtual Desktop Infrastructure (VDI)
  • Enhance Chrome Management with the Workspace ONE UEM Extension
  • Top General Tools for WSOUEM Troubleshooting-Workspace One UEM (AirWatch)
  • You are not allowed to enroll your device. This device is registered to another user - Workspace One UEM (AirWatch)
  • How to allow clock, Network and Battery status on Secure Launcher - Workspace One UEM (AirWatch)
  • Enrollment Blocked - Workspace One UEM (AirWatch)
  • com.airwatch.lockdown.launcher blocked by the - Workspace One UEM (AirWatch)
  • Event Logs Overview - Workspace One UEM (AirWatch)
  • Files that make up a virtual machine (VM)
  • Workspace One UEM | How to renew an APNs Certificate?
  • 53 Top Free Tools for VMware Administrators

How to allow clock, Network and Battery status on Secure Launcher – Workspace One UEM (AirWatch)

Posted by Pratheesh K on July 23, 2019 in Workspace One UEM | 315 Views | Leave a response

In corporate-owned android devices with a secure launcher profile, you may come across an issue that the Status Bar at the top of the screen which includes a clock, battery status, and network status are missing. However, when you enter the admin passcode for the secure launcher you would be able to see the status bar.

Launcher 4.0 uses new native Android APIs for Google EMM Registered enrollments in the standard Android profile. These new APIs fall under the umbrella of Corporate-Owned Single-Use (COSU) mode. Some features are removed while using COSU mode, this is purposeful to be able to drastically increase the security of the Launcher application.

To resolve this issue, just disable the COSU (Corporate-Owned Single-Use) adding a custom XML profile on the secure launcher payload.

Tested device: Samsung note S series.
WSO UEM Console: 9.X 
Secure Launcher ver: 4.X 

In DO mode, COSU will be configured by default.

Just add that XML as a custom setting to your launcher profile.

<characteristic
type="com.airwatch.android.androidwork.launcher"
uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="SkipCosuSetup" value="True"/>
<parm name="AllowStatusBar" value="True" />
<parm name="AllowNotificationBar" value="True"/>
</characteristic> 

I hope this is informative for you. Thanks for Reading! Be Social and share it in social media, if you feel worth sharing it.

Posted in Workspace One UEM | Tagged Android, Secure Launcher, WSO UEM

Related Posts

Top General Tools for WSOUEM Troubleshooting-Workspace One UEM (AirWatch)→

You are not allowed to enroll your device. This device is registered to another user – Workspace One UEM (AirWatch)→

Enrollment Blocked – Workspace One UEM (AirWatch)→

com.airwatch.lockdown.launcher blocked by the – Workspace One UEM (AirWatch)→

DISCLAIMER

The postings on this site are my own and don’t necessarily represent my current or previous employer positions, strategies or opinions. It is solely my and ONLY my opinion.

Useful Tools

  1. DNS Propagation checker
  2. Port Forwarding Tester
  3. SSL Checker
  4. SSL Labs
  5. Java keystore GUI
  6. NMap
  7. Postman

Categories

 
 
 
 

Copyright © 2020 WSOUEM, Pratheesh K. All rights reserved.

Menu

  • Privacy Policy
  • Advertise with us