Fixed
Status Update
No update yet.
Comments
rk...@google.com
rk...@google.com
Project: platform/frameworks/support
Branch: androidx-main
commit 16c5a4617aa5d0709ffe27cef015e001b31de79b
Author: George Mount <mount@google.com>
Date: Mon Apr 10 13:31:49 2023
Fix leak from ReportFullyDrawnExecutor
Fixes: 277434271
The runnable was not being removed immediately after the activity
was destroyed. This removes it when it becomes destroyed so that
it can be collected without delay.
Test: new test, exemplar test
Change-Id: Id2ff2311e16d89fc7309a6e99f302cf3e8d9d595
M activity/activity/src/androidTest/java/androidx/activity/ComponentActivityReportFullyDrawnTest.kt
M activity/activity/src/main/java/androidx/activity/ComponentActivity.java
https://android-review.googlesource.com/2530063
Branch: androidx-main
commit 16c5a4617aa5d0709ffe27cef015e001b31de79b
Author: George Mount <mount@google.com>
Date: Mon Apr 10 13:31:49 2023
Fix leak from ReportFullyDrawnExecutor
Fixes: 277434271
The runnable was not being removed immediately after the activity
was destroyed. This removes it when it becomes destroyed so that
it can be collected without delay.
Test: new test, exemplar test
Change-Id: Id2ff2311e16d89fc7309a6e99f302cf3e8d9d595
M activity/activity/src/androidTest/java/androidx/activity/ComponentActivityReportFullyDrawnTest.kt
M activity/activity/src/main/java/androidx/activity/ComponentActivity.java
ga...@gmail.com
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.activity:activity:1.7.1
rk...@google.com
Update
ga...@gmail.com
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!
an...@gmail.com
le...@gmail.com
Gracias
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