Title says it all: send, but not receive. My carrier is MetroPCS, stock A505G (have skipped all updates since Aug 2019). Haven't had a single prob with this phone until yesterday when I realized I wasn't receiving any texts. Everything else is working fine.
Did all the basics (resetting Network settings to defaults, restarting 10,000 times, blah blah blah). No effect.
Installed several alternate text messaging apps. No effect.
Did the call-in-tech support thing. No effect.
Did the walk-in to the MetroPCS store thing. No effect.
Swapped SIM cards including a new one from the store. No effect.
Changed APN settings to every alternate under the sun that I've seen. No effect.
Absolutely cannot figure it out and neither could the neophytes (I think I got the C-crew today) at the local store.
I've got the North American version (A505G) and have *not* updated the phone since August 2019. I've forsaken all the updates after since I saw some probs with it on the XDA forums and just kept putting it off. Could that help fix it? I'm doubting it, but am open to suggestions and crossing my damn fingers someone somewhere has encountered a similar problem.
Of course I know I can do a factory reset, but why do I have a feeling it won't cure the problem..... Anyone have any ideas, I'd be real grateful.
Related
I really have tried to avoid posting but I'm really not sure what to attempt next. I've been through a few threads on the XDA as well as trawled Google but I've not really come up to much.
Basically my One X has been fine since I got it up until the last couple of weeks, I'm not entirely sure if that coincided with a software update or any other changes I could have made but I never seemed to have a problem initially.
I've been using GO SMS since I got the phone, but having just re-installed the app to no avail and having just tried the exact message within a 60 second window through the standard messager it still did not send. This has happened in alternative locations too, so it doesn't appear to be signal based on where I am. After the 4th attempt and the message would not send I put my phone into Airplane mode to reactivate the sim, after doing so and turning it off the message sent.. So it might even be network related.. I've no idea! I've removed the sim card and left it for a few minutes to see whether when it's reinserted if there is still a problem, failing that though I am out of ideas!
Just for your reference I am with Vodafone, totally stock phone as it comes out of the box running the updated 1.29.401.11 software
Any help greatly appreciated.
Ashalak said:
I really have tried to avoid posting but I'm really not sure what to attempt next. I've been through a few threads on the XDA as well as trawled Google but I've not really come up to much.
Basically my One X has been fine since I got it up until the last couple of weeks, I'm not entirely sure if that coincided with a software update or any other changes I could have made but I never seemed to have a problem initially.
I've been using GO SMS since I got the phone, but having just re-installed the app to no avail and having just tried the exact message within a 60 second window through the standard messager it still did not send. This has happened in alternative locations too, so it doesn't appear to be signal based on where I am. After the 4th attempt and the message would not send I put my phone into Airplane mode to reactivate the sim, after doing so and turning it off the message sent.. So it might even be network related.. I've no idea! I've removed the sim card and left it for a few minutes to see whether when it's reinserted if there is still a problem, failing that though I am out of ideas!
Just for your reference I am with Vodafone, totally stock phone as it comes out of the box running the updated 1.29.401.11 software
Any help greatly appreciated.
Click to expand...
Click to collapse
I have the same problem, AT&T HOX, stock 1.73.502 rom, completely un-modded.
You are not alone my friend.
So I wanted to see if somebody would provide me with the settings they have for the SMSC. Starting this morning I was no longer able to send text messages and I know its not an issue with a ROM or anything because I Odin'd back to factory and I am still having the issue. This isn't the first time I have had an issue with a GNex not being able to text and I had to take my old one back to the store and get a replacement because they were unable to fix. I think I stumbled upon my problem/solution and was hoping that somebody from this great community would help me out. Could somebody do the below and paste what settings they have or give a screenshot. THANKS in advanced.
Open Dialer
Type the following sequence *#*#4636#*#*
Open Phone Information
Well for starters, My first Gnex had this issue a few days after receiving it, approximately one month ago. This morning I noticed I was once again unable to send or receive text messages. Up till now, I have been stock with root. I have been scouring pages and forums trying to find more info on this problem.
Unfortunately the farthest I have gotten is a wiki page on Cyanogenmod that goes through the process of updating your SMSC based on your Carrier's Gateway Number and putting it into PDU format. You can fidn the gage here.
To make it worse, as I thought I was going to be able to manually update it and get SMS back up, i still receive update error.
To make matters worse, for the past four days calls drop out every four to six minutes regardless of coverage. Not just on my line, but my wife's and my sister's lines as well. However they have not been able to reproduce any SMS problem like the one I have once again come across. I'm pretty close to dropping Sprint even if I've got a year left on contract.
Thanks for the reply. When I went to update or refresh the smsc I would get an error as well. This is my second GNex and really frustrated by it. I ended up odin'ing back to factory to and called sprint. they had me re-activate the phone *#*#72786#*#* then a few minutes later it started working again...
Well at least you were able to get yours working again. I've performed several resets via the 72786 menu to no avail. I went to a store today, to see them try it themselves, and eventually reactivate it. After seeing my problem was the same as the last, They decided to order a new/refurb phone. If this doesn't work out I plan on going back to my Evo 4G or just dropping my line on Sprint.
Well last night the modem died completely, this is some bull****. Can't connect to any sprint towers, makes me wish I still had my old phone. With 3 lines I just cant spend that much money to leave sprint.
Sent from my cm_tenderloin using xda app-developers app
I completely understand the cost of leaving sprint. I'm in the same boat with three lines as well. I have read up that in many cases an etf can be waived by returning the phone.
I am currently waiting for a new nexus to get shipped out here. If this third one doesn't hold up I'm going to have some bickering to do with account services. The other two lines are only experiencing dropped calls every few minutes and after talking with several reps, there is ongoing maintenance in my area.
What I want to know is why can't the smsc number be updated. And then why after wiping system and data and then flashing stock, that the smsc still cannot be updated. Something about the smsc cant be updated or there's a read error, corrupted sector, i dunno. I feel like I have exhausted everything I can think and tried everything I can. Not to mention this problem seems relatively isolated.
Sent from my Nexus 7 using Tapatalk 2
Okay, so today I was at work, receiving calls, making calls, sending texts, phone was working fine. I'm on AT&T, using their SIM in the Galaxy Nexus. Suddenly, I have no service. Nothing. So, after several reboots, I finally check the APN. There's nothing there. I attempt to add one, and it promptly disappears.
I went online and found others had a similar experience when they attempted to change their MCC and MNC, but I never had. Just running stock JB with the settings the OS automatically found for my SIM, which has worked for nearly a week.
Thinking my SIM might be to blame, I pulled out my Straight Talk (at&t compatible) SIM that I have on my backup Samsung Captivate. Not only does the Galaxy Nexus not find an APN, any attempt to add an APN fails. I can add one, it'll "save" but it doesn't show up in the list.
Both SIMs work fine in the Captivate.
So I just installed MIUI, in case it was some issue in stock. Same results for both. It seems it's ROM-independent and SIM-independent. Can't make an APN stick.
Any thoughts? Is my phone a lemon? I can't imagine what else to do, since a new ROM and a new SIM doesn't fix it.
Okay, further update:
I dialed the *#*#4636#*#* number to check the phone info, and the IMEI is listed as Unknown.
I'm assuming this is bad? :|
Nevermind, finally found some threads on it. Looks like I'm SOL. /sigh
I have exactly the same problem, anyone has an answer to this problem...
what tread did you found...did you fix your problem?
Hello, I'm desperately seeking help to remedy this issue I'm having. I have unlocked Note 10+ on T-Mobile Network and ever since I got the device I been getting this "Network Error" pop up message dead on center of the screen.
It happens very randomly regardless of which app I'm using, on both wifi and mobile data. The error message pops up very briefly and disappears. Luckily it hasn't stopped me from doing daily tasks but it's extremely annoying.
These are things that I have already tried;
Factory reset, Network reset, brand new simcard, clear cache, returned the device for brand new replacement, uninstalled all 3rd party apps.
Nothing seems to help, I still get error message intermittently...
I'm out of ideas and clueless on how to go about it.
Anyone else on unlocked Note 10+ with T-Mobile experiencing same issue?
as you have tried everything else, maybe try with tm firmware or maybe contact tm tech support in case they can push some config settings
raul6 said:
as you have tried everything else, maybe try with tm firmware or maybe contact tm tech support in case they can push some config settings
Click to expand...
Click to collapse
Thanks for your input. When I contacted tm, they told me since it's unlocked they can't do much about it....
If I flash to tm firmware would it cause an issue when I return the device to Samsung for Samsung upgrade?
zen0s said:
When I contacted tm, they told me since it's unlocked they can't do much about it....
Click to expand...
Click to collapse
That wasn't nice on part of tm, I also have U1 N10+ and I've never had problems switching sims for different networks. Have you tried using other provider's sim? Some tm secondary mvnos, I know to work well on my phone, will send you a free 1 month sim to try. I'm not going to spell its name(to avoid xda-free advertisement) but I'm very happy with its services(and super low prices)
What apps are you using? And have you disabled anything? You say you factory reset it, but did you start to install something again? And it happening with a 2nd device is odd
Asking this for a friend who has an S9. I have an S10, so I have some familiarity, but we're still fighting with the problem. Here's the story:
He was on TMobile. I suggested he try changing to Total Wireless (Verizon MVNO) as I have had good luck with them. He switched and things were working fine for a few weeks.
Nothing on the phone was changed, but then about 2 weeks ago, his text messages weren't going through, particularly to iPhone users. Normally, we'd think this is a problem on the iPhone side, but nothing changed there either (his wife's iPhone)... in addition, this happened with multiple iPhone users, so it's not just one person...
We've done a ton of digging, contacted the carrier, they contacted VZ for help, tried different apps (stock, Google Messages, etc)... no one has been able to figure out the solution. The most recent finding was that the stock Samsung messaging app works fine for all users, but GMessages continues to have problems. With regard to GMessages, we have checked and confirm that iPhone users are getting detected at "SMS/MMS" and not RCS, so that doesn't appear to be the issue either.
APN settings match what I have (I have no problems with my S10 with any users - iPhone or otherwise).
Only remaining thing I can see is that his phone is seeing a CSC of TMB/XAA/SPR (mine is TFN/TFN/SPR). I think it could be due to the TMB/XAA he's seeing, but the carrier thinks this is not the issue. His ROM is showing up as SM-G960U_OYN_TMB.... I wonder if it's because it's U (instead of U1) so it's unable to switch to TFN?
Anyone else have any ideas on what could be going on here? Since the stock app works, it seems it's not a carrier issue... but I still don't get why that would fail to work on GMessages when it works fine on the stock messaging app?
Any ideas appreciated. We're quite technical and able to do all sorts of things (ODIN flashing, etc)... so nothing is off the table. Just trying to figure out how to fix this.
Bump - no one has any ideas or theories? I'm in brainstorming mode, so no idea is not worth trying!