
本文来源:http://www.tpcf.cn/bicheng/54376.shtml
若有版权问题,请来信告知:13951431913#139.com 或在右方提交评论。
鸿蒙(HarmonyOS)应用层开发(北向)知识点汇总
鸿蒙(OpenHarmony)南向开发保姆级知识点汇总~
OpenHarmony(鸿蒙南向开发)——轻量系统STM32F407芯片移植案例
OpenHarmony(鸿蒙南向开发)——Combo解决方案之W800芯片移植案例
OpenHarmony(鸿蒙南向开发)——小型系统STM32MP1芯片移植案例
OpenHarmony(鸿蒙南向开发)——标准系统方案之瑞芯微RK3568移植案例(上)
本文章是基于瑞芯微RK3566芯片的khdvk_3566b开发板,进行标准系统相关功能的移植,主要包括产品配置添加,内核启动、升级,音频ADM化,Camera,TP,LCD,WIFI,BT,vibrator、sensor、图形显示模块的适配案例总结,以及相关功能的适配。
在产品 //vendor/ 目录下创建以kaihong名字命名的文件夹,并在kaihong文件夹下面新建产品命的文件夹khdvk_3566b。
在 //vendor/kaihong/khdvk_3566b 目录下创建config.json文件。该文件用于描述产品所使用的SOC以及所需的子系统。配置如下
type:配置系统的级别,这里直接standard即可。
subsystems:系统需要启用的子系统。子系统可以简单理解为一块独立构建的功能块。
已定义的子系统可以在 //build/subsystem_config.json 中找到。当然你也可以定制子系统。
这里建议先拷贝Hi3516DV300开发板的配置文件,删除掉hisilicon_products这个子系统。这个子系统为Hi3516DV300 SOC编译内核,不适合rk3566
参考https://gitee.com/openharmony-sig/sig-content/blob/master/devboard/docs/board-soc-arch-design.md,并把芯片适配目录规划为:
二级启动简单来说就是将之前直接挂载sytem,从system下的init启动,改成先挂载ramdsik,从ramdsik中的init 启动,做些必要的初始化动作,如挂载system,vendor等分区,然后切到system下的init。
Rk3566适配主要是将主线编译出来的ramdisk打包到boot.img中,主要有以下工作:
2.把主线编译出来的ramdsik.img 打包到boot.img
由于rk 启动uboot 支持从ramdisk 启动,只需要在打包boot_linux.img 的配置文件中增加ramdisk.img,因此没有使用主线的its格式,具体配置就是在内核编译脚本make-ohos.sh中增加:
增加了打包boot镜像的脚本make-boot.sh,供编译完ramdisk,打包boot 镜像时调用,主要内容:
调用make-boot.sh的修改可以参考如下pr:
init相关配置请参考 启动子系统的规范要求 即可
实现Audio HAL层驱动(HDI接口适配),给Audio服务(frameworks)提供所需的音频硬件驱动能力接口。包含 Audio Manager、Audio Adapter、Audio Control、Audio Capture、Audio Render等接口对象。
配合内核中的Audio Driver Model使用,实现音频硬件的控制、录音数据的读取、播放数据的写入。它里面包括Stream_ctrl_common 通用层,主要是为了和上层的audio HDI adapter层进行对接。
音频驱动框架模型,向上服务于多媒体音频子系统,便于系统开发者能够更便捷的根据场景来开发应用。向下服务于具体的设备厂商,对于Codec和DSP设备厂商来说,可根据ADM模块提供的向下统一接口适配各自的驱动代码,就可以实现快速开发和适配OpenHarmony系统。
接收lib层的控制指令并将控制指令分发到驱动层。
接收lib层的数据并将数据分发到驱动层
多声卡管理模块,每个声卡含有Dai、Platform、Codec、Accessory、Dsp、SAPM模块。
电源管理模块,对整个ADM电源进行功耗策略优化。
这里以khdvk_3566b为例,讲述Audio驱动开发,其涉及到的模块驱动主要有:Codec驱动、platform驱动、Dai驱动。 相关代码路径如下:
Codec模块需要填充下面三个结构体:
g_codecData:codec设备的操作函数集和私有数据集。
g_codecDaiDeviceOps:codecDai的操作函数集,包括启动传输和参数配置等函数接口。
g_codecDaiData:codec的数字音频接口的操作函数集和私有数据集。
1> CodecData结构体操作函数的实现
2> g_rk809DaiDeviceOps结构体的具体实现
完成 bind、init和release函数的实现
HdfDriverEntry结构体的具体填充:
该文件涉及音量、静音模式、mic、通道模式等相关寄存器配置
g_daiData:dai设备私有配置,其中包含dai设备的初始化、读写寄存器、操作函数。
g_daiDeviceOps:dai设备操作函数集,包含了dai的参数设置、触发、启动。
1> AudioDaiOps结构体的具体填充
2> DaiData结构体的具体填充
HdfDriverEntry结构体中的bind、init、release具体填充:
该文件涉及I2S时序、配置参数以及rk809使能等相关寄存器配置
没有特殊参数需要配置,一般情况下不需改动。
khdvk_3566b平台默认支持一个mipi接口的lcd屏幕
LCD的适配主要依赖于HDF显示模型,显示驱动模型基于 HDF 驱动框架、Platform 接口及 OSAL 接口开发,可以屏蔽不同内核形态(LiteOS、Linux)差异,适用于不同芯片平台,为显示屏器件提供统一的驱动平台。
如图为 HDF Display驱动模型层次关系
当前驱动模型主要部署在内核态中,向上对接到 Display 公共 hal 层,辅助 HDI 的实现。显示驱动通过 Display-HDI 层对图形服务暴露显示屏驱动能力;向下对接显示屏 panel 器件,驱动屏幕正常工作,自上而下打通显示全流程通路。
所以LCD的适配主要在于LCD panel器件驱动的适配
器件驱动的适配分为2部分:panel驱动和hcs配置
驱动中在初始化接口中实例化该结构体:
PanelInit负责panel的软件初始化
PanelPrepare负责亮屏的硬件时序初始化
PanelUnprepare负责灭屏的硬件时序初始化
需要说明的是,khdvk_3566b上的这款lcd使用的时候DRM显示框架
背光控制分为原生linux内核框架下背光驱动以及基于HDF框架开发的背光驱动模型。
rk3566背光是通过pwm控制占空比实现的,具体使用的是pwm4
使用HDF框架下的背光驱动,需要关闭原生驱动
基于HDF框架开发的背光驱动模型,如下图:
HDF PWM实现的调用的就是内核pwm的接口。
cat /sys/kernel/debug/pwm 来查看hdf pwm是否申请到pwm4
显示适配需要完成的工作:图形服务HDI接口适配、GPU适配、mipi dsi驱动适配
显示HDI 对图形服务提供显示驱动能力,包括显示图层的管理、显示内存的管理及硬件加速等。 显示HDI需要适配两部分:gralloc 和 display_device。
OpenHarmony提供了使用与Hi3516DV300参考实现,厂商可根据实际情况参考适配,khdvk_3566b display适配是在//device/soc/rockchip/hardware/display目录下,仓名为 device_soc_rockchip 。
gralloc模块提供显示内存管理功能,该实现基于drm开发。
drm设备节点定义在//device/soc/rockchip/hardware/display/src/display_gralloc/display_gralloc_gbm.c文件中,根据khdvk_3566b实际情况修改了drm文件节点。
display device模块提供显示设备管理、layer管理、硬件加速等功能。
display drm设备节点初始化,根据khdvk_3566b实际情况修改了drm设备名称。
硬件合成文件添加了颜色空间的支持模式
hello_composer 测试模块:Rosen图形框架提供的测试程序,主要显示流程,HDI接口等功能是否正常,默认随系统编译。
运行hello_composer测试相关接口 切换到/system/bin目录下,运行hello_composer测试命令
https://gitee.com/openharmony/drivers_peripheral/tree/master/display/test/unittest/standard单元测试:HDI显示模块提供的测试模块,主要测试HDI接口、显示buffer、驱动等能力,测试时也需要关闭render service和fondation进程。
添加编译模块 修改drivers/peripheral/display/test/BUILD.gn
添加缺失的文件包含 修改drivers/peripheral/display/test/unittest/standard/BUILD.gn 在第63行处,添加包含目录//device/soc/rockchip/hardware/display/src/display_gralloc,如果不修改此处有可能编译报错。
编译命令 编译hdf_test_display的命令如下:
编译结果 编译结果路径在out/khdvk_3566b/tests/unittest/hdf/display目录下,该目录下有三个可执行文件devicetest、gfxtest、gralloctest,可将这三文件通过hdc发送到khdvk_3566b开发板上运行测试。
运行测试 通过hdc下载到开发板/system/bin/目录下,并修改测试程序的可执行属性,在终端下输入如下命令
再分别执行命令,查看mipi屏显示结果:
GPU图形处理器, khdvk_3566b GPU适配是在//device/soc/rockchip/hardware/gpu目录下,目前采用的是rockchip提供闭源的bifrost gpu方案。
gpu编译的内容,我们来看下BUILD.gn的内容,其中我们预编译了libmali-bifrost-g52-g2p0-ohos.so动态库,khdvk_3566b是arm64位的,所以编译了lib64目录下的libmali-bifrost-g52-g2p0-ohos.so动态库。其中gup模块符号链接libEGL.so、libGLESv1.so、libGLESv2.so、libGLESv3.so、libmali.so.0、libmali.so.1动态库的符号。
常见的INPUT设备有键盘、鼠标、游戏杆、Touch Screen等。Touch 设备与主机通讯采用标准 I2C 总线,触屏 IC 提供中断支持,提高了触屏数据的实时性。本项目的触摸屏器件IC 为 GT911。
INPUT 驱动模型核心部分由设备管理层、公共驱动层、器件驱动层组成。
(2)平台驱动层:指各类input设备的公共抽象驱动(例如触摸屏的公共驱动),负责对板级硬件进行初始化、硬件中断处理、向manager注册input设备等;
(3)器件驱动层:指各器件厂家的差异化驱动,通过适配平台驱动预留的差异化接口,实现器件驱动开发量最小化。
INPUT驱动提供给系统服务Input Service可直接调用的驱动能力接口,按照属性分类三类:input设备管理模块、input数据上报模块、input业务控制模块,HDI接口主要包括如下三大类:
input设备管理模块:管理输入设备,包括输入设备的打开、关闭、设备列表信息获取等;
input业务控制模块:提供input设备的业务控制接口,包括获取器件信息及设备类型、设置电源状态等。
配置设备描述信息,在device_info.hcs中添加device_touch_chip:
配置Touch器件信息,在input_config.hcs中添加器件的特性:
Touch驱动适配涉及的文件及目录:
HDF驱动模型高度抽象集成,TP驱动的适配主要是器件驱动层的适配,首先需要明确TP所需要的软硬件资源。
3.使用的哪一组i2c,从设备的地址是什么
4.TP的初始化固件(通常由IC厂商提供)
TP模组需要依赖主机上的如下软件资源:
1.Hdf gpio子系统 用于设置gpio pin脚以及一些中断资源
2.Hdf i2c 子系统 用于进行i2c通信
经常有很多小伙伴抱怨说: 不知道学习鸿蒙开发哪些技术?不知道需要重点掌握哪些鸿蒙应用开发知识点?
为了能够帮助到大家能够有规划的学习,这里特别整理了一套纯血版鸿蒙(HarmonyOS Next)全栈开发技术的学习路线,包含了鸿蒙开发必掌握的核心知识要点,内容有(ArkTS、ArkUI开发组件、Stage模型、多端部署、分布式应用开发、WebGL、元服务、OpenHarmony多媒体技术、Napi组件、OpenHarmony内核、OpenHarmony驱动开发、系统定制移植等等)鸿蒙(HarmonyOS NEXT)技术知识点。
1.基本概念 2.构建第一个ArkTS应用 3.……
1.应用基础知识 2.配置文件 3.应用数据管理 4.应用安全管理 5.应用隐私保护 6.三方应用调用管控机制 7.资源分类与访问 8.学习ArkTS语言 9.……
1.Ability开发 2.UI开发 3.公共事件与通知 4.窗口管理 5.媒体 6.安全 7.网络与链接 8.电话服务 9.数据管理 10.后台任务(Background Task)管理 11.设备管理 12.设备使用信息统计 13.DFX 14.国际化开发 15.折叠屏系列 16.……
Linux 与 Windows 之间的文件共享

本文来源:http://www.tpcf.cn/bicheng/54376.shtml
若有版权问题,请来信告知:13951431913#139.com 或在右方提交评论。
Summary of Knowledge Points for HarmonyOS Application Layer Development (Northbound)
Comprehensive Guide to OpenHarmony Southbound Development ~
OpenHarmony (HarmonyOS Southbound Development) – Lightweight System STM32F407 Chip Porting Case
OpenHarmony (HarmonyOS Southbound Development) – W800 Chip Porting Case for Combo Solution
OpenHarmony (HarmonyOS Southbound Development) – STM32MP1 Chip Porting Case for Small Systems
OpenHarmony (HarmonyOS Southbound Development) – Standard System Solution: Rockchip RK3568 Porting Case (Part 1)
This article is based on the khdvk_3566b development board using the Rockchip RK3566 chip, and focuses on porting standard system-related functions. It mainly covers product configuration additions, kernel boot and upgrade, audio ADM conversion, and adaptation cases for Camera, TP, LCD, Wi-Fi, Bluetooth, vibrator, sensor, and graphics display modules, as well as the adaptation of related functions.
Create a folder named kaihong in the product //vendor/ directory, and create a new folder named khdvk_3566b under the kaihong folder.
Create the config.json file in the //vendor/kaihong/khdvk_3566b directory. This file is used to describe the SOC used by the product and the required subsystems. The configuration is as follows:
Type: The level of the configuration system; here, "standard" is sufficient.
Subsystems: Subsystems that need to be enabled by the system. A subsystem can be simply understood as an independently built functional block.
The defined subsystems can be found in //build/subsystem_config.json. Of course, you can also customize the subsystems.
Here, it is recommended to first copy the configuration file of the Hi3516DV300 development board and remove the hisilicon_products subsystem. This subsystem compiles the kernel for the Hi3516DV300 SOC and is not suitable for the RK3566.
Refer to https://gitee.com/openharmony-sig/sig-content/blob/master/devboard/docs/board-soc-arch-design.md and plan the chip adaptation directory as follows:
In simple terms, level 2 boot means changing the previous direct mounting of the system and booting from init under the system to first mounting the ramdisk and booting from init in the ramdisk, performing some necessary initialization actions, such as mounting the system, vendor, and other partitions, and then switching to init under the system.
The RK3566 adaptation mainly involves packaging the ramdisk compiled from the mainline into boot.img, and the main tasks are as follows:
2. Package the ramdisk.img compiled from the main line into boot.img.
Since rk's U-Boot supports booting from ramdisk, you only need to add ramdisk.img to the configuration file for packaging boot_linux.img. Therefore, the mainline its format is not used. The specific configuration is to add the following to the kernel compilation script make-ohos.sh:
Added the script make-boot.sh for packaging the boot image, to be called when compiling the ramdisk and packaging the boot image. Main contents:
For changes to the invocation of make-boot.sh, refer to the following PR:
For init-related configurations, please refer to the Specification Requirements for Starting Subsystems.
Implements the Audio HAL layer driver (HDI interface adaptation) and provides the required audio hardware driver capability interface for the Audio service (frameworks). Includes interface objects such as Audio Manager, Audio Adapter, Audio Control, Audio Capture, Audio Render, etc.
Used in conjunction with the Audio Driver Model in the kernel to control audio hardware, read recording data, and write playback data. It includes the Stream_ctrl_common common layer, which is mainly used to interface with the upper-layer audio HDI adapter layer.
The audio driver framework model serves the multimedia audio subsystem upstream, making it easier for system developers to develop applications based on specific scenarios. It serves specific device manufacturers downstream. For Codec and DSP device manufacturers, they can adapt their respective driver code according to the downstream unified interface provided by the ADM module, thus achieving rapid development and adaptation to the OpenHarmony system.
Receives control commands from the lib layer and distributes them to the driver layer.
Receive data from the lib layer and distribute it to the driver layer
Multi-sound card management module, each sound card contains Dai, Platform, Codec, Accessory, DSP, and SAPM modules.
Power management module, which optimizes the power consumption strategy for the entire ADM power supply.
Here, taking khdvk_3566b as an example, we will discuss the development of the audio driver, which mainly involves the following module drivers: Codec driver, platform driver, and DAI driver. The relevant code paths are as follows:
The codec module needs to populate the following three structures:
g_codecData: Set of operation functions and private data sets for the codec device.
g_codecDaiDeviceOps: The set of operation functions for codecDai, including function interfaces such as starting transmission and parameter configuration.
g_codecDaiData: Set of operation functions and private data sets for the codec's digital audio interface.
1> Implementation of CodecData Structure Operation Functions
2> Specific implementation of the g_rk809DaiDeviceOps structure
Complete the implementation of the bind, init, and release functions
Specific filling of the HdfDriverEntry structure:
This document covers the relevant register configurations for volume, mute mode, mic, channel mode, etc.
g_daiData: Private configuration of the DAI device, which includes the initialization, read/write registers, and operation functions of the DAI device.
g_daiDeviceOps: DAI device operation function set, which includes DAI parameter settings, triggering, and startup.
1> Specific population of the AudioDaiOps structure
2> Specific Population of the DaiData Structure
Specific filling of bind, init, and release in the HdfDriverEntry structure:
This document covers the configuration of relevant registers, including I2S timing, configuration parameters, and rk809 enablement.
There are no special parameters to configure, and generally no changes are required.
The khdvk_3566b platform supports an LCD screen with a MIPI interface by default.
The adaptation of LCD mainly relies on the HDF display model. The display driver model is developed based on the HDF driver framework, Platform interface and OSAL interface, which can shield the differences between different kernel forms (LiteOS, Linux), and is suitable for different chip platforms, providing a unified driver platform for display devices.
The figure shows the hierarchical relationship of the HDF Display driver model.
The current driver model is mainly deployed in kernel mode, connecting upwards to the Display public HAL layer to assist in the implementation of HDI. The display driver exposes the display driver capabilities to the graphics service through the Display-HDI layer; it connects downward to the display panel device, drives the screen to operate normally, and opens up the entire display process from top to bottom.
Therefore, the adaptation of LCD mainly lies in the adaptation of the LCD panel device driver.
The device driver adaptation is divided into two parts: panel driver and HCS configuration.
Instantiate this structure in the initialization interface in the driver:
PanelInit is responsible for the software initialization of the panel
PanelPrepare is responsible for the hardware timing initialization of screen activation.
PanelUnprepare is responsible for initializing the hardware timing for screen off.
It should be noted that the DRM display framework is used when this LCD on khdvk_3566b is in use.
Backlight control is divided into the backlight driver under the native Linux kernel framework and the backlight driver model developed based on the HDF framework.
The backlight of the RK3566 is achieved by controlling the duty cycle through PWM, specifically using PWM4.
To use the backlight driver under the HDF framework, the native driver needs to be disabled.
The backlight driver model developed based on the HDF framework is shown in the figure below:
The HDF PWM implementation calls the kernel PWM interface.
Use cat /sys/kernel/debug/pwm to check whether hdf pwm has requested pwm4.
Display adaptation requires the following tasks to be completed: adaptation of the graphics service HDI interface, GPU adaptation, and adaptation of the MIPI DSI driver.
The display HDI provides display driver capabilities for graphics services, including management of display layers, management of display memory, and hardware acceleration, etc. The display HDI needs to be adapted to two parts: gralloc and display_device.
OpenHarmony provides a reference implementation using Hi3516DV300. Manufacturers can refer to it for adaptation based on actual conditions. The khdvk_3566b display adaptation is located in the //device/soc/rockchip/hardware/display directory, and the repository name is device_soc_rockchip.
The gralloc module provides display memory management functions, and this implementation is based on DRM development.
The drm device node is defined in the file //device/soc/rockchip/hardware/display/src/display_gralloc/display_gralloc_gbm.c, and the drm file node has been modified according to the actual situation of khdvk_3566b.
The display device module provides functions such as display device management, layer management, and hardware acceleration.
Initialization of the display drm device node. The drm device name has been modified based on the actual conditions of khdvk_3566b.
The hardware composition file has added support for color space modes.
hello_composer test module: A test program provided by the Rosen graphics framework, mainly to check whether the process, HDI interface, and other functions are working properly. It is compiled with the system by default.
Run the hello_composer test-related interface Switch to the /system/bin directory and run the hello_composer test command
https://gitee.com/openharmony/drivers_peripheral/tree/master/display/test/unittest/standard test: The test module provided by the HDI display module mainly tests the capabilities of the HDI interface, display buffer, and driver, etc. The render service and foundation processes also need to be closed during the test.
Add compilation module Modify drivers/peripheral/display/test/BUILD.gn
Add the missing file include Modify drivers/peripheral/display/test/unittest/standard/BUILD.gn at line 63, add the include directory //device/soc/rockchip/hardware/display/src/display_gralloc. If this is not modified, a compilation error may occur.
Compilation Commands The commands to compile hdf_test_display are as follows:
Compilation results The compilation results are located in the out/khdvk_3566b/tests/unittest/hdf/display directory, which contains three executable files: devicetest, gfxtest, and gralloctest. These three files can be sent via hdc to the khdvk_3566b development board for running tests.
Run the test Download to the /system/bin/ directory of the development board via hdc, modify the executable attributes of the test program, and enter the following command in the terminal
Execute the commands again separately to check the display results on the MIPI screen:
GPU graphics processor: The khdvk_3566b GPU adaptation is located in the //device/soc/rockchip/hardware/gpu directory. Currently, the closed-source Bifrost GPU solution provided by Rockchip is used.
Regarding the content compiled by the GPU, let's take a look at the content of BUILD.gn, where we precompiled the libmali-bifrost-g52-g2p0-ohos.so dynamic library. Since khdvk_3566b is 64-bit ARM, the libmali-bifrost-g52-g2p0-ohos.so dynamic library under the lib64 directory was compiled. Among them, the GPU module symbolically links to the symbols of the dynamic libraries libEGL.so, libGLESv1.so, libGLESv2.so, libGLESv3.so, libmali.so.0, and libmali.so.1.
Common input devices include keyboards, mice, joysticks, touch screens, etc. The touch device communicates with the host using a standard I2C bus, and the touchscreen IC provides interrupt support, improving the real-time performance of touchscreen data. The touchscreen device IC for this project is the GT911.
The core part of the INPUT driver model consists of the device management layer, the common driver layer, and the device driver layer.
(2) Platform driver layer: Refers to the common abstract driver for various input devices (such as the common driver for touchscreens), responsible for initializing board-level hardware, handling hardware interrupts, registering input devices with the manager, etc.
(3) Device driver layer: Refers to the differentiated drivers of each device manufacturer. By adapting to the differentiated interfaces reserved by the platform driver, the amount of device driver development is minimized.
The INPUT driver provides a driver capability interface that can be directly called by the Input Service provided to the system service. It is classified into three categories according to attributes: input device management module, input data reporting module, and input service control module. The HDI interface mainly includes the following three categories:
Input device management module: Manages input devices, including turning input devices on and off, retrieving device list information, etc.
Input business control module: Provides the business control interface for input devices, including obtaining device information and device type, setting power status, etc.
Configure the device description information and add device_touch_chip in device_info.hcs:
Configure Touch device information and add device properties in input_config.hcs:
Files and directories involved in Touch driver adaptation:
The HDF driver model is highly abstract and integrated. The adaptation of the TP driver is mainly the adaptation of the device driver layer. First, the software and hardware resources required by the TP need to be clarified.
3. Which set of I2C is used, and what is the address of the slave device?
4. TP initialization firmware (usually provided by the IC manufacturer)
The TP module needs to rely on the following software resources on the host:
1. HDF GPIO subsystem is used to set GPIO pins and some interrupt resources
2. HDF I2C subsystem for I2C communication
Many people often complain that they don't know which technologies to learn for HarmonyOS development. They don't know which HarmonyOS application development knowledge points they need to focus on.
To help everyone plan their learning, we have specially compiled a learning roadmap for full-stack development technologies in the pure-blood version of HarmonyOS (HarmonyOS Next). It covers the core knowledge points essential for HarmonyOS development, including HarmonyOS (HarmonyOS NEXT) technical knowledge points such as ArkTS, ArkUI development components, the Stage model, multi-platform deployment, distributed application development, WebGL, meta-services, OpenHarmony multimedia technologies, Napi components, the OpenHarmony kernel, OpenHarmony driver development, system customization and porting, and more.
1. Basic Concepts 2.Building the first ArkTS application 3.……
1. Application Fundamentals 2.Configuration File 3.Application Data Management 4.Application Security Management 5.Application Privacy Protection 6.Third-party application invocation control mechanism 7.Resource Classification and Access 8.Learning the ArkTS language 9.……
1. Ability Development 2. UI Development 3.Public Events and Notifications 4.Window Management 5.Media 6. Security 7.Network and Connectivity 8.Telephone Services 9.Data Management 10.Background Task Management 11.Device Management 12.Device Usage Information Statistics 13. DFX 14.Internationalization Development 15.Foldable Screen Series 16.……
File sharing between Linux and Windows