Please help with the "hello hello bug" (2-3 secs delay when answering a call)
There are lots of old threads about this, but I can't believe this is still an issue. You know the same old problem - When I answer a call the first 2-3 seconds the other side does not hear me, then everything is fine. It is called the "hello hello" bug or "Call Delay" bug, The oldest posts I see that explain the same issue are from 2011. Now 3 years later this is still NOT fixed. Come on Google get your **** together seriously...
It seems that every android phone that I've owned had this problem. This is my 2nd nexus 5 (the first had memory problems) and I still experience the same bug.
Anyway is there a known fix for this? Does anyone had this problem and fixed it somehow? I've read that there was some "Call Delay Patch" but I cannot find a working link for this, the app is no longer in the play store also.
I am experiencing the same issue since I bought the phone, even changing the rom to CM11 did not change the situation. Does anyone have an answer to this problem?
no issues here, im using lichtis rastakat build with trinity kernel.
bump bump.. Is no one else experiencing this issue? Saying hello 2 times after answering is a bit annoying .
I've experienced this issue as well, but I've only noticed it when I'm communicating with an iphone user. It never happens when i call or receive a call from someone on landlines or android phones.
I my case this happens with litteraly any type of phone. This is a really weird bug because it doesn't seem to be device specific, i had this happen to me on my old lg optimus black, but then installing a different rom, fixed the bug, now this happens on all the roms i've installed.
Could it be baseband specific?
Related
Hello everybody,
I recently had a very strange experience with my Vodafone VDA Compact GPS (this device is identical to HTC Trinity). I've talked to some friends of mine who know about mobile networks and Windows Mobile but it seems, I'm the only person who ever had this particular problem.
Here's what happened:
I had called a friend. He had picked up and we were talking so the call had already been established.
All of a sudden, during our conversation, I start hearing a busy tone from my phone. I'm still hearing my friend so the busy signal came out of nowhere parallel to the active call.
I check my phone display and it now shows two separate calls. First it says "Busy" and underneath this it shows the call with my friend (his name and the seconds counting).
In other words it looked as if my phone on its own accord had tried to call someone else during my call and was now getting a busy signal.
I asked my friend if he could hear the signal but he heard nothing.
Then the next strange thing happens. After 10 seconds of this then the phone software shows the call being finished. Meaning in the display I could see "Last call - my friend's name" and the "call" icon was back to green. I even tried pressing the "call" icon but nothing happens.
Only the call isn't really over. Although the display says otherwise, the call is still ongoing and I can talk to my friend for another 15 seconds or so before the actual call is suddenly interrupted.
In other words, the software is showing that the call is over but it really isn't. And the whole incident was caused by a busy signal that came out of nowhere.
After this incident I call customer support but they insist that I didn't call anyone else at the time.
As stated above, I've not been able to find anyone who has ever even heard about this particular malfunction let alone who could explain to me what might have been going on.
Has anyone here ever had the same or a similar experience or can anyone explain what might have happend?
I really hope somebody can help me out here.
/peter
Hmm, still no answers.
Maybe I should clarify my question. What I'm wondering is if anybody has experienced the same problem?
And/or if there's somebody out there who knows about these things whether this strange incident was most likely caused by a software malfunction on the device or any kind of network glitch....
I was told this forum is where the best of the best gather. So where do I find an answer if not here?
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....
Hello, i need some serious help over here
What's the problem:
I own a galaxy 3 since June, a week ago i started noticing the internal mic wasn't working on some incoming calls.
Details:
First of all the problem began for no apparent reason (the phone works fine otherwise and no major updates / new apps were installed)
This started happening on the official froyo ROM which was an excuse for me to flash the Kyrillos 9.4 ROM (wiped all data / formatted sd card in the process). The problem still occurs on Kyrillos 9.4 ROM suggesting that this is not a ROM issue
I thought it was a hardware issue but the caller can hear me perfectly if i connect the headset or use the speaker Also the internal mic works fine on some incoming calls and ALL outgoing ones!
Upon further investigation i came upon 2 threads on other forums (unfortunately i can't post the urls as i am a new user, if needed pm me or search google for "Microphone not working on incoming calls") which point out that the same problem incurs on HTCs and XPERIAs. Also it happens on replacement phones (original unit shipped back after this problem), on different providers, on official and custom ROMs, on clean phones (only the stock apps installed).
This seems to happen when the phone is idle for a set period of time (unconfirmed). Fast Reboot app / manual reboot / removing battery don't fix this, however making an outgoing call seems to enable the internal mic temporarily (even if the outgoing call never connects)
When this happens apart from the mic not working on incoming calls it becomes also unresponsive for other apps (Tape-a-Talk, Skype, Soundhound etc.)
Conclusion:
It seems to me that there is bug in froyo that keeps the incoming call code from activating the microphone or perhaps there is a conflict of sorts that keeps the microphone blocked. It is highly unprobable i think that the microphone would randomly start to fail on different android phones in the exact same way, so this shouldn't be a hardware issue.
Question:
Does anyone know/guess or can produce a possible solution for this? If not, could you please suggest further testing steps to help reproduce 100% this problem in an attempt to solve it?
Any help would be greatly appreciated as this is a pain in the neck for me (and others i guess?!)
PS: Excuse the thread form, i 'm really bored of writing / reading long posts
PS 2: This is my first post, hello xda community!
samsung vibrant
I have the same problem. I flashed the phone from android 2.1 TO cyanogen 2.3 and from it TO ice cream. I had this problem even to cyanogen and only in incoming call,never in other situation.
Googling I found same information but no solution. Anyone here knows something?
Anyway I found a stupid solution....try switching to 2g( I know that it's not a solution but...). It works for me!
that's ridiculous! how can network state have anything to do with the microphone of the device? can this be related to service providers maybe a more techish member could tell us.
anyway i am on 2g already as i don't have a usim card and this happens even if data network mode is deactivated. glad you found a way out but is it really a solution? i mean you have to ditch 3g for the phone to be actually a phone...
Since we seem to be the only ones among so many to be having this problem i am seriously thinking of taking back the phone for a replacement and hope for the best...
just an update, i lost functionallity of the microphone completely earlier today. That is with outgoing / incoming calls and any app i can think of, so i thought i 'd try changing the network data setting to 3g only since i was already on 2g...
WOW!!! that had an instant effect,it works seamlessly now,didn't even have to reboot.fingers crossed it will last.
that is one nasty and very strange bug. Please any of the developers could you take a closer look at this?
much appreciated
Sent from my GT-I5800 using XDA App
Hello,
I recently got lollipop update for my Nexus 5 OTA, After updating my phone i am experiencing issues while answering incoming calls. When i get an incoming call my phone rings and vibrate but nothing shows up on the screen.
I have to press the power button to bring my screen back to life and then unlock it to answer the incoming call. Without unlocking the phone i am not able to answer any incoming calls
This was not happening with 4.4.4. I am not sure if anyone else is facing same issue and i am not able to locate any workaround under settings of the phone. Any help on this will be highly appreciated.
Roy2208 said:
Hello,
I recently got lollipop update for my Nexus 5 OTA, After updating my phone i am experiencing issues while answering incoming calls. When i get an incoming call my phone rings and vibrate but nothing shows up on the screen.
I have to press the power button to bring my screen back to life and then unlock it to answer the incoming call. Without unlocking the phone i am not able to answer any incoming calls
This was not happening with 4.4.4. I am not sure if anyone else is facing same issue and i am not able to locate any workaround under settings of the phone. Any help on this will be highly appreciated.
Click to expand...
Click to collapse
Unfortunately this is a known issue that hundreds, if not thousands of people have been experiencing and reporting ever since the phone was released a year ago. So yes ever since 4.4, before even 4.4.2. Even more unfortunately it is a known issue that neither Google nor any carriers admit to own up to. Anyways to my knowledge no one knows if it is a software or hardware issue, but it is most likely not a carrier issue since it is reproduced on multiple different carriers. Anyways I will link you to the Google Forums thread that started on this issue a year ago and has hundreds of people posting and reporting it in that thread. You can find that post if you click right here.
The only solution is a work around, not a permanent solution. If you find out that someone called you, and the phone did not ring, restart the phone. It seems to have resolved the issue temporarily. I always restart mine every 2 to 3 days anyways to try to prevent it as little as possible, so that is what I would suggest. Also maybe state on your voice mail if you did not pick up to leave you a voice mail or send you a text so you know they called, because you been having issues with calls on your phone. That way you know someone called, because you will still get the text message or voice mail notification.
I had the problem mentioned in the second post (which may not be what OP was describing) and I solved it by trying out different radios. Latest one with Lollipop is fine, but the two before that weren't good.
I have been facing this issue from the time I installed CM12 or any CM12 based ROM. Pretty surprised that there are two or three mentions of this problem in some of the threads but non has replied. Don't know whether its a bug or some intermittent issue. Problem is When I am on a call and a new call comes in(call waiting), my call goes on HOLD automatically and if I reject the new call, my already active call didn't work. I have to disconnect the call and call the person again. This problem is very annoying.
Can anyone please help.
mannu_in said:
I have been facing this issue from the time I installed CM12 or any CM12 based ROM. Pretty surprised that there are two or three mentions of this problem in some of the threads but non has replied. Don't know whether its a bug or some intermittent issue. Problem is When I am on a call and a new call comes in(call waiting), my call goes on HOLD automatically and if I reject the new call, my already active call didn't work. I have to disconnect the call and call the person again. This problem is very annoying.
Can anyone please help.
Click to expand...
Click to collapse
I'm having the exact same problem and have been searching for a solution but no luck. Because of this reason I've been having to go back to KitKat. Does anyone have a solution for this? I have the lollipop one plus modem that I flash every time I flash any lollipop rom
That's what happens when you volunteer to test alpha firmware.
An easy workaround is disable call waiting bc it sucks anyway. Nobody likes to be put on hold. You can have interruption-free calling and extra incoming callers get an old-fashioned busy tone.
Did anyone filed bug for this..
tollboy said:
Did anyone filed bug for this..
Click to expand...
Click to collapse
No I just went back to kit kat.
same problem. its really problematic.even the people are ia m in call with are getting irritated as they are being pushed to hold. some one from cyanogen should address this
mannu_in said:
I have been facing this issue from the time I installed CM12 or any CM12 based ROM. Pretty surprised that there are two or three mentions of this problem in some of the threads but non has replied. Don't know whether its a bug or some intermittent issue. Problem is When I am on a call and a new call comes in(call waiting), my call goes on HOLD automatically and if I reject the new call, my already active call didn't work. I have to disconnect the call and call the person again. This problem is very annoying.
Can anyone please help.
Click to expand...
Click to collapse
Hello...I am yureka plus user....I have installed Cm12 manually.....I have resolved many issue.....but still facing is conference call....as it shows"can't switch calls" and goes back to current call......neither it hold the call.....shows same error...please help.....big fan of cyanogen.....as able to use full features of my device...