fossifyorg/messages

An easy and quick way of managing SMS and MMS messages without ads.

messages's Issues

Search individual conversations

Checklist

• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.
• I optionally donated to support the Fossify mission.

Feature description

SimpleMobileTools/Simple-SMS-Messenger#218: At the moment you can globally search messages. It would be nice if you could search individual conversations (search button within conversation view).

For example, how it is in Signal.

Why do you want this feature?

Searching in conversation will refine and facilitate many more searches than globally. It will also speed things up, as there will be far fewer messages to search through.

Additional information

There is an unimplemented pull request in Simple Mobile Tools (SimpleMobileTools/Simple-SMS-Messenger#665) that would probably add this.

[Feature Request] Enable emojis

Checklist

• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I have read the FAQ and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the feature request will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.

Is your feature request related to a problem? Please describe.
Unable to send emoji in text messages as they are just not available for my use in this app.

Describe the solution you'd like
I would like to be able to use emojis in my text messages.

Describe alternatives you've considered
I can copy and paste emojis from other apps, but that's not enjoyable.

Additional context
N/A

RCS?

Is RCS possible?

Import & Export blocked keywords

Checklist

• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I have read the FAQ and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the feature request will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.

Is your feature request related to a problem? Please describe.
The app has "import & export blocked numbers" features in the "blocked numbers" settings, but this feature is missing in the "blocked keywords" settings.

Describe the solution you'd like
Add "import & export blocked keywords" features in the "blocked keywords" settings.

[Feature request] Better showing of SMS subject

Checklist

• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I have read the FAQ and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the feature request will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.

Is your feature request related to a problem? Please describe.
I only see subject of sms in preview when sms wasnt already opened

Describe the solution you'd like
show subject above sms text, maybe with undercut and highlighting? I'm not sure

SMS content sender only

Checklist

• [ V] I can reproduce the bug with the latest version.
• [V ] I made sure that there are no existing issues - open or closed - to which I could contribute my information to.
• [ V] I have read the FAQ and my problem isn't listed.
• [V ] I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• [ V] This issue contains only one bug.
• [ V] I have read and understood the contribution guidelines.

Describe the bug
I can see SMS body but option is set to sender only

To Reproduce
Steps to reproduce the behavior:

1. Settings
2. Notifications
3. Sender Only
4. Lock the screen
5. Get a new SMS
6. Scroll down to Android shortcuts
7. You can see sms body even if config set to sender only
8. See error

Expected behavior
I'd like to hide sms body even if screen is locked

Screenshots
If applicable, add screenshots to help explain your problem.

Device info (please complete the following information):

• Model: Pixel 7
• OS: LineageOS 18.1
• App version 1.0.0

Additional context
I've set Settings > Notifications > Sender only but when screen is locked and scroll-down and scroll-up can still view the sms content.

[Feature request] Being able to see "sent time" of received SMS

Checklist

• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.
• I optionally donated to support the Fossify mission.

Feature description

I would like to be able the see the "sent time" in the message details as done in my default SMS app (incuded in the box fromLineageOS/CrDroid, a very basic one)

if possible, it may be good to see the "sent time" without going on messages detailed. Maybe for instance something in parentheses when received and sent time are different ?

Ex :

exemple of a message
(sent at < insert a date >)

Why do you want this feature?

There is a difference between "sent time" and "received time". It is the case when we use airplain mode for instance. It gives more context to received messages.

Additional information

No response

force app to send sms only from one sim card

Checklist

• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.
• I optionally donated to support the Fossify mission.

Feature description

an option to force app to use only one sim cards

Why do you want this feature?

app sometimes changes to 2nd sim card (as a result of missclicking or some bug) which results in recipent's confussion and high charges. I use that sim card only for data and i would like to disable sending sms from it.

Additional information

No response

Private Conversation

Checklist

• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.
• I optionally donated to support the Fossify mission.

Feature description

Mark Conversation as Private

• Hide the Conversation From Conversation list
• Add a private Conversation list
• Open the private list by Passcode or Biometric
• Hide the new message Details on the notification and Lock screen

Why do you want this feature?

Have more privacy on specific Conversations

Additional information

No response

"unread messages" filter

Checklist

• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.
• I optionally donated to support the Fossify mission.

Feature description

Add a filter view showing unread messages only, either via the three-dot menu or via a pulldown like how Signal does it¹:

filter-release-notes.mp4

or even better: both!
¹ Signal actually does both, which is the best IMO

Why do you want this feature?

filtering for unread messages is an important decluttering tool in any messanger.
even if one only uses SMS to get texts from the bank and the insurance company (which is actually the case for me), such a filter is still very useful.

Additional information

since Signal is AGPL, its license is compatible with Fossify and code can be borrowed without worry. whether the code itself is compatible with how the messenger is written is another question though...

Theme isn't applying on the Action Bar.

Checklist

• [✅] I can reproduce the bug with the latest version.
• [✅] I made sure that there are no existing issues - open or closed - to which I could contribute my information to.
• [✅] I have read the FAQ and my problem isn't listed.
• [✅] I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• [✅] This issue contains only one bug.
• [✅] I have read and understood the contribution guidelines.

Describe the bug
Whenever you long-press on a message or conversation, an Action Bar appears. But the problem is that the bar doesn't follow the custom theme chosen by the user. So, please fix this.

To Reproduce
Steps to reproduce the behavior:

1. Open Fossify Messages app.
2. Long-press on any conversation, then notice the Action Bar.
3. Open any conversation & long-press any message, then notice the Action Bar.

Note: Before following above steps, you should already be using a pure black AMOLED Theme like me.

Expected behavior
Whatever colour user has chosen in "Background Colour" & "Primary Colour" should also get applied to the Action Bar.

Screenshots

Device info (please complete the following information):

• Model: Realme 7 Pro
• OS: Android 12 (skin name is RUI 3.0)
• App version: v1.0.0

Additional context
Not really, wrote everything above.

Badge Icon Doesn't Show Up When I Change App Icon Color

Checklist

• I can reproduce the bug with the latest version given here.
• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• I have read and understood the contribution guidelines.

Affected app version

1.0.0

Affected Android/Custom ROM version

Android 10

Affected device model

LG355DL

How did you install the app?

F-Droid / IzzyOnDroid

Steps to reproduce the bug

When I go to settings and change the icon color, the badges for new messages disappear.

1. Go to Settings
2. Click Customize colors
3. Click App icon color
4. Change color to desired color

Expected behavior

I expected the icon badges to stay there no matter what color I changed to.

Actual behavior

No badge numbers when getting a new message after changing the app icon color.

Screenshots/Screen recordings

No response

Additional information

No response

[BUG] Subject isnt in UTF-8

Checklist

• I can reproduce the bug with the latest version.
• I made sure that there are no existing issues - open or closed - to which I could contribute my information to.
• I have read the FAQ and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• I have read and understood the contribution guidelines.

Describe the bug
title

It should say "Nová zpráva od"

To be clear I'm using English (uk) as system language and this is Czech

To Reproduce
Steps to reproduce the behavior:

1. Open the app
2. See message with default text "New message from xxxxxxx" isnt in UTF-8.

Expected behavior
It should use UTF-8

Screenshots

Device info (please complete the following information):

• Model: xiaomi redmi note 8 pro
• OS: Android 11
• Version: 5.19.3

Group messages error

Checklist

• I can reproduce the bug with the latest version.
• I made sure that there are no existing issues - open or closed - to which I could contribute my information to.
• I have read the FAQ and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• I have read and understood the contribution guidelines.

Describe the bug
Trying to create a Group Massage ends up with an "An unknown error occurred"

To Reproduce
Steps to reproduce the behavior:

1. open the app
2. Click on Plus/+ to create a new message
3. select a contact
4. click on the button to add more contacts
5. type the phone number or the name of the contact and select the contact
6. press the accept/check button

Expected behavior
It should create a new group message with the selected contacts, but instead a popup with the message "An unknown error occurred" is shown and the app gets back to the contacts selection list (point 3).

Device info (please complete the following information):

• Model: Xiaomi Redmi 5
• OS: Android 8.1
• App version: 1.0.0

Additional context
Connection with #40

Add swipe to archive/delete for the SMS application

Checklist

[ x] I made sure that there are no existing issues - open or closed - to which I could contribute my information.
[x ] I have read the FAQ and my problem isn't listed.
[x ] I have taken the time to fill in all the required details. I understand that the feature request will be dismissed otherwise.
[x ] This issue contains only one feature request.
[x ] I have read and understood the contribution guidelines.
Is your feature request related to a problem? Please describe.
The simple sms application requires a long press to select and fumbling through the menu to archive/delete. The ability to swipe left or right is a more common gesture and imo is more intuitive.

Describe the solution you'd like
It would be great to have the left or right swipes configurable to either archive or delete.

Describe alternatives you've considered

Additional context

Add setting to make phone numbers clickable

Checklist

• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I have read the FAQ and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the feature request will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.

Is your feature request related to a problem? Please describe.
So, if I miss a call by being offline my provider sends me an SMS with the missed number and some other information regarding the missed call, e.g. date, time. In most cases, I do not recognize the number. Therefore, in order to know whose call I missed, I have to enter the number into my dialer app and see which contact it is. Unfortunately, the number is not clickable, so I have to either copy the number or type it manually. Copying the number requires the following steps:

1. Long press the message
2. click 3 dots in the top right
3. click "select text"
4. select the number
5. copy to dialer app

In total, a minimum of 5 clicks is required to know which number tried to call me. In my optinion, this is not the easiest solution.

Describe the solution you'd like
Would it be possible to add a setting to make phone numbers clickable? In more detail, recognize the phone numbers as links and if someone clicks the number then the dialer app should open with the number already inserted. Furthermore, if someone would like to only copy the number or send an sms, make these options available by long pressing the clickable number.

Additional context
I was very very surprised to hear that the SMT suit was sold to a company with no advice. Therefore, I am delighted that someone is continuing the project - keep up the good vibes!

Can't send MMS, error code 5

Checklist

• I can reproduce the bug with the latest version given here.
• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• I have read and understood the contribution guidelines.

Affected app version

1.0.0

Affected Android/Custom ROM version

Graphene OS

Affected device model

Pixel 8 pro

How did you install the app?

None

Steps to reproduce the bug

Sending gif text results in cannot send, touch to retry. Then error code 5 pops up.

Expected behavior

Can't send Gifs

Actual behavior

Error code 5

Screenshots/Screen recordings

No response

Additional information

No response

Auto-set conversation name based on rules

Checklist

• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.
• I optionally donated to support the Fossify mission.

Feature description

Use keywords to set a conversation name, e.g. if a message contains "Your Amazon package with" OR "Details amzn(dot)com/orders" rename the conversation automatically from ###### to Amazon.

Why do you want this feature?

To make it more clear who texts are from by automatically replacing (or appending) the numbers with a user-customizable name based on text content.

Additional information

No response

Automatic messages backup

Checklist

• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I have read the FAQ and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the feature request will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.

Is your feature request related to a problem? Please describe.
Exporting messages manually is a bit tiring.

Describe the solution you'd like
Automatic backup as in Simple Calendar, with a selectable location, e.g. on an SD card.

Describe alternatives you've considered
None.

Additional context
Scheduling a backup would be great, e.g. at a specific time or while the phone is charging.

Simplify group messages creation

Checklist

• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I have read the FAQ and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the feature request will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.

Is your feature request related to a problem? Please describe.
Yes. Currently i'm not able to create a massage to multiple contacts.
After choosing the first contact (the app will enter the chat history of that contact, which does not make much sense if i'm planing to create a group chat), and then start adding other contacts (by typing it, instead of scrolling thru the list - which i also think is not ideal) when i press the accept button the app returns an error and does not create the desired group message.

Describe the solution you'd like
When we start up the app and after we go to the Plus Button to create a new chat/message we get to a list of contacts.
In this list of contacts we should be able to:

long press a contact to enter "selection mode" and be able to select multiple contacts

in order to create a group message.

Describe alternatives you've considered
there's no any good FOSS alternative that deals well with group messages that i know of. Only proprietary apps (i don't trust).

Additional context
An example from the Xiaomi group massage creation:

Problems receiving long text-only MMS messages - org-xmlpull error

Checklist

• I can reproduce the bug with the latest version given here.
• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• I have read and understood the contribution guidelines.

Affected app version

1.0.0

Affected Android/Custom ROM version

LineageOS 20

Affected device model

Xiaomi Poco F1, Motorola Moto g100

How did you install the app?

F-Droid / IzzyOnDroid

Steps to reproduce the bug

Problem occurs when you receive a (long) text-only MMS from a sender using a different messaging app.

Example:
Using Google Messages (updated Jan 18, 2024) send a long text message which gets converted to MMS due to it's length.
I first found out about this when I got a MMS from a stranger (so don't know the app they were using) and then asked a friend to test with me with their Google Messages app. Since we immediately recreated the problem I doubt Google's app is the only one causing the problem.

Problem only happens with text MMSs and not long SMSs. Since Goog's app was unable to produce a short text-only MMS only long text was tested. We tested MMS picture + text which did not trigger the error. Admittedly the text there was short. Unfortunately I cannot re-test.

If using Fossify-Messages to SEND with "combine long texts to MMS" the problem seems not to be there - but this may be due to reverse role (sender vs receiver).

Expected behavior

Application should be able to display such messages even if the sender's app uses different ~formating.

Actual behavior

When the problem occurs the received message may appear empty / or be displayed but it will always produce a org-xmlpull error message (see screenshots)

Screenshots/Screen recordings

Error in Fossify Messages:

QKSMS:

LineageOS's Messaging:

Additional information

One thing I noticed when re-opening these tests in other messaging apps (see attached images) -QKSMS and LineageOS's default "Messaging" is that the problematic MMS had a subject line displayed there "subject: MMS". Long text MMS produced Fossyfy did not have the subject. The sender did not write the subject their app produced it without their knowledge. Fossify does not show those subject lines.

It appears it's either the length of the text in MMSs or inclusion of the subject that produces the error. It also happens with only ascii characters as well if you're wondering.

Typing cursor

When phone goes into sleep mode while writing a message, typing cursor goes back to the beginning of the message.

Maybe this could be improved.

Many thanks for this app/fork.

Dearly.

Read me my texts!

(Was №794 of Simple Messenger)

Many years ago, I had a non-Android flip-phone that had a text-to-speech user preference. Since moving to Android, I have never found a way to command any SMS app, including Messenger, to pass incoming texts to TTS. When driving, with the phone in the "hands-free" holster required by local law, I'd prefer to hear every SMS immediately when it's received. Otherwise, even such an option on the long-press message menu would be welcome. (I imagine it would be "marked as read" after being read TO me.)

[Feature request] Option to write sms with subject

Checklist

• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I have read the FAQ and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the feature request will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.

Is your feature request related to a problem? Please describe.
other sms apps can write sms messages with subject

Describe the solution you'd like
same as in google sms, in menu option to show second text field for the subject. dont remember this option for chats

Additional context
this doesnt have high priority

[Feature request] End-to-end SMS encryption

Checklist

• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.
• I optionally donated to support the Fossify mission.

Feature description

In the interest of security, it's be nice to have the ability to have end-to-end encryption for SMS messages. There's various apps that perform E2EE via the network, but (with the exception of Silence, which is abandoned) there's no app as far as I know that lets you encrypt SMS messages.

Of course, it'd require the other person to also have the same application, but that's the way it usually is with any kind of encryption regardless.

Why do you want this feature?

As of January 2024, there are no SMS apps for Android that:

1. Support E2E Encryption via SMS
2. Are actively maintained (Silence does not work on the newest Android devices and never will, and it has probably accumulated a plethora of security vulnerabilities in the past couple of years)

Additional information

Silence source code: https://git.silence.dev/Silence/Silence-Android/

"Trash can" icon nearly invisible if new text arrives

(Was №606 of Simple Messenger—look there for screenshots.)
(Last of three issue imports for me.)

Icon colors generally have good contrast to the background color—but here's a fleeting bug.

➊ Phone A texts phone B.
➋ I tap the notification on B, bring up Messenger. Background of header* and message area are my chosen pastel color, trash can is black, good.
➌ I long-press the new message. Header turns black, icons turn white, good.
➍ A texts B again. First text is still selected but trash can is now dark gray on black and nearly invisible. That's the bug. (After typing this item and switching back to Messenger, trash can is white again. A third text and trash can is gray again. You can still press trash can and it reverts to white, though the entire screen dims in favor of the confirmation pop-up.)
➎ After deleting one of these test texts, trash can is white (on same pastel background; bad). Other icons are black on pastel, good. Again, switching to browser to type this then switching back to Messenger, all icons are black on pastel.

Found this bug when texting for a report and preparing to delete a previous report—after comparing it to the fresh report.

*Separate observation: When viewing a thread from one texter, it would better distinguish the header from the list if the header background were the chosen "primary color" rather than "background color".

Exporting Messages causes crash

Checklist

• [X ] I can reproduce the bug with the latest version.
• [X ] I made sure that there are no existing issues - open or closed - to which I could contribute my information to.
• [ X] I have read the FAQ and my problem isn't listed.
• [ X] I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• [ X] This issue contains only one bug.
• [ X] I have read and understood the contribution guidelines.

Describe the bug
Exporting messages generates file with 0kb and application force close/crash

To Reproduce
Open SMS-Messanger and goto settings -> export messages -> select SMS & MMS -> export to any sdcard location

Expected behavior
Export succseeds

Device info (please complete the following information):

• Model: [Sony pdx203]
• OS: [Android 11 - Lineageos-18.1 latest selfbuild]
• Version [5.19.3]

Additional context
Reported at SimpleMobileTools/Simple-SMS-Messenger#806

catlog

2-17 11:23:17.983 27980 27980 D PickerActionHandler: onFinished( [content://com.android.externalstorage.documents/document/7489-9A91%3ABackup%2FSettings%2FSimpleMobileTools%2FMessages_2023_12_17_11_23_15.json]

12-17 11:23:18.008 30867 30867 D CompatibilityChangeReporter: Compat change id reported: 147798919; UID 10194; state: ENABLED
12-17 11:23:18.015 30867 30867 D skia : --- Failed to create image decoder with message 'unimplemented'
12-17 11:23:18.045 1896 1916 W System : A resource failed to call release.
12-17 11:23:18.066 951 951 I QTI PowerHAL: Power setBoost: 0, duration: 0
12-17 11:23:18.066 951 951 I QTI PowerHAL: Power setBoost: 0, duration: 0
12-17 11:23:18.078 27980 27980 D AbstractActionHandler: Loader has finished for: content://com.android.externalstorage.documents/document/7489-9A91%3ABackup%2FSettings%2FSimpleMobileTools
12-17 11:23:18.078 27980 27980 I Model : Updating model with new result set.
12-17 11:23:18.078 27980 27980 D DirectoryFragment: Received model update. Loading=false
12-17 11:23:18.349 30867 31904 E CursorWindow: Failed to read row 0, column -1 from a CursorWindow which has 1 rows, 17 columns.
12-17 11:23:18.385 30867 31904 E CursorWindow: Failed to read row 0, column -1 from a CursorWindow which has 2 rows, 17 columns.
12-17 11:23:18.407 30867 31904 E CursorWindow: Failed to read row 1, column -1 from a CursorWindow which has 2 rows, 17 columns.
12-17 11:23:11.523 0 0 I pm8150b_charger: somc_aicl_irq_handler: IRQ: aicl-done
12-17 11:23:11.528 0 0 I FG : fg_gen4_cl_ok_to_begin: IBAT_FLT thr: 100 val: -13 but ignore this function
12-17 11:23:11.528 0 0 I ALG : cap_learning_update: [SOMC CL][OFF] charge_status:1 bsoc_cp:7271
12-17 11:23:18.444 30867 31904 E CursorWindow: Failed to read row 0, column -1 from a CursorWindow which has 6 rows, 17 columns.
12-17 11:23:11.540 0 0 W healthd : battery l=76 v=4046 t=24.7 h=2 st=2 c=12207 fc=3464000 cc=6 chg=u
12-17 11:23:18.455 959 959 D illumination-service: 'battery': Color ffffff00, BrMode 0, OnMS 0, OffMS 0, Mode 0
12-17 11:23:11.546 0 0 E leds rgb: rgbcommon_sync_state_store do nothing. same state
12-17 11:23:18.465 30867 31904 E CursorWindow: Failed to read row 1, column -1 from a CursorWindow which has 6 rows, 17 columns.
12-17 11:23:18.483 30867 31904 E CursorWindow: Failed to read row 2, column -1 from a CursorWindow which has 6 rows, 17 columns.
12-17 11:23:18.514 30867 31904 E CursorWindow: Failed to read row 3, column -1 from a CursorWindow which has 6 rows, 17 columns.
12-17 11:23:18.532 30867 31857 W System : A resource failed to call release.
12-17 11:23:18.535 30867 31904 E CursorWindow: Failed to read row 4, column -1 from a CursorWindow which has 6 rows, 17 columns.
12-17 11:23:18.551 30867 31904 E CursorWindow: Failed to read row 5, column -1 from a CursorWindow which has 6 rows, 17 columns.
12-17 11:23:18.571 30867 31904 E CursorWindow: Failed to read row 0, column -1 from a CursorWindow which has 6 rows, 17 columns.
12-17 11:23:18.586 30867 31904 E CursorWindow: Failed to read row 1, column -1 from a CursorWindow which has 6 rows, 17 columns.
12-17 11:23:18.602 30867 31904 E CursorWindow: Failed to read row 2, column -1 from a CursorWindow which has 6 rows, 17 columns.
12-17 11:23:18.619 30867 31904 E CursorWindow: Failed to read row 3, column -1 from a CursorWindow which has 6 rows, 17 columns.
12-17 11:23:18.637 30867 31904 E CursorWindow: Failed to read row 4, column -1 from a CursorWindow which has 6 rows, 17 columns.
12-17 11:23:18.652 30867 31904 E CursorWindow: Failed to read row 5, column -1 from a CursorWindow which has 6 rows, 17 columns.
12-17 11:23:18.676 30867 31904 E CursorWindow: Failed to read row 0, column -1 from a CursorWindow which has 1 rows, 17 columns.
12-17 11:23:18.698 30867 31904 E CursorWindow: Failed to read row 0, column -1 from a CursorWindow which has 14 rows, 17 columns.
12-17 11:23:18.727 30867 31904 E CursorWindow: Failed to read row 1, column -1 from a CursorWindow which has 14 rows, 17 columns.
12-17 11:23:18.752 30867 31904 E CursorWindow: Failed to read row 2, column -1 from a CursorWindow which has 14 rows, 17 columns.
12-17 11:23:18.773 30867 31904 E CursorWindow: Failed to read row 3, column -1 from a CursorWindow which has 14 rows, 17 columns.
12-17 11:23:18.802 30867 31904 E CursorWindow: Failed to read row 4, column -1 from a CursorWindow which has 14 rows, 17 columns.
12-17 11:23:18.843 30867 31904 E CursorWindow: Failed to read row 5, column -1 from a CursorWindow which has 14 rows, 17 columns.
12-17 11:23:18.857 30867 31904 E CursorWindow: Failed to read row 6, column -1 from a CursorWindow which has 14 rows, 17 columns.
12-17 11:23:18.872 30867 31904 E CursorWindow: Failed to read row 7, column -1 from a CursorWindow which has 14 rows, 17 columns.
12-17 11:23:18.886 30867 31904 E CursorWindow: Failed to read row 8, column -1 from a CursorWindow which has 14 rows, 17 columns.
12-17 11:23:18.903 30867 31904 E CursorWindow: Failed to read row 9, column -1 from a CursorWindow which has 14 rows, 17 columns.
12-17 11:23:18.931 30867 31904 E CursorWindow: Failed to read row 10, column -1 from a CursorWindow which has 14 rows, 17 columns.
12-17 11:23:18.949 30867 31904 E CursorWindow: Failed to read row 11, column -1 from a CursorWindow which has 14 rows, 17 columns.
12-17 11:23:18.966 30867 31904 E CursorWindow: Failed to read row 12, column -1 from a CursorWindow which has 14 rows, 17 columns.
12-17 11:23:18.984 30867 31904 E CursorWindow: Failed to read row 13, column -1 from a CursorWindow which has 14 rows, 17 columns.
12-17 11:23:19.023 30867 31904 E CursorWindow: Failed to read row 0, column -1 from a CursorWindow which has 1 rows, 17 columns.
12-17 11:23:19.048 30867 31904 E CursorWindow: Failed to read row 0, column -1 from a CursorWindow which has 4 rows, 17 columns.
12-17 11:23:19.063 30867 31904 E CursorWindow: Failed to read row 1, column -1 from a CursorWindow which has 4 rows, 17 columns.
12-17 11:23:19.077 30867 31904 E CursorWindow: Failed to read row 2, column -1 from a CursorWindow which has 4 rows, 17 columns.
12-17 11:23:19.092 30867 31904 E CursorWindow: Failed to read row 3, column -1 from a CursorWindow which has 4 rows, 17 columns.
12-17 11:23:19.114 30867 31904 E CursorWindow: Failed to read row 0, column -1 from a CursorWindow which has 1 rows, 17 columns.
12-17 11:23:19.132 30867 31904 E CursorWindow: Failed to read row 0, column -1 from a CursorWindow which has 1 rows, 17 columns.
12-17 11:23:19.154 30867 31904 E CursorWindow: Failed to read row 0, column -1 from a CursorWindow which has 3 rows, 17 columns.
12-17 11:23:19.168 30867 31904 E CursorWindow: Failed to read row 1, column -1 from a CursorWindow which has 3 rows, 17 columns.
12-17 11:23:19.189 30867 31904 E CursorWindow: Failed to read row 2, column -1 from a CursorWindow which has 3 rows, 17 columns.
12-17 11:23:19.214 30867 31904 E CursorWindow: Failed to read row 0, column -1 from a CursorWindow which has 3 rows, 17 columns.
12-17 11:23:19.232 30867 31904 E CursorWindow: Failed to read row 1, column -1 from a CursorWindow which has 3 rows, 17 columns.
12-17 11:23:19.247 30867 31904 E CursorWindow: Failed to read row 2, column -1 from a CursorWindow which has 3 rows, 17 columns.
12-17 11:23:19.272 30867 31904 E CursorWindow: Failed to read row 0, column -1 from a CursorWindow which has 1 rows, 17 columns.
12-17 11:23:19.301 30867 31904 I chatty : uid=10194(com.simplemobiletools.smsmessenger) Thread-18 identical 1 line
12-17 11:23:19.333 30867 31904 E CursorWindow: Failed to read row 0, column -1 from a CursorWindow which has 1 rows, 17 columns.
12-17 11:23:19.369 30867 31904 E CursorWindow: Failed to read row 0, column -1 from a CursorWindow which has 2 rows, 17 columns.
12-17 11:23:19.384 30867 31904 E CursorWindow: Failed to read row 1, column -1 from a CursorWindow which has 2 rows, 17 columns.
12-17 11:23:19.415 30867 31904 E CursorWindow: Failed to read row 0, column -1 from a CursorWindow which has 2 rows, 17 columns.
12-17 11:23:19.436 30867 31904 E CursorWindow: Failed to read row 1, column -1 from a CursorWindow which has 2 rows, 17 columns.
12-17 11:23:19.454 30867 31904 E CursorWindow: Failed to read row 0, column -1 from a CursorWindow which has 7 rows, 17 columns.
12-17 11:23:19.477 30867 31904 E CursorWindow: Failed to read row 1, column -1 from a CursorWindow which has 7 rows, 17 columns.
12-17 11:23:19.497 30867 31904 E CursorWindow: Failed to read row 2, column -1 from a CursorWindow which has 7 rows, 17 columns.
12-17 11:23:19.515 30867 31904 E CursorWindow: Failed to read row 3, column -1 from a CursorWindow which has 7 rows, 17 columns.
12-17 11:23:19.536 30867 31904 E CursorWindow: Failed to read row 4, column -1 from a CursorWindow which has 7 rows, 17 columns.
12-17 11:23:19.554 30867 31904 E CursorWindow: Failed to read row 5, column -1 from a CursorWindow which has 7 rows, 17 columns.
12-17 11:23:19.572 30867 31904 E CursorWindow: Failed to read row 6, column -1 from a CursorWindow which has 7 rows, 17 columns.
12-17 11:23:19.614 30867 31904 E CursorWindow: Failed to read row 0, column -1 from a CursorWindow which has 4 rows, 17 columns.
12-17 11:23:19.632 30867 31904 E CursorWindow: Failed to read row 1, column -1 from a CursorWindow which has 4 rows, 17 columns.
12-17 11:23:19.657 30867 31904 E CursorWindow: Failed to read row 2, column -1 from a CursorWindow which has 4 rows, 17 columns.
12-17 11:23:19.679 30867 31904 E CursorWindow: Failed to read row 3, column -1 from a CursorWindow which has 4 rows, 17 columns.
12-17 11:23:19.715 30867 31904 E CursorWindow: Failed to read row 0, column -1 from a CursorWindow which has 1 rows, 17 columns.
12-17 11:23:19.744 30867 31904 E CursorWindow: Failed to read row 0, column -1 from a CursorWindow which has 1 rows, 17 columns.
12-17 11:23:19.766 30867 31904 E CursorWindow: Failed to read row 0, column -1 from a CursorWindow which has 2 rows, 17 columns.
12-17 11:23:19.783 30867 31904 E CursorWindow: Failed to read row 1, column -1 from a CursorWindow which has 2 rows, 17 columns.
12-17 11:23:19.818 30867 31904 E CursorWindow: Failed to read row 0, column -1 from a CursorWindow which has 1 rows, 17 columns.
12-17 11:23:19.859 30867 31904 E CursorWindow: Failed to read row 0, column -1 from a CursorWindow which has 2 rows, 17 columns.
12-17 11:23:19.873 30867 31904 E CursorWindow: Failed to read row 1, column -1 from a CursorWindow which has 2 rows, 17 columns.
12-17 11:23:19.892 30867 31904 E CursorWindow: Failed to read row 0, column -1 from a CursorWindow which has 1 rows, 17 columns.
12-17 11:23:19.910 30867 31904 E CursorWindow: Failed to read row 0, column -1 from a CursorWindow which has 5 rows, 17 columns.
12-17 11:23:19.930 30867 31904 E CursorWindow: Failed to read row 1, column -1 from a CursorWindow which has 5 rows, 17 columns.
12-17 11:23:19.947 30867 31904 E CursorWindow: Failed to read row 2, column -1 from a CursorWindow which has 5 rows, 17 columns.
12-17 11:23:19.976 30867 31904 E CursorWindow: Failed to read row 3, column -1 from a CursorWindow which has 5 rows, 17 columns.
12-17 11:23:20.002 30867 31904 E CursorWindow: Failed to read row 4, column -1 from a CursorWindow which has 5 rows, 17 columns.
12-17 11:23:20.028 1507 1824 W NotificationService: Toast already killed. pkg=com.simplemobiletools.smsmessenger token=android.os.BinderProxy@9335011
12-17 11:23:13.122 0 0 I qcom_rpmh DRV: apps_rsc TCS Busy, retrying RPMH message send: addr=0x30080
12-17 11:23:20.034 951 951 I QTI PowerHAL: Power setBoost: 0, duration: 0
12-17 11:23:20.052 30867 31904 E CursorWindow: Failed to read row 0, column -1 from a CursorWindow which has 2 rows, 17 columns.
12-17 11:23:20.068 30867 31904 E CursorWindow: Failed to read row 1, column -1 from a CursorWindow which has 2 rows, 17 columns.
12-17 11:23:20.070 1507 1520 W System : A resource failed to call release.
12-17 11:23:13.170 0 0 I IRQ 5 : no longer affine to CPU7
12-17 11:23:20.071 1507 1520 I chatty : uid=1000(system) FinalizerDaemon identical 5 lines
12-17 11:23:20.072 1507 1520 W System : A resource failed to call release.
12-17 11:23:20.092 30867 31904 E CursorWindow: Failed to read row 0, column -1 from a CursorWindow which has 1 rows, 17 columns.
12-17 11:23:20.113 30867 31904 I chatty : uid=10194(com.simplemobiletools.smsmessenger) Thread-18 identical 1 line
12-17 11:23:20.132 30867 31904 E CursorWindow: Failed to read row 0, column -1 from a CursorWindow which has 1 rows, 17 columns.
12-17 11:23:20.149 951 951 I QTI PowerHAL: Power setBoost: 0, duration: 0
12-17 11:23:20.161 30867 31904 E CursorWindow: Failed to read row 0, column -1 from a CursorWindow which has 1 rows, 17 columns.
12-17 11:23:20.186 30867 31904 E CursorWindow: Failed to read row 0, column -1 from a CursorWindow which has 2 rows, 17 columns.
12-17 11:23:20.206 30867 31904 E CursorWindow: Failed to read row 1, column -1 from a CursorWindow which has 2 rows, 17 columns.
12-17 11:23:20.236 30867 31904 E CursorWindow: Failed to read row 0, column -1 from a CursorWindow which has 5 rows, 17 columns.
12-17 11:23:20.260 30867 31904 E CursorWindow: Failed to read row 1, column -1 from a CursorWindow which has 5 rows, 17 columns.
12-17 11:23:20.282 30867 31904 E CursorWindow: Failed to read row 2, column -1 from a CursorWindow which has 5 rows, 17 columns.
12-17 11:23:20.297 30867 31904 E CursorWindow: Failed to read row 3, column -1 from a CursorWindow which has 5 rows, 17 columns.
12-17 11:23:20.312 30867 31904 E CursorWindow: Failed to read row 4, column -1 from a CursorWindow which has 5 rows, 17 columns.
12-17 11:23:20.341 30867 31904 E CursorWindow: Failed to read row 0, column -1 from a CursorWindow which has 1 rows, 17 columns.
12-17 11:23:20.385 30867 31904 E CursorWindow: Failed to read row 0, column -1 from a CursorWindow which has 1 rows, 17 columns.
12-17 11:23:20.757 30867 31904 I ls.smsmessenge: Starting a blocking GC Alloc
12-17 11:23:20.757 30867 31904 I ls.smsmessenge: Starting a blocking GC Alloc
12-17 11:23:20.766 30867 31904 I ls.smsmessenge: Alloc young concurrent copying GC freed 2112(79KB) AllocSpace objects, 0(0B) LOS objects, 17% free, 116MB/140MB, paused 30us total 8.613ms
12-17 11:23:20.766 30867 31904 I ls.smsmessenge: Starting a blocking GC Alloc
12-17 11:23:20.788 30867 31904 I ls.smsmessenge: Alloc concurrent copying GC freed 7(16KB) AllocSpace objects, 1(26MB) LOS objects, 21% free, 89MB/113MB, paused 26us total 21.693ms
12-17 11:23:20.788 30867 31904 I ls.smsmessenge: Forcing collection of SoftReferences for 104MB allocation
12-17 11:23:20.788 30867 31904 I ls.smsmessenge: Starting a blocking GC Alloc
12-17 11:23:20.802 30867 31904 I ls.smsmessenge: Alloc concurrent copying GC freed 5480(203KB) AllocSpace objects, 0(0B) LOS objects, 21% free, 89MB/113MB, paused 28us total 13.666ms
12-17 11:23:20.802 30867 31904 W ls.smsmessenge: Throwing OutOfMemoryError "Failed to allocate a 109453288 byte allocation with 25165824 free bytes and 102MB until OOM, target footprint 119157176, growth limit 201326592" (VmSize 14045404 kB)
12-17 11:23:20.802 30867 31904 I ls.smsmessenge: Starting a blocking GC Alloc
12-17 11:23:20.802 30867 31904 I ls.smsmessenge: Starting a blocking GC Alloc
12-17 11:23:20.809 30867 31904 I ls.smsmessenge: Alloc young concurrent copying GC freed 4(31KB) AllocSpace objects, 0(0B) LOS objects, 21% free, 89MB/113MB, paused 25us total 7.326ms
12-17 11:23:20.809 30867 31904 I ls.smsmessenge: Starting a blocking GC Alloc
12-17 11:23:20.827 30867 31904 I ls.smsmessenge: Alloc concurrent copying GC freed 4(16KB) AllocSpace objects, 0(0B) LOS objects, 21% free, 89MB/113MB, paused 26us total 17.139ms
12-17 11:23:20.827 30867 31904 I ls.smsmessenge: Forcing collection of SoftReferences for 104MB allocation
12-17 11:23:20.827 30867 31904 I ls.smsmessenge: Starting a blocking GC Alloc
12-17 11:23:20.840 30867 31904 I ls.smsmessenge: Alloc concurrent copying GC freed 5(16KB) AllocSpace objects, 0(0B) LOS objects, 21% free, 89MB/113MB, paused 26us total 13.044ms
12-17 11:23:20.840 30867 31904 W ls.smsmessenge: Throwing OutOfMemoryError "Failed to allocate a 109453288 byte allocation with 25165824 free bytes and 102MB until OOM, target footprint 119157176, growth limit 201326592" (VmSize 14045404 kB)
--------- beginning of crash
12-17 11:23:20.841 30867 31904 E AndroidRuntime: FATAL EXCEPTION: Thread-18
12-17 11:23:20.841 30867 31904 E AndroidRuntime: Process: com.simplemobiletools.smsmessenger, PID: 30867
12-17 11:23:20.841 30867 31904 E AndroidRuntime: java.lang.OutOfMemoryError: Failed to allocate a 109453288 byte allocation with 25165824 free bytes and 102MB until OOM, target footprint 119157176, growth limit 201326592
12-17 11:23:20.841 30867 31904 E AndroidRuntime: at java.util.Arrays.copyOf(Arrays.java:3257)
12-17 11:23:20.841 30867 31904 E AndroidRuntime: at kb.m.a(SourceFile:12)
12-17 11:23:20.841 30867 31904 E AndroidRuntime: at kb.f.i(SourceFile:19)
12-17 11:23:20.841 30867 31904 E AndroidRuntime: at kb.v.t(SourceFile:8)
12-17 11:23:20.841 30867 31904 E AndroidRuntime: at ib.b1.a(SourceFile:13)
12-17 11:23:20.841 30867 31904 E AndroidRuntime: at kb.v.n(SourceFile:106)
12-17 11:23:20.841 30867 31904 E AndroidRuntime: at com.bumptech.glide.d.p(SourceFile:34)
12-17 11:23:20.841 30867 31904 E AndroidRuntime: at kb.v.p(SourceFile:19)
12-17 11:23:20.841 30867 31904 E AndroidRuntime: at d9.u.g(SourceFile:79)
12-17 11:23:20.841 30867 31904 E AndroidRuntime: at d9.s.a(SourceFile:19)
12-17 11:23:20.841 30867 31904 E AndroidRuntime: at kb.v.n(SourceFile:106)
12-17 11:23:20.841 30867 31904 E AndroidRuntime: at com.bumptech.glide.d.b0(SourceFile:14)
12-17 11:23:20.841 30867 31904 E AndroidRuntime: at ib.o.a(SourceFile:45)
12-17 11:23:20.841 30867 31904 E AndroidRuntime: at kb.v.n(SourceFile:106)
12-17 11:23:20.841 30867 31904 E AndroidRuntime: at com.bumptech.glide.d.b0(SourceFile:14)
12-17 11:23:20.841 30867 31904 E AndroidRuntime: at d9.r.h(SourceFile:134)
12-17 11:23:20.841 30867 31904 E AndroidRuntime: at d9.p.a(SourceFile:19)
12-17 11:23:20.841 30867 31904 E AndroidRuntime: at jb.j.a(SourceFile:687)
12-17 11:23:20.841 30867 31904 E AndroidRuntime: at kb.v.n(SourceFile:106)
12-17 11:23:20.841 30867 31904 E AndroidRuntime: at com.bumptech.glide.d.b0(SourceFile:14)
12-17 11:23:20.841 30867 31904 E AndroidRuntime: at ib.o.a(SourceFile:45)
12-17 11:23:20.841 30867 31904 E AndroidRuntime: at kb.v.n(SourceFile:106)
12-17 11:23:20.841 30867 31904 E AndroidRuntime: at com.bumptech.glide.c.n0(SourceFile:32)
12-17 11:23:20.841 30867 31904 E AndroidRuntime: at e8.k0.E(SourceFile:396)
12-17 11:23:20.841 30867 31904 E AndroidRuntime: at j.a.d(SourceFile:339)
12-17 11:23:20.841 30867 31904 E AndroidRuntime: at n8.o.b(SourceFile:1443)
12-17 11:23:20.841 30867 31904 E AndroidRuntime: at n8.o.f(SourceFile:229)
12-17 11:23:20.841 30867 31904 E AndroidRuntime: at p1.v.run(SourceFile:20)
12-17 11:23:20.841 30867 31904 E AndroidRuntime: at java.lang.Thread.run(Thread.java:923)
12-17 11:23:20.842 1507 7831 W ActivityTaskManager: Force finishing activity com.simplemobiletools.smsmessenger/.activities.SettingsActivity
12-17 11:23:20.842 1507 31911 I DropBoxManagerService: add tag=data_app_crash isTagEnabled=true flags=0x2
12-17 11:23:20.861 30867 31904 I Process : Sending signal. PID: 30867 SIG: 9
12-17 11:23:13.980 0 0 I binder : undelivered TRANSACTION_COMPLETE
12-17 11:23:13.980 0 0 I binder : undelivered transaction 118411719, process died.
12-17 11:23:20.891 1507 27195 I WindowManager: WIN DEATH: Window{1b89499 u0 com.simplemobiletools.smsmessenger/com.simplemobiletools.smsmessenger.activities.MainActivity}
12-17 11:23:20.891 1507 27195 W InputDispatcher: Attempted to unregister already unregistered input channel '1b89499 com.simplemobiletools.smsmessenger/com.simplemobiletools.smsmessenger.activities.MainActivity (server)'
12-17 11:23:20.891 793 793 I Zygote : Process 30867 exited due to signal 9 (Killed)
12-17 11:23:20.892 1507 2674 I ActivityManager: Process com.simplemobiletools.smsmessenger (pid 30867) has died: fg TOP
12-17 11:23:20.893 1507 1556 I libprocessgroup: Successfully killed process cgroup uid 10194 pid 30867 in 0ms
12-17 11:23:20.895 1507 7275 W WindowManager: Cannot find window which accessibility connection is added to
12-17 11:23:20.895 1507 2017 I WindowManager: WIN DEATH: Window{4bf4f3e u0 com.simplemobiletools.smsmessenger/com.simplemobiletools.smsmessenger.activities.SettingsActivity}
12-17 11:23:20.895 1507 2017 W InputDispatcher: Attempted to unregister already unregistered input channel '4bf4f3e com.simplemobiletools.smsmessenger/com.simplemobiletools.smsmessenger.activities.SettingsActivity (server)'
12-17 11:23:20.902 1507 26240 W WindowManager: Cannot find window which accessibility connection is added to
12-17 11:23:20.908 1507 1547 W ActivityManager: setHasOverlayUi called on unknown pid: 30867
12-17 11:23:20.909 1507 1547 D CompatibilityChangeReporter: Compat change id reported: 135634846; UID 10194; state: DISABLED
12-17 11:23:20.909 1507 1547 D CompatibilityChangeReporter: Compat change id reported: 135754954; UID 10194; state: ENABLED
12-17 11:23:20.910 1507 1555 D CompatibilityChangeReporter: Compat change id reported: 143937733; UID 10194; state: ENABLED
12-17 11:23:20.916 1507 1555 I ActivityManager: Start proc 30868:com.simplemobiletools.smsmessenger/u0a194 for top-activity {com.simplemobiletools.smsmessenger/com.simplemobiletools.smsmessenger.activities.MainActivity}
12-17 11:23:20.917 5160 5164 I adbd : jdwp connection from 30868
12-17 11:23:20.927 30868 30868 I ls.smsmessenge: The ClassLoaderContext is a special shared library.
12-17 11:23:20.936 30868 30868 W ls.smsmessenge: JIT profile information will not be recorded: profile file does not exist.
12-17 11:23:20.941 30868 30868 D NetworkSecurityConfig: No Network Security Config specified, using platform default
12-17 11:23:20.941 30868 30868 D NetworkSecurityConfig: No Network Security Config specified, using platform default
12-17 11:23:20.949 1022 1575 W DisplayIdentification: Invalid EDID: ASCII text is not printable.
12-17 11:23:20.949 1022 1575 W DisplayIdentification: Invalid EDID: falling back to serial number due to missing display name.
12-17 11:23:20.949 1022 1575 W DisplayIdentification: Invalid EDID: falling back to ASCII text due to missing serial number.
12-17 11:23:20.950 1022 1575 E DisplayIdentification: Invalid EDID: display name and fallback descriptors are missing.
12-17 11:23:20.954 30868 30868 D AppCompatDelegate: Checking for metadata for AppLocalesMetadataHolderService : Service not found
12-17 11:23:20.991 30868 30868 D skia : --- Failed to create image decoder with message 'unimplemented'
12-17 11:23:21.009 30868 31930 I AdrenoGLES-0: QUALCOMM build : 191610ae03, Ic907de5ed0
12-17 11:23:21.009 30868 31930 I AdrenoGLES-0: Build Date : 09/17/20
12-17 11:23:21.009 30868 31930 I AdrenoGLES-0: OpenGL ES Shader Compiler Version: EV031.32.02.01
12-17 11:23:21.009 30868 31930 I AdrenoGLES-0: Local Branch :
12-17 11:23:21.009 30868 31930 I AdrenoGLES-0: Remote Branch : refs/tags/AU_LINUX_ANDROID_LA.UM.9.12.10.00.00.582.274
12-17 11:23:21.009 30868 31930 I AdrenoGLES-0: Remote Branch : NONE
12-17 11:23:21.009 30868 31930 I AdrenoGLES-0: Reconstruct Branch : NOTHING
12-17 11:23:21.009 30868 31930 I AdrenoGLES-0: Build Config : S P 10.0.5 AArch64
12-17 11:23:21.009 30868 31930 I AdrenoGLES-0: Driver Path : /vendor/lib64/egl/libGLESv2_adreno.so
12-17 11:23:21.012 30868 31930 I AdrenoGLES-0: PFP: 0x016dd091, ME: 0x00000000
12-17 11:23:21.049 951 951 I QTI PowerHAL: Power setBoost: 0, duration: 0
12-17 11:23:21.113 30868 30868 W Glide : Failed to find GeneratedAppGlideModule. You should include an annotationProcessor compile dependency on com.github.bumptech.glide:compiler in your application and a @GlideModule annotated AppGlideModule implementation or LibraryGlideModules will be silently ignored
12-17 11:23:14.210 0 0 I IRQ 5 : no longer affine to CPU6
12-17 11:23:21.156 30868 30868 W Glide : Load failed for [] with dimensions [113x113]
12-17 11:23:21.156 30868 30868 W Glide : class com.bumptech.glide.load.engine.GlideException: Failed to load resource
12-17 11:23:21.524 1507 1547 W WindowManager: Unable to start animation, surface is null or no children.
12-17 11:23:21.157 30868 30868 I chatty : uid=10194(com.simplemobiletools.smsmessenger) identical 8 lines
12-17 11:23:21.157 30868 30868 W Glide : Load failed for [] with dimensions [113x113]
12-17 11:23:21.157 30868 30868 W Glide : class com.bumptech.glide.load.engine.GlideException: Failed to load resource
12-17 11:23:22.319 4119 4119 D MyReceiver: ACTION_MONITOR_BATTERY_LEVEL received.
12-17 11:23:22.320 4119 4119 D MyReceiver: min level setting=20; max level setting=80
12-17 11:23:22.320 4119 4119 D MyReceiver: current level=76
12-17 11:23:22.322 4119 4119 D Util : Trigger alarm in 5 seconds
12-17 11:23:26.781 30868 31958 D ProfileInstaller: Skipping profile installation for com.simplemobiletools.smsmessenger
12-17 11:23:27.069 959 959 D illumination-service: 'buttons': Color ff000000, BrMode 0, OnMS 0, OffMS 0, Mode 0

To big message box -> could not view other messages

Checklist

• I can reproduce the bug with the latest version given here.
• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• I have read and understood the contribution guidelines.

Affected app version

1.0.0

Affected Android/Custom ROM version

Android 11 / CrDroid 7

Affected device model

Galaxy A3 2017

How did you install the app?

GitHub releases

Steps to reproduce the bug

Being writing a very long SMS.

Expected behavior

The message box should not take ALL the height. It is very usefull to increase the message box as the message length increase (it is not the case on my default SMS app) but it should be possibe to scroll older messages or being able to read messages received when writing a long message.

Actual behavior

The message box take ALL the height : it is not possible to read other message in the conversation.

Screenshots/Screen recordings

No response

Additional information

No response

SMSs are not imported in chronological order

This was issue 802 of Simple Messages

Please refer to it for further details and discussions.

Checklist

• I can reproduce the bug with the latest version.
• I made sure that there are no existing issues - open or closed - to which I could contribute my information to.
• I have read the FAQ and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• I have read and understood the contribution guidelines.

Describe the bug
When running it the first time after installation(and after making it default SMS app), it automatically starts loading the messages but all the messages show the same timestamp of when it was imported(and not that of when the message was sent or received). Although when opened, it shows correct time.

So messages order in my stock SMS app and in Simple SMS are completely different.

I also tried to manually export messages from the default SMS app so that I can import it in simple SMS but that also fails since probably the format(keys) don't match. Can you refer to some app that exports SMS in a compatible format?
I tried using SMS Import Export

To Reproduce
Steps to reproduce the behavior:
Detailed steps and behaviour explained in the original issue.

Expected behavior
All messages should have been imported in correct chronological order. Doesn't happen all the time. Maybe an external tool/script would help convert the exported SMSs to a compatible format importable by Fossify Messages.

Screenshots
If applicable, add screenshots to help explain your problem.

Device info (please complete the following information):

• Model: [Pixel 7]
• OS: [Android 14]
• App version [1.0.0]

Additional context
Issue explained in detail in the original issue on simple messages. Also, issue 783 and issue 499 may be related to this issue.

Issue 499 from simple messages:
I have exported SMS messages from Signal and then switched to Simple SMS Messenger. However, I have random order in the thread list, due to sorting by exported time, not sent/received time.

What's interesting: stock (AOSP, outdated) messages app shows everything correctly, in correct order, with correct date/time.

Tried reexporting, clearing app cache and data (to trigger app's database initialization) and unfortunately nothing helped.

Reduce padding between conversations

Checklist

• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.
• I optionally donated to support the Fossify mission.

Feature description

Suggest an option to reduce padding between conversations, or reduce it by default.

Why do you want this feature?

The padding between conversations on the message list is large and make it less comfortable for me to read. Changing the font size to small reduces the padding, but the font (obviously) is pretty small. I've added three photos to show the difference in what is shown on my screen on Fossify Messages vs Google Messages & QKSMS. My phone is pretty tall so I'm not sure if that's part of the problem (eg, the padding is based on a % of screen height).

Additional information

No response

[Feature request] Optional display of phone numbers next to contact names

Checklist

• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I have read the FAQ and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the feature request will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.

Is your feature request related to a problem? Please describe.
It would be great if it could optionally view phone numbers on the main page next to the contacts. Especially useful for contacts with multiple phone numbers.

Describe the solution you'd like
Next to the name would be a number in a smaller font, for example:
John Doe ^{020 7123 4567}

Describe alternatives you've considered
The alternative is to leave it as it is.

Additional context

Sending group message in existing group sends individual message to each recipient

Checklist

• I can reproduce the bug with the latest version given here.
• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• I have read and understood the contribution guidelines.

Affected app version

1.0.0

Affected Android/Custom ROM version

Android 11

Affected device model

Motorola G Stylus 2021

How did you install the app?

Google Play Store

Steps to reproduce the bug

1. Have existing group message (I had one started from Google Messages & QKSMS already)
2. Send message to group from Fossify Messages
3. View messages in another app or start a new message to individual contacts from Fossify Messages, there will be an individual message to each contact.

Expected behavior

Message stays within group message thread rather than individiaul messages

Actual behavior

Individual message sent to each contact.

Screenshots/Screen recordings

No response

Additional information

There is a "group message as MMS" setting that is disabled by default but I don't know if that's required or not. I don't have a similar setting in QKSMS.

Prompt for group messages settings on install

Checklist

• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.
• I optionally donated to support the Fossify mission.

Feature description

Upon install, Fossify Messages should prompt the user to select a group message setting.

Why do you want this feature?

Group messages do not actually send as group messages (MMS) by default. This is expected behavior with the current implementation.

If you are migrating to this app from another, the current implementation can lead to confusion when resuming a group text as it causes the thread to split into multiple individual conversations.

See #50

Additional information

No response

Lock-screen preference also affects notification

(Was №791 of Simple Messenger)

When the setting "Lock screen notification visibility" is set to "Nothing", it also results in an empty notification in the windowshade and inhibits the medallion on the home-page icon. If you meant this setting to have all these effects, at least reword the prompt.

Observed on Samsung J3 with Android 9 and Samsung J7 with Android 8, Messenger 5.19.3.
Initially reported and misdiagnosed in [№765 of Simple Messenger].
Low priority; obvious workaround.

Template Messages folder

Checklist

• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.
• I optionally donated to support the Fossify mission.

Feature description

Template messages could have their place in a steady, floating folder at the down left of the home screen, on the opposite side of + button, with the following management options:

1. Create
2. Modify
3. Delete

Other ideas:

1. As a "Template Messages" option, along with "Show recycle bin" and "Show archived conversations" at the three-dot menu, right of the settings (gear) icon
2. As a secondary option when writing new message, new conversation or selecting an existing template message
3. As a secondary option when long pressing the + button to write new message or select a template message

Why do you want this feature?

There is the need to write SMS messages and save them as templates in order to be ready to select, and when needed, modify before send.

Template messages are text messages stored with specific body text and with or without recipient(s).

Additional information

No response

Add markdown support

Checklist

• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I have read the FAQ and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the feature request will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Please add the markdown support (like WhatsApp)

group SMS limit

Checklist

• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.
• I optionally donated to support the Fossify mission.

Feature description

Group SMS lists can be generated and group SMS can be sent, but I think it is a rule of Android that group SMS cannot be sent to more than 20 people. Then it gives an error. But if there is an interval of 2 minutes between each session, there is no problem.

Can it be developed with a feature like this?

Let's say I added 108 people to the list. I said send a group message.
108/20=5.4. So if we round this up, it has to be divided by 6.

If it automatically divided the list into 6 and sent them 2 minutes apart...

If the message is 2 messages long, it should also take that into account.

Why do you want this feature?

When we want to send more than 20 group messages, it takes a lot of time.

Additional information

No response

Draft saved despite being erased

Checklist

• I can reproduce the bug with the latest version.
• I made sure that there are no existing issues - open or closed - to which I could contribute my information to.
• I have read the FAQ and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• I have read and understood the contribution guidelines.

Describe the bug
I have one conversation in which the previous draft keeps being saved. Let's say the draft read hello, i enter the conversation, erase the text in the text area, leave the conversation… the draft still

To Reproduce
Steps to reproduce the behavior:

1. Enter a conversation page
2. Write some text in the text area: eg. hello
3. Leave the conversation
4. Draft is saved as expected, shown to be hello
5. Enter the conversation again
6. Change draft to any other text, a single letter is enough: eg E
7. Leave conversation
8. Draft is changed and saved as expected, and is shown to be E
9. Enter conversation again
10. Erase entirely previous draft E from the text area
11. Leave conversation
12. Draft isn't erased and is shown to still be E

Expected behavior
Draft should be erased and forgotten about after being deleted from the text area

Device info (please complete the following information):

• Model: NOKIA TA-1157
• OS: Android 11
• Version: SMT 5.19.3

Additional context
i checked on SMT issue tracker and haven't seen issues about this.

Display scheduled messages in conversations list

Checklist

• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I have read the FAQ and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the feature request will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.

Is your feature request related to a problem? Please describe.
I have scheduled a text message to be sent tomorrow morning, going through the several (confirmation) steps. When going back to the 'conversations' list, the scheduled message isn't there. I've recently moved phones so have no history yet, probably causing the conversation not to show up.

(When searching for and opening the contact, I do see the scheduled message.)

Describe the solution you'd like

If a message is scheduled (or maybe even drafted), can it/the contact be shown in the conversations list? That both acts as reassurance that it is scheduled, and faster access to the message to make any changes if needed.

Describe alternatives you've considered
n/a

Additional context
n/a

Option to disable parsing and opening weblinks

Checklist

• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.
• I optionally donated to support the Fossify mission.

Feature description

Option in Settings > Security > to enable Disable parsing weblinks. When enabled, secondary option to select color of highlighting. Weblinks are shown as simple text in underscore format, highlighted with user's selected colored.

Why do you want this feature?

For security purposes it would be very useful to disable opening weblinks when pressing and only be custom highlighted as simple text.

It is the most common method for installing spyware and malicious software/app from a phishing attack.

It will be very useful for many people who would like to use it in order to protect themselves, even from accidental pressing, for old and young people who lack the concept and experience of security, for journalists, and for anyone may need this safety feature.

Additional information

No response

Wake Screen with New Message

Checklist

• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.
• I optionally donated to support the Fossify mission.

Feature description

I would like my phone to wake when I get a new text message.

Why do you want this feature?

This would allow me to know if I got a new message without looking in my notifications.

Additional information

No response

E2EE for SMS /MMS (and even RCS)

Checklist

• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I have read the FAQ and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the feature request will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.

Is your feature request related to a problem? Please describe.
NO

Describe the solution you'd like
I would like to have the possibility like Silence or Deku to enable E2EE for SMS or MMS (and even RCS)? Maybe you can also use a qr code to enable the e2ee: deku-messaging/Deku-SMS-Android#183

Describe alternatives you've considered
Until now I only know Silence (https://git.silence.dev/Silence/Silence-Android) or Deko SMS (https://github.com/deku-messaging/Deku-SMS-Android) for E2EE SMS or MMS

Additional context
Maybe you could have settings (opt-in) that messages without E2EE are not accepted / send an error message
Display a warning if the messages don't have E2EE (opt-in; like a red lock icon)

addition of "Sync Messages" button in the settings

Is your feature request related to a problem? Please describe.
I am using stock android 8.1 and many times the new messages don't get loaded automatically although it is already received by device. Later I found out it is a sync issue with native android SMS database.

Describe the solution you'd like
It would be convenient to have a sync button within the app settings which can sync manually with native android sms data base. QK-SMS app has this functionality.

Make it possible to switch MMS off

Checklist

• [x ] I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• [x ] I have read the FAQ and my problem isn't listed.
• [x ] I have taken the time to fill in all the required details. I understand that the feature request will be dismissed otherwise.
• [x ] This issue contains only one feature request.
• [x ] I have read and understood the contribution guidelines.

Is your feature request related to a problem? Please describe.
MMS in Germany are very expensive, also in price models with free SMS. Sometimes somebody can send a MMS by mistake (thinking it is a SMS)

Describe the solution you'd like
Don't send MMS by mistake (and pay extra fees)

Describe alternatives you've considered
warn before sending MMS

Additional context
In Germany some (not all) operators have switched off MMS. MMS is unpopular because it is expensive and many people use Messengers like WhatsApp/Signal/Telegram, etc. In some price models you have free SMS but MMS are very expensive. If i have the wrong characters in my SMS or text is to long or something similar, the maybe wanted SMS convert to a MMS. Can you make a switch to toggle the use of MMS completly off or as an alternative: warn before a MMS is send?

[Feature request] Option in settings to set numbers in messages as hotlinks to copy

Checklist

• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I have read the FAQ and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the feature request will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.

Is your feature request related to a problem? Please describe.
So if someone send me contact/bank number/amount I need to pay, I just have to click on the number to copy it.

Describe the solution you'd like
title

Automatic remove of old messages

Checklist

• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.
• I optionally donated to support the Fossify mission.

Feature description

Add time limit to keep messages.

Why do you want this feature?

To forget old messages

Additional information

Like signal or whatsapp it would be great to be able to set retaining time for messages. Preferably per conversation setting. So that I could set that messages are automatically removed after 1 week, 1 month or similar.

Spam folder for messages

Checklist

• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.
• I optionally donated to support the Fossify mission.

Feature description

I know its an initial release and i am sorry to requesting a feature too early, Only issue with the fossify sms is there isn't a spam folder or a way to retrieve accidentally blocked sms

Why do you want this feature?

I accidentally blocked an sms , i couldn't find an spam folder or anything like that, as a temporary solution i installed another sms app and retrieve that blocked message from there

Additional information

Even there won't be a spam folder ,please add any way to retrieve blocked messages

Keywords enhancement - Boolean logic / regex

Checklist

• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.
• I optionally donated to support the Fossify mission.

Feature description

The keywords feature is a great idea, and with some improvements can be very useful. As it is, though, it's too limited to be of much use, as blocking any SMS with a particular keyword may cause blocking one that shouldn't be blocked. To help ensure this doesn't happen, it should be improved to allow blocking only messages that contain e.g. WORD1 AND WORD2 but NOT WORD3, and it should allow regex usage. While more complex, it should even allow things such as WORD1 AND (WORD2 OR WORD3).

Why do you want this feature?

See above

Additional information

No response

[Feature Request] Add Fossify SMS Messenger to F-Droid

Checklist

• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I have read the FAQ and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the feature request will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.

Is your feature request related to a problem? Please describe.
Add Fossify SMS Messenger to F-Droid

Describe the solution you'd like
Add Fossify SMS Messenger to F-Droid

Describe alternatives you've considered
N/A

Additional context
N/A

Delayed sending, aka cool down period

Checklist

• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.
• I optionally donated to support the Fossify mission.

Feature description

After hitting the send button, the message should only be sent after a (configurable) delay has elapsed. During this delay a count-down timer showing the remaining time should replace the send button. A circular progress meter in icon size running towards zero would be ideal. As long as the timer has not elapsed, it is possible to cancel the sending of the message, e.g. by clicking on that progress meter or pressing the back button.

If the user decides to cancel, s/he will be taken back to the message and edit it.

Why do you want this feature?

Often you click on the send button but immediately regret having sent the message. In this case a traditional confirmation, if one really wants to send the message does not help, because this question is generally automatically confirmed.

Such a ‘cool down’ period could help you avoiding stupid/embarrassing/(or even) costly mistakes!

Additional information

QKSMS (now QUIK) solves this problem by having a (customizable) ‘cool down’ period: A countdown timer is displayed after hitting the send button. Without any interaction, the text message is dispatched when the timer reaches zero. The sending can be cancelled by the user by clicking on this countdown timer. S/he returns immediately to the text message and can edit it.