Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Incoming caller ID "Unknown" #2

Closed
penn5 opened this issue Mar 13, 2019 · 2 comments
Closed

Incoming caller ID "Unknown" #2

penn5 opened this issue Mar 13, 2019 · 2 comments
Assignees
@penn5
Labels
bug Something isn't working
Milestone
1.0

Comments

@penn5
Copy link
Owner

penn5 commented Mar 13, 2019

I don't know how to tell AOSP the incoming number, is it via ImsCallSession (looked quite hard, couldn't find anything) or via the notification sent to MmTelFeature? Or some other weird way?
@penn5 penn5 added this to the 1.0 milestone Mar 13, 2019
@penn5 penn5 added the bug Something isn't working label Mar 13, 2019
@penn5 penn5 self-assigned this Mar 13, 2019
@penn5
Copy link
Owner Author

penn5 commented Mar 15, 2019

Looking at the logs, the caller ID is being given to AOSP. According to https://forum.xda-developers.com/apps/magisk/module-v4-volte-enabler-t3649613/post76881758#post76881758, this is caused by no phone ID sent to aosp. It is true I'm not sending AOSP a phoneID but I can't see where that should be done...

@penn5 penn5 added the help wanted Extra attention is needed label Mar 15, 2019
@penn5
Copy link
Owner Author

penn5 commented Mar 17, 2019

Fixed as of 5e3d96a, f268032

@penn5 penn5 closed this as completed Mar 17, 2019
@penn5 penn5 removed the help wanted Extra attention is needed label Mar 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@penn5 penn5

Labels
bug Something isn't working
Projects
None yet
Milestone
1.0
Development

No branches or pull requests
1 participant
@penn5