[Q] Speaker volume problem after Kitkat update, any fix? - Moto G Q&A, Help & Troubleshooting

The speaker was really working really well before the Kitkat update. I am not 100% sure if that was the cause since the phone was updated shortly after I got it. After the update, every now and then the speaker will become really low volume. Sometimes it can be fixed by restarting the phone, but the problem has been happening more and more often. I have the phone for about a month now.
Is anyone else experiencing this problem? Any suggestion in fixing it? Thank you.

Ailin said:
The speaker was really working really well before the Kitkat update. I am not 100% sure if that was the cause since the phone was updated shortly after I got it. After the update, every now and then the speaker will become really low volume. Sometimes it can be fixed by restarting the phone, but the problem has been happening more and more often. I have the phone for about a month now.
Is anyone else experiencing this problem? Any suggestion in fixing it? Thank you.
Click to expand...
Click to collapse
Search xda, its reported already in other threads.

Related

[Q] [LOLLIPOP] Phone calls broken with headphones only. Internal mic broken.

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.

Audio Issue Questions?

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:

Extremely low call volume

hello, I'm having trouble with call volume on my S8+ Korean model. All other sounds are normal but call volume is like a whisper. Normal phone calls and WhatsApp calls are impossible to hear, I have to turn on the speaker or connect headphone every time I want to make a call.
Im using Batman rom without any sound mods.
I've tried googling and asking around but non seems to have this problem. I was thinking it was a defective earpiece speaker but there is still sound.
Anyone has any idea, please advise.
P/s: I've also tried resetting
This may seem simplistic but I would go back to the stock ROM and if the issues goes away you know the problem is with the ROM, if not then the issue is with the phone, probably.
I have the same problem on stock. Think it happened after last update and that's a while ago now. See there are a lot of people with the same problem at the samsung forum. Still no fix though :/
Maybe there is a way to fix it if we root? Force the speaker levels up or something.

What Custom ROM that fixes Microphone Issue?

As we all know Pixels have this dreaded microphone issue. Sometimes it works, sometimes not. If you restart the phone, it temporary fix the problem and after few minutes/hours my mic doesn't respond again. I tried to flash different official rom released from https://developers.google.com/android/images but the issue is still there. I believe it's software issue because the hardware works. I'm now looking to root my phone and flash a custom rom, maybe they fixed the issue in their end.
I installed Sound Meter and Mic Tester to check once in while (you should too) if my mic is working. When I found that the mic don't respond the way it should, that's the time I restart my phone.
* Flashed different versions of: Nougat, Oreo, P (preview) ... but the issue is still there.
Can we list the Custom ROMs that fixes this annoying problem (is there any)?
Sound Meter(if mic is working)
https://photos.app.goo.gl/kcU0APX2pNPYjoG12
Sound Meter(No Response)
https://photos.app.goo.gl/a1lqNeyogTtuHRkE3
Mic Tester (if mic is working)
https://photos.app.goo.gl/K7oZYvSQDS2ndJHc2
Mic Tester (Flat)
https://photos.app.goo.gl/6BPoSryI3ECNJxwu1
chrizcrozz said:
As we all know Pixels have this dreaded microphone issue. Sometimes it works, sometimes are not. I tried to flash different official release from https://developers.google.com/android/images but the issue is still there. I believe it's software issue because the hardware works.
Can we list the Custom ROMs that fixes this annoying problem?
Click to expand...
Click to collapse
I had the problem in all oreo roms, but not in nougat or P. Been running the P preview since it was available and haven't had the issue once
jacobas92 said:
I had the problem in all oreo roms, but not in nougat or P. Been running the P preview since it was available and haven't had the issue once
Click to expand...
Click to collapse
Did you try to install Sound Meter and Mic Tester? If yes, is it stable (referring to mic Issue)?
chrizcrozz said:
Did you try to install Sound Meter and Mic Tester? If yes, is it stable (referring to mic Issue)?
Click to expand...
Click to collapse
No, I would just lose microphone functionality for a minute at a time, sometimes longer. It happened in phone calls a lot. I just thought my mic was going out but I'm glad I tried a few other roms before buying a new phone. I feel like my issue was far different from your current problems
If this was a software issue, everyone running android 8.1 would have this issue. This sounds like the audio codec manufacturing defect. Unless you have an app that is interfering with something, probably not software
That's weird,. I haven't encountered that issue not on stock but I never stayed on stock for long though as I flashed custom rom a couple of days after receiving my phone. Bought it new in March. I'm running Dirty Unicorns rom though, can be found from the link to Discord on my signature.
I'm definitely interested if you find anything. Installed the April update over the weekend and bam, no mic and random reboots. Factory reset didn't help. I would think it's firmware related since it happened immediately after the update, but idk. Both Sound Meter and Mic Tester show no response.
UPDATE:
I tried to load a custom ROM - Resurrection Remix 6
So far so good. I haven't experience the problem this day.
Usually, I restart my phone 6-8(or more) times a day just to temporary fix the microphone issue.
I will observe in a few days and update this asap.
UPDATE
Resurrection Remix 6.0 works great! I didn't have any problems! It seems fixes that microphone bug.
I have uptime of 36 hours and counting with out restarting my phone. I had few voice calls and few net calls (FB and Skype).
Super big thanks to all who's involved in making that project.
https://photos.app.goo.gl/60ABq4dUFnKNKAcE2
I installed Resurrection Remix 6 and I still have the same microphone issue. Can someone please confirm if by downgrading the problem will be fixed? Thank you.
chrizcrozz said:
UPDATE
Resurrection Remix 6.0 works great! I didn't have any problems! It seems fixes that microphone bug.
I have uptime of 36 hours and counting with out restarting my phone. I had few voice calls and few net calls (FB and Skype).
Super big thanks to all who's involved in making that project.
https://photos.app.goo.gl/60ABq4dUFnKNKAcE2
Click to expand...
Click to collapse
Do I need to downgrade before flashing Resurrection Remix 6.0?
I'm on 8.1.
jacobas92 said:
I had the problem in all oreo roms, but not in nougat or P. Been running the P preview since it was available and haven't had the issue once
Click to expand...
Click to collapse
Man, you can comfirm that you got no audio and microphone problems on android P?
If so, I will cry. :,)
zeth717 said:
Man, you can comfirm that you got no audio and microphone problems on android P?
If so, I will cry. :,)
Click to expand...
Click to collapse
problem persisting in Android P too..... i upgraded last night and works well for few hours, then today, starts again........
Thanks for the tip. Ever since I got the June 18 update (D1 android 8.1) I've had random reboots, mic and the odd speaker issue.
I rooted stock with twrp n magick no difference. Even b4 restoring apps. So this week have installed pixel dust. Such a great time BUT mic n speaker problems persist, and the random reboots have become complete crashes. Where I think my phone is bricked, but if you hold power long enough it reboots. That's where I'm at now. Barely got any apps installed, dealing with it. I think I'll give ressurection ROM a ago tomorrow. Thanks for the tip. I know easily when it's happening, because I use ok Google and voice typing ALOT.
I can't believe that only last month I was totally ignorant to this issue and loved my pixel a bit too much. Now it's like dancing with a dragon ?
Does anyone else have any more tips for dealing with this?
mattyyey said:
Thanks for the tip. Ever since I got the June 18 update (D1 android 8.1) I've had random reboots, mic and the odd speaker issue.
I rooted stock with twrp n magick no difference. Even b4 restoring apps. So this week have installed pixel dust. Such a great time BUT mic n speaker problems persist, and the random reboots have become complete crashes. Where I think my phone is bricked, but if you hold power long enough it reboots. That's where I'm at now. Barely got any apps installed, dealing with it. I think I'll give ressurection ROM a ago tomorrow. Thanks for the tip. I know easily when it's happening, because I use ok Google and voice typing ALOT.
I can't believe that only last month I was totally ignorant to this issue and loved my pixel a bit too much. Now it's like dancing with a dragon
Does anyone else have any more tips for dealing with this?
Click to expand...
Click to collapse
I was also pleasantly oblivious a week ago. And I've been running on the March 2018 security patch since...well...March. So I can confirm this issue isn't caused by the June (or April, as another hypothesized) security patch. I haven't updated because I've been using Magisk for root since day 1 (opted not to install twrp), and the one time I system-updated to March, it don't go smoothly with magisk.
My repeating symptoms:
Mic failure some number of hours after boot.
And yesterday (not sure if it's repeating):
Could not receive income phone calls
so I received a Hangouts call instead, and phone did not stop vibrating until the Hangouts call was finished.
Around the time these symptoms started I had:
1 never-before-seen phone brick while I wasn't looking at it. Picked up phone, black screen, no response. Held power button for ~10 seconds to reboot.
1 never-before-seen instance of super laggy scrolling. Freezing for a second before it would scroll. Rebooted to fix.
Claimed fixes:
some say uninstalling apps solved it
some say upgrading to P
some say replacing the motherboard
The frustrating part is not having any way to know what the problem is or what the solution is. And people are experiencing different symptoms, so we can't even be sure we are having the same problem.
This article https://9to5google.com/2018/02/08/google-lawsuit-pixel-defective-microphone/ explains the cause:
If you’ll recall, Google’s 2016 Pixel devices, the Pixel and Pixel XL, faced microphones issues not too long after launch. As Google explained in early 2017, this issue was attributed to “a hairline crack in the solder connection on the audio codec,” with a warranty replacement being the only reliable fix. Later on in the manufacturing process, Google refined this part of the device to reduce the chances of this problem occurring.
Obviously, that was a frustrating issue for Pixel users, as it essentially disabled all three microphones on the device. What made the problem worse, though, was that holding the device in a different way or even a change in temperature could make the problem come back after it had seemingly gone away.
Click to expand...
Click to collapse
Free Motherboard replacements are being offered http://piunikaweb.com/2018/05/03/untangling-google-og-pixel-motherboard-replacement-mess/ by UBreakIFix:
Google is providing free motherboard replacements, but only to those encountering bootloops due to microphone-related issues (lawsuit affect?). Some one who claims to be working for uBreakiFix have recently confirmed this on a Reddit thread discussing the matter.
Click to expand...
Click to collapse
abemore said:
I was also pleasantly oblivious a week ago. And I've been running on the March 2018 security patch since...well...March. So I can confirm this issue isn't caused by the June (or April, as another hypothesized) security patch. I haven't updated because I've been using Magisk for root since day 1 (opted not to install twrp), and the one time I system-updated to March, it don't go smoothly with magisk.
My repeating symptoms:
Mic failure some number of hours after boot.
And yesterday (not sure if it's repeating):
Could not receive income phone calls
so I received a Hangouts call instead, and phone did not stop vibrating until the Hangouts call was finished.
Around the time these symptoms started I had:
1 never-before-seen phone brick while I wasn't looking at it. Picked up phone, black screen, no response. Held power button for ~10 seconds to reboot.
1 never-before-seen instance of super laggy scrolling. Freezing for a second before it would scroll. Rebooted to fix.
Claimed fixes:
some say uninstalling apps solved it
some say upgrading to P
some say replacing the motherboard
The frustrating part is not having any way to know what the problem is or what the solution is. And people are experiencing different symptoms, so we can't even be sure we are having the same problem.
This article https://9to5google.com/2018/02/08/google-lawsuit-pixel-defective-microphone/ explains the cause:
Free Motherboard replacements are being offered http://piunikaweb.com/2018/05/03/untangling-google-og-pixel-motherboard-replacement-mess/ by UBreakIFix:
Click to expand...
Click to collapse
I never had bootloops but the mic and audio issue, with stockROM, pixel dust and CrDroid. Then I heard about the ubreakifix possibility and when to the next store and they changed the MB without hesitation. Since then it works like a charm. Just go there, they are very helpful. That's a hardware issue not a software one.
Long story short - the update triggers the behavior(s), but its actually a manufacturing fault. You can replace part or your full motherboard to fix it. I personally just flashed stock and took it back to EE and they replaced it no cost. I remembering reading its a common problem with a certain early batch of Pixels. I've lost the link but you can use your serial number to check if its an early version thats effected. Apparently its only effects less than 3% of phones but the problem looks bigger when i was searching lmfao.
Anyway software fixes might help, but ultimately its a hardware issue. Get it replaced. Yeah they sent me a new one with a locked bootloader so i have to start from scratch but thats better than living with the error.
mattyyey said:
Long story short - the update triggers the behavior(s), but its actually a manufacturing fault. You can replace part or your full motherboard to fix it. I personally just flashed stock and took it back to EE and they replaced it no cost. I remembering reading its a common problem with a certain early batch of Pixels. I've lost the link but you can use your serial number to check if its an early version thats effected. Apparently its only effects less than 3% of phones but the problem looks bigger when i was searching lmfao.
Anyway software fixes might help, but ultimately its a hardware issue. Get it replaced. Yeah they sent me a new one with a locked bootloader so i have to start from scratch but thats better than living with the error.
Click to expand...
Click to collapse
You're right. I ended up getting a free repair from uBreakifix. The guy said he wasn't allowed to tell me what he did to fix it. I noticed he had downgraded me from Android 9 to 7.1.2. I hoped that wasn't the secret fix. On closer examination, I noticed the serial number had changed, which means they replaced my motherboard...for free...on an out of warranty Pixel that I bought second hand. :good:

Audio & Mic issue

Sometimes i found that the audio and the mic of the phone is not working so in the call i cannot hear the other person and the other person is not hearing me. in music app when i play a song this error shown to me.
this problem appears without any reason and when i restart the phone.
Sometimes when i restart the phone again, this problem is fixed but many times not.
I have this problem on any roms and any kernels.
Has anyone ever had this problem?
What can i do?
after 1 year i still have this problem
Mh Tachi said:
after 1 year i still have this problem
Click to expand...
Click to collapse
I have also same phone but not any problem fees me just battery is fast dinay.
Btw what you do in your life you are doing job ?

Categories

Resources