Fixed
Status Update
No update yet.
Comments
rk...@google.com
rk...@google.com
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
Looks like this is fixed in master, presumably as part of the synchronization with the chromeos gcc. Won't make r11, but will be in the next update.
rk...@google.com
Is this fixed? I am seeing linker error on log2 while using ndk-r13b.
ga...@gmail.com
log2 wasn't available in android until jb-mr2 (android-18).
Also possible that the problem you're seeing is just more ofhttps://github.com/android-ndk/ndk/issues/82 . Essentially, we have to build gnustl against the minimum supported version (currently android-14), so it can't make use of anything that was present in that version. We're working on fixing this for libc++ with a better libandroid_support, but that's still WIP.
Also possible that the problem you're seeing is just more of
ga...@gmail.com
Yes, I agree. 0x147 is something similar, but correct one is 0xd1
rk...@google.com
an...@google.com
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