We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
For whatever reason, my device doesn't known it's own number. If you navigate into:
System -> About phone -> Status -> Sim Status
The "My phone number" section reads "unknown". This is a T-Mobile SIM card.
As I understand it, this means that TelephonyManager#getLine1Number returns blank.
TelephonyManager#getLine1Number
The reply should be in the same "thread" as the original outgoing group MMS.
The reply was instead put into a new thread, with my own number as an extra recipient:
The text was updated successfully, but these errors were encountered:
I also have this issue. I'm on lineageos 16 / oneplus3. My phone knows about both of my SIM cards and both of my phone numbers, though.
Sorry, something went wrong.
Hmmm interesting - what phone do you have @hhff?
@moezbhatti we're an OEM, so this device isn't released yet.
FWIW - this is the solution we implemented: klinker41/android-smsmms#156
We haven't had this merged yet as there's still one last change the repo owner would like. I'm hoping to finish that PR off on the weekend!
This happens to me. H3123 LineageOS 16. I should add that I can see my own number.
No branches or pull requests
DESCRIPTION
For whatever reason, my device doesn't known it's own number. If you navigate into:
The "My phone number" section reads "unknown". This is a T-Mobile SIM card.
As I understand it, this means that
TelephonyManager#getLine1Number
returns blank.STEPS
EXPECTED
The reply should be in the same "thread" as the original outgoing group MMS.
OBSERVATIONS
The reply was instead put into a new thread, with my own number as an extra recipient:
The text was updated successfully, but these errors were encountered: