Bug 467822 - SMS messages are sent but not acknowledged and replies are not received on CalyxOS
Summary: SMS messages are sent but not acknowledged and replies are not received on Ca...
Status: REPORTED
Alias: None
Product: kdeconnect
Classification: Applications
Component: android-application (show other bugs)
Version: unspecified
Platform: Android Unspecified
: NOR normal
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-03-26 18:25 UTC by Tony Schmidt
Modified: 2023-12-25 22:34 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tony Schmidt 2023-03-26 18:25:41 UTC
SUMMARY
SMS messages are sent but not acknowledged and replies are not received on Pixel 4a5g running CalyxOS 4.7.5.


STEPS TO REPRODUCE
1. Pair phone with computer.
2. Send an SMS to a contact from the computer.

OBSERVED RESULT
Messages are sent to contact but the message appears gray (unacknowledged?) in desktop UI and replies from the contact are only received on the phone and not the computer.

EXPECTED RESULT
Sent messages should turn black and replies from contact should be received (tested and works on Pixel 6 running stock Android).

SOFTWARE/OS VERSIONS
Desktop OS: PopOS 22.04
Mobile OS: CalyxOS 4.7.5
Android KDE Connect 1.23.2

ADDITIONAL INFORMATION
Several warnings are posted in the attached Android logs, but I'm unsure which warning is the primary issue or what configuration the CalyxOS system may be missing to support the SMS message acknowledgement and receiving functions.

Some of the suspect warnings and logs include:
* W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcastMultiplePermissions:1222 com.android.server.TelephonyRegistry.broadcastServiceStateChanged:3085 com.android.server.TelephonyRegistry.notifyServiceStateForPhoneId:1616 com.android.internal.telephony.ITelephonyRegistry$Stub.onTransact:492 android.os.Binder.execTransactInternal:1285
* W BroadcastQueue: Permission Denial: receiving Intent { act=android.intent.action.SERVICE_STATE flg=0x1000010 (has extras) } to ProcessRecord{df2db07 2591:com.android.systemui/u0a171} (pid=2591, uid=10171) requires android.permission.ACCESS_FINE_LOCATION due to sender android (uid 1001)
* I QImsService: ImsSmsImpl : onSendSmsResult:: token:6 smsResponse:{ mMessageRef = 6, mSendSmsResult = 1, mSendSmsReason = 0, mNetworkErrorCode = -1}
Comment 1 Tony Schmidt 2023-03-27 01:14:22 UTC
Sorry, I guess I can't grok how to edit a ticket description in Bugzilla, so adding as a comment:

Desktop KDEConnect Version:  GSConnect 50 (Also tried with latest KDE-Connect version)
Comment 2 Tony Schmidt 2023-12-25 22:34:50 UTC
Still haven't figured out whether this is an issue that should be fixed on the KDE Connect or Android ROM side, but just switched phones to FairPhone5/eOS on Android13 and now things are working fine.