Mudi V2 character encoding issues

Since the 4.8.3 beta Mudi V2 has some PIM(?) related issues. I thought it does not read the SIM's phonebook, but now it shows the contact name instead of the phone number. FYI: My private numbers are stored in the SIM memory and the GUI now shows the contact name. But what's strange that it cannot handle diacritic letters like "à" or "è" while these are not even Unicode characters.

And the other half of my report is related with messaging. Now it replaces diacritic letters with greek letters like "ΰ" or "φ". My language is using latin letters strictly, so it is a weird issue.

Hi, the SMS sender displayed on the web GUI should be the phone number.
And the issue that SMS does not show letters à or è, this might be related to the content of the text message. I did not reproduce the problem. Can you provide the complete SMS message along with some screenshots related to the errors to check? Thanks

Now I had time to test things. Here's a screenshot:

Explanation:
I sent diacritic letters which are common in my language. Then I sent diacritic letters which are commonly used by providers in my country to meet the restricted charset to aware of the limitations. Before I sent the messages I changed the charset on the sender phone. As you see the issue comes up when I sent the messages with restricted charset support. This encoding issue only appears on the router. Phones are not affected. So it is not something provider related.

Providers commonly use the restricted charset for many reasons.

Oh and yeah. The number thing... I did an investigation on it.

So if the "own number" (AT+CPBS="ON") is not empty on the SIM the interface will read that and will display the number or the name of that record. First I tried a Three UK card and looks like they use this record but for some reason they don't upload the number, but add a record with a name/label like "My number". This is what I saw on the interface. Then I checked it via AT with AT+CNUM:

+CNUM: "My Number","",129
OK

This is why it showed only the name/label but not the number. I also tested a different card and I can confirm that this is completely independent from the SIMs. I don't know what's changed since the last firmware update, because I never ever seen any names/labels before just the numbers.

Conclusion:
If there is a record with a name/label in the SIM card's EF_MSISDN entry (own number) then the GUI will display that. If it contains a label like "My number", it will shows only that. If the record contains just the number, then the GUI will shows that. If the entry is completely entry then the GUI will won't show anything. And this entry is also infected about this encoding issue what I described above. The GUI will show different letters if the name/label contains diacritic letters.

Since this issue somewhat related with my other report I turned on the device share.

Regarding the SMS displays the contact name instead of the phone number, is it possible to resend a message to the router, and then see if it's still displayed the contact name. If yes, export the router log from SYSTEM ->Log page and send to us to check.
Thanks

How do you mean? I need a bit more explanation.

I'm talking about the fact, that since the last beta (since the GUI censors the infos by default) the GUI shows the SIM cards "own number" entry and displays it's own name/label if that is stored on the card. For example I always store my own numbers on every private SIM cards.

Like this:

AT+CPBS="ON"
AT+CPBW=1,"+001234567890",129,"My Number"

Result:

This is very common way. Providers store numbers like this and now the GUI don't show the number itself, but the number's name/label, because the record contains it. And the GUI for some reason prefers to show the name instead of the number itself which is more relevant in this case.

But if the provider just add the number itself:

AT+CPBS="ON"
AT+CPBW=1,"+001234567890",129,""

The result will be this. It will displays the number:
Képernyőkép 2025-09-24 13-37-30

This issue of course a separate issue. But why I referred to the encoding issue is that the GUI struggle to display the name/label of the number if it contains diacritic letters:

For example:

AT+CPBS="ON"
AT+CPBW=1,"+001234567890",129,"áéíóőúű"

Or:

AT+CPBS="ON"
AT+CPBW=1,"+001234567890",129,"àèìòù"

And then I tried to check what happens if I save a contact with diacritic letters. Sadly for some reason the modem cannot access SIM phonebook. Pretty bad. But I can store contact in the modem itself. Looks like it also affected and cannot display diacritic letters if I check it via AT terminal.

Thanks for your detailed information. We are verifying this issue.

Hello @ViBE
The module parameters and the web GUI are incompatible after using the AT command AT+CPBS and AT+CPBW. Therefore, you can't send message and get error "Illegal parameter"

AT+CPBS="ON"
AT+CPBW=1,"+001234567890",129,"My Number"

You can revert it to normal using the following AT commands:

AT+CPBS="ON"
AT+CPBW=1

Similarly, the phone number being displayed as garbled text is also a incompatibility.
problem. Thanks

We haven't gotten much feedback on this, need to evaluate whether to implement compatibility

Please do. I mean the message sending is kinda implemented. The UI is there. But what is the goal with it if users cannot use it because it is half baked? What is the purpose? The encoding issue is globally affects on PIM features and it is not the biggest issue. However it would be good to see fully working PIM functions like a phonebook/contact management. But many users just ignore issues and there will be lack of feedbacks on this too, sadly.

Btw my share ended yesterday. Do you still need my Mudi for any investigations of the reported issues?

Hi, the remote access is not required currently. Thanks