You of course can't notice the delay with the way you tested it interactively with a send script action.

Try again by adding the line

    showmessagebox "abc"  5

before "sleep 20" to see the 20-second delay before the app is started.

Fot actual use in kiosk, put the 2-line script in a file with extension .cmd  on the device, and  use script://   instead of launch://  in your kiosk item.

Hi Enrico,

Thanks for posting your query!

How did you setup the WiFi configurations on the device? Did you do it manually or pushed it as a profile to those devices?

If not, please try to push the WiFi Configurations profile to the device, so that when the device start-up it will connect to the WiFi signal and then proceed with the lockdown mode.

Regards,

Hi,.

The connection parameters are distributed through a dedicated profile.

The issue occurs because at the startup the browser is opened when the wireless connection is not yet established.

Thanks

Hi Enrico,

How is that application pushed to the device? Is it via package? If so, did you check mark "Automatically Run Activity" while creating the PCG file in MobiControl-Package studio?

Regards,

Maybe you can try using a script ://  item in your single-item kiosk, and the script include a worst-case delay needed for Wifi connection set-up,  followed by a "start" script command to run the  browser app.

A smarter script using the new javascript engine should be able to give better result if more features on getting device status are added in the future.  

Thank you all for the help.

The application is pushed trough a package.

I had taken a look at the syntax of the android scripts but I had not found the delay field except for the reset command.

I will give a try to the new javascript engine if there are parameters suitable to my problem.

Just use 

    sleep  N  

in your script to create a fixed N-second delay.  

It should be followed by 

   start    YourBrowser_BundleID

to run your browser after the delay.

I tried these two commands in sequence through the SEND SCRIPT UTILITY

sleep 5
start com.wavelink.velocity

Nothing happens. I have to reset the device to be able to send script again.

Thank you very much for your help.

The startup script in lockdown works perfectly as well as the modified version in send script action.

Hi Enrico,

Thank you for advising us that your post has been solutioned. Please let us know what reply you found to assist you in solving your inquiry so others may benefit from this information by selecting "is solution".

Regards,

Done.