Can't leave kiosk mode with admin password

Can't leave kiosk mode with admin password

Hello,

I am testing the kiosk mode for an android terminal +, everything seems to work well apart from one thing.

I can not leave the kiosk mode from the terminal.
Let me explain, when I'm on my kiosk I keep pressing the return key and type my password, the kiosk is unlocked but 3 or 4 seconds later the kiosk mode relaunches itself.

Could you help me? below my version of mobicontrol and android +

 

Spec:

Mobicontrol-config Android-Config

 

6 Answers

Order By:   Standard | Newest | Votes
HKMOD@SOTI | posted this 17 September 2019

Hello Teddy,

 

Can you please try sending the script "notify kiosk off" and check, if it still go back to user mode? 

 

Kind Regards, Technical Support | SOTI Inc. |1.905.624.9828 | support@soti.net | www.soti.net |

  • 0
  • 0
teddy | posted this 18 September 2019

Hello HKMOD@SOTI?

I already tried to send the script "notify kiosk of" and it works.
But by doing this we are forced to have access to the console soti and we want to have the opportunity to do without.

  • 0
  • 0
HKMOD@SOTI | posted this 18 September 2019

Hello Teddy,

Thank you for your response.

I would suggest you to create an Support Ticket, we might need to check the device logs for further troubleshooting.

 

 

Kind Regards, Technical Support | SOTI Inc. |1.905.624.9828 | support@soti.net | www.soti.net |

  • 0
  • 0
Edgar Gomez | posted this 19 September 2019

Hello,

I've seen that exactly lately. 

For Android Enterprise that happened to us when we checked the Activity Suppression option in advance settings of Lockdown. Leaving that option unchecked solved the problem in that case.

 

 

I hope you can post your solution when you get it.

  • 0
  • 0
teddy | posted this 08 October 2019

Hello everybody

The problem is due to adding chrome in the application blacklist. actually after removing chrome from the blacklist the problem disappears. as we are in kiosk mode the blacklist is not necessary.

  • 0
  • 0
Matt Dermody | posted this 09 October 2019

That could possibly have something to do with the fact that the lockdown itself is effectively a webview that could be powered by the same WebView as Chrome depending on the version of Android. In Blacklisting Chrome you may have ended up in some strange state where the lockdown couldn't properly run. Just a theory. 

  • 0
  • 0

Give us your feedback
Give us your feedback
Feedback