Kiosk mode | Developer Portal

Please Register or Login to post a reply

5 Replies

d daron rice 5 years 6 months ago

just send version information along with source code

E Efkan YILMAZ 5 years 6 months ago

Hey Daron,
     I believe I found the issue, It looks as though we have a bug in the EHS documentation sample.  The sample should be the following.  Notice the "i" in intent should be lowercase in the putExtra call. I modified that line in the code you sent me,and it now works as expected. I will update the documentation with this fix.

Intent intent = new Intent("com.symbol.enterprisehomescreen.actions.MODIFY_KIOSK_MODE"); intent.putExtra("enable",false); sendBroadcast(intent);

d daron rice 5 years 6 months ago

my issue is that it will not exist kiosk mode...here is my code

C#:

     disableButton.Click += delegate
            {
                Intent intent = new Intent("enterprisehomescreen.MODIFY_KIOSK_MODE");
                intent.PutExtra("enable", false); // False to turn it off
                SendBroadcast(intent);
           
                Intent myintent = new Intent();
                myintent.SetClassName("com.motorolasolutions.enterprisehomescreen", "com.motorolasolutions.enterprisehomescreen.HomeScreenActivity");
                StartActivity(myintent);

                statusBox.Text = "Disabling....Disabled";
            };

manifest:

here is the exception i am getting:

Android.Content.ActivityNotFoundException: Unable to find explicit activity class {com.motorolasolutions.enterprisehomescreen/com.motorolasolutions.enterprisehomescreen.HomeScreenActivity}; have you declared this activity in your AndroidManifest.xml?

E Efkan YILMAZ 5 years 6 months ago

Ah ok, i do see some issues with what you have here.  First, this thread is from 2013, and there have been some changes to EHS since then. We have recently published a new set of documentation for EHS and it can be found here.  Have a look at the Kiosk Mode section, our package names have been rebranded since our purchase by Zebra. a few years back.

Also, I'm not clear on why you are implementing a filter in your manifest.  The intent you send will be received by EHS, which is where that intent filter is implemented.

The way you have the Intents firing sequentially in that button callback may introduce a race condition. EHS will need a bit of time to receive the first intent and make the appropriate changes before you call it back to the foreground with the second Intent.

P Peter Arcuri 11 years 6 months ago

Not sure if this would help but there is a full_screen setting in Rhoconfig.txt:

# open rhodes app in full screen mode
# default 1 for Android up to Rhodes 2.2.5.
# on all other platforms and on Android from Rhodes >2.2.5 default 0
full_screen = 1

You may also want to investigate the Enterprise Home Screen software which locks down the ET1 from end-users navigating through the device. This is at no cost and can be downloaded from Motorola support site.
http://support.symbol.com/support/search.do?cmd=displayKC&docType=k… 0 558076555