-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ColorOS Call Recorder Support #100
Comments
Here's is the example: |
No, it doesn't actually work. One question: the first placeholder in your pattern is |
Thanks a lot!
It just works. The test result can write the phone number into caller_name and contact_name. |
Update. I've changed |
That feature was not released yet, sorry.
My question is: is the first placeholder always a phone number? Or it's a phone number only when no contact name is associated with the caller (and, in this case, it's replaced with contact name)? In the first case, filenames are always like this:
otherwise, when receiving a call from a known contact, they could be like this:
If it's always a phone number, it's better to use |
The situation is the latter one.
Now I see it. Sorry for my understanding. |
Nevermind, that was my first thought, but I needed a confirm 😉 So, the final ColorOS pattern will be: |
Thanks! |
One more question, why these {caller_name}, {contact_name} and {call_log_name} has a same note: Caller name: any character? |
Nothing relevant, it's some kind of "hystorical" reason.
Well done, thanks. |
Just released v.1.7.1 with both this feature and your Chinese (simplified) translation |
Hi Developer.
I've just known the BCR-GUI have supported Huawei Call Recorder's File Pattern.
Here's are the ColorOS's one: (MP3 file format)
^{contact_name}-{date:year}{date:month}{date:day}{date:hours}{date:minutes}
The only difference is this placeholder {date:year} should be 2 digits instead of 4. (I wonder if that works without correction)
Thanks!
The text was updated successfully, but these errors were encountered: