sms bugs with gingerbread and galaxy SSupport

Last Updated:

  1. annoporci

    annoporci New Member

    Dear all,

    This is my first post on the forum. I have registered precisely to ask about this problem I've been having with my Samsung Galaxy S, running gingerbread, installed via the Samsung Kies software. I have encountered numerous discussions about very similar problems, but have not been able to solve it using those suggestions. After one week of daily attempts, I turn to the expert community for advice.

    Description of the problem:

    Running the default android SMS application, multiple threads get created for the same number.

    This is how it started: I was visiting a foreign country, I got a legit sms from the service provider (smartone in Hong Kong) suggesting that I could get cheaper calls by dialing *131*001 followed by country code and number. I tried it on an sms to see if it would work. It didn't but from then on the sms app started two threads, in a seemingly random way: most of the received sms are listed under a number starting with *131*001 that I cannot reply to. In the process all the past sms conversations were "captured" and listed under that number. To send sms I had to start a new thread with the same number but without *131*001.

    This is what I tried: first, I added *131*001etc as an additional number for my contact, hoping that the threads would be merged. But it did nothing.

    Secondly, after reading some, I used SMSBackupAndRestore to save the sms and modify the resulting xml file. I noticed one difference between the sms in the two different threads, namely, a difference in the service_center, for instance service_center="+852161645501" for the sms listed as *131*001etc and service_center="null" for the properly listed sms. So I replaced every instance of service_center="+852161645501" (numbers varied) with service_center="null". I then reloaded the modified xml file using SMSBackupAndRestore.

    Before the "fix" just described, I had about 2,000 messages listed under *131*001etc and about 5 or 6 listed under the correct number. After the "fix", I had two more or less evenly split lists, of about 1,000 messages each. Plus a third list got created with 2 messages in it.

    As I was doing this, it occurred to me that SMSBackupAndRestore only saves the text of the sms, not the pictures and other attachments. Yet, the pictures and attachments were showing up after applying the "fix", showing that the sms had not really been deleted, merely taken off the directory and upon being re-loaded the android sms app would "recognize" the messages and re-load the pictures and attachments. This means that there is a folder somewhere with the history of my sms. And the android sms app is using information stored there to recreate the *131*001etc thread that I'm trying to delete.

    I wanted to delete all the cache. I couldn't find it by browsing (I'm using Windows 7), so I downloaded some apps to help me, two apps named 1tap cleaner, both worked in a similar way and deleted cache, but obviously not the cache I want to delete since it hasn't solved anything.

    I have deleted all the sms, but double threads listed as *131*001etc still happen with the new messages. Plus now I can't even add a picture to my contacts (when I "edit" the contact, I can only edit the name and number, nothing else).

    Handcent hasn't helped. Even worse because it has a ringtone notification which I disable but immediately reenables itself!

    Any suggestions on how to get out of this nightmare? many thanks!

  2. annoporci

    annoporci New Member

    My question has not attracted any interest so far, am I the only one to have experienced this weird bug? At this stage, it seems that the only way is to access the sms cache to blast it, and I think that means I need to be "root", would you agree that's the way to go?
  3. Rush

    Rush {<>}~{<>}

    I've moved your thread over to the Samsung Galaxy S forum. Hopefully, you'll get a faster response. :)

Share This Page