maemo.org - Talk - [Announce] SMScon (control your device with SMS)

maemo.org - Talk (https://talk.maemo.org/index.php)

- Applications (https://talk.maemo.org/forumdisplay.php?f=41)

- - [Announce] SMScon (control your device with SMS) (https://talk.maemo.org/showthread.php?t=60729)

Re: [Announce] SMScon (control your device with SMS)

Thanks for backing me up Estel. I have run out of ideas on where to look for those hidden scripts that initiate the 'change of sim' and 'gps location' commands after every reboot.
There is no point in trying to reinstall smscon and editor and deactivate them. It did not work.
So, as far as I can tell, I should have an smscon-free N900, but I don't.
I could use some help. Anyone? Saturn?

Re: [Announce] SMScon (control your device with SMS)

Major release for the SMSCON project.

With the amazing contribution from Lutz (yablacky) we have released version 0.9.3-1 of both SMSCON and SMSCON Editor packages in extras-devel (see links for the long changelogs below).

In addition, all the code is now public in SVN at the garage site for your scrutiny and proposal/contributions for further improvement.

Warning: Choose your settings accordingly to the contract you have for your telephony functions to avoid unnecessary costs from SMS.

Changelog for SMSCON
Changelog for SMSCON Editor

Re: [Announce] SMScon (control your device with SMS)

Not sure if older versions had the same, but the tabs in the main menu partially missing in portrait mode?
Not a really big deal, I just have to switch back to landscape to see them...

Edit:just noticed you can scoll between the tabs by pressing on the edge of the line of tabs, so forget about my remark.

Re: [Announce] SMScon (control your device with SMS)

Quote:

Originally Posted by ade (Post 1139037)

Thanks, I've missed that in the last update.
Just uploaded a version that behaves better in both orientations.

Re: [Announce] SMScon (control your device with SMS)

Quote:

Originally Posted by refugee (Post 1136747)

Hi,

Please follow the steps.
1. install the latest SMSCON and SMSCON Editor with the application manager
2. (dont close the application manager and) save the log > post it here.
3. close the application manager
4. (open the application manager and) unistall both packages and save the log > post it again here.

All should be fixed now. We have added better scripts to (un)install both applications.

Cheers

Re: [Announce] SMScon (control your device with SMS)

OK, I've installed new version and configured it. Upon using "test" page (SMS) I got "Nokia N900 test message" correctly, but just after receiving it, SMSCON started to spam masternumber with SMS messages with content:

Code:

-fatal error-

smscon_daemon crashed.

only 'priority' keyword argument accepted

I had to killall smscon_daemon to stop sending SMS'es ;)

If I can provide more info that will help debugging this issue, just point me what to do.

/Estel

// Edit
Same message also appeared on e-mail (I've used "both" sms and email as receiver), although only once (no spam as with SMS).

Re: [Announce] SMScon (control your device with SMS)

Quote:

Originally Posted by Saturn (Post 1139141)

Thanks, I've missed that in the last update.
Just uploaded a version that behaves better in both orientations.

Could you tell me what has changed in the last update? I can't see a visible difference, but perhaps because the change is minor.

I'm also having a little issue with SMScon. I reinstalled SMScon and SMScon-Editor, but it made no difference.
When I test sending an email, it responses with "Test initiation failed.". Nevertheless, the mail is send succesfully. A new process is started and stays active. There is also a daemon process from boottime, but it also has a faulty state concluding from the logging:

Code:

2011-12-18 22:54:12[SMSCON] ERROR: Daemon smscon_daemon failed to start.

2011-12-18 22:54:21[DAEMON] CRITICAL: smscon_daemon is starting.

2011-12-18 22:54:21[DAEMON] INFO: Successfully loaded "/opt/smscon/smscon_config" file.

2011-12-18 22:54:22[DAEMON] INFO: Found 1 IMSI code(s) in "/opt/smscon/smscon_code" file.

2011-12-18 22:54:23[DAEMON] INFO: Authorized IMSI code found.

2011-12-18 22:54:23[DAEMON] INFO: smscon auto-loads at boot. OK.

2011-12-18 22:54:23[DAEMON] INFO: Phone battery charge is 95%, charging.

2011-12-18 22:54:23[DAEMON] INFO: Keyboard slider change detection is off.

2011-12-18 22:54:23[DAEMON] INFO: Battery status change detection is off.

2011-12-18 22:54:23[DAEMON] INFO: (CHECKHOST) Checkhost is off.

2011-12-18 22:56:02[SMSCON] INFO: Export to user setting file "/home/user/.smscon-editor/smscon_config" successful.

2011-12-18 22:56:13[SMSCON] INFO: Daemon smscon_daemon was not running.

2011-12-18 22:56:13[SMSCON] INFO: "EMAIL1" TEST BEGINS --------------

2011-12-18 22:56:13[SMSCON] INFO: Daemon smscon_daemon requested to start -test "email1" .

2011-12-18 22:56:14[SMSCON] ERROR: "EMAIL1" TEST: Daemon smscon_daemon failed to start.

These are the processes afterwards:

Code:

root      1727     1  0 22:54 ?        00:00:00 python /opt/smscon/smscon_daemon

root      2049     1  0 22:56 ?        00:00:01 python /opt/smscon/smscon_daemon -test email1

A new email test will lead to a new daemon (email2)

Any suggestions for further debugging?

Re: [Announce] SMScon (control your device with SMS)

Quote:

Originally Posted by Estel (Post 1139215)

Code:

-fatal error-

smscon_daemon crashed.

only 'priority' keyword argument accepted

You can send me the log file at:

Code:

/opt/smscon/smscon.log

I propose after to switch it from the settings to email only to avoid more SMSs until this is solved.

EDIT: could you please also give the output of

Code:

dpkg -l |grep gobject

Re: [Announce] SMScon (control your device with SMS)

OK, I'll upload log in few minutes. Meanwhile, another thing (although, I'm not sure if it is a bug, or a feature ;) ) - selecting "send reply messages on" 'battery status' and ''slide open'', result in (after reboot) message containing battery status /indicating that slide was open even though SIM *wasn't* replaced by one with different IMSI. Which, I think, kill purpose of this command.

Requested log:

Code:

2011-12-18 23:36:04[DAEMON] INFO: Authorized IMSI code found.

2011-12-18 23:36:04[DAEMON] INFO: smscon auto-loads at boot. OK.

2011-12-18 23:36:04[DAEMON] INFO: Phone battery charge is 66%, discharging.

2011-12-18 23:36:21[DAEMON] ERROR: Failed to send SMS to "+48606880774".

2011-12-18 23:36:21[DAEMON] WARNING: Trying to re-send SMS message after 15.0 minutes.

2011-12-18 23:36:21[DAEMON] CRITICAL: <<< SMSCON FATAL ERROR:

only 'priority' keyword argument accepted >>>

2011-12-18 23:36:38[DAEMON] ERROR: Failed to send SMS to "+xxxxxxxxx".

2011-12-18 23:36:38[DAEMON] INFO: (EMAIL) Trying to connect to "smtp.gmail.com:587" (2011-12-18 23:36:38).

2011-12-18 23:36:38[DAEMON] ERROR: (EMAIL) Mailserver connection failure.

2011-12-18 23:36:38[DAEMON] INFO: Message sending disabled by user setting (both).

2011-12-18 23:36:38[DAEMON] CRITICAL: smscon_daemon is stopping on fatal error.

2011-12-18 23:37:01[SMSCON] INFO: Daemon smscon_daemon requested to start.

2011-12-18 23:37:01[DAEMON] CRITICAL: smscon_daemon is starting.

2011-12-18 23:37:01[DAEMON] INFO: Successfully loaded "/opt/smscon/smscon_config" file.

2011-12-18 23:37:01[DAEMON] INFO: Found 1 IMSI code(s) in "/opt/smscon/smscon_code" file.

2011-12-18 23:37:01[DAEMON] INFO: Authorized IMSI code found.

2011-12-18 23:37:01[DAEMON] INFO: smscon auto-loads at boot. OK.

2011-12-18 23:37:01[DAEMON] INFO: Phone battery charge is 66%, discharging.

2011-12-18 23:37:01[SMSCON] INFO: Daemon smscon_daemon started [PID=2237].

2011-12-18 23:37:01[DAEMON] INFO: Keyboard slider change detection is on.

2011-12-18 23:37:01[DAEMON] INFO: Battery status change detection is on.

2011-12-18 23:37:01[DAEMON] INFO: (CHECKHOST) Checkhost is off.

Of course number wasn't xxxxxxxxxxx, i just replaced it.

Result of dpkg -l | grep gobject:

Code:

BloodRose:~# dpkg -l | grep gobject

ii  libsofia-sip-ua-glib3                               1.12.10-0maemo5+0m5                        Sofia-SIP library glib/gobject interfaces ru

ii  python-gobject                                      2.16.1-1maemo2                             Python bindings for the GObject library

// edit
Another minor mistake (?) in SMSCON editor - On tab "general", under "Mobile number of contact" (aka masternumber) is:

Code:

*will change on first command

AFAIU, it's not true - masternumber doesn't change, SMS is just sent twice.

Also, another observation - after testing sms message, I got *two* messages with "test message", and also *two* messages with fatal error - hence the feeling of being spammed. In fact, it's only 4 messages instead of 1 (no irony, just trying to be specific).

+feature upgrade request:
Allowing to start (remotely) reverse ssh is great option, but, AFAIK, now it works only with ssh connection with password authentication. could You, please, implement authorisation via public key - preferably, located @ configurable (from SMSCON editor) path?

The idea is, to create special private/public key part, only for using it with SMSCON. normally, sane usage of public key authentication on mobile device require locking it with password - so, no way to use it remotely, as there is no one on the device to write password - but, special pubkey without password just for SMSCON (thus, creating connection with limited access), would be nice to have.

/Estel

Re: [Announce] SMScon (control your device with SMS)

Quote:

Originally Posted by ade (Post 1139218)

Could you tell me what has changed in the last update? I can't see a visible difference, but perhaps because the change is minor.

Have you changed the font (or use a theme with larger font)?
If you use the standard font then you will not need to scroll horizontally at any window any more. Only vertically.

Quote:

I'm also having a little issue with SMScon. I reinstalled SMScon and SMScon-Editor, but it made no difference.
When I test sending an email, it responses with "Daemon smscon_daemon failed to start.". Nevertheless, the mail is send succesfully. A new process is started and stays active. There is also a daemon process from boottime, but it also has a faulty state concluding from the logging:
...

Any suggestions for further debugging?

Can you reboot your device and test again?