I have a Vodafone UK set, non-rooted, which will not play any music, phonecalls, ringtones, alarms etc through the loudspeaker. The ear speaker works fine for phonecalls and headphones work fine for music
The media, alarm and ringtone volume is up on maximum but it just wont play any noise out loud at all.
I have turned off and on the phone and still have the same issue.
I am on firmware 1.28.161.9
Any help much appreciated!
looks like a hardware fault. if i tap or hold the bak of the phone firmly (ie. try to press the screen towards the back of the phone) then the sound comes back on. when i let go it vanishes.
so basicly to get sound i would have to walk about pressing the phone together lol
will take it back to them tomorrow to get a replacement handset - lame.....
Sounds like a Hardware fault as i had one. Try to softly press the back near the speaker to regain contact between the speaker and the board. Had to swap my Device for Warranty. The One X is of poor build quality
Had this happen to my last phone htc desire send it back mate
Hi
I put a new eBay screen into my 2 yr old g3.
Screen works fine but since the change vibrate doesn't work anymore and I can't hear ppls voices on calls
I Can hear music thru the speaker and hear ppl when they call me and I switch on loudspeaker
Any ideas what I've done wrong?
I checked the speaker and vibrate battery and they seem to have good contact with the motherboard
I cant figure out why this is happening but when i am in the call on speakerphone the phone will sometimes just turn off speaker and revert to the phone earpiece but the software still thinks its in speaker mode thus the only way to go back to speaker is to change the audio to handset first then reenable speaker.. this can sometimes happen several times withing a single call. I also have an android wear watch that is paired via bluetooth which i though may be the culprit but i have noticed it even when my watch is dead... anyone else?
Having same issue when connected to Bluetooth in my car. It will change output and I have to manually put it on phone headset then back. Sometimes it will just drop a call all together. Usually 6 minutes approx into the call. I am on Verizon 7.1.1. NMF260. Anyone else still having these issues on most recent update as I am.
Yeah I noticed it to. Thought it was my Android wear watch so I turned off gestures thinking the wrist movements were switching the output. I haven't had a chance to retest.
Sent from my Pixel XL using Tapatalk
I am going to resurrect this thread because I'm having the same issue and it's one of the most infuriating things ever. To have my private conversation suddenly switch to speakerphone, or to be in the car and have it switch from car speakers to speakerphone is frustrating beyond words!
I have the issue as well. Sometimes it happens when another calls comes in or when a notification comes in, but also happens randomly. Pixel 2, Android 9.
Back from the dead
Odd bug, any mention of it on the bug tracker?
Ok, as per the title, and here are some things covering the issue:
Initially the speaker stopped working immediately after plugging the charger in. It is a genuine Pixel charger.
The problem went away in less that a day later, but reappeared straight after charging again.
Yet again the problem went away
Yesterday the issue reappeared randomly whilst using the phone and hasn't corrected itself since
The issue results in any short sound played giving exactly 16 feint clicks from the speaker, no crackling or coarse sounds, just 16 programmed clicks from the speaker. Press the home button - 16 clicks, like a comment on the Facebook app - 16 clicks
Playing a Youtube video results in constant feint clicking from the speaker, same frequency as the 16 clicks, but as said, constant.
Set the phone to "do not disturb" so no sounds from apps/software are allowed and the 16 clicks from phone interaction (home button etc etc) still happen exactly the same as before; this confuses me further as if it was ingress or a faulty speaker it would not give any sound while "do not disturb" is enabled. If it was a hardware fault, it'd have to be at chip level, so pointing toward software/firmware
Safemode has no effect
Factory reset has no effect
The Google "piano" boot up sound is not played.
Now, the very odd one; if I am browsing the Facebook app and auto play videos are on, the clicking sound is developed. To clarify, the video has not been clicked, it is not full screen, it is just there, on the newsfeed playing thus creating constant clicking while the video is playing. There would be NO sound playing if the speaker worked, but still, it clicks.
I'm unsure how the phone picks up audio playing for the volume rocker to adjust media volume instead of notification volume, but from what I can infer, it works on some sort of pass through. If the phone picks up sound, the volume rocker, when pressed, focuses on and adjusts media volume. As per number 11, in this state of a video playing but NOT focused, the volume buttons revert to notification volumes, hence no sound coming from the app; why is the clicking apparent when there is no sound trying to be played?
Phone calls work fine
Phone calls with loud speaker do not work
Sound via headphones do work perfectly
I have tried checking to see if ingress via the headphone jack is causing the issue by plugging/unplugging headphones but this has had no effect.
Bluetooth is OFF
Have turned on headset in "System UI Tuner" in status bar to show if the phone thinks they are connected. There is no notification of this
Any ideas?
Regards​
Dave
whoa that's crazy, is it similar to the issue in this video?
https://www.youtube.com/watch?v=7ZH8lLFRWN4
does audio play through your earphones when connected or does this also come across as clicks?
fatapia said:
whoa that's crazy, is it similar to the issue in this video?
https://www.youtube.com/watch?v=7ZH8lLFRWN4
does audio play through your earphones when connected or does this also come across as clicks?
Click to expand...
Click to collapse
Headphones work as normal. Such a confusing issue with the phone. With regards​ to phone condition etc, it is two months old and in immaculate condition, never dropped or wet. It's my second pixel as my previous one died one day and wouldn't turn on again. Google are happy to replace, but as it's an intermittent fault they have warned me that if they don't find anything wrong when this phone by the time it gets back to them, I could have to stump the cost of a new phone.
They had organised a return, but a day later it started working again, so cancelled the return; now stopped working again
As for the video, will wait until I'm at a PC, can't hear what's going on in that one currently (on my phone haha).
EDIT
@fatapia - I have watched the video, the fault is nothing like that in the video. There is no sound no matter what, just 16 feint programmed clicks as mentioned before after every interaction with the phone that would make a click/sound, even on silent it still does it.
DavidVanstone said:
Headphones work as normal. Such a confusing issue with the phone. With regards​ to phone condition etc, it is two months old and in immaculate condition, never dropped or wet. It's my second pixel as my previous one died one day and wouldn't turn on again. Google are happy to replace, but as it's an intermittent fault they have warned me that if they don't find anything wrong when this phone by the time it gets back to them, I could have to stump the cost of a new phone.
They had organised a return, but a day later it started working again, so cancelled the return; now stopped working again
As for the video, will wait until I'm at a PC, can't hear what's going on in that one currently (on my phone haha).
EDIT
@fatapia - I have watched the video, the fault is nothing like that in the video. There is no sound no matter what, just 16 feint programmed clicks as mentioned before after every interaction with the phone that would make a click/sound, even on silent it still does it.
Click to expand...
Click to collapse
Did you ever solve this? I just started having the same exact problem with the 8.1 update.
Sent from my Nexus 7 using Tapatalk
psychephylax said:
Did you ever solve this? I just started having the same exact problem with the 8.1 update.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I'm having the same issue on my Pixel 1st gen too after my 8.1.0 update. In phone calls, I can only hear sound when i turn on speaker phone. Headphone sound works fine, but all media volume isn't playing.
Did anyone solve this? I am having the same issues. No sound. But ringtones and notifications work fine. Speakphone only during calls.
Google approved an RMA for mine and sent me a refurbished handset which works great
Sent from my Nexus 7 using Tapatalk
Hello, I have been having this problem with my previous s10+ and it has continued into my zfold3 so this is not specific to the zfold3 but it is where I am experiencing this issue currently.
So the problem is when I am in a call and someone texts me I get a barely audible notification sound that I almost never actually hear. I have gone into the in call settings and only see an option to turn on/off in call notifications but no customization such as what tone to use nor the volume. I also tested this with notification volume set to around 25% vs 100% and it goes from no audible sound at all to a ding that is barely hearable in a completely quiet setting, but once you are in an actual real world situation of talking to someone you will not hear it.
I talk on the phone while using headphones, specifically buds live editions. I include this info in case its relevant, but I have tested while not using the earbuds and had the same result so I don't the headphones are the problem.
Am I missing something in the settings somehow where I can actually have control of in call notifications? With my previous phone I dont remember having this issue early on. After at least a year of using the s10+ this issue started happening and I couldnt figure it out, got the new phone and purposely did not connect the transfer cable and set it up and transfered files manually to avoid potentially having a bad setting transfer over and continuing this problem. Yet the problem still continues regardless. My best guess is its something that started after a big UI update or something like that. Hoping someone can give me some insight or advice on fixing this cause its causing me a lot of strife.