Related
Edit: please see this Google issue tracker post and star it to get Google's attention!
http://code.google.com/p/android/issues/detail?id=24019
I've had it happen 3 times now that I'll be on a call for a number of minutes and all of a sudden the person I'm talking to won't hear me any more. To be fair, I've been talking to the same person, and each time it's been an extended call (5+ minutes). It happened on Saturday, twice. Since then, I have wiped data/cache and flashed a custom rom. It happened again this evening, right around 10 minutes into the call.
The microphone doesn't come back. I tried turning on speaker phone and muting/unmuting my mic, but it won't bring the microphone back. Like I said, this is the same person I've spoken to each time, however, I've been speaking with them often (with their current phone) on my previous phone and never had this issue, so I'm not sure if it's their phone's problem. I spoke with someone else for 30+ minutes on Sunday and didn't have this happen.
To remedy the situation, I just hang up and call back and it works fine, until it happens again.
I'm confused. Is my phone problematic or is it a software bug or is it the other person's phone? Is anyone else experiencing this?
EDIT: Just thought I'd mention I'm on VZW LTE/CDMA.
Thought I was the only one with this problem. Had the exact same thing happen to me talking with my girlfriend the past two nights. Think I'm going to blow away everything and go back to stock 4.0.2. I think it's an app that's misbehaving.
Please report back with your findings.
I've had the same thing happen to me. It has happened the most often when talking to my gf who has an iphone 4 on ATT, but it also happened when I was trying to make dinner reservations at a restaurant that was using a landline.
I am running stock 4.0.2.
If anyone has any suggestions, I'm all ears.
This was a common problem on the Samsung Droid Charge, which uses the same questionable Via baseband modem for voice calls. The earlier Charge Froyo firmware had all kinds of voice issues: 1) outgoing voice drop. 2) systematic cut in/out. 3) garbled robot voice quality. 4) loud ear hurting static. Since the latest Charge firmware EP4 (gingerbread), all issues except occasional robot voice are fixed. The phone is now usable where it was laughable before. The loud static may have been linked to certain phones / hardware rather than firmware.
Hopefully Samsung can incorporate the Charge fixes into the Nexus.
Hopefully Samsung stops using 3rd rate Via chips.
Thanks for the input. Nice to have an idea of what's going on.
Sent from my Galaxy Nexus using Tapatalk
Hey I have this happen about once a day sometimes more and doesnt matter who im talking to it can happen to anyone at anytime. This is very annoying seems like the smarter and more advance these phones get the crappier the actual phone call part of it gets. I think they forget cell phones primarily are for phone calls
Ironically 2 of my calls today complained i was dropping out. But i had full signal. My phone is brand new so these are the only calls ive really made so far.
Reply I had the same thing happening to mine. I was actually on the phone with VZW Level 2 Tech support when the mic went dead. It happened twice while talking to the same agent. She said it sounded like a clicking noise on her end. She then told me to take the phone back to the store.
I went in and got it swapped for a new one and had to return that one the same day because the ear piece sounded blown. Now on my 3rd Galaxy Nexus. The mic issue hasn't happened yet but I just got this one yesterday.... I'll report back if it happens again.
Sent from my Galaxy Nexus using xda premium
I don't think this is a hardware problem. I've had this happen on all three GNs I've had. This last time I was talking on my jawbone headset. I tried switching to the phone mike and speaker phone it did not make a difference. I also tried muting and unmuting. How do we get Samsung to acknowledge this problem?
This happened to me a couple of times also, stock 4.0.2
I have the same problem on stock 4.0.2 and on RevolutionHD 2.1.2. I spent an hour or so with level 2 tech support. I was told that I was the only person to report this issue. They suggested that I change it out or switch to a different phone. My Son-in-Law has the Nexus as well and also has the same issue. I guess I have till 1/15/2012 to make up my mind.
I am having the exact same issues. I will say it lasts about 3-5mins in the call then no one can hear me, and I have to call the people back. I love my Nexus!! I am so glad that I am not the only one having this issue. Edit: I have gone on the VZW Tech Forums and informed them of my problem, and pointed to this thread. I am hoping I hear something from VZW. Maybe if we can get more people to post on the thread over there, VZW and Samsung will see there is a problem. Heres the link h t t p ://community.vzw.com/t5/4G-Discussion/No-One-Can-Hear-Me-After-3-5mins/td-p/762556 (sorry had to space the http part since I am new.
I've had this issue too. Sounds like a resonably easy thing to fix with software.
Sent from my Xoom using xda premium
Has anybody had this happen on 4.0.3? How about on the GSM GNex? Just trying to narrow it down.
Exact same problem here. I called Verizon and they sent out a new one. But after a few calls longer than 5 minutes the microphone went out and I had to call back. I reused the same SIM card. Could that be a potential solution?
Sent from my Galaxy Nexus using Tapatalk
I made tons of test calls today and not a single issue on my GSM version. I only experienced this cut out issue the first day so guess I'm good for now...
I've had this happen on me twice running a 4.03 Custom Rom. Happened about 15 minutes into each call
I believe it to be hardware.
Why do you think its hardware?
Sent from my Galaxy Nexus using Tapatalk
Been on the forums for awhile now... never really posted anything more or less just read and take advice from the plenty haha. This time around, I actually could use a hand.
I've been having ongoing issues with my T989D with either the radio or the modem I can't really determine, but what seems to be happening is periodically when I'm on the call with someone they claim I cut in and out or the line fades out. I'm beyond boggled what could be the issue and more or less have tried everything and anything ?!?
1) As for another post I tested the microphone with the recorder app and it works 100%.
2) I'm currently running TLLE4 on Telus 4.0.3 stock from ODIN
3) My signal strength on HSPA is always around -69dbm to -82dbm so I can't determine if it's somehow network issues?
4) I'm from Toronto, ON and on virgin mobile if that helps at all...
5) I've reverted to stock numerous times / custom and still people say I cut in and out.
6) Almost down to my last resort and send the phone in for repairs if anyone out there believes I have a lemon
Any help would be I would be beyond grateful.
Thanks XDA
Tlle4 radio?
Sent from my SGH-T989D using XDA
Would definitely want to confirm the radio/modem there. There have been some issues with some ROM's and bad voice quality, but that doesn't sound like it should be the case with you since you have reverted to stock and still have it.
In the event you have to bring the phone back for repair then you should flash the counter discussed in this thread:
http://forum.xda-developers.com/showthread.php?t=1578184
The modified telus radio can be found in this thread courtesy of thederekjay
http://forum.xda-developers.com/showthread.php?t=1703045
The unmodified is here courtesy of Mr X
http://forum.xda-developers.com/showpost.php?p=27117457&postcount=103
:S
Yes sorry im on TLLE4 on Telus 4.0.3 stock from ODIN.
I've reverted back the counter already incase. Im just utterly confused why every call seems to cut in and out ?!?
I'll try to be succinct here. I got a replacement Nexus from Asurion when my screen cracked earlier this month. Incidentally, this was also around the time I started flashing Jelly Bean ROMs rather consistently. I have been experiencing (what I would actually refer to as) a crippling issue where my phone's signal will just completely drop. As in, no calls, no texts, no anything. Mobile network connection is gone. And while it does do it in my apartment, which has shoddy reception in the first place, it's doing it just as much when I'm in the middle of Best Buy, or a bar, or anywhere with FULL 4G. It will simply go from 4 bars to no service and then back to 4G (once the radio presumably cycles).
Do you guys think this is a hardware issue or a Jelly Bean issue? I've run two different ROMs overall (Jelly Belly and PARANOIDANDROID), so I've hit both the CM10 and non-CM10 ends of the spectrum and they're both doing it, so that leads me to believe that it's not a specific ROM issue, but either an overall Jelly Bean issue or a hardware malfunction. Any advice would be greatly appreciated. Thanks in advance.
enigmaisdead said:
I'll try to be succinct here. I got a replacement Nexus from Asurion when my screen cracked earlier this month. Incidentally, this was also around the time I started flashing Jelly Bean ROMs rather consistently. I have been experiencing (what I would actually refer to as) a crippling issue where my phone's signal will just completely drop. As in, no calls, no texts, no anything. Mobile network connection is gone. And while it does do it in my apartment, which has shoddy reception in the first place, it's doing it just as much when I'm in the middle of Best Buy, or a bar, or anywhere with FULL 4G. It will simply go from 4 bars to no service and then back to 4G (once the radio presumably cycles).
Do you guys think this is a hardware issue or a Jelly Bean issue? I've run two different ROMs overall (Jelly Belly and PARANOIDANDROID), so I've hit both the CM10 and non-CM10 ends of the spectrum and they're both doing it, so that leads me to believe that it's not a specific ROM issue, but either an overall Jelly Bean issue or a hardware malfunction. Any advice would be greatly appreciated. Thanks in advance.
Click to expand...
Click to collapse
I have the same issue with my phone. I have actually gotten 3 new phones only to have them all do the same thing. I flashed to Jelly Bean hoping it would fix the issue but no luck.
Sounds like a hardware issue. I have flashed many roms, ICS and JB and all are good for reception. Once we got new radios 5 months ago it fixed my 3g to 4g handoffs when I would lose data for minutes if not an hour. All good now.
It's common issue for Google nexus. I am also having same problem. You may ask a replacement or switch network mode to "CDMA only" instead of "LTE/CDMA".
Sent from my Galaxy Nexus using Tapatalk 2
It happens to my Galaxy Nexus too. >_<
Happens to me too. From HSPA (which should bei constant high-quality in my area) down to 2G, and if I am in areas with bad coverage, it looses signal completely.
Finally, after several ROMs, and basebands haven't fixed it, I'm going to send it in, as soon as possible now.
Sent from my Galaxy Nexus using xda app-developers app
This is a hardware issue. I515.10 is the one I have and it does this as well, the I515.9 however does not seem to be affected. The .10 was made in china and the .9 in korea... or maybe the other way around, hell who cares... Bottom line is, its a huge issue that samsung should have addressed long ago.
For more info check out the samsung forums. I'm waiting on a replacement to come Monday.
Sent from my VS910 4G using xda app-developers app
Same thing
This is happening on mine too. I installed the stock rom on my Verizon GNex and the signal has deteriorated significantly, almost like 4.0.2
I'm hoping a fix, or the new binaries fix this issues and put it back to it's 4.0.4 state.
I am still plagued by this. Anybody know of any fixes in the works? I have exchanged my phone 4 times to no avail.
Crandolph2001 said:
I am still plagued by this. Anybody know of any fixes in the works? I have exchanged my phone 4 times to no avail.
Click to expand...
Click to collapse
It's an issue with a certain batch of phones. All the ones I had that had issues were either manufactured in January or February (says 12.01 or 12.02 under the battery). I was finally able to get a new replacement at a Verizon store thanks to knowing the manager and it was just manufactured in July (12.07) and has worked like a charm (except a single stuck pixel in the upper right-hand corner, but I don't see it unless I'm looking for it, so I'll deal).
enigmaisdead said:
It's an issue with a certain batch of phones. All the ones I had that had issues were either manufactured in January or February (says 12.01 or 12.02 under the battery). I was finally able to get a new replacement at a Verizon store thanks to knowing the manager and it was just manufactured in July (12.07) and has worked like a charm (except a single stuck pixel in the upper right-hand corner, but I don't see it unless I'm looking for it, so I'll deal).
Click to expand...
Click to collapse
My current phone says it was manufactured 7/11/12 in China. I thought it was going to behave at first but the problem showed it's ugly head several days later.
Crandolph2001 said:
My current phone says it was manufactured 7/11/12 in China. I thought it was going to behave at first but the problem showed it's ugly head several days later.
Click to expand...
Click to collapse
That's strange. In my experience, it should either be screwed up totally or not at all. It shouldn't gradually onset. You sure it's not a ROM and/or radio issue this time that's just exhibiting similar symptoms?
enigmaisdead said:
That's strange. In my experience, it should either be screwed up totally or not at all. It shouldn't gradually onset. You sure it's not a ROM and/or radio issue this time that's just exhibiting similar symptoms?
Click to expand...
Click to collapse
When it started acting up I hadn't rooted / romed yet. I am now rooted and have flashed to 4 different roms and every single one of them still had the issue. I may have had the issue on the first couple days and not noticed it for whatever reason...
I bought this phone on sale at WalMart about 3 weeks ago to replace my HTC Mytouch 4G, which has been a great phone but I thought it was time for an upgrade. So far I'm not too impressed, and several times I've had an issue when I make a call that no one can hear anything. It shows it's dialing, then connected and I hear nothing. If I call back it usually will remedy itself, but not always. The other day I called my sister back after the first time of no audio, and I could hear her but she could not hear me.
This has happened about 5 to 7 times in the last 3 weeks, but it's unacceptable to me. I don't want to root the phone and run a custom ROM at this time since the phone still has a warranty, but I have a feeling it's the software, not a hardware problem. Is it a known problem with 4.04?
Also, the voice recognition on this thing is terrible! I drive a truck for a living and use my Plantronics Voyager Pro exclusively, and I have to use voice command or take my eyes off the road. I can't get this thing to recognize half of what I ask it to do. My HTC was pretty good at that, too!
I really had some expectations with this phone, and it is a nice one in many respects, but it's faults are driving me crazy!
WarrenEC said:
I bought this phone on sale at WalMart about 3 weeks ago to replace my HTC Mytouch 4G, which has been a great phone but I thought it was time for an upgrade. So far I'm not too impressed, and several times I've had an issue when I make a call that no one can hear anything. It shows it's dialing, then connected and I hear nothing. If I call back it usually will remedy itself, but not always. The other day I called my sister back after the first time of no audio, and I could hear her but she could not hear me.
This has happened about 5 to 7 times in the last 3 weeks, but it's unacceptable to me. I don't want to root the phone and run a custom ROM at this time since the phone still has a warranty, but I have a feeling it's the software, not a hardware problem. Is it a known problem with 4.04?
Also, the voice recognition on this thing is terrible! I drive a truck for a living and use my Plantronics Voyager Pro exclusively, and I have to use voice command or take my eyes off the road. I can't get this thing to recognize half of what I ask it to do. My HTC was pretty good at that, too!
I really had some expectations with this phone, and it is a nice one in many respects, but it's faults are driving me crazy!
Click to expand...
Click to collapse
Why didn't u get the s3?
Anyways, there shouldn't be any calling issues. T989 is a pretty popular phone and wouldn't be if it did not successfully make calls imho. As for voice recognition... guess HTC is better for your voice? Again mine works fine. Idk... this phone is pretty baddass
Sent from my SGH-T989 using xda app-developers app
bzlik88 said:
Why didn't u get the s3?
Anyways, there shouldn't be any calling issues. T989 is a pretty popular phone and wouldn't be if it did not successfully make calls imho. As for voice recognition... guess HTC is better for your voice? Again mine works fine. Idk... this phone is pretty baddass
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
The SII was $299 on sale, the SIII was about $699 without contract....
Having the same problem also with the call connected, but can't hear anything.
kruang said:
Having the same problem also with the call connected, but can't hear anything.
Click to expand...
Click to collapse
I knew I wasn't alone!
This happens to me sometimes actually, but it only happens when I am connected to WIFI calling. Does not happen when on the network.
Its possible that your losing a 4G connection or its a weak signal when you answer the call?
Either way, when it happens to me, I battery pull and then it works again.
ITALIANNYC said:
This happens to me sometimes actually, but it only happens when I am connected to WIFI calling. Does not happen when on the network.
Its possible that your losing a 4G connection or its a weak signal when you answer the call?
Either way, when it happens to me, I battery pull and then it works again.
Click to expand...
Click to collapse
I was thinking of the WiFi calling may cause the connection issue before, so I only turn on WiFi connection at home, but didn't help. Also, it only happens after update to ICS. It happens randomly quite often and I have to use apps (i.e. Tango, Line, etc.) to make call instead. I was outdoor with full signal and 4G.
Too lazy to pull battery because of the protective case. Reboot wouldn't help either
My family has two galaxy s2 and blaze phones and all experience same issues. And that to with no WiFi and in DFW metroplex. It looks like Samsung and T-mobile issue to me because I don't see any ATT side complaint on this.
Sent from my SGH-T989 using xda app-developers app
My girlfriend and I both began having these issues with the 4.0.4 update, and never before that. It's awful, because it's so sporadic.
Edit: I never use wifi calling, and it happens both when connected to wifi and when far away from wifi, with it on and off.
Sent from my SGH-T989 using xda premium
I've seen multiple people with this issue in some of the custom rom threads. This didn't happen to me on 4.03, but it does on 4.04 based roms. It seems to happen with or without wifi calling.
Sent from my SGH-T989 using xda premium
ditto
I been having the same problems. stock or multiple custom ROMs. wifi-calling or no.
thought it was the wifi calling function at first, but verified that even on tmo signal and my family been having the same problems...
I've heard of people calling TMobile for support but leads to nowhere. I'ma try calling too and see what i can find out. will post with any news.
And here I was thinking it was a Rom issue. I have literally installed every Rom this morning and tested to see if the issue remained. It has happened with every one of the Roms which led me to think it was a HW issue. It seems to happen more often when my signal is weak. I have tried all the of the Radios too. Im not sure when the issue started but its very consistent with my phone. I have to try 7-8 times EVERY call to finally talk to the person. I normally just switch to my work phone or send a text.
Same problem, on both stock and custom. Must be a t-mobile thing.
So what do we do? Should we all call T-Mobile? Maybe if enough of us call, they will actually look into it.
WarrenEC said:
The SII was $299 on sale, the SIII was about $699 without contract....
Click to expand...
Click to collapse
I also just made the identical decision (also choosing the SII over the Nexus 4 16GB—call me crazy). I seriously hope I don't have this problem... Setting up the phone now.
Most likely T-Mobile won't help. It's weird though that this only happened on the GS II. The GS I and GNex don't have this problem...
Me and my mom have this phone she is stock but we both have had this same issue lately and its been on 4.0.4 has anyone tried another radio to see if that's it? Maybe the new uvli1 will be better
Sent from my Infamous Jedi
I sign in only to tell how I fix my problem with calling I root and flash Jedi Mind Trick ROM for T-Mobile Galaxy S2 SGH-T989! [X1] and RADIO SGH-T989 UVLE1 (T-Mobile) 4.0.3 . The problem is fix after a few nights no sleep and a lot flashing
style154 said:
Me and my mom have this phone she is stock but we both have had this same issue lately and its been on 4.0.4 has anyone tried another radio to see if that's it? Maybe the new uvli1 will be better
Sent from my Infamous Jedi
Click to expand...
Click to collapse
I've tried all available radios except uvli1. I don't think it's a radio issue. I'm pretty sure it's 4.0.4. I've tried a few 4.0.3 roms and they seem fine so far.
---------- Post added at 09:03 AM ---------- Previous post was at 08:34 AM ----------
Do you have a link to uvli1? I'd like to rule it out
edgie13 said:
I've tried all available radios except uvli1. I don't think it's a radio issue. I'm pretty sure it's 4.0.4. I've tried a few 4.0.3 roms and they seem fine so far.
---------- Post added at 09:03 AM ---------- Previous post was at 08:34 AM ----------
Do you have a link to uvli1? I'd like to rule it out
Click to expand...
Click to collapse
Hmm wonder what it could be no its not out yet. Rushaoz is extracting it from his phone maybe we should ask him if he has had issues because Tmobile said they won't release the uvli1 update it will only come on new phones I feel somewhat cheated
Sent from my Infamous Jedi
I'm wondering if this is a ROM problem or problem with my local Verizon service.
I'm getting very frequent dropped calls. In the Seattle area we have 4g service, I'm running AOKP Toro jb milestone 1.
Service drops to 0 bars, then after several seconds, comes back. Generally to show 3 bars of 4G service.
I was contemplating going back to stock to see if the problem is the same. But I thought I'd post here first to see if it may be a ROM problem.
Any ideas?
Thanks, RWM
I would use the new radios FG02. This might help. Helps with spotty transitions of 4G lte to 3G.
Sent from my Galaxy Nexus using xda premium
Mods please move this thread to general
If 4g drops to no signal and then comes back it could be hardware related. If you have the latest radios on your phone and this still happens you may need to get a replacement phone. If you take it to Verizon they'll probably try to swap the SIM first.
To return to Verizon do you think I should go back to stock first?
Sent from my Xoom using xda premium
elcap373 said:
To return to Verizon do you think I should go back to stock first?
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
I would to be safe. If you're returning it, use the factory image and relock the bootloader.
I've had this issue too but only on AOKP milestone 1...dunno what it is. I've noticed when it happens "system ui" fails which has also happened when using the phone.
I haven't dropped any calls, but I get data drops every now and then.
Sent from my Galaxy Nexus using xda premium
I have this same issue, it only happens when I have good signal, when my signal is weak it's fine, it's only when I have strong signal or 4g, I assume it's a hardware issue at least for myself, because I haven't noticed a difference with different roms
elcap373 said:
I'm wondering if this is a ROM problem or problem with my local Verizon service.
I'm getting very frequent dropped calls. In the Seattle area we have 4g service, I'm running AOKP Toro jb milestone 1.
Service drops to 0 bars, then after several seconds, comes back. Generally to show 3 bars of 4G service.
I was contemplating going back to stock to see if the problem is the same. But I thought I'd post here first to see if it may be a ROM problem.
Any ideas?
Thanks, RWM
Click to expand...
Click to collapse
Welcome to the Android Community. For sure you will find the answer to all your questions regarding android in these forums. With that said, make you read before you post. It makes you look like a noob and rightly so. This is for the Development Contribution alone. This should have been posted in the Q&A or General forum.. BTW your device is deffective- return it until you get a good one. It took me 5 times. Talk to Tech Support Level 2 when you call Verizon no one else.
Hey was wondering if you ever figured out this issue, im having the same problems only mine drops the call every 30 exactly. If i use the phone for say 28 minutes then the next call will drop in 2 min to finish out the original 30. I have been having this problem for awhile but was never this predictable, gone through many different radios, roms, eery did a factory wipe with a full wipe of everything and reinstalled xenonHD rom build number JOP40G. Please any help would be awesome. Thanks Also in the seattle area.
mverzal said:
Hey was wondering if you ever figured out this issue, im having the same problems only mine drops the call every 30 exactly. If i use the phone for say 28 minutes then the next call will drop in 2 min to finish out the original 30. I have been having this problem for awhile but was never this predictable, gone through many different radios, roms, eery did a factory wipe with a full wipe of everything and reinstalled xenonHD rom build number JOP40G. Please any help would be awesome. Thanks Also in the seattle area.
Click to expand...
Click to collapse
Hi, I am running AOKP JB 4.2 milestone 2 on my Galaxy Nexus and experiencing the same problem. My calls dropped after some time between 5 an 30 minutes with "Out of area service" alert. I am from the Czech Republic using Vodafone. I tried getRIL to install matching RIL (baseband i9250XXKK1), but this did not help. Before this I was running old AOKP ICS 4.0 without any problem. Does anyone have an idea, how to solve this problem?
Thank you very much.
hubik.tomas said:
Hi, I am running AOKP JB 4.2 milestone 2 on my Galaxy Nexus and experiencing the same problem. My calls dropped after some time between 5 an 30 minutes with "Out of area service" alert. I am from the Czech Republic using Vodafone. I tried getRIL to install matching RIL (baseband i9250XXKK1), but this did not help. Before this I was running old AOKP ICS 4.0 without any problem. Does anyone have an idea, how to solve this problem?
Thank you very much.
Click to expand...
Click to collapse
SOLUTION: I finally found out a solution for my problem. I reflashed radio firmware to the new version (i9250XXLJ1) and installed matching RIL using GetRIL. Now everything works without any problem.