qksms
qksms copied to clipboard
moezbhatti
not receiving messages when qksms is being used
DESCRIPTION
I am currently running HavocOS on android pie on a OnePlus 3T , and I have not received texts when qksms is the default app. When Google messages is used as the default app, I receive messages, but have to resync with native Android database each time. Sending works just fine.
STEPS
- Use pie (havocos) (using op3t)
- Set qksms as default messaging app
- Send message from other device
EXPECTED
Message successfully received
OBSERVATIONS
No message is received on QKSMS end
It appears I encounter exactly the same issue. I'm running Android 8.1 on a Nokia 5 with QKSMS 3.5.4 installed.
(QKSMS is a great app btw).
also exactly the same here, on PIE, omnirom. But the really nasty thing is that senders on their side DO HAVE THE DELIVERY REPORT ! Be aware of this ! that is a really vicious bug. QK version 3.5.4
I have the opposite issue on my Nokia 6.1 (Android Pie) - messages I send from QKSMS aren't reaching recipients.
I would like to confirm I am having the same issue on an Asus Zenfone 4 Max. I had wrote the developer an email about it and got a response a couple days ago. I just responded to it but would like to add to this ticket as well.
Using Android 8.1 currently. I also made sure qksms was NOT being optimized in the battery saver.
May or may not be related... BLU Advance 4.0 L3 + Android 6.0. QKSMS works fine as the default SMS app as long as I keep the system Messages app enabled. As soon as I disable the Messages app SMS messages start to be lost or delayed randomly, (lost much more often than received).
@linulin are you setting QKSMS as your default SMS app before or after disabling your built-in messaging app?
IIRC I was setting QKSMS as the default SMS app before disabling the built-in messaging app. So, I've just tried the other way - enabled the built-in Messages app, made it the default, then disabled it. The default was automatically transferred to QKSMS. Sent a test SMS, didn't receive it within reasonable time, rebooted the phone, and this seemed to resolve the issue. Several SMS notifications from different sources were received in time after that, although I need to test it for a few days to be sure. (There is one more thing that could affect the result this time - when I started making changes the built-in messaging app was at its default out-of-the-box version rather than at a later version from Google Play.)
Unfortunately, the issue reappeared the next morning without any other changes on my side. And again the fix was in enabling the disabled built-in Messages app.
What puzzles me is that QKSMS does not experience this issue on a slightly different phone (BLU Vivo 5 Mini) which uses the same Android build number (MRA58K), and is configured in a similar way using a similar set of installed apps. (The only user-visible differences are low-level stuff, like Baseband version and Kernel version, and the Custom build version.)
Yes, as was mentioned above by a different person, I also confirm that senders see successful delivery reports on their side while no messages are received by QKSMS.
Possibly fixed by 11ecf65642c4d090df6eae9d5d09d3b27bb7500b, which I'll be releasing in 3.6.8 shortly
If one of you could confirm whether or not this helps, that would be a great help!
Wow that would be awesome ! That's the only reason I couldn't use QKSMS till now. I sadly can't test it for now :/ I really need to be confident with SMS reliance during those days... But gonna follow this, and many thanks for having tried yet.
Le mardi 27 août 2019, Moez Bhatti [email protected] a écrit :
Possibly fixed by 11ecf65 https://github.com/moezbhatti/qksms/commit/11ecf65642c4d090df6eae9d5d09d3b27bb7500b, which I'll be releasing in 3.6.8 shortly
If one of you could confirm whether or not this helps, that would be a great help!
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/moezbhatti/qksms/issues/1336?email_source=notifications&email_token=AIX4ZQGALVB7ZCOIB3KP3U3QGWKWXA5CNFSM4GCHL7PKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5JEVZI#issuecomment-525486821, or mute the thread https://github.com/notifications/unsubscribe-auth/AIX4ZQDSH45CFRA7TXGF7XTQGWKWXANCNFSM4GCHL7PA .
-- Jason Lacam
@voxitme perhaps, if you don't mind, you could just do a quick test and then switch back to your other app? All you'll need to do is set QK as your default, send a text message to yourself, and see if you get it
The thing is that I remember it was sometimes long to replicate this bug. Sometimes I could receive SMS correctly during days, and randomly, the bug was reappearing for 2 or 3 messages, and then vanished again for some days and so on... So I think a simple test with self sent messages won't be sufficient and concluding.
Le mercredi 28 août 2019, Moez Bhatti [email protected] a écrit :
@voxitme https://github.com/voxitme perhaps, if you don't mind, you could just do a quick test and then switch back to your other app? All you'll need to do is set QK as your default, send a text message to yourself, and see if you get it
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/moezbhatti/qksms/issues/1336?email_source=notifications&email_token=AIX4ZQDRJ3O5CYJQ4LNPWDDQGZFMDA5CNFSM4GCHL7PKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5KTI6I#issuecomment-525677689, or mute the thread https://github.com/notifications/unsubscribe-auth/AIX4ZQGBWH6ZD4CQSIGYTL3QGZFMDANCNFSM4GCHL7PA .
-- Jason Lacam
Hello there !
I'm using the 3.6.8 F-Droid build of the app since yesterday (with the messages stock app disabled) and it seems to be working fine now. I didn't notice any trouble when sending/receiving messages. Nice work, thank you !
@Leroux47 that's awesome! How often was the issue happening for you previously?
Well, honestly when I noticed the issue in past November, I first disabled QKSMS to use the stock app instead, waiting for a fix. Then I switched back to it, letting the stock app enabled, having no trouble at all with that. But before using the 3.6.8 build, I encountered the issue everytime I received a message, which was really annoying.
Hi Moez, thanks for your commitment to resolution of this issue! I'm also trying the 3.6.8 F-Droid build now. No lost messages after install but will need several days to confirm the problem is gone for good.
OK, subjectively 3.6.8 works better than previous problem versions for me in the sense that if you open the app manually it seems to receive new SMS messages without issues. Unfortunately, after not using QKSMS for a day or so, incoming SMS messages start to be lost until it is manually started. (I suspect some phone vendor background service might kill unused apps after some time to reduce memory pressure, and this is not configurable anywhere. Presumably, it makes an exception to certain important system apps by default.) Therefore, it seems I'm still stuck with the default Messages app.
The issue is still here on Android Q (GSI) on Oneplus 6. Default SMS app (AOSP) is enabled and QKSMS is set as default SMS app.
I sent to myself a bunch of messages in a row containing only the single word "test":
- 11 text messages sent
- 9 received messages written in the database
- but 11 delivery reports received.
I don't think so, since they are not even written in the main SMS database (switching back to the default SMS app doesn't make them reappear) :/
I've just encountered the same problem after using QKSMS without issue for a long time. Logcat revealed this line when a SMS was received:
BroadcastQueue: Permission Denial: receiving Intent { act=android.provider.Telephony.SMS_DELIVER flg=0x18000010 cmp=com.moez.QKSMS/.receiver.SmsReceiver (has extras) } to com.moez.QKSMS/.receiver.SmsReceiver requires android.permission.RECEIVE_SMS due to sender com.android.phone (uid 1001)
I've checked in App settings and SMS permission was enabled for QKSMS. I've switched it to disabled and enabled again, and it seems to resolve the issue.
I have recently seen an Android pop-up regarding some permissions being automatically disabled for some apps. I don't recall but it might have been about QKSMS. All in all it seems like an OS bug, android shouldn't sneak in and disable the SMS permission for the main SMS app. I'm using a crdroid ROM so it might be their bug.
