Keyguard automatically disabled when kioskCustomLauncherEnabled is enabled

Andeo
Level 1.5: Cupcake

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

3 REPLIES 3

Andeo
Level 1.5: Cupcake

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
Level 4.0: Ice Cream Sandwich

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
Level 1.5: Cupcake

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: 

Andeo_0-1727077635640.png

 

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

Andeo_1-1727077831535.png

 

Is there maybe another input that you could give me?

 

Kind regards

 

Kol