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
I seem to have encountered this bug: https://code.google.com/p/android/issues/detail?id=79580
551ML, currently running 2.20.40.59. My carrier is Vodafone NL. SMS sends fine when the SIM card is installed in my HTC One M7 running 5.1, or an old Nokia dumbphone I had lying around.
I've attempted to remedy the issue by the means described in various articles online, to no avail. I am able to SMS to people in the Netherlands if I strip the country code out of their phone book entry first. I am also able to SMS to people in the USA with the country code left in. All of my friends in Ireland, however, are feeling terribly ignored since I have to use the IE country code when texting them, and those messages are never delivered. I've just wiped and done a fresh install of the latest ROM, but the issue persists.
Any other Dutchies (or anyone else) here able to corroborate my trouble?
update:
Apparently this issue was supposed to have been resolved in December 2014:
http://www.androidplanet.nl/nieuws/nexus-5-vodafone-bug/
http://tweakers.net/nieuws/99715/vo...-5-en-android-lollipop-kunnen-niet-smsen.html
Is it possible that ASUS's codebase is so outdated that we're still contending with bugs that were fixed 9 months ago?
Hi guys,
I am experiencing a bug on my Swift where the phone reboots itself during almost all calls after a minute or so. When the phone comes back on, there is no record of the call in the call log! The phone does not reboot during any other activities. Phone details below:
Wileyfox Swift
Cyanogen OS 12.1.1-YOG7DAS2FI
Kernel version 3.10.49
Build Number LMY48Y
I have checked for another similar thread without any luck. Thanks!
I have a similar,though not identical issue. Phone keeps rebooting,seemingly at random,every other day or so. During a call, listening to spotify,idle on the desk...i have an untampered with original Os on the phone.
Cheers,
Me too.
Hi, I just registered to say I'm having the same problem. If you check the Amazon UK reviews too there are several people with this rebooting problem.
So far I have:
- uninstalled all additional apps I installed
- tried it with wifi and data off
- tried the other SIM slot
- done a factory reset
and it still reboots during calls. After the factory reset things appeared to work better in general (alarms now worked properly, and there were more options available, eg in the power button menu), but it rebooted 5 seconds into a phone call, which is a record. It's usually a few minutes into it.
The factory reset didn't actually delete my data (photos, files, etc), so I am going to do a reinstall via Fastboot now; firstly because I'll have to do that I guess if I want to send it back, and secondly to see if it finally fixes it.
I personally think the update process has screwed something up. It did an update as soon as it was powered on for the first time (it to 12.1), then a couple of weeks ago did another update to 12.1.1. It was rebooting before 12.1.1, so it is either 12.1 or earlier where the problem exists.
If it still reboots after a Fastboot reinstall then it's getting send back, and I probably won't ask for another. It's a nice phone, and a nice idea but I can't have a phone that reboots during >50% of calls. That's useless.
Pretty sure you can discount the update process too! I have also had this issue on cyanogenmod nightlies, I honestly thought I had inadvertently pushed the power button..but, NO
*edit* CM13 nightlies
That's strange as I have had no such problem with mine (bought in October) and mine is rooted with the unofficial builds of CM13... Maybe it is a manufacturing error and only on some devices...
Have you tried contacting Wileyfox?
I have not experienced this yet on the Swift when making or taking calls on it.
i'm on the latest cm13 nightly for crackling. each and every time the phone is called, whichever sim, the phone reboots. what a waste...
I have the same issue of spontaneous reboots, mostly during calls but also at other times. Spoke to Wileyfox who weren't very helpful. Has anyone found a solution for this?
Hi, I'm having the very same issue (appears a few are on other forums). Has anyone found a solution? I'm about to factory reset if it continues
Update
Hi guys, so i returned my phone for repair, and they gave me a new phone. Must have been a hardware fault I assume
enzoparker said:
Hi guys, so i returned my phone for repair, and they gave me a new phone. Must have been a hardware fault I assume
Click to expand...
Click to collapse
Hi thanks for the update, I've just factory reset, if problem persists I'll try to get a replacement too! Was it quite a quick replacement process?
R
I'm in South Africa and have the same problem. Whenever sound is involved, I get random reboots. Calls, and music/audio books.
Not with videos though.
It doesn't reset any other time except when I've been listening to music, or on a call.
Been doing this from the beginning.
I thought it was Google Play Music, so downloaded different player.. That made it much less frequent, but then it started affecting my calls as well.
Not happy.
Hi, UK user here. I got this phone less than a week ago and have already had this issue a few times. Two spontaneous reboots on resuming from sleep, being connected to a large WiFi network was the only change from normal use here; then twice regarding calls, once when answering then immediately after reboot it rebooted again while the missed call notification was present, although still on the aforementioned large WiFi network. Unmodified, unrooted, Cyanogen OS 6.0.1 with two sims in use.
Same issue on my a1g2.
It reboots on wf swift Roms. It stucks in call screen on a1g2 stock rom. Strange...
i am having same issue, i make any call and mobile Soft Reboots itself.
So, much annoying cannot make a single call on this WileyFox Swift mobile phone.
Making calls is the main basic purpose of every mobile, but this phone just does not let me make a single call.
.Had this issue on Cyanogen OS 5.1. Now updated to Cynogen OS 6.0.1 having same issue. I have done phone setting HARD RESET and Clean Wipe 2-3 times. Still no solution.
DevilMind007 said:
i am having same issue, i make any call and mobile Soft Reboots itself.
So, much annoying cannot make a single call on this WileyFox Swift mobile phone.
Making calls is the main basic purpose of every mobile, but this phone just does not let me make a single call.
.Had this issue on Cyanogen OS 5.1. Now updated to Cynogen OS 6.0.1 having same issue. I have done phone setting HARD RESET and Clean Wipe 2-3 times. Still no solution.
Click to expand...
Click to collapse
Maybe it's the Dialer in Cyanogen OS, i installed the Google Dialer and made it default Dialer on my Swift, i don't have any problems with reboots during calls and i make long phonecalls. You don't need root access for this.
Although Wileyfox accept that there is a grounds for returns, I believe it is a software bug in Cyanogen OS 13. This fits in with using another dialler. You could also downgrade, or switch to Cyanogenmod.
Also, I only have found the issue when receiving calls, rather than making them, although I don't use a lot of minutes.
Sent bug reports to Wileyfox.. They're saying that what they see is a battery-pull reboot..
I tell them it's happening while I'm using the phone (music or calls)..
They say they can't see what the issue is.
Cos I'm in South Africa, sending the phone overseas is pointless.
Can anyone confirm that the Google dialer does cure a phone that does the reboots during calls ?
Just got a replacement swift from Amazon after Wilyefox service department had my phone since 16th of June. Amazon argued my case and in the end just sent one to me. !
Set phone up on wifi for my wife to use then put in the Voda UK sim, checked the APN setting were OK then tried making a few calls between our phones. first reboot was after 20 seconds or so and then after various tests it rebooted 4 or 5 times at which point I gave up for the night..
Any help appreciated or do I just give up now and throw in the towel, bought original swift in late May and never managed to make it work properly !!
Thanks
phil-w said:
Can anyone confirm that the Google dialer does cure a phone that does the reboots during calls ?
Just got a replacement swift from Amazon after Wilyefox service department had my phone since 16th of June. Amazon argued my case and in the end just sent one to me. !
Set phone up on wifi for my wife to use then put in the Voda UK sim, checked the APN setting were OK then tried making a few calls between our phones. first reboot was after 20 seconds or so and then after various tests it rebooted 4 or 5 times at which point I gave up for the night..
Any help appreciated or do I just give up now and throw in the towel, bought original swift in late May and never managed to make it work properly !!
Thanks
Click to expand...
Click to collapse
Well I've given up !!!
A second Swift was supplied with the help of a Amazon Rep.
We even got a £25 Amazon gift card from Wileyfox direct for all the trouble !
Set phone up on wifi, added all apps required by my wife. Put Vodafone SIM in and ...... Shutting down message.
Restarted phone and it did it a few more times. Ordered a replacement 4G SIM in case there was a problem with the 3G SIM we had. Activated new SIM and fitted it, worked for ten minutes then rebooted itself.
SIM is fine in any other phones I've tried.
Just about to return phone to Amazon, checked and my original swift is still sat with the engineer (since 16th June !!) according to the repair company website.
I feel sorry for anyone wanting their phones repairing after what I've been through.
---------- Post added at 07:07 PM ---------- Previous post was at 07:05 PM ----------
phil-w said:
Can anyone confirm that the Google dialer does cure a phone that does the reboots during calls ?
Just got a replacement swift from Amazon after Wilyefox service department had my phone since 16th of June. Amazon argued my case and in the end just sent one to me. !
Set phone up on wifi for my wife to use then put in the Voda UK sim, checked the APN setting were OK then tried making a few calls between our phones. first reboot was after 20 seconds or so and then after various tests it rebooted 4 or 5 times at which point I gave up for the night..
Any help appreciated or do I just give up now and throw in the towel, bought original swift in late May and never managed to make it work properly !!
Thanks
Click to expand...
Click to collapse
Well I've given up !!!
A second Swift was supplied with the help of a Amazon Rep.
We even got a £25 Amazon gift card from Wileyfox direct for all the trouble !
Set phone up on wifi, added all apps required by my wife. Put Vodafone SIM in and ...... Shutting down message.
Restarted phone and it did it a few more times. Ordered a replacement 4G SIM in case there was a problem with the 3G SIM we had. Activated new SIM and fitted it, worked for ten minutes then rebooted itself.
SIM is fine in any other phones I've tried.
Just about to return phone to Amazon, checked and my original swift is still sat with the engineer (since 16th June !!) according to the repair company website.
I feel sorry for anyone wanting their phones repairing after what I've been through.
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.
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!