Related
I woke up today to my alarm vibrating and with no sound. I checked volume levels and everything looked good.
I tried to play audio in a few apps and nothing worked.
I rebooted and everything was good.
A little worried I'm going to miss my alarm if this happens intermittently
Sent from my Nexus 5 using Tapatalk
epg0 said:
I woke up today to my alarm vibrating and with no sound. I checked volume levels and everything looked good.
I tried to play audio in a few apps and nothing worked.
I rebooted and everything was good.
A little worried I'm going to miss my alarm if this happens intermittently
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
My main loud speaker stopped working yesterday (1 day after receiving the phone) and I just contacted Google for an RMA and replacement. I tried rebooting and toggling settings and even a factory reset but the speaker just does not work at all.
UberGoat said:
My main loud speaker stopped working yesterday (1 day after receiving the phone) and I just contacted Google for an RMA and replacement. I tried rebooting and toggling settings and even a factory reset but the speaker just does not work at all.
Click to expand...
Click to collapse
I don't think my issue is with the speaker, because even the headset speaker doesn't work when the sound cuts out. It seems like it must be a software issue.
UberGoat said:
My main loud speaker stopped working yesterday (1 day after receiving the phone) and I just contacted Google for an RMA and replacement. I tried rebooting and toggling settings and even a factory reset but the speaker just does not work at all.
Click to expand...
Click to collapse
Same exact thing here. Ive tried calling but they want me to put up another $350 until the recieve the defective device which could be a week. So frustrating.
Grims said:
I don't think my issue is with the speaker, because even the headset speaker doesn't work when the sound cuts out. It seems like it must be a software issue.
Click to expand...
Click to collapse
Yeah I have exactly the same issue as you. Was playing music on my phone through headphones. Took headphones out when I arrived at where I was walking. When I put my headphones back in to listen to music again, the screen said it was playing but nothing came out. I took out headphones and didn't get any sound out the speaker. I rebooted and all was fine again.... Is this a software bug or hardware? Should I try get a replacement for my phone?
timfimjim said:
Yeah I have exactly the same issue as you. Was playing music on my phone through headphones. Took headphones out when I arrived at where I was walking. When I put my headphones back in to listen to music again, the screen said it was playing but nothing came out. I took out headphones and didn't get any sound out the speaker. I rebooted and all was fine again.... Is this a software bug or hardware? Should I try get a replacement for my phone?
Click to expand...
Click to collapse
It's possible it's an issue with the headphone jack thinking headphones are plugged in when they're not. I've seen it happen before, and even plugging in headphones didn't resolve it until I cleaned the jack. Haven't seen that issue on a brand new device though.
Google has fantastic support, so I'm going to wait it out as long as possible so if I do have to RMA it I'll have a better chance of getting a later hardware revision.
Is the devices still locked and rooted? My still new from factory. When I do a factory reset sound will work for few seconds and give out. I am going to try to root and unlock load a custom rom and see if that fixes the problem.
Mine is stock, unrooted.
It has to be a software issue because when I reboot the sound works again.
I really do not want to RMA, everything else seems fine.
Just rooted unlocked flashed a custom rom. Still no sound...then just now out of nowhere sound works??
emeniit ealdne
Reporting a similar issue on my end. Doublethinking if I ripped out the headphones too roughly but initially thought my right earbud was busted so a coworker opted to let me use his. It was playing YouTube videos on loudspeaker just fine during lunch. OTW back to the office noticed that sound notifications were buggy. Plugged in coworker's headphones to confirm if mine was busted but experienced same outage. Then both earbuds went silent. Thought I had to clean the jack when I got home but I did a restart and they work fine.
I have the same problem with my N5. When I adjust the volume with the rocker, I no longer hear the sound that lets you know it's being changed. It resolves itself after a few minutes, but it concerns me.
Sent from my Nexus 5 using Tapatalk
I have the same issue. Restarting put it right. Last night I used headphones, and it's possible that this is what causes the sound to stop working, since I can't remember hearing any notifications after that.
epg0 said:
I woke up today to my alarm vibrating and with no sound. I checked volume levels and everything looked good.
I tried to play audio in a few apps and nothing worked.
I rebooted and everything was good.
A little worried I'm going to miss my alarm if this happens intermittently
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
gdarren said:
I have the same issue. Restarting put it right. Last night I used headphones, and it's possible that this is what causes the sound to stop working, since I can't remember hearing any notifications after that.
Click to expand...
Click to collapse
In my case it is the headphones. Everything works fine until the headphones are pulled out. Now sound is not working again, hoping it will fix itself like it did yesterday. 2nd time this has happened. Reboot does not fix my problem. How did yall clean the headphone jack safely?
kp432 said:
In my case it is the headphones. Everything works fine until the headphones are pulled out. Now sound is not working again, hoping it will fix itself like it did yesterday. 2nd time this has happened. Reboot does not fix my problem. How did yall clean the headphone jack safely?
Click to expand...
Click to collapse
I just posted about this issue -- a reboot does fix the issue. I also had it partially working with just the left earbud working. Once again, a reboot fixed.
zmattmanz said:
I just posted about this issue -- a reboot does fix the issue. I also had it partially working with just the left earbud working. Once again, a reboot fixed.
Click to expand...
Click to collapse
Ive rebooted multiple times, wiped re-flashed rom, and nothing. The only reason i unlocked/rooted was hopes that a new Rom would fix. Started acted this way fresh from the box. Thinking of flashing the whole .img?
This problem started for me a few days ago, when I got a call and noticed there was no sound from the speaker. After fiddling with my sound settings and rebooting all was working again for a few hours, then the sound stopped again. I had a colume toggle widget installed which I though may have been causing a prob so uninstalled it. This morning, I had no sound from the speaker again. Did a safe mode boot and still no sound. Fiddled with the volume controls, rebooted a couple of more times and still nothing. I rang Google, and while I was on hold, hit the speaker button and the speaker worked fine in-call. Spoke to a Google device "expert" who had not heard of this prob, and suggested I do a factory restore (the good old "Have you tried turning it off and on again?" fix). Just did a factory restore and the speaker is working fine again. So seems like a software issue, I hope Google addresses this soon.
hi guys,
not sure if this is still actual but same thing happened to my missus tonight. she missed the work today cos of this. there is no sound what so ever. for now I haven't have much time to play with it as she was running late. its the latest device bought just few weeks ago and there is latest update on it. its in factory state, untouched, no root as she doesnt want me to touch her phones (not sure why ??? )
anybody else still having same issues these days? anyone can confirm if it is SW or HW issue?
thx
it seems a software issue though i never faced it try flashing the factory imange after a clean wipe or switch to cm
bhavstech said:
it seems a software issue though i never faced it try flashing the factory imange after a clean wipe or switch to cm
Click to expand...
Click to collapse
phone is in factory condition as I mentioned I haven't touch it as I'm not allowed only thing what was done is the OTA update from new.thats all.
will see tonight when she come back from work. in worst I will RMA what I dont really want to do
rikardo1979 said:
phone is in factory condition as I mentioned I haven't touch it as I'm not allowed only thing what was done is the OTA update from new.thats all.
will see tonight when she come back from work. in worst I will RMA what I dont really want to do
Click to expand...
Click to collapse
If it's completely stock then perform a factory reset from the stock recovery and make sure she hasn't installed any apps that could interfere with sound. Apps like Tasker may be.
- Sent from an IceCold Hammerhead!
A few days ago I discovered that people I talk to over the phone can't hear me, whether they call me or I call them, while I can hear them perfectly.
My voice if very muffled, impossible to comprehend, sometime it cuts out completely and there's also a persistent "static" noise in the background, kind of like wind blowing. I can usually make myself heard only if I raise my voice by a lot, close to yelling actually.
I tested the microphone via the service menu AND the Xperia Diagnostics app and I'm even more puzzled. Initially I'd say that about 70-80% of the time I had to raise my voice a lot so that the recorder can pick up anything and the results I got were essentially what the people I talked to reported. I looked up the issue on various forums, fiddled with the settings, disabled xLoud, noise suppression, took the SIM out and put it back in, did a repair via the PC Companion AND a factory reset later on and nothing seems to consistently work. Sometimes they can hear me, sometimes they can't. Testing results are also much better now and I'm able to clearly hear my voice most of the time, but when actually calling someone, even when they say they hear me clearly they can still hear that annoying static. I now have noise suppression turned off, since that seems to help.
To my knowledge, this started to happen after the 4.2.2 update, a very buggy update. I also had a problem with headphones (two pairs in otherwise working order) not being recognised, even though both were initially working well with the phone. Eventually I had to repair the phone twice for that (the first time it didn't fix anything) just to get the phones working again. It's after that that I noticed this mic problem.
I also found this thread and I wonder if that lil' piece of rubber can be the problem. Apparently those are Ions, but I'm thinking maybe there's enough internal commonality between that and the XL that I could actually have the same problem.
Other than that, what would you advise? Try to go back to 4.1.2?
Service is my last option due to time and distance concerns. Thanks!
Model: C2105
Android: 4.2.2
Build no.: 15.3.A.0.26
potato muncher said:
A few days ago I discovered that people I talk to over the phone can't hear me, whether they call me or I call them, while I can hear them perfectly.
My voice if very muffled, impossible to comprehend, sometime it cuts out completely and there's also a persistent "static" noise in the background, kind of like wind blowing. I can usually make myself heard only if I raise my voice by a lot, close to yelling actually.
I tested the microphone via the service menu AND the Xperia Diagnostics app and I'm even more puzzled. Initially I'd say that about 70-80% of the time I had to raise my voice a lot so that the recorder can pick up anything and the results I got were essentially what the people I talked to reported. I looked up the issue on various forums, fiddled with the settings, disabled xLoud, noise suppression, took the SIM out and put it back in, did a repair via the PC Companion AND a factory reset later on and nothing seems to consistently work. Sometimes they can hear me, sometimes they can't. Testing results are also much better now and I'm able to clearly hear my voice most of the time, but when actually calling someone, even when they say they hear me clearly they can still hear that annoying static. I now have noise suppression turned off, since that seems to help.
To my knowledge, this started to happen after the 4.2.2 update, a very buggy update. I also had a problem with headphones (two pairs in otherwise working order) not being recognised, even though both were initially working well with the phone. Eventually I had to repair the phone twice for that (the first time it didn't fix anything) just to get the phones working again. It's after that that I noticed this mic problem.
I also found this thread and I wonder if that lil' piece of rubber can be the problem. Apparently those are Ions, but I'm thinking maybe there's enough internal commonality between that and the XL that I could actually have the same problem.
Other than that, what would you advise? Try to go back to 4.1.2?
Service is my last option due to time and distance concerns. Thanks!
Model: C2105
Android: 4.2.2
Build no.: 15.3.A.0.26
Click to expand...
Click to collapse
Well since you said that this started happening after you've updated to 4.2.2 you have 2 options
1. Reflash the 4.2.2 update
2. Downgrade to 4.1.2
I hope that helps
Sent from my C2104 using xda app-developers app
Unfortunately, I can't be sure if it's due to 4.2.2 or just a coincidence, since it didn't start immediately after the update. Like I said, that thread about the Ion mic problem got me thinking that maybe this is what happened, in which case it's only a coincidence that I also updated to 4.2.2 a couple of days prior.
"Reflash the 4.2.2 update" - is this different from repairing it via the PC Companion? Like I said, I already did that and a factory reset later on and it didn't help with this.
In any case, thanks for your help! :good:
potato muncher said:
A few days ago I discovered that people I talk to over the phone can't hear me, whether they call me or I call them, while I can hear them perfectly.
My voice if very muffled, impossible to comprehend, sometime it cuts out completely and there's also a persistent "static" noise in the background, kind of like wind blowing. I can usually make myself heard only if I raise my voice by a lot, close to yelling actually.
I tested the microphone via the service menu AND the Xperia Diagnostics app and I'm even more puzzled. Initially I'd say that about 70-80% of the time I had to raise my voice a lot so that the recorder can pick up anything and the results I got were essentially what the people I talked to reported. I looked up the issue on various forums, fiddled with the settings, disabled xLoud, noise suppression, took the SIM out and put it back in, did a repair via the PC Companion AND a factory reset later on and nothing seems to consistently work. Sometimes they can hear me, sometimes they can't. Testing results are also much better now and I'm able to clearly hear my voice most of the time, but when actually calling someone, even when they say they hear me clearly they can still hear that annoying static. I now have noise suppression turned off, since that seems to help.
To my knowledge, this started to happen after the 4.2.2 update, a very buggy update. I also had a problem with headphones (two pairs in otherwise working order) not being recognised, even though both were initially working well with the phone. Eventually I had to repair the phone twice for that (the first time it didn't fix anything) just to get the phones working again. It's after that that I noticed this mic problem.
I also found this thread and I wonder if that lil' piece of rubber can be the problem. Apparently those are Ions, but I'm thinking maybe there's enough internal commonality between that and the XL that I could actually have the same problem.
Other than that, what would you advise? Try to go back to 4.1.2?
Service is my last option due to time and distance concerns. Thanks!
Model: C2105
Android: 4.2.2
Build no.: 15.3.A.0.26
Click to expand...
Click to collapse
The ultimate method for fix this problem is send it to sony service center,,i suggest so,,i think it the best choices
potato muncher said:
"Reflash the 4.2.2 update" - is this different from repairing it via the PC Companion? Like I said, I already did that and a factory reset later on and it didn't help with this.
In any case, thanks for your help! :good:
Click to expand...
Click to collapse
You can either use as you said repairing via PCC or just flash FTF.
Hello,
Im running Lollipop stock if I make a phone call with my headphones with no mic plugged in, the other side tells me that they can't hear me . As soon as I unplug the headphone, sound is normal again. Its like as if the internal microphone on the phone is shut off. If I use the speakerphone on the phone without headphones then its fine. This was never a problem when using the latest Kitkat. This just started since I have upgraded to Lollipop on my Nexus 5. Is there a fix to return the behaviour as it was in Kitkat? Thanks.
raiden said:
Hello,
Im running Lollipop stock if I make a phone call with my headphones with no mic plugged in, the other side tells me that they can't hear me . As soon as I unplug the headphone, sound is normal again. Its like as if the internal microphone on the phone is shut off. If I use the speakerphone on the phone without headphones then its fine. This was never a problem when using the latest Kitkat. This just started since I have upgraded to Lollipop on my Nexus 5. Is there a fix to return the behaviour as it was in Kitkat? Thanks.
Click to expand...
Click to collapse
Same here, and it's very annoying, but i don't think the mic is disabled because if i shout right into the microphone the person on the other side can hear me, but very feebly.
Sometimes, if i reboot the phone, it will work with no problem but i can't reboot every time i receive a call.
I'm also seeing this problem. I haven't checked if yelling works! It was fine on KitKat. I updated using the OTA and don't have root or any modifications.
Is it possible to report this to Google?
bdtouchpro said:
I'm also seeing this problem. I haven't checked if yelling works! It was fine on KitKat. I updated using the OTA and don't have root or any modifications.
Is it possible to report this to Google?
Click to expand...
Click to collapse
I think so, on Android bug tracker maybe. Too bad there is no right way to reproduce the issue every time.
I have the same issue withe 5.0 every time I am using my phone (N5 stock) with normal headphones.
I have also raised an issue in the Android issue tracker (Issue 80251 if you want to add updates to it)
Sadly I am a new user and I cannot post direct links yet
Same problem
I have the same issue. Person on the other end cannot hear me when I have headphones plugged in. It was fine before the update to lollipop.
Using a nexus 5
+1
My nexus 5 has the same issue. Hope this is fixed soon.
+1. I used to have a cool hands free in the car. Now I have to pick up the Phone. Not cool.
Anyone who tried 5.0.1 can tell if it has been fixed?
I am also having this issue since i upgraded to lollipop, I've tried rolling back to 4.4.4 and the microphone still doesn't. I even bought a new microphone usb port cable off ebay and replaced it with no luck
I have this problem now too..
All of a sudden I have this problem too. It's really weird. Mic doesn't work for voice typing or video recording. But if I start a phone call and turn speakerphone on, the mic does work for videos and voice typing! So its obviously a software bug (not a hardware problem).
I called Google Nexus support and they couldn't help me. So they sent me over to LG who also couldn't help. Is there any fix for this yet (besides factory reset!?)..
I just figured out how to fix the problem!! I made a youtube video to more easily demonstrate how to fix it. (It's an easy fix!) https://www.youtube.com/watch?v=_dPQKopQq9k (scroll to 1:46 to go straight to the fix).
Just worked OK on Android 5.1 on Nexus 5. So it looks like the software is now fixed.
Android 5.1 here, fresh install. I have this problem too, so it's not fixed in the firmware.
[Q] In-call mic & speaker dead on stock device, can only make calls with Bluetooth
Anyone else encountered this problem? It's NOT a volume issue, it's an 'in-call speaker and mic not working at all' issue. About two months ago my phone calls completely cut out all in-call sound, UNLESS I use a Bluetooth headset, in which case I can talk and hear just fine. When it first went out, I was able to use the mic and in-call speaker as long as I put it in speakerphone mode, but after a few weeks, that cut out, too. It will answer the call...I just can't communicate without BT engaged. Factory reset and other known "try this first" solutions have been dead-ends.
The OTA to KitKat didn't change or help anything in regard to this problem, and the same problem persists in the same fashion. I am currently still stock...after modding my M7 on TMO repeatedly, when I switched to Verizon and got an M8, I resolved to stick with stock and try to appreciate getting the OTAs before the other carriers. All well and good--until your in-call sounds bugs out and renders your device useless as a phone unless you put your BT earpiece in first.
I'm curious if this is a widely known problem, as I couldn't find evidence of it being common, but wasn't sure if I was just looking in the wrong place or using the wrong search terms. If so, is there a decent fix, or did VZ just sell me a lemon? If there's not a decent solution, would Factory Reset, unlock, and flashing TWRP and a good aftermarket ROM, say CM, cause this problem to be fixed?
Just figured I'd ask the hive before I dig into it myself and end up pissing away the rest of my weekend on it. Cheers and thanks!
I'm having a few Issues with audio on my pixel that I'm having a hard time finding answers to.
1. The biggest issue that I'm having the hardest time finding info about is this; when listening to music through my headphones after about 5 seconds there will be a pop, the all the audio on my phone will stop working completely. no, mic, no assistant, no headset, bluetooth, speakerphone, or speaker in general.
2. Often, my pixel will just not detect headphones at all. or detect them, then play no sound.
3 Sometime only the mic stops working. I know this one is common in android in general.
A reboot fixes all these things, but the headphone pop happens every single time. I'm talking with support now and they want me to factory reset the phone, so we'll see what happens after that. My questions are if any of you have found fixes, and if the problems happen on custom ROMs. And Does ROMing void the warranty on this phone?
Did you buy your phone from Verizon or Google? The pop and audio dying compare results of a poorly made headphone plug. Check with another pair of headphones and see if you get the same results unless you already have. If the alignment is slightly off it could be shorting across contacts although I don't understand why would work for a short period of time and then stop.
I had the issue with several pairs of headphones and auxillary cables. I talked with Google support and they had me factory reset the phone, and that seems to have fixed the headphone jack issue. The other issues still persist with the mic and call problems though.
The guy from Google support doesn't seem to be getting it. I told him that I'm still having issues the other stuff, but he keeps asking if I tried other headphones. This is the 5th time he's asked.
Yeah, the mic only works about %20 of the time. I've had to restart my phone just to make phone calls for about a week now. I'm going to try and get a replacement.
I'm having an issue from time to time where the phone speaker at the top stops working when taking a call. Only happened twice in 3-4 months. reboot fixed it... ugh..
That's how mine started. Now, o times out of ten I have to restart my phone and pray that my phone likes me that day to make a phone call.
Figured I would pop in here guys. Had a Pixel since launch and have had myriad problems, mic stopped working and couldn't make calls, headphones not being recognized. Factory reset didnt help, safe mode no help, etc. Scoured the net and found on google product forums a possible solution, tried it and so far it has worked.
https://productforums.google.com/forum/#!topic/phone-by-google/4kyIdArEve8
basically go to clock app, find alarms and delete them, then delete data and cache from clock app and reboot. worked a charm for me, try it out.
I'll give this a shot. How long has this been working for you?
Anyone having issue with music "skipping" when connected to a 3rd party bluetooth for cars?
chadhoard said:
Anyone having issue with music "skipping" when connected to a 3rd party bluetooth for cars?
Click to expand...
Click to collapse
Occasionally. Typically a reboot fixes it for me.
magicCrazyThing said:
I'll give this a shot. How long has this been working for you?
Click to expand...
Click to collapse
meant to post earlier but got tied up, this worked for a few hours then back to the same thing. I RMA'd the phone and have a new one now. Hope this one is better
also fyi, my verizon new/possibly refurb phone was received today running 7.1 , not 7.1.1 , i thought some had questions about that.
CaddymanLNL said:
meant to post earlier but got tied up, this worked for a few hours then back to the same thing. I RMA'd the phone and have a new one now. Hope this one is better
also fyi, my verizon new/possibly refurb phone was received today running 7.1 , not 7.1.1 , i thought some had questions about that.
Click to expand...
Click to collapse
I'm just waiting until I get another screen ordered for my MXPE to swap my pixel. If that one has issues too I'll probably just try to get my money back. I love this phone, but that's not an issue I can handle.
magicCrazyThing said:
Yeah, the mic only works about %20 of the time. I've had to restart my phone just to make phone calls for about a week now. I'm going to try and get a replacement.
Click to expand...
Click to collapse
I have the exact same issue Are we sure it's a hardware problem?
d3sm0nd said:
I have the exact same issue Are we sure it's a hardware problem?
Click to expand...
Click to collapse
If it's not, then it has to be a really deep seated software issue. I flashed pure Nexus to see if it still did it and had no luck at all. Lol
magicCrazyThing said:
If it's not, then it has to be a really deep seated software issue. I flashed pure Nexus to see if it still did it and had no luck at all. Lol
Click to expand...
Click to collapse
Then i'm ****ed because I bought off ebay and I nobody can exchange my phone. I have to send it to Google and wait probably weeks until I get a new one. :crying: