Fixed
Status Update
No update yet.
Comments
el...@google.com
ap...@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.
pr...@google.com
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.
wo...@gmail.com
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.
Description
The room-paging KMP integration on initial load starts an 'immediate' transaction which grabs a 'write' lock immediately on a reader connection which is illegal:
Seehttps://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:room/room-paging/src/commonMain/kotlin/androidx/room/paging/LimitOffsetPagingSource.kt;l=112-113