I have been trying to glean useful information from the serial monitor, but this hasnāt shown me much so far. When I press A to send an SMS, this is all that I get on the monitor - the ā#ā is me masking my real number (selected from contacts to save myself typing, hence āpressed3ā; ācontactIDā; ā-1ā), and āHIā is the actual message I sent in all caps:
Cursor: 0
chosen: -2
AT+CREG?
+CREG: 0,1
OK
pressed3
contactID
-1
AT+CMGS="+###########"
>
HI
At this point, the message is actually received by my other phone, but it doesnāt look like a response was processed as being received from the networkā¦we hang on āSending textā¦ā forever. Still could be timing, as previously mentioned, or perhaps some EOL or EOM is not being sent and the network is the one still waiting? I donāt know what IS or ISNāT being sent to the serial monitor.
And now on to Callsā¦ When I place a call, here is the serial monitor output from the moment I press A:
AT+CREG?
+CREG: 0,1
OK
call id: 2
Then it hangs on the āCallingā¦ā screen until it times out and shows this:
ENDED
Direction of call: 1
Nothing else shows in the monitor and it just returns to the dialer screen. I hope this helps somehow!
EDIT: Alright. Now that I figured out how the SIM module debug works in tandem with the Serial Monitor, I have new information. We seem to be getting held up around line #1063 of /src/messagesApp.cpp
Since the SMS is actually sending out to the other phone (and is received), we know the ESC is making it to the module. If I manually run the commands to send myself an SMS via debug, I get the following (again using # to mask my real num):
AT+CMGF=1
OK
AT+CMGS="+###########"
> Hello
+CMGS: 25,"20/06/07,03:29:18-28"
OK
Of course, I currently have no way of knowing what messagesApp is actually receiving back, as this is not sent to the serial monitor, but I donāt think it is receiving what it is expecting to receive and this causes it to get stuck in the while() loop.