Empty Inbox and unable to send sms

[Yeag3r]

Anyone find a fix? None of the above worked.

 

[GSDer]

Guess you didn't get my off-the-cuff reference to Chuck Yeager...
So, you did a Factory Reset and nothing has changed?

Sent from my rooted, debloated, deodexed Sinclair ZX-80 running CM -0.001 using Tapatalk 2

 

[Yeag3r]

Oh my, went right over my head. I did read your response though, but had no idea who the hell you were talking to

But yes, I did try all of the things mentioned and at first it didn't work. But now, days later, it seems to have snapped out of it.

 

[Ozor93]

I changed Micro-Sim on mine. But maybe it got a hot-fix or something. Since mine snapped out of it as well.

 

[kanes39]

Hi all,

I am facing the exact same issue and I have tried doing a factory reset and delete all sms related apps but none of it worked...After a factory reset it seemed to work good for a few days bit later act up again...my phone is stock standard

 

[GSDer]

(Hopefully you're paying more attention than Mr. Yeager was when I referred to him as "Chuck")
Candy,
So everything worked fine after the Factory Reset, but then you started having problems again? Did you install any apps after the reset? Did you keep track of them so that you can uninstall any likely culprits?
There's a high probability that you installed an app (or updated an app) that's causing this problem. Without knowing what apps you added it's hard to make a recommendation on where to go from here, but this isn't typical behavior (unless you're rooted and running a different ROM).

Sent from my rooted, debloated, deodexed Sinclair ZX-80 running CM -0.001 using Tapatalk 2

 

[anyare]

Hello GSDer! I am having the same problem. I think we all appreciate your suggestions (but no dice, unfortunately). It's a peculiar problem that I don't think is caused by an app. It feels as if it's part of the recent software update, as my problem started along with it.

I'm using GoSMSPro, but when the messages disappear (usually happens when I send a group message), it also disappears in the stock SMS app. I can't really pin it but I know the messages are there but the SMS apps (stock or otherwise) seem to have difficulty accessing them. If I close the app and open it again, I'll see the list of SMS conversations I have but if I open one, they'll disappear again. Restarting the phone makes the messages come back to work normally, but it'll eventually happen again.

I think it's OS related, not network or apps

 

[GSDer]

Hello anyare! I think I appreciate your appreciation
I'm not an Android developer/expert, so my ideas/suggestions may be totally useless; it seems unlikely, though, that there's an inherent problem in the OS, or everyone and their brother would be clamoring about this issue, and not just on the Samsung Galaxy S III, since Jelly Bean is used across multiple platforms.

I realize that doesn't solve your problem, though, so maybe we can look at what you have/haven't tried already.
Have you done a Factory Reset, and if you did, were things working fine immediately after? Did you restore any previous SMS/MMS, or did you start fresh?
If you haven't done a Factory Reset that would be the place to start. I'd recommend NOT restoring any MMS (SMS is ok), since I have run across problems doing that.

Sent from my rooted, debloated, deodexed Sinclair ZX-80 running CM -0.001 using Tapatalk 2

 

[Mark Morrison]

It's a Samsung Jelly Bean issue, my Note 2 loses all messaging ability periodically and requires a phone restart. No known cure yet.

Sent from my Note 2 using Tapatalk 2

 

[Kyle Floberg]

Just a thought.... I cracked my S3 screen (vibrated itself off the cliff of a urinal); I had insurance on it with Assurance (or something like that). Anyway, they sent me, as far as I can tell, a new S3. I never had a problem with my old phone, but this phone continually fails to send text messages. Same problem everyone is describing above. I haven't added any apps yet, everything is stock.
I constantly have to restart the phone to get the sms sent - its possibly the most annoying thing in the universe.

Could it be the hardware - bad RF, wifi, PA, LTE, chip? I have no idea what any of those are, but assume some chip controls test messaging. Should I sent it back? Anyone ever had success having Verizon will replace an impaired phone it? Or am I all wrong, and its a software bug.

A lot of questions, with no reward to offer. but if have an answer and the time. I'd appreciate the feedback.... thx

 

[GSDer]

Kyle,
Sounds like you're describing the problem that Verizon users have encountered after the latest OTA about a week ago. If you're a Verizon user, and if your firmware is MD3 (last 3 characters of the Baseband version), then you can either roll the firmware back to the previous release or wait for Verizon to release a fix (supposedly in the works). Might as well hang on to the new phone in either case.
If you're not with Verizon then I don't have an answer for you - sorry.
Edit: after rereading, looks like you are a Verizon user.

Sent from my rooted, debloated, deodexed Sinclair ZX-80 running CM -0.001 using Tapatalk 2

 

[anyare]

Hello again everyone (and GSDer!)!

What I was thinking was that it is a problem with the specific 'strain'/flavor of android Jellybean installed in recent Samsung Galaxy phones (I've read reports of it happening on the S3 and Note2, not sure about the S4). I know that Jelly Bean is used across different phones and manufacturers, but I do know that the phone manufacturers customize it and modify it for use with their hardware.

Anyway, other than restarting, I've discovered (at least on my phone) that by calling my own number (which will get me a busy tone) will fix this issue and return all my messages/let me send messages again. It will cause the phone dialer app (I use stock) to crash giving me this error: "the process com.android.phone has stopped", which makes me believe further that this is an under-the-hood problem with Samsung-flavored Jellybean.

Haven't tried a factory reset --- I can still live with it so I'll just hold off until they fix it over an OTA (I think it started happening after one of the OTAs in the last few months).

How can I tell Samsung that I'm having issues with it though? I've never sent a phone manufacturer an error complaint before.

 

[angehub]

*sigh* no cure yet!
I have had this issue ever since I got my Galaxy s3 which was back in December 2012. It is extremely frustrating because I have to turn off my phone for a few seconds, and turn it back on. I have tried all things mentioned above and nothing works. I am software tester and it drives me crazy not knowing how to reproduce this bug 100%! It just happens randomly! Some times it happens up up to 5 times a week, while other times, it takes about 2 weeks to reproduce. I have had 2 software updates since December and none has either made this issue better/worse. I have replaced my SIM cards a few months ago and the issue still persists. I started deleting a ton of apps thinking that maybe one application had been causing this, almost got rid of all my games lol
I have t-mobile, stock messaging app.