Related
I have an HTC Hero that keeps entering "Emergency Callback Mode" for what seems to be no reason at all. It mostly happens as soon as I answer an incoming call but also randomly in between.
This mode kills all data conenctions and prevents outgoing calls for 5:00. But, even if I say cancel, or wait the 5 minutes, it still stays on and I have to reset the device. It usually resolves itself after 45 mins or so. It happens once or twice a day.
I have researched the issue on google and I have found very little information about this problem. On some phones, this mode is enabled immediately after calling 911 to allow rescuers to call you back and locate you via GPS. I have never called 911 on this device.
I am currently running Cyanogen 7.1 RC2 ROM but I had the same issue on many different ROMS I tried so its not related to that.
on baseband 2.42.01.04.27. Maybe I should try downgrading it? How can I do that safely?
I really don't want to try reverting back to a stock ROM...
EDIT:
I think I posted this in the wrong forum, mod please move, sorry.
Hmmmm........so a complete doesn't solve the issue? And when you say ''sense'', does that mean with sense, it doesn't happen, but with the other Roms it does?
Try updating your radio to the latest .29
Yea its Me Again With the
Modified Hero
I just upgraded to the lastest baseband and it's still doing it.
I also figured out I can trigger the problem immediately by going to mobile network settings and changing my roaming preferences.
I should probably not that I recently repaired this phone and used QPST service programming tool to copy settings over from a touch pro 2 to the Hero. Could there maybe have been a wrong setting from the TP2 that is affecting the CDMA on this phone??
Just did a PRL update. No luck...
Did a succesful over-the-air profile and PRL update. Same problem...
ki1022 said:
Could there maybe have been a wrong setting from the TP2 that is affecting the CDMA on this phone??
Click to expand...
Click to collapse
Sounds like it. Is there no way to put everything back to default manufactured settings?
oohaylima said:
Sounds like it. Is there no way to put everything back to default manufactured settings?
Click to expand...
Click to collapse
I am considering using a stock RUU to completely wipe the phone to factory settings, but am trying to exhaust all my other options first so I won't have to re-root it and set everything up again... I'm almost at that point though.
ki1022 said:
I am considering using a stock RUU to completely wipe the phone to factory settings, but am trying to exhaust all my other options first so I won't have to re-root it and set everything up again... I'm almost at that point though.
Click to expand...
Click to collapse
!!!!!!!!!!!
FIXED IT SUCKAS.
Did a ##786# which reset all the CDMA settings, then re-did my NAM and data profile settings and it works. Go figure. Doing the ##786# on this phone also retained nearly everything including meid, baseband, recovery, and ROM. All it did was fix the problem. Awesome.
I still have no idea what was causing this to begin with, it was driving me crazy. Hopefully this thread will be helpful to someone else who has the issue.
On a side note, how dumb is this emergency mode?? So you call 911, then you can't call anyone else after that?? What if you need to call your wife and kids to say you love them one more time?! Haha.
Awesome!!!!!! Glad it's fixed. Now I'll just star this just in case it happens to me.
So my girlfriend's Nexus S has been losing the entire voice and data network and going into no service mode, no biggie at first, just cycle airplane mode, then it went on to rebooting because you would select airplane mode from the power off menu but it would not check the box in the wireless settings menu.
After the reboot the box would show checked and airplane mode could be disabled and the service would resume. The the phone started getting stuck in airplane mode and not even rebooting it would bring it out the first few times, then it got to the point of resetting the phone, a wipe cache/data reset didn't fixed it. So off to T-Mobile for a new sim card. Rebooted the network immediately. And as of last night its back in full force and now not even a new sim will resurrect the network.
Have tried wiping, reflashing stock 2.3.3, new sim again, multiple resets, had to get an toggle widget to get it out of airplane mode and still a dead network, all this time the network in the *#*#4636#*#* menu showing unknown and is not able to be changed and reverts back to unknown immediately, OEM specifics settings button is greyed out and you are not able to disable the radio either.
While I'm going to call Samsung on Monday and I guess send the phone off, I worry about mine because it too does it but only once a month or so, but I do constantly have issues resurrecting the phone from airplane mode at times because the box will not be checked in the wireless settings menu but I can see the airplane instead of network bars, problem persists with reboots sometimes.
I also would like to add that even when the box is not checked in the wireless settings menu for airplane mode, if you click it it just hangs forever and will try to select but never will and stays grey like its turning everything off, but if the scren goes off its like you never tried.
Has anyone else seen this? I have seen a lot of people with data network issues or having to reboot to get voice network back but nothing as bad as I'm experiencing.
Both our phones are and have been completely stock and unmodified.
Thankfully we still have her Vibrant and in case I need to send mine in my Nexus One.
Sent from my Xoom using XDA App
Have you tried restoring from another persons' pre-made nandroid backup?
This over-writes the radio firmware, you should give it a go!
I also found that I had problems on 2.3.3, however reverting to 2.3.2 gave me no problems!
Just contact me if you need any help restoring from a nandroid backup or finding the 2.3.2 backup files
cdaly985 said:
Have you tried restoring from another persons' pre-made nandroid backup?
This over-writes the radio firmware, you should give it a go!
I also found that I had problems on 2.3.3, however reverting to 2.3.2 gave me no problems!
Just contact me if you need any help restoring from a nandroid backup or finding the 2.3.2 backup files
Click to expand...
Click to collapse
Is that true? I am just on the verge of calling samsung. My phone won't connect to or display any available networks, and is pretty much now dumbed down to a small tablet. I've tried everything except another persons nandroid backup. I've been told to stay away from flashing another persons... but I'm really desperate.
If you could provide me with a backup, that would be awesome.
I'm having identical problem.
It was working fine yesterday, look back to it and now it's got no mobile network, nothing. Just the no bars and cross symbol. I've tried wiping dalvik cache, reflashing the radio, wiping data/factory reset, reflashing the rom, restoring with a backup (Backup of when I first rooted the phone) and still no signal. Nothing has worked..
Anyone got ideas on how to fix this issue?
Gawthorne said:
I'm having identical problem.
It was working fine yesterday, look back to it and now it's got no mobile network, nothing. Just the no bars and cross symbol. I've tried wiping dalvik cache, reflashing the radio, wiping data/factory reset, reflashing the rom, restoring with a backup (Backup of when I first rooted the phone) and still no signal. Nothing has worked..
Anyone got ideas on how to fix this issue?
Click to expand...
Click to collapse
Can you search for and view available networks?
This sounds like the CM7 powerwidget problem (3g/2g) I used it and I loss all network, phone process will crash every second, however if your phones are stock I can't think in anything causing it.
For CM7 you'll have to reflash and delete userdata or edit the sql database for the providers and change a value to 0, but you need root.
When I went to *#*4636.... my preferred service was "unknown" too, but now it is OK.
Try to dail:
*#*#4636#*#*
and find your network information.
ketchup539 said:
Can you search for and view available networks?
Click to expand...
Click to collapse
Nope. Sits their 'searching' but nothing shows up.
In, *#*#4636#*#*, it gives little to no information. Just says nothing for current network and for GSM disconnects it has,
Sate: DvInactiveState
disconnected with last try
at 9:59AM
fail because No Error
And that time never changes, stays at 9:59AM.
As my above post suggested, I've tried doing a factory reset and reflashing. I don't think I use CM.. I flashed with Oxygen 2.1.6 (using it's kernel) but I restored to Oxygen rom and trinity kernel after it didn't work.
Gawthorne said:
Nope. Sits their 'searching' but nothing shows up.
In, *#*#4636#*#*, it gives little to no information. Just says nothing for current network and for GSM disconnects it has,
Sate: DvInactiveState
disconnected with last try
at 9:59AM
fail because No Error
And that time never changes, stays at 9:59AM.
As my above post suggested, I've tried doing a factory reset and reflashing. I don't think I use CM.. I flashed with Oxygen 2.1.6 (using it's kernel) but I restored to Oxygen rom and trinity kernel after it didn't work.
Click to expand...
Click to collapse
That is the EXACT same problem I have. I too was using Oxygen 2.1.6 and lost all connectivity. I've just locked my bootloader and flashed back to stock ready to send for repairs. That rom must be doing something >.>
Oh no
I didn't want to send it back D:
Anyone got some suggestions that I haven't tried?
Gawthorne said:
Oh no
I didn't want to send it back D:
Anyone got some suggestions that I haven't tried?
Click to expand...
Click to collapse
I've been trying *everything* for last past few days. Nothing is working. That shouldn't stop you from trying though. Just stay well away from ODIN and those i9023 files, I've seen bad things.
ketchup539 said:
I've been trying *everything* for last past few days. Nothing is working. That shouldn't stop you from trying though. Just stay well away from ODIN and those i9023 files, I've seen bad things.
Click to expand...
Click to collapse
Cheers, going to a mates place soon to see if he has anything up his sleeves to try and fix this annoying issue..
If we somehow fix it, I'll be sure to post how we did here.
Gawthorne said:
Cheers, going to a mates place soon to see if he has anything up his sleeves to try and fix this annoying issue..
If we somehow fix it, I'll be sure to post how we did here.
Click to expand...
Click to collapse
Ok, it'd be great if you worked something out. I'm so glad i'm not the only person with this issue!
Anyone had any breakthroughs? *hopeful*
I wouldn't call it a breakthrough but I got somewhere!
Ended up putting a extremely thin piece of wire into the external antenna port at the back of the phone. Wasn't too keen on doing this, but my phone now has reception isn't stuck at the dreaded -113dbm.
The reception isn't good, but it's enough to send texts and have calls.
Although the area needs quite good reception for me to receive anything, and it's extremely sensitive. To get 3 bars in a place where I usually get full bars, I have to be outside. While inside it's reduced to none or 1 bar, which is enough to send/receive texts and a sort of lagging phone call (did a few tests). As mentioned before extremely sensitive. The phone seems to like it better when it's up-right. In the middle of the CBD at Brisbane I get full reception and 3G, which is fine but in the places where you usually get 2 bars, you get no signal at all, unless you're outside.
So this is hardly a fix. I will most likely be sending it to Samsung to get it actually fixed. Either that or get it fixed the same day and pay probably close to $100 so I don't have to wait 2 months waiting for Samsung to twiddle their thumbs.
Thats awesome! But I'm going to post mine off to Samsung USA tomorrow, which will take forever considering international shipping. Where could you get it fixed same-day? I'm going to try this wire thing
So it can't be a software issue, but maybe the rom overloaded the antenna and fried it or something? I'm glad we've got that far.
I've seen that nexus s has a problem like the iphone, the antenna gate. Try take the phone with the left hand looking to no touch the rear of the softkeys
Inviato dal mio Nexus S usando Tapatalk
RcrdBrt said:
I've seen that nexus s has a problem like the iphone, the antenna gate. Try take the phone with the left hand looking to no touch the rear of the softkeys
Inviato dal mio Nexus S usando Tapatalk
Click to expand...
Click to collapse
Its more serious than that my friend! Thanks anyway
I got a quote from a place in Brissy called "FixMyMobile" and they said if they can fix it, it will cost $99. Although I'll get quotes from different places (if I find them) and see what they charge however I don't think I will be able to get cheaper, most likely around the same price..
So I may do that to not wait the ridiculous time it will take to get it back from Samsung.. Not sure on places in NZ though.
Yeah it seems like a hardware issue definitely. I eventually reverted the phone back to stock everything and it still happened, so that there shouts hardware issue.
Hello everyone;
I flashed the latest official 2.3.5 last night. Missed three calls afterwards, as if I was not connected to GSM network. I was at home and signal was stable as usual. Anyone else noted unusual GSM behaviour?
Cheers
----------------------------------------
UPDATE: In order to better understand this issue, it could be interesting to know which service providers are being used; in my case, TMN in Portugal.
One week before flashing this ROM, I started using 3G, so I'm not sure if these missing calls are as result of the ROM change. I'm going to switch back to 2G for daily use and see how it goes.
Yes, if you search you will find other users with the same problem.
happens also with the other beta roms.
Sent from my U8800 using XDA App
It happens to me too unfortunately.. can't tell the reason why. GSM status seems ok.
I confirm this missing call issue.
People when ring me the first time they go straight to voicemail and only get connection on second try.
I think the only way to solve it is Huawei but there is not point of trying to speak to them and they just won't listen for what people say to them.
I can confirm this is happening to me too....after reporting all was well this was one of the things I didn't test out.
Weird thing is that I called my mobile from home and both went straight to voicemail...
yep.
but if you immediatly make a 2nd attempt you get connection
OK try this...
Turn off phone... re move battery and sim card.
Replace battery and start phone without sim card and boot up.
Unlock phone and open any app (doesn't matter just do something)
Turn off, remove battery, replace sim.... boot up again.
Just called from my wifes mobile phone and my phone rang OK.... will test further but that seems to have done the trick for now.
I got the same problem and so far nothing i did solve it... Just missing reinstall the rom again and see if wasnt any bug i got while installing... I don't see too many ppl with the same problem and i don't belive huawei had so many diferent hardwares in a single mobile phone model according with all the different ppl have with different phones.
I also have this problem with the new firmware. My phone doesn't connect to the network upon powering on.
I have to manually connect it, by going into the Mobile networks settings. Once i'm in that menu, it connects.
druida_69,
I can confirm that does not happens every time, I tested from other phone I only on the sixth call I got the ring... Worst, during this time I made a call without problems.
The question is on reception...
Sent from my U8800 using XDA App
this issue is killing me.
when I have the device disconnected or in a cal, when someone try to ring me and can't I always receive a message informing that the xxxx number tried to ring you at that time bla bla bla.
no calls
The same thing happened to me... also tried many things without success... downgraded to 2.2.2 (B138) problem solved...
I'm getting tired of huawei's poor support and buggy updates!!!
To be honest i don't know if this start to happen after or before installing geno‘s OC Kernel.
I can confirm that this happens when the phone stays for a long time inactive. Try not playing with you're phone gore 20 minutes or so and then try to ring youselves.
Its like if the phone entering in a zen deep sleep....
Same here
Started after updating to 2.3.5, anyone tried the updated 2.3.5 from Huawei? it removes the pink screen I heard, but maybe it fixes this issue
F****** Huawei. Just realised that I have this bug too with latest 2.3.5 release... I think that it's data dependent. If you turn them off it connects ok...
I didn't realize until I read this thread, but I have the same problem!
I'm over it, I'm going back to Oxygen until I can buy a new phone, and will probably never buy huawei again.
I had this problem initially but since I booted up without sim card and boot up again with it in hasn't been a problem...I've had to test this on a few different phones & reboots now and everything is fine....
Clevo89 said:
I had this problem initially but since I booted up without sim card and boot up again with it in hasn't been a problem...I've had to test this on a few different phones & reboots now and everything is fine....
Click to expand...
Click to collapse
I 've just done that and it seems to be fixed.
I 'll test it until tomorrow and if it works ok I will do a marrige proposal to you.
Thanks for now!
I've also tried, let see if this works!
Regards!
Didnt worked with me
Hi All,
I'm currently using Straight Talk with ATT SIM. Everything was working fine. I updated the software to 4.2.2 on Sunday. It didn't come OTA so I updated by going to Google Services Framework, clear data, then force stop. After a reboot, the OTA 4.2.2. showed up and I updated then.
Now, I am realizing that I cannot make or receive calls at all. Phone shows signal strength at 100% (4 bars) but when dialing, it does not go through, just silence, then a beep, then ends call.
I have tried rebooting phones, pulling SIM card out and replacing (twice) all with no luck.
HELP!!
Edit: I just realized I don't have internet connection either.
Larry216 said:
Hi All,
I'm currently using Straight Talk with ATT SIM. Everything was working fine. I updated the software to 4.2.2 on Sunday. It didn't come OTA so I updated by going to Google Services Framework, clear data, then force stop. After a reboot, the OTA 4.2.2. showed up and I updated then.
Now, I am realizing that I cannot make or receive calls at all. Phone shows signal strength at 100% (4 bars) but when dialing, it does not go through, just silence, then a beep, then ends call.
I have tried rebooting phones, pulling SIM card out and replacing (twice) all with no luck.
HELP!!
Edit: I just realized I don't have internet connection either.
Click to expand...
Click to collapse
Did you forget to pay the bill?
Sent from my Nexus 4 using xda app-developers app
What radio are you on?
Sent from my iPad 4
BigDig said:
Did you forget to pay the bill?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Haha. I wish it was that easy. No...account is current
mitchdickson said:
What radio are you on?
Sent from my iPad 4
Click to expand...
Click to collapse
Sorry for the newbie response but how can I find out what radio I am on?
Ah...found it.
Radio: 2.0.1700.48
I was on the same situation a couple days ago. after flashing 4.2.2, I can still make a call, people can still call me, but no sound from either me or them. The micros work fine (you can check by Voice Search).
At that time, after I ended messing everything up, I restocked the phone to 4.2.1. Everything worked fine after then. I dont know why this happens. You may wait for another solution. Just let you know that a restock can fix it, so dont worry. However I dont encounrage it becuase it wipes your phone completly.
opticaldh said:
I was on the same situation a couple days ago. after flashing 4.2.2, I can still make a call, people can still call me, but no sound from either me or them. The micros work fine (you can check by Voice Search).
At that time, after I ended messing everything up, I restocked the phone to 4.2.1. Everything worked fine after then. I dont know why this happens. You may wait for another solution. Just let you know that a restock can fix it, so dont worry. However I dont encounrage it becuase it wipes your phone completly.
Click to expand...
Click to collapse
Thanks for your reply. Yeah, I would like a solution that doesn't require complete wipe of phone.
So frustrating...been unable to use phone all day. Who knows how many calls I've missed.
Larry216 said:
Thanks for your reply. Yeah, I would like a solution that doesn't require complete wipe of phone.
So frustrating...been unable to use phone all day. Who knows how many calls I've missed.
Click to expand...
Click to collapse
In case you have no choice, back up your phone by Titanium backup. That saves everything you have at the moment
Same issue after 4.2.2 update
I'm having the exact same issue with my Nexus 4. Let me elaborate. I've had my Nexus 4 since the initial sale, today I got the OTA update sent via Tmobile. My phone seemed to work fine afterwards until I tried to answer a call. Upon attempting to answer or make a call (even with full service) the bars instantly drop to zero (hollow triangle) and an out-of-area tone & message display.
Restarted, pulled sim, sim worked fine in other phone, checked & rechecked APN/other settings, had Tmobile "reset" my device on network, finally wiped my device. I still can not make or receive phone calls. The radio seems to just disconnect when attempting to.
Spoke with Tmobile customer support (worthless), Tech Care (Very helpful & knowledgeable but no fix), Google Nexus support (Offered to replace device! However can't have any cosmetic damage). LG also contacted but zero assistance given.
I'm stumped, it seems to me that this issue might be related to the update disabling the LTE radio, because data & everything else works except for making calls. Like I said, Google offered to replace the device however I did (in good faith) advise them of a hairline crack on the back of the device, like many other N4 owners have had, not from a drop. Upon hearing of cosmetic damage they said that it's no longer their liability. I'm very disappointed but I understand.
Since the warranty is void from the crack, I'm going to root & play around.
Any questions or advice?
---------- Post added at 08:10 PM ---------- Previous post was at 07:44 PM ----------
Also, I'm on the same radio (Baseband?) as OP.
Radio: 2.0.1700.48
I'm curious to see if rooting will solve this issue. If yes, I will go this route.
Keep me posted. So frustrated.
Thanks johnmedic.
I'm having a constant problem with my phone. It seems like any time I leave the house and return, I'm unable to make or receive calls, until I reboot or switch airplane mode on/off. I still receive and send text/mms just fine, it's only calls. Anyone experience anything similar or have any ideas what may be going on? I have a constant 3-4 bar LTE signal.
Sent from my SM-G900V using XDA Free mobile app
Same problem
I am also experiencing this problem. I can send texts and otherwise use data to connect to websites and such, but cannot make or receive calls. When someone calls me, it goes straight to voicemail. When I make a call it does not even start ringing, or beep at the start of a call to indicate the connection.
I had this issue when i first got my phone. i had to call verizon and they updated something on their side and reset a few things.
Travisholt92 said:
I had this issue when i first got my phone. i had to call verizon and they updated something on their side and reset a few things.
Click to expand...
Click to collapse
Part of me thinks this wouldn't be a bad thing to have, just in case that pesky Ex decides today is the day she wants to call you. lolz
Nothing Worked
If anyone else is facing this problem, I would like to say that all Verizon could do was send me a refurbished phone. Even after a factory reset and resetting the network (on their end) worked. I hope this problem doesn't affect too many people.
Same issue - S5 will not make/recv calls
raziel36 said:
I'm having a constant problem with my phone. It seems like any time I leave the house and return, I'm unable to make or receive calls, until I reboot or switch airplane mode on/off. I still receive and send text/mms just fine, it's only calls. Anyone experience anything similar or have any ideas what may be going on? I have a constant 3-4 bar LTE signal.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
I'm now having this problem with my 2-week-old S5. Has anyone found a resolution?
gwaldron said:
I'm now having this problem with my 2-week-old S5. Has anyone found a resolution?
Click to expand...
Click to collapse
I had an issue with my S5 connecting to 4GLTE (Because of something stupid I did playing around). Chat give Verizon a ring (or chat with them on their website) and they will have you do the following:
1. Turn off WiFi.
2. Power down your phone
3. They will resync the signal (and do other secret things)
4. Power up your phone.
5. Your phone will reconnect to 4GLTE, the radio will then recycle, then connect back.
I've had zero issues since I did this a few days ago. Wouldn't hurt to try. Have your IMEI number ready for them incase they need it.
Solution, sort of
DarkMidnight said:
I had an issue with my S5 connecting to 4GLTE (Because of something stupid I did playing around). Chat give Verizon a ring (or chat with them on their website) and they will have you do the following:
1. Turn off WiFi.
2. Power down your phone
3. They will resync the signal (and do other secret things)
4. Power up your phone.
5. Your phone will reconnect to 4GLTE, the radio will then recycle, then connect back.
I've had zero issues since I did this a few days ago. Wouldn't hurt to try. Have your IMEI number ready for them incase they need it.
Click to expand...
Click to collapse
Didn't work for me unfortunately. I ended up going back to Costco and swapping it out for a new one. Back in business....for now. Thanks for the help.
I have a Samsung Galaxy S5, 4G LTE, Verizon it can make calls and send text fine the problem is that it cannot receive calls and text. Grateful your assistance in resolving this issue.
I haven't had the issue for a while but I had to get a new phone from Verizon .