Originally Posted by yablacky

It seems that the error is not that the daemon did not start. The error is that something is wrong in detecting that the daemon got started. Because in the ps list you posted, it seems to be there, even more than once (which is ok but normally should not happen).

So we have to find out why the detection of specific processes in the process list does not work on your device.

Could you please do the following: check if ps shows a process like "python /opt/smscon/smscon_daemon". Then enter (as normal user)

Code:

$ pidof /opt/smscon/smscon_daemon
    ### expected empty result
    # then:
$ ps | grep -v grep | grep /opt/smscon/smscon_daemon
    ### expected something like
    7774 root     15684 S    python /opt/smscon/smscon_daemon

Should you get any other than the expected output please let me know exactly which output you got.