Issue during high traffic - Nexus S General

So today I had a weird issue with my phone. I was not able to make calls or receive calls. When I was dialing a number I was getting the "Dialing" screen and nothing. The call would hang up automatically. I thought this was a Google Voice integration issue with Sprint so I disabled it. Still same issue, so I enabled adb and started checking the logcat. Nothing particularly suspicious in the log either. The whole issue started happening RIGHT AFTER a major shootout across the street between cops and some armed bank robbers. I was not able to place calls for more than 4 hours (1 out of 20 calls would work...)...and now finally all my calls are going through. I called Sprint and the CSR had no idea, he updated my Profile remotely (noticed my phone went to Profile update by itself). Anyways, I believe this is Sprint towers near my area getting JAMMED with calls about the whole shootout. 3G data was still working though. This is INSANE because what would have happened if I needed to call 911? i was not able to even send regular SMS...

It happens. Same reason phones are tied up after a major disaster. Networks are typically built to a capacity which accounts for the heaviest usage under normal conditions. Paying for excess capacity only needed a small fraction of a percentage of the time isn't cost effective. Of course, that's rarely consolation when you can't place a call in an emergency, but the economics make sense.

Related

Ring Delays Problem?

So i have had my hero for a couple of months now, and ive been noticing i get voicemail notifications without my phone ever even ringing, i was hoping u guys could help me out and to see if you guys have the same problem
so i had my friend sitting right next to me and he called me, it took like 8+ rings on his side before my phone actually began ringing on my side and then after 2 rings that i heard on my side the phone went straight to voicemail.
but it didnt happen all the time, sometimes my phone rang right after we heard 2 rings on his side, which i think is normal
now i use google voice, i was wondering if you guys experience this as well? and if so do u use google voice or normal voicemail.
also i think its worth to mention i changed my phones meid to match my old lg rumor. so it is a cloned phone, but the original donor phone is always off with the battery out.
this problem sucks cuz people call me and in essence i dont pick up their calls because my phone sometimes doesnt ring n people think i ignore them...
I haven't ever had that problem (and I also use GV). But you can change your slot cycle to tell it to poll the tower more often which might help you. Now there is going to be an extra delay because of GV, but it shouldn't take 8 rings. If this doesn't work then there might be something causing a slow down on your phone which is why it takes a while to realize it's ringing, or it might be the MEID swap causing strange things.
##3282# Set slot cycle index to 1. Your phone will poll towers more often and will respond to incoming texts and calls faster.
http://forum.ppcgeeks.com/showthread.php?p=1391130
this was set to 2 so hopefully this works, what about 0?
0 might drain your batt faster then normal
So I went to "##3282#" to make a change and it wouldnt let edit anything because it asks for password, anybody know what could be the password?
The password is actually your phones individual MSL#. It can be obtained by calling Sprints tech support. They might refuse to give it to you, but just tell them what you want it for and they probably will.
had my MSL thankfully since i make notes for all my sprint calls.
thanks for this tip - hope it helps me out too!
I just did this, lets see what happens.
Any updates on this? I am set to 0 for slot cylcle but consistently get more than 2 rings before my phone rings.
Please correct me if I'm wrong, but I think slot 0 is reserved for police and other first responders. You're not supposed to use it without permission.
I believe I read somewhere that changing the slot cycle index on the phone itself will not actually change anything, except that it may drain your battery faster. As I understand it, the tower's setting for that attribute will override end-user devices' settings.
FWIW, I changed it on my Hero, and it made exactly zero difference in the ring delay (timed in seconds). If you watch a timestamped kernel debug log when a call comes in, you can see that it simply takes the phone a long time to get its sh*t together and start ringing. This is common across HTC phones. Piss-poor design for a phone if you ask me.
My phone takes 2-3 rings on the callers end before my phone rings, this would be fine if it didn't go to voice mail after 6 rings. Is there any way to change how many times the phone rings before it goes to VM?
Nanan00 said:
My phone takes 2-3 rings on the callers end before my phone rings, this would be fine if it didn't go to voice mail after 6 rings. Is there any way to change how many times the phone rings before it goes to VM?
Click to expand...
Click to collapse
According to Sprint's latest answer, "no". With past phones, Sprint HAS changed that parameter for me. My previous phone would ring for more than 60 seconds before going to voicemail. Sprint now tells me that is not possible, nor was it ever possible. Obviously, it *was* possible. I didn't just imagine that it would ring for a full minutes.
The ring configuration is actually managed by number of seconds before voicemail, as the number of rings depends completely on what ringtone you use. I forget exactly what number they have it configured for currently (I know its less than 30s), although I do remember that the Hero itself only rings for exactly half of the Sprint-specific time. Sprint did acknowledge that that Hero (and other smartphones) have a problem with the ring time, but they offered no suggestions to fix it.
I was going to use this method to try to reduce my ring delay. When I put in ##DATA# nothing happens on my phone. I know the debug codes work because I can put in *#*#4636#*#* and it brings up a screen. Any ideas why this code doesn't work?
kynetx said:
Please correct me if I'm wrong, but I think slot 0 is reserved for police and other first responders. You're not supposed to use it without permission.
Click to expand...
Click to collapse
Negative, that is the Access Overload Class.
I have my slot index set to 0 and my ACCOLC set to 2. I make it a full day without charging for whatever it is worth.
Trevor said:
SCI - Slot Cycle Index - This determines how often a handset polls thenetwork for coverage and incoming packets. The default value is 2. A"Slot" is 1.28 seconds and doubles with each incremental change from 0to 7 (0=1.28, 1=2.56, 2=5.12 seconds, etc). setting a handset to pollmore often may use noticibly more battery if coverage is thin orlacking.
ACCOLC - Access Overload Class - This code determines your priority tomake and receive calls on the network. Higher the number, lower thepriority. Lower the number, higher the priority. Emergency Servicesreserves 0 + 1 (please do not use these) leaving your choices to 2-9.Years ago we began defaulting this code to the last digit of a usersMIN to help assure equal priority seeding.
Click to expand...
Click to collapse
I found this thread on the EVO forum and decided WTH I'll try it. Worst that can happen is I have to go back to the stock prl cause it doesn't work. However when I tried it, I have significantly less ring delay "lag" and not one call has gone directly to VM. Hope it helps everyone that is having this problem. Please report back with results.
BTW I had no hand in figuring this out I am just passing on my findings. all credit goes to techknowfile.
http://forum.xda-developers.com/showthread.php?t=696073
animal7296 said:
I found this thread on the EVO forum and decided WTH I'll try it. Worst that can happen is I have to go back to the stock prl cause it doesn't work. However when I tried it, I have significantly less ring delay "lag" and not one call has gone directly to VM. Hope it helps everyone that is having this problem. Please report back with results.
BTW I had no hand in figuring this out I am just passing on my findings. all credit goes to techknowfile.
http://forum.xda-developers.com/showthread.php?t=696073
Click to expand...
Click to collapse
I tried this just for the heck of it and not 10 minutes after I rebooted I kept getting "Error 67 Data Call Failure your Sprint PCS Vision user name or password is wrong"
Maybe I did something wrong, but as soon as I put 60065 back on my phone it went away.
For reference I am in Knoxville, TN
Kcarpenter said:
I tried this just for the heck of it and not 10 minutes after I rebooted I kept getting "Error 67 Data Call Failure your Sprint PCS Vision user name or password is wrong"
Maybe I did something wrong, but as soon as I put 60065 back on my phone it went away.
For reference I am in Knoxville, TN
Click to expand...
Click to collapse
I am not getting this error. So maybe this will not fix everyone but it sure has helped me a lot.
Thanks for the reply. Kcarpenter
animal7296 said:
I am not getting this error. So maybe this will not fix everyone but it sure has helped me a lot.
Thanks for the reply. Kcarpenter
Click to expand...
Click to collapse
Luckily the area I live in has excellent sprint coverage (better than big red) Just wish we had 4g...one day...
This problem is the main reason why I will be abandoning my hero soon. I have tried at least a dozen different roms and have yet to find one where the phone function ACTUALLY WORKS............ WTF?? My phone usually rings for 2-7 seconds before going to voicemail in a good coverage area, and normally not at all when I'm at my house (poor coverage). I'm currently using the latest Fresh ROM (2.1.2), have done the slot-cycle mod, and have flashed the overclocked kernel, all to no avail. It may be a fine data device, but is a pretty damn pathetic phone.
Heck, I've even cleared my call history (which at 3 weeks old was long enough to lag the dialer for 4-5 seconds every time it was pulled up), and that hasn't helped. It also doesn't help that the phone app crashes on about 1/3 incoming calls.

Calls go straight to voicemail despite having good reception on handset

I seem to be experiencing issues that sometimes people call me and the call goes direct to voicemail without even ringing. I get no missed call alert and dont know that someone has called unless they leave a message. I have tested this by calling my handset from my office phone with the HD2 in my other hand showing full network coverage... call goes direct to voicemail. 5 mintues later all worked fine. This seems to be totally random however it seems to be getting worse to the extent that no-one could call me all afternoon today. I know that i missed at least 7 calls and possibly more. All the settings are correct for call diverts etc.
Also the new 1.66 Rom seems to have made my phone worse but most people seem to be saying that theres is quicker.
Other details?
Who's your carrier, were the calls from within your carrier's network or outside, etc.?
Carrier is o2 uk
CARRIER IS O2 UK. THE CALLS THAT GET DIVERTED STRAIGHT TO VOICEMAIL ARE RANDOM.some within the network others are not. it seems to have no relevance. o2 advise me to test using another phone to see if the sim card is faulty. does anyone else have this issue?
I noticed it this morning at a real bad time. Was waiting for an important call back for an IT problem, and thankfully he left voice mail with a call back.
While the HD2 does many non-phone things, foremost it needs to work perfectly as a phone!
(i'm on t-mobile usa)
Working fine for a few days, but who knows how often it happened & the person didn't leave voice mail!
Me too!
yep! I have had this for the first two months of getting the phone except mine says "do you want to send a text" instead of going to voicemail..... I "discussed" with T Mobile UK several times and they eventually did a full account refresh which seemed to solve "most" of it. I don't get people telling me they called me and couldn't get through any more although I have dialled my HD2 from my landline and it's still random. T Mobile gave me money back on line rental though..... that's something I suppose.
Hopefully some of us can find a solution.... or am I right in thinking we should be able to send it back!?

receiving text late

lately i been noticing that my texts have been coming 10 mins late or more after the person sent them,i think this has to do with the data connection cutting off on its own problem i been having because as soon as the person calls me i would get the text at the same time that they're calling me. has anyone else had this problem and if so how did you fix it.
texts dont use data connection.
Late txt behavour is usually caused by the network, not the phone. The SMS service was never intended to be an instant service, we have just gotten used to them being delivered almost instantly.
If you have another phone that your sim works in, id do some testing and compare the two.
i hag the g1 and my sim was in that phone last week and the texts was coming in on time and now they come in late,maybe it's this phones radio.
heh, yea, could be, but that was last week, too. on thursday my broadband was fine but all weekend its been half speed,,,,
all i'm saying is you need two phones right there and compare, just to be sure.
first step in trouble shooting is proving the fault.

Weird incoming call/voicemail error

We have 8 lines on our business account from Sprint. Here is what is happening:
When Line 1 calls Line 2, the call goes through, the phone rings, and everything works like normal. When we switch it around and Line 2 calls Line 1, the phone on Line 1 never rings. Line 2 gets Line 1's voicemail. This has been going on since March. It never changes. Line 1 will never ring when Line 2 is calling it. All other phones can call Line 1 and it rings perfectly and acts like normal.
Line 1 and Line 2 are both HTC EVO's with Cyanogenmod 7 on them. They were working perfectly for two months, and then it changed. When the problem first started happening, sometimes instead of getting voicemail when calling Line 1, I would sometimes get a message that said: "This is channel 47 4".
Around the same time when this started happening, it also started with another phone on our plan. Line 3 on our plan cannot receive phone calls from one certain Verizon cell phone number. The Verizon phone is a Samsung Fascinate that is rooted. Line 3 on our plan is a Sprint HTC Hero running Cyanogenmod 7. The same thing happened here. At first the Verizon Phone calling in would here a message that said "This is channel 47 4", but now all they get is voicemail immediately.
All of the phones use Google Voice voicemail, but I tried disabling it and then they just got the Sprint voicemail immediately.
I called sprint about it but they said they need to troubleshoot it in a repair store. We do not have corporate stores in our area, and I don't trust the repair stores that are here. Last time my old Touch Pro was in to them, it came back severely damaged. Also, I don't want to risk losing the root on my phones and having them upgraded to Gingerbread which hasn't been rooted yet.
Has anyone ever heard of an issue like this, or does anyone have any idea what I should do?
Thank YOU!
I did check and make sure that in the contacts the phone was not set to forward the call to voicemail immediately.
I am on AT&T with an HTC Tilt/Kaiser and have the same issue with my step-father who has an EVO. And yet my Mother, who is on the second line on that account with another EVO, can receive them from me. Not just you. Except none of the phones have mods and we don't get the "47 4" thing.
If anyone ever has this problem, the solution for me was to completely wipe the phone, install a cm7 again, and NOT restore any backed up applications.
Sent from my PG86100 using Tapatalk
UPDATED INFORMATION:
I misposted. My problem has not been fixed. All that was solved was that I can now log into my ATT voicemail myself from my own phone - prior to that, by pressing "1" to access my voicemail, I got the message: "This is channel 47-4"
Now though my voicemail seems OK on my end, people calling in still receive the message "This is channel 47-4"
I am in Los Angeles but I have found a newspaper article about a whole community in Norfolk, VA whose phones are supplied by a Time Warner subcontractor, Intrado Communications in Longmont, Colo and the panic it has caused that they were unable to reach Emergency Services on their phones.
(I have not posted enough to post a link. I cannot seem to post even the unlinked URL but here is the article title and newspaper - it was printed in several local newspapers, it's easy to find.)
Phone Service Trouble Remains
Watertown Daily Times
A quote from the article:
"Most of the time, the phone rings busy," Mrs. Michaud said. "Sometimes, it says this is channel 47-4."
Still nowhere can I find anyone who knows what is going on. And back in January, apparently even Time Warner had no idea, they fixed the cable but not the phones.
A NEW TEST: I have just deactivated Google Voice again and tested - my ATT voicemail IS reachable. My problem is gone. Unless I want to forward to Google Voice. I have searched Google and Google Voice Help up and down and have not found a reference to "channel 47-4"
But at this point - in my situation anyway - Google Voice is the culprit. Or possibly the target.
ORIGINAL POST:
I just finished spending 2 hours with ATT in 2 different tech support attempts for this same 47-4 message problem - only mine was slightly different. I fixed the problem but I can't let it go. I am curious how the same recording could be reached across different carriers, ATT and Sprint.
Blow by Blow to maybe help someone figure it out:
I have an unmodded Galaxy S2 SGH-i777
I have been using Google Voice for this and my previous 2 phones all with the same ATT Wireless account.
Today, when people called my number they got the same weird message as everyone - weird for the message and loud background noise.
"This is channel 47-4"
I called my phone from a landline and got the message.
Clicking the hook switch makes the message repeat without hanging up.
(I tried it 4 times)
Google Voice should have intercepted an unanswered call, right?
The first tech support advice:
Reboot the phone, they would send a voicemail reset signal and then I should reset my password.
(I took it upon myself to deactivate the Google Voice account first.)
When I pressed the "1" key to access ATT Voicemail and set the password, I got "Unable to perform this action contact customer service."
I then tried to access my voicemail account online and got ERROR E1018
I called tech support again and they weren't interested in the error code.
They called me back on my landline and asked me to reset my password using "1"
I held the phone up for her to hear. This time when I pressed "1" I immediately got the recording "THIS IS CHANNEL 47-4"
What I found fun is that the message freaked out the tech support. She had never heard anything like it, she said.
Here is the new oddity:
When she came back on the line she was more freaked out! There was no record of any voicemail on my line. Voicemail isn't an "option," she said, it comes with every account. She knew of no type of account without voicemail. Having no voicemail account on my number was impossible, she said.
Regardless, I popped out the battery and restarted while she sent a "reset" signal and everything is now back to normal. I enabled Google Voice and all is as it was before today.
I've searched online and there is a lot of recent 47-4 issues and a lot of good solutions only no one seems to know what the message is or how it got there. I have the added piece of information that somehow my ATT record of any voicemail account was wiped out in the system.
The same message across carriers means what? That it's in the shared data lines? Shared towers?
If someone knows what this message is and who it originates from, I'd like to know. If I find out, I'll come back here and leave an update.

[Q] Nexus 4 repeated signal loss and calls not coming through

I've got some serious issues with my Nexus 4, I've found posts with similar problems but not exactly what I have. I'm at a loss what to do next so any advice would be much appreciated.
I bought a N4 around March this year, direct from Google, and connected it to TPG Mobile here in Australia which uses the Optus network.
It was fine until about the end of May or beginning of June where it started losing signal regularly. First thing I noticed is it would start dropping calls and displaying "No network available", the triangular status bar at the top would go blank (completely black, not grey) for about 30 seconds, then it would return to normal signal and I could make calls again. However it would do this every few minutes, whether I was on a call or not, and each time it would last roughly 30 seconds and then return to normal.
Around the same time I started to receive SMS on either a delay, or they'd arrive on-time, but then keep sending multiple times for about the next hour.
I rang Google, they got me to go through recovery mode, then it worked fine, for about 24 hours, before it started again. They sent me a new device, which did the same thing within hours of activation, so I requested a 3rd device. At the same time I thought it might be the sim card, so I got a new one of those too.
My 3rd device and new sim card worked perfectly for about 3 days then the same problem started. Factory resets etc seem to fix the problem for either minutes or hours, but never permanently.
Then last week I noticed further weird symptoms, I started getting the usual sms to say someone had called and left a voicemail, however my phone never showed any sign of a call (visual, audio or missed call in the call log). I confirmed with several people who tried calling me and they confirmed the phone rang on their end before going to VM. I tried it myself from a landline and it randomly rings or doesn't ring on my end, however I also noticed when I hung up on the landline without answering my Nexus 4, it continued to ring indefinitely, ie. it hadn't registered the caller hung up.
My provider assures me there isn't an issue in my area, my wife uses the same provider (with an iphone) and has not had these issues. I can't swap sim cards with her though as she has a full-size sim. I tried another sim with my phone for a few hours and it worked fine, however my phone with my sim will sometimes go a whole day without issues so it wasn't long enough to truly test it.
I've deleted all apps that might somehow affect it and the hasn't helped either.
Basically I'd like to know is this likely to be a phone issue, and I pursue the issue with Google, or some sort of network/sim issue and I pursue it with my provider?

Categories

Resources