Jump to content

EVO LTE text messaging problems


Mondays In Flames

Recommended Posts

Today I woke up to my phone not being able to send or receive text messages... I can call and I can use data. But no text messages at all! Nothing I have tried sending some, and I haven't been receiving any of the texts people have said they sent me

 

 

I called sprint and they reset the phone with the network, did a whole hands-free activation and nothing. I'm sitting here an hour later trying to figure this out...

 

Can you guys suggest anything?

 

As far as Sprint is concerned the towers in my area are all fine and there are no active tickets for any troubles around the area. I live in Miami, FL 33172

 

 

-Luis

Link to comment
Share on other sites

Couple questions from a troubleshooting perspective that you may have already answered with Sprint.

  1. Are you using the stock messaging app? If not, can you replicate the issue on both your app and the stock app?
  2. Are you having the same problem over both wifi and mobile data?

Link to comment
Share on other sites

Couple questions from a troubleshooting perspective that you may have already answered with Sprint.

  1. Are you using the stock messaging app? If not, can you replicate the issue on both your app and the stock app?
  2. Are you having the same problem over both wifi and mobile data?

 

I am using the stock app. I don't use any other one and the problems persists regardless of mobile or WiFi network.

Link to comment
Share on other sites

If you can call then Texting would work. Now that doesn't mean something else up the chain isn't working. The wife has had issues today of delayed texts sending and receiving even though it shows as sent. Then sometimes she gets duplicates many times over of what people sent. I haven't had the issue so it's not tower related.

 

Sent from my C64 w/Epyx FastLoad cartridge

Link to comment
Share on other sites

  • 1 month later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • https://www.fiercewireless.com/wireless/t-mobile-gets-little-closer-accessing-its-25-ghz-spectrum-auction-108 Senator Kennedy's bill to grant the FCC temporary auction authority to finish processing the Auction 108 licenses it has sold to their proper licensees. This would greatly benefit T-Mobile.  This delayed process took what would have been a strategic advantage for T-Mobile (1 one year plus head start)  and turned into catch-up, since AT&T and Verizon haven been busy installing their c-band n77 in rural areas.
    • I configured -44/-3 scenarios on an Edge 2022 to be an invalid connection, so yes, it would show no service.. I didn't realize it was a frequent issue though. How certain are you about the other values? Perhaps they are just unchanged from the previous array of signal information that was reported? If that is the case, I can try to have the app discard -44/-3 datapoints and leave the screen unchanged. I worry about the slippery slope of having it display as -140, because that leads users to believe there is a -140 signal present, when in reality we don't know what the actual reading is.   Haha me and you both wish this!!!
    • Following up, I've gone into the office in person today and took my Edge with me. It looks like it now shows "No service" instead of the -44/-3 value.  I saw a lot of "no service" because it apparently does it a lot.  I'll check again on the train ride home later. Assuming I'm correct, is it possible to have some kind of middle ground on this?  I think it was showing other legitimate values, like the TA, even when it was showing -44/-3.  I'd prefer it show the data it has but at -140 dBm in those cases.  I recognize this could be a pain to implement, and if it is, then no worries, mostly curious. EDIT:  But now I'm sitting here thinking "what if the PCI is bad and I don't know it?"  But that can just as easily be the case on other phones that aren't caught.  I do regularly see bad PCI entries on my other devices, so maybe this isn't the best option.  Bleh, I wish this stuff just worked properly! - Trip
    • Forgot to follow up on this. The service was once again abysmal .
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...