harmony 鸿蒙Charging Idle State Customization
Charging Idle State Customization
Overview
Introduction
By default, OpenHarmony provides the charging idle state feature. It determines whether a device is currently in the idle state according to a thermal level, battery level, charging state, and charging current of the device. A device in this state may execute some background intensive tasks. However, the conditions that determine the charging idle state vary according to product specifications. To address this issue, OpenHarmony provides the charging idle state customization function.
Constraints
The configuration path for battery level customization is subject to the configuration 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.
How to Develop
Setting Up the Environment
Hardware requirements:
Development board running the standard system, for example, the DAYU200 or Hi3516D V300 open source suite.
Environment requirements:
For details about the requirements on the Linux environment, see Quick Start.
Getting Started with Development
The following uses DAYU200 as an example to illustrate charging idle state customization.
Create the
thermal
folder in the product directory /vendor/hihope/rk3568.Create a target folder by referring to the default folder of battery idle state configuration, and install it in
//vendor/hihope/rk3568/thermal
. The content is as follows:profile ├── BUILD.gn ├── thermal_service_config.xml
Write the custom
thermal_service_config.xml
file by referring to the thermal_service_config.xml file in the default folder of charging idle state configuration. The following table describes the related configuration items.Table 1 Configuration items for the charging idle state
|Configuration Item|Description|Data Type|Value Range| |——–|——–|——–|——–| |thermallevel|Thermal level threshold|int|This field is defined based on the thermal level of a device. If the thermal level of a device is less than or equal to the threshold, the device is in the charging idle state.| |soc|Battery level threshold|int|The value of this field ranges from 0 to 100. If the battery level of the device is greater than or equal to the specified threshold, the device is in the charging idle state.| |charging|Charging status|int|The value 1 indicates that the battery is being charged, and the value 0 indicates the opposite.| |current|Battery charging current threshold|int|When the battery charging current is greater than or equal to the specified threshold (in mA), the battery is in the charging idle state.|
```shell
<idle name="charging">
<thermallevel>1</thermallevel>
<soc>90</soc>
<charging>1</charging>
<current>1000</current>
</idle>
```
Write the
BUILD.gn
file by referring to the BUILD.gn file in the default folder of charging idle state configuration to pack thethermal_service_config.xml
file to the/vendor/etc/thermal_config
directory. The configuration is as follows:import("//build/ohos.gni") # Reference build/ohos.gni. ohos_prebuilt_etc("thermal_service_config") { source = "thermal_service_config.xml" relative_install_dir = "thermal_config" install_images = [ chipset_base_dir ] # Required configuration for installing the thermal_service_config.xml file in the vendor directory. part_name = "product_rk3568" # Set part_name to product_rk3568 for subsequent build. You can change it as required. }
Add the build target to
module_list
in ohos.build in the/vendor/hihope/rk3568
directory. For example:{ "parts": { "product_rk3568": { "module_list": [ "//vendor/hihope/rk3568/default_app_config:default_app_config", "//vendor/hihope/rk3568/image_conf:custom_image_conf", "//vendor/hihope/rk3568/preinstall-config:preinstall-config", "//vendor/hihope/rk3568/resourceschedule:resourceschedule", "//vendor/hihope/rk3568/etc:product_etc_conf", "//vendor/hihope/rk3568/thermal/profile:thermal_service_config", // Add the configuration for building of thermal_service_config. ] } }, "subsystem": "product_hihope" }
In the preceding code,
//vendor/hihope/rk3568/thermal/
is the folder path,profile
is the folder name, andthermal_service_config
is the build target.Build the customized version by referring to Quick Start.
./build.sh --product-name rk3568 --ccache
Burn the customized version to the DAYU200 development board.
Debugging and Verification
After startup, run the following command to launch the shell command line:
hdc shell
Obtain the current charging idle state.
hidumper -s 3303 -a -i
The following is the reference charging idle state after customization:
-------------------------------[ability]------------------------------- ----------------------------------ThermalService--------------------------------- thermallevel: 1 soc: 100 charging: 1 current: 1000
Reference
During development, you can refer to the default charging idle state configuration.
Packing path: /vendor/etc/thermal_config/hdf
你可能感兴趣的鸿蒙文章
harmony 鸿蒙AI Framework Development Guide
harmony 鸿蒙NNRt Access Adaptation
harmony 鸿蒙Application Privilege Configuration
harmony 鸿蒙Setting Up a Development Environment
harmony 鸿蒙Development Guidelines
harmony 鸿蒙Application Framework Overview
- 所属分类: 后端技术
- 本文标签:
热门推荐
-
2、 - 优质文章
-
3、 gate.io
-
8、 golang
-
9、 openharmony
-
10、 Vue中input框自动聚焦