Hi,
I noticed weird problem with Nexus 5/ 4.4.
Whenever I make a phone call and if the the receiver is busy (line engaged) it is impossible to hang up the phone straight away. First it give untraditional busy tone and then if I press hang up the tone won't go away at least for next 10secs and impossible hang up until phone it hangs up it self after 10sec. I'm sure lots of people must be having same problem.
Please advise.
Many thanks
above
Sabrber said:
Hi,
I noticed weird problem with Nexus 5/ 4.4.
Whenever I make a phone call and if the the receiver is busy (line engaged) it is impossible to hang up the phone straight away. First it give untraditional busy tone and then if I press hang up the tone won't go away at least for next 10secs and impossible hang up until phone it hangs up it self after 10sec. I'm sure lots of people must be having same problem.
Please advise.
Many thanks
Click to expand...
Click to collapse
Please any1???
I've had this as well once. Just tested it, wenn calling myself I cannot hang up, but the phone hangs up after 2 seconds.
same
becks5 said:
I've had this as well once. Just tested it, wenn calling myself I cannot hang up, but the phone hangs up after 2 seconds.
Click to expand...
Click to collapse
Mine about 10secs at least. Is it same with urs? when u call and if line is busy impossible to hang up straight away?
quan ubspod
Try to calk some other number and reject it see if it hangs up straight away.
I'm not at home right now, will test this later...
https://code.google.com/p/android/i...+5&colspec=ID+Type+Status+Owner+Summary+Stars
Here is the bug report for this. From what I am hearing it may be carrier dependent but could also be a hardware issue.
Sabrber said:
Mine about 10secs at least. Is it same with urs? when u call and if line is busy impossible to hang up straight away?
Click to expand...
Click to collapse
Most phones will respond this way - this isn't a "new" problem. Perhaps 10 seconds is an extremely long time and it doesn't make sense why you're getting that kind of time, but standard 2-6 seconds is common. Typically what happens with these phone lines is when you call a number and receive a busy tone in response, the transaction is metaphorically grabbed and held onto in the attempt that the called line becomes free again.
Perhaps with Android 4.4 or the Nexus 5, a newer technology has been integrated which is causing long times in this case. I have not experienced this but it sounds frustrating. When this happens - are you calling a land line or mobile device?
same
FourPointedFreak said:
Most phones will respond this way - this isn't a "new" problem. Perhaps 10 seconds is an extremely long time and it doesn't make sense why you're getting that kind of time, but standard 2-6 seconds is common. Typically what happens with these phone lines is when you call a number and receive a busy tone in response, the transaction is metaphorically grabbed and held onto in the attempt that the called line becomes free again.
Perhaps with Android 4.4 or the Nexus 5, a newer technology has been integrated which is causing long times in this case. I have not experienced this but it sounds frustrating. When this happens - are you calling a land line or mobile device?
Click to expand...
Click to collapse
Hi,
Doesn't matter whether I call mobile or landline. I tested both and same problem. And its really really frustrating.
I know it might take few secs to hang up with other phone but not this one unbelievably long and I hope thisnt hardware issue. Already exchanged this one previous n5 came CPU faulty (posted on my previous post)
same
bekyndnunwind said:
https://code.google.com/p/android/i...+5&colspec=ID+Type+Status+Owner+Summary+Stars
Here is the bug report for this. From what I am hearing it may be carrier dependent but could also be a hardware issue.
Click to expand...
Click to collapse
Mate you are a Star. I knew it wasnt only me. GOOGLE, please sort this one out before i change my mind and return my phone.
I have the same issue on Three in the UK. Hope it's fixed soon!
Sabrber said:
Hi,
Doesn't matter whether I call mobile or landline. I tested both and same problem. And its really really frustrating.
I know it might take few secs to hang up with other phone but not this one unbelievably long and I hope thisnt hardware issue. Already exchanged this one previous n5 came CPU faulty (posted on my previous post)
Click to expand...
Click to collapse
Does this happen when you hang up ANY call or only calls unanswered and you receive a stern dial-tone back signaling they're busy?
same
FourPointedFreak said:
Does this happen when you hang up ANY call or only calls unanswered and you receive a stern dial-tone back signaling they're busy?
Click to expand...
Click to collapse
No!
It happens when I call and receiver is busy (I get busy signal, not the one with short tones but music like tone) and that's it I am unable to hung up. Even I press hang up, hunging up button turns to grey from red but tone goes on for at least 10-15secs, I tried to exit by pressing home button but still tone will be there until the phone ends it in long time.
Hope this helps.
May be later I'll post the link on YouTube.
I have this issue too on three UK. Have to use airplane mode to end the call. Very frustrating.
Sent from my Nexus 5 using xda app-developers app
YES...I also have this issue here in Canada on Bell network.... Really hope there is a fix for this. Not being able to use your dialer again for another 15 seconds until the phone decides it is going to hangup is unacceptable. Not sure why the person earlier said its normal for phones to take a few seconds, yeah right..my SG2 hung up immediately! How else is one to win radio contests by spamming the phone lines?
Tonster1983 said:
YES...I also have this issue here in Canada on Bell network.... Really hope there is a fix for this. Not being able to use your dialer again for another 15 seconds until the phone decides it is going to hangup is unacceptable. Not sure why the person earlier said its normal for phones to take a few seconds, yeah right..my SG2 hung up immediately! How else is one to win radio contests by spamming the phone lines?
Click to expand...
Click to collapse
No, I stated earlier that it is common for a few seconds when receiving a busy dial tone. Not every single call you end should take time, most will end instantly. If it's a cell phone, should be right away.
I haven't experienced calling a number and receiving a busy tone to test if mine does this also. Hopefully this is something that gets worked out soon.
same
Smith2001 said:
I have this issue too on three UK. Have to use airplane mode to end the call. Very frustrating.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
By the way I'm on Three as well, However not 100% sure if it netowrk preference. I tried same SIM on my iPhone 4 and the problem DOESN'T happen.
I'm gonna try my Nexus 5 with different network SIM and see if the issue occurs.
Sabrber said:
By the way I'm on Three as well, However not 100% sure if it netowrk preference. I tried same SIM on my iPhone 4 and the problem DOESN'T happen.
I'm gonna try my Nexus 5 with different network SIM and see if the issue occurs.
Click to expand...
Click to collapse
I tried on Virgin UK, didn't get the problem. It was only 5 mins test to few numbers.
So looks like it's rather network issue..
I noticed this because I have an account with a "callback" long distance service. It's designed so that I call a designated number, get an intentional busy signal, and then hang up quickly so they can call me back. Once I answer the callback I dial the number I want to reach.
Well now on my Nexus 5 with KitKat, I hang up, but the callback never reaches me because the device has failed to hang up in actual fact. Instead the callback hits my voicemail.
This is on WIND Mobile Canada which can be a bit of a wonky network, but I am also seeing reports from big North American networks like Bell and AT&T.
I have the same problem. It seems to take about 20 seconds of the busy signal after I have hung up before the call disconnects. Its really annoying.
Related
Is there a way to stop the phone from "notifying" me that my bluetooth headset has been disconnected?
Stock VZW ROM
I second the need for a solution to this! Every time I exit my Acura RL with hands free dialing, I get a message a minute or two later. It's a pain to dismiss it . . . .
Anybody?
I know more than 2 people have to find this annoying...
me too!!! This bugs the crap out of me!
there is already a fix for this... go check this thread
http://forum.xda-developers.com/showthread.php?t=524655
bitslizer said:
there is already a fix for this... go check this thread
http://forum.xda-developers.com/showthread.php?t=524655
Click to expand...
Click to collapse
HOLY CRAP!!!
I don't know how I missed it.
Works great!
brent372 said:
HOLY CRAP!!!
I don't know how I missed it.
Works great!
Click to expand...
Click to collapse
AWESOME.
Thanks!
Just a little fyi, after the first day of applying the fix, this issue started up again.
really? ever since applying the fix the disconnect notification issue never bother me again, there's a seperate fix for BT headset Volume cannot be adjust or something like that too i think
now to fix the annoying cannot hang up with the BT headset.... there's a partial fix for that too, but didn't work for me
Yup. I get the message every morning and every evening when I get in/out of my truck. 4 messages a day. It's getting old.
I'll apply the fix again just for giggles.
I used the hangup fix and it also worked for the first day, then stopped. It was SO nice for the short time that it worked.
The one I wish they would fix is that annoying balloon you get when data coverage gets spotty or you lose data connectivity. There should be a way to turn it off but I can't find one. When roaming, every time I change networks or lose signal for a second a windows balloon pops up to let me know. Some places it can happen hundreds of times a day. Really MS, we don't need to know that bad. No other phone does this. A little notification on the bar like everyone else uses would be fine. A big balloon popping up repeatedly when your trying to use a map or something is beyond annoying.
mdphoenix, mine did the same. worked for a day & then came up with the same errors.
This happen to anyone? This isn't the first time this has happened. Phone doesn't ring, and of course I don't get a missed call. I am in a full reception area so it cant be a loss of signal.
Thanks
Rob
Could you give more specifics? Were your bars green or grey? Were you on a stock rom? Are you rooted?
Sent from my Darkginger CM7 Google Nexus S!
kenvan19 said:
Could you give more specifics? Were your bars green or grey? Were you on a stock rom? Are you rooted?
Sent from my Darkginger CM7 Google Nexus S!
Click to expand...
Click to collapse
Stock everything. green, full signal and on wifi as well.
Sent from my Nexus S using Tapatalk
Me too
I also loose the few calls that I get. first I thought it was because it was on vibrate but then i put it on sound and I was just holding the phone with the home screen showing and it just flashes the incoming call and when i tried to answer it said: missed call in the notification area.
I guess being pure google has its disadvantages.
Phone (sometimes) doesn't ring, goes right to VM...
This past few days, my phone has started to skip ringing and goes right to VM. This has happened 3 times now, I'll be sitting right next to my phone - look down and see that I have a VM - and the phone never rang!
I called the caller(s) back, and they said it only rang 1 time on their end, or not at all - and then went straight to VM for them. The same effect that would happen, if I had my phone off, which wasn't the case in any of the 3 times this occurred.
Just wondered if anyone here has experienced the same thing? This isn't happening on every call that comes in, but has happened 3 times (too many) so far out of the blue this past few days.
cgerdb said:
I also loose the few calls that I get. first I thought it was because it was on vibrate but then i put it on sound and I was just holding the phone with the home screen showing and it just flashes the incoming call and when i tried to answer it said: missed call in the notification area.
I guess being pure google has its disadvantages.
Click to expand...
Click to collapse
I've seen this on my Nexus S as well. I never had any issue like this with my Nexus One. I do wonder if this is an issue within Gingerbread or the Nexus S.
Bmerz said:
This past few days, my phone has started to skip ringing and goes right to VM. This has happened 3 times now, I'll be sitting right next to my phone - look down and see that I have a VM - and the phone never rang!
I called the caller(s) back, and they said it only rang 1 time on their end, or not at all - and then went straight to VM for them. The same effect that would happen, if I had my phone off, which wasn't the case in any of the 3 times this occurred.
Just wondered if anyone here has experienced the same thing? This isn't happening on every call that comes in, but has happened 3 times (too many) so far out of the blue this past few days.
Click to expand...
Click to collapse
You're not alone -this doesn't happen frequently, but when it does it's annoying.
http://forum.xda-developers.com/showthread.php?p=11188474
krohnjw said:
You're not alone -this doesn't happen frequently, but when it does it's annoying.
http://forum.xda-developers.com/showthread.php?p=11188474
Click to expand...
Click to collapse
Oops! Sorry, I did a search here in "General" and this topic didn't come up. I didn't think to search in Q & A, as I thought bugs were all here in General.
My apologies, as I know to ALWAYS do a search before posting. Mod; feel free to merge my thread, if need be - thank you.
are you possibly connected to EDGE when this happens? if so it could just be in an active data transfer which would block ou tht eincoming call to voicemail..
simply weird
robstunner said:
This happen to anyone? This isn't the first time this has happened. Phone doesn't ring, and of course I don't get a missed call. I am in a full reception area so it cant be a loss of signal.
Thanks
Rob
Click to expand...
Click to collapse
i just had that happened to me yesterday.
i can't explain why
and to be worse, it was myself calling myself using another cell phone from another provider, cuz .... i was hoping to easily save the new number into my address book, without having to type everything in.
so i then tried calling myself again the 2nd time, and then it worked.
the SNS was in full bars, good reception, not lagging, responding to screen selection and everything in a speedy manner.
so i have completely no clue, why the first call did not ever reach the phone.
after 4 rings (that never arrived) it send the other phone i was using to the voice mail.
you guys are connected to 3g and not EDGE when this happens right?
RogerPodacter said:
are you possibly connected to EDGE when this happens? if so it could just be in an active data transfer which would block ou tht eincoming call to voicemail..
Click to expand...
Click to collapse
I don't think so, as I rarely drop to EDGE. But I guess it's hard to be 100% certain of this, since my screen isn't on at the time a call comes in.
However, as soon as I see that I have a VM (via No LED), I turn on my screen, and it's not in EDGE - but this is not to say, that perhaps it wasn't in EDGE status a min or 2 before the VM came in. So who knows...
I thought this was GVoice...
I had problems on my Galaxy S, too. I assumed it was GVoice, but since the latest OTA, it seems my network connectivity has become REALLY flaky anyway (disconnecting, dropping to EDGE, complaining there is no SIM card!) - and I didn't even put a custom ROM on there! I think this will be my last Samsung. HTC dual-core, baby.
I am on EDGE all the time because of AT&T provider.
My guess is that Google voice servers are having heavy traffic forwarding to a phone. Not to mention if you have more than one, half would ring and the ones that do just for about 2 rings.
I appreciate Google trying to make it a carrier-like experience but we would not have that experience with VOIP just yet.
RogerPodacter said:
you guys are connected to 3g and not EDGE when this happens right?
Click to expand...
Click to collapse
i'm always on 3G
good signal all around the areas i go to, including basement levels on Pickering, Scarborough, Markham, North York, Vaughan, and Richmond Hill areas, including Mississauga & Brampton
i don't frequent much the core zones like Toronto & Etobicoke, not car friendly
Only on 3g. Happens a decent amount. I've been on wifi this last time as well.
Sent from my Nexus S using Tapatalk
it happened again
this time i had to reboot the phone, shutdown, then turn it back on
after the reboot everything worked
but before the reboot, i was still on 3G, had data access, but all voice calls got a message saying "this customer is currently unreachable, please call back again" or message of that sort, or goes to voice mail
i was unable to make outgoing calls too, i was only able to make outgoing calls after the reboot
good thing it was not an emergency situation
Is only through google voice?
man I really want this phone but I can't miss calls because of my job.
I don't think so
dman777 said:
Is only through google voice?
man I really want this phone but I can't miss calls because of my job.
Click to expand...
Click to collapse
for me it was, regular At&t line on edge. Google voice number to ring on VOIP number on WIFI.
So I don't think is the kind of connection. The Nexus S is too busy to take the calls doing something else???
I had to reboot my phone like 4 times in order for me to get calls.
Not for me. I use Google voice, but really only for it's voicemail
hey,
I bought the nexus s (9023) about two months ago, stock rom, not rooted, and for the last week or two, it started making problems.
about 1-5 times a day, i can't here the other side at all. as if it's on mute. not even the ringing tone, before I'm answered. the only thing that solves it, is to restart the phone.
in other forums i've read that it's a mess, and that i should use my warranty. the problem is i bought the phone abroad, and shipping it should take about 3 weeks.
is it a common issue?
can i solve it alone, mabye by switching to a non-stock rom?
i'll be very happy to read some good news here, but bad news is better than non.
thanks a lot,
tal
p.s, iv'e downloaded system info to monitor the temp, and it doesn't happen necessarily when the phone is hot.
I don't know... I am rooted, I have used 5 different roms since purchasing my phone.
Stock
CM 7
Savaged Zen
Oxygen
Soju
I have also used several kernels
CM Stock
Netarchy
Matrix
James Bond
Trinity
So far, on all roms and kernels I have experienced the same problem. You make a call and it connects, looking at the screen the time counter is going but there is no sound; it will sit there and hold the call for 30-55 seconds then ends call. A quick redial and bam it works. Some people have reported that they answered and there was nothing. I don't know, it's really obnoxious.
The other, more annoying problem is that randomly on calls throughout the day the phone will just reboot itself. Right in the middle of a call. AHHHH like 3-5 times daily!
help, anyone?
i'm stuck with this, and a bit clueless.
Well, somehow I discovered that the problem is related to the bluetooth. as long as it's turned of, nothing will happen, on the other hand, when I use my earphone (most of my conversations happen while driving) i need to restart my phone every 1-2 calls
any ideas?
just u can't hear other one while calling u?
thanks.
so it was in the beginning, but now neither of us can hear the other. no matter who made the call.
and again, only when BT is working.
tal89 said:
so it was in the beginning, but now neither of us can hear the other. no matter who made the call.
and again, only when BT is working.
Click to expand...
Click to collapse
If u can hear him,just press and then unhold it ,then u can hear him.
Sent from my Nexus S using XDA App
it's quite obvious, unfortunately it doesn't work.
cutiyar said:
If u can hear him,just press and then unhold it ,then u can hear him.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
i can't hear, and he can't hear as well.
tal89 said:
i can't hear, and he can't hear as well.
Click to expand...
Click to collapse
hehee its problem ,
am really disappointing with nexus s , but i dont have enough money to buy HTC product again.
any solution?
Hi, did anybody have any solution to this problem?
I live this problem on almost half calls of specific numbers.
I am desparate...
Try setting discoverable timeout to never? Have you tried a different Bluetooth device?
Sent from my Nexus S 4G using xda premium
I have this problem too. This seem to happen on some Kangs and nightly, but not all of them. I can't hear when someone calls me. But when I call someone, I can hear them. I always have Bluetooth off (do not use them).
I live the same problem. No problem for outgoing calls. For incoming calls, I cannot hear caller's voice but they can hear me. It is not for all numbers.
I am on t-mobile and nexus s (cynagenmod nightlies). For all incoming calls from tmobile numbers no problem. But for almost all other carriers, it is just random.
I feel like I started having this problem after updating from CM 7.0.2 to 7.1 RC and thereafter(but not very sure on this).
If anybody still following this topic, I would suggest you to contact samsung if you still have warranty. On the second attempt they sent me a brand new phone with box and accessories.
Sent from my SGH-T989 using XDA
Or, you might give it a try with a different radio for your model:
http://forum.xda-developers.com/showthread.php?t=1116884
If you go this road, make sure you backup your EFS folder.
What i would do is if it is still in warranty just give it back to them and they'll probably give you a new phone. Since you said it takes 3 weeks to ship, just wait for it and use another phone if possible. Its not like your life is going to end. I think the problem is, not every phone is the same so there will be problems especielly when flashing a rom. For example unstable roms might not allow you to use this app or have serious effects on your phone.
Best to give it back to samsung and get a replacement.
Something very weird just started happening with my SamChg.
When I am a few minutes into a phone call (about 3 - 4 minutes), all audio drops out on both sides of the call. The call is still connected, but neither side hears anything anymore.
I did a factory reset on the phone, but it didn't make a difference.
What can be causing this? If I can't use my smartphone as a phone, I'm screwed!
are you running any special ROM or anything because its happening to me as well
I have been having the same problem for almost a month now. I was rooted when this started happening. I went back stock still happened. New 4g card still happened. Another phone still happened. I have been getting the runaround from verizon the whole time they have no clue what is going on.
On a side note asked a friend that works at a little vzw store if they have seen this problem and sure enough she had. She told me that they had a customer go through 4 phones and she started making calls and was told by Customer Support that it was a known thing and there was a software update coming out for that.
After hearing this I called good ole *611 yet again and they were clueless and said they knew nothing about it. *sigh*
¿GotJazz? said:
Something very weird just started happening with my SamChg.
When I am a few minutes into a phone call (about 3 - 4 minutes), all audio drops out on both sides of the call. The call is still connected, but neither side hears anything anymore.
I did a factory reset on the phone, but it didn't make a difference.
What can be causing this? If I can't use my smartphone as a phone, I'm screwed!
Click to expand...
Click to collapse
What rom ???
Yorto said:
What rom ???
Click to expand...
Click to collapse
Umm can't even remember now was a month ago LOL. But my 2nd phone I didn't put one app on or anything left it bone stock and still had the same problem. Same as the customer my friend had they would mess up right out of the box.
probably weak antenna
no you don't lose signal call keeps running you lose Audio.
chiahead52 said:
are you running any special ROM or anything because its happening to me as well
Click to expand...
Click to collapse
Yorto said:
What rom ???
Click to expand...
Click to collapse
Yes, I am running a custom ROM, but it's basically a stock rooted & voodoo'd EE4 ROM (by danalo1979, I think). It's got all the yucky poo-brown colors and all the bloatware.
Same issue here. I'm running completely stock right now, non-rooted. Sometimes the audio will drop at the onset of placing a call (I won't even hear ringing) and sometimes it will happen a few minutes into a call. Other parties do say they can hear me though.
Personally, I've noticed that this problem only happens when I am also connected to a Wireless Network. If I'm running 4G/3G, sometimes I hear echos of my voice, but the audio won't drop out.
Weird, but glad to know others are having this issue and that VZW is aware it's happening.
What should we do? Personally, I'd like to wait for the SG2 to arrive before I start complaining. My plan would be to basically flip out explaining that I need my phone to work like a phone, etc. Then flip out that I paid for 4G and my decision was battery based (so I don't get stuck with a Thunderbolt). I bet I could talk my way into a new SG2 over this... Just saying.
KarateExplosion6 said:
Weird, but glad to know others are having this issue and that VZW is aware it's happening.
Click to expand...
Click to collapse
Well they do not tell me they know what is wrong they tell me they have no clue. I even explained to them somebody there does know as they have explained the issue to someone else that has had the problem but I still get they you just need another phone speel.
I don't have this problem watch as soon as I try to make a call the audio drops...
Sent from my Droid Charge running GummyFroyo 1.9.1
kvswim said:
I don't have this problem watch as soon as I try to make a call the audio drops...
Sent from my Droid Charge running GummyFroyo 1.9.1
Click to expand...
Click to collapse
same, don't have this problem but i probably just jinxed it.
I've had this happen a couple times too...hard to pinpoint consistency. The other thing I've encountered more than once, is that my mic seems to go off mid-conversation, e.g. I can still hear the person on the other end very clearly, but they can't hear me. Anyone else experience this?
Edvard_Greig said:
I've had this happen a couple times too...hard to pinpoint consistency. The other thing I've encountered more than once, is that my mic seems to go off mid-conversation, e.g. I can still hear the person on the other end very clearly, but they can't hear me. Anyone else experience this?
Click to expand...
Click to collapse
I've experienced that. But I'm not so sure I'm not just covering the mic with my finger.
I was on nluetooth, with the phone in the cupholder... Don't think my finger was involved.
Sent from my SCH-I510 using XDA App
Well 2nd Fru and as I told them it would. It does the same thing. Bone stock. *sigh*
One thing that seems odd to me is that I seem to see this problem more when calling another mobile phone vs. a landline.
Maybe it's just my imagination, but I always see problems when calling my wife's mobile phone. Last night, I called a landline for over an hour without any problem.
same here I can talk to customer service for 1hr+ but mobile to mobile most Ican get is maybe 15 min.
I drive around as part of my job and today I tested a call out to my wife who has a charge as well and we were able to talk for over 20 minutes with no issues. That same area I drove through a few days ago caused 3-4 drops in audio before. So in my opinion its a network related issue and hopefully its get fixed 100% cause most of us need our phones to work solidly
To the people losing audio during their calls, can you post your location?
The reason why I ask this is because on the Verizon forums there is an eight page post about this issue. Seems like a lot of people in Arizona are experiencing this. I'm in Chandler, Az and have this issue, especially when calling other VZW people in AZ.
Can't post links yet but check the VZW community forum for the Charge.
Hi guys
I just got new u11 from sprint. I was very excited about this phone until I started to notice that the phone goes on mute while I'm on a call. The mute icon is not pressed. I usually click it to activate then deactivate it and it brings it back. Sometimes I hit that and speakerphone until the caller can hear me again. It's pretty frustrating. I searched online and it appears to affect many phones with 7.1.1, so I'm not sure if replacing the phone will cure this issue. I'm still within my exchange period but wanted to check with the community if there's a solution to this annoyance. It looks like it's affecting many phones and the users are pretty pissed off about it. Is there a fix from either sprint / HTC or Google ? Any advice is appreciated!
Yaboc
yaboc said:
Hi guys
I just got new u11 from sprint. I was very excited about this phone until I started to notice that the phone goes on mute while I'm on a call. The mute icon is not pressed. I usually click it to activate then deactivate it and it brings it back. Sometimes I hit that and speakerphone until the caller can hear me again. It's pretty frustrating. I searched online and it appears to affect many phones with 7.1.1, so I'm not sure if replacing the phone will cure this issue. I'm still within my exchange period but wanted to check with the community if there's a solution to this annoyance. It looks like it's affecting many phones and the users are pretty pissed off about it. Is there a fix from either sprint / HTC or Google ? Any advice is appreciated!
Yaboc
Click to expand...
Click to collapse
I suggest a factory reset first...since you just got the phone, you shouldn't have much to lose (and as a XDA user, you really have no reason not to be backed up somewhere....).
My second suggestion is to bring it to Sprint and let them fix/repair it, especially since you are within the return period.
AarSyl said:
I suggest a factory reset first...since you just got the phone, you shouldn't have much to lose (and as a XDA user, you really have no reason not to be backed up somewhere....).
My second suggestion is to bring it to Sprint and let them fix/repair it, especially since you are within the return period.
Click to expand...
Click to collapse
Hi I did the factory reset without restoring any apps settings and the problem remains where during the call it goes on mute in and out. I called sprint and requested a new phone since this is either a hardware problem or bad sprint rom flash from factory. I went with a new phone route since I didn't want to waste the 14 day return/replacement period. Hopefully the new unit will work as expected out of the box. It's funny that a lot of people seem to have this issue on different brands.
AarSyl said:
I suggest a factory reset first...since you just got the phone, you shouldn't have much to lose (and as a XDA user, you really have no reason not to be backed up somewhere....).
My second suggestion is to bring it to Sprint and let them fix/repair it, especially since you are within the return period.
Click to expand...
Click to collapse
yaboc said:
Hi I did the factory reset without restoring any apps settings and the problem remains where during the call it goes on mute in and out. I called sprint and requested a new phone since this is either a hardware problem or bad sprint rom flash from factory. I went with a new phone route since I didn't want to waste the 14 day return/replacement period. Hopefully the new unit will work as expected out of the box. It's funny that a lot of people seem to have this issue on different brands.
Click to expand...
Click to collapse
Nothing to do with HTC and/or Sprint specifically. It seams to be a new feature if Android and is bound to the OS version 7.1.1 and upwards. OEMs can't do anything about it. Got it as well on my unit, bit when I activate knock on feature when in call it still does work as on previous versions, thus I don't care about the automatic DND during call in any way.
Sent from my htc_pmeuhl using XDA Labs
5m4r7ph0n36uru said:
Nothing to do with HTC and/or Sprint specifically. It seams to be a new feature if Android and is bound to the OS version 7.1.1 and upwards. OEMs can't do anything about it. Got it as well on my unit, bit when I activate knock on feature when in call it still does work as on previous versions, thus I don't care about the automatic DND during call in any way.
Click to expand...
Click to collapse
What knock on feature are you talking about.
yaboc said:
What knock on feature are you talking about.
Click to expand...
Click to collapse
You can activate a knock feature for a second incoming call when talking on the line already. Sorry the knock on should try to describe this one.
Sent from my htc_pmeuhl using XDA Labs
5m4r7ph0n36uru said:
You can activate a knock feature for a second incoming call when talking on the line already. Sorry the knock on should try to describe this one.
Sent from my htc_pmeuhl using XDA Labs
Click to expand...
Click to collapse
im still not sure what you mean by knoc on feature. I will search the forum but this has nothing to do with another incoming phone call. i'm having in and out sound issues with the first call that's coming in.
yaboc said:
im still not sure what you mean by knoc on feature. I will search the forum but this has nothing to do with another incoming phone call. i'm having in and out sound issues with the first call that's coming in.
Click to expand...
Click to collapse
You guys are talking about 2 different things.
One is micrpohone mute in call (seems like a bug) and the other one is DND mode while in call (seems like a feature).
I don't experience the behaviour you experience with calls on European model.
velimirchek said:
You guys are talking about 2 different things.
One is micrpohone mute in call (seems like a bug) and the other one is DND mode while in call (seems like a feature).
I don't experience the behaviour you experience with calls on European model.
Click to expand...
Click to collapse
yes it's DND while on call, but it's not pressed/activated. i'm getting new phone anyways and will see if the issue persists. it's very annoying and not a good first experience with U11. i'm not sure if this is a software or hardware bug but this shouldn't be happening with a new device out of the box.
yaboc said:
yes it's DND while on call, but it's not pressed/activated. i'm getting new phone anyways and will see if the issue persists. it's very annoying and not a good first experience with U11. i'm not sure if this is a software or hardware bug but this shouldn't be happening with a new device out of the box.
Click to expand...
Click to collapse
So what is it then?
1. DND while on call? It's nornal, you got your answer and new phone will act the same. It's not a bug.
2. Microphone goes on mute automatically and caller can not hear you? That's what you said in first post. It might be a bug.
velimirchek said:
So what is it then?
1. DND while on call? It's nornal, you got your answer and new phone will act the same. It's not a bug.
2. Microphone goes on mute automatically and caller can not hear you? That's what you said in first post. It might be a bug.
Click to expand...
Click to collapse
I receive a call and after some time ( varies from few seconds to a min) the caller can't hear me. I put them on speakerphone they can hear me. Switch speakerphone off they can hear me again via normal call. It's ****ing frustrating. It's happening with a new replacement phone from sprint. I'm thinking about giving up on this u11 and getting galaxy. Its unlikely that it's a hardware issue on two new phones twice in a row
I have this same issue I also have several people tell me that they've called me several times yeah I have no missed calls I also have a strange text messages from the number 9479 and their blank
yaboc said:
I receive a call and after some time ( varies from few seconds to a min) the caller can't hear me. I put them on speakerphone they can hear me. Switch speakerphone off they can hear me again via normal call. It's ****ing frustrating. It's happening with a new replacement phone from sprint. I'm thinking about giving up on this u11 and getting galaxy. Its unlikely that it's a hardware issue on two new phones twice in a row
Click to expand...
Click to collapse
Hi Yaboc,
John here in Ireland and I'm having the same issue with my European HTC U11 and I feel your pain. I've been doing some Googling on the issue and have seen that (on previous HTC models anyway) it may be if you have Bluetooth on, the phone tries to connect to devices to pass the audio through and this is what causes the muting of the call. Do you have bluetooth switched on when the problem occurs? I have Bluetooth permenantly on for connecting to my Moto 360 watch so will try when I get home from work today to see if the problem still occurs if I switch Bluetooth off.
I'll be sure to let you know how I get it and just thought I'd share with you what I've read elsewhere online.
Here's the article I was on about earlier:
https://thedroidguy.com/2015/08/how...-cannot-be-heard-other-related-issues-1047469