Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Expose InCallService data to other applications

Aperta
  • Qualcosa non va?
#837 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 4 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
8/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Tranquilla
Stack tecnologico
android, kotlin
Ambito
mobile

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
Kotlin
Stelle
1.4k
Fork
213
Merge medio
5g 10h
PR unite (30g)
14

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di FossifyOrg/Phone

Tutte le issue di FossifyOrg/Phone

Issue simili

Altre issue su Kotlin

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.