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

Thank you for camera feedback.

It already should work similar like this. There are two deadlines in GPS coordinate acquisition. Which ever is reached first causes a notification being sent:

• timeout reached (GPSTIMEOUT parameter, seconds, default 1800) and
• accuracy reached (GPSMAXDEVIATION, meters, default 50 - setting is not yet shown in SMSCON Editor)

It seems in your case the phone was located where it was not able to receive GPS satellite signals (deep indoor or the like)?!

Note that the timeout starts again after each successfully received GPS coordinate.

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

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 :confused: 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?

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

Thanks a lot for investigating this.

sequence of events haven't changed since very beginning of Maemo - I always wondered, how SMSCON is supposed to achieve that. I suppose, that no one tried this before :(

USB cable connection won't change that - lock code is persistent even after reflash (although, not asked on boot). there *is* a hackish - yet, 100% safe and working - way to reset lock code to default, by placing certain file in appropriate directory and running it - I don't remember exactly, as it was one of first things I was doing with my N900 (seller had no idea about code he set, and re-gaining it wasn't possible - DES encrypted hash wasn't present at all [!]), but it was something about writing actual asterisks as lock code. Could re-find that utility, if needed.

Although - while it, probably, would allow SMSCON to reset lock code and disable asking for it on boot - it still doesn't answer, how we may achieve that, as different SIM card is recognized (and enabled, at all) *after* prompt for lock code.
---

I really hope, that someone will get an ingenious idea, as for now, it makes - sadly - smscon quite unusable in pair with lock code. First thing thief/people buying is going to do, if prompted for lock code on boot, is to - probably - flash device, which get rids of smscon :/ Our only "chance" to fool them into running N900 with SMSCON, was by providing access to device functionality, when it's stolen.

On the other hand, lock code is *very* essential for other anti-thievery things, like keeping personal files/photos/whatever in encrypted partition, mounted on boot via truecrypt. Such partition is unmounted on every reboot, so short lock code time ensure that - no matter what, even after complete reflash - no one will have access to our encrypted partition/container.

Add to this other use cases for lock code, and we have serious dilemma :/

/Estel

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

How did you achieve this while the phone was locked? Just a hint, please - no exact how-to ;) In my experience a WLAN connection, prerequisite for remote login, is not available at this time.

Despite this, in my opinion the lock-code/SIM code dilemma should not be solved by somehow resetting the lock-code. Even less automatically on boot. The regular owner's lock code should persist even if phone is in thief or finders hands. May be a solution is, if smscon could change boot time order of questions to first SIM code and then lock code. Where SIM code may be skipped as usual but lock code can't. In other words, to reach a phone status that is similar to when a regular user locks the phone.

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

I've used to have security lock code enabled in every phone which I've had. So when phone is booted, it asks the security code. But because the known reasons with SMSCON, I do not have that setting anymore in N900.

Therefore, even when the phone is not lost or stolen,
I'd prefer SMSCON (optionally) to lock the phone after it has been booted up and SMSCON daemon has started. Is it possible?

(2nd solution)
Maybe it could even start an app, which doesn't allow itself to be killed nor switched to the background, and which will grab keyboard and touch screen. The unlock code would be given with the physical keyboard and if it would match, then the application would quit and free the access to the device.

If the SIM card had been changed, then based on the user settings either lock, do not lock, or run some other blocking or non-blocking app.

Edit2:
Also auto-locking after inactivity (1 - N min) should be inside smscon daemon, because the system setting for that cannot be used.

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

Hi guys,
too many healthy and technical disscusion here now a days( since i am noob i dont understand too much)

but as Estel says

so i think i should test it too!

i had some dead SIM cards(old sim cards which are not active now so i test with them)


but here in my case it is absolutely opposite happanes.

my n900 never ask for lock code on boot :mad: with both settings "Unlock Device" checked and unchecked.






NOTE:-

1. i am using PR 1.3
2. my smscon editor is 0.9.12-1
3. and smscon is 0.9.19-1
4. i checked with dead sim cards that on boot show "SIM card Registration failed"

EDIT: may be i should check with active sim cards

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

Yes, I think so. There could be a very small timing window until smscon starts up and does the job. Hackers which know what's going on could use the time to cancel locking. May be this risk, should it really exist, is only theoretical or so minor that it can be ignored.

Generally this to me sounds like a possible solution.

Yes, whereby smscon would only lock/unlock and try to notify the owner who is responsible to send further commands to start apps.

I don't understand why. Could you please explain?
-- OK, I got it. Because locking is turned of et all. Yes.

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

This has nothing to do with smscon. Do it like this:

• (1) First enable N900's own device lock function.
• (2) Then lock the phone explicitly. When locking the first time the phone will ask for lock code (just to ensure there is anybody who knows the code before it really goes locked).
• (3) Tab on the outside of the "enter lock code" window and the phone asks for shutdown. If you do so, it will ask for lock code on boot.

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

Maybe, if I want locking, smscon could enable the system setting after booting, and disable it on shutdown. This way the lock code would not be checked at boot time, default system locking would be switched on afterwards, and (hopefully) not too much extra code would need to be added to smscon itself. Also, if some attacker manages to kill smscon on the running phone, default system locking would still be activated.

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

The problem is, that with locked phone, we lesser our chances to retrieve phone - as normal solution for thief - when facing locked phone - is to flash it (or give to someone else to flash). This way, without knowing it, he also get rids of SMSOCN.

Optimal solution would be to have lock code present - to protect device from spying eyes and for protection of truecrypt partitions/volumes - but, to have a way to auto-disable lock code, when phone is in "stolen" state. This way, we present thief with "usable" phone (without access to our private things via truecrypt), so odds are, that he won't even flash it.

Ho ever, I've no idea how to achieve it :(

@yablacky
Method I've described (to reset security code) is only useful, when device have lock code set, but not asked during boot. Of course, You're right that there is no way to reset it when it's asked during boot, other than flashing.
---

Maybe SMSCOC should have a small part run via U-Boot/backupmenu? This way, it could reset lock code in a way we can do this via recovery console, manually (generic one, or bundled in backupmenu). After all, with proper mounting, everything can be achieved from recovery console - so, some script to automaticaly disable lock code, when pre-defined conditions are meet, should work too.

/Estel

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

Hi guys,

Not sure if I fully understand your problem but let me just explain the reason behind this feature and how it was intended to work (it is already explained somewhere in this thread too, but too difficult to find it).

Two sets of people/uses only considered:
A) don't care about the contents and don't have a lock - the phone is more valuable to them
B) content is the most valuable but can't be bothered with a lock always kicking in - phone can be spared.

Note: none of them uses a lock code but they have set one.

USAGE:
A) sets the option "do not lock on new SIM"
B) sets the option "lock on new SIM"

- when A loses the phone the phone does not lock whether someone found it or not and the owner tries to recover it.
- when B loses the phone the owner tries to recover it. If the SIM changes it means that someone has already found it and tries to own it. In that case the lock kicks in and (unless he has read this forum) he has some data protected.

That's it. If you want a locked phone, i.e. with an enabled lock in the settings, to be unlocked when a new SIM card is inserted you will need to modify the lock functionality in Maemo. Not so easy..

On the other hand, if the phone can be unlocked by just changing the SIM why did you put the lock code in the first place?

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

My idea is this:

* set a lock code in the settings, but disable autolock (which includes boot-time check)
* at boot time, have smscon check for SIM change
* if known SIM found, enable autolock (if wanted), possibly checking lock code before continuing boot process
* if unknown SIM found, keep locking disabled (if wanted)

* at shutdown, have smscon disable autolock so the lock code is not checked by the system at next boot

A thief, after changing the SIM, would not be asked for the lock code and (hopefully) would not flash the device. We could try to recover it using smscon. Our data is hopefully encrypted and safe. :)
Does that make any sense?


To prevent buddies from tampering with the device while I'm not in the room, for example. ;)

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

Because data from mounted TrueCrypt partition are accessible to everyone, even the thief - and we need it to be mounted, to allow normal usage (so, for example, our SMS'es, mails, contacts, photos work as usual, despite being on encrypted partition).

Yet, when lock code kick in, someone need to turn device off to remove lock code - either by flashing, or *if* SMSCON option would work like we expected it to (so, changing simc would disable lock code). This (reboot) makes truecrypt partition unmounted again, with password/keyfiles prompt on new boot.

This way, if someone boot my device, but fail to provide lock code and keyfiles, she/he is presented with device without my contacts, messages, mails, passwords, etc.

It makes sense, but suffer form what I've written above - this way - without lock code kicking in every few minutes, our encrypted, yet mounted TrueCrypt partition's content is exposed to everyone.
---

I just hope, that we'll be able to found a way, that will address people that, at the same time. care about their private files/contacts/etc, and value their device.

/Estel

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

To prevent misunderstandings: there is no option like (B) yet ;) Currently smscon has a (not working) "UNlock on new SIM" option only.

But whether or not we find a way to change things that device lock on boot suits our needs, a option to "lock on new SIM" makes sense in any case.

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

Estel, please could you give a brief explanation on how the device lock and device lock code is related to TrueCrypt partitions? Is it enough to know the device lock code to mount and access TrueCrypt partitions or is there a separate password mechanism? And should this be the case, when is that password been asked for?

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

SMSCON 0.10.1-1 has been queued for loading into fremantle extras-devel repository.

Changes:

• FIX: Wrong access modes for smscon_boot file.
• ADD: New options for SIMUNLOCK to control automatic phone un/locking depending on SIM:
  • "no": Do not automatically change phone lock status. This is the old "unchecked" status of SIMUNLOCK.
  • "yes": Try to UNLOCK the phone if new (or no) SIM is detected. This option is left for downward compatibility only and does probably not work (old "checked" status). Don't use it.
  • "locknewsim" : New: Automatically LOCK the phone if new (or no) SIM is detected.
  • "lockalways" : New: Automatically LOCK the phone regardless of SIM.
  The SIMUNLOCK option is evaluated each time SMSCON re/starts. Locking takes place after the SIM pin has been entered (or was skipped). This means the phone is ready to receive SMSCON commands. A thief or finder is only allowed to shutdown the phone.

This version hopefully provides solutions for the device-lock/sim-lock dilemma. Please test a little and give me some feedback. The idea is, not to shut down the phone in a locked status. This way the phone comes up with SIM code question first. If SIMUNLOCK is set to new "lockalways" option then SMSCON will lock the phone immediately no matter which SIM was present. Since SIM pin was entered already, the notification about new SIM was sent and the phone can be controlled but is locked from finder or thief.

Note: The current version of SMSCON-Editor does not yet support the new option values "locknewsim" and "lockalways" and will reset the SIMUNLOCK value to "no" or "yes". Please be patient and while testing this extras-devel version of smscon and use the xterm command line to set the SIMUNLOCK option like this, for example:
No effort was made to change device-lock settings before shutdown. I found out that this is much too unreliable. Shutdown comes fast and SMSCON usually didn't get a change to prepare things.

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

SMSCON 0.10.2-1 has been queued for loading into fremantle extras-devel repository.

At a glance:

New option EMAILSENDER fixes some SMTP connection problems. (thanks to Casey aka doctorcolossus).

Changes:

• NEW: New smscon option EMAILSENDER. It is an email address like EMAILFROM.
  If configuration upgrade takes place, the default EMAILSENDER is empty.
  Empty means everything works as usual. Usual means that the meaning of
  settings EMAILFROM and EMAILSENDER is switched for historical reasons:
  * The EMAILFROM setting is used as technical sender in the email's "Sender" field.
  * The "From" field, the logical sender, is generated by SMSCON.
  Unfortunately some SMTP server complain about that generated "From" field.
  This was reason for this fix. In this case you set the new EMAILSENDER
  option. If EMAILSENDER is set to non-empty email address, then both
  settings are used as their names propose:
  * EMAILSENDER is used as technical sender ("Sender" field) and
  * EMAILFROM is used as logical sender ("From" field)
  On SMTP problems try to set both options to the same email address.

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

Hey, just tried to reboot after the new SMSCON and new SIMUNLOCK setting which I set to "lockalways".

The locking thing works now OK, after smscond has been started, thanks!

But, it doesn't have to send SMS now every time when phone is started and autolocked. Only if the SIM card has been changed. Now it does send SMS every time although the normal use case the phone is just booted up.

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

You are right. I will change it.

I was going on using the "lockalways" option and found bad news: If the phone gets locked via "lockalways" everything is as expected, namely phone is "SMSCON-able" but finder/thief can't use it because its locked. User can only shutdown+reboot. But in this case, the lock-code question comes first again, before SIM-pin question. Now we are at same point we've been already. Means: For those regular users which make use of device locking et all the "lockalways" option provides only and exactly one more chance to contact the phone in cases where finder/thief reboots it (no matter if with/or without new SIM).

This, I think, is a better situation to them as before. But not perfect. I can imagine even better phone behavior. As far I can see, it ends up in not making use of built-in device lock functionality: A "device lock" we need:

• must behave as a lock concerning our private data which is on the phone.
  Reason is evident.
• must not behave as a lock concerning phone usage (sms, telephony, network, camera, microphone, sound, sensors, etc...).
  Reason: Even SMSCON depends on that stuff.
• must make a finder/thief think that it is not locked.
  Reason: A locked device is unusable and a good reason to turn it off, throw away or re-flash it.

So there is still work to do.

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

Maybe smscon doesn't have to implement it all. Why not co-operate with TrueCrypt, if user wants to have better security.

When the phone boots, /home/user/ (or /home/user/MyDocs/) would be TrueCrypted.

SMSCON when starts, asks "lock code", which at the same time is TrueCrypt password so /home/user (or /home/user/MyDocs) can be mounted. User can also bypass using "Cancel" button, but then /home/user/MyDocs is not mounted and the device has limited access and workings.

Then again, maybe SMSCON doesn't need to know about TrueCrypt at all. When the device boots, user has to oneself to mount TrueCrypt device by clicking a shortcut in the desktop.

TrueCrypt would make the device's user data really secure also against copying when stolen. Security code itself won't protect data.

But at least if SMSCON would have its own locking mechanism, which when powercycled would still allow SMSCON to be started before the lock code, that would be great.

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

As long as the password to mount TrueCrypt partitions is also stored on the phone, there is no security. Same applies when there is a mechanism to mount those partitions just by a click on a desktop button. In these scenarios only the built-in device lock provides security. But it provides same security to ordinary, not cyphered file system as well. OK, with the exception that the later ones can be examined using hardware technique - but that's not the point.

Those users mounting TrueCrypt partitions only after interactively entering the TrueCrypt password don't need device lock on boot. What they need is a mechanism to unmount the partition after a while the user is inactive (what device lock on activity timeout would provide [edit: not exactly but in effect], would device lock be used).

Its appropriate and convenient to use the build-in device lock in conjunction with TrueCrypt if the device lock password opens everything.

On the other hand, its inappropriate to use the build-in device lock in conjunction with SMSCON because it disables SMSCON on boot.

One possibility to make TrueCrypt and SMSCON match in this issue leads to what I've said in earlier post: We need a different kind, look and feel of "device lock".

Its nothing that SMSCON should provide by itself, that's right.

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

If SMSCON would use the same password for unlocking the device and mounting a Truecrypt volume, SMSCON just needs to save the strong-collision-resistant hash of the password to check if the password is matched and then use that same password to mount TrueCrypt. Then clear text password is never saved on the phone.

Just if SMSCON is going to have its own locking mechanism, and user wants also to use TrueCrypt, it would be convenient to have the same password to unlock and mount the Truecrypted device and in the same time after phone has booted.

Ofcourse, if there is a desktop button to mount TC volume, it also has to open a dialog for asking the password.

Also as the device lock code can be cracked (it uses weak encryption as we know), one should not use that security code as a TrueCrypt password. But in SMSCON strong collision resistant hash algorithm, (for example sha512sum which is already ported to N900) can be used instead to store the verification code to check if TrueCrypt password is OK and unlock the device.

But yes, own "smscon"-style of locking policy would be good. One way is to put some of those critical files to that TrueCrypt volume, so for example some library which is needed by some restricted program, is really in TrueCrypted volume and in the /usr/lib there is only a soft link to the actual file. This would of course break when the said restricted program is upgraded to the newer version with apt-get, but there could be some "re-restrict" button in the SMScon-editor to fix it (or even if going to be really professional, some tricker in apt-get which would automatically fix things after upgrade).

For example to restrict calendar working in the smscon locked mode, put libcalendar_backend.so.0 from /usr/lib/ to /home/user/truecrypted/lib

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

edited alot the above message few times, so .... (nothing here)

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

zimob, encrypting whole /home/user is extremely bad idea. You do *not* want to be in need to FIASCO reflash, after doing so.

Proper way is to have dedicated partition encrypted via truecrypt, files moved there, and symlinked.

yablacky, You described it correctly - the one and only benefit of device lock code re truecrypt, is that it makes device unusable, until at least 1 reboot (either, if lock code on boot isn't asked - device locked manually - or, to reflash, wchich, obviously, require reboot). Rebooting make already mounted TC partitions unmounted, so no access to them without password and/or keyfiles.
---

Ideal solution, would be to, indeed, have some kind of "lock code" replacement, that, upon failing, result in unconditional unmounting of all TC partitions. This can be tricky, as files on mounted Tc partitions are - typically - in use (by messaging, contacts, etc), and I've observed - many times - that even forcing unmount doesn't work. a workaround, would be to reboot unconditionally upon fail to "unlock", but it would be very irritating - in case of accidental mistakes.

Of course, there is also dilemma, how to *not* "scare" thief - yablacky perfectly described it, we need solution, that make phone pretend to be in usable state.

It require some thinking, as - for example - messages, contacts, etc, stored on truecrypt partition and symlinked, behave in weird way, when don't have access to TC partition - basically, it "seems" to work, but don't save changes, etc. Such oddities could make thief/ new "owner" to reflash anyway, getting rid of SMSCON in the process.
---

i'm sure it's achievable, but would require smart programmer (yablacky, i'm looking at You ;) ) coming with ideas to overcome problems mentioned above, and, of course, implementing those ideas.

/Estel

// Edit

for example, problem with usual things like messaging, contacts, etc, being symlinked to truecrypt part, yet, not having access to it (when new "owner" uses device) - it would require quite complicated logic, to re-create symlinks pointing to "disposable" (i.e, worthless for true owner) location, that got deleted (and truecrypt symlinks recreated), as soon as proper encrypted partition is accessible again.

It sounds PITA, but, in reality, would require few relatively simple (yet, well-tested) sh scripts. Or anyone have better idea?

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

I do no use TrueCrypt partitions yet, may be I should to get some experience :D

Its just an idea, but instead of changing or rebuilding symlinks, it could be possible to use the effect, that mounting a file system hides, while mounted, the content that was present at&below the mount point. Means: the mount point, while nothing mounted, could provide empty or fake data. Of course open files in either location could rise problems while mounting or dismounting "true" data. Its just an idea.

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

How nice. I lost my N900 yesterday in a night club.

Few questions.
"'Call' will issue an outgoing call to you."
Does this call to the number which sent the "Call" command, or to the master number?

And what happens when there is several Smscon commands coming at once in several SMSs when if the phone is turned on. Will Smscon do them all orderly, for example two "Call" commands from 2 different phone numbers?

I had setting "lock always" on. Now I am thinking what to do.
Already sent "Camera" and "Trackon" commands, but no delivery message yet received. I know the device had empty battery when I lost it.

Now I regret, I didn't configure remote purge script. I could easily send "Unlock"if I could first "rm -fr /home/user/MyDocs/*" somehow.

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

Anyway, if you are going to build Smscon own locking mechanism, please implement it so the TrueCrypt mounting could be done later then with the same password. So use fairly strong encryption (like sha512 hash).

And yes, hiding critical files under some unmounted volume (even without TC) would work OK also. In fact, it may slow the device down if software libraries are behind TC, so it may make sense to keep those restricted files in non-TC volume even if TC-support is added to Smscon. Or user can choose how secured restrictions he wants to use.

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

Sure. I meant something like /home/user/.truecrypted.d as a mount point to VC-ext2-volume somewhere in /home/user/MyDocs or if user wants, in SD-card somewhere. The TC-volume path should be configurable.

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

I hope you get it back !!

It calls the number the command comes from. It command comes from remote command server (CHECKHOST) it calls the master number.

Most of commands will be worked of stack-like whereby an new incoming command interrupts the current one and later comes back to it.

At least two COM_CALL seem to work simultaneously. But ensure not to call the same number twice! Because the receiving phone is busy with the 1st call, the 2nd call may go the mail box. Then you have a serious problem to cancel the 2nd call. There is no such SMSCON command (nice to have: could cancel finders/thiefs calls)

If you didn't get any SMSCON notifications it may not have received your commands. On the phone you're sending the commands from, you could enable sms delivery notifications.
If battery was low its probably empty now. Instead of COM_TRACKON I recommend a COM_LOCATION command. Tracking must be turned of explicitly, and it is a battery hog.

Good luck!

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

Lately GPS locking on that N900 has been extremely slow, I do not know the reason, so I thought Trackon would eventually send the accurate enough coordinates, where Location would fail and send coordinates centre of country.

Yes I have sms delivery notifications on, but no delivery yet.

//edit

One thing which came to my mind, whether one has locking set on or off, the initial blue "NOKIA" pic and the handshaking animation could be replaceable in SmsCon-Editor. It would help if when booting the device the screen would show a pic which would read something like: "Please return this device if lost. $20 reward. Send email to XXXXX@XXXXXX". Or do you guys think it is out of scope of SMSCon-editor? Anyone can hack it oneself also if finds the instructions, but it would be more user freindly in SMSCon-Editor.

Also, maybe out of scope, but these features (NFC,BT,WLAN,GSM cell proximity alarm) could be in Smscon.

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

The main problem is you would have to make an individual video for each person. I have done this and it works well.
Also you can use the CUSTOM_COM to send a return to Onwer screen.
Anybody wishing to do these see link to previous my post below.

http://talk.maemo.org/showpost.php?p...postcount=1100

Another idea is the secure screen can be edited to display contact details.
Using the link below I edited the text on my "swipe to unlock" and the "Enter Lock Code".
I have edited enter lock code to:-

Enter lock code or return to onwer at (postcode)(phone no)

http://talk.maemo.org/showthread.php?t=69249

I have done all of these to my N900's so hopefully combined with SMSCON, my phone would be returned if lost.

I would hope the hildon banner custom command would be fairly easy to include into SMSCON, although it's the least useful. As for the others they maybe hard to implement.

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

I just realised I should have tested Smscon more lately with another phone. I used to do it in the start when Smscon was published, but lots have changed since then.

In the latest version, if the COM_PREFIX is Smscon, should for example Location command to be sent in SMS like:
Smscon Location
OR
SmsconLocation

Space or without space?

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

The N900 is not GPS-online all the time, like other phones may be.
Particularly if assisted GPS is not available, it takes minutes of time to rebuild the GPS almanac that contains info about satellites. Tracking saves nothing. Simply spoken, tracking are repeated location commands.

I spoke about delivery notification on the phone at which you SEND the sms command ;) It's a service of the telecom provider. There should be a #xxx* code to enabled it (try google).

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

without space. Don't forget to add the suffix if you defined one.

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

Yes I have that setting set, and none of the SMS messages have reached the phone yet. Maybe the finder doesn't have a charger, because I know it had empty battery and that is one reason (long story) why I lost it.

Also my N900 had these weird booting probs, so pressing the power button "the right way" maybe not be success experience for the finder.

I am using Nokia N95, where there is a user friendly setting where SMS delivery notifications can be turned on in telecom providers system.

Ah, so no space. All command this far (if they ever reach the N900) will fail then.

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

zimon, keeping thumbs for You regaining Your N900!

As per slow lock - You've been, probably, using supl.nokia.com as supl server - Nokia, lately, did something to deny access for older devices. You should use supl.google.com OR, as lma suggested (and created), supl proxy on device, that seems to "sanitize" contact to supl.nokia.com (which proves, that disabling it for N900 is done on purpose).

/Estel

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

Oh s.h.i.t. that is why GPS locking has been failing lately then. I did check just the other day I had A-GPS on, and supl.nokia.com was there.
I have missed totally this information in t.m.o.

//edit

I find it useful now, that one could send several commands in one single SMS, something like:
"prefixUnlock, prefixLocation, prefixCall, prefixLog"
And I've before suggested prefix would really be a "password", so the set of Smscon commands sent by single SMS message could be just:
"prefix Unlock, Location, Call, Log"

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

SMSCON 0.10.3-2 has been queued for loading into fremantle extras-devel repository.

Change log:

• FIX: Don't send SMS notification on "lockalways" if SIM is authorized (but stil lock).
• FIX: Completely established SMSCON as a system service that is subject to job control. This way SMSCON gets notified and stopped regularly on shutdown. This is a prerequisite for preparing things that have to do with device locking. Further, SMSCON is now restarted automatically on unexpected termination e.g. in case of errors or other events.
• FIX: Minor fixes in installer if smscon is installed the first time.

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

For your information:

as with smscon 0.10.3-2 the smscon-editor 0.9.12 does not correctly indicate if smscon loads at boot (shows always "no" even if loading at boot is in fact enabled). The next editor version should fix that.

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

Hi,

first of all: cool stuff!

Two questions using 0.10.3 on N900:
configured:
COM_CUSTOM = 'Script*'
COMMANDREPLY = 'no'
SILENCEDEVICE = 'yes'

and
Works so far but two problems:
- I always get an SMS back like -script-
Script [u' blueon'] executes in BG [PIDs=4532].
-> Any way to prevent/silence this?
And silence doesnt work:
What I basically try to achieve is turning BT on/off by SMS and silence the sms-sound for only commands to smscon(if possible at all).

Thanks,

Michael