Template for Call Recorder app (com.github.axet.callrecorder) from F-Droid app store

[nicolas2957]

Hello @nicorac,

First, thanks for your app, it is welcome for this accessibility issue.

Is your feature request related to a problem? Please describe. I have the Call Recorder app (com.github.axet.callrecorder) from the F-Droid app store, and already have hundreds of phone calls saved with a specific pattern that I can't match with the JS regexp placeholders available in your app. I know it's a bit lazy not renaming all my files to one of the preconfigured templates of the bcr-gui app but maybe there is a solution in between.

Here are three examples for my naming pattern:

20200101T010101 ↑ +33611111111 (Mum).ogg
20200102T020202 ↓ +262622222222 (John Smith).ogg
20200103T030303 ↓ +33612345678 (0612345678).ogg

I tried these rexexp, none worked:

^{date:year}{date:month}{date:day}T{date:hours}{date:minutes}{date:seconds} [↑↓] {phone_number} {contact_name}
^{date:year}{date:month}{date:day}T{date:hours}{date:minutes}{date:seconds} {*} {phone_number} {contact_name}

Have I did something wrong ? Please guide me. Otherwise is it possible that the special charaters are messing with the regexp ? Thank you in advance !

[nicorac]

Just tested your first sample filename 20200101T010101 ↑ +33611111111 (Mum).ogg

against your first RegExp pattern ^{date:year}{date:month}{date:day}T{date:hours}{date:minutes}{date:seconds} [↑↓] {phone_number} {contact_name}

and it worked:

Please double check that you've inserted the exact pattern you've posted (no extra whitespaces). Otherwise there could be an issue with ↑↓ chars on Android SAF storage on your side.

The best fix is to avoid all non-ASCII chars in filenames (except the ones strictly needed by your culture). Meanwhile you could try to workaround it with this pattern (it also works on my side): ^{date:year}{date:month}{date:day}T{date:hours}{date:minutes}{date:seconds} \W {phone_number} {contact_name}

\W (uppercase means) "any non-word character"

[nicolas2957]

You are correct, both RegExs pattern works (arrows and \W), I don't know why it didn't when I've tried it for couple hours... Probably as you said a mistakenly placed whitespace, probably just a reboot was needed...

Problem solved.

The arrows down an up are not displayed so i f I understand correctly, if call direction is not "in;out;conference" it won't be displayed, is this correct ?

[nicorac]

if call direction is not "in;out;conference" it won't be displayed, is this correct ?

Those are the keywords actually recognized; I could add some other words but I' like to avoid using "problematic" unicode chars 😉