Thursday, September 21, 2006

Phone problem found, but not solved

Siemens M75
I have been unable to send SMS through my phone for some time now, so if you've not received SMS from me for some time, you know why. Too lazy/busy to get my phone fixed, so I'm living with it. Should be fixing my phone this Saturday.. (I've been telling myself this for the past month or so. :| )

Anyway, I think I've found out why my phone can't send sms! It's because of a certain header attached to the outgoing message (virus??) which caused the message to be unreadable by non-robust sms applications.

If your phone can't read my sms, it's because the sms reader on your hp is clueless on how to handle this header, and simply throws an exception.

For those who can, it can either be because your hp is robust enough to recover from the error, or it simply can't be bothered enough to put a finger on the error (ignores header!).

Here's how I found out:
I sent a message ("Test") from my phone over to a GPRS modem and decipher the received data (which shows a lot of other information!):
SMS (RAW STREAM): 06915689450002440A9156393820140000609072818304230B050A03000408A8E5391D
Service Center Address: 6598540020
Destination Address: 6593830241
Protocol Data Unit Type: 68 <----- BUGGY :: Should by 4. An extra value of 64 denotes an attached header!
Reply Path?: false
User Data Header Indicator?: true
Status Report Indicator: false
More Message to send: true
Message Type Indicator: 0
Data Coding Scheme: 0
Service Center Time Stamp: 2006/9/27 18:38:40 (Time Zone:32)
User Data Length: 11
UDL Checksum: Passed

IEI: 0A <---- ID of the belligerent Information Element in header
IED: 000408 <---- Data of the belligerent Information Element

Message: Test

Sunday, September 17, 2006


This is a snapshot of my screensaver.
I found it sort of weird when I first saw it. I couldn't make anything out of it till quite some time later (for those who can, don't be smug - the pic is easier to decrypt than the screensaver itself.)

The screensaver has 3 randomly drifting objects - one eye, one bee, and one 'M' character (which reminded me of the day my dot-matrix printer ran out of ink just before project submission. =|)

The eye is always looking out for the bee, the bee is always flapping its wings and moving randomly as bees do, while the blue M is just looking blue - perhaps because its horizontal stripes are making it look fat or something, I dunno.

Now who got what it stands for? =)

Wednesday, September 06, 2006


Was debugging my GPRS modem application when I noticed this unfamiliar error in my server console:

INFO [Win32SerialPort Notification thread] ( - unknow cmd received =

+CLIP: "91070617",129

DEBUG [Win32SerialPort Notification thread] ( - data availabel on serial port
data received = "P: "91070617",129
INFO [Win32SerialPort Notification thread] ( - unknow cmd received = P: "91070617",129

DEBUG [Win32SerialPort Notification thread] ( - data availabel on serial port
data received = "

+CLIP: "91070617",129
INFO [Win32SerialPort Notification thread] ( - unknow cmd received =

+CLIP: "91070617",129

Then I found out it was someone trying to call me, cos I was using my SIM card as the GPRS connection source in the modem. :|