Bug 414306

Summary: Samsung compat mode enabled on linageOS
Product: [Applications] kdeconnect Reporter: wargreen
Component: android-applicationAssignee: Albert Vaca Cintora <albertvaka>
Status: RESOLVED FIXED    
Severity: normal    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Android   
OS: Android 7.x   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description wargreen 2019-11-19 15:57:10 UTC
SUMMARY

On my samsung phone, the samsung compatibility mode should not be enabled cause it run LineageOS. This mode seem to break the sms functionalities.

STEPS TO REPRODUCE
1. Install LineageOS on a Samsung device
2. Install KDEconnect from F-Droid
3. Try to grab sms via GSconnect

OBSERVED RESULT
No responses from the device.

I got this log : 
11-17 19:24:00.052 25935 8421 I SMSHelper: Samsung compatibility mode enabled. This may cause some features to not work properly. 11-17 19:24:00.094 25935 8421 I SMSHelper: Samsung compatibility mode enabled. This may cause some features to not work properly. 11-17 19:24:00.172 25935 8421 E KDE/Device: Exception in SMSPlugin's onPacketReceived() 11-17 19:24:00.172 25935 8421 E KDE/Device: org.kde.kdeconnect.Helpers.SMSHelper$MessageAccessException: Error getting messages from content://mms-sms/conversations?simple=true . Available columns were: [_id, date, message_count, recipient_ids, snippet, snippet_cs, read, archived, type, error, has_attachment, attachment_info, notification] 11-17 19:24:00.172 25935 8421 E KDE/Device: at org.kde.kdeconnect.Helpers.SMSHelper.getMessages(SMSHelper.java:297) 11-17 19:24:00.172 25935 8421 E KDE/Device: at org.kde.kdeconnect.Helpers.SMSHelper.getConversations(SMSHelper.java:335) 11-17 19:24:00.172 25935 8421 E KDE/Device: at org.kde.kdeconnect.Plugins.SMSPlugin.SMSPlugin.handleRequestConversations(SMSPlugin.java:393) 11-17 19:24:00.172 25935 8421 E KDE/Device: at org.kde.kdeconnect.Plugins.SMSPlugin.SMSPlugin.onPacketReceived(SMSPlugin.java:329) 11-17 19:24:00.172 25935 8421 E KDE/Device: at org.kde.kdeconnect.Device.onPacketReceived(Device.java:569) 11-17 19:24:00.172 25935 8421 E KDE/Device: at org.kde.kdeconnect.Backends.BaseLink.packageReceived(BaseLink.java:84) 11-17 19:24:00.172 25935 8421 E KDE/Device: at org.kde.kdeconnect.Backends.LanBackend.LanLink.receivedNetworkPacket(LanLink.java:255) 11-17 19:24:00.172 25935 8421 E KDE/Device: at org.kde.kdeconnect.Backends.LanBackend.LanLink.lambda$reset$0$LanLink(LanLink.java:109) 11-17 19:24:00.172 25935 8421 E KDE/Device: at org.kde.kdeconnect.Backends.LanBackend.-$$Lambda$LanLink$TabvaCXA5qL_bcJDmIELWusNThw.run(lambda) 11-17 19:24:00.172 25935 8421 E KDE/Device: at java.lang.Thread.run(Thread.java:761) 11-17 19:24:00.172 25935 8421 E KDE/Device: Caused by: android.database.sqlite.SQLiteException: no such column: address (code 1): , while compiling: SELECT address, thread_id, sub_id, text_only, read, date, body, _id, type, msg_box FROM threads ORDER BY date DESC 11-17 19:24:00.172 25935 8421 E KDE/Device: at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:179) 11-17 19:24:00.172 25935 8421 E KDE/Device: at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:135) 11-17 19:24:00.172 25935 8421 E KDE/Device: at android.content.ContentProviderProxy.query(ContentProviderNative.java:421) 11-17 19:24:00.172 25935 8421 E KDE/Device: at android.content.ContentResolver.query(ContentResolver.java:534) 11-17 19:24:00.172 25935 8421 E KDE/Device: at android.content.ContentResolver.query(ContentResolver.java:475) 11-17 19:24:00.172 25935 8421 E KDE/Device: at org.kde.kdeconnect.Helpers.SMSHelper.getMessages(SMSHelper.java:229) 11-17 19:24:00.172 25935 8421 E KDE/Device: ... 9 more 

EXPECTED RESULT
Grab the sms on my computer.

SOFTWARE/OS VERSIONS
Debian SID
Gnome shell 3.34.1-1 with GSConnect 28
LineageOS 14.1 (android 7.1.2) on a Samsung GT-I9195
KDEconnect 1.13.2 from F-Droid

ADDITIONAL INFORMATION
Seem to work with KDEconnect 1.13 (from memory) but i can't try, downgrade fail.
Comment 1 Albert Vaca Cintora 2019-11-21 20:54:01 UTC
Should be fixed in v1.13.3