1# Thermal Scene Customization 2 3## Overview 4 5### Introduction 6 7By default, OpenHarmony provides the thermal scene feature. During device usage, for example, gaming, photographing, or calling, the system will try to balance the performance, temperature, and power consumption. The thermal policy is usually scenario-specific. For example, the thermal policy in the gaming scenario does not decrease the screen brightness. However, the thermal scene definition varies according to product specifications. To address this issue, OpenHarmony provides the thermal scene customization function. 8 9### Constraints 10 11The configuration path for battery level customization is subject to the [configuration policy](https://gitee.com/openharmony/customization_config_policy). In this development guide, `/vendor` is used as an example of the configuration path. During actual development, you need to modify the customization path based on the product configuration policy. 12 13## How to Develop 14 15### Setting Up the Environment 16 17**Hardware requirements:** 18 19Development board running the standard system, for example, the DAYU200 or Hi3516D V300 open source suite. 20 21**Environment requirements:** 22 23For details about the requirements on the Linux environment, see [Quick Start](../quick-start/quickstart-overview.md). 24 25### Getting Started with Development 26 27The following uses [DAYU200](https://gitee.com/openharmony/vendor_hihope/tree/master/rk3568) as an example to illustrate thermal scene customization. 28 291. Create the `thermal` folder in the product directory [/vendor/hihope/rk3568](https://gitee.com/openharmony/vendor_hihope/tree/master/rk3568). 30 312. Create a target folder by referring to the [default thermal scene configuration folder](https://gitee.com/openharmony/powermgr_thermal_manager/tree/master/services/native/profile), and install it in `//vendor/hihope/rk3568/thermal`. The content is as follows: 32 33 ```text 34 profile 35 ├── BUILD.gn 36 ├── thermal_service_config.xml 37 ``` 38 393. Write the custom `thermal_service_config.xml` file by referring to the [thermal_service_config.xml](https://gitee.com/openharmony/powermgr_thermal_manager/blob/master/services/native/profile/thermal_service_config.xml) file in the default thermal scene configuration folder. The following table describes the related configuration items. 40 41 **Table 1** Configuration items for the thermal scene 42 43 | Configuration Item| Configuration Item Description| Parameter| Parameter Description| Parameter Type| Value Range| 44 | -------- | -------- | -------- | -------- | -------- | -------- | 45 | name="scene" | One or more application scenarios specified by enum values.| param | Application scenarios: photographing, calling, and gaming.| enum | cam, call, and game| 46 47 **screen** and **charge** indicate the status of the application scenario; and specifically, whether the screen is turned on and whether the battery is being charged. 48 49 ```shell 50 <state> 51 <item name="scene" param="cam,call,game"/> 52 <item name="screen"/> 53 <item name="charge"/> 54 </state> 55 ``` 56 574. Write the `BUILD.gn` file by referring to the [BUILD.gn](https://gitee.com/openharmony/powermgr_thermal_manager/blob/master/services/native/profile/BUILD.gn) file in the default thermal scene configuration folder to pack the `thermal_service_config.xml` file to the `/vendor/etc/thermal_config` directory. The configuration is as follows: 58 59 ```shell 60 import("//build/ohos.gni") # Reference build/ohos.gni. 61 62 ohos_prebuilt_etc("thermal_service_config") { 63 source = "thermal_service_config.xml" 64 relative_install_dir = "thermal_config" 65 install_images = [ chipset_base_dir ] # Required configuration for installing the thermal_service_config.xml file in the vendor directory. 66 part_name = "product_rk3568" # Set part_name to product_rk3568 for subsequent build. You can change it as required. 67 } 68 ``` 69 705. Add the build target to `module_list` in [ohos.build](https://gitee.com/openharmony/vendor_hihope/blob/master/rk3568/ohos.build) in the `/vendor/hihope/rk3568` directory. For example: 71 72 ```json 73 { 74 "parts": { 75 "product_rk3568": { 76 "module_list": [ 77 "//vendor/hihope/rk3568/default_app_config:default_app_config", 78 "//vendor/hihope/rk3568/image_conf:custom_image_conf", 79 "//vendor/hihope/rk3568/preinstall-config:preinstall-config", 80 "//vendor/hihope/rk3568/resourceschedule:resourceschedule", 81 "//vendor/hihope/rk3568/etc:product_etc_conf", 82 "//vendor/hihope/rk3568/thermal/profile:thermal_service_config", // Add the configuration for building of thermal_service_config. 83 ] 84 } 85 }, 86 "subsystem": "product_hihope" 87 } 88 ``` 89 In the preceding code, `//vendor/hihope/rk3568/thermal/` is the folder path, `profile` is the folder name, and `thermal_service_config` is the build target. 90 916. Build the customized version by referring to [Quick Start](../quick-start/quickstart-overview.md). 92 93 ```shell 94 ./build.sh --product-name rk3568 --ccache 95 ``` 96 977. Burn the customized version to the DAYU200 development board. 98 99### Debugging and Verification 100 1011. After startup, run the following command to launch the shell command line: 102 ```shell 103 hdc shell 104 ``` 105 1062. Obtain the current thermal scene information. 107 ```shell 108 hidumper -s 3303 -a -s 109 ``` 110 111 The following is the reference thermal scene result after customization: 112 ```shell 113 -------------------------------[ability]------------------------------- 114 115 116 ----------------------------------ThermalService--------------------------------- 117 name: scene params: cam,call,game 118 name: screen 119 name: charge 120 ``` 121 122## Reference 123During development, you can refer to the [default thermal scene configuration](https://gitee.com/openharmony/powermgr_thermal_manager/blob/master/services/native/profile/thermal_service_config.xml). 124 125Packing path: `/vendor/etc/thermal_config/hdf` 126