-
Notifications
You must be signed in to change notification settings - Fork 148
Frequently Asked Questions
First, please disable all battery optimizations, enforced by your OS. This will generally solve the problem. If it doesn't, please report an issue. For more information, see Don't Kill My App.
This is most likely a compatibility issue with Google Messages and is related to RCS.
Occasionally, when solving an issue, the developers will ask for logs of the issue. These can be collected in multiple ways. On Graphene OS, after the issue has been reproduced, head to the app settings page, and tap Collect App Logs. On other versions of Android, you can use adb with this command: adb shell logcat | grep dev.octoshrimpy.quik
This is most likely caused by the Auto-compress MMS image attachments setting. We recommend trying different amounts of image compression to see if this solves the problem. If this doesn't work, please open an issue.
Currently it is not supported. There are many technical challenges to implementing RCS, including getting access to the RCS servers, and developing an application that implements all the required standards and features. Please see #124, where this issue is being tracked.
This is a planned feature that is on the roadmap for the near future. Any implementation will most likely involve using Deku SMS's system, of double-ratchet encryption, originally implemented by Signal.
This is planned, and should be implemented soon.
Currently, we recommend using KDE connect. It is also planned to develop some sort of web/desktop application. However, this is a massive undertaking and will take time.
Please see planned features and all issues with the enhancement label.
Since QUIK version 4.3.2, a dedicated worker was created in order to receive messages. Unfortunately, on Android 12 and older, a persistent notification is required to keep this worker running in the foreground, which prevents the system from killing the service and dropping messages.