i face a different issue now. i hv managed to find a way for the conversation app to update itself. however. i hv issues with the yellow notification bubble.
first, it shows the old contentof the sms. i can live with that. but when i tap on it, it opens up a conversation view for the new sms and it shows the old content as well even though the sqlite db has been updated and the conversation ui too has been updated to show the new contents of the sms.

some kinda caching going on??

which component / class handles all this?

is there a way i can force the conversation / thread view for the sms to be updated?? it seems disconnected from the main conversation view (the one that shows the list of smses).

i checked dbus and saw the RefreshHint signal being issued when i do some stuff in the conversations app to change the underlying messages. manually issuing this signal with dbus-send does nothing. sigh.

guess this will have to be a limitation that i have to live with.

to anyone interested in this little script, i've attached it in this message. btw, i don't take credit for a lot of the code inside. i'm new to python so i just went around piecing bits and pieces of other people's work.

installation is simple enough. drop to x-term and run it in the background like so "python NameLookup.py &"

it currently watches for incoming smses from "Maxis" and "Voicemail". that's the way it works for the telcos where i live anyway. i could change it to be more generic and watch for any sms messages that has phone numbers in the body and do a name lookup if people are interested.

thanks.

fixed some stoopid bugs in the script during text parng. here is the updated version.
i've also changed the behaviour so that any incoming smses with phone numbers in them gets the name lookup treatment. probably more useful to everyone.

hv a nice day

Works on DiGi (MY)... ^_^

thank you. oi, reply to the draw something request la.... :P