[Feature]: Use Android Telecom Framework

未关闭
#8,117 0 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
30/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
android
领域
mobile

调研方向

Start by locating the Android call UI and its current WebView implementation; the issue does not name files or tests. Read the Android Telecom Framework integration guidance and map how calls are handled in the app before estimating the change. Done means replacing the laggy custom call UI with native Telecom integration and supporting the listed call, audio routing, DND, and multi-call behaviors.

由索引模型根据 Issue 内容生成。

描述

enhancement triage
Is there an existing issue for this?
  • I have searched the existing issues
Platform

Android

App version

7.1.2

Feature

Use Android Telecom Framework instead of custom UI which is laggy and running in webview...

The Android Telecom Framework is packed with specific features designed to standardize the communication experience. Here are the core capabilities developers rely on:

Universal Call Logging: The framework automatically logs all calls (both cellular and VoIP) into the native Android Call Log, provided the app requests the correct permissions.

Seamless Audio Routing: It intelligently transitions audio between the earpiece, speakerphone, wired headphones, and Bluetooth devices without requiring the developer to write complex audio-switching logic.

System UI Integration: VoIP calls can ring over the lock screen exactly like regular phone calls, offering a premium, native feel to third-party applications.

Do Not Disturb (DND) Compliance: The service automatically respects the user’s priority settings, muting incoming VoIP calls if the device is set to DND mode.

Multi-Call Management: It gracefully handles call waiting and conference calls, allowing users to hold a cellular call while answering an incoming internet call.

主要语言
Haskell
星标
19.7k
派生
1.3k
平均合并
1 天 10 小时
30 天内合并 PR
236

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

simplex-chat/simplex-chat 的其他 Issue

查看 simplex-chat/simplex-chat 的全部 Issue

相似的 Issue

更多 Haskell Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。