I can confirm this behavior. And to be honest, I'm not able to explain. I did some investigations now and found out that it can't work as expected. Because:

(1) If the phone is asking for the lock code on boot, then this will be the very first question et all. Even before SIM card PIN code is being asked for.

(2) The information whether the phone runs with authorized SIM card is first available after the SIM card PIN code question was displayed and answered by user.

(3) Consequence: Even if smscon would run before the lock code is being asked (it does not - this happens too early in the boot sequence) then smscon has no information about SIM yet. So smscon could neither lock nor unlock the phone depending on SIM authorization status.

This is amazing May be the order of questions was vice versa in earlier maemo/osso/firmware phone versions? I don't know. But this is the only explanation I have why smscon has this (not working) feature still.

Is there anybody having different experience in this issue? If not, this "feature" (and the setting to control it) should be removed in next release.

Wow, what did we discuss lock/unlock issues and either it worked in the past and/or nobody tried it.

To me it seem this way: If the phone was locked on shutdown then it is locked on boot and there is no, or at least no obvious or simple way to change it. May be usb-cable connection can change things. Haven't tried this yet.

BTW: I tried to start smscon earlier in the boot sequence to cope with that situation (namely as service at run level 2, started before lock code question). But I had no success. smscon depends on too many resources that are not yet available at this this time (dbus, network, python run time environment, ...). But even if I would got it run, what to do without SIM card information at this time?