Related
Has anyone suffered this problem? Phone rings, I pick up the call, the screen shows connected and starts the call timer but you cant hear anyone the other end. hang up the call and the phone freezes with only a soft reset (taking battery out) works. I have a T-Mobile contract handset and was running the 1.43 rom. I thought maybe flashing to another rom might help so tried the 1.48 update but still having problems. I have hard reset and installed no software but still have the problem. Any ideas guys.....
Since I cant see this problem on the forum I'm guessing its hardware related. I guess I'm going to have to find the original T-Mobile rom and flash it back before returning.
hey, I had the same problem and had even started a thread today. I went for broke and did a hard reset and this has solved it. Back up all your info and hard reset and pronto good to go!!
I wish it was that easy for me. I have hard reset 3 times, the last time I didnt install any software just in case one of my apps was causing the problem.
Everything seemed fine for a day or so then someone called me and it crashed again.
HTC HD2 call crashe Bug
flashflash said:
I wish it was that easy for me. I have hard reset 3 times, the last time I didnt install any software just in case one of my apps was causing the problem.
Everything seemed fine for a day or so then someone called me and it crashed again.
Click to expand...
Click to collapse
it has happen to me 2 times in one month, first time i was listening some musique some one call and as soon the call ended it Freeze.
Another time the phone was on stand by and some one call, and could not answer the phone just freeze.
Why why why Is HTC brilliant
I have the same problem with my WWE HD2. It seems to be linked to music playback off a slow microSD card. I used to get the bug with a Class 2 16GB card if I happened to be listening to music while I received the phone. After tha call ended the playback would resume normally but after a while it would start to stutter (reminds me of a similar bug in the original Diamond, infact) and eventually stop. After that, the phone would just stop responding to any inputs.
After popping in a Class 6 8GB card the issue is gone.
novaci said:
I have the same problem with my WWE HD2. It seems to be linked to music playback off a slow microSD card. I used to get the bug with a Class 2 16GB card if I happened to be listening to music while I received the phone. After tha call ended the playback would resume normally but after a while it would start to stutter (reminds me of a similar bug in the original Diamond, infact) and eventually stop. After that, the phone would just stop responding to any inputs.
After popping in a Class 6 8GB card the issue is gone.
Click to expand...
Click to collapse
Interesting you mention listening to music but for me the crash happens when the phone is in standby, caller id shows, then I hit the answer button and the call timer starts but I cant hear the caller. From then on, I can hang up and then a complete freeze. I wasnt listening to any music, the ring tone is on the phones memory not sd card, so not sure about the sd card connection. After my last HR I didnt install any software except resco file explorer and microsoft my phone. I still get a crash.
I was going to return the phone back to tmobile for repair but it sounds like its software related rather than hardware.
Flash,
Have a look at this thread...http://forum.xda-developers.com/showthread.php?t=468284 , act on it and see if it helps. Phone lockup in the way you described happened to me a couple of times when I first had the phone; no problems now.
WB
wacky.banana said:
Flash,
Have a look at this thread...http://forum.xda-developers.com/showthread.php?t=468284 , act on it and see if it helps. Phone lockup in the way you described happened to me a couple of times when I first had the phone; no problems now.
WB
Click to expand...
Click to collapse
was that the right thread you attached?
Anyone know of a solution to this as yet? Also happening to me - extermely frustrating.
flashflash said:
Has anyone suffered this problem? Phone rings, I pick up the call, the screen shows connected and starts the call timer but you cant hear anyone the other end. hang up the call and the phone freezes with only a soft reset (taking battery out) works. I have a T-Mobile contract handset and was running the 1.43 rom. I thought maybe flashing to another rom might help so tried the 1.48 update but still having problems. I have hard reset and installed no software but still have the problem. Any ideas guys.....
Since I cant see this problem on the forum I'm guessing its hardware related. I guess I'm going to have to find the original T-Mobile rom and flash it back before returning.
Click to expand...
Click to collapse
I have the same problem but only when my band is switched to 3G but not every time.
Daniel
I have had my phone since Xmas no problems, updated to 1.66 ROM and have had this issue twice since.
DexterDuck said:
I have had my phone since Xmas no problems, updated to 1.66 ROM and have had this issue twice since.
Click to expand...
Click to collapse
Me too. i didn't had this problem with Rom 1.43
Found solution guys! It was me not closing down the radio before pulling the headset out. I have not experienced the issue anymore.
flashflash said:
Found solution guys! It was me not closing down the radio before pulling the headset out. I have not experienced the issue anymore.
Click to expand...
Click to collapse
What do you mean by "not closing down the radio" ?
Daniel
Sorry, I forgot the FM bit. In the past I used to listen to the FM Radio and pull the headphones out and the handset I thought automatically closed the FM app down. Any calls recieved on the handset after this would hang the HD2 after picking up the call. Up until the phone rang the HD2 would perform as normal, it was just an incomming call that triggered a crash. You could even make an outgoing call without a problem!
Now I close the FM app (by using the standbye icon on the app) first, then pull the headphones out. Not had the issue again.
Not solved for us that this happens to everytime... i can reset myphone and try to call right after the reset and it still happens.... I cant make a call or recieve a call at all lol
I had the same problem with radio rom 2.06.50.04 and 2.07.50.27 and miri's rom 6.5 v4.0.
Flashing to dutty's HG v0.8 rom with radio rom 2.07.50.27 solved it.
I had the problem with Dutty's v.06 and now have it with RoMEoS Rom....Don't think it is the Rom, and thought it was an app I isntalled until the OP said that he still had the problem with it even with no apps installed...
Bowhuntr11 said:
I had the problem with Dutty's v.06 and now have it with RoMEoS Rom....Don't think it is the Rom, and thought it was an app I isntalled until the OP said that he still had the problem with it even with no apps installed...
Click to expand...
Click to collapse
You might wanna try some different radio roms. Not really sure if it helps, but I guess the radio rom deals with calls etc.
Hmmm alright I will try that, I didn't think the radio rom's would freeze the phone...but I will try that as soon as I can get home.
My Problem is whenever i use to get an incoming call,i slide it to ANSWER direction,and it becomes stuck over there..i tried calling to my hd2 through other phone and whenever i tried to answer it in my hd2 by sliding it to ANSWER direction it stucks over there without connecting,and on the other which i am calling keeps on Ringing..
what is this problem..atlast i have to reset to the factory setting then only it becomes OK.
Please someone find me a solution
thank you
try to turn off 3G. Set GSM.
run \Windows\CMBandSwitching.exe, uncheck "Auto", check "GSM"
still having the same problem...anyone help
I've got the same problem!
Tried hard reset, tried upgrade tot official 1.66 rom... Still having the same problem. That after 3months of perfect use...weird!
i also facing the same problem ....
just wonder how to solve it?? seems like more serious now... really sad! need some body to help.
has anyone tried a hard reset and seeing if this solves the issue, remember a hard reset will wipe all your data.
ya hard reset will solve the problem ..but it will come later ...
we should found out the root cause to avoid it happen again & again ...
as per others member mentioned in the others thread it may caused by did not close the FM radio application is it true...
I have same problem and still unknow how to fix that, it happened some times not always but its causes annoying. Anyone can help ?
nghienppc said:
I have same problem and still unknow how to fix that, it happened some times not always but its causes annoying. Anyone can help ?
Click to expand...
Click to collapse
I had the same problem and solved it by updating my ROM.
nessqn said:
I had the same problem and solved it by updating my ROM.
Click to expand...
Click to collapse
The smart way to resolve it
this problem has been reported when using cht lock screen in earlier versions of cht...any bells ringing???
Incoming call problem
Hello ! I have a major problem....
I cannot receive calls ( call disconnected ) it appears when someone try to call me !
This problem i have it since i upgraded my rom version (3.14.479.2)
i tryed soft reset, hard restet.......and nothing happen ! Still this problem....aaa help???
Hello,
I have the same problem. I have had this problem with the MIUI and the Cyanogen ROM. Even after updating it still gets stuck.
When I receive a call the screen turns black and I can only answer it by pressing the button, not by using the screen. After the call the screen is still black and the only way to use it is to reset my phone (take out battery).
Any help?
Have only had my HD2 since Friday and was going to send it back tomorrow because the speaker has never worked. But now it's starting working.
No idea what triggered this or whether it'll remain "fixed" forever. All I did was try to replicate something that made my HD2 freeze in a completely unusable way yesterday (see my other thread) and suddenly it started working.
Having done a search it appears a few users have had speaker issues. Has anyone else had this problem rectify itself? Can I expect it to remain okay?
Cheers
SC
I have tried searching through out the forums and even on Google haven't been able to find a fix.
Out of nowhere my phone will stop notifying me of text messages and phone calls. The sound wont work at all, even if I notice someone is calling and I answer I wont be able to hear them and they cant hear me. It will work again after a reboot but it is still VERY annoying.
This is the second epic I have had this problem on.
I'm running SRF 1.2 and genocide 2.0 I've tried re-flashing the ROM and kernel multiple times on both devices.
anyone have any ideas?
I had problems with Notification sounds, but remounting SD card solves them
All stock.
hmm i don't think that will fix my issue if the person on the other end cannot hear me as well. it has to be a system problem however i'm not sure if it has to do with my kernel, ROM or if i'm just very unlucky and had two phones with the same problem back to back .
OK, having a huge problem with my Nexus 4. I'm still running stock kernel/ROM (although I am rooted) and everything about the phone works great EXCEPT for the phone itself! What I mean by this is: everything works (data, texts, tethering, et cetera), I can make and receive calls... but on those calls, there is no sound in *either direction*; when on a call, the mic doesn't pick up my voice, nor does the speaker relay the caller's voice. WTF?
My in-call volume is set to maximum, as checked via Power Toggles.
I've also noticed that the phone has a hell of a time hanging up after a call. For instance, I make a call on the N4 (again, no voice/sound during said call), and when I go to hang up the phone screen simply says "hanging up" and hangs like that for almost a minute. If I try to make another call after that, I get an error "Call Not Sent".
Any ideas how I might be able to track this problem down?
I should also mention that I don't know how long this problem has been present. I really don't use voice calling very much. When I tested the phone when I first received it, I simply made a call from it and to it from our land line and made sure it rang... I didn't think that there might be any issues with the call itself!
I have a brand new N4 that I just rooted using WugFresh toolkit and I see now that I can't hear anything during a call nor can the other person hear anything.
I've tried downgrading to .33 and .27. Also reflashing .48 with no success.
What should I do?
If you are experiencing the same problem I was, it wasn't fixable. I tried everything (reflashing stock, trying different ROMs, etc.)... and apparently it was just a hardware defect. I contacted Google and after explaining the issue (which they hadn't heard about at that point) they shipped me a new phone, which works perfectly.
I would highly recommend not wasting your time trying to diagnose the issue further and get in touch with Google about getting a replacement.
Cheers,
Matt
Thanks a lot for getting back to me. I contacted them and they already sent a replacement unit.
I found a thread on Google forums with six pages of people complaining about this. Apparently is not an isolated problem. Half of the people have the problem after updating to 4.2.2 and the other half (last pages) are all with new phones (4.2.2).
jumped in been a while since I had a play with LS - first impression love the splash screen :good:
Same problem, no warranty
Lucky you guys who were still under warranty. My Nexus 4 is 2 years old now and I just got this problem. It seems to be software related. The mic and speaker works for anything else other than placing phone calls. Furthermore, even if I plug a standard headset thought the 3.5mm jack, still no luck. The same with bluetooth headset.
It's interesting that when this problem started I would be able to place or receive a call once per reboot, i.e., after rebooting, the speaker and mic would work on the first call, but not for the second call unless I reboot the phone. Now I doesn't work even after reboot.
Gargabe?
Hi,
I have exactly same problem with sound during call. I'm using CM11. It doesn't matter if it is nightly or snapshot, simply there is no sound during call. Everything except calling works fine - music, ringing etc.
Restart didn't fork for me and also deleting application data has no effect. I've found only one solution - factory reset approximately each week. It is obvious that this is only workaround and not real solution.
I don't know if it is HW or SW issue. Strange think is that factory reset helps.
Any ideas are welcome. Thank you in advance.
novicz said:
Hi,
I have exactly same problem with sound during call. I'm using CM11. It doesn't matter if it is nightly or snapshot, simply there is no sound during call. Everything except calling works fine - music, ringing etc.
Restart didn't fork for me and also deleting application data has no effect. I've found only one solution - factory reset approximately each week. It is obvious that this is only workaround and not real solution.
I don't know if it is HW or SW issue. Strange think is that factory reset helps.
Any ideas are welcome. Thank you in advance.
Click to expand...
Click to collapse
I have the same problem.
Reverting to stock solved the issue form me until a fix for CM11 will be found.
BTW there is a bug report for CM11.
I can't post links but the code is CYAN-5728 on the CM bugtracking system.
novicz said:
Hi,
I have exactly same problem with sound during call. I'm using CM11. It doesn't matter if it is nightly or snapshot, simply there is no sound during call. Everything except calling works fine - music, ringing etc.
Restart didn't fork for me and also deleting application data has no effect. I've found only one solution - factory reset approximately each week. It is obvious that this is only workaround and not real solution.
I don't know if it is HW or SW issue. Strange think is that factory reset helps.
Any ideas are welcome. Thank you in advance.
Click to expand...
Click to collapse
The issue is with Google Play Services. more specifically the checkin service within it.
(this is from the CM bugtracking system , code: CYAN-5728, as stated by pupillo)
download/install the app "DisableService" from the play store. (must be rooted)
under the [System] tab, browse to "Google Play Services", tap it, then browse to "checkinservice", uncheck. (it will prompt for superuser, allow)
restart phone
try placing/receiving a call
none of u guys spent even 1 second to check this forums for answer. there have been at least 2-3 threads about this issue, all of them containing/linking to the fix.