Noticed within a few hours after rooting, my mic was not working. Callers could not hear me. This occurs for both regular calls and Hangouts calls. This dosen't seem to be a hardware issue as the mic works for google voice assistant. Seems to occur out of the blue, and so far ive been messing with settings and somehow the mic began working again, but the issue repeated itself later yet again.
Has anyone else had a similar issue?
Looks like im a loner with this issue. This may still be a HW issue. Might swap and get a new phone while i still can and see if the issue persists.
I have a river_amz I just obtained, waiting for sis to come over and get the FRP thing sorted. I'm going to be rooting immediately after unlocking bootloader. I will post here and let you know if I experience the same thing.
Have you found out anything since your last post regarding this btw?
No. It's been solidly working all day yesterday. Trying to make it fail again.
My only hope is its not a intermittent HW issue that will pop up bigtime after my return window expires.
smokinu said:
No. It's been solidly working all day yesterday. Trying to make it fail again.
My only hope is its not a intermittent HW issue that will pop up bigtime after my return window expires.
Click to expand...
Click to collapse
So far, I've not experienced the issue on a rooted river_amz on 16_7.
Mic on MOTO G7 not working
I'm having an issue like this, but my mic just does not work at all. I'm pretty sure this one is a hardware issue because the only way I can talk to people is plugging in headphones. Do you have the regular G7, or the play/power/plus?
Related
Hi guys,
I've got a weird issue that seems to be happening only with my girlfriend when she calls me and/or I call her, but mostly when she calls me. Sometimes she will call me and I pick up and I can hear her but she can't hear me. It seems to be only her that is experiencing this, and I'm not hitting the mute key or putting her on hold accidentally or anything of the sort... if I call her back immediately then everything is fine... just wondering if anyone else is experiencing something similar/has a solution?
Thanks in advance!
happens to me on occasion as well
same. i just usually redial.
known issue .. change gf
I have exactly the same intermittent issue when I dial home and speak to my wife - every so often I can hear her and she is unable to hear me.
Hasn't happened with other numbers?
I was very pissed off when that happened to me couple of times..
I'm not sure, but after that i was looking for the "audio settings" and one of the switches was set to 0,.. not sure if that was the case but i hope it was.
Will play some more with that once i get my second nexus
I had the problem where they couldn't hear me, called two numbers to confirm, did a reboot and haven't seen it again.
Lmao! Classic!
bug666 said:
known issue .. Change gf
Click to expand...
Click to collapse
surprised to see this. Anyone had it since receiving the OTA update (which I STILL have not received)?
bug666 said:
known issue .. change gf
Click to expand...
Click to collapse
Ha ha ha... she does have an iPhone... hmmm you may be on to something J/K... but yeah I'm hoping maybe the OTA will fix it... I hope
I am having this issue to when I call my mom who is on Verizon, and a few other friends. For me it happens randomly in the call, nothing gets muted or put on hold, I can hear them, but they can't hear me, so it usually ends up in them hanging up cause they thought I hanged up lol. This issue is still present after the OTA update, but I haven't tried it on a custom ROM yet.
ive had this issue w/tmobile in general. ive been using unlocked phones in the past, however. dont know if that makes a difference...used phones like the iphone and htc touch hd. i usually have to redial and its fine but once in a while it will happen. i have the nexus 1 w/stock rom. no OTA update yet.
Hmmmm... I've used unlocked phones on T-Mo's network as well, but this is the first time I've had this problem in areas with 2+ bars of reception... interesting.
Have only had my HD2 since Friday and was going to send it back tomorrow because the speaker has never worked. But now it's starting working.
No idea what triggered this or whether it'll remain "fixed" forever. All I did was try to replicate something that made my HD2 freeze in a completely unusable way yesterday (see my other thread) and suddenly it started working.
Having done a search it appears a few users have had speaker issues. Has anyone else had this problem rectify itself? Can I expect it to remain okay?
Cheers
SC
So usually after the phone has been in my pocket a bit, if I try to make a call, the screen and everything looks normal, but I hear no ringing. I don't know if it is actually going through but I doubt it.
Hang up, call right back... the phone starts ringing as normal.
I do this more and more often lately. Have to call everyone twice.
Has anyone else ever had this?
I've had this happen on several different ROMs, and I've been using 2.2 since it was publicly available.
same thing is happening to me, figured it was one of the bugs with dk28, hoping the official release will fix this annoyance
+1 same bug---same hope
I've been having it at least since DK17, maybe earlier.
I have the same problem.
Same problem as soon as I installed DK28. Hopefully they have these kinks worked out in the final release.
had this same problem from long ago. but i heard it was part of the delay for then the call is being sent 2 the tower... or something along those lines
Also intermittently having this issue, but it happened with my previous, non-android phone, too. I'm pretty sure the problem isn't the phone or its software.
I'd believe it was the network easier if hanging up and calling back didn't fix it...
Same problem. When I try the first time and hear nothing, no ringing or anything, the person Im calling says their phone rang and they answered it but heard nothing.
Sent from my SPH-D700 using Tapatalk
I've had this happen also.
So why is this not widely discussed? Did everyone think it was just them? I know that's how I felt...
This is a pretty serious issue. Is anyone on stock ROM?
i have this same issue and it only started happening once i flashed froyo. quantum rom. i dont think this was happening on eclair from what i remember but also people do say their phone rings. this is kinda annoying.
I'm using Quantum, too...
this started happening to me right when I installed DK28.
I had this issue too when I installed DK28.
I just flashed back to DI18 cause it was driving me nuts.
But one thing I found was that if you turn the speaker phone on then off, your good to go.
Have this problem. I have froyo, didn't happen on DK18.
Same here. By the way...I've also had a failed audio issue on voice dialing as well. First call the receving part can never hear me. I have to hang up and call right back manually.
Omg I thought I was crazy! Its been doing this since dk17. It only happens when I call businesses though :/
Sent from my SPH-D700 using XDA App
Okay, this just happened to me on my new flash of Cyanogenmod. So it's either a radio or "didn't wipe cache enough times" problem, right?
OK, having a huge problem with my Nexus 4. I'm still running stock kernel/ROM (although I am rooted) and everything about the phone works great EXCEPT for the phone itself! What I mean by this is: everything works (data, texts, tethering, et cetera), I can make and receive calls... but on those calls, there is no sound in *either direction*; when on a call, the mic doesn't pick up my voice, nor does the speaker relay the caller's voice. WTF?
My in-call volume is set to maximum, as checked via Power Toggles.
I've also noticed that the phone has a hell of a time hanging up after a call. For instance, I make a call on the N4 (again, no voice/sound during said call), and when I go to hang up the phone screen simply says "hanging up" and hangs like that for almost a minute. If I try to make another call after that, I get an error "Call Not Sent".
Any ideas how I might be able to track this problem down?
I should also mention that I don't know how long this problem has been present. I really don't use voice calling very much. When I tested the phone when I first received it, I simply made a call from it and to it from our land line and made sure it rang... I didn't think that there might be any issues with the call itself!
I have a brand new N4 that I just rooted using WugFresh toolkit and I see now that I can't hear anything during a call nor can the other person hear anything.
I've tried downgrading to .33 and .27. Also reflashing .48 with no success.
What should I do?
If you are experiencing the same problem I was, it wasn't fixable. I tried everything (reflashing stock, trying different ROMs, etc.)... and apparently it was just a hardware defect. I contacted Google and after explaining the issue (which they hadn't heard about at that point) they shipped me a new phone, which works perfectly.
I would highly recommend not wasting your time trying to diagnose the issue further and get in touch with Google about getting a replacement.
Cheers,
Matt
Thanks a lot for getting back to me. I contacted them and they already sent a replacement unit.
I found a thread on Google forums with six pages of people complaining about this. Apparently is not an isolated problem. Half of the people have the problem after updating to 4.2.2 and the other half (last pages) are all with new phones (4.2.2).
jumped in been a while since I had a play with LS - first impression love the splash screen :good:
Same problem, no warranty
Lucky you guys who were still under warranty. My Nexus 4 is 2 years old now and I just got this problem. It seems to be software related. The mic and speaker works for anything else other than placing phone calls. Furthermore, even if I plug a standard headset thought the 3.5mm jack, still no luck. The same with bluetooth headset.
It's interesting that when this problem started I would be able to place or receive a call once per reboot, i.e., after rebooting, the speaker and mic would work on the first call, but not for the second call unless I reboot the phone. Now I doesn't work even after reboot.
Gargabe?
Hi,
I have exactly same problem with sound during call. I'm using CM11. It doesn't matter if it is nightly or snapshot, simply there is no sound during call. Everything except calling works fine - music, ringing etc.
Restart didn't fork for me and also deleting application data has no effect. I've found only one solution - factory reset approximately each week. It is obvious that this is only workaround and not real solution.
I don't know if it is HW or SW issue. Strange think is that factory reset helps.
Any ideas are welcome. Thank you in advance.
novicz said:
Hi,
I have exactly same problem with sound during call. I'm using CM11. It doesn't matter if it is nightly or snapshot, simply there is no sound during call. Everything except calling works fine - music, ringing etc.
Restart didn't fork for me and also deleting application data has no effect. I've found only one solution - factory reset approximately each week. It is obvious that this is only workaround and not real solution.
I don't know if it is HW or SW issue. Strange think is that factory reset helps.
Any ideas are welcome. Thank you in advance.
Click to expand...
Click to collapse
I have the same problem.
Reverting to stock solved the issue form me until a fix for CM11 will be found.
BTW there is a bug report for CM11.
I can't post links but the code is CYAN-5728 on the CM bugtracking system.
novicz said:
Hi,
I have exactly same problem with sound during call. I'm using CM11. It doesn't matter if it is nightly or snapshot, simply there is no sound during call. Everything except calling works fine - music, ringing etc.
Restart didn't fork for me and also deleting application data has no effect. I've found only one solution - factory reset approximately each week. It is obvious that this is only workaround and not real solution.
I don't know if it is HW or SW issue. Strange think is that factory reset helps.
Any ideas are welcome. Thank you in advance.
Click to expand...
Click to collapse
The issue is with Google Play Services. more specifically the checkin service within it.
(this is from the CM bugtracking system , code: CYAN-5728, as stated by pupillo)
download/install the app "DisableService" from the play store. (must be rooted)
under the [System] tab, browse to "Google Play Services", tap it, then browse to "checkinservice", uncheck. (it will prompt for superuser, allow)
restart phone
try placing/receiving a call
none of u guys spent even 1 second to check this forums for answer. there have been at least 2-3 threads about this issue, all of them containing/linking to the fix.
It started suddenly after a week on the January update, but I downgraded to Dec update and still have the same issues, meaning it's a hardware defect. Already reported this to google. Anyone else?
Had similar issue
I had a similar issue since yesterday. Tried booting into the safe mode to check if any third party app is doing it( If you wanna try that hold the power button then touch and hold the power icon on the screen). If it still stays it is a hardware issue you need to get it repaired. I just gave my phone to Ubreakfixit
Yes it is a hardware issue. Safe mode, factory reset, downgrading the software did not work.
This just happened to me this morning.
what is going on? this literally just happened to me too this morning. I can make calls via whatsapp/facebook etc, but if I try to call anyone it just says "calling" but there's no sound, eventually it cuts off. If someone tries to call me, the phone doesn't ring and I just get the sms saying there's a message in my voicemail. It says I'm on the 4g network, I can send sms messages and wifi works fine. If I have to ship the phone anywhere I'm ****ed, I'll have to buy another phone as a spare :crying:
SmokewiseGanja said:
what is going on? this literally just happened to me too this morning. I can make calls via whatsapp/facebook etc, but if I try to call anyone it just says "calling" but there's no sound, eventually it cuts off. If someone tries to call me, the phone doesn't ring and I just get the sms saying there's a message in my voicemail. It says I'm on the 4g network, I can send sms messages and wifi works fine. If I have to ship the phone anywhere I'm ****ed, I'll have to buy another phone as a spare :crying:
Click to expand...
Click to collapse
It appears the bottom speaker just burnt out. Hundreds of other people have the same issue across all pixel models.
backslashV said:
It appears the bottom speaker just burnt out. Hundreds of other people have the same issue across all pixel models.
Click to expand...
Click to collapse
Looks like I'm one of the lucky ones. I had to go out and soon as I got to the next town a call came in, so I tested making more calls and it worked fine there. Upon returning home the issue returned. I figured it's gotta mean something is up with my provider or the nearby antenna so asked a few friends who live near me and a neighbour. Turns out they all have the same issue. I'll have to wait it out now and see if they fix it. The wierd part is 4g data and sms work fine and I've still got full signal strength or I'd have assumed that right away.
SmokewiseGanja said:
Looks like I'm one of the lucky ones. I had to go out and soon as I got to the next town a call came in, so I tested making more calls and it worked fine there. Upon returning home the issue returned. I figured it's gotta mean something is up with my provider or the nearby antenna so asked a few friends who live near me and a neighbour. Turns out they all have the same issue. I'll have to wait it out now and see if they fix it. The wierd part is 4g data and sms work fine and I've still got full signal strength or I'd have assumed that right away.
Click to expand...
Click to collapse
That sounds more plausible than hundreds of Pixels bottom speaker burning out all of a sudden. When the call supposedly comes in does it show on the screen or just go directly to voicemail? That would be the initial test of the speaker. Does it play music, can you hear notifications? Every once in a while that happens to me and then I just try again a mile or so down the road and it connects fine. If you have wifi calling you can try that too.
bobby janow said:
That sounds more plausible than hundreds of Pixels bottom speaker burning out all of a sudden. When the call supposedly comes in does it show on the screen or just go directly to voicemail? That would be the initial test of the speaker. Does it play music, can you hear notifications? Every once in a while that happens to me and then I just try again a mile or so down the road and it connects fine. If you have wifi calling you can try that too.
Click to expand...
Click to collapse
No, it was the service provider in the end. My whole town had the issue for a couple days. The company (movistar) have fixed it now so I can make calls and recieve them no problem. To say I was relieved is an understatement.
Bottom speaker broke out of nothing
I guess I'm really unlucky, me and my girlfriend got two pixel 4 in black Friday and both of the phones had the same issue, it started having a crackling sound for a few seconds and then the bottom speaker completely died while in a speakerphone call tried a factory reset with no luck, no sounds comes out, my girlfriend had the phone only for a few weeks when that happened, and in my phone happened last week, now we have to figure how to ship the phone back to the US and try to get a refund, since if it breaks again it would be close to impossible for us to ship it back again
backslashV said:
It started suddenly after a week on the January update, but I downgraded to Dec update and still have the same issues, meaning it's a hardware defect. Already reported this to google. Anyone else?
Click to expand...
Click to collapse
Hello everyone
I own a pixel 4 and it has a constant problem.
after operating normally, suddenly for no apparent reason it loses all sounds and vibrations.
also it is not possible to make calls and freezes in various system applications.
sometimes this is solved with a simple restart of the phone, other times a factory reset is necessary and lately it is required to unlock the boot loader to reinstall the factory image and test with which security patch recovers all its functions and returns to function normally.
It started suddenly after a week on the January update
What would be the cause of this failure in the phone?
At first I reported the problem to google and they indicated the same to most of you; restarting the phone or factory reset and how the method worked no longer insisted.
after the February update its operation was normalized, but with the arrival of the May update the same problem returned.
I had to downgrade to the April update, then to the March update and after several attempts it worked again, but a few days later the problem returns and I have to repeat the process.
What arguments should i use to convince google to change the phone or return my money?
I never rooted
Buy the unlocked phone at BHphoto on Black Friday
model G020I
I live in Peru
NOTE: I do not speak English and use the translator.
sorry
I'm on latest Android 11 DP and I noticed that this release removed a lot of bass from the speaker. I think to prevent the clipping and damage of the speaker.
SmokewiseGanja said:
what is going on? this literally just happened to me too this morning. I can make calls via whatsapp/facebook etc, but if I try to call anyone it just says "calling" but there's no sound, eventually it cuts off. If someone tries to call me, the phone doesn't ring and I just get the sms saying there's a message in my voicemail. It says I'm on the 4g network, I can send sms messages and wifi works fine. If I have to ship the phone anywhere I'm ****ed, I'll have to buy another phone as a spare :crying:
Click to expand...
Click to collapse
Is your "Do not disturb" mode turned on by chance.
Sorry if this is a stupid suggestion.