Andrew Gunnerson

You might have to ask the developer of your ROM about that. I'm not too familiar with what's required at the ROM and firmware level for supporting call recording.

Hmm, is it possible for the cloud sync to only delete the contents, but not the folder itself? It is not possible for BCR to recreate the folder due to...

Thanks for bringing this up--I didn't realize other projects have shown interest in this. However, I don't plan on relicensing BCR at this time. I intentionally choose GPLv3 for apps...

Glad to hear it's working on one device at least! You'll probably need to ask the developers of the NamelessOS ROM to see if they have any recommendations.

@Deathwish98 Can you post the output again but with `ls -lZ` (instead of just `ls -l`)? And what symptoms are you seeing? Does BCR not show up in the app...

Glad to hear you got it working! > the apk inside it didn't have 644 permission and maybe that could have been the issue in Nusantara as well . I...

Interesting. If you can grab `/tmp/recovery.log` via adb after a failed attempt, I can try and fix it.

Interesting. `rm -rf` is supposed to silently ignore `ENOENT` (No such file or directory) errors. I added a small workaround for it. Please give this debug build a try: [BCR-1.20.r3.gba47509-debug.zip](https://github.com/chenxiaolong/BCR/files/9690953/BCR-1.20.r3.gba47509-debug.zip)...

``` /system_root | /dev/block/mmcblk0p24 | Size: 3023MB Used: 1626MB Free: 1397MB Backup Size: 1626MB Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_Available_in_GUI IsPresent Mount_Read_Only ``` Hmm, so TWRP doesn't mount `/system_root` as writable....

Please grab `/tmp/recovery.log` via `adb pull` after attempting to flash through recovery.