Forums | developer.brewmp.com Forums | developer.brewmp.com

Developer

Forums

Forums:

I've seen on some devices (IIRC, Kyocera KX5 and LG5000 just to name a couple) that when a Brew-directed SMS arrives, andwhen you assign a char* to the dwParam to get the payload, i.e.

case EVT_APP_MESSAGE:
char *message = (char *)dwParam;

the trailing character in the string (before the NULL string terminator) is something "weird." It's usually something like 0x01, 0x02, 0x03 or 0x04. I haven't found anything else in the documentation about this little oddity. Has anyone else run across it, and if so, did you come up with any solution for dealing with it? Or, do you just assume that it's a garbage character and handle it "appropriately" in code?

Thanks in advance.