Over the weekend I had to dial 911 from my house. I got a message saying "All circuits are busy, please try again later." My phone went into emergency mode, as indicated by an icon in the notification bar and a timer on the screen. I tried calling twice, a few minutes apart. I ended up sending someone across the street to call.
I called Verizon today to ask about the situation and disclosed that I'm rooted and running a custom ROM (currently Nonsensikal 16.1). The guy told me that it's common for custom software to mess up some types of calls including 911 and 411. I have no trouble calling 411.
So, my question: Is this true? Can a custom ROM really prevent you from calling 911? Was it just coincidence that I couldn't connect? Is there some other problem? How might I test a possible fix?
To my knowledge out can be somewhat true but unlikely since your phone connected and the message "all circuits busy" is something that happens on emergency service lines. It happens when a high volume of calls are coming in to 911. Verizon people are not associated with custom roms and usually don't know much on the subject
Sent from my FroyoEris using XDA App
So today I just called 911. Went through just fine. They told me the "all circuits are busy" msg was not from them. Im thinking that was Verizon's lines being busy and had nothing to do with custom software.
Sent from my nonsensikal froyo using XDA App
i have read somewhere that someone who had a rooted eris and a custom rom had to call 911. when they tried to dial it something happened with the rom that 911 didnt work or wouldnt complete. so it has happened before
Not saying it wouldn't happen on a custom rom but the reports are few and far between
Sent from my FroyoEris using XDA App
It'll receive/send texts perfectly fine (well, it'll give me an error but it still sends it).
It happens so often, it starts to get frustrating.
Does this happen to anyone, if it does, any help?
(If it helps, I'm running BAMF Sense 3.0 RC3).
I can't use the phone function most of the time. When this happens, I usually have to do a battery pull, or a soft reset. Usually when I do a data wipe, it fixes the problem.
But how can I stop this problem from happening and make my phone reliable again?
You never explained exactly what it is that's happening that is making your phone unusable. How does it not send/receive calls?
sorry for the clarity.
but basically when I receive calls, they go straight to voicemail.
when dialing an outgoing call, it won't ring and the phone will say "call was lost", even when I have full service.
ss0mohit said:
sorry for the clarity.
but basically when I receive calls, they go straight to voicemail.
when dialing an outgoing call, it won't ring and the phone will say "call was lost", even when I have full service.
Click to expand...
Click to collapse
Have you try on stock rom and does data work ?
Sent from my ADR6400L using Tapatalk
I just wiped everything clean. Data works fine and I'm able to send texts (but I receive a warning) and receive them too. Phone calls don't work. Do you think its a problem with the phone itself?
Sent from my ADR6400L using XDA App
ss0mohit said:
I just wiped everything clean. Data works fine and I'm able to send texts (but I receive a warning) and receive them too. Phone calls don't work. Do you think its a problem with the phone itself?
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Should call Verizon tech support if I were and run stock ota update , they might be able to help you more then us right now
Sent from my PC36100 using Tapatalk
Hi I hope someone can help me with thi one.....
I'm out of USA right now for matter of work, I unlock my Thunderbolt for use it here but I have now some odd errors around..once I updated to Build 2.11.605.5
Mainly is.... I can receive calls and SMS with out any problem, BUT if I want to make a call the phone freezes on dialing and the upper notification bar starts to blink in green (like it was on a call) but nothing happens and I can't hang I need to restart my phone in order to use it again.
I trie a lot of PRL's and carefully manually program any single option with QPST and every single PRL give me incoming calls/data/messages but can't make any call...
Also if I dial *611 the phone automatically dials 0019085594899 and hangs there in the calling freeze problem.
Any one knows something about this error or knows someone that suffer the same problem and found any solution?!
Thanks again for your valuable help!!!
I found this was because I update the Thunderbolt to 2.11.605.9 is there a way to solve this??
What Rom??
Need more info to really help...
Sent from my ADR6400L using xda premium
Thanks for response
The original was 1.60 Something I don't remembered exactly FROYO
I install RUU_Mecha_GINGERBREAD_S_VERIZON_WWE_2.11.605.9
And since I install that I loose the possibility of calling anyone and just hangs I only receive calls and SMS.....
Have you updated your radio to see if that helps?
Sent from my HTC Mecha using XDA App
Ive noticed that when sending certain sms messages, the messages will keep spooling and not send unless I delete and resend it. Seems to happen at random times, even with no signal it should still send when it gets a signal right ? Using the Handcent SMS
Same thing happens to me.
I had the exact same issue. I stopped using Handcent and the issue went away. I've never had this issue on any of my last 5 android devices. Really frustrating since I have used handcent as long as I can remember.
+1 - Yep, me too! Even using GVoice + Sprint integration, too!
Also, if I restart my phone all the texts will magically send. Anyone else find this to be the case?
I also noticed that I can't get voice to text to work. I speak, select the line that reflects what I said....and then nothing. It doesn't paste it in. Any one else?
amishbobinc said:
Also, if I restart my phone all the texts will magically send. Anyone else find this to be the case?
I also noticed that I can't get voice to text to work. I speak, select the line that reflects what I said....and then nothing. It doesn't paste it in. Any one else?
Click to expand...
Click to collapse
My speech to text didn't work when using swiftkey. I switched to stock keyboard. Speech to text is amazing
Sent from my EVO using xda premium
I'm having the same problem. texts i sent after and before the unsent ones send fine. using go SMS pro
Sent from my HTC EVO 4G LTE
i have this same issue with handcent as well
I used to always have issues with handcent. When I had the Hero none of the MMS would send. So since then I have been using Go SMS Pro.
I am using Go Sms and I have the same issue. It seems if I am receiving a text at the same time, mine won't send and I have to delete it and start over. Also, when I send an MMS, it will create drafts of the same thing that I have to remove. My voice to text on swiftkey won't work either. I will have to try it out on stock.
Sent from my EVO LTE using xda premium
I was having the same problem and what I thought was happening was the phone was closing Handcent (multitasking issue) before the text sent. I don't currently have my EVO LTE to prove that this is the case.
Sent from my PC36100 using xda app-developers app
It's all network improvements boys and girls. If you been experiencing dropped calls, network busy tones, missed, super late, or texts being rejected; its due to nv work.
Sent from my EVO LTE
mbaseball3 said:
It's all network improvements boys and girls. If you been experiencing dropped calls, network busy tones, missed, super late, or texts being rejected; its due to nv work.
Sent from my EVO LTE
Click to expand...
Click to collapse
How can you be so sure? I started experiencing this the day I got this phone.
I have the same issues. Unfortunately, the only time I actually get text on time and/or send text reliably is when I use Google voice. I hate Google voices SMS setup, its ugly, and you can't send attachments. Its a shame we have this very cool phone, that can't do the basic cell phone operations. However, I do agree that this issue could very well be a Sprint signal issue and not the fault of HTC.
I'd also like to add, this is my second EVOLTE and both had this issue. Also both phones were and is having problems receiving calls. My missed calls don't even register, so once again, I have to rely on Google voice to let me know I missed a call via email, even after my phone never rang.
WUESTSIDER!
Sent with my rEVOLTe, the Family JEWEL!
mbaseball3 said:
It's all network improvements boys and girls. If you been experiencing dropped calls, network busy tones, missed, super late, or texts being rejected; its due to nv work.
Sent from my EVO LTE
Click to expand...
Click to collapse
I can 100% guarantee you that this is not the reason for this btw....it may be in some places the reason but it is NOT the main reason this is happening...
I know for a FACT there has been 0 work on the towers in my area and seen this same thing happen...
Ok, so for me this is only an issue with third party messaging apps.
I have been using the stock app now and haven't had the issue once.
Go back to Handcent sms, boom! issues again.
amishbobinc said:
Ok, so for me this is only an issue with third party messaging apps.
I have been using the stock app now and haven't had the issue once.
Go back to Handcent sms, boom! issues again.
Click to expand...
Click to collapse
I have the same issue. I had the same issue briefly a few weeks ago; however, now it's happening only on Sprint's network. If I check "Roam Only" on Meanrom I'm able to place calls, and send/receive text messages just fine. It started happening again when I used the LazyPanda s-off. I asked Sprint to do an HLR reset, and I still have the same problem. I've updated the profile 7 times now.
The problem mainly happened on aosp roms and always has for me at least. People tell me they tried to call me and/or text me and couldn't get through but others can. So I tried virus's new sense rom to see if that would help and she couldn't get through to me either plus I never got her texts. Also, I often get busy signals and call cannot be completed messages when trying to call out.
When on aosp I ru, the enghboot and sense its 1.58. Any ideas?
Sent from my shooter using Tapatalk 2
Flash a stock rom, and call your carrier. They can refresh your device, or re-activate it to fix this problem.