Speed Dial strips * and # from USSD codes

[JakeSFR]

Checklist

• I can reproduce the bug with the latest version given here.
• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• I have read and understood the contribution guidelines.

Affected app version

1.7.0

Affected Android/Custom ROM version

Android 15

Affected device model

moto g15 power

How did you install the app?

F-Droid / IzzyOnDroid

Steps to reproduce the bug

0. Have a phone with this issue (it's becoming a theme of my bug reports).
1. Add a new contact with a number like, e.g.: *123#.
2. Add the newly created contact to one of the Speed Dial slots.
3. Open dial pad and call that contact by holding the appropriate slot number.

Expected behavior

USSD code *123# should be dialed.

Actual behavior

123 is being called.

Screenshots/Screen recordings

No response

Additional information

No problem on Galaxy A12.

Seems related to #235, OP's phone is also Motorola.
However, it's different, because OP's *86 actually dials (an invalid) USSD code for me, but e.g. *123 calls 123 again.

Weird...

[Aga-C]

I was able to reproduce it on OnePlus 8 Pro, OnePlus 9 Pro, and even on an emulator, so I'd say it's strange that there's no problem on Galaxy A12.

Also, this problem isn't only with speed dial. When I choose a contact with USSD code from the list in the dialpad, it also strips * and #. Everything works fine on the contacts list, though.

[JakeSFR]

Ok, so I moved my SIM card back to A12, to make sure I wasn't hallucinating for the last couple of years, but nope - it still works there (*101# specifically).
Same version, 1.7.0.

So, it's even weirder than I thought. ;)

And yes, choosing the USSD contact from dial pad also doesn't work for me on Moto.

[naveensingh]

No problem on Galaxy A12.
I'd say it's strange that there's no problem on Galaxy A12

I have a theory. Samsung likely has a modified contacts implementation that is more "intelligent" about USSD codes. I found that a USSD contact created on a Samsung device works on every device (because they don't normalize/strip the special characters).

[JakeSFR]

Alright, fixed for me, thanks!

I noticed that Google Contacts also strips USSD codes while exporting contacts to .vcf, so despite all the bad things I could say about Samsung, they seem to be more sane after all.

[naveensingh]

Thanks for confirming!