Help Text probs after unlocking phone and swapping sim, please help

[Mo M]

Hi I wonder if anyone can help me. I have a Samsung Galaxy Ace S5839i that was locked to vodaphone and I was using a Sainsbury mobile sim. But it kept cutting out a few seconds into the calls, or the other person wouldnt be able to hear me after a few seconds but I could hear them. Mobile reception is bad here, so I got it unlocked yesterday by a guy in town with a stall. Today I have put my asda sim in it as it has always been ok in my old back up phone. Now I find I can make calls and receive them ok but if i write a text and send it, it seems to just disappear, I cant see it, but the other person gets it. If someone texts me, I receive an alert but when I go to it there is nothing there.
When I look at the log, it is all from when I had the old sim in the phone, there is no record of anything that I have done since swapping sims. Also when I turn the phone on the first thing that happens is that the vodaphone logo and jingle happen, even tho it is no longer on Vodaphone.

I phoned Asda mobile and the young girl that I spoke to said that it sounds like it hadnt been unlocked properly. Im confused as I can make and receive calls so it is unlocked but texts and the logs of my actions are messed up. Surely its either unlocked or its not?

Sorry for the long message but I am not smartphone savvy at all (or mobiles in general)
Dont know whether to take it back to the guy or if its even his fault. When I told him about the calls cutting out he said the software needs reinstalling for a tenner extra, but I opted for having it unlocked 1st to see if it was a problem with vodaphone reception where I live. I think if I go back knowing nothing he will say the same, although the sim swap has sorted the call cut out

Any help gratefully received, thanks

 

[Hadron]

The Vodafone logo and jingle are a red herring. Those are stored in the phone's software, and will be played on startup whether the phone is locked or unlocked and regardless of what SIM you put in the phone. So you can just ignore them, because all they mean is that it was originally a Vodafone handset.

It does sound very much like the original cutting out was a reception issue. So that just leaves the message thing. And as messages are sending OK, and you are getting notification of replies, it's simply a question of why your message app isn't displaying new messages (incoming or outgoing)?

The commonest cause of things like this is if the time or date is set wrong. What happens then is that your phone thinks that your new messages are much older than some of the older ones, and because the app always shows the latest messages you don't see the new ones at all unless you spot what's happened and scroll back far enough. So check the date and time on your phone: if they got scrambled during the unlocking or when you changed SIM then that could be your problem. And that's quite possible with an old phone: the backup battery on the motherboard will be dead by now, so when you remove the battery (to change SIM) it will lose the time, and if it or you didn't reset both time and date that could cause this (especially since the date would probably set itself to 1970!).

Otherwise, can you try installing a different message app? I suggest Textra, because it's quite small and simple. Then just open it up and see whether you can see any newer messages you sent or received since the SIM swap. Messages are not stored in the message app but in a central database, which any message app can access. So if the problem is just the current message app not displaying stuff then they should be visible to a different message app. If on the other hand the problem is that they are not going stored in the database (more likely, if I'm honest, but worth checking) then neither app will be able to see them. In that case we'll have to work out why that might be.

But try the time/date thing first, because I reckon that's most likely.

 

[Mo M]

The Vodafone logo and jingle are a red herring. Those are stored in the phone's software, and will be played on startup whether the phone is locked or unlocked and regardless of what SIM you put in the phone. So you can just ignore them, because all they mean is that it was originally a Vodafone handset.

It does sound very much like the original cutting out was a reception issue. So that just leaves the message thing. And as messages are sending OK, and you are getting notification of replies, it's simply a question of why your message app isn't displaying new messages (incoming or outgoing)?

The commonest cause of things like this is if the time or date is set wrong. What happens then is that your phone thinks that your new messages are much older than some of the older ones, and because the app always shows the latest messages you don't see the new ones at all unless you spot what's happened and scroll back far enough. So check the date and time on your phone: if they got scrambled during the unlocking or when you changed SIM then that could be your problem. And that's quite possible with an old phone: the backup battery on the motherboard will be dead by now, so when you remove the battery (to change SIM) it will lose the time, and if it or you didn't reset both time and date that could cause this (especially since the date would probably set itself to 1970!).

Otherwise, can you try installing a different message app? I suggest Textra, because it's quite small and simple. Then just open it up and see whether you can see any newer messages you sent or received since the SIM swap. Messages are not stored in the message app but in a central database, which any message app can access. So if the problem is just the current message app not displaying stuff then they should be visible to a different message app. If on the other hand the problem is that they are not going stored in the database (more likely, if I'm honest, but worth checking) then neither app will be able to see them. In that case we'll have to work out why that might be.

But try the time/date thing first, because I reckon that's most likely.

It's working fine after setting the time and date again. Thanks for your help