You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If it is checked, the message is sent using 7 instead of 0.
Not sure if I understood you right, you mean instead of a 7-Bit / 160 char text you want to send 16-Bit / 70 chars Unicode SMS messages ?
If so, I think it isn't such a big effort, and it would make sense to add this for all message types.
We could label this an enhancement, but I will be working on some other project I plan to host on put online in the next weeks.
For now I am planning to add some more info about usage and installation this weekend. Will also try to find out if the android license allows publishing an built ready-for-install-apk using an extracted telephony jar.
If you have more feature requests or ideas, feel free to open issue.
@romankh I was talking about the prefixed text on the message.
An unicode message looks like this allyourmessagesarebelongtous|7|Lorem ipsum ⭐ when sent using HushSMS, while an ordinary message looks like allyourmessagesarebelongtous|0|Lorem ipsum.
I have no idea about what it says about the implementation, sorry.
Good to know, I wish you luck with this and the other project.
FlashSMS has a checkbox to select wether you want to send a Class 0 using Unicode or not.
If it is checked, the message is sent using 7 instead of 0.
The text was updated successfully, but these errors were encountered: