-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IncomingCall screen not appearing when default dialer app doesn't implement InCallService #1
Comments
If that's the case, show me where the problem is in my code and suggest a commit to revert or include. AFAIK, I touched almost nothing in Dialer. This is nearly straight from CAF. How can you say it doesn't happen on stock Android? Stock Android on which device? I would appreciate if you can look into this further and let me know. Thanks! |
I'm the creator of a popular dialer app on Google Play, we received a report from a user that when our app is set as the default dialer app in settings he no longer sees the incoming call screen (neither full-screen incoming call nor the header notification). We tried to recreate and investigate this in the docs. I'm not saying that the system dialer in Vertex has a bug, I'm sure it implements the InCallService as it should, however, the system can't count on the user-selected default dialer, which can be an app downloaded from Google Play like ours, to implement this service. You can install almost any dialer app from Google Play, set it as the default dialer app in settings, and check incoming calls yourself. |
Can you help me with something? |
according to InCallService docs
This doesn't mean that a default app must implement this service.
Because of this assumption in VertexOS, when setting a 3rd party dialer app from Google Play as the default dialer app, the incoming call screen stops appearing (both full screen and header).
This doesn't happen on stock Android.
The text was updated successfully, but these errors were encountered: