Delayed sms messages

BraX3 iodéOS
61

The only thing left is to take a LogCat while sending the SMS and you may catch some error, Delayed sms messages - #36 by george

62

FWIW I imported mine as JSON with no problem, but I did use a very soecific app/process as I was on iPhone. A couple of questions (1) did you ‘export’ the contacts from your old device or from a cloud store, or just copy an existing JSON file from your existing message srorage? (2) if you did do an export process have you gone back and tried it again, as (a) you may have a corrupted file, or (b) there may be alternate options you can select for the JSON format, so tryingdifferent ones may help (if there are any).

Note also that if you have any weird stuff in your contacts themselves, like especially unusual characters or objects, etc, this might make your JSON file unreadable when something tries to import it (as it may not recognise it or it may break the file format)…

(e.g. a simplistic example is like a spreadsheet you use commas in then export to csv, the commas in the content then get read as part of the csv format (i.e. columns) instead of content… JSON files can sometimes have similar sorts of issues depending on how they were generated/exported).

1 Like
63

Mycenius, I exported the messages from the default sms app simplemobile. I no longer have the luxury of trying again since that phone was sent back to brax support. All I have are the exported files. The Brax replacement phone comes with the sms app from fossify that finds my .json export from simplemobile as a invalid file. It cant read it for some reason. Thanks for your explanation.

64

Can’t you view the file with the app I told you? It’s just a text file that even browsers can open it, Brave renders jsons very well.

1 Like
65

George & Mycenius SURPRISE POSITIVE UPDATE :upside_down_face: I have an external sdxc card. I had a few exported sms files the download folder. These .json files appear slightly different (had Under score symbols every 2 characters) that differ from the 2 sms exports that I’ve been trying to import. I REMOVED THEM and tried again. SMS import successful!! I don’t know what to call this User Error or what? Thank you both for your continued attentive efforts to assist!

Now, Everything Works! for my needs :grinning_face_with_smiling_eyes: :grin: :rofl:

2 Likes
66

Great news @Steve577 ! Nice! :smiley:

1 Like
67

Same issues with Quik, but at least it’s not a total blocker

68

The “not sent” means that the app is aware so either the modem responds with a failure code or the app fails to connect to the modem, both can be captured with the log. I’ll check the source code to see the possible failures.

It seems this is a system exception so it will show up as an E message.

69

I think the failure code is 1. How do I go about checking the log?

70

Here, Delayed sms messages - #36 by george

1 Like
71

@gina Where did you see the error code ?
Do you get it as a toast as it appears in the source code?

As you can see error code -1 is associated with EMPTY_DESTINATION_ADDRESS, Messages/app/src/main/kotlin/org/fossify/messages/messaging/SmsException.kt at main · FossifyOrg/Messages · GitHub

It comes from the Android API, probably the application isn’t sending a proper format of the phone number to the modem.

The LogCat could provide some more detailed information.

Try all the 3 options,

  • no country code
  • +1
  • 001

assuming that you have a +1 number and you’re texting to a +1 number

I will try to research it further and then get into the group MMS problem.

72

I haven’t had a chance to check the logs yet.

It’s on a thread I already have going rather than a new one, so I’m not sure how it could be empty based on my actions.

Yes this is all US numbers used for many years, person to person and not group messages so far. No country codes in my address book. It is intermittent, so it’s hard to narrow down who/when. I can’t put country codes in every entry. It does happen across different numbers. I could put a country code in 1 number. And if that works, it’s not definitive, because it’s random across many people. I probably won’t put a country code in all my hundreds of numbers :grinning_face: .

I will do my best to check the logs though so you can have some clues if any.

Thank you for your help George

73

The exception is thrown by the SmsSender, Messages/app/src/main/kotlin/org/fossify/messages/messaging/SmsSender.kt at main · FossifyOrg/Messages · GitHub

I’ll have a look how it accesses the contacts and why it fails to load the phone number.

74

@gina Update to 7.3 to see if it’s related, it’s still a beta update, follow the instructions if you want to update, Iode' 7.2 update seems good - #26 by george