It seems today my phone quit receiving all text messages. I'm on Skyraider 1.3 and the .09 Radio. In the middle of the day I starting having people tell me they sent me messages and I never got them. I since reflashed my ROM with no wipe and updated to a new radio. Neither helped. any thoughts?
Related
So this is an issue that I have seen many a variation on, but none quite like this. The issue is that some texts from folks I receive fine others are sporadic. It seems to vary from day to day and person to person. I can receive a text from someone and respond then not get any other from that person after. Others I gave been able to receive from in the past but do not receive now. I am running GSB 2.2 with the latest vzw radio for the Eris (2.42.01.04.27), using GO sms with the stock messenger installed, but notifications turned off. I've tried a reflash, Full wipe and Flash, *22899, APN backup from a 2.1 rom, tried the spn provided by roirraW "edor" ehT no change. This has happened with chomp also. I am at a loss. It's a shame, because work shed has made a awesome phone out of my little Eris. Any thoughts?
Missing Texts solved
After some experimentation on my part I have discovered that as GoSMS states in its help section, you can remove the stock application but is not recommended. That'll teach me to read more closely before removing apps . So a heads up for all you GOSMS users out there. leave the stock app installed. I have had zero issues with texts since I updated to a newer version of GSB, which reinstalled the stock sms app.
I am running SHIFTS3NS3 1.6 with lean kernel 5.01 set to normal...
Since last Friday I can not receive TXT msgs properly. I was using Chomp SMS and read all the threads that I could find and could not find anything about it.
Pulled battery, rebooted, cleared cache, installed 2 different SMS programs... received 2 TXT messages and then... nothing.
Does anyone have any suggestions?
Know of any threads that I have missed?
Thanks...
Did your phone get Unprogrammed? You may need to call in and activate it again. I had that happen to me once when I was flashing roms.
I can still make calls... I can send txt... Could it still be deactivated?
No if you can make calls you are fine. Could be an outage in your area I have had that happen before.
Try reseating the sim card
king.james said:
I am running SHIFTS3NS3 1.6 with lean kernel 5.01 set to normal...
Since last Friday I can not receive TXT msgs properly. I was using Chomp SMS and read all the threads that I could find and could not find anything about it.
Pulled battery, rebooted, cleared cache, installed 2 different SMS programs... received 2 TXT messages and then... nothing.
Does anyone have any suggestions?
Know of any threads that I have missed?
Thanks...
Click to expand...
Click to collapse
What Leak is SHIFTS3NS3 1.6 based off of. If it is a GB leak prior to 605.5 there is a known issue.
Some phones will receive some but not all SMS messages. The GB 605.5 leak seems to have corrected the issue.
If SHIFTS3NS3 1.6 is based off an older leak and you love it, extract the message.apk from 605.5 leak and install it on your phone
I was having this problem on a bunch of ROMS until they were updated
The 1.6 is based off the 605.3 so maybe that is what is causing it.. I have tried everything else listed... The Dev is said to update the ROM to the newest 605.5 soon... so I hope that will fix it. If I knew how to extract the message.apk from the new one I would do that too... but sadly I am not that far advanced yet.
Thanks,
So today my phone stopped getting text messages. I can send them okay as verified by some friends, but nothing comes back my way. Now yes I have considered that perhaps nobody wants to talk to me :sad: but I cannot even receive messages that I have sent to myself.
I had a similar issue back in the day with my Motorola Milestone, but the solution to the problem at that time (data wipe) did not do the trick this time around. So I again wiped data/caches, I reflashed 3 different modems (KP8, KH3, KI3), flashed three kernels (NEAK, latest Siyah, and Abyss 3.0). I also reflashed my ROM (GingerMOD).
Currently I have come to stay on stock GingerMOD (KI3, Abyss 3.0)
I am on the bell network in Canada. Thanks for any help... I kinda live off text messages, being 17 :S
Sent from right behind you
Unsure if this is the correct thread, but I would like assistance.
So I've been texting my girlfriend on viperROM, and it has been working perfectly. I transferred to MIUI the other day, and we were able to text for a few hours, but then I just stopped being able to receive her text messages. She can receive mine. I cannot receive hers, but I can receive texts from everyone else who has tried to text me. I have done a data wipe and reinstalled MIUI, and I've quadruple checked that she is not on my DND list. Any reasons this could be happening? Any suggestions to fix it?
This could be a kernel or baseband issue. Before I upgraded my baseband, I would send out texts and not hear back from anyone until i sent another few texts. It turned out that people would receive all my messages days later (the longest was 3 days I believe), and I would suddenly get flooded with people responding all at once. So, please post whether you're on hboot 1.5 or not and post what radio baseband you're on (you can check both of those by booting into your bootloader). with that information, either I or someone else who's more experienced with this phone than me could better help you out.
um, i'm on the 2.08 ota, and i have hboot 1.5
The problem mainly happened on aosp roms and always has for me at least. People tell me they tried to call me and/or text me and couldn't get through but others can. So I tried virus's new sense rom to see if that would help and she couldn't get through to me either plus I never got her texts. Also, I often get busy signals and call cannot be completed messages when trying to call out.
When on aosp I ru, the enghboot and sense its 1.58. Any ideas?
Sent from my shooter using Tapatalk 2
Flash a stock rom, and call your carrier. They can refresh your device, or re-activate it to fix this problem.