Forum Discussion

Andeo's avatar
Andeo
Level 1.5: Cupcake
6 months ago

Keyguard automatically disabled when kioskCustomLauncherEnabled is enabled

Hey guys

 

The title says it all. I want my customers to be able to see their device name on the lock screen, when using the kiosk custom launcher.

Our customers can only see the device name when they restart the phone. If they lock the phone normally, it doesn't activate the keyguard.

 

Is there a possibility to have this fixed?

 

Regards

  • Andeo's avatar
    Andeo
    Level 1.5: Cupcake
    6 months ago

    can a supporter please give us an update to this post?

     

    it doesn't make any sense that the user has to unlock the phone with a pin only once, and doesn't get asked again until the phone is restarted because of the keyguard that is disabled

  • Moombas's avatar
    Moombas
    Level 4.1: Jelly Bean
    5 months ago

    I dont use a custom launcher but for me it very sounds like launcher dependent.

    Does the launcher maybe need something to send the relevant "lock" commands to the device and that part is maybe broken or so?

    Does the launcher work on a non managed device as expected?

  • Andeo's avatar
    Andeo
    Level 1.5: Cupcake
    5 months ago

    Hey Moombas 

     

    Thanks for the answer.

     

    When the kioskCustomLauncherEnabled flag is set to true then the DevicePolicy on the phone automatically sets the Home-Launcher to "Device Policy" (it's the home-launcher that is automatically provided by the Device-Policy, if kioskCustomLauncherEnabled  is set to true). I can't really test this on a non-managed device, because this home-launcher activity is set by the Device Policy. Do you know if I can test this on a non-managed device? 

     

    This is how the home-launcher looks like and it's automatically set by the Device Policy: 

     

    The standard-app is actually set to "Device Policy"

     

    Is there maybe another input that you could give me?

     

    Kind regards

     

    Kol