Hacktoberfest 2026: những issue maintainer đã đánh dấu cho tháng Mười, đang mở và phù hợp người mới. Xem issue Hacktoberfest

Expose InCallService data to other applications

Đang mở
  • Có gì không ổn?
#837 0 bình luận 0 reaction 0 người được giao Xem trên GitHub

Maintainer thường phản hồi trong vòng 4 ngày

Chưa có ai nhận issue này.

Đánh giá

Độ khó
5/5
Thời gian dự kiến
Hơn một tuần
Mức phù hợp với người mới
8/100
Loại issue
Tính năng
Độ rõ ràng
Cần làm rõ
Mức độ hoạt động
Ít trao đổi
Công nghệ
android, kotlin
Lĩnh vực
mobile

Hướng nghiên cứu

The issue names no files, tests or entry points, so there is no obvious starting point in the code. It asks for a new permission-gated way for other apps to receive InCallService call updates, but does not choose a mechanism, so the first step is a maintainer decision on the design. Done means an agreed design and a scoped follow-up issue, not a patch.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.

Mô tả

feature request needs triage
Checklist
  • I made sure that there are no existing issues - open or closed - to which I could contribute my information.
  • I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
  • I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
  • I have taken the time to fill in all the required details. I understand that the request will be dismissed otherwise.
  • This issue contains only one feature request.
  • I have read and understood the contribution guidelines.
Feature description

Basically, the application would declare its own permission. A bit like Shizuku, where applications that where allowed, will be able to ask/receive updates from InCallService. This would allow automation applications and call recording apps to detect and get informations about on-going calls. Since Android restrict access to call data to role-unique apps and system-apps, this would be the only way for a non-dialer app to get reliable access to this information. Since phone state is very limited, and getting the phone number is DEPRECATED and could be removed at any point.

As of now, I am only aware of the Welefon who does this, but its is very feature lacking.

Why do you want this feature?

I am the developer of ShizuCallRecorder and for a while now I have been hoping to see a dialer app implement a system that would allow third-party app to get access to the data given by InCallService. This data generally cannot be accesed by third-party app since Android restrict everything related to call to role-unique permission, system-apps, or very specific scenarios, with no way of letting the user decide / controls them.

Since ShizuCallRecorder is only a call recording, it would not make sense to force users to define the app as a dialer to get the unique dialer role. There are of courses work-arounds, and right now we have two of them, but Android or OEM could kill them at any moment.

Because of this, I have been looking for alternatives and also had Shizuku in mind. That's when a user made a feature request on our project and I discovered Welefon who does exactly what I just proposed. The only problem is that it is very lacking in features. This is bad since it would mean that if someone would wish to use ShizuCallRecorder, they would be forced to use X dialer, even if its lacking features for them.

FossifyOrg phone dialer is one of the most stable dialer app I know of, so I'm taking a shot, even trought this is probably a weird feature to ask. I could also see it beeing used by users who use automations apps (trought phone state broadcast may be enought for them)

Additional information

https://codeberg.org/wivewa/wivewa-dialer-android

Ngôn ngữ chính
Kotlin
Star
1.4k
Fork
213
Merge trung bình
5 ngày 10 giờ
Pull request đã merge (30 ngày)
14

Chuẩn bị môi trường

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của FossifyOrg/Phone

Tất cả issue của FossifyOrg/Phone

Issue tương tự

Thêm issue về Kotlin

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.