kitsumed/ShizuCallRecorder

Checklist I have searched existing issues and discussions and this is not a duplicate. I am suggesting a new feature or enhancement for ShizuCallRecorder itself, NOT for Shizuku or another app. I have read the project README.md and CONTRIBUTING.md. I have read the application docs. Is your feature request related to a problem? Please describe. Hello, I am a regular user of your app, and I am writing to suggest an improvement. Currently, the app does not offer any feature for exporting or backing up user settings. However, when switching smartphones, this requires reconfiguring everything manually, with the risk of losing personalized settings. Describe the solution you'd like I would therefore like to suggest two ways to improve this: Add a feature to back up settings - ideally one that runs automatically and periodically (with a frequency configurable by the user) - rather than just a simple manual export. Allow users to freely choose the destination folder for the backup file,

Checklist I have searched existing issues and discussions and this is not a duplicate. I am suggesting a new feature or enhancement for ShizuCallRecorder itself, NOT for Shizuku or another app. I have read the project README.md and CONTRIBUTING.md. I have read the application docs. Is your feature request related to a problem? Please describe. Hi! First of all, thank you for ShizuCallRecorder — it works really well, especially together with GrapheneOS and Shizuku. I have one feature request regarding saving recordings to cloud storage. Currently, when I select a folder located on Google Drive, the app creates the recording file but sometimes leaves it at 0 KB. It seems that writing the audio directly through Android's storage framework/cloud provider is not handled reliably. It would be great if you could improve cloud storage support so that recordings can be saved/synced reliably to cloud folders. Alternatively, it would be awesome to have built-in support for several cloud s

Checklist I have searched existing issues and discussions and this is not a duplicate. I am suggesting a new feature or enhancement for ShizuCallRecorder itself, NOT for Shizuku or another app. I have read the project README.md and CONTRIBUTING.md. I have read the application docs. Is your feature request related to a problem? Please describe. Running a central Shizuku manager service introduces a shared attack surface on non-rooted devices, as Shizuku acts as a centralized authority that can grant elevated ADB shell permissions to multiple applications. For privacy-hardened setup threat models, relying on a shared Shizuku bridge requires keeping Shizuku running globally, exposing the system to potential cross-app permission abuse if another app requests/exploits Shizuku access. Currently, the app strictly relies on Shizuku, forcing users into this shared model. Describe the solution you'd like I'm thinking of an alternative, standalone backend option (such as "Direct Local ADB /

Checklist I have searched existing issues and discussions and this is not a duplicate. I am suggesting a new feature or enhancement for ShizuCallRecorder itself, NOT for Shizuku or another app. I have read the project README.md and CONTRIBUTING.md. I have read the application docs. Is your feature request related to a problem? Please describe. At low bitrates, e.g. AAC-LC or Opus at a nominal 16 kbps, the resulting recording is of acceptable quality, yet it sounds robotic and somewhat dynamically compressed. The average 3 or 4 minutes recording bitrate actually settles around 22 kbps for AAC-LC and 27 kbps for Opus (despite the selected rate was 16 kbps). Higher bitrates can obviously fix the issue at the expense of storage space. Describe the solution you'd like Add alternative codecs, such as xHE-AAC, HE-AAC v2, or Codec2, with the aim of delivering speech recordings at high quality yet low bitrates, thereby containing the storage space needed on the device. Describe alternativ

Checklist I have searched existing issues and discussions and this is not a duplicate. I am suggesting a new feature or enhancement for ShizuCallRecorder itself, NOT for Shizuku or another app. I have read the project README.md and CONTRIBUTING.md. I have read the application docs. Is your feature request related to a problem? Please describe. I've enabled record all calls. So what it does it records both Incoming and Outgoing call from Both Phone calls and WhatsApp calls (WhatsApp call recording is not working properly-Thats not my complaint). That makes the storage flood. WhatsApp calls shouldn't be recorded at all. Even if it records. It capture only from oneside. So I don't want to record to auto start for WhatsApp calls. Describe the solution you'd like So the soultion I'd like is like creating a new section for blocklist/whitelist apps. So if a incoming/outgoing happens from blocklisted apps, It shouldn't start call records Describe alternatives you've considered No respons