Related
OK, I've been having this problem for a good couple of months now. About half the time that someone calls me, when I hit the Talk button on my phone it just mutes the ringer and doesn't answer the phone. Usually I try the 'Slide to answer' deal, and that just slides over to Answer and still doesn't do anything. I know the actual button is fine, it works great, i've tested it over and over again. I've changed HardSPL, ROM's, Radio's, etc. and I still see the same issue. What is wrong?! or is anyone else having something similar at least?
So I guess no one else has this issue, at all, with any ROM, radio, etc.?! I guess there must be something wrong with my phone. That kind of sucks.
schwags said:
OK, I've been having this problem for a good couple of months now. About half the time that someone calls me, when I hit the Talk button on my phone it just mutes the ringer and doesn't answer the phone. Usually I try the 'Slide to answer' deal, and that just slides over to Answer and still doesn't do anything. I know the actual button is fine, it works great, i've tested it over and over again. I've changed HardSPL, ROM's, Radio's, etc. and I still see the same issue. What is wrong?! or is anyone else having something similar at least?
Click to expand...
Click to collapse
I had the same issue with my htc mogul. These suggestions worked, give it a try (i will NOT take credit for these great tips/found them by searching):
dial ##778#/EPST/Modem Settings, change the slot cycle index number to 1
and or if that didn't fix it...
Take a look at your HKLM/Comm/ConnMgr/Planner/Settings/SuspendResume
It is a multi-sz value and should be #777. If it shows anything like ~GPRS or
something containing GPRS, change it back to #777 and soft reset.
Once I changed it back to #777, I can answer the call immediately when data is on, time and time again. Prior to this, there was a significant delay.
Please backup your phone prior to making these changes...
Good luck...
montecristo1 said:
I had the same issue with my htc mogul. These suggestions worked, give it a try (i will NOT take credit for these great tips/found them by searching):
dial ##778#/EPST/Modem Settings, change the slot cycle index number to 1
and or if that didn't fix it...
Take a look at your HKLM/Comm/ConnMgr/Planner/Settings/SuspendResume
It is a multi-sz value and should be #777. If it shows anything like ~GPRS or
something containing GPRS, change it back to #777 and soft reset.
Once I changed it back to #777, I can answer the call immediately when data is on, time and time again. Prior to this, there was a significant delay.
Please backup your phone prior to making these changes...
Good luck...
Click to expand...
Click to collapse
Thanks for the help, I don't know if I believe any of that though. First of all, the # codes are carrier specific, I have AT&T, what's your service? These codes didn't work at all for me. Second of all, I mentioned that I've changed ROM's numerous times, along with Radios, etc. and I still have the same issue. Maybe this worked for you, but for me it doesn't. I've been trying some stuff recently, re-flashing SPL, hardSPL, Stock ROMs, and I'm hoping the problem goes away although I'm not that confident. I keep thinking it must be physical as my phone's "talk" button works perfect. Every time I try it it always responds appropriately, except when trying to answer a call. Beyond that, when it does screw up, it at least mute's the ringer, so I know it's responding somewhere.
I'm not sure what to do about this. Guess I'd better just wait it out for a TP2 and sell this one and forget about it. Could be due to bad blocks, I've had numerous problems in the past that I've been able to pretty much prove were a result of bad blocks in the phone's memory. Oh well, thanks for trying, although none of that works!!
I assume he has Sprint.
I have the same problem answering calls too, and I think it's because of the slidetoanswer dialer. I'm using xECK29x's 6.5 ROM.
rccola159 said:
I assume he has Sprint.
I have the same problem answering calls too, and I think it's because of the slidetoanswer dialer. I'm using xECK29x's 6.5 ROM.
Click to expand...
Click to collapse
Thanks for the input, I think I'm going to try a different dialer for a while and see if that solves the problem. I wouldn't be surprised if that's the issue.
While his codes may be different (I'm also with AT&T), he may be onto something... I have had the same issue, but after reading this post, I have been watching, and the times the phone prevents me from answering are when I have had some sort of data (browser, GPS, etc) open in another window.
My 2 cents FWIW
schwags said:
So I guess no one else has this issue, at all, with any ROM, radio, etc.?! I guess there must be something wrong with my phone. That kind of sucks.
Click to expand...
Click to collapse
I have an unlocked euro touch pro and cannot answer a call by touching the onscreen answer button. It will continue to ring tho. I have gotten in the habit of just using the hardware answer key. I've flashed numerous diff roms and all are this way, even the htc updated rom from their site. The only one that worked was the oem rom preloaded on the phone from factory. Not a big issue to me. I just deal with it.
Have this problem with energy's Roms. If you are on his 3.0 still go into Start>Tweaks>Advanced Config. Scroll down to Phone, Click on Phone Skin then Disable it. The setup of the call is different. Be sure to re enter you voicemail for it is erased when you disable the skin. Worked for me. No problems here. BTW you must understand that any Rom you flash will not be perfect!
I also have the same problem. And i to beleve its the new dialer thing. will try and change it, although i realy like the way you can search a contact with it. The other one is just a litte to small i feel. Anyway thanx for a good tip.
I'm also running into the same problem. I'll try disabling the phone skin to see how that works out.
Thanks everyone for your input!! I was a little scared to see no one answer this is at first, but now I can see this is a common problem. The dialer has to be the issue here, I've been running a standard dialer (not the phone canvas) for a couple days now and it's been perfect everytime.
montecristo1 said:
I had the same issue with my htc mogul. These suggestions worked, give it a try (i will NOT take credit for these great tips/found them by searching):
dial ##778#/EPST/Modem Settings, change the slot cycle index number to 1
and or if that didn't fix it...
Take a look at your HKLM/Comm/ConnMgr/Planner/Settings/SuspendResume
It is a multi-sz value and should be #777. If it shows anything like ~GPRS or
something containing GPRS, change it back to #777 and soft reset.
Once I changed it back to #777, I can answer the call immediately when data is on, time and time again. Prior to this, there was a significant delay.
Please backup your phone prior to making these changes...
Good luck...
Click to expand...
Click to collapse
Hey, it worked! I can't thank you enough, as this has been bugging the heck outa me. My slot cycle index was already set to 1, but my SuspendResume setting in the registry was "GPRS_bye_if_device_off". I had gotten to the point that I knew my problem was related to having a data connection going, but I had no idea where to go from there, and had no luck when searching the forums for a solution. Now my phone answers almost immediately, even whan I have a data connection going. Thanks again.
Firstly, I have been searching this forum for about 2 hours. I have found a few threads with the same issues, but they are either not relevant or I have tried the solutions within the threads and they have not worked. Also, the threads I have found are a few months old. I have also searched the ROM thread seen below.
ROM: [06 Nov 2011][MAG/cLK] NexusHD2-Gingerbread V3.2a (GWK74)(Android 2.3.7)[tytung_r13]
Device: HTC HD2
ROM Installation Method: MAGLDR 1.13
SPL: 2.08.HSPL
When I accept an incoming call, the phone application hangs and after about 10 seconds I get a force close notification. Sometimes this is accompanied with a buzzing sound from my speaker. In some instances I have to remove the battery to restart the phone as it totally freezes.
This happened on Android 2.3.5 (of the ROM linked above) so I upgraded to 2.3.7 (of the ROM linked above) to see if it would fix the issue. It has not. I also wiped the phone and reinstalled the ROM, and again it hasn't fixed the issue.
Also, I do not have Skype installed so it's definetely not that.
I would have posted in the ROM thread but it wouldn't let me.
Any suggestions?
Many thanks in advance. I can provide additional information should it be required.
Benetration said:
Firstly, I have been searching this forum for about 2 hours. I have found a few threads with the same issues, but they are either not relevant or I have tried the solutions within the threads and they have not worked. Also, the threads I have found are a few months old. I have also searched the ROM thread seen below.
ROM: [06 Nov 2011][MAG/cLK] NexusHD2-Gingerbread V3.2a (GWK74)(Android 2.3.7)[tytung_r13]
Device: HTC HD2
ROM Installation Method: MAGLDR 1.13
SPL: 2.08.HSPL
When I accept an incoming call, the phone application hangs and after about 10 seconds I get a force close notification. Sometimes this is accompanied with a buzzing sound from my speaker. In some instances I have to remove the battery to restart the phone as it totally freezes.
This happened on Android 2.3.5 (of the ROM linked above) so I upgraded to 2.3.7 (of the ROM linked above) to see if it would fix the issue. It has not. I also wiped the phone and reinstalled the ROM, and again it hasn't fixed the issue.
Also, I do not have Skype installed so it's definetely not that.
I would have posted in the ROM thread but it wouldn't let me.
Any suggestions?
Many thanks in advance. I can provide additional information should it be required.
Click to expand...
Click to collapse
this isnt something about your phone so try another rom or tell the developers.
linkin_p said:
this isnt something about your phone so try another rom or tell the developers.
Click to expand...
Click to collapse
thanks a lot, i have same issue...maybe i'll try another ROM
buzzing HD2
Sometimes it happens on my HD2 on diferent rooms: NexusHD2 3.2, NexusHD2 ICS 1.1, MIUI 1.12.30, MIUI 2.2.17. It is not often. Any sollution?
It's same here! I am starting to think that the problem is with my phone! I tryed meny different ROM and settings...it always the same!
It doing it 2-3 times per day.
How to fix it ?
same problem
I'm using CM9 (v2.8) android 4.0.4 and facing the same problem. I tried many ROMs but can't fix the problem. Also tried some solution on this 4rum but no help until now.
I'm going to throw my HD2.
Same here
I have the same issues with different rom using nand or nativeSD.
1 on 2 receiving call, the phone freezes with a buzzing sound. I must to take the battery out to restart the phone.
same problem
I have the same problem with my HD2!
The phone freezes after I receive an incoming call with a buzzing sound/no sound. Sometimes it shows the error message of com.android.phone process, in other cases I need to remove the battery and restart the phone.
I have tried different kind and version of ROM(for e.g. NexusHD2, MIUI, TouchWizMod v3.0) but the freezing issue is still not solved.
As far as I checked the freezing is not related to any kind of installed software.
If anybody has a solution to this problem please share with me/us. I really do not want to get rid of my HD2.
Thanks in advance.
------------------------------------------------------------------------------------------------------------------------------------------------------------
I have found the solution. The reason why the phone did not work is the Viber application. I uninstalled it a moth ago and thence everything works well. I use the WeChat app instead of Viber and my phone works like a charm.
By the way, a member of the Viber team has commented on this forum that their application does not support any kind of custom ROM currently.
Im facing the same problem,its killing me, its been worst recently ! I cant answer any call on my HD2
this problem happend first time on android 4+ roms,
I tried diffrent roms after that, but still not fixed, anyone can help us to find a solution?!
-----
anyone using CLk has this problem?!
Im using Magldr
Im having the same problem here. Found no sulition currently. ROM - tytung NexusHD2 2.5
The phone freezes after I receive an incoming call with a buzzing sound/no sound. Sometimes it shows the error message of com.android.phone process, in other cases I need to remove the battery and restart the phone.
Click to expand...
Click to collapse
hmm same here, tried some different ROMS - SD (froyo) and NANDs (2 gingerbreads, now ICS), tried these on both of my HD2s, also changed RADIO from 2.15.50.14 to 2.08.50.05 - nothing helps.
sometimes when im getting a call (usually it happens twice a week, some weeks more often, some less), i press the button and the phone/app freezes, sometimes with a buzzing sound.
after that, system doesnt respond normally, on GB sometimes it autorebooted....
also tried without viber AND tried directly after reinstalling the different ROMS with no contacts, original ringtones - also happens there sometimes!
i dont think that could be a hardware problem, because both of my hd2 phones act the same way.....
any solution since that time?
At the moment I have latest Jelly Bean by cotulla, with Cyanogenmod, and when I make a call, the screen is black (turned off) even though I don't have it close to my head and sensor is not covered. When I abort the call, it doesn't respond and stays dark with button panel highlighted for several seconds, and only after I press power button for several times it awakens. The same happens for incoming calls. The phone is not usable as phone with such things happening... That's frustrating.
So, let me sum up what people (and I) have had on the subject:
1. Various Android ROMs were tried and issue is always present.
2. In my case, stock Windows 6.5 has a very similar issue - incoming calls are even ignored! At least I had the described problem after I decided to have an "old" but working phone and reverted to the stock ROM instead of Android. Alas, the phone was still having glitches when answering.
3. We don't know exactly how many HD2 are affected by the issue but it looks like more than 1% which is pretty much to be a serious issue.
I might assume we faced an intermittent hardware issue, that does not always reveal itself, and can only be reproduced after a certain "failure". I think it's hardware dependent because my phone was working fine but suddenly ceased to do that.
I'm very sceptical about fixing this issue for me or other users. It's an obsolete phone and any mass hardware issues that is not reported by manufacturer (btw, could this be checked out?) will scarcely be considered. The whole thing makes me think we just have to switch to our phones are gaming/browsing accessories, since it just doesn't work and the issue is apparently non-trivial to be examined. I would be though glad to provide any information and logs... but who cares? Even cotulla doesn't think HD2 is worth developing any more....
Hi folks
I have a Nexus S (i9020a). It has stock 4.1.2 Jelly bean from Google (downloaded the stock image and flashed it). It worked fine for over a month.
Suddenly few days back this device got a problem. When I dial any number I can't hear any dialing sounds and even after the call has connected I can't hear the opposite person and the opposite person also can't hear me (The phone still shows as 'Dialing' though it's already connected). The same is true when I answer any call. Both parties can't hear anything.
This is solved by rebooting the phone for the first phone call only. After I reboot, the 1st phone call works fine, then this problem persists for any calls I make/receive until I reboot the phone again.
I tried flashing a different radio but this problem is still there. I tried my sim card on a different phone and it works fine, so the problem is not that too. My 3G data works just fine.
I need this phone for the next few days/weeks (hopefully not months) before my Nexus 4 gets delivered :laugh:
Thanks..
Edit: Modified the title; Probably gave the wrong meaning that the problem is solved.
<bump> Modified the title. Earlier title gave an impression that the problem is solved whereas I still have a problem.
Have you installed any apps which could somehow affect the dialler?
Unless someone else can give you a different advice, I can't think of any other option than do a full wipe and reflash.
I haven't installed any such apps.
Also, I already did a full wipe and flashed the stock image again. The problem is still there.
Don't know what else you could try, sorry mate - hope someone else can help you sort it out!
Thanks for trying. I think I will go to some hardware shop and see if they can figure out..
Try using a headset for making phone calls so that we can identify if it's really the hardware's problem.
ej8989 said:
Try using a headset for making phone calls so that we can identify if it's really the hardware's problem.
Click to expand...
Click to collapse
That's the first thing that I tried... doesnt work.
mailrachit said:
That's the first thing that I tried... doesnt work.
Click to expand...
Click to collapse
I had similar problem when RAM running out. Usually a reboot fix the problem for a bit.
What I did:
1. With Titanium Backup Pro, froze unused RAM hogging system apps, like Google+, Google play magazine,etc
2. Froze or uninstall Facebook, Word with Friends, etc which are resident and hog RAMs .
3. Install marmite kernel, free up more usable RAMs.
Hope it helps you too.
_android_ said:
I had similar problem when RAM running out. Usually a reboot fix the problem for a bit.
What I did:
1. With Titanium Backup Pro, froze unused RAM hogging system apps, like Google+, Google play magazine,etc
2. Froze or uninstall Facebook, Word with Friends, etc which are resident and hog RAMs .
3. Install marmite kernel, free up more usable RAMs.
Hope it helps you too.
Click to expand...
Click to collapse
Thanks for the suggestion!
I tried this too but doesn't work...
Try any custom ROM instead of stock ROM and a different kernel too. There could be chances that you've flashed the wrong ROM / radio too.
Sent from my Nexus S
Problem solved.
I went to a hardware store today. The guy said that it's a problem with the 3G service of my carrier (Vodafone India). The moment I enabled the '2G only' option in the Mobile networks settings area, this problem was gone. The technician said that this issue is affecting some people randomly. He said that since 3G service was launched just last year, the networks are not yet capable of handling all kinds of devices (he claims that the bug is so erratic that another Nexus S i9020a may work just fine with the very same bootloader/radio/rom which doesn't make any sense). When I said that 3G service was working fine before, he said that most probably my carrier changed some settings on their side which is causing this issue for me.
I have tried this for 6-8 hours now, making a lot of phone calls and it seems that the issue is gone. It saddens me that I am off 3G for now but at least my phone calls and basic EDGE internet works fine. I will have to work with Vodafone to solve this or simply wait for my new phone (Nexus 4) and hope it won't have the same problem..
Hi everyone,
this is my problem. I use almost always a very good quality headphones set (but without mic): obviously if I need to answer/make a call I have to talk into the phone's mic. Well, very often I'm not able to send my speech...I'm receiving very well, but the listener on the other side is not able to hear me, or at least he listen a very-very-very low sound. I did myself a test, calling me from an other mobile phone, and obviously I tried more than one headset.
I wrote "very often": actually, at the beginning after a reboot, this is not happening. It starts happening after a while, usually one hour after reboot: if you have a call, you are able to talk for 5 maybe 10 seconds, then there is the issue.
I thought it was a ROM bug (I was using Viper 3.1.4), then I tried Viper 5, then Elegancia, then Revelation...same problem... so I think it could be a kernel related bug ( @SebastianFM Kernel). Actually, no AOSP ROM has the same issue (Albinoman, Sultan, bilal, etc.).
Please, someone with these ROM can check if it is true?
Sorry for bumping it up. Anyone has experienced same issue? @SebastianFM, could it be ROM related issue, or I must search in a different place? Take in account that it happens only in ROM powered with your kernel...
pdbc said:
Hi everyone,
this is my problem. I use almost always a very good quality headphones set (but without mic): obviously if I need to answer/make a call I have to talk into the phone's mic. Well, very often I'm not able to send my speech...I'm receiving very well, but the listener on the other side is not able to hear me, or at least he listen a very-very-very low sound. I did myself a test, calling me from an other mobile phone, and obviously I tried more than one headset.
I wrote "very often": actually, at the beginning after a reboot, this is not happening. It starts happening after a while, usually one hour after reboot: if you have a call, you are able to talk for 5 maybe 10 seconds, then there is the issue.
I thought it was a ROM bug (I was using Viper 3.1.4), then I tried Viper 5, then Elegancia, then Revelation...same problem... so I think it could be a kernel related bug ( @SebastianFM Kernel). Actually, no AOSP ROM has the same issue (Albinoman, Sultan, bilal, etc.).
Please, someone with these ROM can check if it is true?
Click to expand...
Click to collapse
Hi, would like to ask for some help to the community because every ROM i've tested, Arrow, Pixel Experience, etc etc i have an issue regarding receiving calls. When someone calls me, after 30 seconds call goes off. If i am the one who calls, all seems fine.
How can i make a better report for what is happening to me? I have no idea why this happens.
Now i tried ACIP ROM, and the same happened. Just after a clean install, the only ROM that this doesn't happen is MIUI latest. I am completely losing hope on using custom ROMS. Would love some help to log or whatever.
Is 30 seconds a time to screen off?
I observe similar behavior in Lineageos, but it is only screen off, not disconnect.
No, just the call. between 20 - 30 seconds it just disconnects.
Try turning off Wifi-calling
i_sagnik said:
Try turning off Wifi-calling
Click to expand...
Click to collapse
i will try that, but i don't think that comes by default.
Is there anyway i can log the moment it happens so i can post it here?
hfmls said:
i will try that, but i don't think that comes by default.
Is there anyway i can log the moment it happens so i can post it here?
Click to expand...
Click to collapse
Wifi calling caused my phone to double call, it would call hang up then call again.
Maybe its a network provider issue?
Have you tried format data and also if you use Wifi calling do calls get disconnected ?
I dont use wi-fi connection.
Strange that Miui works fine. Is there a way i can make a log?
still having this issue, any thoughts on this? how to debug it?
have you tried using other cards or networks?
@OP - is the phone still under warranty? Sounds like a hardware connection problem.
plskillme said:
@OP - is the phone still under warranty? Sounds like a hardware connection problem.
Click to expand...
Click to collapse
i thought that, but using MIUI works fine. Any custom ROM it doesn't.
hfmls said:
i thought that, but using MIUI works fine. Any custom ROM it doesn't.
Click to expand...
Click to collapse
Bruh that's weird, i've never experienced apps like this going ape crazy in the long run of me installing ROMs from here in XDA. Everything works fine except in all the custom ROMs
Ever tried to backup that "working" phone app and installing it on the custom ROMs?
Not sure if there's a way to log that event if ever you want logs to be saved and documented for troubleshooting.
hfmls said:
I dont use wi-fi connection.
Strange that Miui works fine. Is there a way i can make a log?
Click to expand...
Click to collapse
https://f-droid.org/repo/com.dp.logcatapp
Set Filter for errors, save output to file and analyze on a another device or try live? You could try to call somebody with speakers enabled while watching logcat
edit: forgot to mention - settings->buffers release don't stupidity