Compare commits

...

25 Commits

Author SHA1 Message Date
zhangxiaowei16 6438eeb901 Delete gdbus related descriptions from the Readme 2025-08-06 17:17:57 +08:00
openvela-robot 86a200d89a update .github 2025-07-23 10:50:44 +08:00
openvela-robot b0071817bb update .github 2025-07-23 00:25:25 +08:00
openvela-robot 16f69f7121 workflows add stale.yml 2025-05-06 16:36:38 +08:00
openvela-robot 01c1f328bb Update the ci trigger from pull_request to pull_request_target 2025-01-09 23:56:42 +08:00
openvela-robot 8aa3e8b9cd update workflows ci.yml, delete pull_request_review trigger 2024-12-28 00:05:51 +08:00
openvela-robot 094a623c98 add .github/CODEOWNERS PULL_REQUEST_TEMPLATE.md 2024-12-27 19:49:45 +08:00
openvela-robot b4c7dedb71 update ci pull_request types to [opened, reopened, synchronize] 2024-12-24 01:16:47 +08:00
zhangxiaowei16 f087619da6 Merge open-vela/dev into dev and resolved conflict in README.md 2024-12-19 15:31:12 +08:00
zhangxiaowei16 30e8c59106 Merge open-vela/dev into dev and resolved conflict in README.md 2024-12-19 15:31:12 +08:00
zhangxiaowei16 482ccbae85 Add sub-warehouse description 2024-12-19 15:31:12 +08:00
zhangxiaowei16 3a066fe786 Add sub-warehouse description 2024-12-19 15:31:12 +08:00
zhangxiaowei16 2162092562 Add Sub-Repositories description 2024-12-19 15:31:12 +08:00
zhangxiaowei16 2b9d57e716 Add Sub-Repositories description 2024-12-19 15:31:12 +08:00
zhangxiaowei16 40c8137ad2 Add sub-warehouse description 2024-12-19 11:17:00 +08:00
zhangxiaowei16 358053c007 Add sub-warehouse description 2024-12-19 11:17:00 +08:00
zhangxiaowei16 4e9269a46d Add sub-warehouse description 2024-12-19 11:17:00 +08:00
liujinye ddd11f61fe workflows add ci.yaml 2024-12-17 10:25:40 +08:00
openvela-robot 9a1420afc2 workflows add checkpatch.yaml 2024-12-12 16:14:45 +08:00
zhangxiaowei16 05299971f7 Add ReadMe
Signed-off-by: zhangxiaowei16 <zhangxiaowei16@xiaomi.com>
2024-12-11 23:07:32 +08:00
openvela-robot f129ca1baf update issue template 2024-12-10 22:13:51 +08:00
openvela-robot 689200193d update workflows ci 2024-12-10 15:55:25 +08:00
openvela-robot 71c09c150c add issue template 2024-12-09 21:52:27 +08:00
openvela-robot 9ac514453d add ci.yml
Change-Id: Ia5ed2dd7d12acfe7879f464a120471333a780b0a
2024-11-25 19:44:06 +08:00
openvela-robot c5ab78a771 Merge commit
Change-Id: I28cf034b10e10cbe5d219e8f13df5959e2fc156a
2024-11-25 17:34:53 +08:00
22 changed files with 501 additions and 0 deletions

View File

@ -0,0 +1,40 @@
name: 缺陷反馈 | Bug
description: 当您发现了一个缺陷,需要向社区反馈时,请使用此模板。
title: "[BUG] <标题>"
labels: [👀 needs triage, "Type: Bug"]
body:
- type: markdown
attributes:
value: |
感谢您对 openvela 社区的支持与关注,欢迎反馈缺陷。
- type: textarea
attributes:
label: "重现问题的步骤"
description: "简洁地描述错误是什么,为什么您认为它是一个错误,以及如何重现它的步骤"
placeholder: |
重现问题的步骤,可能包括日志和截图。
1. 步骤 1
2. 步骤 2
validations:
required: true
- type: dropdown
id: architecture
attributes:
label: Issue Architecture
multiple: true
options:
- "Arch: arm"
- "Arch: arm64"
- "Arch: x86_64"
validations:
required: true
- type: markdown
attributes:
value: |
提交前请确认您已遵循以下步骤:
- 确认问题在 [**dev**](../) 上可重现。
- 遇到构建问题时运行 `make distclean`。
- 搜索 [现有问题](./)

View File

@ -0,0 +1,34 @@
name: 新需求 | Feature
description: 当您需要反馈或实现一个新需求时,使用此模板。
title: "[FEATURE] <标题>"
body:
- type: markdown
attributes:
value: |
感谢您对 openvela 社区的支持与关注。
- type: textarea
id: question-description
attributes:
label: 您的需求是否和问题相关?
description: 请简单描述问题并提供issue链接。
validations:
required: true
- type: textarea
id: solution
attributes:
label: 请描述您想要的解决方案
validations:
required: true
- type: textarea
id: 替代方案
attributes:
label: 请描述您考虑过的替代解决方案
- type: markdown
attributes:
value: |
提交前请搜索 [现有功能需求](./)

View File

@ -0,0 +1,22 @@
name: 问题咨询
title: "[问题咨询]"
body:
- type: markdown
attributes:
value: |
感谢您对 openvela 社区的支持与关注。
- type: textarea
id: question-description
attributes:
label: 描述
description: 请解释您的问题的背景或上下文,这有助于其他人更好地理解您的问题或疑问。
validations:
required: true
- type: markdown
attributes:
value: |
提交前请确认您已遵循以下步骤:
- 我已搜索 [openvela 文档](../),但未找到问题的答案。
- 已搜索 [现有问题](./)

View File

@ -0,0 +1 @@
blank_issues_enabled: false

View File

@ -0,0 +1,11 @@
## 概要
*在此部分更新信息,说明更改的必要性、具体做了什么以及如何实现的,如果有新功能出现,请提供参考资料(依赖关系、类似问题和解决方案等)。*
## 影响
*在此部分更新信息(如适用),说明更改如何影响用户、构建过程、硬件、文档、安全性、兼容性等。*
## 测试
*在此部分更新信息详细说明如何验证更改使用什么主机进行构建操作系统、CPU、编译器等使用什么目标进行验证架构、板子配置等。提供更改前后的构建和运行日志将非常有帮助。*

1
.github/CODEOWNERS vendored Normal file
View File

@ -0,0 +1 @@
* @xiaoxiang781216 @GUIDINGLI

View File

@ -0,0 +1,60 @@
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
name: Bug report
description: Report a bug to improve openvela stability
title: "[BUG] <title>"
labels: [👀 needs triage, "Type: Bug"]
body:
- type: markdown
attributes:
value: |
Hello openvela Community member! Please keep things tidy by putting your post in the proper place:
Reporting a bug: use this form.
Asking a question or getting help: use the [General Help](./new?assignees=&labels=Community%3A+Question&projects=&template=003_help.yml&title=%5BHELP%5D+%3Ctitle%3E) form.
Requesting a new feature: use the [Feature request](./new?assignees=&labels=Type%3A+Enhancement&projects=&template=002_feature_request.yml&title=%5BFEATURE%5D+%3Ctitle%3E) form.
- type: textarea
attributes:
label: "Description / Steps to reproduce the issue"
description: "A clear and concise description of what the bug is, and why you consider it to be a bug, and steps for how to reproduce it"
placeholder: |
A description with steps to reproduce the issue.
May include logs, images, or videos.
1. Step 1
2. Step 2
validations:
required: true
- type: dropdown
id: architecture
attributes:
label: Issue Architecture
description: What architecture(s) are you seeing the problem on?
multiple: true
options:
- "[Arch: arm]"
- "[Arch: arm64]"
- "[Arch: x86_64]"
validations:
required: true
- type: markdown
attributes:
value: |
### Before You Submit
Please verify that you've followed these steps:
- Confirm the problem is reproducible on [**dev**](../).
- Run `make distclean` when encountering build issues.
- Search [existing issues](./) (including [closed](./?q=is%3Aissue+is%3Aclosed))

View File

@ -0,0 +1,55 @@
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
name: Feature request
description: Request an enhancement for openvela
title: "[FEATURE] <title>"
labels: ["Type: Enhancement"]
body:
- type: markdown
attributes:
value: |
Hello openvela Community member! Please keep things tidy by putting your post in the proper place:
Requesting a new feature: use this form.
Asking a question or getting help: use the [General Help](./new?assignees=&labels=Community%3A+Question&projects=&template=003_help.yml&title=%5BHELP%5D+%3Ctitle%3E) form.
Reporting a bug: use the [Bug report](./new?assignees=&labels=%F0%9F%91%80+needs+triage%2CType%3A+Bug&projects=&template=001_bug_report.yml&title=%5BBUG%5D+%3Ctitle%3E) form.
- type: textarea
id: question-description
attributes:
label: Is your feature request related to a problem? Please describe.
description: Please provide a clear and concise description of what the problem is. Add relevant issue link.
validations:
required: true
- type: textarea
id: solution
attributes:
label: Describe the solution you'd like
description: Please provide a clear and concise description of what you want to happen.
validations:
required: true
- type: textarea
id: alternatives
attributes:
label: Describe alternatives you've considered
description: Please provide a clear and concise description of any alternative solutions or features you've considered.
- type: markdown
attributes:
value: |
### Before You Submit
Please verify that you've followed these steps:
- Search [existing feature requests](./) (including [closed](./?q=is%3Aissue+is%3Aclosed))

47
.github/ISSUE_TEMPLATE/003_help.yml vendored Normal file
View File

@ -0,0 +1,47 @@
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
name: General Help
description: Get general support regarding openvela
title: "[HELP] <title>"
labels: ["Community: Question"]
body:
- type: markdown
attributes:
value: |
Hello openvela Community member! Please keep things tidy by putting your post in the proper place:
Asking a question or getting help: use this form.
Reporting a bug: use the [Bug report](./new?assignees=&labels=%F0%9F%91%80+needs+triage%2CType%3A+Bug&projects=&template=001_bug_report.yml&title=%5BBUG%5D+%3Ctitle%3E) form.
Requesting a new feature: use the [Feature request](./new?assignees=&labels=Type%3A+Enhancement&projects=&template=002_feature_request.yml&title=%5BFEATURE%5D+%3Ctitle%3E) form
- type: markdown
attributes:
value: |
### Whether you're a beginner or an experienced developer, openvela Help is here to assist you with all your openvela questions and concerns.
- type: textarea
id: question-description
attributes:
label: Description
description: Explain the background or context of your question. This helps others understand your problem or inquiry better.
validations:
required: true
- type: markdown
attributes:
value: |
### Before You Submit
Please verify that you've followed these steps:
- I have searched [openvela Documentation](../) and didn't find an answer to my question.
- Search [existing issues](./) (including [closed](./?q=is%3Aissue+is%3Aclosed))

1
.github/ISSUE_TEMPLATE/config.yml vendored Normal file
View File

@ -0,0 +1 @@
blank_issues_enabled: false

20
.github/PULL_REQUEST_TEMPLATE.md vendored Normal file
View File

@ -0,0 +1,20 @@
*Note: Please adhere to [Contributing Guidelines](https://github.com/open-vela/docs/blob/dev/CONTRIBUTING.md).*
## Summary
*Update this section with information on why change is necessary,
what it exactly does and how, if new feature shows up, provide
references (dependencies, similar problems and solutions), etc.*
## Impact
*Update this section, where applicable, on how change affects users,
build process, hardware, documentation, security, compatibility, etc.*
## Testing
*Update this section with details on how did you verify the change,
what Host was used for build (OS, CPU, compiler, ..), what Target was
used for verification (arch, board:config, ..), etc. Providing build
and runtime logs from before and after change is highly appreciated.*

14
.github/workflows/checkpatch.yml vendored Normal file
View File

@ -0,0 +1,14 @@
# This is a basic workflow to help you get started with Actions
name: checkpatch
# Controls when the workflow will run
on:
pull_request:
types: [opened, reopened, synchronize]
# A workflow run is made up of one or more jobs that can run sequentially or in parallel
jobs:
checkpatch:
uses: open-vela/public-actions/.github/workflows/checkpatch.yml@dev
secrets: inherit

14
.github/workflows/ci.yml vendored Normal file
View File

@ -0,0 +1,14 @@
# This is a basic workflow to help you get started with Actions
name: CI
# Controls when the workflow will run
on:
pull_request_target:
types: [opened, reopened, synchronize]
# A workflow run is made up of one or more jobs that can run sequentially or in parallel
jobs:
ci:
uses: open-vela/public-actions/.github/workflows/ci.yml@dev
secrets: inherit

13
.github/workflows/clang-format.yml vendored Normal file
View File

@ -0,0 +1,13 @@
# This is a basic workflow to help you get started with Actions
name: clang-format
# Controls when the workflow will run
on:
pull_request:
types: [opened, reopened, synchronize]
# A workflow run is made up of one or more jobs that can run sequentially or in parallel
jobs:
clang-format:
uses: open-vela/public-actions/.github/workflows/clang-format.yml@dev

11
.github/workflows/stale.yml vendored Normal file
View File

@ -0,0 +1,11 @@
name: 'Close stale issues and PR'
on:
schedule:
- cron: '30 1 * * *'
workflow_dispatch: # 允许手动触发
jobs:
stale:
uses: open-vela/public-actions/.github/workflows/stale.yml@dev
secrets: inherit

19
.gitignore vendored Normal file
View File

@ -0,0 +1,19 @@
.depend
.kconfig
Kconfig
Make.dep
*.o
*.a
*.d
*.i
*~
.swp
.*.swp
core
.gdbinit
cscope.out
/*/
/.context
/.config
/.depend
/*.lib

23
CMakeLists.txt Normal file
View File

@ -0,0 +1,23 @@
# ##############################################################################
# frameworks/CMakeLists.txt
#
# Licensed to the Apache Software Foundation (ASF) under one or more contributor
# license agreements. See the NOTICE file distributed with this work for
# additional information regarding copyright ownership. The ASF licenses this
# file to you under the Apache License, Version 2.0 (the "License"); you may not
# use this file except in compliance with the License. You may obtain a copy of
# the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
# License for the specific language governing permissions and limitations under
# the License.
#
# ##############################################################################
nuttx_add_subdirectory()
nuttx_generate_kconfig(MENUDESC "Frameworks")

10
LICENSE Normal file
View File

@ -0,0 +1,10 @@
Copyright (C) 2024 Xiaomi Corporation
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

17
Make.defs Normal file
View File

@ -0,0 +1,17 @@
#
# Copyright (C) 2023 Xiaomi Corporation
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
include $(wildcard $(APPDIR)/frameworks/*/Make.defs)

19
Makefile Normal file
View File

@ -0,0 +1,19 @@
#
# Copyright (C) 2023 Xiaomi Corporation
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
MENUDESC = "Frameworks"
include $(APPDIR)/Directory.mk

35
README.md Normal file
View File

@ -0,0 +1,35 @@
# Frameworks Overview
\[ English | [简体中文](README_zh-cn.md) \]
This project adopts a top-level repository (super repository) management approach to organize multiple sub-repositories. This method allows for better management and maintenance of different parts of the codebase while ensuring the independence and flexibility of each sub-repository. The sub-repositories are prefixed with the `frameworks` field.
## List of Sub-Repositories
| Sub-repository Link | Description |
| -------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [frameworks_bluetooth](../../../../open-vela/frameworks_bluetooth) | This repository provides developers with a rich Bluetooth API, including API layers, various Services components, SAL protocol stack adaptation layers, and HAL hardware adaptation layers. |
| [frameworks_connectivity_telephony](../../../../open-vela/frameworks_connectivity_telephony) | This repository provides a set of tools and interfaces for application developers, covering network services, telephony services, SMS services, data services, and SIM card services. Developers can easily access telephony-related information and efficiently develop applications without delving into the internal logic of `Telephony`. |
| [frameworks_graphics_uikit](../../../../open-vela/frameworks_graphics_uikit) | This repository is based on `LVGL` and offers components like `video`, along with an extended font management system. It also includes various demo cases to help developers quickly get started. |
| [frameworks_multimedia_media](../../../../open-vela/frameworks_multimedia_media) | This repository provides key interfaces for multimedia playback and recording, audio focus management, audio strategies, etc. Developers can easily implement multimedia-related features using these interfaces. |
| [frameworks_multimedia_media_pfw](../../../../open-vela/frameworks_multimedia_media_pfw) | This repository provides a generic state machine framework with interfaces for use by the audio strategy module. |
| [frameworks_runtimes_services_brightness](../../../../open-vela/frameworks_runtimes_services_brightness) | This repository provides brightness control functionality, supporting automatic adjustment of screen brightness based on ambient light, as well as manual brightness adjustments and real-time curve modifications. |
| [frameworks_runtimes_services_am](../../../../open-vela/frameworks_runtimes_services_am) | This repository implements application lifecycle management in the `openvela` multi-application framework, including the creation, launch, pause, resume, and destruction of activities. |
| [frameworks_runtimes_services_pm](../../../../open-vela/frameworks_runtimes_services_pm) | This repository implements application package management functionality in the `openvela` multi-application framework, including installation, uninstallation, and querying. |
| [frameworks_runtimes_services_system_server](../../../../open-vela/frameworks_runtimes_services_system_server) | This repository implements the management and launch of multiple system services in the `openvela` multi-application framework, including application management, package management, window management, and brightness management services. |
| [frameworks_runtimes_services_wm](../../../../open-vela/frameworks_runtimes_services_wm) | This repository implements window management functionality in the `openvela` multi-application framework, including input, output, and display management capabilities. |
| [frameworks_runtimes_services_xmsdemo](../../../../open-vela/frameworks_runtimes_services_xmsdemo) | This repository provides demo applications for developers to quickly get started with application development in the `openvela` multi-application framework, ideal for beginners. |
| [frameworks_runtimes_typescript_ts2native](../../../../open-vela/frameworks_runtimes_typescript_ts2native) | This repository provides the core framework and examples for converting `TypeScript` to `Native` code in `openvela`. |
| [frameworks_runtimes_typescript_ts2wasm](../../../../open-vela/frameworks_runtimes_typescript_ts2wasm) | This repository provides the core framework and examples for converting `TypeScript` to `Wasm` bytecode in `openvela`, aimed at improving the runtime performance of `TypeScript`. |
| [frameworks_runtimes_wasm](../../../../open-vela/frameworks_runtimes_wasm) | This repository provides examples and extended API implementations for the `openvela` Wasm runtime environment, allowing quick integration of system capabilities into the Wasm runtime. |
| [frameworks_security](../../../../open-vela/frameworks_security) | This repository mainly includes the implementation of `openvela TEE (Trusted Execution Environment)` default security applications, including `TA (Trusted Application)` and `CA (Client Application)`. |
| [frameworks_security_optee_vela](../../../../open-vela/frameworks_security_optee_vela) | This repository provides the implementation of the `OPTEE (Open Portable Trusted Execution Environment)` framework compatible with the `openvela` kernel, allowing quick integration of `openvela` systems without needing to understand the details of the `openvela` architecture layer. |
| [frameworks_system_binder](../../../../open-vela/frameworks_system_binder) | This repository provides examples, performance testing programs, and C language implementations for various Binder scenarios, supporting the study and development of Binder. |
| [frameworks_system_charger](../../../../open-vela/frameworks_system_charger) | This repository provides `openvela` charging services, monitoring and managing battery charging processes, including thermal control, current limiting, and charge/discharge scenarios to ensure safe and fast charging. |
| [frameworks_system_healthd](../../../../open-vela/frameworks_system_healthd) | This repository provides `openvela` battery information monitoring services, publishing through the `battery_state` topic for applications to subscribe via the `uORB` framework. |
| [frameworks_system_ota](../../../../open-vela/frameworks_system_ota) | This repository mainly contains the implementation of OTA (Over-the-Air) updates and AVB (Android Verified Boot) signature verification. |
| [frameworks_system_topics](../../../../open-vela/frameworks_system_topics) | This repository provides the definitions of commonly used `topics` in `openvela`, including system, connectivity, and virtual sensor topics, supporting publishing and subscribing through the `uORB` framework. |
| [frameworks_system_utils](../../../../open-vela/frameworks_system_utils) | This repository contains basic system components and services, including `kvdb`, `trace`, `uv`, and others. |
| [frameworks_system_utils_uv](../../../../open-vela/frameworks_system_utils_uv) | This repository implements database and network interfaces in the style of `libuv`, making it easier to integrate these capabilities into asynchronous applications based on `libuv`. |
| [frameworks_system_vibrator](../../../../open-vela/frameworks_system_vibrator) | This repository provides powerful vibration functionality for various devices, enhancing user experience with customizable vibration patterns, amplitude, and intensity, and supporting cross-core API calls to control vibrator devices. |

34
README_zh-cn.md Normal file
View File

@ -0,0 +1,34 @@
# frameworks 简介
\[ [English](README.md) | 简体中文 \]
本项目采用顶层仓库super repository管理多个子仓库的方式进行组织。通过这种方式可以更好地管理和维护不同部分的代码库同时确保每个子仓库的独立性和灵活性。子仓库以 `frameworks` 字段开头。
## 子仓库列表
| 子仓库链接 | 描述 |
| :------------------------------------------------------------------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [frameworks_bluetooth](../../../../open-vela/frameworks_bluetooth) | 该仓库旨在为应用程序开发者提供丰富的蓝牙应用编程接口,包括 API 接口层、各种 Services 服务组件层、SAL 协议栈适配层和 HAL 硬件适配层。 |
| [frameworks_connectivity_telephony](../../../../open-vela/frameworks_connectivity_telephony) | 该仓库为应用程序提供了一组功能丰富的工具和接口,涵盖网络服务、通话服务、短信服务、数据服务和 SIM 卡服务。通过这些接口,应用开发者无需深入了解 `Telephony` 的内部业务逻辑,只需调用 `API` 即可轻松获取与 `Telephony` 相关的信息,并高效完成应用开发。 |
| [frameworks_graphics_uikit](../../../../open-vela/frameworks_graphics_uikit) | 该仓库基于 `LVGL` 提供了 `video` 等特色组件,并扩展了字体管理机制,同时包含多个基于这些组件的 demo 用例,帮助开发者快速上手。 |
| [frameworks_multimedia_media](../../../../open-vela/frameworks_multimedia_media) | 该仓库提供了用于实现多媒体播放与录制、音频焦点管理、音频策略等关键接口。通过这些接口,开发者可以轻松实现多媒体相关功能。 |
| [frameworks_multimedia_media_pfw](../../../../open-vela/frameworks_multimedia_media_pfw) | 该仓库为通用状态机框架,提供接口给音频策略模块使用。 |
| [frameworks_runtimes_services_brightness](../../../../open-vela/frameworks_runtimes_services_brightness) | 该仓库提供亮度控制功能,支持根据环境光自动调节屏幕亮度,并允许用户手动调整亮度,同时实时修改控制曲线。 |
| [frameworks_runtimes_services_am](../../../../open-vela/frameworks_runtimes_services_am) | 该仓库实现了 `openvela` 在多应用框架下的应用程序生命周期管理,包括活动的创建、启动、暂停、恢复和销毁。 |
| [frameworks_runtimes_services_pm](../../../../open-vela/frameworks_runtimes_services_pm) | 该仓库实现了 `openvela` 在多应用框架下的应用包管理功能,包括安装、卸载和查询。 |
| [frameworks_runtimes_services_system_server](../../../../open-vela/frameworks_runtimes_services_system_server) | 该仓库实现了 `openvela` 在多应用框架下启动和管理多个系统服务的功能,包括应用管理、包管理、窗口管理和亮度管理服务。 |
| [frameworks_runtimes_services_wm](../../../../open-vela/frameworks_runtimes_services_wm) | 该仓库实现了 `openvela` 在多应用框架下的窗口管理功能,包括输入、输出和显示管理等能力。 |
| [frameworks_runtimes_services_xmsdemo](../../../../open-vela/frameworks_runtimes_services_xmsdemo) | 该仓库提供了 `openvela` 在多应用框架下的应用开发 demo适合初学者和开发者快速上手。 |
| [frameworks_runtimes_typescript_ts2native](../../../../open-vela/frameworks_runtimes_typescript_ts2native) | 该仓库提供了 `openvela` 中将 `TypeScript` 转换为 `Native` 代码的核心框架和示例。 |
| [frameworks_runtimes_typescript_ts2wasm](../../../../open-vela/frameworks_runtimes_typescript_ts2wasm) | 该仓库是 `openvela` 中将 `TypeScript` 语言转换为 `Wasm` 字节码的核心框架和示例,旨在提高 `TypeScript` 的运行性能。 |
| [frameworks_runtimes_wasm](../../../../open-vela/frameworks_runtimes_wasm) | 该仓库提供了 `openvela` Wasm 运行时环境的部分示例和扩展 API 实现,使用该框架可以快速将系统的能力导入到 Wasm 运行时环境中。 |
| [frameworks_security](../../../../open-vela/frameworks_security) | 该仓库主要包含了 `openvela TEETrusted Execution Environment` 默认的安全应用 `TATrusted Application``CAClient Application` 实现。 |
| [frameworks_security_optee_vela](../../../../open-vela/frameworks_security_optee_vela) | 该仓库提供了兼容 `openvela` 内核的 `OPTEEOpen Portable Trusted Execution Environment` 框架实现,使用 `OPTEE` 框架可以快速接入 `openvela` 系统,无需了解 `openvela` 架构层的细节。 |
| [frameworks_system_binder](../../../../open-vela/frameworks_system_binder) | 该仓库提供了 `Binder` 各种场景的示例、性能测试程序,以及 `C` 语言版本的实现,旨在支持 `Binder` 的学习和开发。 |
| [frameworks_system_charger](../../../../open-vela/frameworks_system_charger) | 该仓库提供了 `openvela` 充电服务,用于监控和管理电池充电过程,包括温控、限流和停复充等场景,确保电池安全快速充电。 |
| [frameworks_system_healthd](../../../../open-vela/frameworks_system_healthd) | 该仓库提供了 `openvela` 电池信息监控服务,通过 `battery_state` 主题向外发布,供应用通过 `uORB` 框架订阅。 |
| [frameworks_system_ota](../../../../open-vela/frameworks_system_ota) | 该仓库主要包含 `OTA` 实现和 `AVB` 验签实现。 |
| [frameworks_system_topics](../../../../open-vela/frameworks_system_topics) | 该仓库提供了 `openvela` 常用 `topic` 的定义,包括系统、连接和虚拟传感器等,支持通过 `uORB` 框架进行发布和订阅。 |
| [frameworks_system_utils](../../../../open-vela/frameworks_system_utils) | 该仓库包含了系统基础组件和服务,包括 `kvdb`、`trace` 和 `uv` 等。 |
| [frameworks_system_utils_uv](../../../../open-vela/frameworks_system_utils_uv) | 该仓库实现了 `libuv` 风格的数据库和网络等接口,便于将这些能力集成到基于 `libuv` 的异步应用程序中。 |
| [frameworks_system_vibrator](../../../../open-vela/frameworks_system_vibrator) | 该框架旨在为各种设备提供强大的振动功能,通过可自定义的振动模式、幅度和强度提升用户体验,并支持跨核 API 调用以控制振动器设备。 |