Tuesday, December 16, 2008


nueGPSSecurity is a lightweight service that sits between your text message client (using CEMAPI and CellCore). It waits for a text message with a special string, and replies back with your location if it is available.

Basically, it is a free (well, donationware) version of one of those anti-theft software packages. The service works in “stealth”, it hides the text messages being sent between you and your phone.

You’ll need a device with built-in GPS for it to work reliably, though it can technically work with a bluetooth GPS unit. To install, simply use the cab below, however – I highly recommend burning it into a ROM (OEM package should be available shortly – it should be rather simple to make your own- see OEM instructions below).

Right now, there is no configuration UI – I am debating whether one would be necessary or not. The only configuration option is located in the registry, which is the PIN number. It defaults to 0000, and if you want to change it, edit:
[HKEY_LOCAL_MACHINE\Software\Wei Enterprises\nueGPSSecurity]

The number will automatically be padded with zeros to the left, so "123” is the pin number “0123”. Enter ONLY a 4 digit number max or you will get unexpected results.

To talk to the service, send a text message:
where pin is your pin number, and action is one of these action verbs:
version: display version number
status: get system status
getpos: text back next position fix (auto-start gps)
help: display this help message
start: start gps monitor
stop: stop gps monitor

So if your pin number was 1234 and you wanted to get the position, send:
!nuegps1234 getpos

After you have sent the getpos message, the GPS will stay on, so you will probably want to send “stop” to conserve battery when you are done. Also note that text message systems are apparently kind of slow, so expect a 1-2 minute delay in getting your message back… Due to the way operators implement text messaging, responses may be VERY slow if you try to text yourself.

Note: There is currently a bug in the way status works, sometimes it returns garbage – I’m looking into that.

OEM Instructions (only if you are burning it into ROM):

Use any OEMizer tool, but add the following registry entries:


Also be sure to add the provisioning XML in the cab (you might need a cab extractor like OCP to view it).


No comments: