Issue #1767
closedSMS not received / Replicant 6.0
100%
Description
Every-time the message length is > 160 characters, the SMS is never received by my contacts.
I also installed Silence IM to test & confirm and same behavior than the default SMS application.
This is 100% reproducible.
Something else which is not 100% reproducible (but very close to) is a random behavior where some messages
with special character like 'ê' or 'ç' or accent or "-" and less than 160 characters are never received either.
Removing the special character and sending the same message works (received by my contacts)
Where it is difficult to find a logic is that writing only a couple of letters with a special character works !
Like: "ça va" as a whole message works...
Going back to Stock ROM on the same phone / same SIM and all the issues gone, no issue on 4.2
Updated by Loic Dachary almost 10 years ago
For the record this is using the Replicant 6.0, at least for the Samsung Galaxy S3 instructions
Updated by Wolfgang Wiedmeyer over 9 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
- Resolution set to fixed
Fixed with this commit: https://code.fossencdi.org/hardware_ril_samsung-ril.git/commit/?h=replicant-6.0&id=3935ea6f21e4f42024a025de2cc3fb6bc1816002
As discussed on irc, the issue with special characters was very likely only happening with multipart messages, so it's also fixed with the commit.
Updated by Wolfgang Wiedmeyer over 9 years ago
The previous mentioned commit didn't fix the issue reliable. Found a much easier solution which should finally fix it:
https://code.fossencdi.org/hardware_ril_samsung-ril.git/commit/?h=replicant-6.0&id=8fc4ebed2b2fd094f09f329fd284b4ce916271c7
Updated by la belette over 9 years ago
Wolfgang many thanks !
I am impatient to see your next version with all theses bug solved :)
Updated by Wolfgang Wiedmeyer over 9 years ago
I released the next version that has this issue fixed. See the updated forum post.
Updated by la belette over 9 years ago
cool :)
I guess there is a typo it is build date: 8.1.17 instead of build date: 8.1.16 ?
So the zip is from today right ?
Updated by Wolfgang Wiedmeyer over 9 years ago
belette belette wrote:
I guess there is a typo it is build date: 8.1.17 instead of build date: 8.1.16 ?
So the zip is from today right ?
Yes, of course :)
Thanks, should be fixed now!