Searched refs:In (Results 1 – 25 of 104) sorted by relevance
12345
/base/telephony/ril_adapter/ |
D | README.md | 38 - In terms of software, the RIL Adapter needs to work with the telephony core service \(core\_ser… 39 - In terms of hardware, the device must be equipped with a modem capable of independent cellular …
|
/base/global/system_resources/ |
D | README.md | 19 …s, such as the layered parameters, permission names and descriptions, etc. In addition, permission…
|
/base/telephony/cellular_data/ |
D | README.md | 55 - In terms of software, this module needs to work with the telephony core service \(core\_service… 56 - In terms of hardware, the accommodating device must be equipped with a modem and a SIM card cap…
|
/base/security/huks/ |
D | README.md | 16 …y provides the example implementation of the root key protection solution. In commercial scenarios…
|
D | LICENSE | 154 8. Limitation of Liability. In no event and under no legal theory,
|
/base/customization/enterprise_device_management/ |
D | README.md | 13 In the architecture of the Enterprise Device Management component:
|
/base/security/appverify/ |
D | README.md | 17 - **In application development**: After developing an application, you need to sign its installat… 19 - **In application installation**: The Application Framework subsystem of OpenHarmony installs ap…
|
/base/hiviewdfx/hiview/adapter/dbstore/include/ |
D | data_query.h | 86 DOCSTORE_API DataQuery& In(const std::string &field, const std::vector<T> &valueList) in In() function
|
/base/security/dataclassification/ |
D | README.md | 6 In OpenHarmony, the data transfer management module provides cross-device data transfer management …
|
/base/useriam/face_auth/ui/Settings_FaceAuth/entry/src/main/ets/pages/ |
D | entryView.ets | 28 …private TYPE_STATUS_BAR_TEMP:number = 2108 // In current version, windows subscribe type id is wro…
|
/base/usb/usb_manager/ |
D | README.md | 87 In this example, the USB device serves as the host and connects to the device to implement data tra… 156 In this example, the USB device is used as the device to set the ACM, ECM, and HDC functions.
|
/base/security/device_security_level/ |
D | README.md | 15 …ification model and actual OpenHarmony service scenarios and device types. In the OpenHarmony ecos… 156 // In this case, the callback will not be invoked.
|
/base/telephony/call_manager/ |
D | README.md | 53 - In terms of software, this module needs to work with the Security subsystem, Multimedia subsyst… 54 - In terms of hardware, the accommodating device must be equipped with a speaker or earphone, and…
|
/base/hiviewdfx/hisysevent/ |
D | README.md | 13 …rmation of key processes during system running, helping you locate faults. In addition, you can up…
|
/base/startup/init/ |
D | README.md | 11 …the first user-space process to the time the first application is started. In addition to loading … 43 In the **init.cfg** file, each of the preceding phases is represented by a job, which corresponds… 45 In addition to the **jobs** array, the **init.cfg** file also provides a **services** array, …
|
/base/security/permission_lite/ |
D | README.md | 14 In OpenHarmony, apps and system services run in independent sandboxes. Both processes and data are … 19 - In addition, app permission management allows users to view and manage the permission granting … 292 …ure access policies for APIs provided by the IPC authentication component. In this example, the se…
|
/base/hiviewdfx/hitrace/ |
D | README.md | 81 <p id="p17041941151217"><a name="p17041941151217"></a><a name="p17041941151217"></a>Note: In nested…
|
/base/security/device_auth/ |
D | README.md | 26 In the architecture:
|
/base/sensors/miscdevice/ |
D | LICENSE | 154 8. Limitation of Liability. In no event and under no legal theory,
|
/base/update/update_app/ |
D | LICENSE | 154 8. Limitation of Liability. In no event and under no legal theory,
|
/base/update/packaging_tools/ |
D | LICENSE | 153 8. Limitation of Liability. In no event and under no legal theory,
|
/base/useriam/pin_auth/ |
D | LICENSE | 154 8. Limitation of Liability. In no event and under no legal theory,
|
/base/powermgr/power_manager/ |
D | LICENSE | 154 8. Limitation of Liability. In no event and under no legal theory,
|
/base/iothardware/peripheral/ |
D | LICENSE | 154 8. Limitation of Liability. In no event and under no legal theory,
|
/base/notification/eventhandler/ |
D | LICENSE | 154 8. Limitation of Liability. In no event and under no legal theory,
|
12345