Fixed
Status Update
Comments
rk...@google.com <rk...@google.com>
rk...@google.com <rk...@google.com> #2
Hi, sorry for the trouble. I am working on improving our radio HAL. Unfortunately, it will take a while because it is very large. Please do not send non-ASCII characters in SMS.
ga...@gmail.com <ga...@gmail.com> #3
Hi, I don't know if it may be implemented as quick fix on the actual code, but looks like Ñ is the only alphabet letter having the issue (at least between ones widely used within GSM 03.38 GSM 7-bit).
I've tried with ÄÇÖÜàèéìòùäñöü and all of them are correctly sending only one SMS and not two concatenated.
I've tried with ÄÇÖÜàèéìòùäñöü and all of them are correctly sending only one SMS and not two concatenated.
rk...@google.com <rk...@google.com> #4
I've tried with ÄÇÖÜàèéìòùäñöü and all of them are correctly sending only one SMS and not two concatenated.
I see, maybe we missed that one Unicode somewhere then. Could be easier to fix then. I will take a look this week. Thank you for pointing this.
ga...@gmail.com <ga...@gmail.com> #5
Just to get the full picture, I've tested with all characters included here https://en.wikipedia.org/wiki/GSM_03.38 both in Basic Character Set (they should take 1 char of the 160) and Basic Character Set Extension (they should take 2 char, first is ESC prefix) and the only one causing the issue is Ñ
Sending a character outside that set, like á, message it's correctly split into 2 parts, first one of 70 chars as expected.
Sending a character outside that set, like á, message it's correctly split into 2 parts, first one of 70 chars as expected.
ga...@gmail.com <ga...@gmail.com> #7
Yes, I agree. 0x147 is something similar, but correct one is 0xd1
rk...@google.com <rk...@google.com>
an...@google.com <an...@google.com> #9
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Emulator 35.4.6 Canary
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
Description
This is the correct behaviour in case characters of UCS-2 Encoding are used, but not for standard characters included into GSM 03.38
Ñ character is included into GSM 03.38 GSM 7-bit default alphabet:
In fact with a real phone only one SMS with 97 characters is received.
Code is pretty easy, see attached screenshots, with $ everything is ok, while with Ñ smsMessages array is made of 2 items
For privacy and security reasons I cannot attach more than this and full log files, but I think it may be enough because it's quite simple to reproduce.
Tested with emulator API 31 and API 35, both have the issue.
Studio Build: Build #AI-242.23726.103.2422.12816248, built on December 18, 2024
Version of Gradle: 8.9
Version of Java: 11
OS: Windows 11 Professional