Robert Craig
Jul 07, 2018
4:42 pm

Kiosk Mode while using shared user id.

I've been successful in receiving the ACTION_ENABLE_KIOSK_MODE_RESULT broadcast when I attempt to enable kiosk mode via the *enableKioskMode("com.foo.test")* api. However, when I declare a shared user id for my app I seem to no longer receiver the broadcast even though all the other code remains unchanged. Is there something I'm missing to receiving the broadcast when using a shared user id with my app?

Device: Galaxy S8+

Knox Version 3.0

Knox API level 24

 

Similar topics

No similar topics found.
Robert Craig
Jul 17, 2018
7:22 pm

To follow up on this, I went ahead and downloaded the sample Kiosk app provided by Samsung at https://seap.samsung.com/sample-app/kiosk-mode-0  and was successfully able to enable kiosk mode. There was also a clear indication that the ACTION_ENABLE_KIOSK_MODE_RESULT broadcast was received because the subsequent toast message was displayed that showed kiosk mode was succcessfully enabled ("Activated Kiosk Mode successfully").

When I add android:sharedUserId="blah.blah" to the app's manifest I no longer receive the broadcast as well as no longer see a toast message being displayed. Oddly enough, Kiosk mode is definetly being enabled because my launcher (home) app has changed. 

What is the recommended path forward with this? I have a deployment scenario where I need to use sharedUserId as well as kiosk mode. Is this a bug or am I missing something obvious?

Robert Craig
Sep 25, 2018
11:46 am

Is it possible to decalre my app as using a sharedUserId and still receive the proper broadcast when enabling Kiosk mode? As referenced above I'm still unable to receive the expected broadcast. When the sharedUserId tag is dropped from my manifest however I receive the expected system broadcast. Any ideas?

Jay H.Samsung SEAP Moderator
Oct 04, 2018
6:24 am

Hi Robert,

To clarify, are you saying that when you add sharedUserId in your manifest file, you're not receiving the broadcast message but still able to enter the Kiosk mode? Are you then noticing any difference in behaviour (such as exiting kiosk mode)?

 

Regards,

Jay

Comments

Hi Jay,

Thanks for the reply and yes your synopsis of the problem is correct. Just to summarize as well as answer your follow up question, when I add the sharedUserId to my manifest and I attempt to enable kiosk mode I do not receive the expected broadcast message yet my device does successfully enter Kiosk mode. Likewise,  when I subsequently disable Kiosk mode I do not receive the expected broadcast message yet the device successfully exits Kiosk mode. All other funtionality and behaviors work as expected though. Meaning, disabling of hardware keys, status bar, etc. work as far as I can tell. Then, when I take out the sharedUserId from my manifest, while not changing anything else in the code, I do receive the expected system broadcast message. As you can imagine, to account for this, our custom app has to do some weird logic checks. 

I also tested this all using the sample app provided by you guys at the link shown above. I also tested these results on the newer S9+ and got the same results as those I've described. The S9+ I have is running Knox 3.1 with Knox api level 25.

Thanks,

Robert

Robert CraigOct 17, 2018 at 2:46 pm
Robert Craig
Oct 04, 2018
10:27 am

Hi Jay,

Thanks for the reply and yes your synopsis of the problem is correct. Just to summarize as well as answer your follow up question, when I add the sharedUserId to my manifest and I attempt to enable kiosk mode I do not receive the expected broadcast message yet my device does successfully enter Kiosk mode. Likewise,  when I subsequently disable Kiosk mode I do not receive the expected broadcast message yet the device successfully exits Kiosk mode. All other funtionality and behaviors work as expected though. Meaning, disabling of hardware keys, status bar, etc. work as far as I can tell. Then, when I take out the sharedUserId from my manifest, while not changing anything else in the code, I do receive the expected system broadcast message. As you can imagine, to account for this, our custom app has to do some weird logic checks. 

I also tested this all using the sample app provided by you guys at the link shown above. I also tested these results on the newer S9+ and got the same results as those I've described. The S9+ I have is running Knox 3.1 with Knox api level 25.

Thanks,

Robert