17 Aug 2018

What's new in Knox Tizen SDK for Wearables v2.3

By Arthur (Programmer Writer)

With the highly anticipated Galaxy Watch releasing soon, the Knox Tizen SDK for Wearables v2.3 is now available for download. This version includes new features for automatic call answering, preventing screen lock, and controlling dangerous permissions at runtime.

 

With v2.3, the Knox Tizen SDK for Wearables now includes:

Automatic call answering

The Galaxy Watch can be set to automatically answer calls. This is particularly useful in emergencies, where the watch owner may not be able to answer calls themselves. The IT admin can whitelist phone numbers that the application may answer automatically.
 

Benefits:

  • In medical emergencies, patients can be located for treatment or rescue via the call connection
  • In logistics, operational emergencies can be quickly reported and triaged via the call connection

 

Enumeration Types:

knox_custom_auto_call_answering_mode
knox_custom_auto_call_answering_number_whitelist_mode
 

APIs:

knox_custom_get_auto_call_answering_mode
knox_custom_get_auto_call_answering_number_whitelist
knox_custom_is_incoming_call_number_in_whitelist
knox_custom_set_auto_call_answering_mode
knox_custom_set_auto_call_answering_number_whitelist

 

Prevent screen lock

By default, users can set a lock screen password for the Galaxy Watch. In situations where the watch is shared between multiple users, this can be a problem when other users do not know the lock screen password.

To avoid this problem, we have added APIs that allow IT admins to block users from setting lock screen passwords.
 

Benefits:

  • Multiple users can now use a single Galaxy Watch without being locked out by another user’s password
  • Example use-cases: shared Galaxy Watches for hotel patrons, shared Galaxy Watches for employees working different shifts

APIs:

knox_mdm_set_allow_lockscreen_type_change
knox_mdm_get_allow_lockscreen_type_change

 

Control dangerous permissions at runtime

In order to enforce security policies in enterprise apps, IT admins may need to bypass user consent for certain device permissions. Apps may now be pre-granted with dangerous permissions so that they do not require user consent. These permissions automatically apply at runtime.
 

Benefits:

  • Allows apps to be pre-granted dangerous permissions, so that additional user action is not required
  • Saves IT admins time, since apps can now run all required permissions out-of-the-box
  • Example use case: acquiring permissions to access the device camera
     

APIs:

knox_mdm_add_privacy_permission_state_for_package
knox_mdm_remove_privacy_permissions_from_packages
knox_mdm_get_privacy_permission_state_for_package
knox_mdm_get_privacy_permission_data

 

Next steps