samsung privileged health sdk the galaxy watch5 is equipped with samsung’s unique bioactive sensor that drives the next era of digital health monitoring. first introduced on the galaxy watch4 series, the bioactive sensor uses a single unique chip that combines three powerful health sensors — optical heart rate, electrical heart signal, and bioelectrical impedance analysis — to deliver extensive readings that include heart rate and blood oxygen level. what is samsung privileged health sdk the samsung privileged health sdk is specialized for galaxy watch4 devices or later. it provides both raw sensor signal data from the samsung bioactive sensor and processed data with our differentiated features. the sdk supports an improved health tracking capability to allow your applications to track the user's health data accurately with the accelerometer, raw ecg (electrocardiogram), ppg (photoplethysmogram), and heart rate including inter-beat interval. in addition, it provides more advanced health features such as the body composition measurement, to enable compelling use cases for health and fitness applications. the blood oxygen level and sweat loss after a running workout are also useful data to check a user's health status. what you can do a watch application using the samsung privileged health sdk runs on a galaxy watch with wear os powered by samsung. it will help users to monitor their overall health data and to provide an advanced healthy life. the sdk can be utilized in various fields such as fitness, remote patient monitoring, senior care, digital therapy, fatigue risk management, and corporate wellness. what are the advantages let's review more advantages of the samsung privileged health sdk. low watch battery consumption the samsung privileged health sdk's accelerometer data, ppg green data, and heart rate data are all received as a batching event. the sdk's batching operation gathers sensor data in an application processor without waking up the cpu and sends an event at specific periods to a watch application. this minimizes the watch's battery consumption and enables a watch application to track the user's status for the entire day. receiving raw sensor data the accelerometer, ecg, and ppg green data are provided as raw data by the samsung privileged health sdk. this is very useful to conduct various analyses and more in-depth research with your own algorithm. using galaxy watch specific features measuring the user's body composition, blood oxygen level, heart rate including the inter-beat interval, and sweat loss after a running workout is a feature specific to the galaxy watch. using the privileged health sdk, your watch application can easily measure these data. what data is provided the following data types are supported by the samsung privileged health sdk: data type details accelerometer raw x, y, and z axis data. provided as a batching event. ecg raw electrocardiogram data. provided as an on-demand event. ppg green raw data from ppg green led. provided as a batching event. ppg red raw data from ppg red led. provided as an on-demand event. ppg ir raw data from ppg infrared led. provided as an on-demand event. heart rate heart rate data, including inter-beat interval. provided as a batching event. bia body composition data. provided as an on-demand event. spo2 blood oxygen level. provided as an on-demand event. sweat loss lost water amount after a running workout. provided as an on-demand event. experience samsung privileged health sdk you can practice using the samsung privileged health sdk with our code labs. visit code lab to get started. partner app program our partner app program is an exclusive service for the samsung privileged health sdk that allows users to discover engaging health and fitness applications. the samsung privileged health sdk is now available for selected partners and we are reviewing all applications to join. apply for partner app program restrictions the samsung privileged health sdk only works on galaxy watch4 devices or later with wear os powered by samsung. testing the samsung privileged health sdk features is not possible in an emulator.

health device specs all samsung health device specs | apr 11, 2019 samsung health provides ble compatible guidelines and samsung health specifications to connect ble health devices with samsung health. ble compatible guidelines the following health devices can connect with samsung health through ble compatible guidelines. compatibility guideline - ble blood pressure monitors | v1.0 compatibility guideline - ble glucose meters | v1.0 compatibility guideline - ble heart rate monitors | v1.0 compatibility guideline - ble weight scales | v2.0 samsung health specifications the following health devices can connect with samsung health through samsung health specifications. samsung health specifications - ble enhanced heart rate monitors | v1.0 samsung health specifications - ble exercise monitors | v1.0 samsung health specifications - ble pedometers | v1.0 samsung health specifications - ble sleep monitors | v1.0 samsung health specifications - ble multiple health service device | v1.0 if a health device implements one more specs above ble multiple health service device specs should be applied together.

hello health data the following sections give you fundamentals for developing the samsung health's partner app. check first the development environment for samsung health's partner apps. importing library add the following library to the “libs” folder in your created application project. samsung-health-data-a.b.c.aar health data store connection add a <queries> element in your app manifest. <manifest . . . > <queries> <package android:name="com.sec.android.app.shealth" /> </queries> </manifest> connect to the health data store with healthdatastore. public class mainactivity extends activity { public static final string app_tag = "simplehealth"; private static mainactivity minstance = null; private healthdatastore mstore; private healthconnectionerrorresult mconnerror; private set<permissionkey> mkeyset; @override public void oncreate(bundle savedinstancestate) { // ... minstance = this; mkeyset = new hashset<permissionkey>(); mkeyset.add(new permissionkey(healthconstants.stepcount.health_data_type, permissiontype.read)); // create a healthdatastore instance and set its listener mstore = new healthdatastore(this, mconnectionlistener); // request the connection to the health data store mstore.connectservice(); } you can end the health data store connection when the activity is destroyed. @override public void ondestroy() { mstore.disconnectservice(); super.ondestroy(); } the connection result is sent to healthdatastore.connectionlistener. if it succeeds, acquiring data permission or querying data will be available. private final healthdatastore.connectionlistener mconnectionlistener = new healthdatastore.connectionlistener() { @override public void onconnected() { log.d(app_tag, "health data service is connected."); healthpermissionmanager pmsmanager = new healthpermissionmanager(mstore); try { // check whether the permissions that this application needs are acquired // request the permission for reading step counts if it is not acquired // get the current step count and display it if data permission is required // ... } catch (exception e) { log.e(app_tag, e.getclass().getname() + " - " + e.getmessage()); log.e(app_tag, "permission setting fails."); } } @override public void onconnectionfailed(healthconnectionerrorresult error) { log.d(app_tag, "health data service is not available."); showconnectionfailuredialog(error); } @override public void ondisconnected() { log.d(app_tag, "health data service is disconnected."); } }; the connection to the health data store can fail and you can check its error result through onconnectionfailed(). if there is an error, an application checks whether the health framework provides a solution with hasresolution() and calls resolve(). if the health framework provides its solution, resolve() makes an application move to one of the following page without a dialog message: app market's samsung health page to install or update it device's settings page to make samsung health available samsung health user's agreement page an application needs to show a proper message for each error case and call resolve(). private void showconnectionfailuredialog(healthconnectionerrorresult error) { alertdialog.builder alert = new alertdialog.builder(this); mconnerror = error; string message = "connection with samsung health is not available"; if (mconnerror.hasresolution()) { switch(error.geterrorcode()) { case healthconnectionerrorresult.platform_not_installed: message = "please install samsung health"; break; case healthconnectionerrorresult.old_version_platform: message = "please upgrade samsung health"; break; case healthconnectionerrorresult.platform_disabled: message = "please enable samsung health"; break; case healthconnectionerrorresult.user_agreement_needed: message = "please agree with samsung health policy"; break; default: message = "please make samsung health available"; break; } } alert.setmessage(message); alert.setpositivebutton("ok", new dialoginterface.onclicklistener() { @override public void onclick(dialoginterface dialog, int id) { if (mconnerror.hasresolution()) { mconnerror.resolve(minstance); } } }); if (error.hasresolution()) { alert.setnegativebutton("cancel", null); } alert.show(); } see the health data store for more information. permission request the meta-data element for the required data permission value in manifest works with the permission request api. if you want to request data permission for reading the step count, write its value in your application project's manifest as the following example. see privacy check flow in privacy. <application <meta-data android:name="com.samsung.android.health.permission.read" android:value="com.samsung.health.step_count" /> </application> create a permission key set and add a permission key for reading the step count. public class mainactivity extends activity { private set<permissionkey> mkeyset; @override public void oncreate(bundle savedinstancestate) { // ... mkeyset = new hashset<permissionkey>(); mkeyset.add(new permissionkey(healthconstants.stepcount.health_data_type, permissiontype.read)); // connect to health data store } and call healthpermissionmanager.requestpermissions() with its listener. private final healthdatastore.connectionlistener mconnectionlistener = new healthdatastore.connectionlistener() { @override public void onconnected() { log.d(app_tag, "health data service is connected."); healthpermissionmanager pmsmanager = new healthpermissionmanager(mstore); try { // check whether the permissions that this application needs are acquired map<permissionkey, boolean> resultmap = pmsmanager.ispermissionacquired(mkeyset); if (resultmap.containsvalue(boolean.false)) { // request the permission for reading step counts if it is not acquired pmsmanager.requestpermissions(mkeyset, mainactivity.this).setresultlistener(mpermissionlistener); } else { // get the current step count and display it // ... } } catch (exception e) { log.e(app_tag, e.getclass().getname() + " - " + e.getmessage()); log.e(app_tag, "permission setting fails."); } } // ... }; if requestpermissions() is called successfully, the permission ui is popped up to the user. the user's permission information is saved by selecting "done" after the user allows each data permission. and it is received through healthresultholder.resultlistener. private final healthresultholder.resultlistener<permissionresult> mpermissionlistener = new healthresultholder.resultlistener<permissionresult>() { @override public void onresult(permissionresult result) { log.d(app_tag, "permission callback is received."); map<permissionkey, boolean> resultmap = result.getresultmap(); if (resultmap.containsvalue(boolean.false)) { // requesting permission fails } else { // get the current step count and display it } } }; } see the health permission manager for more information.

health data store the sdk provides the health data store to access the health data with a user’s consent. the data in the health data store can be shared with other partner apps also. preparing data access an application needs to connect the health data store, and acquire data permission to access the data in the health data store. the following figure shows a basic flow for working with samsung health. in case of connection failure, all exceptions should be handled clearly with a proper message to the user. it helps to prevent unexpected operations on your application. for detailed code, see: app manifest health data connection snippet acquiring data permission snippet health data query healthdataresolver helps to access the data with apis of the following figure. all queries except inserting data can be requested through a filter to set the target range for a query. a data query is sent asynchronously or synchronously. asynchronous query is used usually and you can select one of the methods for your need. see the following examples for more information. asynchronous data query synchronous data query the query result is retrieved as the following table. request result insert()update()delete() baseresult read() readresult aggregate() aggregateresult see data query snippets in api reference. filter healthdataresolver.filter is very useful to clear the data range for reading, updating, and aggregating health data. multiple filters can be combined with: and() or() see more descriptions in api reference. data normalization the health data is stored based on the normalized unit as defined in international system of unit (si) in the following table. item unit height cm weight kg temperature celsius blood glucose mmol/l blood pressure mmhg hba1c % spo2 % calorie kcal speed m/s distance meter time millisecond water intake ml caffeine intake mg data normalization enables your application to read health data without the specific unit. it means that you should be careful to unify the data units when inserting health data to the health data store. healthdataunit helps to convert data value between different units. converting unit

health data type the sdk provides useful predefined and custom data types. the supported data types are: activity daily step count trend step count exercise floorsclimbed rest sleep sleepstage food nutrition caffeine intake water intake health care body temperature blood glucose blood pressure heart rate oxygen saturation hba1c height weight see api reference for more data types. health document healthdocument environment info ambient temperature and humidity uv exposure user profile user profile (read-only) all data types have the following mandatory properties in the following table. each data type’s detailed properties are written in the api reference. property description uuid id of health data.assigned by the system when new data is created in samsung health. created_time utc time when data is created.assigned by the system when new data is created in samsung health. updated_time utc time when data is updated.assigned by the system when new data is created in samsung health. package_name application package name which provides data.assigned by the system when new data is created in samsung health. device_uuid device id which provides health data.

connection design guide samsung health's partner apps can connect to samsung health with samsung health sdk for android. a partner app needs to inform samsung health users that the app connects with samsung health and that it shares data. the connection design guide provides connection flows with unified look and feel for partner apps. notification of samsung health connection menu for connecting to samsung health permission setting menu samsung health name and icon notification of samsung health connection the launch screen of a partner app, event pop-up, or information space is a good approach to notify users of connecting with samsung health. a partner app needs to inform users with as concrete description and information as possible. do show explicitly a notification of working with samsung health as a partner app. the app's launch screen is recommended. do include a concrete description of the data synced with samsung health. do show the "samsung health" name or its icon. see the naming and icon guide. do add a ui flow to show the data permission pop-up after the notification message. menu for connecting to samsung health a partner app should provide a menu with a convenient interface for the user to change the data sync setting with samsung health. do create a menu to set the samsung health's data permission. do use a straightforward menu name like "connect to samsung health". recommended contents in "connect to samsung health" are: benefits available through samsung health connection and the data synced with samsung health link to samsung health do add an option to install samsung health through "connect to samsung health" if it is not installed. do show a samsung health's data permission popup through the menu. do place "connect to samsung health" where the user can find it easily. do not place "connect to samsung health" under multiple layers that are difficult for the user to find. samsung health name & icon samsung health's name and its icon in a partner app should be used properly. samsung health name - "samsung health" do use the name "samsung health". do not modify the official name, “samsung health”. examples of what to avoid are: shealth shealth s health s-health samsunghealth samsung health's icon do use the latest icon. you can get it here. its official icon is: samsung health's icon (april 11th, 2019) (185kb) do not modify the icon. do not use any other resource images of samsung health except its icon. do not use the samsung health's icon or similar icon for your own application.

programming guide samsung health sdk for android helps samsung health's partners to share health data safely and to create useful health applications. samsung health has a health data store where its data can be shared with other partner apps after the user's consent. it supports android devices with marshmallow 6.0 including non-samsung devices. refer to the following table terms for samsung health sdk for android. term description health data framework it provides useful features to handle the user's health data. it is included in samsung health and its interface is provided with samsung health sdk for android. an app that uses the sdk works with samsung health. samsung health an application that helps monitor the user's activities and helps the users to have a healthier life through monitoring walking steps, exercise, heart rate, and etc. it can be downloaded from the app market like google play or galaxy apps. the term is italicized to be easily distinguished. health data framework the health data framework of samsung health sdk for android has the following features: health data store handling the connection to samsung health inserting, reading, updating, or deleting health data storing data based on unified units. see api reference's descriptions for each data type health data type platform-defined and custom data type privacy granting permission based on the user's consent to read or write the specific data type architecture the sdk's health data framework is designed to provide safe access of its data and to have a seamless health service to the user. the following figure shows the health data framework's architecture. health data framework the health data framework is included in samsung health. applications can access the user's data that are stored in samsung health through the sdk. it keeps the user's health data safely. health data from various source devices having pedometer, accelerator, or heart rate sensors are inserted to the health data framework with the unified data unit. the data can be read by the sdk. updating or deleting data is available if the app inserted the data. the figure above shows the class and interface relationships in health data. detailed descriptions for each class and interface are in the api reference. healthdatastore it handles the connection to the data storage of the device. it receives its connection result with healthdatastore.connectionlistener. most requests require the connection to the health data store. healthdataresolver the health data framework provides classes and interfaces to insert, read, update, or delete the data. healthdataresolver is a central class to handle the health data. it sends a data request with related request interfaces. the query result can be received immediately with healthdataholder.baseresult, healthdataresolver.readresult or healthdataresolver.aggregateresult. or it can be received asynchronously with healthresultholder.resultlistener. see health data store for more information. application developers can use platform-defined data types that samsung health sdk for android provides. see health data type for more information. especially healthconstants.common, the base interface of predefined data types, contains the following mandatory properties for health data. unique id of health data created and updated time of health data application package name device that provides health data the health data can be accessed with the user's consent. the following figure shows the relationship between classes and interfaces related to healthpermissionmanager. it requests permissions to the user with healthpermissionmanager.permissionkey to read or write for the specific health data type. the permission result can be received synchronous or asynchronously. see privacy for more information. the sdk's health data library provides the following package: com.samsung.android.sdk.healthdata main interfaces and classes in the library are described in the following table. see the api reference for details. interface / class description healthconnectionerrorresult this class handles errors for connection failure to the health data store. healthconstants this class defines constants of health data and contains interfaces for various kinds such as the step count or exercise. healthdata this class is an object for a health data type, e.g. the blood pressure or weight. quantitative and qualitative values can be defined for the specific health data type based on its data structure definition. it is used to manage health data with healthdataresolver. healthdataobserver this class defines an observer to handle health data changes. healthdataresolver this class accesses health data to insert, read, update, and delete with the filter and aggregate functions. healthdatastore this class handles the connection to the data store in the device. healthdataunit this class provides unified units for the health data store. healthdatautil this class provides useful utility apis. healthdevice this class contains detailed device information that provides health data. healthdevicemanager this class manages devices related health data. healthpermissionmanager this class requests permission to read or write health data for the specific health data type. healthresultholder this interface represents the result of invoking method. healthuserprofile this class provides the user information.

note : for android 11 (targetsdkversion 30), please add a <queries> element for the samsung health app in your app manifest. see hello health data for more details. note : there is a known issue that causes the health data permission to be removed after updating samsung health to version 6.19. if your app is affected by this, please guide the user to allow the permissions on your app again and update the samsung health app to the latest version. the issue has been solved in version 6.19.5. samsung health sdk for android samsung health sdk for android enables sharing health data between samsung health running on android phones and partner apps. it also enables partner apps to use samsung health's tracker feature through app creation with the sdk. samsung health's partner apps can provide their users with additional services with samsung health sdk for android. the sdk provides secure access to samsung health data with applicable data types. data sharing, however, is enabled only after the user's explicit consent. the user can select detailed data sharing settings including which partner app will access the user's data, and which data type will be read or written. furthermore, a partner app can launch a samsung health's tracker and define its own tracker tile. samsung health sdk for android provides the health data features. health data health data has the following features: health data store samsung health sdk for android keeps users' health data secured. the health data store handles the service connection. it facilitates reading samsung health's data or writing the partner's health data to samsung health. health data type it provides useful data types. each data type is designed to contain a given health data type's information. it is used to access the data in health data store. permissions and user controls the user's health data are sensitive information. handling data with the sdk is only available with the user's explicit consent. health data provides a unified user interface and gives the user control of the data sharing settings easily for each data type. partner apps program partner app program is an exclusive service for samsung health that allows users to discover engaging health and fitness applications. note : we are currently going through an update to better support our partners. for that reason, we will not be accepting any applications for the partner apps program at this time. sdk download after having a partnership with samsung health, download samsung health sdk for android and create your app. samsung health sdk for android | data (v1.5.0) nov 3, 2020 (1.62mb) connection design guide samsung health's partner apps connect to samsung health with samsung health sdk for android. unified interfaces in partner apps seamlessly connect with samsung health to provide uninterrupted user experience to the users. for the best result, please see connection design guide. notification of samsung health connection the launch screen of a partner app, event pop-up, or information space is a good approach to notify users of connecting with samsung health. a partner app needs to inform users with as concrete description and information as possible. menu for connecting to samsung health a partner app should provide a menu with a convenient interface for the user to change the data sync setting with samsung health. samsung health name & icon samsung health's name and its icon should be used properly in a partner app. restrictions samsung health android sdk requires samsung health installation. the latest sdk works with samsung health 6.12 or above. see the sdk and samsung health’s compatible versions here. samsung health runs on devices with android 8.0 oreo (api level 26) or above. it is available on all samsung smartphones and also non-samsung android smartphones. an app’s targetsdkversion that uses samsung health sdk for android should be 26 or above. the sdk provides apis to check whether the device supports the sdk. see faq for more information.

overview package class tree deprecated index samsung health android sdk - data api reference 1.5.0 health data this document describes com.samsung.android.sdk.healthdata apis in samsung health sdk for android. see: description packages package description com.samsung.android.sdk.healthdata this package provides classes and interfaces for the health data framework in samsung health sdk for android. health data this document describes com.samsung.android.sdk.healthdata apis in samsung health sdk for android. the health data package contains classes and interfaces which enable you to create applications with the following functionalities. health data store a partner app that uses samsung health sdk for android can write its health data to samsung health or read samsung health's data through the health data store connection. see health data store for more information. health data type the sdk provides useful predefined and custom data types. see health data types for more information. privacy data permission acquisition is required to access a specific data type. see permission manager for more information. for more information related to the development environment, fundamentals, features and sample descriptions, see programming guide. compatible version of samsung health samsung health sdk for android works with samsung health. the sdk's data library works properly with the specific samsung health version. sdk's heath data library version samsung health compatible version 1.5.0 6.12 or above 1.4.0 or above 6.2 or above 6.11 or below 1.3.0 5.11 or above6.1 or below 1.2.01.2.1 5.10 1.0.01.1.0 4.0 or above5.9 or below e.g. if you create your app with the health data library 1.5.0, it requires to install samsung health 6.12 or above in the device. if the sdk and samsung health's version is not matched, the sdk gives an error. old_version_platform you can resolve the error simply and induce the users to update samsung health to the latest version. here is a guide to prevent the related error. connect to the health data store. see healthdatastore.connectservice(). private healthdatastore mstore; @override public void oncreate(bundle savedinstancestate) { // create a healthdatastore instance and set its listener mstore = new healthdatastore(this, mconnectionlistener); // request the connection to the health data store mstore.connectservice(); } if it fails, check healthconnectionerrorresult.onconnectionfailed(). private final healthdatastore.connectionlistener mconnectionlistener = new healthdatastore.connectionlistener() { // ... @override public void onconnectionfailed(healthconnectionerrorresult error) { // ... } if the error is old_version_platform, it means that samsung health needs to be updated to the latest version. show a proper message to the user. @override public void onconnectionfailed(healthconnectionerrorresult error) { if (error.geterrorcode() == healthconnectionerrorresult.old_version_platform) { // show a message to the user to update samsung health } } check a resolution for the error with healthconnectionerrorresult.hasresolution(). if it gives true, resolve the error with healthconnectionerrorresult.resolve(). if (error.hasresolution()) { // if there is a solution, resolve it error.resolve(mainactivity.this); } the samsung health platform leads to upgrade samsung health on the app market. see its example: exception handing

overview package class tree deprecated index com.samsung.android.sdk.healthdata class healthdevicemanager java.lang.object com.samsung.android.sdk.healthdata.healthdevicemanager public class healthdevicemanager extends object this class provides device information that is registered in the data framework and is able to register a new source device that provides health data. if a new data is saved to samsung health and its source device is new, the source device is registered to the health data framework automatically. a device with samsung health installed is recognized as the local device. registering a new source device separately is availble with healthdevice.builder.build() and registerdevice(healthdevice). the user's device that installed your application can meet many environments like: changing a phone and synchronizing samsung health data with the user's samsung account. all data in the old phone are moved to the new one. using an accessory such as galaxy watch with the phone. a data query need to be requested with varied considerations for your application and target devices. if you want to make that the query result contains only data your intended devices, set data's source devices for the data query such as with setsourcedevices() of healthdataresolver.readrequest.builder. otherwise, the query result can contain unintentional data of registered other accessories to samsung health. getting current device information the current device that samsung health runs is registered as the local device in the health data framework. if your application runs the current device and adds a new data to samsung health, set the data's source device as the local device. the following example shows how to get the current device information. public class heathdataexample { // the state of connection private healthdatastore mstore; void createhealthdata() { healthdata data = new healthdata(); // sets required properties // sets source device's uuid data.setsourcedevice(new healthdevicemanager(mstore).getlocaldevice().getuuid()); // adds new data to samsung health healthdataresolver resolver = new healthdataresolver(mstore, null); insertrequest request = new insertrequest.builder().setdatatype(nutrition.health_data_type).build(); request.addhealthdata(data); } } getting all registered devices' information samsung health works with accessories such as galaxy watch by the user's registration and can save the registered accessory's health data. also your application can work with a linked accessory and inserts its measured data to samsung health. you can get all registered devices to samsung health with getalldevices() and figure out other devices beside the current device that samsung health runs as the following example. //gets the current device healthdevicemanager devicemanager = new healthdevicemanager(mstore); string localuuid = devicemanager.getlocaldevice().getuuid(); // gets all registered devices list<healthdevice> healthdevices = new healthdevicemanager(mstore).getalldevices(); // checks registered devices beside the current device for (healthdevice device : healthdevices) { if (!device.getuuid().equals(localuuid)) { log.d(app_tag, "accessory's uuid: " + device.getuuid()); } } registering device to samsung health if you add data to samsung health and the data's source device is not registered yet on samsung health, register the data's source device before to adding data with registerdevice(healthdevice). since: 1.0.0 constructor summary constructors constructor and description healthdevicemanager(healthdatastore store) constructs and initializes an instance of healthdevicemanager. method summary all methods instance methods concrete methods modifier and type method and description boolean changecustomname(string uuid, string name) changes a custom name of the health device for a given device id. list<healthdevice> getalldevices() gets a list of all source devices in samsung health's saved data. healthdevice getdevicebyseed(string seed) gets a health device specified by a seed. healthdevice getdevicebyuuid(string uuid) gets a health device specified by an uuid. list<string> getdeviceuuidsbycustomname(string name) gets uuids of health devices for a given custom name. list<string> getdeviceuuidsbygroup(int group) gets uuids of devices for a given group. list<string> getdeviceuuidsbymanufacturer(string manufacturer) gets uuids of health devices for a given manufacturer. list<string> getdeviceuuidsbymodel(string model) gets uuids of health devices for a given device model. healthdevice getlocaldevice() gets a healthdevice object of the current device. string registerdevice(healthdevice device) registers a new source device that provides health data to the health data framework. constructor detail healthdevicemanager public healthdevicemanager(healthdatastore store) constructs and initializes an instance of healthdevicemanager. parameters: store - a connection with the health data store since: 1.0.0 method detail getlocaldevice public healthdevice getlocaldevice() gets a healthdevice object of the current device. samsung health sdk for android registers the current device where samsung health is installed. returns: the health device object throws: illegalstateexception - if the connection to the health data store is invalid or a remote-invocation error occurs on the connection since: 1.0.0 getalldevices public list<healthdevice> getalldevices() gets a list of all source devices in samsung health's saved data. it's different with getting all connected devices with samsung health. if a connected device didn't save its data to samsung health, the device is not included in this api's return. because this api gives only all device ids based on the saved data. an accessory that the user removes from samsung health's accessory list can be contained in its result if the accessory's data is saved in samsung health. returns: a list of registered all health device objects throws: illegalstateexception - if the connection to the health data store is invalid or a remote-invocation error occurs on the connection since: 1.0.0 registerdevice public string registerdevice(healthdevice device) registers a new source device that provides health data to the health data framework. parameters: device - the health device object to register returns: the registered device's id throws: illegalargumentexception - if the argument is null illegalstateexception - if the connection to the health data store is invalid or a remote-invocation error occurs on the connection since: 1.0.0 see also: healthdevice.builder.build() getdevicebyseed public healthdevice getdevicebyseed(string seed) gets a health device specified by a seed. parameters: seed - the unique value that identifies the device. it can be a wi-fi mac address, bluetooth address, or device's serial number. returns: a health device object for the seed throws: illegalargumentexception - if the argument is null illegalstateexception - if the connection to the health data store is invalid or a remote-invocation error occurs on the connection since: 1.0.0 getdevicebyuuid public healthdevice getdevicebyuuid(string uuid) gets a health device specified by an uuid. parameters: uuid - the uuid that represents the device returns: a health device object for the uuid throws: illegalargumentexception - if the argument is null illegalstateexception - if the connection to the health data store is invalid or a remote-invocation error occurs on the connection since: 1.0.0 getdeviceuuidsbygroup public list<string> getdeviceuuidsbygroup(int group) gets uuids of devices for a given group. parameters: group - the device group. it can be the following value. healthdevice.group_unknown healthdevice.group_mobile healthdevice.group_external healthdevice.group_companion returns: a list of uuids for devices that are specified with the group throws: illegalstateexception - if the connection to the health data store is invalid or a remote-invocation error occurs on the connection since: 1.0.0 getdeviceuuidsbycustomname public list<string> getdeviceuuidsbycustomname(string name) gets uuids of health devices for a given custom name. parameters: name - the custom name returns: a list of uuids for devices that are specified with the custom name. throws: illegalargumentexception - if the argument is null illegalstateexception - if the connection to the health data store is invalid or a remote-invocation error occurs on the connection since: 1.0.0 getdeviceuuidsbymodel public list<string> getdeviceuuidsbymodel(string model) gets uuids of health devices for a given device model. parameters: model - the model name returns: a list of uuids for devices that are specified with the model name throws: illegalargumentexception - if the argument is null illegalstateexception - if the connection to the health data store is invalid or a remote-invocation error occurs on the connection since: 1.0.0 getdeviceuuidsbymanufacturer public list<string> getdeviceuuidsbymanufacturer(string manufacturer) gets uuids of health devices for a given manufacturer. parameters: manufacturer - the manufacturer name returns: a list of uuids for devices that are specified with the manufacturer throws: illegalargumentexception - if the argument is null illegalstateexception - if the connection to the health data store is invalid or a remote-invocation error occurs on the connection since: 1.0.0 changecustomname public boolean changecustomname(string uuid, string name) changes a custom name of the health device for a given device id. parameters: uuid - the device id name - the new custom name of the device returns: true if the change is successful, or false if otherwise throws: illegalargumentexception - if the argument is null illegalstateexception - if the connection to the health data store is invalid or a remote-invocation error occurs on the connection since: 1.0.0