Notices

The volume is already set to 100% before playing the sound. And at least on my phone this works. This is easy to confirm because the volume is not reset to the previous value after playing the sound...
Please test this again with 50% volume set before sending COM_ALARM. After sound is done, check volume. Should be 100%.
Thank you.

smscon should check incoming sms even when in testmode, provided the sms comes in AFTER the test-operation has been performed. Only minor restrictions apply (GPS relatet stuff might not work as expected etc), so it is recommended to terminate test mode. In xterm following command does it:.

If smscon does not recognize your sms-commands, they are probably misspelled. Take a look in the log: Consider to pipe output through "more". If the command has been recognized there will be an log entry (and then this means that smscon does not behave correctly on receiving the command). But I guess that the command is not recognized.

To get a list of all recognized commands send COM_CHECK (if you know how this is spelled) or - on the phone - enter following command in xterm:
Tell me if that helps you.

NEW VERSION OF SMSCON AVAILABLE: 0.9.6-2

smscon 0.9.6-2 has been queued for loading into fremantle extras-devel repository

• NEW: If no user supplied alarm.wav file exists, use a funny default alarm sound.
• FIX: Send notifications on battery charge level change only if the message differs from last message.
• FIX: Beautify battery change message in case device could not supply dis/charge info.
• FIX: More tolerant detection if smscon_daemon is already running.

Uploaded new version of SMSCON Editor (0.9.6-1) in extras-devel

Changes:
CHANGE: Rebuild of the UI; removed tabs and added for each a separate window.
CHANGE: Removed the menu and added its actions as buttons in the main UI.
CHANGE: Modified postrm script; inclusion of new files.
NEW: Added Email-From field.

PS: I think we are close for a 1.0 release that we will push to extras-testing.

Sorry, it does not help. Error: smscon must run as "root"
And when I gain root and run, it says: unknown option (-restart)
There are no spelling mistakes and yet it does not work beyond test-drive mode! Please help.

I've tested latest release, and all my former bug reports still apply - except for different text that I get in "spamming" messages So:

1. No matter which option I use for General -> Reply message settings - even when they're disabled at all! - every Test -> SMS message result in my devic setting *four* messages - two of them contain:
... and another two contain proper "Test message". So, one click @ sending test SMS = 4 SMS's send.

2. Every click on Test -> *Email* message result in getting one email with proper content ("test email"), + one email *and* one *SMS* with already known...
...content. That is, both 'bonus' email and "bonus' SMS contain this thing.

3. Every use of Test -> Send GPS coordinates result in... Guess what, doubled 'proper' sms with coordinates, double sms with
...content - and that only, if I use SMS as mean of informing about GPS position (from General settings). If I use email only, I get two mails with coordinated, one with already overquoted "doesn't start on boot" content, and one SMS with same content. If I use "both", You can already guess what I get?...

And so goes on, for every option.

+, as always, if I use General -> Reply message: slider open (check) - or any other option checked (from "Reply message" settings), after reboot I get message about keyboard being open etc (when I, indeed, open it), even though *my SIM card hasn't been replaced, and was already on list of valid IMSI*. Which, in my opinion, is either bug, or wrong design of potentially useful feature - we may want to know, that someone found/stolen our N900 and opened it's keyboard, and we want such info send as SMS (most chances, that it will be in GSM network range) or e-mail but *only*, when our SIM card was replaced, or we have sent out N900 SMSCON message to get it into "alerted" state.

Think a while - what is use for "keyboard opened" message, if it is sent every time smscon is running? Even using email only, we don't want to be flooded by such messages, until we need it (due to N900 being stolen or lost).

Same apply for other checkboxes under General -> Reply message - we may want to know about battery state, but not until our SIM was replaced by unauthorized one, or we ask by SMSCON message! etc...

---

Sorry for writing everything in such over-verbose manner, but I reported exact same issues many versions ago, and it seems to me, that I was either misunderstood (in case of "4 messages instead of 1") or ignored, apparently due to misunderstanding again (keyboard slider open/ reply message).

---

Besides that, nice job over SMSCON/SMSCON-Editor, it's really a whirlwind of Development (new version almost every day, and every one with no small changes). Thanks for that!

/Estel

//Edit

+ bonus smscon.log of my tinkering with SMSCON(via editor) since update - keep in mind that number +XXXXXXXXXXX and simillar 'private data' obsfucation isn't error, I just replaced real number, mail, passwords etc in log as post-rendering, before posting on forum. Every possible option was set custom (if not disabled totally).
WARNING! It's also over-verbosed (I wasn't cutting it off, to avoid removing something important), so it's ~400 lines of pure joy.

Also, this is *not* tar file - it's plain .txt. I just renamed it to avoid stupid atachement size limitation (someone, in his etheral wisdom, set size limit for txt files to 19.5KB, sic!)
My uneducated guess, is that option for re-sending message in case of fail is behaving bad (it logs about re-sending message after 15 min, but check time of log entry - it's same moment, of initial call for sending message. So, basically, it's sending twice at once).

/Estel

Please I have a problem with smscon 0.7-4 version and kernel 48, when I want choose other password, I have these message: "the new password hash could not be stored". Please I need your help.

Ahh, you are probably using an older version (versions 0.7 and 0.8 are old in this means). You might consider to install the latest 0.9th (which has also better debugging/supporting aids) or try this (as normal user):

Estel, first of all, thank you for your detailed reports! Im goin to make several responses:

You're right, in test-mode this remainder makes not much sense. I change to skip it in test-mode for next release.

In the log file you send (thanx!), the tests are logged twice with no reasonable amount of time in between, so you got 4 replies instead of 2 (where it should be 1 due to the superfluous "does not load at boot").

May be there is a bug that tests may be triggered unintentionally more than once too easily. Will do more investigation on it....