mir/kdeconnect-android
2
0
Fork 0
mirror of https://github.com/KDE/kdeconnect-android synced 2025-09-02 23:25:10 +00:00
Code Issues Releases Wiki Activity

Potentially fix SMS/MMS access on Samsung devices

Browse Source
This commit is contained in:
Simon Redman
2019-06-05 20:32:28 -06:00
parent 9695e5a49e
commit 50f395bdef
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
src/org/kde/kdeconnect/Helpers/SMSHelper.java
View File

@@ -106,6 +106,13 @@ public class SMSHelper {
private static Uri getConversationUri() { private static Uri getConversationUri() {
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.KITKAT) { if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.KITKAT) {
return Telephony.MmsSms.CONTENT_CONVERSATIONS_URI; return Telephony.MmsSms.CONTENT_CONVERSATIONS_URI;
} else if ("Samsung".equals(Build.MANUFACTURER)){
// For some presumably asinine reason, Samsung devices do not support the regular SmsMms column.
// However, according to https://stackoverflow.com/a/13640868/3723163, we can work around it this way.
// By my understanding, "simple=true" means we can't support multi-target messages.
// Go complain to Samsung about their crappy OS changes!
Log.i("SMSHelper", "Samsung compatibility mode enabled. This may cause some features to not work properly.");
return Uri.parse("content://mms-sms/conversations?simple=true");
} else { } else {
// As with getSMSUriBad, this is potentially unsafe depending on whether a specific // As with getSMSUriBad, this is potentially unsafe depending on whether a specific
// manufacturer decided to do their own thing // manufacturer decided to do their own thing