So since Verizon's website is being stupid I can't ask this on the Verizon forums...
The information displayed in your usage logs on Verizon's website.. is this data that has hit the PHONE or just Verizon's network?
Basically...
I'm using the latest update (my "no call notification" issue seems to be gone), and I have confirmed that I have missed two text messages.
My usage log from the website shows the two missing messages.
However, they are not on the phone.
One COULD be an issue related to deep sleep.
..but the other missing one occurred 5-10 minutes after I had checked something on the phone and manually put it back to sleep (my "sleep" term being "turning off the display").
Thoughts?
Is this an issue with the phone not 'doing anything' when receiving the text message or is this a failure of the network to deliver it from Verizon's servers TO my phone?
The phone is stock with the latest updates, and only a handful of apps (none of which modify calling/texting).
I am thinking of factory restoring it and going back through all the updates.
I talked to a Verizon tech and they said that when it appears in the usage log it means that it DID reach the phone.
Related
I followed Bentenrai's guide to S-Off, Rooting, and Recovery. Internet (both Wi-Fi and 3G/4G data) works, but I am unable to make/receive phone calls or send/receive text messages.
The phone call error occurs after about 2 rings, which says "Error 16 (then in Spanish) Switch 694".
The sms error is: "sms error radio interface resource shortage" with details "cause code:64, error class: 2".
I tried everything from the "Phone does not work after S-Off" thread and was on the phone with 2 Sprint operators for over an hour. The first operator had me update profile and PRL, then had me turn off/pull battery while she did stuff twice to no avail. The second operator (who was mean and treated me like a moron) had me turn mobile networks off and on again, update profile and PRL, and pull battery (yes, she actually wanted me to pull the battery while the device was on; I powered it off first).
Is anyone else experiencing this or has anyone found a solution?
Thank you very much!
Yup, I found the fix. It's really easy! Tell the person to do a "CHLS Refresh", and then restart your phone.
http://forum.xda-developers.com/showthread.php?t=1194460
Thanks! I also just saw the thread in the General section about all the lucky people who achieved S-Off without the error.
I'll call them back tomorrow and report back.
i had the same error after rooting my phone, just try to call any number, and after listen to the message, it will connect you to a sprint rep. they will confirm some information with you and they will tell you that they will reset from their side and ask to turn off the phone for 30 sec and boom, it's a go.
After some thought, I realized both Sprint reps only had me pull the battery for a few seconds. I decided to leave the battery out for about 5 minutes and when I powered back on, I was able to connect to voicemail. I let it stay connected for a bit and then was able to make phone calls and texts. Suddenly, I began receiving Error 67 messages, so I updated profile and PRL. Since then, (knock on wood) everything has been ok. Phew!
Forgot to mention this tidbit of wisdom from the 2nd Sprint rep: She told me my problems with making calls was because there's an outage in my area. I told her that wasn't likely because I was using another Sprint phone to talk to her. She still persisted in saying it was an outage. Yay!
That's it? no other responses to this. My sons phone is a paper weight at the moment. He can't even dial Sprint and nothing else has worked. Anyone have another idea?
EDIT: 11:15pm 9/25/2012 - ISSUE RESOLVED, SEE BOTTOM OF POST FOR SOLUTION
Okay, relevant information first:
Evo 4G LTE on Sprint
HBOOT 1.15 S-ON HTC DevUnlock
Current ROM CM10 Nightlies
Sprint-Google Voice integrated number
Now for the issue:
Texts can not be sent through the messaging app. When attempting to send a text, it will say "sending..." for a few seconds, then I get a notification saying "message not sent". Clicking on this notification takes me to the messaging app where the failed message has a red triangle next to it. When I long press the failed message, it comes up with a menu, and when I click "view details" it says "Error Code 98".
This happens both when connected to WiFi and when not connected to WiFi. It also happens both in my home town, and another town 45 minutes away (meaning the issue doesn't seem to be with the particular tower).
The last successful text sent or received was on Sept 13th.
Calls still operate as normal.
No changes were made by me between when my SMS was working properly, and when it stopped working. (Same ROM, Recovery, Kernel, etc). I haven't downloaded any SMS apps (handscent, gosms, etc) that could be interfering with the messaging app. I DO have the Google Voice app, but I had that when SMS was working properly as well, and the GV app hasn't been updated since March (meaning it shouldn't have changed how it was behaving).
Other peculiar behavior:
In addition to not being able to send texts via the messaging app, it seems that my number is also unable to receive texts. When texts are sent to my number, my phone does not receive them and they also do not show up in my Google Voice inbox. The sender is given no notice that the text has not been received. I am able to send texts from the Google Voice app, and others successfully receive them. When I send a text to myself from the Google Voice app, I receive it in my Google Voice app, but not in the stock messaging app (even though my Google Voice app settings say that texts will be received via the messaging app).
Things I've Tried (Updated: 3pm EST, 9/25/2012 ):
* Turning it off and on again
* Updating CM10
* Changing Google Voice settings (though it's possible I overlooked a setting)
* Factory Reset, Reflash ROM
* Flash Sense ROM, Update Profile/PRL
* Flash different AOSP ROM (Paranoid Android)
Things I've Not Tried (in order of how willing I am to do the things):
* Using an alternate SMS app (GoSMS, Handscent, etc)
* Un-integrating (and Re-integrating) Google Voice
* Giving the EvoLTE a relaxing bubble bath, to calm it down
* Flash Stock, Unroot, Update Radio
So, does anyone know what might cause this problem, and/or how to resolve it?
EDIT: Solution below
STORY:
I called Sprint Support, and had them reactivate my old phone (Evo4G running a CM9 alpha), by giving them the MEID for that phone. At this point I powered the phone back on, and called an activation number that they had given me (888-546-0314). On a Sense ROM, I would have simply updated my profile, instead of calling the number. We then tried SMS on the reactivated phone, and it worked (also, texts began showing up in Google Voice again at this time). I turned off my Evo 4G LTE, then I gave him the MEID for it and had him switch my number back to that phone. After he said he had switched it, I powered the Evo 4G LTE back up, and updated the profile, which I was able to do since I was still on Viper4G (note: I had to update the profile via WiFi, it might have worked over data, but it was taking longer than expected so we cancelled and just use WiFi for the update). Once the profile had updated, I called the test number again to confirm that the phone was activated. When I tried SMS, it worked as it should, including sending a copy to Google Voice.
TL;DR:
1. Find an old phone
2. Write down the MEID of both phones
3. Find a third phone to use to call Sprint (since you'll be activating/deactivating the other phones throughout the call)
4. Call Sprint Customer Support (888-211-4727), and punch the appropriate numbers until you are talking to someone
5. Have them switch your number to the old phone's MEID. Make sure the old phone is activated.
6. Have them switch your number back to the new phone's MEID. Make sure the new phone is activated.
7. Texting should be working on your new phone again.
Notes: The old phone may not be necessary. It may be enough for the Sprint Service Rep to deactivate your phone and then reactivate it. But I figured I would write out the EXACT method that solved the problem for me, since I am positive that this method has worked at least once. I have neither the means nor the desire to recreate the problem, so I will have to leave testing of other methods to the next person that experiences this problem.
Update: Clean flash of Paranoid Android did NOT resolve the issue. Still getting "Error Code 98".
So, this tells me/us this is not an issue with CM10 (which is not surprising, since I have no idea how what ROM I have flashed would keep Google Voice from receiving the texts as well).
This may sound odd but try moving the time up an hour or back an hour, error 98 is a problem with home agent, it's a sprint network error. I don't know of anything else that's helped
Try calling sprint and ask them if they can do anything. When I went s-off I had to call them bc my calls and text had errors. Data worked though.
They pushed something that fixed it in less than 10 seconds. Just wanted me to verify my account.
I tried changing the time 1 hour forward, and 1 hour backward, neither of those resolved the issue.
On hold with the Sprint tech department (it's taking longer than 10 seconds, but hopefully they figure out how to fix it.)
EDIT:
Mini-Update: Flashed Viper4G (a sense ROM), problem persists.
Updated profile and PRL while in Viper4G, problem persists.
Was told by Sprint technical support to press ##6-digit-MSL-here# and edit something, then reboot. Did that. Problem persists.
SOLUTION
The problem has been resolved, and the OP has been edited to include the method used to solve the problem.
If this was a game, Anthonicia would win for being closest (though it took closer to 2 hours on the phone with Sprint to fix the issue, if we include all four calls I made, 20-30 minutes if we only include that final one).
Hello,
Recently purchased an LG V10 with 5.1.1 stock, AT&T, and I've done absolutely no modding.
Scenario 1: sending hangouts data messages over LTE (for example; they are quick and easy to test with) work OK from my end. On receiving phone on different carrier, message arrives in about 5sec. Slower than I'm used to on every other phone I've used but not a big deal. SMS are sent faster and arrive in the normal amount of time which is still faster than hangouts.
Scenario 2: My phone is asleep\screen off and hangout messages are sent from the other phone to mine over LTE. My phone does nothing for as long as I let it stay asleep. But Incoming phone calls to my cell number notifies me instantly and
SMS sent to my phone notifies me instantly.
Scenario 1 and 2 are the same when using Wi-Fi, and with other apps that can trigger notifications when the screen is off. Those notifications only appear after I've unlocked the phone, and some appear only after I've opened the app. The notifications will have correct timestamps but the sounds and visuals only happen once I've picked up the phone and started using it; they all flood in at once.
I've made sure that my settings for allowing notifications (priority it's called on the LG ROM) is set to allow everything.
I've done a lot of searching online and people with various phones (Galaxy S6's most recently) appear to have this issue and it also appears to have a history as far back as Android 4.1. They say the fix is an app that changes the checking times from the stock Android 28minutes or something, down to like 5 minutes. I have tried one that doesn't require root and it has not changed any behaviour that I can measure.
My question is, is this a phone problem? Like a bad OS install from the factory (did i just get a bad unit?) or an APN setting issue (haven't messed with it from factory settings) or is it an Android problem that needs a bug submitted since I see it happening on Samsung phones too?
I've had many other phones, mostly Samsung and even a Note 4 with Android 5.1.1 but hangouts and emails and every other notification was practically instantaneous whether on Wi-Fi or cell network.
Thoughts?
USA TA-1085 here, had this issue since I've had the phone. I'm on an AT&T post-paid plan and I can't send or receive MMS, whether it's a picture or a group text, while connected to WiFi. If WiFi is switched off or not connected to a network, MMS functions seamlessly. If connected to a network, Android Messages will prompt me to download, and it'll spin for awhile and then time out. I've tried other messaging apps like Textra with no results. My APN settings are the same as my previous phone (Moto G5+)
Nokia Support had me delete a lot of system app data, toggle battery saver, and nothing worked. They only indicated that a solution may be presented through an app or system update, that they report bugs to Google with a request for resolution, that updates "usually come every month" and "most likely within November I should receive it." For what it's worth, that's a similar response I got to issues with Smart Lock, and those issues have since been resolved.
Has anyone else seen a similar issue and fixed it?
I just tried this on my 7.1 and had no issues. I sent an mms from a MintMobile device to my 7.1 on AT&T and it worked with the WiFi connected. I know this doesn't really help but I'm just letting you know as another data point.
I had issues with MMS in general. I removed all the APNs, created a new one with all the proper TMobile info, and installed Textra (which I own). No issues since then.
Oddly, I wasn't aware I may have been having MMS issues but while I was checking the APN for LTE connection I messed something up and lost connection completely and reset my APN's to default. This prompted an MMS message to be immediately delivered upon reconnecting which could have been a coincidence but after seeing this post and testing sending MMS messages to myself and friends, I have no issues now on T-Mobile on Wi-Fi or off.
Saw a thread in the Nokia 7.1 forum that links this behavior to WiFi calling. Is that enabled on your phone?
https://community.phones.nokia.com/support/discussions/topics/7000038488
I've got an Ulefone Armor 9 I recently purchased. As part of setting it up to work as desired, I swapped away from the default messaging app to one that supports dual SIM operation a bit more gracefully.
I've since noticed that after a prolonged idle, such as sleeping, the phone drops all SMS messages. It isn't that they don't send notifications -- they simply don't exist as far as I can tell. I tried a different messenger, and while it displayed the texts received with the other one, the missing messages weren't there either.
This doesn't appear to be an issue between the carrier and phone. Or, rather, if it is it's impacting both carriers at the same time, because sending text messages to both numbers when the problem is present results in neither being delivered. The carriers don't buffer the messages for later delivery as if the phone was offline, and calls come through okay but do not resolve the SMS issue.
I can reboot the phone or manually open the SMS app/bring it to the foreground, after which point I will start receiving messages again. Only ones sent after performing this activity, however. The prior ones are lost.
I've checked to ensure that the app itself is running in the background and Android says that it is. I've not got anything that should be pausing it (that I'm aware of), so I'm not sure why Android would stop sending it messages. I'm also not familiar enough with Android to know how the OS handles texts. Clearly there's some sort of storage & OS management, because the alternate app I tried as part of troubleshooting was able to pull my message history.
Has anyone got any ideas on further troubleshooting steps, or insight into how Android handles texts in general that might help narrow down the point of failure?
GV00 said:
I've got an Ulefone Armor 9 I recently purchased. As part of setting it up to work as desired, I swapped away from the default messaging app to one that supports dual SIM operation a bit more gracefully.
I've since noticed that after a prolonged idle, such as sleeping, the phone drops all SMS messages. It isn't that they don't send notifications -- they simply don't exist as far as I can tell. I tried a different messenger, and while it displayed the texts received with the other one, the missing messages weren't there either.
This doesn't appear to be an issue between the carrier and phone. Or, rather, if it is it's impacting both carriers at the same time, because sending text messages to both numbers when the problem is present results in neither being delivered. The carriers don't buffer the messages for later delivery as if the phone was offline, and calls come through okay but do not resolve the SMS issue.
I can reboot the phone or manually open the SMS app/bring it to the foreground, after which point I will start receiving messages again. Only ones sent after performing this activity, however. The prior ones are lost.
I've checked to ensure that the app itself is running in the background and Android says that it is. I've not got anything that should be pausing it (that I'm aware of), so I'm not sure why Android would stop sending it messages. I'm also not familiar enough with Android to know how the OS handles texts. Clearly there's some sort of storage & OS management, because the alternate app I tried as part of troubleshooting was able to pull my message history.
Has anyone got any ideas on further troubleshooting steps, or insight into how Android handles texts in general that might help narrow down the point of failure?
Click to expand...
Click to collapse
I'm not sure if this would help but try messing w/ "App Blocker's" settings for your SMS app or even disabling App Blocker altogether (in the settings menu under "smart assist" I think).
BigBossPlaya said:
I'm not sure if this would help but try messing w/ "App Blocker's" settings for your SMS app or even disabling App Blocker altogether (in the settings menu under "smart assist" I think).
Click to expand...
Click to collapse
Unfortunately, it was already off, so no dice there. Ulefone pushed an update I thought might have fixed it, but after about 18 hours of idle I sent a test message and it fell into the void. Opened up the messenger app again and sent another and that one arrived without issue, but no sign of the first.